OptiX iManager T2000 V200R007C03

Operation Guide for PTN NE Management

Issue Date

01 2009-06-30

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any assistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com

Website: Email:

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

Trademarks and Permissions

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

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

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX iManager T2000 Operation Guide for PTN NE Management

Contents

Contents
About This Document.....................................................................................................................1 1 Creating NEs, Links, and Topology Subnets........................................................................1-1
1.1 Creating NEs...................................................................................................................................................1-2 1.1.1 Creating NEs in Batches........................................................................................................................1-2 1.1.2 Creating a Single NE..............................................................................................................................1-4 1.1.3 Creating a Virtual NE.............................................................................................................................1-5 1.2 Configuring the NE Data.................................................................................................................................1-6 1.2.1 Replicating the NE Data.........................................................................................................................1-6 1.2.2 Uploading the NE Data..........................................................................................................................1-7 1.2.3 Configuring the Virtual NE Data...........................................................................................................1-8 1.3 Adding Boards.................................................................................................................................................1-8 1.4 Adding Sub-Boards.........................................................................................................................................1-9 1.5 Creating Links...............................................................................................................................................1-10 1.5.1 Creating Fibers for PTN Equipment Manually....................................................................................1-10 1.5.2 Automatically Creating Radio Links....................................................................................................1-12 1.5.3 Manually Creating Radio Links...........................................................................................................1-13 1.5.4 Creating DCN Communication Cable..................................................................................................1-13 1.6 Creating a Topology Subnet..........................................................................................................................1-14

2 Configuring Communications.................................................................................................2-1
2.1 Overview of the Inband DCN.........................................................................................................................2-2 2.2 Basic Concepts................................................................................................................................................2-3 2.3 Application of the Inband DCN......................................................................................................................2-4 2.4 Configuring an Inband DCN...........................................................................................................................2-4 2.4.1 Setting NE Communication Parameters.................................................................................................2-5 2.4.2 Setting the VLAN ID and Bandwidth Used by an Inband DCN...........................................................2-6 2.4.3 Setting the T2000 Access Parameters....................................................................................................2-6 2.4.4 Enabling the Port DCN..........................................................................................................................2-7 2.4.5 Enabling the Tunnel DCN......................................................................................................................2-8 2.5 Configuration Case of the Inband DCN..........................................................................................................2-8 2.5.1 Networking and Requirements...............................................................................................................2-9 2.5.2 Service Planning...................................................................................................................................2-10 2.5.3 Configuring an Inband DCN................................................................................................................2-13 Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. i

Contents

OptiX iManager T2000 Operation Guide for PTN NE Management 2.5.4 Configuring an IP Tunnel.....................................................................................................................2-16 2.5.5 Configuring an ML-PPP Link..............................................................................................................2-18 2.5.6 Configuring a Radio Link....................................................................................................................2-20

3 Configuring the NE Time.........................................................................................................3-1

3.1 Time Synchronization Schemes for the T2000 and NEs................................................................................3-2 3.2 Synchronizing the NE Time with the T2000 Server Automatically...............................................................3-2 3.3 Synchronizing the NE Time with the T2000 Server Manually.......................................................................3-3 3.4 Setting Time Localization on NEs..................................................................................................................3-3 3.4.1 Setting a Time Zone for an NE..............................................................................................................3-3 3.4.2 Setting DST on NEs...............................................................................................................................3-4

4 Configuring Clocks....................................................................................................................4-1
4.1 Setting the Frequency Selection Mode............................................................................................................4-3 4.2 Configuring the NE Clock Source..................................................................................................................4-3 4.3 Configuring the Clock Source Protection.......................................................................................................4-4 4.4 Configuring Switching Conditions for Clock Sources....................................................................................4-5 4.5 Configuring the Clock Source Reversion........................................................................................................4-5 4.6 Configuring the Phase-Locked Source for External Clock Output.................................................................4-6 4.7 Setting the Clock Source Quality....................................................................................................................4-7 4.8 Configuring the SSM Output..........................................................................................................................4-8 4.9 Switching a Clock Source...............................................................................................................................4-8 4.10 Setting the Attributes of the External Time Interface...................................................................................4-9 4.11 Configuring a Clock Domain......................................................................................................................4-10 4.12 Configuring an ACR Clock.........................................................................................................................4-11

5 PTP Clock.....................................................................................................................................5-1
5.1 Introduction to the PTP Clock.........................................................................................................................5-2 5.2 Basic Information............................................................................................................................................5-3 5.3 Application of the PTP Clock.........................................................................................................................5-7 5.4 Configuration Flow for the PTP Clock...........................................................................................................5-7 5.5 Configuring the PTP Clock.............................................................................................................................5-9 5.5.1 Setting the Frequency Selection Mode.................................................................................................5-10 5.5.2 Setting the PTP System Time...............................................................................................................5-11 5.5.3 Setting the PTP Clock Subnet..............................................................................................................5-11 5.5.4 Setting the Attributes of the External Time Interface..........................................................................5-12 5.5.5 Setting the PTP NE Attributes.............................................................................................................5-13 5.5.6 Creating the PTP Clock Port................................................................................................................5-14 5.5.7 Creating the PTP Clock Service...........................................................................................................5-14 5.5.8 Setting the PTP Packet Period..............................................................................................................5-17 5.5.9 Setting the PTP Clock Port Status........................................................................................................5-17 5.5.10 Setting the Cable Transmitting Wrap.................................................................................................5-19 5.5.11 Setting the Wait-to-Restore Time for the PTP Clock Source............................................................5-20 5.5.12 Setting the PTP Clock Source Priority...............................................................................................5-20 ii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

Contents

5.6 PTP Clock Configuration Case.....................................................................................................................5-21 5.6.1 Configuration Networking Diagram....................................................................................................5-21 5.6.2 Service Planning...................................................................................................................................5-22 5.6.3 Configuration Process (BC).................................................................................................................5-27 5.6.4 Configuration Process (TC).................................................................................................................5-30 5.6.5 Configuration Process (OC).................................................................................................................5-31

6 Configuring a TOP Clock.........................................................................................................6-1

6.1 TOP Clock Overview......................................................................................................................................6-2 6.2 Basic Information............................................................................................................................................6-2 6.3 TOP Clock Application...................................................................................................................................6-5 6.4 TOP Clock Configuration Flow......................................................................................................................6-6 6.5 Configuring a TOP Clock...............................................................................................................................6-8 6.5.1 Selecting a Differential Clock Source....................................................................................................6-9 6.5.2 Creating a TOP Clock Service...............................................................................................................6-9 6.5.3 Setting the Clock Source Priority Table...............................................................................................6-13 6.6 TOP Clock Configuration Example..............................................................................................................6-13 6.6.1 Configuration Networking Diagram....................................................................................................6-14 6.6.2 Service Planning...................................................................................................................................6-15 6.6.3 Creating a TOP Clock Service.............................................................................................................6-18

7 Configuring the Equipment-Level Protection......................................................................7-1

7.1 Configuring the Subcard TPS Protection........................................................................................................7-2 7.1.1 TPS Application.....................................................................................................................................7-2 7.1.2 Creating a TPS Protection Group of Sub-Boards...................................................................................7-2 7.1.3 Checking the Subcard TPS Status..........................................................................................................7-3 7.1.4 Performing a Subcard TPS.....................................................................................................................7-3 7.2 Configuring Board 1+1 Protection..................................................................................................................7-4 7.2.1 Board 1+1 Protection.............................................................................................................................7-5 7.2.2 Querying the Board 1+1 Protection Group............................................................................................7-5 7.2.3 Checking 1+1 Board Switching Status...................................................................................................7-5 7.2.4 Performing 1+1 Board Protection Switching.........................................................................................7-6 7.3 Configuration Case of the TPS........................................................................................................................7-6 7.3.1 Case Description....................................................................................................................................7-6 7.3.2 Configuration Process............................................................................................................................7-7

8 Configuring the Control Plane................................................................................................8-1

8.1 Basic Concepts................................................................................................................................................8-3 8.1.1 IGP-ISIS Protocol..................................................................................................................................8-3 8.1.2 OSPF Protocol........................................................................................................................................8-5 8.1.3 BGP Protocol..........................................................................................................................................8-7 8.1.4 MPLS-LDP Protocol..............................................................................................................................8-9 8.1.5 MPLS-RSVP Protocol..........................................................................................................................8-10 8.1.6 ARP Protocol........................................................................................................................................8-12 Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. iii

Contents

OptiX iManager T2000 Operation Guide for PTN NE Management

8.2 Configuring the IGP-ISIS Protocol...............................................................................................................8-14 8.2.1 Setting Node Attributes........................................................................................................................8-15 8.2.2 Setting Port Attributes..........................................................................................................................8-16 8.2.3 Configuring Parameters of Route Importing........................................................................................8-17 8.2.4 Querying the Link TE Information......................................................................................................8-18 8.3 Configuring the MPLS-LDP Protocol...........................................................................................................8-18 8.3.1 Creating MPLS-LDP Peer Entities......................................................................................................8-19 8.3.2 Configuring the MPLS-LDP Protocol..................................................................................................8-19 8.4 Configuring the MPLS-RSVP Protocol........................................................................................................8-20 8.5 Configuring the OSPF Protocol....................................................................................................................8-20 8.5.1 Setting Node Attributes........................................................................................................................8-21 8.5.2 Setting Port Attributes..........................................................................................................................8-21 8.5.3 Configuring Parameters of Route Importing........................................................................................8-22 8.5.4 Querying the Link TE Information......................................................................................................8-23 8.6 Configuring the MP-BGP..............................................................................................................................8-23 8.7 Configuring Static Routes.............................................................................................................................8-24 8.8 Configuring the Address Parse......................................................................................................................8-25

9 Configuring the QoS Policy.....................................................................................................9-1

9.1 Overview of the QoS.......................................................................................................................................9-3 9.2 Basic Concepts................................................................................................................................................9-4 9.2.1 DiffServ..................................................................................................................................................9-4 9.2.2 HQoS......................................................................................................................................................9-6 9.3 Application of the QoS....................................................................................................................................9-7 9.3.1 Tunnel-Based QoS................................................................................................................................. 9-8 9.3.2 QoS Policy..............................................................................................................................................9-8 9.4 QoS Configuration Flow.................................................................................................................................9-9 9.5 Configuring the DiffServ Domain.................................................................................................................9-11 9.5.1 Creating a DiffServ Domain................................................................................................................9-12 9.5.2 Modifying a DiffServ Domain.............................................................................................................9-14 9.5.3 Deleting a DiffServ Domain................................................................................................................9-15 9.6 Configuring the Port Policy...........................................................................................................................9-15 9.6.1 Creating the Port WRED Policy...........................................................................................................9-15 9.6.2 Creating the Port Policy.......................................................................................................................9-16 9.6.3 Modifying the Port Policy....................................................................................................................9-20 9.6.4 Deleting the Port Policy.......................................................................................................................9-20 9.7 Configuring the V-UNI Ingress Policy.........................................................................................................9-21 9.7.1 Creating the CAR Policy......................................................................................................................9-21 9.7.2 Creating the Service WRED Policy.....................................................................................................9-22 9.7.3 Creating the WFQ Scheduling Policy..................................................................................................9-23 9.7.4 Creating the V-UNI Ingress Policy......................................................................................................9-24 9.7.5 Modifying the V-UNI Ingress Policy...................................................................................................9-26 9.7.6 Querying the V-UNI Ingress Policy-Applied Object...........................................................................9-27 iv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

Contents

9.7.7 Deleting the V-UNI Ingress Policy......................................................................................................9-27 9.8 Configuring the V-UNI Egress Policy..........................................................................................................9-28 9.8.1 Creating the Service WRED Policy.....................................................................................................9-28 9.8.2 Creating the WFQ Scheduling Policy..................................................................................................9-29 9.8.3 Creating the V-UNI Egress Policy.......................................................................................................9-30 9.8.4 Modifying the V-UNI Egress Policy....................................................................................................9-32 9.8.5 Querying the V-UNI Egress Policy-Applied Object............................................................................9-32 9.8.6 Deleting the V-UNI Egress Policy.......................................................................................................9-33 9.9 Configuring the PW Policy...........................................................................................................................9-33 9.9.1 Creating the Service WRED Policy.....................................................................................................9-34 9.9.2 Creating the WFQ Scheduling Policy..................................................................................................9-34 9.9.3 Creating the PW Policy........................................................................................................................9-35 9.9.4 Modifying the PW Policy.....................................................................................................................9-37 9.9.5 Querying the PW Policy-Applied Object.............................................................................................9-37 9.9.6 Deleting the PW Policy........................................................................................................................9-38 9.10 Configuring the QinQ Policy......................................................................................................................9-38 9.10.1 Creating the Service WRED Policy...................................................................................................9-39 9.10.2 Creating the WFQ Scheduling Policy................................................................................................9-39 9.10.3 Creating the QinQ Policy...................................................................................................................9-40 9.10.4 Modifying the QinQ Policy................................................................................................................9-42 9.10.5 Querying the QinQ Policy-Applied Object........................................................................................9-42 9.10.6 Deleting the QinQ Policy...................................................................................................................9-43 9.11 Configuring the ATM CoS Mapping..........................................................................................................9-43 9.12 Configuring the ATM Policy......................................................................................................................9-44 9.12.1 Creating the ATM Policy...................................................................................................................9-44 9.12.2 Modifying the ATM Policy................................................................................................................9-45 9.12.3 Querying the ATM Policy-Applied Object........................................................................................9-46 9.12.4 Deleting the ATM Policy...................................................................................................................9-46 9.13 Applying a QoS Policy................................................................................................................................9-47 9.14 QoS Configuration Case of the ATM Service ...........................................................................................9-47 9.14.1 Case Description................................................................................................................................9-48 9.14.2 Configuration Flow............................................................................................................................9-50 9.15 QoS Configuration Case of the Ethernet Service........................................................................................9-54 9.15.1 Case Description................................................................................................................................9-54 9.15.2 Configuration Flow............................................................................................................................9-56

10 Configuring Interfaces..........................................................................................................10-1
10.1 Configuring SDH Interfaces........................................................................................................................10-6 10.1.1 Setting the General Attributes of SDH Interfaces..............................................................................10-8 10.1.2 Setting the Layer 2 Attributes of SDH Interfaces..............................................................................10-9 10.1.3 Setting the Layer 3 Attributes of SDH Interfaces............................................................................10-10 10.1.4 Setting the Advanced Attributes of SDH Interfaces........................................................................10-11 10.1.5 Setting the VC12 Frame Format and Frame Mode..........................................................................10-11 Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. v

Contents

OptiX iManager T2000 Operation Guide for PTN NE Management 10.1.6 Querying the Running Status of PPP...............................................................................................10-12 10.1.7 Resetting the PPP.............................................................................................................................10-12

10.2 Configuring PDH Interfaces......................................................................................................................10-13 10.2.1 Setting General Attributes of PDH Interfaces..................................................................................10-15 10.2.2 Setting the Layer 3 Attributes of PDH Interfaces............................................................................10-15 10.2.3 Setting the Advanced Attributes of PDH Interfaces........................................................................10-16 10.2.4 Querying the Running Status of PPP...............................................................................................10-17 10.2.5 Resetting the PPP.............................................................................................................................10-17 10.3 Configuring Ethernet Interfaces................................................................................................................10-18 10.3.1 Setting the General Attributes of Ethernet Interfaces......................................................................10-20 10.3.2 Setting the Layer 2 Attributes of Ethernet Interfaces.......................................................................10-21 10.3.3 Setting the Layer 3 Attributes of an Ethernet Interface....................................................................10-21 10.3.4 Setting the Advanced Attributes of Ethernet Interfaces...................................................................10-22 10.3.5 Configuring Flow Control................................................................................................................10-23 10.4 Configuring ADSL Interfaces...................................................................................................................10-23 10.4.1 Process of Configuring an ADSL Interface.....................................................................................10-23 10.4.2 Setting the General Attributes of an ADSL Interface......................................................................10-25 10.4.3 Configuring the VPI/VCI of an ADSL Interface.............................................................................10-25 10.5 Configuring G.SHDSL Interfaces.............................................................................................................10-26 10.5.1 Application of the G.SHDSL Interface............................................................................................10-27 10.5.2 Process of Configuring a G.SHDSL Interface.................................................................................10-29 10.5.3 Setting the BIS Mode of a G.SHDSL Interface...............................................................................10-35 10.5.4 Setting the General Attributes of G.SHDSL Interfaces...................................................................10-35 10.5.5 Setting the Bound Mode for a G.SHDSL Interface.........................................................................10-36 10.5.6 Querying the EFM Bound Group of a G.SHDSL Interface.............................................................10-37 10.5.7 Configuring an ATM Bound Group.................................................................................................10-38 10.5.8 Configuring an IMA Bound Group..................................................................................................10-39 10.6 Configuring Microwave Interfaces...........................................................................................................10-40 10.6.1 Setting the General Attributes of Microwave Interfaces..................................................................10-42 10.6.2 Setting the IF Attributes of Microwave Interfaces...........................................................................10-43 10.6.3 Setting the Layer 2 Attributes of Microwave Interfaces..................................................................10-43 10.6.4 Setting the Layer 3 Attributes of Microwave Interfaces..................................................................10-44 10.6.5 Setting the Advanced Attributes of Microwave Interfaces..............................................................10-45 10.6.6 Setting the Parameters of ODU Ports...............................................................................................10-45 10.7 Configuring Serial Interfaces....................................................................................................................10-47 10.7.1 Creating Serial Interfaces.................................................................................................................10-48 10.7.2 Setting the General Attributes of a Serial Interface.........................................................................10-49 10.7.3 Setting the Layer 3 Attributes of Serial Interfaces...........................................................................10-50 10.7.4 Querying the Running Status of PPP...............................................................................................10-51 10.7.5 Resetting the PPP.............................................................................................................................10-51 10.8 Configuring ML-PPP................................................................................................................................10-52 10.8.1 Overview of the ML-PPP.................................................................................................................10-54 vi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

Contents

10.8.2 Basic Concepts.................................................................................................................................10-54 10.8.3 ML-PPP Application........................................................................................................................10-55 10.8.4 Creating MP Groups.........................................................................................................................10-56 10.8.5 Configuring Member Interfaces of MP Groups...............................................................................10-57 10.9 Configuring an Ethernet Virtual Interface.................................................................................................10-58 10.9.1 Application of the Ethernet Virtual Interfaces.................................................................................10-59 10.9.2 Process of Configuring an Ethernet Virtual Interface......................................................................10-60 10.9.3 Setting the General Attributes of Ethernet Virtual Interfaces..........................................................10-62 10.9.4 Creating VLAN Sub Interface..........................................................................................................10-63 10.9.5 Setting the Layer 3 Attributes of Ethernet Virtual Interfaces..........................................................10-64 10.10 Configuring an IMA Group.....................................................................................................................10-65 10.10.1 Configuring Bound Channels in an ATM IMA Group..................................................................10-66 10.10.2 Configuring Attributes of an ATM IMA Group............................................................................10-68 10.10.3 Configuring the ATM Interfaces....................................................................................................10-69 10.10.4 Querying IMA Group States..........................................................................................................10-75 10.10.5 Querying IMA Link States.............................................................................................................10-75 10.10.6 Resetting an IMA Group................................................................................................................10-76 10.10.7 Modifying an IMA Group..............................................................................................................10-76 10.10.8 Deleting an IMA Group.................................................................................................................10-77 10.11 Configuring the V-UNI Group................................................................................................................10-77 10.11.1 Creating a V-UNI Group................................................................................................................10-78 10.11.2 Modifying a V-UNI Group............................................................................................................10-79 10.11.3 Deleting a V-UNI Group................................................................................................................10-80 10.12 ML-PPP Configuration Case...................................................................................................................10-80 10.12.1 Case Description............................................................................................................................10-81 10.12.2 Service Planning.............................................................................................................................10-83 10.12.3 Configuration Flow........................................................................................................................10-83 10.13 Configuring Environment Monitor Interfaces.........................................................................................10-88 10.14 Setting Automatic Laser Shutdown.........................................................................................................10-88

11 Configuring the IF 1+1 Protection......................................................................................11-1

11.1 Basic Concepts of the 1+1 HSB..................................................................................................................11-2 11.1.1 Description of the 1+1 HSB...............................................................................................................11-2 11.1.2 Realization Principle..........................................................................................................................11-3 11.2 Basic Concepts of the 1+1 FD.....................................................................................................................11-5 11.2.1 Description of the 1+1 FD..................................................................................................................11-5 11.2.2 Realization Principle..........................................................................................................................11-6 11.3 Basic Concepts of the 1+1 SD.....................................................................................................................11-8 11.3.1 Description of the 1+1 SD..................................................................................................................11-9 11.3.2 Realization Principle..........................................................................................................................11-9 11.4 Creating IF 1+1 Protection........................................................................................................................11-12

12 Configuring a Radio Link.....................................................................................................12-1

12.1 Configuring the IF/ODU Information of a Radio Link...............................................................................12-2 Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii

Contents

OptiX iManager T2000 Operation Guide for PTN NE Management

12.2 Creating IF 1+1 Protection..........................................................................................................................12-3 12.3 Hop Management........................................................................................................................................12-4 12.3.1 Introduction to the Hop Management................................................................................................12-4 12.3.2 Setting the IF/RF Information............................................................................................................12-5

13 Configuring an MPLS Tunnel.............................................................................................13-1

13.1 Basic Concepts............................................................................................................................................13-3 13.1.1 MPLS and MPLS Tunnel...................................................................................................................13-3 13.1.2 Application of the MPLS Tunnel.......................................................................................................13-3 13.2 MPLS Tunnel Configuration Flow.............................................................................................................13-5 13.3 Configuring an MPLS Tunnel by Trail.......................................................................................................13-7 13.3.1 Creating a Dynamic MPLS Tunnel and the FRR Protection by Using the Trail Function................13-8 13.3.2 Creating a Static MPLS Tunnel by Using the Trail Function..........................................................13-13 13.3.3 Deleting a Dynamic MPLS Tunnel by Trail....................................................................................13-15 13.3.4 Deleting a Static MPLS Tunnel by Trail..........................................................................................13-15 13.4 Configuring an MPLS Tunnel on a Per-NE Basis....................................................................................13-15 13.4.1 Configuring Basic Attributes of the MPLS......................................................................................13-16 13.4.2 Creating an MPLS Tunnel on a Per-NE Basis.................................................................................13-16 13.4.3 Modifying the Interface of the Static Unicast MPLS Tunnel..........................................................13-18 13.4.4 Deleting an MPLS Tunnel on a Per-NE Basis.................................................................................13-18 13.5 Querying the Tunnel Label Information...................................................................................................13-19 13.6 Configuration Case of the Dynamic MPLS Tunnel..................................................................................13-19 13.6.1 Networking Diagram........................................................................................................................13-19 13.6.2 Service Planning...............................................................................................................................13-21 13.6.3 Creating a Dynamic MPLS Tunnel..................................................................................................13-22 13.7 Configuration Case of the Static MPLS Tunnel........................................................................................13-28 13.7.1 Networking Diagram........................................................................................................................13-29 13.7.2 Service Planning...............................................................................................................................13-30 13.7.3 Creating a Static MPLS Tunnel by Using the Trail Function..........................................................13-32 13.7.4 Configuring a Static MPLS Tunnel on a Per-NE Basis...................................................................13-37

14 Configuring an IP Tunnel....................................................................................................14-1
14.1 IP Tunnel.....................................................................................................................................................14-2 14.2 Configuring a UDP PW Port.......................................................................................................................14-2 14.3 Creating IP Tunnels.....................................................................................................................................14-3 14.4 Deleting IP Tunnels.....................................................................................................................................14-3 14.5 IP Tunnel Configuration Example..............................................................................................................14-4 14.5.1 Configuration Networking Diagram..................................................................................................14-4 14.5.2 Service Planning.................................................................................................................................14-6 14.5.3 Creating an IP Tunnel on a Per-NE Basis..........................................................................................14-7

15 Configuring a GRE Tunnel..................................................................................................15-1

15.1 GRE Tunnel.................................................................................................................................................15-2 15.2 Creating GRE Tunnels................................................................................................................................15-2 viii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

Contents

15.3 Deleting GRE Tunnels................................................................................................................................15-3 15.4 GRE Tunnel Configuration Example..........................................................................................................15-3 15.4.1 Configuration Networking Diagram..................................................................................................15-4 15.4.2 Service Planning.................................................................................................................................15-5 15.4.3 Creating a GRE Tunnel on a Per-NE Basis........................................................................................15-7

16 Configuring Network Level Protection.............................................................................16-1

16.1 Configuring a Linear MSP..........................................................................................................................16-3 16.1.1 MSP Protection Switching Priority....................................................................................................16-3 16.1.2 Linear MSP........................................................................................................................................16-5 16.1.3 Configuring Linear MSP....................................................................................................................16-6 16.1.4 Checking Linear MSP Switching Status............................................................................................16-8 16.1.5 Performing Linear MSP Switching....................................................................................................16-8 16.2 Configuring MPLS Tunnel Protection........................................................................................................16-9 16.2.1 Introduction to MPLS APS..............................................................................................................16-10 16.2.2 Basic Concepts.................................................................................................................................16-13 16.2.3 MPLS APS Application...................................................................................................................16-15 16.2.4 Creating an MPLS Tunnel Protection Group...................................................................................16-16 16.2.5 Perform MPLS Tunnel Protection Switching..................................................................................16-18 16.2.6 Deleting an MPLS Tunnel Protection Group...................................................................................16-19 16.3 Configuring Offload Protection................................................................................................................16-19 16.3.1 Introduction to Offload Protection...................................................................................................16-20 16.3.2 Creating a BFD Session...................................................................................................................16-22 16.3.3 Configuring the Offload Protection..................................................................................................16-23 16.4 Configuring FRR Protection for MPLS Tunnel........................................................................................16-24 16.4.1 Overview of the FRR.......................................................................................................................16-25 16.4.2 Application of the FRR....................................................................................................................16-27 16.4.3 Creating the FRR Protection for MPLS Tunnels.............................................................................16-29 16.4.4 Re-Optimized MPLS Tunnel After the FRR Protection..................................................................16-29 16.5 Configuring LAG......................................................................................................................................16-30 16.5.1 Overview of the LAG.......................................................................................................................16-31 16.5.2 LAG Application..............................................................................................................................16-31 16.5.3 Creating an LAG..............................................................................................................................16-32 16.5.4 Configuring the Port Priority............................................................................................................16-33 16.5.5 Querying Port LACP Packet Statistics.............................................................................................16-34 16.5.6 Querying Detailed LAG Information...............................................................................................16-34 16.5.7 Deleting LAGs.................................................................................................................................16-35 16.6 MPLS APS Configuration Case................................................................................................................16-35 16.6.1 Case Description..............................................................................................................................16-36 16.6.2 Configuration Flow..........................................................................................................................16-37 16.7 Configuration Case of the Offload Protection Group...............................................................................16-40 16.7.1 Configuration Networking Diagram................................................................................................16-40 16.7.2 Service Planning...............................................................................................................................16-41 Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix

Contents

OptiX iManager T2000 Operation Guide for PTN NE Management 16.7.3 Configuration Process......................................................................................................................16-42

16.8 FRR Configuration Case...........................................................................................................................16-45 16.8.1 Case Description..............................................................................................................................16-45 16.8.2 Configuration Flow..........................................................................................................................16-48 16.9 Configuration Case of the LAG................................................................................................................16-54 16.9.1 Case Description..............................................................................................................................16-54 16.9.2 Service Planning...............................................................................................................................16-55 16.9.3 Configuration Process......................................................................................................................16-56

17 Configuring an MPLS PW....................................................................................................17-1

17.1 Querying an MPLS PW...............................................................................................................................17-2 17.2 Querying QoS-Related Parameters of an MPLS PW..................................................................................17-2 17.3 Querying the PW Label Information...........................................................................................................17-2

18 Configuring CES Services....................................................................................................18-1

18.1 CES Service Type.......................................................................................................................................18-3 18.2 Configuration Flow of CES Services..........................................................................................................18-6 18.3 Configuring the CES Service by Using the Trail Function.........................................................................18-9 18.3.1 Creating a UNI-UNI CES Service by Using the Trail Function......................................................18-10 18.3.2 Creating a UNI-NNI CES Service by Using the Trail Function......................................................18-11 18.3.3 Deleting a CES Service by Using the Trail Function.......................................................................18-13 18.4 Configuring a CES Service on a Per-NE Basis.........................................................................................18-14 18.4.1 Creating a UNI-UNI CES Service on a Per-NE Basis.....................................................................18-14 18.4.2 Creating a UNI-NNI CES Service on a Per-NE Basis.....................................................................18-15 18.4.3 Deleting a CES Service on a Per-NE Basis......................................................................................18-18 18.5 Managing the CES Services......................................................................................................................18-18 18.5.1 Searching the CES Services.............................................................................................................18-19 18.5.2 Filtering the CES Services...............................................................................................................18-19 18.5.3 Querying the Node Information of the CES Service........................................................................18-20 18.5.4 Browsing the CES Service Alarms..................................................................................................18-20 18.5.5 Browsing the CES Service Performance..........................................................................................18-21 18.6 Configuration Case of the UNI-UNI CES Service....................................................................................18-21 18.6.1 Case Description..............................................................................................................................18-21 18.6.2 Service Planning...............................................................................................................................18-22 18.6.3 Configuring CES Services by Using the Trail Function..................................................................18-23 18.6.4 Configuring CES Services on a Per-NE Basis.................................................................................18-26 18.6.5 Checking the Correctness of the Service Configuration..................................................................18-29 18.7 Configuration Case of the UNI-NNI CES Service....................................................................................18-30 18.7.1 Case Description..............................................................................................................................18-30 18.7.2 Service Planning...............................................................................................................................18-32 18.7.3 Configuring CES Services by Using the Trail Function..................................................................18-36 18.7.4 Configuring CES Services on a Per-NE Basis.................................................................................18-44 18.7.5 Checking the Correctness of the Service Configuration..................................................................18-55

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

Contents

19 Configuring an ATM Service...............................................................................................19-1

19.1 Basic Concepts............................................................................................................................................19-3 19.1.1 IMA....................................................................................................................................................19-3 19.1.2 Application of the IMA......................................................................................................................19-4 19.1.3 ATM Service......................................................................................................................................19-4 19.1.4 ATM Traffic.......................................................................................................................................19-6 19.2 ATM Service Configuration Flow..............................................................................................................19-9 19.3 Configuring an IMA Group.......................................................................................................................19-14 19.3.1 Configuring Bound Channels in an ATM IMA Group....................................................................19-16 19.3.2 Configuring Attributes of an ATM IMA Group..............................................................................19-17 19.3.3 Configuring the ATM Interfaces......................................................................................................19-18 19.3.4 Querying IMA Group States............................................................................................................19-24 19.3.5 Querying IMA Link States...............................................................................................................19-24 19.3.6 Resetting an IMA Group..................................................................................................................19-25 19.3.7 Modifying an IMA Group................................................................................................................19-25 19.3.8 Deleting an IMA Group...................................................................................................................19-26 19.4 Configuring the ATM Service on a Route Basis.......................................................................................19-26 19.4.1 Creating ATM Services by Using the Trail Function......................................................................19-27 19.4.2 Modifying the ATM Service by Using the Trail Function...............................................................19-30 19.4.3 Deleting ATM Services in Trail Mode............................................................................................19-31 19.5 Configuring the ATM Service on a Per-NE Basis....................................................................................19-32 19.5.1 Creating ATM Services on a Per-NE Basis.....................................................................................19-32 19.5.2 Modifying ATM Services on a Per-NE Basis..................................................................................19-36 19.5.3 Deleting ATM Services on a Per-NE Basis.....................................................................................19-37 19.6 Managing ATM Services..........................................................................................................................19-37 19.6.1 Searching for ATM Services............................................................................................................19-38 19.6.2 Filtering ATM Services....................................................................................................................19-39 19.6.3 Querying Node Information of an ATM Service.............................................................................19-39 19.6.4 Modifying a PW Carrying ATM Services.......................................................................................19-39 19.6.5 Browsing Alarms Related to an ATM Service.................................................................................19-40 19.6.6 Browsing Performance Data Related to an ATM Service...............................................................19-40 19.7 IMA Configuration Example....................................................................................................................19-40 19.7.1 Case Description..............................................................................................................................19-41 19.7.2 Service Planning...............................................................................................................................19-41 19.7.3 Configuration Procedure..................................................................................................................19-43 19.8 Configuration Case of the UNI-UNI ATM Service..................................................................................19-46 19.8.1 Networking Diagram........................................................................................................................19-46 19.8.2 Service Planning...............................................................................................................................19-47 19.8.3 Configuring an ATM Service on a Route Basis...............................................................................19-48 19.8.4 Configuring an ATM Service on a Per-NE Basis............................................................................19-53 19.8.5 Verifying Correctness of Service Configuration..............................................................................19-58 19.9 Configuration Case of the UNIs-NNI ATM Service................................................................................19-59 Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xi

Contents

OptiX iManager T2000 Operation Guide for PTN NE Management 19.9.1 Networking Diagram........................................................................................................................19-59 19.9.2 Service Planning...............................................................................................................................19-60 19.9.3 Configuring an ATM Service on a Route Basis...............................................................................19-63 19.9.4 Configuring an ATM Service on a Per-NE Basis............................................................................19-75 19.9.5 Verifying the Correctness of Service Configuration........................................................................19-94

20 Configuring an Ethernet Service.........................................................................................20-1

20.1 Basic Concepts............................................................................................................................................20-3 20.1.1 E-Line Service....................................................................................................................................20-3 20.1.2 E-LAN Service...................................................................................................................................20-6 20.1.3 E-AGGR Service................................................................................................................................20-7 20.1.4 V-UNI Group.....................................................................................................................................20-8 20.2 Configuring an E-Line Service...................................................................................................................20-9 20.2.1 Configuration Flow for the E-Line Service......................................................................................20-10 20.2.2 Creating a UNI-UNI E-Line Service by Using the Trail Function..................................................20-17 20.2.3 Creating a UNI-NNI E-Line Service by Using the Trail Function..................................................20-18 20.2.4 Creating a UNI-UNI E-Line Service on a Per-NE Basis.................................................................20-20 20.2.5 Creating a UNI-NNI E-Line Service Carried by a Port...................................................................20-22 20.2.6 Creating a UNI-NNI E-Line Service Carried by a PW by Using the Trail Function.......................20-23 20.2.7 Creating a QinQ Link.......................................................................................................................20-26 20.2.8 Creating a UNI-NNI E-Line Service Carried by the QinQ Link.....................................................20-26 20.2.9 Modifying an E-Line Service on a Per-NE Basis............................................................................20-27 20.2.10 Deleting an E-Line Service on a Per-NE Basis..............................................................................20-28 20.2.11 Modifying an E-Line Service by Using the Trail Function...........................................................20-29 20.2.12 Deleting an E-Line Service by Using the Trail Function...............................................................20-29 20.3 Configuring an E-LAN Service.................................................................................................................20-30 20.3.1 Configuration Flow for E-LAN Service...........................................................................................20-31 20.3.2 Creating a QinQ Link.......................................................................................................................20-32 20.3.3 Creating an E-LAN Service.............................................................................................................20-33 20.3.4 Managing the Blacklist.....................................................................................................................20-37 20.3.5 Setting the Broadcast Storm Suppression........................................................................................20-38 20.3.6 Modifying E-LAN Service...............................................................................................................20-39 20.3.7 Deleting E-LAN Service..................................................................................................................20-40 20.4 Configuring an E-AGGR Service.............................................................................................................20-40 20.4.1 Configuration Flow for the E-AGGR Service..................................................................................20-41 20.4.2 Creating an E-AGGR Service on a Per-NE Basis............................................................................20-42 20.4.3 Modifying an E-AGGR Service on a Per-NE Basis........................................................................20-43 20.4.4 Deleting an E-AGGR Service on a Per-NE Basis............................................................................20-44 20.5 L2VPN Service Management....................................................................................................................20-45 20.5.1 Searching for L2VPN Services........................................................................................................20-45 20.5.2 Filtering L2VPN Services................................................................................................................20-46 20.5.3 Modifying the Attributes of an L2VPN Service..............................................................................20-47 20.5.4 Configuring a UNI...........................................................................................................................20-48 xii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

Contents

20.5.5 Configuring UNI QoS......................................................................................................................20-48 20.5.6 Configuring a PW.............................................................................................................................20-49 20.5.7 Configuring PW QoS.......................................................................................................................20-49 20.5.8 Viewing the Alarms Related to an L2VPN Service.........................................................................20-50 20.5.9 Viewing the Performance Data Related to an L2VPN Service........................................................20-50 20.6 Configuring the V-UNI Group..................................................................................................................20-51 20.6.1 Creating a V-UNI Group..................................................................................................................20-51 20.6.2 Modifying a V-UNI Group..............................................................................................................20-52 20.6.3 Deleting a V-UNI Group..................................................................................................................20-53 20.7 Configuration Case of the UNI-UNI E-Line Service................................................................................20-53 20.7.1 Networking Diagram........................................................................................................................20-54 20.7.2 Service Planning...............................................................................................................................20-55 20.7.3 Configuring the E-Line Service at an NE........................................................................................20-56 20.8 Configuration Case of the UNI-NNI E-Line Service Carried by Ports.....................................................20-59 20.8.1 Networking Diagram........................................................................................................................20-60 20.8.2 Service Planning...............................................................................................................................20-60 20.8.3 Configuring the E-Line Service at the Source NE...........................................................................20-61 20.8.4 Verifying the Correctness of Service Configuration........................................................................20-63 20.9 Configuration Case of the UNI-NNI E-Line Service Carried by the PW.................................................20-66 20.9.1 Case Description..............................................................................................................................20-66 20.9.2 Service Planning...............................................................................................................................20-67 20.9.3 Configuring the E-Line Service of the NE.......................................................................................20-69 20.9.4 Verifying the Correctness of Service Configuration........................................................................20-74 20.10 Configuration Case of the UNI-NNI E-Line Service Carried by the QinQ Link....................................20-77 20.10.1 Case Description............................................................................................................................20-77 20.10.2 Service Planning.............................................................................................................................20-78 20.10.3 Configuring the E-Line Service ....................................................................................................20-80 20.10.4 Verifying the Correctness of Service Configuration......................................................................20-83 20.11 Configuration Case of the E-LAN Service.............................................................................................20-86 20.11.1 Case Description............................................................................................................................20-86 20.11.2 Configuring E-LAN Service for the NE........................................................................................20-89 20.12 Configuration Case of the E-AGGR Service..........................................................................................20-92 20.12.1 Case Description............................................................................................................................20-92 20.12.2 Configuring a UNIs-NNI E-AGGR Service for NEs.....................................................................20-96 20.12.3 Configuring an NNIs-UNI E-AGGR Service for NEs...................................................................20-97

21 Configuring an L3VPN Service...........................................................................................21-1

21.1 Introduction to L3VPN................................................................................................................................21-3 21.2 Basic Concepts............................................................................................................................................21-4 21.2.1 Basic Concepts of L3VPN.................................................................................................................21-4 21.2.2 MP-BGP...........................................................................................................................................21-10 21.2.3 Label Allocation of MP-BGP...........................................................................................................21-15 21.2.4 VPN Route Selection on PEs...........................................................................................................21-16 Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiii

Contents

OptiX iManager T2000 Operation Guide for PTN NE Management 21.2.5 Advertisement of VPNv4 Routes.....................................................................................................21-17 21.2.6 Route Advertisement of a Basic BGP/MPLS VPN.........................................................................21-18 21.2.7 Packet Forwarding in a Basic BGP/MPLS VPN.............................................................................21-20

21.3 Application of the L3VPN........................................................................................................................21-21 21.4 L3VPN Service Configuration Flow.........................................................................................................21-25 21.5 Configuring an L3VPN Service................................................................................................................21-27 21.5.1 Creating an L3VPN Service.............................................................................................................21-28 21.5.2 Deleting an L3VPN Service.............................................................................................................21-34 21.6 L3VPN Service Management....................................................................................................................21-34 21.6.1 Synchronizing an L3VPN Service...................................................................................................21-35 21.6.2 Filtering the L3VPN Services..........................................................................................................21-35 21.6.3 Configuring a PE Node....................................................................................................................21-36 21.6.4 Configuring a UNI Interface............................................................................................................21-37 21.6.5 Configuring the Tunnel Selection Policy.........................................................................................21-37 21.6.6 Configuring RT Rules......................................................................................................................21-39 21.6.7 Configuring the ARP Table..............................................................................................................21-40 21.6.8 Querying the FIB Table....................................................................................................................21-41 21.6.9 Querying the Routing Table.............................................................................................................21-42 21.6.10 Viewing the Alarms Related to an L3VPN Service.......................................................................21-43 21.6.11 Viewing the Performance Data Related to an L3VPN Service......................................................21-44 21.7 Configuration Example of an Intranet VPN Service.................................................................................21-44 21.7.1 Configuration Networking Diagram................................................................................................21-45 21.7.2 Service Planning...............................................................................................................................21-46 21.7.3 Configuration Process......................................................................................................................21-49 21.8 Configuration Example of an Extranet VPN Service................................................................................21-60 21.8.1 Configuration Networking Diagram................................................................................................21-60 21.8.2 Service Planning...............................................................................................................................21-61 21.8.3 Configuration Process......................................................................................................................21-63 21.9 Configuration Example of a Hub&Spoke VPN Service...........................................................................21-71 21.9.1 Configuration Networking Diagram................................................................................................21-71 21.9.2 Service Planning...............................................................................................................................21-72 21.9.3 Configuration Process......................................................................................................................21-74

22 Configuring the IGMP Snooping.......................................................................................22-1

22.1 Overview of the IGMP Snooping................................................................................................................22-3 22.2 Basic Concepts............................................................................................................................................22-4 22.3 Application of the IGMP Snooping............................................................................................................ 22-6 22.4 Configuring the IGMP Snooping Parameters............................................................................................. 22-7 22.5 Configuring the Router Management..........................................................................................................22-8 22.6 Configuring the Route Member Port Management.....................................................................................22-9 22.7 Configuring the Packet Statistics..............................................................................................................22-10 22.8 IGMP Snooping Configuration Case........................................................................................................22-11 22.8.1 Case Description..............................................................................................................................22-11 xiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

Contents

22.8.2 Configuration Flow..........................................................................................................................22-13

23 Configuring the MSTP..........................................................................................................23-1

23.1 Overview of the MSTP...............................................................................................................................23-3 23.2 Basic Concepts............................................................................................................................................23-6 23.3 MSTP Application.......................................................................................................................................23-8 23.4 Configuring a Port Group............................................................................................................................23-9 23.5 Configuring Bridge Parameters...................................................................................................................23-9 23.6 Configuring CIST and MSTI Parameters..................................................................................................23-10 23.7 Querying the CIST Running Information.................................................................................................23-11 23.8 Configuring Protocol Transfer for Ports...................................................................................................23-11 23.9 Querying the MSTI Running Information................................................................................................23-12 23.10 MSTP Configuration Case......................................................................................................................23-12 23.10.1 Case Description............................................................................................................................23-12 23.10.2 Configuration Flow........................................................................................................................23-14

24 Configuring Services for the Offload Solution................................................................24-1

24.1 Basic Concepts............................................................................................................................................24-2 24.2 Service Configuration Flow for the Offload Solution.................................................................................24-5 24.3 ATM-Based Service Configuration Case....................................................................................................24-8 24.3.1 Case Description................................................................................................................................24-9 24.3.2 Configuration Process......................................................................................................................24-16 24.4 ETH-Based Service Configuration Case...................................................................................................24-20 24.4.1 Case Description..............................................................................................................................24-21 24.4.2 Configuration Process......................................................................................................................24-28 24.5 IP-Based Service Configuration Case.......................................................................................................24-32 24.5.1 Case Description..............................................................................................................................24-32 24.5.2 Configuration Process......................................................................................................................24-39

25 OAM Management................................................................................................................25-1
25.1 Configuring the Ethernet Port OAM...........................................................................................................25-2 25.1.1 Overview of the Ethernet Port OAM.................................................................................................25-2 25.1.2 Basic Concepts...................................................................................................................................25-3 25.1.3 Application of the Ethernet Port OAM..............................................................................................25-4 25.1.4 Querying the Remote OAM Parameters............................................................................................25-4 25.1.5 Setting the OAM Parameters..............................................................................................................25-5 25.1.6 Setting OAM Error Frame Monitor Parameters.................................................................................25-5 25.1.7 Starting the Remote Loopback...........................................................................................................25-6 25.2 Configuring the Ethernet Service OAM......................................................................................................25-7 25.2.1 Overview of the Ethernet Service OAM............................................................................................25-8 25.2.2 Basic Concepts...................................................................................................................................25-9 25.2.3 Application of the Ethernet Service OAM.......................................................................................25-10 25.2.4 Creating an MD................................................................................................................................25-12 25.2.5 Creating an MA................................................................................................................................25-13 Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xv

Contents

OptiX iManager T2000 Operation Guide for PTN NE Management 25.2.6 Creating a MEP Maintenance Point.................................................................................................25-14 25.2.7 Adding a Remote MEP of the MA...................................................................................................25-15 25.2.8 Creating a Maintenance Intermediate Point.....................................................................................25-16 25.2.9 Performing a Continuity Check........................................................................................................25-17 25.2.10 Performing an LB Test...................................................................................................................25-17 25.2.11 Performing an LT Test...................................................................................................................25-18

25.3 Configuring the MPLS OAM....................................................................................................................25-19 25.3.1 Overview of the MPLS OAM..........................................................................................................25-20 25.3.2 Basic Concepts.................................................................................................................................25-20 25.3.3 Application of the MPLS OAM.......................................................................................................25-22 25.3.4 Enabling the MPLS OAM of a Tunnel............................................................................................25-23 25.3.5 Setting the MPLS OAM Parameters of a Tunnel.............................................................................25-23 25.3.6 Starting the CV/FFD for a Tunnel....................................................................................................25-24 25.3.7 Performing an LSP Ping Test...........................................................................................................25-25 25.3.8 Performing an LSP Traceroute Test.................................................................................................25-26 25.4 Configuring the PW OAM........................................................................................................................25-27 25.4.1 Overview of the PW OAM...............................................................................................................25-27 25.4.2 Basic Concepts.................................................................................................................................25-27 25.4.3 Application of the PW OAM...........................................................................................................25-28 25.4.4 Performing the PW Ping Test...........................................................................................................25-28 25.5 Configuring ATM OAM...........................................................................................................................25-29 25.5.1 Overview of the ATM OAM............................................................................................................25-30 25.5.2 Basic Concepts.................................................................................................................................25-30 25.5.3 Application of the ATM OAM.........................................................................................................25-31 25.5.4 Setting Segment End Attribute.........................................................................................................25-32 25.5.5 Setting the CC Activation Status......................................................................................................25-33 25.5.6 Setting Remote Loopback Test........................................................................................................25-34 25.5.7 Setting Local Loopback ID..............................................................................................................25-35 25.6 Configuration Case of the Ethernet Port OAM.........................................................................................25-35 25.6.1 Case Description..............................................................................................................................25-35 25.6.2 Service Planning...............................................................................................................................25-36 25.6.3 Configuration Process......................................................................................................................25-38 25.7 Configuration Case of the Ethernet Service OAM....................................................................................25-39 25.7.1 Case Description..............................................................................................................................25-40 25.7.2 Service Planning...............................................................................................................................25-40 25.7.3 Configuration Process......................................................................................................................25-42 25.8 Configuration Case of the MPLS OAM....................................................................................................25-46 25.8.1 Case Description..............................................................................................................................25-47 25.8.2 Configuration Process......................................................................................................................25-48 25.9 Configuration Case of the ATM OAM.....................................................................................................25-49 25.9.1 Case Description..............................................................................................................................25-49 25.9.2 Configuration Process......................................................................................................................25-51 xvi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

Contents

25.10 Configuration Case of the PW OAM......................................................................................................25-52 25.10.1 Case Description............................................................................................................................25-53 25.10.2 Configuration Process....................................................................................................................25-54

26 Configuring the BFD.............................................................................................................26-1

26.1 Overview of the BFD..................................................................................................................................26-2 26.2 Basic Concepts............................................................................................................................................26-2 26.3 Creating a BFD Session..............................................................................................................................26-3 26.4 Configuring Parameters of the BFD Session..............................................................................................26-4 26.5 Querying the BFD Session Information......................................................................................................26-4 26.6 Deleting a BFD Session..............................................................................................................................26-5 26.7 Configuration Case......................................................................................................................................26-5 26.7.1 Case Description................................................................................................................................26-5 26.7.2 Configuration Process........................................................................................................................26-6

27 Configuring the LPT..............................................................................................................27-1

27.1 Overview of the LPT...................................................................................................................................27-2 27.2 LPT Application..........................................................................................................................................27-2 27.3 Creating the LPT.........................................................................................................................................27-3 27.4 Configuration Case......................................................................................................................................27-4 27.4.1 Case Description................................................................................................................................27-4 27.4.2 Configuration Process........................................................................................................................27-5

28 Configuring Orderwire.........................................................................................................28-1
28.1 Configuring Orderwire................................................................................................................................28-2 28.2 Configuring F1 Data Port Services.............................................................................................................28-3 28.2.1 F1 Data Port Services.........................................................................................................................28-3 28.2.2 Creating F1 Data Port Services..........................................................................................................28-4

29 Common Maintenance Operations.....................................................................................29-1

29.1 Setting a Scheduled Task............................................................................................................................29-3 29.2 Checking Networkwide Maintenance Status..............................................................................................29-4 29.2.1 Checking Path Loopback Status.........................................................................................................29-5 29.2.2 Checking Port Laser Status................................................................................................................29-6 29.2.3 Checking Path Alarm Suppression Status..........................................................................................29-8 29.3 Checking Protection Switching Status........................................................................................................29-9 29.3.1 Checking the Subcard TPS Status......................................................................................................29-9 29.3.2 Checking 1+1 Board Switching Status.............................................................................................29-10 29.3.3 Checking Linear MSP Switching Status..........................................................................................29-10 29.3.4 Checking GNE Switching Status.....................................................................................................29-11 29.3.5 Checking the Clock Switching Status..............................................................................................29-11 29.3.6 Checking the FRR Protection Status................................................................................................29-11 29.4 Performing a PRBS Test...........................................................................................................................29-12 29.5 Disabling Service-Affecting Settings Automatically................................................................................29-13 29.6 Checking the Network Communication Status.........................................................................................29-13 Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvii

Contents

OptiX iManager T2000 Operation Guide for PTN NE Management

29.7 Performing a Loopback.............................................................................................................................29-14 29.7.1 Looping Back SDH interface...........................................................................................................29-15 29.7.2 Looping Back PDH interface...........................................................................................................29-16 29.7.3 Setting a Loopback for an Ethernet Interface...................................................................................29-18 29.7.4 Looping Back ATM Interface..........................................................................................................29-19 29.8 Replacing the Board Type.........................................................................................................................29-21 29.9 Resetting Boards.......................................................................................................................................29-22 29.9.1 Reset.................................................................................................................................................29-22 29.9.2 Resetting a Board.............................................................................................................................29-23

A Glossary.....................................................................................................................................A-1 B Acronyms and Abbreviations.................................................................................................B-1

xviii

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

Figures

Figures
Figure 2-1 Inband DCN networking mode...........................................................................................................2-2 Figure 2-2 Inband networking scheme.................................................................................................................2-3 Figure 2-3 Outband networking scheme..............................................................................................................2-4 Figure 2-4 Inband networking application.........................................................................................................2-10 Figure 4-1 Typical application.............................................................................................................................4-7 Figure 5-1 Architecture of the IEEE 1588V2 clock.............................................................................................5-4 Figure 5-2 Master-slave synchronization process................................................................................................5-5 Figure 5-3 Networking diagram for typical application of the PTP clock...........................................................5-7 Figure 5-4 Configuration flow for the PTP clock................................................................................................5-8 Figure 5-5 Scenario where the PTP clock is transmitted through the PSN........................................................5-22 Figure 6-1 Phase synchronization and frequency synchronization......................................................................6-3 Figure 6-2 Location of the MASTER, SLAVER, and REPEATER equipment in the network..........................6-4 Figure 6-3 Differential and adaptive TOP packets encapsulated based on PWE3...............................................6-4 Figure 6-4 Adaptive TOP packets encapsulated based on IEEE 1588v2 Ethernet..............................................6-5 Figure 6-5 Adaptive TOP packets encapsulated based on IEEE 1588v2 IP........................................................6-5 Figure 6-6 Typical networking of TOP clock synchronization............................................................................6-6 Figure 6-7 Configuration flow of the TOP clock service.....................................................................................6-7 Figure 6-8 TOP clock networking application...................................................................................................6-14 Figure 6-9 TOP clock networking application...................................................................................................6-15 Figure 7-1 Hardware configuration of TPS..........................................................................................................7-7 Figure 8-1 LSP tunnel created by using the MPLS-RSVP................................................................................ 8-11 Figure 8-2 ARP frame format............................................................................................................................ 8-12 Figure 8-3 ARP address resolution.................................................................................................................... 8-14 Figure 8-4 Example of setting the route color....................................................................................................8-15 Figure 9-1 Networking diagram for the DiffServ model......................................................................................9-4 Figure 9-2 HQoS function points and corresponding QoS processing................................................................9-7 Figure 9-3 QoS configuration flow for the edge node in the DiffServ domain................................................. 9-10 Figure 9-4 QoS configuration flow for the internal node in the DiffServ domain.............................................9-11 Figure 9-5 QoS configuration flow for ATM services.......................................................................................9-11 Figure 9-6 Networking diagram for the QoS configuration of the ATM service.............................................. 9-48 Figure 9-7 Networking diagram for QoS configuration of the Ethernet service................................................9-55 Figure 10-1 Procedure for configuring an SDH interface..................................................................................10-7 Figure 10-2 Procedure for configuring a PDH interface..................................................................................10-14 Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xix

Figures

OptiX iManager T2000 Operation Guide for PTN NE Management Figure 10-3 Procedure for configuring an Ethernet interface..........................................................................10-19

Figure 10-4 Process of configuring the ADSL interface..................................................................................10-24 Figure 10-5 Application scenario of the G.SHDSL interface..........................................................................10-29 Figure 10-6 Process of configuring the G.SHDSL interface............................................................................10-30 Figure 10-7 Process of configuring the G.SHDSL interface............................................................................10-32 Figure 10-8 Process of configuring the G.SHDSL interface............................................................................10-34 Figure 10-9 Procedure for configuring an microwave interface......................................................................10-41 Figure 10-10 Procedure for configuring a serial interface...............................................................................10-47 Figure 10-11 Procedure for configuring an MP group.....................................................................................10-53 Figure 10-12 ML-PPP packet format...............................................................................................................10-55 Figure 10-13 ML-PPP application scenario.....................................................................................................10-55 Figure 10-14 Process of configuring the virtual interface on the xDSL board................................................10-60 Figure 10-15 Process of configuring the virtual interface on the Ethernet board............................................10-61 Figure 10-16 IMA group configuration flow...................................................................................................10-65 Figure 10-17 ML-PPP networking diagram.....................................................................................................10-81 Figure 10-18 NE hardware configuration at POC2..........................................................................................10-82 Figure 10-19 NE hardware configuration at POC1..........................................................................................10-82 Figure 11-1 1+1 HSB protection........................................................................................................................11-2 Figure 11-2 1+1 HSB realization principle (before the switching, in the transmit direction)...........................11-3 Figure 11-3 1+1 HSB realization principle (before the switching, in the receive direction).............................11-3 Figure 11-4 1+1 HSB realization principle (after the switching, in the receive direction)................................11-4 Figure 11-5 1+1 HSB realization principle (after the switching, in the transmit direction)..............................11-4 Figure 11-6 1+1 FD protection...........................................................................................................................11-6 Figure 11-7 1+1 FD realization principle (before the switching, in the transmit direction)..............................11-6 Figure 11-8 1+1 FD realization principle (before the switching, in the receive direction)................................11-7 Figure 11-9 1+1 FD HSB realization principle (after the switching, in the receive direction)..........................11-8 Figure 11-10 1+1 FD HSM realization principle (after the switching, in the receive direction).......................11-8 Figure 11-11 1+1 SD protection.........................................................................................................................11-9 Figure 11-12 1+1 SD realization principle (before the switching, in the transmit direction)..........................11-10 Figure 11-13 1+1 SD realization principle (before the switching, in the receive direction)............................11-10 Figure 11-14 1+1 SD HSB realization principle (after the switching, in the receive direction)......................11-11 Figure 11-15 1+1 SD HSB realization principle (after the switching, in the transmit direction)....................11-11 Figure 11-16 1+1 SD HSM realization principle (after the switching, in the receive direction).....................11-12 Figure 12-1 Radio link.......................................................................................................................................12-5 Figure 13-1 MPLS tunnel in the MPLS network...............................................................................................13-3 Figure 13-2 Transparent transmission of point-to-point data packets................................................................13-4 Figure 13-3 Protection principle for unicast tunnels..........................................................................................13-5 Figure 13-4 MPLS Tunnel configuration flow ..................................................................................................13-6 Figure 13-5 Networking diagram of an MPLS tunnel.....................................................................................13-20 Figure 13-6 NE planning..................................................................................................................................13-20 Figure 13-7 Networking diagram of an MPLS tunnel.....................................................................................13-29 Figure 13-8 NE planning..................................................................................................................................13-30 xx Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

Figures

Figure 14-1 ATM PWE3 over IP tunnel............................................................................................................14-2 Figure 14-2 IP tunnel networking application....................................................................................................14-5 Figure 14-3 NE planning....................................................................................................................................14-5 Figure 15-1 ATM PWE3 over GRE tunnel........................................................................................................15-2 Figure 15-2 GRE tunnel networking application...............................................................................................15-4 Figure 15-3 NE Planning....................................................................................................................................15-5 Figure 16-1 SDH 1+1 linear MSP......................................................................................................................16-6 Figure 16-2 SDH 1:1 linear MSP.......................................................................................................................16-6 Figure 16-3 MPLS APS 1+1 protection...........................................................................................................16-11 Figure 16-4 MPLS APS 1:1 protection............................................................................................................16-12 Figure 16-5 MPLS APS 1+1 protection...........................................................................................................16-15 Figure 16-6 MPLS APS 1:1 protection............................................................................................................16-15 Figure 16-7 Networking diagram for Offload protection.................................................................................16-20 Figure 16-8 Principle of Offload Protection (Normal).....................................................................................16-21 Figure 16-9 Principle of Offload Protection (Switching).................................................................................16-22 Figure 16-10 FRR network protection.............................................................................................................16-26 Figure 16-11 FRR link protection....................................................................................................................16-27 Figure 16-12 FRR node protection...................................................................................................................16-28 Figure 16-13 Link Aggregation Group............................................................................................................16-31 Figure 16-14 Networking diagram of the MPLS APS protection....................................................................16-36 Figure 16-15 Networking diagram of the offload application scenario based on the ETH forwarding and packet encapsulation format ........................................................................................................................................16-41 Figure 16-16 FRR protection networking diagram..........................................................................................16-46 Figure 16-17 Networking of the LAG..............................................................................................................16-55 Figure 18-1 CES service networking sample.....................................................................................................18-4 Figure 18-2 External Clock synchronization of CES service clock...................................................................18-6 Figure 18-3 Auto-adaption synchronization of CES service clock....................................................................18-6 Figure 18-4 UNI-UNI CES service configuration flow.....................................................................................18-7 Figure 18-5 UNI-NNI CES service configuration flow.....................................................................................18-8 Figure 18-6 Networking of the CES service....................................................................................................18-22 Figure 18-7 NE planning diagram....................................................................................................................18-22 Figure 18-8 Checking the CES service............................................................................................................18-29 Figure 18-9 Networking diagram of the CES service......................................................................................18-31 Figure 18-10 NE planning................................................................................................................................18-31 Figure 18-11 Checking the CES service..........................................................................................................18-55 Figure 19-1 ATM IMA group............................................................................................................................19-3 Figure 19-2 IMA networking diagram 1............................................................................................................19-4 Figure 19-3 IMA networking diagram 2............................................................................................................19-4 Figure 19-4 ATM service networking sample................................................................................................... 19-5 Figure 19-5 ATM connection convergence sample........................................................................................... 19-6 Figure 19-6 Configuration flow of the UNI-UNI ATM service.........................................................................19-9 Figure 19-7 Configuration flow of the UNIs-NNI ATM service.....................................................................19-10 Figure 19-8 IMA group configuration flow.....................................................................................................19-15 Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxi

Figures

OptiX iManager T2000 Operation Guide for PTN NE Management Figure 19-9 Networking diagram of the IMA service......................................................................................19-41

Figure 19-10 Networking of the ATM service.................................................................................................19-46 Figure 19-11 NE planning diagram..................................................................................................................19-47 Figure 19-12 ATM OAM.................................................................................................................................19-58 Figure 19-13 Networking of the ATM service.................................................................................................19-60 Figure 19-14 NE planning diagram..................................................................................................................19-60 Figure 19-15 ATM service OAM.....................................................................................................................19-94 Figure 20-1 UNI-UNI E-Line service................................................................................................................20-4 Figure 20-2 UNI-NNI E-Line service carried by ports......................................................................................20-4 Figure 20-3 UNI-NNI E-Line service carried by a PW.....................................................................................20-5 Figure 20-4 UNI-NNI E-Line service carried by a QinQ link...........................................................................20-6 Figure 20-5 E-LAN service................................................................................................................................20-7 Figure 20-6 E-AGGR service.............................................................................................................................20-8 Figure 20-7 Configuration flow for the UNI-UNI E-Line service...................................................................20-10 Figure 20-8 UNI-NNI E-Line service carried by ports....................................................................................20-12 Figure 20-9 UNI-NNI E-Line service carried by PWs.....................................................................................20-14 Figure 20-10 UNI-NNI E-Line service carried by QinQ Link.........................................................................20-16 Figure 20-11 Flow diagram for configuring the E-LAN service.....................................................................20-31 Figure 20-12 Configuration flow for the E-AGGR service..............................................................................20-41 Figure 20-13 Networking diagram for the UNI-UNI E-Line service...............................................................20-54 Figure 20-14 Networking diagram for the UNI-NNI E-Line service carried by ports....................................20-60 Figure 20-15 OAM of the E-Line service........................................................................................................20-63 Figure 20-16 Networking diagram for the UNI-NNI E-Line service carried by the PW.................................20-67 Figure 20-17 OAM of the E-Line service........................................................................................................20-74 Figure 20-18 Networking diagram for the UNI-NNI E-Line service carried by the QinQ link......................20-78 Figure 20-19 OAM of the E-Line service........................................................................................................20-84 Figure 20-20 Networking diagram for the E-LAN service..............................................................................20-87 Figure 20-21 E-AGGR service networking diagram........................................................................................20-93 Figure 21-1 Model of a BGP/MPLS VPN.........................................................................................................21-3 Figure 21-2 Schematic diagram of sites.............................................................................................................21-5 Figure 21-3 One site belonging to multiple VPNs.............................................................................................21-6 Figure 21-4 Schematic diagram of VPN instances.............................................................................................21-7 Figure 21-5 VPN-IPv4 address structure...........................................................................................................21-8 Figure 21-6 Format of a VPN target................................................................................................................21-10 Figure 21-7 BGP running mode.......................................................................................................................21-12 Figure 21-8 Format of MP_REACH_NLRI.....................................................................................................21-12 Figure 21-9 Format of the NLRI field with a Label subfield...........................................................................21-13 Figure 21-10 Format of MP_UNREACH_NLRI.............................................................................................21-13 Figure 21-11 Format of BGP capability parameters........................................................................................21-14 Figure 21-12 Format of the Capability Value field in MP-BGP......................................................................21-14 Figure 21-13 Advertisement of a route from CE2 to CE1...............................................................................21-20 Figure 21-14 Forwarding of a VPN packet from CE1 to CE2.........................................................................21-21 xxii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

Figures

Figure 21-15 Networking diagram of an intranet VPN....................................................................................21-22 Figure 21-16 Networking diagram of an extranet............................................................................................21-23 Figure 21-17 Route advertisement from Site2 to Site1 in Hub&Spoke networking model.............................21-24 Figure 21-18 Path of transmitting customer traffic from Site1 to Site2...........................................................21-25 Figure 21-19 Configuration flow of an L3VPN service...................................................................................21-26 Figure 21-20 Networking of the intranet VPN service....................................................................................21-45 Figure 21-21 NE planning diagram..................................................................................................................21-46 Figure 21-22 Networking of the extranet VPN service....................................................................................21-61 Figure 21-23 NE planning diagram..................................................................................................................21-61 Figure 21-24 Networking of the Hub&Spoke VPN service.............................................................................21-72 Figure 21-25 NE planning diagram..................................................................................................................21-72 Figure 22-1 Application of the IGMP Snooping-Supported Equipment in the Network..................................22-3 Figure 22-2 Multicast forwarding......................................................................................................................22-6 Figure 22-3 IGMP Snooping networking application......................................................................................22-12 Figure 23-1 STP/RSTP.......................................................................................................................................23-3 Figure 23-2 Limitations of the STP/RSTP.........................................................................................................23-4 Figure 23-3 MSTI in an MST region.................................................................................................................23-5 Figure 23-4 Example of the MSTP....................................................................................................................23-6 Figure 23-5 Example of the MST region...........................................................................................................23-7 Figure 23-6 MSTP networking application......................................................................................................23-13 Figure 24-1 Offload solution..............................................................................................................................24-3 Figure 24-2 Offload scenario for the ATM-based service.................................................................................24-3 Figure 24-3 Offload scenario for the ETH-based service..................................................................................24-4 Figure 24-4 Offload scenario for the IP-Based services....................................................................................24-5 Figure 24-5 Configuration flow of the ATM-based service in the offload solution..........................................24-6 Figure 24-6 Configuration flow of the ETH-based service in the offload solution...........................................24-7 Figure 24-7 Configuration flow of the IP-based service in the offload solution................................................24-8 Figure 24-8 Networking diagram of the offload application scenario based on the ATM forwarding and packet encapsulation format.........................................................................................................................................24-10 Figure 24-9 Networking diagram of the offload application scenario based on the ETH forwarding and packet encapsulation format.........................................................................................................................................24-22 Figure 24-10 Networking diagram of the offload application scenario based on the IP forwarding and packet encapsulation format.........................................................................................................................................24-33 Figure 25-1 Application scenario of the Ethernet port OAM.............................................................................25-4 Figure 25-2 Ethernet OAM configuration flow.................................................................................................25-7 Figure 25-3 Relation among the MD, MA, MEP, and MIP.............................................................................25-10 Figure 25-4 CC detection.................................................................................................................................25-10 Figure 25-5 LB detection.................................................................................................................................25-11 Figure 25-6 LT detection..................................................................................................................................25-11 Figure 25-7 Application Scenarios of Ethernet Service OAM.........................................................................25-12 Figure 25-8 Connectivity check of the MPLS OAM.......................................................................................25-21 Figure 25-9 Application scenarios of MPLS OAM.........................................................................................25-22 Figure 25-10 Application scenario of the PW OAM.......................................................................................25-28 Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxiii

Figures

OptiX iManager T2000 Operation Guide for PTN NE Management Figure 25-11 Application scenarios of ATM OAM.........................................................................................25-32

Figure 25-12 Networking of the Ethernet port OAM.......................................................................................25-36 Figure 25-13 Networking of the Ethernet service OAM..................................................................................25-40 Figure 25-14 Networking diagram of the MPLS OAM...................................................................................25-47 Figure 25-15 Networking of the ATM OAM...................................................................................................25-49 Figure 25-16 Application of the PW OAM networking...................................................................................25-53 Figure 26-1 BFD networking application..........................................................................................................26-6 Figure 27-1 LPT networking application scenario.............................................................................................27-2 Figure 27-2 LPT networking diagram................................................................................................................27-4 Figure 28-1 Configuring the ..............................................................................................................................28-3 Figure 29-1 Outloop.........................................................................................................................................29-15 Figure 29-2 Inloop............................................................................................................................................29-16 Figure 29-3 Outloop.........................................................................................................................................29-17 Figure 29-4 Inloop............................................................................................................................................29-17 Figure 29-5 Inloop............................................................................................................................................29-18 Figure 29-6 Outloop.........................................................................................................................................29-18 Figure 29-7 Outloop.........................................................................................................................................29-20 Figure 29-8 Inloop............................................................................................................................................29-20

xxiv

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

Tables

Tables
Table 2-1 Planning of the parameters for the inband DCN configuration.........................................................2-10 Table 2-2 Planning of the parameters for the ML-PPP link between GNE1 and NE3......................................2-11 Table 2-3 Planning of the parameters for the IP tunnel between GNE1 and NE4.............................................2-12 Table 2-4 Planning of the parameters for the radio link between NE3 and NE5...............................................2-12 Table 5-1 Planning of the OptiX PTN 3900 working as a BC...........................................................................5-23 Table 5-2 Planning of the OptiX PTN 3900 working as a TC...........................................................................5-24 Table 5-3 Planning of the OptiX PTN 910 working as an OC...........................................................................5-25 Table 5-4 Planning of the OptiX PTN 950 working as an OC...........................................................................5-26 Table 6-1 Configuration flow of the TOP clock service......................................................................................6-7 Table 6-2 NE parameters....................................................................................................................................6-15 Table 6-3 Static routes........................................................................................................................................6-16 Table 6-4 IP tunnel planning..............................................................................................................................6-16 Table 6-5 MPLS tunnel planning.......................................................................................................................6-16 Table 6-6 TOP clock service planning...............................................................................................................6-17 Table 7-1 Configuration parameters of the TPS protection.................................................................................7-7 Table 9-1 Scheduling and application..................................................................................................................9-6 Table 9-2 Table for mapping relations between the PTN equipment and the supported QoS policies................9-9 Table 9-3 PHB service level and mapping PHB service quality........................................................................9-12 Table 9-4 Default threshold for the port WRED policy.....................................................................................9-18 Table 9-5 Port buffer size of each board for the OptiX PTN 3900....................................................................9-18 Table 9-6 Port buffer size of each board for the OptiX PTN 1900....................................................................9-18 Table 9-7 Mapping relation between the ATM service type and PHB service class.........................................9-43 Table 9-8 Service types and QoS requirements..................................................................................................9-49 Table 9-9 Service types and QoS requirements..................................................................................................9-50 Table 9-10 Requirements for QoS configuration of the Ethernet service..........................................................9-56 Table 10-1 Types of PTN service interfaces......................................................................................................10-1 Table 10-2 Application scenario of SDH interfaces...........................................................................................10-6 Table 10-3 Application scenario of PDH interfaces.........................................................................................10-13 Table 10-4 Application scenario of Ethernet interfaces...................................................................................10-18 Table 10-5 Tasks of configuring the ADSL interface .....................................................................................10-24 Table 10-6 Tasks of configuring the G.SHDSL interface in ATM mode........................................................10-31 Table 10-7 Tasks of configuring the G.SHDSL interface in EFM mode.........................................................10-33 Table 10-8 Tasks of configuring the G.SHDSL interface in IMA mode.........................................................10-34 Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxv

Tables

OptiX iManager T2000 Operation Guide for PTN NE Management Table 10-9 Application scenario of microwave interfaces...............................................................................10-40 Table 10-10 Classification of the Ethernet virtual interfaces...........................................................................10-59 Table 10-11 Tasks for configuring the virtual interface on the xDSL board................................................... 10-61 Table 10-12 Tasks for configuring the virtual interface on the Ethernet board............................................... 10-62 Table 10-13 IMA group status parameters.......................................................................................................10-74 Table 10-14 IMA link status parameters..........................................................................................................10-75 Table 10-15 Parameters planned for the ML-PPP configuration.....................................................................10-83 Table 13-1 Tasks for configuring the MPLS Tunnel.........................................................................................13-6 Table 13-2 Configuration parameters of NEs...................................................................................................13-21 Table 13-3 Configuration parameters of Tunnels.............................................................................................13-21 Table 13-4 Configuration parameters of NEs...................................................................................................13-30 Table 13-5 Planning of Tunnel parameters...................................................................................................... 13-31 Table 14-1 Configuration parameters of NEs.....................................................................................................14-6 Table 14-2 Static route.......................................................................................................................................14-6 Table 14-3 Planning of the IP tunnel..................................................................................................................14-6 Table 14-4 Planning of the protection MPLS tunnel..........................................................................................14-7 Table 15-1 Configuration parameters of NEs.....................................................................................................15-5 Table 15-2 Static route.......................................................................................................................................15-6 Table 15-3 Planning of the working GRE tunnel...............................................................................................15-6 Table 15-4 Planning of the protection MPLS tunnel..........................................................................................15-6 Table 16-1 MSP protection switching priorities.................................................................................................16-4 Table 16-2 Parameters for MPLS APS 1+1 protection....................................................................................16-11 Table 16-3 Parameters for MPLS APS 1:1 protection.....................................................................................16-12 Table 16-4 Planning of service parameters...................................................................................................... 16-42 Table 16-5 Planning of BFD session parameters............................................................................................. 16-42 Table 16-6 Planning of the tunnel protection group parameters...................................................................... 16-42 Table 16-7 Configuration parameters of NEs...................................................................................................16-46 Table 16-8 Planning of parameters of the FRR................................................................................................16-47 Table 16-9 Configuration parameters of the LAG........................................................................................... 16-55 Table 18-1 CES service clock type.....................................................................................................................18-5 Table 18-2 Tasks for configuring the UNI-UNI CES service............................................................................18-7 Table 18-3 Tasks for configuring the UNIs-NNI CES service..........................................................................18-8 Table 18-4 Configuration parameters of NE1..................................................................................................18-22 Table 18-5 Configuration parameters of NEs...................................................................................................18-32 Table 18-6 Planning of Tunnel parameters...................................................................................................... 18-32 Table 18-7 Configuration parameters of the CES service: NE1-NE3 (E1 timeslots partially used)................18-34 Table 18-8 Configuration parameters of the CES service: NE1-NE3 (E1 timeslots fully used)..................... 18-35 Table 19-1 ATM service type and traffic...........................................................................................................19-6 Table 19-2 Tasks for configuring the UNI-UNI ATM service...........................................................................19-9 Table 19-3 Tasks for configuring the UNIs-NNI ATM service.......................................................................19-11 Table 19-4 ATM Interface................................................................................................................................19-12 Table 19-5 IMA group status parameters.........................................................................................................19-23

xxvi

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

Tables

Table 19-6 IMA link status parameters............................................................................................................19-24 Table 19-7 Configuration parameters of IMA1................................................................................................19-41 Table 19-8 Configuration parameters of IMA2................................................................................................19-42 Table 19-9 Configuration parameters of NE1..................................................................................................19-47 Table 19-10 Service types and QoS requirements............................................................................................19-48 Table 19-11 Configuration parameters of NEs.................................................................................................19-61 Table 19-12 Planning of Tunnel parameters....................................................................................................19-61 Table 19-13 Configuration parameters of NE1................................................................................................19-62 Table 19-14 Configuration parameters of NE3................................................................................................19-63 Table 20-1 Tasks for configuring the UNI-UNI E-Line service......................................................................20-11 Table 20-2 Tasks for configuring the UNI-UNI E-Line service carried by a port...........................................20-12 Table 20-3 Tasks for configuring the UNI-NNI E-Line service carried by PWs.............................................20-15 Table 20-4 Tasks for configuring the UNI-NNI E-Line service carried by QinQ Link...................................20-17 Table 20-5 Requirement of the E-Line service.................................................................................................20-54 Table 20-6 Configuration parameters of NE1..................................................................................................20-55 Table 20-7 Configuration parameters of QoS..................................................................................................20-55 Table 20-8 Planning of the UNI-UNI E-Line service......................................................................................20-56 Table 20-9 Configuration parameters of NEs...................................................................................................20-60 Table 20-10 Planning of the UNI-NNI E-Line service carried by ports..........................................................20-61 Table 20-11 Configuration parameters of NEs.................................................................................................20-67 Table 20-12 Planning of the tunnel carrying the PW.......................................................................................20-68 Table 20-13 Planning of the UNI-NNI E-Line service carried by the PW......................................................20-68 Table 20-14 Planning of the PW......................................................................................................................20-69 Table 20-15 Configuration parameters of NEs.................................................................................................20-78 Table 20-16 Planning of the QinQ link carrying the service............................................................................20-79 Table 20-17 Planning of the UNI-NNI E-Line service carried by the QinQ link............................................20-79 Table 20-18 Planning of the tunnel that carries the PW...................................................................................20-87 Table 20-19 Planning of the E-LAN service carried by a PW.........................................................................20-88 Table 20-20 Planning of the UNI port..............................................................................................................20-88 Table 20-21 Planning of the PW......................................................................................................................20-89 Table 20-22 Planning of the tunnel carrying the PW.......................................................................................20-93 Table 20-23 Planning of the E-AGGR service carried by the PW...................................................................20-94 Table 20-24 Planning of the PW......................................................................................................................20-94 Table 20-25 Planning of the VLAN forwarding tables of NE1 and NE2........................................................20-95 Table 20-26 Planning of the VLAN forwarding table of NE3.........................................................................20-95 Table 21-1 Configuration of an L3VPN service..............................................................................................21-26 Table 21-2 VPN1 parameter planning..............................................................................................................21-46 Table 21-3 VPN2 parameter planning..............................................................................................................21-48 Table 21-4 Parameter planning.........................................................................................................................21-62 Table 21-5 VPN parameter planning................................................................................................................21-73 Table 22-1 Configuration parameters for enabling the IGMP Snooping.........................................................22-12 Table 22-2 Configuration parameters for managing the IGMP Snooping routes............................................22-13 Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxvii

Tables

OptiX iManager T2000 Operation Guide for PTN NE Management Table 22-3 Configuration parameters for managing the IGMP Snooping route member ports.......................22-13 Table 22-4 Configuration parameters for packet statistics on the IGMP Snooping.........................................22-13 Table 23-1 Parameters planned for the MSTP configuration...........................................................................23-13 Table 24-1 VPI/VCI values of the Node B service..........................................................................................24-12 Table 24-2 Planning of the UNIs......................................................................................................................24-12 Table 24-3 Planning of the NNIs......................................................................................................................24-13 Table 24-4 Planning of the MPLS tunnel.........................................................................................................24-14 Table 24-5 Planning of the PW........................................................................................................................24-14 Table 24-6 Planning of the ATM service on the OptiX PTN 1900..................................................................24-15 Table 24-7 Planning of the ATM service on the OptiX PTN 3900..................................................................24-15 Table 24-8 VPI/VCI values of the Node B service..........................................................................................24-24 Table 24-9 Planning of the UNIs......................................................................................................................24-24 Table 24-10 Planning of the NNIs....................................................................................................................24-25 Table 24-11 Planning of the MPLS Tunnel......................................................................................................24-26 Table 24-12 Planning of the PW......................................................................................................................24-26 Table 24-13 Planning of the ATM service on the OptiX PTN 1900................................................................24-27 Table 24-14 Planning of the ATM service on the OptiX PTN 3900................................................................24-27 Table 24-15 VPI/VCI values of the Node B service........................................................................................24-35 Table 24-16 Planning of the UNIs....................................................................................................................24-35 Table 24-17 Planning of the NNIs....................................................................................................................24-36 Table 24-18 Planning of the static routing table entries...................................................................................24-36 Table 24-19 Planning of the Tunnel.................................................................................................................24-37 Table 24-20 Planning of the PW......................................................................................................................24-38 Table 24-21 Planning of the ATM service on the OptiX PTN 1900................................................................24-38 Table 24-22 Planning of the ATM service on the OptiX PTN 3900................................................................24-39 Table 25-1 Application scenarios of Ethernet OAM........................................................................................25-12 Table 25-2 Application scenarios of MPLS OAM detection methods.............................................................25-23 Table 25-3 Classification of the OAM function layers....................................................................................25-30 Table 25-4 Application scenarios of ATM OAM detection methods..............................................................25-32 Table 25-5 NE parameter list............................................................................................................................25-36 Table 25-6 Configuration of the MD................................................................................................................25-41 Table 25-7 Configuration of the MA 1.............................................................................................................25-41 Table 25-8 Configuration of the MA 2.............................................................................................................25-41 Table 25-9 Configuration of the MEP point.....................................................................................................25-41 Table 25-10 Configuration of the MIP point....................................................................................................25-42 Table 25-11 Configuration parameters of the MPLS OAM.............................................................................25-48 Table 25-12 Configuration parameters of the ATM OAM..............................................................................25-50 Table 25-13 Configuration of the Ping test......................................................................................................25-53 Table 26-1 Planned configuration parameters of NE1.......................................................................................26-6 Table 27-1 Planned parameters for the LPT configuration................................................................................27-5

xxviii

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

About This Document

About This Document

Purpose
The OptiX iManager T2000 Operation Guide for PTN NE Management describes the operations, such as how to configure the communication, clock and service of the PTN equipment on the T2000. This document also provides the acronyms and abbreviations. This document guides the user to understand basic operations of the T2000.

Related Version
The following table lists the product version related to this document. Product Name OptiX iManager T2000 Version V200R007C03

Intended Audience
The intended audiences of this document are:
l l l l

Network monitors Data configuration engineers Network administrators Maintenance engineers

Organization
This document is organized as follows. Chapter 1 Creating NEs, Links, and Topology Subnets
Issue 01 (2009-06-30)

Description This chapter describes how to create NEs, links, and topology subnets in the T2000.
1

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

OptiX iManager T2000 Operation Guide for PTN NE Management

Chapter 2 Configuring Communications 3 Configuring the NE Time 4 Configuring Clocks 5 PTP Clock 6 Configuring a TOP Clock 7 Configuring the Equipment-Level Protection 8 Configuring the Control Plane 9 Configuring the QoS Policy 10 Configuring Interfaces 11 Configuring the IF 1+1 Protection 12 Configuring a Radio Link 13 Configuring an MPLS Tunnel 14 Configuring an IP Tunnel 15 Configuring a GRE Tunnel 16 Configuring Network Level Protection 17 Configuring an MPLS PW 18 Configuring CES Services 19 Configuring an ATM Service 20 Configuring an Ethernet Service

Description This chapter describes how to configure communication in the T2000. This chapter describes the operations of setting NE time in the T2000. This chapter describes how to configure clocks for the PTN equipment. This chapter describes how to configure PTP clocks for the PTN equipment. This chapter describes how to configure TOP clocks for the PTN equipment. This chapter describes how to configure the protection for the PTN equipment. This chapter describes how to configure the control plane. This chapter describes how to configure the QoS policy. This chapter describes how to configure the interface attributes for the PTN equipment. This chapter describes how to configure IF 1 +1 protection. This chapter describes how to configure radio links. This chapter describes how to configure the MPLS tunnel. This chapter describes how to configure the IP tunnel. This chapter describes how to configure the GRE tunnel. This chapter describes how to configure the protection for the PSN network. This chapter describes how to configure the MPLS PW. This chapter describes how to configure the CES service. This chapter describes how to configure the ATM service. This chapter describes how to configure the Ethernet service.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

About This Document

Chapter 21 Configuring an L3VPN Service 22 Configuring the IGMP Snooping 23 Configuring the MSTP 24 Configuring Services for the Offload Solution 25 OAM Management 26 Configuring the BFD 27 Configuring the LPT 28 Configuring Orderwire 29 Common Maintenance Operations A Glossary B Acronyms and Abbreviations

Description This chapter describes how to configure the L3VPN service. This chapter describes how to configure the IGMP Snooping. This chapter describes how to configure the MSTP. This chapter describes how to configure the services for the offload solution. This chapter describes how to configure the OAM management. This chapter describes how to configure the BFD. This chapter describes how to configure the LPT. This chapter describes how to configure the orderwire. This chapter describes common maintenance operations in the T2000. This part lists the glossary used in the document. This part lists the acronyms and abbreviations used in the document.

Conventions
Symbol Conventions
The following symbols may be found in this document. They are defined as follows Symbol Description

DANGER

Indicates a hazard with a high level of risk which, if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk which, if not avoided, could result in minor or moderate injury.

WARNING

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

OptiX iManager T2000 Operation Guide for PTN NE Management

Symbol

Description

CAUTION
NOTE

Indicates a potentially hazardous situation that, if not avoided, could cause equipment damage, data loss, and performance degradation, or unexpected results. Provides additional information to emphasize or supplement important points of the main text. Indicates a tip that may help you solve a problem or save you time.

TIP

General Conventions
Convention Times New Roman Boldface Description Normal paragraphs are in Times New Roman. Names of files, directories, folders, and users are in boldface. For example, log in as user root. Book titles are in italics. Terminal display is in Courier New.

Italic Courier New

Command Conventions
Convention Boldface Italic [] { x | y | ... } [ x | y | ... ] Description The keywords of a command line are in boldface. Command arguments are in italic. Items (keywords or arguments) in square brackets [ ] are optional. Alternative items are grouped in braces and separated by vertical bars. One is selected. Optional alternative items are grouped in square brackets and separated by vertical bars. One or none is selected. Alternative items are grouped in braces and separated by vertical bars. A minimum of one or a maximum of all can be selected.

{ x | y | ... } *

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

About This Document

Convention [ x | y | ... ] *

Description Optional alternative items are grouped in square brackets and separated by vertical bars. A maximum of all or none can be selected.

GUI Conventions
Convention Boldface Description Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK. Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.

>

Keyboard Operation
Format Key Key 1+Key 2 Description Press the key. For example, press Enter and press Tab. Press the keys concurrently. For example, pressing Ctrl+Alt+A means the three keys should be pressed concurrently. Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.

Key 1, Key 2

Mouse Operation
Action Click Double-click Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.

Drag

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

OptiX iManager T2000 Operation Guide for PTN NE Management

Update History
Updates between document versions are cumulative. Therefore, the latest document version contains all updates made to previous versions.

Updates in Issue 01 (2009-06-30) Based on Product Version V200R007C03

The updated contents are as follows. The new equipments OptiX PTN 910 and OptiX PTN 950 are add.

Updates in Issue 01 (2009-03-30) Based on Product Version V200R007C02

Initial release.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

1 Creating NEs, Links, and Topology Subnets

Creating NEs, Links, and Topology Subnets

About This Chapter

On the T2000, you can create NEs, links, and topology subnets to perform management through the T2000. 1.1 Creating NEs Each equipment is represented as an NE on the T2000. Before the T2000 manages the actual equipment, you need to create the corresponding NEs on the T2000. There are two methods of creating NEs: creating a single NE and creating NEs in batches. When you need to create a large number of NEs, for example, during deployment, it is recommended that you create NEs in batches. When you need to create only a few NEs, it is recommended that you create the NEs one by one. 1.2 Configuring the NE Data Though an NE is successfully created, it is not configured. You need to configure the NE first so that the T2000 can manage and operate the NE. 1.3 Adding Boards When configuring the NE data, you need to add boards on the NE Panel. You can either add the physical boards that actually operate on the NE or add the logical boards that do not exist on the actual equipment. 1.4 Adding Sub-Boards The equipment can realize different functions after you add different sub-boards to a processing board. 1.5 Creating Links You can create fibers/cables, Ethernet lines, serial port lines, microwave links by using the T2000. 1.6 Creating a Topology Subnet The subnet created here is based on a topological concept to facilitate management. In the case of topology objects in the same network area or with similar attributes, you can allocate them in one topology subnet.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

1-1

1 Creating NEs, Links, and Topology Subnets

OptiX iManager T2000 Operation Guide for PTN NE Management

1.1 Creating NEs

Each equipment is represented as an NE on the T2000. Before the T2000 manages the actual equipment, you need to create the corresponding NEs on the T2000. There are two methods of creating NEs: creating a single NE and creating NEs in batches. When you need to create a large number of NEs, for example, during deployment, it is recommended that you create NEs in batches. When you need to create only a few NEs, it is recommended that you create the NEs one by one. 1.1.1 Creating NEs in Batches When the T2000 communicates properly with a GNE, you can search for all NEs that communicate with the GNE by using the IP address of the GNE or the network segment to which the IP address is associated, or by using the NSAP address of the NE. Then, you can create NEs in batches. This method is quicker and more accurate than manual creation. 1.1.2 Creating a Single NE The T2000 can manage an NE after the NE is created. Although creating a single NE is not as fast and accurate as creating NEs in batches, you can perform this operation regardless of whether the data is configured on the NE or not. 1.1.3 Creating a Virtual NE To display the topological relations between the equipment that is directly managed by the T2000 and the equipment that is indirectly managed by the T2000 on the topology, you must create virtual NEs so that the T2000 manages them together with the regular NEs in a uniform manner.

1.1.1 Creating NEs in Batches

When the T2000 communicates properly with a GNE, you can search for all NEs that communicate with the GNE by using the IP address of the GNE or the network segment to which the IP address is associated, or by using the NSAP address of the NE. Then, you can create NEs in batches. This method is quicker and more accurate than manual creation.

Prerequisite
You must be an NM user with "NE administrator" authority or higher. The T2000 must communicate properly with the GNE. The NE Explorer instance of the NEs must be created.

Procedure
Step 1 Choose File > Search for NE from the Main Menu. The Search for NE window is displayed. Step 2 Click Add and the Input Search Domain dialog box is displayed. Step 3 Set Address type to IP Address Range of GNE, IP Address of GNE, or NSAP Address, and enter Search Address, User Name, and Password. Then, click OK.

1-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

1 Creating NEs, Links, and Topology Subnets

NOTE

You can repeat Steps 2 through 3 to add more search domains. You can delete the system default search domain.
l

If you use IP address to search for NEs:

l

Usually, the broadcast function is disabled on the routers on a network, to avoid network broadcast storm. Therefore, by using the IP Address Range of GNE method, only the NEs in the same network segment can be searched out. To search the network segments across routers, the IP Address of GNE method is recommended. Through a gateway NE, you can search out the NEs in the network segment of the gateway NE.

Step 4 Click Start. The Search for NE dialog box is displayed. Step 5 In the Search for NE dialog box, you can perform the following operations: l l Select Search for NE and click OK to search for all NEs in the selected domain. Select Create device after search, and enter NE user and Password. Then, click OK.

NOTE

l l

The default NE user is root. The default password is password.

Select Upload after create and click OK, so that the NE data can be uploaded to the T2000 after the NE is created.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

1-3

1 Creating NEs, Links, and Topology Subnets

NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

If you select all options in the Search for NE dialog box, you can search for NEs, create the NEs, and upload the NE data at one time.

Step 6 Optional: If you select Search for NE only, you can select the NEs, which are not yet created, in the Result list after the search for NEs is complete. Click Create and then the Create dialog box is displayed. Enter User Name and Password in the Create dialog box, and then click OK. ----End

Postrequisite
After an NE is created, if you fail to log in to the NE, possible causes are listed as follows:
l l

The password for the NE user is incorrect. Enter the correct password for the NE user. The NE user is invalid or the NE user is already logged in. Change to use a valid NE user.

1.1.2 Creating a Single NE

The T2000 can manage an NE after the NE is created. Although creating a single NE is not as fast and accurate as creating NEs in batches, you can perform this operation regardless of whether the data is configured on the NE or not.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The license must be installed and the license must support creating the NE of the type. The NE Explorer instance of the NEs must be created.

Background Information
First create a GNE, and then create a non-gateway NE. If the NE is not created properly or the communication between the NE and the T2000 is abnormal, the NE is displayed in gray color.

Procedure
Step 1 Right-click in the blank space of the Main Topology and choose New > Device from the shortcut menu. The Add Object dialog box is displayed. Step 2 Select the NE type from the Object Type tree. Step 3 Complete the following information: ID, Extended ID, Name and Remarks. Step 4 To create a GNE, proceed to Step 5. To create a non-gateway NE, proceed to Step 6. Step 5 Choose Gateway Type, Protocol and set the IP address. 1. 2.
1-4

Select Gateway from the Gateway Type drop-down list. Select the Protocol type.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

1 Creating NEs, Links, and Topology Subnets

If the T2000 communicates with NEs through IP protocol

Do...

Select IP from the Protocol drop-down list. Enter the IP Address and use the default value for the Port number of the GNE.

NOTE

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

Step 6 Select Non-Gateway from the Gateway Type drop-down list. Select the GNE to which the NE is associated to from the Affiliated Gateway drop-down list. Step 7 Enter the NE User and Password.
NOTE

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

Step 8 Click OK. Then, click in the blank space of the Main Topology and the NE icon appears in the position where you clicked. ----End

Result
After an NE is successfully created, the system automatically saves the information, such as the IP address, subnet mask, and NE ID to the T2000 database.

Postrequisite
After an NE is created, if you fail to log in to the NE, possible causes are listed as follows:
l

The communication between the T2000 and the NE is abnormal. Check the settings of communication parameters, such as the IP address of the NE and NE ID. The password for the NE user is incorrect. Enter the correct password for the NE user. The NE user is invalid or the NE user is already logged in. Change to use a valid NE user.

l l

1.1.3 Creating a Virtual NE

To display the topological relations between the equipment that is directly managed by the T2000 and the equipment that is indirectly managed by the T2000 on the topology, you must create virtual NEs so that the T2000 manages them together with the regular NEs in a uniform manner.

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

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

1-5

1 Creating NEs, Links, and Topology Subnets

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 In the Main Topology, right-click and choose New > Device from the shortcut menu. The Add Object dialog box is displayed. Step 2 Choose NE > PTN Series from the Object Tree. Create a Virtual Physical Layer NE, Virtual L2 NE, or Virtual L3 NE as required.
NOTE

Select the virtual NE that is corresponding to the type of the managed equipment.

Step 3 Enter the attributes of the virtual NE and click OK. Step 4 Click the Main Topology. The NE icon is displayed at the spot where you clicked the mouse button. ----End

1.2 Configuring the NE Data

Though an NE is successfully created, it is not configured. You need to configure the NE first so that the T2000 can manage and operate the NE. 1.2.1 Replicating the NE Data You can replicate the data of an existing NE to a new NE, if the existing NE is already configuration and if the existing NE is of the same NE type and the same NE version as the new NE. 1.2.2 Uploading the NE Data By uploading the NE data, you can synchronize the current NE configuration data to the network management system directly. 1.2.3 Configuring the Virtual NE Data By using the T2000, you can create virtual boards on a virtual NE to simulate the boards of the equipment that is not supported by the T2000.

1.2.1 Replicating the NE Data

You can replicate the data of an existing NE to a new NE, if the existing NE is already configuration and if the existing NE is of the same NE type and the same NE version as the new NE.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The NE must be created successfully. The type and NE software version of the source NE must be consistent with the type and software version of the replicated NE.

Procedure
Step 1 Select the NE whose data you need to replicate.
1-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

1 Creating NEs, Links, and Topology Subnets

NE to Be Configured PTN equipment

Operation Double-click the unconfigured NE on the Main Topology. The NE Configuration Wizard dialog box is displayed.

Step 2 Select Copy NE Data and click Next. The NE Replication dialog box is displayed. Step 3 Select the NE from the drop-down list and click Start. The Confirm dialog box is displayed, indicating that the replication operation copies all the data of the source NE.

NOTE

After the NE data is replicated, only the data on the T2000 side is changed, but the data on the equipment side is not changed.

Step 4 Click OK. The Confirm dialog box is displayed, indicating that the replication operation results in the loss of the original data of the NE to which the data is copied. Step 5 Click OK to start the replication. The Operation Result dialog box is displayed after a few seconds. Step 6 Click Close. ----End

1.2.2 Uploading the NE Data

By uploading the NE data, you can synchronize the current NE configuration data to the network management system directly.

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

Procedure
Step 1 Select the NE whose data you need to Replicate.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-7

1 Creating NEs, Links, and Topology Subnets

OptiX iManager T2000 Operation Guide for PTN NE Management

NE to Be Configured PTN equipment

Operation Double-click the unconfigured NE on the Main Topology. Then, the NE Configuration Wizard dialog box is displayed.

Step 2 Select Upload and click Next. The Confirm dialog box is displayed, indicating that the upload may take a long time. Step 3 Click OK to start the upload. The Operation Result dialog box is displayed when the uploading is complete. Step 4 Click Close. ----End

1.2.3 Configuring the Virtual NE Data

By using the T2000, you can create virtual boards on a virtual NE to simulate the boards of the equipment that is not supported by the T2000.

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

Procedure
Step 1 On the Main Topology, double-click a virtual NE to display the NE Panel. Step 2 Right-click the NE Panel and choose Add a New Board from the shortcut menu. Step 3 Configure the attributes of the board according to the configuration of the equipment that is actually managed and click OK.

Step 4 Right-click the NE Panel and choose the new virtual board. ----End

1.3 Adding Boards

When configuring the NE data, you need to add boards on the NE Panel. You can either add the physical boards that actually operate on the NE or add the logical boards that do not exist on the actual equipment.
1-8 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

1 Creating NEs, Links, and Topology Subnets

Prerequisite
l l l

You must be an NM user with "NE operator" authority or higher. The NE must be created. There must be idle slot on the NE Panel.

Context
The physical boards are the actual boards inserted in the subrack. A logical board refers to a board that is created on the T2000. After a logical board is created, you can configure the relevant services. If the corresponding physical board is online, the configured services can be available.
NOTE

The NE panel is able to indicate the mapping relation between slots that house processing boards and interface boards. When you click a processing board that is paired with an interface board in the NE panel, the ID of the slot that houses the mapping interface board is displayed in orange.

Procedure
Step 1 Open the NE Panel. For the PTN equipment, double-click the icon of the NE. Step 2 Right-click the selected idle slot. Select the board you want to add from the drop-down list. ----End

1.4 Adding Sub-Boards

The equipment can realize different functions after you add different sub-boards to a processing board.

Prerequisite
l l

You must be an NM user with "NE maintainer" authority or higher. Applies to only MP1 boardCXP board.

Context
Hot swappable service sub-board interfaces are provided on the MP1 boardCXP board. When different service sub-boards are inserted, the TDM E1, IMA E1, ML-PPP E1, ATM STM-N and channelized STM-N signals can be assessed and processed.

Procedure
Step 1 Double-click an NE on the Main Topology and the NE Panel is displayed in the user interface. Step 2 Select the desired processing board, right-click in the blank area that displays sub-boards, and select the desired sub-board.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

1-9

1 Creating NEs, Links, and Topology Subnets

OptiX iManager T2000 Operation Guide for PTN NE Management

----End

1.5 Creating Links

You can create fibers/cables, Ethernet lines, serial port lines, microwave links by using the T2000. 1.5.1 Creating Fibers for PTN Equipment Manually NEs communicate with each other through fibers. After creating boards for each NE, you need to create fibers for further configuration of services. In this situation, you can manually create fibers one by one. 1.5.2 Automatically Creating Radio Links Using the fiber/cable search function, you can know whether any radio links are connected at a specified IF interface. This helps you quickly create radio links at the IF interface. For a newly created network, you can search for all the IF interfaces networkwide to create radio links after you complete the board configuration on the T2000. In this way, you can monitor the actual working state of each radio link. 1.5.3 Manually Creating Radio Links After you manually fill in the table, the T2000 can create radio links according to the configuration information about the links. This operation is often used when actual radio link is not formed. 1.5.4 Creating DCN Communication Cable The T2000 can communicate with NEs through the Ethernet port or serial port. Depending on the communication mode, different types of cables can be created on the T2000.

1.5.1 Creating Fibers for PTN Equipment Manually

NEs communicate with each other through fibers. After creating boards for each NE, you need to create fibers for further configuration of services. In this situation, you can manually create fibers one by one.

Prerequisite
l l

You must be an NM user with "NE maintainer" authority or higher. The boards to be connected with fibers or cables must be created.

1-10

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

1 Creating NEs, Links, and Topology Subnets

Procedure
Step 1 Right-click in the Main Topology and choose New > Link. The Add Object dialog box is displayed. Step 2 Choose Link > Fiber/Cable from the left pane. Step 3 Click the button in Source NE. Select the source board and port in the Select the source end of the link dialog box. Step 4 Click OK and the cursor changes to a + sign. Step 5 Click the sink NE of the fiber or cable on the Main Topology. Step 6 Click the button in Sink NE. Select the sink board and port in the Select the sink end of the link dialog box.
TIP

When selecting a wrong source or sink NE, right-click and click OK in the Object Selection dialog box to exit.

Step 7 Click OK. Enter the information of the fiber or cable in the Create Fiber/Cable dialog box.

NOTE

Automatically Allocate IP: When you create a fiber/cable, if both ends of the fiber/cable are the PTN equipment, the system can automatically allocate IP addresses to microwave ports, Ethernet ports, and POS ports. If this parameter is set to Yes, the system automatically allocates IP addresses to the ports on the two ends of a fiber after the fiber is created. In this case, after the fiber is created, you can directly configure the static tunnel as required without considering the port IP addresses. To configure the dynamic tunnel, you need to configure the corresponding routing protocol.

Step 8 Click OK. The created fiber or cable appears between the source and sink NEs on the Main Topology. Step 9 Select the fiber you create, right-click and choose Detect Link from the shortcut menu. The Operation Result dialog box is displayed indicating the fiber connection information. ----End
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-11

1 Creating NEs, Links, and Topology Subnets

OptiX iManager T2000 Operation Guide for PTN NE Management

1.5.2 Automatically Creating Radio Links

Using the fiber/cable search function, you can know whether any radio links are connected at a specified IF interface. This helps you quickly create radio links at the IF interface. For a newly created network, you can search for all the IF interfaces networkwide to create radio links after you complete the board configuration on the T2000. In this way, you can monitor the actual working state of each radio link.

Prerequisite
l l

You must be an NM user with "NE maintainer" authority or higher. The IF board for each NE must be created on the T2000.

Context
The radio frequency wireless signals within the frequency range of 300 MHz to 300 GHz are called radio signals. The links that transmit radio signals are called radio links.

Procedure
Step 1 Choose File > Search for Fiber/Cable from the Main Menu. Step 2 In the left-hand pane, select IF interfaces for one or multiple radio NEs. Click Search. A progress bar is displayed.
NOTE

l l l

If you check the Do not search for ports of created fibers on T2000 check box, the system does not search for the ports at which radio links are already created. If you need to check consistency between the created radio links and the actual radio links, do not check this check box. If you check this check box and if all the selected ports radio links are created, a dialog box is displayed after the search is complete, telling that the search domain is empty.

Step 3 After the search is complete, a dialog box is displayed, telling that the operation was successful. Click Close. Step 4 In the Newly Searched Fiber list, select one or multiple radio links. Click Create Fiber/ Cable.
NOTE

When you select one or multiple radio links in the Newly Searched Fiber list, the radio links that conflict with the selected ones are automatically displayed in the Existing Conflicting Fiber list. In this case, refer to Step 5 to delete the conflicting radio links before the creation. During the creation of radio links, if the selected links are all in the Already created state, the system prompts No fiber to create.

Step 5 In the Existing Conflicting Fiber list, select one or multiple conflicting radio links (the Conflict with logical link (Y/N) value of which in the Misconnected Fiber list is displayed as Yes), Click Delete Fiber/Cable. ----End

Subsequent Handling
When the information about the radio link that is created through search is incomplete, you can supplement the information about the radio link by modifying the fiber/cable information.
1-12 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

1 Creating NEs, Links, and Topology Subnets

1.5.3 Manually Creating Radio Links

After you manually fill in the table, the T2000 can create radio links according to the configuration information about the links. This operation is often used when actual radio link is not formed.

Prerequisite
l l

You must be an NM user with "NE maintainer" authority or higher. The boards to be connected with radio links must be created.

Context
Usually, the radio frequency wireless signal within the frequency range of 300 MHz to 300 GHz is called a radio signal. The link that transmits radio signals is called a radio link.

Procedure
Step 1 Click the + sign. shortcut icon on the toolbar of the Main Topology and the cursor changes to a

Step 2 Click the source NE of the radio link on the Main Topology. Step 3 Select the source board and port in the Select the source end of the link dialog box. Step 4 Click OK and the cursor changes to a + sign. Step 5 Click the sink NE of the radio link on the Main Topology. Step 6 Select the sink board and port in the Select the sink end of the link dialog box.
TIP

When selecting the wrong source or sink NE, right-click and click OK in the Object Selection dialog box to exit.

Step 7 Click OK. Enter the information of the fiber or cable in the Create Microwave Link dialog box. Step 8 Click OK. The created radio link appears between the source and sink NEs on the Main Topology. ----End

1.5.4 Creating DCN Communication Cable

The T2000 can communicate with NEs through the Ethernet port or serial port. Depending on the communication mode, different types of cables can be created on the T2000.

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

Procedure
Step 1 Right-click in the blank space of the Main Topology and choose New > Link from the shortcut menu.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-13

1 Creating NEs, Links, and Topology Subnets

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 2 Select a cable type from the expanded items. Step 3 Enter the cable attributes in the right-hand pane. Step 4 Click OK. The cable is displayed on the Main Topology between the T2000 and the GNE. ----End

Postrequisite
If the NEs at the two ends of the DCN communication cables do not belong to the same subnet, you have to return to the upper-level view of the subnet to view the created DCN communication cables.

1.6 Creating a Topology Subnet

The subnet created here is based on a topological concept to facilitate management. In the case of topology objects in the same network area or with similar attributes, you can allocate them in one topology subnet.

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

Background Information
A topology subnet is created only to simplify the user interface and has no impact on the NEs.

Procedure
Step 1 Right-click in the blank space of the Main Topology and choose New > Subnet from the shortcut menu. Step 2 Click the Properties tab in the Add Object dialog box. Enter the attributes of the subnet. Step 3 Click the Select Objects tab. Select the created NEs or subnet from the Available Objects pane. . Click

1-14

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

1 Creating NEs, Links, and Topology Subnets

NOTE

In the case of a similar dialog box for selecting objects,

l l

indicates that to select the objects to be selected on the left to the selected objects on the right. indicates that to select all the objects to be selected on the left to the selected objects on the right.

Step 4 Click OK. Click in the blank space of the Main Topology, the where you clicked. ----End

icon appears in the position

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

1-15

OptiX iManager T2000 Operation Guide for PTN NE Management

2 Configuring Communications

2
About This Chapter

Configuring Communications

The T2000 communicates with NEs and manages and maintains network nodes through a DCN. In the DCN, the T2000 and NEs can be considered as nodes. These nodes are connected by using Ethernet or DCC physical channels. In actual practice, the T2000 and NEs may be located at different floors of the same building, or different buildings or cities. Hence, the T2000 and NEs are usually connected through an external DCN that consists of equipment such as switches and routers. Comparatively, the DCN between NEs is referred to as an internal DCN. The process of configuring the DCN between NEs is described. 2.1 Overview of the Inband DCN Inband DCN refers to the networking mode that uses service paths provided by the managed equipment to realize the management of network equipment. In this mode, the network management information is transmitted over service paths of the equipment. 2.2 Basic Concepts The DCN contains two networking modes, which are inband networking and outband networking. 2.3 Application of the Inband DCN When no special DCN is available for transmitting network management information, you can perform the networking in the inband DCN mode. 2.4 Configuring an Inband DCN This section describes how to configure an inband DCN. 2.5 Configuration Case of the Inband DCN The configuration case of the inband DCN describes the networking mode of the DCN and the configuration method.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

2-1

2 Configuring Communications

OptiX iManager T2000 Operation Guide for PTN NE Management

2.1 Overview of the Inband DCN

Inband DCN refers to the networking mode that uses service paths provided by the managed equipment to realize the management of network equipment. In this mode, the network management information is transmitted over service paths of the equipment.

Objectives and Benefits

A characteristic of the inband DCN mode is the convenient and flexible networking that does not require additional equipment. In this mode, you need not separately provide a network for the DCN and thus save the operation cost.

Realization Principle
As shown in Figure 2-1, in the inband DCN mode, the DCN information and service information share the same path for transmission. Figure 2-1 Inband DCN networking mode
NMS

IP/GRE Tunnel

Ethernet Link

Service DCN Information

2-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

2 Configuring Communications

2.2 Basic Concepts

The DCN contains two networking modes, which are inband networking and outband networking.

Inband DCN Scheme

The inband DCN networking involves using the service channels provided by the managed devices to manage the devices in the network. In this mode, the network management information is transmitted through the service channels of the devices. The inband DCN networking is flexible and does not require additional devices. Figure 2-2 shows the networking diagram. Figure 2-2 Inband networking scheme

NOTE

The devices managed by the T2000 are connected to the IP core network. The NMS center only needs to be connected to the nearby IP devices in the IP core network. You can manage all the devices in the network by configuring the route. The mode of connection between the NMS center and the IP core network is based on the location of the IP devices near the NMS center. If the T2000 and the nearby IP device are in the same equipment room, you can adopt the LAN networking mode. In the case of the long distance transmission, the networking is realized through private line services.

Outband Networking Scheme

The outband networking scheme involves using other channels except service channels to transmit the network management information and thus realizing the network management. Compared with the inband networking, the outband working scheme provides more reliable management channels. When faults occur on the service channels, you can obtain the network management information in time and perform the real-time monitoring. In the outband mode, you need provide a dedicated communication channel as the maintenance channel that is unrelated to the service channel. In the outband networking scheme, the NMS center can set up the DCN network with the equipment managed in various ways, such as the E1 private line or Ethernet. The T2000 manages
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-3

2 Configuring Communications

OptiX iManager T2000 Operation Guide for PTN NE Management

the equipment within the management range through the DCN network. Figure 2-3 shows the networking diagram. Figure 2-3 Outband networking scheme

NOTE

The T2000 uses the dedicated communication channels to transmit the management information to the managed networks.

2.3 Application of the Inband DCN

When no special DCN is available for transmitting network management information, you can perform the networking in the inband DCN mode. When network management information is transmitted through Ethernet ports, the NE distinguishes between network management information and service information by special VLAN ID. When network management information is transmitted through POS or E1 ports, the NE distinguishes between network management information and service information by special MPLS tag.

2.4 Configuring an Inband DCN

This section describes how to configure an inband DCN.

Context
The configuration of an inband DCN includes the following contents: 2.4.1 Setting NE Communication Parameters
2-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

2 Configuring Communications

When configuring the IP Over DCC communication, you need to set the parameters including IP, Subnet Mask, Gateway IP, and Extended ID for the NE. 2.4.2 Setting the VLAN ID and Bandwidth Used by an Inband DCN The PTN equipment communicates with the T2000 in inband DCN mode. The network management information is transmitted with the service information, and the equipment marks the management information with a default VLAN ID. You can adjust the bandwidth of an inband DCN. 2.4.3 Setting the T2000 Access Parameters In the case of the traditional DCN network, the equipment accesses to the T2000 through the SCC board. The PTN equipment can also access to the T2000 through the network interface of the Ethernet board. When the PTN equipment accesses to the T2000 by using the network interface of the Ethernet board, set the access parameters of the Ethernet board for the equipment to communicate with the T2000. 2.4.4 Enabling the Port DCN The NM information can be transported in the inband DCN only when the DCN access function is enabled for the ports at two ends of the link. 2.4.5 Enabling the Tunnel DCN The NM information can be transported in the IP/GRE Tunnel only when the DCN access function is enabled for the IP/GRE tunnel.

2.4.1 Setting NE Communication Parameters

When configuring the IP Over DCC communication, you need to set the parameters including IP, Subnet Mask, Gateway IP, and Extended ID for the NE.

Prerequisite
l l

You must be an NM user with "NE maintainer" authority or higher. The IP GNE must be created.

Context

CAUTION
The operation of modifying the NE communication parameters interrupts the communication and affects the services.

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > Communication Parameters from the Function Tree. Step 2 Set the NE communication parameters, including IP, Subnet Mask, Gateway IP, Extended ID. Step 3 Click Apply and then click OK in the Warning dialog box that appears twice. Click Close in the Operation Result dialog box. ----End
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-5

2 Configuring Communications

OptiX iManager T2000 Operation Guide for PTN NE Management

2.4.2 Setting the VLAN ID and Bandwidth Used by an Inband DCN

The PTN equipment communicates with the T2000 in inband DCN mode. The network management information is transmitted with the service information, and the equipment marks the management information with a default VLAN ID. You can adjust the bandwidth of an inband DCN.

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

Context
l

If the default VLAN ID of the DCN conflicts with the VLAN ID used by the service, manually modify the VLAN ID of the DCN to ensure that the networkwide DCN uses the same VLAN ID. If the DCN packets do not use all the available bandwidth, the idle bandwidth can be shared with the service packets. It is recommended to perform the modification on non-gateway NEs and then the gateway NE, to prevent the non-gateway NEs from being unreachable to the T2000.

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCN Management from the Function Tree. Step 2 Click the Bandwidth Management tab, and enter parameters.

NOTE

When setting the parameters, note the following points:

l l

Click Default to adopt the default value. Generally, use the default VLAN ID. When the VLAN ID used by a service conflicts with that used by a DCN channel, you can define another VLAN ID. Make sure that the networkwide VLAN ID is consistent.

Step 3 Click Apply. ----End

2.4.3 Setting the T2000 Access Parameters

In the case of the traditional DCN network, the equipment accesses to the T2000 through the SCC board. The PTN equipment can also access to the T2000 through the network interface of
2-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

2 Configuring Communications

the Ethernet board. When the PTN equipment accesses to the T2000 by using the network interface of the Ethernet board, set the access parameters of the Ethernet board for the equipment to communicate with the T2000.

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

Context
NOTE

l l

You need to set the parameters only when the T2000 accesses the equipment by using an Ethernet service board. By default, the Enabled Status is Disabled.

CAUTION
In the case of the OptiX PTN equipment, when the DCN port is interconnected to the T2000, the IP address of the T2000 and the IP address of the NNI should not be set to the same subnet. This operation may affect the communication between the T2000 and NEs.

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCN Management from the Function Tree. Step 2 Click the Access Control tab, and enter parameters.

Step 3 Click Apply. ----End

2.4.4 Enabling the Port DCN

The NM information can be transported in the inband DCN only when the DCN access function is enabled for the ports at two ends of the link.

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

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

2-7

2 Configuring Communications

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCN Management from the Function Tree. Step 2 Click the Port Settings tab. Step 3 Select different interface types, and set the corresponding attributes.

NOTE

Take the following precautions when enabling the DCN:

l l l

When you configure an Ethernet service that exclusively uses a port, disable the DCN function of the port. When an E1 port accesses the CES and IMA services, disable the DCN function of the port. After you enable DCN for an port, the VLAN IDs of other services configured for the port cannot be the same as the VLAN IDs of DCN packets.

Step 4 Click Apply. ----End

2.4.5 Enabling the Tunnel DCN

The NM information can be transported in the IP/GRE Tunnel only when the DCN access function is enabled for the IP/GRE tunnel.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCN Management from the Function Tree. Step 2 Click the Tunnel Settings tab. Step 3 Select different tunnel types, and set the corresponding attributes. Step 4 Click Apply. ----End

2.5 Configuration Case of the Inband DCN

The configuration case of the inband DCN describes the networking mode of the DCN and the configuration method.

2-8

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

2 Configuring Communications

2.5.1 Networking and Requirements The PTN equipment provides multiple types of links that carry inband DCN packets. Hence, the PTN equipment has a powerful ability to manage communication and is applicable to complex networks. 2.5.2 Service Planning To plan a service is to design the details of a service to be created according to the service requirements. Service planning provides guidelines for service configuration. The service planning covers details such as the networking, requirements, and configuration data. 2.5.3 Configuring an Inband DCN You can set the parameters related to communication and DCN management according to the networking requirements and service planning. 2.5.4 Configuring an IP Tunnel GNE1 needs to traverse the third-party network to manage NE4. Hence, you can configure an IP tunnel on a per-NE basis to carry inband DCN packets. 2.5.5 Configuring an ML-PPP Link You can configure an ML-PPP link binding E1 port between GNE1 and NE3 to carry inband DCN packets. 2.5.6 Configuring a Radio Link You can configure a radio link that is used between NE3 and NE5 to carry DCN packets.

2.5.1 Networking and Requirements

The PTN equipment provides multiple types of links that carry inband DCN packets. Hence, the PTN equipment has a powerful ability to manage communication and is applicable to complex networks. In Figure 2-4, NE1 and NE2 are the OptiX PTN 3900, and NE3, NE4, and NE5 are the OptiX PTN 950. The NMS communicates with GNE1 through TCP/IP, and manages other NEs through GNE1. The links that carry DCN packets between NEs and the GNE are as follows:
l

If GNE1 manage NE4, a remote NE, the tunnel between them traverses a third-party network. In this example, an IP tunnel is used between NE4 and GNE1 to carry DCN packets. An ML-PPP link is used between NE3 and GNE1 to carry DCN packets. An Ethernet link is used between NE2 and GNE1 to carry DCN packets. A radio link is used between NE5 and NE3 to carry DCN packets, and NE3 forwards the DCN packets to GNE1.

l l l

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

2-9

2 Configuring Communications

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 2-4 Inband networking application

NMS

129.9.0.10/24 129.9.0.2/24 Router IP Network GNE1 192.168.2.1/24 7-EG16-1(Port-1) 25-D75-Port 1-3 192.168.1.1/24 6-ML1-Port 1-3 ML-PPP NE2 5-IFE2-25-ODU NE3 192.168.1.3/24 5-IFE2-25-ODU Node B NE5 192.168.1.5/24 192.168.1.2/24 RNC 7-EG16-1(Port-1) 7-EG16-2(Port-2) 192.168.1.0/24

Node B

NE4 192.168.1.4/24

3-EG2-1(Port-1) 192.168.2.4/24

PTN 3900 Radio link

PTN 950 Physical link IP Tunnel

2.5.2 Service Planning

To plan a service is to design the details of a service to be created according to the service requirements. Service planning provides guidelines for service configuration. The service planning covers details such as the networking, requirements, and configuration data. Figure 2-4 illustrates the configuration of each NE based on the inband DCN link that the NE carries. Refer to Table 2-1, Table 2-2, Table 2-3, and Table 2-4. Table 2-1 Planning of the parameters for the inband DCN configuration Attribute Station Band width Mana geme nt Ether net Board VLA N ID Value GNE1 4094 NE2 4094 NE3 NE4 4094 NE5 -

2-10

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

2 Configuring Communications

Attribute Band width (kbps) E1 Port Band width (kbps) IF Port Band width (kbps) Tunne l (kbps) Port Settin gs Enabl e the inban d DCN port.

Value 512 512 512 -

192

192

512

512

512

512

7-EG16-1 (Port-1), 7EG16-2 (Port-2), 25-D75-1 (E1-1), 25D75-2 (E1-2), 25 D75-3 (E1-3) Enabled

7-EG16-2 (Port-2)

6-ML1-1 (E1-1), 6ML1-1 (E1-2), 6ML1-1 (E1-3), 5IFE21 (Port-1)

3-EG2-1 (Port-1)

5-IFE2-1 (Port-1)

Tunne l Settin gs

Enabl ed Status

Enabled

Table 2-2 Planning of the parameters for the ML-PPP link between GNE1 and NE3 Attribute Station MP Group Number Name Specify IP IP Address IP Mask Value GNE1 1 mlppp01 Unnumbered NE IP NE3 1 mlppp01 Unnumbered NE IP -

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

2-11

2 Configuring Communications

OptiX iManager T2000 Operation Guide for PTN NE Management

Attribute Board for Unnumbered IP Port for Unnumbered IP Min Activated Link Count Enabled Differential Delay Max Differential Delay (100us) Enabled Tunnel Sequence Number Type Board Member Interface

Value 1 Enabled 25 Enabled Short 25-D75 25-D75-1(Port-1) 25-D75-2(Port-2) 25-D75-3(Port-3) 1 Enabled 25 Enabled 6-ML1 6-ML1-1(Port-1) 6-ML1-2(Port-2) 6-ML1-3(Port-3)

Table 2-3 Planning of the parameters for the IP tunnel between GNE1 and NE4 Attribute Station UDP PW Port Size (K) Start of UDP PW Port Size Tunnel ID Source Board Source Port Destination IP Value GNE1 1 49152 1 7EG16 1(Port-1) 192.168.2.4 NE4 1 49152 1 3-EG2 1(Port-1) 192.168.2.1

Table 2-4 Planning of the parameters for the radio link between NE3 and NE5 Attribute Station Enable AM Value NE3 Enabled NE5 Enabled

2-12

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

2 Configuring Communications

Attribute Channel Space Assured Capacity Modulation Full Capacity Modulation Link ID TX Frequency Attributes (MHz) T/R Spacing (MHz) TX Power (dBm) TX High Threshold TX Low Threshold RX High Threshold RX Low Threshold TX Status

Value 7.0M QPSK 128QAM 1 22017.000 1008.000 -10.0 35.0 -10.0 -20.0 -90.0 unmute 7.0M QPSK 128QAM 1 23025.000 1008.000 -10.0 35.0 -10.0 -20.0 -90.0 unmute

2.5.3 Configuring an Inband DCN

You can set the parameters related to communication and DCN management according to the networking requirements and service planning.

Prerequisite
You must be an NM user with "NM operator" authority or higher. You must understand the networking, requirements and service planning of the example.

Context
NOTE

When you configure an inband DCN, it is recommended that you configure a remote NE and then a local NE. Otherwise, if a local NE is modified. the DCN is unavailable and you cannot configure the remote NE.

Procedure
Step 1 Set the communication parameters for each NE. 1. 2. In the NE Explorer, select NE5 and choose Communication > Communication Parameters from the Function Tree. Set the NE communication parameters, and clickApply.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

2-13

2 Configuring Communications

OptiX iManager T2000 Operation Guide for PTN NE Management

3.

Set the communication parameters for NE4, NE3, NE2, and GNE1 by referring to Step 1.1 to Step 1.2. The communication parameters for each NE are as follows:
l

The IP addresses of NE4, NE3, NE2, and GNE1: 192.168.1.4, 192.168.1.3, 192.168.1.2, 192.168.1.1 Subnet mask: 255.255.255.0

Step 2 Configure the GNE for NE5, NE4, NE3, and NE2 to GNE1. 1. 2. Choose System > DCN Management from the Main Menu. Click the NE tab. Set the Primary GNE1 of NE5, NE4, NE3, and NE2 to GNE1. Click Apply.

Step 3 Configure the bandwidth of the inband DCN. 1. 2. In the NE Explorer, select NE5 and choose Communication > DCN Management from the Function Tree. In the right-hand pane, click Bandwidth Management and set IF Port Bandwidth (kbps) to 512. Then, click Apply.

3.

Set the inband DCN bandwidth for NE4, NE3, NE2, and GNE1 by referring to Step 3.1 to Step 3.2. Set the parameters related to the bandwidth of the inband DCN of GNE1 as follows:
l

Ethernet Board VLANID: 4094 (By default, the VLAN ID of the inband DCN is 4094. The VLAN ID must be consistent on the entire network.) Bandwidth (kbps): 512 E1 Port Bandwidth (kbps): 192 (An E1 port is used to create an ML-PPP link between GNE1 and NE3 to carry inband DCN packets.)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

l l

2-14

OptiX iManager T2000 Operation Guide for PTN NE Management

l

2 Configuring Communications

Tunnel Bandwidth (kbps): 512 (Used to carry the inband DCN between GNE1 and NE4.)

Set the parameters related to the bandwidth of the inband DCN of NE2 as follows:
l

Ethernet Board VLANID: 4094 (By default, the VLAN ID of the inband DCN is 4094. The VLAN ID must be consistent on the entire network.) Bandwidth (kbps): 512 (Configure the bandwidth of the inband DCN between NE2 and GNE1.)

Set the parameters related to the bandwidth of the inband DCN of NE3 as follows:
l

E1 Port Bandwidth (kbps): 192 (An E1 port is used to create an ML-PPP link between NE3 and GNE1 to carry inband DCN packets.) IF Port Bandwidth (kbps): 512 (Configure the bandwidth of the inband DCN between NE3 and NE5.)

Set the parameters related to the bandwidth of the inband DCN of NE4 as follows:
l

Tunnel Bandwidth (kbps): 512 (Used to carry the inband DCN between NE4 and GNE1.)

Step 4 Set the status of the port used by each NE. 1. 2. 3. In the NE Explorer, select NE5 and choose Communication > DCN Management from the Function Tree. In the right-hand pane, click Port Settings and select IF. Set Enabled Status of the 4-IFE2-1(Port-1) port to Enabled. Then, click Apply.

4.

Enable the ports used by NE4, NE3, NE2, and GNE1 by referring to Step 4.1 to Step 4.3. The ports that need to be enabled for NE4, NE3, NE2, and GNE1 are as follows:
l l

Set the FE/GE port 3-EG2-1(PORT-1) on NE4 to Enabled. Set the E1 ports 6-ML1-1(E1-1), 6-ML1-1(E1-2), and 6-ML1-1(E1-3) and the IF port 4-IFE2-1(PORT-1) on NE3 to Enabled. Set the ETH port 7-EG16-2(PORT-2) on NE2 to Enabled. Set the ETH ports 7-EG16-1(PORT-1) and 7-EG16-2(PORT-2) and the E1 ports 25D75-1(E1-1), 25-D75-2(E1-2), 25-D75-3(E1-3) on GNE1 to Enabled.
NOTE

l l

After you enable DCN for an port, the VLAN IDs of other services configured for the port cannot be the same as the VLAN IDs of DCN packets.

----End

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

2-15

2 Configuring Communications

OptiX iManager T2000 Operation Guide for PTN NE Management

2.5.4 Configuring an IP Tunnel

GNE1 needs to traverse the third-party network to manage NE4. Hence, you can configure an IP tunnel on a per-NE basis to carry inband DCN packets.

Prerequisite
You must be an NM user with "NM operator" authority or higher. You must understand the networking, requirements and service planning of the example.

Procedure
Step 1 Set the port parameters for each NE. 1. 2. In the NE Explorer, select NE4 and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Click the General Attributes tab. Set the parameters related to the basic attributes of a port, and click Apply.

Set the related parameters as follows:

l l l

Enabled Port: Enabled Port Mode: Layer 3 (carry tunnel) Working Mode: Auto-Negotiation (Set the working modes of the local port and opposite port as the same.) Max Frame Length (byte): 1020 (The maximum length of a DCN packet is 1020 according to the setting of the DCN packet length.)

3.

Click the Layer 3 Attributes tab. Set the parameters related to the Layer-3 attributes of the 3-EG2-1(Port-1) port, and click Apply. Set the related parameters as follows:
l l

Enabled Tunnel: Enabled MaxReserved Bandwidth (kbit/s): 102400 (The maximum reserved bandwidth should not exceed the physical bandwidth of the bearer port.) TE Measurement: 10 (You can intervene in the route selection by adjusting the TE measurement of the link. The smaller the value of the TE measurement, the higher the priority of the link.) Specify IP: Manually (Manually indicates that you can set the IP address of the port.) IP Address: 192.168.2.4 IP Mask: 255. 255.255.0

l l l

4.

In the NE Explorer of GNE1, set the parameters related to the 7-EG16-1(Port-1) port on GNE1 by referring to Step 1.1 to Step 1.3. The 7-EG16-1(Port-1) port on GNE1 has the same parameter settings as the 3-EG2-1 (Port-1) port on NE4. The IP address is 192.168.2.1.

2-16

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

2 Configuring Communications

Step 2 Configure the IP tunnel that carries inband DCN packets between NE4 and GNE1. 1. 2. In the NE Explorer, select NE4 and choose Configuration > IP/GRE Tunnel Management > Basic Configuration from the Function Tree. Set the parameters related to the basic attributes of a UDP PW port, and click Apply. The parameters related to the basic attributes of the UDP PW port on NE4 are as follows:
l l

UDP PW Port Size (K): 1 Start of UDP PW Port Size: 49152

3. 4.

Choose Configuration > IP/GRE Tunnel Management > IP Tunnel Management from the Function Tree. Click New. In the Create IP Tunnel dialog box, set the related parameters and click Apply.

The parameters related to the IP tunnel on NE4 are as follows:

l l l l

Tunnel ID: 1 Source Board: 3-EG2 Source Port: 1 (Port-1) Destination IP: 192.168.2.1 (Set the IP address as the IP address of the 7-EG16-1(Port-1) port on GNE1.)

5.

Configure an IP tunnel on GNE1 by referring to Step 2.1 to Step 2.4. Set the Source Board of the IP tunnel on GNE1 to 7-EG16, and set Destination IP to 192.168.2.4. Use the same values for the UDP PW port and other IP tunnel parameters as the values for NE4.

Step 3 Enable the IP tunnel between GNE1 and NE4. 1. 2. In the NE Explorer, select NE4 and choose Communication > DCN Management from the Function Tree. Click the Tunnel Settings tab. Select IP Tunnel, set the parameters related to the IP tunnel that carries the inband DCN packets, and then click Apply.

The parameters related to the IP tunnel on NE4 are as follows:

l

Enabled Status: Enabled

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-17

Issue 01 (2009-06-30)

2 Configuring Communications
l l

OptiX iManager T2000 Operation Guide for PTN NE Management

Encapsulation Format: UDP UDP Port ID: 49125

3.

Enable the IP tunnel that carries the inband DCN packets on GNE1 by referring to Step 3.1 to Step 3.2.

----End

2.5.5 Configuring an ML-PPP Link

You can configure an ML-PPP link binding E1 port between GNE1 and NE3 to carry inband DCN packets.

Prerequisite
You must be an NM user with "NM operator" authority or higher. You must understand the networking, requirements and service planning of the example.

Procedure
Step 1 Set the parameters related to the member port on the ML-PPP link between GNE1 and NE3. 1. 2. In the NE Explorer, select GNE1 and choose Configuration > Interface Management > PDH Interface from the Function Tree. Click the General Attributes tab. Set the parameters related to the basic attributes of a port, and click Apply.

The parameters related to the port are as follows:

l l l

Port Mode: Layer 3 Encapsulation Type: PPP Max Data Packet Size (byte): 1020 (The maximum length of a DCN packet is 1020 according to the setting of the DCN packet length.)

3.

In the NE Explorer of NE3, set the parameters related to the PDH port on NE3 by referring to Step 1.1 to Step 1.2. The PDH ports 6-ML1-1(Port-1), 6-ML1-2(Port-2), and 6-ML1-3(Port-3) on NE3 have the same parameter settings as the PDH port on GNE1.

Step 2 Configure the ML-PPP link that carries inband DCN packets between GNE1 and NE3. 1. 2. In the NE Explorer, select NE3 and choose Configuration > Interface Management > MP Group Management from the Function Tree. Click New. In the New MP Group dialog box, set the related parameters and click Apply.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

2-18

OptiX iManager T2000 Operation Guide for PTN NE Management

2 Configuring Communications

The parameters related to the ML-PPP link on NE3 are as follows:

l l l

MP Group Number: 100 MP Group Name: mlppp01 Specify IP: Unnumbered NE IP (If you select Manually or Unnumbered Port IP, you need to set the IP address and IP mask, or the board corresponding to the unnumbered IP and the port corresponding to the unnumbered IP.) Min Activated Link Count: 1 (You can activate an MP group only when the number of active links in the MP group reaches the value that you set here.) Enable Differential Delay: Enabled Max Differential Delay (100us): 500 (When the difference between the delay of a link and the delay of another link is more than 25 ms, the link is unavailable.) Enabled Tunnel: Enabled Sequence Number Type: Short (You must set this parameter to Short when the equipment is interconnected to the PTN 3900.) Board: 6-ML1 Member Interface: 6-ML1-1(Port-1), 6-ML1-2(Port-2), 6-ML1-3(Port-3)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-19

l l

l l

l l

Issue 01 (2009-06-30)

2 Configuring Communications

OptiX iManager T2000 Operation Guide for PTN NE Management

3.

Configure an ML-PPP link on GNE1 by referring to Step 2.1 to Step 2.2. The parameters related to the ML-PPP link on NE3 are as follows:
l l l

MP Group Number: 100 MP Group Name: mlppp01 Specify IP: Unnumbered NE IP (If you select Manually or Unnumbered Port IP, you need to set the IP address and IP mask, or the board corresponding to the unnumbered IP and the port corresponding to the unnumbered IP.) Min Activated Link Count: 1 (You can activate an MP group only when the number of active links in the MP group reaches the value that you set here.) Enable Differential Delay: Enabled Max Differential Delay (100us): 500 (When the difference between the delay of a link and the delay of another link is more than 25 ms, the link is unavailable.) Enabled Tunnel: Enabled Board: 25-D75 Member Interface: 25-D75-1(Port-1), 25-D75-2(Port-2), 25-D75-3(Port-3)

l l

l l l

----End

2.5.6 Configuring a Radio Link

You can configure a radio link that is used between NE3 and NE5 to carry DCN packets.

Prerequisite
You must be an NM user with "NM operator" authority or higher. You must understand the networking, requirements and service planning of the example.

Procedure
Step 1 Set port parameters for each NE. 1. 2. In the NE Explorer, select NE3 and choose Configuration > Interface Management > Microwave Interface from the Function Tree. Click the General Attributes tab. Set the parameters related to the basic attributes of a port, and click Apply.

Set the related parameters as follows: The parameters related to the basic attributes of the microwave interface 5-IFE2-1 (PORT-1) on NE3 are as follows:
l l

Port Mode: Layer 3 MTU (byte): 1020

The parameters related to the IF attributes of the microwave interface 5-IFE2-(PORT-1) on NE3 are as follows:
2-20 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

l

2 Configuring Communications

Enable: Enabled (If you set this parameter to Enabled, the radio link uses the corresponding modulation format based on the conditions of a channel.) Channel Space: 7.0M (You can set this parameter based on the usage status of a channel.) Guaranteed Capacity Modulation Format: QPSK (The lowest-efficiency AM mode.) Full Capacity Modulation Format: 128QAM (The highest-efficiency AM mode.) Enable ATPC: Enabled (The ATPC function enables the transmit power of a transmitter to automatically track the change of the received signal level (RSL) at the receive end within the ATPC control range.) ATPC Upper Threshold (0.1dBm): -250 (If you enable ATPC, when the RSL at the receive end is higher than the preset upper ATPC threshold, the receiver notifies the transmitter to decrease the transmit power according to the preset ATPC adjustment increment at the transmit end until the RSL is lower than the upper ATPC threshold.) ATPC Lower Threshold (0.1dBm): -400 (If you enable ATPC, when the RSL at the receive end is lower than the preset lower ATPC threshold, the receiver notifies the transmitter to increase the transmit power according to the preset ATPC adjustment increment at the transmit end until the RSL is higher than the lower ATPC threshold.) ATPC Adjustment (0.1dBm): 50 (The variation of the transmit power caused by an ATPC adjustment.)

l l l l

The parameters related to the advanced attributes of the microwave interface 5-IFE2-1 (PORT-1) on NE3 are as follows:
l

Radio Link ID: 1 (The link IDs of different radio links on the same NE cannot be duplicate, but the two ends of a radio link must have the same link ID.) Error Frame Discard Enabled: Enabled

3.

In the NE Explorer of NE5, set the parameters related to the 5-IFE2-1(Port-1) port on NE5 by referring to Step 1.1 to Step 1.2. The microwave port 5-IFE2-1(Port-1) on NE5 have the same parameter settings as the microwave port on NE3.

Step 2 Configure the radio link that carries inband DCN packets between NE5 and NE3. 1. 2. In the NE Explorer, select NE5 and choose Configure > Link Configuration from the Function Tree. In the right-hand pane, set the parameters related to an ODU and click Apply.

The parameters related to 25-ODU on NE5 are as follows:

l

TX Frequency (MHz): 23025.000 (The difference between the transmit power of the two ends of a link must be the same as the value of T/R Spacing (MHz))
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-21

Issue 01 (2009-06-30)

2 Configuring Communications
l

OptiX iManager T2000 Operation Guide for PTN NE Management

T/R Spacing (MHz): 1008.000 (Set the interval between the transmit frequency and the receive frequency of an ODU board to avoid mutual interference.) TX Power (dBm): -10.0 (Sets this value to a smaller value as much as possible to prolong the life span of an ODU when the receive power requirements of the opposite ODU are met.) TX High Threshold: 35.0 TX Low Threshold: -10.0 RX High Threshold: -20.0 RX Low Threshold: -90.0 TX Status: unmute (In the transmit state, microwave signals can be transmitted and can also be received.)

l l l l l

3.

Set the parameters related to the radio link on NE3 by referring to Step 2.1 to Step 2.2. Set the TX Frequency (MHz) of the ODU on NE3 to 22017.000. Use the same values for other parameters as the values for NE5.

----End

2-22

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

3 Configuring the NE Time

3
About This Chapter

Configuring the NE Time

Time consistency between the T2000 and NEs is very important for troubleshooting and network monitoring. You should set the T2000 time and NE time before service configuration. 3.1 Time Synchronization Schemes for the T2000 and NEs With the time synchronization function, consistency is maintained between the NE time and the T2000 server time. In this way, the T2000 is able to record the correct time at which alarms occur and the correct time at which the abnormal events are reported by NEs. 3.2 Synchronizing the NE Time with the T2000 Server Automatically The NE time can be automatically synchronized with the T2000 server time. In this way, the time of alarms and logs can be correctly recorded in the T2000. 3.3 Synchronizing the NE Time with the T2000 Server Manually In the case of NEs that do not have the NTP service configured, you need to check whether the NE time is consistent with the T2000 server time, so that the T2000 can correctly record the time of alarm generation. Otherwise, manually synchronize the NE time with the time of the T2000 server. 3.4 Setting Time Localization on NEs You can set time localization on NEs to ensure the consistent time displayed on NEs and the T2000.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

3-1

3 Configuring the NE Time

OptiX iManager T2000 Operation Guide for PTN NE Management

3.1 Time Synchronization Schemes for the T2000 and NEs

With the time synchronization function, consistency is maintained between the NE time and the T2000 server time. In this way, the T2000 is able to record the correct time at which alarms occur and the correct time at which the abnormal events are reported by NEs. When NEs report alarms and abnormal events to the T2000, the time at which such alarms and events occur is based on the NE time. If the NE time is incorrect, then the wrong time with regard to the occurrence of alarms is recorded in the T2000. This may cause trouble in fault location. In addition, the wrong time with regard to the occurrence of abnormal events is recorded in the NE security logs. To ensure the NE time accuracy, the T2000 provides time synchronization schemes: synchronizing with the T2000 server and synchronizing with the standard NTP server.
l

If you use the scheme of synchronizing with the T2000 server, all NEs use the T2000 server time as the standard time. The NE time can be synchronized with the T2000 server time manually or automatically. The T2000 server time refers to the system time of the workstation or computer where the T2000 server resides. This scheme features easy operation, and is applicable in networks that require a low accuracy with regard to time.

3.2 Synchronizing the NE Time with the T2000 Server Automatically

The NE time can be automatically synchronized with the T2000 server time. In this way, the time of alarms and logs can be correctly recorded in the T2000.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The NTP service must not be configured for the T2000 and NEs.

Procedure
Step 1 Choose Configuration > NE Time Synchronization from the Main Menu. Step 2 In the Object Tree, select one or more NEs and click the double-right-arrow button (red). Step 3 Click Close in the Operation Result dialog box. Step 4 Set the Synchronous Mode to NM and click Apply. Step 5 Click Close in the Operation Result dialog box. Step 6 Set the Synchronization Starting Time and Synchronization Period (days) in the lower pane. Click Apply.
NOTE

The Synchronization Starting Time cannot be earlier than the current time.

Step 7 Click Yes in the confirmation dialog box. Step 8 Click Close in the Operation Result dialog box. ----End
3-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

3 Configuring the NE Time

3.3 Synchronizing the NE Time with the T2000 Server Manually

In the case of NEs that do not have the NTP service configured, you need to check whether the NE time is consistent with the T2000 server time, so that the T2000 can correctly record the time of alarm generation. Otherwise, manually synchronize the NE time with the time of the T2000 server.

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

Background Information
Synchronizing the NE time does not affect services. Before synchronizing the NE time, verify that the system time on the T2000 server is correct. If you want to change the system time, exit the T2000 to reset the time and then start the T2000 again.

Procedure
Step 1 Choose Configuration > NE Time Synchronization from the Main Menu. Step 2 In the Object Tree, select one or more NEs and click Step 3 Click Close in the Operation Result dialog box. Step 4 Select one or more NEs in the list, right-click and choose Synchronize with NM Time from the shortcut menu. Step 5 Click Yes in the Time Synchronization Operation prompt box. Click Close in the Operation Result dialog box. Step 6 Click Apply. Click Close in the Operation Result dialog box. ----End .

3.4 Setting Time Localization on NEs

You can set time localization on NEs to ensure the consistent time displayed on NEs and the T2000. 3.4.1 Setting a Time Zone for an NE You can set the time zone where an NE is located. 3.4.2 Setting DST on NEs Different regions have a different DST. You need to set the DST to ensure that the display time for history data in the T2000 can be correctly transited.

3.4.1 Setting a Time Zone for an NE

You can set the time zone where an NE is located.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 3-3

3 Configuring the NE Time

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 Choose System > NE Time Localization Management from the Main Menu. Step 2 In the Object Tree, select an NE and click the double-right-arrow button (red). Step 3 Click Query to query the time zone for an NE. Step 4 Double-click TimeZone and select a time zone from the drop-down list.

NOTE

l l

You can modify the NE time zone setting for many times according to the actual situation. The old time data in the NE may be incorrect. Hence, the correctness of the time displayed in the NE cannot be guaranteed after the NE time zone is changed.

Step 5 Click Apply. A prompt is displayed indicating that the operation is successful. Click Close. ----End

3.4.2 Setting DST on NEs

Different regions have a different DST. You need to set the DST to ensure that the display time for history data in the T2000 can be correctly transited.

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

Procedure
Step 1 Choose System > NE Time Localization Management from the Main Menu. Step 2 In the Object Tree, select an NE and click the double-right-arrow button (red). Step 3 Click Query to query the time zone for an NE. Step 4 Double-click DST and select Enabled from the drop-down list.

3-4

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

3 Configuring the NE Time

Step 5 Set the DST attributes, including DST Rule, DST Offset, Start Time and Stop Time. Step 6 Click Apply. A prompt is displayed indicating that the operation is successful. Click Close. ----End

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

3-5

OptiX iManager T2000 Operation Guide for PTN NE Management

4 Configuring Clocks

4
About This Chapter

Configuring Clocks

A clock is the basis for the normal running of NEs. You must configure clocks for all NEs prior to configuring services. In addition, you need to configure clock protection for complex networks. 4.1 Setting the Frequency Selection Mode The OptiX PTN equipment supports two synchronization modes, that is, physical synchronization mode and PTP synchronization mode. The frequency source selection mode is used to set the clock synchronization mode of the NE. Before configuring the IEEE 1588 clock, you should set the frequency source selection mode to the PTP synchronization mode. 4.2 Configuring the NE Clock Source Before configuring services, you must configure the NE clock source and specify the priority level to ensure that correct clock trace relations are created for all the NEs in the network. 4.3 Configuring the Clock Source Protection In a complicated clock network, you need to configure the clock protection for all NEs. After you set the clock source and specify the clock priority level for the NEs, you can enable the standard SSM or extended SSM protocol to prevent the NEs from tracing an incorrect clock source. This is how the clocks are protected. 4.4 Configuring Switching Conditions for Clock Sources If the traceable clock source of an NE is line clock, you can customize switching conditions for the clock source, so that the NE switches to other clocks when the clock source fails. In this manner, services are less affected. 4.5 Configuring the Clock Source Reversion When there are multiple clock sources for an NE, set the clock sources to automatic reversion mode, so that the deteriorated clock source automatically becomes the traceable timing reference after it recovers. 4.6 Configuring the Phase-Locked Source for External Clock Output When a clock signal passes through 14 or more NEs, frequency offset and drift may occur. As a result, the clock signal transmitted to the downstream NE is degraded. To avoid clock signal degrade, you need to set a 2M phase-locked source to optimize the clock signal. 4.7 Setting the Clock Source Quality In a complex clock network, there may be some unknown clock sources. You can uniformly define these clock sources as unavailable clocks so that NEs do not trace wrong clock sources.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 4-1

4 Configuring Clocks

OptiX iManager T2000 Operation Guide for PTN NE Management

The NE obtains their quality information automatically for clock sources that are allocated to an NE. You should define the quality level of clock sources only during test and maintenance. 4.8 Configuring the SSM Output If the standard SSM or extended SSM protocol is enabled, the clock signals carry SSM messages automatically. You can prevent clock sources from sending SSM messages to other clock subnets. This helps you to ensure that the equipment of different clock subnets do not affect each other at the edge of clock networks. 4.9 Switching a Clock Source When the traceable clock source in a network deteriorates, NEs may not be able to execute a switch on the clock source. You need to manually switch the clock source to prevent clock deterioration from affecting the normal running of NEs. 4.10 Setting the Attributes of the External Time Interface If the equipment uses the external time interface to input or output time signals, you should set the corresponding interface attributes. The external time interface attributes include the basic attribute, BMC, and cable transmitting distance. The cable transmitting distance is used to compensate the time for the equipment. 4.11 Configuring a Clock Domain The clocks output by a port include the system clock and ACR clock. For easy management, each clock is considered as a clock domain. By default, all the ports are in a system clock domain. When the ACR clock is used, the port should be bound with the ACR clock domain. 4.12 Configuring an ACR Clock The equipment can select one CES service from multiple CES services and recover the clock from the selected CES service. After the recovered ACR clock is bound with the clock domain, the ACR clock can be used as a system clock.

4-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

4 Configuring Clocks

4.1 Setting the Frequency Selection Mode

The OptiX PTN equipment supports two synchronization modes, that is, physical synchronization mode and PTP synchronization mode. The frequency source selection mode is used to set the clock synchronization mode of the NE. Before configuring the IEEE 1588 clock, you should set the frequency source selection mode to the PTP synchronization mode.

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

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > Frequency Selection Mode from the Function Tree. Step 2 In Select Frequency Source Mode, you can select one of the clock synchronization mode.

CAUTION
l

When the external time interface is set to the external time input interface, the NE can run in only the physical synchronization mode. That is, the frequency selection mode of the equipment that accesses the external clock must be set to the physical synchronization mode. When the NE is running in the PTP synchronization mode, the external interface cannot be set to the external time input interface.

Step 3 Click Apply. ----End

4.2 Configuring the NE Clock Source

Before configuring services, you must configure the NE clock source and specify the priority level to ensure that correct clock trace relations are created for all the NEs in the network.

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

Context
To implement clock protection, you must configure at least two traceable clock sources for the equipment. Usually, the tributary clock is not used as the clock source for the equipment. After you set the clock sources for all the NEs, query the networkwide clock trace status again. For details, see Viewing the Clock Trace Search.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 4-3

4 Configuring Clocks

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Clock > Clock Source Priority from the Function Tree. Step 2 Click Query to query the existing clock source. Step 3 Click Create. In the Add Clock Source dialog box, select a new clock source and click OK. Step 4 Optional: If an external clock source is selected, select External Clock Source Mode according to the type of external clock signals. For 2 Mbit/s clocks, specify the Synchronous Status Byte to deliver SSM message. Step 5 Select a clock source, and click or to adjust its priority level. The clock sources are arranged in the descending order. The clock source on top is the preferred one for the NE.
NOTE

Internal clock sources have the lowest priority because of their low precision.

Step 6 Click Apply. In the Operation Result dialog box, click Close.
NOTE

If the clock trace relation changes because of the clock source change, the Prompt dialog box is displayed, asking you whether to refresh the clock trace relation. Usually you can click OK. If you select Disable Prompting Next Time, the Prompt dialog box is not displayed even when the clock trace relation changes.

----End

4.3 Configuring the Clock Source Protection

In a complicated clock network, you need to configure the clock protection for all NEs. After you set the clock source and specify the clock priority level for the NEs, you can enable the standard SSM or extended SSM protocol to prevent the NEs from tracing an incorrect clock source. This is how the clocks are protected.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Clock > Clock Subnet Configuration from the Function Tree. Step 2 Click the Clock Subnet tab. Click Query to query the existing parameter settings.

4-4

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

4 Configuring Clocks

Step 3 Select Start Standard SSM Protocol or Start Extended SSM Protocol.
NOTE

The same SSM protection protocol must be used within the same clock protection subnet.

Step 4 Set the subnet number of the clock subnet to which the NE is associated.
NOTE

Allocate the same subnet number to NEs tracing the same clock source.

Step 5 Optional: If the extended SSM protocol starts, set the clock ID of the clock source. Step 6 Click Apply. In the Operation Result dialog box, click Close. Step 7 Optional: If the clock ID is specified for the line clock of an NE, click the Clock ID Status tab, and set the Enabled Status to Enabled. Click Apply. In the Operation Result dialog box, click Close. ----End

4.4 Configuring Switching Conditions for Clock Sources

If the traceable clock source of an NE is line clock, you can customize switching conditions for the clock source, so that the NE switches to other clocks when the clock source fails. In this manner, services are less affected.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Clock > Clock Source Switching from the Function Tree. Click the Clock Source Switching Condition tab. Step 2 Click Query to query the existing parameter settings. Step 3 Double-click the parameter column and set the alarms and performance events that are to be used as the clock source switching conditions to Yes.

Step 4 Click Apply. In the Operation Result dialog box, click Close. ----End

4.5 Configuring the Clock Source Reversion

When there are multiple clock sources for an NE, set the clock sources to automatic reversion mode, so that the deteriorated clock source automatically becomes the traceable timing reference after it recovers.

Prerequisite
You must be an NM user with "NE operator" authority or higher.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 4-5

4 Configuring Clocks

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Clock > Clock Source Switching from the Function Tree. Click the Clock Source Reversion Parameter tab. Step 2 Double-click and set the reversion mode and the WTR time.

NOTE

Do not set Clock Source WTR Time(min) to 0 to avoid repeated switching when the clock is unstable.

Step 3 Click Apply. In the Operation Result dialog box, click Close. ----End

4.6 Configuring the Phase-Locked Source for External Clock Output

When a clock signal passes through 14 or more NEs, frequency offset and drift may occur. As a result, the clock signal transmitted to the downstream NE is degraded. To avoid clock signal degrade, you need to set a 2M phase-locked source to optimize the clock signal.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Clock > PhaseLocked Source Output by External Clock from the Function Tree. Step 2 Click Query to query the existing parameter settings. Step 3 Set the external clock attributes of the 2M phase-locked source. Set the parameters manually such as External Clock Output Mode, External Clock Output Timeslot and so on. Step 4 Click Apply. ----End

Example
As shown in Figure 4-1, n NEs comprise a long transmission chain and the external BITS1 equipment is used as the clock synchronization source. After the transmission over several NEs, the BITS1 clock signals are degraded to a certain degree. In this case, you can output the BITS1 signals from NEm that requires clock quality compensation to the local BITS2 equipment for compensating the signals. Then, after the compensation, the clock signals are transmitted from the BITS2 equipment to NEm, to function as the clock synchronization source of the downstream equipment. The 2M phase-locked source of NEm should be the input clock source of the west line board, and the clock synchronization source should be the BITS2 PRC input externally.
4-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

4 Configuring Clocks

Figure 4-1 Typical application

BITS1 BITS2

NE1

west

west

NEm

east

west

NEn

Clock Signal Flow

To make sure that the BITS2 equipment receives clock signals from NEm correctly, you need to set the output external clock of NEm. Perform the settings according to parameters of the BITS2 equipment and make sure that the settings on NEm are consistent with the settings on the BITS2 equipment.

4.7 Setting the Clock Source Quality

In a complex clock network, there may be some unknown clock sources. You can uniformly define these clock sources as unavailable clocks so that NEs do not trace wrong clock sources. The NE obtains their quality information automatically for clock sources that are allocated to an NE. You should define the quality level of clock sources only during test and maintenance.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Clock > Clock Subnet Configuration from the Function Tree. Click the Clock Quality tab. Step 2 Click Query to query the existing parameter settings. Step 3 Click the Clock Source Quality tab and set Configuration Quality to a desired level.

NOTE

Generally, use the default Automatic Extraction.

Step 4 Click Apply. In the Operation Result dialog box, click Close.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 4-7

4 Configuring Clocks

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 5 If the quality level of a clock source is zero, you can specify the level manually. Click the Manual Setting of 0 Quality Level tab and set Manual Setting of 0 Quality Level to a desired level. Step 6 Click Apply. In the Operation Result dialog box, click Close. ----End

4.8 Configuring the SSM Output

If the standard SSM or extended SSM protocol is enabled, the clock signals carry SSM messages automatically. You can prevent clock sources from sending SSM messages to other clock subnets. This helps you to ensure that the equipment of different clock subnets do not affect each other at the edge of clock networks.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Clock > Clock Subnet Configuration from the Function Tree. Click the SSM Output Control tab. Step 2 Set the Control Status of the clock source.

Step 3 Click Apply. In the Operation Result dialog box, click Close. ----End

4.9 Switching a Clock Source

When the traceable clock source in a network deteriorates, NEs may not be able to execute a switch on the clock source. You need to manually switch the clock source to prevent clock deterioration from affecting the normal running of NEs.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The clock source has been created.

4-8

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

4 Configuring Clocks

Context

CAUTION
Performing clock source switching may cause signal jitter and bit errors.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Clock > Clock Source Switching from the Function Tree. Click the Clock Source Switching tab. Step 2 Click Query to query the current switching status of a clock source. Step 3 Optional: If the Lock Status is Lock, right-click and choose Release Lockout. Step 4 Right-click the clock source that you want to switch and choose a switching operation.
NOTE

Before switching the clock source, make sure that the new clock source that is not locked and that is of a good quality is created in the priority table.

Step 5 Optional: To restore the automatic clock source selection mode, right-click the switched clock source and choose Clear Switching. ----End

4.10 Setting the Attributes of the External Time Interface

If the equipment uses the external time interface to input or output time signals, you should set the corresponding interface attributes. The external time interface attributes include the basic attribute, BMC, and cable transmitting distance. The cable transmitting distance is used to compensate the time for the equipment.

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

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > External Time Interface. Step 2 Click the Basic Attribute tab. Step 3 Set Interface Mode of the external time interface. Step 4 Optional: If Interface Mode is set to External Time Interface, you can set Direction, Interface Protocol Type, and Interface Eletricity.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

4-9

4 Configuring Clocks
NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

l l l l

OptiX PTN 3900 and 1900: Interface Protocol Type is set according to the type of the external time protocol. Interface Protocol Type can be set to DCLS, 1PPS+TIME or J.211. OptiX PTN 910 and 950: Interface Protocol Type is set according to the type of the external time protocol. Interface Protocol Type can be set to DCLS or 1PPS+TIME. OptiX PTN 3900 and 1900: Interface Level is set according to the setting of the external time interface. Interface Level can be set to TTL, RS232 or RS422. OptiX PTN 910 and 950: Interface Level is set according to the setting of the external time interface. Interface Level can be set to RS422.

Step 5 Click the BMC tab to set the BMC-related parameters.

NOTE

The BMC-related parameters can be set only the working mode is set to BC or OC, and when the Interface Mode of the External Time Interface is set to External Time Interface.

Step 6 Click Apply. Step 7 Click the Cable Transmitting Distance tab to set the cable parameters for the clock compensation such as Transmitting Distance Mode, Transmitting Length(m), and Transmitting Time(ns).
NOTE

Transmitting Distance Mode can be set to Time or Length.

l l l

When Transmitting Distance Mode is set to Time, the transmitting time ranges from 0 ns to 1350 ns. When Transmitting Distance Mode is set to Length, the length range is 0-300 m. 1 m is equivalent to 4.5 ns.

Step 8 Click Apply. ----End

4.11 Configuring a Clock Domain

The clocks output by a port include the system clock and ACR clock. For easy management, each clock is considered as a clock domain. By default, all the ports are in a system clock domain. When the ACR clock is used, the port should be bound with the ACR clock domain.

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

Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Clock > Clock Domain Management from the Function Tree. Step 2 Click New to display the Create Clock Domain Port dialog box. Step 3 Set Clock Domain, Clock Domain Slot, and Board. Step 4 Select a port from Available Port List in the dialog box, click ----End
4-10 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

, and then click OK.

OptiX iManager T2000 Operation Guide for PTN NE Management

4 Configuring Clocks

4.12 Configuring an ACR Clock

The equipment can select one CES service from multiple CES services and recover the clock from the selected CES service. After the recovered ACR clock is bound with the clock domain, the ACR clock can be used as a system clock.

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

Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Clock > ACR Clock from the Function Tree. Step 2 Double-click the blank below CES Service and click you can select a CES service. to display a dialog box where

Step 3 Select the CES service from which the ACR clock is to be recovered, and then click OK. Step 4 Click Apply. ----End

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

4-11

OptiX iManager T2000 Operation Guide for PTN NE Management

5 PTP Clock

5
About This Chapter

PTP Clock

The equipment complies with the IEEE 1588V2 protocol and can achieve frequency synchronization and time synchronization. 5.1 Introduction to the PTP Clock The precision time protocol (PTP) clock complies with the IEEE 1588V2 protocol and achieves nanosecond-level precision, which meets the requirements of 3G and Long Term Evolution (LTE). 5.2 Basic Information Before configuring the IEEE 1588V2 clock, you should be familiar with the BMC algorithm, clock architecture, master-slave synchronization, and IEEE 1588V2 protocol packets and their functions. 5.3 Application of the PTP Clock By using the IEEE 1588V2 protocol, the OptiX PTN equipment can transfer the precise time information to achieve clock synchronization and time synchronization for equipment in the network. This meets the requirement of the telecommunications network for precise time. The equipment with the PTP clock can achieve networkwide frequency synchronization and time synchronization in the packet switching network (PSN). The telecommunications network carry various services. Certain services require precise time synchronization, such as the network voting and charging services. In such a scenario, the IEEE 1588V2 clock is applicable and ensures precise time synchronization. 5.4 Configuration Flow for the PTP Clock This section describes the flow of configuring the PTP clock in different modes. 5.5 Configuring the PTP Clock To achieve time synchronization and clock synchronization between NEs, configure the PTP clock. 5.6 PTP Clock Configuration Case This section describes the configuration case of the PTP clock.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

5-1

5 PTP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

5.1 Introduction to the PTP Clock

The precision time protocol (PTP) clock complies with the IEEE 1588V2 protocol and achieves nanosecond-level precision, which meets the requirements of 3G and Long Term Evolution (LTE).

Objective and Benefit

As the rate at which the Ethernet data is transmitted is increased to the gigabit-per-second level, the synchronization of the Ethernet fails to meet the requirements. To solve the synchronization problem, the network time protocol (NTP) is presented, which helps achieve the precision of clock synchronization at 200 us. The precision, however, fails to meet the precision requirements of the test instruments and industrial control. To improve the synchronization precision, in 2002, the IEEE committee presented the IEEE 1588 clock protocol. Then, the protocol evolved to the current IEEE 1588V2 protocol, which helps achieve nanosecond-level precision. There are two synchronization modes, that is, clock (frequency) synchronization and time (phase) synchronization. Time (phase) synchronization is applicable to the networks where the absolute networkwide time should be of certain precision, such as the power system network and 3G network. Though the GPS at every node can also solve the precision problem, the high cost limits the application scope of this solution. The traditional clock protocols can achieve only frequency synchronization. The IEEE 1588V2 protocol is the clock protocol that can achieve both frequency synchronization and phase synchronization. The IEEE 1588V2 protocol is applicable for time synchronization at every node in the distributed network that requires precise synchronization. The hardware and software synchronize the system clock of the network equipment (client) with the primary clock in the network at a nanosecond precision level. In the Ethernet where the IEEE 1588V2 protocol is not enabled, there is a 1000 us delay. In the Ethernet where the IEEE 1588V2 protocol is enabled, the timing synchronization is improved to a great extent. The approach of adopting the IEEE 1588V2 protocol to achieve clock synchronization and time synchronization marks a technical innovation for the transformation of the carrier-class IP network. The IEEE 1588V2 protocol helps achieve clock synchronization and time synchronization that meet the requirements of Node B and RNC in a 3G network.
NOTE

l l

Clock synchronization refers to frequency synchronization. Time synchronization refers to phase synchronization, which requires that both the time and frequency should be synchronous.

Standards and Protocols Compliance

The IEEE 1588V2 clock complies with 1588 IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems, IEEE, 2002.

5-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

5 PTP Clock

5.2 Basic Information

Before configuring the IEEE 1588V2 clock, you should be familiar with the BMC algorithm, clock architecture, master-slave synchronization, and IEEE 1588V2 protocol packets and their functions.

BMC Algorithm
In a PTP clock network, the equipment computes the best clock source according to the BMC algorithm. The BMC algorithm compares the descriptive data of two clocks and detects the better one, which is selected as the clock source. The BMC algorithm includes the following algorithms:
l

Data set comparison algorithm: The NE selects the clock of better quality as the clock source. If an NE receives two or more channels of clock signals from the same grandmaster clock (GMC), the NE selects one channel of the clock signals that traverses the least nodes as the clock source. State decision algorithm: The result of data set comparison determines the next state of the port.

Clock Architecture
Figure 5-1 shows the architecture of the IEEE 1588V2 clock.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

5-3

5 PTP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 5-1 Architecture of the IEEE 1588V2 clock

BITS

OC

GMC Master

TC

BC

Slave Master Master

BC Slave Master

TC+OC

OC

Slave

OC

Slave

NOTE

l l

Master: A master port provides a time source for the downstream equipment. Slave: A slave port receives the clock signals from the upstream port.

The OptiX PTN equipment supports four architectures of the IEEE 1588V2 clock.
l

Ordinary clock (OC): The OC equipment provides only one port to extract the IEEE 1588 packets. The OC equipment can work as a slave clock equipment and maintains synchronization with the upstream clock. The equipment extracts the clock packets from the port that supports the IEEE 1588 packets and recovers the clock. The equipment can also work as a master clock equipment, which inputs the external time from the external time interface, and outputs the clock signals to the downstream through the port that supports the IEEE 1588 packets. Boundary clock (BC): When used as a BC, the equipment provides multiple ports to extract the IEEE 1588 packets. The BC can work as either master clock equipment or slave clock equipment. The BC equipment can distribute the clock packets to the downstream through multiple ports, but the OC equipment can distribute the clock packets to the downstream through only one port.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

5-4

OptiX iManager T2000 Operation Guide for PTN NE Management

l

5 PTP Clock

Transparent clock (TC): The TC equipment transparently transmits the IEEE 1588 packets and records the period when the packets stay on the equipment. During the period, the TC equipment transports the packets to the slave clock equipment for processing. The TC equipment only transparently transmits the clock, and does not recover the clock.

End-to-end TC: The TC equipment adopts the end-to-end delay measurement mechanism between the master and slave clocks. Peer-to-peer TC: The TC adopts the point-to-point delay measurement mechanism.

TC+OC: The TC+OC equipment corrects and transparently transmits the time stamps for the IEEE 1588V2 packets, and achieves clock synchronization. By adopting the BMC algorithm, the TC+OC equipment selects the clock source, which is then sent to the system clock module. If necessary, the clock source can be used as the system clock of the equipment.
NOTE

The end-to-end TC and peer-to-peer TC adopt different mechanisms to realize delay transmission, and cannot operate in the same communication channel alternatively. That is, the adjacent TC equipment along one time channel adopts either the end-to-end TC or peer-to-peer TC, but not both at the same time.

Master-Slave Synchronization
In the case of master-slave synchronization, each slave clock maintains synchronization with the master clock by exchanging the synchronization packets with the master clock. Figure 5-2 shows the master-slave synchronization process of the equipment. Figure 5-2 Master-slave synchronization process

Master clock

Time stamp at slave clock Slave clock

t1

Sync packets t2 t1t2

Delay_Req packets t3 t4 t1t2t3

Delay_Resp packets

t1t2t3t4

At time point t1, the master clock sends the Sync packets that contain time stamp t1 to the slave clock.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 5-5

Issue 01 (2009-06-30)

5 PTP Clock
l l l

OptiX iManager T2000 Operation Guide for PTN NE Management

At time point t2, the slave clock receives the Sync packets and obtains time stamp t1. At time point t3, the slave clock sends the Delay_Req packets to the master clock. At time point t4, the master clock receives the Delay_Req packets. Then, the master clock sends the Delay_Resp packets that contain time stamp t4 to the slave clock.
NOTE

A time stamp (TS) is used to transmit the time information. The Sync packets, Delay_Req packets, and Delay_Resp packets are used to generate or communicate the time information. The OC equipment and BC equipment maintain synchronization by processing related time information.

The slave clock computes the delay and offset from the master clock according to time stamps t1, t2, t3, and t4. Then, the slave clock corrects the time according to the delay and offset.
l l

Delay = [(t4-t1)-(t3-t2)]/2 Offset = [(t2-t1)+(t3-t4)]/2

Protocol Packets and Their Functions

The IEEE 1588 protocol defines the Event messages and General messages. The Event messages are timing messages. To transmit and receive the Event messages, the equipment should generate the precise time stamp. To transmit and receive the General messages, the equipment does not need to generate the precise time stamp. The Event messages include the following packets:
l l l l

Sync Delay_Req Pdelay_Req Pdelay_Resp

The General messages include the following packets:

l l l l

Announce Delay_Resp Management Signaling

The Sync, Delay_Req, and Delay_Resp packets are used to generate or transport the timing information. The OC and BC maintains synchronization by using the timing information and adopting the delay request-response mechanism. The Pdelay_Req and Pdelay_Resp packets are used to measure the link delay between two clock ports that support the Pdelay mechanism. The link delay is used to correct the timing information contained in the Sync packets in the P2P TC system. The OC and BC maintain synchronization according to the link delay and the timing information contained in the Sync messages.
NOTE

The Pdelay mechanism is intended to measure the point-to-point transmission time between two communication ports that support the Pdelay mechanism. The point-to-point transmission time is the link delay. The P2P TC has to compute the link delay by adopting the Pdelay mechanism.

The Announce messages are used to set up the synchronization system.

5-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

5 PTP Clock

5.3 Application of the PTP Clock

By using the IEEE 1588V2 protocol, the OptiX PTN equipment can transfer the precise time information to achieve clock synchronization and time synchronization for equipment in the network. This meets the requirement of the telecommunications network for precise time. The equipment with the PTP clock can achieve networkwide frequency synchronization and time synchronization in the packet switching network (PSN). The telecommunications network carry various services. Certain services require precise time synchronization, such as the network voting and charging services. In such a scenario, the IEEE 1588V2 clock is applicable and ensures precise time synchronization. Figure 5-3 shows the scenario where the PTP clock is applicable. Figure 5-3 Networking diagram for typical application of the PTP clock
Node B

NE E GPS NE B NE A OC 950

TC NE C

RNC

BC

NE D

TC

NE F OC

910

Node B

TC+OC

External time signals PTP clock signals

As shown in Figure 5-3, BITS sends clock signals to NE A and RNC. NE A works as BC equipment and sends the PTP packets to two ports. The downstream equipment works as the TC or TC+OC equipment and transparently transmits the PTP packets. NE E and NE F, which are connected to Node B, work as the OC equipment, recover the PTP clock, and send the clock to Node B through the external time interface.

5.4 Configuration Flow for the PTP Clock

This section describes the flow of configuring the PTP clock in different modes. Figure 5-4 shows the flow for configuring the PTP clock.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 5-7

5 PTP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 5-4 Configuration flow for the PTP clock

Required Optional

Start Setting the Frequency Selection Mode Setting the PTP System Time Setting the PTP Clock Subnet

Setting the Attributes of the External Time Interface Setting the PTP NE Attributes

Creating the PTP Clock Port Creating the PTP Clock Service

Setting the PTP Packet Period

Setting the PTP Clock Port Status Setting the Cable Transmitting Wrap Setting the WTR Time for the PTP Clock Sourc Setting the PTP Clock Source Priority End
5-8 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

5 PTP Clock

The PTP priority service needs to be configured only when the PTP clock works in the TC or TC+OC mode. The PTP clock source priority needs to be configured only when the PTP clock works in the TC +OC mode.

5.5 Configuring the PTP Clock

To achieve time synchronization and clock synchronization between NEs, configure the PTP clock. 5.5.1 Setting the Frequency Selection Mode The OptiX PTN equipment supports two synchronization modes, that is, physical synchronization mode and PTP synchronization mode. The frequency source selection mode is used to set the clock synchronization mode of the NE. Before configuring the IEEE 1588 clock, you should set the frequency source selection mode to the PTP synchronization mode. 5.5.2 Setting the PTP System Time If the OptiX PTN equipment is used as the grandmaster clock in the PTP clock network, you should set the PTP system time on the OptiX PTN equipment. Hence, the downstream OptiX PTN equipment can trace the clock. 5.5.3 Setting the PTP Clock Subnet According to the actual networking, the networking planner plans the clock network and divides the entire network into clock domains. In each clock domain, the clock and time of the equipment are synchronized. Each BC, OC or TC+OC equipment can be configured with only one clock domain. The equipment selects the source in only one clock domain, and discards the clock packets from other clock domains. 5.5.4 Setting the Attributes of the External Time Interface If the equipment uses the external time interface to input or output time signals, you should set the corresponding interface attributes. The external time interface attributes include the basic attribute, BMC, and cable transmitting distance. The cable transmitting distance is used to compensate the time for the equipment. 5.5.5 Setting the PTP NE Attributes The NE attributes include Work Mode, Transmitting Message Multi-cast Mode, and Time Adjusting. 5.5.6 Creating the PTP Clock Port When a PTP clock port is created, the PTP clock port can access the PTP packets. You can set the clock reference source number on the PTP clock port created in the BC or OC mode. 5.5.7 Creating the PTP Clock Service When the NE works in the TC or TC+OC mode, you need to create a PTP clock service on the NE so that the NE transparently transmits the PTP clock packets. 5.5.8 Setting the PTP Packet Period When setting the PTP packet period, you can set the periods of the ANNOUNCE, SYNC, DELAY, and PDELAY packets. 5.5.9 Setting the PTP Clock Port Status In the scenario where the OptiX PTN equipment is connected to the client equipment, properly set the status of the PTP clock port. For example, if the PTP packets should contain VLAN ID
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 5-9

5 PTP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

or the PTP packets from the client side should be forwarded (Layer 2 or Layer 3), set the status of the PTP clock port accordingly. By default, the equipment performs Layer 2 forwarding for the PTP packets. 5.5.10 Setting the Cable Transmitting Wrap The cable transmitting distance wrap indicates the transmitting time difference of the cables between two sets of equipment in the transmit and receive directions. During deployment, you can use the GPS to compute the transmitting time difference between the two directions. Set the cable transmitting wrap, and thus the equipment performs the clock compensation. The wrap modes includes the length wrap and time wrap. The equipment can choose only one mode. 5.5.11 Setting the Wait-to-Restore Time for the PTP Clock Source When a clock port recovers from a failure, the system acknowledges the validity of the port a certain period later. This period is referred to as the wait-to-restore (WTR) time. During the WTR time, the system considers the clock signals as unavailable and the clock signals are not involved in the clock source selection. 5.5.12 Setting the PTP Clock Source Priority If the NE works in the TC+OC mode, you need to set the priorities for the clock sources traced by the OC. Normally, the OC traces the PTP clock source of the highest priority. If the PTP clock source of the highest priority fails, the OC traces the PTP clock source of the second highest priority. The priority table is configured with a source ID. When a local port receives a clock source in the priority table, the port checks whether the domain that the clock source belongs to is consistent with the domain configured at the local end.

5.5.1 Setting the Frequency Selection Mode

The OptiX PTN equipment supports two synchronization modes, that is, physical synchronization mode and PTP synchronization mode. The frequency source selection mode is used to set the clock synchronization mode of the NE. Before configuring the IEEE 1588 clock, you should set the frequency source selection mode to the PTP synchronization mode.

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

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > Frequency Selection Mode from the Function Tree. Step 2 In Select Frequency Source Mode, you can select one of the clock synchronization mode.

CAUTION
l

When the external time interface is set to the external time input interface, the NE can run in only the physical synchronization mode. That is, the frequency selection mode of the equipment that accesses the external clock must be set to the physical synchronization mode. When the NE is running in the PTP synchronization mode, the external interface cannot be set to the external time input interface.

5-10

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

5 PTP Clock

Step 3 Click Apply. ----End

5.5.2 Setting the PTP System Time

If the OptiX PTN equipment is used as the grandmaster clock in the PTP clock network, you should set the PTP system time on the OptiX PTN equipment. Hence, the downstream OptiX PTN equipment can trace the clock.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The PTP system time can be set only when the current time of the NE traces the local clock.

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute . Step 2 In PTP System Time, click to set the system time.

NOTE

Move the cursor to the time bar. To increase the value, click or right-click the time bar. To decrease the value, hold the Shift key, and click or right-click the time bar.

Step 3 Click Apply. ----End

5.5.3 Setting the PTP Clock Subnet

According to the actual networking, the networking planner plans the clock network and divides the entire network into clock domains. In each clock domain, the clock and time of the equipment are synchronized. Each BC, OC or TC+OC equipment can be configured with only one clock domain. The equipment selects the source in only one clock domain, and discards the clock packets from other clock domains.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 5-11

5 PTP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

Prerequisite
You must be an NM user with "NE operator" authority or higher. The working mode of the equipment clock should not be TC.

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Subnet Configuration from the Function Tree. Step 2 Select the Clock Subnet tab to set the clock subnet number. Step 3 Click Apply. Step 4 Click the BMC tab to set the parameters related to the BMC in the clock subnet. Step 5 Click Apply. ----End

5.5.4 Setting the Attributes of the External Time Interface

If the equipment uses the external time interface to input or output time signals, you should set the corresponding interface attributes. The external time interface attributes include the basic attribute, BMC, and cable transmitting distance. The cable transmitting distance is used to compensate the time for the equipment.

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

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > External Time Interface. Step 2 Click the Basic Attribute tab. Step 3 Set Interface Mode of the external time interface. Step 4 Optional: If Interface Mode is set to External Time Interface, you can set Direction, Interface Protocol Type, and Interface Eletricity.
NOTE

l l l l

OptiX PTN 3900 and 1900: Interface Protocol Type is set according to the type of the external time protocol. Interface Protocol Type can be set to DCLS, 1PPS+TIME or J.211. OptiX PTN 910 and 950: Interface Protocol Type is set according to the type of the external time protocol. Interface Protocol Type can be set to DCLS or 1PPS+TIME. OptiX PTN 3900 and 1900: Interface Level is set according to the setting of the external time interface. Interface Level can be set to TTL, RS232 or RS422. OptiX PTN 910 and 950: Interface Level is set according to the setting of the external time interface. Interface Level can be set to RS422.

Step 5 Click the BMC tab to set the BMC-related parameters.

5-12 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

5 PTP Clock

The BMC-related parameters can be set only the working mode is set to BC or OC, and when the Interface Mode of the External Time Interface is set to External Time Interface.

Step 6 Click Apply. Step 7 Click the Cable Transmitting Distance tab to set the cable parameters for the clock compensation such as Transmitting Distance Mode, Transmitting Length(m), and Transmitting Time(ns).
NOTE

Transmitting Distance Mode can be set to Time or Length.

l l l

When Transmitting Distance Mode is set to Time, the transmitting time ranges from 0 ns to 1350 ns. When Transmitting Distance Mode is set to Length, the length range is 0-300 m. 1 m is equivalent to 4.5 ns.

Step 8 Click Apply. ----End

5.5.5 Setting the PTP NE Attributes

The NE attributes include Work Mode, Transmitting Message Multi-cast Mode, and Time Adjusting.

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

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree. Step 2 Set Work Mode, SLAVE_ONLY, Time Adjusting, and Transmitting Packet Multi-cast Mode. Step 3 According to the working mode of the NE in the network, set Work Mode.
NOTE

The PTP standard defines four working modes, that is, BC, OC, TC, and TC+OC. When the NE working mode is TC or TC+OC, if the PTP clock service or the clock source priority table is already configured, you cannot modify the working mode.

Step 4 When Work Mode is set to OC, SLAVE_ONLY can be set to SLAVE_ONLY or NON_SLAVE_ONLY.
NOTE

l l

SLAVE_ONLY indicates that the NE in the OC mode can only trace other PTP clocks. NON_SLAVE_ONLY indicates that in the OC mode the NE can function as the standy clock to trace other PTP clocks and the NE can also function as the primary clock. Whether the NE functions as the standby clock or primary clock depends on the quality of the PTP clock.

Step 5 When Work Mode is set to BC or OC, Time Adjusting is configurable.

Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 5-13

5 PTP Clock
NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

If the NE requires time synchronized, Time Adjusting needs to be set to Enabled.

Step 6 When Work Mode is set to BC or OC, Transmitting Packet Multi-cast Mode is configurable.
NOTE

If the mode is set to Entire Multi-cast, the equipment multicasts all the PTP packets. If the mode is set to Part Multi-cast, the equipment unicasts the DELAY packets.

Step 7 When Work Mode is set to BC or OC, Protocol Packet Format is configurable.
NOTE

The Protocol Packet Format can be set to NMEA or UBX. The default parameter value is NMEA. This parameter is valid only when Interface Protocol Type of the external time interface is set to 1PPS +Time. When Interface Protocol Type of the external time interface is set to DCLS, the parameter can still be set but the parameter value is invalid.

----End

5.5.6 Creating the PTP Clock Port

When a PTP clock port is created, the PTP clock port can access the PTP packets. You can set the clock reference source number on the PTP clock port created in the BC or OC mode.

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

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree. Step 2 Click the Port Status tab, and then click New to display the Create PTP Clock Port dialog box. Step 3 Select the corresponding board, and then select the corresponding port from Available Port. Click Step 4 Click OK. ----End .

5.5.7 Creating the PTP Clock Service

When the NE works in the TC or TC+OC mode, you need to create a PTP clock service on the NE so that the NE transparently transmits the PTP clock packets.

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

5-14

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

5 PTP Clock

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Service from the Function Tree. Step 2 Click New to display the New Clock Service dialog box. Step 3 Set Service ID and Service Name. Step 4 In the dialog box, click the UNI tab. Then, click Configuration to display the Configure Port dialog box. Step 5 Select the port from the Available Port list, and then click Selected Port list.
NOTE

to add the port to the

l l l

When the PTP packets contain VLAN tags, you need to set a VLAN tag for the port. The OptiX PTN equipment supports the setting of only one VLAN tag. When two TC services share a port, set a VALN tag for the port if the port is a UNI port. If the port is Layer 3 port, the port can be used only as a UNI port for the TC service. The encapsulation mode should be ETH and no VLAN tag can be set.

Step 6 Click OK, and thus the UNI configuration is complete. Step 7 Optional: If the PTP packets need to be carried by the MPLS tunnel, you can set the related NNI parameters. 1. 2. In the dialog box, click the NNI tab. Then, click New to display the New PW dialog box. Click the General Attributes tab to set PW ID, PW Type, PW Ingress Label, and PW Egress Label.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

5-15

5 PTP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

3.

Click to display Resource Selection Window. Select the tunnel that carries the PW, and then click OK.
NOTE

Select the static MPLS tunnel, because the dynamic MPLS tunnel cannot carry the PTP packets.

4.

Optional: Click the Advanced Attributes tab to set the corresponding parameters.

5.

Click OK in the New PW dialog box to finish the PW configuration on the NNI side.

Step 8 Click OK in the New Clock Service dialog box to complete the configuration of the clock service. Step 9 Optional: Click the Static MAC Address tab, and then click New to display the New Static MAC Address dialog box.

5-16

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

5 PTP Clock

If the MAC address of the received packets is consistent with the configuration in the static MAC address, the packets are forwarded through corresponding port. If Transmitting Message Multi-cast Mode of the BC and OC in the clock subnet is set to Entire Multi-cast, you do not need to set the static MAC address for the NE that functions as a TC.

Step 10 Set MAC Address and Egress Interface, and click OK. A dialog box is displayed, indicating that the operation is successful. Click Close. ----End

5.5.8 Setting the PTP Packet Period

When setting the PTP packet period, you can set the periods of the ANNOUNCE, SYNC, DELAY, and PDELAY packets.

Prerequisite
You must be an NM user with "NE operator" authority or higher. A PTP clock port must be created.

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree. Step 2 Click the Port Message tab to set P/E Mode and the corresponding packet periods.
NOTE

In P2P mode, the TC equipment transmits only the PDELAY packets. You can set the period for the TC equipment to transmit the PDELAY packets.

Step 3 Click Apply. ----End

5.5.9 Setting the PTP Clock Port Status

In the scenario where the OptiX PTN equipment is connected to the client equipment, properly set the status of the PTP clock port. For example, if the PTP packets should contain VLAN ID or the PTP packets from the client side should be forwarded (Layer 2 or Layer 3), set the status of the PTP clock port accordingly. By default, the equipment performs Layer 2 forwarding for the PTP packets.

Prerequisite
You must be an NM user with "NE operator" authority or higher. A PTP clock port must be created. The working mode of the NE must be set to BC or OC.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

5-17

5 PTP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree. Step 2 Click the Port Status tab and set PTP Message Format.

NOTE

If the port is configured with a clock service, do not change the PTP message format of the port.

Step 3 Optional: If the working mode of the NE is set to BC or OC, and the PTP packets contain VLAN IDs, set PTP Message VLAN to a proper VLAN value accordingly.
NOTE

In the case of interconnection with the client equipment, if the client equipment forwards the PTP packets according to VLAN IDs, the PTP packets should contain VLAN IDs.

Step 4 Optional: If the working mode of the NE is set to BC or OC, set Port Status accordingly.
NOTE

Set Port Status to MASTER+SLAVE, MASTER, or SLAVE.

l l

When the Port Status is MASTER, Actual Port Status should not be SLAVE. When the Port Status is SLAVE, Actual Port Status should not be MASTER.

If the NE is set to SLAVE_ONLY in the synchronization attributes, set Port Status only to SLAVE.

Step 5 Optional: If the working mode of the NE is set to BC or OC, double-click the blank line below Selected Clock Source to display the Clock Source Coding Configuration dialog box. Step 6 Optional: Set the parameters related to the clock source and click OK.

5-18

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

5 PTP Clock

CAUTION
The clock sources at the local port should be numbered in the same manner as the clock sources at the upstream port, or the clock sources do not need to be numbered. Otherwise, clock tracing fails if the working mode of the NE is set to BC or OC.
NOTE

When one PTP clock port receives multiple channels of clock signals, number the clock sources so that the NE selects one clock source. For example, multiple TC clock services from the upstream equipment are converged onto one clock port on the local equipment and then are transmitted to the downstream equipment. As a result, the port on the downstream equipment connected to the upstream equipment receives the multiple TC clock services. In this case, you need to number the clock sources at the port on the downstream equipment.

Step 7 Click Apply. ----End

5.5.10 Setting the Cable Transmitting Wrap

The cable transmitting distance wrap indicates the transmitting time difference of the cables between two sets of equipment in the transmit and receive directions. During deployment, you can use the GPS to compute the transmitting time difference between the two directions. Set the cable transmitting wrap, and thus the equipment performs the clock compensation. The wrap modes includes the length wrap and time wrap. The equipment can choose only one mode.

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

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute . Step 2 Click the Cable Transmitting Wrap tab. Step 3 Set Wrap Direction. Positive direction indicates that the transmitting distance or transmitting time of the clock receive end is longer than the transmitting distance or transmitting time at the clock transmit end. Negative direction indicates that the transmitting distance or transmitting time of the clock transmit end is longer than the transmitting distance or transmitting time at the clock receive end. Step 4 Wrap Mode can be set to Length or Time. Step 5 According to Wrap Mode, set Wrap Length(m) or Wrap Time(ns).
NOTE

l l l

The range of Wrap Length(m) is 0-14562 m. The range of Wrap Time(ns) is 0-65529 ns. 1 m is equivalent to 4.5 ns.

Step 6 Click Apply. ----End

Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 5-19

5 PTP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

5.5.11 Setting the Wait-to-Restore Time for the PTP Clock Source
When a clock port recovers from a failure, the system acknowledges the validity of the port a certain period later. This period is referred to as the wait-to-restore (WTR) time. During the WTR time, the system considers the clock signals as unavailable and the clock signals are not involved in the clock source selection.

Prerequisite
You must be an NM user with "NE operator" authority or higher. A PTP clock port must be created. The working mode of the NE must be set to BC, OC or TC+OC.

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Source Priority Table from the NE Explorer. Step 2 Click the Clock Source Reversion Parameter tab and set Clock Source WTR Time(min.).
NOTE

Set Clock Source WTR Time(min.) within the range of 0 minutes to 12 minutes at a spacing of 1 minute. By default, the WTR time is 5 minutes.

Step 3 Click Apply. ----End

5.5.12 Setting the PTP Clock Source Priority

If the NE works in the TC+OC mode, you need to set the priorities for the clock sources traced by the OC. Normally, the OC traces the PTP clock source of the highest priority. If the PTP clock source of the highest priority fails, the OC traces the PTP clock source of the second highest priority. The priority table is configured with a source ID. When a local port receives a clock source in the priority table, the port checks whether the domain that the clock source belongs to is consistent with the domain configured at the local end.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The working mode of the NE must be set to TC+OC.

Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Source Priority Table from the NE Explorer. Step 2 Click the Clock Source Priority Table tab and click New to create a clock source. You can change the working mode of NE only after you delete the PTP clock source priority. Step 3 Select a clock source and click
5-20

or

to adjust the priority of the clock source.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX iManager T2000 Operation Guide for PTN NE Management

5 PTP Clock

Step 4 Click Apply. ----End

5.6 PTP Clock Configuration Case

This section describes the configuration case of the PTP clock. 5.6.1 Configuration Networking Diagram The equipment with the PTP function can achieve synchronization of the entire PSN, or the PSNs that are connected through an asynchronous PSN. 5.6.2 Service Planning In the PSN, the PTP-supported equipment can work in different modes. Plan and configure the PTP clock according to the requirements. 5.6.3 Configuration Process (BC) This section describes the process of configuring the BC of the PTP clock. 5.6.4 Configuration Process (TC) This section describes the process of configuring the TC of the PTP clock. 5.6.5 Configuration Process (OC) This section describes the process of configuring the OC of the PTP clock.

5.6.1 Configuration Networking Diagram

The equipment with the PTP function can achieve synchronization of the entire PSN, or the PSNs that are connected through an asynchronous PSN. As shown in Figure 5-5, RNC and Node B require time synchronization and frequency synchronization. The equipment in the network is the OptiX PTN equipment. The backbone network built with the OptiX PTN 3900 equipment is directly connected to RNC. On the UNI side, the network is connected to Node B through the OptiX PTN 910 and OptiX PTN 950.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

5-21

5 PTP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 5-5 Scenario where the PTP clock is transmitted through the PSN
Node B 1-EF8F-1 19-EFF8-1 GPS 20-EFG2-1 NE A 20-EFG2-2 NE B 20-EFG2-1 20-EFG2-2 NE C 3-EF8F-1 PTN 910 NE F OC Node B NE E PTN 950 OC

TC

RNC

BC NE D 20-EFG2-2 TC+OC 19-EFF8-1 20-EFG2-1 20-EFG2-2 PTN 3900 External time signals PTP clock signals TC 20-EFG2-1

On the RNC side, GPS transmits the clock of high precision to RNC and to the OptiX PTN 3900 connected to RNC through the external time interfaces. Then, the clock is transmitted to the OptiX PTN 910 and OptiX PTN 950 on the UNI side through the PTN. Finally, the clock is transmitted to Node B through the external time interfaces on the OptiX PTN 910 and OptiX PTN 950.

5.6.2 Service Planning

In the PSN, the PTP-supported equipment can work in different modes. Plan and configure the PTP clock according to the requirements. According to the networking diagram and requirements, the OptiX PTN 3900 that is connected to RNC works as a BC, which distributes the clock signals. Other OptiX PTN 3900 NEs work as TCs, which transparently transmit the clock signals. The OptiX PTN 910 and OptiX PTN 950 work as OCs, which receive the clock signals and transmit the clock signals to Node B through the external time interfaces. Table 5-1 lists the details on the planning of the OptiX PTN 3900 that works as a BC.

5-22

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

5 PTP Clock

Table 5-1 Planning of the OptiX PTN 3900 working as a BC Attribute Setting the frequency source selection mode Setting a clock subnet Setting the external time interface attributes Frequency Selection Mode Clock Subnet Interface Mode Direction Interface Protocol Type Interface Electricity Cable Transmitting Distance Setting the PTP NE attributes Work Mode Time Adjusting Transmitting Message Multicast Mode Creating a PTP time interface Setting the PTP packet period Interface P/E Mode SYNC Message Period(s) Description Physical Synchronization

0 External Time Interface Ingress DCLS TTL Transmitting Distance Mode: Length Transmitting Length(m): 5 BC Enabled Entire Multi-cast

20-EFG2-1 and 20-EFG2-2 E2E 8/1024

DELAY Message 128/1024 Period(s) ANNOUNCE Message Period (s) ANNOUNCE Timeout Coefficient Setting the PTP clock port status VLAN PTP Message Format Port Status 128/1024

100 PTP ETH MASTER

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

5-23

5 PTP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

Attribute Setting the cable transmitting wrap 20-EFG2-1

Description Wrap Direction: Positive Wrap Mode: Time Wrap Time(ns): 10 20-EFG2-2 Wrap Direction: Negative Wrap Mode: Time Wrap Time(ns): 20

Table 5-2 lists the details on the planning of the OptiX PTN 3900 that works as a TC. Table 5-2 Planning of the OptiX PTN 3900 working as a TC Attribute Setting the PTP NE attributes Setting the PTP packet period Setting the cable transmitting wrap Work Mode P/E Mode NE B: 19-EFF8-1 Description TC E2E Wrap Direction: Positive Wrap Mode: Time Wrap Time(ns): 2 NE C: 19-EFF8-1 Wrap Direction: Negative Wrap Mode: Time Wrap Time(ns): 2 NE D: 20EFG2-2 Wrap Direction: Positive Wrap Mode: Time Wrap Time(ns): 2 Creating a PTP clock service Service ID Service Name UNI 1 1 NE B: 20-EFG2-2 and 19-EFF8-1 NE C: 20-EFG2-1 and 19-EFF8-1 NE D: 20-EFG2-1 and 20-EFG2-2 VLAN=100

Table 5-3 lists the details on the planning of the OptiX PTN 910 that works as an OC.

5-24

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

5 PTP Clock

Table 5-3 Planning of the OptiX PTN 910 working as an OC Attribute Setting the frequency source selection mode Setting a clock subnet Setting the external time interface attributes Frequency Selection Mode Clock Subnet Interface Mode Direction Interface Protocol Type Interface Electricity Cable Transmitting Distance Setting the PTP NE attributes Work Mode SLAVE_ONLY Time Adjusting Transmitting Message Multicast Mode Creating a PTP time interface Setting the PTP packet period Interface P/E Mode SYNC Message Period(s) DELAY Message Period(s) ANNOUNCE Message Period (s) ANNOUNCE Timeout Coefficient Setting the PTP clock port status VLAN PTP Message Format Description PTP Synchronization

0 External Time Interface Egress DCLS RS422 Transmitting Distance Mode: Length Transmitting Length(m): 5 OC SLAVE_ONLY Enabled Entire Multi-cast

3-EF8F-1 E2E 8/1024 128/1024 128/1024

100 PTP ETH

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

5-25

5 PTP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

Attribute Port Status Setting the cable transmitting wrap 3-EF8F-1

Description SLAVE Wrap Direction: Positive Wrap Mode: Time Wrap Time(ns): 10

Table 5-4 lists the details on the planning of the OptiX PTN 950 that works as an OC. Table 5-4 Planning of the OptiX PTN 950 working as an OC Attribute Setting the frequency source selection mode Setting a clock subnet Setting the external time interface attributes Frequency Selection Mode Clock Subnet Interface Mode Direction Interface Protocol Type Interface Electricity Cable Transmitting Distance Time Quality Level Time Precision Clock Source Type Clock Source Priority 1 Clock Source Priority 2 Setting the PTN NE attributes Work Mode SLAVE_ONLY Time Adjusting Description PTP Synchronization

0 External Time Interface Egress DCLS RS422 Transmitting Distance Mode: Length Transmitting Length(m): 5 187 254 GPS 10 128 OC SLAVE_ONLY Enabled

5-26

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

5 PTP Clock

Attribute Transmitting Message Multicast Mode Creating a PTP time interface Setting the PTP packet period Interface P/E Mode SYNC Message Period(s) DELAY Message Period(s) ANNOUNCE Message Period (s) ANNOUNCE Timeout Coefficient Setting the PTP clock port status VLAN PTP Message Format Port Status Setting the cable transmitting wrap 1-EF8F-1

Description Entire Multi-cast

1-EF8F-1 E2E 8/1024 128/1024 128/1024

100 PTP ETH SLAVE Wrap Direction: Positive Wrap Mode: Time Wrap Time(ns): 10

5.6.3 Configuration Process (BC)

This section describes the process of configuring the BC of the PTP clock.

Procedure
Step 1 Set the frequency source selection mode. Select NE A in the NE Explorer and choose Configuration > Clock > Frequency Selection Mode from the Function Tree. Then, set the related parameters. Set the following parameter: Frequency Selection Mode: Physical Synchronization(NE A receives the clock signals from BITS through the external time interface. If the external time interface works as the clock input interface, Frequency Selection Mode cannot be set to PTP Synchronization for the equipment.) Step 2 Optional: Set the clock subnet.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 5-27

5 PTP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

Choose Configuration > Clock > PTP Clock > Clock Subnet Configuration from the Function Tree and set the related parameters. Click Apply. Set the following parameter: Clock Subnet: 0(The default clock subnet number is 0. By default, all the NEs are in the same clock subnet. Set Clock Subnet only when the clock network should be divided into clock subnets.) Step 3 Set the attributes of external time interface. 1. 2. Choose Configuration > Clock > PTP Clock > External Time Interface from the NE Explorer. Click the Basic Attribute tab and set the related parameters. Then, click Apply.
l l l

Interface Mode: External Time Interface Direction: Ingress Interface Protocol Type: DCLS(Set this parameter to DCLS or 1PPS+TIME according to the protocol type. In the case of OptiX PTN 1900/3900, the Interface Protocol Type can be set to DCLS, 1PPS+TIME or J.211. In the case of OptiX PTN 910/950, the Interface Protocol Type can be set to DCLS or 1PPS+TIME.) Interface Electricity: TTL(Set this parameter according to the external time interface. In the case of OptiX PTN 1900/3900, the Interface Electricity can be set to TTL, RS232 or RS422. In the case of OptiX PTN 910/950, the Interface Electricity can be set to RS422.) Time Quality Level: 187 Time Precision: 254 Clock Source Type: GPS Clock Source Priority 1: 10 Clock Source Priority 2: 128 Transmitting Distance Mode: Length Transmitting Length(m): 5
NOTE

3.

Click the BMC tab and set the related parameters.

l l l l l

4.

Click the Cable Transmitting Distance tab and set the related parameters.
l l

These parameters are used for compensating the clock wrap. The wrap indicates the transmission time difference of the cables between the NE and external time in the transmit and receive directions. You can compute the transmission time difference in a certain direction by using the GPS. Then, set the related parameters for time compensation. You can set the transmission time in a range from 0 ns to 1350 ns and transmission distance in a range from 0 m to 300 m. Only one of the preceding two parameters can be set. 1 m is equivalent to 4.5 ns.

Step 4 Set the PTP NE attributes. 1. Choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree. Set the related parameters, and then click Apply.

l l

Work Mode: BC Time Adjusting: Enabled

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

5-28

OptiX iManager T2000 Operation Guide for PTN NE Management

l

5 PTP Clock

Transmitting Message Multi-cast Mode: Entire Multi-cast(In the case of the entire multi-cast mode, the equipment multi-casts all the PTP packets; in the case of the partial multi-cast mode, the equipment unicasts the DELAY packets packets. In the case of interconnection with the equipment that supports the PTP, you can set the parameters according to the actual scenario.)

Step 5 Create a PTP time interface. 1. 2. 3. Choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree. Click the Port Status tab, and then click New to display the Create PTP Clock Port dialog box. Select 20-EFG2 and select 20-EFG2-1 and 20-EFG2-2 in Available Port. Then, click . 4. 5. 1. 2. Click OK. Set PTP Packet VLAN of each port to 100 and click Apply. Choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree. Click the Port Message tab and set the related parameters. Then, click Apply.
l

Step 6 Set the PTP packet period.

P/E Mode: E2E(In the case of the chain TC networking, the E2E mode is applicable; in the case of the mesh networking, the P2P mode is applicable.) SYNC Message Period(s): 8/1024 DELAY Message Period(s): 128/1024 ANNOUNCE Message Period(s): 128/1024 ANNOUNCE Timeout Coefficient: 3 (If the equipment does not receive the ANNOUNCE packets in three consecutive ANNOUNCE packet periods, the equipment considers that the link is faulty.)
NOTE

Set the periods of the clock packets as consistent for the equipment in the same clock subnet.

Step 7 Set the PTP clock port status. 1. 2. Choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree. Click the Port Status tab and set the related parameters. Then, click Apply.
l

PTP Message Format: PTP ETH(In the case of interconnection with the client-side equipment, set this parameter according to the encapsulation mode, that is, ETH encapsulation or IP encapsulation, of the PTP packets transmitted on the client side. By default, the encapsulation mode is the ETH encapsulation.) Port Status: MASTER

Step 8 Set the cable transmitting wrap.

Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 5-29

5 PTP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

1. 2.

Choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree. Click the Cable Transmitting Wrap tab and set the cable-related parameters for clock compensation such as Wrap Mode, Wrap Length(m), and Wrap Time(ns). Then, click Apply. 20-EFG2-1:
l

Wrap Direction: Positive(The positive direction indicates that the transmission distance or transmission time at the clock receive end is longer than the transmission distance or transmission time at the clock transmit end.) Wrap Mode: Time Wrap Time(ns): 10

l l

20-EFG2-2:
l

Wrap Direction: Negative(The negative direction indicates that the transmission distance or transmission time at the clock transmit end is longer than the transmission distance or transmission time at the clock receive end.) Wrap Mode: Time Wrap Time(ns): 20
NOTE

l l

These parameters are used for compensating the clock wrap. The wrap indicates the transmission time difference of the cables between the two NEs in the transmit and receive directions. You can compute the transmission time difference in a certain direction by using the GPS. Then, set the related parameters for time compensation. You can set the transmission time in a range from 0 ns to 65529 ns and transmission distance in a range from 0 m to 14652 m. Only one of the preceding two parameters can be set. 1 m is equivalent to 4.5 ns.

----End

5.6.4 Configuration Process (TC)

This section describes the process of configuring the TC of the PTP clock.

Procedure
Step 1 Set PTP NE attributes. 1. Choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree. Set the related parameters, and then click Apply. Work Mode: TC Step 2 Set the PTP packet period. 1. 2. Choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree. Click the Port Message tab and set the corresponding parameters. Then, click Apply. P/E Mode: E2E
NOTE

When P/E Mode is set to P2P, PDELAY Message Period(s) is configurable.

5-30

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

5 PTP Clock

Step 3 Set the cable transmitting wrap. Click the Cable Transmitting Wrap to set the cable-related parameters for clock compensation such as Wrap Mode, Wrap Length(m), and Wrap Time(ns). Then, click Apply. NE B: 19-EFF8-1
l l l

Wrap Direction: Positive Wrap Mode: Time Wrap Time(ns): 2

NE C: 19-EFF8-1
l l l

Wrap Direction: Negative Wrap Mode: Time Wrap Time(ns): 2

NE D: 20-EFG2-2
l l l

Wrap Direction: Positive Wrap Mode: Time Wrap Time(ns): 2

Step 4 Create the PTP clock service. 1. 2. Choose Configuration > Clock > PTP Clock > Clock Service from the Function Tree. Click New to display the Create Clock Service dialog box. Set the related parameters.
l l

Service ID: 1 Service Name: 1

3.

In the displayed dialog box, click the UNI tab, and then click Configuration to display the Configure Port dialog box. In the Available Port list select the port, and then click the Selected Port list.
l l l

4.

to remove the port to

NE B: 20-EFG2-2, 19-EFF8-1 NE C: 20-EFG2-1, 19-EFF8-1 NE D: 20-EFG2-1, 20-EFG2-2

5. 6. 7.

Set VLANs of each port to 100. Click OK to complete the configuration of the UNI. Click OK in the New Clock Service dialog box, and thus the clock service is created.

----End

5.6.5 Configuration Process (OC)

This section describes the process of configuring the OC of the PTP clock.

Procedure
Step 1 Set the frequency source selection mode.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 5-31

5 PTP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

In NE Explorer, select the NE icon. Choose Configuration > Clock > Frequency Selection Mode from the Function Tree. Set the related parameters. NE E and NE F: Frequency Selection Mode: PTP Synchronization Step 2 Optional: Set the clock subnet Choose Configuration > Clock > PTP Clock > Clock Subnet Configuration from the Function Tree. Set related parameters. Click Apply. NE E and NE F: Clock Subnet: 0 (The default clock subnet number is 0. By default, all the NEs are in the same clock subnet. The clock subnet number is set only when the clock subnet is divided.) Step 3 Set the attributes of the external time interface. 1. 2. In the NE Explorer, choose Configuration > Clock > PTP Clock > External Time Interface . Click the Basic Attribute tab to set the corresponding parameters. Then, click Apply. NE E and NE F:
l l l

Interface Mode: External Time Interface Direction: Egress Interface Protocol Type: DCLS (Set this parameter to DCLS or 1PPS+TIME according to the protocol type. In the case of OptiX PTN 1900/3900, the Interface Protocol Type can be set to DCLS, 1PPS+TIME or J.211. In the case of OptiX PTN 910/950, the Interface Protocol Type can be set to DCLS or 1PPS+TIME.) Interface Eletricity: RS422(Set this parameter according to the external time interface. In the case of OptiX PTN 1900/3900, the Interface Electricity can be set to TTL, RS232 or RS422. In the case of OptiX PTN 910/950, the Interface Electricity can be set to RS422.)

3.

Click the Cable Transmitting Distance tab to set the corresponding parameters. NE E and NE F:
l l

Transmitting Distance Mode: Length Transmitting Length(m): 5

NOTE

The preceding parameters are used to compensate the clock wrap. The wrap indicates the transmitting time difference of the cables between the NE and external time in the transmit and receive directions. You can compute the transmitting time difference in a certain direction by using the GPS, and then set the related parameters for time compensation. You can set the transmitting time that ranges from 0 ns to 1350 ns and transmitting distance that ranges from 0 m to 300 m. Only one of the preceding two parameters can be set. 1 m is equivalent to 4.5 ns.

Step 4 Set the PTP NE attributes. 1. Choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree. Set the related parameters, and then click Apply. NE E and NE F:
l

Work Mode: OC
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

5-32

OptiX iManager T2000 Operation Guide for PTN NE Management

l l l

5 PTP Clock

SLAVE_ONLY: SLAVE_ONLY Time Adjusting: Enabled Transmitting Message Multi-cast Mode: Entire Multi-cast (If it is set to the entire multicast mode, the equipment multicasts all the PTP packets. If it is set to the part multicast mode, the equipment unicasts the DELAY and PDELAY packets. In the case of the interconnection with the equipment that supports the PTP, you can set the parameters according to the actual scenario.)

Step 5 Create the PTP time port. 1. 2. Choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree. Click the Port Status tab, and then click New to display the Create PTP Clock Port dialog box. Select the corresponding port.
l l

NE E: 1-EF8F-1 NE F: 3-EF8F-1 .

3. 4. 5.

Click Click OK.

Set PTP Packet VLAN of each port to 100 and click Apply.

Step 6 Set the PTP packet period. 1. 2. Choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree. Click the Port Message tab to set the corresponding parameters. Click Apply. NE E:
l

P/E Mode: E2E (In the case of the TC networking, the E2E mode is applicable. In the case of the Mesh networking, the P2P mode is applicable.) SYNC Message Period(s): 8/1024 DELAY Message Period(s): 128/1024 ANNOUNCE Message Period(s): 128/1024 ANNOUNCE Timeout Coefficient: 3 (If the equipment does not receive the ANNOUNCE packets in three consecutive ANNOUNCE packet periods, the equipment takes that the link is faulty.)

NE F:
l l

P/E Mode: E2E SYNC Message Period(s): 8/1024 DELAY Message Period(s): 128/1024

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

5-33

5 PTP Clock
l

OptiX iManager T2000 Operation Guide for PTN NE Management

ANNOUNCE Message Period(s): 128/1024 ANNOUNCE Timeout Coefficient: 3

NOTE

In a clock subnet, periods of different clock packets of different sets of equipment should be consistent.

Step 7 Set the PTP time port status. 1. 2. Choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree. Click the Port Status tab to set related parameters. Click Apply. NE E and NE F:
l

PTP Message Format: PTP ETH (In the case of the interconnection with the clientside equipment, this parameter is set according to the encapsulation mode, that is, ETH encapsulation or IP encapsulation, used by the PTP packets transmitted by the client side. By default, the encapsulation mode is the ETH encapsulation.) Port Status: SLAVE

Step 8 Set the cable transmitting wrap. 1. 2. Choose Configuration > Clock > PTP Clock > Clock Synchronization Attribute from the Function Tree. Click the Cable Transmitting Wrap tab to set the cable-related parameters for clock compensation such as Wrap Mode, Wrap Length(m), and Wrap Time(ns). Then, click Apply. NE E: 1-EF8F-1:
l

Wrap Direction: Positive (The positive direction indicates that the transmitting distance or transmitting time of the clock receive end is longer than the transmitting distance or transmitting time of the clock transmit end.) Wrap Mode: Time Wrap Time(ns): 10

l l

NE F: 3-EF8F-1:
l l l

Wrap Direction: Positive Wrap Mode: Time Wrap Time(ns): 10

NOTE

The preceding parameters are used to commentate the clock wrap. The wrap indicates the transmitting time difference of the cables between the two NEs in the transmit and receive directions. You can compute the transmitting time difference in a certain direction by using the GPS, and then set the related parameters for time compensation. You can set the transmitting time that ranges from 0 ns to 65529 ns and transmitting distance that ranges from 0 m to 14562 m. Only one of the preceding two parameters can be set. 1 m is equivalent to 4.5 ns.

----End
5-34 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

6 Configuring a TOP Clock

6
About This Chapter

Configuring a TOP Clock

Timing transparent over PSN (TOP) clocks help to realize the frequency synchronization among packet clocks. 6.1 TOP Clock Overview TOP clock signals travel across a PSN so that the end-to-end clock synchronization and multiple clock domains are realized. 6.2 Basic Information This topic describes certain basic concepts, including the synchronization, TOP clock system number, TOP clock type, and TOP clock packet format. 6.3 TOP Clock Application In an asynchronous PSN network, TOP clocks helps to realize the frequency synchronization among different equipment. 6.4 TOP Clock Configuration Flow This topic describes the operation tasks for configuring the TOP clock service, and relations among these tasks. When configuring and managing the TOP clock services, follow the configuration flow. 6.5 Configuring a TOP Clock By configuring TOP clocks, you can synchronize the frequency among equipment. 6.6 TOP Clock Configuration Example This topic describes how to configure a TOP clock through a configuration example.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

6-1

6 Configuring a TOP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

6.1 TOP Clock Overview

TOP clock signals travel across a PSN so that the end-to-end clock synchronization and multiple clock domains are realized.

Purposes and Benefits

In a PTN clock transport network, clock signals can be introduced from external reference clocks or other clock transport network, and then transmitted to the equipment whose clocks need to be synchronized, for example, 3G base stations. The clock signals of the RNC of the wireless carrier can also be transmitted to 3G stations. Alternatively, networkwide time synchronization can also be realized, so that the end-to-end frequency and phase synchronization can be realized on the wireless equipment. TOP clock signals travel across a PSN so that the end-to-end clock synchronization and multiple clock domains are realized. The implementation principles are as follows: Clocks are mapped to TOP packets on the transmit end and then recovered from the TOP packets on the receive end. In this way, the end-to-end synchronization is realized. The TOP clock performance is greatly affected by the delay and jitter in the transmission path. Therefore, the TOP clock performance is greatly affected by the networking complexity and network transmission performance. In certain situations (for example, complex networking and severe network congestion), the performance of the clocks that are recovered may fail to meet the requirements. TOP clocks realize the frequency synchronization.

Compliant Standards and Protocols

There is no standards and protocols for the TOP clock.

6.2 Basic Information

This topic describes certain basic concepts, including the synchronization, TOP clock system number, TOP clock type, and TOP clock packet format.

Synchronization
Synchronization includes the frequency synchronization or phase synchronization. Frequency synchronization, that is, clock synchronization, indicates that certain strict relations are kept between signals in terms of frequency and phase. Therefore, the corresponding transience occurs at the same rate. In this way, the equipment in the entire network runs at the same rate. Phase synchronization synchronizes both the frequency and phase of the clock. The clock phase is expressed in numbers, that is, instant. Usually, time refers to the instant and interval. Difference between phase synchronization and frequency synchronization is shown in Figure 6-1.

6-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

6 Configuring a TOP Clock

Figure 6-1 Phase synchronization and frequency synchronization

Phase Synchronization Clock A

Clock B

Frequency Synchronization Clock A

Clock B

TOP Clock System Number

TOP clock system numbers are mapping to the adaptive clock and differential clock.
l

Adaptive clock: Clock signals are encapsulated into TOP clock packets. The precision of an adaptive clock is greatly affected by the PSN network. Differential clock: Differences between clock signals and a common clock are encapsulated into TOP clock packets. A differential clock is slightly affected by the network.

The difference between an adaptive clock and a differential clock is that the differential clock requires a common clock.

TOP Clock Type

Adaptive clocks can be classified into three types as follows: MASTER, SLAVER, and REPEATER. Differential clocks are classified into two types as follows: MASTER and SLAVER. Figure 6-2 shows the location of the MASTER, SLAVER, and REPEATER equipment in the network.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

6-3

6 Configuring a TOP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 6-2 Location of the MASTER, SLAVER, and REPEATER equipment in the network

GPS

NE3

Node B

NE2 MASTER REPEATRER

SLAVER

REPEATRER

RNC

NE1 REPEATRER NE5 NE4 NE6 SLAVER

Node B

MASTER: Clock signals are encapsulated into TOP packets and the packets are transmitted to downstream NEs. SLAVER: TOP packets received are decapsulated and clock signals are regained. Then, the clock signals are transmitted to cross-connect boards. REPEATER: TOP packets received are decapsulated and clock signals are regained. Then, the clock signals are encapsulated into TOP packets and the packets are transmitted to the downstream equipment.

TOP Clock Packet Format

TOP clock packets are classified into three types as follows: differential and adaptive TOP packets encapsulated based on PWE3, adaptive TOP packets encapsulated based on IEEE 1588v2 Ethernet, and adaptive TOP packets encapsulated based on IEEE 1588v2 IP. Figure 6-3 Differential and adaptive TOP packets encapsulated based on PWE3

DA

SA

Type

ECID 0x102 CESOP RTP 96bits

SSM 4bits

48bits 48bits 16bits 20bits 12bits 32bits

6-4

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

6 Configuring a TOP Clock

Figure 6-4 Adaptive TOP packets encapsulated based on IEEE 1588v2 Ethernet

DA

SA

Type

PTP 272bits

TimeStamp 80bits

48bits 48bits 16bits

Figure 6-5 Adaptive TOP packets encapsulated based on IEEE 1588v2 IP

DA

SA

Type

IP

UDP

PTP

TimeStamp 80bits

48bits 48bits 16bits 160bits 64bits 272bits

The TOP clock packets of the three types are mainly used for the interconnection with the thirdparty equipment during transmission. When the third-party equipment receives TOP clock packets or TOP clock packets are transmitted to the third-party, adaptive TOP packets encapsulated based on the IEEE 1588 are used, because the TOP packets encapsulated based on PWE3 is not standard. The differential and adaptive TOP packets encapsulated based on PWE3 can be used for the transmission among the PTN equipment. Currently, the PTN equipment supports the adaptive TOP packets encapsulated based on PWE3.

6.3 TOP Clock Application

In an asynchronous PSN network, TOP clocks helps to realize the frequency synchronization among different equipment. Figure 6-6 shows the application scenario where the equipment supports TOP clocks.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

6-5

6 Configuring a TOP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 6-6 Typical networking of TOP clock synchronization

GPS

NE3

Node B

SLAVER MASTER NE2

PSN
NE1

RNC

REPEATRER Router2 NE4 Router4 NE5

Router1

Third-Party IP Network

SLAVER Router3

Node B

Externel time signals TOP clock signals

In Figure 6-6, BITS sends clock signals to NE1 and RNC. As master node, NE1 sends TOP clock packets to two ports. One of the ports is connected to the PSN network. The TOP clock packets can be transmitted through the PSN network to realize the clock synchronization among NE1, NE2, and NE3. Then, the clock signals are transmitted to Node B. The other port is connected to a third-party network. The TOP clock packets can be transparently transmitted through the third-party network to realize the clock synchronization between NE1 and NE5. Then, the clock signals are transmitted to Node B.

6.4 TOP Clock Configuration Flow

This topic describes the operation tasks for configuring the TOP clock service, and relations among these tasks. When configuring and managing the TOP clock services, follow the configuration flow. Figure 6-7 shows the flow of configuring a TOP clock service. For details of each procedure, see the related topic.

6-6

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

6 Configuring a TOP Clock

Figure 6-7 Configuration flow of the TOP clock service

Required Start Optional Configure Differential clock source Configure the network-side interface

Configure the LSR ID

Configure the control plane

Configure the Tunnel

Configure the TOP clock service

Configure clock source priority sequence End

Table 6-1 Configuration flow of the TOP clock service Operation 1. Configure differential clock source 2. Configure the network-side interface 3. Configure the LSR ID Remarks When configuring a differential TOP clock, you need to specify the differential clock source as the common clock. Set the basic attributes and layer 3 attributes (including the status of a tunnel and IP address) of an interface for carrying a tunnel. Configure the LSR ID of an NE and the start value of the global label space.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

6-7

6 Configuring a TOP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

Operation 4. Configure the control plane

Remarks Set the protocol parameters related to the control plane to realize the creation of a tunnel.
l

If you create the static MPLS tunnel for transmitting TOP clock services, you need not configure the control plane. To create a dynamic MPLS tunnel to transmit the TOP clock service, you need to set the following protocol parameters: 1. Set the IGP-ISIS protocol parameters. 2. Set the MPLS-RSVP protocol parameters. Currently, only the static PW service is supported. Therefore, you do not need to configure the IGP-ISIS protocol parameters and the MPLS-RSVP protocol parameters.

If you create the IP tunnel or GRE tunnel for transmitting TOP clock services, you need to add static routes. For details, see Configuring Static Routes.

5. Configure a Tunnel

A tunnel is created to transmit services. TOP clock services can be transmitted only in static MPLS tunnels, IP tunnels, and GRE tunnels.
l

If a static MPLS tunnel is used, you can configure the tunnel on the per-NE or per-trail basis. You can set the relevant information such as the tunnel ID, service name, ingress node, egress node and transit node, and set the signaling type to static. If a dynamic MPLS Tunnel is required, name the service, set signaling type to dynamic, and specify the source node and sink node for the tunnel. If IP Tunnel or GRE Tunnel is used, you can set the relevant information such as the source board, source port, and sink port IP address.

6. Configure the TOP clock service

1. Create the TOP clock service, including setting the service ID, service name, clock type, and system clock number. 2. Configure the static PW, including setting the related information, such as the PW ID, label, and tunnel type. 3. Configure the QoS, including setting the QoS policy of the PW.

7. Configure the clock source priority table

Set the clock source priority table.

6.5 Configuring a TOP Clock

By configuring TOP clocks, you can synchronize the frequency among equipment. 6.5.1 Selecting a Differential Clock Source

6-8

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

6 Configuring a TOP Clock

When configuring differential clock services, you need a common clock for the restoration of clock signals. 6.5.2 Creating a TOP Clock Service TOP clock services are classified into three types: MASTER, SLAVER, and REPEATER. This topic describes how to configure the service clocks of the three types. 6.5.3 Setting the Clock Source Priority Table You can set the clock source priority table for an NE. In the MASTER mode, you can add external clock sources to the table. In the REPEATER and SLAVER modes, you can add the clock sources that are transmitted from the ingress directions of PWs to the table.

6.5.1 Selecting a Differential Clock Source

When configuring differential clock services, you need a common clock for the restoration of clock signals.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > TOP Clock > Differential Clock Source from the Function Tree.

Step 2 You can specify a system clock or an adaptive TOP clock as a differential clock source. You need to specify differential clock sources only for the differential clock services of the MASTER and SLAVER types. Step 3 Click Apply. The Operation Result dialog box is displayed, indicating that the operation is successful. ----End

6.5.2 Creating a TOP Clock Service

TOP clock services are classified into three types: MASTER, SLAVER, and REPEATER. This topic describes how to configure the service clocks of the three types.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The tunnel for transmitting clock services must be created.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

6-9

6 Configuring a TOP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

Context
NOTE

You can configure only three TOP services for an NE. They are the adaptive TOP clock, one-channel differential TOP clock, and two-channel differential TOP clock.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > TOP Clock > Clock Service from the Function Tree. Step 2 In the middle of the window, click New. The Create TOP Clock Service dialog box is displayed.

Step 3 Sets the parameters of the TOP clock service.

NOTE

When setting parameters, note the following:

l l

You can set Clock Type to MASTER, SLAVER, or REPEATER. MASTER: If this value is selected, clock signals are transmitted to the downstream equipment. Only the PW in the egress direction is supported. On an NE, the number of the PWs that are connected to all MASTER services cannot exceed 128. REPEATER: If this value is selected, the clock signals from the upstream equipment are received for frequency synchronization and then are transmitted to the downstream equipment. Hence, you need to create two PWs. Specifically, one of the PWs is in the ingress direction and used for transmitting clock signals from the upstream equipment. The other PW is in the egress direction and used for transmitting clock signals to downstream equipment. A maximum of five PWs are supported in the ingress direction and a maximum of 128 PWs are supported in the egress direction. SLAVER: If this value is selected, clock signals from the upstream equipment are received. Only the PW in the ingress direction is supported. A SLAVER service supports a maximum of five PWs.

6-10

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

6 Configuring a TOP Clock

Step 4 Click New, and the New PW dialog box is displayed.

Step 5 Click the General Attributes tab and set the basic attributes of the PW.
NOTE

When setting parameters, note the following:

l l l

You can set PW Type to Ethernet or Ethernet Tagged Mode. If the PW type is set to Ethernet Tagged Mode, a VLAN tag is added to the service that is transmitted in the PW. The tunnel type can be set to MPLS, IP, or GRE. If a tunnel needs to traverse a third-party network, the IP tunnel or GRE tunnel can be used. In the case of the REPEATER mode, you need to add the PWs in the ingress and egress directions.

Step 6 Click the Advanced Attributes tab and set the advanced attributes of the PW. After you complete the settings, click OK.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

6-11

6 Configuring a TOP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

l l

VCCV Verification Mode: VCCV is used to check the connectivity of a PW. To support the ping test of a PW, the parameter cannot be set to None. Request VLAN: When PW Type is set to Ethernet Tagged Mode, if the packet transmitted from the opposite end is without a VLAN tag, the PW adds a VLAN tag to the packet according to the preset value of Request VLAN.

Step 7 Click Configure QoS. The Configure QoS dialog box is displayed. Set the QoS information for the PW. After you complete the settings, click OK.

Step 8 Click OK. The Operation Result dialog box is displayed, indicating that the operation is successful. ----End

6-12

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

6 Configuring a TOP Clock

6.5.3 Setting the Clock Source Priority Table

You can set the clock source priority table for an NE. In the MASTER mode, you can add external clock sources to the table. In the REPEATER and SLAVER modes, you can add the clock sources that are transmitted from the ingress directions of PWs to the table.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The TOP clock service must be created.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > TOP Clock > Clock Service from the Function Tree. Select a clock service, then click the Clock Source Priority Table tab. Step 2 In the lower right portion of the window, click New. The Add Clock Source dialog box is displayed.

Step 3 Select the clock source that you want to add and click OK.
NOTE

You can add 16 clock sources for the priority table in the MASTER mode. You can add only 5 clock sources for the priority table in the REPEATER or SLAVER mode.

Step 4 Click Apply. The Operation Result dialog box is displayed, indicating that the operation is successful. Step 5 Optional: When selecting clock sources, you can click priorities of clock sources. or to adjust the

Step 6 Optional: Click Apply. The Operation Result dialog box is displayed, indicating that the operation is successful. ----End

6.6 TOP Clock Configuration Example

This topic describes how to configure a TOP clock through a configuration example. 6.6.1 Configuration Networking Diagram This topic describes the networking diagram for the TOP clock service configuration example.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 6-13

6 Configuring a TOP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

6.6.2 Service Planning To realize clock synchronization between the RNC and Node B, you need to create two TOP clock services. One of the services is transmitted in an MPLS tunnel and the other is transmitted in an IP tunnel. 6.6.3 Creating a TOP Clock Service This topic describes how to create an adaptive TOP clock service. In the configuration networking diagram, the differential TOP clock service is transmitted in an IP tunnel.

6.6.1 Configuration Networking Diagram

This topic describes the networking diagram for the TOP clock service configuration example. In Figure 6-8, as the master node, NE1 sends TOP clock packets to two ports. One of the ports is connected to the PSN network. The TOP clock packets among the MASTER and SLAVER equipment are transmitted in MPLS tunnels. The adaptive TOP clock services are created among NE1, and NE3 for clock synchronization among the three NEs. Then, the clock signals are transmitted to Node B. The other port is connected to a third-party network. The TOP clock packets can be transparently transmitted through the third-party network. The IP tunnel transmitting TOP clock packets needs to be created between the MASTER and SLAVER equipment, and the differential TOP clock service needs to be created between NE1 and NE5. In this way, the clock synchronization between NE1 and NE5 is realized. Then, the clock signals are transmitted to Node B. Figure 6-8 TOP clock networking application

GPS

NE3

Node B

SLAVER MASTER NE2

PSN
NE1

RNC

Router2 NE4 Router4 NE5

Router1

Third-Party IP Network

SLAVER Router3

Node B

Externel time signals TOP clock signals

In Figure 6-9, NE1 is the OptiX PTN 3900, and NE2, NE3, and NE5 are the OptiX PTN 1900. The Figure 6-9 shows the planning of boards and ports on each NE.
6-14 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

6 Configuring a TOP Clock

Figure 6-9 TOP clock networking application

10.0.1.1 10.0.0.2 4-EFG2- 1 (Port - 1) NE3

GPS

4-EFG2- 2 (Port - 2) 10.0.1.2 3-EG16- 2 (Port - 2) MASTER

Node B
SLAVER

4-EFG2- 1 (Port - 1) NE2 10.0.0.1

PSN
RNC
NE1 3-EG16- 1 (Port - 1) NE4 10.0.2.1 Router1 10.0.2.2 Router3 Router2 Router4 NE5

Third-Party IP Network

10.0.5.2

SLAVER

Node B

4-EFG2- 1 (Port - 1) 10.0.5.1

Externel time signals TOP clock signals

6.6.2 Service Planning

To realize clock synchronization between the RNC and Node B, you need to create two TOP clock services. One of the services is transmitted in an MPLS tunnel and the other is transmitted in an IP tunnel. Table 6-2 shows the planned parameters of the NEs. Table 6-2 NE parameters NE NE1 LSR ID 1.0.0.1 Port 3-EG16-2(Port-2) 3-EG16-1(Port-1) 4-EFG2-1(Port-1) 4-EFG2-2(Port-2) 4-EFG2-1(Port-1) 4-EFG2-1(Port-1) Port IP Address 10.0.1.2 10.0.2.1 10.0.0.2 10.0.1.1 10.0.0.1 10.0.5.1 Mask 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252
6-15

NE2 NE3 NE5

Issue 01 (2009-06-30)

1.0.0.2 1.0.0.3 1.0.0.4

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

6 Configuring a TOP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

Table 6-3 shows the planned static routes of the NEs. Table 6-3 Static routes Field Station Route List ID Board Port Next Hop IP Address Destination IP Destination IP Subnet Mask Value NE1 1 3-EG16 1(Port-1) 10.0.2.2 10.0.5.1 255.255.255.252 NE5 1 4-EFG2 1(Port-1) 10.0.5.2 10.0.2.1 255.255.255.252

Table 6-4 shows the planned parameters of the IP tunnel. Table 6-4 IP tunnel planning Field Station Tunnel ID Source Board Source Port Destination IP Value NE1 90 3-EG16 1(Port-1) 10.0.5.1 NE5 90 4-EFG2 1(Port-1) 10.0.2.1

Table 6-5 shows the planned parameters of the MPLS tunnel. Table 6-5 MPLS tunnel planning Field Tunnel ID Tunnel Name Signaling Type Scheduling Type
6-16

Positive Tunnel 100 TunnelforTOP Static E-LSP 101

Reverse Tunnel

ReverseTunnelforTOP Static E-LSP

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX iManager T2000 Operation Guide for PTN NE Management

6 Configuring a TOP Clock

Field Bandwidth(kbit/s) Ingress Node Transit Node Egress Node Ingress Node Route Information

Positive Tunnel No Limit NE3 NE2 NE1 NE1

l l

Reverse Tunnel No Limit NE1 NE2 NE3 NE3

l l

Out Port: 3-EG16-2(Port-2) Out Label: 20

Out Port: 4-EFG2-1(Port-1) Out Label: 21

Transit Node Route Information

NE2
l l l l

NE2
l l l l

In Port: 4-EFG2-2(Port-2) In Label: 20 Out Port: 4-EFG2-1(Port-1) Out Label: 30

In Port: 4-EFG2-1(Port-1) In Label: 21 Out Port: 4-EFG2-2(Port-2) Out Label: 31

Egress Node Route Information

NE3
l l

NE1
l l

In Port: 4-EFG2-1(Port-1) In Label: 30

Out Port: 3-EG16-2(Port-2) Out Label: 31

Table 6-6 shows the planned parameters of the TOP clock service. One of the TOP services is transmitted in the MPLS tunnel and the other is transmitted in the IP tunnel. Table 6-6 TOP clock service planning Field Service ID Service Name Clock Type 100 TOP Service1
l l

Value 101 TOP Service2

l l

NE1: MASTER NE3: SLAVER

NE1: MASTER NE5: SLAVER

Clock System No PW ID PW Signaling Type PW Type Direction

Adaptive TOP Clock 100 Static Ethernet

l l

One-Channel Differential TOP Clock 101 Static Ethernet

l l

NE1: Egress NE3: Ingress

NE1: Egress NE5: Ingress

PW Encapsulation Type
Issue 01 (2009-06-30)

MPLS

MPLS
6-17

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

6 Configuring a TOP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

Field PW Ingress Label/Source Port PW Egress Label/Sink Port Tunnel Type Tunnel 40 40 MPLS NE1: 100(TunnelforTOP)

Value 50 50 IP 90(Null)

NE3: 101(ReverseTunnelforTOP) Peer IP NE1: 1.0.0.3 NE3: 1.0.0.1 Control Word Control Channel Type VCCV Verification Mode No Use CW Ping NE1: 1.0.0.4 NE5: 1.0.0.1 No Use CW Ping

6.6.3 Creating a TOP Clock Service

This topic describes how to create an adaptive TOP clock service. In the configuration networking diagram, the differential TOP clock service is transmitted in an IP tunnel.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must learn about the networking requirements and service planning described in the example. The network must be created.

Procedure
Step 1 Set the frequency source selection mode. In the NE Explorer, select NE1 and choose Configuration > Clock > Select Frequency Source Mode from the Function Tree. Sets Frequency Selection Mode of NE1 to Physical Synchronization. ( NE A receives the clock signals from BITS through the external time interface. If the external time interface works as the clock input interface, Frequency Selection Mode cannot be set to PTP Synchronization for the equipment.) Step 2 Set LSR IDs. 1. 2. In the NE Explorer, select the NE1 and choose Configuration > MPLS Management > Basic Configuration. Set LSR ID, Start of Global Label Space and Start of Multicast Label Space. Click Apply. The configuration parameters are as follows:
6-18 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

l l

6 Configuring a TOP Clock

LSR ID: 1.0.0.1 (The LSR ID must be unique in the entire network) Start of Global Label Space: 0 (The minimum values of egress and ingress labels of the unicast tunnel.)

3.

Display the NE Explorer of NE2, NE3, and NE5 separately and perform the preceding two steps to set the parameters such as LSR ID. The configuration parameters are as follows:
l l l

NE2 LSR ID: 1.0.0.2 NE3 LSR ID: 1.0.0.3 NE5 LSR ID: 1.0.0.4

Step 3 Configure NNI interfaces. 1. 2. In the NE Explorer, select NE1 and choose Configuration > Interface Management > Ethernet Interface . In the General Attributes tab, select the 3-EG16-1(Port-1) and 3-EG16-2(Port-2). Rightclick the Port Mode filed and choose Layer 3 from the shortcut menu. Set the parameters as required, and click Apply.

The configuration parameters are as follows:

l l l

Enabled Port: Enabled Port Mode: Layer 3 (The port carries a tunnel.) Working Mode: Auto-Negotiation (Set the working modes of the local port and opposite port as the same.) Max Frame Length (byte): 1620 (Set this parameter according to the length of data packets. All the received data packets that contain more bytes than the maximum frame length are discarded.)

3. 4.

Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Select 3-EG16-1(Port-1) and 3-EG16-2(Port-2) in the Layer 3 Attributes tab. Right click the Enable Tunnel field and select Enabled from the drop-down list. Right-click the Specify IP field and choose Manually. Then, set the parameters such as IP Address and IP Mask. The configuration parameters are as follows:
l l

Enable Tunnel: Enabled Max Reserved Bandwidth (kbit/s): 1000000 (The maximum reserved bandwidth should not exceed the physical bandwidth of the bearer port. ) TE Measurement: 10 (The link with a smaller TE measurement value is preferred for route selection of a tunnel. You can intervene in the route selection by adjusting the TE measurement of the link. The smaller the value of the TE measurement, the higher the priority of the link. ) Specify IP: Manually (Manually indicates that you can set the IP address of the port.) IP Address: 10.0.2.1(3-EG16-1(Port-1)), 10.0.1.2(3-EG16-2(Port-2)) IP Mask: 255.255.255.252
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 6-19

l l l

Issue 01 (2009-06-30)

6 Configuring a TOP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

5. 6.

Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Display the NE Explorer for NE2, NE3, and NE5 separately. Perform Step 3.1 throughStep 3.5 to set parameters of each related interface. The NNIs to be configured on NE2 are 4-EFG2-1(Port-1) and 4-EFG2-2(Port-2). The basic attribute settings of each NNI are consistent with the settings of NE1-3-EG16-1(Port-1). The Layer 3 attribute settings of the NNIs are as follows:
l l

Enable Tunnel: Enabled Max Reserved Bandwidth (kbit/s): 1000000 ( The maximum reserved bandwidth should not exceed the physical bandwidth of the bearer port.) TE Measurement: 10 (The link with a smaller TE measurement value is preferred for route selection of a tunnel. You can intervene in the route selection by adjusting the TE measurement of the link. The smaller the value of the TE measurement, the higher the priority of the link. ) Specify IP: Manually (Manually indicates that you can set the IP address of the port.) IP Address: 10.0.0.2(4-EFG2-1(Port-1)), 10.0.1.1(4-EFG2-2(Port-2)) IP Mask: 255.255.255.252

l l l

The NNI to be configured on NE3 is 4-EFG2-1(Port-1). The basic attribute settings of the NNI are consistent with the settings of NE1-3-EG16-1(Port-1). The Layer 3 attribute settings of the NNI are as follows:
l l

Enable Tunnel: Enabled Max Reserved Bandwidth (kbit/s): 1000000 ( The maximum reserved bandwidth should not exceed the physical bandwidth of the bearer port.) TE Measurement: 10 (The link with a smaller TE measurement value is preferred for route selection of a tunnel. You can intervene in the route selection by adjusting the TE measurement of the link. The smaller the value of the TE measurement, the higher the priority of the link. ) Specify IP: Manually (Manually indicates that you can set the IP address of the port.) IP Address: 10.0.0.1(4-EFG2-1(Port-1)) IP Mask: 255.255.255.252

l l l

The NNI to be configured on NE5 is 4-EFG2-1(Port-1) The basic attribute settings of the NNI are consistent with the settings of NE1-3-EG16-1(Port-1). The Layer 3 attribute settings of the NNI are as follows:
l l

Enable Tunnel: Enabled Max Reserved Bandwidth (kbit/s): 1000000 ( The maximum reserved bandwidth should not exceed the physical bandwidth of the bearer port.) TE Measurement: 10 (The link with a smaller TE measurement value is preferred for route selection of a tunnel. You can intervene in the route selection by adjusting the TE measurement of the link. The smaller the value of the TE measurement, the higher the priority of the link.) Specify IP: Manually (Manually indicates that you can set the IP address of the port.) IP Address: 10.0.5.1(4-EFG2-1(Port-1)) IP Mask: 255.255.255.252
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

l l l

6-20

OptiX iManager T2000 Operation Guide for PTN NE Management

6 Configuring a TOP Clock

Step 4 Configure the control plane. 1. Configure the static routes for the IP tunnel. In the NE Explorer, select NE1 and choose Configuration > Control Plane Configuration > Static Route Management from the Function Tree. Click Create to create the static route between NE1 and NE5.

2.

Set the related parameters as follows:

l l l l

Route List ID: 1 Board: 3-EG16 port: 1(PORT-1) Next Hop IP Address: 10.0.2.2 (The IP address of the port must be in the same network segment as the next hop IP address.) Destination Node IP: 10.0.5.1 Destination Node Subnet Mask: 255.255.255.252

l l

3. 4.

Click Apply. The Operation Result dialog box is displayed indicating that the operation is success ful. In the NE Explorer of NE5, Refer to Step 4.1 to Step 4.3 to configure the static route between NE5 and NE1. Set the related parameters as follows:
l l l l

Route List ID: 1 Board: 4-EFG2 Port: 1(Port-1) Next Hop IP Address: 10.0.5.2 (The IP address of the port must be in the same network segment as the next hop IP address.) Destination Node IP: 10.0.2.1 Destination Node Subnet Mask: 255.255.255.252

l l

Step 5 Create the IP Tunnel. 1. In the NE Explorer, select NE1 and choose Configuration > IP/GRE Tunnel Management > IP Tunnel Managementfrom the Function Tree. Click New. The Create IP Tunnel dialog box is displayed.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

6-21

6 Configuring a TOP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

2.

Set the ID, source board, source port, and destination IP address for the IP tunnel. Click OK. Set the related parameters as follows:
l l

Tunnel ID: 90 Source Board: 3-EG16 (The Ethernet interface whose Layer 3 attribute is enabled can transmit the IP tunnel.) Source Port: 1(Port-1) Destination IP: 10.0.5.1

l l

3.

In the NE Explorer of NE3, refer to Step 5.1 to Step 5.2 to configure the information about the IP tunnel. Set the related parameters as follows:
l l l l

Tunnel ID: 90 Source Board: 4-EFG2 Source Port: 1(Port-1) Destination IP: 10.0.2.1

Step 6 Create an MPLS tunnel. 1. Select NE1 in the NE Explorer. Choose Configuration > MPLS Management > Unicast Tunnel Management from Function Tree. Click New. The New Unicast Tunnel dialog box is displayed. Configure parameters for the positive tunnel and reverse MPLS tunnel such as Tunnel ID, Tunnel name, port and labels. The clock service is unidirectional. Hence, you only need to create a unidirectional tunnel.

2.

6-22

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

6 Configuring a TOP Clock

The configuration parameters are as follows:

l l

Tunnel ID: 100(Positive Tunnel), 101(Reverse Tunnel) Tunnel Name: TunnelforTOP (Positive Tunnel), ReverseTunnelforTOP (Reverse Tunnel) Node Type: Ingress(Positive Tunnel), Egress(Reverse Tunnel) Bandwidth(kbit/s): No Limit (Set the bandwidth according to networking planning.) Out Board/Logic Interface Type: 3-EG16 (The source board of the Tunnel.) Out Port: 2(Port-2) (The source port of the Tunnel.) Next Hop Address: 10.0.1.1 (The IP address of the interface on the next node on the tunnel.) Sink Node: 1.0.0.3 (The LSR ID of the interface on the sink node on the tunnel.) Tunnel Type: E-LSP(E-LSP indicates that the tunnel determines the scheduling priority and discard priority of packets according to the EXP information. On one MPLS tunnel of the E-LSP type, there can be a maximum of eight types of PWs.) EXP: none (Set the tunnel priority according to networking planning.)

l l l l l

l l

3.

Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 6-23

Issue 01 (2009-06-30)

6 Configuring a TOP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

4.

In the NE Explorer, select NE2. Then, configure the tunnel parameters of the transit node by following Step 6.1 to Step 6.3.

Set related parameters and ensure that the general information of the tunnel is the same as that on NE1. The configuration parameters are as follows:
l l l l l l l l l l

Node Type: Transit (NE2 is a transit node on the tunnel.) In Board/Logic Interface Type: 4-EFG2 In Port: 1(Port-1)(Positive Tunnel), 2(Port-2)(Reserve Tunnel) In Label: 20(Positive Tunnel), 21(Reserve Tunnel) Out Board/Logic Interface Type: 4-EFG2 Out Port: 2(Port-2)(Positive Tunnel), 1(Port-1)(Reserve Tunnel) Out Label: 30(Positive Tunnel), 31(Reserve Tunnel) Next Hop Address: 10.0.0.1 Source Node: 1.0.0.1 (The LSR ID of the source node on the tunnel.) Sink Node: 1.0.0.3 (The LSR ID of the sink node on the tunnel.)

5.

In the NE Explorer, select NE3. Then, configure the tunnel parameters of the egress node by following Step 6.1 to Step 6.3.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

6-24

OptiX iManager T2000 Operation Guide for PTN NE Management

6 Configuring a TOP Clock

Set related parameters and ensure that the general information of the tunnel is the same as that on NE1. The configuration parameters are as follows:
l l l l l l

Node Type: Egress (NE3 is a terminal node on the tunnel.) In Board/Logic Interface Type: 4-EFG2 In Port: 1(Port-1) In Label: 30 (Positive Tunnel) Out Label: 31 (Reverse Tunnel) Source Node: 1.0.0.1 (The LSR ID of the source node on the tunnel.)

Step 7 Create adaptive TOP clock services for NE1, and NE3. 1. In the NE Explorer, select NE1 and choose Configuration > Clock > TOP Clock > Clock Service from the Function Tree. In the middle of the window, click New. The Create TOP Clock Service dialog box is displayed.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

6-25

6 Configuring a TOP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

2.

Set the basic attributes of the TOP clock service according to the service planning. Set the related parameters as follows:
l l l l

Service ID: 100 Service Name: TOP Service1 Clock Type: MASTER Clock System Number: Adaptive TOP clock

3.

Click New, and the New PW dialog box is displayed.

6-26

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

6 Configuring a TOP Clock

4.

Click the General Attributes tab and set the basic attributes of a PW based on the service planning. Set the related parameters as follows:
l l l l

PW ID: 100 PW Signaling: Static PW Type: Ethernet Direction: Egress (A MASTER node supports only the PWs in the outbound direction and transmits the clock signals to the downstream PTN equipment.) PW Encapsulation Type: MPLS PW Ingress Label: 40 PW Egress Label: 40 Tunnel Type: MPLS Tunnel: 100(TunnelforTOP) Peer IP: 1.0.0.3

l l l l l l

5.

Click the Advanced Attributes tab and set the advanced attributes of the PW based on the service planning. After you complete the setting, click OK.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

6-27

6 Configuring a TOP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

Set the related parameters as follows:

l l l

Control Word: No Use Control Channel Type: CW VCCV Verification Mode: Ping

6.

Optional: Click Configure QoS. The Configure QoS dialog box is displayed. Set the QoS information for the PW. After you complete the setting, click OK.

7. 8.

Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Configure the clock source priority table. In the NE Explorer, select NE1 and choose Configuration > Clock > TOP Clock > Clock Service from the Function Tree. Click the Clock Source Priority Table tab. Select the clock service, in the lower right portion of the window, click New. The Add Clock Source dialog box is displayed.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

9.

6-28

OptiX iManager T2000 Operation Guide for PTN NE Management

6 Configuring a TOP Clock

10. Specify 23-D12-1(Port-1) as the clock source and click OK. 11. Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. 12. In the NE Explorer of NE3, refer to Step 7.1 to Step 7.7 to configure the adaptive TOP clock service of NE3. The NE3 is a SLAVER node and thus you need to create a PW in the ingress direction for transmitting the clock signals from the upstream equipment. Set the parameters related to basic attributes as follows:
l l l l

Service ID: 100 Service Name: TOP Service1 Clock Type: SLAVER Clock System Number: Adaptive TOP clock

Set the parameters related the basic attributes of the PW as follows:

l l l l

PW ID: 100 PW Signaling: Static PW Type: Ethernet Direction: Ingress (A SLAVER node supports the PW in the ingress direction. The PW in the ingress direction receives the clock signals from upstream nodes. PW Encapsulation Type: MPLS PW Ingress Label: 40 PW Egress Label: 40 Tunnel Type: MPLS Tunnel: 101(ReverseTunnelforTOP) Peer IP: 1.0.0.1

l l l l l l

Set the parameters related the advanced attributes of the PW as follows:

l l l

Control Word: No Use Control Channel Type: CW VCCV Verification Mode: Ping

Step 8 Create differential TOP clock services for NE1 and NE5. 1. Select a common clock. In the NE Explorer, select NE1 and choose Configuration > Clock > TOP Clock > Differential Clock Source from the Function Tree. Set Differential Clock Source to System Clock.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 6-29

Issue 01 (2009-06-30)

6 Configuring a TOP Clock

OptiX iManager T2000 Operation Guide for PTN NE Management

2.

To create a one-channel differential TOP clock service on NE1, refer to Step 7.1 to Step 7.7. Set the parameters related to basic attributes as follows:
l l l l

Service ID: 101 Service Name: TOP Service2 Clock Type: MASTER Clock System Number: One-Channel Differential TOP clock

Set the parameters related to basic attributes of the PW as follows:

l l l l l l l l l l

PW ID: 101 PW Signaling: Static PW Type: Ethernet Direction: Egress PW Encapsulation Type: MPLS PW Ingress Label: 50 PW Egress Label: 50 Tunnel Type: MPLS Tunnel: 90() Peer IP: 1.0.0.4

Set the parameters related the advanced attributes of the PW as follows:

l l l

Control Word: No Use Control Channel Type: CW VCCV Verification Mode: Ping

3. 4. 5.

To select the clock source for the differential clock on NE1, refer to Step 7.8 to Step 7.11. In the NE Explorer of NE5, refer to Step 8.1 to specify the common clock of NE5 as the system clock. In the NE Explorer of NE5, refer to Step 7.1 to Step 7.7 to configure the differential TOP clock service of NE5. Set the parameters related to basic attributes as follows:
l l l l

Service ID: 101 Service Name: TOP Service2 Clock Type: Slaver Clock System Number: One-Channel Differential TOP clock

Set the parameters related to basic attributes of the PW as follows:

6-30 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

l l l l l l l l l l

6 Configuring a TOP Clock

PW ID: 101 PW Signaling: Static PW Type: Ethernet Direction: Ingress PW Encapsulation Type: MPLS PW Ingress Label: 50 PW Egress Label: 50 Tunnel Type: MPLS Tunnel: 90() Peer IP: 1.0.0.1

Set the parameters related the advanced attributes of the PW as follows:

l l l

Control Word: No Use Control Channel Type: CW VCCV Verification Mode: Ping

----End

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

6-31

OptiX iManager T2000 Operation Guide for PTN NE Management

7 Configuring the Equipment-Level Protection

Configuring the Equipment-Level Protection

About This Chapter

The equipment-level protection includes the subcard TPS protection and board 1+1 protection. 7.1 Configuring the Subcard TPS Protection This section describes how to configure the subcard TPS protection. 7.2 Configuring Board 1+1 Protection BPS is a protection mode based on the board. BPS requires two boards: active and standby. When a link is down or a hardware failure is detected on the active board at any port, services are switched from the active board to the protection board. In this way, services are protected. 7.3 Configuration Case of the TPS The configuration case of the TPS describes how to configure the TPS.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

7-1

7 Configuring the Equipment-Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

7.1 Configuring the Subcard TPS Protection

This section describes how to configure the subcard TPS protection.

Context
The configuration of the subcard TPS protection includes the following contents: 7.1.1 TPS Application The TPS protects processing boards that are accessed by using interface boards. When important services run on a working board, you can use a protection board of the same type to provide the TPS protection for the working board. The TPS can be triggered in the case that the hardware of the working board fails or is removed. You can also manually trigger the TPS on the T2000. 7.1.2 Creating a TPS Protection Group of Sub-Boards The working board and protection board form a TPS protection group. If the working board becomes faulty after the creation of a TPS protection group is completed, the service is automatically switched to the protection board. 7.1.3 Checking the Subcard TPS Status When a tributary protection switching (TPS) occurs, it indicates that the protected working board fails. You can check the TPS status to timely find faults so that services are not affected. 7.1.4 Performing a Subcard TPS During deployment and commissioning, you can perform a switching to test whether the TPS of a board works properly and to check whether the protection switching ability is available. During maintenance, you can perform this operation to locate faults.

7.1.1 TPS Application

The TPS protects processing boards that are accessed by using interface boards. When important services run on a working board, you can use a protection board of the same type to provide the TPS protection for the working board. The TPS can be triggered in the case that the hardware of the working board fails or is removed. You can also manually trigger the TPS on the T2000.

7.1.2 Creating a TPS Protection Group of Sub-Boards

The working board and protection board form a TPS protection group. If the working board becomes faulty after the creation of a TPS protection group is completed, the service is automatically switched to the protection board.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. Creation of the working and protection service sub-boards must be completed.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > TPS Protection from the Function Tree.
7-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

7 Configuring the Equipment-Level Protection

Step 2 Click Create and the Create TPS Protection Group dialog box is displayed. Step 3 Select the protection board and the working board, and set priorities in the working board list.

Step 4 Set the wait-to-restore (WTR) time. Step 5 Click OK. A prompt is displayed indicating that the operation is successful. Click Close. ----End

7.1.3 Checking the Subcard TPS Status

When a tributary protection switching (TPS) occurs, it indicates that the protected working board fails. You can check the TPS status to timely find faults so that services are not affected.

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. A TPS protection group must be correctly configured.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > TPS Protection from the Function Tree. Step 2 Click Query to check the subcard TPS status. ----End

7.1.4 Performing a Subcard TPS

During deployment and commissioning, you can perform a switching to test whether the TPS of a board works properly and to check whether the protection switching ability is available. During maintenance, you can perform this operation to locate faults.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 7-3

7 Configuring the Equipment-Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. A TPS protection group must be correctly configured.

Context

CAUTION
Performing the protection switching may interrupt services.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > TPS Protection from the Function Tree. Step 2 Right-click in the protected board list and select a switching operation. Step 3 In the Confirm dialog box, click OK. Step 4 In the Operation Result dialog box, click Close. Step 5 Click Query to query the switching status. ----End

7.2 Configuring Board 1+1 Protection

BPS is a protection mode based on the board. BPS requires two boards: active and standby. When a link is down or a hardware failure is detected on the active board at any port, services are switched from the active board to the protection board. In this way, services are protected. 7.2.1 Board 1+1 Protection For the important system control, cross-connect board of the equipment, an NE supports installing two boards of the same type. In this way, one board serves as a backup of the other. When the working board fails or receives a protection switching command, a switching of services is performed to prevent the equipment from being affected, and thus the equipment can run normally. 7.2.2 Querying the Board 1+1 Protection Group You can create 1+1 protection for the SCC and cross-connect boards. When the working board fails, the services are automatically switched to the protection board. 7.2.3 Checking 1+1 Board Switching Status If board 1+1 protection switching is triggered, it indicates that the protected board has failed. The network maintenance engineers can check 1+1 board switching status to detect the faults that caused the failure. 7.2.4 Performing 1+1 Board Protection Switching By using the T2000, you can perform or clear protection switching for a board. During deployment and commissioning, you can perform switching to test whether the board protection switching works properly. In fault maintenance, you can perform this operation to locate faults.
7-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

7 Configuring the Equipment-Level Protection

7.2.1 Board 1+1 Protection

For the important system control, cross-connect board of the equipment, an NE supports installing two boards of the same type. In this way, one board serves as a backup of the other. When the working board fails or receives a protection switching command, a switching of services is performed to prevent the equipment from being affected, and thus the equipment can run normally.

7.2.2 Querying the Board 1+1 Protection Group

You can create 1+1 protection for the SCC and cross-connect boards. When the working board fails, the services are automatically switched to the protection board.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Board 1+1 Protection from the Function Tree. Step 2 Click Query to query the current primary and secondary status from the NE.

----End

7.2.3 Checking 1+1 Board Switching Status

If board 1+1 protection switching is triggered, it indicates that the protected board has failed. The network maintenance engineers can check 1+1 board switching status to detect the faults that caused the failure.

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. The protection board must be created.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Board 1+1 Protection from the Function Tree. Step 2 Click Query to query the 1+1 board switching status. Step 3 Click Close. ----End
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 7-5

7 Configuring the Equipment-Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

7.2.4 Performing 1+1 Board Protection Switching

By using the T2000, you can perform or clear protection switching for a board. During deployment and commissioning, you can perform switching to test whether the board protection switching works properly. In fault maintenance, you can perform this operation to locate faults.

Prerequisite
l l l

You must be an NM user with "NE operator" authority or higher. The 1+1 board protection group must be available. The protection board works properly.

Context

CAUTION
If the protection board is abnormal, services may be interrupted when you perform switching.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Board 1+1 Protection from the Function Tree. Step 2 Click Query to view the active board and the current working board. Step 3 Select a 1+1 protection group, right-click, and choose Working/Protection Switching from the shortcut menu. Step 4 Click Query to refresh the switching status of the 1+1 protection group. ----End

7.3 Configuration Case of the TPS

The configuration case of the TPS describes how to configure the TPS. 7.3.1 Case Description Before the service creation, the service planning designs the details of the service, which are used for guiding the service configuration. The service planning includes the networking and requirement, and planning of the configuration data. 7.3.2 Configuration Process This section describes the process of configuring the TPS protection in the configuration case.

7.3.1 Case Description

Before the service creation, the service planning designs the details of the service, which are used for guiding the service configuration. The service planning includes the networking and requirement, and planning of the configuration data.
7-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

7 Configuring the Equipment-Level Protection

Board Planning
When used with the CXP, the MD1 sub-board provides the TPS protection. After the TPS protection is realized, if the working board fails, the services are switched to the protection board. In this way, the services are protected. As shown in Figure 7-1, in the case of the OptiX PTN 1900 NE, a sub-board MD1, housed in slot 1-1, performs as the working sub-board. A sub-board MD1, housed in slot 2-1, performs as the protection sub-board. In this way, the 1:1 TPS protection is realized. Figure 7-1 Hardware configuration of TPS
SLOT 10 (FANA) SLOT 9 PIU SLOT 1-1 SLOT 1 SLOT 2-1 SLOT 2 MD1 CXP MD1 CXP SLOT 2-2 SLOT 8 PIU SLOT 3 SLOT 4 L75 L75 SLOT 5 SLOT 6 SLOT 7 SLOT 1-2

SLOT 11 (FANB)

Service Planning
According to engineering requirements, the engineering department makes engineering planning and then outputs the detailed planning information. Figure 7-1 shows the board planning, and Table 7-1 lists the configuration parameters of the TPS protection. Table 7-1 Configuration parameters of the TPS protection Attribute Working Board Protection Board Priority WTR Time(s) Value 1-CXP-1-MD1 2-CXP-1-MD1 Priority-1 600

7.3.2 Configuration Process

This section describes the process of configuring the TPS protection in the configuration case.

Prerequisite
You must understand the board and service planning of the example.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 7-7

7 Configuring the Equipment-Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 On the T2000, configure the TPS protection group for the sub-board. For the configuration method, see 7.1.2 Creating a TPS Protection Group of Sub-Boards. The following parameters, which are related to the TPS protection group, should be configured.
l l l l

Working Board: 1-CXP-1-MD1 Protection Board: 2-CXP-1-MD1 Priority: Priority-1 WTR Time(s): 600

----End

7-8

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

8 Configuring the Control Plane

8
About This Chapter

Configuring the Control Plane

The control plane, responsible for the call control and connection control, consists of a group of communication entities. The control plane creates, releases, monitors and maintains the connection through signaling, and it automatically recovers the connection upon failure. 8.1 Basic Concepts This section describes the related protocols of the control plane and application scenarios of these protocols when the control plane is configured. 8.2 Configuring the IGP-ISIS Protocol If the dynamic MPLS tunnel is required, the IGP-ISIS protocol must be configured. The IGPISIS protocol is used to discover the network topology. Through the IGP-ISIS protocol, each NE can obtain the information of the adjacent NE. When the IGP-ISIS protocol is used with the RSVP-TE protocol, the creation of the MPLS tunnel is complete. The IGP-ISIS protocol configuration includes the configuration of node and port attributes, query and configuration of route importing information, and query of the TE link information. 8.3 Configuring the MPLS-LDP Protocol If the dynamic PW need be configured, the MPLS-LDP protocol must be configured. The MPLSLDP is used to create the dynamic PW and to distribute the PW label. The NE can only obtain the information of the adjacent NE through the IGP-ISIS protocol. In the case of a single service, the NEs at the two ends can known each other by configuring the MPLS-LDP peer entity of the MPLS-LDP protocol. On the T2000, the MPLS-LDP peer entities can be created and the MPLSLDP protocol can be configured. 8.4 Configuring the MPLS-RSVP Protocol The MPLS-RSVP protocol is used to create dynamic MPLS tunnel and to distribute the tunnel label. On the T2000, the parameters of the MPLS-RSVP protocol can be queried. This protocol does not need special configuration, and thus the user can configure each parameter according to requirements. 8.5 Configuring the OSPF Protocol On the network, the OSPF protocol transfers the link state information and computes routes to obtain the routing information according to the link state information. Through the OSPF protocol, each NE can obtain the information of the adjacent NE. When the OSPF protocol is used with the RSVP-TE protocol, the creation of the MPLS tunnel is complete. The OSPF
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8-1

8 Configuring the Control Plane

OptiX iManager T2000 Operation Guide for PTN NE Management

protocol configuration includes the configuration of node and port attributes, query and configuration of route importing information, and query of the TE link information. 8.6 Configuring the MP-BGP MP-BGP means that the BGP runs in the interior of the autonomous system. In an L3VPN, route switching between the PE equipment is realized through the MP-BGP. 8.7 Configuring Static Routes The static routes are selected according to the preset route options in the network. On the T2000, the static routes can be queried and created. 8.8 Configuring the Address Parse On the T2000, the IP address and MAC address of the ARP table items can be created and queried.

8-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

8 Configuring the Control Plane

8.1 Basic Concepts

This section describes the related protocols of the control plane and application scenarios of these protocols when the control plane is configured. 8.1.1 IGP-ISIS Protocol The intermediate system to intermediate system (IS-IS) routing protocol, a link state protocol, belongs to the internal gateway protocol and is applicable to the internal of the autonomous system. The equipment uses the IS-IS routing protocol, which is used with the label distribution protocols RSVP-TE and LDP to realize the dynamic creation of the MPLS LSP. 8.1.2 OSPF Protocol The open shortest path first (OSPF) protocol is a dynamic interior gateway protocol (IGP) that is compiled based on link status by IETF. 8.1.3 BGP Protocol The border gateway protocol (BGP) is the used to discover dynamic routes between autonomous systems (ASs). The earlier three versions of BGP are BGP-1 (defined in RFC 1105), BGP-2 (defined in RFC 1163), and BGP-3 (defined in RFC 1267). The present version of BGP is BGP-4 (defined in RFC1771). BGP-4 (RFC1771) is applied to distributed structures and supports classless inter-domain routing (CIDR). 8.1.4 MPLS-LDP Protocol The multi-protocol label switch label distribution protocol (MPLS-LDP) is used for the label switched routers (LSR) to distribute labels in the network. 8.1.5 MPLS-RSVP Protocol Multi-protocol label switch resource reservation protocol (MPLS-RSVP) supports the distribution of MPLS labels. In addition, when transmitting the label binding message, it carries the resource reservation information, used as a signaling protocol to create, delete or modify the tunnel in the MPLS network. 8.1.6 ARP Protocol Address resolution protocol (ARP) is used to map the IP address (alias: logical address) at the network layer into the MAC address (alias: physical address) at the data link layer.

8.1.1 IGP-ISIS Protocol

The intermediate system to intermediate system (IS-IS) routing protocol, a link state protocol, belongs to the internal gateway protocol and is applicable to the internal of the autonomous system. The equipment uses the IS-IS routing protocol, which is used with the label distribution protocols RSVP-TE and LDP to realize the dynamic creation of the MPLS LSP. The IS-IS routing protocol used by the equipment creates and synchronizes the link state database (LSD) through routing protocol packets, such as link state PDUs. Based on the LSDB and path cost, the equipment uses the optimized shortest path first (SPF) algorithm to generate the routing table, and uses the IS-IS TE of the IS-IS routing protocol to generate the traffic engineering database (TEDB). The TEDB and routing table are the bases of creating the MPLS LSP. The TEDB computes the route that the MPLS LSP travels through. The routing table forwards the RSVP-TE and LDP protocol packets to realize label distribution. In this way, the MPLS LSP is dynamically created.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

8-3

8 Configuring the Control Plane

OptiX iManager T2000 Operation Guide for PTN NE Management

Three features of the IS-IS routing protocol are supported by the equipment, that is, three types of IS-IS routing protocol packets, optimized SPF algorithm, path cost, and IS-IS traffic engineering (IS-IS TE).

Three Types of IS-IS Routing Protocol Packets

The IS-IS routing protocol belongs to the network player of the OSI protocol model. The IS-IS routing protocol runs directly at the data link layer. When the IS-IS routing protocol is processed, the decapsulation of the network layer is absent. With the preceding feature, the IS-IS routing protocol is more applicable to the PTN transport network using the MPLS packet switching technology. The IS-IS routing protocol packets use the uniform encapsulation format. The length of the packets is changeable and the extensibility is strong. The complexity of the protocol is decreased, because the types of the protocol packets are few. Thus, the running is more reliable and efficient. The equipment realizes the following three types of IS-IS routing protocol packets:
l

Hello packets Hello packets are used to construct and maintain neighbor relation between network nodes. Hence, Hello packets are also called IS-to-IS hello (IIH) PDUs.

Link state PDUs Link state PDUs are used to exchange the link state information. In a network running the IS-IS routing protocol, each network node generates a link state PDU, which contains all the link state information of this network node. To generate its own LSDB, each network node collects all the link state PDUs within the local domain and between domains.

SNP packets Sequence number PDUs (SNP) describe the link state PDUs in all or part of the LSDB. The SNP is used to synchronize and maintain the LSDB of each network node in the PTN network.

Optimized SPF Algorithm

The IS-IS routing protocol realized by the equipment uses the optimized SPF algorithm for route computation and update. When the topology is changed, the resources (network bandwidth, processing capability of network nodes, and memory) for updating the new route are few, and thus the convergence rate of the entire network is improved.

Path Cost
The equipment supports the manual setting of path cost, and controls the route that the MPLS LSP travels through when it is dynamically created.

IS-IS TE
When the MPLS constructs the LSP, the traffic engineering information of all the links in the local domain should be known. The IS-IS TE realized by the equipment supports the construction of the MPLS LSP. The equipment obtains the traffic engineering information (link utilization and path cost) of all the links in the network through the IS-IS routing protocol. It constructs and synchronizes the TEDB, and uses the constrained shortest path first (CSPF) algorithm used by the TEDB to compute the route that the MPLS LSP travels through.
8-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

8 Configuring the Control Plane

8.1.2 OSPF Protocol

The open shortest path first (OSPF) protocol is a dynamic interior gateway protocol (IGP) that is compiled based on link status by IETF. The OptiX PTN equipment supports the OSPF protocol. On the client side, the OptiX PTN equipment discovers routes by running the OSPF protocol. On the network side, the OptiX PTN equipment discovers routes by running the OSPF protocol and provides the conditions for tunnel creation, that is, enables OSPF traffic engineering (TE). On the network, the OSPF protocol transfers the link state information and computes routes to obtain the routing information according to the link state information. The OSPF protocol supported by the OptiX PTN equipment complies with RFC 3623 (Graceful OSPF Restart), RFC 2328 (OSPF Version 2), RFC 3630 (TE Extensions to OSPF Version 2), and RFC 2370 (The OSPF Opaque LSA Option).

Basic Concepts
The basic concepts with regard to the OSPF protocol include the OSPF protocol packet, link state advertisement (LSA), neighbor, adjacency, router ID, and OSPF TE.
l

There are the following categories of OSPF protocol packets:

Hello packets: The Hello packets are used to discover and maintain the OSPF neighborhood and are sent periodically. Database description (DD) packets: Exchanging the DD packets are used to maintain synchronization of the databases. The DD packets describe the summary of the local link state database (LSDB). Link state request (LSR) packet: The LSR packets are used to request for the required LSA from each other. The LSR packets are sent to each other only after they successfully start to exchange the DD packets. Link state update (LSU) packet: The LSU packets are used to send the required LSA to each other. Link state acknowledgment (LSAck) packet: The LSAck packets are used to acknowledge the received LSA.

The OSPF advertises the routing information by encapsulating the route description into LSAs. The common LSA categories are as follows:

Router LSA (type 1): The router LSA describes the link status and cost of the OptiX PTN equipment and is flooded only in the OSPF area. Network LSA (type 2): The network LSA describes the status of the links in the local network segment and is flooded in the OSPF area. Network summary LSA (type 3): The network summary LSA describes the routes in a certain network segment in the OSPF area and advertises the routing information to other related OSPF areas. AS boundary router (ASBR) summary LSA (Type 4): The ASBR summary LSA describes the routes to the ASBRs and advertises the routing information to all other related OSPF areas except the areas where the ASBRs are located. AS external LSA (type 5): The AS external LSA describes the routers to the outside of the AS and advertises the routing information to all the OSPF areas (Stub area and NSSA excluded).
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8-5

Issue 01 (2009-06-30)

8 Configuring the Control Plane

OptiX iManager T2000 Operation Guide for PTN NE Management

Not so totally stub area (NSSA) LSA (type 7): The NSSA LSA describes the routers to the outside of the AS and is flooded only in the NSSA. Opaque LSA (type 10): The opaque LSA carries the TE information.

Neighbor: When running the OSPF protocol, the OptiX PTN equipment sends the Hello packets through the OSPF interface. When receiving the Hello packets, the OptiX PTN equipment checks the related parameters defined in the packets for consistency. If the related parameters are consistent, the neighborhood is established. Adjacency: The neighborhood does not necessarily ensure the adjacency. The network type determines when the adjacency can be established. Two OptiX PTN systems can establish the adjacency only after they successfully exchange the DD packets and LSA. Router ID: A router ID is a 32-bit value that uniquely identifies an OptiX PTN equipment in an AS. A router ID is important for the OptiX PTN equipment to run the OSPF protocol. OSPF TE: The OSPF TE supports the creation of the label switching paths (LSPs) for TE. Before building LSPs, the MPLS protocol has to know the traffic information of all links in the area. The MPLS protocol obtains the TE information of the links through the OSPF protocol.

OSPF Route Computation

The OSPF protocol computes routes in the following way: 1. Each OptiX PTN equipment generates the LSA based on the surrounding network topology and sends the LSA to other systems on the network through the DD packets, LSR packets, or LSU packets. Each OptiX PTN equipment collects the LSAs sent by the adjacent systems. The collection of LSAs is referred to an LSDB. The OptiX PTN equipment can obtain the topology of the entire network from the LSDB. The LSDB is the same for the OptiX PTN equipment of the PTN network.
NOTE

2.

The LSA describes the surrounding topology of the OptiX PTN equipment and the LSDB describes the network topology of the entire AS.

3.

According to the LSDB, each OptiX PTN equipment computes a shortest path tree that is rooted at itself by using the shortest path first (SPF) algorithm. The tree defines the routes to each node in the AS.

OSPF Area
The OSPF protocol logically divides the OptiX PTN systems into areas, which are identified by area IDs. Each interface where the OSPF protocol runs must belong to an area. The OptiX PTN equipment supports the OSPF backbone area, which is responsible for interarea routing information. Backbone areas should be interconnected.

OSPF Router Classification

According to the positions in the AS, the OptiX PTN systems can be classified as follows:
l l

Internal router, IR: All interfaces on an internal router belong to one OSPF area. Backbone router: A backbone router must have one interface or more that belong to a backbone area. Hence, all the routers in the backbone areas are backbone routers.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

8-6

OptiX iManager T2000 Operation Guide for PTN NE Management

l

8 Configuring the Control Plane

Autonomous System Border Routers, ASBR: The OptiX PTN equipment that exchanges the routing information with other ASs is referred to as ASBR. An ASBR may not be located at the border of an AS. The OptiX PTN equipment that introduces the external routing information is an ASBR.

OSPF Network Classification

According to the link-layer protocol types, the OSPF classifies networks as follows:
l

Broadcast network: When Ethernet is used as the link-layer protocol, the OSPF considers the network as a broadcast network by default. Point-to-point network: When PPP is used as the link-layer protocol, the OSPF considers the network as a point-to-point network by default.

8.1.3 BGP Protocol

The border gateway protocol (BGP) is the used to discover dynamic routes between autonomous systems (ASs). The earlier three versions of BGP are BGP-1 (defined in RFC 1105), BGP-2 (defined in RFC 1163), and BGP-3 (defined in RFC 1267). The present version of BGP is BGP-4 (defined in RFC1771). BGP-4 (RFC1771) is applied to distributed structures and supports classless inter-domain routing (CIDR).

BGP Overview
The characteristics of BGP are as follows:
l

BGP is an external gateway protocol (EGP). Different from the internal routing protocols (IGPs), such as OSPF and RIP, BGPc focuses on route propagation control and selection of best routes other than discovery and calculation of routes. BGP eliminates routing loop by adding AS path information to BGP routes. BGP enhances its own reliability by using TCP as the transport layer protocol. When routes are updated, BGP only transmits updated routes, which greatly reduces bandwidth occupation by route propagation and can be applied to propagation of a great amount of routing information on the Internet. BGP-4 supports the classless inter-domain routing (CIDR), which is an important improvement to BGP-3. In consideration of management and security, users want to control outgoing and incoming routes of each AS. BGP-4 provides abundant routing policies to flexibly filter and select routes. BGP-4 can be extended easily to support the new development of the network.

l l l

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

8-7

8 Configuring the Control Plane

NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

Autonomous system (AS): An AS is a collection of routers that are under the control of one entity and have the same internal routing policy. Each AS has a unique AS number. The AS number ranges from 1 to 65535. The numbers from 1 to 64511 are registered on Internet and the numbers from 64512 to 65535 are for private networks. An AS refers to an area that consists of the routers that adopt the same routing management policy. An AS is a single entity externally. Each AS runs an IGP to provide the route selection policy. CIDR handles IP addresses in an entirely new way, that is, it does not distinguish networks of Class A, Class B and Class C. For example, an invalid Class C network address 192.213.0.0 (255.255.0.0) can be expressed as 192.213.0.0/16 in CIDR mode, which is a valid super network. Here /16 means that the subnet mask consists of the first 16 bits from the left. The introduction of CIDR simplifies route aggregation. Actually, route aggregation is the process of aggregating several different routes, which turns advertisements of several routes to the advertisement of a single route so as to simplify the routing table.

l l

BGP runs on a router in any of the following two modes:

l l

Internal BGP (IBGP) External BGP (EBGP)

The BGP is called IBGP when it runs in an AS and EBGP when it runs among different ASs.

BGP Message Type

BGP is driven by messages, which include the following types:
l

OPEN: The first message that is sent after the TCP connection is created to create association between BGP peers. UPDATE: The most important information in BGP system used to exchange routing information between peers. It consists of up to three parts, that is, unreachable route, path attributes, and network layer reachable information (NLRI). NOTIFICATION: The message is used to notify errors. KEEPALIVE: The message is used to check connectivity. ROUTE-REFRESH: The message is used to advertise its own route refreshing capability to peers.

l l l

The first four types are defined in RFC1771, while the last one is in RFC2918 (Route Refresh Capability for BGP-4).

BGP Routing Mechanism

On the first startup of the BGP system, the router exchanges routing information with its peers by transmitting the complete BGP routing table. After that only Update messages are exchanged. In the running of the system, keepalive messages are received and transmitted to check the connections between various neighbors. The router that transmits BGP messages is called a BGP speaker, which receives and generates new routing information and advertises the information to the other BGP speakers. When a BGP speaker receives a new route from another AS, it will advertise the route, if the route is better than the currently known route or is a new route, to all the other BGP speakers in the AS. BGP speakers among which messages are exchanged are peers to one another. Multiple related peers compose a peer group. The following policies are used by BGP during route advertisement.
8-8 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

l l l

8 Configuring the Control Plane

If there are multiple routes available, a BGP speaker only selects the optimum one. A BGP only advertises its own route to its peers. A BGP advertises the routes obtained from EBGP to all its BGP peers, including EBGP and IBGP peers. A BGP speaker does not advertise the routes obtained from IBGP to its IBGP peers. Whether a BGP speaker advertises the routes obtained from IBGP to its IBGP peers depends on the synchronization between BGP and IGP. Once the connection is set up, a BGP speaker will advertise all its BGP routes to new peers.

l l

The following policies are used by BGP during route selection.

l l l l l l l l

First discard the routes unreachable to the next hop. First select the routes with the highest local preference. First select the routes rooted from the router itself. First select the routes with the least AS-paths. First select the routes with the lowest origin. First select the routes with the lowest multi-exit discrimination (MED) value. First select the routes learnt from EBGP. First select the routes advertised by the router with the lowest BGP ID.

8.1.4 MPLS-LDP Protocol

The multi-protocol label switch label distribution protocol (MPLS-LDP) is used for the label switched 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-LDP to exchange labels mapping relation.

MPLS-LDP Session
The MPLS-LDP session is used to exchange label mapping and releasing messages between different 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. 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. Session message, which is used to set up, maintain and end the session between MPLSLDP peer entities. Advertisement message, which is used to create, change and delete the label mapping.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8-9

Issue 01 (2009-06-30)

8 Configuring the Control Plane

l

OptiX iManager T2000 Operation Guide for PTN NE Management

Notification message, which is used to provide the constructive message and error notification.

Working Mode of the MPLS-LDP

The label distribution process has two modes. The main difference between the two modes is whether the label mapping is released in the upstream request mode or downstream unsolicited distribution mode. The two label releasing modes are as follows:
l

Upstream request mode, in which the equipment in the upstream sends the label request message to the equipment in the downstream. The equipment in the downstream returns the bound labels to the equipment in the upstream through label mapping message. When the equipment in the downstream returns the label mapping message is determined by the label control mode used by the equipment.

If the ordered mode is used, only when the equipment receives the label mapping message returned by the equipment in the downstream, it sends the label mapping information to the upstream. If the independent mode is used, the equipment immediately sends the label mapping message to the upstream, regardless of whether it receives the label mapping message returned by the equipment in the downstream.

Downstream unsolicited distribution mode, in which the equipment in the downstream take the initiative to release the label mapping message to the equipment in the upstream after the MPLS-LDP session is successfully set up. The equipment in the upstream saves the label mapping information, and manages the received label mapping information according to the route table information.

Basic Operation of the MPLS-LDP

In sequence, the MPLS-LDP operation consists of the following four phases:
l

Development phase: In this phase, the equipment that expects to set up a session periodically sends Hello message to the adjacent equipment to notify the adjacent node of the local peer relation. In this process, the equipment can automatically discover its LDP peer entity without manual configuration. Session set-up and maintenance: After the peer relation is set up, the equipment begins to set up the session. PW set-up and maintenance: The set-up of the PW is based on the MPLS-LDP protocol. Session cancellation: A life state timer is set up for each session. When each LDP PDU is received, this timer is refreshed. If the timer times out before a new LDP PDU is received, the equipment takes that the session is interrupted and the peer relation is invalid. The equipment shuts down the corresponding connection at the transmission layer to end the session.

l l

8.1.5 MPLS-RSVP Protocol

Multi-protocol label switch resource reservation protocol (MPLS-RSVP) supports the distribution of MPLS labels. In addition, when transmitting the label binding message, it carries the resource reservation information, used as a signaling protocol to create, delete or modify the tunnel in the MPLS network.

8-10

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

8 Configuring the Control Plane

Basic Concepts of the MPLS-RSVP

The MPLS-RSVP is a notification mechanism of the resource reservation in the network, which realizes the bandwidth reservation on the control plane. As a label distribution protocol, it is used 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 RSVP session is set up, the receive end determines which reservation style to be used, and thus determines 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 each other. Shared-explicit (SE) style: When this style is used, resources are reserved for all transmit ends in the same session. Thus, transmit ends can share the resources.

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. Resv message: The receive end sends this type of message in the reverse transmission direction of data packets. In addition, the resource reservation is requested, and the reservation state is created and maintained on all the nodes along the trail.

Tunnel Created by Using the MPLS-RSVP

As shown in Figure 8-1, the creation process of the LSP tunnel by using the MPLS-RSVP is listed as follows:
l

The ingress equipment generates the Path message, which is transmitted in the direction of the egress equipment. After the egress equipment receives the Path message, the Resv message is generated and then is returned to the ingress equipment. In addition, the Resv message reserves resources on the equipment along the trail. When the ingress equipment receives the Resv message, the LSP is successfully created. The LSP created by using the MPLS-RSVP has the resource reservation function. The equipment along the trail can distribute some resources to the LSP to ensure the services on the LSP.

Figure 8-1 LSP tunnel created by using the MPLS-RSVP

Ingress
Path Resv Path Resv

Egress

Sender

Receiver

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

8-11

8 Configuring the Control Plane

OptiX iManager T2000 Operation Guide for PTN NE Management

Parameters of the MPLS-RSVP State Timer

The parameters of the MPLS-RSVP state timer include the refreshing period of the Path or Resv message, 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 to the Path message. When the receive end receives the Path message with the LABEL_REQUEST object, 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 object is saved in the RSB of the downstream node. When the message indicating that the number of message refreshing times exceeds the multiple of the PSB or RSB timeout is not continuously received, 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 on some nodes. In some cases, this request is not supposed to be immediately deleted, but it cannot stop other requests from using its reserved resources. In this case, the node enters the blockade state, and the blockade state block (BSB) is generated on the node of the downstream. When the message indicating that the number of the message refreshing times exceeds the multiple of the PSB or RSB timeout is continuously received, the corresponding state in the BSB is deleted.

8.1.6 ARP Protocol

Address resolution protocol (ARP) is used to map the IP address (alias: logical address) at the network layer into the MAC address (alias: physical address) at the data link layer.

ARP Frame Format

Figure 8-2 shows the ARP frame format. Figure 8-2 ARP frame format
Destination MAC address Source MAC address Frame type ARP request/answer

2
IP address at the transmit end

MAC address type

IP MAC protocol addres type s length

IP address length

OP

MAC address at the transmit end

Destination MAC address

Destination IP address

Destination MAC address: six bytes. When an ARP request is sent, the destination MAC address is the broadcast MAC address, that is, 0xFF.FF.FF.FF.FF.FF. Source MAC address: six bytes. Frame type: two bytes. The value of this field is 0x0806.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

l l

8-12

OptiX iManager T2000 Operation Guide for PTN NE Management

l

8 Configuring the Control Plane

MAC address type: two bytes. It defines the address type in the network that runs the ARP. Value 1 indicates the Ethernet address. IP protocol type: two bytes. It defines the protocol type. Value 0x0800 indicates the IP address. MAC address length: one byte. It defines the length of the physical address expressed in bytes. In the case of an ARP request or answer, the value of this field is 6. IP address length: one byte. It defines the length of the logical address expressed in bytes. In the case of an ARP request or answer, the value of this field is 4. OP: two bytes. It defines the ARP packet type. Value 1 indicates the ARP request and value 2 indicates the ARP answer. MAC address at the transmit end: six bytes. It defines the MAC address of the transmit station. IP address at the transmit end: four bytes. It defines the IP address of the transmit station. Destination MAC address: six bytes. It defines the destination MAC address. In the case of an ARP request packet, the value of this field is all-zero. Destination IP address: four bytes. It defines the destination IP address.

l l

Static ARP
Static ARP means that there is a fixed mapping relation between the IP address and the MAC address, and thus you cannot adjust this relation dynamically on the equipment or the router. For the static ARP, you need to manually create a table that is stored on each equipment in the network. The static ARP table is used in the following scenarios:
l

When a packet is transmitted to a destination address beyond the local network segment, this packet is bound with a specific network interface card (NIC) in order to be forwarded through this gateway. To filter out certain illegal IP addresses, you can bind these addresses with an MAC address that does not exist to realize the filtering.

Dynamic ARP
Dynamic ARP means that the mapping relation between the IP address and the MAC address is constantly refreshed and adjusted through address learning. Changing the NIC or moving the host to another network usually changes the physical address. The corresponding MAC address can be obtained in a timely manner based on the dynamic ARP address resolution.

ARP Principle
When a host or other network equipment needs to transmit data to another host or equipment, IP data packets must be encapsulated into frames to be transmitted in the physical network. During the transmission, the destination MAC address must be available. When the equipment on the transmit station wants to obtain the MAC address of another equipment in the network, the transmit station searches for the MAC address corresponding to the IP address in the ARP table. If the ARP table is available, the transmit station obtains the MAC address from the ARP table directly. Otherwise, the ARP function is enabled. As shown in Figure 8-3, host A sends data to host B to obtain the MAC address of host B.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8-13

8 Configuring the Control Plane

OptiX iManager T2000 Operation Guide for PTN NE Management

To obtain the MAC address of the station whose IP address is 10.1.1.2, host A broadcasts an ARP request packet in the network. The packet carries the information about the MAC address and IP address of the transmit station, and the IP address of the destination station. All the equipment in the network receives and handles the ARP request packet. Only host B on the destination station, however, can identify the IP address and return an ARP answer packet. According to the MAC address of the transmit station in the request packet, host B sends the ARP answer packet to the request station in unicast mode. After receiving the ARP answer packet, host A obtains the MAC address of host B. Figure 8-3 ARP address resolution
Host A IP: 10.1.1.1 MAC: A-A-A
Transmit station: A-A-B;10.1.1.2 Destination station: A-A-A;10.1.1.1

Host B IP: 10.1.1.2 MAC: A-A-B

ARP answer packet

ARP request packet

Transmit station: A-A-A;10.1.1.1 Destination station: 10.1.1.2

Host C IP: 10.1.1.3 MAC:A-A-C

Host D IP: 10.1.1.4 MAC:A-A-D

8.2 Configuring the IGP-ISIS Protocol

If the dynamic MPLS tunnel is required, the IGP-ISIS protocol must be configured. The IGPISIS protocol is used to discover the network topology. Through the IGP-ISIS protocol, each NE can obtain the information of the adjacent NE. When the IGP-ISIS protocol is used with the RSVP-TE protocol, the creation of the MPLS tunnel is complete. The IGP-ISIS protocol configuration includes the configuration of node and port attributes, query and configuration of route importing information, and query of the TE link information. 8.2.1 Setting Node Attributes On the T2000, the parameters of nodes managed by the IGP-ISIS protocol can be queried and set. 8.2.2 Setting Port Attributes On the T2000, the parameters of ports managed by the IGP-ISIS protocol can be queried and set. 8.2.3 Configuring Parameters of Route Importing On the T2000, the parameters of route importing can be queried and set.
8-14 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

8 Configuring the Control Plane

8.2.4 Querying the Link TE Information On the T2000, the parameters of the link TE can be queried.

8.2.1 Setting Node Attributes

On the T2000, the parameters of nodes managed by the IGP-ISIS protocol can be queried and set.

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

Setting the Route Color

Set Route Color to divide a large autonomous domain into multiple logical sub-domains. The sub-domains with different Route Color values cannot interconnect through the IS-IS routing protocol. In this manner, the sub-domains are isolated for easy link management and maintenance. The network shown in Figure 8-4 is considered as an example. All the NEs are within the same autonomous domain. The autonomous domain is divided into three logical domains by setting to different colors. Within logical domains 1, 2, and 3, services are available between stations. Services are also available between domain 1 and domain 2, and between domain 1 and domain 3. In domain 1, services are available between NE 1 and NE2, and between NE2 and NE3. Route Color of NE1 is set to 1, 2, and 3, and Route Color of other NEs in domain 1 is set to 1. In domain 2, services are available between NE2 and NE1. Route Color of NE2 is set to 1 and 2, and Route Color of other NEs in domain 2 is 3 set to 1. In domain 3, services are available between NE1 and NE3. Route Color of NE3 is set to 1 and 3, and Route Color of other NEs in domain 3 is set to 3. In this manner, the IS-IS protocol packets are transmitted in each logical domain, between NE1 and NE2, and between NE1 and NE3. Figure 8-4 Example of setting the route color
Route color: 1 Route color: 1, 2, and 3 Domain 1 NE4 NE1 Route color: 1 and 2 Domain 2 NE2

Route color: 1 and 3

Domain 3 NE3

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

8-15

8 Configuring the Control Plane

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration > IGP-ISIS Configuration from the Function Tree. Step 2 Click the Node Configuration tab.
NOTE

Currently, the equipment supports only one IS-IS instance.

Step 3 Click New. Set the parameters of the node in the Create ISIS Protocol Instance dialog box displayed.

NOTE

The Node Level can only be set to Level-1-2. The string of the Area ID should be composed of digits. In addition, the Area ID of nodes in the same domain must be consistent.

Step 4 Optional: Select the ISIS Instance, you can modify the parameter of nodes managed by the IGPISIS protocol.
NOTE

Set Route Color to divide a large autonomous domain into multiple logical sub-domains. The sub-domains with different Route Color values cannot interconnect through the IS-IS routing protocol. In this manner, the sub-domains are isolated for easy link management and maintenance.

Step 5 Click Apply to complete the setting of parameters. Step 6 Click Query to query the parameters of a node. ----End

8.2.2 Setting Port Attributes

On the T2000, the parameters of ports managed by the IGP-ISIS protocol can be queried and set.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. Enable Tunnel of the layer 3 attributes must be set to Enabled.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration > IGP-ISIS Configuration from the Function Tree.
8-16 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

8 Configuring the Control Plane

Step 2 Click the Port Configuration tab. Step 3 Click New. Add ports managed by the ISIS protocol in the Config ISIS Protocol Interface dialog box displayed.

Step 4 Optional: Select the port, you can modify the parameter of ports managed by the IGP-ISIS protocol.

Step 5 Click Apply to complete the setting of port parameters. Step 6 Click Query to query the parameters of each port. ----End

8.2.3 Configuring Parameters of Route Importing

On the T2000, the parameters of route importing can be queried and set.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration > IGP-ISIS Configuration from the Function Tree. Step 2 Click the Route Import tab. Step 3 Click Import to display the Route Import dialog box, and then set parameters of the imported routes.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

8-17

8 Configuring the Control Plane

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 4 Click Apply to complete the setting of parameters of the imported routes. Then, click OK. Step 5 Click Query to query the parameters of the imported routes.

CAUTION
When modifying the parameters of the imported routes, click Delete to delete the original settings, and then click Import to re-set. This operation, however, interrupts the services. Thus, exercise caution when performing this operation. ----End

8.2.4 Querying the Link TE Information

On the T2000, the parameters of the link TE can be queried.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration > IGP-ISIS Configuration from the Function Tree. Step 2 Click the Link TE Information tab. Step 3 Click Query to query the information on the parameters of the link TE. ----End

8.3 Configuring the MPLS-LDP Protocol

If the dynamic PW need be configured, the MPLS-LDP protocol must be configured. The MPLSLDP is used to create the dynamic PW and to distribute the PW label. The NE can only obtain the information of the adjacent NE through the IGP-ISIS protocol. In the case of a single service, the NEs at the two ends can known each other by configuring the MPLS-LDP peer entity of the MPLS-LDP protocol. On the T2000, the MPLS-LDP peer entities can be created and the MPLSLDP protocol can be configured. 8.3.1 Creating MPLS-LDP Peer Entities On the T2000, the LDP peer entities can be created. Thus, the MPLS-LDP session is available between NEs, and the NEs can obtain the label mapping messages of each other.
8-18 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

8 Configuring the Control Plane

8.3.2 Configuring the MPLS-LDP Protocol On the T2000, the parameters of the MPLS-LDP protocol can be set.

8.3.1 Creating MPLS-LDP Peer Entities

On the T2000, the LDP peer entities can be created. Thus, the MPLS-LDP session is available between NEs, and the NEs can obtain the label mapping messages of each other.

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

Context
For the local session and remote session, you only need to create bidirectional LDP peers between the source equipment and sink equipment. That is, you need to create peers from the source to the sink, and from the sink to source.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration > MPLS-LDP Configuration from the Function Tree. Step 2 Click Create to display the Create LDP Peer Entity dialog box. Step 3 For the Local LSR ID and Opposite LSR ID fields, enter LSR ID of the opposite NE. Then, click Apply. Step 4 After the setting is complete, click OK.

Step 5 Click Query to query the parameters of the MPLS-LDP peer entities.
NOTE

Click Delete to delete the MPLS-LDP peer entities.

----End

8.3.2 Configuring the MPLS-LDP Protocol

On the T2000, the parameters of the MPLS-LDP protocol can be set.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration > MPLS-LDP Configuration from the Function Tree.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8-19

8 Configuring the Control Plane

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 2 Set the parameters of the MPLS-LDP protocol. Step 3 Click Apply to complete the setting of the parameters of the MPLS-LDP protocol. Step 4 Click Query to query the parameters of the MPLS-LDP protocol. ----End

8.4 Configuring the MPLS-RSVP Protocol

The MPLS-RSVP protocol is used to create dynamic MPLS tunnel and to distribute the tunnel label. On the T2000, the parameters of the MPLS-RSVP protocol can be queried. This protocol does not need special configuration, and thus the user can configure each parameter according to requirements.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration > MPLS-RSVP Configuration from the Function Tree. Step 2 Set the parameters of the MPLS-RSVP protocol. Step 3 Click Apply to complete the setting of the parameters of the MPLS-RSVP protocol. Step 4 Click Query to query the parameters of the MPLS-RSVP protocol. ----End

8.5 Configuring the OSPF Protocol

On the network, the OSPF protocol transfers the link state information and computes routes to obtain the routing information according to the link state information. Through the OSPF protocol, each NE can obtain the information of the adjacent NE. When the OSPF protocol is used with the RSVP-TE protocol, the creation of the MPLS tunnel is complete. The OSPF protocol configuration includes the configuration of node and port attributes, query and configuration of route importing information, and query of the TE link information. 8.5.1 Setting Node Attributes On the T2000, the OSPF Instance can be added. 8.5.2 Setting Port Attributes On the T2000, the parameters of ports managed by the OSPF protocol can be queried and set. 8.5.3 Configuring Parameters of Route Importing On the T2000, the parameters of route importing can be queried and set. 8.5.4 Querying the Link TE Information On the T2000, the parameters of the link TE can be queried.
8-20 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

8 Configuring the Control Plane

8.5.1 Setting Node Attributes

On the T2000, the OSPF Instance can be added.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration > IGP-OSPF Configuration from the Function Tree. Step 2 Click the Node Configuration tab. Step 3 Click New. Set the parameters of the node in the Create IGP-OSPF Protocol Instance dialog box displayed.

Step 4 Click OK. ----End

8.5.2 Setting Port Attributes

On the T2000, the parameters of ports managed by the OSPF protocol can be queried and set.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. Enable Tunnel of the layer 3 attributes must be set to Enabled.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration > IGP-OSPF Configuration from the Function Tree. Step 2 Click the Port Configuration tab. Step 3 Click New. Add ports managed by the OSPF protocol in the Config IGP-OSPF Protocol Interface dialog box displayed.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

8-21

8 Configuring the Control Plane

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

The OSPF protocol port can be an Ethernet interface, Ethernet virtual interface, or MP group.

Step 4 Click OK. ----End

8.5.3 Configuring Parameters of Route Importing

On the T2000, the parameters of route importing can be queried and set.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration > IGP-OSPF Configuration from the Function Tree. Step 2 Click the Route Import tab. Step 3 Click Import to display the Route Import dialog box, and then set parameters of the imported routes.

Step 4 Click Apply to complete the setting of parameters of the imported routes. Then, click OK. Step 5 Click Query to query the parameters of the imported routes.

8-22

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

8 Configuring the Control Plane

CAUTION
When modifying the parameters of the imported routes, click Delete to delete the original settings, and then click Import to re-set. This operation, however, interrupts the services. Thus, exercise caution when performing this operation. ----End

8.5.4 Querying the Link TE Information

On the T2000, the parameters of the link TE can be queried.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration > IGP-OSPF Configuration from the Function Tree. Step 2 Click the Link TE Information tab. Step 3 Click Query to query the information on the parameters of the link TE. ----End

8.6 Configuring the MP-BGP

MP-BGP means that the BGP runs in the interior of the autonomous system. In an L3VPN, route switching between the PE equipment is realized through the MP-BGP.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration > MP-BGP Configuration from the Function Tree. Step 2 Click the MP-BGP Configuration tab. Click New and the Create MP-BGP Protocol Instance dialog box is displayed. Step 3 Set MP-BGP Protocol Instance and AS Number. Step 4 Click OK and the Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click the Peer Configuration tab. Click New, and the Create Peer dialog box is displayed.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 8-23

8 Configuring the Control Plane

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 6 Configure the peer of the MP-BGP protocol instance. You can select the MP-BGP Protocol Instance that is already configured, and set the Remote IP Address and the Remote AS Number that corresponds to the MP-BGP protocol instance. Step 7 Click OK and the Operation Result dialog box is displayed indicating that the operation is successful. ----End

8.7 Configuring Static Routes

The static routes are selected according to the preset route options in the network. On the T2000, the static routes can be queried and created.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. You must complete the setting of the basic attributes and Layer 3 attributes of the port.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration > Static Route Management from the Function Tree. Step 2 Click Create to create the static routes, and then click Apply.

NOTE

l l l l

When selecting boards or ports, select those that have Layer 3 attributes. When the static route is configured, the port IP address and the next hop IP address must be in the same network section. When the last digit of the IP address of the destination is not 0, the subnet mask is 255.255.255.255. For example, if the IP address is 193.168.3.2, the mask of the destination node is 255.255.255.255. When the last digit of the IP address of the destination is 0, the subnet mask is 255.255.255.0 or 255.255.255.255. For example, if the IP address is 193.168.3.0, the mask of the destination node is 255.255.255.255 or 255.255.255.0.

Step 3 After the setting is complete, click OK. Step 4 Click Query to query the parameters of the static routes.
NOTE

Click Delete to delete the original static routes.

----End
8-24 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

8 Configuring the Control Plane

8.8 Configuring the Address Parse

On the T2000, the IP address and MAC address of the ARP table items can be created and queried.

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

Procedure
Step 1 In the NE Explorer, click the NE, and choose Configuration > Control Plane Configuration > Address Parse from the Function Tree. Step 2 Click Create and the Add Address Parse dialogue box is displayed.

Step 3 Set the IP address and MAC address of the ARP table items separately, and then click Apply.

CAUTION
When configuring the MAC address of the ARP table items, the first digit of the address must be of an even number. Step 4 After the setting is complete, click OK.

WARNING
The configuration of the address resolution refers to the creation of the static ARP table items. To delete the dynamic ARP table items, click Clear. This operation, however, clears all the contents in the ARP table items, and interrupts the services. Thus, exercise caution when performing this operation.
NOTE

Click Delete to delete the contents of the ARP table items.

----End

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

8-25

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

9
About This Chapter

Configuring the QoS Policy

For service of different types, configure different QoS policies to provide different QoS, and to ensure availability of important services in the case of network congestion. 9.1 Overview of the QoS The overview of the QoS describes in terms of the purposes, compliant standards and suggestions. 9.2 Basic Concepts Before configuring the quality of service (QoS) policy, familiar yourself with the basic concepts related to the QoS, and the QoS polices supported by the PTN equipment. 9.3 Application of the QoS The application of the QoS describes the tunnel-based QoS control and application of several QoS policies. The QoS policies include the port policy, V-UNI ingress policy, V-UNI egress policy, PW policy, QinQ policy and ATM policy. In addition, the QoS policies include the WFQ scheduling policy and WRED policy. 9.4 QoS Configuration Flow The QoS configuration is classified into the QoS configuration for the DiffServ domain and the QoS configuration for ATM services. This section describes the flow for the two types of QoS configuration. 9.5 Configuring the DiffServ Domain As a node in the DiffServ domain, the PTN equipment can perform QoS control over the service traffic. For this purpose, first configure a DiffServ domain for the equipment. 9.6 Configuring the Port Policy The port policy should be configured to realize the QoS control over ports. 9.7 Configuring the V-UNI Ingress Policy Configure the V-UNI ingress policy at the access side of the euqipment to perform the QoS control over the ingress traffic. 9.8 Configuring the V-UNI Egress Policy Configure the V-UNI egress policy at the access side of the equipment to perform the QoS control over the egress traffic. 9.9 Configuring the PW Policy
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9-1

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

Configure the PW policy at the network side to perform the QoS control over the ingress and egress traffic carried by the PW. 9.10 Configuring the QinQ Policy Configure the QinQ policy at the network side to perform the QoS control over traffic carried by the QinQ link. 9.11 Configuring the ATM CoS Mapping Configure the mapping relation between the ATM service type and PHB service class to ensure the end-to-end QoS for ATM services. 9.12 Configuring the ATM Policy For ATM services, configure the ATM policy to perform the QoS control over the traffic. 9.13 Applying a QoS Policy If the same QoS policy has to be applied for multiple NEs (for example, the V-UNI Ingress policy), it is easier to adopt the QoS policy application mode. In this mode, you only need to create the QoS policy on one NE and then you can apply the QoS policy to other NEs. 9.14 QoS Configuration Case of the ATM Service Configure the ATM policy and use the ATM policy on specified ATM service. In this way, the QoS for the ATM service is ensured. In addition, the tunnel QoS can be configured to control the tunnel bandwidth of the carried service flow. 9.15 QoS Configuration Case of the Ethernet Service Configure the hierarchical QoS policy and use it for a specified Ethernet service. In this way, the QoS for the service is ensured.

9-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

9.1 Overview of the QoS

The overview of the QoS describes in terms of the purposes, compliant standards and suggestions.

Purpose of the QoS

Quality of service (QoS) indicates the performance of the data flow that travels through the network. The purpose of the QoS is to ensure the end-to-end service quality. The QoS cannot increase the bandwidth, but can reduce the delay and jitter in the network to the minimum by reasonably allocating and monitoring network resources. In this way, the quality of important services is ensured. The specifications used to measure the QoS are as follows.
l l

Service availability, which indicates the ensured normal running time of a service. Delay, which indicates the period between transmission and receiving of data packets between two reference points. Jitter, which indicates the time interval difference for the receive side to receive a group of data packets transmitted on the same route. Throughout, which indicates the rate at which data packets are transmitted in the network. The rate can be expressed as the mean rate or peak rate. Packet loss rate, which indicates the maximum ratio of discarded data packets among the transmitted data packets in the network. Data packets are discarded mainly due to network congestion.

Compliant Standards and Protocols

RFC1349 Type of Service in the Internet Protocol Suite RFC2474 Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers RFC2475 An Architecture for Differentiated Services RFC2597 Assured Forwarding PHB Group RFC2598 An Expedited Forwarding PHB RFC2698 A Two Rate Three Color Marker RFC3086 Definition of Differentiated Services Per Domain Behaviors and Rules for their Specification RFC3140 Per Hop Behavior Identification Codes RFC3246 An Expedited Forwarding PHB (Per-Hop Behavior) RFC3247 Supplemental Information for the New Definition of the EF PHB (Expedited Forwarding Per-Hop Behavior) RFC3248 A Delay Bound alternative revision of RFC 2598 RFC3260 New Terminology and Clarifications for Diffserv RFC3270 Multi-Protocol Label Switching (MPLS) Support of Differentiated Services
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9-3

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

RFC3289 Management Information Base for the Differentiated Services Architecture RFC3290 An Informal Management Model for Diffserv Routers RFC3317 Differentiated Services Quality of Service Policy Information Base The ATM Forum Traffic Management Specification Version 4.1

9.2 Basic Concepts

Before configuring the quality of service (QoS) policy, familiar yourself with the basic concepts related to the QoS, and the QoS polices supported by the PTN equipment. 9.2.1 DiffServ As an end-to-end QoS control model, the DiffServ can be simply realized and easily extended. 9.2.2 HQoS When used as an edge DS node, the PTN equipment supports hierarchical QoS (HQoS).

9.2.1 DiffServ
As an end-to-end QoS control model, the DiffServ can be simply realized and easily extended. Figure 9-1 shows the application of the DiffServ model. Figure 9-1 Networking diagram for the DiffServ model
DS node DS domain Non-DS node DS node DS node Non-DS node

The DS (DiffServ) domain consists of a group of network nodes (DS nodes) that provide the same service policy and realize the same PHB (per-hop behavior). The DS nodes are classified into edge DS nodes and internal DS nodes. The edge DS nodes classify the traffic that enters the DS domain. For the service traffic of different types, different PHB service levels are marked. The internal DS nodes control the flow according to the PHB service level. As a node in the DS domain, the PTN equipment uses the following technologies to realize the end-to-end QoS control.

Flow Classification
The PTN equipment supports two flow classifying schemes, that is, simple flow classification and complex flow classification.
l

Simple flow classification

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

9-4

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

The priorities of the accessed packets are mapped into the specified PHB service level. In this way, when crossing the DS domain, these packets can be provided with a uniform PHB service. The simple flow classification is mainly used for the internal nodes in a DS domain. The flow classifying rules of all nodes in a DS domain should be the same. The PTN equipment can access Ethernet, IP and MPLS packets, and supports the mutual mapping between the VLAN priority, IP DSCP, MPLS EXP and the PHB service level.
l

Complex flow classification The complex flow classification is mainly used for the edge nodes in a DS domain. The PTN equipment can perform the complex flow classification for Ethernet and IP packets, and thus provides more specific and more flexible flow classification for the user.

CAR Control
Committed access rate (CAR) is used at the access side of the PTN equipment to perform dualrate three-color management for the accessed traffic. In normal cases, when the traffic is lower than the committed information rate (CIR), packets are marked green and normally pass. When the traffic is higher than the CIR and lower than the peak information rate (PIR), the packets that exceed the CIR are marked yellow and normally pass. When the traffic exceeds the PIR, the packets that exceed the PIR are marked red and are directly discarded. The PTN equipment supports two colorizing modes, that is, color-blind and color-aware. The difference between the two modes lies in that the current colors of packets should be considered in the case of the color-aware mode. The PTN equipment supports the configuration of processing methods for packets with different colors. The PTN equipment supports two colorizing modes, that is, color-blind and color-aware. The difference between the two modes lies in that the current colors of packets should be considered in the case of the color-aware mode. The PTN equipment supports the configuration of processing methods for packets with different colors.
NOTE

In the case of OptiX PTN 910&950, the color-aware mode is not supported.

Congestion Management
When network congestion occurs or aggregates, specific packet discarding policies are used to ensure the QoS of services of higher priorities. Three common packet discarding policies are available.
l

Tail drop policy When the queue is full, packets that arrive latterly are discarded. Random early detection (RED) policy In the case of the RED policy, when the queue reaches a certain length, packets are randomly discarded. In this way, overall synchronization caused by the TCP slow-start mechanism is prevented.

Weighted random early detection (WRED) policy In the case of the WRED, the queue length and priorities of packets (color) should be considered for packet discarding. The user can make the configuration that packets of higher

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

9-5

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

discarding priorities, such as red packets and yellow packets, are discarded first, and these packets are more likely to be discarded. The PTN equipment supports the tail drop policy and the WRED policy. In addition, it supports the configuration of discarding starting point and discarding rate of the WRED.
NOTE

In the case of OptiX PTN 910&950, the tail drop policy is not supported.

Queue Scheduling
In the case of congestion, the PTN equipment provides the ensured QoS for services at the higher service level by using different queue scheduling schemes. The PTN uses two queue scheduling schemes, that is, priority queuing (PQ) and weighted fair queuing (WFQ). Table 9-1 lists the features and application of the two queue scheduling schemes. Table 9-1 Scheduling and application Schedu ling Mode PQ Basic Concept Scheduling Feature PTN Application

The PQ is a strict priority queue scheduling scheme. In the case of the PQ, packets in queues are scheduled strictly according to the queue priority. Only when the queues of higher priorities are empty, packets in queues of lower priorities are transmitted. In the case of the WFQ, queues are scheduled according to the weight allocated to each queue. Generally, more weights and bandwidth are allocated to queues of higher priorities, and less weights and bandwidth are allocated to queues of lower priorities.

This queue scheduling scheme ensures low delay for forwarding packets in queues of higher priorities. Packets in queues of lower priorities, however, may not be processed.

For queues of highest priorities, which carry CS7, CS6 or EF packets, use the PQ scheme to schedule queues.

WFQ

This scheduling scheme not only ensures low delay for forwarding packets in queues of higher priorities, but also ensures that packets in queues of lower priorities are effectively processed.

For queues of higher priorities, which carry AF4, AF3, AF2 and AF1 packets, use the WFQ scheme to schedule queues.

NOTE

For queues of the lowest priorities, which carry BE packets, the QoS is not ensured. In the case of congestion, the PTN equipment does not schedule queues that provide this service level (BE).

9.2.2 HQoS
When used as an edge DS node, the PTN equipment supports hierarchical QoS (HQoS).
9-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

To increase the QoS control efficiency in the network, the HQoS control is always realized at edge nodes in the network and only simple QoS processing is performed at internal nodes in the network. As an edge DS node, the PTN equipment provides multi-layer QoS function points to realize the HQoS control function. Compared with the traditional QoS, the HQoS provided by the PTN equipment has the following advantages.
l

The hierarchical scheduling mechanism is used to realize the scheduling based on port, service, PW or QinQ link. In this way, the QoS control granularities are further divided. The hierarchical flow control mechanism is used to control the traffic based on port, service, PW or QinQ link. In this way, the service QoS can be fully controlled. The WFQ and WRED policies can be configured to increase the flexibility of the QoS control.

Figure 9-2 shows where the HQoS function points are and how the QoS processing is performed. Figure 9-2 HQoS function points and corresponding QoS processing
Access side QoS function point Network side

Port

V-UNI

PW/QinQ

Tunnel

Port

QoS management

Apply port policy

Apply V-UNI ingrees policy Apply V-UNI egrees policy

Control V-UNI group bandwidth

Apply PW policy / Control PW bandwidth Apply QinQ policy

Control tunnel bandwidth

Apply port policy

Service flow

9.3 Application of the QoS

The application of the QoS describes the tunnel-based QoS control and application of several QoS policies. The QoS policies include the port policy, V-UNI ingress policy, V-UNI egress policy, PW policy, QinQ policy and ATM policy. In addition, the QoS policies include the WFQ scheduling policy and WRED policy. 9.3.1 Tunnel-Based QoS The PTN equipment can use the tunnel-based QoS control to limit the tunnel bandwidth. 9.3.2 QoS Policy
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9-7

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

For the PTN equipment, the configurable QoS policies include the port policy, V-UNI ingress policy, V-UNI egress policy, PW policy, QinQ policy and ATM policy. In addition, the QoS policies include the WFQ scheduling policy, WRED policy. In addition, the QoS policies include the CAR policy, WRED policy. This section briefly describes how the QoS policy is applied.

9.3.1 Tunnel-Based QoS

The PTN equipment can use the tunnel-based QoS control to limit the tunnel bandwidth. At the ingress or egress of a network, the PTN equipment supports the pseudo wire emulation edge-to-edge (PWE3) function. Different services are adapted to different PWs, and then the PWs are transmitted in the Tunnel. One tunnel can carry the PWs of the same destination. The PTN equipment supports the control over the tunnel bandwidth. The overall bandwidth of PWs in one tunnel should not exceed the allowed bandwidth of this tunnel. The tunnel bandwidth is configured during configuration of the tunnel. For details on how to configure the tunnel bandwidth, see 13 Configuring an MPLS Tunnel.

9.3.2 QoS Policy

For the PTN equipment, the configurable QoS policies include the port policy, V-UNI ingress policy, V-UNI egress policy, PW policy, QinQ policy and ATM policy. In addition, the QoS policies include the WFQ scheduling policy, WRED policy. In addition, the QoS policies include the CAR policy, WRED policy. This section briefly describes how the QoS policy is applied. First the PTN equipment establishes the mapping relation between the service priority and PHB forwarding type. The OptiX PTN 3900 and OptiX PTN 1900 can access Ethernet, IP and MPLS packets. In the ingress direction of a port, the priorities of these packets are mapped to the standard PHB forwarding service type. In the egress direction of a port, the standard PHB forwarding service type is mapped to the priorities of these packets. The OptiX PTN 912 can access Ethernet and MPLS packets. In the ingress direction of a port, the priorities of these packets are mapped to the BA (Behavior Aggregate). Then the PTN equipment can use the following QoS polices to realize the end-to-end QoS control.
l

Establish the port QoS policy. In the ingress direction, the port policy is used to filter the traffic at the ingress port according to the ACL rule. The ingress port only receives or discards the traffic that matches with the ACL rule. In the egress direction, the usable port QoS policy is the traffic control for different PHB forwarding types.

Establish the V-UNI ingress policy. The V-UNI ingress policy is used to control the traffic based on services respectively in the ingress directions.

Establish the V-UNI egress policy. The V-UNI egress policy is used to control the traffic based on services respectively in the egress directions.

Establish the pseudo wire (PW) policy.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

9-8

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

The PW policy is used to control the PW traffic in the ingress direction. The equipment does not support the QoS control over the PW traffic in the egress direction.
l

Establish the QinQ policy. The QinQ policy is used to control the QinQ traffic in the ingress direction. Establish the ATM policy. The ATM policy is used to control the ATM traffic. Establish the weighted fair queuing (WFQ) scheduling policy. In the case of the OptiX PTN 3900 and OptiX PTN 1900, the WFQ scheduling policy is provided for different QoS control policies.

Establish the weighted random early detection (WRED) policy.

Table 9-2 Table for mapping relations between the PTN equipment and the supported QoS policies Port Policy V-UNI Ingres s Policy Support ed Support ed Support ed Support ed Support ed V-UNI Egress Policy Suppor ted Suppor ted Not support ed Not support ed Not support ed PW Policy QINQ Policy ATM Policy WFQ Sched uling Policy Support ed Support ed Support ed Support ed Support ed WRED Policy

PTN 3900 PTN 1900 PTN 912 PTN 910 PTN 950

Support ed Support ed Support ed Support ed Support ed

Support ed Support ed Not support ed Not support ed Not support ed

Support ed Support ed Not support ed Not support ed Not support ed

Suppor ted Suppor ted Suppor ted Suppor ted Suppor ted

Support ed Support ed Not support ed Support ed Support ed

9.4 QoS Configuration Flow

The QoS configuration is classified into the QoS configuration for the DiffServ domain and the QoS configuration for ATM services. This section describes the flow for the two types of QoS configuration.

QoS Configuration Flow for the DiffServ Domain

The QoS configuration flow for the PTN equipment used as an edge node is different from that for the PTN equipment used as an internal node. When the PTN equipment is used as an edge node in the DiffServ domain, the QoS configuration flow is as shown in Figure 9-3.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9-9

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 9-3 QoS configuration flow for the edge node in the DiffServ domain
Required Optional PTN 912 could not support Configure DiffServ domain Start

Configure WFQ policy

Configure service WRED policy

Configure port policy

Configure VUNI ingress policy

Configure VUNI egress policy

Configure PW policy

Configure QinQ policy

Configure tunnel bandwidth

Apply port policy

Apply V-UNI ingress/egress policy

Configure V-UNI group bandwidth

Apply PW/QinQ policy

End

When the PTN equipment is used as an internal node in the DiffServ domain, the QoS configuration flow is as shown in Figure 9-4.

9-10

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

Figure 9-4 QoS configuration flow for the internal node in the DiffServ domain

Required Optional PTN 912 could not support

Start

Configure DiffServ domain

Configure tunnel bandwidth

Configure and apply port policy

End

QoS Configuration Flow for ATM Services

Figure 9-5 shows the QoS configuration flow for ATM services. Figure 9-5 QoS configuration flow for ATM services
Required Optional

Start

PTN 912 could not support

Configure tunnel bandwidth

Configure and apply ATM policy

Configure PW bandwidth

End

9.5 Configuring the DiffServ Domain

As a node in the DiffServ domain, the PTN equipment can perform QoS control over the service traffic. For this purpose, first configure a DiffServ domain for the equipment. 9.5.1 Creating a DiffServ Domain To create a DiffServ domain, create mapping relations in the DiffServ domain, and configure ports that use the mapping relations.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9-11

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

9.5.2 Modifying a DiffServ Domain The PTN equipment supports modifying parameters of a created DiffServ domain. 9.5.3 Deleting a DiffServ Domain A DiffServ domain not used can be deleted.

9.5.1 Creating a DiffServ Domain

To create a DiffServ domain, create mapping relations in the DiffServ domain, and configure ports that use the mapping relations.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. You must complete the configuration of the control plane on the PTN equipment.

Context
As a node in the DiffServ domain, the PTN equipment supports creating the DiffServ domain according to the physical ports. Each PTN NE supports a maximum of eight DiffServ domains. By default, there is a DiffServ domain for the PTN equipment. Before any DiffServ domain is created, all ports belong to this default domain. To create a DiffServ domain, perform the following operations.
l

Create mapping relations in the DiffServ domain, which include the mapping relation between the priorities of user packets in both the ingress and egress directions, and the PHB service levels. Configure the physical ports that use the mapping relations, that is, add the physical ports to this domain.

Table 9-3 lists the service quality that corresponds to the PHB service level. Table 9-3 PHB service level and mapping PHB service quality PHB Service Level BE PHB Service Quality The focus is on the reachability. The quality of forwarding services is not required. BE is the default PHB service level. All DS nodes should support the BE PHB. The service traffic is allowed to exceed the specified range. For the traffic within the specified range, forwarding quality is ensured. For the traffic beyond the specified range, the forwarding quality is lowered and such traffic is not simply discarded. This PHB service level is applicable for transmission of multimedia services. Each AF level is further divided into three discarding priorities (color). For example, the AF1 level is further divided into the following discarding priorities. l AF11, green priority. Traffic with this priority can normally pass.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

AF1 AF2 AF3

9-12

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

PHB Service Level AF4

PHB Service Quality

l l

AF12, yellow priority. Packets with this priority are discarded in the case of congestion according to requirements. AF13, red priority. Packets with this priority are discarded first.

EF CS6 CS7

On any conditions, traffic sent by any DS node should be at the specified rate or higher. The forwarding effect in a virtual lease line is then simulated. In this way, the forwarding service of low packet loss ratio, low delay and high bandwidth is provided. This PHB service level is applicable to video services and VoIP services.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > DiffServ Domain Management from the Function Tree. Step 2 Click Create. The Create DS Mapping Relation dialog box is displayed. Set the following parameters in the dialog box.
l l

ID and name of the DS domain mapping relation, and mapping packet type. Mapping relation between priorities of ingress and egress packets, and the PHB service level. (When no configuration is performed, the mapping relation recommended by the system is used.)
NOTE

By default, the equipment performs the mapping according to CVLAN, If the mapping according to DEISVLAN is required, enable SVLAN DEI in the SVLAN DEI Used Flag tab.
NOTE

OptiX PTN 3900 and 1900: By default, the equipment performs the mapping according to CVLAN, If the mapping according to DEISVLAN is required, enable SVLAN DEI in the SVLAN DEI Used Flag tab.
NOTE

Regarding the DSCP priority, if the DSCP value is not within the range specified in the Ingress Mapping Relation table, the PHB service level is BE.
l

Ports that use the mapping relation.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

9-13

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

After the mode of an Ethernet port is modified, the Ethernet port is resumed to the default DiffServ domain. The services at the Ethernet port are mapped according to the relation of the default C-VLAN type and PHB service level.
NOTE

OptiX PTN 3900 and 1900: After the mode of an Ethernet port is modified, the Ethernet port is resumed to the default DiffServ domain. The services at the Ethernet port are mapped according to the relation of the default C-VLAN type and PHB service level.

Step 3 Click OK. ----End

9.5.2 Modifying a DiffServ Domain

The PTN equipment supports modifying parameters of a created DiffServ domain.

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

Context
The default DiffServ cannot be modified or deleted.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > DiffServ Domain Management from the Function Tree. Step 2 Select the DiffServ domain to be modified. For a DiffServ domain, the following parameters can be modified.
l l l l

Modify the name of the domain mapping relation, and then click Apply. In the Ingress Mapping Relation tab, modify the mapping relation, and then click Apply. In the Egress Mapping Relation tab, modify the mapping relation, and then click Apply. In the Apply Port tab, click Modify. In the displayed Config Ports dialog box, modify the applied port. Then, click OK.

----End
9-14 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

9.5.3 Deleting a DiffServ Domain

A DiffServ domain not used can be deleted.

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

Context
l

To delete a DiffServ domain, first delete the ports involved in the DiffServ domain, and then delete the mapping relations in the DiffServ domain. If the DiffServ domain contains any port, the mapping relations cannot be successfully deleted. The default DiffServ cannot be deleted.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > DiffServ Domain Management from the Function Tree. Step 2 Select the DiffServ domain to be deleted. Click Modify in the Apply Port tab. The Config Ports dialog box is displayed. Step 3 All ports chosen in this domain are deleted. Click OK. Step 4 Click Delete in the Ingress Mapping Relation tab. The Confirm dialog box is displayed, Click OK. ----End

9.6 Configuring the Port Policy

The port policy should be configured to realize the QoS control over ports. 9.6.1 Creating the Port WRED Policy The port-based WRED policy can be created, which includes the discarding threshold and discarding ratio for packets of different colors. 9.6.2 Creating the Port Policy The traffic at the port can be controlled by configuring the port policy. 9.6.3 Modifying the Port Policy The created port policy can be modified. The port policy name, CAR parameter for different CoS, and packet discarding parameter can be modified. 9.6.4 Deleting the Port Policy Delete the port policy not required. If used by a port, this policy cannot be deleted.

9.6.1 Creating the Port WRED Policy

The port-based WRED policy can be created, which includes the discarding threshold and discarding ratio for packets of different colors.

Prerequisite
You must be an NM user with "NE operator" authority or higher.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9-15

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

The OptiX PTN 910 and OptiX PTN 950 support the function of creating a port WRED policy. The OptiX 1900 and OptiX 3900, however, support the default port WRED policies only. For details of the parameters for the default port WRED policies, see Table 1 in 9.6.2 Creating the Port Policy.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the Port WRED Policy tab. Click New. The Create Port WRED Policy dialog box is displayed. Set the following parameters in the dialog box.
l l

Policy ID and name. Discarding policy for green, yellow and red packets. The policy includes the lower threshold for discarding, higher threshold for discarding, and discarding policy.

Step 3 Click OK. ----End

9.6.2 Creating the Port Policy

The traffic at the port can be controlled by configuring the port policy.

Prerequisite
l

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

NOTE

When a physical port is configured with both the port policy and UNI ingress policy, only the UNI ingress policy functions. Configuring one physical port with both the port policy and UNI ingress policy is not recommended.

Context
In the case of OptiX PTN 1900 and OptiX PTN 3900, to configure the port policy, perform the following operations.
9-16 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

l

9 Configuring the QoS Policy

Configure the port ACL rule. Ports only access the service traffic that matches with the ACL rule. Configure the parameters for different CoS. Specify the packet discarding policy to provide different QoS for different CoS.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the Port Policy tab. Click New in the tab. The Create Port Policy dialog box is displayed. Set the following parameters in the dialog box.
l

Policy ID , Policy Name, WFQ Schedule Policy, CoS parameters and packet discarding parameter.
NOTE

l l

In the case of the OptiX PTN 912/910/950, the port policy can be associated with the WFQ scheduling policy. In the case of the OptiX PTN 912, the parameter for different CoS cannot be set and the packet discarding policy cannot be specified.

In the case of OptiX PTN 3900 and OptiX PTN 1900, only the default Port WRED Policy can be used.
NOTE

When Bandwidth Limit is set to Enable, you can set Tail Drop Threshold or Port WRED Policy. Adopt the default template for Port WRED Policy. For the parameters in different templates, see Table 9-4.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

9-17

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

Table 9-4 Default threshold for the port WRED policy Packet Color Green Yellow Red Lower Threshold Port buffer size * (3/6) Port buffer size * (2/6) Port buffer size * (1/6) Higher Threshold Port buffer size Port buffer size * (5/6) Port buffer size * (4/6) Discard Rate 100 100 100

For the port buffer size of each board, see Table 9-5 and Table 9-6. Table 9-5 Port buffer size of each board for the OptiX PTN 3900 PHB Service Level Port Buffer Size (256 Bytes) EX2 12800 12800 12800 25600 25600 25600 25600 51200 EG16/POD41/ EFG2 1280 1280 1280 2560 2560 2560 2560 5120 EFF8 320 320 320 640 640 640 640 1280 ETFC 160 160 160 320 320 320 320 640

CS7 CS6 EF AF4 AF3 AF2 AF1 BE

Table 9-6 Port buffer size of each board for the OptiX PTN 1900 PHB Service Leve Port Buffer Size (256 Bytes) POD41/EFG2 EF AF3 AF2 BE 2304 4608 4608 9216 EFF8 576 1152 1152 2304 ETFC 288 576 576 1152

If the ACL filter is required for the accessed traffic, click New. In the Create Traffic Classification dialog box, configure the following attributes:

Traffic Classification ID
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

9-18

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

ACL Action Click Add, configure the traffic classification rule

Click OK.

NOTE

The OptiX PTN 3900 and OptiX PTN 1900 support traffic classification at a port and support the function of setting ACL for the port.

Step 3 In the Create Port Policy dialog box, click OK. Step 4 Select the port policy created. Click the Applied Object tab, and then click Modify. Step 5 In the displayed Configure Port dialog box, select the port to be applied, and then click OK.
NOTE

The OptiX PTN 912/910/950 supports the port policy at the ML-PPP port.

----End

Related Operation
Use the copy function to fast create a new port policy based on the created port policy. The detailed operation is as follows: 1. 2. In the Port Policy tab, click Copy. In the displayed Duplicate QoS Policy dialog box, select the policy to be copied, and then enter the new policy name. Then, click OK. Modify the related parameters of the newly created policy, and then make the new policy meet the QoS requirement.
NOTE

l l

For the method of modifying the port policy, see 9.6.3 Modifying the Port Policy. In the case of the copy function, the application policy of port can not be copied.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

9-19

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

9.6.3 Modifying the Port Policy

The created port policy can be modified. The port policy name, CAR parameter for different CoS, and packet discarding parameter can be modified.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The policy is not applied.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the Port Policy tab. In the tab, select the port policy to be modified. The following parameters can be modified.
l l l

Policy name. Parameters of traffic classification bandwidth sharing. CoS parameters. In the CoS Configuration tab, modify the traffic control parameters and packet discarding policy, and then click Apply.

Traffic classification rule. Click the Traffic Classification Configuration tab.

Select the traffic classification rule to be modified, and then click Traffic Classification Rule. In the Traffic Classification Configuration dialog box, modify the traffic classification rule, and then click OK. Click New. In the displayed Create Traffic Classification dialog box, configure the new ACL rule, and then click OK. Select the traffic classification rule to be deleted, and then click Delete. Click Applied Object tab, and then click Modify. In the displayed Configure Port dialog box, modify the applied port, and then click OK.

Applied port.

----End

9.6.4 Deleting the Port Policy

Delete the port policy not required. If used by a port, this policy cannot be deleted.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The policy to be deleted is not used.

9-20

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the Port Policy tab. In the tab, select the port policy to be deleted. Step 3 Click Delete. ----End

9.7 Configuring the V-UNI Ingress Policy

Configure the V-UNI ingress policy at the access side of the euqipment to perform the QoS control over the ingress traffic. 9.7.1 Creating the CAR Policy The CAR policy is used to control the each traffic classification in the V-UNI ingress policy. 9.7.2 Creating the Service WRED Policy Create the WRED discarding policy based on services, which includes the discarding threshold and discarding ratio for packets of different colors. The service WRED policy is applicable to the V-UNI ingress policy, V-UNI egress policy, PW policy and QinQ policy. 9.7.3 Creating the WFQ Scheduling Policy The WFQ scheduling policy is used to configure the weights for scheduling AF1 - AF4 queues. If no WFQ scheduling policy is available, the AF1-AF4 queues are scheduled according to the default template, that is, the 1:1:1:1 mode. 9.7.4 Creating the V-UNI Ingress Policy Create the V-UNI ingress policy to classify the accessed traffic, and to specify the parameters such as CoS. 9.7.5 Modifying the V-UNI Ingress Policy Modify the V-UNI ingress policy that is successfully created. The policy name, applied WFQ scheduling policy, CoS parameters and traffic classification parameters, and packet discarding policy can be modified. 9.7.6 Querying the V-UNI Ingress Policy-Applied Object The created V-UNI ingress policy is applied to a certain service to perform the QoS control. The PTN equipment supports querying the V-UNI ingress policy-applied objects, including service ID and V-UNI ID. 9.7.7 Deleting the V-UNI Ingress Policy Delete the V-UNI ingress policy not required. If used by a service, this policy cannot be deleted.

9.7.1 Creating the CAR Policy

The CAR policy is used to control the each traffic classification in the V-UNI ingress policy.

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

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

9-21

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

Context
In the case of the OptiX PTN 3900 and OptiX PTN 1900, the CAR parameters can be set in VUNI Ingress policy. OptiX PTN 912 does not supports CAR.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the CAR Policy tab. Step 3 Click New. The Create CAR Policy dialog box is displayed.

Step 4 Set the Policy ID, Policy Name, CAR parameters and Coloration Mode. Step 5 Set the handing mode of the packet with different color. Step 6 Click OK. ----End

9.7.2 Creating the Service WRED Policy

Create the WRED discarding policy based on services, which includes the discarding threshold and discarding ratio for packets of different colors. The service WRED policy is applicable to the V-UNI ingress policy, V-UNI egress policy, PW policy and QinQ policy.

Prerequisite
You must be an NM user with "NE operator" authority or higher.
9-22 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Select Service WRED Policy and click New. The Create Service WRED Policy dialog box is displayed. Set the following parameters in the dialog box.
l l

Policy ID and name. Discarding policy for green, yellow and red packets. The policy includes the lower threshold for discarding, higher threshold for discarding, and discarding probability.

Step 3 Click OK. ----End

9.7.3 Creating the WFQ Scheduling Policy

The WFQ scheduling policy is used to configure the weights for scheduling AF1 - AF4 queues. If no WFQ scheduling policy is available, the AF1-AF4 queues are scheduled according to the default template, that is, the 1:1:1:1 mode.

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

Context
The default WFQ schedule policy (Policy ID: 1; Policy Name: WFQ Default Scheduling) cannot be created, modified or deleted. In the case of the OptiX PTN 3900 and OptiX PTN 1900, the WFQ scheduling policy can be applied to the V-UNI Ingress, V-UNI Egress, PW, and QinQ policies. In the case of the OptiX PTN 912, the WFQ scheduling policy can be applied to the Port policy. In the case of the OptiX PTN 910 and OptiX PTN 950, the WFQ scheduling policy can be applied to the Port policy.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

9-23

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the WFQ Schedule Policy tab. Step 3 Click New. The Create WFQ Schedule Policy dialog box is displayed. Set the following parameters in the dialog box.
l l

Policy ID and name. AF scheduling weight.

NOTE

The total schedule weights of AF1-AF4 should not exceed 100.

Step 4 Click OK. ----End

9.7.4 Creating the V-UNI Ingress Policy

Create the V-UNI ingress policy to classify the accessed traffic, and to specify the parameters such as CoS.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. OptiX PTN 1900 and OptiX PTN 3900: Configuration of the WFQ scheduling policy must be complete. Otherwise, the V-UNI ingress policy is associated with the default WFQ scheduling policy OptiX PTN 1900 and OptiX PTN 3900: If the V-UNI ingress policy requires the WRED packet discarding policy to control the traffic, you must complete the configuration of the service WRED policy.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the V-UNI Ingress Policy tab. Click New. The Create V-UNI Ingress Policy dialog box is displayed.
9-24 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

Step 3 Set the Policy ID and Policy Name. Step 4 Click , and then choose the applied WFQ scheduling policy in the displayed WFQ Schedule Policy dialog box.
NOTE

Use the default WFQ scheduling policy by default.

NOTE

In the case of OptiX PTN 912/910/950, the V-UNI ingress policy cannot be associated with the WFQ scheduling policy, and the parameter for different CoS and packet discarding cannot be set.

Step 5 Set CoS parameters and packet discarding parameter.

NOTE

l l l

The CIR parameters of the CS7, CS6, EF queues must equal the value of the PIR parameter. The value of the CIR parameter of other queues must be less than or be equal to the value of the PIR parameter. To configure the PIR parameters for different queues, the maximum PIR should be not more than 100 times of the minimum PIR. The tail drop threshold value and service WRED policy cannot be configured at the same time.

Step 6 Click New. Then, configure the following attributes in the displayed Create Traffic Classification dialog box. Step 7 Set Traffic Classification ID, ACL Action and Logical Relation Between Matched Rules.
NOTE

In the case of OptiX PTN 912/910/950, the default value of ACL Action is Permit and cannot be set. Logical Relation Between Matched Rules can be set to And or Or. And indicates that all the traffic classification rules must be followed. Or indicates that just one traffic classification rule need be followed. In the case of OptiX PTN 910/950, the default value of Logical Relation Between Matched Rules is Or and cannot be set.

Step 8 Click Add and configure the traffic classification rules. You can set more traffic classification rules.
NOTE

In the case of OptiX PTN 912, the match type of the traffic classification rule only can be set to CVlan ID. In the case of OptiX PTN 910/950, the match type of the traffic classification rule can be set to CVlan ID or SVlan ID.

Step 9 Set CoS, CAR parameters and Coloration Mode. When Bandwidth Limit is set to Enabled, you can set the CIR/PIR/CBS/PBS.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9-25

9 Configuring the QoS Policy

NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

In the case of OptiX PTN 912/910/950, you need to select a CAR policy. CAR parameters and coloration mode can be set in CAR policy.

Step 10 Set the handing mode of the packet with different color. When Handling Mode is set to Remark, you can relabel the CoS and color of the packets. Step 11 Click OK to exit the Create Traffic Classification dialog box. Step 12 Set the Traffic Classification Bandwidth Sharing, you can set it to Disable or Enabled.
NOTE

In the case of OptiX PTN 912, the Traffic Classification Bandwidth Sharing cannot be set.

Step 13 Click OK to exit the Create V-UNI Ingress Policy dialog box. ----End

Related Operation
Use the copy function to fast create a new V-UNI Ingress policy based on the created V-UNI Ingress policy. The detailed operation is as follows: 1. 2. In the V-UNI Ingress Policy tab, click Copy. In the displayed Duplicate QoS Policy dialog box, select the policy to be copied, and then enter the new policy name. Then, click OK. Modify the related parameters of the newly created policy, and then make the new policy meet the QoS requirement.
NOTE

l l

For the method of modifying the V-UNI ingress policy, see 9.7.5 Modifying the V-UNI Ingress Policy. In the case of the copy function, the application information of the policy can not be copied.

9.7.5 Modifying the V-UNI Ingress Policy

Modify the V-UNI ingress policy that is successfully created. The policy name, applied WFQ scheduling policy, CoS parameters and traffic classification parameters, and packet discarding policy can be modified.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The policy is not applied.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the V-UNI Ingress Policy tab. In the tab, select the V-UNI ingress policy to be modified. Step 3 Modify the following parameters.
l l

Policy name. Applied WFQ scheduling policy.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

9-26

OptiX iManager T2000 Operation Guide for PTN NE Management

l

9 Configuring the QoS Policy

Traffic classification bandwidth sharing.

Step 4 Modify the CoS parameters. In the CoS Configuration tab, modify the CoS parameters. Then, click Apply. Step 5 Modify the traffic classification parameters. 1. 2. Click the Traffic Classification Configuration tab. Add new traffic classification. Click New. In the displayed Create Traffic Classification dialog box, enter the new traffic classification parameters, and then click OK. 3. Create the traffic classification parameters.
l l l

Select the traffic classification to be modified. Modify ACL action, CAR parameters, and then click Apply. Modify traffic classification rule. Click Traffic Classification Rule. In the displayed Traffic Classification Configuration dialog box, add, modify or delete the traffic classification rule, and then click OK.

Modify the processing mode of the colorized packets. Click Colorize. In the displayed Advanced Attributes dialog box, modify the processing mode of the colorized packets, and then click OK.

----End

9.7.6 Querying the V-UNI Ingress Policy-Applied Object

The created V-UNI ingress policy is applied to a certain service to perform the QoS control. The PTN equipment supports querying the V-UNI ingress policy-applied objects, including service ID and V-UNI ID.

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. You must use the V-UNI ingress policy to a service.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the V-UNI Ingress Policy tab. In the tab, select the V-UNI ingress policy for the query. Step 3 Click the Applied Object tab and click Query. Information on the service that uses this policy is displayed. ----End

9.7.7 Deleting the V-UNI Ingress Policy

Delete the V-UNI ingress policy not required. If used by a service, this policy cannot be deleted.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9-27

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The policy to be deleted is not used.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the V-UNI Ingress Policy tab. In the tab, select the V-UNI ingress policy to be deleted. Step 3 Click Delete. ----End

9.8 Configuring the V-UNI Egress Policy

Configure the V-UNI egress policy at the access side of the equipment to perform the QoS control over the egress traffic. 9.8.1 Creating the Service WRED Policy Create the WRED discarding policy based on services, which includes the discarding threshold and discarding ratio for packets of different colors. The service WRED policy is applicable to the V-UNI ingress policy, V-UNI egress policy, PW policy and QinQ policy. 9.8.2 Creating the WFQ Scheduling Policy The WFQ scheduling policy is used to configure the weights for scheduling AF1 - AF4 queues. If no WFQ scheduling policy is available, the AF1-AF4 queues are scheduled according to the default template, that is, the 1:1:1:1 mode. 9.8.3 Creating the V-UNI Egress Policy Create the V-UNI egress policy to specify the WFQ scheduling policy for the egress traffic at the access side, and to specify the traffic control parameters and packet discarding policy for different traffic. 9.8.4 Modifying the V-UNI Egress Policy Modify the V-UNI egress policy that is successfully created. The policy name, applied WFQ scheduling policy, CoS parameters and packet discarding parameters can be modified. 9.8.5 Querying the V-UNI Egress Policy-Applied Object The created V-UNI egress policy is applied to a certain service to perform the QoS control. The PTN equipment supports querying the V-UNI egress policy-applied objects, including service ID and V-UNI ID. 9.8.6 Deleting the V-UNI Egress Policy Delete the V-UNI egress policy not required. If used by a service, this policy cannot be deleted.

9.8.1 Creating the Service WRED Policy

Create the WRED discarding policy based on services, which includes the discarding threshold and discarding ratio for packets of different colors. The service WRED policy is applicable to the V-UNI ingress policy, V-UNI egress policy, PW policy and QinQ policy.

Prerequisite
You must be an NM user with "NE operator" authority or higher.
9-28 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Select Service WRED Policy and click New. The Create Service WRED Policy dialog box is displayed. Set the following parameters in the dialog box.
l l

Policy ID and name. Discarding policy for green, yellow and red packets. The policy includes the lower threshold for discarding, higher threshold for discarding, and discarding probability.

Step 3 Click OK. ----End

9.8.2 Creating the WFQ Scheduling Policy

The WFQ scheduling policy is used to configure the weights for scheduling AF1 - AF4 queues. If no WFQ scheduling policy is available, the AF1-AF4 queues are scheduled according to the default template, that is, the 1:1:1:1 mode.

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

Context
The default WFQ schedule policy (Policy ID: 1; Policy Name: WFQ Default Scheduling) cannot be created, modified or deleted. In the case of the OptiX PTN 3900 and OptiX PTN 1900, the WFQ scheduling policy can be applied to the V-UNI Ingress, V-UNI Egress, PW, and QinQ policies. In the case of the OptiX PTN 912, the WFQ scheduling policy can be applied to the Port policy. In the case of the OptiX PTN 910 and OptiX PTN 950, the WFQ scheduling policy can be applied to the Port policy.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

9-29

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the WFQ Schedule Policy tab. Step 3 Click New. The Create WFQ Schedule Policy dialog box is displayed. Set the following parameters in the dialog box.
l l

Policy ID and name. AF scheduling weight.

NOTE

The total schedule weights of AF1-AF4 should not exceed 100.

Step 4 Click OK. ----End

9.8.3 Creating the V-UNI Egress Policy

Create the V-UNI egress policy to specify the WFQ scheduling policy for the egress traffic at the access side, and to specify the traffic control parameters and packet discarding policy for different traffic.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. You must complete the configuration of the WFQ scheduling policy that can be used by the V-UNI egress policy. If the V-UNI egress policy requires the WRED packet discarding policy to control the traffic, you must complete the configuration of the service WRED policy.

Context
To create the V-UNI egress policy, perform the following operations.
l l

Specify the WFQ scheduling policy. Set the CAR parameters for different CoS, and specify the packet discarding policy, tail drop or WRED.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

9-30

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the V-UNI Egress Policy tab. Click New. The Create V-UNI Egress Policy dialog box is displayed. In the dialog box, set the following parameters.
l l

Policy ID and name. Applied WFQ scheduling policy. , and then choose the applied WFQ scheduling policy in the displayed WFQ Click Schedule Policy dialog box.
NOTE

Use the default WFQ scheduling policy by default.

l

CoS parameters and packet discarding parameter.

NOTE

The CIR parameters of the CS7, CS6, EF queues must equal the value of the PIR parameter. The value of the CIR parameter of other queues must be less than or be equal to the value of the PIR parameter. To configure the PIR parameters for different queues, the maximum PIR should be not more than 100 times of the minimum PIR. The tail drop threshold value and service WRED policy cannot be configured at the same time.

l l

Step 3 Click OK. ----End

Related Operation
Use the copy function to fast create a new V-UNI egress policy based on the created V-UNI egress policy. The detailed operation is as follows: 1. 2. In the V-UNI Egress Policy tab, click Copy. In the displayed Duplicate QoS Policy dialog box, select the policy to be copied, and then enter the new policy name. Then, click OK. Modify the related parameters of the newly created policy, and then make the new policy meet the QoS requirement.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9-31

Issue 01 (2009-06-30)

9 Configuring the QoS Policy

NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

In the case of the copy function, the application information of the policy can not be copied.

Postrequisite

9.8.4 Modifying the V-UNI Egress Policy

Modify the V-UNI egress policy that is successfully created. The policy name, applied WFQ scheduling policy, CoS parameters and packet discarding parameters can be modified.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The policy is not applied.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the V-UNI Egress Policy tab. In the tab, select the V-UNI egress policy to be modified. The following parameters can be modified.
l l l

Policy name. Applied WFQ scheduling policy. CoS parameters and packet discarding parameter.

Step 3 Click Apply. ----End

9.8.5 Querying the V-UNI Egress Policy-Applied Object

The created V-UNI egress policy is applied to a certain service to perform the QoS control. The PTN equipment supports querying the V-UNI egress policy-applied objects, including service ID and V-UNI ID.

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. A service must use the V-UNI egress policy.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the V-UNI Egress Policy tab. In the tab, select the V-UNI egress policy for the query. Step 3 Click the Applied Object tab and click Query. Information on the service that uses this policy is displayed. ----End
9-32 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

9.8.6 Deleting the V-UNI Egress Policy

Delete the V-UNI egress policy not required. If used by a service, this policy cannot be deleted.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The policy to be deleted is not used.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the V-UNI Egress Policy tab. In the tab, select the V-UNI egress policy to be deleted. Step 3 Click Delete. ----End

9.9 Configuring the PW Policy

Configure the PW policy at the network side to perform the QoS control over the ingress and egress traffic carried by the PW. 9.9.1 Creating the Service WRED Policy Create the WRED discarding policy based on services, which includes the discarding threshold and discarding ratio for packets of different colors. The service WRED policy is applicable to the V-UNI ingress policy, V-UNI egress policy, PW policy and QinQ policy. 9.9.2 Creating the WFQ Scheduling Policy The WFQ scheduling policy is used to configure the weights for scheduling AF1 - AF4 queues. If no WFQ scheduling policy is available, the AF1-AF4 queues are scheduled according to the default template, that is, the 1:1:1:1 mode. 9.9.3 Creating the PW Policy Create the PW policy to specify the WFQ scheduling policy for traffic at the network side, to specify different flow control parameters and packet discarding policies (tail drop or WRED) for different QoS. 9.9.4 Modifying the PW Policy Modify the PW policy that is successfully created. The policy name, applied WFQ scheduling policy, CoS parameters and packet discarding parameters can be modified. 9.9.5 Querying the PW Policy-Applied Object The created PW policy is applied to a certain PW to perform the QoS control over the ingress and egress traffic carried by the PW. The PTN equipment supports querying the PW policyapplied objects, including the PW ID, signel type, PW type, PW direction and function point direction. 9.9.6 Deleting the PW Policy Delete the PW policy not required. If used by a PW, this policy cannot be deleted.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

9-33

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

9.9.1 Creating the Service WRED Policy

Create the WRED discarding policy based on services, which includes the discarding threshold and discarding ratio for packets of different colors. The service WRED policy is applicable to the V-UNI ingress policy, V-UNI egress policy, PW policy and QinQ policy.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Select Service WRED Policy and click New. The Create Service WRED Policy dialog box is displayed. Set the following parameters in the dialog box.
l l

Policy ID and name. Discarding policy for green, yellow and red packets. The policy includes the lower threshold for discarding, higher threshold for discarding, and discarding probability.

Step 3 Click OK. ----End

9.9.2 Creating the WFQ Scheduling Policy

The WFQ scheduling policy is used to configure the weights for scheduling AF1 - AF4 queues. If no WFQ scheduling policy is available, the AF1-AF4 queues are scheduled according to the default template, that is, the 1:1:1:1 mode.

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

Context
The default WFQ schedule policy (Policy ID: 1; Policy Name: WFQ Default Scheduling) cannot be created, modified or deleted.
9-34 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

In the case of the OptiX PTN 3900 and OptiX PTN 1900, the WFQ scheduling policy can be applied to the V-UNI Ingress, V-UNI Egress, PW, and QinQ policies. In the case of the OptiX PTN 912, the WFQ scheduling policy can be applied to the Port policy. In the case of the OptiX PTN 910 and OptiX PTN 950, the WFQ scheduling policy can be applied to the Port policy.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the WFQ Schedule Policy tab. Step 3 Click New. The Create WFQ Schedule Policy dialog box is displayed. Set the following parameters in the dialog box.
l l

Policy ID and name. AF scheduling weight.

NOTE

The total schedule weights of AF1-AF4 should not exceed 100.

Step 4 Click OK. ----End

9.9.3 Creating the PW Policy

Create the PW policy to specify the WFQ scheduling policy for traffic at the network side, to specify different flow control parameters and packet discarding policies (tail drop or WRED) for different QoS.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. You must complete the configuration of the WFQ scheduling policy that can be used by the PW policy. If the PW policy requires the WRED packet discarding policy to control the traffic, you must complete the configuration of the service WRED policy.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9-35

Issue 01 (2009-06-30)

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the PW Policy tab. Click New in the tab. The Create PW Policy dialog box is displayed. Set the following parameters in the dialog box.
l l

Policy ID and name. Applied WFQ scheduling policy. Click , and then choose the applied WFQ scheduling policy in the displayed WFQ Schedule Policy dialog box.
NOTE

Use the default WFQ scheduling policy by default.

l

CoS parameters and packet discarding parameters.

NOTE

The CIR parameters of the CS7, CS6, EF queues must equal the value of the PIR parameter. The value of the CIR parameter of other queues must be less than or be equal to the value of the PIR parameter. To configure the PIR parameters for different queues, the maximum PIR should be not more than 100 times of the minimum PIR. The tail drop threshold value and service WRED policy cannot be configured at the same time. The bandwidth and PW policy can be configured in the ingress direction of the PW, but not in the egress direction of the PW.

l l l

Step 3 Click OK. ----End

Related Operation
Use the copy function to fast create a new PW policy based on the created PW policy. The detailed operation is as follows: 1. In the PW Policy tab, click Copy. In the displayed Duplicate QoS Policy dialog box, select the policy to be copied, and then enter the new policy name. Then, click OK.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

9-36

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

2.

Modify the related parameters of the newly created policy, and then make the new policy meet the QoS requirement.
NOTE

l l

For the method of modifying the PW policy, see 9.9.4 Modifying the PW Policy. In the case of the copy function, the application information of the policy can not be copied.

9.9.4 Modifying the PW Policy

Modify the PW policy that is successfully created. The policy name, applied WFQ scheduling policy, CoS parameters and packet discarding parameters can be modified.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The policy is not applied.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the PW Policy tab and select the PW policy to be modified. The following parameters can be modified.
l l l

Policy name. Applied WFQ scheduling policy. CoS parameters and packet discarding parameter.

Step 3 Click Apply. ----End

9.9.5 Querying the PW Policy-Applied Object

The created PW policy is applied to a certain PW to perform the QoS control over the ingress and egress traffic carried by the PW. The PTN equipment supports querying the PW policyapplied objects, including the PW ID, signel type, PW type, PW direction and function point direction.

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. You must use the PW policy for a PW.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the PW Policy tab and select the PW policy for the query.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9-37

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 3 Click the Applied Object tab and click Query. Information on PW that uses this policy is displayed. ----End

9.9.6 Deleting the PW Policy

Delete the PW policy not required. If used by a PW, this policy cannot be deleted.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The policy to be deleted is not used.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the PW Policy tab and select the PW policy to be deleted. Step 3 Click Delete. ----End

9.10 Configuring the QinQ Policy

Configure the QinQ policy at the network side to perform the QoS control over traffic carried by the QinQ link. 9.10.1 Creating the Service WRED Policy Create the WRED discarding policy based on services, which includes the discarding threshold and discarding ratio for packets of different colors. The service WRED policy is applicable to the V-UNI ingress policy, V-UNI egress policy, PW policy and QinQ policy. 9.10.2 Creating the WFQ Scheduling Policy The WFQ scheduling policy is used to configure the weights for scheduling AF1 - AF4 queues. If no WFQ scheduling policy is available, the AF1-AF4 queues are scheduled according to the default template, that is, the 1:1:1:1 mode. 9.10.3 Creating the QinQ Policy Create the QinQ policy to specify the WFQ scheduling policy for traffic at the network side, to specify different flow control parameters and packet discarding policy (tail drop or WRED) for different QoS. 9.10.4 Modifying the QinQ Policy Modify the QinQ policy that is successfully created. The policy name, applied WFQ scheduling policy, CoS parameters and packet discarding parameters can be modified. 9.10.5 Querying the QinQ Policy-Applied Object The created QinQ policy is applied to a certain QinQ link to perform the QoS control. The PTN equipment supports querying the QinQ policy-applied objects, including the QinQ link ID, physical port ID, S-VLAN ID and direction. 9.10.6 Deleting the QinQ Policy Delete the QinQ policy not required. If used by a QinQ link, this policy cannot be deleted.
9-38 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

9.10.1 Creating the Service WRED Policy

Create the WRED discarding policy based on services, which includes the discarding threshold and discarding ratio for packets of different colors. The service WRED policy is applicable to the V-UNI ingress policy, V-UNI egress policy, PW policy and QinQ policy.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Select Service WRED Policy and click New. The Create Service WRED Policy dialog box is displayed. Set the following parameters in the dialog box.
l l

Policy ID and name. Discarding policy for green, yellow and red packets. The policy includes the lower threshold for discarding, higher threshold for discarding, and discarding probability.

Step 3 Click OK. ----End

9.10.2 Creating the WFQ Scheduling Policy

The WFQ scheduling policy is used to configure the weights for scheduling AF1 - AF4 queues. If no WFQ scheduling policy is available, the AF1-AF4 queues are scheduled according to the default template, that is, the 1:1:1:1 mode.

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

Context
The default WFQ schedule policy (Policy ID: 1; Policy Name: WFQ Default Scheduling) cannot be created, modified or deleted.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9-39

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

In the case of the OptiX PTN 3900 and OptiX PTN 1900, the WFQ scheduling policy can be applied to the V-UNI Ingress, V-UNI Egress, PW, and QinQ policies. In the case of the OptiX PTN 912, the WFQ scheduling policy can be applied to the Port policy. In the case of the OptiX PTN 910 and OptiX PTN 950, the WFQ scheduling policy can be applied to the Port policy.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the WFQ Schedule Policy tab. Step 3 Click New. The Create WFQ Schedule Policy dialog box is displayed. Set the following parameters in the dialog box.
l l

Policy ID and name. AF scheduling weight.

NOTE

The total schedule weights of AF1-AF4 should not exceed 100.

Step 4 Click OK. ----End

9.10.3 Creating the QinQ Policy

Create the QinQ policy to specify the WFQ scheduling policy for traffic at the network side, to specify different flow control parameters and packet discarding policy (tail drop or WRED) for different QoS.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. You must complete the configuration of the WFQ scheduling policy that can be used by the QinQ policy. If the QinQ policy requires the WRED packet discarding policy to control the traffic, you must complete the configuration of the service WRED policy.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

9-40

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the QinQ Policy tab. Click New in the tab. The Create QinQ Policy dialog box is displayed. Set the following parameters in the dialog box.
l l

Policy ID and name. Applied WFQ scheduling policy. Click , and then choose the applied WFQ scheduling policy in the displayed WFQ Schedule Policy dialog box.
NOTE

Use the default WFQ scheduling policy by default.

l

CoS parameters and packet discarding parameter.

NOTE

The CIR parameters of the CS7, CS6, EF queues must equal the value of the PIR parameter. The value of the CIR parameter of other queues must be less than or be equal to the value of the PIR parameter. To configure the PIR parameters for different queues, the maximum PIR should be not more than 100 times of the minimum PIR. The tail drop threshold value and service WRED policy cannot be configured at the same time.

l l

Step 3 Click OK. ----End

Related Operation
Use the copy function to fast create a new QinQ policy based on the created QinQ policy. The detailed operation is as follows: 1. In the QinQ Policy tab, click Copy. In the displayed Duplicate QoS Policy dialog box, select the policy to be copied, and then enter the new policy name. Then, click OK.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9-41

Issue 01 (2009-06-30)

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

2.

Modify the related parameters of the newly created policy, and then make the new policy meet the QoS requirement.
NOTE

l l

For the method of modifying the QinQ policy, see 9.10.4 Modifying the QinQ Policy. In the case of the copy function, the application information of policy can not be copied.

9.10.4 Modifying the QinQ Policy

Modify the QinQ policy that is successfully created. The policy name, applied WFQ scheduling policy, CoS parameters and packet discarding parameters can be modified.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The policy is not applied.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the QinQ Policy tab and select the QinQ policy to be modified. The following parameters can be modified.
l l l

Policy name. Applied WFQ scheduling policy. CoS parameters and packet discarding parameter.

Step 3 Click Apply. ----End

9.10.5 Querying the QinQ Policy-Applied Object

The created QinQ policy is applied to a certain QinQ link to perform the QoS control. The PTN equipment supports querying the QinQ policy-applied objects, including the QinQ link ID, physical port ID, S-VLAN ID and direction.

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. You must use the QinQ policy for a QinQ link.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the QinQ Policy tab and select the QinQ policy for the query. Step 3 Click the Applied Object tab and click Query. Information on QinQ link that uses this policy is displayed. ----End
9-42 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

9.10.6 Deleting the QinQ Policy

Delete the QinQ policy not required. If used by a QinQ link, this policy cannot be deleted.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The policy to be deleted is not used.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the QinQ Policy tab and select the QinQ policy to be deleted. Step 3 Click Delete. ----End

9.11 Configuring the ATM CoS Mapping

Configure the mapping relation between the ATM service type and PHB service class to ensure the end-to-end QoS for ATM services.

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

Context
The OptiX PTN equipment supports the flexible mapping between the ATM service type and PHB service class. Table 9-7 lists the default ATM CoS mapping relation. Table 9-7 Mapping relation between the ATM service type and PHB service class Service Type CBR RT-VBR NRT-VBR UBR+ UBR PHB Service Class EF AF31 AF21 AF11 BE

NOTE

The default ATM CoS mapping cannot be modified or deleted.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

9-43

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > QoS Management > Diffserv domain Management from the Function Tree. Step 2 Click the ATM CoS Mapping Configuration tab and click Create. The Create ATM CoS Mapping Relation dialog box is displayed. Step 3 Set the following parameters in the dialog box.
l l l

Mapping Relation ID Mapping Relation Name Mapping between the service type and CoS level

Step 4 Click OK. ----End

9.12 Configuring the ATM Policy

For ATM services, configure the ATM policy to perform the QoS control over the traffic. 9.12.1 Creating the ATM Policy Create the ATM policy to configure the service type and bandwidth for the ATM traffic. 9.12.2 Modifying the ATM Policy Modify the ATM policy that is successfully created. The policy name, ATM service type and traffic parameter can be modified. 9.12.3 Querying the ATM Policy-Applied Object The created ATM policy is applied to a certain service to perform the QoS control. The PTN equipment supports querying the ATM policy-applied objects, including the service ID, service name, link ID and direction. 9.12.4 Deleting the ATM Policy Delete the ATM policy not required. If used by a service, this policy cannot be deleted.

9.12.1 Creating the ATM Policy

Create the ATM policy to configure the service type and bandwidth for the ATM traffic.
9-44 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the ATM Policy tab. Click New. The Create ATM Policy dialog box is displayed. Set the following parameters in the dialog box.
l l l l l

Policy ID and name Service type Traffic parameter Frame discarding label UPC/NPC

NOTE

The service encapsulated in AAL5 is sliced into cells. Enable Traffic Frame Discarding Flag determines whether to discard cells or to discard the complete AAL5 frames for the cells. When Enable Traffic Frame Discarding Flag is set to Enabled, the PTN equipment will discards the complete AAL5 frames for the cells. OptiX PTN 912 does not supports Enable Traffic Frame Discarding Flag. Only when UPC/NPC is enabled for the ATM policy, the Scr, Pcr, MBS, and CDVT bucket parameters are functional.

Step 3 Click OK. ----End

9.12.2 Modifying the ATM Policy

Modify the ATM policy that is successfully created. The policy name, ATM service type and traffic parameter can be modified.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9-45

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The policy is not applied.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the ATM Policy tab and select the ATM policy to be modified. The following parameters can be modified.
l l l l l

Policy name. Service type. ATM traffic parameter. Frame discarding label. UPC/NPC.

Step 3 Click Apply. ----End

9.12.3 Querying the ATM Policy-Applied Object

The created ATM policy is applied to a certain service to perform the QoS control. The PTN equipment supports querying the ATM policy-applied objects, including the service ID, service name, link ID and direction.

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. You must use the ATM policy for a service.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the ATM Policy tab and select the ATM policy for the query. Step 3 Click the Applied Object tab and click Query. Information on the service that uses this policy is displayed. ----End

9.12.4 Deleting the ATM Policy

Delete the ATM policy not required. If used by a service, this policy cannot be deleted.

Prerequisite
l

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

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

9-46

OptiX iManager T2000 Operation Guide for PTN NE Management

l

9 Configuring the QoS Policy

The policy to be deleted is not used.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the ATM Policy tab and select the ATM policy to be deleted. Step 3 Click Delete. ----End

9.13 Applying a QoS Policy

If the same QoS policy has to be applied for multiple NEs (for example, the V-UNI Ingress policy), it is easier to adopt the QoS policy application mode. In this mode, you only need to create the QoS policy on one NE and then you can apply the QoS policy to other NEs.

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

Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the tab of the QoS policy to be created and click New. Then, set the related parameters. Step 3 Click Apply to display a drop-down menu. Step 4 Choose Single NE or Multi NE to display the Select Equipment dialog box. Step 5 From Unselected NE, select the NEs to which the QoS policy is to be applied and click . Step 6 Click OK. ----End

9.14 QoS Configuration Case of the ATM Service

Configure the ATM policy and use the ATM policy on specified ATM service. In this way, the QoS for the ATM service is ensured. In addition, the tunnel QoS can be configured to control the tunnel bandwidth of the carried service flow. 9.14.1 Case Description This section describes the networking and data planning of this case. 9.14.2 Configuration Flow This section describes the configuration steps for this example. The configuration steps include Tunnel bandwidth configuration,ATM policy configuration and application, and PW bandwidth configuration.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9-47

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

9.14.1 Case Description

This section describes the networking and data planning of this case. As shown in Figure 9-6, the OptiX PTN equipment establishes IMA connections to two NodeBs through the E1 ports, and receives ATM services from these NodeBs. The OptiX PTN equipment first encapsulates the accessed ATM services into the PWE3 packets and transports the packets to the opposite OptiX PTN equipment. When receiving the packets , the opposite OptiX PTN equipment decapsulates the packets and transports the ATM services to the RNC through the STM-1 optical interface. Each NodeB transports services such as the real-time audio service, the signal and the data service. To ensure the QoS for different service types, the OptiX PTN equipment specifies different ATM policies for different service types, and uses different PWs to carry these services of various types. Figure 9-6 Networking diagram for the QoS configuration of the ATM service

NE4 NE5 10GE ring on NE6

GE ring on access layer

NE1 IMA1 pw1 pw2 pw3 IMA2 NE2

convergence layer

NE3 ATM STM-1

RNC
Working Tunnel

NodeB 1

NodeB 2

PW Protection Tunnel

UNI
IMA1:
Connection1 Connection2 Connection3 R99 HSDPA Signalling VPI 1 1 1 VCI 100 101 102

NNI
VPI 50 51 52 VCI 32 32 32

NNI
VPI 50 51 52 VCI 32 32 32

UNI
VPI 50 51 52 VCI 32 32 32

UNI
Connection1

NNI
VCI 100 101 102 VPI 60 61 62 VCI 32 32 32

NNI
VPI 60 61 62 VCI 32 32 32

UNI
VPI 60 61 62 VCI 32 32 32

IMA2:

Connection2 Connection3

R99 HSDPA Signalling

VPI 1 1 1

Table 9-8 lists the service types of the IMA traffic and the QoS requirements.

9-48

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

Table 9-8 Service types and QoS requirements Application Scenario Audio service, which is carried by the RT-VBR type. ATM Policy PW Bandwidth Tunnel Bandwidt h 30M bit/s

l l l l

Policy ID: 1 Policy name: RT-VBR Service type: RT-VBR Traffic type: ClpNoTaggingScrCdvt Clp01Pcr(cell/s): 4000 Clp0Scr(cell/s): 1000 MBS(cell): 100 CDVT(us): 10000 Enable Traffic Frame Discarding Flag: Disable UPC/NPC: Enabled Policy ID: 2 Policy name: CBR Service type: CBR Traffic type: NoClpNoScr Clp01Pcr(cell/s): 800 Enable Traffic Frame Discarding Flag: Disable UPC/NPC: Enabled Policy ID: 3 Policy name: UBR Service type: UBR Traffic type: NoTrafficDescriptor Enable Traffic Frame Discarding Flag: Disable UPC/NPC: Disabled

Bandwidth: 4 Mbit/s

l l l l l

Signal service, which is carried by the CBR type.

l l l l l l

Bandwidth: 1 Mbit/s

Data service, which is carried by the UBR type.

l l l l

Bandwidth: 15 Mbit/s

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

9-49

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

Table 9-9 Service types and QoS requirements Application Scenario Audio service, which is carried by the RT-VBR type. ATM Policy
l l l l l l l l l

Tunnel Bandwidth 10 Mbit/s

Policy ID: 1 Policy name: RT-VBR Service type: RT-VBR Traffic type: ClpNoTaggingScrCdvt Clp01Pcr(cell/s): 4000 Clp0Scr(cell/s): 1000 MBS(cell): 100 CDVT(us): 10000 Enable Traffic Frame Discarding Flag: No Policy ID: 2 Policy name: CBR Service type: CBR Traffic type: NoClpNoScr Clp01Pcr(cell/s): 800 Enable Traffic Frame Discarding Flag: No Policy ID: 3 Policy name: UBR Service type: UBR Traffic type: NoTrafficDescriptor Enable Traffic Frame Discarding Flag: No

Signal service, which is carried by the CBR type.

l l l l l l

Data service, which is carried by the UBR type.

l l l l l

9.14.2 Configuration Flow

This section describes the configuration steps for this example. The configuration steps include Tunnel bandwidth configuration,ATM policy configuration and application, and PW bandwidth configuration.

Prerequisite
You must understand the networking and data planning of the example.

Procedure
Step 1 Configure the RT-VBR policy.
9-50 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

1. 2.

In the NE Explorer, select NE1 and choose Configuration > QoS Management > Policy Management. Click the ATM Policy tab. Click New, set the parameters in the Create ATM Policydialog box displayed. Click OK.

Set the parameters for the RT-VBR policy as follows:

l l l

Policy ID: 1 Policy name: RT-VBR Service type: RT-VBR (Select the service type according to the accessed service. Herein, the audio service corresponds to the RT-VBR service, which is of the highest service priority.) Service Type: ClpNoTaggingScrCdvt (This parameter indicates that the two-level bucket is valid. At one level, CLP01 is processed according to Clp01Pcr and exceptional cells are discarded. At the other level, CLP0 is processed according to Clp0Scr and exceptional cells are discarded.) Clp01Pcr(cell/s): 4000 (This parameter indicates the maximum permitted rate at which cells are transmitted. Set the parameter according to the service rate.) Clp0Scr(cell/s): 1000 (This parameter indicates the sustainable cell rate at which cells are transmitted. Set the parameter according to the service rate.) MBS(cell): 100 (This parameter indicates the maximum number of burst cells tolerated by the equipment after the traffic exceeds Clp01Pcr.) CDVT(us): 10000 (This parameter indicates the capability of tolerating burst ATM cells. When a cell arrives later than it is expected, the cell bursts. The burst volume is measured by the time difference between the actual arrival time and expected arrival time. If the burst volume of multiple consecutive cells exceeds the CDVT, the equipment discards the exceptional cells. Set the parameter to a large value, when possible, to minimize the number of lost packets.)

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

9-51

9 Configuring the QoS Policy

l

OptiX iManager T2000 Operation Guide for PTN NE Management

Enable Traffic Frame Discarding: Disabled (The service encapsulated in AAL5 is sliced into cells. Enable Traffic Frame Discarding Flag determines whether to discard cells or to discard the complete AAL5 frames for the cells.) UPC/NPC: Enable (UPC and NPC stand for user parameter control and network parameter control respectively. The bucket algorithm is based on the content of UPC/ NPC. UPC/NPC is intended to monitor the cells received by the equipment according to the specified traffic parameters, and thus to prevent network congestion. Only when UPC/NPC is enabled for the ATM policy, the Scr, Pcr, MBS, and CDVT bucket parameters are functional.)

3. 4.

Click OK. In the NE Explorer, select NE2 and repeat the previous two steps to create the ATM policies for NE2. Set the policy-related parameters of NE2 as the same as the policy-related parameters of NE1.

Step 2 Configure the CBR policy. 1. 2. In the NE Explorer, select NE1 and choose Configuration > QoS Management > Policy Management. Click the ATM Policy tab. Click New, set the parameters in the Create ATM Policydialog box displayed. Click OK.

Set the parameters for the CBR policy as follows:

l l l

Policy ID: 2 Policy name: CBR Service type: CBR (Select the service type according to the accessed service. Herein, the signal service corresponds to the CBR service, which is of the highest service priority.) Service Type: NoClpNoScr (The bucket at the first level takes effect, processes the cells with the Clp01 flags according to Clp01Pcr, and discards the cells without the Clp01 flags.) Clp01Pcr(cell/s): 800
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

9-52

OptiX iManager T2000 Operation Guide for PTN NE Management

l l

9 Configuring the QoS Policy

Enable Traffic Frame Discarding: Disabled UPC/NPC: Enable

3. 4.

Click OK. In the NE Explorer, select NE2 and repeat the previous two steps to create the ATM policies for NE2. Set the policy-related parameters of NE2 as the same as the policy-related parameters of NE1. In the NE Explorer, select NE1 and choose Configuration > QoS Management > Policy Management. Click the ATM Policy tab. Click New, set the parameters in the Create ATM Policydialog box displayed. Click OK.

Step 3 Configure the UBR policy. 1. 2.

Set the parameters for the UBR policy as follows:

l l

Policy ID: 3 Policy name: UBR (Select the service type according to the accessed service. Herein, the data service corresponds to the UBR service, which is of the lowest service priority.) Service type: UBR (No QoS is ensured for the accessed service. In the case of network congestion, the UBR cells are discarded at the earliest.) Traffic Type: NoTrafficDescriptor (no traffic description) Enable Traffic Frame Discarding: Disabled UPC/NPC: Enable

l l l

3. 4.

Click OK. In the NE Explorer, select NE2 and repeat the previous two steps to create the ATM policies for NE2. Set the policy-related parameters of NE2 as the same as the policy-related parameters of NE1.

Step 4 Configure the ATM CoS mapping. The default ATM CoS mapping is adopted in this case.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9-53

9 Configuring the QoS Policy

NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

For details on how to configure the ATM CoS mapping, see 9.11 Configuring the ATM CoS Mapping.

Step 5 Configure the ATM service. When creating a ATM service, do as follows.
l

Configure the ATM connection.

Specify the uplink and downlink ATM policy, that is, Policy 1(RT-VBR), for the ATM connections that carry the audio services. Specify the uplink and downlink ATM policy, that is, Policy 2(CBR), for the ATM connections that carry the signal services. Specify the uplink and downlink ATM policy, that is, Policy 3(UBR), for the ATM connections that carry the data services.

Configure the PW. Specify the bandwidth for the PW in the QoS tab.

The bandwidth of PW 1 (corresponding to CBR service type) is 4 Mbit/s. The bandwidth of PW 2 (corresponding to rt-VBR service type) is 1 Mbit/s. The bandwidth of PW 3 (corresponding to UBR service type) is 15 Mbit/s.

Configure the ATM CoS mapping relation. Specify the ATM CoS mapping the ATM service. The mapping ID is 1 and the mapping name is DefaultAtmCosMap.
NOTE

DefaultAtmCosMap is the default ATM CoS mapping table of the equipment and cannot be deleted. In this example, the default CoS mapping table is used. The user can also create an ATM CoS mapping table as required. For details on how to create an ATM CoS mapping table, see 9.11 Configuring the ATM CoS Mapping.
NOTE

For the ATM service configuration method, see 19.9 Configuration Case of the UNIs-NNI ATM Service.

----End

9.15 QoS Configuration Case of the Ethernet Service

Configure the hierarchical QoS policy and use it for a specified Ethernet service. In this way, the QoS for the service is ensured. 9.15.1 Case Description This section describes the networking and data planning for this example. 9.15.2 Configuration Flow This section describes the configuration steps for this case. The configuration steps include domain configuration, and configuration and application of various QoS policies.

9.15.1 Case Description

This section describes the networking and data planning for this example. Several PTN NEs form a DiffServ domain to provide ensured end-to-end QoS for the Ethernet traffic.
9-54 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

As an edge DS node, the PTN equipment provides the hierarchical QoS control function for Ethernet traffic.
l l

Mapping between the service priority and PHB service level Hierarchical QoS policy

Port policy V-UNI ingress policy and V-UNI egress policy PW Policy V-UNI group bandwidth control Tunnel bandwidth control
NOTE

Hierarchical bandwidth control

The bandwidth of the V-UNI group and the tunnel bandwidth are configured during service configuration. For details on how to configure the bandwidth, see the specific sections. This example only focuses on the configuration and application of the QoS policy.

As an internal DS node, the PTN equipment provides the following QoS control functions for Ethernet traffic.
l l l

Mapping between the service priority and PHB service level Port policy (optional) Tunnel bandwidth control
NOTE

The mapping relation between the service priority of the internal DS node and PHB service level should be consistent with that between the service priority of the edge DS node and PHB service level. It is recommended that all the PTN equipment use the default mapping relation. The QoS configuration for the internal DS node is much simpler than that for the edge DS node. This example focuses on the QoS configuration for the edge DS node.

Figure 9-7 shows the networking diagram for QoS configuration of the Ethernet service. Figure 9-7 Networking diagram for QoS configuration of the Ethernet service
Access side V-UNI Port ingress V-UNI egress V-UNI group Network side PW Tunnel Port

DiffServ domain Tunnel

Ethernet switch

PTN (edge DS node)

PTN (internal DS node)

PTN (edge DS node)

Core switch

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

9-55

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

The PTN equipment accesses the Ethernet services (VLAN = 20, including VoIP, IPTV and data services) of a user to the DifferServ domain through the FE interface. In addition, the PTN equipment provides different QoS for different types of services of the user. Table 9-10 lists the requirements for QoS configuration of the Ethernet service. Table 9-10 Requirements for QoS configuration of the Ethernet service V-UNI Ingress Policy Flow classification parameters
l

V-UNI Egress Policy

l

PW Policy
l

EF CIR: 2 Mbit/s PIR: 2 Mbit/s CBS: 120000 bytes PBS: 10000000 bytes WRED: 2

EF CIR: 2 Mbit/s PIR: 2 Mbit/s CBS: 120000 bytes PBS: 10000000 bytes WRED: 2

VoIP service Network section of the source IP address: 129.5.1.0 PHB: EF CIR: 2 Mbit/s PIR: 2 Mbit/s
l

AF4 CIR: 6 Mbit/s PIR: 16 Mbit/s CBS: 120000 bytes PBS: 10000000 bytes WRED: 2

AF4 CIR: 6 Mbit/s PIR: 16 Mbit/s CBS: 120000 bytes PBS: 10000000 bytes WRED: 2

IPTV service Network section of the source IP address: 129.5.2.0 PHB: AF4 CIR: 6 Mbit/s PIR: 16M bit/s

Data service Network section of the source IP address: 129.5.3.0 PHB: BE CIR: 320 kbit/s PIR: 16 Mbit/s

BE CIR: 512 kbit/s PIR: 16 Mbit/s CBS: 120000 bytes PBS: 10000000 bytes WRED: 2

BE CIR: 512 kbit/s PIR: 16 Mbit/s CBS: 120000 bytes PBS: 10000000 bytes WRED: 2

For the CoS parameters, refer to parameters of "V-UNI Egress Policy."

9.15.2 Configuration Flow

This section describes the configuration steps for this case. The configuration steps include domain configuration, and configuration and application of various QoS policies.

Prerequisite
You must understand the networking and data planning of the example.

Procedure
Step 1 Configure a domain.
9-56 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

This case uses the default mapping relation between the service priority and PHB service level, and thus no configuration is required.
l l

Mapping Relation ID: 1 Mapping Relation Name: Default Map

NOTE

For configuration of new mapping relation, see 9.5.1 Creating a DiffServ Domain.

Step 2 Configure the WFQ policy. This case uses the default WFQ policy, and thus no configuration is required.
l l

Policy ID: 1 Policy Name: WFQ Default Scheduling

NOTE

For configuration of new WFQ policy, see 9.10.2 Creating the WFQ Scheduling Policy.

Step 3 Configure the service WRED policy.

l l l

Policy ID: 2 Policy Name: service-wred Discarding rule of red packets:

Discarding lower threshold: 2048 Discarding upper threshold: 2550 Discarding rate: 70% Discarding lower threshold: 2500 Discarding upper threshold: 3500 Discarding rate: 70% Discarding lower threshold: 3500 Discarding upper threshold: 4095 Discarding rate: 30%

Discarding rule of yellow packets:

Discarding rule of green packets:

NOTE

For the configuration method, see 9.10.1 Creating the Service WRED Policy.

Step 4 Configure the port policy. This case does not use port policy, and then this step can be skipped.
NOTE

For the configuration of port policy, see 9.6.2 Creating the Port Policy.

Step 5 Configure the V-UNI Ingress policy.

l l l

Policy ID: 1 Policy Name: V-UNI-Ingress WFQ Policy: Default value

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 9-57

Issue 01 (2009-06-30)

9 Configuring the QoS Policy

l

OptiX iManager T2000 Operation Guide for PTN NE Management

Traffic classification (ID = 1) parameters:

Traffic Classification ID: 1 ACL Action: Allowed Traffic classification Rule: Match Type: Source IP; Match Value: 129.5.1.0; Wildcard: 129.5.0.255. CAR parameters: CoS CIR CBS Coloration Mode EF 2 Mbit/s 120000 bytes Color Blindness Bandwidth Limit PIR PBS Packet Processing Mode Enabled 2 Mbit/s 10000000 bytes Default value

Traffic classification (ID = 2) parameters:

Traffic Classification ID: 2 ACL Action: Allowed Traffic classification Rule: Match Type: Source IP; Match Value: 129.5.2.0; Wildcard: 129.5.0.255. CAR parameters: CoS CIR CBS Coloration Mode AF4 6 Mbit/s 120000 bytes Color Blindness Bandwidth Limit PIR PBS Packet Processing Mode Enabled 16 Mbit/s 10000000 bytes Default value

Traffic classification (ID = 3) parameters:

Traffic Classification ID: 3 ACL Action: Allowed Traffic classification Rule: Match Type: Source IP; Match Value: 129.5.3.0; Wildcard: 129.5.0.255. CAR parameters: CoS CIR CBS Coloration Mode BE 320 Kbit/s 120000 bytes Color Blindness Bandwidth Limit PIR PBS Packet Processing Mode Enabled 16 Mbit/s 10000000 bytes Default value

CoS parameters:
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

9-58

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

CoS CIR CBS Tail Drop

EF 2 Mbit/s 120000 bytes -

Bandwidth Limit PIR PBS WRED

Enabled 2 Mbit/s 10000000 bytes service-wred

CoS CIR CBS Tail Drop

AF4 6 Mbit/s 120000 bytes -

Bandwidth Limit PIR PBS WRED

Enabled 16 Mbit/s 10000000 bytes service-wred

CoS CIR CBS Tail Drop

BE 120000 bytes -

Bandwidth Limit PIR PBS WRED

Enabled 16 Mbit/s 10000000 bytes service-wred

NOTE

For configuration method, see 9.7.4 Creating the V-UNI Ingress Policy.

Step 6 Configure the V-UNI Egress policy.

l l l

Policy ID: 1 Policy Name: V-UNI-Egress CoS parameters: CoS CIR CBS Tail Drop EF 2 Mbit/s 120000 bytes Bandwidth Limit PIR PBS WRED Enabled 2 Mbit/s 10000000 bytes service-wred

CoS CIR CBS Tail Drop

AF4 6 Mbit/s 120000 bytes -

Bandwidth Limit PIR PBS WRED

Enabled 16 Mbit/s 10000000 bytes service-wred

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

9-59

9 Configuring the QoS Policy

OptiX iManager T2000 Operation Guide for PTN NE Management

CoS CIR CBS Tail Drop

BE 120000 bytes -

Bandwidth Limit PIR PBS WRED

Enabled 16 Mbit/s 10000000 bytes service-wred

NOTE

For the configuration method, see 9.8.3 Creating the V-UNI Egress Policy.

Step 7 Configure the PW policy.

l l l

Policy ID: 1 Policy Name: PW-Policy CoS parameters: CoS CIR CBS Tail Drop EF 2 Mbit/s 120000 bytes Bandwidth Limit PIR PBS WRED Enabled 2 Mbit/s 10000000 bytes service-wred

CoS CIR CBS Tail Drop

AF4 6 Mbit/s 120000 bytes -

Bandwidth Limit PIR PBS WRED

Enabled 16 Mbit/s 10000000 bytes service-wred

CoS CIR CBS Tail Drop

BE 120000 bytes -

Bandwidth Limit PIR PBS WRED

Enabled 16 Mbit/s 10000000 bytes service-wred

NOTE

For configuration method, see 9.9.3 Creating the PW Policy.

Step 8 Apply the port policy. This case does not use the port policy, and thus this step can be skipped.
NOTE

For the application of port policy, see 9.6.2 Creating the Port Policy.

9-60

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

9 Configuring the QoS Policy

Step 9 Configure the Tunnel. When configuring the tunnel, set the Tunnel bandwidth to 16 Mbit/s.
NOTE

For configuration method, see 13 Configuring an MPLS Tunnel.

Step 10 When configuring the Ethernet service, use the V-UNI Ingress policy, V-UNI Egress policy, or PW policy. When configuring the Ethernet service, use the following policies:
l

V-UNI Ingress Policy

Policy ID: 1 Policy Name: V-UNI-Ingress Policy ID: 1 Policy Name: V-UNI-Egress Policy ID: 1 Policy Name: PW-Policy

V-UNI Egress Policy

PW Policy

NOTE

For configuration method, see 20.2 Configuring an E-Line Service, 20.3 Configuring an E-LAN Service or 20.4 Configuring an E-AGGR Service.

----End

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

9-61

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

10
About This Chapter
Context

Configuring Interfaces

This section describes how to set the interface attributes of the boards. In the case of the PTN equipment, the attributes of SDH interfaces, PDH interfaces, Ethernet interfaces, Ethernet virtual interfaces, Serial interfaces, ADSL interfaces, G.SHDSL interfaces and MP Group can be set.

The settings of the interface attributes of an interface depends on the application scenario. For details, refer to Table 10-1. Table 10-1 Types of PTN service interfaces Service Interface Supported Port Mode/ Encapsulation Type General attributes Port Type MP Group Supported or Not Not supported Function

SDH interface

Physical port

Sets together with the Layer 3 attributes or connects to the equipment as the channelized STM service interface. This interface can carry the ATM services. This interface can carry tunnels after the PPP is enabled.

Layer 2 attributes Layer 3 attributes

Physical port

Not supported

Physical port

Not supported

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-1

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Service Interface

Supported Port Mode/ Encapsulation Type General attributes Layer 2 attributes Layer 3 attributes

Port Type

MP Group Supported or Not Not supported

Function

PDH interface

Physical port

This interface can carry the TDM services. Carries the IMA signals. This interface can be added into a multilink PPP (MP) group after the PPP is enabled. Sets together with the Layer 2 and Layer 3 attributes. Carries the userside or networkside Ethernet services. Carries tunnels. Sets together with the Layer 2 and Layer 3 attributes. Carries the Ethernet services for VLAN Sub Interface.
l

Physical port Physical port

Not supported Supported

Ethernet interface

General attributes

None

None

Layer 2 attributes

Physical port

Not supported

Layer 3 attributes Ethernet Virtual interface General attributes

Physical port Logical port

Not supported Not supported

Layer 2 attributes

Logical port

Not supported

Layer 3 attributes

Logical port

Not supported

EOA Virtual Interface: carries the IP or GRE tunnels. VLAN Sub Interface: applies to the BFD, L3VPN or Tunnel

10-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Service Interface

Supported Port Mode/ Encapsulation Type General attributes General attributes General attributes Layer 3 attributes

Port Type

MP Group Supported or Not -

Function

ADSL interface G.SHDSL interface Serial interface

Physical port Physical port

Carries the ADSL signals Carries the G.SHDSL signals Sets together with the Layer 3 attributes. This interface can be added to an MP group after the PPP is enabled. Sets together with the IP attributes. Carries tunnels.

None

None

Logical port

Supported

MP Group

General attributes IP attributes

None

None

Logical port

None

10.1 Configuring SDH Interfaces This section describes how to set the attributes of SDH interfaces. In a packet switching network (PSN), set the attributes of the SDH interfaces for them to work in the channelized STM mode, ATM mode or POS mode. In a PSN network, the ATM interface can be used to connect to the user-side equipment, and the POS interface can be used to carry the tunnel. The attributes of SDH interfaces include the general attributes, Layer 2 attributes, Layer 3 attributes and advanced attributes. 10.2 Configuring PDH Interfaces This section describes how to set the attributes of PDH interfaces. In a PSN network, the PDH interfaces can be used to carry TDM signals, IMA signals, or tunnels, depending on different settings of the interface attributes. The attributes of a PDH interface include the general attributes, layer 2 attributes, layer 3 attributes and advanced attributes. 10.3 Configuring Ethernet Interfaces This section describes how to set the attributes of Ethernet interfaces. In a PSN network, the Ethernet interfaces can be used to carry Ethernet packets or tunnels, depending on different settings of the interface attributes. The attributes of the Ethernet interface include the general attributes, Layer 2 attributes, Layer 3 attributes, advanced attributes and flow control. 10.4 Configuring ADSL Interfaces This topic describes how to configure ADSL interfaces. ADSL interfaces are used to carry offload services. The configuration of the ADSL interface includes the basic attributes of the interface, VPI/VCI of the interface, and enabling status of the tunnel at the virtual interface. After configuring the ADSL interface, you can configure offload services. 10.5 Configuring G.SHDSL Interfaces
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 10-3

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

This section describes how to configure the G.SHDSL interface, which carries the Offload service. The G.SHDSL interface can carry the Offload service by adopting three working modes, that is, ATM mode, IMA mode and EFM mode. The SHD4 board supports the ATM mode and EFM mode. The SHD4I supports the IMA mode. Configure attributes for the G.SHDSL interface according to the encapsulation mode so that the G.SHDSL interface can transmit the Offload service. 10.6 Configuring Microwave Interfaces This section describes how to configure the IF 1+1 protection of the IF board, the IF/ODU information of the radio link, microwave interface attributes, and ODU interface parameters. 10.7 Configuring Serial Interfaces This topic describes how to set the attributes of serial interfaces. Currently, serial interfaces have two levels, which are VC12 level and 64 kbit/s timeslot level. If you create a serial interface at the VC12 level, you can use a certain E1 timeslot in a channelized STM-1 frame to carry tunnels. If you create a serial interface at the 64 kbit/s timeslot level, you can bind certain timeslots in an E1 frame to a path. Timeslots 0 and 16 in the E1 frame are used to transmit control words, signaling, and other information. You can bind 10 timeslots to form an ATM path to transmit ATM services or bind five timeslots to form a CES path to transmit CES services. In this way, an E1 signal can carry both CES and ATM services. 10.8 Configuring ML-PPP This section describes how to configure Multilink PPP (MP) group. MP is a technology used to bind multiple PPP links to increase the bandwidth. MP is applied to the interface that supports PPP. MP supports fragmented packets. The fragmented packets are transmitted on multiple PPP links in the MP group to the same destination. 10.9 Configuring an Ethernet Virtual Interface This section describes how to configure an Ethernet virtual interface. After you configure the Ethernet virtual interface, the NE can process ATM AAL5-encapsulated or VLAN-encapsulated Ethernet packets. The Ethernet virtual interface attributes include general attributes and layer 3 attributes. 10.10 Configuring an IMA Group When the PTN equipment accesses IMA services, configure an ATM IMA group at the access node. 10.11 Configuring the V-UNI Group When one user has multiple Ethernet service access points or one Ethernet service has multiple access points, the V-UNI group can be configured. The V-UNI group can realize the overall bandwidth restriction on group members, that is, the V-UNI in the group. On the T2000, the user can create, modify and delete the V-UNI group. 10.12 ML-PPP Configuration Case A case is provided here to show how to configure the ML-PPP in terms of the typical application and configuration operations. 10.13 Configuring Environment Monitor Interfaces The environment monitoring interfaces of the equipment include enabling status of the input relay and output relay, temperature attributes and so on. You can set the environment monitoring interfaces so that the running environment of the equipment can be automatically monitored. 10.14 Setting Automatic Laser Shutdown Automatic laser shutdown is a function of automatically shutting down the laser when there is no input light and the laser stops emitting optical signals. For example, when an optical interface board does not bear services, a fault occurs on the fiber, or the received optical signals are lost, the laser is automatically turned off. This reduces the on period of the laser, extends the service
10-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

life of the laser, and prevents hazardous laser radiation exposure from causing permanent eye damage.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-5

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

10.1 Configuring SDH Interfaces

This section describes how to set the attributes of SDH interfaces. In a packet switching network (PSN), set the attributes of the SDH interfaces for them to work in the channelized STM mode, ATM mode or POS mode. In a PSN network, the ATM interface can be used to connect to the user-side equipment, and the POS interface can be used to carry the tunnel. The attributes of SDH interfaces include the general attributes, Layer 2 attributes, Layer 3 attributes and advanced attributes.

Context
The attributes vary with the application scenarios of SDH interfaces. Table 10-2 lists the application scenarios. Table 10-2 Application scenario of SDH interfaces Application Scenario Carrying the CES service Carrying the ATM service Carrying the tunnel Interface Type Channelized STM-1 interface ATM interface POS interface Required Interface Attribute General attributes General attributes, Layer 2 attributes General attributes, Layer 3 attributes

Follow the procedure shown in Figure 10-1 to configure an SDH interface.

10-6

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Figure 10-1 Procedure for configuring an SDH interface

Configure cSTM interface Start Configure ATM interface Start Configure POS interface Start

Configure general attributes

Configure general attributes

Configure general attributes

Configure advanced attributes

Configure layer 2 attributes

Configure layer 3 attributes

End

Configure advanced attributes

Configure advanced attributes

End

End

Required

Optional

10.1.1 Setting the General Attributes of SDH Interfaces The general attributes of an SDH interface define the physical-layer information, such as the port mode, encapsulation type, and maximum data packet length. An SDH interface can be configured as a channelized STM interface, ATM interface, or POS interface. Before you configure an SDH interface into a POS interface, set the general attributes of the SDH interface. 10.1.2 Setting the Layer 2 Attributes of SDH Interfaces Before you create an ATM service, you need to set the layer 2 attributes of the corresponding SDH interface. The layer 2 attributes of a SDH interface define the related information of the data link layer. 10.1.3 Setting the Layer 3 Attributes of SDH Interfaces Before you run PPP on an SDH interface, you need to set the layer 3 attributes of the SDH interface. The layer 3 attributes of an SDH interface define the related attributes of the network layer. 10.1.4 Setting the Advanced Attributes of SDH Interfaces The routine maintenance parameters can be set by setting the advanced attributes of SDH interfaces. 10.1.5 Setting the VC12 Frame Format and Frame Mode Before you configure a service, you can set the VC12 frame format and frame mode of a channelized SDH interface, to ensure that the two interconnected ports have the same frame
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 10-7

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

format and frame mode. If the two interconnected ports have different frame formats or frame mode, the services are unavailable. 10.1.6 Querying the Running Status of PPP In the case of a network failure, you can query the running status of the PPP to analyze the cause of the failure. 10.1.7 Resetting the PPP In the case of a network failure, you can reset the PPP to enable the PPP ports on the two ends of a link to re-negotiate.

10.1.1 Setting the General Attributes of SDH Interfaces

The general attributes of an SDH interface define the physical-layer information, such as the port mode, encapsulation type, and maximum data packet length. An SDH interface can be configured as a channelized STM interface, ATM interface, or POS interface. Before you configure an SDH interface into a POS interface, set the general attributes of the SDH interface.

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

Context
Packet over SDH (POS) is a technology that is used to transport packet data in MAN and WAN networks. POS adopts SDH and SONET as the physical layer protocols and directly maps the variable-length data packets into SDH payload, thus providing a type of high-speed, reliable, and point-to-point data connection.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > SDH Interface from the Function Tree. Step 2 Select the desired board. Step 3 Set the parameters as required.

10-8

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

10 Configuring Interfaces

Note the following issues during parameter settings:

l l l

When Port Mode is set to Layer 1, Encapsulation Type does not support the settings. In this case, channelized STM-N services can be accessed. When Port Mode is set to Layer 2, Encapsulation Type supports ATM only. In this case, ATM services can be accessed. If you set Port Mode to Layer 3, select Null or PPP for Encapsulation Type. If you select Null, the interface does not enable the PPP, and thus the equipment bears less load. If you select PPP, the interface can access the MPLS or IP service. In the case an NNI interface,Max Data Packet Size(byte) must be larger than 960. A DCN packet contains a maximum of 960 bytes. If Max Data Packet Size(byte) is smaller than 960, the DCN packets in the receive direction may be lost.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

10.1.2 Setting the Layer 2 Attributes of SDH Interfaces

Before you create an ATM service, you need to set the layer 2 attributes of the corresponding SDH interface. The layer 2 attributes of a SDH interface define the related information of the data link layer.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > SDH Interface from the Function Tree. Step 2 Click the Layer 2 Attributes tab. Step 3 Select the board to be configured and set the parameters as required.

NOTE

AD1 sub-board: VPI ranges from 0 to 4095 and VCI ranges from 32 to 65535. The VPI range and VCI range can be set for each port on the AD1. Each VP uses two items in the VP switch table and each VC uses one item in the VC switch table. For the AD1, the number of total items in the VP switch table and VC switch table is 88324.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-9

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

CAUTION
If any service is configured on the port, modifying the VPI or VCI range for the port causes transient interruption of the service. Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

10.1.3 Setting the Layer 3 Attributes of SDH Interfaces

Before you run PPP on an SDH interface, you need to set the layer 3 attributes of the SDH interface. The layer 3 attributes of an SDH interface define the related attributes of the network layer.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. In General Attributes, Encapsulation Type must be set to PPP.

Context
In a PSN network, the SDH interface is used to transport the PPP-encapsulated packet data.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > SDH Interface from the Function Tree. Step 2 Click the Layer 3 Attributes tab. Step 3 Select the desired board and set the parameters as required.
NOTE

Note the following issues during parameter settings:

l

Max Reserved Bandwidth indicates the bandwidth used by tunnels. The total of the maximum reserved bandwidth of the tunnels carried by port should be not more than the physical bandwidth of the port. When changing Specify IP from Manually to Unnumbered IP, manually specify the invalid IP address (255.255.255.255) and invalid IP mask (255.255.255.255) to release the IP address manually specified. When modifying the IP address of the interface, make sure that the IP address of this interface and the IP addresses of other interfaces configured with services are not in the same subnet.

Step 4 Click Apply. The Operation Result dialog box is displayed, indicating that the operation is successful. Step 5 Click Close. ----End
10-10 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

10.1.4 Setting the Advanced Attributes of SDH Interfaces

The routine maintenance parameters can be set by setting the advanced attributes of SDH interfaces.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > SDH Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Select the board to be configured and set the parameters as required.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

10.1.5 Setting the VC12 Frame Format and Frame Mode

Before you configure a service, you can set the VC12 frame format and frame mode of a channelized SDH interface, to ensure that the two interconnected ports have the same frame format and frame mode. If the two interconnected ports have different frame formats or frame mode, the services are unavailable.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must set the frame format and frame mode before you configure a service. You cannot change the frame format and frame mode of a port that is already configured with services.

Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > Interface Management > Path Configuration from the Function Tree. Step 2 Set the VC12 frame format as required.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 10-11

10 Configuring Interfaces
NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

When setting parameters, note the following points:

l l l l

You must set the frame format before you configure a service. In addition, the frame formats of the two interconnected ports must be consistent. If you set this parameter to Unframe, you can only configure a CES service in the SAToP mode. Double Frame: 32 bits form one G.704 basic frame. The double frame is a multiframe formed by two G.704 basic frames. The double frame is used for alignment. CRC-4 Multiframe: 32 bits form one G.704 basic frame. The CRC-4 multiframe is formed by 16 basic G.704 frames, which is defined in G.706 standard. The CRC-4 multiframe carries the cyclical redundancy check (CRC) information and line monitoring information. In the case of the CRC-4 multiframe flow, align the frames in the double frame mode. After the frames are successfully aligned in the double frame mode, align the frames in the CRC-4 multiframe mode. Unframe: The signals are continuous bit streams, which have no frame structure.

Step 3 Set the VC12 fame mode as required. Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

10.1.6 Querying the Running Status of PPP

In the case of a network failure, you can query the running status of the PPP to analyze the cause of the failure.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The encapsulation type of the created SDH interface must be PPP.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > SDH Interface from the Function Tree. Step 2 Select Port, right-click, and choose Query PPP Running Status from the shortcut menu. The PPP Running Status dialog box is displayed. Step 3 Click Close. ----End

10.1.7 Resetting the PPP

In the case of a network failure, you can reset the PPP to enable the PPP ports on the two ends of a link to re-negotiate.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The encapsulation type of the created SDH interface must be PPP.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

10-12

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Context

CAUTION
Resetting the PPP will interrupt services.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > SDH Interface from the Function Tree. Step 2 Right-click Port, and choose Reset PPP from the shortcut menu. A dialog box is displayed, indicating that the operation will interrupt the services. Step 3 Click Yes. A dialog box is displayed, indicating that the operation was successful. Step 4 Click Close. ----End

10.2 Configuring PDH Interfaces

This section describes how to set the attributes of PDH interfaces. In a PSN network, the PDH interfaces can be used to carry TDM signals, IMA signals, or tunnels, depending on different settings of the interface attributes. The attributes of a PDH interface include the general attributes, layer 2 attributes, layer 3 attributes and advanced attributes.

Context
The application scenario of a PDH interface depends on the setting of the interface attributes. For details, refer to Table 10-3. Table 10-3 Application scenario of PDH interfaces Application Scenario Carrying the CES service Carrying the ATM service Carrying the tunnel Interface Type E1 interface E1 interface E1 interface Required Interface Attribute General attributes, Advanced attributes General attributes, Layer 2 attributes General attributes, Layer 3 attributes

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-13

10 Configuring Interfaces
NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

When the E1 interface is used to carry the CES service, set the general attributes and an advanced attribute, that is, frame format, to ensure that the frame format is the same as the service encapsulation format. When the emulation mode of a CES service is CESoPSN, it is recommended that you set the frame format at the interface to CRC-4 multiframe. When the emulation mode of a CES service is SAToP, the frame format at the interface should be set to non-framing. When the E1 interface is used to carry the ATM service, the Layer 2 attributes should be set. In addition, the IMA group should be created. When setting the layer 2 attributes of the E1 interface, set Port Mode to Layer 2 in 10.2.1 Setting General Attributes of PDH Interfaces. When the E1 interface is used to carry the tunnels, the Layer 3 attributes should be set. In addition, create the ML-PPP group, and configure the interface as an ML-PPP member.

Follow the procedure shown in Figure 10-2 to configure a PDH interface. Figure 10-2 Procedure for configuring a PDH interface
Carry CES service Carry ATM service Carry Tunnel

Start

Start

Start

Configure general attributes

Configure general attributes

Configure general attributes

Configure advanced attributes

Configure advanced attributes

Configure layer 3 attributes

End

End

Configure advanced attributes

End

Required

Optional

10.2.1 Setting General Attributes of PDH Interfaces Before you create services, you need to set the general attributes of the corresponding PDH interfaces. The general attributes of a PDH interface define the related information of the physical layer. 10.2.2 Setting the Layer 3 Attributes of PDH Interfaces Before you run PPP on a PDH interface, you need to set the layer 3 attributes of the PDH interface. The layer 3 attributes of a PDH interface define the related attributes of the network layer. 10.2.3 Setting the Advanced Attributes of PDH Interfaces The advanced attributes of PDH interfaces include frame format, line encoding format and loopback mode. 10.2.4 Querying the Running Status of PPP
10-14 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

In the case of a network failure, you can query the running status of the PPP to analyze the cause of the failure. 10.2.5 Resetting the PPP In the case of a network failure, you can reset the PPP to enable the PPP ports on the two ends of a link to re-negotiate.

10.2.1 Setting General Attributes of PDH Interfaces

Before you create services, you need to set the general attributes of the corresponding PDH interfaces. The general attributes of a PDH interface define the related information of the physical layer.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > PDH Interface from the Function Tree. Step 2 Select the desired board. Step 3 Set the parameters as required.

NOTE

Note the following issues during parameter settings:

l l l l

When Port Mode is set to Layer 1, Encapsulation Type does not support the settings. In this case, TDM services can be accessed. When Port Mode is set to Layer 2, Encapsulation Type supports ATM only. In this case, ATM services can be accessed. If the PDH interface is used for the inband DCN, the Port Mode cannot be set to Layer 1 or Layer 2. If you set Port Mode to Layer 3, select Null or PPP for Encapsulation Type. If you select Null, the interface does not enable the PPP protocol, and thus the equipment bears less load. If you select PPP, the interface can carry the MPLS. In the case an NNI interface,Max Data Packet Size(byte) must be larger than 960. A DCN packet contains a maximum of 960 bytes. If Max Data Packet Size(byte) is smaller than 960, the DCN packets in the receive direction may be lost.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

10.2.2 Setting the Layer 3 Attributes of PDH Interfaces

Before you run PPP on a PDH interface, you need to set the layer 3 attributes of the PDH interface. The layer 3 attributes of a PDH interface define the related attributes of the network layer.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 10-15

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Prerequisite
l l l

You must be an NM user with "NE operator" authority or higher. In General Attributes, Port Mode must be set to Layer 3. In General Attributes, Encapsulation Type must be set to PPP.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > PDH Interface from the Function Tree. Step 2 Click the Layer 3 Attributes tab. Step 3 Select the desired board and set the parameters as required.
NOTE

Note the following issues during parameter settings:

l

Max Reserved Bandwidth indicates the bandwidth used by tunnels. The total maximum reserved bandwidth of the tunnel carried by port should be not more than the physical bandwidth of the port.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

10.2.3 Setting the Advanced Attributes of PDH Interfaces

The advanced attributes of PDH interfaces include frame format, line encoding format and loopback mode.

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

Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > Interface Management > PDH Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Select the board to be configured and set the parameters as required.

10-16

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

10 Configuring Interfaces

If the E1 interface carries the CES service whose emulation mode is CESoPSN, Frame Format of the interfaces can be set to Double Frame or CRC-4 Multiframe. It is recommended that you set Frame Format to CRC-4 Multiframe. If the emulation mode of the CES service is SAToP, Frame Format of the interface must be set to Unframe. If the E1 interface carries the ATM service, Frame Format of the interface can be set to Double Frame or CRC-4 Multiframe. In the case of the OptiX PTN 3900, OptiX PTN 1900, OptiX PTN 950, or OptiX PTN 910, Frame Mode of the packets at the PDH interface can be set to 30 or 31. In the case of the OptiX PTN 912, Frame Mode of the packets at the PDH interface can be set only to 30. In hybrid networking, make sure that the frame modes of the local port and opposite port should be the same.
l l

30: In the E1 frame format, timeslots 1-15 and 17-31 are used to transport service data. 31: In the E1 frame format, timeslots 1-31 are used to transport service data.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

10.2.4 Querying the Running Status of PPP

In the case of a network failure, you can query the running status of the PPP to analyze the cause of the failure.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The encapsulation type of the created PDH interface must be PPP.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > PDH Interface from the Function Tree. Step 2 Select Port, right-click, and choose Query PPP Running Status from the shortcut menu. The PPP Running Status dialog box is displayed. Step 3 Click Close. ----End

10.2.5 Resetting the PPP

In the case of a network failure, you can reset the PPP to enable the PPP ports on the two ends of a link to re-negotiate.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The encapsulation type of the created PDH interface must be PPP.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 10-17

Issue 01 (2009-06-30)

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Context

CAUTION
Resetting the PPP will interrupt services.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > PDH Interface from the Function Tree. Step 2 Right-click Port, and choose Reset PPP from the shortcut menu. A dialog box is displayed, indicating that the operation will interrupt the services. Step 3 Click Yes. A dialog box is displayed, indicating that the operation was successful. Step 4 Click Close. ----End

10.3 Configuring Ethernet Interfaces

This section describes how to set the attributes of Ethernet interfaces. In a PSN network, the Ethernet interfaces can be used to carry Ethernet packets or tunnels, depending on different settings of the interface attributes. The attributes of the Ethernet interface include the general attributes, Layer 2 attributes, Layer 3 attributes, advanced attributes and flow control.

Context
The application scenario of an Ethernet interface depends on the setting of the interface attributes. For details, refer to Table 10-4. Table 10-4 Application scenario of Ethernet interfaces Application Scenario Accessing the Ethernet service Carrying the QinQ Link Carrying the tunnel Interface Type Ethernet interface Ethernet interface Ethernet interface Required Interface Attribute General attributes, Layer 2 attributes General attributes, Layer 2 attributes General attributes, Layer 3 attributes

10-18

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

10 Configuring Interfaces

When the Ethernet interface is used to carry the QinQ Link, the configuration procedure is similar to the configuration procedure when the Ethernet interface is used to carry the Ethernet service. In this case, however, the encapsulation types are different. For details, see 10.3.2 Setting the Layer 2 Attributes of Ethernet Interfaces.

Follow the procedure shown in Figure 10-3 to configure an Ethernet interface. Figure 10-3 Procedure for configuring an Ethernet interface
Carry Ethernet Packets Carry Tunnel

Start

Start

Configure general attributes

Configure general attributes

Configure layer 2 attributes

Configure layer 3 attributes

Configure advanced attributes

Configure advanced attributes

Configure flow control

Configure flow control

End

End

Required

Optional

10.3.1 Setting the General Attributes of Ethernet Interfaces Before you configure the layer 2 and layer 3 attributes of an Ethernet interface, you need to configure the general attributes of the corresponding Ethernet interface. The general attributes of an Ethernet interface define the physical-layer information, such as the port mode, encapsulation type, and maximum frame length. 10.3.2 Setting the Layer 2 Attributes of Ethernet Interfaces After the layer 2 attributes of an Ethernet interface are set, the interface can be used for connecting to the client-side equipment at the edge of a PSN network or for forwarding Ethernet packets
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 10-19

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

within the PSN network. The Layer 2 attributes of an Ethernet interface define the related information of the data link layer. 10.3.3 Setting the Layer 3 Attributes of an Ethernet Interface When an Ethernet interface is used to carry a tunnel, you need to configure the layer 3 attributes of the Ethernet interface. The layer 3 attributes of an Ethernet interface define the related attributes of the network layer. 10.3.4 Setting the Advanced Attributes of Ethernet Interfaces The routine maintenance parameters can be set through setting the advanced attributes of Ethernet interfaces. 10.3.5 Configuring Flow Control In the case that the flow control function is enabled, if congestion occurs on the link, the Ethernet interface sends a PAUSE frame to the opposite end, and then the opposite end stops transmitting Ethernet packets. As a result, congestion is avoided.

10.3.1 Setting the General Attributes of Ethernet Interfaces

Before you configure the layer 2 and layer 3 attributes of an Ethernet interface, you need to configure the general attributes of the corresponding Ethernet interface. The general attributes of an Ethernet interface define the physical-layer information, such as the port mode, encapsulation type, and maximum frame length.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the General Attributes tab. Step 3 Select the desired board and set the parameters as required.

NOTE

l l l l

When Port Mode is set to Layer 2, the Encapsulation Type support Null, 802.1Q and QinQ. When Port Mode is set to Layer 3, the Encapsulation Type support 802.1Q, and then the interface can be used by tunnel. When Port Mode is set to Layer Mix, the port can carry layer 2 services and layer 3 services. To create a VLAN sub-interface, set the port mode to Layer Mix. Before changing Layer 3 to Layer Mix, make sure that route protocols, such as IGP-ISIS, OSPF, and RIP, are not enabled on the port. Before changing Layer Mix to Layer 3, make sure that no VLAN tag is added to the port and no Layer 2 service is configured on the port. In the case an NNI interface,Max Data Packet Size(byte) must be larger than 960. A DCN packet contains a maximum of 960 bytes. If Max Data Packet Size(byte) is smaller than 960, the DCN packets in the receive direction may be lost.

10-20

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

10.3.2 Setting the Layer 2 Attributes of Ethernet Interfaces

After the layer 2 attributes of an Ethernet interface are set, the interface can be used for connecting to the client-side equipment at the edge of a PSN network or for forwarding Ethernet packets within the PSN network. The Layer 2 attributes of an Ethernet interface define the related information of the data link layer.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. In General Attributes, Port Mode must be set to Layer 2.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Layer 2 Attributes tab. Step 3 Select the desired board and set the parameters as required.

NOTE

Note the following issues during parameter settings:

l l l

QinQ Type Domain can be set only when Encapsulation Type is QinQ. TAG can be set only when Encapsulation Type is 802.1Q. Default VLAN ID and VLAN Priority are valid when TAG is access or hybrid.

Step 4 Click Apply. Click OK, The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

10.3.3 Setting the Layer 3 Attributes of an Ethernet Interface

When an Ethernet interface is used to carry a tunnel, you need to configure the layer 3 attributes of the Ethernet interface. The layer 3 attributes of an Ethernet interface define the related attributes of the network layer.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-21

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. In General Attributes, Port Mode must be set to Layer 3.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Layer 3 Attributes tab. Step 3 Select the desired board and set the parameters as required.
NOTE

Note the following issues during parameter settings:

l l

Max Reserved Bandwidth indicates the bandwidth used by tunnels. The total maximum reserved bandwidth of the tunnels carried by port cannot exceed the physical bandwidth of the port. When modifying the IP address of the interface, make sure that the IP address of this interface and the IP addresses of other interfaces configured with services are not in the same subnet.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

10.3.4 Setting the Advanced Attributes of Ethernet Interfaces

The routine maintenance parameters can be set through setting the advanced attributes of Ethernet interfaces.

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

Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Select the board to be configured and set the parameters as required. Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

10-22

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

10.3.5 Configuring Flow Control

In the case that the flow control function is enabled, if congestion occurs on the link, the Ethernet interface sends a PAUSE frame to the opposite end, and then the opposite end stops transmitting Ethernet packets. As a result, congestion is avoided.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Flow Control tab. Step 3 Select the desired board and set the parameters as required. Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

10.4 Configuring ADSL Interfaces

This topic describes how to configure ADSL interfaces. ADSL interfaces are used to carry offload services. The configuration of the ADSL interface includes the basic attributes of the interface, VPI/VCI of the interface, and enabling status of the tunnel at the virtual interface. After configuring the ADSL interface, you can configure offload services. 10.4.1 Process of Configuring an ADSL Interface The configuration process defines the tasks and the sequence in which the tasks should be finished. 10.4.2 Setting the General Attributes of an ADSL Interface The general attributes of the ADSL interface define the related information at the physical layer. 10.4.3 Configuring the VPI/VCI of an ADSL Interface The VPI/VCI of an ADSL interface is used to identify service flows of offload services. After AAL5 adaptation, the ATM encapsulation is performed to an accessed packet. The VPI/VCI is used during the ATM encapsulation.

10.4.1 Process of Configuring an ADSL Interface

The configuration process defines the tasks and the sequence in which the tasks should be finished. Follow the procedure shown in Figure 10-4 to configure the ADSL interface attributes.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-23

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 10-4 Process of configuring the ADSL interface

Start

Configure and query general attributes of an ADSL interface

Configure VPI/VCI

Configure and query general attributes of a virtual Interface

Configure layer3 attributes of an Ethermet virtual interface

End

Required Optional

Table 10-5 Tasks of configuring the ADSL interface Tasks Configure and query general attributes of an ADSL interface Configure VPI/VCI for the interface Configure and query general attributes of a virtual interface
10-24

Remarks Specify a port name.

Configure VPI/VCI for the interface according to service requirements so that cells can be transported between the interface and DSLAM. Specify a port name, set the port mode, and query the bound board, bound port, and interface MAC address.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Tasks Create a VLAN subinterface

Remarks Create a VLAN sub-interface and set the port VLAN ID so that the service can pass through a third-party Layer 2 network. When creating a VLAN sub-interface, make sure that the port mode is set to Layer Mix.

Configure layer 3 attributes of an Ethernet virtual interface

Set the IP address of the interface and enable the tunnel. When setting Layer 3 attributes is complete, you can create a tunnel to carry services.

10.4.2 Setting the General Attributes of an ADSL Interface

The general attributes of the ADSL interface define the related information at the physical layer.

Prerequisite
You must be an NM user with "NE operator" authority or higher. Applies to OptiX PTN 912. Make sure that the port is activated before setting the general attributes of the ADSL interface.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > DSL Interface > ADSL Interface from the Function Tree. Step 2 Click the General Attributes tab and set the parameters as required. Step 3 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 4 Click Close. ----End

10.4.3 Configuring the VPI/VCI of an ADSL Interface

The VPI/VCI of an ADSL interface is used to identify service flows of offload services. After AAL5 adaptation, the ATM encapsulation is performed to an accessed packet. The VPI/VCI is used during the ATM encapsulation.

Prerequisite
You must be an NM user with "NE operator" authority or higher. Applies to OptiX PTN 912.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-25

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > DSL Interface > ADSL Interface from the Function Tree. Step 2 Click Configure VPI/VCI in the VPI/VCI Configuration tab. The Configure VPI/VCI dialog box is displayed.
NOTE

VPI/VCI 1/39 is a reserved PVC pair. Do not set VPI/VCI for an ADSL interface to 1/39. By default, eight VPI/VCI pairs are configured on the equipment. During service transmission, if the VPI/ VCI of the opposite DSLAM is consistent with any of the eight default VPI/VCI pairs, the ADS2A board automatically delivers configuration by matching the default eight VPI/VCI pairs. In this case, manual configuration of the VPI/VCI is unnecessary. If the VPI/VCI of the opposite DSLAM is consistent with none of the eight default VPI/VCI pairs, manually configure the VPI/VCI. The default VPI/VCI pairs of the equipment are 0/35, 8/35, 0/32, 8/32, 0/33, 8/33, 1/32 and 1/35.

Step 3 In the Configure VPI/VCI dialog box, select a port and set VPI and VCI for the port.

Step 4 Click Apply. ----End

10.5 Configuring G.SHDSL Interfaces

This section describes how to configure the G.SHDSL interface, which carries the Offload service. The G.SHDSL interface can carry the Offload service by adopting three working modes, that is, ATM mode, IMA mode and EFM mode. The SHD4 board supports the ATM mode and EFM mode. The SHD4I supports the IMA mode. Configure attributes for the G.SHDSL interface according to the encapsulation mode so that the G.SHDSL interface can transmit the Offload service.
10-26 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

10.5.1 Application of the G.SHDSL Interface This section describes the single-pair high-speed digital subscriber line (SHDSL) technology and the three working modes of the G.SHDSL interface. 10.5.2 Process of Configuring a G.SHDSL Interface The configuration process defines the tasks and the sequence in which the tasks should be finished. To configure a G.SHDSL interface, you need to configure the interface in ATM mode, EFM mode, or IMA mode. 10.5.3 Setting the BIS Mode of a G.SHDSL Interface The G.SHDSL interface of PTN equipment supports the SHDSL.BIS protocol. By default, the BIS mode is enabled. When the DSLAM connected to the PTN equipment does not support the SHDSL.BIS protocol, you need to disable the BIS mode for the SHD4 board. 10.5.4 Setting the General Attributes of G.SHDSL Interfaces Before configuring offload services, you need to configure general attributes of a G.SHDSL interface on the desired board. The general attributes include Name, Port Mode, Line Up Rate (k), Line Down Rate(k), and Line Protocol. The general attributes of the G.SHDSL interface define the related information at the physical layer. 10.5.5 Setting the Bound Mode for a G.SHDSL Interface The SHD4 board supports the EFM bound mode and the ATM bound mode. The physical bearer mode for transmitting Offload services varies with the bound mode of the interface. 10.5.6 Querying the EFM Bound Group of a G.SHDSL Interface The EFM bound group converges the G.SHDSL interfaces into an EFM interface. The EFM interface works as the traffic interface of offload services. 10.5.7 Configuring an ATM Bound Group When the bound mode of the SHD4 board is set to the ATM mode, you should set the relevant information about the ATM bound group for the transmission of Offload services. 10.5.8 Configuring an IMA Bound Group In the offload scenario, the SHD4I board can be configured on the equipment so that the equipment is interconnected with DSLAM through IMA. Set VPI/VCI of the interface for cell switching.

10.5.1 Application of the G.SHDSL Interface

This section describes the single-pair high-speed digital subscriber line (SHDSL) technology and the three working modes of the G.SHDSL interface.

SHDSL Technology
SHDSL refers to a new symmetric digital subscriber line (DSL) technology that is based on high-speed DSL (HDSL), symmetric DSL (SDSL), and HDSL2, and also refers to the singlepair symmetric DSL standard defined by ITU-T in G.991.2. SHDSL adopts the trellis coded pulse amplitude modulation (TC-PAM) technology on the plain twisted pairs to transmit high-speed data and thus to provide a broadband access approach. SHDSL.bis enhances SHDSL and supports all the features that SHDSL has. The SHD4 board supports SHDSL.bis and SHDSL. By enabling or disabling BIS for the SHD4 board, the SHD4 board can be interconnected with DSLAM. G.SHDSL is widely used in the scenarios such as symmetric high-speed data service, video conference service, and voice over DSL (VoDSL).
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 10-27

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Working Modes of the G.SHDSL Interface

The OptiX PTN equipment supports three working modes of the G.SHDSL interface, that is, ATM mode, EFM mode, and IMA mode. The SHD4 board supports the ATM mode and EFM mode. The SHD4I supports the IMA mode. In the three working modes, the G.SHDSL interface has the following features:
l

In ATM mode, one service is diverted to multiple lines. If one line becomes faulty, the entire service is interrupted. When the G.SHDSL interface works in ATM mode, the lines can be manually bound in M-Pair mode. In this case, the number of bound pairs should be consistent with the number of bound pairs at DSLAM on the central office (CO) side. In EFM mode, the service overhead is used to monitor the physical service links. When one link becomes faulty, the service is automatically diverted to other links. In this case, when the service traffic is lower than the available bandwidth of the interface, the service is not interrupted. When the G.SHDSL interface works in EFM mode, the line binding at the interface is the same as the CO-side line binding and you do not need to configure the line binding on the board. In IMA mode, the ATM cells are inversely multiplexed to multiple SHDSL links at the local end and the multiple SHDSL links are combined to recover the ATM cells in the original sequence at the opposite end. In this manner, multiple low-speed links can be multiplexed in a flexible manner. When one line becomes faulty, the service is automatically diverted to other lines and the service is still available. When the G.SHDSL interface works in IMA mode, a certain number of pairs should be bound to form an IMA group. The number of member pairs at the interface should be the same as the number of bound pairs on the CO side.

Application of the G.SHDSL Interface

The SHDSL line features high bandwidth but low cost, and thus is applicable to transporting the 3G HSDPA service. Figure 10-5 provides an example of the service in the offload solution based on ETH forwarding. This example shows how the SHD4/SHD4I transports the HSDPA service. The OptiX PTN equipment on the access side performs PW emulation for the ATM cells and encapsulates the ATM packets in Ethernet packets. The xDSL board (SHD4 or SHD4I) performs AAL5 adaptation and ATM encapsulation (IMA or EFM encapsulation) for the Ethernet packets, and transports the packets to DSLAM. Then, DSLAM terminates the xDSL encapsulation layer and transports the Ethernet packets to the Layer 2 ETH switching network. The OptiX PTN 3900 on the convergence side receives the Ethernet packets and decapsulates the Ethernet packets to recover the ATM packets.

10-28

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Figure 10-5 Application scenario of the G.SHDSL interface

ATM
PWE3 PW Label LSP Label Ethernet AAL5 ATM SHDSL
ATM/IMA Mode

ATM
PWE3 PW Label LSP Label Ethernet EFM SHDSL
EFM Mode

ATM PWE3 PW Label LSP Label Ethernet

ATM PWE3 PW Label LSP Label Ethernet

HSDPA flow

DSLAM

Wholesale xDSL service

NodeB

OptiX PTN 912

R99 flow PTN

OptiX PTN 3900

RNC

10.5.2 Process of Configuring a G.SHDSL Interface

The configuration process defines the tasks and the sequence in which the tasks should be finished. To configure a G.SHDSL interface, you need to configure the interface in ATM mode, EFM mode, or IMA mode.

Context
NOTE

Before you configure a G.SHDSL interface, set the BIS mode depending on whether the opposite DSLAM supports the SHDSL.BIS protocol. By default, the BIS mode is enabled for the board. If the opposite DSLAM does not support the SHDSL.BIS protocol, you need to disable the BIS mode. For details, see 10.5.3 Setting the BIS Mode of a G.SHDSL Interface.

ATM Mode
When the G.SHDSL interface works in ATM mode, configure the G.SHDSL interface according to Figure 10-6.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-29

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 10-6 Process of configuring the G.SHDSL interface

Start

Enable or disable the BIS for the interface

Configure and query general attributes of a G.SHDSL interface

Configure interface bound mode

Configure attributes of ATM bound group

Configure and query general attributes of a virtual Interface

Create a VLAN sub interface

Configure layer3 attributes of an Ethermet virtual interface Required End Optional

10-30

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Table 10-6 Tasks of configuring the G.SHDSL interface in ATM mode Tasks Enable or disable the BIS for the interface Remarks Enable or disable the BIS for the SHD4 board according to the BIS status of DSLAM that is connected to the SHD4 board. By default, the BIS is enabled for the SHD4 board. Configure and query general attributes of a G.SHDSL interface Specify a port name, enable the port, and query the status, line uplink rate, link downlink rate, and line protocol of the port. Before configuring a service for the port, make sure that the port is activated. Set the bound mode of the interface to ATM mode according to service requirements. Set the pair mode of the interface, enable the PVC numbering, and configure VPI/VCI. Specify a port name, set the port mode, and query the bound board, bound port, and interface MAC address. Create a VLAN sub-interface and set the port VLAN ID so that the service can pass through a third-party Layer 2 network. When creating a VLAN sub-interface, make sure that the port mode is set to Layer Mix. Configure layer 3 attributes of an Ethernet virtual interface Set the IP address of the interface and enable the tunnel. When setting Layer 3 attributes is complete, you can create a tunnel to carry services.

Configure interface bound mode Configure attributes of ATM bound group Configure and query general attributes of a virtual interface Create a VLAN subinterface

EFM Mode
When the G.SHDSL interface works in EFM mode, configure the G.SHDSL interface according to Figure 10-7.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-31

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 10-7 Process of configuring the G.SHDSL interface

Start

Enable or disable the BIS for the interface

Configure and query general attributes of a G.SHDSL interface

Configure interface bound mode

Query attributes of EFM bound group

Configure and query general attributes of a virtual Interface

Create a VLAN sub interface

Configure layer3 attributes of an Ethermet virtual interface Required End Optional

10-32

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Table 10-7 Tasks of configuring the G.SHDSL interface in EFM mode Task Enable or disable the BIS for the interface Remarks Enable or disable the BIS for the SHD4 board according to the BIS status of DSLAM that is connected to the SHD4 board. By default, the BIS is enabled for the SHD4 board. Configure and query general attributes of a G.SHDSL interface Specify a port name, enable the port, and query the status, line uplink rate, link downlink rate, and line protocol of the port. Before configuring a service for the port, make sure that the port is activated. Set the bound mode of the interface to EFM mode according to service requirements. Query the bound ports of the bound group and status of the bound ports. Specify a port name, set the port mode, and query the bound board, bound port, and interface MAC address. Create a VLAN sub-interface and set the port VLAN ID so that the service can pass through a third-party Layer 2 network. When creating a VLAN sub-interface, make sure that the port mode is set to Layer Mix. Configure layer 3 attributes of an Ethernet virtual interface Set the IP address of the interface and enable the tunnel. When setting Layer 3 attributes is complete, you can create a tunnel to carry services.

Configure interface bound mode Query attributes of EFM bound group Configure and query general attributes of a virtual interface Create a VLAN subinterface

IMA Mode
When the G.SHDSL interface works in IMA mode, configure the G.SHDSL interface according to Figure 10-8.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-33

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 10-8 Process of configuring the G.SHDSL interface

Start

Configure and query general attributes of a G.SHDSL interface

Configure VPI/VCI of the interface

Configure attributes of the IMA group

Configure and query general attributes of a virtual Interface

Create a VLAN sub interface

Configure layer3 attributes of an Ethermet virtual interface Required Optional

End

Table 10-8 Tasks of configuring the G.SHDSL interface in IMA mode Tasks Configure and query general attributes of a G.SHDSL interface Remarks Specify a port name, enable the port, and query the status, line uplink rate, link downlink rate, and line protocol of the port. Before configuring a service for the port, make sure that the port is activated. Configure VPI/VCI for the interface according to service requirements so that cells can be transported between the interface and DSLAM.
Issue 01 (2009-06-30)

Configure VPI/VCI for the interface

10-34

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Tasks Configure attributes of the IMA group Configure and query general attributes of a virtual interface Create a VLAN subinterface

Remarks Add ports to the IMA group, configure the attributes of the IMA group and enable the IMA protocol so that the interface can be interconnected to the DSLAM through IMA. Specify a port name, set the port mode, and query the bound board, bound port, and interface MAC address. Create a VLAN sub-interface and set the port VLAN ID so that the service can pass through a third-party Layer 2 network. When creating a VLAN sub-interface, make sure that the port mode is set to Layer Mix.

Configure layer 3 attributes of an Ethernet virtual interface

Set the IP address of the interface and enable the tunnel. When setting Layer 3 attributes is complete, you can create a tunnel to carry services.

10.5.3 Setting the BIS Mode of a G.SHDSL Interface

The G.SHDSL interface of PTN equipment supports the SHDSL.BIS protocol. By default, the BIS mode is enabled. When the DSLAM connected to the PTN equipment does not support the SHDSL.BIS protocol, you need to disable the BIS mode for the SHD4 board.

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

Procedure
Step 1 In the NE Explorer, select the SHD4 board and choose Configuration > BIS Mode Setting > BIS Mode from the Function Tree. Step 2 In the right-hand pane, select the SHD4 board and set Enabled Status. Step 3 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 4 Click Close. ----End

10.5.4 Setting the General Attributes of G.SHDSL Interfaces

Before configuring offload services, you need to configure general attributes of a G.SHDSL interface on the desired board. The general attributes include Name, Port Mode, Line Up Rate (k), Line Down Rate(k), and Line Protocol. The general attributes of the G.SHDSL interface define the related information at the physical layer.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-35

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. Make sure that the port is activated before setting the general attributes of the SHDSL interface. Applies to OptiX PTN 912.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > DSL Interface > G.SHDSL Interface from the Function Tree. Step 2 Click the General Attributes tab and set the parameters as required.

Step 3 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 4 Click Close. ----End

10.5.5 Setting the Bound Mode for a G.SHDSL Interface

The SHD4 board supports the EFM bound mode and the ATM bound mode. The physical bearer mode for transmitting Offload services varies with the bound mode of the interface.

Prerequisite
You must be an NM user with "NE operator" authority or higher. Applies to OptiX PTN 912.

Context
In the ATM mode, the outgoing lines of four G.SHDSL interfaces support the M-Pair binding of lines. In addition, M can be 1, 2, 3, or 4. Multiple single-pairs are bound together and services are divided to several lines. Hence, the bandwidth used for transmitting services is increased. In the M-Pair mode, if a line is faulty, the services are interrupted. In EFM mode, the service is transported over the egress lines of the four G.SHDSL interfaces. By adding physical link overhead to the service, the link quality can be monitored. When one line becomes faulty, the service is automatically diverted to other lines. In this manner, the service is still available when the service traffic is lower than the available bandwidth of the interface. In ATM mode, the number of pairs to be bound is manually set; in EFM mode, the number of pairs to be bound is based on negotiation. In either mode, the pair sequence of the interface should be consistent with the pair sequence of DSLAM. In ATM mode:
10-36 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

l l l l

10 Configuring Interfaces

When the number of bound pairs is 1, only the first G.SHDSL interface is available. When the number of bound pairs is 2, only the first two G.SHDSL interfaces are available. When the number of bound pairs is 3, only the first three G.SHDSL interfaces are available. When the number of bound pairs is 4, all the four G.SHDSL interfaces are available.

In EFM mode:
l l l l

When the number of bound pairs is 1, only the first G.SHDSL interface is available. When the number of bound pairs is 2, only the first two G.SHDSL interfaces are available. When the number of bound pairs is 3, only the first three G.SHDSL interfaces are available. When the number of bound pairs is 4, all the four G.SHDSL interfaces are available.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > DSL Interface > G.SHDSL Interface from the Function Tree. Step 2 Click the Bound Mode tab, and set the Bound Mode of the interface according to the service required.

CAUTION
When services are carried on boards, you cannot switch the bound mode. Step 3 Click Apply. A prompt is displayed indicating that the operation is successful. Step 4 Click Close. ----End

10.5.6 Querying the EFM Bound Group of a G.SHDSL Interface

The EFM bound group converges the G.SHDSL interfaces into an EFM interface. The EFM interface works as the traffic interface of offload services.

Prerequisite
You must be an NM user with "NE monitor" authority or higher. Applies to OptiX PTN 912/910/950. Bound Mode must be set to EFM.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-37

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > DSL Interface > G.SHDSL Interface from the Function Tree. Step 2 In the EFM Bound Group tab, click Query to check the port binding information of the EFM bound group. ----End

10.5.7 Configuring an ATM Bound Group

When the bound mode of the SHD4 board is set to the ATM mode, you should set the relevant information about the ATM bound group for the transmission of Offload services.

Prerequisite
You must be an NM user with "NE operator" authority or higher. Bound Mode must be set to ATM.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > DSL Interface > G.SHDSL Interface from the Function Tree. Step 2 Click the ATM Bound Group tab and set the Pair Mode of the interface.

NOTE

The OptiX PTN equipment supports the binding of lines in the M-Pair mode. M can be 1, 2, 3, or 4, which indicates that one, two, three, or four lines connected to the four interfaces of the SDH4 can be bound as one ATM bound group.

Step 3 Set the Enable PVC. According to the value of the PVC pair at the opposite end, select the PVC pair of the same value. Then, click Apply. Step 4 Optional: In the bottom portion of the window, click Configure VPI/VCI. Set the VPI/VCI value of the bound group.
NOTE

For Enable PVC, you can enable the eight default PVC pairs. During service transmission, if the VPI/VCI of the PVC pair on the opposite DSLAM is consistent with any of the eight default PVC pairs, enable the PVC pair. For VPI/VCI Configuration, any of the eight default PVC pairs can be modified. During service transmission, if the VPI/VCI of the PVC pair on the opposite DSLAM is consistent with none of the eight default PVC pairs, modify the VPI/VCI of any PVC to the same as that of the opposite DSLAM.

10-38

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Step 5 Click Apply. A prompt is displayed indicating that the operation is successful. Step 6 Click Close. ----End

10.5.8 Configuring an IMA Bound Group

In the offload scenario, the SHD4I board can be configured on the equipment so that the equipment is interconnected with DSLAM through IMA. Set VPI/VCI of the interface for cell switching.

Prerequisite
You must be an NM user with "NE operator" authority or higher. Applies to SHD4I board.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > DSL Interface > G.SHDSL Interface from the Function Tree. Step 2 Click IMA Bound Group tab, and click Configure VPI/VCI to configure the interface VPI/ VCI.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-39

10 Configuring Interfaces
NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

The VPI/VCI values of the interface should be the same as the VPI/VCI values of DSLAM that is connected to the interface.

Step 3 Click Apply. ----End

10.6 Configuring Microwave Interfaces

This section describes how to configure the IF 1+1 protection of the IF board, the IF/ODU information of the radio link, microwave interface attributes, and ODU interface parameters.

Context
The application scenario of an microwave interface depends on the setting of the interface attributes. For details, refer to Table 10-9. Table 10-9 Application scenario of microwave interfaces Interface Attributes Layer 2 attributes Layer 3 attributes Signal to Carry Ethernet packets Tunnels Functioning Location UNI side or NNI side NNI side

NOTE

When the microwave interface is used to carry the QinQ Link, the configuration procedure is similar to the configuration procedure when the microwave interface is used to carry the Ethernet service. In this case, however, the encapsulation types are different. For details, see 10.6.3 Setting the Layer 2 Attributes of Microwave Interfaces.

Follow the procedure shown in Figure 10-9 to configure an microwave interface.

10-40

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Figure 10-9 Procedure for configuring an microwave interface

Carry Ethernet Packets Carry Tunnel

Start

Start

Creating IF 1+1 Protection

Creating IF 1+1 Protection

Configuring the IF/ ODU Information of a Radio Link

Configuring the IF/ ODU Information of a Radio Link

Setting the General Attributes

Setting the General Attributes

Setting the IF Attributes

Setting the IF Attributes

Setting the Layer 2 Attributes

Setting the Layer 3 Attributes

Setting the Advanced Attributes

Setting the Advanced Attributes

Setting the Parameters of ODU Ports

Setting the Parameters of ODU Ports

End

End

Required Optional

10.6.1 Setting the General Attributes of Microwave Interfaces Before you configure the layer 2 and layer 3 attributes of an microwave interface, you need to configure the general attributes of the corresponding microwave interface. The general attributes of an microwave interface define the physical-layer information, such as the port mode, encapsulation type, and maximum frame length. 10.6.2 Setting the IF Attributes of Microwave Interfaces The IF information of the microwave interface specifies the relevant information of the IF board, including the AM attribute and ATPC attribute.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 10-41

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

10.6.3 Setting the Layer 2 Attributes of Microwave Interfaces After the layer 2 attributes of an microwave interface are set, the interface can be used for connecting to the client-side equipment at the edge of a PSN network or for forwarding Ethernet packets within the PSN network. The Layer 2 attributes of an microwave interface define the related information of the data link layer. 10.6.4 Setting the Layer 3 Attributes of Microwave Interfaces The layer 3 attributes of an microwave interface define the related attributes of the network layer. 10.6.5 Setting the Advanced Attributes of Microwave Interfaces The routine maintenance parameters can be set through setting the advanced attributes of microwave interfaces. 10.6.6 Setting the Parameters of ODU Ports This section describes how to set the parameters of ODU ports, including the RF attributes, power attributes, and advanced attributes of the ODU.

10.6.1 Setting the General Attributes of Microwave Interfaces

Before you configure the layer 2 and layer 3 attributes of an microwave interface, you need to configure the general attributes of the corresponding microwave interface. The general attributes of an microwave interface define the physical-layer information, such as the port mode, encapsulation type, and maximum frame length.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The IF board and the ODU that connects to the IF board must be added.

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Step 2 Click the General Attributes tab. Step 3 Select the desired board and set the parameters as required.
NOTE

l l l

When Port Mode is set to Layer 2, the Encapsulation Type support Null, 802.1Q and QinQ. When Port Mode is set to Layer 3, the Encapsulation Type support 802.1Q, and then the interface can be used by tunnel. In the case an NNI interface, MTU(byte), which indicates the maximum data packet length, must be set to a value larger than 960. A DCN packet contains a maximum of 960 bytes. If MTU(byte) is smaller than 960, the DCN packets in the receive direction may be lost.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

10-42

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

10.6.2 Setting the IF Attributes of Microwave Interfaces

The IF information of the microwave interface specifies the relevant information of the IF board, including the AM attribute and ATPC attribute.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The IF board and the ODU that connects to the IF board must be added.

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Step 2 Click the IF Attributes tab. Step 3 Select the desired board and set the parameters as required.
NOTE

When you set Assured Capacity Modulation and Full Capacity Modulation, note the following points: This parameter is valid only when Enable AM is set to Enable. When you set Manually Specified Modulation, note the following points: This parameter is valid only when Enable AM is set to Disable. When you set ATPC Upper Threshold(0.1dBm), note the following points: Generally, ATPC Upper Threshold(0.1dBm) should be 20 dB to 30 dB higher than ATPC Lower Threshold(0.1dBm), and must not be less than 15 dB. If the difference between the upper threshold and the lower threshold is big, the number of ATPC adjustments is reduced and the system load is also reduced. If the difference between the upper threshold and the lower threshold is small, the transmit power is adjusted in a timely manner and the interference to adjacent systems is reduced.

When you set ATPC Lower Threshold(0.1dBm), note the following points: Generally, set this parameter to a value of 10 dB or greater than the receiver sensitivity to prevent sudden fast fading because sudden fast fading makes the RSL value lower than the receiver sensitivity.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

10.6.3 Setting the Layer 2 Attributes of Microwave Interfaces

After the layer 2 attributes of an microwave interface are set, the interface can be used for connecting to the client-side equipment at the edge of a PSN network or for forwarding Ethernet packets within the PSN network. The Layer 2 attributes of an microwave interface define the related information of the data link layer.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The IF board and the ODU that connects to the IF board must be added.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 10-43

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Step 2 Click the Layer 2 Attributes tab. Step 3 Select the desired board and set the parameters as required.
NOTE

When you set QinQ Type Domain, note the following points: QinQ Type Domain can be set only when Encapsulation Type is QinQ.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

10.6.4 Setting the Layer 3 Attributes of Microwave Interfaces

The layer 3 attributes of an microwave interface define the related attributes of the network layer.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The IF board and the ODU that connects to the IF board must be added.

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Step 2 Click the Layer 3 Attributes tab. Step 3 Select the desired board and set the parameters as required.
NOTE

Note the following issues during parameter settings:

l l l

Max Reserved Bandwidth indicates the bandwidth used by tunnels. The total maximum reserved bandwidth of the tunnel that is carried by a port cannot exceed the physical bandwidth of the port. Modifying the IP address can cause the equipment to re-establish the link. As a result, the services are interrupted. When modifying the IP address of the interface, make sure that the IP address of this interface and the IP addresses of other interfaces configured with services are not in the same subnet.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End
10-44 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

10.6.5 Setting the Advanced Attributes of Microwave Interfaces

The routine maintenance parameters can be set through setting the advanced attributes of microwave interfaces.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The IF board and the ODU that connects to the IF board must be added.

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Select the desired board and set the parameters as required.
NOTE

When you set Radio Link ID, note the following points:
l l l

If this parameter is different from Received Link ID, the NE reports the MW_LIM alarm and inserts the AIS into the downstream. Set this parameter according to the planning. Each radio link of an NE should have a unique Link ID, and the Link IDs at both the ends of a radio link should be the same. Before performing the loopback operation for the IF board, disable the AM function at the two ends of a link.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

10.6.6 Setting the Parameters of ODU Ports

This section describes how to set the parameters of ODU ports, including the RF attributes, power attributes, and advanced attributes of the ODU.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The required IF boards must be added. The corresponding ODU must be added in the slot layout diagram.

Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Step 2 Click the Radio Frequency Attributes tab.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 10-45

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 3 Configure the TX frequency and T/R spacing.

NOTE

When you set Transmission Frequency (MHz), note the following points:
l l

The parameter specifies the channel center frequency. This parameter cannot be set to a value that is less than the minimum TX frequency supported by the ODU + 50% channel spacing or more than the maximum TX frequency supported by the ODU - 50% channel spacing. The difference between the TX frequencies of both the ends of a radio link is a T/R spacing. Set this parameter according to the planning.

l l l

When you set T/R Spacing (MHz), note the following points:
l

This parameter indicates the spacing between the TX power and receive power of the ODU. If Station Type of the ODU is TX high, the TX power is one T/R spacing higher than the receive power. If Station Type of the ODU is TX low, the TX power is one T/R spacing lower than the receive power. If the ODU supports only one T/R spacing, set this parameter to 0, indicating that the T/R spacing supported by the ODU is used. The T/R spacing of the ODU should be set to the same value at both the ends of a radio link.

l l

Step 4 Click Apply. Step 5 Click the Power Attributes tab. Step 6 Configure the TX power of the ODU.
NOTE

Note the following when setting the Transmit Power(dBm) parameters.

l l l

This parameter cannot be set to a value that exceeds the nominal power range supported by the ODU. The TX power of the ODU should be set to the same value at both the ends of a radio link. Set this parameter according to the planning.

Note the following when setting the TX High Threshold(dBm) and TX Low Threshold(dBm) parameters.
l

When the actual launched power of the ODU is higher than TX High Threshold(dBm), the system records the time when the actual launched power is higher than TX High Threshold(dBm) and the time when the actual launched power is higher than TX Low Threshold(dBm) as performance events. When the actual launched power of the ODU is within the range from TX Low Threshold(dBm) to TX High Threshold(dBm), the system records the time when the actual launched power of the ODU is higher than TX Low Threshold(dBm) as a performance event. When the actual launched power of the ODU is lower than TX Low Threshold(dBm), no record is saved. The TX High Threshold(dBm) and TX Low Threshold(dBm) parameters are valid only when the ATPC function is enabled. When the actual received power of the ODU is lower than RX Low Threshold(dBm), the system records the time when the actual received power is lower than RX High Threshold(dBm) and the time when the actual received power is lower than RX Low Threshold(dBm) as performance events. When the actual received power of the ODU is within the range from RX Low Threshold(dBm) to RX High Threshold(dBm), the system records the time when the actual received power of the ODU is higher than RX Low Threshold(dBm) as a performance event. When the actual received power of the ODU is higher than RX Low Threshold(dBm), no record is saved.

l l

Note the following when setting the RX High Threshold(dBm) and RX Low Threshold(dBm).
l

10-46

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Step 7 Click Apply. Step 8 Click the Advanced Attributes tab. Step 9 Set Configure Transmission Status. Step 10 Click Apply. ----End

10.7 Configuring Serial Interfaces

This topic describes how to set the attributes of serial interfaces. Currently, serial interfaces have two levels, which are VC12 level and 64 kbit/s timeslot level. If you create a serial interface at the VC12 level, you can use a certain E1 timeslot in a channelized STM-1 frame to carry tunnels. If you create a serial interface at the 64 kbit/s timeslot level, you can bind certain timeslots in an E1 frame to a path. Timeslots 0 and 16 in the E1 frame are used to transmit control words, signaling, and other information. You can bind 10 timeslots to form an ATM path to transmit ATM services or bind five timeslots to form a CES path to transmit CES services. In this way, an E1 signal can carry both CES and ATM services.

Context
Follow the procedure shown in Figure 10-10 to configure the serial interface attributes. Figure 10-10 Procedure for configuring a serial interface
Start

Create Serial interface

Configure general attributes

Configure layer 3 attributes

End

Required

Optional

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-47

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

10.7.1 Creating Serial Interfaces You can create a serial interface at the VC12 level or 64 kbit/s timeslot level. 10.7.2 Setting the General Attributes of a Serial Interface Before you set the layer 3 attributes of a serial interface, you need to set the general attributes of the serial interface. The general attributes of a serial interface define the related information of the physical layer. 10.7.3 Setting the Layer 3 Attributes of Serial Interfaces In a PSN network, the serial interfaces are used to transport the PPP-encapsulated packet data. The layer 3 attributes of a serial interface define the related attributes of the network layer. 10.7.4 Querying the Running Status of PPP In the case of a network failure, you can query the running status of the PPP to analyze the cause of the failure. 10.7.5 Resetting the PPP In the case of a network failure, you can reset the PPP to enable the PPP ports on the two ends of a link to re-negotiate.

10.7.1 Creating Serial Interfaces

You can create a serial interface at the VC12 level or 64 kbit/s timeslot level.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Serial Interface from the Function Tree. Step 2 Click New in the General Attributes tab and the New Serial Interface dialog box is displayed. Step 3 Set the parameters as required.

10-48

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

NOTE

l l

In the case of the serial interface at the VC12 level, currently a serial interface can be bound to only one timeslot. In the case of the serial interface at the 64 kbit/s level, when the E1 frame mode is 30, timeslots 0 and 16 are unavailable. When the E1 frame mode is 31, timeslot 0 is unavailable.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 5 Click Close. ----End

10.7.2 Setting the General Attributes of a Serial Interface

Before you set the layer 3 attributes of a serial interface, you need to set the general attributes of the serial interface. The general attributes of a serial interface define the related information of the physical layer.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. A serial interface must be created.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-49

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Serial Interface from the Function Tree. Step 2 Set the parameters as required.

NOTE

When you set Port Mode to Layer 2, Encapsulation Type is ATM. The serial interface supports IMA binding. When you set Port Mode to Layer 3, you can set Encapsulation Type to PPP or Null. When you set Encapsulation Type to PPP, you can add the serial interface to an MP group. The serial interfaces that are bound to the same MP group have the same E1 frame mode. When Encapsulation Type is Null, Port Mode can be changed to Layer 2. In the case an NNI interface,Max Data Packet Size (byte) must be larger than 960. A DCN packet contains a maximum of 960 bytes. If Max Data Packet Size (byte) is smaller than 960, the DCN packets in the receive direction may be lost.

Step 3 Click Apply. The Operation Result dialog box is displayed indicating that the operation was successful. Step 4 Click Close. ----End

10.7.3 Setting the Layer 3 Attributes of Serial Interfaces

In a PSN network, the serial interfaces are used to transport the PPP-encapsulated packet data. The layer 3 attributes of a serial interface define the related attributes of the network layer.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. In General Attributes, Encapsulation Type must be set to PPP.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Serial Interface from the Function Tree. Step 2 Click the Layer 3 Attributes tab and set the parameters as required.

10-50

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

10 Configuring Interfaces

Note the following issues during parameter settings:

l l l

Max Reserved Bandwidth indicates the bandwidth used by tunnels. The total maximum reserved bandwidth of the tunnels carried by port should be not more than the physical bandwidth of the port. Modifying the IP address can cause the equipment to re-establish the link. As a result, the services are interrupted. When changing Specify IP from Manually to Unnumbered IP, manually specify the invalid IP address (255.255.255.255) and invalid IP mask (255.255.255.255) to release the IP address manually specified. When modifying the IP address of the interface, make sure that the IP address of this interface and the IP addresses of other interfaces configured with services are not in the same subnet.

Step 3 Click Apply. The Operation Result dialog box is displayed indicating that the operation was successful. Step 4 Click Close. ----End

10.7.4 Querying the Running Status of PPP

In the case of a network failure, you can query the running status of the PPP to analyze the cause of the failure.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The encapsulation type of the created serial interface must be PPP.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Serial Interface from the Function Tree. Step 2 Select Port, right-click, and choose Query PPP Running Status from the shortcut menu. The PPP Running Status dialog box is displayed. Step 3 Click Close. ----End

10.7.5 Resetting the PPP

In the case of a network failure, you can reset the PPP to enable the PPP ports on the two ends of a link to re-negotiate.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The encapsulation type of the created serial interface must be PPP.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-51

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Context

CAUTION
Resetting the PPP will interrupt services.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Serial Interface from the Function Tree. Step 2 Right-click Port, and choose Reset PPP from the shortcut menu. A dialog box is displayed, indicating that the operation will interrupt the services. Step 3 Click Yes. A dialog box is displayed, indicating that the operation was successful. Step 4 Click Close. ----End

10.8 Configuring ML-PPP

This section describes how to configure Multilink PPP (MP) group. MP is a technology used to bind multiple PPP links to increase the bandwidth. MP is applied to the interface that supports PPP. MP supports fragmented packets. The fragmented packets are transmitted on multiple PPP links in the MP group to the same destination.

Context
Follow the procedure shown in Figure 10-11 to configure an MP group.

10-52

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Figure 10-11 Procedure for configuring an MP group

Start

Enable the PPP at the interface

Create MP group

Configure members to an MP group

End

Required

Optional

10.8.1 Overview of the ML-PPP The Multilink PPP, also ML-PPP or MP, indicates that multiple point-to-point protocol (PPP) links are bundled and used. In this document, the Multilink PPP is referred to as ML-PPP. 10.8.2 Basic Concepts Before configuring the ML-PPP, you need to know the basic concepts, such as the packet format of the ML-PPP. 10.8.3 ML-PPP Application In the case of the ML-PPP, several ports that adopt the PPP encapsulation are bundled into one logical port to increase the transmission bandwidth. The ML-PPP allows that packets be divided into fragments, which are transported over several PPP links to the same destination. The MLPPP is applicable to the PPP-supported ports, such as the E1 interface. 10.8.4 Creating MP Groups You can bind multiple serial interfaces or E1 interfaces on which PPP is enabled by creating an MP group, so that the bound serial interfaces or E1 interfaces are used as a logical port to carry tunnels. 10.8.5 Configuring Member Interfaces of MP Groups To modify the bandwidth of the MP group, add or delete the member interfaces into or from the MP group.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-53

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

10.8.1 Overview of the ML-PPP

The Multilink PPP, also ML-PPP or MP, indicates that multiple point-to-point protocol (PPP) links are bundled and used. In this document, the Multilink PPP is referred to as ML-PPP. The ML-PPP function benefits the network in the following aspects:
l l l

Bandwidth increased. Load shared and backed up. Delay shortened by fragments.

The ML-PPP complies with RFC1990 (PPP multilink protocol). The ML-PPP protocol focuses on the transmission of fragments of data packets over multiple data links, reassembly and sequence of these fragments.

10.8.2 Basic Concepts

Before configuring the ML-PPP, you need to know the basic concepts, such as the packet format of the ML-PPP.

ML-PPP Packet Format

The ML-PPP packets have the following formats, shown as Figure 10-12:
l

Long sequence number fragment format (LSNFF): The sequence number field has 24 bits. This format is the default format. Short sequence number fragment format (SSNFF): The sequence number field has 12 bits.

The fragment format of transmitted packets can be different from that of received packets on the condition of mutual negotiation. If the negotiation does not allow that the received packets are of the LSNFF format, the MP packets of the SSNFF format should be transmitted.

10-54

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Figure 10-12 ML-PPP packet format

Adress PPP Header Protocol 0x003d 0x003d 0xFF 0xFF Control 0x03

B ML-PPP Header

sequence number

sequence number

fragment data ....

PPP FCS

FCS

Long Sequence Number Fragment Format

Adress PPP Header

0xFF 0xFF

Control

0x03

Protocol

0x003d 0x003d

ML-PPP Header

sequence number

fragment data ....

PPP FCS

FCS

Short Sequence Number Fragment Format

10.8.3 ML-PPP Application

In the case of the ML-PPP, several ports that adopt the PPP encapsulation are bundled into one logical port to increase the transmission bandwidth. The ML-PPP allows that packets be divided into fragments, which are transported over several PPP links to the same destination. The MLPPP is applicable to the PPP-supported ports, such as the E1 interface. As shown in Figure 10-13, the ML-PPP bundles several PPP links into one logical port. Figure 10-13 ML-PPP application scenario
NE1 PPP link PPP link PPP link ML-PPP NE2

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-55

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

10.8.4 Creating MP Groups

You can bind multiple serial interfaces or E1 interfaces on which PPP is enabled by creating an MP group, so that the bound serial interfaces or E1 interfaces are used as a logical port to carry tunnels.

Prerequisite
l l l

You must be an NM user with "NE operator" authority or higher. Multiple serial interfaces or E1 interfaces on which PPP is enabled must be created. The E1 Frame Format or VC12 Frame Format of the local MP group and the opposite MP group should be consistent.

Context
NOTE

The MP group can be bound only with the E1 interfaces of the same processing board, or the serial interfaces of the same physical interface.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > MP Group Management from the Function Tree. Step 2 Click New in the General Attributes tab and the New MP Group dialogue box is displayed. Step 3 Set the parameters as required.

10-56

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation was successful. Step 5 Click Close. ----End

10.8.5 Configuring Member Interfaces of MP Groups

To modify the bandwidth of the MP group, add or delete the member interfaces into or from the MP group.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. An MP group must be configured.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-57

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > MP Group Management from the Function Tree. Step 2 Select an MP group and click Configuration. The Config Member Interface dialog box is displayed. Step 3 Set the parameters as required.

Step 4 Click Apply. The Warning dialog box is displayed, indicating that the operation may interrupt the services.
NOTE

Deleting the member interface of the MP group may damage the service. The member interface in the same MP group must have the same frame mode. That is, the values of Frame Mode are all 30 or 31. for the parameters of Frame Mode, to see E1 Frame Format or VC12 Frame Format.

Step 5 Click Yes. A dialog box is displayed, indicating that the operation is successful. Step 6 Click Close. ----End

10.9 Configuring an Ethernet Virtual Interface

This section describes how to configure an Ethernet virtual interface. After you configure the Ethernet virtual interface, the NE can process ATM AAL5-encapsulated or VLAN-encapsulated Ethernet packets. The Ethernet virtual interface attributes include general attributes and layer 3 attributes. 10.9.1 Application of the Ethernet Virtual Interfaces This section describes the classification of the Ethernet virtual interfaces and application of the Ethernet virtual interfaces. 10.9.2 Process of Configuring an Ethernet Virtual Interface
10-58 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

The configuration process defines the tasks and the sequence in which the tasks should be finished. To configure an Ethernet virtual interface, you need to configure the virtual interface on the xDSL board or on the Ethernet board. 10.9.3 Setting the General Attributes of Ethernet Virtual Interfaces The general attributes of an Ethernet virtual interface define the related information of the ATM adaptation layer (AAL) or VLAN. Before you configure an Ethernet virtual interface, you need to configure the general attributes of the Ethernet virtual interface. 10.9.4 Creating VLAN Sub Interface A VLAN tag can be stuck onto the services at a VLAN sub-interface so that the services can traverse a third-party Layer 2 network. 10.9.5 Setting the Layer 3 Attributes of Ethernet Virtual Interfaces The Layer 3 attributes of an Ethernet virtual interface include the IP address and tunnel enabling status. You can create a tunnel after setting the Layer 3 attributes.

10.9.1 Application of the Ethernet Virtual Interfaces

This section describes the classification of the Ethernet virtual interfaces and application of the Ethernet virtual interfaces. Table 10-10 lists details on the classification of the Ethernet virtual interfaces. Table 10-10 Classification of the Ethernet virtual interfaces Interface Type EoADSL Virtual Interface EoATM Virtual Interface Supported Board ADS2A/B Application On the EoADSL virtual interface, the interface IP address is configured and the tunnel is created to carry services. On the EoATM virtual interface, the interface IP address is configured and the tunnel is created to carry services. DSLAM that is interconnected with the SHD4 supports the ATM mode. EoEFM Virtual Interface SHD4 On the EoEFM virtual interface, the interface IP address is configured and the tunnel is created to carry services. DSLAM that is interconnected with the SHD4 supports the EFM mode. EoIMA Virtual Interface SHD4I On the EoIMA virtual interface, the interface IP address is configured and the tunnel is created to carry services. DSLAM that is interconnected with the SHD4I supports the IMA mode. EoA Virtual Interface ASD1 Supports ATM PWE3 over IP/GRE/MPLS tunnel. On an ATM network, the services are transported through the EoA virtual interfaces.

SHD4

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-59

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Interface Type VLAN Sub Interface

Supported Board ADS2A, ADS2B, SHD4, SHD4I, and Ethernet boards

Application By creating the VLAN sub-interfaces, the VLAN tags are added to the Ethernet packets to distinguish various services. When traversing a third-party Layer 2 network, the various services carry different VLAN tags. Then, the services are forwarded according to the VLAN tags.

10.9.2 Process of Configuring an Ethernet Virtual Interface

The configuration process defines the tasks and the sequence in which the tasks should be finished. To configure an Ethernet virtual interface, you need to configure the virtual interface on the xDSL board or on the Ethernet board.

Virtual Interface on the xDSL Interface

Configure the virtual interface on the xDSL board according to Figure 10-14. Figure 10-14 Process of configuring the virtual interface on the xDSL board

Start

Configure and query general attributes of a virtual Interface

Create a VLAN sub interface

Configure layer3 attributes of an Ethermet virtual interface End

Required Optional
10-60 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Table 10-11 Tasks for configuring the virtual interface on the xDSL board Tasks Configure and query general attributes of a virtual interface Create a VLAN subinterface Remarks Specify a port name, set the port mode, and query the bound board, bound port, and interface MAC address. Create a VLAN sub-interface and set the port VLAN ID so that the service can pass through a third-party Layer 2 network. When creating a VLAN sub-interface, make sure that the port mode is set to Layer Mix. Configure layer 3 attributes of an Ethernet virtual interface Set the IP address of the interface and enable the tunnel. When setting Layer 3 attributes is complete, you can create a tunnel to carry services.

Virtual Interface on the Ethernet Board

Configure the virtual interface on the Ethernet board according to Figure 10-15. Figure 10-15 Process of configuring the virtual interface on the Ethernet board

Start

Configure and query general attributes of an Ethernet Interface

Create a VLAN sub interface

Configure layer3 attributes of an Ethermet virtual interface End

Required Optional
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 10-61

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Table 10-12 Tasks for configuring the virtual interface on the Ethernet board Tasks Configure general attributes of an Ethernet interface Create a VLAN subinterface Remarks Enable the port, set the port mode to Layer Mix, and set the working mode and maximum frame length for the port. Create a VLAN sub-interface and set the port VLAN ID so that the service can pass through a third-party Layer 2 network. When creating a VLAN sub-interface, make sure that the port mode is set to Layer Mix. Configure layer 3 attributes of an Ethernet virtual interface Set the IP address of the interface and enable the tunnel. When setting Layer 3 attributes is complete, you can create a tunnel to carry services.

10.9.3 Setting the General Attributes of Ethernet Virtual Interfaces

The general attributes of an Ethernet virtual interface define the related information of the ATM adaptation layer (AAL) or VLAN. Before you configure an Ethernet virtual interface, you need to configure the general attributes of the Ethernet virtual interface.

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

Context
When you create a ADS2 , SHD4I or SHD4 logical board, the DSL ports are automatically bound as Ethernet virtual interfaces, which control the Offload service flow and carry tunnels. The Ethernet virtual interface supports the creation of the VLAN sub-interface. OptiX PTN 1900 and OptiX PTN 3900 support to create VLAN sub-interface and EOA Virtual Interface.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Ethernet Virtual Interface from the Function Tree. Step 2 Click Query. The Operation Result dialog box is displayed dialog box is displayed indicating that the operation is successful. Step 3 Click Close. The general attributes of an Ethernet virtual interface are displayed in the field. Step 4 Specify the port name and set the port mode to Layer 3 or Layer Mix as required.

10-62

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

10 Configuring Interfaces

To create a VLAN sub-interface, set the port mode to Layer Mix. Before changing Layer 3 to Layer Mix, make sure that route protocols, such as IGP-ISIS, OSPF, and RIP, are not enabled on the port. Before changing Layer Mix to Layer 3, make sure that no VLAN tag is added to the port and no Layer 2 service is configured on the port.

Step 5 Click OK. A prompt is displayed indicating that the operation is successful. Click Close. ----End

10.9.4 Creating VLAN Sub Interface

A VLAN tag can be stuck onto the services at a VLAN sub-interface so that the services can traverse a third-party Layer 2 network.

Prerequisite
You must be an NM user with "NE operator" authority or higher. Port mode must be set to Layer mix.

Context
A VLAN sub-interface is similar to a Layer 3 port. Hence, a tunnel can be created to carry services by setting the Layer 3 attributes of the VLAN sub-interface. The OptiX PTN equipment on the access layer accesses multiple services and maps the services into the tunnel. At the VLAN sub-interfaces, different VLAN tags can be stuck onto the services according to the configuration requirements of the third-party Layer 2 network. In this manner, the services can be correctly forwarded when traversing a third-party network. The OptiX PTN equipment on the convergence layer distinguishes the services according to the VLAN sub-interfaces.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Ethernet Virtual Interface from the Function Tree. Step 2 Click New in the General Attributes tab and the Create Ethernet Virtual Interface dialog box is displayed. Step 3 Set the parameters as required in the Create Ethernet Virtual Interface displayed.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-63

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 4 Click Apply. ----End

10.9.5 Setting the Layer 3 Attributes of Ethernet Virtual Interfaces

The Layer 3 attributes of an Ethernet virtual interface include the IP address and tunnel enabling status. You can create a tunnel after setting the Layer 3 attributes.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Layer 3 Attributes tab, set the Specify IP to Manually and set the IP Address and IP Mask for the port. Step 3 Double-click the Enable Tunnel field, and select Enabled.
10-64 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Step 4 Click Apply. A prompt is displayed indicating that the operation is successful. Click Close. ----End

10.10 Configuring an IMA Group

When the PTN equipment accesses IMA services, configure an ATM IMA group at the access node.

Context
Figure 10-16 shows the flow for configuring an IMA group. Figure 10-16 IMA group configuration flow
Start

Configure bound paths for an ATM IMA group

Configure IMA group attributes

Configure ATM interface attributes

Query the IMA group states

Query the states of the link of an IMA group

Reset an IMA group

Modify an IMA group

Delete an IMA group

End

Required

Optional

10.10.1 Configuring Bound Channels in an ATM IMA Group

Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 10-65

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

When the PTN equipment accesses IMA services, configure bound channels in an ATM IMA group at the access node. One ATM IMA group corresponds to one ATM trunk port. Bind channels with the ATM trunk port and then enable the IMA group. The ATM trunk port can be bound with one or several E1, VC12-xv or Fractional E1 ports. 10.10.2 Configuring Attributes of an ATM IMA Group After configuring the channels bound with the IMA group, enable the IMA protocol and configure attributes of the IMA group to make the IMA group meet the service requirements. 10.10.3 Configuring the ATM Interfaces By using the E1 board, channelized STM-1 board, or ATM STM-1 board, the OptiX PTN equipment can access ATM services at the E1/VC-12, fractional E1, or STM-1 level. In the case of fractional E1, one E1/VC12 channel can carry multiple services. Certain timeslots of the 32 timeslots in an E1/VC12 channel can be allocated for the CES services and the others for the ATM services. In this manner, the resources are saved and the costs are reduced. 10.10.4 Querying IMA Group States In the case of routine maintenance and troubleshooting, the operator need query information on states of an IMA group to check whether the IMA group is normal. 10.10.5 Querying IMA Link States In the case of routine maintenance and troubleshooting, the operator need query information on states of an IMA link to check whether the IMA link is normal. 10.10.6 Resetting an IMA Group In the case of deployment and troubleshooting, the operator can reset an IMA group to re-enable the IMA group protocol. 10.10.7 Modifying an IMA Group When attributes of an IMA group displayed on the T2000 are not consistent with those in the network, modify attributes of this IMA group. If any service is configured and activated at the ATM Trunk port for an IMA group, modification of the IMA group may interrupt services. 10.10.8 Deleting an IMA Group Delete the redundant or idle IMA groups to release the resources. If any service is configured and activated at the ATM Trunk port for an IMA group, deleting the IMA group may interrupt the services.

10.10.1 Configuring Bound Channels in an ATM IMA Group

When the PTN equipment accesses IMA services, configure bound channels in an ATM IMA group at the access node. One ATM IMA group corresponds to one ATM trunk port. Bind channels with the ATM trunk port and then enable the IMA group. The ATM trunk port can be bound with one or several E1, VC12-xv or Fractional E1 ports.

Prerequisite
You must be an NM user with "NE operator" authority or higher. When the MLPPP or CES services is configured or the DCN is enabled on the VCTRUNK, the VCTRUNK resources are occupied and thus the IMA group cannot be created. When an E1or Fractional E1 port is bound with an IMA group, Port Mode should be set to Layer 2.

10-66

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Context
NOTE

Only the E1 ports or the VC12 paths on the same processing board can be bound.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM IMA Management from Function Tree. Step 2 Click the Binding tab and click Configuration. The Bound Path dialog box is displayed.

Step 3 Configure boards and VCTRUNK ports in Available Boards and Configurable Ports respectively. Step 4 Select E1, Fractional E1 or VC12-xv for Level. Step 5 Select a port in Available Resources. Click to bind the port to the VCTRUNK. Click

to cancel binding of the port to the VCTRUNK.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-67

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

CAUTION
The VCTRUNK that is first added into the IMA group should be deleted at last. The ports that are bound to the same VCTRUNK must have the same E1 frame mode or VC12 frame mode. When the member links of an IMA group are at the serial ports of the 64K level, there are the following restrictions:
l l l

One serial port should be bound with a minimum of three 64K timeslots. The number of bound 64K timeslots should be the same for different serial ports. In one E1, only one serial port can be used as a member link of an IMA group.

Step 6 Click OK. A dialog box is displayed, indicating that the operation succeeds. Click Close. ----End

10.10.2 Configuring Attributes of an ATM IMA Group

After configuring the channels bound with the IMA group, enable the IMA protocol and configure attributes of the IMA group to make the IMA group meet the service requirements.

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

Procedure
Step 1 Click the NE in the NE Explorer. Choose Configuration > Interface Management > ATM IMA Management from Function Tree. Step 2 Click the IMA Group Management tab, enable the IMA protocol, and configure attributes of the IMA group. Click Apply. A dialog box is displayed, indicating that the operation succeeds. Click Close.

10-68

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

10 Configuring Interfaces

Take the following precautions when setting parameters.

l l l l l

You can enable or disable the IMA Protocol Enable Status of the IMA group only after configuring the bound path of the corresponding VCTRUNK of the IMA group. IMA Protocol Version: For the OptiX PTN 912, set this parameter to 1.1. IMA Protocol Version: The IMA protocols running on interconnected equipment must be of the same version. IMA Transmit Frame Length: The optional values are 32, 64, 128 and 256. IMA Symmetry Mode: This parameter should be set to Symmetric Mode and Symmetric Operation. In this case, Minimum Number of Active Transmitting Links should be consistent with Minimum Number of Active Receiving Links. Maximum Delay Between Links: This parameter indicates the maximum delay variance among different links in one IMA group. The value ranges from 1 ms to 120 ms, with 1 ms spacing. If the IMA protocol is enabled, only Minimum Number of Active Transmitting Links, Minimum Number of Active Receiving Links and Maximum Delay Between Links can be set. In the case of OptiX 3900/1900/912, the Clock Mode can be set only after the IMA protocol is disabled. You can modify the IMA Protocol Version, IMA Transmit Frame Length and IMA Symmetry Mode only after you disable the IMA Protocol Enable Status.

l l l l

----End

10.10.3 Configuring the ATM Interfaces

By using the E1 board, channelized STM-1 board, or ATM STM-1 board, the OptiX PTN equipment can access ATM services at the E1/VC-12, fractional E1, or STM-1 level. In the case of fractional E1, one E1/VC12 channel can carry multiple services. Certain timeslots of the 32 timeslots in an E1/VC12 channel can be allocated for the CES services and the others for the ATM services. In this manner, the resources are saved and the costs are reduced.

Prerequisite
You must be an NM user with "NE operator" authority or higher. Disable the DCN function of the port that carries the ATM IMA services.

Context
In the case of the OptiX PTN equipment, Frame Mode of the packets at the PDH interface or SDH interfaces can be 30-timeslot or 31-timeslot. In an E1/VC12 frame, the timeslots used to transport service data vary with Frame Mode:
l

When Frame Mode is set to 30-timeslot, timeslots 1-15 and 17-31 of an E1 frame are used to transport service data, and timeslots 0 and 16 cannot be used for fractional E1. When Frame Mode is set to 31-timeslot, timeslots 1-31 of an E1 frame are used to transport service data, and timeslot 0 cannot be used for fractional E1.

Procedure
l Use an E1 board to carry the ATM IMA services.
Issue 01 (2009-06-30)

Configure an Interface at the Fractional E1 Level.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 10-69

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

1. 2.

In the NE Explorer, click an NE and choose Configuration > Interface Management > PDH Interface from the Function Tree. In the General Attributes tab, select 23-D12-4(Port-4) and 23-D12-5(Port-5). Set the Port Mode to Layer 1 and click Apply.

3.

Click Advanced Attributes tab, set Frame Format and Frame Mode according to networking planning. Click Apply.

4.

Choose Configuration > Interface Management > Serial Interface from the Function Tree. Click New in the General Attributes tab and the New Serial Interface dialog box is displayed. In the New Serial Interface dialog box, set the Level, Used Board, Used Port, and 64K Timeslot fields and then click OK. Create serial interfaces of 23D12-4(Port-4) and 23-D12-5(Port-5).
NOTE

5.

The serial interface at the 64k timeslots level is created as follows:

l l l

The number of bundled timeslots ranges from 3 to 30. In one E1, only one serial interface can be used as the member link of the IMA group. The number of bundled 64k timeslots for all the member serial interfaces configured in an IMA group should be the same. In this example, when the serial interfaces of 23-D12-4(Port-4) and 23-D12-5 (Port-5) are created, nine 64k timeslots are used.

6.

Select the created serial interfaces, set Port Mode to Layer 2, and then click Apply.

7.

Choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Click Configuration in the Binding tab and the Bound Path dialog box is displayed. Select the bound board and port, select Fractional E1 for the Level field, and select Available Resources. Then, click port to Selected Bound Paths. to add the bound board and

8.

10-70

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

9.

Click Apply.

10. On the IMA Group Management tab, select the IMA group 3-MP1-1-MD1-1 (Trunk-1). Set the parameters such as IMA Transmit Frame Length and IMA Symmetry Mode according to the network planning. Then, set IMA Protocol Enable Status to Enabled. Click Apply. 11. On the ATM Interface Management tab, click the IMA group 3-MP1-1-MD1-1 (Trunk-1). Then, set the parameters such as VPI/VCI range for the ports according to the network planning. Click Apply. Configure an Interface at the E1 Level. 1. 2. 3. 4. 5. In the NE Explorer, select an NE and choose Configuration > Interface Management > PDH Interface from the Function Tree. In General Attributes tab, select 19-D75-10(Port-10) to 19-D75-15(Port-15). Set Port Mode to Layer 2, and click Apply. In Advanced Attributes tab, set Frame Format and Frame Mode according to networking planning. Click Apply. Set the parameters about the IMA group at the E1 level according to 7 through 11 of "Using an E1 board to configure an interface at the fractional E1 level". Select E1 for the Level field for the available bound path and select ports in Available Resources.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-71

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Use an channelized STM-1 board to carry the ATM IMA services. Configure an Interface at the Fractional E1 Level. 1. 2. 3. 4. In the NE Explorer click 3-MP1 board, and choose Configuration > Interface Management > Path Configuration from the Function Tree. Set VC12 Frame Format and Frame mode according to networking planning. Click Apply. Create serial interfaces for the CD1 board according to 4 through 6 of "Using an E1 board to configure an interface at the fractional E1 level". In the displayed New Serial Interface dialog box, set Used Timeslot and 64K Timeslot for ports.

NOTE

Used Timeslot: VC-12 path number. The CD1 board can access 2 x channelized STM-1 signals.Each channel of channelized STM-1 signals support 63 VC-12 paths. 64K Timeslot: One VC-12 path contains 32 64K timeslots. Among the 32 64K timeslots, timeslot 0 transports the signaling information and thus is unavailable.

5.

Set the parameters about the IMA group at the Fractional E1 level of 3-MP1CD1-1(Tunk-1) according to 7 through 11 of "Using an E1 board to configure an interface at the fractional E1 level". Set the VC12 Frame Format and Frame Mode according to 1 through 2 of "Using an STM-1 board to configure an interface at the fractional E1 level". Set the parameters about the IMA group at the VC-12 level according to 7 through 11 of "Using an E1 board to configure an interface at the fractional E1 level". Select E1 for the Level field for the available bound path and select VC-12 paths in Available Resources.

Configure an Interface at the VC-12 Level. 1. 2. 3.

10-72

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Use the ATM STM-1 board to carry the ATM services. 1. 2. 3. Set the VC12 Frame Format and Frame Mode according to 1 through 2 of "Using an STM-1 board to configure an interface at the fractional E1 level". In the NE Explorer, select an NE and choose Configuration > Interface Management > SDH Interface from the Function Tree. In Layer 2 Attributes, select 3-MP1-1-AD1-1(Trunk-1) and set the parameters such as VPI/VCI range for the ports according to the network planning. Click Apply.

----End

Result
When creating the IMA groups at both ends of the interconnected equipment is complete, you can query the IMA group status on the U2000 to check whether the IMA groups are in proper status. 1. 2. In the NE Explorer, click an NE and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. On the IMA Group States tab, click Query. Check Near-End Group Status, Far-End Group Status, and Number of Transmit/Receive Links.
l

If Near-End Group Status and Far-End Group Status are displayed as Operational, the negotiation of the IMA groups is successful. If Near-End Group Status and Far-End Group Status are displayed as other status, handle the anomaly with reference to Table 10-13.

3.

In the IMA Link Status tab, click Query. Check Near-End Receiving/Transmitting Status and Far-End Receiving/Transmitting Status.
l

If Near-End Receiving Status, Near-End Transmitting Status, Far-End Receiving Status, and Far-End Transmitting Status are displayed as Usable, it indicates that the IMA link is normal. If Near-End Receiving Status, Near-End Transmitting Status, Far-End Receiving Status, and Far-End Transmitting Status are displayed as Unusable, it indicates that the IMA link is faulty. For details on the IMA link status parameters, see Table 10-14.

Table 10-13 lists the IMA group status parameters.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-73

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Table 10-13 IMA group status parameters Near-End/Far-End Group Status Start-Up Description This end is in the Start-Up status and is waiting to be indicated that the far-end is also in the Start-Up status. Suggestion Start the IMA protocol for the opposite IMA group and check whether the IMA groups are normal. The IMA groups are in the progress of negotiation. Wait for 500 ms and then check whether the IMA groups are normal. Check whether the parameter settings are consistent for the IMA groups at both ends. If not, re-set the inconsistent parameters to ensure that all the parameter settings are consistent for the IMA groups at both ends. When the fault of the IMA link is rectified, check whether the IMA groups are in proper status. .

Start-Up-ACK

This is a transitional state. When both the near-end and far-end groups startup, they move to this state.

Config-Aborted

This state is entered when the far-end tries to apply unacceptable configuration parameters.

Insufficient-Links

The status is displayed when the parameter settings for the IMA groups at both ends are consistent but the link resources are insufficient. In this case, the number of activated links is less than the minimum number of activated links for an IMA group. The group is blocked. The group can be blocked for maintenance purposes while sufficient links are Active in both transmitting and receiving directions. The group is not inhibited and has sufficient links in both transmitting and receiving directions.

Blocked

Operational

Table 10-14 lists the IMA link status parameters.

10-74

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Table 10-14 IMA link status parameters Receive/Transmit Status Unusable Description The status is displayed when an IMA link is added to an IMA group but the IMA link is not available because of fault-caused or manual suppression. This status indicates that the link is availably and it is displayed when you are waiting for the remote receive link to be activated. In this case, this link is not added to the cyclical transmitting process of the IMA group. This status indicates that the link is activated. If service cells accessed, they can be transmitted. This link is added to the cyclical transmitting process of the IMA group. Suggestion

Usable

Active

10.10.4 Querying IMA Group States

In the case of routine maintenance and troubleshooting, the operator need query information on states of an IMA group to check whether the IMA group is normal.

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. You must complete the configuration of an IMA group.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM IMA Management from Function Tree. Step 2 Click the IMA Group States tab and select the IMA group for query. Click Query. A dialog box is displayed, indicating that the operation succeeds. Click Close. ----End

10.10.5 Querying IMA Link States

In the case of routine maintenance and troubleshooting, the operator need query information on states of an IMA link to check whether the IMA link is normal.

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. You must complete the configuration of an IMA link.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 10-75

Issue 01 (2009-06-30)

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM IMA Management from Function Tree. Step 2 Click the IMA Link States tab and select the IMA link for query. Click Query. A dialog box is displayed, indicating that the operation succeeds. Click Close. ----End

10.10.6 Resetting an IMA Group

In the case of deployment and troubleshooting, the operator can reset an IMA group to re-enable the IMA group protocol.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. You must complete the creation of the IMA group.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM IMA Management from Function Tree. Step 2 Click the IMA Group Management tab and select the IMA group. Click Reset. A dialog box is displayed, indicating that the operation succeeds. Click Close. ----End

10.10.7 Modifying an IMA Group

When attributes of an IMA group displayed on the T2000 are not consistent with those in the network, modify attributes of this IMA group. If any service is configured and activated at the ATM Trunk port for an IMA group, modification of the IMA group may interrupt services.

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

Context

CAUTION
If any service is configured and activated at the ATM Trunk port for the IMA group, modification of the IMA group may interrupt services. Exercise caution for this.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM IMA Management from Function Tree.
10-76 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Step 2 Click the IMA Group Management tab and modify related attributes of the IMA group. Click Apply. A dialog box is displayed, indicating that the operation succeeds. Click Close. ----End

10.10.8 Deleting an IMA Group

Delete the redundant or idle IMA groups to release the resources. If any service is configured and activated at the ATM Trunk port for an IMA group, deleting the IMA group may interrupt the services.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The IMA Protocol Enable Status of the IMA group must be Disabled.

Context

CAUTION
If any service is configured and activated at the ATM Trunk port for the IMA group, deleting the IMA group may interrupt the services. Exercise caution for this.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Step 2 Click the Banding tab and select an IMA group. Click Delete. A dialog box is displayed, indicating that the operation may interrupt the services. Click OK. A dialog box is displayed, indicating that the operation is successful. Click Close. ----End

10.11 Configuring the V-UNI Group

When one user has multiple Ethernet service access points or one Ethernet service has multiple access points, the V-UNI group can be configured. The V-UNI group can realize the overall bandwidth restriction on group members, that is, the V-UNI in the group. On the T2000, the user can create, modify and delete the V-UNI group. 10.11.1 Creating a V-UNI Group The creation of the V-UNI group includes the selection of V-UNI group members and setting of overall bandwidth of V-UNI members. The overall bandwidth in the V-UNI group can be restrained by creating the V-UNI group. 10.11.2 Modifying a V-UNI Group The re-selection of V-UNI group members or modification of the bandwidth of the V-UNI group can be realized by modifying the V-UNI group. 10.11.3 Deleting a V-UNI Group
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 10-77

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

When the overall bandwidth of members in the V-UNI is not expected to be restrained, delete the V-UNI group at any time.

10.11.1 Creating a V-UNI Group

The creation of the V-UNI group includes the selection of V-UNI group members and setting of overall bandwidth of V-UNI members. The overall bandwidth in the V-UNI group can be restrained by creating the V-UNI group.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must complete the creation of multiple Ethernet services. The PIR value of the V-UNI group should be set to a value that is higher than or equal to the total CIR value of the V-UNI members.

Procedure
Step 1 Select the NE in the NE Explorer . Choose Configuration > Ethernet Service Management > V-UNI Group from the Function Tree. Step 2 Click New to display the NEW V-UNI Group window. Step 3 Set V-UNI Group ID, V-UNI Group Type, PIR(kbit/s) and PBS(byte).

10-78

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Step 4 Select the interface to be added in Selecting Interface list. Click the Selected Interface list.
NOTE

to add the port to

The interfaces on the same interface board can be configured into the same V-UNI group. The former eight interfaces on the EG16 can be configured into the same V-UNI group, and the latter eight interfaces can be configured into the same V-UNI group.

Step 5 Click OK to display the Operation Result dialog box, which indicates the operation success. Then, click Close. ----End

10.11.2 Modifying a V-UNI Group

The re-selection of V-UNI group members or modification of the bandwidth of the V-UNI group can be realized by modifying the V-UNI group.

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

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-79

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > Ethernet Service Management > V-UNI Group from the Function Tree. Step 2 Select the V-UNI group to be modified. Click Modify to display the Modify V-UNI Group window. Step 3 Modify PIR(kbit/s) and PBS(byte) of the V-UNI group in the Modify V-UNI Group window. Step 4 Click Configure Interface to display the Configure Interface dialog box. Step 5 Select the interface, and then click OK to return to the Modify V-UNI Group window. Then, the selected interface is in Selecting Interface list of the Member Setting. Step 6 Select the interface to be added. Click Step 7 Select the interface to be deleted. Click Interface list. to add the port to the Selected Interface list. to delete the port from the Selected

Step 8 Click OK to display the Operation Result dialog box, which indicates the operation success. Then, click Close. ----End

10.11.3 Deleting a V-UNI Group

When the overall bandwidth of members in the V-UNI is not expected to be restrained, delete the V-UNI group at any time.

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

Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > Ethernet Service Management > V-UNI Group from the Function Tree. Step 2 Select the V-UNI group to be deleted. Click Delete to display a dialog box. Step 3 Click Yes to display the Operation Result dialog box, which indicates the operation success. Then, click Close. ----End

10.12 ML-PPP Configuration Case

A case is provided here to show how to configure the ML-PPP in terms of the typical application and configuration operations. 10.12.1 Case Description The ML-PPP group between POC1 and POC2 is bound with three links, which are used to transmit four IMA over E1 services accessed at POC2.
10-80 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

10.12.2 Service Planning To plan a service is to design the details of a service to be created according to the service requirements. Service planning provides guidelines for service configuration. 10.12.3 Configuration Flow This topic describes the typical flow of configuring the ML-PPP.

10.12.1 Case Description

The ML-PPP group between POC1 and POC2 is bound with three links, which are used to transmit four IMA over E1 services accessed at POC2. As shown in Figure 10-17, the OptiX PTN 3900 is used at POC1, and the OptiX PTN 1900 is used at POC2. The ML-PPP bundles ports to increase the link bandwidth and improve the link reliability. The OptiX PTN 1900 accesses four IMA over E1 base station services and transmits these services to the OptiX PTN 3900 at POC1 through the MP group.
NOTE

The microwave, leased link or channelized STM-1The microwave or leased link can be present between POC2 and POC1. In this case, the E1 link is used between POC2 and POC1.

Figure 10-17 ML-PPP networking diagram

IMA over E1 POC 2 IMA over E1 1-CXP-MD1-3-L75 IMA over E1 192.168.1.1/24 3-MP1-MQ1-24-D75 192.168.1.2/24 ML-PPP POC 1

IMA over E1

Physical connection

Figure 10-18 shows the NE hardware configuration at POC2.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-81

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 10-18 NE hardware configuration at POC2

SLOT 8 PIU SLOT 3 SLOT 4 SLOT 5 SLOT 9 PIU SLOT 1-1 SLOT 11 (FANB) SLOT 1 SLOT 2-1 SLOT 2 MD1 CXP SLOT 6 SLOT 7 MD1 CXP SLOT 2-2 SLOT 1-2 L75

SLOT 10 (FANA)

Figure 10-19 shows the NE hardware configuration at POC1. Figure 10-19 NE hardware configuration at POC1
S L O T 1 9 S L O T 2 0 S L O T 2 1 S L O T 2 2 S L O T 2 3 S L O T 2 4 S L O T 2 5 D 7 5 S L O T 2 6 S L O T 2 7 P I U S L O T 2 8 P I U S L O T 2 9 S C A S L O T 3 0 S C A S L O T 3 1 S L O T 3 2 S L O T 3 3 S L O T 3 4 S L O T 3 5 S L O T 3 6 S L O T 3 7

Fan SLOT 39 S L O T 1 S L O T 2 S L O T 3 S L O T 4 S L O T 5 S L O T 6 S L O T 7 S L O T 8 S L O T 9 G X C S S L O T 1 0 G X C S Fiber routing trough Fan SLOT 40 Air filter S L O T 1 1 S L O T 1 2 S L O T 1 3 S L O T 1 4 S L O T 1 5 S L O T 1 6 S L O T 1 7 S L O T 1 8

Fiber routing trough

MQ1
M P 1

10-82

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

10.12.2 Service Planning

To plan a service is to design the details of a service to be created according to the service requirements. Service planning provides guidelines for service configuration. The engineering planning department should plan the engineering according to the related requirements, and output detailed planning information. Figure 10-17 is considered as an example to show the service planning. Table 10-15 shows how to plan the parameters for the ML-PPP configuration. Table 10-15 Parameters planned for the ML-PPP configuration Attribute Station MP Group Number MP Group Name Specify IP IP Address IP Mask Board for Unnumbered IP Port for Unnumbered IP Min Activated Link Count Max Differential Delay (ms) Board Member Interface Value POC1 100 mlppp01 Unnumbered NE IP 1 25 24-D75 24-D75-5(port 5) 24-D75-6(port 6) 24-D75-7(port 7) POC2 100 mlppp01 Unnumbered NE IP 1 25 3-L75 3-L75-1 (port 1) 3-L75-2 (port 2) 3-L75-3 (port 3)

10.12.3 Configuration Flow

This topic describes the typical flow of configuring the ML-PPP.

Prerequisite
You must understand the networking, requirements and service planning of the example.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-83

10 Configuring Interfaces

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 Configure the network-side port at the POC1 station. 1. 2. In the NE Explorer, select POC1 and choose Configuration > Interface Management > PDH Interface from the Function Tree. Click General Attributes. Set the parameters for three ports, which are 24-D75-5(Port-5), 24-D75-6(Port-6), and 24-D75-7(Port-7). Click Apply.

The parameters related to the Port:

l l l l

Port Mode: Layer 3 (carry tunnel) Encapsulation Type: PPP Channelize: No Max Data Packet Size (byte): 1620 (Set the parameter based on the lengths of data packets. All received data packets whose lengths are greater than the parameter value are discarded.)

Step 2 Configure the ML-PPP bundle at POC1. 1. 2. In the NE Explorer, select POC1 and choose Configuration > Interface Management > MP Group Management from the Function Tree. Choose General Attributes. Click New and the New MP Group dialog box is displayed.

10-84

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

3.

Configure the parameters related to the ML-PPP, and click Apply. The related parameters of the ML-PPP are as follows:
l l l

MP Group Number: 100 MP Group Name: mlppp01 Specify IP: Unnumbered NE IP (If you select Manually or Unnumbered Port IP, you need to set the IP address and IP mask, or the board corresponding to the unnumbered IP and the port corresponding to the unnumbered IP.) IP Address: - (You need not set the parameter in this example because the value of Specify IP is Unnumbered NE IP.) IP Mask: - (You need not set the parameter in this example because the value of Specify IP is Unnumbered NE IP.) Board for Unnumbered IP: - (You need not set the parameter in this example because the value of Specify IP is Unnumbered NE IP.) Port for Unnumbered IP: - (You need not set the parameter in this example because the value of Specify IP is Unnumbered NE IP.)

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-85

10 Configuring Interfaces
l

OptiX iManager T2000 Operation Guide for PTN NE Management

Min Activated Link Count: 1 (You can activate an MP group only when the number of active links in the MP group reaches the value that you set here.) Enable Differential Delay: Enabled Max Differential Delay (ms): 125 (When the difference between the delay of a link and the delay of another link is more than 125 ms, the link is unavailable.) Enabled Tunnel: Enabled Board: 3-L75 Member Interface: 3-L75-1(port-1), 3-L75-2(port-2), 3-L75-3(port-3)

l l

l l l

4.

Choose General Attributes. Set the general attributes of MP Group. Click Apply.

l l

Link Status: / (You can click PPP Running Status to query the actual value.) Max Reserved Bandwidth (kbit/s): 6000 (The maximum reserved bandwidth cannot exceed the actual physical bandwidth.) TE Measurement: 10 (When you set the parameter, you can intervene routing on the network manually. The smaller the value, the higher the priority.) Admin Group: 12 (Represents link attributes. When a dynamic tunnel selects a link, the dynamic tunnel determines to select or reject the link in an admin group that you set to a value different from 12.) IP Address Negotiation Result: / (You can click PPP Running Status to query the actual value.) IP Mask Negotiation Result: / (You can click PPP Running Status to query the actual value.)

Step 3 Configure the network-side port at the POC2 station. 1. 2. In the NE Explorer, select the POC2 and choose Configuration > Interface Management > PDH Interface from the Function Tree. Click General Attributes. Set the parameters for three ports, which are 24-D75-5(Port-5), 24-D75-6(Port-6), and 24-D75-7(Port-7). Click Apply.

The parameters related to the port are as follows:

l l l l

Port Mode: Layer 3 Encapsulation Type: PPP (carrying tunnels) Channelize: No Max Data Packet Size (byte): 1620 (Set the parameter based on the lengths of data packets. All received data packets whose lengths are greater than the parameter value are discarded.)

Step 4 Configure the ML-PPP bundle at POC2.

10-86 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

1. 2.

In the NE Explorer, select the POC2 and choose Configuration > Interface Management > MP Group Management from the Function Tree. Choose General Attributes. Click New and the New MP Group dialog box is displayed.

3.

Configure the parameters related to the ML-PPP, and click Apply. The related parameters of the ML-PPP are as follows:
l l l

MP Group Number: 100 MP Group Name: mlppp01 Specify IP: Unnumbered NE IP (If you select Manually or Unnumbered Port IP, you need to set the IP address and IP mask, or the board corresponding to the unnumbered IP and the port corresponding to the unnumbered IP.) IP Address: - (You need not set the parameter in this example because the value of Specify IP is Unnumbered NE IP.) IP Mask: - (You need not set the parameter in this example because the value of Specify IP is Unnumbered NE IP.) Board for Unnumbered IP: - (You need not set the parameter in this example because the value of Specify IP is Unnumbered NE IP.)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 10-87

Issue 01 (2009-06-30)

10 Configuring Interfaces
l

OptiX iManager T2000 Operation Guide for PTN NE Management

Port for Unnumbered IP: - (You need not set the parameter in this example because the value of Specify IP is Unnumbered NE IP.) Min Activated Link Count: 1 (You can activate an MP group only when the number of active links in the MP group reaches the value that you set here.) Enable Differential Delay: Enabled Max Differential Delay (ms): 125 (When the difference between the delay of a link and the delay of another link is more than 125 ms, the link is unavailable.) Enabled Tunnel: Enabled Board: 3-L75 Member Interface: 3-L75-1(port-1), 3-L75-2(port-2), 3-L75-3(port-3)

l l

l l l

----End

10.13 Configuring Environment Monitor Interfaces

The environment monitoring interfaces of the equipment include enabling status of the input relay and output relay, temperature attributes and so on. You can set the environment monitoring interfaces so that the running environment of the equipment can be automatically monitored.

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

Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > Environment Monitor Configuration > Environment Monitor Interface from the Function Tree. Step 2 Select the attributes you want to configure from the drop-down list.

Step 3 Click Query to query parameter values. Step 4 Double-click a field to select or enter a value. click Apply. ----End

10.14 Setting Automatic Laser Shutdown

Automatic laser shutdown is a function of automatically shutting down the laser when there is no input light and the laser stops emitting optical signals. For example, when an optical interface board does not bear services, a fault occurs on the fiber, or the received optical signals are lost, the laser is automatically turned off. This reduces the on period of the laser, extends the service life of the laser, and prevents hazardous laser radiation exposure from causing permanent eye damage.
10-88 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

10 Configuring Interfaces

Prerequisite
You must be an NM user with "NE operator" authority or higher. The optical interface board must be created.

Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > Automatic Laser Shutdown from the Function Tree. Step 2 Set Automatic Shutdown to Enabled. Set the On Period (ms), Off Period (ms) and Continuously On-test Period (ms).

Step 3 Click Apply.

NOTE

The displayed Prompt telling you that the operation may cause service interruption or NE login failure. You can confirm the settings according to actual service requirement.

----End

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

10-89

OptiX iManager T2000 Operation Guide for PTN NE Management

11 Configuring the IF 1+1 Protection

11

Configuring the IF 1+1 Protection

About This Chapter

The IF 1+1 protection includes the 1+1 HSB protection, 1+1 FD protection, and 1+1 SD protection. 11.1 Basic Concepts of the 1+1 HSB The 1+1 HSB is a configuration mode of 1+1 protection. In the 1+1 HSB protection mode, the equipment provides a 1+1 hot standby configuration for the IF board and ODU at the two ends of each hop of a radio link to realize the protection. 11.2 Basic Concepts of the 1+1 FD The 1+1 FD is a configuration mode of 1+1 protection. In the 1+1 FD protection mode, the system uses two channels that have a frequency spacing between them, to transmit and receive the same signal. The opposite end selects signals from the two received signals. With the 1+1 FD protection, the impact of the fading on signal transmission is reduced. 11.3 Basic Concepts of the 1+1 SD In the 1+1 SD protection mode, the system uses two antennas that have a space distance between them, to receive the same signal. The equipment selects signals from the two received RF signals. With the 1+1 SD protection, the impact of the fading on signal transmission is reduced. 11.4 Creating IF 1+1 Protection If the microwave link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding IF 1+1 protection group.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

11-1

11 Configuring the IF 1+1 Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

11.1 Basic Concepts of the 1+1 HSB

The 1+1 HSB is a configuration mode of 1+1 protection. In the 1+1 HSB protection mode, the equipment provides a 1+1 hot standby configuration for the IF board and ODU at the two ends of each hop of a radio link to realize the protection. 11.1.1 Description of the 1+1 HSB In the case of the 1+1 HSB protection, the main channel of the transmit end transmits the RF signal to the opposite end, and the main channel and the standby channel of the receive end receive the same RF signal respectively. When the main channel is faulty, the service unit of the receive end receives the signal from the standby channel. Hence, the protection switching is implemented. 11.1.2 Realization Principle The packet switching unit of the system control, switch, and clock board selects the service signal from the main receive channel or from the standby receive channel. Thus, the 1+1 protection switching for the Packet microwave is achieved.

11.1.1 Description of the 1+1 HSB

In the case of the 1+1 HSB protection, the main channel of the transmit end transmits the RF signal to the opposite end, and the main channel and the standby channel of the receive end receive the same RF signal respectively. When the main channel is faulty, the service unit of the receive end receives the signal from the standby channel. Hence, the protection switching is implemented. Figure 11-1 shows the application of the 1+1 HSB protection. Figure 11-1 1+1 HSB protection
Before the Switching Main channel Main channel Receiver MODEM Service MODEM Transmitter Receiver MODEM

MODEM Service

Transmitter

Standby channel After the Switching Main channel

Standby channel

Main channel Receiver MODEM Service

MODEM Service MODEM

Transmitter

Transmitter

Receiver

MODEM

Standby channel

Standby channel

11-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

11 Configuring the IF 1+1 Protection

11.1.2 Realization Principle

The packet switching unit of the system control, switch, and clock board selects the service signal from the main receive channel or from the standby receive channel. Thus, the 1+1 protection switching for the Packet microwave is achieved.

Before the Switching

Figure 11-2 1+1 HSB realization principle (before the switching, in the transmit direction)
Main ODU Main IF board Packet Switching Unit (System control, Switch & Clock board) Service board

Antenna

Hybrid coupler

Standby ODU

Standby IF board

In the transmit direction: 1. 2. 3. 4. The service board sends the received service signal to the packet switching unit. The packet switching unit transmits the service signal to both the main IF board and the standby IF board. The main IF board and the standby IF board send the processed analog IF signal to the main ODU and the standby ODU respectively. The main ODU transmits the RF signal to the hybrid coupler, which sends the RF signal to the antenna. The standby ODU is muted (that is, the standby ODU does not transmit the RF signal).

Figure 11-3 1+1 HSB realization principle (before the switching, in the receive direction)
Main ODU Main IF board Packet Switching Unit (System control, Switch & Clock board) Service board

Antenna

Hybrid coupler

Standby ODU

Standby IF board

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

11-3

11 Configuring the IF 1+1 Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

In the receive direction: 1. 2. 3. 4. 5. The hybrid coupler splits the RF signal received from the antenna into two signals and sends them to the main ODU and the standby ODU. The main ODU and the standby ODU send the processed analog IF signal to the main IF board and the standby IF board respectively. The main IF board and the standby IF board send the service signal to the packet switching unit. The packet switching unit selects the service signal from the main IF board and sends the signal to the service board. The service board sends the service signal to the equipment at the opposite end.

After the Switching

Figure 11-4 1+1 HSB realization principle (after the switching, in the receive direction)
Main ODU Packet Switching Unit Main (System control, Switch & Service Clock board) IF board board

Antenna

Hybrid coupler

Standby ODU

Standby IF board

Figure 11-5 1+1 HSB realization principle (after the switching, in the transmit direction)
Main ODU Packet Switching Unit Main (System control, Switch & Service IF board board Clock board)

Antenna

Hybrid coupler

Standby ODU

Standby IF board

After the 1+1 HSB switching:

l

In the receive direction, the packet switching unit selects the service signal from the standby IF board.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

11-4

OptiX iManager T2000 Operation Guide for PTN NE Management

l

11 Configuring the IF 1+1 Protection

In the transmit direction, the standby ODU outputs the RF signal to the hybrid coupler, which sends the RF signal to the antenna. The main ODU is muted (that is, the main ODU does not send the RF signal).

11.2 Basic Concepts of the 1+1 FD

The 1+1 FD is a configuration mode of 1+1 protection. In the 1+1 FD protection mode, the system uses two channels that have a frequency spacing between them, to transmit and receive the same signal. The opposite end selects signals from the two received signals. With the 1+1 FD protection, the impact of the fading on signal transmission is reduced. 11.2.1 Description of the 1+1 FD In the case of the 1+1 FD protection, the main channel and the standby channel of the receive end receive RF signals at different frequencies from the transmit end respectively. When the quality of the microwave signal is degraded, bit errors may occur in the service on the main channel. Due to spatial fading, the service unit then selects the service signal from the standby channel to protect the service. 11.2.2 Realization Principle When the 1+1 FD HSB switching occurs, the packet switching unit selects the service signal from the main receive channel or from the standby receive channel to implement the switching. When the 1+1 FD HSM switching occurs, the IF board selects the signal from the main receive channel or from the standby channel to implement the switching.

11.2.1 Description of the 1+1 FD

In the case of the 1+1 FD protection, the main channel and the standby channel of the receive end receive RF signals at different frequencies from the transmit end respectively. When the quality of the microwave signal is degraded, bit errors may occur in the service on the main channel. Due to spatial fading, the service unit then selects the service signal from the standby channel to protect the service. Figure 11-6 shows the application of the 1+1 FD protection.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

11-5

11 Configuring the IF 1+1 Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 11-6 1+1 FD protection

Before the swtiching Main channel Main channel Receiver F1 Service MODEM Transmitter F2 F1 F2 Receiver MODEM Service

MODEM

Transmitter

MODEM

Standby channel

Standby channel

After the swtiching Main channel Main channel

MODEM

Transmitter F1 F1 F2

Receiver

MODEM

Service MODEM Transmitter

F2

Service Receiver MODEM

Standby channel

Standby channel

11.2.2 Realization Principle

When the 1+1 FD HSB switching occurs, the packet switching unit selects the service signal from the main receive channel or from the standby receive channel to implement the switching. When the 1+1 FD HSM switching occurs, the IF board selects the signal from the main receive channel or from the standby channel to implement the switching.

Before the Switching

Figure 11-7 1+1 FD realization principle (before the switching, in the transmit direction)

Antenna f1

Main ODU

Packet Switching Unit (System control, Switch Main & Clock board) IF board

Service board

f2

Antenna

Standby ODU

Standby IF board
Issue 01 (2009-06-30)

11-6

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX iManager T2000 Operation Guide for PTN NE Management

11 Configuring the IF 1+1 Protection

In the transmit direction: 1. 2. 3. 4. The service board sends the received service signal to the packet switching unit. The packet switching unit transmits the service signal to both the main IF board and the standby IF board. The main IF board and the standby IF board send the processed analog IF signal to the main ODU and the standby ODU respectively. The main ODU and the standby ODU output RF signals at different frequencies and send the signals to their respective antennas.

Figure 11-8 1+1 FD realization principle (before the switching, in the receive direction)
Antenna Main ODU Main IF board Packet Switching Unit (System control, Switch & Clock board) Service board

Antenna

Standby ODU

Standby IF board

In the receive direction: 1. 2. 3. The antennas receive RF signals and send the signals to their respective ODUs. The main ODU and the standby ODU send the processed analog IF signal to the main IF board and the standby IF board respectively. The standby IF board sends the processed baseband signal to itself and to the multiplex unit of its paired board. The main IF board selects its own baseband signal and sends the signal to the packet switching unit. The packet switching unit selects the service signal from the main IF board and sends the signal to the service board. The service board sends the service signal to the equipment at the opposite end.

4. 5.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

11-7

11 Configuring the IF 1+1 Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

After the Switching

Figure 11-9 1+1 FD HSB realization principle (after the switching, in the receive direction)
Antenna Main ODU Main IF board Packet Switching Unit (System control, Switch & Clock board) Service board

Antenna

Standby ODU

Standby IF board

After the 1+1 FD HSB switching:

l

In the receive direction, the IF boards select their own service signal. The packet switching unit selects the signal from the standby IF board. In the transmit direction, no processing is required.

Figure 11-10 1+1 FD HSM realization principle (after the switching, in the receive direction)
Antenna Main ODU Main IF board Packet Switching Unit (System control, Switch & Clock board) Service board

Antenna

Standby ODU

Standby IF board

After the 1+1 FD HSM switching:

l

In the receive direction, the IF boards select the baseband signal from their own paired IF board. In the transmit direction, no processing is required.

11.3 Basic Concepts of the 1+1 SD

In the 1+1 SD protection mode, the system uses two antennas that have a space distance between them, to receive the same signal. The equipment selects signals from the two received RF signals. With the 1+1 SD protection, the impact of the fading on signal transmission is reduced.

11-8

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

11 Configuring the IF 1+1 Protection

11.3.1 Description of the 1+1 SD In the case of the 1+1 SD protection, the two antennas at the receive end receive the same RF signals from the transmit end. When the quality of the microwave signal that is received by the main antenna is degraded, bit errors may occur in the service on the main channel. Due to multipath fading, the quality of the signal that is received by the standby antenna may not be degraded. In this case, the service unit receives the service from the standby receive channel to protect the service. 11.3.2 Realization Principle When the 1+1 SD HSB switching occurs, the packet switching unit selects the service signal from the main receive channel or from the standby receive channel to implement the switching. When the 1+1 SD HSM switching occurs, the IF board selects the signal from the main receive channel or from the standby channel to implement the switching.

11.3.1 Description of the 1+1 SD

In the case of the 1+1 SD protection, the two antennas at the receive end receive the same RF signals from the transmit end. When the quality of the microwave signal that is received by the main antenna is degraded, bit errors may occur in the service on the main channel. Due to multipath fading, the quality of the signal that is received by the standby antenna may not be degraded. In this case, the service unit receives the service from the standby receive channel to protect the service. Figure 11-11 shows the application of the 1+1 SD protection. Figure 11-11 1+1 SD protection
Before the Swtiching Main channel
T1 T2 T1

Main channel
T2

MODEM Service MODEM

Transmitter

Receiver

MODEM Service

Transmitter
T2 T1

Receiver

MODEM

Standby channel

Standby channel

After the Swtiching Main channel

T1 T2 T2 T1

Main channel

MODEM Service MODEM

Transmitter

Receiver

MODEM Service

Transmitter
T2 T1

Receiver

MODEM

Standby channel

Standby channel

11.3.2 Realization Principle

When the 1+1 SD HSB switching occurs, the packet switching unit selects the service signal from the main receive channel or from the standby receive channel to implement the switching.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 11-9

11 Configuring the IF 1+1 Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

When the 1+1 SD HSM switching occurs, the IF board selects the signal from the main receive channel or from the standby channel to implement the switching.

Before the Switching

Figure 11-12 1+1 SD realization principle (before the switching, in the transmit direction)

Antenna

Main ODU

Packet Switching Unit (System control, Switch Main & Clock board) IF board

Service board

Antenna

Standby ODU

Standby IF board

In the transmit direction: 1. 2. 3. 4. The service board sends the received service signal to the packet switching unit. The packet switching unit transmits the service signal to both the main IF board and the standby IF board. The main IF board and the standby IF board send the processed analog IF signal to the main ODU and the standby ODU respectively. The main ODU transmits the RF signal to the hybrid coupler, which sends the RF signal to the antenna. The standby ODU is muted (that is, the standby ODU does not transmit the RF signal).

Figure 11-13 1+1 SD realization principle (before the switching, in the receive direction)
Antenna Main ODU Main IF board Packet Switching Unit (System control, Switch & Clock board) Service board

Antenna

Standby ODU

Standby IF board

In the receive direction:

11-10 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

11 Configuring the IF 1+1 Protection

1. 2. 3.

The antennas receive RF signals and send the signals to their respective ODUs. The main ODU and the standby ODU send the processed analog IF signal to the main IF board and the standby IF board respectively. The standby IF board sends the processed baseband signal to itself and to the MUX unit of its paired board. The main IF board selects its own baseband signal and sends the signal to the packet switching unit. The main IF board and the standby IF board select their own baseband signal. The packet switching unit selects the service signal from the main IF board and sends the signal to the service board. The service board sends the service signal to the equipment at the opposite end.

4. 5. 6.

After the Switching

Figure 11-14 1+1 SD HSB realization principle (after the switching, in the receive direction)
Antenna Main ODU Main IF board Packet Switching Unit (System control, Switch & Clock board) Service board

Antenna

Standby ODU

Standby IF board

Figure 11-15 1+1 SD HSB realization principle (after the switching, in the transmit direction)

Antenna

Main ODU

Packet Switching Unit Main (System control, Switch Service IF board board & Clock board)

Antenna

Standby ODU

Standby IF board

After the 1+1 SD HSB switching:

l

In the receive direction, the IF boards select their own service signal. The packet switching unit selects the signal from the standby IF board.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 11-11

Issue 01 (2009-06-30)

11 Configuring the IF 1+1 Protection

l

OptiX iManager T2000 Operation Guide for PTN NE Management

In the transmit direction, the standby ODU outputs the RF signal to the hybrid coupler, which sends the RF signal to the antenna. The main ODU is muted (that is, the main ODU does not send the RF signal).

Figure 11-16 1+1 SD HSM realization principle (after the switching, in the receive direction)
Antenna Main ODU Main IF board Packet Switching Unit (System control, Switch & Clock board) Service board

Antenna

Standby ODU

Standby IF board

After the 1+1 SD HSM switching:

l

In the receive direction, the IF boards select the baseband signal from their own paired IF board. In the transmit direction, no processing is required.

11.4 Creating IF 1+1 Protection

If the microwave link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding IF 1+1 protection group.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The IF boards and their corresponding ODUs that form the IF 1+1 protection must be included in the NE Panel.

Background Information
When a 1+0 service is converted into a 1+1 service by configuring the 1+1 protection, the original services are not interrupted.

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Step 2 Click the IF 1+1 Protection tab. Step 3 Click New. The system displays the Create IF 1+1 Protection dialog box.
11-12 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

11 Configuring the IF 1+1 Protection

Step 4 Set the parameters of the IF 1+1 protection group.

NOTE

The parameters Working Mode, Revertive Mode, WTR Time (s), and Enable Reverse Switching must be set to the same values at both ends of a radio link hop.

Step 5 Click OK. ----End

Postrequisite
l

In the case of the 1+1 HSB protection and 1+1 SD protection, you need to configure the IF/ODU information of the active microwave link later. The standby microwave link automatically copies the related information of the active microwave link except the transmission status of the ODU. In the case of the 1+1 FD protection, you need to configure the IF/ODU information of the active microwave link and the information of the standby ODU later. The standby microwave link automatically copies the IF information of the active microwave link.
NOTE

The default transmission status of an ODU is Unmute. Hence, you do not need to configure the transmission status of the standby ODU after you create an IF 1+1 protection group.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

11-13

OptiX iManager T2000 Operation Guide for PTN NE Management

12 Configuring a Radio Link

12
About This Chapter

Configuring a Radio Link

In the case of the PTN equipment, you can configure radio links to transmit packet services. 12.1 Configuring the IF/ODU Information of a Radio Link This topic describes how to configure the common IF/ODU information for each radio link. 12.2 Creating IF 1+1 Protection If the microwave link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding IF 1+1 protection group. 12.3 Hop Management The Hop management is based on per link and the equipment at the two ends of a link is managed at the same time.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

12-1

12 Configuring a Radio Link

OptiX iManager T2000 Operation Guide for PTN NE Management

12.1 Configuring the IF/ODU Information of a Radio Link

This topic describes how to configure the common IF/ODU information for each radio link.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The IF board and the ODU that connects to the IF board must be added.

Precautions
l

In 1+1 HSB/SD protection mode, one protection group corresponds to one radio link. In this case, you need configure only the IF/ODU information of the main equipment. In 1+1 FD protection mode, one protection group corresponds to one radio link. In this case, you need configure the IF/ODU information of the main equipment and the ODU information of the standby equipment.

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Step 2 Click IF/ODU Configuration. Step 3 Click IF board icon or ODU icon. Then, the system displays the IF/ODU information of the radio link to which the IF board or ODU belongs. Step 4 Set the corresponding IF information of the radio link.
NOTE

When you set Link ID, note the following points:

l l

If this parameter is different from Received Link ID, the NE reports the MW_LIM alarm and inserts the AIS into the downstream. Set this parameter according to the planning. Each radio link of an NE should have a unique Link ID, and the Link IDs at both the ends of a radio link should be the same.

When you set Assured Capacity Modulation and Full Capacity Modulation, note the following points: This parameter is valid only when Enable AM is set to Enable. When you set Manually Specified Modulation, note the following points: This parameter is valid only when Enable AM is set to Disable.

Step 5 Click Apply. Step 6 Set the corresponding ODU information of the radio link.

12-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

12 Configuring a Radio Link

When you set TX Frequency (MHz), note the following points:

l l

The parameter specifies the channel center frequency. This parameter cannot be set to a value that is less than the minimum TX frequency supported by the ODU + 50% channel spacing or more than the maximum TX frequency supported by the ODU - 50% channel spacing. The difference between the TX frequencies of both the ends of a radio link is a T/R spacing. Set this parameter according to the planning.

l l l

When you set T/R Spacing (MHz), note the following points:
l

This parameter indicates the spacing between the TX power and receive power of the ODU. If Station Type of the ODU is TX high, the TX power is one T/R spacing higher than the receive power. If Station Type of the ODU is TX low, the TX power is one T/R spacing lower than the receive power. If the ODU supports only one T/R spacing, set this parameter to 0, indicating that the T/R spacing supported by the ODU is used. The T/R spacing of the ODU should be set to the same value at both the ends of a radio link.

l l l

When you set TX Power(dBm), note the following points:

l l l

This parameter cannot be set to a value that exceeds the nominal power range supported by the ODU. The TX power of the ODU should be set to the same value at both the ends of a radio link. Set this parameter according to the planning.

Step 7 Click Apply.

NOTE

Click Apply after you set the IF information of the radio link and after you set the ODU information of the radio link.

----End

12.2 Creating IF 1+1 Protection

If the microwave link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding IF 1+1 protection group.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The IF boards and their corresponding ODUs that form the IF 1+1 protection must be included in the NE Panel.

Background Information
When a 1+0 service is converted into a 1+1 service by configuring the 1+1 protection, the original services are not interrupted.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

12-3

12 Configuring a Radio Link

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Step 2 Click the IF 1+1 Protection tab. Step 3 Click New. The system displays the Create IF 1+1 Protection dialog box. Step 4 Set the parameters of the IF 1+1 protection group.
NOTE

The parameters Working Mode, Revertive Mode, WTR Time (s), and Enable Reverse Switching must be set to the same values at both ends of a radio link hop.

Step 5 Click OK. ----End

Postrequisite
l

In the case of the 1+1 HSB protection and 1+1 SD protection, you need to configure the IF/ODU information of the active microwave link later. The standby microwave link automatically copies the related information of the active microwave link except the transmission status of the ODU. In the case of the 1+1 FD protection, you need to configure the IF/ODU information of the active microwave link and the information of the standby ODU later. The standby microwave link automatically copies the IF information of the active microwave link.
NOTE

The default transmission status of an ODU is Unmute. Hence, you do not need to configure the transmission status of the standby ODU after you create an IF 1+1 protection group.

12.3 Hop Management

The Hop management is based on per link and the equipment at the two ends of a link is managed at the same time. 12.3.1 Introduction to the Hop Management Based on Hop management, the system can simultaneously display the information of the two ends of a link. Thus, you can view and set the information of a hop in an easy manner. The Hop management supports the functions such as the setting and query of the intermediate frequency (IF) and radio frequency (RF) information, and the configuration of services and protection. 12.3.2 Setting the IF/RF Information By using the Hop management function, you can set the intermediate frequency (IF) and radio frequency (RF) information, to compare the data of equipment at the two ends of a radio link in an easy manner.

12.3.1 Introduction to the Hop Management

Based on Hop management, the system can simultaneously display the information of the two ends of a link. Thus, you can view and set the information of a hop in an easy manner. The Hop
12-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

12 Configuring a Radio Link

management supports the functions such as the setting and query of the intermediate frequency (IF) and radio frequency (RF) information, and the configuration of services and protection. The Hop management function is used to view and set the information based on a pair of equipment, one of which transmits signals and the other receives signals. In the case of the radio equipment, the configuration parameters are complicated. You need to ensure the consistency of parameters between the equipment at the two ends of a radio link. By using the Hop management function, you can perform operations on the equipment at the two ends of a link at the same time. This facilitates the parameter configuration. In Figure 12-1, a radio link represents a hop. Figure 12-1 Radio link

The Hop management is based on per link and the equipment at the two ends of a link is managed at the same time. This ensures the consistency of configuration data between NEs at the two ends.

12.3.2 Setting the IF/RF Information

By using the Hop management function, you can set the intermediate frequency (IF) and radio frequency (RF) information, to compare the data of equipment at the two ends of a radio link in an easy manner.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The radio link must be created.

Procedure
Step 1 Double click the NE on the main topology, select the IF board in the NE panel, right-click, and choose HOP Management from the shortcut menu. Step 2 In the HOP Management window. Step 3 In the IF/ODU Configuration tab, set the related parameters.

CAUTION
Modifying the value of Transmit Frequency interrupts the link. Exercise caution when you perform this operation.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 12-5

12 Configuring a Radio Link

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 4 Click Apply. ----End

12-6

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

13 Configuring an MPLS Tunnel

13
About This Chapter

Configuring an MPLS Tunnel

In a PSN network, the MPLS tunnel carries PWs where various services are encapsulated. In this way, data packets can be transparently transmitted among NEs. One MPLS tunnel can carry several PWs. Before configuring a service, first configure a MPLS tunnel that carries the service. On the T2000, you can use the trail function or per-NE configuration scheme to configure an MPLS tunnel. 13.1 Basic Concepts Before configuring the MPLS tunnel, familiar yourself with the MPLS and MPLS tunnel, and application scenarios of the MPLS tunnel. 13.2 MPLS Tunnel Configuration Flow This section describes the operation tasks for configuring the MPLS Tunnel, and relations among these tasks. When configuring and managing the MPLS Tunnel, follow the configuration flow. 13.3 Configuring an MPLS Tunnel by Trail Configuring MPLS tunnel by trail can be used to configure an MPLS tunnel. On the T2000, you can configure a static MPLS tunnel or a dynamic MPLS tunnel by trail. For a static MPLS tunnel, the involved NEs should be manually specified. For a dynamic MPLS tunnel, the involved NEs are determined by the RSVP-TE protocol through computation. On the T2000, the user can create or delete an MPLS tunnel. 13.4 Configuring an MPLS Tunnel on a Per-NE Basis The per-NE configuration scheme can be used to create an MPLS tunnel. At each node involved in the tunnel, set the tunnel-related parameters. The per-NE configuration scheme can be used to create a unicast MPLS tunnel. On the T2000, the user can create or delete a unicast MPLS tunnel. 13.5 Querying the Tunnel Label Information On the NE, the label for each tunnel is unique. By querying the tunnel label information, you can learn the usage of tunnel labels. Thus, you can avoid the conflict of labels when creating a static tunnel. 13.6 Configuration Case of the Dynamic MPLS Tunnel This section describes how to configure a dynamic MPLS tunnel. The configuration case and configuration flowchart help you better understand the process of configuring a dynamic MPLS tunnel. The configuration case includes tunnel planning and tunnel configuration.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 13-1

13 Configuring an MPLS Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

13.7 Configuration Case of the Static MPLS Tunnel This section describes how to configure a static MPLS tunnel by using the trail function and on a per-NE basis. The configuration case and configuration flowchart help you better understand the service configuration process. The configuration includes networking, service planning, and configuration process.

13-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

13 Configuring an MPLS Tunnel

13.1 Basic Concepts

Before configuring the MPLS tunnel, familiar yourself with the MPLS and MPLS tunnel, and application scenarios of the MPLS tunnel. 13.1.1 MPLS and MPLS Tunnel As a transmission technology, the multi-protocol label switching (MPLS) can realize transparent transmission of data packets among users. The MPLS tunnel is the tunnel defined in the MPLS protocol. Independent from the service, the MPLS tunnel realizes the end-to-end transmission and carries the PWs related to the service. 13.1.2 Application of the MPLS Tunnel As the carrier of PWs in the network, the MPLS Tunnel provides the service tunnel to transmit service packets. The MPLS Tunnel can carry various services, such as IP packets, C-VLAN and S-VLAN packets, MPLS packets, and ATM packets. The MPLS Tunnel is mainly used for transparent transmission of point-to-point data service packets and Tunnel protection group.

13.1.1 MPLS and MPLS Tunnel

As a transmission technology, the multi-protocol label switching (MPLS) can realize transparent transmission of data packets among users. The MPLS tunnel is the tunnel defined in the MPLS protocol. Independent from the service, the MPLS tunnel realizes the end-to-end transmission and carries the PWs related to the service. Figure 13-1 shows how the MPLS tunnel is used as the service transmission channel. Figure 13-1 MPLS tunnel in the MPLS network

IMA E1 FE ATM STM-1

Ingress node

Transit node MPLS tunnel

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 is encapsulated in the PW it carries. Data packets are first encapsulated in the PW, which is stuck with an MPLS label and sent to the MPLS tunnel for transmission. At the sink end, data packets are recovered and retain the original service features. In the tunnel, the intermediate nodes are called Transit nodes. Hence, a tunnel contains the Ingress node, Egress node and Transit nodes.

13.1.2 Application of the MPLS Tunnel

As the carrier of PWs in the network, the MPLS Tunnel provides the service tunnel to transmit service packets. The MPLS Tunnel can carry various services, such as IP packets, C-VLAN and S-VLAN packets, MPLS packets, and ATM packets. The MPLS Tunnel is mainly used for transparent transmission of point-to-point data service packets and Tunnel protection group.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 13-3

13 Configuring an MPLS Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

Transparent Transmission of Point-to-Point Data Packets

Commonly, the MPLS tunnel is used to provide a point-to-point service channel for services such as the E-Line service. In this way, provider edges (PEs) in a PSN network can transparently transmit services. Figure 13-2 shows how point-to-point data packets are transparently transmitted. Figure 13-2 Transparent transmission of point-to-point data packets
Node B

PE

MPLS tunnel Node B PE MPLS tunnel PE RNC

MPLS tunnel

PE

Node B

An edge node in one network accesses the services from Node B, and transports the services to the RNC connected to another PE. For such transport, one point-to-point MPLS tunnel can be used. On the T2000, two schemes can be used to create such a unicast tunnel.
l

Configuration on a per-NE basis: Configure the ingress port and the IP address of the next hop at each NE involved in the MPLS tunnel. In this way, one unicast MPLS tunnel is created. Configuration by trail: This configuration is classified into static configuration and dynamic configuration.

Static configuration: Specify the source and sink NEs for the MPLS tunnel, and each NE involved in the tunnel. In this way, one unicast MPLS tunnel is created. Dynamic configuration: Only specify the source and sink NEs of the MPLS tunnel. The equipment then creates a unicast MPLS tunnel through signaling.

Tunnel Protection Group

The MPLS tunnels of the same type are created in one tunnel protection group. In this way, 1 +1 or 1:1 protection is provided to these MPLS tunnels. If the working MPLS tunnel fails, the Tunnel protection group ensures that services can still normally run.
13-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

13 Configuring an MPLS Tunnel

By using the T2000, the user can configure 1+1 or 1:1 protection for MPLS tunnels that carry important services. Figure 13-3 shows the protection principle for unicast tunnels. Figure 13-3 Protection principle for unicast tunnels
CE CE Working tunnel

Ingress node

Protection tunnel

Egress node

Configuration of source protection group

Configuration of sink protection group

13.2 MPLS Tunnel Configuration Flow

This section describes the operation tasks for configuring the MPLS Tunnel, and relations among these tasks. When configuring and managing the MPLS Tunnel, follow the configuration flow. Configure and manage MPLS Tunnels by following the configuration flow shown in Figure 13-4.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

13-5

13 Configuring an MPLS Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 13-4 MPLS Tunnel configuration flow

Required Optional Creating Network Start

Configure the network-side interface

Configure the LSR ID

Configure the control plane

Configure the Tunnel

End

For the tasks in Figure 13-4, see Table 13-1. Table 13-1 Tasks for configuring the MPLS Tunnel Task 1. Creating Network 2. Configure the network-side interface 3. Configure the LSR ID Remarks To create a network, you need to create NEs, configure NE data, and create fibers. Set the general attributes and Layer 3 attributes (tunnel enable status and IP address) for interfaces to carry the tunnel carrying. Configure the LSR ID of the NE and start of global label space. The LSR ID of the NE must be unique.

13-6

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

13 Configuring an MPLS Tunnel

Task 4. Configure the control plane

Remarks Set the protocol parameters related to the control plane to create the tunnel.
l

When you create a static MPLS tunnel to carry services, you does not need to set the parameters related to the control plane but you need to manually add labels. When you create a dynamic MPLS tunnel to carry services, the LDP automatically distributes labels. In this case, you need to set the parameters related to the control plane. 1. Set the IGP-ISIS protocol parameters. 2. Set the MPLS-RSVP protocol parameters.

When you create a static PW to carry services, you does not need to set the parameters related to the control plane but you need to manually add labels. When you create a dynamic PW to carry services, the LDP automatically distributes labels. In this case, you need to set the parameters related to the control plane. 1. Set the IGP-ISIS protocol parameters. 2. Set the MPLS-LDP protocol parameters.

5. Configure the Tunnel

A tunnel transmits the service.

l

If an static MPLS tunnel is required, configure an MPLS tunnel in the per-NE or per-trail mode. Specify the tunnel ID, set signaling type to static, name the tunnel, and specify the ingress node, egress node, and transit node. If a dynamic MPLS Tunnel is required, name the tunnel, set signaling type to dynamic, and specify the source node and sink node for the tunnel.

13.3 Configuring an MPLS Tunnel by Trail

Configuring MPLS tunnel by trail can be used to configure an MPLS tunnel. On the T2000, you can configure a static MPLS tunnel or a dynamic MPLS tunnel by trail. For a static MPLS tunnel, the involved NEs should be manually specified. For a dynamic MPLS tunnel, the involved NEs are determined by the RSVP-TE protocol through computation. On the T2000, the user can create or delete an MPLS tunnel. 13.3.1 Creating a Dynamic MPLS Tunnel and the FRR Protection by Using the Trail Function To fast create a dynamic MPLS tunnel by using the trail function, just specify the Ingress and Egress nodes of the MPLS tunnel. During creation of the MPLS tunnel, fast rerouting can be configured. 13.3.2 Creating a Static MPLS Tunnel by Using the Trail Function
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 13-7

13 Configuring an MPLS Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

To create a static MPLS tunnel by using the trail function, specify the NEs involved in the MPLS tunnel. 13.3.3 Deleting a Dynamic MPLS Tunnel by Trail To delete a dynamic MPLS tunnel by trail, directly delete it in the Trail > Tunnel Management > Dynamic Tunnel Management interface on the T2000, instead of deleting the related settings on each NE. 13.3.4 Deleting a Static MPLS Tunnel by Trail To delete a static MPLS tunnel by trail, directly delete it in the Trail > Tunnel Management > Static Tunnel Management interface on the T2000, instead of deleting the related settings on each NE.

13.3.1 Creating a Dynamic MPLS Tunnel and the FRR Protection by Using the Trail Function
To fast create a dynamic MPLS tunnel by using the trail function, just specify the Ingress and Egress nodes of the MPLS tunnel. During creation of the MPLS tunnel, fast rerouting can be configured.

Prerequisite
l l l l

You must be an NM user with "NE operator" authority or higher. You must complete the correct configuration of the port attributes. You must complete the correct setting of the LSR ID for each NE. You must complete the correct configuration of the control plan for each NE.

Procedure
Step 1 On the Main Topology, choose Trail > Tunnel > Tunnel Creation . The Create Tunnel dialog box is displayed. Step 2 Select Create Reverse Tunnel to configure the parameters for the forward and reverse dynamic tunnels.

13-8

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

13 Configuring an MPLS Tunnel

NOTE

Take the following precautions when setting each parameter.

l

Tunnel ID: You can manually set this parameter, or select automatic allocation from the drop-down menu to allocate a tunnel ID. When manually setting this parameter, enter the Tunnel ID manually. The value of the ID ranges from 1 to 65535. Signal type: Select dynamic. The signal type indicates that the MPLS Tunnel of this type is created.

Step 3 Click Next. In the Select Node dialog box, select Source Node and Sink Node. Step 4 Optional: Click Add to add the route restriction conditions of the forward route and reverse route. For route restrictions, set Route Constraint Port IP Address and Rerouting Mode.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

13-9

13 Configuring an MPLS Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

For Route Constraint Port IP Address, set the IP address of the port involved in the MPLS tunnel. For Rerouting Mode, set the excluded node, loose explicit node or strict explicit node.
l l

Exclude indicates that the created MPLS tunnel does not involve the Route Constraint Port IP Address. Include Loose indicates that the tunnel must traverse the ports with Route Constraint Port IP Address and must traverse the constraint ports in the same sequence in which the ports are added into the constraint list. There can be multiple hops between Include Loose constraint ports. That is, the number of hops along the tunnel can be larger than the number of constraint ports added in the constraint list for the tunnel. Include Strict indicates that the tunnel must traverse the ports with Route Constraint Port IP Address and must traverse the constraint ports in the same sequence in which the ports are added into the constraint list. There can be only one hop between Include Strict ports. That is, the Include Strict constraint port must be directly connected to the existing constraint port.

Step 5 Click Next. Set Setup Priority, Hold Priority, Color(0x), Mask(0x), Tunnel Type and ReRoute.

13-10

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

13 Configuring an MPLS Tunnel

Step 6 Optional: If the tunnel is the bypass tunnel for fast rerouting, set Tunnel Type to Bypass Tunnel.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

13-11

13 Configuring an MPLS Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 7 Optional: If the tunnel is the working tunnel for fast rerouting, set Tunnel Type to Primary Tunnel first. Then select Fast Re-Route to activate the grey area and configure the parameters.

NOTE

In this case, you can set FRR Protection Type and FRR Bandwidth(kbit/s). When an MPLS tunnel traverses the OptiX PTN 912, the OptiX PTN 912 supports the function of configuring FRR to enable switching of the dynamic MPLS tunnels with the FRR attributes. The OptiX PTN 912, however, does not work as a local repair point (LRP) to perform FRR switching. Point of local repair refers to the source node on the bypass tunnel for FRR. The source node should be on a dynamic MPLS tunnel with the FRR attribute and cannot be the tail node on the dynamic MPLS tunnel.

Step 8 Click Next. A dialog box is displayed to show information on the created tunnel. Step 9 Click Finish. The progress bar is displayed to show the creation progress. The Operation Result dialog box is displayed, indicating that the dynamic tunnel is successfully created. Then, click Close. Step 10 Optional: Set the protection port of the bypass tunnel. 1. 2. In the Main Topology, choose Trail > Tunnel > Dynamic Tunnel Management. The Set Dynamic Tunnel Filter Criteria dialog box is displayed. Click Filter. Select a bypass tunnel in the tunnel list.
NOTE

If Tunnel Type is set to Bypass Tunnel for a tunnel, the tunnel is a bypass tunnel.

3.

Click the Protected Port tab and click Modify. The Modify Protected Port dialog box is displayed. Select the bypass tunnel protected port, and click
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

4.
13-12

. Then, click OK.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

13 Configuring an MPLS Tunnel

When the protection port of the bypass tunnel is configured, all the working tunnels that pass through this port and intersect with the sink node (MP node) of the bypass tunnel are protected by the bypass tunnel. To be protected by the bypass tunnel, the setup priority, hold priority, and color of the working tunnel must be consistent with the setup priority, hold priority, and color of the bypass tunnel. If these parameters of the working tunnel are inconsistent with that of the bypass tunnel, the working tunnel is not protected.

----End

13.3.2 Creating a Static MPLS Tunnel by Using the Trail Function

To create a static MPLS tunnel by using the trail function, specify the NEs involved in the MPLS tunnel.

Prerequisite
l l l

You must be an NM user with "NE operator" authority or higher. You must complete the correct configuration of the port attributes. You must complete the correct setting of the LSR ID for each NE.

Procedure
Step 1 On the Main Topology, choose Trail > Tunnel > Tunnel Creation. The Create Tunnel dialog box is displayed. Step 2 Select Create Reverse Tunnel to configure the parameters for the forward and reverse static tunnels.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

13-13

13 Configuring an MPLS Tunnel

NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

Take the following precautions when setting each parameter.

l

Tunnel ID: You can manually set this parameter, or select automatic allocation from the drop-down menu to allocate a tunnel ID. When manually setting this parameter, enter the Tunnel ID manually. The value of the ID ranges from 1 to 65535. Signal Type: Select static. The signal type indicates that the MPLS Tunnel of this type is created.

Step 3 Click Next. Select nodes from the Available NE. Click node, Egress node or Transit node.

to add each node as an Ingress

NOTE

When adding the transit node, follow the sequence of NEs that the link traverses in the networking.

Step 4 Click Next. Set parameters for nodes selected in the previous step. 1. 2. 3. 4. Ingress node: Set Out Port, Out Label and Next Hop Address. Egress node: Set In Port and In Label. Transit node: Set Out Port, Out Label, In Port, In Label and Next Hop Address. After you select Auto assign label, the system automatically assigns the In Label and Out Label for the Tunnel.
NOTE

If the ports along a tunnel are of different types (for example, an Ethernet port and a virtual port are of different types), de-select Filter Ports by Port Type to display all ports. If you select Filter Ports by Port Type, only the ports of the same type are displayed. The label value of the ingress node may be same as or different from the label value of the egress node. The label value of the egress node is signalled by the upstream node.

Step 5 Click Next. A dialog box is displayed to show information on the created tunnel. Step 6 Click Finish. A progress bar is displayed to show the creation progress. When the creation is complete, the Operation Result is displayed, indicating that the MPLS tunnel is successfully created. Then, click Close. ----End

13-14

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

13 Configuring an MPLS Tunnel

13.3.3 Deleting a Dynamic MPLS Tunnel by Trail

To delete a dynamic MPLS tunnel by trail, directly delete it in the Trail > Tunnel Management > Dynamic Tunnel Management interface on the T2000, instead of deleting the related settings on each NE.

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

Procedure
Step 1 On the Main Topology, choose Trail > Tunnel > Dynamic Tunnel Management to display the Dynamic Tunnel Management window. The Set Dynamic Tunnel Filter Criteria dialog box is displayed. Step 2 In the dialog box, set the filter parameters and click Filter. In Dynamic Tunnel Management window, the filtered dynamic tunnels are displayed. Step 3 Right-click the dynamic tunnel to be deleted and select Delete. A dialog box is displayed for confirmation. Click OK. Another dialog box is displayed. Click OK. A dialog box is then displayed, indicating that the dynamic tunnel is successfully deleted. Click Close. ----End

13.3.4 Deleting a Static MPLS Tunnel by Trail

To delete a static MPLS tunnel by trail, directly delete it in the Trail > Tunnel Management > Static Tunnel Management interface on the T2000, instead of deleting the related settings on each NE.

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

Procedure
Step 1 On the Main Topology, choose Trail > Tunnel > Tunnel Management > Static Tunnel Management to display the Static Tunnel Management window. The Set Tunnel Browse Filter Conditions dialog box is also displayed. Step 2 In the dialog box, set the filter parameters and click Filter. In Static Tunnel Management window, the filtered static tunnels are displayed. Step 3 Right-click the static tunnel to be deleted and select Delete. A dialog box is displayed for confirmation. In the dialog box, click OK. Another dialog box is displayed for confirmation. Click OK. Then, a dialog box is displayed, indicating that the static MPLS tunnel is successfully deleted. Click Close. ----End

13.4 Configuring an MPLS Tunnel on a Per-NE Basis

The per-NE configuration scheme can be used to create an MPLS tunnel. At each node involved in the tunnel, set the tunnel-related parameters. The per-NE configuration scheme can be used
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 13-15

13 Configuring an MPLS Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

to create a unicast MPLS tunnel. On the T2000, the user can create or delete a unicast MPLS tunnel. 13.4.1 Configuring Basic Attributes of the MPLS In the Basic Configuration interface, you can set LSR ID, Start of Global Label Space and Start of Multicast Label Space. 13.4.2 Creating an MPLS Tunnel on a Per-NE Basis You can create an end-to-end unicast MPLS tunnel on a per-NE basis. To create such a tunnel, create a tunnel at each node involved in the tunnel. 13.4.3 Modifying the Interface of the Static Unicast MPLS Tunnel In this user interface, you can modify the static unicast MPLS tunnel that is created successfully. You can modify the following: In Board/Logic interface Type, In Port, In Label, Out Board/ Logic Interface Type, Out Port, Out Label, and Next Hop Address. 13.4.4 Deleting an MPLS Tunnel on a Per-NE Basis To delete an MPLS tunnel using the single-station scheme, delete the MPLS tunnel at each node involved in the tunnel.

13.4.1 Configuring Basic Attributes of the MPLS

In the Basic Configuration interface, you can set LSR ID, Start of Global Label Space and Start of Multicast Label Space.

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

Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > MPLS Management > Basic Configuration from the Function Tree. Step 2 Set LSR ID, Start of Global Label Space and Start of Multicast Label Space.

CAUTION
If there are services on the NE, modifying LSR ID may result in NE reset and service interruption. ----End

13.4.2 Creating an MPLS Tunnel on a Per-NE Basis

You can create an end-to-end unicast MPLS tunnel on a per-NE basis. To create such a tunnel, create a tunnel at each node involved in the tunnel.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. You must complete the correct configuration of the port attributes.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

13-16

OptiX iManager T2000 Operation Guide for PTN NE Management

l

13 Configuring an MPLS Tunnel

You must complete the correct setting of the LSR ID for each NE.

Procedure
Step 1 Select the source NE of the tunnel in the NE Explorer. Choose Configuration > MPLS Management > Unicast Tunnel Management from Function Tree. Step 2 Click the Static Tunnel tab and click New. The New Unicast Tunnel dialog box is displayed. Step 3 Select Create Reverse Tunnel to set parameters for the forward and reverse tunnels.

NOTE

When Node Type is set to Egress, Bandwidth(kbit/s) must be consistent with the tunnel bandwidth in the Ingress direction and cannot be set. For Next Hop Address, select the IP address of the interface of the next node, or the LSR ID of the next node.

Step 4 Click OK to finish creation of the static tunnel. Step 5 Follow Steps 1 - 4 to create static tunnels for Transit nodes and the Egress node. Step 6 Optional: Select the created tunnel. Double-click the Vlan ID filed, and differentiate different tunnels by adding a VLAN ID.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 13-17

13 Configuring an MPLS Tunnel

NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

If the created tunnel is carried by VLAN sub-interfaces, Vlan ID cannot be set for the tunnel.

----End

13.4.3 Modifying the Interface of the Static Unicast MPLS Tunnel

In this user interface, you can modify the static unicast MPLS tunnel that is created successfully. You can modify the following: In Board/Logic interface Type, In Port, In Label, Out Board/ Logic Interface Type, Out Port, Out Label, and Next Hop Address.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. A static unicast MPLS tunnel must be created successfully.

Procedure
Step 1 In the NE Explorer, select an NE and then choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Click the Static Tunnel tab. Step 2 Select a created tunnel. Click Modify and the Modify Unicast Tunnel dialog box is displayed. Step 3 Modify the interface of the static tunnel.
NOTE

When modifying parameters, note the following:

l l l

In the case of an ingress tunnel, you can modify Out Board/Logic Interface Type, Out Port, Out Label, and Next Hop Address. In the case of a transit tunnel, you can modify In Board/Logic interface Type, In Port, In Label, Out Board/Logic Interface Type, Out Port, Out Label, and Next Hop Address. In the case of an egress tunnel, you can modify In Board/Logic interface Type, In Port, and In Label.

Step 4 Click OK. The Warning dialog box is displayed, indicating that the operation may interrupt services. Step 5 Click OK. The Operation Result dialog box is displayed indicating that the operation is successful. Step 6 Click Close. ----End

13.4.4 Deleting an MPLS Tunnel on a Per-NE Basis

To delete an MPLS tunnel using the single-station scheme, delete the MPLS tunnel at each node involved in the tunnel.

Prerequisite
You must be an NM user with "NE operator" authority or higher.
13-18 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

13 Configuring an MPLS Tunnel

Procedure
Step 1 Select the source NE of the tunnel in the NE Explorer. Choose Configuration > MPLS Management > Unicast Tunnel Management from Function Tree. Step 2 Click the Static Tunnel tab. Select the tunnel to be deleted from the static MPLS tunnel list. Step 3 Click Delete. A dialog box is displayed for confirmation. Step 4 Follow Steps 1 - 3 to delete static tunnels for Transit nodes and the Egress node. ----End

13.5 Querying the Tunnel Label Information

On the NE, the label for each tunnel is unique. By querying the tunnel label information, you can learn the usage of tunnel labels. Thus, you can avoid the conflict of labels when creating a static tunnel.

Prerequisite
You must be an NM user with "NE monitor" authority or higher. You must complete the creation of an MPLS tunnel.

Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > MPLS Management > MPLS Label Management from the Function Tree. Step 2 In the Tunnel Label tab, click Query to view the tunnel label information. ----End

13.6 Configuration Case of the Dynamic MPLS Tunnel

This section describes how to configure a dynamic MPLS tunnel. The configuration case and configuration flowchart help you better understand the process of configuring a dynamic MPLS tunnel. The configuration case includes tunnel planning and tunnel configuration. 13.6.1 Networking Diagram This section describes the networking diagram for the example of configuring an MPLS tunnel. 13.6.2 Service Planning The services between the branches of Company A are carried by the primary tunnel. Bypass tunnel 1 and bypass tunnel 2 provide FRR protection for the primary tunnel. 13.6.3 Creating a Dynamic MPLS Tunnel This section describes how to configure the dynamic MPLS Tunnel in the example.

13.6.1 Networking Diagram

This section describes the networking diagram for the example of configuring an MPLS tunnel.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 13-19

13 Configuring an MPLS Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

As shown in Figure 13-5, Company A has branches in City 1 and City 2. Real-time service transmission is required between the branches. In this case, an MPLS tunnel can be created to carry the real-time services. Real-time services require high network security. Hence, FRR protection should also be configured for the MPLS tunnel between NE1 and NE3.
l l

The NE1-to-NE3 primary tunnel is along the NE1-NE2-NE3 trail. NE2 is the transit node. The NE1-to-NE3 bypass tunnel 1 is along the NE1-NE4-NE3 trail. When the NE1-NE2 link fails or the NE2 has a fault, bypass tunnel 1 protects the primary tunnel. The NE2-to-NE3 bypass tunnel 2 is along the NE2-NE4-NE3 trail. When the NE2-NE3 link fails, bypass tunnel 2 protects the primary tunnel.

Figure 13-5 Networking diagram of an MPLS tunnel

NE4

NE1
A Company City1

NE3
A Company City2

NE2 Primary Tunnel

Bypass Tunnel 1 Bypass Tunnel 2

Figure 13-6 shows the NE planning. NE1 is an OptiX PTN 1900 NE. NE2, NE3 and NE4 are OptiX PTN 3900 NEs. Figure 13-6 NE planning
10.1.3.1 1-EG16-1 10.1.3.2 4-EFG2-2 10.1.4.1 1EG16-3

NE4

10.1.5.2 1-EG16-2 10.1.5.1 1-EG16-2

NE1
A Company 4-EFG2-1 City1 10.1.1.2 1-EG16-1 10.1.1.1 1EG16-3

NE3
10.1.2.1 10.1.4.2 1-EG16-2 1-EG16-1 A Company City2

NE2

10.1.2.2

Primary Tunnel Bypass Tunnel 1 Bypass Tunnel 2

13-20

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

13 Configuring an MPLS Tunnel

13.6.2 Service Planning

The services between the branches of Company A are carried by the primary tunnel. Bypass tunnel 1 and bypass tunnel 2 provide FRR protection for the primary tunnel. On the NNI side of the NEs, the GE boards are used and a GE ring is built on the boards. Table 13-2 lists the planning details of NE parameters. Table 13-2 Configuration parameters of NEs NEs LSR ID Interface 4-EFG2-1(Port-1) 4-EFG2-2(Port-2) 1-EG16-1(Port-1) NE2 1.0.0.2 1-EG16-2(Port-2) 1-EG16-3(Port-3) NE3 1.0.0.3 1-EG16-1(Port-1) 1-EG16-2(Port-2) 1-EG16-1(Port-1) NE4 1.0.0.4 1-EG16-2(Port-2) 1-EG16-3(Port-3) IP Address of the Interface 10.1.1.2 10.1.3.2 10.1.1.1 10.1.2.2 10.1.4.2 10.1.2.1 10.1.5.1 10.1.5.2 10.1.3.1 10.1.4.1 Subnet Mask of the Interface 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252

NE1

1.0.0.1

Since the service bandwidth is 10 Mbit/s, the bypass tunnel should have bandwidth more than 10 Mbit/s. In addition, the service travels through several NEs. Hence, several bypass tunnels are required to completely protect the tunnel for the service. According to the actual condition, two bypass tunnels are planned for the FRR. Table 13-3 lists the planned parameters of the primary tunnel and the two bypass tunnels. Table 13-3 Configuration parameters of Tunnels Parameter Tunnel ID Primary Tunnel Positive: 1 Reverse: 2 Name Positive: Tunnel-0001 Reverse: Tunnel-0002 Signal Type Scheduling Type
Issue 01 (2009-06-30)

Bypass Tunnel 1 Positive: 3 Reverse: 4 Positive: Tunnel-0003 Reverse: Tunnel-0004 Dynamic E-LSP

Bypass Tunnel 2 Positive: 5 Reverse: 6 Positive: Tunnel-0005 Reverse: Tunnel-0006 Dynamic E-LSP
13-21

Dynamic E-LSP

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

13 Configuring an MPLS Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

Parameter Bandwidth (kbit/s) Tunnel Source Node Tunnel Sink Node Positive Route Constraint Port IP Address

Primary Tunnel 10240 NE1 NE3 IP addresses of ingress port of NE2: 1-EG16-1: 10.1.1.1 IP addresses of ingress port of NE3: 1-EG16-1: 10.1.2.1

Bypass Tunnel 1 10240 NE1 NE3 IP addresses of ingress port of NE4: 1-EG16-1: 10.1.3.1 IP addresses of ingress port of NE3: 1-EG16-2: 10.1.5.1 IP addresses of ingress port of NE4: 1-EG16-2: 10.1.5.2 IP addresses of ingress port of NE1: 4-EFG2-2: 10.1.3.2 Include Strict

Bypass Tunnel 2 10240 NE2 NE3 IP addresses of ingress port of NE4: 1-EG16-3: 10.1.4.1 IP addresses of ingress port of NE3: 1-EG16-2: 10.1.5.1 IP addresses of ingress port of NE4: 1-EG16-2: 10.1.5.2 IP addresses of ingress port of NE2: 1-EG16-3: 10.1.4.2 Include Strict

Reverse Route Constraint Port IP Address

IP addresses of ingress port of NE2: 1-EG16-2: 10.1.2.2 IP addresses of ingress port of NE1: 4-EFG2-1: 10.1.1.2

Rerouting Mode

Include Strict

Note: In this case, the subnet mask at each NNI is 255.255.255.252.

13.6.3 Creating a Dynamic MPLS Tunnel

This section describes how to configure the dynamic MPLS Tunnel in the example.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must understand the networking, requirements and service planning of the example. A network must be created.

Procedure
Step 1 Set LSR IDs. 1. 2. In the NE Explorer, select the NE1 and choose Configuration > MPLS Management > Basic Configuration from the Function Tree. Set LSR ID, Start of Global Label Space and Start of Multicast Label Space. Click Apply. The configuration parameters are as follows:
l l

LSR ID: 1.0.0.1 (The LSR ID must be unique in the entire network.) Start of Global Label Space: 0 (The minimum values of egress and ingress labels of the unicast tunnel.)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

13-22

OptiX iManager T2000 Operation Guide for PTN NE Management

13 Configuring an MPLS Tunnel

3.

Display the NE Explorer for NE2, NE3, and NE4 separately. Set the parameters such as LSR ID of each NE by following the previous two steps. The configuration parameters are as follows:
l l l

NE2 LSR ID: 1.0.0.2 NE3 LSR ID: 1.0.0.3 NE4 LSR ID: 1.0.0.4

Step 2 Configure NNI interfaces. 1. 2. In the NE Explorer, select NE1 and choose Configuration > Interface Management > SDH Interface from the Function Tree to configure the network-side interface. In the General Attributes tab, select the 5-POD41-1(Port-1) and 5-POD41-2(Port-2). Right click the Port Mode filed, and select Layer 3. Set the parameters as required, and click Apply. Set Encapsulation to PPP and set the port name as required. Click Apply. The configuration parameters are as follows: Encapsulation: PPP (Currently, the POS port supports only the PPP. Before setting the Layer 3 attributes for the POS port, set the encapsulation type to PPP.) 3. Select the 5-POD41-1(Port-1) and 5-POD41-2(Port-2) in the Layer 3 Attributes tab. Right click the Enable Tunnel field and select Enabled. Right-click the Specify IP field and choose Manually. Then, set the parameters such as IP Address and IP Mask. Click Apply. The configuration parameters are as follows:
l l

Enable Tunnel: Enabled Max Reserved Bandwidth (kbit/s): 155500 (The maximum reserved bandwidth should not exceed the physical bandwidth of the bearer port.) TE Measurement: 10 (The link with a smaller TE measurement value is preferred for route selection of a tunnel. You can intervene in the route selection by adjusting the TE measurement of the link. The smaller the value of the TE measurement, the higher the priority of the link. ) Specify IP: Manually (Manually indicates that you can set the IP address of the port.) 5-POD41-1(Port-1) IP Address: 10.1.3.2 5-POD41-2(Port-2) IP Address: 10.1.1.2 IP Mask: 255.255.255.252

l l l l

4.

Display the NE Explorer for NE2, NE3, and NE4 separately. Perform 1 through 3 to set parameters of each related interface. The configuration parameters are as follows: Set the parameters of each interface the same as NE1-5-POD41 and set different IP addresses for them.
l l l l l

NE2-19-POD41-1(Port-1) IP Mask: 10.1.1.1 NE2-19-POD41-2(Port-2) IP Mask: 10.1.2.2 NE2-20-POD41-1(Port-1) IP Mask: 10.1.4.2 NE3-19-POD41-1(Port-1) IP Mask: 10.1.2.1 NE3-19-POD41-2(Port-2) IP Mask: 10.1.5.1
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 13-23

Issue 01 (2009-06-30)

13 Configuring an MPLS Tunnel

l l l

OptiX iManager T2000 Operation Guide for PTN NE Management

NE4-19-POD41-1(Port-1) IP Mask: 10.1.5.2 NE4-19-POD41-2(Port-2) IP Mask: 10.1.3.1 NE4-20-POD41-1(Port-1) IP Mask: 10.1.4.1

Step 3 Configure the control plane. 1. 2. In the NE Explorer, select an NE1 and choose Configuration > Control Plane Configuration > IGP-ISIS Configuration from the Function Tree. Choose the Port Configuration tab and then click New. Click Add in the dialog box displayed. Then Select 5-POD41-1(Port-1) and 5-POD41-2(Port-2) in the port tab. Click OK. The configuration parameters are as follows:
l l

Link Level: level-1-2 LSP Retransmission Interval(s): 5 (In the case of a point-to-point link, if the local equipment fails to receive any response in a period after transmitting the LSP, the local equipment considers that the LSP is lost or discarded. To ensure the transmission reliability, the local equipment transmits the LSP again.) Minimum LSP Transmission Interval (ms): 30

3.

Optional: Choose Configuration > Control Plane Configuration > MPLS-LDP Configuration from the Function Tree.
NOTE

When creating a dynamic PW to carry services, set the parameters related to MPLS-LDP.

4.

Optional: Click Create. Enter the ID of the opposite NE in the Create LDP Peer Entity dialog box. Click OK. The configuration parameters are as follows:
l

Opposite LSR ID: 1.0.0.3 (The opposite LSR ID indicates the LSR ID of the terminal NE on the PW, that is, NE3 in this case.) Hello Send Interval(s): 10 (The Hello packets are periodically sent to maintain the neighborship.) KeepAlive Send Interval(s): 10 (The KeepAlive packets are periodically sent to maintain the LDP session.)

5.

Display the NE Explorer for NE2 and NE3 separately. Perform Step 3.1 through Step 3.4 to set the parameters related to the control plane. Set the IS-IS parameters of NE2 and NE3 as the same as the IS-IS parameters of NE1. Set the LDP parameters as follows:
l

NE2 LDP parameters

Opposite LSR ID: 1.0.0.3 (The opposite LSR ID indicates the LSR ID of the terminal NE on the PW, that is, NE3 in this case.) NE3-NE1 peers Opposite LSR ID: 1.0.0.1 (The opposite LSR ID indicates the LSR ID of the terminal NE on the PW, that is, NE1 in this case.)

NE3 LDP parameters

NE3-NE2 peers Opposite LSR ID: 1.0.0.2 (The opposite LSR ID indicates the LSR ID of the terminal NE on the PW, that is, NE2 in this case.)

13-24

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

13 Configuring an MPLS Tunnel

Step 4 Creating Primary MPLS Tunnel. 1. 2. On the Main Topology, choose Trail > Tunnel > Tunnel Creation. The Create Tunnel dialog box is displayed. Select Create Reverse Tunnel, and configure parameters for the positive tunnel and reverse tunnel in the General Attributes.

The configuration parameters are as follows:

l l l

Tunnel ID: 1 (Positive), 2 (Reverse) Name: Tunnel-0001 (Positive), Tunnel-0002 (Reverse) Signal Type: Dynamic (If you set signal type to dynamic, the LDP distributes labels and the tunnel is a dynamic tunnel; if you set signal type to static, labels are manually added and the tunnel is a static tunnel.) Scheduling Type: E-LSP

E-LSP indicates that the tunnel determines the scheduling priority and discard priority of packets according to the EXP information. On one MPLS tunnel of the E-LSP type, there can be a maximum of eight types of PWs. L-LSP indicates that the tunnel determines the scheduling policy of packets according to the MPLS labels and determines the discard policy of packets according to the EXP information. On one MPLS tunnel of the L-LSP type, there can be a maximum of one type of PWs. Currently, the OptiX PTN equipment does not support the L-LSP type.

l l

EXP:- (tunnel priority.) Bandwidth (kbit/s): 10240 (Set the bandwidth according to networking planning.)

3.

Click Next, and select Source Node and Sink Node. Click Add to add route restrictions.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

13-25

13 Configuring an MPLS Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

The configuration parameters are as follows:

l l l l

Source Node: NE1 Sink Node: NE3 Positive Route Constraint Port IP Address: 10.1.1.1, 10.1.2.1, Include Strict Reverse Route Constraint Port IP Address: 10.1.2.2, 10.1.1.2, Include Strict

4.

Click Next. Set the parameters such as Setup Priority and Hold Priority for the tunnel according to the planning. Then, click Next. Confirm the tunnel information and then click Finish. The configuration parameters are as follows:
l

Setup Priority: 7 (Setup priority is specified for an MPLS tunnel during creation. "0" indicates the highest priority. In the case insufficiency of resources, the MPLS tunnel of a higher setup priority can preempt the bandwidth of other MPLS tunnels and thus can be created successfully.) Hold Priority: 0 (Hold priority is specified for an MPLS tunnel after creation. "0" indicates the highest priority. In the case of insufficiency of resources, the bandwidth for the MPLS tunnel of a higher hold priority is less likely to be preempted by other tunnels. When creating a dynamic tunnel, make sure that the hold priority is higher or equal to the setup priority.) Color(0x): 0 (Set the affinity attribute of a link. When the primary tunnel is faulty, the link with the same color is preferred during rerouting. When the affinity attribute of links is not required, adopt the default value.) Mask(0x): 0 (Set the number of bits of the mask. Match the number of bits of a mask with the link color. Select the route of a matching link color.) Tunnel Type: Primary Tunnel (You can set the tunnel type to primary tunnel or bypass tunnel. According to the planning, the tunnel is a primary tunnel in this case.) Fast Re-Route: Selected
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

13-26

OptiX iManager T2000 Operation Guide for PTN NE Management

l

13 Configuring an MPLS Tunnel

FRR Type: Facility Mode (In the facility mode, one LSP tunnel protects multiple LSP tunnels. Currently, the OptiX PTN equipment supports only the facility backup mode.) FRR Protection Type: Protection Link Mode

In the case of the protection node mode, the bypass tunnel selected by the PLR must protect the downstream node adjacent to the PLR, and the links between them. If any other link is faulty, the FRR protection switching is triggered through the control plane. This process takes a relatively long time. In the case of the protection link mode, the bypass tunnel selected by the PLR must protect the link between the PLR and downstream adjacent node. The protection link mode is recommended.

FRR Bandwidth(kbit/s): No Limit (Set the bandwidth according to networking planning.)

Step 5 Creating Primary MPLS Tunnel. 1. Configure the General Attributes of Bypass Tunnel1 by following Step 4.1 to Step 4.2. The configuration parameters are as follows:
l l l l l l

Tunnel ID: 3 (Positive), 4 (Reverse) Name: Tunnel-0003 (Positive), Tunnel-0004 (Reverse) Signal Type: Dynamic Scheduling Type: E-LSP EXP:- (tunnel priority) Bandwidth (kbit/s): 10240 (Set the bandwidth according to networking planning.)

2.

Click Next, and select Source Node and Sink Node. Click Add to add route restrictions. The configuration parameters are as follows:
l l l l

Source Node: NE1 Sink Node: NE3 Positive Route Constraint Port IP Address: 10.1.3.1, 10.1.5.1, Include Strict Reverse Route Constraint Port IP Address: 10.1.5.2, 10.1.3.2, Include Strict

3.

Click Next. Set the parameters such as Setup Priority and Hold Priority for the tunnel according to the planning. Then, click Next. Confirm the tunnel information and then click Finish. The configuration parameters are as follows:
l

Setup Priority: 7 (The setup priority of the bypass tunnel must be the same as the setup priority of the primary tunnel.) Hold Priority: 0 (The hold priority of the bypass tunnel must be the same as the hold priority of the primary tunnel.) Color(0x): 0 (The link color of the bypass tunnel must be the same as the link color of the primary tunnel.) Mask(0x): 0 (Set this parameter the same as the primary tunnel.) Tunnel Type: Bypass Tunnel (According to the planning, the tunnel is a bypass tunnel in this case.) Re-Route: selected
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 13-27

l l

Issue 01 (2009-06-30)

13 Configuring an MPLS Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

4.

Create Bypass Tunnel2 by following Step 5.1 to Step 5.3. The configuration parameters are as follows:
l

General Attributes

Tunnel ID: 5(Positive), 6(Reverse) Name: Tunnel-0005(Positive), Tunnel-0006(Reverse) Signal Type: Dynamic Scheduling Type: E-LSP EXP: Bandwidth(kbit/s): 10240 Source Node: NE2 Sink Node: NE3 Positive Route Constraint Port IP Address: 10.1.4.1, 10.1.5.1, Include Strict Reverse Route Constraint Port IP Address: 10.1.5.2, 10.1.4.2, Include Strict Setup Priority: 7 Hold Priority: 0 Color(0x): 0 Mask(0x): 0 Tunnel Type: Bypass Tunnell (According to the planning, the tunnel is a bypass tunnel in this case.) Re-Route: selected

Route Constraint

Tunnel Management Attributes

----End

13.7 Configuration Case of the Static MPLS Tunnel

This section describes how to configure a static MPLS tunnel by using the trail function and on a per-NE basis. The configuration case and configuration flowchart help you better understand the service configuration process. The configuration includes networking, service planning, and configuration process. 13.7.1 Networking Diagram This section shows the networking diagram for the example of configuring a static MPLS tunnel. 13.7.2 Service Planning There are services between NodeB and RNC. Two static MPLS tunnels are to be created. One is the working tunnel and the other is the protection tunnel. Then, the services can be securely transmitted on the network. 13.7.3 Creating a Static MPLS Tunnel by Using the Trail Function This section describes how to configure the static MPLS Tunnel in the example by using the trail function. 13.7.4 Configuring a Static MPLS Tunnel on a Per-NE Basis
13-28 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

13 Configuring an MPLS Tunnel

This section describes how to configure the static MPLS Tunnel in the example on a per-NE basis.

13.7.1 Networking Diagram

This section shows the networking diagram for the example of configuring a static MPLS tunnel. As shown in Figure 13-7, the service between NodeB and RNC is to be carried by a static MPLS tunnel. NE1 accesses the service from NodeB. Then, the service is transmitted to the 10GE ring on the convergence layer through the GE ring on the access layer. Finally, the service is converged at NE3 and transmitted to RNC. If the service requires high network security, configure the MPLS APS protection to ensure service transmission. For details on how to configure the MPLS APS protection, refer to 16.2 Configuring MPLS Tunnel Protection.
l l

Working tunnel: NE1-NE2-NE3. NE2 is a transit node. Protection tunnel: NE1-NE6-NE5-NE4-NE3. NE6, NE5, and NE4 are transit nodes. When the working tunnel becomes faulty, the service on it is switched to the protection tunnel for protection.

Figure 13-7 Networking diagram of an MPLS tunnel

NE4 NE5 NE6 GE ring on access layer NE1 10GE ring on convergence layer

NE2

NE3

RNC
Working Tunnel

NodeB
OptiX PTN 3900

Protection Tunnel

OptiX PTN 1900

NE1 and NE6 are OptiX PTN 1900 NEs. NE2, NE3, NE4 and NE5 are OptiX PTN 3900 NEs. Figure 13-8 shows the planning details of boards on the NE and interfaces on the boards.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

13-29

13 Configuring an MPLS Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 13-8 NE planning

3-EG16-1(Port-1) 10.0.4.2 1-EX2-1(Port-1) 10.0.3.2 1-EX2-2(Port-2) 10.0.3.1 1-EX2-1(Port-1) 10.0.2.2

NE5
4-EFG2-2(Port-2) 10.0.4.1

NE6

GE ring on access layer NE1

3-EG16-1(Port-1) 10.0.0.2

NE4 10GE ring on convergence layer

1-EX2-1(Port-1) 10.0.1.2 1-EX2-2(Port-2) 10.0.2.1

4-EFG2-1(Port-1) 10.0.5.2

NE2
4-EFG2-1(Port-1) 10.0.0.1

1-EX2-1(Port-1) 10.0.1.1

NE3

4-EFG2-2(Port-2) 10.0.5.1

RNC
Protected tunnel

NodeB
OptiX PTN 3900

Bypass tunnel

OptiX PTN 1900

13.7.2 Service Planning

There are services between NodeB and RNC. Two static MPLS tunnels are to be created. One is the working tunnel and the other is the protection tunnel. Then, the services can be securely transmitted on the network. Table 13-4 lists the configuration parameters of NEs. Table 13-4 Configuration parameters of NEs NE NE1 LSR ID 1.0.0.1 Port 4-EFG2-1(Port-1) 4-EFG2-2(Port-2) 3-EG16-1(Port-1) 1-EX2-1(Port-1) 1-EX2-1(Port-1) 1-EX2-2(Port-2) 1-EX2-1(Port-1) 1-EX2-2(Port-2) 1-EX2-1(Port-1) 3-EG16-1(Port-1) 4-EFG2-1(Port-1) 4-EFG2-2(Port-2) Port IP Address 10.0.0.1 10.0.5.1 10.0.0.2 10.0.1.1 10.0.1.2 10.0.2.1 10.0.2.2 10.0.3.1 10.0.3.2 10.0.4.2 10.0.5.2 10.0.4.1 IP Mask 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252
Issue 01 (2009-06-30)

NE2

1.0.0.2

NE3

1.0.0.3

NE4

1.0.0.4

NE5

1.0.0.5

NE6

1.0.0.6

13-30

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX iManager T2000 Operation Guide for PTN NE Management

13 Configuring an MPLS Tunnel

Table 13-5 lists the configuration parameters of Tunnels. Table 13-5 Planning of Tunnel parameters Parameters Tunnel ID Name 100 Working TunnelPositive Static E-LSP No Limit NE1 NE2 NE3 NE1
l

Working Tunnel 101 Working TunnelReverse Static E-LSP No Limit NE3 NE2 NE1 NE3
l

Protection Tunnel 120 Protection Tunnel-Positive Static E-LSP No Limit NE1 NE6, NE5, NE4 NE3 NE1
l

121 Protection Tunnel-Reverse Static E-LSP No Limit NE3 NE4, NE5, NE6 NE1 NE3
l

Signal Type Scheduling Type Bandwidth (kbit/s) Ingress Node Transit Node Egress Node Ingress Node Route Information

Out Port: 4EFG2-1 (Port-1) Out Label: 20

Out Port: 1EX2-1(Port-1) Out Label: 21

Out Port: 4EFG2-2 (Port-2) Out Label: 22

Out Port: 1EX2-2 (Port-2) Out Label: 23

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

13-31

13 Configuring an MPLS Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

Parameters Transit Node Route Information NE2

l

Working Tunnel NE2

l

Protection Tunnel NE6

l

NE4
l

In Port: 3EG16-1 (Port-1) In Label: 20 Out Port: 1EX2-1 (Port-1) Out Label: 30

In Port: 1EX2-1(Port-1) In Label: 21 Out Port: 3EG16-1 (Port-1) Out Label: 31

l l

In Port: 4EFG2-1 (Port-1) In Label: 22 Out Port: 4EFG2-2 (Port-2) Out Label: 32 In Port: 3EG16-1 (Port-1) In Label: 32 Out Port: 1EX2-1 (Port-1) Out Label: 42 In Port: 1EX2-2 (Port-2) In Label: 42 Out Port: 1EX2-1 (Port-1) Out Label: 52

In Port: 1EX2-1 (Port-1) In Label: 23 Out Port: 1EX2-2 (Port-2) Out Label: 33 In Port: 1EX2-1 (Port-1) In Label: 33 Out Port: 3EG16-1 (Port-1) Out Label: 43 In Port: 4EFG2-2 (Port-2) In Label: 43 Out Port: 4EFG2-1 (Port-1) Out Label: 53

l l

l l

l l

NE5
l

NE5
l

l l

l l

NE4
l

NE6
l

l l

l l

Egress Node Route Information

NE3
l

NE1
l

NE3
l

NE1
l

In Port: 1EX2-1 (Port-1) In Label: 30

In Port: 4EFG2-1 (Port-1) In Label: 31

In Port: 1EX2-2 (Port-2) In Label: 52

In Port: 4EFG2-2 (Port-2) In Label: 53

13.7.3 Creating a Static MPLS Tunnel by Using the Trail Function

This section describes how to configure the static MPLS Tunnel in the example by using the trail function.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must understand the networking, requirements and service planning of the example.
13-32 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

13 Configuring an MPLS Tunnel

A network must be created.

Procedure
Step 1 Set LSR IDs. 1. 2. In the NE Explorer, select the NE1 and chooseConfiguration > MPLS Management > Basic Configuration from the Function Tree. Set LSR ID, Start of Global Label Space and Start of Multicast Label Space. Click Apply. The configuration parameters are as follows:
l l

LSR ID: 1.0.0.1 (The LSR ID must be unique in the entire network.) Start of Global Label Space: 0 (The minimum values of egress and ingress labels of the unicast tunnel.)

3.

Display the NE Explorer of NE2, NE3, NE4, NE5, and NE6 separately and perform the preceding two steps to set the parameters such as LSR ID. The configuration parameters are as follows:
l l l l l

NE2 LSR ID: 1.0.0.2 NE3 LSR ID: 1.0.0.3 NE4 LSR ID: 1.0.0.4 NE5 LSR ID: 1.0.0.5 NE6 LSR ID: 1.0.0.6

Step 2 Configure NNI interfaces. 1. 2. In the NE Explorer, select NE1 and choose Configuration > Interface Management > Ethernet Interface from the Function Tree to configure the network-side interface. In the General Attributes tab, select the 4-EFG2-1(Port-1) and 4-EFG2-2(Port-2). Right click the Port Mode filed, and select Layer 3. Set the parameters as required, and click Apply.

The configuration parameters are as follows:

l l l

Enable Port: Enabled Port Mode: Layer 3 (The port carries a tunnel.) Working Mode: Auto-Negotiation (Set the working modes of the local port and opposite port as the same.) Max Frame Length (byte): 1620 (Set this parameter according to the length of data packets. All the received data packets that contain more bytes than the maximum frame length are discarded.)

3.

Select the 4-EFG2-1(Port-1) and 4-EFG2-2(Port-2) in the Layer 3 Attributes tab. Right click the Enable Tunnel field and select Enabled. Right-click the Specify IP field and choose Manually. Then, set the parameters such as IP Address and IP Mask. Click Apply. The configuration parameters are as follows:

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

13-33

13 Configuring an MPLS Tunnel

l l

OptiX iManager T2000 Operation Guide for PTN NE Management

Enable Tunnel: Enabled Max Reserved Bandwidth (kbit/s): 1000000 (The maximum reserved bandwidth should not exceed the physical bandwidth of the bearer port.) TE Measurement: 10 (The link with a smaller TE measurement value is preferred for route selection of a tunnel. You can intervene in the route selection by adjusting the TE measurement of the link. The smaller the value of the TE measurement, the higher the priority of the link. ) Specify IP: Manually (Manually indicates that you can set the IP address of the port.) 4-EFG2-1(Port-1) IP Address: 10.0.0.1 4-EFG2-2(Port-2) IP Address: 10.0.5.1 IP Mask: 255.255.255.252

l l l l

4.

Display the NE Explorer for NE2, NE3, and NE4 separately. Perform Step 2.1 through Step 2.3 to set parameters of each related interface. Set the parameters of each interface the same as NE1-4-EFG2-1(Port-1). The layer 3 attributes of each ports are as follows:
l

NE2-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.1.1

NE2-3-EG16-1(Port-1) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.0.2

NE3-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.1.2

NE3-1-EX2-2(Port-2) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.2.1

NE4-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.2.2

NE4-1-EX2-2(Port-2) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.3.1

NE5-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.3.2

NE5-3-EG16-1(Port-1) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.4.2

NE6-4-EFG2-1(Port-1) Max Reserved Bandwidth (kbit/s): 1000000

13-34

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

13 Configuring an MPLS Tunnel

IP Address: 10.0.5.2
l

NE6-4-EFG2-2(Port-2) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.4.1

Step 3 Creating Working MPLS Tunnels 1. 2. On the Main Topology, choose Trail > Tunnel Creation. The Create Tunnel dialog box is displayed. Select Create Reverse Tunnel, and configure parameters for the positive tunnel and reverse tunnel in the General Attributes.

The configuration parameters are as follows:

l l l

Tunnel ID: 100(Positive), 101(Reverse) Name: Working Tunnel-Positive, Working Tunnel-Reverse Signal Type: Static (If you set signal type to dynamic, the LDP distributes labels and the tunnel is a dynamic tunnel; if you set signal type to static, labels are manually added and the tunnel is a static tunnel.) Scheduling Type: E-LSP

E-LSP indicates that the tunnel determines the scheduling priority and discard priority of packets according to the EXP information. On one MPLS tunnel of the E-LSP type, there can be a maximum of eight types of PWs.

l l

EXP:- (Set the tunnel priority according to networking planning.) Bandwidth (kbit/s): No Limit (Set the bandwidth according to networking planning.)

3.

Click Next, and select Ingress Node, Egress Node and Transit Node to set route restrictions.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

13-35

13 Configuring an MPLS Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

The configuration parameters are as follows:

l

Ingress Node: NE1 (The source node on a tunnel is referred to as ingress node, that is, the node where the tunnel enters the network.) Egress Node: NE3 (The sink node on a tunnel is referred to as egress node, that is, the node where the tunnel exists the network.) Transit Node: NE2 (The pass-through node on a tunnel is referred to as transmit node.)

4.

Click Next. Set tunnel-related parameters and route constraints. Then, click Next. Confirm the tunnel information and then click Finish.

The configuration parameters are as follows:

l

Positive Route Information

NE1 Ingress Node

Out Port: 4-EFG2-1(Port-1) (the source port on the tunnel) Out Label: 20 (The local out label is the same as the downstream in label. Labels are used to forward packets.) Next Hop Address: 10.0.0.2
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

13-36

OptiX iManager T2000 Operation Guide for PTN NE Management

13 Configuring an MPLS Tunnel

NE2 Transit Node

In Port: 3-EG16-1(Port-1) In Label: 20 Out Port: 1-EX2-1(Port-1) Out Label: 30 Next Hop Address: 10.0.1.2 In Port: 1-EX2-1(Port-1) In Label: 30

NE3 Egress Node

Reverse Route Information

NE3 Ingress Node

Out Label: 21 In Label: 21 Out Label: 31 In Label: 31

NE2 Transit Node

NE1 Egress Node

Step 4 Creating Protection Tunnel. 1. Create protection Tunnel by following Step 3.1 toStep 3.4. The configuration parameters are as follows:
l

General Attributes

Tunnel ID: 120 (Positive), 121 (Reverse) Name: Protection Tunnel-Positive, Protection Tunnel-Reverse Signal Type: Static Scheduling Type: E-LSP EXP:Bandwidth (kbit/s): No Limit Ingress Node: NE1 Egress Node: NE3 Transit Node: NE6, NE5, NE4

Node Information

For the route information, see Table 13-5.

----End

13.7.4 Configuring a Static MPLS Tunnel on a Per-NE Basis

This section describes how to configure the static MPLS Tunnel in the example on a per-NE basis.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 13-37

13 Configuring an MPLS Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must understand the networking, requirements and service planning of the example. A network must be created.

Procedure
Step 1 Set LSR IDs. 1. 2. In the NE Explorer, select the NE1 and chooseConfiguration > MPLS Management > Basic Configuration from the Function Tree. Set LSR ID, Start of Global Label Space and Start of Multicast Label Space. Click Apply. The configuration parameters are as follows:
l l

LSR ID: 1.0.0.1 (The LSR ID must be unique in the entire network.) Start of Global Label Space: 0 (The minimum values of egress and ingress labels of the unicast tunnel.)

3.

Display the NE Explorer of NE2, NE3, NE4, NE5, and NE6 separately and perform the preceding two steps to set the parameters such as LSR ID. The configuration parameters are as follows:
l l l l l

NE2 LSR ID: 1.0.0.2 NE3 LSR ID: 1.0.0.3 NE4 LSR ID: 1.0.0.4 NE5 LSR ID: 1.0.0.5 NE6 LSR ID: 1.0.0.6

Step 2 Configure NNI interfaces. 1. 2. In the NE Explorer, select NE1 and choose Configuration > Interface Management > Ethernet Interface from the Function Tree to configure the network-side interface. In the General Attributes tab, select the 4-EFG2-1(Port-1) and 4-EFG2-2(Port-2). Right click the Port Mode filed, and select Layer 3. Set the parameters as required, and click Apply.

The configuration parameters are as follows:

l l l

Enable Port: Enabled Port Mode: Layer 3 (The port carries a tunnel.) Working Mode: Auto-Negotiation (Set the working modes of the local port and opposite port as the same.) Max Frame Length (byte): 1620 (Set this parameter according to the length of data packets. All the received data packets that contain more bytes than the maximum frame length are discarded.)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

13-38

OptiX iManager T2000 Operation Guide for PTN NE Management

13 Configuring an MPLS Tunnel

3.

Select the 4-EFG2-1(Port-1) and 4-EFG2-2(Port-2) in the Layer 3 Attributes tab. Right click the Enable Tunnel field and select Enabled. Right-click the Specify IP field and choose Manually. Then, set the parameters such as IP Address and IP Mask. Click Apply. The configuration parameters are as follows:
l l

Enable Tunnel: Enabled Max Reserved Bandwidth (kbit/s): 1000000 (The maximum reserved bandwidth should not exceed the physical bandwidth of the bearer port.) TE Measurement: 10 (The link with a smaller TE measurement value is preferred for route selection of a tunnel. You can intervene in the route selection by adjusting the TE measurement of the link. The smaller the value of the TE measurement, the higher the priority of the link. ) Specify IP: Manually (Manually indicates that you can set the IP address of the port.) 4-EFG2-1(Port-1) IP Address: 10.0.0.1 4-EFG2-2(Port-2) IP Address: 10.0.5.1 IP Mask: 255.255.255.252

l l l l

4.

Display the NE Explorer for NE2, NE3, and NE4 separately. Perform Step 2.1 through Step 2.3 to set parameters of each related interface. Set the parameters of each interface the same as NE1-4-EFG2-1(Port-1). The layer 3 attributes of each ports are as follows:
l

NE2-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.1.1

NE2-3-EG16-1(Port-1) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.0.2

NE3-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.1.2

NE3-1-EX2-2(Port-2) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.2.1

NE4-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.2.2

NE4-1-EX2-2(Port-2) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.3.1

NE5-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.3.2

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

13-39

13 Configuring an MPLS Tunnel

l

OptiX iManager T2000 Operation Guide for PTN NE Management

NE5-3-EG16-1(Port-1) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.4.2

NE6-4-EFG2-1(Port-1) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.5.2

NE6-4-EFG2-2(Port-2) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.4.1

Step 3 Creating Working MPLS Tunnels. 1. Select NE1 in the NE Explorer . Choose Configuration > MPLS Management > Unicast Tunnel Management from Function Tree. Click New and the New Unicast Tunnel dialog box is displayed. Configure parameters for the positive tunnel and reverse tunnel such as Tunnel ID, Tunnel name, port and labels. Click OKto finish creating the ingress node.

2.

The configuration parameters are as follows:

l l l l l l

Tunnel ID: 100(Positive), 101(Reverse) Tunnel Name: Working Tunnel-Positive, Working Tunnel-Reverse Node Type: Ingress(Positive), Egress(Reverse) Bandwidth (kbit/s): No Limit (Set the bandwidth according to networking planning.) Out Board/Logic Interface Type: 4-EFG2 (The source board of the Tunnel.) Out Port: 1(Port-1) (The source port of the Tunnel.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

13-40

OptiX iManager T2000 Operation Guide for PTN NE Management

l

13 Configuring an MPLS Tunnel

Next Hop Address: 10.0.0.2 (The IP address of the interface on the next node on the tunnel.) Sink Node: 1.0.0.3 (The LSR ID of the interface on the sink node on the tunnel.) Tunnel Type: E-LSP

l l

E-LSP indicates that the tunnel determines the scheduling priority and discard priority of packets according to the EXP information. On one MPLS tunnel of the E-LSP type, there can be a maximum of eight types of PWs.

EXP: none (Set the tunnel priority according to networking planning.)

3.

In the NE Explorer, select NE2. Then, configure the Tunnel parameters of the transit node by following Step 3.1 to Step 3.2.

Set related parameters and ensure that the general information of the tunnel is the same as that on NE1. The configuration parameters are as follows:
l l l l l l l l l

Node Type: Transit (NE2 is a transit node on the tunnel.) In Board/Logic Interface Type: 3-EG16 In Port: 1(Port-1) In Label: 20 (Positive), 21 (Reverse) Out Board/Logic Interface Type: 1-EX2 Out Port: 1(Port-1) Out Label: 30 (Positive), 31 (Reverse) Next Hop Address: 10.0.1.2 (Positive), 10.0.0.1 (Reverse) Source Node: 1.0.0.1 (Positive), 10.0.1.2 (Reverse) (The LSR ID of the source node on the tunnel.) Sink Node: 1.0.0.2. (The LSR ID of the sink node on the tunnel.)

4.

In the NE Explorer, select NE3. Then, configure the Tunnel parameters of the egress node by following Step 3.1 to Step 3.2.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 13-41

Issue 01 (2009-06-30)

13 Configuring an MPLS Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

Set related parameters and ensure that the general information of the tunnel is the same as that on NE1. The configuration parameters are as follows:
l l l l l l

Node Type: Egress (NE3 is a terminal node on the tunnel.) In Board/Logic Interface Type: 1-EX2 In Port: 1(Port-1) In Label: 30(Positive), Out Label: 31 (Reverse) Next Hop Address: -(Positive), 10.0.1.1 (Reverse) Source Node: 1.0.0.1 (Positive) (The LSR ID of the source node on the tunnel.)

Step 4 Creating Protection Tunnel. 1. Display the NE Explorer for NE1, NE6, NE5, NE4, and NE3 separately. Perform Step 3.1 through Step 3.4 to create the ingress node, transit node, and egress node on the bypass tunnel. The configuration parameters are as follows:
l l l l l l

Tunnel ID: 120 (Positive), 121 (Reverse) Tunnel Name: Protection Tunnel-Positive, Protection Tunnel-Reverse Bandwidth(kbit/s): No Limit Tunnel Type: E-LSP EXP: none For the route information, see Table 13-5.

----End

13-42

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

14 Configuring an IP Tunnel

14
About This Chapter

Configuring an IP Tunnel

When the services that cross an IP network need to be created, the OptiX PTN equipment supports carrying PWs over the IP tunnel. In this way, services can be transparently transmitted in an IP network. 14.1 IP Tunnel IP tunnel can be used to carry the ATM PWE3 service or the CES service. 14.2 Configuring a UDP PW Port Use the UDP port ID to encapsulate PW so that the service carried by the PW can be transmitted transparently through the third-part IP network. The UDP PW can only be carried on an IP tunnel, but not on a GRE tunnel. 14.3 Creating IP Tunnels In the offload scenario of a mobile communication system, you can transmit the client services by connecting an IP tunnel to the DSLAM. 14.4 Deleting IP Tunnels To release ports for other services, you can delete redundant IP tunnels. 14.5 IP Tunnel Configuration Example This topic describes the configuration example of creating an IP tunnel on a per-NE basis. In addition to the example, the configuration flow diagram is provided for you to learn the configuration process of services. The configuration example includes information about the configuration networking diagram, service planning, and configuration process.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

14-1

14 Configuring an IP Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

14.1 IP Tunnel
IP tunnel can be used to carry the ATM PWE3 service or the CES service. If ATM or CES emulation service that travels through an IP network is required, the PTN equipment can use the IP tunnel to carry the service. This complies with RFC 4023 as shown in Figure 14-1. 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 IP network between NE A and NE B does not support the MPLS. Figure 14-1 ATM PWE3 over IP tunnel
ATM switch PTN Router Router PTN ATM switch

IP network NE A ATM E1/STM-1 ATM PWE3 PW Label IP Ethernet ATM PWE3 PW Label IP Ethernet NE B ATM E1/STM-1

14.2 Configuring a UDP PW Port

Use the UDP port ID to encapsulate PW so that the service carried by the PW can be transmitted transparently through the third-part IP network. The UDP PW can only be carried on an IP tunnel, but not on a GRE tunnel.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > IP/GRE Tunnel Management > Basic Configuration from the Function Tree. Step 2 Configure the parameters related to the port of UDP PW. Click Apply.

----End

14-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

14 Configuring an IP Tunnel

14.3 Creating IP Tunnels

In the offload scenario of a mobile communication system, you can transmit the client services by connecting an IP tunnel to the DSLAM.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The static route must be configured.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > IP/GRE Tunnel Management > IP Tunnel Management from the Function Tree. Step 2 Click New and the Create IP Tunnel dialog box is displayed.

NOTE

Sink Port IP Address must be consistent with Sink Node IP in Static Route Management.

Step 3 Set parameters. Step 4 Click OK. A prompt appears indicating that the operation was successful. Click Close. Step 5 Optional: Select the created tunnel. Double-click the Vlan ID filed, and differentiate different tunnels by adding a VLAN ID.
NOTE

If the created tunnel is carried by VLAN sub-interfaces, Vlan ID cannot be set for the tunnel.

Step 6 Click Apply. ----End

14.4 Deleting IP Tunnels

To release ports for other services, you can delete redundant IP tunnels.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 14-3

14 Configuring an IP Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

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

Procedure
Step 1 In the NE Explorer, click an NE. Choose Configuration > IP Tunnel Management from the Function Tree. Step 2 Select an IP tunnel and click Delete. The Confirm dialog box is displayed. Click OK. A dialog box is displayed indicating that the operation is successful. Step 3 Click Close. ----End

14.5 IP Tunnel Configuration Example

This topic describes the configuration example of creating an IP tunnel on a per-NE basis. In addition to the example, the configuration flow diagram is provided for you to learn the configuration process of services. The configuration example includes information about the configuration networking diagram, service planning, and configuration process. 14.5.1 Configuration Networking Diagram This topic describes the networking of IP tunnel configuration. 14.5.2 Service Planning When there is service transmission between Node B and the RNC, you can create a working IP tunnel and a protection MPLS tunnel to ensure the security of service transmission in the network. 14.5.3 Creating an IP Tunnel on a Per-NE Basis This topic describes the process of creating an IP tunnel on a per-NE basis.

14.5.1 Configuration Networking Diagram

This topic describes the networking of IP tunnel configuration. As shown in Figure 14-2, the signal transmission between the PTN equipment needs to traverse a third-party IP network, and the services between Node B and RNC are carried by the IP tunnel. The outgoing services from Node B are accessed on NE1, are transmitted through a third-party IP network, converge on NE3, and are finally transmitted to the RNC. IP tunnel: NE1-a third-party network-NE3. As shown in Figure 14-2, for services that require high network security, you can create the MPLS APS protection to guarantee the service transmission. The PTN equipment supports the ability to protect the IP tunnel by creating the MPLS tunnel. For information on how to create the MPLS APS protection, see MPLS APS.
l l

Working IP tunnel: NE1-a third-party network-NE3. Protection MPLS tunnel: NE1-NE2-NE3, in which NE2 is a transit node. When the working IP tunnel is faulty, the services are switched to the protection MPLS tunnel.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

14-4

OptiX iManager T2000 Operation Guide for PTN NE Management

14 Configuring an IP Tunnel

Figure 14-2 IP tunnel networking application

DSLAM

Third-Party IP Network

Node B 1

NE1

NE3

RNC

PTN
NE2

IP Tunnel MPLS Tunnel

In Figure 14-3, NE1 is the PTN 950, while NE2 and NE3 are the PTN 3900s. Figure 14-3 shows the planning for boards and interfaces on each NE. Figure 14-3 NE planning

DSLAM

Third-Party IP Network

10.0.2.2

10.0.5.2 4-SHD4-1 (Port -1) NE1 10.0.5.1 2-EG2-1 (Port -1) 10.0.0.1 3-EG16-1 (Port -1) 10.0.2.1 1-EX2-1 (Port -1) 10.0.1.2 NE3 RNC

Node B 1

PTN
NE2

3-EG16-1 (Port -1) 10.0.0.2

1-EX2-1 (Port -1) 10.0.1.1 I P Tunnel MPLS Tunnel

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

14-5

14 Configuring an IP Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

14.5.2 Service Planning

When there is service transmission between Node B and the RNC, you can create a working IP tunnel and a protection MPLS tunnel to ensure the security of service transmission in the network. Table 14-1 lists the configuration parameters of NEs. Table 14-1 Configuration parameters of NEs NE NE1 LSR ID 1.0.0.1 Port 2-EG2-1(Port-1) 4-SHD4-1(Port-1) 3-EG16-1(Port-1) 1-EX2-1(Port-1) 1-EX2-1(Port-1) 3-EG16-1(Port-1) Port IP Address 10.0.0.1 10.0.5.1 10.0.0.2 10.0.1.1 10.0.1.2 10.0.2.1 IP Mask 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252

NE2

1.0.0.2

NE3

1.0.0.3

Table 14-2 shows the planning of static routes for NEs. Table 14-2 Static route Field Station Route List ID Board port Next Hop IP Address Destination Node IP Destination Node Subnet Mask Value NE1 1 Virtual Ethernet 1(VEther-1) 10.0.5.2 10.0.2.1 255.255.255.252 NE3 1 3-EG16 1(Port-1) 10.0.2.2 10.0.5.1 255.255.255.252

Table 14-3 shows the planning of parameters for the IP tunnel. Table 14-3 Planning of the IP tunnel Field Station
14-6

Value NE1
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

NE3
Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

14 Configuring an IP Tunnel

Field Tunnel ID Source Board Source Port Destination IP

Value 90 Virtual Ethernet 1(VEther-1) 10.0.2.1 90 3-EG16 1(Port-1) 10.0.5.1

Table 14-4 shows the planning of parameters for the protection MPLS tunnel. Table 14-4 Planning of the protection MPLS tunnel Field Tunnel ID Name Signal Type Scheduling Type Bandwidth(kbit/s) Ingress Node Transit Node Egress Node Ingress Node Route Information 100 Protecting Tunnel-Positive Static E-LSP No Limit NE1 NE2 NE3 NE1
l l

Value 101 Protecting Tunnel-Reverse Static E-LSP No Limit NE3 NE2 NE1 NE3
l l

Out Port: 2-EG2-1(Port-1) Out Label: 20

Out Port: 2-EG2-1(Port-1) Out Label: 21

Transit Node Route Information

NE2
l l l l

NE2
l l l l

In Port: 3-EG16-1(Port-1) In Label: 20 Out Port: 1-EX2-1(Port-1) Out Label: 30

In Port: 1-EX2-1(Port-1) In Label: 21 Out Port: 3-EG16-1(Port-1) Out Label: 31

Egress Node Route Information

NE3
l l

NE1
l l

In Port: 1-EX2-1(Port-1) In Label: 30

In Port: 2-EG2-1(Port-1) In Label: 31

14.5.3 Creating an IP Tunnel on a Per-NE Basis

This topic describes the process of creating an IP tunnel on a per-NE basis.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 14-7

14 Configuring an IP Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must understand the networking, requirements and service planning of the example. A network must be created.

Procedure
Step 1 Set LSR IDs. 1. 2. In the NE Explorer, select the NE1 and chooseConfiguration > MPLS Management > Basic Configuration from the Function Tree. Set LSR ID, Start of Global Label Space and Start of Multicast Label Space. Click Apply. The configuration parameters are as follows:
l l

LSR ID: 1.0.0.1 (The LSR ID must be unique in the entire network.) Start of Global Label Space: 0 (The minimum value of egress and ingress labels of the unicast tunnel.)

3.

Enter the NE Explorers of NE2 and NE3 respectively and perform the preceding two steps to set the parameters such as LSR ID. The configuration parameters are as follows:
l l

NE2 LSR ID: 1.0.0.2 NE3 LSR ID: 1.0.0.3

Step 2 Configure the network-side interface for the IP tunnel. 1. In the NE Explorer, select NE1 and choose Configuration > Interface Management > DSL Interface > G.SHDSL Interface from the Function Tree. Configure the networkside interface. Click the Bound Mode tab. Select the port 4-SHD4-1(Bind-1) and set Bound Mode of the port to ATM.

2.

3. 4. 5. 6. 7.

Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Click the ATM Bound Group tab. Set Enabled PVC Number to 1 and Pair Mode to 4Pair. Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Optional: Click Configure VPI/VCI. The Configure VPI/VCI dialog box is displayed. Select the port 4-SHD4-1(Bind-1), and set the number of PVC pairs.
NOTE

The OptiX PTN equipment supports up to eight pairs of PVCs. You can enable the proper PVC pairs according to the number of PVC pairs of the connected DSLAM at the opposite end. If the number of PVC pairs to be set is different from the default number of PVC pairs to be enabled, you can set them to be the same by using the Configure VPI/VCI function.

14-8

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

14 Configuring an IP Tunnel

8. 9.

Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. In the NE Explorer, select NE1 and choose Configuration > Interface Management > Ethernet Virtual Interface from the Function Tree. Click the Layer 3 Attributes tab.

10. Set Enable Tunnel to Enabled, Specify IP to Manually, IP Address to 10.0.5.1, and IP Mask to 255.255.255.252.

11. Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. 12. In the NE Explorer, select NE3 and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Configure the network-side interface. 13. On the General Attributes tab page, select the port 3-EG16-1(Port-1) and set Port Mode to Layer 3.

The configuration parameters are as follows:

l l l

Enable Port: Enabled Port Mode: Layer 3 (The port carries a tunnel.) Working Mode: Auto-Negotiation (Set the working modes of the local port and opposite port as the same.) Max Frame Length (byte): 1620 (Set this parameter according to the length of data packets. All the received data packets that contain more bytes than the maximum frame length are discarded.)

14. Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. 15. On the Layer 3 Attributes tab page, select the port 3-EG16-1(Port-1), and set Enabled Tunnel to Enabled, Specify IP to Manually, IP Address as 10.0.2.1, and IP Mask as 255.255.255.252. Set the related parameters as follows:
l l

Enable Tunnel: Enabled Max Reserved Bandwidth (kbit/s): 1000000 (The maximum reserved bandwidth should not exceed the physical bandwidth of the bearer port.) TE Measurement: 10 (The link with a smaller TE measurement value is preferred for route selection of a tunnel. You can intervene in the route selection by adjusting the TE measurement of the link. The smaller the value of the TE measurement, the higher the priority of the link. ) Specify IP: Manually (Manually indicates that you can set the IP address of the port.) IP Address: 10.0.2.1 IP Mask: 255.255.255.252

l l l

16. Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

14-9

14 Configuring an IP Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 3 Configure the network-side interface for the protection MPLS tunnel. Enter the NE Explorers for NE1, NE2 and NE3 respectively. To configure the related parameters of each interface, refer to Step 2.12 to Step 2.16. The settings of general attributes for each interface are the same as the settings of general attributes for the port NE3-3-EG16-1(Port-1). The settings of Layer 3 attributes for each interface are as follows:
l

NE1-2-EG2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.0.1

NE2-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.1.1

NE2-3-EG16-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.0.2

NE3-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.1.2

Step 4 Configure the control plane. 1. Configure the static routes for the working tunnel. In the NE Explorer, select NE1 and choose Configuration > Control Plane Configuration > Static Route Management from the Function Tree. Click Create to create the static route between NE1 and NE3.

2.

Set the related parameters as follows:

l l l l

Route List ID: 1 Board: Virtual Ethernet Port: 1(VEther-1) Next Hop IP Address: 10.0.5.2. (The IP address of the port must be in the same network segment as the next hop IP address.) Destination Node IP: 10.0.2.1
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

14-10

OptiX iManager T2000 Operation Guide for PTN NE Management

l

14 Configuring an IP Tunnel

Destination Node Subnet Mask: 255.255.255.252

3. 4.

Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Enable the IGP-ISIS protocol of the protection MPLS tunnel. In the NE Explorer, select NE1 and choose Configuration > Control Plane Configuration > IGP-ISIS Configuration from the Function Tree. Choose the Port Configuration tab and then click New. Click Add in the dialog box displayed. Then Select 2-EG2-1(Port-1) in the port tab. Click OK. The configuration parameters are as follows:
l l

5.

Link Level: level-1-2 LSP Retransmission Interval(s): 5 (In the case of a point-to-point link, if the local equipment fails to receive any response in a period after transmitting the LSP, the local equipment considers that the LSP is lost or discarded. To ensure the transmission reliability, the local equipment transmits the LSP again.) Minimum LSP Transmission Interval (ms): 30

6. 7.

Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Choose Configuration > Control Plane Configuration > MPLS-LDP Configuration from the Function Tree.
NOTE

When creating a dynamic PW to carry services, set the parameters related to MPLS-LDP.

8.

Click Create. Enter the ID of the opposite NE in the Create LDP Peer Entity dialog box. Click OK. The configuration parameters are as follows:
l

Opposite LSR ID: 1.0.0.3 (The opposite LSR ID indicates the LSR ID of the terminal NE on the PW, that is, NE3 in this case.) Hello Send Interval(s): 10 (The Hello packets are periodically sent to maintain the neighborship.) KeepAlive Send Interval(s): 10 (The KeepAlive packets are periodically sent to maintain the LDP session.)

9.

Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful.

10. In the NE Explorer of NE3, refer to Step 4.1 to Step 4.3 to configure the static routes for NE3. Set the related parameters as follows:
l l l l

Route List ID: 1 Board: 3-EG16 Port: 1(Port-1) Next Hop IP Address: 10.0.2.2. (The IP address of the port must be in the same network segment as the next hop IP address.) Destination Node IP: 10.0.5.1 Destination Node Subnet Mask: 255.255.255.252
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 14-11

l l

Issue 01 (2009-06-30)

14 Configuring an IP Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

11. In the NE Explorer of NE3, refer to Step 4.4 to Step 4.6 to enable the IGP-ISIS protocol for NE3. The settings of the IS-IS protocol for NE3 are consistent with the settings of the IS-IS protocol for NE1. 12. In the NE Explorer of NE3, refer to Step 4.7 to Step 4.9 to configure the peer of NE3. Set the related parameters as follows:
l l l

Opposite LSR ID: 1.0.0.1 Hello Send Interval(s): 10 KeepAlive Send Interval(s): 10

Step 5 Create the working IP tunnel. 1. In the NE Explorer, select NE1 and choose Configuration > IP/GRE Tunnel Management > IP Tunnel Management from the Function Tree. Click New. The Create IP Tunnel dialog box is displayed.

2.

Set the ID, source board, source port, and destination IP address for the IP tunnel. Click OK. Set the related parameters as follows:
l l

Tunnel ID: 90 Source Board: Virtual Ethernet (The virtual interface with Layer 3 attributes enabled can carry the IP tunnel.) Source Port: 1(VEther-1) Destination IP: 10.0.2.1

l l

3.

In the NE Explorer of NE3, refer to Step 5.1 to Step 5.2 to configure the information about the IP tunnel. Set the related parameters as follows:
l l l l

Tunnel ID: 90 Source Board: 3-EG16 Source Port: 1(Port-1) Destination IP: 10.0.5.1

Step 6 Create a protection MPLS Tunnel.

14-12 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

14 Configuring an IP Tunnel

1.

Select NE1 in the NE Explorer. Choose Configuration > MPLS Management > Unicast Tunnel Management from Function Tree. Click New. The New Unicast Tunnel dialog box is displayed. Configure parameters for the positive tunnel and reverse MPLS tunnel such as Tunnel ID, Tunnel name, port and labels. Click OK to finish creating the ingress node.

2.

The configuration parameters are as follows:

l l l l l l l

Tunnel ID: 100(Positive), 101(Reverse) Tunnel Name: Protecting Tunnel-Positive, Protecting Tunnel-Reverse Node Type: Ingress(Positive), Egress(Reverse) Bandwidth (kbit/s): No Limit (Set the bandwidth according to networking planning.) Out Board/Logic Interface Type: 2-EG2 (The source board of the Tunnel.) Out Port: 1(Port-1) (The source port of the Tunnel.) Next Hop Address: 10.0.0.2 (The IP address of the interface on the next node on the tunnel.) Sink Node: 1.0.0.3 (The LSR ID of the interface on the sink node on the tunnel.) Tunnel Type: E-LSP

l l

E-LSP indicates that the tunnel determines the scheduling priority and discard priority of packets according to the EXP information. On one MPLS tunnel of the E-LSP type, there can be a maximum of eight types of PWs.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 14-13

Issue 01 (2009-06-30)

14 Configuring an IP Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

L-LSP indicates that the tunnel determines the scheduling policy of packets according to the MPLS labels and determines the discard policy of packets according to the EXP information. On one MPLS tunnel of the L-LSP type, there can be a maximum of one type of PWs. Currently, the OptiX PTN equipment does not support the L-LSP type.

EXP: none (Set the tunnel priority according to networking planning.)

3.

In the NE Explorer, select NE2. Then, configure the tunnel parameters of the transit node by following Step 6.1 to Step 6.2.

Set related parameters and ensure that the general information of the tunnel is the same as that on NE1. The configuration parameters are as follows:
l l l l l l l l l

Node Type: Transit (NE2 is a transit node on the tunnel.) In Board/Logic Interface Type: 3-EG16 In Port: 1(Port-1) In Label: 20 (Positive), 21 (Reverse) Out Board/Logic Interface Type: 1-EX2 Out Port: 1(Port-1) Out Label: 30 (Positive), 31 (Reverse) Next Hop Address: 10.0.1.2 (Positive), 10.0.0.1 (Reverse) Source Node: 1.0.0.1 (Positive), 10.0.1.2 (Reverse) (The LSR ID of the source node on the tunnel.)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

14-14

OptiX iManager T2000 Operation Guide for PTN NE Management

l

14 Configuring an IP Tunnel

Sink Node: 1.0.0.2. (The LSR ID of the sink node on the tunnel.)

4.

In the NE Explorer, select NE3. Then, configure the tunnel parameters of the egress node by following Step 6.1 to Step 6.2.

Set related parameters and ensure that the general information of the tunnel is the same as that on NE1. The configuration parameters are as follows:
l l l l l l

Node Type: Egress (NE3 is a terminal node on the tunnel.) In Board/Logic Interface Type: 1-EX2 In Port: 1(Port-1) In Label: 30(Positive), Out Label: 31 (Reverse) Next Hop Address: -(Positive), 10.0.1.1 (Reverse) Source Node: 1.0.0.1 (Positive) (The LSR ID of the source node on the tunnel.)

----End

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

14-15

OptiX iManager T2000 Operation Guide for PTN NE Management

15 Configuring a GRE Tunnel

15
About This Chapter

Configuring a GRE Tunnel

When the services that cross an IP network need to be created, the OptiX PTN equipment supports carrying ATM PWE3 services over generic routing encapsulation (GRE) tunnels. In this way, services can be transparently transmitted in an IP network. 15.1 GRE Tunnel GRE tunnel can be used to carry the PWE3 service or the CES service. 15.2 Creating GRE Tunnels In the offload scenario of a mobile communication system, you can transmit the client services by connecting an GRE tunnel to the digital subscriber line access multiplexer (DSLAM). 15.3 Deleting GRE Tunnels To release ports for other services, you can delete redundant GRE tunnels. 15.4 GRE Tunnel Configuration Example This topic describes the configuration example of creating a GRE tunnel on a per-NE basis. In addition to the example, the configuration flow diagram is provided for you to learn the configuration process of services. The configuration example includes information about the configuration networking diagram, service planning, and configuration process.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

15-1

15 Configuring a GRE Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

15.1 GRE Tunnel

GRE tunnel can be used to carry the PWE3 service or the CES service. If ATM or CES emulation service that travels through an IP network is required, the PTN equipment can use the GRE tunnel to carry the service. This complies with RFC 4023 as shown in Figure 15-1. In the case of the GRE tunnel, the situation is similar to that where "GRE encapsulation + 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 IP network between NE A and NE B does not support the MPLS. Figure 15-1 ATM PWE3 over GRE tunnel
ATM switch PTN Router Router PTN ATM switch

IP network NE A ATM E1/STM-1 ATM PWE3 PW Label GRE IP Ethernet ATM PWE3 PW Label GRE IP Ethernet NE B ATM E1/STM-1

15.2 Creating GRE Tunnels

In the offload scenario of a mobile communication system, you can transmit the client services by connecting an GRE tunnel to the digital subscriber line access multiplexer (DSLAM).

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The static route must be configured.

Procedure
Step 1 In the NE Explorer, click an NE. Choose Configuration > IP/GRE Tunnel Management > GRE Tunnel Management from the Function Tree. Step 2 Click New and the Create GRE Tunnel dialog box is displayed.

15-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

15 Configuring a GRE Tunnel

NOTE

Sink Port IP Address must be consistent with Sink Node IP in Static Route Management.

Step 3 Set parameters. Step 4 Click OK. A prompt is displayed indicating that the operation is successful. Click Close. Step 5 Optional: Select the created tunnel. Double-click the Vlan ID filed, and differentiate different tunnels by adding a VLAN ID.
NOTE

If the created tunnel is carried by VLAN sub-interfaces, Vlan ID cannot be set for the tunnel.

Step 6 Click Apply. ----End

15.3 Deleting GRE Tunnels

To release ports for other services, you can delete redundant GRE tunnels.

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

Procedure
Step 1 In the NE Explorer, click an NE. Choose Configuration > GRE Tunnel Management from the Function Tree. Step 2 Select a GRE tunnel and click Delete. The Confirm dialog box is displayed. Click OK. A dialog box is displayed indicating that the operation is successful. Step 3 Click Close. ----End

15.4 GRE Tunnel Configuration Example

This topic describes the configuration example of creating a GRE tunnel on a per-NE basis. In addition to the example, the configuration flow diagram is provided for you to learn the
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 15-3

15 Configuring a GRE Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

configuration process of services. The configuration example includes information about the configuration networking diagram, service planning, and configuration process. 15.4.1 Configuration Networking Diagram This topic describes the networking of GRE tunnel configuration. 15.4.2 Service Planning When there is service transmission between Node B and the RNC, you can create a working GRE tunnel and a protection MPLS tunnel to ensure the security of service transmission in the network. 15.4.3 Creating a GRE Tunnel on a Per-NE Basis This topic describes the process of creating a GRE tunnel on a per-NE basis.

15.4.1 Configuration Networking Diagram

This topic describes the networking of GRE tunnel configuration. As shown in Figure 15-2, the signal transmission between the PTN equipment needs to traverse a third-party IP network, and the services between Node B and RNC are carried by the GRE tunnel. The outgoing services from Node B are accessed on NE1, are transmitted through a thirdparty IP network, converge on NE3, and are finally transmitted to the RNC. GRE tunnel: NE1-a third-party network-NE3. As shown in Figure 15-2, for services that require high network security, you can create the MPLS APS protection to guarantee the service transmission. The PTN equipment supports the ability to protect the GRE tunnel by creating the MPLS tunnel. For information on how to create the MPLS APS protection, see MPLS APS.
l l

Working GRE tunnel: NE1-a third-party network-NE3. Protection MPLS tunnel: NE1-NE2-NE3, in which NE2 is a transit node. When the working GRE tunnel is faulty, the services are switched to the protection MPLS tunnel.

Figure 15-2 GRE tunnel networking application

DSLAM

Third-Party IP Network

Node B 1

NE1

NE3

RNC

PTN
NE2

GRE Tunnel MPLS Tunnel

15-4

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

15 Configuring a GRE Tunnel

In Figure 15-3, NE1 is the PTN 950, while NE2 and NE3 are the PTN 3900s. Figure 15-3 shows the planning for boards and interfaces on each NE. Figure 15-3 NE Planning

DSLAM

Third-Party IP Network

10.0.2.2

10.0.5.2 4-SHD4-1 (Port -1) NE1 10.0.5.1 2-EG2-1 (Port -1) 10.0.0.1 3-EG16-1 (Port -1) 10.0.2.1 1-EX2-1 (Port -1) 10.0.1.2 NE3 RNC

Node B 1

PTN
NE2

3-EG16-1 (Port -1) 10.0.0.2

1-EX2-1 (Port -1) 10.0.1.1 GRE Tunnel MPLS Tunnel

15.4.2 Service Planning

When there is service transmission between Node B and the RNC, you can create a working GRE tunnel and a protection MPLS tunnel to ensure the security of service transmission in the network. Table 15-1 lists the configuration parameters of NEs. Table 15-1 Configuration parameters of NEs NE NE1 LSR ID 1.0.0.1 Port 2-EG2-1(Port-1) 4-SHD4-1(Port-1) 3-EG16-1(Port-1) 1-EX2-1(Port-1) 1-EX2-1(Port-1) 3-EG16-1(Port-1) Port IP Address 10.0.0.1 10.0.5.1 10.0.0.2 10.0.1.1 10.0.1.2 10.0.2.1 IP Mask 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252

NE2

1.0.0.2

NE3

1.0.0.3

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

15-5

15 Configuring a GRE Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

Table 15-2 shows the planning of static routes for NEs. Table 15-2 Static route Field Station Route List ID Board Port Next Hop IP Address Destination Node IP Destination Node Subnet Mask Value NE1 1 Virtual Ethernet 1(VEther-1) 10.0.5.2 10.0.2.1 255.255.255.252 NE3 1 3-EG16 1(Port-1) 10.0.2.2 10.0.5.1 255.255.255.252

Table 15-3 shows the planning of parameters for the working GRE tunnel. Table 15-3 Planning of the working GRE tunnel Field Station Tunnel ID Source Board Source Port Destination IP Value NE1 90 Virtual Ethernet 1(VEther-1) 10.0.2.1 NE3 90 3-EG16 1(Port-1) 10.0.5.1

Table 15-4 shows the planning of parameters for the protection MPLS tunnel. Table 15-4 Planning of the protection MPLS tunnel Field Tunnel ID Name Signal Type Scheduling Type Bandwidth(kbit/s) Ingress Node
15-6

Value 100 Protecting Tunnel-Positive Static E-LSP No Limit NE1

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

101 Protecting Tunnel-Reverse Static E-LSP No Limit NE3

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

15 Configuring a GRE Tunnel

Field Transit Node Egress Node Ingress Node Route Information NE2 NE3 NE1
l l

Value NE2 NE1 NE3

l l

Out Port: 2-EG2-1(Port-1) Out Label: 20

Out Port: 1-EX2-1(Port-1) Out Label: 21

Transit Node Route Information

NE2
l l l l

NE2
l l l l

In Port: 3-EG16-1(Port-1) In Label: 20 Out Port: 1-EX2-1(Port-1) Out Label: 30

In Port: 1-EX2-1(Port-1) In Label: 21 Out Port: 3-EG16-1(Port-1) Out Label: 31

Egress Node Route Information

NE3
l l

NE1
l l

In Port: 1-EX2-1(Port-1) In Label: 30

In Port: 2-EG2-1(Port-1) In Label: 31

15.4.3 Creating a GRE Tunnel on a Per-NE Basis

This topic describes the process of creating a GRE tunnel on a per-NE basis.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must understand the networking, requirements and service planning of the example. A network must be created.

Procedure
Step 1 Set LSR IDs. 1. 2. In the NE Explorer, select the NE1 and chooseConfiguration > MPLS Management > Basic Configuration from the Function Tree. Set LSR ID, Start of Global Label Space and Start of Multicast Label Space. Click Apply. The configuration parameters are as follows:
l l

LSR ID: 1.0.0.1 (The LSR ID must be unique in the entire network.) Start of Global Label Space: 0 (The minimum value of egress and ingress labels of the unicast tunnel.)

3.

Enter the NE Explorers of NE2 and NE3 respectively and perform the preceding two steps to set the parameters such as LSR ID. The configuration parameters are as follows:

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

15-7

15 Configuring a GRE Tunnel

l l

OptiX iManager T2000 Operation Guide for PTN NE Management

NE2 LSR ID: 1.0.0.2 NE3 LSR ID: 1.0.0.3

Step 2 Configure the network-side interface for the GRE tunnel. 1. In the NE Explorer, select NE1 and choose Configuration > Interface Management > DSL Interface > G.SHDSL Interface from the Function Tree. Configure the networkside interface. Click the Bound Mode tab. Select the port 4-SHD4-1(Bind-1) and set Bound Mode of the port to ATM.

2.

3. 4. 5. 6. 7.

Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Click the ATM Bound Group tab. Set Enabled PVC Number to 1 and Pair Mode to 4Pair. Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Optional: Click Configure VPI/VCI. The Configure VPI/VCI dialog box is displayed. Select the port 4-SHD4-1(Bind-1), and set the number of PVC pairs.
NOTE

The OptiX PTN equipment supports up to eight pairs of PVCs. You can enable the proper PVC pairs according to the number of PVC pairs of the connected DSLAM at the opposite end. If the number of PVC pairs to be set is different from the default number of PVC pairs to be enabled, you can set them to be the same by using the Configure VPI/VCI function.

8. 9.

Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. In the NE Explorer, select NE1 and choose Configuration > Interface Management > Ethernet Virtual Interface from the Function Tree. Click the Layer 3 Attributes tab.

10. Set Enable Tunnel to Enabled, Specify IP to Manually, IP Address to 10.0.5.1, and IP Mask to 255.255.255.252.

11. Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. 12. In the NE Explorer, select NE3 and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Configure the network-side interface. 13. On the General Attributes tab page, select the port 3-EG16-1(Port-1) and set Port Mode to Layer 3.

The configuration parameters are as follows:

l l l

Enable Port: Enabled Port Mode: Layer 3 (The port carries a tunnel.) Working Mode: Auto-Negotiation (Set the working modes of the local port and opposite port as the same.)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

15-8

OptiX iManager T2000 Operation Guide for PTN NE Management

l

15 Configuring a GRE Tunnel

Max Frame Length (byte): 1620 (Set this parameter according to the length of data packets. All the received data packets that contain more bytes than the maximum frame length are discarded.)

14. Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. 15. On the Layer 3 Attributes tab page, select the port 3-EG16-1(Port-1), and set Enabled Tunnel to Enabled, Specify IP to Manually, IP Address as 10.0.2.1, and IP Mask as 255.255.255.252. Set the related parameters as follows:
l l

Enable Tunnel: Enabled Max Reserved Bandwidth (kbit/s): 1000000 (The maximum reserved bandwidth should not exceed the physical bandwidth of the bearer port.) TE Measurement: 10 (The link with a smaller TE measurement value is preferred for route selection of a tunnel. You can intervene in the route selection by adjusting the TE measurement of the link. The smaller the value of the TE measurement, the higher the priority of the link. ) Specify IP: Manually (Manually indicates that you can set the IP address of the port.) IP Address: 10.0.2.1 IP Mask: 255.255.255.252

l l l

16. Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 3 Configure the network-side interface for the protection MPLS tunnel. Enter the NE Explorers for NE1, NE2 and NE3 respectively. To configure the related parameters of each interface, refer to Step 2.12 to Step 2.16. The settings of general attributes for each interface are the same as the settings of general attributes for the port NE3-3-EG16-1(Port-1). The settings of Layer 3 attributes for each interface are as follows:
l

NE1-2-EG2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.0.1

NE2-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.1.1

NE2-3-EG16-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.0.2

NE3-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.1.2

Step 4 Configure the control plane.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

15-9

15 Configuring a GRE Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

1.

Configure the static routes for the working tunnel. In the NE Explorer, select NE1 and choose Configuration > Control Plane Configuration > Static Route Management from the Function Tree. Click Create to create the static route between NE1 and NE3.

2.

Set the related parameters as follows:

l l l l

Route List ID: 1 Board: Virtual Ethernet Port: 1(VEther-1) Next Hop IP Address: 10.0.5.2. (The IP address of the port must be in the same network segment as the next hop IP address.) Destination Node IP: 10.0.2.1 Destination Node Subnet Mask: 255.255.255.252

l l

3. 4.

Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Enable the IGP-ISIS protocol of the protection MPLS tunnel. In the NE Explorer, select NE1 and choose Configuration > Control Plane Configuration > IGP-ISIS Configuration from the Function Tree. Choose the Port Configuration tab and then click New. Click Add in the dialog box displayed. Then Select 2-EG2-1(Port-1) in the port tab. Click OK. The configuration parameters are as follows:
l l

5.

Link Level: level-1-2 LSP Retransmission Interval(s): 5 (In the case of a point-to-point link, if the local equipment fails to receive any response in a period after transmitting the LSP, the local equipment considers that the LSP is lost or discarded. To ensure the transmission reliability, the local equipment transmits the LSP again.) Minimum LSP Transmission Interval (ms): 30

6. 7.

Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Choose Configuration > Control Plane Configuration > MPLS-LDP Configuration from the Function Tree.
NOTE

When creating a dynamic PW to carry services, set the parameters related to MPLS-LDP.

15-10

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

15 Configuring a GRE Tunnel

8.

Click Create. Enter the ID of the opposite NE in the Create LDP Peer Entity dialog box. Click OK. The configuration parameters are as follows:
l

Opposite LSR ID: 1.0.0.3 (The opposite LSR ID indicates the LSR ID of the terminal NE on the PW, that is, NE3 in this case.) Hello Send Interval(s): 10 (The Hello packets are periodically sent to maintain the neighborship.) KeepAlive Send Interval(s): 10 (The KeepAlive packets are periodically sent to maintain the LDP session.)

9.

Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful.

10. In the NE Explorer of NE3, refer to Step 4.1 to Step 4.3 to configure the static routes for NE3. Set the related parameters as follows:
l l l l

Route List ID: 1 Board: 3-EG16 Port: 1(Port-1) Next Hop IP Address: 10.0.2.2. (The IP address of the port must be in the same network segment as the next hop IP address.) Destination Node IP: 10.0.5.1 Destination Node Subnet Mask: 255.255.255.252

l l

11. In the NE Explorer of NE3, refer to Step 4.4 to Step 4.6 to enable the IGP-ISIS protocol for NE3. The settings of the IS-IS protocol for NE3 are consistent with the settings of the IS-IS protocol for NE1. 12. In the NE Explorer of NE3, refer to Step 4.7 to Step 4.9 to configure the peer of NE3. Set the related parameters as follows:
l l l

Opposite LSR ID: 1.0.0.1 Hello Send Interval(s): 10 KeepAlive Send Interval(s): 10

Step 5 Create a working GRE tunnel. 1. In the NE Explorer, select NE1 and choose Configuration > IP/GRE Tunnel Management > GRE Tunnel Management from the Function Tree. Click New. The Create GRE Tunnel dialog box is displayed.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

15-11

15 Configuring a GRE Tunnel

OptiX iManager T2000 Operation Guide for PTN NE Management

2.

Set the ID, source board, source port, and destination IP address for the GRE tunnel. Click OK. Set the related parameters as follows:
l l

Tunnel ID: 90 Source Board: Virtual Ethernet (The virtual interface with Layer 3 attributes enabled can carry the GRE tunnel.) Source Port: 1(VEther-1) Destination IP: 10.0.2.1

l l

3.

In the NE Explorer of NE3, refer to Step 5.1 to Step 5.2 to configure the information about the GRE tunnel. Set the related parameters as follows:
l l l l

Tunnel ID: 90 Source Board: 3-EG16 Source Port: 1(Port-1) Destination IP: 10.0.5.1

Step 6 Create a protection MPLS Tunnel. 1. Select NE1 in the NE Explorer. Choose Configuration > MPLS Management > Unicast Tunnel Management from Function Tree. Click New. The New Unicast Tunnel dialog box is displayed. Configure parameters for the positive tunnel and reverse MPLS tunnel such as Tunnel ID, Tunnel name, port and labels. Click OK to finish creating the ingress node.

2.

15-12

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

15 Configuring a GRE Tunnel

The configuration parameters are as follows:

l l l l l l l

Tunnel ID: 100(Positive), 101(Reverse) Tunnel Name: Protecting Tunnel-Positive, Protecting Tunnel-Reverse Node Type: Ingress(Positive), Egress(Reverse) Bandwidth (kbit/s): No Limit (Set the bandwidth according to networking planning.) Out Board/Logic Interface Type: 2-EG2 (The source board of the Tunnel.) Out Port: 1(Port-1) (The source port of the Tunnel.) Next Hop Address: 10.0.0.2 (The IP address of the interface on the next node on the tunnel.) Sink Node: 1.0.0.3 (The LSR ID of the interface on the sink node on the tunnel.) Tunnel Type: E-LSP

l l

E-LSP indicates that the tunnel determines the scheduling priority and discard priority of packets according to the EXP information. On one MPLS tunnel of the E-LSP type, there can be a maximum of eight types of PWs. L-LSP indicates that the tunnel determines the scheduling policy of packets according to the MPLS labels and determines the discard policy of packets according to the EXP information. On one MPLS tunnel of the L-LSP type, there can be a maximum of one type of PWs. Currently, the OptiX PTN equipment does not support the L-LSP type.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 15-13

Issue 01 (2009-06-30)

15 Configuring a GRE Tunnel

l

OptiX iManager T2000 Operation Guide for PTN NE Management

EXP: none (Set the tunnel priority according to networking planning.)

3.

In the NE Explorer, select NE2. Then, configure the tunnel parameters of the transit node by following Step 6.1 to Step 6.2.

Set related parameters and ensure that the general information of the tunnel is the same as that on NE1. The configuration parameters are as follows:
l l l l l l l l l

Node Type: Transit (NE2 is a transit node on the tunnel.) In Board/Logic Interface Type: 3-EG16 In Port: 1(Port-1) In Label: 20 (Positive), 21 (Reverse) Out Board/Logic Interface Type: 1-EX2 Out Port: 1(Port-1) Out Label: 30 (Positive), 31 (Reverse) Next Hop Address: 10.0.1.2 (Positive), 10.0.0.1 (Reverse) Source Node: 1.0.0.1 (Positive), 10.0.1.2 (Reverse) (The LSR ID of the source node on the tunnel.) Sink Node: 1.0.0.2. (The LSR ID of the sink node on the tunnel.)

4.

In the NE Explorer, select NE3. Then, configure the tunnel parameters of the egress node by following Step 6.1 to Step 6.2.

15-14

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

15 Configuring a GRE Tunnel

Set related parameters and ensure that the general information of the tunnel is the same as that on NE1. The configuration parameters are as follows:
l l l l l l

Node Type: Egress (NE3 is a terminal node on the tunnel.) In Board/Logic Interface Type: 1-EX2 In Port: 1(Port-1) In Label: 30(Positive), Out Label: 31 (Reverse) Next Hop Address: -(Positive), 10.0.1.1 (Reverse) Source Node: 1.0.0.1 (Positive) (The LSR ID of the source node on the tunnel.)

----End

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

15-15

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

16

Configuring Network Level Protection

About This Chapter

The network level protection includes the linear MSP, FRR protection, MPLS tunnel protection and LAG. 16.1 Configuring a Linear MSP In a chain network, you can configure a linear MSP to protect services in the link. 16.2 Configuring MPLS Tunnel Protection When you configure an MPLS tunnel on a per-NE basis, you can configure 1+1 protection and 1:1 protection for the MPLS tunnel. You can also create an MPLS tunnel protection group, perform switching, and delete an MPLS tunnel protection group. 16.3 Configuring Offload Protection In the Offload solution, the IP/GRE tunnel in the wholesale managed service (WMS) network should be configured with protection to ensure that the service is protected if the IP/GRE tunnel becomes faulty. 16.4 Configuring FRR Protection for MPLS Tunnel This section describes the application of the FRR and how to configure the FRR protection for MPLS tunnel. 16.5 Configuring LAG This section describes how to configure the LAG. 16.6 MPLS APS Configuration Case This section describes an MPLS APS configuration case. The configuration case covers service planning and configuration process. 16.7 Configuration Case of the Offload Protection Group This section describes a configuration case of the offload protection group. 16.8 FRR Configuration Case A case is provided here to show how to configure the protected tunnel and bypass tunnel for the FRR protection. 16.9 Configuration Case of the LAG

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

16-1

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

The configuration case of the LAG describes the networking of the LAG and configuration method of the LAG.

16-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

16.1 Configuring a Linear MSP

In a chain network, you can configure a linear MSP to protect services in the link. 16.1.1 MSP Protection Switching Priority MSP protection switching is triggered by automatic switching conditions and external switching requests. Automatic switching is triggered by signal failure (for example, when the LOS, LOF, MS_AIS and B2_EXC alarms are generated on the equipment) and signal degrade (for example, when the B2_SD alarm is generated on the equipment). External switching is performed by the user by issuing an external switching command, and changes the status of the multiplex section. External switching requests include lockout, forced switching, manual switching, exercise switching and clear of switching. 16.1.2 Linear MSP Linear multiplex section (MS) is an SDH protection mechanism to protect services in an SDH chain network. 16.1.3 Configuring Linear MSP For a link network, you can configure a linear MSP to protect services in the link. 16.1.4 Checking Linear MSP Switching Status To detect faults in NEs or in the fibers of a linear MSP protection subnet, the maintenance engineers can check the switching status of the linear MSP. The engineers can then locate the point where the fault is generated, according to the switching status of each NE in the protection subnet. 16.1.5 Performing Linear MSP Switching On the T2000, you can perform or clear external switching for linear MSP. During deployment and commissioning, you can perform switching to test whether the linear MSP switching works properly. In fault maintenance, you can perform this operation to locate faults.

16.1.1 MSP Protection Switching Priority

MSP protection switching is triggered by automatic switching conditions and external switching requests. Automatic switching is triggered by signal failure (for example, when the LOS, LOF, MS_AIS and B2_EXC alarms are generated on the equipment) and signal degrade (for example, when the B2_SD alarm is generated on the equipment). External switching is performed by the user by issuing an external switching command, and changes the status of the multiplex section. External switching requests include lockout, forced switching, manual switching, exercise switching and clear of switching. For MSP protection, the following switching requests can change the status of the multiplex section. See the Table 16-1 for their switching (or preemption) priorities.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

16-3

16 Configuring Network Level Protection

NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

In the following table, the switching priorities are given in a descending order, that is, LP_S (SF_P) has the highest priority, and NR has the lowest. The requests of lockout, forced switching, manual switching and exercise switching can be cleared as required. In the case of LP_S (SF_P), the lockout of protection is available only for the span instead of the ring. LP_S and SF_P have the same priority, and perform the same action on both the protocol and the service. LP_S is triggered by an external command, and SF_P is triggered by the protection channel failure in a four-fiber or two-fiber ring. The span switching has a higher priority than the ring switching. External commands are issued on the T2000. After the execution of a command, the NE retains the command request until the command is cleared or preempted by another command that has a higher priority. If there is a switching request with a higher priority in the network, the external command cannot be issued, and the NE loses the external command request. An external command can be cleared only when the clear request is performed on the NE in the same direction as the switching request.

l l

Table 16-1 MSP protection switching priorities No. 1 Switching Request LP_S (SF_P) Description Lockout of protection - span Trigger Condition An external command, or signal failure on the protection channel of a four-fiber or twofiber ring An external command An external command Signal failure on a span of the four-fiber ring working channel Signal failure on the working channel of a four-fiber or twofiber ring Signal degrade on the protection channel of a four-fiber or twofiber ring Signal degrade on a span of the four-fiber ring working channel Signal degrade on the working channel of a four-fiber or twofiber ring
Issue 01 (2009-06-30)

2 3 4

FS_S FS_R SF_S

Forced switching to protection - span Forced switching to protection - ring Signal failure - span

SF_R

Signal failure - ring

SD_P

Signal degrade protection

SD_S

Signal degrade - span

SD_R

Signal degrade - ring

16-4

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

No. 9 10 11

Switching Request MS_S MS_R WTR

Description Manual switching to protection - span Manual switching to protection - ring Wait-to-restore

Trigger Condition An external command An external command Status request between NEs during the switching An external command An external command A reverse request during the switching A reverse request during the switching

12 13 14 15 16

EXER_S EXER_R RR_S RR_R NR

Exerciser - span Exerciser - ring Reverse request span Reverse request ring No request

16.1.2 Linear MSP

Linear multiplex section (MS) is an SDH protection mechanism to protect services in an SDH chain network.

Implementation Principle
Linear multiplex section protection (MSP) includes 1+1 linear MSP and 1:1 linear MSP, which use the protection channel to protect services transmitted in the working channel. When a fault of the working channel occurs, services are switched to the protection channel. The linear MSP applies to POS interface and structured STM-N interface. The APS protocol of the MSP is transmitted by using the protection channel, and the two NEs at the two ends of an MS transmit the protocol status and switching status to each other. The NEs perform a switching of services according to the protocol status and switching status.

SDH 1+1 Linear MSP

See Figure 16-1. When the SDH 1+1 linear MSP is used, services are dual fed and selectively received. If a fault of the working channel occurs, the receive end of services uses the protection channel to receive the services, and thus a service switching is performed.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

16-5

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 16-1 SDH 1+1 linear MSP

Service detection point Working path Line board Line board Service detection point

Access

Cross-connect

Cross-connect

Access

Line board Protection path

Line board

SDH 1:1 Linear MSP

See Figure 16-2. When the SDH 1:1 linear MSP is used, services are transmitted in the working channel. When a fault of the working channel occurs, services are switched to the protection channel and are single-fed and single-received. The APS protocol is transmitted by using the protection channel, and the two NEs at the two ends of an MS transmit the protocol status and switching status to each other. The NEs perform a switching of services and selectively receive the services according to the protocol status and switching status. Figure 16-2 SDH 1:1 linear MSP
Service detection point Working path Line board Line board Service detection point

Access

Cross-connect

Cross-connect

Access

Line board Protection path

Line board

NOTE

In the case of the linear MSP, do not configure any extra service on the protection path.

16.1.3 Configuring Linear MSP

For a link network, you can configure a linear MSP to protect services in the link.

Prerequisite
You must be an NM user with "NE operator" authority or higher. Before you configure the linear MSP protection, make sure that there is no service on the ports of the protection path.
16-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

When the CD1 or POD41 is used to configure the linear MSP, disable the DCN for the port where the protection channel resides.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Linear MS from the Function Tree. Step 2 Click Create. The Create a Linear Multiplex Section dialog box is displayed. Step 3 Set parameters, such as Protection Type, Switching Mode and Revertive Mode for the newly created linear MSP.

Step 4 In Slot Mapping Relation, click West Working Unit and select the board with the working to finish the mapping of West unit from the list of mapping modes. Then, click Working Unit. Similarly, set the mapping of the west protection unit. Step 5 Optional: Click Active check box.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 16-7

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 6 Click OK. Step 7 Select a created protection group and click Start Protocol. Then, the protection group takes effect. Step 8 Optional: Select a created protection group and click Stop Protocol. The protection protocol stops running. ----End

16.1.4 Checking Linear MSP Switching Status

To detect faults in NEs or in the fibers of a linear MSP protection subnet, the maintenance engineers can check the switching status of the linear MSP. The engineers can then locate the point where the fault is generated, according to the switching status of each NE in the protection subnet.

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. The linear MSP must be created.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Linear MS from the Function Tree. Step 2 Click Query. Select Query Switching Status to query the switching status of the nodes. ----End

16.1.5 Performing Linear MSP Switching

On the T2000, you can perform or clear external switching for linear MSP. During deployment and commissioning, you can perform switching to test whether the linear MSP switching works properly. In fault maintenance, you can perform this operation to locate faults.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The linear MSP must be created.

16-8

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

Context
NOTE

The external switching for MSP protection includes: lockout of protection, forced switching, manual switching and exercise switching.
l l

In the event of lockout of protection, the switching request for the port is denied, but the reversion of switching is allowed. 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 channel is satisfying a higher priority bridging request. 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 the protection section. The exercise switching is used to test the APS protocol. In fact services are not switched to the protection section, and only the calculation result of the protocol is displayed.

CAUTION
Switching other than the exercise switching may interrupt services.

Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > Linear MS from the Function Tree. Step 2 In the slot mapping table, right-click a direction and choose a switching or lockout option from the shortcut menu. Click OK in the dialog box.
NOTE

The switching is performed only when the direction is not locked.

----End

16.2 Configuring MPLS Tunnel Protection

When you configure an MPLS tunnel on a per-NE basis, you can configure 1+1 protection and 1:1 protection for the MPLS tunnel. You can also create an MPLS tunnel protection group, perform switching, and delete an MPLS tunnel protection group. 16.2.1 Introduction to MPLS APS MPLS APS is a network protection mechanism. In the case of MPLS APS, a protection tunnel is created to protect the working tunnel when the working tunnel fails. 16.2.2 Basic Concepts Basic concepts related to the MPLS APS protection include the switching mode, revertive mode, wait-to-restore (WTR) time, hold-off time, and protocol state. 16.2.3 MPLS APS Application To realize the MPLS APS function, you need to configure two different tunnels which the source and the sink is same but the route is different. When the working tunnel is faulty, services are switched to the protection tunnel that is previously created.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 16-9

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

16.2.4 Creating an MPLS Tunnel Protection Group You can create an MPLS tunnel protection group to protect MPLS tunnels. You can configure 1+1 protection and 1:1 protection in an MPLS tunnel protection group. To create an MPLS tunnel protection group, the MPLS tunnel protection group must be configured at the source and sink NEs of the MPLS tunnel. 16.2.5 Perform MPLS Tunnel Protection Switching On the T2000, you can perform MPLS tunnel protection switching. The protection switching operations include forced switching, exercise switching, manual to working, and manual to protection. 16.2.6 Deleting an MPLS Tunnel Protection Group To delete an MPLS Tunnel protection group, the MPLS Tunnel protection groups must be deleted at the source NE and sink NE.

16.2.1 Introduction to MPLS APS

MPLS APS is a network protection mechanism. In the case of MPLS APS, a protection tunnel is created to protect the working tunnel when the working tunnel fails.

Purpose and Benefit

The purpose of adopting the MPLS APS mechanism is to protect certain important working tunnels in the network and thus preventing service interruption in the case of the tunnel failure. The APS mechanism can determine whether to perform switching based on detection at the physical layer and the link layer.
l l

At the physical layer, the loss of signal is detected in microseconds. At the link layer, the detection is conducted by MPLS OAM in 10 ms. Set Detection Packet Period to 3.3 ms so that the protection switching time is less than 50 ms.

In MPLS APS, detection at the link layer is performed by MPLS OAM. Thus, you must set the MPLS OAM parameters for relevant tunnels before configuring MPLS APS.

MPLS APS 1+1 Protection

In the case of the MPLS APS 1+1 protection, the transmit end dually feeds the service to the working and protection tunnels and the receive end selectively receives the service. When the equipment detects a fault of the working tunnel, the receive end receives the service from the protection tunnel. Figure 16-3 shows MPLS APS 1+1 protection supported by the equipment.

16-10

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

Figure 16-3 MPLS APS 1+1 protection

Service detection point Working path Processing board Service detection point Subnetwork Processing board switching Access

Access

switching

Processing board

Protection path/ protocol path Subnetwork

Processing board

The APS protocol is transmitted through the protection tunnel to exchange the protocol state and the switching state. The equipment at the two ends performs service switching and selectively receives services according to the protocol state and switching state. Table 16-2 lists parameters for MPLS APS 1+1 protection. Table 16-2 Parameters for MPLS APS 1+1 protection Switching Mode Revertive Mode Switching Protocol Switching Time Switching Hold-off Time (100ms) 1+1 singleended switching 1+1 dualended switching 1+1 singleended switching 1+1 dualended switching Nonrevertive Nonrevertive Revertive APS protocol APS protocol APS protocol APS protocol 50 ms 0 to 100 (0 by default) 0 to 100 (0 by default) 0 to 100 (0 by default) 0 to 100 (0 by default) Default Recovery Time

50 ms

50 ms

5 minutes

Revertive

50 ms

5 minutes

Any of the following conditions triggers the switching:

l l l l

The board has a hardware or software failure. A cold reset is performed on the board. A switching command is manually issued. MPLS OAM detects that the working tunnel is faulty at the link layer.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

16-11

16 Configuring Network Level Protection

NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

If the MPLS Tunnel in the protection group passes through the xDSL network (Offload scenarios), the MPLS Tunnel 1+1 protection switching time is less than 100 ms. It is recommended that you set Detection Packet Period(ms) of FFD packet to 20 ms.

MPLS APS 1:1 Protection

In MPLS APS 1:1 protection, a protection tunnel is used to protect services transmitted on the working tunnel. When the working tunnel fails, the services are switched to the protection tunnel. The 1:1 protection adopts the single fed and single receiving mechanism. Figure 16-4 shows MPLS APS 1:1 protection supported by the equipment. Figure 16-4 MPLS APS 1:1 protection
Service detection point Working path Processing board Subnetwork Processing board Service detection point

Access

switching

switching

Access

Processing board Subnetwork Protocol path

Processing board Protection path

In MPLS APS 1:1 protection, services accessed are transmitted through the working tunnel. When the working tunnel fails, the services are switched to the protection tunnel. Then, the services are transmitted through the protection tunnel and the receive end receive the services from the protection tunnel. The APS protocol is transmitted through the protection tunnel to exchange the protocol state and the switching state. The equipment at the two ends performs service switching and selectively receives services according to the protocol state and switching state. Table 16-3 lists parameters for MPLS APS 1:1 protection. Table 16-3 Parameters for MPLS APS 1:1 protection Switching Mode Revertive Mode Switching Protocol Switching Time Switching Hold-off Time (100ms) 1:1 dualended switching Nonrevertive APS protocol 50 ms 0 to 100 (0 by default) Default Recovery Time

16-12

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

Switching Mode

Revertive Mode

Switching Protocol

Switching Time

Switching Hold-off Time (100ms) 0 to 100 (0 by default)

Default Recovery Time 5 minutes

1:1 dualended switching

Revertive

APS protocol

50 ms

Any of the following conditions triggers the switching:

l l l l

The board has a hardware or software failure. A cold reset is performed on the board. A switching command is manually issued. MPLS OAM detects that the working tunnel is faulty at the link layer.

NOTE

If the MPLS Tunnel in the protection group passes through the xDSL network (Offload scenarios), the MPLS Tunnel 1:1 protection switching time is less than 100 ms. It is recommended that you set Detection Packet Period(ms) of FFD packet to 20 ms.

Compliant Standards and Protocols

MPLS APS complies with ITU-T Y.1720.

16.2.2 Basic Concepts

Basic concepts related to the MPLS APS protection include the switching mode, revertive mode, wait-to-restore (WTR) time, hold-off time, and protocol state.

APS
The automatic protection switching (APS) protocol is used to coordinate actions of the source and the sink in the case of bidirectional protection switching. By the APS protocol, the source and 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 protection switching, 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 at either end knows that the tunnel from which the APS protocol is received is the protection tunnel of the opposite end and thus to determine whether the configuration about the working tunnel and the protection tunnel is consistent at the two ends. When the equipment cannot receive any APS packet, services should be always transmitted and received from the working tunnel.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

16-13

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

Switching Mode
MPLS APS provides two switching modes, that is, single-ended switching and dual-ended switching. In the case of single-ended switching, when one end detects a fault, it only performs switching on 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 the local end and also instructs the opposite end to perform switching. Single-ended switching does not require the APS protocol for negotiation and it features rapid and stable switching. Dual-ended switching ensures that the services are transmitted in a consistent channel, which facilitates service management.

Revertive Mode
The MPLS APS function supports two revertive modes, that is, revertive mode and non-revertive mode. In the non-revertive mode, services are not switched from the protection tunnel to the working tunnel even the working tunnel is restored to the normal state. In the revertive mode, services are switched from the protection tunnel to the original working tunnel 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 restored to the time when the services are switched from the protection tunnel to the original working tunnel. In certain scenarios, the state of the working tunnel is unstable. In this case, setting the WTR time can prevent frequent switching of services between the working tunnel and the protection tunnel. 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 the time when the switching operation is performed. When the equipment is configured with the MPLS APS protection and other protection, setting the hold-off time can ensure that other protection switching operations are performed first. By default, the hold-off time of the equipment is 0s.

Protocol State
The protocol state indicates whether the APS protocol of the protection group is valid currently. In the case of configuring the MPLS APS protection, the protocol state is disabled by default. If you enable the APS protocol at the local NE first and then the opposite NE when configuring the MPLS APS protection, the opposite NE may has an anomaly in receiving services. After the MPLS APS protection group is configured at the two ends, start the protocol.
16-14 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

16.2.3 MPLS APS Application

To realize the MPLS APS function, you need to configure two different tunnels which the source and the sink is same but the route is different. When the working tunnel is faulty, services are switched to the protection tunnel that is previously created.

MPLS APS 1+1 Protection

In the case of MPLS APS 1+1 protection, a protection tunnel is used to protect the working tunnel. The 1+1 protection adopts the dual fed and selective receiving mechanism. The services are switched to the protection tunnel only when the working tunnel fails. Figure 16-5 shows the MPLS APS 1+1 protection. Figure 16-5 MPLS APS 1+1 protection
NE A Working Tunnel NE B

Protection Tunnel

There are two MPLS tunnels as shown in the figure. Normally, services are transmitted through the working tunnel, and the protection tunnel is used to transmit the APS protocol. MPLS OAM performs the connectivity check for each unidirectional MPLS tunnel. The source sends connectivity check packets periodically and the sink performs the check. Set the OAM packet type to FFD and the sending period to 3.3 ms to ensure that the APS switching time is less than 50 ms. The switching mode of the MPLS APS 1+1 protection includes single-ended and dual-ended switching.

MPLS APS 1:1 Protection

In the case of MPLS APS 1:1 protection, a protection tunnel is used to protect the working tunnel. Normally, services are transmitted through the working tunnel. The services are switched to the protection tunnel only when the working tunnel fails. Figure 16-6 shows the MPLS APS 1:1 protection. Figure 16-6 MPLS APS 1:1 protection
Working Tunnel NE A NE B

Protection Tunnel

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

16-15

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

There are two MPLS tunnels as shown in the figure. The continuous line indicates the working tunnel and the dashed line indicates the protection tunnel. Normally, services are transmitted through the working tunnel, and the protection tunnel is used to transmit the APS protocol. MPLS OAM performs the connectivity check for each unidirectional MPLS tunnel. The source sends connectivity check packets periodically and the sink performs the check. Set the OAM packet type to FFD and the sending period to 3.3 ms to ensure that the APS switching time is less than 50 ms. The switching mode of the MPLS APS 1:1 protection is dual-ended switching.

Guide to Configuring the MPLS APS Protection

Pay attention to the following when configuring the MPLS APS protection.
l l l

Enable MPLS OAM of the tunnels before configuring the APS protection. Set the MPLS OAM packet type to FFD and the sending period to 3.3 ms. Set the APS protocol to the enabled state after the nodes at both ends are configured with the APS protection group.

16.2.4 Creating an MPLS Tunnel Protection Group

You can create an MPLS tunnel protection group to protect MPLS tunnels. You can configure 1+1 protection and 1:1 protection in an MPLS tunnel protection group. To create an MPLS tunnel protection group, the MPLS tunnel protection group must be configured at the source and sink NEs of the MPLS tunnel.

Prerequisite
l l l l

You must be an NM user with "NE operator" authority or higher. The working and protection tunnels of an MPLS tunnel must be created. You must have enabled the MPLS OAM state of each MPLS tunnel in the protection group. The OAM packet type must be set to FFD and transmission period to 3.3 ms.

CAUTION
l

In the case of a network-side port configured with the MPLS tunnel 1+1 protection, the linear multiplex section protection (LMSP) should not configured for the port. The node that is configured with the MPLS APS protection cannot be configured with the FRR protection. The protection tunnel should not carry any extra service.
NOTE

If the MPLS Tunnel in the protection group passes through the xDSL network (Offload scenarios), the MPLS Tunnel 1+1 protection switching time is less than 100 ms. It is recommended that you set Detection Packet Period(ms) of FFD packet to 20 ms.

16-16

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

Procedure
Step 1 Select the source NE of the Tunnel in the NE Explorer. Choose Configuration > APS Protection Management from the Function Tree. Step 2 Click New. The New Tunnel Protection Group dialog box is displayed.

Step 3 Set parameters for the tunnel protection group.

l l

Protection Type: You can select 1+1 or 1:1. Switching Mode: You can select Single-Ended or Dual-Ended. When the protection type is 1:1, the switching mode must be dual-ended. Revertive Mode: You can select Non-revertive or Revertive. Hold-off Time(100ms): The unit is 100 millisecond. You can enter an integer from 0 to 100, that is, 0 to 10 seconds.

l l

CAUTION
When creating an APS protection group, disable Protocol Status. Start the protocol only when the configuration of the APS protection group is complete at both nodes.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

16-17

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 4 Click OK. The MPLS tunnel protection group is successfully configured.
NOTE

The bandwidth of the protection tunnel should exceed that of the working tunnel. To increase the bandwidth of the working tunnel after the protection group is created, increase the bandwidth of the protection tunnel first.

Step 5 Refer to Steps 1 through 4 to configure the protection group on the sink NE of the tunnel. Step 6 Start the protocol state of the MPLS APS protection group. 1. 2. 3. Select the source NE of the Tunnel in the NE Explorer. Choose Configuration > APS Protection Management from the Function Tree. Right-click a created APS protection group, and select Start Protocol. A dialog box is displayed indicating that the operation is successful. Protocol Status of the APS protection group turns to Enabled.

----End

16.2.5 Perform MPLS Tunnel Protection Switching

On the T2000, you can perform MPLS tunnel protection switching. The protection switching operations include forced switching, exercise switching, manual to working, and manual to protection.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. You must complete the creation of the MPLS tunnel protection group and you must have enable the protocol status.

Context

CAUTION
When other switching operations, excluding the exercise switching, are performed, the services may be interrupted.

Procedure
Step 1 Select the source NE of the Tunnel in the NE Explorer. Choose Configuration > APS Protection Management from the Function Tree. Step 2 Select a protection group that you want to perform protection switching. Step 3 Click Function tab.

16-18

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

Step 4 Choose the switching operation to be performed from the displayed shortcut menu. Step 5 Confirm in the confirmation dialog box. ----End

16.2.6 Deleting an MPLS Tunnel Protection Group

To delete an MPLS Tunnel protection group, the MPLS Tunnel protection groups must be deleted at the source NE and sink NE.

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

Procedure
Step 1 Select the source NE of the Tunnel in the NE Explorer. Choose Configuration > APS Protection Management from the Function Tree. Step 2 Select a protection group that you want to delete. Step 3 Click Delete. A dialog box is displayed for confirmation. Step 4 Click Yes. The Operation Result dialog box is displayed. Step 5 Click Close. ----End

16.3 Configuring Offload Protection

In the Offload solution, the IP/GRE tunnel in the wholesale managed service (WMS) network should be configured with protection to ensure that the service is protected if the IP/GRE tunnel becomes faulty. 16.3.1 Introduction to Offload Protection Offload protection performs bidirectional forwarding detection (BFD) to detect faults on the IP/ GRE tunnels. When BFD detects a fault on an IP or GRE tunnel, the service on the IP or GRE tunnel is switched to an MPLS tunnel in the backhaul network. In this manner, the service is protected.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 16-19

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

16.3.2 Creating a BFD Session Create a BFD session to enable the BFD function. When BFD detects a link fault, the BFD_DOWN alarm is reported to trigger the APS protection switching. 16.3.3 Configuring the Offload Protection An offload protection group protects the HSDPA service in the leased xDSL wholesale network.

16.3.1 Introduction to Offload Protection

Offload protection performs bidirectional forwarding detection (BFD) to detect faults on the IP/ GRE tunnels. When BFD detects a fault on an IP or GRE tunnel, the service on the IP or GRE tunnel is switched to an MPLS tunnel in the backhaul network. In this manner, the service is protected. Currently, the OptiX PTN supports 1:1 dual-ended switching. That is, the service is singly fed at the transmit end and dually received at the receive end. The working tunnel can be an IP tunnel or GRE tunnel, and the protection tunnel must be an MPLS tunnel. The BFD session is bound with the IP/GRE tunnel to detect faults on the IP/GRE tunnel. In the case of a fault on the IP/ GRE tunnel, the service can be protected. As shown in Figure 16-7, the MPLS tunnel in the leased lines (LLs) in the Backhaul network detects the tunnel fault through the MPLS OAM. When the MPLS tunnel is normal and when a link in the xDSL WMS network becomes faulty, the HSDPA service on the faulty link is switched to the MPLS tunnel. In this manner, the HSDPA service is protected. The priority of the MPLS tunnel that carries the HSDPA service is of the lowest. Hence, the HSDPA service is transported in the LL as possible, and other tunnels in the link can normally transmit the R99 service. Figure 16-7 Networking diagram for Offload protection

xDSL WMS DSLAM HSDPA flow Node B 1

Leased Lines Backhaul network

ATM RNC

IP/GRE Tunnel MPLS Tunnel

Introduction to BFD
BFD is similar to a hello protocol and detects the route-layer faults. BFD can quickly detect the communication faults between adjacent nodes. Currently, only the single hop check is supported. A BFD session is set up between two nodes and then the BFD control packets are periodically transmitted along the trail between the two nodes. If one node fails to receive the BFD control packets in a certain period, the node considers the trail as faulty. In this manner, if a tunnel becomes faulty, an alternate tunnel can be quickly set up or the service can be directly switched
16-20 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

to another tunnel. In the case of Offload protection, when BFD detects a faulty tunnel, the service over the faulty tunnel is quickly switched to another tunnel.

Implementation Principle
As shown in Figure 16-8, both NE A and NE B are OptiX PTN NE. In the forward direction, NE A accesses the HSDPA service, performs PWE3 emulation for the service, and encapsulates the service into a tunnel. Then, an xDSL board (ADS2A/B or SHD4) sends the service to an NNI IP/GRE tunnel for transmission. At the opposite end, the service is decapsulated. In the reverse direction, NE B accesses the HSDPA service, performs PWE3 emulation for the service, and encapsulates the service into a tunnel. Then, the service is sent to an NNI IP/GRE tunnel for transmission. At the opposite end, the service is decapsulated. Figure 16-8 Principle of Offload Protection (Normal)
IP/GRE Tunnel

MPLS Tunnel

Direction of the forward working signal flow Direction of the forward protection signal flow Direction of the reverse working signal flow Direction of the reverse protection signal flow

As shown in Figure 16-9, if the working tunnel in the A-B direction becomes faulty, NE B fails to receive the BFD packets for three consecutive periods and the BFD session is interrupted. Then, NE B reports the BFD_DOWN alarm and the protection module of NE B starts the switching at the transmit end in the B-A direction. As BFD is bidirectional, NE B transmits the BFD packets to inform NE A of the tunnel fault; when receiving the BFD packets, NE A reports the BFD_DOWN alarm and the protection module of NE A starts the switching at the transmit end in the A-B direction. When the switching is complete at both ends, the service is switched to the LL link.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

16-21

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 16-9 Principle of Offload Protection (Switching)

Reporting of BFD_DOWN Reporting of BFD_DOWN

IP/GRE Tunnel

Fault

MPLS Tunnel

B
Direction of the forward working signal flow Direction of the forward protection signal flow Direction of the reverse working signal flow Direction of the reverse protection signal flow

When the tunnel fault is rectified and the BFD session recovers, the protection modules of NE A and NE B switch the service back to the original tunnel.

16.3.2 Creating a BFD Session

Create a BFD session to enable the BFD function. When BFD detects a link fault, the BFD_DOWN alarm is reported to trigger the APS protection switching.

Prerequisite
You must be an NM user with "NE operator" authority or higher. Configuring working tunnel must be complete.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > BFD management from the Function Tree. Step 2 Click New. The Create BFD dialog box is displayed.

NOTE

Sink port IP address: IP address of the opposite port of the BFD session.

16-22

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

Step 3 Set the parameters related to the BFD session.

NOTE

Take the following precautions when setting these parameters. If Session Type is set to Single-Hop, select Board and Port, that is, select a port on a board that transmits the BFD packets. The PTN only supports the single hop check.

Step 4 Click OK. Step 5 Select a created BFD session and double-click the Bound Object filed. In the displayed Bound Port dialog box, set the bound tunnel.
NOTE

Bundling type: IP tunnel or GRE tunnel. Select the tunnel that requires protection.

Step 6 Click OK. Binding the BFD session is complete. ----End

16.3.3 Configuring the Offload Protection

An offload protection group protects the HSDPA service in the leased xDSL wholesale network.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The working tunnel (IP/GRE Tunnel) must be created, and the BFD session must be created. The protection tunnel (MPLS Tunnel) must be created, and Configuring MPLS OAM must be complete.

Procedure
Step 1 Select the source NE of the Tunnel in the NE Explorer. Choose Configuration > APS Protection Management from the Function Tree. Step 2 Click New, the New Tunnel Protection Group dialog box is displayed. Step 3 Set parameters for the tunnel protection group. Select the working tunnel and protection tunnel.
NOTE

The offload supports only the 1:1 protection.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

16-23

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 4 Click OK. The tunnel protection group is successfully configured. Step 5 Display the NE Explorer of the opposite NE and perform Steps 1-4 to create a protection group on the opposite NE. ----End

16.4 Configuring FRR Protection for MPLS Tunnel

This section describes the application of the FRR and how to configure the FRR protection for MPLS tunnel. 16.4.1 Overview of the FRR As a network protection scheme, the fast reroute (FRR) requires that extra resources be reserved for protection. The FRR can be considered as a partial and temporary protection measure. The PTN equipment provides the FRR function based on the RSVP-TE. When the protected MPLS tunnel fails, the protection tunnel that is created beforehand protects the service in milliseconds. The equipment then creates a new MPLS tunnel, and switches the service from the protection tunnel to the new MPLS tunnel. Several protection tunnels can be created to protect the protected MPLS tunnel that involves several NEs to the most extent. The FRR applies to protection of real-time services, which require high network security. 16.4.2 Application of the FRR In the case of the facility backup, the bypass tunnel is created beforehand to provide protection for sections of the protected tunnel. Hence, the protection meets the requirements of the realtime services, such as the VoIP service, which require high security. The FRR can be considered as a temporary protection measure. In the case of switching, the source node of the MPLS tunnel triggers the global reversion to create a new protected MPLS tunnel, and deletes the faulty MPLS tunnel. The service on the bypass tunnel is then switched to the new MPLS tunnel. The application of the FRR covers node protection and link protection.
16-24 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

16.4.3 Creating the FRR Protection for MPLS Tunnels When dynamic MPLS Tunnels are created, enable Fast Re-Route and As Bypass Tunnel for different MPLS Tunnels to complete the configuration of the FRR protection for MPLS Tunnels. 16.4.4 Re-Optimized MPLS Tunnel After the FRR Protection The OptiX PTN equipment supports the FRR protocol. When a protected tunnel fail, the bypass tunnel can be used to protect a group of protected tunnels. In this case, the network-wide recovery can be initiated from the source node to switch services from the original protected tunnel to the new working MPLS tunnel. When the protected tunnel is restored, services can be restored to the original protected tunnel by means of re-optimization.

16.4.1 Overview of the FRR

As a network protection scheme, the fast reroute (FRR) requires that extra resources be reserved for protection. The FRR can be considered as a partial and temporary protection measure. The PTN equipment provides the FRR function based on the RSVP-TE. When the protected MPLS tunnel fails, the protection tunnel that is created beforehand protects the service in milliseconds. The equipment then creates a new MPLS tunnel, and switches the service from the protection tunnel to the new MPLS tunnel. Several protection tunnels can be created to protect the protected MPLS tunnel that involves several NEs to the most extent. The FRR applies to protection of real-time services, which require high network security.

Objective and Benefit

The FRR is based on the extension of the RSVP-TE signaling. The protection tunnel is created beforehand. If the protected MPLS tunnel fails, the protection tunnel protects the service in milliseconds. The FRR meets the security requirements of real-time services, such as the VoIP service. In the case of the FRR, the service can be switched from the protected tunnel to the protection tunnel within 50 ms. Since the protection tunnel is created beforehand, much time is saved for transferring the message among NEs and for NEs to compute and create a tunnel when the protected tunnel fails. Hence, the FRR protection switching time is as short as several milliseconds. The PTN equipment adopts the facility backup protection scheme. In the case of the facility backup, the protection tunnel is also called the bypass tunnel. Figure 16-10 shows a network where the FRR is used to protect the service. The bypass tunnel, marked in red, protects the three protected tunnels.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

16-25

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 16-10 FRR network protection

NE 8 NE 5 PLR NE 1 NE 2 NE 3 NE 4 NE 9 MP

NE 6 Protected Tunnel 1 Protected Tunnel 2 Protected Tunnel 3

NE 7 Bypass Tunnel 1 Bypass Tunnel 2

The source node of the bypass tunnel is the point of local repair (PLR). The sink node of the bypass tunnel is the merge point (MP). The PLR functions to switch the service on the protected tunnel to the bypass tunnel. The MP functions to aggregate the service on the bypass tunnel to the protected tunnel. The bypass tunnel protects the links or nodes that are between the PLR and MP, and are directly connected to the PLR. The protected nodes exclude the PLR and MP. As shown in Figure 16-10, bypass tunnel 1 protects the link between NE2 and NE3, or protects NE3. For protection of the link between NE3 and NE4, another bypass tunnel that starts from NE3 should be created, that is, bypass tunnel 2 shown in Figure 16-10. If bypass tunnel 2 is not at NE3, and the link between NE3 and NE4 becomes faulty, the equipment selects bypass tunnel 1 for protection. In this case, as NE2 does not trigger the protection until NE2 receives the fault information of NE3, the switching time is uncertain.
NOTE

Which protection schemes provided by the PLR by using the bypass tunnel depends on the parameters configured when the protected tunnel is created.
l l l

To configure the link protection, the PLR selects the bypass tunnel that meets the link protection requirement. To configure the node protection, the PLR selects the bypass tunnel that meets the node protection requirement. When the protected tunnel requires link protection but the PLR fails to find suitable bypass tunnel, the PLR tries to select other bypass tunnel to provide the node protection.

For a protected tunnel that involves N nodes, N-1 bypass tunnels should be created to protect the protected tunnel to the most extent. The FRR protection scheme shows advantages in the following aspects:
l

The protection switching time is reduced, and thus the real-time service can be protected.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

16-26

OptiX iManager T2000 Operation Guide for PTN NE Management

l

16 Configuring Network Level Protection

Several bypass tunnels are created to protect the protected tunnel to the most extent, and thus the security is enhanced.

Compliant Standard and Protocol

The FRR complies with RFC 4090-Fast Reroute Extensions to RSVP-TE for LSP Tunnels.

16.4.2 Application of the FRR

In the case of the facility backup, the bypass tunnel is created beforehand to provide protection for sections of the protected tunnel. Hence, the protection meets the requirements of the realtime services, such as the VoIP service, which require high security. The FRR can be considered as a temporary protection measure. In the case of switching, the source node of the MPLS tunnel triggers the global reversion to create a new protected MPLS tunnel, and deletes the faulty MPLS tunnel. The service on the bypass tunnel is then switched to the new MPLS tunnel. The application of the FRR covers node protection and link protection.

Link Protection
When you create a protected tunnel, the tunnel can be configured with link protection. In the case of link protection, the bypass tunnel protects the links adjacent to the PLR node on the protection tunnel. Figure 16-11 shows the FRR link protection. Figure 16-11 FRR link protection
NE 5 PLR NE 1 NE 2 NE 3 NE 4 MP

NE 6 Protected Tunnel 2

NE 7 Bypass Tunnel 1 Bypass Tunnel 2

The protected tunnel carries the real-time service, and is configured with link protection during creation. When the link between NE2 and NE3 fails, the bypass tunnel created beforehand protects this link. In the case of link protection, if one link on the protected tunnel fails, the PLR node selects the bypass tunnel that starts from the PLR node to protect this link. If several bypass tunnels are available, the PLR node selects the best bypass tunnel for protection according to a series of algorithms.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 16-27

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

When the bypass tunnel is available, the source node of the MPLS tunnel starts the comprehensive recovery to set up a new protected MPLS tunnel. In this case, if you query the actual route of the original protected tunnel, the displayed route is of the new protected MPLS tunnel.
NOTE

When multiple bypass tunnels are available, the PLR node selects the bypass tunnel with priority in the following way in most cases.
l l l l l

The bypass tunnel of the same protection scheme as the protected tunnel. The bypass tunnel where the PLR node and MP node are closest to each other. The bypass tunnel with the fewest hops. The bypass tunnel with the lowest bandwidth. The bypass tunnel not intersected with the protected tunnel.

NOTE

In the case of link protection, if a node fails and the bypass tunnel meets the requirements of node protection, the bypass tunnel can also protect the node. As shown in Figure 16-11, if NE3 fails, bypass tunnel 1 can also protect the node, even if the protected tunnel is configured with link protection.

Node Protection
When you create a protected tunnel, the tunnel can be configured with node protection. In the case of node protection, the FRR functions when the node or link on the protection tunnel fails. In this case, the downstream node of the PLR node on the protected tunnel can be protected. Figure 16-12 shows the FRR node protection. Figure 16-12 FRR node protection
NE 5 PLR NE 1 NE 2 NE 3 NE 4 MP

NE 6 Protected Tunnel

NE 7 Bypass Tunnel

The protected tunnel carries the real-time service, and is configured with node protection during creation. If NE3 fails, the bypass tunnel created beforehand can protect NE3. In the case of node protection, the bypass tunnel protects the nodes on the protected tunnel. In the previous figure, the bypass tunnel can protect NE3, the link between NE3 and NE4, and the link between NE2 and NE3.
16-28 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

16.4.3 Creating the FRR Protection for MPLS Tunnels

When dynamic MPLS Tunnels are created, enable Fast Re-Route and As Bypass Tunnel for different MPLS Tunnels to complete the configuration of the FRR protection for MPLS Tunnels.

Prerequisite
l l l

You must be an NM user with "NE operator" authority or higher. You must complete the correct setting of the LSR ID for each NE. You must complete the correct configuration of the port attributes.

Procedure
Step 1 On the T2000, configure the FRR protection for the MPLS Tunnel. For details, see 13.3.1 Creating a Dynamic MPLS Tunnel and the FRR Protection by Using the Trail Function. ----End

16.4.4 Re-Optimized MPLS Tunnel After the FRR Protection

The OptiX PTN equipment supports the FRR protocol. When a protected tunnel fail, the bypass tunnel can be used to protect a group of protected tunnels. In this case, the network-wide recovery can be initiated from the source node to switch services from the original protected tunnel to the new working MPLS tunnel. When the protected tunnel is restored, services can be restored to the original protected tunnel by means of re-optimization.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. You must complete the creation of an FRR.

Procedure
Step 1 On the Main Topology, choose Trail > Tunnel > Dynamic Tunnel Management. The Set Dynamic Tunnel Filter Criteria dialog box is displayed. Step 2 Click Filter. In the filtered tunnel list, select the protection tunnel that need be re-optimized. Step 3 Click the Actual Route tab on the lower left side. Click Query to view the actual route of the protected tunnel after the FRR switching. Step 4 Click the Route Constraint tab and click Add. Step 5 Enter the IP address of the interface on the node that the protected tunnel passes into Route Constraint Port IP Address. Set Routing Style to Include Strict.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

16-29

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 6 Click Re-Optimize. The protected tunnel is restored to the original route before the switching. Step 7 Click the Actual Route tab on the lower left side. Click Query. Then, you can view that the actual route of the protected tunnel is the original route after the re-optimization. ----End

16.5 Configuring LAG

This section describes how to configure the LAG. 16.5.1 Overview of the LAG A link aggregation group (LAG) aggregates multiple Ethernet ports, and handles the aggregation as a port, to increase the bandwidth and link reliability. 16.5.2 LAG Application The link aggregation group (LAG) indicates that several Ethernet ports are aggregated and processed as one. Then, an LAG can be considered as one link. In this way, the bandwidth is increased and the link security is enhanced. 16.5.3 Creating an LAG The link aggregation makes the output and input load shared by the members of an LAG to increase the bandwidth. In the meantime, the members of the LAG can dynamically back up each other to enhance the connection reliability. 16.5.4 Configuring the Port Priority In a link aggregation group (LAG), the member ports have the same default priority. By setting the port priority, the port with a higher priority substitutes the working port with preference when the working port becomes faulty. In the case of a manual LAG, if the numbers of interconnected ports at the two ends increase or decrease in the different manners, you need to adjust the port priorities to ensure proper interconnection. 16.5.5 Querying Port LACP Packet Statistics By querying the port LACP packet statistics, you can determine the current link aggregation state. 16.5.6 Querying Detailed LAG Information By querying the LAG details, you can obtain detailed information of the current LAG. 16.5.7 Deleting LAGs To release the occupied resources, you can delete the redundant or idle LAGs.

16-30

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

16.5.1 Overview of the LAG

A link aggregation group (LAG) aggregates multiple Ethernet ports, and handles the aggregation as a port, to increase the bandwidth and link reliability.

Objectives and Benefits

An LAG aggregates several physical links to form a logical link for data transmission at a higher rate. The function domain of the LAG is between adjacent equipment and irrelevant to the entire network structure. In an Ethernet, a link corresponds to a port, so the link aggregation is also called the port aggregation. The LAG works between the MAC sublayer and the LLC sublayer, and belongs to the data link layer. Figure 16-13 Link Aggregation Group
Link 1 Link 2 Ethernet Message Link 3 LAG Ethernet Message

See Figure 16-13. The LAG can realize the following functions:
l

Improve the link availability: In an LAG, members dynamically back up each other. Once a link is interrupted, another link takes over its work immediately. The process that an LAG starts the backup occurs only inside the LAG, invisible outside of the LAG and irrelevant to other links. Increase the link capability: An LAG can provide an economic method of increasing the link transmission rate. When multiple physical links are bundled, you can obtain a data link with higher bandwidth, without upgrading the existing equipment. The capacity of an LAG equals the sum of the capacity of all member links. The aggregation module allocates the traffic to different LAG members according to the load sharing algorithm, to realize the link-level load sharing.

Compliant Standards and Protocols

The LAG complies with IEEE 802.3ad (Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications).

16.5.2 LAG Application

The link aggregation group (LAG) indicates that several Ethernet ports are aggregated and processed as one. Then, an LAG can be considered as one link. In this way, the bandwidth is increased and the link security is enhanced.

Application
The LAG increases the link availability. In an LAG, the member links back up each other. If one link becomes faulty, another member link instantly takes the work of the faulty link. The
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 16-31

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

backup in an LAG is not visible for links outside the LAG. The work of the faulty link can be taken over in milliseconds. The LAG increases the link capacity. The LAG provides an economical method of increasing the link transmission rate. Several physical links are bound to provide a data link of more bandwidth even when the existing equipment is not upgraded. The capacity of the bound links equals the sum of the bandwidth of each link. The aggregation module distributes the traffic to different members according to a certain algorithm. In this way, the link-level load sharing is available.

16.5.3 Creating an LAG

The link aggregation makes the output and input load shared by the members of an LAG to increase the bandwidth. In the meantime, the members of the LAG can dynamically back up each other to enhance the connection reliability.

Prerequisite
l l l l

You must be an NM user with "NE operator" authority or higher. The port mode of the main port and slave port must be consistent. The Enable Tunnel of ports must be disabled. The slave port should not carry any service.

Context
When the main port and the slave port of the LAG are set to Layer 3, the Layer 3 port whose IP address is configured cannot be set to the slave port.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Link Aggregation Group Management from the Function Tree. Step 2 Click New to display the Create Link Aggregation Group dialog box.

16-32

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

Step 3 Set attributes.

NOTE

l l l l

After you check the Automatically Assign check box, the T2000 automatically assigns the LAG No. Otherwise, you need to manually enter the LAG No. When LAG Type is Static, the link aggregation control protocol (LACP) is running. When LAG Type is Manual, the LACP is not running. Sharing means that each member link of the LAG has traffic at the same time and shares the load together. Non-Sharing means that only one member link of the LAG has traffic. After creating an LAG of the static aggregation mode, you can query the Link Aggregation Group Details and Link LACP Packet Statistics of this LAG.

Step 4 Click OK. A prompt is displayed indicating that the operation is successful. Click Close. ----End

16.5.4 Configuring the Port Priority

In a link aggregation group (LAG), the member ports have the same default priority. By setting the port priority, the port with a higher priority substitutes the working port with preference when
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 16-33

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

the working port becomes faulty. In the case of a manual LAG, if the numbers of interconnected ports at the two ends increase or decrease in the different manners, you need to adjust the port priorities to ensure proper interconnection.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Link Aggregation Group Management from the Function Tree. Step 2 Click the Port Priority tab. Then, set the port priority. For details on the parameters for Port Priority, see Table 2.
NOTE

The smaller the value is, the higher the priority is.

Step 3 Click Apply. A prompt is displayed to indicate that the operation is successful. Step 4 Click Close. ----End

16.5.5 Querying Port LACP Packet Statistics

By querying the port LACP packet statistics, you can determine the current link aggregation state.

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. It is only applicable to LAGs of the static aggregation mode.

Procedure
Step 1 In the NE Explorer, click an NE. Choose Configuration > Interface Management > Link Aggregation Group Management from the Function Tree. Step 2 Select an LAG of the static aggregation mode. Right-click the LAG and choose Link LACP Packet Statistics . The Link LACP Packet Statistics window is displayed. ----End

16.5.6 Querying Detailed LAG Information

By querying the LAG details, you can obtain detailed information of the current LAG.

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. It is only applicable to LAGs of the static aggregation mode.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

16-34

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

Procedure
Step 1 In the NE Explorer, click an NE. Choose Configuration > Interface Management > Link Aggregation Group Management from the Function Tree. Step 2 Select an LAG of the static aggregation mode. Right-click the LAG and choose Link Aggregation Group Details. The Link Aggregation Group Details window is displayed. ----End

16.5.7 Deleting LAGs

To release the occupied resources, you can delete the redundant or idle LAGs.

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

Context

CAUTION
This operation interrupts services on the LAGs.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Link Aggregation Group Management from the Function Tree. Step 2 Choose Link Aggregation Group Management. Select an LAG. Click Delete. A confirmation dialog box is displayed. Step 3 Click OK. A dialog box is displayed telling you that the operation was successful. Step 4 Click Close. ----End

16.6 MPLS APS Configuration Case

This section describes an MPLS APS configuration case. The configuration case covers service planning and configuration process. 16.6.1 Case Description The case description includes the function requirements, networking diagram, and service planning. 16.6.2 Configuration Flow This section describes the flow of configuring the MPLS APS protection.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 16-35

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

16.6.1 Case Description

The case description includes the function requirements, networking diagram, and service planning.

Requirements and Networking Diagram

A 2 Mbit/s service is present between Node B and RNC. After the 2 Mbit/s service is encapsulated, it is transmitted through the working tunnel NE1-NE2-NE4 as shown in Figure 16-14. Because the 2 Mbit/s service has a high requirement for safety, a protection tunnel NE1NE3-NE4 is created to protect the working tunnel. Then, the MPLS APS 1:1 protection is established between the two tunnels. Figure 16-14 Networking diagram of the MPLS APS protection
Ingress Tunnel 1 Egress Tunnel 2 Egress Tunnel 1

NE 2 PSN NE 3

Ingress Tunnel 2 Egress Tunnel 3

Node B

NE 1
Egress Tunnel 4

Ingress Tunnel 3

NE 4
Ingress Tunnel 4

RNC

Protection Tunnel Working Tunnel

Service Planning
In this case, the NEs are OptiX PTN equipment. NE1 and NE4 are connected to Node B and RNC respectively through E1 interfaces. NEs are connected to each other through FE interfaces. The working MPLS tunnel has been created between NE1 and NE4, that is, MPLS tunnel 1. The bandwidth for the working tunnel is 10 Mbit/s. A protection tunnel with the same bandwidth is to be created, that is, MPLS tunnel 2, so that MPLS tunnel 2 protects MPLS tunnel 1. The two tunnels on NE1 are planned as follows: Working tunnel
l l l l

Working Tunnel: MPLS Tunnel 1 Ingress Tunnel ID: 1 Egress Tunnel ID: 2 Bandwidth: 10 Mbit/s

Protection tunnel
l l l

Working Tunnel: MPLS Tunnel 2 Ingress Tunnel ID: 3 Egress Tunnel ID: 4
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

16-36

OptiX iManager T2000 Operation Guide for PTN NE Management

l

16 Configuring Network Level Protection

Bandwidth: 10 Mbit/s

The two MPLS tunnels on NE4 are planned as follows: Working tunnel
l l l l

Working Tunnel: MPLS Tunnel 1 Ingress Tunnel ID: 2 Egress Tunnel ID: 1 Bandwidth: 10 Mbit/s

Protection tunnel
l l l l

Working Tunnel: MPLS Tunnel 2 Ingress Tunnel ID: 4 Egress Tunnel ID: 3 Bandwidth: 10 Mbit/s

According to the MPLS APS configuration principle, you must set the OAM parameters for the two MPLS tunnels and enable the OAM function in the ingress direction of the two tunnels before configuring the MPLS APS protection group.
l l

OAM packet type: FFD Packet sending period: 3.3 ms

16.6.2 Configuration Flow

This section describes the flow of configuring the MPLS APS protection.

Prerequisite
You must have learned about the networking, requirements, and service planning. Two tunnels for the MPLS APS protection must be created. The bandwidth of the protection tunnel must be higher than or equal to the bandwidth of the working tunnel. To increase the bandwidth of the working tunnel after the protection group is created, increase the bandwidth of the protection tunnel first.

Procedure
Step 1 Check whether the bandwidth of the protection tunnel is higher than or equal to the bandwidth of the working tunnel. 1. 2. 3. Click NE1 in the NE Explorer. Choose > Configuration > MPLS Management > Unicast Tunnel Managementfrom the Function Tree. Click Static Tunnel and check whether the bandwidth of the protection tunnel is higher than or equal to the bandwidth of the working tunnel. If the bandwidth of the protection tunnel is lower than the bandwidth of the working tunnel, increase the bandwidth of the protection tunnel so that the protection tunnel has higher bandwidth than the working tunnel.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 16-37

Issue 01 (2009-06-30)

16 Configuring Network Level Protection

NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

In the case of an MPLS tunnel with services, if the bandwidth for the services is ensured through the QoS policy, you can set the bandwidth for the MPLS tunnel to No Limit. Then, the network bandwidth is allocated to the MPLS tunnel according to its priority. The priority of the service packets loaded on the MPLS tunnel on the network determines the priority of the MPLS tunnel. If the bandwidth is insufficient, the MPLS tunnel of a higher priority preempts the bandwidth of the bandwidth of the MPLS tunnel of a lower priority.

4.

Check the bandwidth of the tunnel on NE4. Take preceding steps as reference.

Step 2 Enable the MPLS OAM function for the two MPLS tunnels and set the OAM packet parameters. 1. 2. 3. Click the NE1 in the NE Explorer. Choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Click the OAM Parameters tab. Set OAM Status to Enabled for the tunnels whose tunnel IDs are 1, 2, 3, and 4. Set Detection Packet Type to FFD and Detection Packet Period (ms) to 3.3 for the tunnels whose tunnel IDs are 1 and 3.
NOTE

The equipment adopts the MPLS OAM mechanism to transmit FFD packets in the ingress direction of the tunnel. When the opposite equipment does not receive the FFD packets for three consecutive times, the opposite equipment considers the tunnel as faulty. Then, the equipment starts the MPLS APS switching by running the APS protocol. To ensure that the protection switching time is less than 50 ms, set the FFD packet period to a value less than 3.3 ms.

4. 5. 6.

Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Click Close. Set Detection Packet Type to FFD and Detection Packet Period(ms) to 3.3 for the tunnels with 2 and 4 as tunnel IDs on NE4. Take preceding steps as reference.

Step 3 Create an MPLS APS protection group. 1. 2. Select NE1 in the NE Explorer. Choose Configuration > APS Protection Management from the Function Tree. Click New to display the New Tunnel Protection Group dialog box. Set the parameter as follows:
l

Set Protection Type to 1:1.

NOTE

Differences between 1:1 and 1+1:

l l

In the case of 1:1 APS protection, the protection tunnel cannot carry any extra service. In the case of 1+1 APS protection, services are dually fed. Therefore, 1+1 APS protection requires double bandwidth, when compared with 1:1 APS protection. In addition, 1+1 APS protection requires more multicast resources on the ingress node and egress node. 1:1 APS protection cannot be configured as single-ended. When the OptiX PTN equipment is interconnected with the equipment that does not support the APS protocol, only 1+1 protection is applicable.

Set Switching Mode to Dual-Ended.

NOTE

If Protection Type is set to 1:1, Switching Mode defaults to Dual-Ended and is not for setting.
l l

Set Working Ingress Tunnel ID to 1. Set Working Egress Tunnel ID to 2.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

16-38

OptiX iManager T2000 Operation Guide for PTN NE Management

l l l l

16 Configuring Network Level Protection

Set Protection Ingress Tunnel ID to 3. Set Protection Egress Tunnel ID to 4. Set Revertive Mode to Non-Revertive. Set Hold-off Time(100ms) to 0.
NOTE

When the equipment is configured with the MPLS APS protection and another protection, set Hold-off Time(100ms) to determine which protection scheme functions first in the case of a fault. The value of the Hold-off Time(100ms) is 0 to 100 and the unit is 100ms.
l

Set Protocol Statues to Disabled.

NOTE

When creating a protection group, set Protocol Status to Disabled. After the APS protection group is created on the nodes at both ends, start the protocol for the two nodes at the time. If the APS protocol is enabled first for the local NE and then for the opposite NE during creation of the APS protection group, the opposite NE may abnormally receive services.

3. 4.

Click OK. Create the MPLS APS protection group on NE4. Take preceding steps as reference. Set the parameter as follows:
l l l

Set Protection Type to 1:1. Set Switching Mode to Dual-Ended. Set Working Ingress Tunnel ID to 2.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 16-39

Issue 01 (2009-06-30)

16 Configuring Network Level Protection

l l l l l l

OptiX iManager T2000 Operation Guide for PTN NE Management

Set Working Egress Tunnel ID to 1. Set Protection Ingress Tunnel ID to 4. Set Protection Egress Tunnel ID to 3. Set Revertive Mode to Non-Revertive. Set Hold-off Time(100ms) to 0. Set Protocol Statues to Disabled.

Step 4 Create an MPLS APS protection group on NE4. Set the parameters by following Step 1 to Step 3. Step 5 Enable the APS protocol for the MPLS APS protection group. 1. 2. 3. 4. Click the NE1 in the NE Explorer. Choose Configuration > APS Protection Management from the Function Tree. Right-click the APS protection group that is already created and choose Function > Start Protocol. A dialog box is displayed indicating that the operation is successful. Then, Protocol Status of the APS protection group changes toEnabled. Enable the APS protocol for the MPLS APS protection group on NE4. Take preceding steps as reference.

----End

16.7 Configuration Case of the Offload Protection Group

This section describes a configuration case of the offload protection group. 16.7.1 Configuration Networking Diagram In the offload protection scenario, the accessed HSDPA and R99 services are diverted to different networks for transmission. When the link with the HSDPA service becomes faulty, the HSDPA service is switched to the LL link. In this manner, the HSDPA service is protected. 16.7.2 Service Planning There are HSDPA and R99 services between NodeB and RNC. 16.7.3 Configuration Process This section describes the process of configuring the offload protection.

16.7.1 Configuration Networking Diagram

In the offload protection scenario, the accessed HSDPA and R99 services are diverted to different networks for transmission. When the link with the HSDPA service becomes faulty, the HSDPA service is switched to the LL link. In this manner, the HSDPA service is protected. As shown in Figure 16-15, the transmitted services are as follows:
l

HSDPA service: The xDSL board (ADS2A in this example) on the OptiX PTN 910 converges the HSDPA service to the DSLAM and then the DSLAM transmits the HSDPA service to the Ethernet network leased from another operator. As the Ethernet network ensures only bandwidth for the HSDPA service, the lease cost is relatively low.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

16-40

OptiX iManager T2000 Operation Guide for PTN NE Management

l

16 Configuring Network Level Protection

R99 voice service: The R99 voice service is transmitted through the backhaul network, which is built with the OptiX PTN equipment. The quality, delay, and bandwidth are ensured for the R99 voice service.

Figure 16-15 Networking diagram of the offload application scenario based on the ETH forwarding and packet encapsulation format
ATM E1 ATM PWE3 PW Label LSP Label Ethernet AAL5 ATM ADSL ATM PWE3 PW Label LSP Label Ethernet ATM PWE3 PW Label LSP Label Ethernet ATM E1

2-EF8F-1(Port-1): 192.168.1.6 4-ADS2A-1(Vether-1): 192.168.1.5 DSLAM Node B 1

3-ML-1(Port-1)~ 3-ML-1(Port-16)

Wholesale xDSL service

HSDPA flow R99 flow PTN 2-EF8F-5(Port-5): 192.168.10.6 ATM RNC

2-CXPA-4(Port-4)~ 2-CXPA-5(Port-5) 3-EF8F-1(Port-1):192.168.2.5

IP Tunnel MPLS Tunnel OptiX PTN 910 OptiX PTN 950

16.7.2 Service Planning

There are HSDPA and R99 services between NodeB and RNC. On the OptiX PTN 910, the CXPA accesses the HSDPA and R99 services from NodeB, and the ADS2A and EF8F boards transport the HSDPA and R99 services to the NNI side respectively. Then, the OptiX PTN 950 converges the HSDPA and R99 services, which travel through multiple leased networks, and sends the services to RNC. The IP tunnel or GRE tunnel (IP tunnel in this case) transmits the HSDPA service and the MPLS tunnel transmits the R99 service. When the IP tunnel becomes faulty, the HSDPA service is switched to the MPLS tunnel in the created offload protection group. In this manner, the HSDPA service is restored and protected. The parameters related to the offload protection group are planned as follows.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

16-41

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

Table 16-4 Planning of service parameters Service HSDPA service R99 voice service NNI Interface on the OptiX PTN 910 4-ADS2A-1(VEther-1) IP address: 192.168.1.5 3-EF8F-1(Port-1) IP: 192.168.2.5 NNI Interface on the OptiX PTN 950 2-EF8F-1(Port-1) IP address: 192.168.1.6 2-EF8F-5(Port-5) IP: 192.168.10.6 MPLS Tunnel Tunnel IP Tunnel

Table 16-5 Planning of BFD session parameters NE 910 Source Board Virtual Ethernet Source Port 1(VEther-1) Sink Port IP Address 192.168.1.6 Bound Object IP Tunnel 1 (192.168.1.6) 950 2-EF8F 1(PORT-1) 192.168.1.5 IP Tunnel 1 (192.168.1.5)

Table 16-6 Planning of the tunnel protection group parameters NE Working Tunnel Type IP Tunnel IP Tunnel Working Ingress Tunnel ID 1 1 Working Egress Tunnel ID 1 1 Protectio n Tunnel Type MPLS Tunnel MPLS Tunnel Protection Ingress Tunnel ID 20 21 Protectio n Egress Tunnel ID 21 20

910 950

16.7.3 Configuration Process

This section describes the process of configuring the offload protection.

Prerequisite
You must know information about networking, requirement and data planning of this case. A working tunnel and a protection tunnel must be configured.

Procedure
Step 1 Create a BFD session.
16-42 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

1. 2.

In the NE Explorer, select NE910 and choose Configuration > BFD management from the Function Tree. Click New. Set the parameters related to the BFD session in the Create BFD dialog box displayed. And then click OK.

The configuration parameters are as follows:

l l

Session Type: Single-Hop (BFD session on directly connected links) Board: Virtual Ethernet (The IP tunnel between the ADS2A on NE910 and the EF8F on NE950 transmits the HSDPA service. Create BFD sessions on the ADS2A and EF8F. Then, BFD detects the link faults.) Port: 1(VEther-1) (The IP tunnel is on port 1(VEther-1) on NE910.) Sink Port IP Address: 192.168.1.6 (The 2-EF8F-1(Port-1) port on opposite NE950 receives the service and the IP address of the port is 192.168.1.6.)

l l

3.

Select a created BFD session and double-click the Bound Object field. In the displayed Bound Port dialog box, set the tunnel bound with the BFD session. Then, click OK. The configuration parameters are as follows:
l l

Bound Type: IP Tunnel (In this case, the HSDPA service is on an IP tunnel.) Tunnel: 1 (192.168.1.6)

4.

Display the NE Explorer of NE950 and perform the previous three steps to create a BFD session on NE950. The configuration parameters are as follows:
l l l l

Session Type: Single-Hop Board: 2-EF8F Port: 1(PORT-1) (The IP tunnel is on port 1(PORT-1) on NE950.) Sink Port IP Address: 192.168.1.5 (The 4-ADS2A-1(VEther-1) port on opposite NE910 receives the service and the IP address of the port is 192.168.1.5.) Bound type: IP Tunnel Tunnel: 1 (192.168.1.5)

l l

Step 2 Create a tunnel protection group. 1. 2. In the NE Explorer, select NE910 and choose Configuration > APS Protection management from the Function Tree Click New. Set the parameters related to the protection group in the New Tunnel Protection Group box displayed. And then click OK.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 16-43

Issue 01 (2009-06-30)

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

The configuration parameters are as follows:

l l

Working Tunnel Type: IP Tunnel (In this case, the HSDPA service is on an IP tunnel.) Working Ingress Tunnel ID: 1 (192.168.1.6) (According to the networking planning, working tunnel 1 transmits the HSDPA service and the IP address of the opposite port, that is, 2-EF8F-1(port-1), is 192.168.1.6.) Working Egress Tunnel ID: 1 (192.168.1.6) (According to the networking planning, working tunnel 1 transmits the HSDPA service and the IP address of the opposite port, that is, 2-EF8F-1 (port-1) is 192.168.1.6.) Protection Ingress Tunnel ID: 20 (192.168.10.6) (According to the networking planning, protection ingress tunnel 20 protects the working tunnel and the IP address of port 2-EF8F-5 (port-5) is 192.168.10.6.) Protection Egress Tunnel ID: 21 (192.168.2.5) (According to the networking planning, protection egress tunnel 21 protects the working tunnel and the IP address of the port 3-EF8F-1(port-1) is 192.168.2.5.) Protocol Status: Enabled (When the protocol is enabled, the APS protection group functions.)

3.

Display the NE Explorer of NE950 and perform Step 2.1 through Step 2.2 to create an APS protection group. The configuration parameters are as follows:
l l

Working Tunnel Type: IP Tunnel (In this case, the HSDPA service is on an IP tunnel.) Working Ingress Tunnel ID: 1 (192.168.1.5) (According to networking planning, working tunnel 1 transmits the HSDPA service and the IP address of the opposite port, that is, 2-EF8F-1 (port-1), is 192.168.1.5.)

16-44

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

l

16 Configuring Network Level Protection

Working Egress Tunnel ID: 1 (192.168.1.5) (According to networking planning, working tunnel 1 transmits the HSDPA service and the IP address of the opposite port, that is, 2-EF8F-1 (port-1), is 192.168.1.5.) Protection Ingress Tunnel ID: 21 (192.168.2.5) (According to networking planning, protection ingress tunnel 21 protects the working tunnel and the IP address of the opposite port, that is, 3-EF8F-1(port-1), is 192.168.2.5.) Protection Egress Tunnel ID: 20 (192.168.10.6) (According to networking planning, protection egress tunnel 20 protects the working tunnel and the IP address of port 2EF8F-5(port-5) is 192.168.10.6.) Protocol Status: Enabled (When the protocol is enabled, the APS protection group functions.)

----End

16.8 FRR Configuration Case

A case is provided here to show how to configure the protected tunnel and bypass tunnel for the FRR protection. 16.8.1 Case Description The case description covers the requirement, networking diagram and service planning. 16.8.2 Configuration Flow This section describes how to configure the FRR.

16.8.1 Case Description

The case description covers the requirement, networking diagram and service planning.

Requirement and Networking Diagram

The FRR provides protection for parts of the working tunnel, that is, the link and node that are between the PLR and MP, and are connected to the PLR. Company A has departments in City 1 and City 2, which have 10 Mbit/s real-time service between each other. As shown in Figure 16-16, the service trail is marked in blue. Since the real-time service requires high network security, the service tunnel between A and C needs the FRR protection. A is the OptiX PTN 1900, and other equipment is the OptiX PTN 3900. The equipment is networked through the POS interfaces. Figure 16-16 shows connections among boards of NEs.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

16-45

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 16-16 FRR protection networking diagram

10.1.3.1 1-EG16-19POD41-2 10.1.3.2 1-CXP-5POD41-1

NE4

10.1.5.2 1-EG16-19POD41-1 10.1.5.1 1-EG16-19POD41-2

10.1.4.1

NE1
A Company City1 1-CXP-5POD41-2 10.1.1.2 1-EG16-20POD41-1 1-EG16-19POD41-1 10.1.1.1

1-EG16-20POD41-1 10.1.2.1 10.1.4.2 1-EG16-19POD41-2 10.1.2.2

NE3
1-EG16-19POD41-1 A Company City2

NE2

Primary Tunnel Bypass Tunnel 1 Bypass Tunnel 2

Service Planning
Table 16-7 lists the configuration parameters of NEs. Table 16-7 Configuration parameters of NEs NEs LSR ID Interface 5-POD41-1(Port-1) 5-POD41-2(Port-2) 19-POD41-1(Port-1) NE2 1.0.0.2 19-POD41-2(Port-2) 20-POD41-1(Port-1) NE3 1.0.0.3 19-POD41-1(Port-1) 19-POD41-2(Port-2) 19-POD41-1(Port-1) NE4 1.0.0.4 19-POD41-2(Port-2) 20-POD41-1(Port-1) IP Address of the Interface 10.1.3.2 10.1.1.2 10.1.1.1 10.1.2.2 10.1.4.2 10.1.2.1 10.1.5.1 10.1.5.2 10.1.3.1 10.1.4.1 Subnet Mask of the Interface 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252

NE1

1.0.0.1

Since the service bandwidth is 10 Mbit/s, the bypass tunnel should have bandwidth more than 10 Mbit/s. In addition, the service travels through several NEs. Hence, several bypass tunnels are required to completely protect the tunnel for the service. According to the actual condition, two bypass tunnels are planned for the FRR.
16-46 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

Bypass tunnel 1 is NE1-NE4-NE3, which protects the service tunnel when the link NE1-NE2 or NE2 fails. Bypass tunnel 2 is NE2-NE4-NE3, which protects the service tunnel when the link NE2-NE3 fails. Table 16-8 lists the planned parameters of the primary tunnel and the two bypass tunnels. Table 16-8 Planning of parameters of the FRR Parameter Tunnel ID Protected Tunnel Positive: 1 Negative: 2 Name Positive: Tunnel-0001 Negative: Tunnel-0002 Signal Type Scheduling Type Bandwidth (kbit/s) Tunnel Source Node Tunnel Sink Node Positive Route Constraint Port IP Address Dynamic E-LSP 10240 NE1 NE3 IP addresses of ingress port of NE2: 19-POD41-1: 10.1.1.1 IP addresses of ingress port of NE3: 19-POD41-1: 10.1.2.1 Negative Route Constraint Port IP Address IP addresses of ingress port of NE2: 19-POD41-2: 10.1.2.2 IP addresses of ingress port of NE1: 5-POD41-2: 10.1.1.2 Rerouting Mode Include Strict Include Strict Bypass Tunnel 1 Positive: 3 Negative: 4 Positive: Tunnel-0003 Negative: Tunnel-0004 Dynamic E-LSP 10240 NE1 NE3 IP addresses of ingress port of NE4: 19-POD41-2: 10.1.3.1 IP addresses of ingress port of NE3: 19-POD41-2: 10.1.5.1 IP addresses of ingress port of NE4: 19-POD41-1: 1.1.5.2 IP addresses of ingress port of NE1: 5-POD41-1: 1.1.3.2 Bypass Tunnel 2 Positive: 5 Negative: 6 Positive: Tunnel-0005 Negative: Tunnel-0006 Dynamic E-LSP 10240 NE2 NE3 IP addresses of ingress port of NE4: 20-POD41-1: 10.1.4.1 IP addresses of ingress port of NE3: 19-POD41-2: 10.1.5.1 IP addresses of ingress port of NE4: 19-POD41-1: 10.1.5.2 IP addresses of ingress port of NE2: 20-POD41-1: 10.1.4.2 Include Strict

Note: In this case, the subnet mask at each NNI is 255.255.255.252.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

16-47

16 Configuring Network Level Protection

NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

As the FRR requires dynamic MPLS tunnels, the IP address of the NNI should meet the following requirements:
l l

The IP addresses of the connected ports of adjacent NEs should belong to the same network section. The IP addresses of ports on the same NE should not belong to the same network section.

16.8.2 Configuration Flow

This section describes how to configure the FRR.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must understand the networking, requirements and service planning of the example. A network must be created.

Procedure
Step 1 Set LSR IDs. 1. 2. In the NE Explorer, select the NE1 and choose Configuration > MPLS Management > Basic Configuration from the Function Tree. Set LSR ID, Start of Global Label Space and Start of Multicast Label Space. Click Apply. The configuration parameters are as follows:
l l

LSR ID: 1.0.0.1 (The LSR ID must be unique in the entire network.) Start of Global Label Space: 0 (The minimum values of egress and ingress labels of the unicast tunnel.)

3.

Display the NE Explorer for NE2, NE3, and NE4 separately. Set the parameters such as LSR ID of each NE by following the previous two steps. The configuration parameters are as follows:
l l l

NE2 LSR ID: 1.0.0.2 NE3 LSR ID: 1.0.0.3 NE4 LSR ID: 1.0.0.4

Step 2 Configure NNI interfaces. 1. 2. In the NE Explorer, select NE1 and choose Configuration > Interface Management > SDH Interface from the Function Tree to configure the network-side interface. In the General Attributes tab, select the 5-POD41-1(Port-1) and 5-POD41-2(Port-2). Right click the Port Mode filed, and select Layer 3. Set the parameters as required, and click Apply. Set Encapsulation to PPP and set the port name as required. Click Apply. The configuration parameters are as follows: Encapsulation: PPP (Currently, the POS port supports only the PPP. Before setting the Layer 3 attributes for the POS port, set the encapsulation type to PPP.) 3. Select the 5-POD41-1(Port-1) and 5-POD41-2(Port-2) in the Layer 3 Attributes tab. Right click the Enable Tunnel field and select Enabled. Right-click the Specify IP field and
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

16-48

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

choose Manually. Then, set the parameters such as IP Address and IP Mask. Click Apply. The configuration parameters are as follows:
l l

Enable Tunnel: Enabled Max Reserved Bandwidth (kbit/s): 155500 (The maximum reserved bandwidth should not exceed the physical bandwidth of the bearer port.) TE Measurement: 10 (The link with a smaller TE measurement value is preferred for route selection of a tunnel. You can intervene in the route selection by adjusting the TE measurement of the link. The smaller the value of the TE measurement, the higher the priority of the link. ) Specify IP: Manually (Manually indicates that you can set the IP address of the port.) 5-POD41-1(Port-1) IP Address: 10.1.3.2 5-POD41-2(Port-2) IP Address: 10.1.1.2 IP Mask: 255.255.255.252

l l l l

4.

Display the NE Explorer for NE2, NE3, and NE4 separately. Perform 1 through 3 to set parameters of each related interface. The configuration parameters are as follows: Set the parameters of each interface the same as NE1-5-POD41 and set different IP addresses for them.
l l l l l l l l

NE2-19-POD41-1(Port-1) IP Mask: 10.1.1.1 NE2-19-POD41-2(Port-2) IP Mask: 10.1.2.2 NE2-20-POD41-1(Port-1) IP Mask: 10.1.4.2 NE3-19-POD41-1(Port-1) IP Mask: 10.1.2.1 NE3-19-POD41-2(Port-2) IP Mask: 10.1.5.1 NE4-19-POD41-1(Port-1) IP Mask: 10.1.5.2 NE4-19-POD41-2(Port-2) IP Mask: 10.1.3.1 NE4-20-POD41-1(Port-1) IP Mask: 10.1.4.1

Step 3 Configure the control plane. 1. 2. In the NE Explorer, select an NE1 and choose Configuration > Control Plane Configuration > IGP-ISIS Configuration from the Function Tree. Choose the Port Configuration tab and then click New. Click Add in the dialog box displayed. Then Select 5-POD41-1(Port-1) and 5-POD41-2(Port-2) in the port tab. Click OK. The configuration parameters are as follows:
l l

Link Level: level-1-2 LSP Retransmission Interval(s): 5 (In the case of a point-to-point link, if the local equipment fails to receive any response in a period after transmitting the LSP, the local equipment considers that the LSP is lost or discarded. To ensure the transmission reliability, the local equipment transmits the LSP again.) Minimum LSP Transmission Interval (ms): 30

3.

Optional: Choose Configuration > Control Plane Configuration > MPLS-LDP Configuration from the Function Tree.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 16-49

Issue 01 (2009-06-30)

16 Configuring Network Level Protection

NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

When creating a dynamic PW to carry services, set the parameters related to MPLS-LDP.

4.

Optional: Click Create. Enter the ID of the opposite NE in the Create LDP Peer Entity dialog box. Click OK. The configuration parameters are as follows:
l

Opposite LSR ID: 1.0.0.3 (The opposite LSR ID indicates the LSR ID of the terminal NE on the PW, that is, NE3 in this case.) Hello Send Interval(s): 10 (The Hello packets are periodically sent to maintain the neighborship.) KeepAlive Send Interval(s): 10 (The KeepAlive packets are periodically sent to maintain the LDP session.)

5.

Display the NE Explorer for NE2 and NE3 separately. Perform Step 3.1 through Step 3.4 to set the parameters related to the control plane. Set the IS-IS parameters of NE2 and NE3 as the same as the IS-IS parameters of NE1. Set the LDP parameters as follows:
l

NE2 LDP parameters

Opposite LSR ID: 1.0.0.3 (The opposite LSR ID indicates the LSR ID of the terminal NE on the PW, that is, NE3 in this case.) NE3-NE1 peers Opposite LSR ID: 1.0.0.1 (The opposite LSR ID indicates the LSR ID of the terminal NE on the PW, that is, NE1 in this case.)

NE3 LDP parameters

NE3-NE2 peers Opposite LSR ID: 1.0.0.2 (The opposite LSR ID indicates the LSR ID of the terminal NE on the PW, that is, NE2 in this case.)

Step 4 Creating Primary MPLS Tunnel. 1. 2. On the Main Topology, choose Trail > Tunnel > Tunnel Creation. The Create Tunnel dialog box is displayed. Select Create Reverse Tunnel, and configure parameters for the positive tunnel and reverse tunnel in the General Attributes.

16-50

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

The configuration parameters are as follows:

l l l

Tunnel ID: 1 (Positive), 2 (Reverse) Name: Tunnel-0001 (Positive), Tunnel-0002 (Reverse) Signal Type: Dynamic (If you set signal type to dynamic, the LDP distributes labels and the tunnel is a dynamic tunnel; if you set signal type to static, labels are manually added and the tunnel is a static tunnel.) Scheduling Type: E-LSP

E-LSP indicates that the tunnel determines the scheduling priority and discard priority of packets according to the EXP information. On one MPLS tunnel of the E-LSP type, there can be a maximum of eight types of PWs. L-LSP indicates that the tunnel determines the scheduling policy of packets according to the MPLS labels and determines the discard policy of packets according to the EXP information. On one MPLS tunnel of the L-LSP type, there can be a maximum of one type of PWs. Currently, the OptiX PTN equipment does not support the L-LSP type.

l l

EXP:- (tunnel priority.) Bandwidth (kbit/s): 10240 (Set the bandwidth according to networking planning.)

3.

Click Next, and select Source Node and Sink Node. Click Add to add route restrictions.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

16-51

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

The configuration parameters are as follows:

l l l l

Source Node: NE1 Sink Node: NE3 Positive Route Constraint Port IP Address: 10.1.1.1, 10.1.2.1, Include Strict Reverse Route Constraint Port IP Address: 10.1.2.2, 10.1.1.2, Include Strict

4.

Click Next. Set the parameters such as Setup Priority and Hold Priority for the tunnel according to the planning. Then, click Next. Confirm the tunnel information and then click Finish. The configuration parameters are as follows:
l

Setup Priority: 7 (Setup priority is specified for an MPLS tunnel during creation. "0" indicates the highest priority. In the case insufficiency of resources, the MPLS tunnel of a higher setup priority can preempt the bandwidth of other MPLS tunnels and thus can be created successfully.) Hold Priority: 0 (Hold priority is specified for an MPLS tunnel after creation. "0" indicates the highest priority. In the case of insufficiency of resources, the bandwidth for the MPLS tunnel of a higher hold priority is less likely to be preempted by other tunnels. When creating a dynamic tunnel, make sure that the hold priority is higher or equal to the setup priority.) Color(0x): 0 (Set the affinity attribute of a link. When the primary tunnel is faulty, the link with the same color is preferred during rerouting. When the affinity attribute of links is not required, adopt the default value.) Mask(0x): 0 (Set the number of bits of the mask. Match the number of bits of a mask with the link color. Select the route of a matching link color.) Tunnel Type: Primary Tunnel (You can set the tunnel type to primary tunnel or bypass tunnel. According to the planning, the tunnel is a primary tunnel in this case.) Fast Re-Route: Selected
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

16-52

OptiX iManager T2000 Operation Guide for PTN NE Management

l

16 Configuring Network Level Protection

FRR Type: Facility Mode (In the facility mode, one LSP tunnel protects multiple LSP tunnels. Currently, the OptiX PTN equipment supports only the facility backup mode.) FRR Protection Type: Protection Link Mode

In the case of the protection node mode, the bypass tunnel selected by the PLR must protect the downstream node adjacent to the PLR, and the links between them. If any other link is faulty, the FRR protection switching is triggered through the control plane. This process takes a relatively long time. In the case of the protection link mode, the bypass tunnel selected by the PLR must protect the link between the PLR and downstream adjacent node. The protection link mode is recommended.

FRR Bandwidth(kbit/s): No Limit (Set the bandwidth according to networking planning.)

Step 5 Creating Primary MPLS Tunnel. 1. Configure the General Attributes of Bypass Tunnel1 by following Step 4.1 to Step 4.2. The configuration parameters are as follows:
l l l l l l

Tunnel ID: 3 (Positive), 4 (Reverse) Name: Tunnel-0003 (Positive), Tunnel-0004 (Reverse) Signal Type: Dynamic Scheduling Type: E-LSP EXP:- (tunnel priority) Bandwidth (kbit/s): 10240 (Set the bandwidth according to networking planning.)

2.

Click Next, and select Source Node and Sink Node. Click Add to add route restrictions. The configuration parameters are as follows:
l l l l

Source Node: NE1 Sink Node: NE3 Positive Route Constraint Port IP Address: 10.1.3.1, 10.1.5.1, Include Strict Reverse Route Constraint Port IP Address: 10.1.5.2, 10.1.3.2, Include Strict

3.

Click Next. Set the parameters such as Setup Priority and Hold Priority for the tunnel according to the planning. Then, click Next. Confirm the tunnel information and then click Finish. The configuration parameters are as follows:
l

Setup Priority: 7 (The setup priority of the bypass tunnel must be the same as the setup priority of the primary tunnel.) Hold Priority: 0 (The hold priority of the bypass tunnel must be the same as the hold priority of the primary tunnel.) Color(0x): 0 (The link color of the bypass tunnel must be the same as the link color of the primary tunnel.) Mask(0x): 0 (Set this parameter the same as the primary tunnel.) Tunnel Type: Bypass Tunnel (According to the planning, the tunnel is a bypass tunnel in this case.) Re-Route: selected
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 16-53

l l

Issue 01 (2009-06-30)

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

4.

Create Bypass Tunnel2 by following Step 5.1 to Step 5.3. The configuration parameters are as follows:
l

General Attributes

Tunnel ID: 5(Positive), 6(Reverse) Name: Tunnel-0005(Positive), Tunnel-0006(Reverse) Signal Type: Dynamic Scheduling Type: E-LSP EXP: Bandwidth(kbit/s): 10240 Source Node: NE2 Sink Node: NE3 Positive Route Constraint Port IP Address: 10.1.4.1, 10.1.5.1, Include Strict Reverse Route Constraint Port IP Address: 10.1.5.2, 10.1.4.2, Include Strict Setup Priority: 7 Hold Priority: 0 Color(0x): 0 Mask(0x): 0 Tunnel Type: Bypass Tunnell (According to the planning, the tunnel is a bypass tunnel in this case.) Re-Route: selected

Route Constraint

Tunnel Management Attributes

----End

16.9 Configuration Case of the LAG

The configuration case of the LAG describes the networking of the LAG and configuration method of the LAG. 16.9.1 Case Description This topic describes how to configure a link aggregation group (LAG) by using the T2000. In this topic, the four GE ports between NE1 and the client side equipment are converged. 16.9.2 Service Planning Before the service creation, the service planning designs the details of the service, which is used for guiding the service configuration. 16.9.3 Configuration Process This topic describes the process of configuring the LAG in the configuration case.

16.9.1 Case Description

This topic describes how to configure a link aggregation group (LAG) by using the T2000. In this topic, the four GE ports between NE1 and the client side equipment are converged.
16-54 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

A LAG binds multiple links that are connected to the same equipment, to increase the bandwidth and improve the link reliability. The aggregated links are considered as one logical link. The LAG is application to the Ethernet interface. As shown in Figure 16-17, NE1 is an OptiX PTN 3900 NE, which is connected to the user side equipment through four GE links. To increase the bandwidth and improve the link reliability, the four GE links form an LAG. Figure 16-17 Networking of the LAG
User Side Equipment NE 1 LAG 1-EG16-10(Port-10) 1-EG16-11(Port-11) 1-EG16-12(Port-12) 1-EG16-13(Port-13)

GE Link

16.9.2 Service Planning

Before the service creation, the service planning designs the details of the service, which is used for guiding the service configuration. According to engineering requirements, the engineering department makes engineering planning and then outputs the detailed planning information. The service shown in Figure 16-17 is taken as an example. Table 16-9 lists the configuration parameters of the LAG. Table 16-9 Configuration parameters of the LAG Attribute LAG No. LAG Name LAG Type Revertive Mode Load Sharing Load Sharing Hash Algorithm System Priority Main Board Board Main Port
Issue 01 (2009-06-30)

Value NE1 LAG_1 Static Revertive Sharing Automatic 0 1-EG16 1-EG16 1-EG16-10(Port-10)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 16-55

16 Configuring Network Level Protection

OptiX iManager T2000 Operation Guide for PTN NE Management

Attribute Slave Port Port 1 Priority Port 2 Priority Port 3 Priority Port 4 Priority

Value 1-EG16-11(Port-11), 1-EG16-12(Port-12), 1-EG16-13 (Port-13) 1 2 3 4

16.9.3 Configuration Process

This topic describes the process of configuring the LAG in the configuration case.

Prerequisite
You must understand the networking, requirements and service planning of the example.

Procedure
Step 1 Configure the Ethernet port on the NE1. 1. 2. In the NE Explorer, select the NE1 and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Click General Attributes. Set the parameters for ports, which are 1-EG16-10(Port-10), 1EG16-11(Port-11), 1-EG16-12(Port-12), and 1-EG16-13(Port-13). Click Apply.

The parameters related to the Ethernet port are as follows:

l l

Enable Port: Enabled Port Mode: Layer 2 (Set the parameter based on the actual situation. The modes of the ports in the LAG must be the same. When you set the parameter to Layer 3, tunnel must be disabled for the ports.) Encapsulation Type: 802.1Q Working Mode: Auto-Negotiation Max Frame Length (byte): 1620 (Set the parameter based on the lengths of data packets. All received data packets whose lengths are greater than the parameter value are discarded.)
NOTE

l l l

The ports at the two ends of the LAG between NE1 and the user-side equipment must have the same port setting.

16-56

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

16 Configuring Network Level Protection

Step 2 Configure the LAG for NE1. 1. 2. In the NE Explorer, select the NE1 and choose Configuration > Interface Management > Link Aggregation Group Management from the Function Tree. Click New, and the Create Link Aggregation Group dialog box is displayed.

3.

Set the parameters related to the LAG. Click Apply. The parameters related to the LAG are as follows:
l l l

LAG No.: 1 LAG Name: LAG_1 LAG Type: Static (Start the LACP protocol so that the T2000 automatically determines whether the port carries services.) Revertive Mode: Revertive Load Sharing: Sharing (Multiple ports in LAG 1 are allowed to carry services at the same time.) Load Sharing Hash Algorithm: Destination MAC (The parameter is selected according to the type of service carried by the LAG. If the LAG carries the Ethernet service, select MAC. If the LAG carries the MPLS packets, select MPLS label. If the LAG carries the L3VPN service, select IP.) System Priority: 0 (The local LAG has the highest system priority. The logical calculation result at the local end is shared by both ends.) Main Board: 1-EG16 Slave Board: 1-EG16
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 16-57

l l

l l

Issue 01 (2009-06-30)

16 Configuring Network Level Protection

l l

OptiX iManager T2000 Operation Guide for PTN NE Management

Main Port: 1-EG16-10(Port 10) Slave Port: 1-EG16-11(Port 11), 1-EG16-12(Port 12), 1-EG16-13(Port 13)

Step 3 Click Port Priority. Set the priority of ports in the LAG. Click Apply.

The priority of each port is as follows:

l l l l

1-EG16-10(Port-10) Priority: 1 1-EG16-11(Port-11) Priority: 2 1-EG16-12(Port-12) Priority: 3 1-EG16-13(Port-13) Priority: 4

NOTE

The smaller the value, the higher port priority. The port priority and system priority jointly determine that a port should carry services.

----End

16-58

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

17 Configuring an MPLS PW

17
About This Chapter

Configuring an MPLS PW

PWs should exist with services. When create or delete a services, create or delete the PW. The T2000 provides a specific function to manage PWs. With this function, you can query reference information of a PW, set QoS parameters and OAM parameters of a PW, modify and delete a PW. 17.1 Querying an MPLS PW When you create a service on the T2000, a PW is created. The PWs not bundled with services, however, are not displayed. Hence, you need to query these PWs in the PW Management interface. In the PW Management interface, you can query all PWs created on the equipment, and parameters such as PW type, QoS parameters, OAM parameters and bearer tunnel. 17.2 Querying QoS-Related Parameters of an MPLS PW The PW supports querying the QoS parameters. 17.3 Querying the PW Label Information In an PSN, the label for each PW is unique. By querying the PW label information, you can learn the usage of PW labels. Thus, you can avoid the conflict of labels when creating a PW.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

17-1

17 Configuring an MPLS PW

OptiX iManager T2000 Operation Guide for PTN NE Management

17.1 Querying an MPLS PW

When you create a service on the T2000, a PW is created. The PWs not bundled with services, however, are not displayed. Hence, you need to query these PWs in the PW Management interface. In the PW Management interface, you can query all PWs created on the equipment, and parameters such as PW type, QoS parameters, OAM parameters and bearer tunnel.

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. You must complete the creation of an MPLS PW during creating of a service.

Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > MPLS Management > PW Management from Function Tree. Step 2 Click Query. All MPLS PWs created on the NE are displayed. ----End

17.2 Querying QoS-Related Parameters of an MPLS PW

The PW supports querying the QoS parameters.

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. You must complete the creation of an MPLS PW when creating a service.

Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > MPLS Management > PW Management from Function Tree. Step 2 Click Query. All MPLS PWs created on the NE are displayed in the upper pane. Step 3 In the QoS information below, query the QoS parameters. ----End

17.3 Querying the PW Label Information

In an PSN, the label for each PW is unique. By querying the PW label information, you can learn the usage of PW labels. Thus, you can avoid the conflict of labels when creating a PW.

Prerequisite
You must be an NM user with "NE monitor" authority or higher.
17-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

17 Configuring an MPLS PW

Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > MPLS Management > MPLS Label Management from the Function Tree, and then click the PW Label tab. Step 2 Click Query to view the PW label information. ----End

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

17-3

OptiX iManager T2000 Operation Guide for PTN NE Management

18 Configuring CES Services

18
About This Chapter

Configuring CES Services

The CES service is a type of technology that carries layer 2 services. In the packet switched network (PSN), the CES service tries to emulate basic behaviors and characteristics of the lowrate TDM service, SONET and SDH services. The CES service configuration contains fast configuration and configuration on a per-NE basis. In the fast configuration mode, you need to specify the source and sink nodes in the trail configuration user interface, and then you can fast configurate a complete CES service. In the configuration on a per-NE basis mode, you need to configure the CES service seperately on the source node and sink node, and then you can configure an entire CES service. 18.1 CES Service Type Circuit emulation service (CES) applies the PWE3 emulation technology. For a CES service, the PWE3 packet headers contain the frame format information, alarm information, signaling information, and synchronous timing information of the TDM service flow. After encapsulated by the protocol, the PW packets are transported over the MPLS tunnel, IP Tunnel, GRE Tunnel in the PSN network. When reaching the PW egress, the PW packets are decapsulated to rebuild the TDM circuit-switching service flow. 18.2 Configuration Flow of CES Services This section describes the operation tasks for configuring CES services, and relations among these tasks. When configuring or managing CES services, follow the configuration flows. 18.3 Configuring the CES Service by Using the Trail Function You can quickly configure the CES service by using the trail function. The quick configuration of CES service includes the quick creation and the quick deletion. 18.4 Configuring a CES Service on a Per-NE Basis When configuring a CES service on a per-NE basis, you need to configure the attributes of the source node and sink node of each station one by one. The efficiency of configuring the service on a per-NE basis is low. It is recommended to use the trail function to configure the services. 18.5 Managing the CES Services The CES service management includes searching for, querying, and modifying the CES services, and viewing the alarms and performance events relevant to the CES services. This management function provides network administrators a method to ensure the normal running of the CES services.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 18-1

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

18.6 Configuration Case of the UNI-UNI CES Service This section describes the configuration case of the UNI-UNI CES service. 18.7 Configuration Case of the UNI-NNI CES Service This section describes the configuration case of the UNI-NNI CES service.

18-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

18 Configuring CES Services

18.1 CES Service Type

Circuit emulation service (CES) applies the PWE3 emulation technology. For a CES service, the PWE3 packet headers contain the frame format information, alarm information, signaling information, and synchronous timing information of the TDM service flow. After encapsulated by the protocol, the PW packets are transported over the MPLS tunnel, IP Tunnel, GRE Tunnel in the PSN network. When reaching the PW egress, the PW packets are decapsulated to rebuild the TDM circuit-switching service flow.

Application Mode
The CES service allows a metropolitan Ethernet network (MEN) carrier to provide TDM services to customers that have only the TDM equipment. This enlarges the service range and the number of users of the MEN carriers, and provides a way to transform the traditional circuit network to the wideband data network. The CES service mainly applies to the wireless service and the enterprise private line service. The application scenarios include UNI-NNI and UNI-UNI, as shown in Figure 18-1.
l

UNI-NNI CES service: The PTN equipment accesses the TDM services of customers by using the TDM or channelized STM interface. The CES PW can be created between the PTN equipments to emulate the end-to-end TDM service. To customers, the CES services are similar to actual TDM services. UNI-UNI CES service: The PTN equipment accesses the TDM services by using a single point.
NOTE

Now only the point-to-point service is supported. That is, the service of one E1 interface mapping to one PW is supported. But converged services of several TDM interfaces mapping to one PW are not supported.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

18-3

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 18-1 CES service networking sample

UNI-UNI

BTS UNI-NNI BSC PE

PE BTS TDM Link cSTM Link PW Tunnel PE

BTS

Emulation Mode
The PTN equipment supports two types of CES services: structure-aware TDM circuit emulation service over packet switched network (CESoPSN) and structure-agnostic TDM over packet (SAToP). In the CESoPSN mode:
l

The PTN equipment senses frame structures, frame alignment modes and timeslots in the TDM circuit. The PTN equipment processes the overhead and extracts the payload in TDM frames. Then, the PTN equipment delivers the timeslot of each channel to the packet payload according to certain sequence. As a result, the service in each channel in the packet is fixed and visible. Each Ethernet frame that carries the CES service loads TDM frames of a fixed number. Usually the loading time is 0.125 to 5 ms.

In the SAToP mode:

18-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

l

18 Configuring CES Services

The equipment regards TDM signals as constant rate bit flows, instead of sensing structures in the TDM signals. The entire bandwidth of TDM signals is emulated. The overhead and payload in the TDM signal are transparently transmitted. The Ethernet frame carries the CES service. Usually the loading time is 1 ms.

l l

In the CESoPSN mode, for the free 64 kbit/s timeslot in TDM E1 signal, the PTN equipment provides the compression function to save the transmission bandwidth. The timeslot number ranges from 0 to 31. The timeslot number of 0 indicates a reserved timeslot for transmitting signaling.

Service Clock
The TDM service has high requirements for the clock synchronization. The PTN equipment provides two solutions to the CES service clock synchronization. See Table 18-1. Table 18-1 CES service clock type Synchroni zation Solution External Clock Synchroniza tion PRC Access Position PE equipment Whether the Clock is Transmitted in Carrying Ethernet No Description

Introduces the PRC/GPS clock to the PE equipment, and uses this clock as the transmit clock of the CES port service (retiming). The CE system clock synchronizes the PE service clock. This realizes the synchronization of all PEs and CEs, and ensures that transmit clocks of TDM services on all CEs and PEs are synchronous, and indirectly realizes the transfer of the TDM service clock. See Figure 18-2.

Autoadaptation Clock Synchroniza tion

No need of the reference clock

Yes

For the PE equipment in the ingress side, extracts the clock from the TDM interface. Recovers the TDM clock according to the change caused by the frequency of NNI packets in the buffer area for receiving CES services in the case of egress PE. See Figure 18-3.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

18-5

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 18-2 External Clock synchronization of CES service clock

PRC/GPS PRC/GPS

CES CE TDM+Clock PE PE TDM+Clock CE

Figure 18-3 Auto-adaption synchronization of CES service clock

Line timing mode started to extract the clock from the TDM interface Service clock generated according to the clock information in the CES service

CES CE PE PE CE

18.2 Configuration Flow of CES Services

This section describes the operation tasks for configuring CES services, and relations among these tasks. When configuring or managing CES services, follow the configuration flows. Configure and manage UNI-UNI CES services by following the configuration flow shown in Figure 18-4. Configure and manage UNI-NNI CES services by following the configuration flow shown in Figure 18-5.

18-6

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

18 Configuring CES Services

Figure 18-4 UNI-UNI CES service configuration flow

Required Start Optional Creating a Network

Configure inferface

Configure UNI-UNI CES Service End

Table 18-2 Tasks for configuring the UNI-UNI CES service Task 1. Creating Network 2. Configuring the Interface 3. Configuring the UNI-UNI CES Service Remarks To create a network, you need to create NEs, configure NE data, and create fibers. Use the E1 board or the channelized STM-1 board to access the CES service from the BTS. To configure the UNI-UNI CES service, you need to specify the service ID and service name, select the source board and the sink board.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

18-7

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 18-5 UNI-NNI CES service configuration flow

Required Optional

Start

Creating a Network

Configure inferface

Configure Control Plan

Configure Tunnel

Configure UNI-NNI CES Service End

Table 18-3 Tasks for configuring the UNIs-NNI CES service Task 1. Creating Network 2. Configuring the LSR ID 3. Configuring the NetworkSide Interface Remarks To create a network, you need to create NEs, configure NE data, and create fibers. Configure the LSR ID of the NE and start of global label space. Set the general attributes and Layer 3 attributes (tunnel enable status and IP address) for interfaces to carry the tunnel carrying.

18-8

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

18 Configuring CES Services

Task 4. Configuring the Control Plane

Remarks Set the protocol parameters related to the control plane to create the tunnel.
l

To create a static MPLS tunnel to transmit the ATM service, the parameters related to the control plane need not be set. To create a dynamic MPLS tunnel to transmit the ATM service, you need to set the following protocol parameters: 1. Set the IGP-ISIS protocol parameters. 2. Set the MPLS-RSVP protocol parameters. To create a dynamic PW to transmit the service, you need to set the parameters related to the MPLS-LDP protocol.

To create an IP Tunnel or GRE Tunnel to transmit the ATM service, you need to Configuring Static Routes.

5. Configuring the Tunnel

A tunnel transmits the service.

l

If an static MPLS tunnel is required, configure an MPLS tunnel in the per-NE or per-trail mode. Specify the tunnel ID, set signaling type to static, name the service, and specify the ingress node, egress node, and transit node. If a dynamic MPLS Tunnel is required, name the service, set signaling type to dynamic, and specify the source node and sink node for the tunnel. If an IP Tunnel or GRE Tunnel is required, select the source board, source port, and IP address of the sink port.

6. Configuring the Service Interface 7. Configuring the UNIs-NNI CES service

Use the E1 board or the channelized STM-1 board to access the CES service from the BTS. 1. Create a CES service: Set the service ID and specify a service name. 2. Setting the source: Select the board and the specific channel. 3. Configure a PW: Set the PW type, PW label, and tunnel type. 4. Set advanced attributes: Set the jitter buffer time, packet loading time, and clock mode.

18.3 Configuring the CES Service by Using the Trail Function

You can quickly configure the CES service by using the trail function. The quick configuration of CES service includes the quick creation and the quick deletion. 18.3.1 Creating a UNI-UNI CES Service by Using the Trail Function In an operation interface of the T2000, you can directly configure the attributes of the source and sink nodes and the PW of a CES service by using the T2000 trail function. In this way, a CES service can be fast created. 18.3.2 Creating a UNI-NNI CES Service by Using the Trail Function
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 18-9

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

In an operation interface of the T2000, you can directly configure the attributes of the source and sink nodes and the PW of a CES service by using the T2000 trail function. In this way, a CES service can be fast created. 18.3.3 Deleting a CES Service by Using the Trail Function You can delete a CES service directly in the user interface by using the T2000 trail function.

18.3.1 Creating a UNI-UNI CES Service by Using the Trail Function

In an operation interface of the T2000, you can directly configure the attributes of the source and sink nodes and the PW of a CES service by using the T2000 trail function. In this way, a CES service can be fast created.

Prerequisite
l l

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

Procedure
Step 1 Choose Trail > PTN Service > CES Service Creation from the Main Menu. The Create CES Service dialog box is displayed. Step 2 In the Create CES Service dialog box, create the UNI-UNI service.

NOTE

For the UNI-UNI service, you need not specify a PW and set parameters of the PW.

18-10

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

18 Configuring CES Services

Step 3 Set attributes related to the UNI-UNI service. 1. In Basic Information, set the basic attributes of the CES service.
NOTE

Note the following when setting the parameters: Service ID(e.g.1,3-6): After you select Automatically Assigned, the system automatically assigns the service ID. If not, you need to manually assign the service ID.

2.

In Source, click Browse. Then select source board, source port and lower order path of the service in the Please select the source timeslot dialog box. In Sink, click Browse and select the sink NE, sink port, higher order path and lower order path of the service.

NOTE

Note the following when setting the parameters: The source and sink NEs of the UNI-UNI service need to be the same.

3.

Click Apply, and the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close.

----End

18.3.2 Creating a UNI-NNI CES Service by Using the Trail Function

In an operation interface of the T2000, you can directly configure the attributes of the source and sink nodes and the PW of a CES service by using the T2000 trail function. In this way, a CES service can be fast created.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The DCN of the port with the CES service must be disabled.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 18-11

Issue 01 (2009-06-30)

18 Configuring CES Services

l

OptiX iManager T2000 Operation Guide for PTN NE Management

A tunnel for carrying the service must be configured by using the trail function. For configuration method, see 13.3.1 Creating a Dynamic MPLS Tunnel and the FRR Protection by Using the Trail Function or 13.3.2 Creating a Static MPLS Tunnel by Using the Trail Function.

Procedure
Step 1 Choose Trail > PTN Service > CES Service Creation from the Main Menu. The Create CES Service dialog box is displayed. Step 2 In the Create CES Service dialog box, create the UNI-NNI service.

NOTE

For the UNI-NNI service, you need specify a PW and set parameters of the PW.

Step 3 Set attributes related to the UNI-NNI service. 1. In Basic Information, set the basic attributes of the CES service.
NOTE

Note the following when setting the parameters: Service ID(e.g.1,3-6): After you select Automatically Assigned, the system automatically assigns the service ID. If not, you need to manually assign the service ID.

2.

In Source, click Browse and select the source NE, source port, higher path and lower path of the service. In Sink, click Browse and select the sink NE, sink port, high path and low path of the service.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

18-12

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

18 Configuring CES Services

Note the following when setting the parameters: When you create a UNI-NNI CES service, the source and sink NEs cannot be the same.

3.

In PW, set the attributes of the PW.

NOTE

Note the following when setting the parameters:

l l l

ID(e.g.1,3-6): After you select Automatically Assigned, the system automatically assigns the ID for the PW that carries the services. If not, you need to manually assign the ID for the PW. When Protocol Type is set to Static, you need to set the uplink and downlink labels. When it is set to Dynamic, the system automatically assigns the uplink and downlink labels. The Emulation Mode includes structure-aware TDM circuit emulation service over packet switched network (CESoPSN) and structure-agnostic TDM over packet (SAToP). You can configure the 64K Timeslot function for the CESoPSN but not for the SAToP. Uplink Label/Source Port(e.g.16,33-36): The label that indicates a service is encapsulated into a PW. Downlink Label/Sink Port(e.g.16,33-36): The label that indicates the service is decapsulated from the PW. After you select Auto assign label, the system automatically assigns the Uplink Label/Source Port(e.g.16,33-36) and Downlink Label/Sink Port(e.g.16,33-36) for the PW.

l l l

4.

Click Advanced and the Advanced Attribute dialog box is displayed.

NOTE

Note the following when setting the parameters: Generally, Packet Loading Time(us) for carrying the CES service packets is 1000 us. The value of Jitter Compensation Buffering Time(us) must be greater than the value of Packet Loading Time(us) on the opposite end.

5. 6.

Click OK. Click Apply, and the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close.

----End

18.3.3 Deleting a CES Service by Using the Trail Function

You can delete a CES service directly in the user interface by using the T2000 trail function.

Prerequisite
You must be an NM user with "NE operator" authority or higher.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 18-13

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

Context

CAUTION
This operation will interrupt the service. Exercise caution when you perform this operation.

Procedure
Step 1 Choose Trail > PTN Service > CES Service Management from the Main Menu. The Set Service Browse Filter Conditions dialog box is displayed. Step 2 Set relevant filtering conditions and click Filter. Step 3 Right-click the CES service that you want to delete and choose Delete from the shortcut menu. A dialog box is displayed, indicating that deleting the trail will interrupt the service. Click OK. A re-confirming dialog box is displayed, indicating that deleting the trail is a dangerous operation. Click OK. A prompt is displayed, indicating that the operation is successful. Step 4 Click Close. ----End

18.4 Configuring a CES Service on a Per-NE Basis

When configuring a CES service on a per-NE basis, you need to configure the attributes of the source node and sink node of each station one by one. The efficiency of configuring the service on a per-NE basis is low. It is recommended to use the trail function to configure the services. 18.4.1 Creating a UNI-UNI CES Service on a Per-NE Basis If you create a CES service on a per-NE basis, you need to create relevant attributes of the service separately on the source and sink nodes of the service. 18.4.2 Creating a UNI-NNI CES Service on a Per-NE Basis If you create a CES service on a per-NE basis, you need to create relevant attributes of the service separately on the source and sink nodes of the service. After the CES service is created, the corresponding PW is automatically created. 18.4.3 Deleting a CES Service on a Per-NE Basis When you delete a CES service on a per-NE basis, you need to delete relevant attributes of the service separately on the source and sink nodes of the service. After the CES service is deleted, the corresponding PW is automatically deleted.

18.4.1 Creating a UNI-UNI CES Service on a Per-NE Basis

If you create a CES service on a per-NE basis, you need to create relevant attributes of the service separately on the source and sink nodes of the service.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The ports must be configured.
18-14 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

18 Configuring CES Services

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > CES Service Management from the Function Tree. Step 2 Click New, and the Create CES Service dialog box is displayed. In this dialog box, configure the UNI-UNI service.
NOTE

In the case of the UNI-UNI service, QoS and Advanced Attributes do not need to be set.

Step 3 Set attributes related to the UNI-UNI service. 1. Configure the parameters of the service.

NOTE

Note the following when setting the parameters: Mode: UNI-UNI.

2.

Click Apply. A dialog box is displayed, indicating that the operation is successful. Click Close.

----End

18.4.2 Creating a UNI-NNI CES Service on a Per-NE Basis

If you create a CES service on a per-NE basis, you need to create relevant attributes of the service separately on the source and sink nodes of the service. After the CES service is created, the corresponding PW is automatically created.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

18-15

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

Prerequisite
l l l

You must be an NM user with "NE operator" authority or higher. The DCN of the port with the CES service must be disabled. The tunnel must be created. For configuration method, see 13.3.1 Creating a Dynamic MPLS Tunnel and the FRR Protection by Using the Trail Function, 13.3.2 Creating a Static MPLS Tunnel by Using the Trail Function or 13.4.2 Creating an MPLS Tunnel on a Per-NE Basis.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > CES Service Management from the Function Tree. Step 2 Click New, and the Create CES Service dialog box is displayed. In this dialog box, configure the UNI-UNI or UNI-NNI CES services.
NOTE

In the case of the UNI-NNI service, set QoS and Advanced Attributes.

Step 3 Set attributes related to the UNI-NNI service. 1. Configure the parameters of the service.

18-16

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

18 Configuring CES Services

Note the following when setting the parameters:

l l

Mode: UNI-NNI. In the case of PW Signaling Type, if you select Static, you need to set PW Ingress Label/ Source Port(e.g.16,33-36) and PW Engress Label/Sink Port(e.g.16,33-36). If you select Dynamic, the system automatically allocates PW Ingress Label/Source Port(e.g.16,33-36) and PW Engress Label/Sink Port(e.g.16,33-36). PW Ingress Label/Source Port(e.g.16,33-36): the label that indicates a service is encapsulated into a PW. PW Engress Label/Sink Port(e.g.16,33-36): the label that indicates the service is decapsulated from the PW. Tunnel: Select the tunnel to carry the services.

l l l

2.

Click QoS and the QoS dialog box is displayed.

3.

Set the parameters of QoS.

NOTE

Note the following when setting the parameters: EXP: Set the Ingress value only. 7 indicates the highest priority.

4. 5.

Click OK. Click Advanced Attributes, and the Advanced Attributes dialog box is displayed.

6.

Configure parameters in the Advanced Attributes dialog box.

NOTE

Note the following when setting the parameters: Generally, Packet Loading Time(us) for carrying the CES service packets is 1000 us. The value of Jitter Compensation Buffering Time(us) must be greater than the value of Packet Loading Time(us) on the opposite end.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

18-17

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

7. 8.

Click OK. Click Apply. A dialog box is displayed, indicating that the operation is successful. Click Close.

----End

18.4.3 Deleting a CES Service on a Per-NE Basis

When you delete a CES service on a per-NE basis, you need to delete relevant attributes of the service separately on the source and sink nodes of the service. After the CES service is deleted, the corresponding PW is automatically deleted.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > CES Service Management from the Function Tree. Step 2 Select the service that you want to delete. Click Delete, and the Prompt dialog box is displayed. Step 3 Confirm the deletion, and the Operation Result dialog box is displayed, indicating that the operation is successful. Step 4 Click Close. ----End

18.5 Managing the CES Services

The CES service management includes searching for, querying, and modifying the CES services, and viewing the alarms and performance events relevant to the CES services. This management function provides network administrators a method to ensure the normal running of the CES services. 18.5.1 Searching the CES Services You can search for the CES services in the network in this user interface. The T2000 saves and displays the CES services that are searched out. 18.5.2 Filtering the CES Services You can query the CES services according to the filtering conditions. On the T2000, the CES services that meet the filtering conditions are displayed. 18.5.3 Querying the Node Information of the CES Service You can query the node information of the CES service in this user interface. The node information includes the nodes, channels and 64K timeslots. The nodes include all the source and sink nodes of the CES service. 18.5.4 Browsing the CES Service Alarms In this user interface, you can query the alarms related to a CES service to check whether the CES service has any potential fault. 18.5.5 Browsing the CES Service Performance
18-18 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

18 Configuring CES Services

In this user interface, you can query the performance data related to a CES service to check the running status of the CES service.

18.5.1 Searching the CES Services

You can search for the CES services in the network in this user interface. The T2000 saves and displays the CES services that are searched out.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The CES services must be created.

Procedure
Step 1 Choose Trail > PTN Service > PTN Service Search from the Main Menu. Step 2 In the Emulation Service Search window, select Search CES and click Next to perform the search. Click Finish.

NOTE

The CES trail search is the full search. That is, all the information of the network-layer CES trails on the T20000 side and their PWs are deleted. Then, the service configuration of each NE is searched out and the network-layer CES trails on the T2000 side are formed.

----End

18.5.2 Filtering the CES Services

You can query the CES services according to the filtering conditions. On the T2000, the CES services that meet the filtering conditions are displayed.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 18-19

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The CES services must be created.

Procedure
Step 1 Choose Trail > PTN Service > CES Service Management from the Main Menu. The Set Service Browse Filter Conditions window is displayed. Step 2 Select the filter conditions. Click Filter to filter the CES services according to these filter conditions. ----End

18.5.3 Querying the Node Information of the CES Service

You can query the node information of the CES service in this user interface. The node information includes the nodes, channels and 64K timeslots. The nodes include all the source and sink nodes of the CES service.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The CES services must be created.

Procedure
Step 1 Choose Trail > PTN Service > CES Service Management from the Main Menu. Click Filter. Step 2 Select a CES service and view the node information of the CES service in the lower part of the user interface. ----End

18.5.4 Browsing the CES Service Alarms

In this user interface, you can query the alarms related to a CES service to check whether the CES service has any potential fault.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The CES service must be created.

Procedure
Step 1 Choose Trail > PTN Service > CES Service Management from the Main Menu. Click Filter. Step 2 Select a CES service. Click Alarm. Select Current Alarm or History Alarm to query the alarms related to the CES service. ----End
18-20 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

18 Configuring CES Services

18.5.5 Browsing the CES Service Performance

In this user interface, you can query the performance data related to a CES service to check the running status of the CES service.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The CES service must be created.

Procedure
Step 1 Choose Trail > PTN Service > CES Service Management from the Main Menu. Click Filter. Step 2 Select a CES service. Click Performance to query the performance data related to the CES service. ----End

18.6 Configuration Case of the UNI-UNI CES Service

This section describes the configuration case of the UNI-UNI CES service. 18.6.1 Case Description This section describes the application scenario of the UNI-UNI CES service, including the networking diagram and service planning. 18.6.2 Service Planning To transport the CES services between BTS and BSC, two CES services should be created. 18.6.3 Configuring CES Services by Using the Trail Function This section describes how to configure the two CES services in the example by using the trail function. 18.6.4 Configuring CES Services on a Per-NE Basis This section describes how to configure the two CES services in the example on a per-NE basis. 18.6.5 Checking the Correctness of the Service Configuration After the UNI-UNI CES service is configured, you need to check the correctness of the service configuration. You can check the correctness of the UNI-UNI CES service configuration as follows: attach a 2M BER tester at the CES access port and then perform loopbacks at the other port.

18.6.1 Case Description

This section describes the application scenario of the UNI-UNI CES service, including the networking diagram and service planning. Figure 18-6 shows the networking diagram of the UNI-UNI CES service. shows the networking diagram of the UNI-UNI CES service. A CES service is present between each BTS and BSC. On NE1, the OptiX PTN 1900 accesses the services from the base station.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 18-21

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 18-6 Networking of the CES service

BTS

NE1

BSC

BTS

Figure 18-7 shows the NE planning diagram. Figure 18-7 NE planning diagram

BTS

NE1

BSC

BTS
1-CXP-MD1-3-L12 1-CXP-MD1-5-L12

18.6.2 Service Planning

To transport the CES services between BTS and BSC, two CES services should be created. The UNI-UNI is used to access the local service, and then the UNI-UNI transmits the accessed service to BSC. A CES service is present between each BTS and BSC. Two E1 timeslots of the CES service are fully used. The service shown in Figure 18-6 is taken as an example. Table 18-4 lists the configuration parameters of NE1. Table 18-4 Configuration parameters of NE1 Attribute NE Level
18-22

Value NE1 E1
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Value NE1 E1
Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

18 Configuring CES Services

Attribute Service ID Service Name Mode Source Board Source High Channel Source Low Channel Sink Board Sink High Channel Sink Low Channel

Value 7 CES Local Service 1 UNI-UNI 3-L12 1 5-L12 1

Value 8 CES Local Service 2 UNI-UNI 3-L12 2 5-L12 2

18.6.3 Configuring CES Services by Using the Trail Function

This section describes how to configure the two CES services in the example by using the trail function.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must understand the networking, requirements and service planning of the example. A network must be created.

Procedure
Step 1 Configure E1 interface: BTS-side E1 interface and BSC-side E1 interface. 1. Configure the BTS-side E1 interface. a. b. c. d. In the NE Explorer, select an NE1 and choose Communication > DCN Management from the Function Tree. Click the Port Settings tab. Click E1. Select 3-L12-1(Port-1) and 3-L12-2(Port-2), and set the Enabled Status to Disabled. Click Apply. In the NE Explorer, select NE1 and choose Configuration > Interface Management > PDH Interface from the Function Tree. Then, configure the BTSside interface. Select 3-L12-1(Port-1) and 3-L12-2(Port-2). Set the Port Mode to Layer1. Set the parameters as required.

e.

The configuration parameters are as follows:

Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 18-23

18 Configuring CES Services

l l

OptiX iManager T2000 Operation Guide for PTN NE Management

Port: 3-L12-1(Port-1) and 3-L12-2(Port-2) Name: port1, port2 (Set the port name as required. The port name distinguishes the port from other ports and helps to query the port.) Port Mode: Layer 1 (The port transmits E1 signals.) Encapsulation: Null Channelize: No

l l l

f. g. h. 2.

Click Apply, and the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Click Advanced Attributes tab, Select 3-L12-1(Port-1) and 3-L12-2(Port-2). Set the Frame Format to Unframe. Click Apply, and the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close.

Configure the BSC-side E1 interface. a. b. c. d. In the NE Explorer, select an NE1 and choose Communication > DCN Management from the Function Tree. Click the Port Settings tab. Click E1. Select 5-L12-1(Port-1) and 5-L12-2(Port-2), and set the Enabled Status to Disabled. Click Apply. In the NE Explorer, select NE1 and choose Configuration > Interface Management > PDH Interface from the Function Tree. Then, configure the BSCside interface. Select 5-L12-1(Port-1) and 5-L12-2(Port-2). Set the Port Mode to Layer1. Set the parameters as required. The configuration parameters are as follows:
l l

e.

Port: 5-L12-1(Port-1) and 5-L12-2(Port-2) Name: port11, port22 (Set the port name as required. The port name distinguishes the port from other ports and helps to query the port.) Port Mode: Layer 1 (The port transmits E1 signals.) Encapsulation: Null Channelize: No

l l l

f. g. h.

Click Apply, and the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Click Advanced Attributes tab, Select 5-L12-1(Port-1) and 5-L12-2(Port-2). Set the Frame Format to Unframe. Click Apply, and the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close.

Step 2 Creating UNI-UNI CES Local service 1. 1. 2. On the Main Topology, choose Trail > Emulation Service Creation > CES Service Creation, The Create CES Service dialog box is displayed. Set the parameters of CES service.

18-24

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

18 Configuring CES Services

The configuration parameters are as follows:

l

Basic Information

Service Level: E1 Service Name: CES Local Service 1 Service ID: 7 NE: NE1 Port: 3-L12 High Path: - (In the case of the line port, set the VC-4 higher order path number.) Low Path: 1(In the case of the E1 port, set the E1 port number. In the case of the line port, set the VC-12 lower order path number.) NE: NE1 Port: 5-L12 High Path: Low Path: 1

Source

sink

3.

Click OK, and the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close.

Step 3 Creating UNI-UNI CES Local service 1. Set the parameters related to the CES service by following Step 2.1 to Step 2.3. The configuration parameters are as follows:
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 18-25

18 Configuring CES Services

l

OptiX iManager T2000 Operation Guide for PTN NE Management

Basic Information

Service Level: E1 Service Name: CES Local Service 2 Service ID: 8 NE: NE1 Port: 3-L12 High Path: - (In the case of the line port, set the VC-4 higher order path number.) Low Path: 2 (In the case of the E1 port, set the E1 port number. In the case of the line port, set the VC-12 lower order path number.) NE: NE1 Port: 5-L12 High Path: Low Path: 2

Source

sink

----End

18.6.4 Configuring CES Services on a Per-NE Basis

This section describes how to configure the two CES services in the example on a per-NE basis.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must understand the networking, requirements and service planning of the example. A network must be created.

Procedure
Step 1 Configure E1 interface: BTS-side E1 interface and BSC-side E1 interface. 1. Configure the BTS-side E1 interface. a. b. c. d. In the NE Explorer, select an NE1 and choose Communication > DCN Management from the Function Tree. Click the Port Settings tab. Click E1. Select 3-L12-1(Port-1) and 3-L12-2(Port-2), and set the Enabled Status to Disabled. Click Apply. In the NE Explorer, select NE1 and choose Configuration > Interface Management > PDH Interface from the Function Tree. Then, configure the BTSside interface. Select 3-L12-1(Port-1) and 3-L12-2(Port-2). Set the Port Mode to Layer1. Set the parameters as required.

e.

18-26

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

18 Configuring CES Services

The configuration parameters are as follows:

l l

Port: 3-L12-1(Port-1) and 3-L12-2(Port-2) Name: port1, port2 (Set the port name as required. The port name distinguishes the port from other ports and helps to query the port.) Port Mode: Layer 1 (The port transmits E1 signals.) Encapsulation: Null Channelize: No

l l l

f. g. h. 2.

Click Apply, and the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Click Advanced Attributes tab, Select 3-L12-1(Port-1) and 3-L12-2(Port-2). Set the Frame Format to Unframe. Click Apply, and the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close.

Configure the BSC-side E1 interface. a. b. c. d. In the NE Explorer, select an NE1 and choose Communication > DCN Management from the Function Tree. Click the Port Settings tab. Click E1. Select 5-L12-1(Port-1) and 5-L12-2(Port-2), and set the Enabled Status to Disabled. Click Apply. In the NE Explorer, select NE1 and choose Configuration > Interface Management > PDH Interface from the Function Tree. Then, configure the BSCside interface. Select 5-L12-1(Port-1) and 5-L12-2(Port-2). Set the Port Mode to Layer1. Set the parameters as required. The configuration parameters are as follows:
l l

e.

Port: 5-L12-1(Port-1) and 5-L12-2(Port-2) Name: port11, port22 (Set the port name as required. The port name distinguishes the port from other ports and helps to query the port.) Port Mode: Layer 1 (The port transmits E1 signals.) Encapsulation: Null Channelize: No

l l l

f. g. h.

Click Apply, and the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Click Advanced Attributes tab, Select 5-L12-1(Port-1) and 5-L12-2(Port-2). Set the Frame Format to Unframe. Click Apply, and the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close.

Step 2 Creating UNI-UNI CES Local service 1. 1. 2. In the NE Explorer, Choose Configuration > CES Service Management from the Function Tree. Click New, Set the parameters of CES service.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

18-27

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

The configuration parameters are as follows:

l l l l l l

Service Level: 7 Service Name: CES Local Service 1 Level: E1 Mode: UNI-NNI Source Board: 3-L12 Source High Channel: - (In the case of the line port, set the VC-4 higher order path number.) Source Low Channel: 1 (In the case of the E1 port, set the E1 port number. In the case of the line port, set the VC-12 lower order path number.) Sink Board: 5-L12 Sink High Channel: Sink Low Channel: 1

l l l

3.

Click OK, and the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close.

Step 3 Creating UNI-UNI CES Local service 2. Set the parameters related to the CES service by following Step 2.1 to Step 2.3. The configuration parameters are as follows:
18-28 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

l l l l l l l

18 Configuring CES Services

Service Level: 8 Service Name: CES Local Service 2 Level: E1 Mode: UNI-NNI Source Board: 3-L12 Source High Channel: - (In the case of the line port, set the VC-4 higher order path number.) Source Low Channel: 2 (In the case of the E1 port, set the E1 port number. In the case of the line port, set the VC-12 lower order path number.) Sink Board: 5-L12 Sink High Channel: Sink Low Channel: 2

l l l

----End

18.6.5 Checking the Correctness of the Service Configuration

After the UNI-UNI CES service is configured, you need to check the correctness of the service configuration. You can check the correctness of the UNI-UNI CES service configuration as follows: attach a 2M BER tester at the CES access port and then perform loopbacks at the other port.

Context
As shown in Figure 18-8, a UNI-UNI CES service accesses NE1. Attach a 2M BER tester at the 3-L12 port (port-1) on NE1. On the T2000, set the outloop of the 3-L12 port (port-2) on NE1. Check the correctness of the CES service. Figure 18-8 Checking the CES service
1-CXP-MD1-3-L12

NE1 2M BER tester

Procedure
Step 1 Connect one end of the 2M cable to the 3-L12 port (port-1) on NE1 and the other end to inservice test interface of the 2M BER tester. Step 2 On the T2000, configure the outloop of the 3-L12 port (port-2) on NE1. For the setting of a loopback, refer to 29.7.2 Looping Back PDH interface. Step 3 Start the test. Normally, there should be no bit error in 24 hours. ----End
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 18-29

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

18.7 Configuration Case of the UNI-NNI CES Service

This section describes the configuration case of the UNI-NNI CES service. 18.7.1 Case Description This section describes the UNI-NNI application scenarios of the CES service, including the networking diagram and service planning.UNI-NNI CES 18.7.2 Service Planning There are CES services between BTS and BSC. Two static MPLS tunnels are to be created. One is the working tunnel and the other is the protection tunnel. Then, the CES services can be securely transmitted on the network. 18.7.3 Configuring CES Services by Using the Trail Function This section describes how to configure the three CES services in the example by using the trail function. 18.7.4 Configuring CES Services on a Per-NE Basis This section describes how to configure the three CES services in the example on a per-NE basis. 18.7.5 Checking the Correctness of the Service Configuration After the CES service is configured, you need to check the correctness of the service configuration. You can check the correctness of the CES service configuration as follows: attach a 2M BER tester at the CES port and then perform loopbacks at the remote end.

18.7.1 Case Description

This section describes the UNI-NNI application scenarios of the CES service, including the networking diagram and service planning.UNI-NNI CES

Networking and Requirement

Between BTS and BSC, the CES service is transported through the PTN equipment, as shown in Figure 18-9. Two CES services are available between BTS and BSC that are connected to NE1. NE1 uses the OptiX PTN 1900 to access the services from the base stations, and NE2 and NE3 uses the OptiX PTN 3900. Tunnels should be configured between NE1 and NE3. If the service requires high network security, configure the MPLS APS protection to ensure service transmission.
l l

Working tunnel: NE1-NE2-NE3. NE2 is a transit node. Protection tunnel: NE1-NE6-NE5-NE4-NE3. NE6, NE5, and NE4 are transit nodes. When the working tunnel becomes faulty, the service on it is switched to the protection tunnel for protection.

18-30

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

18 Configuring CES Services

Figure 18-9 Networking diagram of the CES service

NE4 NE5

GE ring on access layer

NE1 NE2

10GE ring on convergence layer

NE3

BSC Working Tunnel Protection Tunnel OptiX PTN 3900 OptiX PTN 1900

BTS

Figure 18-10 shows the planning details of boards on the NE and interfaces on the boards. Figure 18-10 NE planning
1-EX2-2(Port-2) 10.0.3.1 NE4 1-EX2-1(Port-1) 10.0.2.2

4-EFG2-2(Port-2) 10.0.4.1 NE6 4-EFG2-1(Port-1) 10.0.5.2

3-EG16-1(Port-1) 10.0.4.2

1-EX2-2(Port-2) 10.0.3.2 NE5

GE ring on access layer

3-EG16-1(Port-1) 10.0.0.2 NE1

10GE ring on convergence layer

1-EX2-1(Port-1) 10.0.1.2

NE3

1-EX2-2(Port-2) 10.0.2.1

4-EFG2-2(Port-2) 4-EFG2-1(Port-1) 10.0.5.1 10.0.0.1 6-L12

NE2 1-EX2-1(Port-1) 10.0.1.1

6-MP1-1-CD1-1Port-1 10.0.6.1 BSC

BTS

Working Tunnel Protection Tunnel OptiX PTN 3900 OptiX PTN 1900

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

18-31

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

18.7.2 Service Planning

There are CES services between BTS and BSC. Two static MPLS tunnels are to be created. One is the working tunnel and the other is the protection tunnel. Then, the CES services can be securely transmitted on the network. Table 18-5 lists the configuration parameters of NEs. Table 18-5 Configuration parameters of NEs NE NE1 LSR ID 1.0.0.1 Port 4-EFG2-1(Port-1) 4-EFG2-2(Port-2) 3-EG16-1(Port-1) 1-EX2-1(Port-1) 1-EX2-1(Port-1) 1-EX2-2(Port-2) 1-EX2-1(Port-1) 1-EX2-2(Port-2) 1-EX2-1(Port-1) 3-EG16-1(Port-1) 4-EFG2-1(Port-1) 4-EFG2-2(Port-2) Port IP Address 10.0.0.1 10.0.5.1 10.0.0.2 10.0.1.1 10.0.1.2 10.0.2.1 10.0.2.2 10.0.3.1 10.0.3.2 10.0.4.2 10.0.5.2 10.0.4.1 IP Mask 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252

NE2

1.0.0.2

NE3

1.0.0.3

NE4

1.0.0.4

NE5

1.0.0.5

NE6

1.0.0.6

Table 18-6 lists the configuration parameters of Tunnels. Table 18-6 Planning of Tunnel parameters Parameters Tunnel ID Name 100 Working TunnelPositive Static E-LSP No Limit Working Tunnel 101 Working TunnelReverse Static E-LSP No Limit 120 Protection Tunnel-Positive Static E-LSP No Limit Protection Tunnel 121 Protection Tunnel-Reverse Static E-LSP No Limit

Signal Type Scheduling Type Bandwidth (kbit/s)

18-32

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

18 Configuring CES Services

Parameters Ingress Node Transit Node Egress Node Ingress Node Route Information NE1 NE2 NE3 NE1
l

Working Tunnel NE3 NE2 NE1 NE3

l

Protection Tunnel NE1 NE6, NE5, NE4 NE3 NE1

l

NE3 NE4, NE5, NE6 NE1 NE3

l

Out Port: 4EFG2-1 (Port-1) Out Label: 20

Out Port: 1EX2-1(Port-1) Out Label: 21

Out Port: 4EFG2-2 (Port-2) Out Label: 22

Out Port: 1EX2-2 (Port-2) Out Label: 23

Transit Node Route Information

NE2
l

NE2
l

NE6
l

NE4
l

In Port: 3EG16-1 (Port-1) In Label: 20 Out Port: 1EX2-1 (Port-1) Out Label: 30

In Port: 1EX2-1(Port-1) In Label: 21 Out Port: 3EG16-1 (Port-1) Out Label: 31

l l

In Port: 4EFG2-1 (Port-1) In Label: 22 Out Port: 4EFG2-2 (Port-2) Out Label: 32 In Port: 3EG16-1 (Port-1) In Label: 32 Out Port: 1EX2-1 (Port-1) Out Label: 42 In Port: 1EX2-2 (Port-2) In Label: 42 Out Port: 1EX2-1 (Port-1) Out Label: 52

In Port: 1EX2-1 (Port-1) In Label: 23 Out Port: 1EX2-2 (Port-2) Out Label: 33 In Port: 1EX2-1 (Port-1) In Label: 33 Out Port: 3EG16-1 (Port-1) Out Label: 43 In Port: 4EFG2-2 (Port-2) In Label: 43 Out Port: 4EFG2-1 (Port-1) Out Label: 53

l l

l l

l l

NE5
l

NE5
l

l l

l l

NE4
l

NE6
l

l l

l l

Egress Node Route Information

NE3
l

NE1
l

NE3
l

NE1
l

In Port: 1EX2-1 (Port-1) In Label: 30

In Port: 4EFG2-1 (Port-1) In Label: 31

In Port: 1EX2-2 (Port-2) In Label: 52

In Port: 4EFG2-2 (Port-2) In Label: 53

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

18-33

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

Table 18-7 lists the configuration parameters of CES services. Table 18-7 Configuration parameters of the CES service: NE1-NE3 (E1 timeslots partially used) Attribute NE Level Service ID Service Name Mode Source Board Source High Channel Source Low Channel PW ID Tunnel Sink Board Sink High Channel Sink Low Channel Source 64K Timeslot PW Signaling Type PW Type PW Ingress Label/Source Port PW Egress Label/Sink Port Peer IP RTP Head Jitter Compensation Buffering Time(us) Packet Loading Time(us) Clock Mode EXP Value NE1 E1 4 CES Remote Service 1 UNI-NNI 6-L12 2 8 Working Tunnel-Positive (Tunnel-0100) 1-14,20 Static CESoPSN 36 36 10.0.1.2 Disabled 8000 1000 External Clock Mode 4 Value NE3 E1 4 CES Remote Service 1 UNI-NNI 8 Working Tunnel-Reverse (Tunnel-0101) 6-MP1-1-CD1-1(Port-1) VC4-1 2 1-14,20 Static CESoPSN 36 36 10.0.0.1 Disabled 8000 1000 External Clock Mode 4

18-34

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

18 Configuring CES Services

Table 18-8 Configuration parameters of the CES service: NE1-NE3 (E1 timeslots fully used) Attribute NE Level Service ID Service Name Mode Source Board Source High Channel Source Low Channel PW ID Tunnel Sink Board Sink High Channel Sink Low Channel Source 64K Timeslot PW Signaling Type PW Type PW Ingress Label/Source Port PW Egress Label/Sink Port Peer IP RTP Head Jitter Compensation Buffering Time(us) Packet Loading Time(us) Clock Mode EXP Value NE1 E1 5 CES Remote Service 2 UNI-NNI 6-L12 3 9 Working Tunnel-Positive (Tunnel-0100) 1-31 Static SAToP 37 37 10.0.1.2 Disabled 8000 1000 External Clock Mode 4 Value NE3 E1 5 CES Remote Service 2 UNI-NNI 9 Working Tunnel-Reverse (Tunnel-0101) 6-MP1-1-CD1-1(Port-1) VC4-1 3 1-31 Static SAToP 37 37 10.0.0.1 Disabled 8000 1000 External Clock Mode 4

NOTE

For details on the configuration for MPLS APS, see 16.2.4 Creating an MPLS Tunnel Protection Group.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

18-35

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

18.7.3 Configuring CES Services by Using the Trail Function

This section describes how to configure the three CES services in the example by using the trail function.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must understand the networking, requirements and service planning of the example. A network must be created.

Procedure
Step 1 Set LSR IDs. 1. 2. In the NE Explorer, select the NE1 and chooseConfiguration > MPLS Management > Basic Configuration from the Function Tree. Set LSR ID, Start of Global Label Space and Start of Multicast Label Space. Click Apply. The configuration parameters are as follows:
l l

LSR ID: 1.0.0.1 (The LSR ID must be unique in the entire network.) Start of Global Label Space: 0 (The minimum values of egress and ingress labels of the unicast tunnel.)

3.

Display the NE Explorer of NE2, NE3, NE4, NE5, and NE6 separately and perform the preceding two steps to set the parameters such as LSR ID. The configuration parameters are as follows:
l l l l l

NE2 LSR ID: 1.0.0.2 NE3 LSR ID: 1.0.0.3 NE4 LSR ID: 1.0.0.4 NE5 LSR ID: 1.0.0.5 NE6 LSR ID: 1.0.0.6

Step 2 Configure NNI interfaces. 1. 2. In the NE Explorer, select NE1 and choose Configuration > Interface Management > Ethernet Interface from the Function Tree to configure the network-side interface. In the General Attributes tab, select the 4-EFG2-1(Port-1) and 4-EFG2-2(Port-2). Right click the Port Mode filed, and select Layer 3. Set the parameters as required, and click Apply.

The configuration parameters are as follows:

l l

Enable Port: Enabled Port Mode: Layer 3 (The port carries a tunnel.)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

18-36

OptiX iManager T2000 Operation Guide for PTN NE Management

l

18 Configuring CES Services

Working Mode: Auto-Negotiation (Set the working modes of the local port and opposite port as the same.) Max Frame Length (byte): 1620 (Set this parameter according to the length of data packets. All the received data packets that contain more bytes than the maximum frame length are discarded.)

3.

Select the 4-EFG2-1(Port-1) and 4-EFG2-2(Port-2) in the Layer 3 Attributes tab. Right click the Enable Tunnel field and select Enabled. Right-click the Specify IP field and choose Manually. Then, set the parameters such as IP Address and IP Mask. Click Apply. The configuration parameters are as follows:
l l

Enable Tunnel: Enabled Max Reserved Bandwidth (kbit/s): 1000000 (The maximum reserved bandwidth should not exceed the physical bandwidth of the bearer port.) TE Measurement: 10 (The link with a smaller TE measurement value is preferred for route selection of a tunnel. You can intervene in the route selection by adjusting the TE measurement of the link. The smaller the value of the TE measurement, the higher the priority of the link. ) Specify IP: Manually (Manually indicates that you can set the IP address of the port.) 4-EFG2-1(Port-1) IP Address: 10.0.0.1 4-EFG2-2(Port-2) IP Address: 10.0.5.1 IP Mask: 255.255.255.252

l l l l

4.

Display the NE Explorer for NE2, NE3, and NE4 separately. Perform Step 2.1 through Step 2.3 to set parameters of each related interface. Set the parameters of each interface the same as NE1-4-EFG2-1(Port-1). The layer 3 attributes of each ports are as follows:
l

NE2-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.1.1

NE2-3-EG16-1(Port-1) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.0.2

NE3-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.1.2

NE3-1-EX2-2(Port-2) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.2.1

NE4-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.2.2

NE4-1-EX2-2(Port-2) Max Reserved Bandwidth (kbit/s): 10000000

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

18-37

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

IP Address: 10.0.3.1
l

NE5-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.3.2

NE5-3-EG16-1(Port-1) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.4.2

NE6-4-EFG2-1(Port-1) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.5.2

NE6-4-EFG2-2(Port-2) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.4.1

Step 3 Creating Working MPLS Tunnels 1. 2. On the Main Topology, choose Trail > Tunnel Creation. The Create Tunnel dialog box is displayed. Select Create Reverse Tunnel, and configure parameters for the positive tunnel and reverse tunnel in the General Attributes.

The configuration parameters are as follows:

l l l

Tunnel ID: 100(Positive), 101(Reverse) Name: Working Tunnel-Positive, Working Tunnel-Reverse Signal Type: Static (If you set signal type to dynamic, the LDP distributes labels and the tunnel is a dynamic tunnel; if you set signal type to static, labels are manually added and the tunnel is a static tunnel.) Scheduling Type: E-LSP

E-LSP indicates that the tunnel determines the scheduling priority and discard priority of packets according to the EXP information. On one MPLS tunnel of the E-LSP type, there can be a maximum of eight types of PWs.

EXP:- (Set the tunnel priority according to networking planning.)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

18-38

OptiX iManager T2000 Operation Guide for PTN NE Management

l

18 Configuring CES Services

Bandwidth (kbit/s): No Limit (Set the bandwidth according to networking planning.)

3.

Click Next, and select Ingress Node, Egress Node and Transit Node to set route restrictions.

The configuration parameters are as follows:

l

Ingress Node: NE1 (The source node on a tunnel is referred to as ingress node, that is, the node where the tunnel enters the network.) Egress Node: NE3 (The sink node on a tunnel is referred to as egress node, that is, the node where the tunnel exists the network.) Transit Node: NE2 (The pass-through node on a tunnel is referred to as transmit node.)

4.

Click Next. Set tunnel-related parameters and route constraints. Then, click Next. Confirm the tunnel information and then click Finish.

The configuration parameters are as follows:

l

Positive Route Information

NE1 Ingress Node

Out Port: 4-EFG2-1(Port-1) (the source port on the tunnel)

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

18-39

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

Out Label: 20 (The local out label is the same as the downstream in label. Labels are used to forward packets.) Next Hop Address: 10.0.0.2 In Port: 3-EG16-1(Port-1) In Label: 20 Out Port: 1-EX2-1(Port-1) Out Label: 30 Next Hop Address: 10.0.1.2 In Port: 1-EX2-1(Port-1) In Label: 30

NE2 Transit Node

NE3 Egress Node

Reverse Route Information

NE3 Ingress Node

Out Label: 21 In Label: 21 Out Label: 31 In Label: 31

NE2 Transit Node

NE1 Egress Node

Step 4 Creating Protection Tunnel. 1. Create protection Tunnel by following Step 3.1 toStep 3.4. The configuration parameters are as follows:
l

General Attributes

Tunnel ID: 120 (Positive), 121 (Reverse) Name: Protection Tunnel-Positive, Protection Tunnel-Reverse Signal Type: Static Scheduling Type: E-LSP EXP:Bandwidth (kbit/s): No Limit Ingress Node: NE1 Egress Node: NE3 Transit Node: NE6, NE5, NE4

Node Information

For the route information, see Table 13-5.

Step 5 Configure BTS-side E1 interface. 1. 2. In the NE Explorer, select the NE1 and choose Configuration > Interface Management > PDH Interface. Click General Attributes tab, Select 6-L12-2(Port-2) and 6-L12-3(Port-3). Set the Port Mode to Layer 1.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

18-40

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

18 Configuring CES Services

Before setting the port mode, make sure that the port DCN is disabled.

3. 4.

Click Apply, and the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Click Advanced Attributes tab, Select 6-L12-2(Port-2) and set the Frame Format to CRC-4 Multiframe. Select 6-L12-3(Port-3) and set the Frame Format to Unframe.
NOTE

Before setting the port mode, make sure that the port DCN is disabled.

5.

Click Apply, and the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. In the NE Explorer, select the board 6-MP1 of NE1 and choose Configuration > Interface Management > Path Configuration. Select NE3-6-MP1-1-CD1-1(Port-1)-VC4:1-VC12:2 and set VC12 Frame Format to CRC-4 Multiframe. Select NE3-6-MP1-1-CD1-1(Port-1)-VC4:1-VC12:3 and set VC12 Frame Format to Unframe. Click Apply, and the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. On the Main Topology, choose Trail > Emulation Service Creation > CES Service Creation, The Create CES Service dialog box is displayed. Set the parameters of CES service. Select Auto Assign Label,the system automatically assigns the Uplink Label and Downlink Label for the PW.

Step 6 Configure BSC-side STM-1 interface. 1. 2.

3.

Step 7 Creating CES Remote Service 1. 1. 2.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

18-41

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

Basic Information
l l l

Service Level: E1 Service Name: CES Remote Service 1 Service ID: 4

Source
l l l l

NE: NE1 Port: 6-L12 High Path: - (In the case of the line port, set the VC-4 higher order path number.) Low Path: 2 (In the case of the E1 port, set the E1 port number. In the case of the line port, set the VC-12 lower order path number.) 64K Timeslot: 1-14,20 (The 64K Timeslot parameter indicates the timeslot compression list during the configuration of the structured emulation CES services. The selected timeslots are loaded to the PW packets, and then are transmitted to the opposite end through the Ethernet. The timeslot lists at the two ends can be inconsistent, but the number of timeslots must be consistent. Otherwise, the services are unavailable.)

sink
l l l l l

NE: NE3 Port: 6-MP1-1-CD1-1(Port-1) High Path: VC4-1 Low Path: 2 64K Timeslot: 1-14,20

PW
l l

ID: 8 Emulation Mode: CESoPSN (The CESoPSN is of structuralized emulation, and you can set the timeslot compression for it. The SAToP is of non-structuralized emulation, and you cannot set the timeslot compression for it.) Signaling Type: Static (The PW signaling type indicates whether the PW is static or dynamic. In the case of the dynamic PW, the services are available after the signaling negotiation is successful. In the case of the static PW, the signaling negotiation is not needed.) Encapsulation Type: MPLS Uplink Label/Source Port: 36 (The uplink label is the label attached on the packet header when the TDM frames are encapsulated in the PW.) Downlink Label/Sink Port: 36 (The downlink label is the label attached on the packet header when the TDM frames are encapsulated in the PW.) Tunnel Type: MPLS Tunnel Tunnel Name: Working Tunnel-Positive(Tunnel-0100)

l l

l l

3.

Click Advanced and the Advanced Attribute dialog box is displayed. Configure parameters for advanced attribute, Click OK to finish configuring the advanced attributes..

18-42

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

18 Configuring CES Services

The configuration parameters are as follows:

l l

RTP Head: Disabled (The RTP head carries the clock signals.) Jitter Compensation Buffering Time(us): 8000(The Jitter Compensation Buffering Time indicates the buffer size in the receive direction. The PSN is delayed, while the TDM network is plesiochronous. The packet needs to be saved temporarily so that it can be transmitted to the PDH port smoothly. The buffer size is measured in time. This parameter can be set when the pseudo wire (PW) is used for the circuit emulation service (CES).) Packet Loading Time(us): 1000 (The Packet Loading Time parameter indicates the time that the PW packet requires to load the TDM frames. That is, the parameter is used to specify the number of the TDM frames that are loaded in the PW packet. The period of the TDM frame is 125 us. If Packet Loading Time is 1 ms, then eight TDM frames can be loaded in a PW packet.) Uplink Clock Mode: External Clock Mode (The Clock Mode parameter indicates whether the clocks of the PDH/SDH services accessed at both ends are synchronous.) Downlink Clock Mode: External Clock Mode

4.

Click OK, and the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close.

Step 8 Creating CES Remote Service 2. Set the parameters related to the CES service by following Step 7.1 to Step 7.4. Basic Information
l l l

Service Level: E1 Service Name: CES Remote Service 2 Service ID: 5

Source
l l l l

NE: NE1 Port: 6-L12 High Path: Low Path: 3

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 18-43

Issue 01 (2009-06-30)

18 Configuring CES Services

l

OptiX iManager T2000 Operation Guide for PTN NE Management

64K Timeslot: 1-31

sink
l l l l l

NE: NE3 Port: 6-MP1-1-CD1-1(Port-1) High Path: VC4-1 Low Path: 3 64K Timeslot: 1-31

PW
l l l l l l l l

ID: 9 Emulation Mode: CESoPSN Signaling Type: Static Encapsulation Type: MPLS Uplink Label/Source Port: 37 Downlink Label/Sink Port: 37 Tunnel Type: MPLS Tunnel Tunnel Name: Working Tunnel-Positive(Tunnel-0100)

Advanced
l l l l l

RTP Head: Disabled Jitter Compensation Buffering Time(us): 8000 Packet Loading Time(us): 1000 Uplink Clock Mode: External Clock Mode Downlink Clock Mode: External Clock Mode

----End

18.7.4 Configuring CES Services on a Per-NE Basis

This section describes how to configure the three CES services in the example on a per-NE basis.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must understand the networking, requirements and service planning of the example. A network must be created.

Procedure
Step 1 Set LSR IDs. 1. 2. In the NE Explorer, select the NE1 and chooseConfiguration > MPLS Management > Basic Configuration from the Function Tree. Set LSR ID, Start of Global Label Space and Start of Multicast Label Space. Click Apply.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

18-44

OptiX iManager T2000 Operation Guide for PTN NE Management

18 Configuring CES Services

The configuration parameters are as follows:

l l

LSR ID: 1.0.0.1 (The LSR ID must be unique in the entire network.) Start of Global Label Space: 0 (The minimum values of egress and ingress labels of the unicast tunnel.)

3.

Display the NE Explorer of NE2, NE3, NE4, NE5, and NE6 separately and perform the preceding two steps to set the parameters such as LSR ID. The configuration parameters are as follows:
l l l l l

NE2 LSR ID: 1.0.0.2 NE3 LSR ID: 1.0.0.3 NE4 LSR ID: 1.0.0.4 NE5 LSR ID: 1.0.0.5 NE6 LSR ID: 1.0.0.6

Step 2 Configure NNI interfaces. 1. 2. In the NE Explorer, select NE1 and choose Configuration > Interface Management > Ethernet Interface from the Function Tree to configure the network-side interface. In the General Attributes tab, select the 4-EFG2-1(Port-1) and 4-EFG2-2(Port-2). Right click the Port Mode filed, and select Layer 3. Set the parameters as required, and click Apply.

The configuration parameters are as follows:

l l l

Enable Port: Enabled Port Mode: Layer 3 (The port carries a tunnel.) Working Mode: Auto-Negotiation (Set the working modes of the local port and opposite port as the same.) Max Frame Length (byte): 1620 (Set this parameter according to the length of data packets. All the received data packets that contain more bytes than the maximum frame length are discarded.)

3.

Select the 4-EFG2-1(Port-1) and 4-EFG2-2(Port-2) in the Layer 3 Attributes tab. Right click the Enable Tunnel field and select Enabled. Right-click the Specify IP field and choose Manually. Then, set the parameters such as IP Address and IP Mask. Click Apply. The configuration parameters are as follows:
l l

Enable Tunnel: Enabled Max Reserved Bandwidth (kbit/s): 1000000 (The maximum reserved bandwidth should not exceed the physical bandwidth of the bearer port.) TE Measurement: 10 (The link with a smaller TE measurement value is preferred for route selection of a tunnel. You can intervene in the route selection by adjusting the TE measurement of the link. The smaller the value of the TE measurement, the higher the priority of the link. ) Specify IP: Manually (Manually indicates that you can set the IP address of the port.)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 18-45

Issue 01 (2009-06-30)

18 Configuring CES Services

l l l

OptiX iManager T2000 Operation Guide for PTN NE Management

4-EFG2-1(Port-1) IP Address: 10.0.0.1 4-EFG2-2(Port-2) IP Address: 10.0.5.1 IP Mask: 255.255.255.252

4.

Display the NE Explorer for NE2, NE3, and NE4 separately. Perform Step 2.1 through Step 2.3 to set parameters of each related interface. Set the parameters of each interface the same as NE1-4-EFG2-1(Port-1). The layer 3 attributes of each ports are as follows:
l

NE2-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.1.1

NE2-3-EG16-1(Port-1) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.0.2

NE3-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.1.2

NE3-1-EX2-2(Port-2) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.2.1

NE4-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.2.2

NE4-1-EX2-2(Port-2) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.3.1

NE5-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.3.2

NE5-3-EG16-1(Port-1) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.4.2

NE6-4-EFG2-1(Port-1) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.5.2

NE6-4-EFG2-2(Port-2) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.4.1

Step 3 Creating Working MPLS Tunnels.

18-46 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

18 Configuring CES Services

1.

Select NE1 in the NE Explorer . Choose Configuration > MPLS Management > Unicast Tunnel Management from Function Tree. Click New and the New Unicast Tunnel dialog box is displayed. Configure parameters for the positive tunnel and reverse tunnel such as Tunnel ID, Tunnel name, port and labels. Click OKto finish creating the ingress node.

2.

The configuration parameters are as follows:

l l l l l l l

Tunnel ID: 100(Positive), 101(Reverse) Tunnel Name: Working Tunnel-Positive, Working Tunnel-Reverse Node Type: Ingress(Positive), Egress(Reverse) Bandwidth (kbit/s): No Limit (Set the bandwidth according to networking planning.) Out Board/Logic Interface Type: 4-EFG2 (The source board of the Tunnel.) Out Port: 1(Port-1) (The source port of the Tunnel. Next Hop Address: 10.0.0.2 (The IP address of the interface on the next node on the tunnel.) Sink Node: 1.0.0.3 (The LSR ID of the interface on the sink node on the tunnel.) Tunnel Type: E-LSP

l l

E-LSP indicates that the tunnel determines the scheduling priority and discard priority of packets according to the EXP information. On one MPLS tunnel of the E-LSP type, there can be a maximum of eight types of PWs.

EXP: none (Set the tunnel priority according to networking planning.)

3.

In the NE Explorer, select NE2. Then, configure the Tunnel parameters of the transit node by following Step 3.1 to Step 3.2.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

18-47

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

Set related parameters and ensure that the general information of the tunnel is the same as that on NE1. The configuration parameters are as follows:
l l l l l l l l l

Node Type: Transit (NE2 is a transit node on the tunnel.) In Board/Logic Interface Type: 3-EG16 In Port: 1(Port-1) In Label: 20 (Positive), 21 (Reverse) Out Board/Logic Interface Type: 1-EX2 Out Port: 1(Port-1) Out Label: 30 (Positive), 31 (Reverse) Next Hop Address: 10.0.1.2 (Positive), 10.0.0.1 (Reverse) Source Node: 1.0.0.1 (Positive), 10.0.1.2 (Reverse) (The LSR ID of the source node on the tunnel.) Sink Node: 1.0.0.2. (The LSR ID of the sink node on the tunnel.)

4.

In the NE Explorer, select NE3. Then, configure the Tunnel parameters of the egress node by following Step 3.1 to Step 3.2.

18-48

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

18 Configuring CES Services

Set related parameters and ensure that the general information of the tunnel is the same as that on NE1. The configuration parameters are as follows:
l l l l l l

Node Type: Egress (NE3 is a terminal node on the tunnel.) In Board/Logic Interface Type: 1-EX2 In Port: 1(Port-1) In Label: 30(Positive), Out Label: 31 (Reverse) Next Hop Address: -(Positive), 10.0.1.1 (Reverse) Source Node: 1.0.0.1 (Positive) (The LSR ID of the source node on the tunnel.)

Step 4 Creating Protection Tunnel. 1. Display the NE Explorer for NE1, NE6, NE5, NE4, and NE3 separately. Perform Step 3.1 through Step 3.4 to create the ingress node, transit node, and egress node on the bypass tunnel. The configuration parameters are as follows:
l l l l l l

Tunnel ID: 120 (Positive), 121 (Reverse) Tunnel Name: Protection Tunnel-Positive, Protection Tunnel-Reverse Bandwidth(kbit/s): No Limit Tunnel Type: E-LSP EXP: none For the route information, see Table 13-5.

Step 5 Configure BTS-side E1 interface. 1. 2. In the NE Explorer, select the NE1 and choose Configuration > Interface Management > PDH Interface. Click General Attributes tab, Select 6-L12-2(Port-2) and 6-L12-3(Port-3). Set the Port Mode to Layer 1.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 18-49

Issue 01 (2009-06-30)

18 Configuring CES Services

NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

Before setting the port mode, make sure that the port DCN is disabled.

3. 4.

Click Apply, and the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Click Advanced Attributes tab, Select 6-L12-2(Port-2) and 6-L12-3(Port-3). Set the Frame Format to Unframe.
NOTE

Before setting the port mode, make sure that the port DCN is disabled.

5.

Click Apply, and the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. In the NE Explorer, select the board 6-MP1 of NE1 and choose Configuration > Interface Management > Path Configuration . Select NE3-6-MP1-1-CD1-1(Port-1)-VC4:1-VC12:2 and NE3-6-MP1-1-CD1-1(Port-1)VC4:1-VC12:3. Set VC12 Frame Format to Unframe. Click Apply, and the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. In the NE Explorer, select NE1 and choose Configuration > CES Service Management from the Function Tree. Click New and the Create CES Service dialog box is displayed. Configure parameters for CES Remote Service 1.

Step 6 Configure BSC-side STM-1 interface. 1. 2. 3.

Step 7 Creating CES Remote Service 1. 1. 2.

18-50

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

18 Configuring CES Services

The configuration parameters are as follows:

l l l l l l

Service ID: 4 Service Name: CES Remote Service 1 Level: E1 Mode: UNI-NNI Source Board: 6-L12 Source High Channel: - (In the case of the line port, set the VC-4 higher order path number.) Source Low Channel: 2 (In the case of the E1 port, set the E1 port number. In the case of the line port, set the VC-12 lower order path number.) Source 64K Timeslot: 1-14,20 (The 64K Timeslot parameter indicates the timeslot compression list during the configuration of the structured emulation CES services. The
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 18-51

Issue 01 (2009-06-30)

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

selected timeslots are loaded to the PW packets, and then are transmitted to the opposite end through the Ethernet. The timeslot lists at the two ends can be inconsistent, but the number of timeslots must be consistent. Otherwise, the services are unavailable.)
l l l

PW ID: 8 PW Signaling Type: Static PW Type: CESoPSN (The CESoPSN is of structuralized emulation, and you can set the timeslot compression for it. The SAToP is of non-structuralized emulation, and you cannot set the timeslot compression for it.) PW Encapsulation Type: MPLS PW Ingress Label/Source Port: 36 (The ingress label is the label attached on the packet header when the TDM frames are encapsulated in the PW.) PW Egress Label/Sink Port: 36 (The egress label is the label attached on the packet header when the TDM frames are encapsulated in the PW.) Peer IP: 10.0.1.2 Tunnel: Working Tunnel-Positive(Tunnel-0100)

l l l l l

3.

Click QoS. Set the EXP to 4. Click OK to finish configuring the QoS.

4.

Click Advanced Attributes. Then, configure the advanced attributes parameters of the CES service. Click OK to finish configuring the advanced attributes.

The configuration parameters are as follows:

l l

RTP Head: Disabled (The RTP head carries the clock signals.) Jitter Compensation Buffering Time(us): 8000 (The Jitter Compensation Buffering Time indicates the buffer size in the receive direction. The PSN is delayed, while the
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

18-52

OptiX iManager T2000 Operation Guide for PTN NE Management

18 Configuring CES Services

TDM network is plesiochronous. The packet needs to be saved temporarily so that it can be transmitted to the PDH port smoothly. The buffer size is measured in time. This parameter can be set when the pseudo wire (PW) is used for the circuit emulation service (CES).)
l

Packet Loading Time(us): 1000 (The Packet Loading Time parameter indicates the time that the PW packet requires to load the TDM frames. That is, the parameter is used to specify the number of the TDM frames that are loaded in the PW packet. The period of the TDM frame is 125 us. If Packet Loading Time is 1 ms, then eight TDM frames can be loaded in a PW packet.) Ingress Clock Mode: - (The Clock Mode parameter indicates whether the clocks of the PDH/SDH services accessed at both ends are synchronous.) Ingress Clock Mode: External Clock Mode

5. 1.

Click OK, and the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. In the NE Explorer, select NE3. Then, configure the CES Remote Service 1 parameters of NE3 by following Step 7.2 to Step 7.5. The configuration parameters are as follows:
l l l l l l l l l l l l l l l l l l l l l

Service Level: E1 Service Name: CES Remote Service 1 Service ID: 4 Mode: UNI-NNI Source Board: 6-MP1-1-CD1-1(Port-1) Source High Channel: VC4-1 Source Low Channel: 2 Source 64K Timeslot: 1-14,20 PW ID: 8 PW Signaling Type: Static PW Type: CESoPSN PW Ingress Label/Source Port: 36 PW Egress Label/Sink Port: 36 Peer IP; 10.0.0.1 Tunnel: Working Tunnel-Positive(Tunnel-0101) EXP: 4 RTP Head: Disabled Jitter Compensation Buffering Time(us): 8000 Packet Loading Time(us): 1000 Ingress Clock Mode: Egress Clock Mode: External Clock Mode

Step 8 Creating CES Remote Service 2. 1. In the NE Explorer, select NE1 and choose Configuration > CES Service Management from the Function Tree.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 18-53

Issue 01 (2009-06-30)

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

2.

Configure the CES Remote Service 2 parameters of the NE1 by following Step 7.2 to Step 7.5. The configuration parameters are as follows:
l l l l l l l l l l l l l l l l l l l l l

Service Level: E1 Service Name: CES Remote Service 2 Service ID: 5 Mode: UNI-NNI Source Board: 6-L12 Source High Channel: Source Low Channel: 3 Source 64K Timeslot: 1-31 PW ID: 9 PW Signaling Type: Static PW Type: SAToP PW Ingress Label/Source Port: 37 PW Egress Label/Sink Port: 37 Peer IP: 10.0.1.2 Tunnel: Working Tunnel-Positive(Tunnel-0100) EXP: 4 RTP Head: Disabled Jitter Compensation Buffering Time(us): 8000 Packet Loading Time(us): 1000 Ingress Clock Mode: Egress Clock Mode: External Clock Mode

3. 4.

In the NE Explorer, select NE3 and choose Configuration > CES Service Management from the Function Tree. Configure the CES Remote Service 2 parameters of the NE3 by following Step 7.2 to Step 7.5. The configuration parameters are as follows:
l l l l l l l l l l

Service Level: E1 Service Name: CES Remote Service 2 Service ID: 5 Mode: UNI-NNI Source Board: 6-MP1-1-CD1-1(Port-1) Source High Channel: VC4-1 Source Low Channel: 3 Source 64K Timeslot: 1-31 PW ID: 9 PW Signaling Type: Static
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

18-54

OptiX iManager T2000 Operation Guide for PTN NE Management

l l l l l l l l l l l

18 Configuring CES Services

PW Type: SAToP PW Ingress Label/Source Port: 37 PW Egress Label/Sink Port: 37 Peer IP; 10.0.0.1 Tunnel: Working Tunnel-Reverse(Tunnel-0101) EXP: 4 RTP Head: Disabled Jitter Compensation Buffering Time(us): 8000 Packet Loading Time(us): 1000 Ingress Clock Mode: Egress Clock Mode: External Clock Mode

----End

18.7.5 Checking the Correctness of the Service Configuration

After the CES service is configured, you need to check the correctness of the service configuration. You can check the correctness of the CES service configuration as follows: attach a 2M BER tester at the CES port and then perform loopbacks at the remote end.

Context
See Figure 18-11. A CES service exists between NE1 and NE2. Attach a 2M BER tester at the 1-MP1-1-CD1-1 port on NE1. On the T2000, set the inloop of the 1-MP1-1-CD1-1 port on NE2. Check the correctness of the CES service. Figure 18-11 Checking the CES service
1-MP1-1-CD1-1 1-MP1-1-CD1-1

NE1 2M BER tester

NE2

Tunnel PW

Procedure
Step 1 Connect one end of the 2M cable to the 1-MP1-1-CD1-1 port on NE1 and the other end to inservice test interface of the 2M BER tester.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 18-55

18 Configuring CES Services

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 2 Choose Configuration > Automatic Disabling of NE Function from the Main Menu to display the Automatic Disabling of NE Function dialog box. Step 3 Select the NE2 in the left-hand object tree and click .

Step 4 Set Auto Disabling to Disabled for SDH Optical/Electrical Interface Loopback. Step 5 In the NE Explorer, select NE2 and choose Configuration > Interface Management > SDH Interface, and set the Loopback Mode of 1-MP1-1-CD1-1(Port-1) to Inloop. On the T2000, configure the outloop of the 1-MP1-1-CD1-1 port on NE2. For the setting of a loopback, refer to 29.7.2 Looping Back PDH interface. Step 6 Start the test. Normally, there should be no bit error in 24 hours. Step 7 Set Automatic Disabling to Enabled for SDH Optical/Electrical Interface Loopback on NE2 with reference to step 2 to step 4. ----End

18-56

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

19
About This Chapter

Configuring an ATM Service

You can configure an ATM service per trail or per NE. In the case of the per-trail configuration, to configure a complete ATM service is to specify the source and sink nodes in the Trail Management interface. In the case of the per-NE configuration, to configure a complete ATM service is to configure an ATM service at each NE involved in the service trail. 19.1 Basic Concepts Before using the T2000 to configure and manage ATM services, make yourself familiar with the basic concepts related to the ATM service. The information facilitates the operations related to ATM services. 19.2 ATM Service Configuration Flow This section describes the operation tasks for configuring the ATM service, and relations among these tasks. When configuring and managing the ATM services, follow the configuration flow. The application scenarios of the ATM service include the UNI-UNI and UNIs-NNI services. 19.3 Configuring an IMA Group When the PTN equipment accesses IMA services, configure an ATM IMA group at the access node. 19.4 Configuring the ATM Service on a Route Basis This section describes how to configure, on a route basis, an ATM PWE3 service channel that transports ATM signals. When the ATM service is configured on a route basis, the source and sink nodes of the ATM service and the attributes of the PW can be configured in an operation interface. In this way, the ATM service can be fast created. 19.5 Configuring the ATM Service on a Per-NE Basis You can configure an ATM PWE3 service path for transmitting ATM signals on a per-NE basis. When the ATM service is configured on a per-NE basis, the service attributes should be configured at the source end and sink end separately. In this way, a complete ATM service is configured. The configuration of the ATM services on a per-NE basis is of low efficiency, and thus the configuration on an end-to-end basis is recommended. 19.6 Managing ATM Services The ATM service management includes searching for, filtering, querying, and modifying an ATM service, and viewing alarms and performance events relevant to the ATM service. This
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-1

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

management function provides network administrators a method to ensure the normal running of ATM services. 19.7 IMA Configuration Example A case is provided here to show the IMA networking application and the details on how to configure the IMA. 19.8 Configuration Case of the UNI-UNI ATM Service This section describes a configuration case of the UNI-UNI ATM service. The configuration flow diagram is provided to describe the configuration process. The configuration case includes service planning and ATM service configuration. 19.9 Configuration Case of the UNIs-NNI ATM Service This section describes a configuration case of the UNIs-NNI ATM service. The configuration flow diagram is provided to describe the configuration process. The configuration case includes service planning and ATM service configuration.

19-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

19.1 Basic Concepts

Before using the T2000 to configure and manage ATM services, make yourself familiar with the basic concepts related to the ATM service. The information facilitates the operations related to ATM services. 19.1.1 IMA The inverse multiplexing for ATM (IMA) technology, demultiplexes an ATM cell flow to multiple low-speed links, which are then multiplexed at the far end so that the cell flow is restored to its original form. In this way, the multiplexing of multiple low-speed links becomes flexible and easy. 19.1.2 Application of the IMA The ATM IMA service is mainly used to interconnect the wireless base station to the equipment at the transmission access side. 19.1.3 ATM Service Asynchronous transfer mode (ATM) is a technology used to transport packets in cells with ensured QoS. ATM meets the requirements of real-time services and non-real-time services. The OptiX PTN equipment supports both the UNIs-NNI ATM service and UNI-UNI ATM service. 19.1.4 ATM Traffic The ATM communicates through virtual connections, which are uniquely identified by the VPI/ VCI in the cell header. During data transmission, you need to control the traffic of each virtual connection to ensure the quality of service (QoS).

19.1.1 IMA
The inverse multiplexing for ATM (IMA) technology, demultiplexes an ATM cell flow to multiple low-speed links, which are then multiplexed at the far end so that the cell flow is restored to its original form. In this way, the multiplexing of multiple low-speed links becomes flexible and easy. This functionality applies to E1 interconnections between ATM networks, and does not have special requirements for service types. See Figure 19-1. Figure 19-1 ATM IMA group

Physical Link#0 Physical Link#1 Single ATM Cell Stream from ATM Layer Physical Link#2
IMA Virtual Link

Single ATM Cell Stream from ATM Layer

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19-3

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

19.1.2 Application of the IMA

The ATM IMA service is mainly used to interconnect the wireless base station to the equipment at the transmission access side. The ATM IMA service has the following two scenarios.
l l

As shown in Figure 19-2, the ATM service on Node B is directly interconnected to the PTN equipment at the access side through the E1 links. As shown in Figure 19-3, the ATM service on Node B is accessed to the SDH equipment through the E1 links, and then the ATM service is aggregated to the STM-1 link. At last, the IMA protocols are interconnected on the PTN equipment at the access side.

Figure 19-2 IMA networking diagram 1

IMA 1

IMA 2 Node B PTN

E1 Link

Figure 19-3 IMA networking diagram 2

Node B PTN SDH

Node B SDH

E1 Link
Node B

cSTM-1 Link

19.1.3 ATM Service

Asynchronous transfer mode (ATM) is a technology used to transport packets in cells with ensured QoS. ATM meets the requirements of real-time services and non-real-time services. The OptiX PTN equipment supports both the UNIs-NNI ATM service and UNI-UNI ATM service.
19-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

ATM emulation services mainly apply to wireless services. The application scenarios include UNIs-NNI and UNI-UNI, as shown in Figure 19-4.
l

UNIs-NNI ATM service: The PTN equipment accesses the ATM services of customers by using the IMA link or STM link respectively. You can create the ATM PW between the PTN equipment to emulate end-to-end ATM services. At the source end, the ATM cells are encapsulated in the PW. Then, data packets are transparently transmitted in the MPLS network. At the sink end, the ATM services are decapsulated and forwarded to the connected customer network. To customers, the UNIs-NNI ATM services are similar to actual ATM services. UNI-UNI ATM services: The PTN equipment switches and transmits the ATM services at a single point.

Figure 19-4 ATM service networking sample

UNI-UNI

Node B UNI-NNI RNC PE

PE Node B
IMA Link STM-1 ATM Link PW Tunnel

PE

Node B

The ATM UNIs-NNI emulation service supports the convergence of multiple ATM connections into a PW for transmission. As shown in Figure 19-5, three ATM connections are encapsulated into a PW.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19-5

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 19-5 ATM connection convergence sample

19.1.4 ATM Traffic

The ATM communicates through virtual connections, which are uniquely identified by the VPI/ VCI in the cell header. During data transmission, you need to control the traffic of each virtual connection to ensure the quality of service (QoS).

ATM Traffic Modes

As shown in Table 19-1, the PTN equipment supports four traffic modes. During traffic control, you need to set different traffic parameters according to different service types. Table 19-1 ATM service type and traffic Application Type Constant bit rate (CBR) service Application Instance Voice services, video services of a constant bit rate, and circuit emulation services Traffic Parameter PCR, CDVT Remarks The CBR supports the strict requirements for CTD and CDV, but does not support services with variable delay. The UBR does not require a strict delay and the delay variation. Besides, it does not provide a special QoS or ensure the output.

Unspecified bit rate (UBR) service

LAN emulation, IP over ATM, and nonspecial traffic services

PCR, CDVT

19-6

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Application Type UBR+

Application Instance LAN emulation, IP over ATM, and nonspecial traffic services

Traffic Parameter PCR, CDVT

Remarks There are UBR+ services on many NodeBs. The UBR+ services are configured with the MCR. When the service rate does not exceed the configured MCR, the normal service transmission is ensured. The features of the UBR+ service other than the MCR are the same as the features of the UBR service. The rtVBR supports time-sensitive service applications and have restrictions on the delay and delay variation. The nrtVBR does not have restrictions on the delay and delay variation but supports application of services with the variable rate and burst traffic features.

Real time variable bit rate (rtVBR) service

Audio services, and video services of a variable bit rate

PCR, SCR, CDVT, MBS

Non real time variable bit rate (nrtVBR) service

Data packet transmission, terminal meeting, and file transmission

PCR, SCR, MBS

The meanings of the traffic parameters in the table are as follows:

l

Peak cell rate (PCR): It defines the maximum cell rate at which cells are transmitted to a network. Sustainable cell rate (SCR): It defines the maximum sustainable average cell rate at which cells are transmitted to a network. Cell delay variation tolerance (CDVT): When multiple connected cells are converged, at the convergence egress, the transmission of a connected cell may be delayed because of the insertion of other connected cells. Similarly, the transmission delay may also be caused by the insertion of physical layer overheads and OAM cells. In other words. the cells do not evenly arrive at the receive station. The arrival intervals of consecutive cells are different in different periods. The maximum tolerance of this difference is called CDVT. Maximum burst size (MBS): It limits the maximum cell burst amount within the maximum rate permitted.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-7

Issue 01 (2009-06-30)

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Users require each service type to provide a certain QoS and comply with a certain traffic protocol, which is realized by traffic control. During transmission, only user cells complying with the protocol can be successfully transmitted. Cells that do not comply with the protocol are labelled or discarded according to different situations.

Basic Principle of Traffic Control

In general, the control of ATM services combines the preventive control and reactive control methods. Preventive control is the main method, but when congestion occurs, the network can take measures to clear the congestion. In point of effect, the ATM traffic control can be classified into two parts as follows:
l l

Traffic parameter control: preventive control Congestion control: reactive control

Traffic Parameter Control

The function of traffic parameter control is used to set up proper connections and to control the connected cell flow according to the traffic parameters. If the control of these parameters fails, traffic congestion may occur. The traffic parameter control includes the following methods:
l l

Usage parameter control (UPC)/network parameter control (NPC) Traffic shaping

UPC/NPC UPC/NPC monitors and controls the traffic to judge whether cell violation occurs according to the negotiated parameters. If cell violation occurs, corresponding measures will be taken to prevent network resources from being invaded viciously or unintentionally. This ensures that one link never violates the traffic control. UPC is an act of connection monitoring at the UNI (dedicated or public), and NPC is an act of connection monitoring at the NNI (dedicated or public). According to different traffic types. the UPC includes the following measures:
l l

Allow cells to pass through: The cells are considered protocol-abiding by the UPC. Label cells: This operation is performed on the cell loss priority (CLP). The UPC labels only cells whose CLP values are 0 by changing the CLP values to 1. In this case, these cells are in conflict with the traffic convention. If the bandwidth is sufficient, these cells are allowed to pass through. If the bandwidth is insufficient, however, these labeled cells are discarded. Discard cells: The cells violate the protocol and thus cannot be transmitted continuously.

Traffic Shaping Traffic shaping is a method of changing the traffic feature of a cell flow to realize a higher network efficiency and ensure the QoS index. Traffic shaping helps the cell flow to be transmitted more evenly, maximize the efficiency, and eases the network burden.

Congestion Control
Traffic parameter control is based on the connection and cells, but congestion control relates to different service types.
19-8 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

If a network requires discarding cells, a better solution of congestion is to discard packets rather than cells. When an NE discards cells, it also discards a part of the packet. As a result, the upper layer protocol, such as the TCP/IP protocol, is retransmitted, and thus congestion or even collapse occurs.

19.2 ATM Service Configuration Flow

This section describes the operation tasks for configuring the ATM service, and relations among these tasks. When configuring and managing the ATM services, follow the configuration flow. The application scenarios of the ATM service include the UNI-UNI and UNIs-NNI services.

UNI-UNI ATM service

Figure 19-6 shows the configuration flow of the UNI-UNI ATM service. For details of each step, see the related section. Figure 19-6 Configuration flow of the UNI-UNI ATM service

Required Optional

Start

Creating Network

Configure the ATM Policy

Configure the ATM Interface Configure the UNIUNI ATM Service End

Table 19-2 Tasks for configuring the UNI-UNI ATM service Task 1. Creating Network 2. Configure the ATM Policy
Issue 01 (2009-06-30)

Remarks To create a network, you need to create NEs, configure NE data, create fibers, and configure the clock. The ATM policy is used for traffic management of the ATM service.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19-9

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Task 3. Configure the ATM Interface 4. Configure the UNI-UNI ATM Service

Remarks The ATM interface accesses services from NodeB. To configure the UNI-UNI ATM service, you need to specify the service ID and service name, select the connection type, and configure the connection.

UNIs-NNI ATM service

Figure 19-7 shows the configuration flow of the UNIs-NNI ATM service. For details of each step, see the related section. Figure 19-7 Configuration flow of the UNIs-NNI ATM service

Required Optional

Start

Creating Network

Configure the network-side interface

Configure the LSR ID

Configure the control plane

Configure the Tunnel

Configure the ATM Policy

Configure the ATM Interface

Configure the UNIsNNI ATM service

End

19-10

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Table 19-3 Tasks for configuring the UNIs-NNI ATM service Task 1. Creating Network 2. Configure the LSR ID 3. Configure the network-side interface 4. Configure the control plane Remarks To create a network, you need to create NEs, configure NE data, create fibers, and configure the clock. Configure the LSR ID of the NE and start of global label space. Set the general attributes and Layer 3 attributes (tunnel enable status and IP address) for interfaces to carry the tunnel carrying. Set the protocol parameters related to the control plane to create the tunnel.
l

To create a static MPLS tunnel to transmit the ATM service, the parameters related to the control plane need not be set. To create a dynamic MPLS tunnel to transmit the ATM service, you need to set the following protocol parameters: 1. Set the IGP-ISIS protocol parameters. For details, see 8.2 Configuring the IGP-ISIS Protocol. 2. Set the MPLS-RSVP protocol parameters. For details, see 8.4 Configuring the MPLS-RSVP Protocol. To create a dynamic PW to transmit the service, you need to set the parameters related to the IGP-ISIS protocol and the MPLS-LDP protocol.

To create an IP Tunnel or GRE Tunnel to transmit the ATM service, you need to Configuring Static Routes.

5. Configure the Tunnel

A tunnel transmits the service.

l

If an static MPLS tunnel is required, configure an MPLS tunnel in the per-NE or per-trail mode. Specify the tunnel ID, set signaling type to static, name the service, and specify the ingress node, egress node, and transit node. If a dynamic MPLS Tunnel is required, name the service, set signaling type to dynamic, and specify the source node and sink node for the tunnel. If an IP Tunnel or GRE Tunnel is required, select the source board, source port, and IP address of the sink port.

6. Configure the ATM Policy 7. Configure the ATM Interface

The ATM policy is used for traffic management of the ATM service. The ATM interface accesses services from NodeB.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19-11

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Task 8. Configure the UNIs-NNI ATM service

Remarks 1. Create an ATM service: Specify the service ID, name the service, and select the service type and connection type. 2. Configure the connection: Set the source information, PW ID, sink information, and policy. 3. Configure a PW: Set the PW type, label, and tunnel type. 4. Configure CoS mapping: Set the CoS policy for the PW.

Table 19-4 ATM Interface Support ed Board Type Leve l Configuration Method

E1

1. In General attributes for the PDH interface, set the port mode to Layer 2. For details, see 10.2.1 Setting General Attributes of PDH Interfaces. 2. In Advanced Attributes for the PDH interface, set the Frame Format and Frame Mode. For details, see 10.2.3 Setting the Advanced Attributes of PDH Interfaces.

E1 board (For example: D75)

3. Configuring bound channels in an ATM IMA Group, for details, see 19.3.1 Configuring Bound Channels in an ATM IMA Group in the . 4. Set attributes of the ATM IMA group. In particular, specify the IMA Transmit Frame Length, set the IMA Symmetry Mode, and enable the IMA protocol. For details, see 19.3.2 Configuring Attributes of an ATM IMA Group in the . 5. Set attributes of the ATM interface. In particular, set the interface type, maximum VPI, and maximum VCI. For details, see Configuring ATM Interface Attributes.

19-12

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Support ed Board Type

Leve l

Configuration Method

64K times lots

1. In General attributes for the PDH interface, set the port mode to Layer 1. For details, see 10.2.1 Setting General Attributes of PDH Interfaces. 2. In Advanced Attributes for the PDH interface, set the Frame Format and Frame Mode. For details, see 10.2.3 Setting the Advanced Attributes of PDH Interfaces. 3. Create a serial port and specify the timeslots used by the service. Set the port mode to Layer 2 and the encapsulation type is ATM. For details, see 10.7.1 Creating Serial Interfaces. 4. Configuring bound channels in an ATM IMA Group, for details, see 19.3.1 Configuring Bound Channels in an ATM IMA Group. 5. Set attributes of the ATM IMA group. In particular, specify the IMA Transmit Frame Length, set the IMA Symmetry Mode, and enable the IMA protocol. For details, see 19.3.2 Configuring Attributes of an ATM IMA Group. 6. Set attributes of the ATM interface. In particular, set the interface type, maximum VPI, and maximum VCI. For details, see Configuring ATM Interface Attributes.

ATM STM-1 board (For example: AD1)

STM -1

1. In Layer 2 Attributes for the SDH interface, set the port type, maximum VPI, and maximum VCI. For details, see 10.1.2 Setting the Layer 2 Attributes of SDH Interfaces.

Channeli zed STM-1 board (For example: CD1)

VC1 2

1. Configuring bound channels in an ATM IMA Group, for details, see 19.3.1 Configuring Bound Channels in an ATM IMA Group in the . 2. Set attributes of the ATM IMA group. In particular, specify the IMA Transmit Frame Length, set the IMA Symmetry Mode, and enable the IMA protocol. For details, see 19.3.2 Configuring Attributes of an ATM IMA Group. 3. Set attributes of the ATM interface. In particular, set the interface type, maximum VPI, and maximum VCI. For details, see Configuring ATM Interface Attributes.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19-13

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Support ed Board Type

Leve l

Configuration Method

64K times lots

1. Create a serial port and specify the timeslots used by the service. Set the port mode to Layer 2 and the encapsulation type is ATM. For details, see 10.7.1 Creating Serial Interfaces. 2. Configuring bound channels in an ATM IMA Group, for details, see 19.3.1 Configuring Bound Channels in an ATM IMA Group. 3. Set attributes of the ATM IMA group. In particular, specify the IMA Transmit Frame Length, set the IMA Symmetry Mode, and enable the IMA protocol. For details, see 19.3.2 Configuring Attributes of an ATM IMA Group. 4. Set attributes of the ATM interface. In particular, set the interface type, maximum VPI, and maximum VCI. For details, see Configuring ATM Interface Attributes.

19.3 Configuring an IMA Group

When the PTN equipment accesses IMA services, configure an ATM IMA group at the access node.

Context
Figure 19-8 shows the flow for configuring an IMA group.

19-14

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Figure 19-8 IMA group configuration flow

Start

Configure bound paths for an ATM IMA group

Configure IMA group attributes

Configure ATM interface attributes

Query the IMA group states

Query the states of the link of an IMA group

Reset an IMA group

Modify an IMA group

Delete an IMA group

End

Required

Optional

19.3.1 Configuring Bound Channels in an ATM IMA Group When the PTN equipment accesses IMA services, configure bound channels in an ATM IMA group at the access node. One ATM IMA group corresponds to one ATM trunk port. Bind channels with the ATM trunk port and then enable the IMA group. The ATM trunk port can be bound with one or several E1, VC12-xv or Fractional E1 ports. 19.3.2 Configuring Attributes of an ATM IMA Group After configuring the channels bound with the IMA group, enable the IMA protocol and configure attributes of the IMA group to make the IMA group meet the service requirements. 19.3.3 Configuring the ATM Interfaces By using the E1 board, channelized STM-1 board, or ATM STM-1 board, the OptiX PTN equipment can access ATM services at the E1/VC-12, fractional E1, or STM-1 level. In the case of fractional E1, one E1/VC12 channel can carry multiple services. Certain timeslots of the 32 timeslots in an E1/VC12 channel can be allocated for the CES services and the others for the ATM services. In this manner, the resources are saved and the costs are reduced. 19.3.4 Querying IMA Group States In the case of routine maintenance and troubleshooting, the operator need query information on states of an IMA group to check whether the IMA group is normal. 19.3.5 Querying IMA Link States

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19-15

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

In the case of routine maintenance and troubleshooting, the operator need query information on states of an IMA link to check whether the IMA link is normal. 19.3.6 Resetting an IMA Group In the case of deployment and troubleshooting, the operator can reset an IMA group to re-enable the IMA group protocol. 19.3.7 Modifying an IMA Group When attributes of an IMA group displayed on the T2000 are not consistent with those in the network, modify attributes of this IMA group. If any service is configured and activated at the ATM Trunk port for an IMA group, modification of the IMA group may interrupt services. 19.3.8 Deleting an IMA Group Delete the redundant or idle IMA groups to release the resources. If any service is configured and activated at the ATM Trunk port for an IMA group, deleting the IMA group may interrupt the services.

19.3.1 Configuring Bound Channels in an ATM IMA Group

When the PTN equipment accesses IMA services, configure bound channels in an ATM IMA group at the access node. One ATM IMA group corresponds to one ATM trunk port. Bind channels with the ATM trunk port and then enable the IMA group. The ATM trunk port can be bound with one or several E1, VC12-xv or Fractional E1 ports.

Prerequisite
You must be an NM user with "NE operator" authority or higher. When the MLPPP or CES services is configured or the DCN is enabled on the VCTRUNK, the VCTRUNK resources are occupied and thus the IMA group cannot be created. When an E1or Fractional E1 port is bound with an IMA group, Port Mode should be set to Layer 2.

Context
NOTE

Only the E1 ports or the VC12 paths on the same processing board can be bound.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM IMA Management from Function Tree. Step 2 Click the Binding tab and click Configuration. The Bound Path dialog box is displayed.

19-16

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Step 3 Configure boards and VCTRUNK ports in Available Boards and Configurable Ports respectively. Step 4 Select E1, Fractional E1 or VC12-xv for Level. Step 5 Select a port in Available Resources. Click to bind the port to the VCTRUNK. Click

to cancel binding of the port to the VCTRUNK.

CAUTION
The VCTRUNK that is first added into the IMA group should be deleted at last. The ports that are bound to the same VCTRUNK must have the same E1 frame mode or VC12 frame mode. When the member links of an IMA group are at the serial ports of the 64K level, there are the following restrictions:
l l l

One serial port should be bound with a minimum of three 64K timeslots. The number of bound 64K timeslots should be the same for different serial ports. In one E1, only one serial port can be used as a member link of an IMA group.

Step 6 Click OK. A dialog box is displayed, indicating that the operation succeeds. Click Close. ----End

19.3.2 Configuring Attributes of an ATM IMA Group

After configuring the channels bound with the IMA group, enable the IMA protocol and configure attributes of the IMA group to make the IMA group meet the service requirements.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-17

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

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

Procedure
Step 1 Click the NE in the NE Explorer. Choose Configuration > Interface Management > ATM IMA Management from Function Tree. Step 2 Click the IMA Group Management tab, enable the IMA protocol, and configure attributes of the IMA group. Click Apply. A dialog box is displayed, indicating that the operation succeeds. Click Close.
NOTE

Take the following precautions when setting parameters.

l l l l l

You can enable or disable the IMA Protocol Enable Status of the IMA group only after configuring the bound path of the corresponding VCTRUNK of the IMA group. IMA Protocol Version: For the OptiX PTN 912, set this parameter to 1.1. IMA Protocol Version: The IMA protocols running on interconnected equipment must be of the same version. IMA Transmit Frame Length: The optional values are 32, 64, 128 and 256. IMA Symmetry Mode: This parameter should be set to Symmetric Mode and Symmetric Operation. In this case, Minimum Number of Active Transmitting Links should be consistent with Minimum Number of Active Receiving Links. Maximum Delay Between Links: This parameter indicates the maximum delay variance among different links in one IMA group. The value ranges from 1 ms to 120 ms, with 1 ms spacing. If the IMA protocol is enabled, only Minimum Number of Active Transmitting Links, Minimum Number of Active Receiving Links and Maximum Delay Between Links can be set. In the case of OptiX 3900/1900/912, the Clock Mode can be set only after the IMA protocol is disabled. You can modify the IMA Protocol Version, IMA Transmit Frame Length and IMA Symmetry Mode only after you disable the IMA Protocol Enable Status.

l l l l

----End

19.3.3 Configuring the ATM Interfaces

By using the E1 board, channelized STM-1 board, or ATM STM-1 board, the OptiX PTN equipment can access ATM services at the E1/VC-12, fractional E1, or STM-1 level. In the case of fractional E1, one E1/VC12 channel can carry multiple services. Certain timeslots of the 32 timeslots in an E1/VC12 channel can be allocated for the CES services and the others for the ATM services. In this manner, the resources are saved and the costs are reduced.

Prerequisite
You must be an NM user with "NE operator" authority or higher. Disable the DCN function of the port that carries the ATM IMA services.

Context
In the case of the OptiX PTN equipment, Frame Mode of the packets at the PDH interface or SDH interfaces can be 30-timeslot or 31-timeslot. In an E1/VC12 frame, the timeslots used to transport service data vary with Frame Mode:
19-18 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

l

19 Configuring an ATM Service

When Frame Mode is set to 30-timeslot, timeslots 1-15 and 17-31 of an E1 frame are used to transport service data, and timeslots 0 and 16 cannot be used for fractional E1. When Frame Mode is set to 31-timeslot, timeslots 1-31 of an E1 frame are used to transport service data, and timeslot 0 cannot be used for fractional E1.

Procedure
l Use an E1 board to carry the ATM IMA services. Configure an Interface at the Fractional E1 Level. 1. 2. In the NE Explorer, click an NE and choose Configuration > Interface Management > PDH Interface from the Function Tree. In the General Attributes tab, select 23-D12-4(Port-4) and 23-D12-5(Port-5). Set the Port Mode to Layer 1 and click Apply.

3.

Click Advanced Attributes tab, set Frame Format and Frame Mode according to networking planning. Click Apply.

4.

Choose Configuration > Interface Management > Serial Interface from the Function Tree. Click New in the General Attributes tab and the New Serial Interface dialog box is displayed. In the New Serial Interface dialog box, set the Level, Used Board, Used Port, and 64K Timeslot fields and then click OK. Create serial interfaces of 23D12-4(Port-4) and 23-D12-5(Port-5).
NOTE

5.

The serial interface at the 64k timeslots level is created as follows:

l l l

The number of bundled timeslots ranges from 3 to 30. In one E1, only one serial interface can be used as the member link of the IMA group. The number of bundled 64k timeslots for all the member serial interfaces configured in an IMA group should be the same. In this example, when the serial interfaces of 23-D12-4(Port-4) and 23-D12-5 (Port-5) are created, nine 64k timeslots are used.

6.

Select the created serial interfaces, set Port Mode to Layer 2, and then click Apply.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19-19

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

7.

Choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Click Configuration in the Binding tab and the Bound Path dialog box is displayed. Select the bound board and port, select Fractional E1 for the Level field, and select Available Resources. Then, click port to Selected Bound Paths. to add the bound board and

8.

9.

Click Apply.

10. On the IMA Group Management tab, select the IMA group 3-MP1-1-MD1-1 (Trunk-1). Set the parameters such as IMA Transmit Frame Length and IMA Symmetry Mode according to the network planning. Then, set IMA Protocol Enable Status to Enabled. Click Apply. 11. On the ATM Interface Management tab, click the IMA group 3-MP1-1-MD1-1 (Trunk-1). Then, set the parameters such as VPI/VCI range for the ports according to the network planning. Click Apply. Configure an Interface at the E1 Level. 1. 2. 3. 4. 5. In the NE Explorer, select an NE and choose Configuration > Interface Management > PDH Interface from the Function Tree. In General Attributes tab, select 19-D75-10(Port-10) to 19-D75-15(Port-15). Set Port Mode to Layer 2, and click Apply. In Advanced Attributes tab, set Frame Format and Frame Mode according to networking planning. Click Apply. Set the parameters about the IMA group at the E1 level according to 7 through 11 of "Using an E1 board to configure an interface at the fractional E1 level". Select E1 for the Level field for the available bound path and select ports in Available Resources.

19-20

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Use an channelized STM-1 board to carry the ATM IMA services. Configure an Interface at the Fractional E1 Level. 1. 2. 3. 4. In the NE Explorer click 3-MP1 board, and choose Configuration > Interface Management > Path Configuration from the Function Tree. Set VC12 Frame Format and Frame mode according to networking planning. Click Apply. Create serial interfaces for the CD1 board according to 4 through 6 of "Using an E1 board to configure an interface at the fractional E1 level". In the displayed New Serial Interface dialog box, set Used Timeslot and 64K Timeslot for ports.

NOTE

Used Timeslot: VC-12 path number. The CD1 board can access 2 x channelized STM-1 signals.Each channel of channelized STM-1 signals support 63 VC-12 paths. 64K Timeslot: One VC-12 path contains 32 64K timeslots. Among the 32 64K timeslots, timeslot 0 transports the signaling information and thus is unavailable.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19-21

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

5.

Set the parameters about the IMA group at the Fractional E1 level of 3-MP1CD1-1(Tunk-1) according to 7 through 11 of "Using an E1 board to configure an interface at the fractional E1 level". Set the VC12 Frame Format and Frame Mode according to 1 through 2 of "Using an STM-1 board to configure an interface at the fractional E1 level". Set the parameters about the IMA group at the VC-12 level according to 7 through 11 of "Using an E1 board to configure an interface at the fractional E1 level". Select E1 for the Level field for the available bound path and select VC-12 paths in Available Resources.

Configure an Interface at the VC-12 Level. 1. 2. 3.

Use the ATM STM-1 board to carry the ATM services. 1. 2. 3. Set the VC12 Frame Format and Frame Mode according to 1 through 2 of "Using an STM-1 board to configure an interface at the fractional E1 level". In the NE Explorer, select an NE and choose Configuration > Interface Management > SDH Interface from the Function Tree. In Layer 2 Attributes, select 3-MP1-1-AD1-1(Trunk-1) and set the parameters such as VPI/VCI range for the ports according to the network planning. Click Apply.

----End

Result
When creating the IMA groups at both ends of the interconnected equipment is complete, you can query the IMA group status on the U2000 to check whether the IMA groups are in proper status. 1. 2. In the NE Explorer, click an NE and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. On the IMA Group States tab, click Query. Check Near-End Group Status, Far-End Group Status, and Number of Transmit/Receive Links.
l

If Near-End Group Status and Far-End Group Status are displayed as Operational, the negotiation of the IMA groups is successful. If Near-End Group Status and Far-End Group Status are displayed as other status, handle the anomaly with reference to Table 19-5.

3.

In the IMA Link Status tab, click Query. Check Near-End Receiving/Transmitting Status and Far-End Receiving/Transmitting Status.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

19-22

OptiX iManager T2000 Operation Guide for PTN NE Management

l

19 Configuring an ATM Service

If Near-End Receiving Status, Near-End Transmitting Status, Far-End Receiving Status, and Far-End Transmitting Status are displayed as Usable, it indicates that the IMA link is normal. If Near-End Receiving Status, Near-End Transmitting Status, Far-End Receiving Status, and Far-End Transmitting Status are displayed as Unusable, it indicates that the IMA link is faulty. For details on the IMA link status parameters, see Table 19-6.

Table 19-5 lists the IMA group status parameters. Table 19-5 IMA group status parameters Near-End/Far-End Group Status Start-Up Description This end is in the Start-Up status and is waiting to be indicated that the far-end is also in the Start-Up status. Suggestion Start the IMA protocol for the opposite IMA group and check whether the IMA groups are normal. The IMA groups are in the progress of negotiation. Wait for 500 ms and then check whether the IMA groups are normal. Check whether the parameter settings are consistent for the IMA groups at both ends. If not, re-set the inconsistent parameters to ensure that all the parameter settings are consistent for the IMA groups at both ends. When the fault of the IMA link is rectified, check whether the IMA groups are in proper status. .

Start-Up-ACK

This is a transitional state. When both the near-end and far-end groups startup, they move to this state.

Config-Aborted

This state is entered when the far-end tries to apply unacceptable configuration parameters.

Insufficient-Links

The status is displayed when the parameter settings for the IMA groups at both ends are consistent but the link resources are insufficient. In this case, the number of activated links is less than the minimum number of activated links for an IMA group. The group is blocked. The group can be blocked for maintenance purposes while sufficient links are Active in both transmitting and receiving directions. The group is not inhibited and has sufficient links in both transmitting and receiving directions.

Blocked

Operational

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19-23

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Table 19-6 lists the IMA link status parameters. Table 19-6 IMA link status parameters Receive/Transmit Status Unusable Description The status is displayed when an IMA link is added to an IMA group but the IMA link is not available because of fault-caused or manual suppression. This status indicates that the link is availably and it is displayed when you are waiting for the remote receive link to be activated. In this case, this link is not added to the cyclical transmitting process of the IMA group. This status indicates that the link is activated. If service cells accessed, they can be transmitted. This link is added to the cyclical transmitting process of the IMA group. Suggestion

Usable

Active

19.3.4 Querying IMA Group States

In the case of routine maintenance and troubleshooting, the operator need query information on states of an IMA group to check whether the IMA group is normal.

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. You must complete the configuration of an IMA group.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM IMA Management from Function Tree. Step 2 Click the IMA Group States tab and select the IMA group for query. Click Query. A dialog box is displayed, indicating that the operation succeeds. Click Close. ----End

19.3.5 Querying IMA Link States

In the case of routine maintenance and troubleshooting, the operator need query information on states of an IMA link to check whether the IMA link is normal.

19-24

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. You must complete the configuration of an IMA link.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM IMA Management from Function Tree. Step 2 Click the IMA Link States tab and select the IMA link for query. Click Query. A dialog box is displayed, indicating that the operation succeeds. Click Close. ----End

19.3.6 Resetting an IMA Group

In the case of deployment and troubleshooting, the operator can reset an IMA group to re-enable the IMA group protocol.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. You must complete the creation of the IMA group.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM IMA Management from Function Tree. Step 2 Click the IMA Group Management tab and select the IMA group. Click Reset. A dialog box is displayed, indicating that the operation succeeds. Click Close. ----End

19.3.7 Modifying an IMA Group

When attributes of an IMA group displayed on the T2000 are not consistent with those in the network, modify attributes of this IMA group. If any service is configured and activated at the ATM Trunk port for an IMA group, modification of the IMA group may interrupt services.

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

Context

CAUTION
If any service is configured and activated at the ATM Trunk port for the IMA group, modification of the IMA group may interrupt services. Exercise caution for this.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-25

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM IMA Management from Function Tree. Step 2 Click the IMA Group Management tab and modify related attributes of the IMA group. Click Apply. A dialog box is displayed, indicating that the operation succeeds. Click Close. ----End

19.3.8 Deleting an IMA Group

Delete the redundant or idle IMA groups to release the resources. If any service is configured and activated at the ATM Trunk port for an IMA group, deleting the IMA group may interrupt the services.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The IMA Protocol Enable Status of the IMA group must be Disabled.

Context

CAUTION
If any service is configured and activated at the ATM Trunk port for the IMA group, deleting the IMA group may interrupt the services. Exercise caution for this.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Step 2 Click the Banding tab and select an IMA group. Click Delete. A dialog box is displayed, indicating that the operation may interrupt the services. Click OK. A dialog box is displayed, indicating that the operation is successful. Click Close. ----End

19.4 Configuring the ATM Service on a Route Basis

This section describes how to configure, on a route basis, an ATM PWE3 service channel that transports ATM signals. When the ATM service is configured on a route basis, the source and sink nodes of the ATM service and the attributes of the PW can be configured in an operation interface. In this way, the ATM service can be fast created. 19.4.1 Creating ATM Services by Using the Trail Function You can create an ATM PWE3 service path for transmitting ATM signals by using the trail function. By using the trail function, you can directly configure the source and sink nodes of an ATM service and the PW attributes in a user interface of the T2000. In this way, the ATM service can be fast created.
19-26 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

19.4.2 Modifying the ATM Service by Using the Trail Function If the configuration information of an ATM service is inconsistent with that in the real network, modify the ATM service by using the trail function. 19.4.3 Deleting ATM Services in Trail Mode If any ATM service channels are redundant, delete the ATM service channels to release resources. To fast delete an ATM service, fast delete the ATM service that contains information on the source and sink NEs on the T2000.

19.4.1 Creating ATM Services by Using the Trail Function

You can create an ATM PWE3 service path for transmitting ATM signals by using the trail function. By using the trail function, you can directly configure the source and sink nodes of an ATM service and the PW attributes in a user interface of the T2000. In this way, the ATM service can be fast created.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. You must complete the configuration of the control plane. For configuration method, see 8 Configuring the Control Plane. If IMA services are accessed, you must complete the configuration of an IMA group. For configuration method, see Configuring the IMA. You must complete the configuration of the ATM policy. For configuration method, see 9.12.1 Creating the ATM Policy. You must complete the creation of a tunnel. For configuration method, see 13.3.2 Creating a Static MPLS Tunnel by Using the Trail Function.

Context
The OptiX PTN equipment can access services at the E1/VC-12 level or 64K timeslot level. When the OptiX PTN equipment accesses the services at the E1/VC-12 level, all the available timeslots of the E1/VC-12 channels are used to transport services. When the OptiX PTN equipment accesses the services at the 64K timeslot level, one E1/VC-12 channel can be used to transport both the ATM services and CES services (certain timeslots allocated for ATM services and others for CES services). In this manner, the E1/VC-12 channels are used flexibly.

Procedure
Step 1 Choose Trail > PTN Service > ATM Service Creation from the Main Menu. Step 2 Create a UNI-UNI or UNIs-NNI service in the Create ATM Service window.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19-27

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

For the UNI-UNI service, you need not specify a PW and set parameters of the PW. For the UNIs-NNI service, you need specify a PW and set parameters of the PW.

Step 3 To create a UNI-UNI service, go to Step 4. To create a UNIs-NNI service, go to Step 5. Step 4 Optional: Create a UNI-UNI service. 1. Set basic attributes of the ATM service in General Attributes.
NOTE

For the ATM Service type, you can select the following.
l l

PVP: Only the VPI value of the ATM connection can be modified. PVC: The VPI and VCI values of the ATM connection can be modified.

2.

In Source, click Browse and select the source NE and source port of the service. In Sink, click Browse and select the sink NE and sink port of the service.
NOTE

For a UNI-UNI service, select the same source and sink NEs. Select one source port and one sink port.

3.

In ATM Connection, click Add to add an ATM connection.

19-28

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

19 Configuring an ATM Service

l l

Modify the VPI and VCI or not, according to the ATM Service type. You can proceed with the next operation only after selecting the uplink and downlink ATM policies of the ATM connection.

Step 5 Optional: Create a UNIs-NNI service. 1. Set basic attributes of the ATM service in General Attributes.
NOTE

For the ATM Service type, you can select the following.
l l

PVP: Only the VPI value of the ATM connection can be modified. PVC: The VPI and VCI values of the ATM connection can be modified.

2.

In Source, click Browse and select the source NE and source port of the service. In Sink, click Browse and select the sink source and sink port of the service.
NOTE

For a UNIs-NNI service, select different source and sink NEs.

3.

In ATM Connection, click Add to add an ATM connection.

NOTE

l l

Modify the VPI and VCI or not, according to the ATM Service type. The Sink VPI value ranges from 0 to (2MaxVPIbits-1). The Sink VCI value ranges from 32 to (2MaxVCIbits-1). For example, the value of Max. VPI Bits for the ATM interface is 8 and the value of Max. VCI Bits is 7, the value of the sink VPI ranges from 0 to (28-1) (that is, 0 to 255) and the value of the sink VCI ranges from 32 to (27-1) (that is, 32 to 127). If Encapsulation Type is set n-to-one, you can add several ATM connections. You can proceed with the next operation only after selecting the uplink and downlink ATM policies of the ATM connection.

l l

4.

Click Next. The Create ATM Service dialog box is displayed. Configure the PW and set the parameters.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19-29

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

In the ATM service management interface, select QoS Policy and configure the QoS policy for the PW. If the QoS policy is not otherwise set, the default policy is adopted.

Step 6 Click Finish. The Operation Result window is displayed. Click Close. ----End

19.4.2 Modifying the ATM Service by Using the Trail Function

If the configuration information of an ATM service is inconsistent with that in the real network, modify the ATM service by using the trail function.

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

Context

CAUTION
This operation causes service interruption. Exercise caution when you perform this operation.
19-30 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Procedure
Step 1 Choose Trail > PTN Service > ATM Service Management from the Main Menu. Click Filter. Step 2 Select a created service and click the ATM Connection tab. In the tab, click Configure Connection to modify connection attributes of the service. Click OK. A dialog box is displayed, indicating that the operation affects services. Click OK. A dialog box is displayed, indicating that the operation is successful. Click Close. Step 3 Click the PW tab. In the tab, modify PW attributes of the service. Click Apply. A dialog box is displayed, indicating that the operation affects services. Click OK. A dialog box is displayed, indicating that the operation is successful. Click Close. Step 4 Select a created service and click the CoS Mapping tab. Modify the CoS mapping attributes of the service. Click OK. Click Apply. A dialog box is displayed, indicating that the operation affects services. Click OK. A dialog box is displayed, indicating that the operation is successful. Click Close. ----End

19.4.3 Deleting ATM Services in Trail Mode

If any ATM service channels are redundant, delete the ATM service channels to release resources. To fast delete an ATM service, fast delete the ATM service that contains information on the source and sink NEs on the T2000.

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

Context

CAUTION
This operation causes service interruption. Exercise caution when you perform this operation.

Procedure
Step 1 Choose Trail > PTN Service > ATM Service Management from the Main Menu. The Set Service Browse Filter Conditions dialog box is displayed. Step 2 Set filter criteria and click Filter. Step 3 Right-click the ATM service to be deleted and choose Delete from the shortcut menu. A dialog box is displayed indicating that deleting the trail causes service interruption. Click OK. Another dialog box is displayed indicating that deleting the trail is risky. Click OK. A dialog box is displayed telling you that the operation was successful. Click Close. ----End

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19-31

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

19.5 Configuring the ATM Service on a Per-NE Basis

You can configure an ATM PWE3 service path for transmitting ATM signals on a per-NE basis. When the ATM service is configured on a per-NE basis, the service attributes should be configured at the source end and sink end separately. In this way, a complete ATM service is configured. The configuration of the ATM services on a per-NE basis is of low efficiency, and thus the configuration on an end-to-end basis is recommended. 19.5.1 Creating ATM Services on a Per-NE Basis This section describes how to create an ATM PWE3 service channel that transports ATM signals on a per-NE basis. The per-NE basis means that, to configure a complete ATM service, you need to separately configure the service attributes at the source and sink ends of the service first. 19.5.2 Modifying ATM Services on a Per-NE Basis If the configuration information on an ATM service on the T2000 is inconsistent with that in the network, modify the ATM service on a per-NE basis. 19.5.3 Deleting ATM Services on a Per-NE Basis If any ATM service channels are redundant, delete the ATM service channels to release resources. To delete an ATM service on a per-NE basis, delete the ATM service specified at the source NE and sink NE.

19.5.1 Creating ATM Services on a Per-NE Basis

This section describes how to create an ATM PWE3 service channel that transports ATM signals on a per-NE basis. The per-NE basis means that, to configure a complete ATM service, you need to separately configure the service attributes at the source and sink ends of the service first.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. You must complete the configuration of the control plane. For configuration method, see 8 Configuring the Control Plane. If IMA services are accessed, you must complete the configuration of an IMA group. For configuration method, see Configuring the IMA. You must complete the configuration of the ATM policy. For configuration method, see 9.12.1 Creating the ATM Policy. You must complete the creation of a tunnel. For configuration method, see 13.4.2 Creating an MPLS Tunnel on a Per-NE Basis.

Context
The OptiX PTN equipment can access services at the E1/VC-12 level or 64K timeslot level. When the OptiX PTN equipment accesses the services at the E1/VC-12 level, all the available timeslots of the E1/VC-12 channels are used to transport services. When the OptiX PTN equipment accesses the services at the 64K timeslot level, one E1/VC-12 channel can be used to transport both the ATM services and CES services (certain timeslots allocated for ATM services and others for CES services). In this manner, the E1/VC-12 channels are used flexibly.

19-32

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > ATM Service Management from the Function Tree. Step 2 Click the Connection tab. Click New. The New ATM Service window is displayed. In the window, configure a UNIs-NNI or UNI-UNI service.

NOTE

l l

For the UNIs-NNI service, set the attributes in the Connection, PW and CoS Mapping tabs. For the UNI-UNI service, set only the attributes in the Connection tab.

Step 3 To create a UNI-UNI service, go to Step 4. To create a UNIs-NNI service, go to Step 5. Step 4 Optional: Create a UNI-UNI service. 1. Set ATM-related general attributes.
NOTE

Select UNI-UNI for the service type. For the connection type, select the following.
l l

PVP: Only the VPI value of the ATM connection can be modified. PVC: The VPI and VCI values of the ATM connection can be modified.

2.

Click the Connection tab and click Add. The Configure Connection window is displayed. In the window, set connection attributes.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-33

Issue 01 (2009-06-30)

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

The Sink VPI value ranges from 0 to (2MaxVPIbits-1). The Sink VCI value ranges from 32 to (2MaxVCIbits-1).

3. 1.

Click OK. Set ATM-related general attributes.

NOTE

Step 5 Optional: Create a UNIs-NNI service.

Select UNIs-NNI for the service type. For the connection type, select the following.
l l

PVP: Only the VPI value of the ATM connection can be modified. PVC: The VPI and VCI values of the ATM connection can be modified.

2.

Click the Connection tab and click Add. The Configure Connection window is displayed. In the window, set connection attributes.

19-34

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

3.

Click the PW tab and click Add. The Configure PW window is displayed. In the window, set attributes of the PW.

NOTE

OptiX PTN 912 only supports the ATM one-to-one VCC Cell Mode for PW Type.

4.

Click the General Attributes tab and set the general attributes of PW.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19-35

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

5. 6. 7.

Optional: Click the QoS tab and set the QoS attribute of PW. Optional: Click the Advanced Attributes tab and set the advanced attributes of PW. Click the CoS Mapping tab and click Add to configure the CoS mapping table.
NOTE

You can configure the CoS mapping only after configuring the parameters in the PW tab.

8.

Click OK.

Step 6 In the New ATM Service window, click OK. A dialog box is displayed, indicating that the operation is successful. Click Close. ----End

19.5.2 Modifying ATM Services on a Per-NE Basis

If the configuration information on an ATM service on the T2000 is inconsistent with that in the network, modify the ATM service on a per-NE basis.

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

Context

CAUTION
This operation causes service interruption. Exercise caution when you perform this operation.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > ATM Service Management from the Function Tree. Step 2 Select a created service and click the Connection tab. In the tab, click Configure Connection to modify connection attributes of the service. Click OK. A dialog box is displayed, indicating that the operation affects services. Click OK. A dialog box is displayed, indicating that the operation is successful. Click Close. Step 3 Click the PW tab. In the tab, modify PW attributes of the service. Click Apply. A dialog box is displayed, indicating that the operation affects services. Click OK. A dialog box is displayed, indicating that the operation is successful. Click Close.
NOTE

You can modify parameters only in the QoS and Advanced Attributes tabs of the PW, but not the parameters in the General Attributes tab.

Step 4 Select a created service and click the CoS Mapping tab. Modify the CoS mapping attributes of the service. Click OK. Click Apply. A dialog box is displayed, indicating that the operation affects services. Click OK. A dialog box is displayed, indicating that the operation is successful. Click Close. ----End
19-36 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

19.5.3 Deleting ATM Services on a Per-NE Basis

If any ATM service channels are redundant, delete the ATM service channels to release resources. To delete an ATM service on a per-NE basis, delete the ATM service specified at the source NE and sink NE.

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

Context

CAUTION
This operation causes service interruption. Exercise caution when you perform this operation.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > ATM Service Management from Function Tree. Step 2 Select a created service and click the Connection tab. In the tab, click Delete. A dialog box is displayed indicating that the operation affects services. Click OK. A dialog box is displayed telling you that the operation was successful. Click Close. ----End

19.6 Managing ATM Services

The ATM service management includes searching for, filtering, querying, and modifying an ATM service, and viewing alarms and performance events relevant to the ATM service. This management function provides network administrators a method to ensure the normal running of ATM services. 19.6.1 Searching for ATM Services On the T2000, search for ATM services in the network. The T2000 stores and displays information on found ATM services. 19.6.2 Filtering ATM Services Query ATM services according to certain conditions. On the T2000, information on ATM services that meet the conditions is displayed. 19.6.3 Querying Node Information of an ATM Service You can query node information of an ATM service. The node information includes node name, ports of the node, source and sink VPI and VCI labels, source and sink UPC and NPC, Uplink and downlink ATM Policy Name(ID), and Transit VPI and VCI. 19.6.4 Modifying a PW Carrying ATM Services If the information of the PW that carries ATM services on the T2000 is inconsistent with that in the network, you can modify the maximum concatenation cells, packet loading parameter, CAR parameter, and QoS policy.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-37

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

19.6.5 Browsing Alarms Related to an ATM Service Query alarms related to an ATM service to check whether the ATM service has any probable fault. 19.6.6 Browsing Performance Data Related to an ATM Service Query performance data related to an ATM service to check the running state of the ATM service.

19.6.1 Searching for ATM Services

On the T2000, search for ATM services in the network. The T2000 stores and displays information on found ATM services.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. You must complete the creation of an ATM service.

Procedure
Step 1 Choose Trail > PTN Service > PTN Service Search from the Main Menu. Step 2 In the Emulation Service Search window, select Search ATM and click Next to start the search. Click Finish.

NOTE

In the case of ATM trail search, the full search is performed. That is, during the search, all the ATM trail information at the network layer of the T2000 side, the related connections of each trail, and the PW information are deleted first. Then, the service configuration information on each NE is searched again, and ATM trails at the network layer of the T2000 side are formed.

----End
19-38 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

19.6.2 Filtering ATM Services

Query ATM services according to certain conditions. On the T2000, information on ATM services that meet the conditions is displayed.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. You must complete the creation of an ATM service.

Procedure
Step 1 Choose Trail > PTN Service > ATM Service Management from the Main Menu. The Set Service Browse Filter Conditions window is displayed. Step 2 Set filter conditions and click Filter. ATM services are then filtered according to these filter conditions. ----End

19.6.3 Querying Node Information of an ATM Service

You can query node information of an ATM service. The node information includes node name, ports of the node, source and sink VPI and VCI labels, source and sink UPC and NPC, Uplink and downlink ATM Policy Name(ID), and Transit VPI and VCI.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. An ATM service must be created.

Procedure
Step 1 Choose Trail > PTN Service > ATM Service Management from the Main Menu. Click Filter. Step 2 Select an ATM service and observe node information of the ATM service.

----End

19.6.4 Modifying a PW Carrying ATM Services

If the information of the PW that carries ATM services on the T2000 is inconsistent with that in the network, you can modify the maximum concatenation cells, packet loading parameter, CAR parameter, and QoS policy.

Prerequisite
You must be an NM user with "NE operator" authority or higher.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-39

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 Choose Trail > PTN Service > ATM Service Management from the Main Menu. Click Filter. Step 2 Select an ATM service and click the PW tab. In the tab, modify information on the PW that carries the ATM service. ----End

19.6.5 Browsing Alarms Related to an ATM Service

Query alarms related to an ATM service to check whether the ATM service has any probable fault.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. You must complete the creation of an ATM service.

Procedure
Step 1 Choose Trail > PTN Service > ATM Service Management from the Main Menu. Click Filter. Step 2 Select one ATM service. Click Alarm. Select Current Alarm or History Alarm to query alarms related to the ATM service. ----End

19.6.6 Browsing Performance Data Related to an ATM Service

Query performance data related to an ATM service to check the running state of the ATM service.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. You must complete the creation of an ATM service.

Procedure
Step 1 Choose Trail > PTN Service > ATM Service Management from the Main Menu. Click Filter. Step 2 Select an ATM service. Click Performance to query performance data related to the ATM service. ----End

19.7 IMA Configuration Example

A case is provided here to show the IMA networking application and the details on how to configure the IMA.

19-40

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

19.7.1 Case Description This topic describes the application scenario and networking diagram of IMA based on an example of the PTN equipment accessing two IMA links. 19.7.2 Service Planning Before the service creation, the service planning designs the details of the service, which is used for guiding the service configuration. 19.7.3 Configuration Procedure This topic describes the configuration procedure of the ATM IMA group attributes by using an example.

19.7.1 Case Description

This topic describes the application scenario and networking diagram of IMA based on an example of the PTN equipment accessing two IMA links. As shown in Figure 19-9, NE1 uses the OptiX PTN 1900 to access Node B. Node B provides two IMA links, that is, IMA1 and IMA2. IMA1 is bound with three E1 links, which are used for transmitting audio services. IMA2 is bound with two E1 links, which are used for transmitting Internet access services. IMA1 is connected to ports 1 to 3 of the interface board L75. IMA2 is connected to ports 11 to 12 of the interface board L75. Figure 19-9 Networking diagram of the IMA service
1-CXP-1-MD1-3-L75 IMA 1

IMA 2 Node B NE1

E1 Link

19.7.2 Service Planning

Before the service creation, the service planning designs the details of the service, which is used for guiding the service configuration. According to engineering requirements, the engineering department makes engineering planning and then outputs the detailed planning information. The service shown in Figure 19-9 is taken as an example. Table 19-7 lists the configuration parameters of IMA1, and Table 19-8 lists the configuration parameters of IMA2. Table 19-7 Configuration parameters of IMA1 Attribute Binding
Issue 01 (2009-06-30)

Value Binding Path Level E1

19-41

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Attribute Configurable Ports Available Resources IMA Group Management IMA Protocol Version IMA Transmit Frame Length IMA Symmetry Mode Maximum Delay Between Links (ms) Minimum Number of Active Transmitting Links Minimum Number of Active Receiving Links IMA Protocol Enable Status ATM Interface Management Port Type Min. VPI Max. VPI Min. VCI Max. VCI VCC-Supported VPI Count

Value 1-CXP-1-MD1-1(Trunk-1) 3-L75-2(Port-2), 3-L75-3(Port-3), 3L75-4(Port-4) Consistent with that of Node B Consistent with that of Node B Consistent with that of Node B Consistent with that of Node B Consistent with that of Node B

Consistent with that of Node B Enable UNI 255(properly set according to the parameters of Node B) 127 (properly set according to the parameters of Node B) 32 (properly set according to the parameters of Node B)

Table 19-8 Configuration parameters of IMA2 Attribute Binding Binding Path Level Configurable Ports Available Resources IMA Group Management IMA Protocol Version IMA Transmit Frame Length Value E1 1-CXP-1-MD1-2(Trunk-2) 3-L75-11(Port-11), 3-L75-12Port-12) Consistent with that of Node B Consistent with that of Node B

19-42

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Attribute IMA Symmetry Mode Maximum Delay Between Links (ms) Minimum Number of Active Transmitting Links Minimum Number of Active Receiving Links IMA Protocol Enable Status ATM Interface Management Port Type Min. VPI Max. VPI Min. VCI Max. VCI VCC-Supported VPI Count

Value Consistent with that of Node B Consistent with that of Node B Consistent with that of Node B

Consistent with that of Node B Enable UNI 255 (properly set according to the parameters of Node B) 127 (properly set according to the parameters of Node B) 32 (properly set according to the parameters of Node B)

19.7.3 Configuration Procedure

This topic describes the configuration procedure of the ATM IMA group attributes by using an example.

Prerequisite
You must understand the networking, requirements and service planning of the example.

Procedure
Step 1 Configure the user-side port on NE1. 1. 2. In the NE Explorer, select NE1 and choose Configuration > Interface Management > PDH Interface from the Function Tree. Click General Attributes. Set the parameters for five ports, which are 3-L75-2(Port-2), 3L75-3(Port-3), 3-L75-4(Port-4), 3-L75-11(Port-11), and 3-L75-12(Port-12).

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19-43

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

The relevant parameters for each port are as follows:

l l l

Port Mode: Layer 2 (carrying IMA signals) Encapsulation Type: ATM Channelize: No

3. 1. 2.

Click Apply. In the NE Explorer, select NE1 and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Choose Binding and click Configuration. The Bound Path dialog box is displayed.

Step 2 Configure the bound paths in the ATM IMA group on NE1.

3.

Configure the bound path in the IMA 1 and IMA 2. Click Apply. For the bound path in the IMA 1, set the following parameters:
l l l l l

Available Board: 1-CXP Configurable Ports: 1-CXP-1-MD1-1(Trunk-1) Bound Path Level: E1 Direction: Bidirectional (default) Optical Interface: - (Select E1 for ATM E1 boards. Select VC12-xv for ATM STM-1 boards. ATM E1 boards are used in this example. Configurable Ports: 1-CXP-1-MD1-1(Trunk-1). Available Resources: 3-L75-2(Port-2), 3-L75-3(Port-3), 4-L75-4(Port-4)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

l l

19-44

OptiX iManager T2000 Operation Guide for PTN NE Management

l

19 Configuring an ATM Service

Available Timeslots: - (In the case of the E1 level, you need not set this parameter. In the case of the VC12-xv level, you need to select the corresponding timeslot.)

For the bound path in the IMA 2, set the following parameters:
l l l l l

Available Board: 1-CXP Configurable Ports: 1-CXP-1-MD1-2(Trunk-2) Bound Path Level: E1 Direction: Bidirectional (default) Optical Interface: - (Select E1 for ATM E1 boards. Select VC12-xv for ATM STM-1 boards. ATM E1 boards are used in this example. Configurable Ports: 1-CXP-1-MD1-2(Trunk-2). Available Resources: 3-L75-11(Port-11), 3-L75-12(Port-12) Available Timeslots: - (In the case of the E1 level, you need not set this parameter. In the case of the VC12-xv level, you need to select the corresponding timeslot.)

l l l

Step 3 Click IMA Group Management. Set the attributes of the ATM IMA group on NE1. Click Apply.

You need to configure the attributes of the 1-CXP-1-MD1-1(Trunk-1) and 1-CXP-1-MD1-2 (Trunk-2) in the IMA 1 as follows:
l l

IMA Protocol Enable Status is set as Enabled. The settings of IMA Protocol Version, IMA Transmit Frame Length, IMA Symmetry Mode, Maximum Delay Between Links (ms), Minimum Number of Active Transmitting Links and Minimum Number of Active Receiving Links need to be consistent with those on the Node B side.

Step 4 Click ATM Interface Management. Set the management parameters for the ATM interface on NE1. Click Apply.

You need to configure the port attributes of the 1-CXP-1-MD1-1(Trunk-1) and 1-CXP-1-MD1-2 (Trunk-2) in the IMA 1 as follows:
l

Port Type: UNI (The interface of the UNI type is used to connect to the client-side equipment, and the interface of the NNI type is used to connect the ATM equipment on the network.) Min. VPI: Max. VPI: 255 (Set the parameter based on the networking planning. The value of VPI is between 0 and 255.) Min. VCI: Max. VCI: 127 (Set the parameter based on the networking planning. The value of VCI is between 0 and 127.) VCC-Supported VPI Count: 32 (Set the parameter based on the networking planning.)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-45

l l

l l

Issue 01 (2009-06-30)

19 Configuring an ATM Service

l

OptiX iManager T2000 Operation Guide for PTN NE Management

Loopback: No Loopback

----End

19.8 Configuration Case of the UNI-UNI ATM Service

This section describes a configuration case of the UNI-UNI ATM service. The configuration flow diagram is provided to describe the configuration process. The configuration case includes service planning and ATM service configuration. 19.8.1 Networking Diagram This section describes the networking diagram for the case where the R99 service, Signalling service and HSDPA service are transported between Node B and RNC. 19.8.2 Service Planning To transport the R99 and HSDPA services between NodeB and RNC, three ATM connections should be created. 19.8.3 Configuring an ATM Service on a Route Basis This section describes the process of configuring a UNI-UNI ATM service on a route basis. 19.8.4 Configuring an ATM Service on a Per-NE Basis This section describes the process of configuring a UNI-UNI ATM service on a per-NE basis. 19.8.5 Verifying Correctness of Service Configuration After configuring an ATM service, you need to verify the correctness of service configuration, to ensure that the service is correctly configured. You can use the ATM OAM to perform the verification.

19.8.1 Networking Diagram

This section describes the networking diagram for the case where the R99 service, Signalling service and HSDPA service are transported between Node B and RNC. Figure 19-10 shows the networking diagram of the UNI-UNI ATM service. The ATM service is required between Node B and RNC. Connection 1 is used for transmitting R99 services, Connection 2 is used for transmitting HSDPA services, and Connection 3 is used for transmitting Signalling services. Node B transmits services to RNC through NE1. NE1 uses the OptiX PTN 3900 to access the services from the base station, and NE1 transmits services to RNC through STM-1. Figure 19-10 Networking of the ATM service

UNI
Connection 1 Connection 2 Connection 3 R99 HSDPA
Signalling

UNI
VPI 70 71 72 VCI 32 32 32

VPI 1 1 1 IMA 1

VCI 100 101 102

STM-1

Node B
19-46

NE 1

RNC
Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Figure 19-11 shows the NE planning diagram. Figure 19-11 NE planning diagram
UNI UNI

1-MP1-MD1-19-D75

2-MP1-AD1 STM-1 NE 1 RNC

Node B

IMA 1

19.8.2 Service Planning

To transport the R99 and HSDPA services between NodeB and RNC, three ATM connections should be created. Node B accesses the ATM service through IMA1, and then transmits the service to RNC. three services that are connected to the N:1 VCC service should be created. Figure 19-10 shows the VPI/VCI switching. The service shown in Figure 19-10 is taken as an example. Table 19-9 lists the configuration parameters of NE1. Table 19-9 Configuration parameters of NE1 Attribute Base Station of Service IMA Group Port Accessing the IMA Group at NodeB Port Connected to RNC Connectio n1 Connectio n2 Connectio n3 Source VPI/VCI Sink VPI/VCI Source VPI/VCI Sink VPI/VCI Source VPI/VCI Sink VPI/VCI Remarks NodeB IMA1 NE1-1-MP1-1-MD1-1(Trunk1) NE1-2-MP1-1-AD1-1(1-AD1.PORT-1) 1/100 70/32 1/101 71/32 1/102 72/32

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19-47

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Table 19-10 lists the configuration parameters of Qos. Table 19-10 Service types and QoS requirements Application Scenario Audio service, which is carried by the RT-VBR type. ATM Policy PW Bandwidth Tunnel Bandwidt h 30M bit/s

l l l l

Policy ID: 1 Policy name: RT-VBR Service type: RT-VBR Traffic type: ClpNoTaggingScrCdvt Clp01Pcr(cell/s): 4000 Clp0Scr(cell/s): 1000 MBS(cell): 100 CDVT(us): 10000 Enable Traffic Frame Discarding Flag: Disable UPC/NPC: Enabled Policy ID: 2 Policy name: CBR Service type: CBR Traffic type: NoClpNoScr Clp01Pcr(cell/s): 800 Enable Traffic Frame Discarding Flag: Disable UPC/NPC: Enabled Policy ID: 3 Policy name: UBR Service type: UBR Traffic type: NoTrafficDescriptor Enable Traffic Frame Discarding Flag: Disable UPC/NPC: Disabled

Bandwidth: 4 Mbit/s

l l l l l

Signal service, which is carried by the CBR type.

l l l l l l

Bandwidth: 1 Mbit/s

Data service, which is carried by the UBR type.

l l l l

Bandwidth: 15 Mbit/s

19.8.3 Configuring an ATM Service on a Route Basis

This section describes the process of configuring a UNI-UNI ATM service on a route basis.

19-48

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must understand the networking, requirements and service planning of the example. A network must be created.

Procedure
Step 1 Configure three ATM policies: CBR, RT-VBR, UBR. 1. 2. 3. 1. Configure the CBR policy, refer to QoS Configuration Case of the ATM Service . Configure the RT-VBR policy, refer to QoS Configuration Case of the ATM Service . Configure the UBR policy, refer to QoS Configuration Case of the ATM Service . Configure the NodeB-side ATM interface. a. In the NE Explorer, select NE1 and choose Configuration > Interface Management > PDH Interface from the Function Tree. Then, configure the NodeBside interface. Select 19-D75-3(Port-3) and 19-D75-4(Port-4). Right click the Port Mode field, and select Layer 2. Set the parameters as required, and click Apply.
NOTE

Step 2 Configure ATM interface: NodeB-side ATM interface and RNC-side ATM interface.

b.

Before setting the port mode, make sure that the port DCN is disabled.

The configuration parameters are as follows:

l l

Port: 19-D75-3(Port-3), 19-D75-4(Port-4) Name: NodeB ATM (Set the port name as required. The port name distinguishes the port from other ports and helps to query the port.) Port Mode: Layer 2 (The port transmits IMA signals.) Encapsulation: ATM

l l

c.

In the Advanced Attributes tab, set the Frame Format, Frame Mode of the 19D75-3(Port-3) and 19-D75-4(Port-4). Click Apply. The configuration parameters are as follows:
l l

Port: 19-D75-3(Port-3) and 19-D75-4(Port-4) Frame Format: CRC-4 Multiframe (Set the Frame Format as the same as the parameter of NodeB.) Frame Mode: 31

d. e.

Choose Configuration > Interface Management > ATM IMA Management from Function Tree, and click the Binding tab. In the Binding tab, click Configuration and set the parameters such as Available Boards, Configuration Ports. Then, click OK.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19-49

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

The configuration parameters are as follows:

l l

Available Boards: 1-MP1 (Set this parameter according to networking planning.) Configuration Ports: 1-MP1-1-MD1-1(Trunk-1) (Set this parameter according to networking planning.) Available Bound Paths Level: E1 (Select E1 for an ATM E1 board and VC12-xv for an ATM STM-1 board. Herein, the board is an ATM E1 board.) Direction: Bidirectional (Default) Optical Interface: - (This parameter need not be set for E1, but need be set for VC12-xv. Herein, the path level is E1.) Available Resources: 19-D75-3(Port-3), 19-D75-4(Port-4) Available Timeslots: - (This parameter need not be set for E1, but need be set for VC12-xv.)

l l

l l

f.

In the IMA Group Management tab, double-click the IMA Protocol Enable Status field and select Enabled. Set the other parameters as required. Then, click Apply.

The configuration parameters are as follows: Set the IMA Protocol Version, IMA Transmit Frame Length, IMA Symmetry Mode, Maximum Delay Between Links, Minimum Number of Active Transmitting Links, and Minimum Number of Active Receiving Links parameters as the same as these parameters of NodeB. g. In the ATM Interface Management tab, set the parameters such as Max. VPI Bits and Max. VCI Bits for the interface. Then, click Apply. The configuration parameters are as follows:
l

Port Type: UNI (A UNI interface is connected to the client equipment and an NNI interface is connected to ATM equipment in the core network.) ATM Cell Payload Scrambling: Enabled
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

19-50

OptiX iManager T2000 Operation Guide for PTN NE Management

l

19 Configuring an ATM Service

Max. VPI Bits: 8 (Set this parameter according to networking planning. Set Max. VPI Bits to specify the value range of VPI. The VPI ranges from 0 to 2MaxVPIbits-1.) Max. VCI Bits: 7 (Set this parameter according to networking planning. Set Max. VCI Bits to specify the value range of VCI. The VCI ranges from 0 to 2MaxVCIbits-1.) VCC-Supported VPI Count: 32 (Set this parameter according to networking planning.) Loopback: Non-Loopback

2.

Configure the RNC-side ATM interface. a. In the NE Explorer, select NE1 and choose Configuration > Interface Management > SDH Interface from the Function Tree. Configure the RNC-side interface. In the Layer 2 Attributes tab, select 2-MP1-1-AD1-1(1-AD1.PORT-1), and set the parameters such as Max. VPI Bits and Max. VCI Bits for the interface. Then, click Apply. The configuration parameters are as follows:
l l l l l

b.

Port Type: UNI ATM Cell Payload Scrambling: Enabled Max.VPI Bits: 8 Max.VCI Bits: 7 VCC-Supported VPI Count: 32

Step 3 Create a UNI-UNI ATM service, add three connections. 1. 2. Choose Trail > PTN Service > ATM Service Creation from the Main Menu. In the displayed Create ATM Service dialog box, set the parameters such as Service ID, Service Name, Connection Type, Source NE, and Sink NE. The configuration parameters are as follows:
l l l

Service ID: 10 Service Name: ATMService-10 Connection Type: PVC (PVC indicates that the VPI and VCI of the ATM connection can be modified; PVP indicates that only the VPI of the ATM connection can be modified.) Source NE: NE1 Source Port: 1-MP1-1-MD1-Trunk1 Sink NE: NE1 Sink Port: 2-MP1-1-AD1-1(Port-1)

l l l l

3.

In the Create ATM Service, click Add to add connections. Set the parameters as needed, and click Finish to complete the service configuration.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19-51

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

The configuration parameters are as follows:

l

Connection 1

Name: Connection 1 Source Port: NE1-1-MP1-1-MD1-Trunk1 Source VPI: 1 (the VPI information transmitted with the service from NodeB) Source VCI: 100 (the VCI information transmitted with the service from NodeB) Sink Port: NE1-2-MP1-1-AD1-1(Port-1) Sink VPI: 70 (The VPI information transmitted with the service after VPI switching. The Sink VPI ranges from 0 to 2MaxVPIbits-1.) Sink VCI: 32 (The VCI information transmitted with the service after VCI switching. The Sink VCI ranges from 0 to 2MaxVCIbits-1.) Uplink ATM Policy Name(ID): RT-VBR (Select the RT-VBR policy, because connection 1 is an R99 service.) Downlink ATM Policy Name(ID): RT-VBR (Select the RT-VBR policy, because connection 1 is an R99 service.) Transit VPI: Transit VCI: -

Connection 2
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

19-52

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Name: Connection 2 Source Port: NE1-1-MP1-1-MD1-Trunk1 Source VPI: 1 Source VCI: 101 Sink Port: NE1-2-MP1-1-AD1-1(Port-1) Sink VPI: 71 Sink VCI: 32 Uplink ATM Policy Name(ID): UBR (policy) (Select the UBR policy, because connection 2 is an HSDPA service.) Downlink ATM Policy Name(ID): UBR (policy)(Select the UBR policy, because connection 2 is an HSDPA service.) Transit VPI: Transit VCI: Source Port: NE1-1-MP1-1-MD1-Trunk1 Source VPI: 1 Source VCI: 102 Sink Port: NE1-2-MP1-1-AD1-1(Port-1) Sink VPI: 72 Sink VCI: 32 Uplink ATM Policy Name(ID): CBR (policy) (Select the CBR policy, because connection 3 is a signalling service.) Downlink ATM Policy Name(ID): CBR (policy) (Select the CBR policy, because connection 3 is a signalling service.) Transit VPI: Transit VCI: -

Connection 3

----End

19.8.4 Configuring an ATM Service on a Per-NE Basis

This section describes the process of configuring a UNI-UNI ATM service on a per-NE basis.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must understand the networking, requirements and service planning of the example. A network must be created.

Procedure
Step 1 Configure three ATM policies: CBR, RT-VBR, UBR. 1.
Issue 01 (2009-06-30)

Configure the CBR policy, refer to QoS Configuration Case of the ATM Service .
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-53

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

2. 3.

Configure the RT-VBR policy, refer to QoS Configuration Case of the ATM Service . Configure the UBR policy, refer to QoS Configuration Case of the ATM Service .

Step 2 Configure ATM interface: NodeB-side ATM interface and RNC-side ATM interface. 1. Configure the NodeB-side ATM interface. a. In the NE Explorer, select NE1 and choose Configuration > Interface Management > PDH Interface from the Function Tree. Then, configure the NodeBside interface. Select 19-D75-3(Port-3) and 19-D75-4(Port-4). Right click the Port Mode field, and select Layer 2. Set the parameters as required, and click Apply.
NOTE

b.

Before setting the port mode, make sure that the port DCN is disabled.

The configuration parameters are as follows:

l l

Port: 19-D75-3(Port-3), 19-D75-4(Port-4) Name: NodeB ATM (Set the port name as required. The port name distinguishes the port from other ports and helps to query the port.) Port Mode: Layer 2 (The port transmits IMA signals.) Encapsulation: ATM

l l

c.

In the Advanced Attributes tab, set the Frame Format, Frame Mode of the 19D75-3(Port-3) and 19-D75-4(Port-4). Click Apply. The configuration parameters are as follows:
l l

Port: 19-D75-3(Port-3) and 19-D75-4(Port-4) Frame Format: CRC-4 Multiframe (Set the Frame Format as the same as the parameter of NodeB.) Frame Mode: 31

d. e.

Choose Configuration > Interface Management > ATM IMA Management from Function Tree, and click the Binding tab. In the Binding tab, click Configuration and set the parameters such as Available Boards, Configuration Ports. Then, click OK.

The configuration parameters are as follows:

19-54 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

l l l l l l l

19 Configuring an ATM Service

Available Boards: 1-MP1 (Set this parameter according to networking planning.) Configuration Ports: 1-MP1-1-MD1-1(Trunk-1) (Set this parameter according to networking planning.) Available Bound Paths Level: E1 (Select E1 for an ATM E1 board and VC12-xv for an ATM STM-1 board. Herein, the board is an ATM E1 board.) Direction: Bidirectional (Default) Optical Interface: - (This parameter need not be set for E1, but need be set for VC12-xv. Herein, the path level is E1.) Available Resources: 19-D75-3(Port-3), 19-D75-4(Port-4) Available Timeslots: - (This parameter need not be set for E1, but need be set for VC12-xv.)

f.

In the IMA Group Management tab, double-click the IMA Protocol Enable Status field and select Enabled. Set the other parameters as required. Then, click Apply.

The configuration parameters are as follows: Set the IMA Protocol Version, IMA Transmit Frame Length, IMA Symmetry Mode, Maximum Delay Between Links, Minimum Number of Active Transmitting Links, and Minimum Number of Active Receiving Links parameters as the same as these parameters of NodeB. g. In the ATM Interface Management tab, set the parameters such as Max. VPI Bits and Max. VCI Bits for the interface. Then, click Apply. The configuration parameters are as follows:
l l l

Port Type: UNI (A UNI interface is connected to the client equipment and an NNI interface is connected to ATM equipment in the core network.) ATM Cell Payload Scrambling: Enabled Max. VPI Bits: 8 (Set this parameter according to networking planning. Set Max. VPI Bits to specify the value range of VPI. The VPI ranges from 0 to 2MaxVPIbits-1.) Max. VCI Bits: 7 (Set this parameter according to networking planning. Set Max. VCI Bits to specify the value range of VCI. The VCI ranges from 0 to 2MaxVCIbits-1.) VCC-Supported VPI Count: 32 (Set this parameter according to networking planning.) Loopback: Non-Loopback

l l

2.

Configure the RNC-side ATM interface. a. In the NE Explorer, select NE1 and choose Configuration > Interface Management > SDH Interface from the Function Tree. Configure the RNC-side interface. In the Layer 2 Attributes tab, select 2-MP1-1-AD1-1(1-AD1.PORT-1), and set the parameters such as Max. VPI Bits and Max. VCI Bits for the interface. Then, click Apply.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-55

b.

Issue 01 (2009-06-30)

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

The configuration parameters are as follows:

l l l l l

Port Type: UNI ATM Cell Payload Scrambling: Enabled Max.VPI Bits: 8 Max.VCI Bits: 7 VCC-Supported VPI Count: 32

Step 3 Configure a UNI-UNI ATM service. 1. 2. Choose Configuration > ATM Service Management from the Function Tree. In the Connection tab, click New. The New ATM Service window is displayed. In the window, configure a UNI-UNI service. The configuration parameters are as follows:
l l l l

Service ID: 10 Service Name: ATMService-10 Service Type: UNI-UNI Connection Type: PVC (PVC indicates that the VPI and VCI of the ATM connection can be modified; PVP indicates that only the VPI of the ATM connection can be modified.)

3.

Click the Connection tab and click Add to add connection 1 and connection 2. Then, click OK.

The configuration parameters are as follows:

l

Connection 1

Connection Name: Connection 1 Source Board: 1-MP1

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

19-56

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Source Port: 1-MD1-1(Trunk1) Source VPI: 1 (the VPI information transmitted with the service from NodeB) Source VCI: 100 (the VCI information transmitted with the service from NodeB) PW ID: Sink Board: 2-MP1 Sink Port: 1-AD1-1(Port-1) Sink VPI: 70 (The VPI information transmitted with the service after VPI switching. The Sink VPI ranges from 0 to 2MaxVPIbits-1.) Sink VCI: 32 (The VCI information transmitted with the service after VCI switching. The Sink VCI ranges from 0 to 2MaxVCIbits-1.) Uplink Policy: RT-VBR (Select the RT-VBR policy, because connection 1 is an R99 service.) Downlink Policy: RT-VBR (Select the RT-VBR policy, because connection 1 is an R99 service.) Connection Name: Connection 2 Source Board: 1-MP1 Source Port: 1-MD1-1(Trunk1) Source VPI: 1 Source VCI: 101 PW ID: Sink Board: 2-MP1 Sink Port: 1-AD1-1(Port-1) Sink VPI: 71 Sink VCI: 32 Uplink Policy: UBR (policy) (Select the UBR policy, because connection 2 is an HSDPA service.) Downlink Policy: UBR (policy) (Select the UBR policy, because connection 2 is an HSDPA service.) Source Board: 1-MP1 Source Port: 1-MD1-1(Trunk1) Source VPI: 1 Source VCI: 102 PW ID: Sink Board: 2-MP1 Sink Port: 1-AD1-1(Port-1) Sink VPI: 72 Sink VCI: 32
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-57

Connection 2

Connection 3

Issue 01 (2009-06-30)

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Uplink Policy: CBR (Select the CBR policy, because connection 2 is a signalling service.) Downlink Policy: CBR (Select the CBR policy, because connection 2 is a signalling service.)

----End

19.8.5 Verifying Correctness of Service Configuration

After configuring an ATM service, you need to verify the correctness of service configuration, to ensure that the service is correctly configured. You can use the ATM OAM to perform the verification.

Context
To verify the correctness of service configuration, you need to configure the ATM OAM. See Figure 19-12. A UNI-UNI ATM service is created between the base station and RNC. The service type is 1:1 VC exchange. The source VPI/VCI is 32/33, and the sink VPI/VCI is 52/53. The OptiX PTN 3900 is used on NE1. Figure 19-12 ATM OAM
UNI UNI

1-MP1-MD1-19-D75

2-MP1-AD1 STM-1 NE 1 RNC

Node B

IMA 1

Procedure
Step 1 On the T2000, configure the segment and end attribute of NE1. For details, refer to 25.5.4 Setting Segment End Attribute. Configure related parameters for the segment and end attribute of NE1:
l l l l

Source: 1-MP1-1-MD1-1(Trunk1)-32-33 Sink: 2-MP1-1-AD1-1 (1-AD1.PORT-1)-52-53 Connection Direction: Forward Segment and End Attribute: Segment Point

Step 2 On the T2000, configure the CC activation status of NE1. For details, refer to 25.5.5 Setting the CC Activation Status. Configure related parameters for the CC activation status of NE1:
l

Source: 1-MP1-1-MD1-1(Trunk1)-32-33
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

19-58

OptiX iManager T2000 Operation Guide for PTN NE Management

l l l l

19 Configuring an ATM Service

Sink: 2-MP1-1-AD1-1 (1-AD1.PORT-1)-52-53 Connection Direction: Forward Segment and End Attribute: Segment Point CC Activate Flag: Source activate

----End

19.9 Configuration Case of the UNIs-NNI ATM Service

This section describes a configuration case of the UNIs-NNI ATM service. The configuration flow diagram is provided to describe the configuration process. The configuration case includes service planning and ATM service configuration. 19.9.1 Networking Diagram This section describes the networking diagram for the case where the R99 service, Signalling service and HSDPA service are transported between NodeB1 and RNC, NodeB2 and RNC. 19.9.2 Service Planning To transport the R99, Signalling and HSDPA services between NodeB1 and RNC, NodeB2 and RNC respectively, three ATM services must be created. 19.9.3 Configuring an ATM Service on a Route Basis This section describes the process of configuring a UNIs-NNI ATM service on a route basis. 19.9.4 Configuring an ATM Service on a Per-NE Basis This section describes the process of configuring a UNIs-NNI ATM service on a per-NE basis. 19.9.5 Verifying the Correctness of Service Configuration After the ATM service is configured, the correctness of service configuration should be verified. The ATM OAM is used for verifying the correctness of the ATM service configuration.

19.9.1 Networking Diagram

This section describes the networking diagram for the case where the R99 service, Signalling service and HSDPA service are transported between NodeB1 and RNC, NodeB2 and RNC. Figure 19-13 shows the networking diagram of the UNIs-NNI ATM service. The 3G R99, signalling and HSDPA services are required between the two base stations and RNC. NE1 accesses the MPLS network formed by the PTN equipment. Node B1 is connected to NE1 through IMA1, and Node B2 is connected to NE1 through IMA2. The VPI/VCI switching is performed on NE1, and the VPI/VCI transparent transmission is performed on NE2 and NE3. Between NE1 and NE3, three PWs are used to carry the R99, signalling and HSDPA services respectively. At the remote end, to transparently transmit the ATM service in the MPLS network, NE3 is connected to RNC through STM-1. NE1 is an OptiX PTN 1900 NE, and NE2, NE3, NE4, NE5 are OptiX PTN 3900s, and NE6 is an OptiX PTN 950. The ATM services are carried by the working tunnel. The protection tunnel can be created to protect the services that have high real-time requirement. The working tunnel is NE1-NE2-NE3, and the protection tunnel is NE1-NE6-NE5-NE4-NE3.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19-59

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 19-13 Networking of the ATM service

NE4 NE5 10GE ring on NE6

GE ring on access layer

NE1 IMA1 pw1 pw2 pw3 IMA2 NE2

convergence layer

NE3 ATM STM-1

RNC
Working Tunnel

NodeB 1

NodeB 2

PW Protection Tunnel

UNI
IMA1:
Connection1 Connection2 Connection3 R99 HSDPA Signalling VPI 1 1 1 VCI 100 101 102

NNI
VPI 50 51 52 VCI 32 32 32

NNI
VPI 50 51 52 VCI 32 32 32

UNI
VPI 50 51 52 VCI 32 32 32

UNI
Connection1

NNI
VCI 100 101 102 VPI 60 61 62 VCI 32 32 32

NNI
VPI 60 61 62 VCI 32 32 32

UNI
VPI 60 61 62 VCI 32 32 32

IMA2:

Connection2 Connection3

R99 HSDPA Signalling

VPI 1 1 1

Figure 19-14 shows the NE planning diagram. Figure 19-14 NE planning diagram
3-EG16-1(Port-1) 10.0.4.2 1-EX2-1(Port-1) 10.0.3.2 1-EX2-2(Port-2) 10.0.3.1 1-EX2-1(Port-1) 10.0.2.2

NE5
2-EG2-2(Port-2) 10.0.4.1

NE6

GE ring on access layer NE1

3-EG16-1(Port-1) 10.0.0.2

NE4 10GE ring on convergence layer

1-EX2-1(Port-1) 10.0.1.2 1-EX2-2(Port-2) 10.0.2.1

NE2
4-EFG2-1(Port-1) 10.0.0.1

1-EX2-1(Port-1) 10.0.1.1

NE3

3-MP1-AD1

4-EFG2-2(Port-2) 10.0.5.1

1-CXP-MD1-3-L12

RNC
Working tunnel Protection tunnel

NodeB 1 NodeB 2

19.9.2 Service Planning

To transport the R99, Signalling and HSDPA services between NodeB1 and RNC, NodeB2 and RNC respectively, three ATM services must be created. Between NE1 and NE3, the R99 service is carried by PW1, the HSDPA service is carried by PW2, and the Signalling service is carried by PW3. Thus, three ATM services should be created.
19-60 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

At the two base stations, the R99 service is aggregated and the Signalling service and HSDPA service is accessed. Thus, two ATM services connected to the N:1 VCC should be created. The service shown in Figure 19-13 is taken as an example. Table 19-11 lists the configuration parameters of NE1. Table 19-11 Configuration parameters of NEs NE NE1 LSR ID 1.0.0.1 Port 4-EFG2-1(Port-1) 4-EFG2-2(Port-2) 3-EG16-1(Port-1) 1-EX2-1(Port-1) 1-EX2-1(Port-1) 1-EX2-2(Port-2) 1-EX2-1(Port-1) 1-EX2-2(Port-2) 1-EX2-1(Port-1) 3-EG16-1(Port-1) 4-EFG2-1(Port-1) 4-EFG2-2(Port-2) Port IP Address 10.0.0.1 10.0.5.1 10.0.0.2 10.0.1.1 10.0.1.2 10.0.2.1 10.0.2.2 10.0.3.1 10.0.3.2 10.0.4.2 10.0.5.2 10.0.4.1 IP Mask 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.252

NE2

1.0.0.2

NE3

1.0.0.3

NE4

1.0.0.4

NE5

1.0.0.5

NE6

1.0.0.6

Table 19-12 Planning of Tunnel parameters Parameters Tunnel ID Name 100 Working TunnelPositive Dynamic E-LSP No Limit NE1 NE3 Working Tunnel 101 Working TunnelReverse Dynamic E-LSP No Limit 120 Protection Tunnel-Positive Dynamic E-LSP No Limit NE1 NE3 Protection Tunnel 121 Protection Tunnel-Reverse Dynamic E-LSP No Limit

Signal Type Scheduling Type Bandwith (kbit/s) Source Node Sink Node

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19-61

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Parameters Route Constraint Port IP Address

Working Tunnel IP addresses of ingress port of NE2: 3-EG16-1 (Port-1) 10.0.0.2 IP addresses of ingress port of NE3: 1-EX2-1 (Port-1) 10.0.1.2 IP addresses of ingress port of NE2: 1-EX2-2 (Port-2) 10.1.2.2 IP addresses of ingress port of NE1: 4-EFG2-1 (Port-1) 10.1.1.2

Protection Tunnel IP addresses of ingress port of NE6: 2-EG2-1 (Port-1) 10.0.5.2 IP addresses of ingress port of NE5: 3-EG16-1 (Port-1) 10.0.4.2 IP addresses of ingress port of NE4: 1-EX2-2 (Port-2) 10.0.3.1 IP addresses of ingress port of NE3: 1-EX2-2 (Port-2) 10.0.2.1 IP addresses of ingress port of NE4: 1-EX2-1 (Port-1) 10.0.2.2 IP addresses of ingress port of NE5: 1-EX2-2 (Port-2) 10.0.3.2 IP addresses of ingress port of NE6: 2-EG2-2 (Port-2) 10.0.4.1 IP addresses of ingress port of NE1: 4-EFG2-2 (Port-2) 10.0.5.1

Table 19-13 Configuration parameters of NE1 Attribute Base Station of Service IMA Group Source Port Service Source VPI/VCI Sink VPI/ VCI PW of Service PW ID Remarks NodeB1 NodeB2

IMA1 1-CXP-1-MD1-1(Trunk1) R99 1/100 50/32 PW1 35 HSDPA 1/101 51/32 PW2 36 Signalling 1/102 52/32 PW3 37

IMA2 1-CXP-1-MD1-2(Trunk2) R99 1/100 60/32 PW1 35 HSDPA 1/101 61/32 PW2 36 Signalling 1/102 62/32 PW3 37

Table 19-14 lists the configuration parameters of NE3.

19-62

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Table 19-14 Configuration parameters of NE3 Attribut e Service Source (VPI/ VCI) Sink (VPI/ VCI) PW of Service PW ID Sink Port Remarks R99 50/32 HSDPA 51/32 Signalling 52/32 Remarks R99 60/32 HSDPA 61/32 Signalling 52/32

50/32

51/32

52/32

60/33

61/33

52/32

PW1 35

PW2 36

PW3 37

PW1 35

PW2 36

PW3 37

3-MP1-1-AD1-1(1-AD1.PORT-1)

19.9.3 Configuring an ATM Service on a Route Basis

This section describes the process of configuring a UNIs-NNI ATM service on a route basis.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must understand the networking, requirements and service planning of the example. A network must be created.

Procedure
Step 1 Set LSR IDs. 1. 2. In the NE Explorer, select the NE1 and chooseConfiguration > MPLS Management > Basic Configuration from the Function Tree. Set LSR ID, Start of Global Label Space and Start of Multicast Label Space. Click Apply. The configuration parameters are as follows:
l l

LSR ID: 1.0.0.1 (The LSR ID must be unique in the entire network.) Start of Global Label Space: 0 (The minimum values of egress and ingress labels of the unicast tunnel.)

3.

Display the NE Explorer of NE2, NE3, NE4, NE5, and NE6 separately and perform the preceding two steps to set the parameters such as LSR ID. The configuration parameters are as follows:
l

NE2 LSR ID: 1.0.0.2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-63

Issue 01 (2009-06-30)

19 Configuring an ATM Service

l l l l

OptiX iManager T2000 Operation Guide for PTN NE Management

NE3 LSR ID: 1.0.0.3 NE4 LSR ID: 1.0.0.4 NE5 LSR ID: 1.0.0.5 NE6 LSR ID: 1.0.0.6

Step 2 Configure NNI interfaces. 1. 2. In the NE Explorer, select NE1 and choose Configuration > Interface Management > Ethernet Interface from the Function Tree to configure the network-side interface. In the General Attributes tab, select the 4-EFG2-1(Port-1) and 4-EFG2-2(Port-2). Right click the Port Mode filed, and select Layer 3. Set the parameters as required, and click Apply.

The configuration parameters are as follows:

l l l

Enable Port: Enabled Port Mode: Layer 3 (The port carries a tunnel.) Working Mode: Auto-Negotiation (Set the working modes of the local port and opposite port as the same.) Max Frame Length (byte): 1620 (Set this parameter according to the length of data packets. All the received data packets that contain more bytes than the maximum frame length are discarded.)

3.

Select the 4-EFG2-1(Port-1) and 4-EFG2-2(Port-2) in the Layer 3 Attributes tab. Right click the Enable Tunnel field and select Enabled. Right-click the Specify IP field and choose Manually. Then, set the parameters such as IP Address and IP Mask. Click Apply. The configuration parameters are as follows:
l l

Enable Tunnel: Enabled Max Reserved Bandwidth (kbit/s): 1000000 (The maximum reserved bandwidth should not exceed the physical bandwidth of the bearer port.) TE Measurement: 10 (The link with a smaller TE measurement value is preferred for route selection of a tunnel. You can intervene in the route selection by adjusting the TE measurement of the link. The smaller the value of the TE measurement, the higher the priority of the link. ) Specify IP: Manually (Manually indicates that you can set the IP address of the port.) 4-EFG2-1(Port-1) IP Address: 10.0.0.1 4-EFG2-2(Port-2) IP Address: 10.0.5.1 IP Mask: 255.255.255.252

l l l l

4.

Display the NE Explorer for NE2, NE3, and NE4 separately. Perform Step 2.1 through Step 2.3 to set parameters of each related interface. Set the parameters of each interface the same as NE1-4-EFG2-1(Port-1). The layer 3 attributes of each ports are as follows:

19-64

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

l

19 Configuring an ATM Service

NE2-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.1.1

NE2-3-EG16-1(Port-1) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.0.2

NE3-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.1.2

NE3-1-EX2-2(Port-2) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.2.1

NE4-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.2.2

NE4-1-EX2-2(Port-2) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.3.1

NE5-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.3.2

NE5-3-EG16-1(Port-1) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.4.2

NE6-4-EFG2-1(Port-1) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.5.2

NE6-4-EFG2-2(Port-2) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.4.1

Step 3 Configure the control plane. 1. 2. In the NE Explorer, select an NE1 and choose Configuration > Control Plane Configuration > IGP-ISIS Configuration from the Function Tree. Choose the Port Configuration tab and then click New. Click Add in the dialog box displayed. Then Select 4-EFG2-1(Port-1) and 4-EFG2-2(Port-2) in the port tab. Click OK. The configuration parameters are as follows:
l l

Link Level: level-1-2 LSP Retransmission Interval(s): 5 (In the case of a point-to-point link, if the local equipment fails to receive any response in a period after transmitting the LSP, the local
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-65

Issue 01 (2009-06-30)

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

equipment considers that the LSP is lost or discarded. To ensure the transmission reliability, the local equipment transmits the LSP again.)
l

Minimum LSP Transmission Interval (ms): 30

3.

Optional: Choose Configuration > Control Plane Configuration > MPLS-LDP Configuration from the Function Tree.
NOTE

When creating a dynamic PW to carry services, set the parameters related to MPLS-LDP.

4.

Optional: Click Create. Enter the ID of the opposite NE in the Create LDP Peer Entity dialog box. Click OK. The configuration parameters are as follows:
l l l

Opposite LSR ID: 1.0.0.3 (The opposite LSR ID indicates the LSR ID of the terminal NE on the PW, that is, NE3 in this case.) Hello Send Interval(s): 10 (The Hello packets are periodically sent to maintain the neighborship.) KeepAlive Send Interval(s): 10 (The KeepAlive packets are periodically sent to maintain the LDP session.)

5.

In the NE Explorer, select NE3. Set the parameters related to the control plane by following Step 3.1 to Step 3.4. Set the IS-IS parameters of NE3 as the same as the IS-IS parameters of NE1. Set the LDP parameters as follows:
l

Opposite LSR ID: 1.0.0.1 (The opposite LSR ID indicates the LSR ID of the terminal NE on the PW, that is, NE1 in this case.)

Step 4 Creating Working MPLS Tunnel. 1. 2. On the Main Topology, choose Trail > Tunnel Creation. The Create Tunnel dialog box is displayed. Select Create Reverse Tunnel, and configure parameters for the positive tunnel and reverse tunnel in the General Attributes.

The configuration parameters are as follows:

19-66 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

l l l

19 Configuring an ATM Service

Tunnel ID: 1 (Positive), 2 (Reverse) Name: Tunnel-0001 (Positive), Tunnel-0002 (Reverse) Signal Type: Dynamic (If you set signal type to dynamic, the LDP distributes labels and the tunnel is a dynamic tunnel; if you set signal type to static, labels are manually added and the tunnel is a static tunnel.) Scheduling Type: E-LSP

E-LSP indicates that the tunnel determines the scheduling priority and discard priority of packets according to the EXP information. On one MPLS tunnel of the E-LSP type, there can be a maximum of eight types of PWs.

l l

EXP:- (tunnel priority.) Bandwidth (kbit/s): 30000 (Set the bandwidth according to networking planning.)

3.

Click Next, and select Source Node and Sink Node. Click Add to add route restrictions. The configuration parameters are as follows:
l l l l

Source Node: NE1 Sink Node: NE3 Positive Route Constraint Port IP Address: 10.0.0.2, 10.0.1.2, Include Strict Reverse Route Constraint Port IP Address: 10.0.1.1, 10.0.0.1, Include Strict

4.

Click Next. Set the parameters such as Setup Priority and Hold Priority for the tunnel according to the planning. Then, click Next. Confirm the tunnel information and then click Finish. The configuration parameters are as follows:
l

Setup Priority: 7 (Setup priority is specified for an MPLS tunnel during creation. "0" indicates the highest priority. In the case insufficiency of resources, the MPLS tunnel of a higher setup priority can preempt the bandwidth of other MPLS tunnels and thus can be created successfully.) Hold Priority: 0 (Hold priority is specified for an MPLS tunnel after creation. "0" indicates the highest priority. In the case of insufficiency of resources, the bandwidth for the MPLS tunnel of a higher hold priority is less likely to be preempted by other tunnels. When creating a dynamic tunnel, make sure that the hold priority is higher or equal to the setup priority.) Color(0x): 0 (Set the affinity attribute of a link. When the primary tunnel is faulty, the link with the same color is preferred during rerouting. When the affinity attribute of links is not required, adopt the default value.) Mask(0x): 0 (Set the number of bits of the mask. Match the number of bits of a mask with the link color. Select the route of a matching link color.) Tunnel Type: Primary Tunnel (You can set the tunnel type to primary tunnel or bypass tunnel. According to the planning, the tunnel is a primary tunnel in this case.)

Step 5 Configure three ATM policies: CBR, RT-VBR, UBR. 1. 2. 3. 1.

Issue 01 (2009-06-30)

Configure the CBR policy, refer to QoS Configuration Case of the ATM Service . Configure the RT-VBR policy, refer to QoS Configuration Case of the ATM Service . Configure the UBR policy, refer to QoS Configuration Case of the ATM Service . Configure the NodeB-side ATM interface.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-67

Step 6 Configure interfaces: NodeB-side ATM interface and RNC-side ATM interface.

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

a.

In the NE Explorer, select NE1 and choose Configuration > Interface Management > PDH Interface from the Function Tree. Then, configure the NodeBside interface. Select 3-L12-1(Port-1) to 3-L12-8(Port-8). Right-click the Port Mode field and choose Layer 2. Then, click Apply.
NOTE

b.

Before setting the port mode, make sure that the port DCN is disabled.

The configuration parameters are as follows:

l l

Port: 3-L12-1(Port-1) to 3-L12-8(Port-8) Name: NodeB ATM (Set the port name as required. The port name distinguishes the port from other ports and helps to query the port.) Port Mode: Layer 2 (The port transmits IMA signals.) Encapsulation: ATM

l l

c.

In the Advanced Attributes tab, set the Frame Format, Frame Mode of the 3L12-1(Port-1) to 3-L12-8(Port-8). Click Apply. The configuration parameters are as follows:
l l

Port: 3-L12(Port-1) to 3-L12-8(Port-8) Frame Format: CRC-4 Multiframe (Set the Frame Format as the same as the parameter of NodeB.) Frame Mode: 31

d. e.

Choose Configuration > Interface Management > ATM IMA Management from Function Tree, and click the Binding tab. In the Binding tab, click Configuration and set the ports to be bound with 1-CXP-1MD1-1(Trunk1) and 1-CXP-1-MD1-2(Trunk2). Then, click OK. Set the parameters related to 1-CXP-1-MD1-1(Trunk1) as follows:
l l l

Available Boards: 1-CXP Configuration Ports: 1-CXP-1-MD1-1(Trunk1) Available Bound Paths Level: E1

E1: In the case of the E1 boards, when the E1 level is selected, the entire E1 channel is used to transport ATM IMA signals. Fractional E1: In the case of the E1 boards, when the fractional E1 level is selected, certain 64k timeslots of the E1 channel are used to transport ATM IMA signals. In the case of the ATM STM-1 boards, when the fractional E1 level is selected, certain 64k timeslots of the VC-12 lower order path are used to transport ATM IMA signals. When the fractional E1 level is selected, you should ensure that the 64k serial port is already created. VC12-xv: In the case of the ATM STM-1 boards, the STM-1 VC-4 path contains 63xVC-12 lower order paths. When the VC12-xv level is selected, certain VC-12 lower order paths of the VC-4 path are used to transport ATM IMA signals.

l l

Direction: Bidirectional (Default) Optical Interface: - (This parameter need not be set for E1, but need be set for VC12-xv. Herein, the path level is E1.) Available Resources: 3-L12-1(Port-1) to 3-L12-4(Port-4)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

19-68

OptiX iManager T2000 Operation Guide for PTN NE Management

l

19 Configuring an ATM Service

Available Timeslots: - (This parameter need not be set for E1, but need be set for VC12-xv.) Available Boards: 1-CXP Configuration Ports: 1-CXP-1-MD1-2(Trunk2) Available Bound Paths Level: E1 Direction: Bidirectional Optical Interface: Available Resources: 3-L12-5(Port-5) to 3-L12-8(Port-8) Available Timeslots: -

Set the parameters related to 1-CXP-1-MD1-2(Trunk2) as follows:

l l l l l l l

f.

In the IMA Group Management tab, double-click the IMA Protocol Enable Status field and select Enabled. Set the other parameters as required. Then, click Apply. The configuration parameters are as follows: Set the IMA Protocol Version, IMA Transmit Frame Length, IMA Symmetry Mode, Maximum Delay Between Links, Minimum Number of Active Transmitting Links, and Minimum Number of Active Receiving Links parameters as the same as these parameters of NodeB.

g.

In the ATM Interface Management tab, set the parameters such as Max. VPI Bits and Max. VCI Bits for the interface. Then, click Apply. The configuration parameters are as follows:
l l l

Port Type: UNI (A UNI interface is connected to the client equipment and an NNI interface is connected to ATM equipment in the core network.) ATM Cell Payload Scrambling: Enabled Max. VPI Bits: 8 (Set this parameter according to networking planning. Set Max. VPI Bits to specify the value range of VPI. The VPI ranges from 0 to 2MaxVPIbits-1.) Max. VCI Bits: 7 (Set this parameter according to networking planning. Set Max. VCI Bits to specify the value range of VCI. The VCI ranges from 0 to 2MaxVCIbits-1.) VCC-Supported VPI Count: 32 (Set this parameter according to networking planning.) Loopback: Non-Loopback

l l

2.

Configure the RNC-side ATM interface. a. In the NE Explorer, select NE3 and choose Configuration > Interface Management > SDH Interface from the Function Tree. Configure the RNC-side interface. In the Layer 2 Attributes tab, select 3-MP1-1-AD1-(1-AD1.PORT-1) and set the parameters such as Max. VPI Bits and Max. VCI Bits for the interface. Then, click Apply.

b.

The configuration parameters are as follows:

Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-69

19 Configuring an ATM Service

l l l l l

OptiX iManager T2000 Operation Guide for PTN NE Management

Port Type: UNI ATM Cell Payload Scrambling: Enabled Max.VPI Bits: 8 Max. VCI Bits: 7 VCC-Supported VPI Count: 32

Step 7 Create three UNIs-NNI ATM services. 1. 2. Choose Trail > PTN Service > ATM Service Creation from the Main Menu. Create an R99 service from NE1 to NE3. In the displayed Create ATM Service dialog box, set the parameters such as Service ID, Service Name, Connection Type, Source NE, and Sink NE. The configuration parameters are as follows:
l l l

Service ID: 1 Service Name: ATMService-R99 Connection Type: PVC (PVC indicates that the VPI and VCI of the ATM connection can be modified; PVP indicates that only the VPI of the ATM connection can be modified.) Source NE: NE1 Source Port: 1-CXP-1-MD1-1(Trunk1) and 1-CXP-1-MD1-2(Trunk2) Sink NE: NE3 Sink Port: 3-MP1-1-AD1-1(Port-1)

l l l l

3.

In the Create ATM Service, click Add to add connections. The configuration parameters are as follows:
l

Connection 1

Name: Connection 1 Source Port: NE1-1-CXP-1-MD1-Trunk1 Source VPI: 1 (the VPI information transmitted with the service from NodeB) Source VCI: 100 (the VCI information transmitted with the service from NodeB) Sink Port: NE3-3-MP1-1-AD1-1(Port-1) Sink VPI: 50 (The VPI information transmitted with the service after VPI switching. The Sink VPI ranges from 0 to 2MaxVPIbits-1.) Sink VCI: 32 (The VCI information transmitted with the service after VCI switching. The Sink VCI ranges from 0 to 2MaxVCIbits-1.) Uplink ATM Policy Name(ID): RT-VBR (Select the RT-VBR policy, because connection 1 is an R99 service.) Downlink ATM Policy Name(ID): RT-VBR (Select the RT-VBR policy, because connection 1 is an R99 service.) Transit VPI: Transit VCI: Name: Connection 2
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

Connection 2

19-70

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Source Port: NE1-1-CXP-1-MD1-2(Trunk2) Source VPI: 1 Source VCI: 100 Sink Port: NE3-3-MP1-1-AD1-1(Port-1) Sink VPI: 60 Sink VCI: 32 Uplink ATM Policy Name(ID): RT-VBR (Select the RT-VBR policy, because connection 2 is an R99 service.) Downlink ATM Policy Name(ID): RT-VBR (Select the RT-VBR policy, because connection 2 is an R99 service.) Transit VPI: Transit VCI: -

4.

Click Next and set PW-related parameters. The configuration parameters are as follows:
l l

PW ID: 35 Protocol Type: Dynamic (Dynamic indicates that the LDP protocol distributes the PW labels; Static indicates that the ingress and egress labels are manually added.) Encapsulation Type: ATM n-to-one VPC cell transport (Select ATM n-to-one VPC cell transport if multiple ATM connections are mapped to one PW; select ATM oneto-one VCC Cell Mode if one ATM connection is mapped to one PW. Herein, two ATM connections are mapped to one PW.) Direction: Bidirectional Tunnel Type: MPLS Tunnel Tunnel Name (ID): Tunnel-001(Uplink), Tunnel-002(Downlink) Control Word Use Policy: Must use Control Channel Type: CW (CW realizes connectivity check of the PW.) VCCV Verification Mode: Ping ( PW Ping realizes connectivity check of the PW.) Max. Concatenated Cell Count: 10 (the maximum number of ATM cells that can be encapsulated in each packet) Packet Loading Time (us): 1000 Bandwidth Enabled: Enabled CIR (kbit/s): 4096 (Set the bandwidth according to the service traffic.) CBS (byte): PIR (kbit/s): 10240 PBS (byte): EXP: 1 NE: NE1 CoS Mapping Name(ID): 1(mapping1) NE: NE3 CoS Mapping Name(ID): 1(mapping1)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-71

l l l l l l l

l l l l l l l l l l l

Issue 01 (2009-06-30)

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

5. 6.

Click Finish. The ATMService-R99 service is successfully created. Repeat the previous steps to create an ATMService-HSDPA service.
l

Set the general attributes of the ATM service as follows:

Service ID: 2 Service Name: ATMService-HSDPA Connection Type: PVC Source NE: NE1 Source Port: 1-CXP-1-MD1-1(Trunk1), 1-CXP-1-MD1-2(Trunk2) Sink NE: NE3 Sink Port: 3-MP1-1-AD1-1(1-AD1.PORT-1) Connection 1

Configure ATM connections:

Name: Connection 1 Source Port: NE1-1-CXP-1-MD1-Trunk1 Source VPI: 1 Source VCI: 101 Sink Port: NE3-3-MP1-1-AD1-1(1-AD1.PORT-1) Sink VPI: 51 Sink VCI: 32 Uplink ATM Policy Name (ID): UBR (policy) Downlink ATM Policy Name (ID): UBR (policy) Transit VPI: Transit VCI: Name: Connection 2 Source Port: NE1-1-CXP-1-MD1-Trunk1 Source VPI: 1 Source VCI:101 Sink Port: NE3-3-MP1-1-AD1-1(1-AD1.PORT-1) Sink VPI: 61 Sink VCI: 32 Uplink ATM Policy Name (ID): UBR (policy) Downlink ATM Policy Name (ID): UBR (policy) Transit VPI: Transit VCI: -

Connection 2

Set the PW-related parameters as follows:

PW ID: 36 Protocol Type: Dynamic Encapsulation Type: ATM n-to-one VPC cell transport
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

19-72

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Direction: Bidirectional Tunnel Type: MPLS Tunnel Tunnel Name (ID): Tunnel-001 Control Word Use Policy: Must use Control Channel Type: CW VCCV Verification Mode: Ping Max. Concatenated Cell Count: 20 Packet Loading Time (us): 1000 Bandwidth Enabled: Enabled CIR (kbit/s): 4096 CBS (byte): PIR (kbit/s): 10240 PBS (byte): EXP: 3 NE: NE1 CoS Mapping Name(ID): 1(mapping1) NE: NE3 CoS Mapping Name(ID): 1(mapping1)

7.

Repeat the previous steps to create an ATMService-Sinalling service.

l

Set the general attributes of the ATM service as follows:

Service ID: 23 Service Name: ATMService-Sinalling Connection Type: PVC Source NE: NE1 Source Port: 1-1-CXP-1-MD1-1(Trunk1), 1-1-CXP-1-MD1-2(Trunk2) Sink NE: NE3 Sink Port: 3-MP1-1-AD1-1(1-AD1.PORT-1) Connection 1

Configure ATM connections:

Name: Connection 1 Source Port: NE1-1-CXP-1-MD1-Trunk1 Source VPI: 1 Source VCI: 102 Sink Port: NE3-3-MP1-1-AD1-1(1-AD1.PORT-1) Sink VPI: 52 Sink VCI: 32 Uplink ATM Policy Name (ID): CBR Downlink ATM Policy Name (ID): CBR
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-73

Issue 01 (2009-06-30)

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Transit VPI: Transit VCI: Name: Connection 2 Source Port: NE1-1-CXP-1-MD1-Trunk1 Source VPI: 1 Source VCI:102 Sink Port: NE3-3-MP1-1-AD1-1(1-AD1.PORT-1) Sink VPI: 62 Sink VCI: 32 Uplink ATM Policy Name (ID): CBR Downlink ATM Policy Name (ID): CBR Transit VPI: Transit VCI: -

Connection 2

Set the PW-related parameters as follows:

PW ID: 37 Protocol Type: Dynamic Encapsulation Type: ATM n-to-one VPC cell transport Direction: Bidirectional Tunnel Type: MPLS Tunnel Tunnel Name (ID): Tunnel-001 Control Word Use Policy: Must use Control Channel Type: CW VCCV Verification Mode: Ping Max. Concatenated Cell Count: 20 Packet Loading Time (us): 1000 Bandwidth Enabled: Enabled CIR (kbit/s): 4096 CBS (byte): PIR (kbit/s): 10240 PBS (byte): EXP: 0 NE: NE1 CoS Mapping Name(ID): 1(mapping1) NE: NE3 CoS Mapping Name(ID): 1(mapping1)

----End
19-74 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

19.9.4 Configuring an ATM Service on a Per-NE Basis

This section describes the process of configuring a UNIs-NNI ATM service on a per-NE basis.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must understand the networking, requirements and service planning of the example. A network must be created.

Procedure
Step 1 Set LSR IDs. 1. 2. In the NE Explorer, select the NE1 and chooseConfiguration > MPLS Management > Basic Configuration from the Function Tree. Set LSR ID, Start of Global Label Space and Start of Multicast Label Space. Click Apply. The configuration parameters are as follows:
l l

LSR ID: 1.0.0.1 (The LSR ID must be unique in the entire network.) Start of Global Label Space: 0 (The minimum values of egress and ingress labels of the unicast tunnel.)

3.

Display the NE Explorer of NE2, NE3, NE4, NE5, and NE6 separately and perform the preceding two steps to set the parameters such as LSR ID. The configuration parameters are as follows:
l l l l l

NE2 LSR ID: 1.0.0.2 NE3 LSR ID: 1.0.0.3 NE4 LSR ID: 1.0.0.4 NE5 LSR ID: 1.0.0.5 NE6 LSR ID: 1.0.0.6

Step 2 Configure NNI interfaces. 1. 2. In the NE Explorer, select NE1 and choose Configuration > Interface Management > Ethernet Interface from the Function Tree to configure the network-side interface. In the General Attributes tab, select the 4-EFG2-1(Port-1) and 4-EFG2-2(Port-2). Right click the Port Mode filed, and select Layer 3. Set the parameters as required, and click Apply.

The configuration parameters are as follows:

l l

Enable Port: Enabled Port Mode: Layer 3 (The port carries a tunnel.)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-75

Issue 01 (2009-06-30)

19 Configuring an ATM Service

l

OptiX iManager T2000 Operation Guide for PTN NE Management

Working Mode: Auto-Negotiation (Set the working modes of the local port and opposite port as the same.) Max Frame Length (byte): 1620 (Set this parameter according to the length of data packets. All the received data packets that contain more bytes than the maximum frame length are discarded.)

3.

Select the 4-EFG2-1(Port-1) and 4-EFG2-2(Port-2) in the Layer 3 Attributes tab. Right click the Enable Tunnel field and select Enabled. Right-click the Specify IP field and choose Manually. Then, set the parameters such as IP Address and IP Mask. Click Apply. The configuration parameters are as follows:
l l

Enable Tunnel: Enabled Max Reserved Bandwidth (kbit/s): 1000000 (The maximum reserved bandwidth should not exceed the physical bandwidth of the bearer port.) TE Measurement: 10 (The link with a smaller TE measurement value is preferred for route selection of a tunnel. You can intervene in the route selection by adjusting the TE measurement of the link. The smaller the value of the TE measurement, the higher the priority of the link. ) Specify IP: Manually (Manually indicates that you can set the IP address of the port.) 4-EFG2-1(Port-1) IP Address: 10.0.0.1 4-EFG2-2(Port-2) IP Address: 10.0.5.1 IP Mask: 255.255.255.252

l l l l

4.

Display the NE Explorer for NE2, NE3, and NE4 separately. Perform Step 2.1 through Step 2.3 to set parameters of each related interface. Set the parameters of each interface the same as NE1-4-EFG2-1(Port-1). The layer 3 attributes of each ports are as follows:
l

NE2-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.1.1

NE2-3-EG16-1(Port-1) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.0.2

NE3-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.1.2

NE3-1-EX2-2(Port-2) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.2.1

NE4-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.2.2

NE4-1-EX2-2(Port-2) Max Reserved Bandwidth (kbit/s): 10000000

19-76

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

IP Address: 10.0.3.1
l

NE5-1-EX2-1(Port-1) Max Reserved Bandwidth (kbit/s): 10000000 IP Address: 10.0.3.2

NE5-3-EG16-1(Port-1) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.4.2

NE6-4-EFG2-1(Port-1) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.5.2

NE6-4-EFG2-2(Port-2) Max Reserved Bandwidth (kbit/s): 1000000 IP Address: 10.0.4.1

Step 3 Configure the control plane. 1. 2. In the NE Explorer, select an NE1 and choose Configuration > Control Plane Configuration > IGP-ISIS Configuration from the Function Tree. Choose the Port Configuration tab and then click New. Click Add in the dialog box displayed. Then Select 4-EFG2-1(Port-1) and 4-EFG2-2(Port-2) in the port tab. Click OK. The configuration parameters are as follows:
l l

Link Level: level-1-2 LSP Retransmission Interval(s): 5 (In the case of a point-to-point link, if the local equipment fails to receive any response in a period after transmitting the LSP, the local equipment considers that the LSP is lost or discarded. To ensure the transmission reliability, the local equipment transmits the LSP again.) Minimum LSP Transmission Interval (ms): 30

3.

Optional: Choose Configuration > Control Plane Configuration > MPLS-LDP Configuration from the Function Tree.
NOTE

When creating a dynamic PW to carry services, set the parameters related to MPLS-LDP.

4.

Optional: Click Create. Enter the ID of the opposite NE in the Create LDP Peer Entity dialog box. Click OK. The configuration parameters are as follows:
l

Opposite LSR ID: 1.0.0.3 (The opposite LSR ID indicates the LSR ID of the terminal NE on the PW, that is, NE3 in this case.) Hello Send Interval(s): 10 (The Hello packets are periodically sent to maintain the neighborship.) KeepAlive Send Interval(s): 10 (The KeepAlive packets are periodically sent to maintain the LDP session.)

5.

In the NE Explorer, select NE3. Set the parameters related to the control plane by following Step 3.1 to Step 3.4. Set the IS-IS parameters of NE3 as the same as the IS-IS parameters of NE1. Set the LDP parameters as follows:

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

19-77

19 Configuring an ATM Service

l

OptiX iManager T2000 Operation Guide for PTN NE Management

Opposite LSR ID: 1.0.0.1 (The opposite LSR ID indicates the LSR ID of the terminal NE on the PW, that is, NE1 in this case.)

Step 4 Creating Working MPLS Tunnel. 1. 2. On the Main Topology, choose Trail > Tunnel Creation. The Create Tunnel dialog box is displayed. Select Create Reverse Tunnel, and configure parameters for the positive tunnel and reverse tunnel in the General Attributes.

The configuration parameters are as follows:

l l l

Tunnel ID: 1 (Positive), 2 (Reverse) Name: Tunnel-0001 (Positive), Tunnel-0002 (Reverse) Signal Type: Dynamic (If you set signal type to dynamic, the LDP distributes labels and the tunnel is a dynamic tunnel; if you set signal type to static, labels are manually added and the tunnel is a static tunnel.) Scheduling Type: E-LSP

E-LSP indicates that the tunnel determines the scheduling priority and discard priority of packets according to the EXP information. On one MPLS tunnel of the E-LSP type, there can be a maximum of eight types of PWs.

l l

EXP:- (tunnel priority.) Bandwidth (kbit/s): 30000 (Set the bandwidth according to networking planning.)

3.

Click Next, and select Source Node and Sink Node. Click Add to add route restrictions. The configuration parameters are as follows:
l l l l

Source Node: NE1 Sink Node: NE3 Positive Route Constraint Port IP Address: 10.0.0.2, 10.0.1.2, Include Strict Reverse Route Constraint Port IP Address: 10.0.1.1, 10.0.0.1, Include Strict
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

19-78

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

4.

Click Next. Set the parameters such as Setup Priority and Hold Priority for the tunnel according to the planning. Then, click Next. Confirm the tunnel information and then click Finish. The configuration parameters are as follows:
l

Setup Priority: 7 (Setup priority is specified for an MPLS tunnel during creation. "0" indicates the highest priority. In the case insufficiency of resources, the MPLS tunnel of a higher setup priority can preempt the bandwidth of other MPLS tunnels and thus can be created successfully.) Hold Priority: 0 (Hold priority is specified for an MPLS tunnel after creation. "0" indicates the highest priority. In the case of insufficiency of resources, the bandwidth for the MPLS tunnel of a higher hold priority is less likely to be preempted by other tunnels. When creating a dynamic tunnel, make sure that the hold priority is higher or equal to the setup priority.) Color(0x): 0 (Set the affinity attribute of a link. When the primary tunnel is faulty, the link with the same color is preferred during rerouting. When the affinity attribute of links is not required, adopt the default value.) Mask(0x): 0 (Set the number of bits of the mask. Match the number of bits of a mask with the link color. Select the route of a matching link color.) Tunnel Type: Primary Tunnel (You can set the tunnel type to primary tunnel or bypass tunnel. According to the planning, the tunnel is a primary tunnel in this case.)

Step 5 Configure three ATM policies: CBR, RT-VBR, UBR. 1. 2. 3. Configure the CBR policy, refer to QoS Configuration Case of the ATM Service . Configure the RT-VBR policy, refer to QoS Configuration Case of the ATM Service . Configure the UBR policy, refer to QoS Configuration Case of the ATM Service .

Step 6 Configure interfaces: NodeB-side ATM interface and RNC-side ATM interface. 1. Configure the NodeB-side ATM interface. a. In the NE Explorer, select NE1 and choose Configuration > Interface Management > PDH Interface from the Function Tree. Then, configure the NodeBside interface. Select 3-L12-1(Port-1) to 3-L12-8(Port-8). Right-click the Port Mode field and choose Layer 2. Then, click Apply.
NOTE

b.

Before setting the port mode, make sure that the port DCN is disabled.

The configuration parameters are as follows:

l l

Port: 3-L12-1(Port-1) to 3-L12-8(Port-8) Name: NodeB ATM (Set the port name as required. The port name distinguishes the port from other ports and helps to query the port.) Port Mode: Layer 2 (The port transmits IMA signals.) Encapsulation: ATM

l l

c.

In the Advanced Attributes tab, set the Frame Format, Frame Mode of the 3L12-1(Port-1) to 3-L12-8(Port-8). Click Apply. The configuration parameters are as follows:
l

Port: 3-L12(Port-1) to 3-L12-8(Port-8)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-79

Issue 01 (2009-06-30)

19 Configuring an ATM Service

l

OptiX iManager T2000 Operation Guide for PTN NE Management

Frame Format: CRC-4 Multiframe (Set the Frame Format as the same as the parameter of NodeB.) Frame Mode: 31

d. e.

Choose Configuration > Interface Management > ATM IMA Management from Function Tree, and click the Binding tab. In the Binding tab, click Configuration and set the ports to be bound with 1-CXP-1MD1-1(Trunk1) and 1-CXP-1-MD1-2(Trunk2). Then, click OK. Set the parameters related to 1-CXP-1-MD1-1(Trunk1) as follows:
l l l

Available Boards: 1-CXP Configuration Ports: 1-CXP-1-MD1-1(Trunk1) Available Bound Paths Level: E1

E1: In the case of the E1 boards, when the E1 level is selected, the entire E1 channel is used to transport ATM IMA signals. Fractional E1: In the case of the E1 boards, when the fractional E1 level is selected, certain 64k timeslots of the E1 channel are used to transport ATM IMA signals. In the case of the ATM STM-1 boards, when the fractional E1 level is selected, certain 64k timeslots of the VC-12 lower order path are used to transport ATM IMA signals. When the fractional E1 level is selected, you should ensure that the 64k serial port is already created. VC12-xv: In the case of the ATM STM-1 boards, the STM-1 VC-4 path contains 63xVC-12 lower order paths. When the VC12-xv level is selected, certain VC-12 lower order paths of the VC-4 path are used to transport ATM IMA signals.

l l

Direction: Bidirectional (Default) Optical Interface: - (This parameter need not be set for E1, but need be set for VC12-xv. Herein, the path level is E1.) Available Resources: 3-L12-1(Port-1) to 3-L12-4(Port-4) Available Timeslots: - (This parameter need not be set for E1, but need be set for VC12-xv.) Available Boards: 1-CXP Configuration Ports: 1-CXP-1-MD1-2(Trunk2) Available Bound Paths Level: E1 Direction: Bidirectional Optical Interface: Available Resources: 3-L12-5(Port-5) to 3-L12-8(Port-8) Available Timeslots: -

l l

Set the parameters related to 1-CXP-1-MD1-2(Trunk2) as follows:

l l l l l l l

f.

In the IMA Group Management tab, double-click the IMA Protocol Enable Status field and select Enabled. Set the other parameters as required. Then, click Apply. The configuration parameters are as follows: Set the IMA Protocol Version, IMA Transmit Frame Length, IMA Symmetry Mode, Maximum Delay Between Links, Minimum Number of Active

19-80

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Transmitting Links, and Minimum Number of Active Receiving Links parameters as the same as these parameters of NodeB. g. In the ATM Interface Management tab, set the parameters such as Max. VPI Bits and Max. VCI Bits for the interface. Then, click Apply. The configuration parameters are as follows:
l

Port Type: UNI (A UNI interface is connected to the client equipment and an NNI interface is connected to ATM equipment in the core network.) ATM Cell Payload Scrambling: Enabled Max. VPI Bits: 8 (Set this parameter according to networking planning. Set Max. VPI Bits to specify the value range of VPI. The VPI ranges from 0 to 2MaxVPIbits-1.) Max. VCI Bits: 7 (Set this parameter according to networking planning. Set Max. VCI Bits to specify the value range of VCI. The VCI ranges from 0 to 2MaxVCIbits-1.) VCC-Supported VPI Count: 32 (Set this parameter according to networking planning.) Loopback: Non-Loopback

l l

2.

Configure the RNC-side ATM interface. a. In the NE Explorer, select NE3 and choose Configuration > Interface Management > SDH Interface from the Function Tree. Configure the RNC-side interface. In the Layer 2 Attributes tab, select 3-MP1-1-AD1-(1-AD1.PORT-1) and set the parameters such as Max. VPI Bits and Max. VCI Bits for the interface. Then, click Apply.

b.

The configuration parameters are as follows:

l l l l l

Port Type: UNI ATM Cell Payload Scrambling: Enabled Max.VPI Bits: 8 Max. VCI Bits: 7 VCC-Supported VPI Count: 32

Step 7 Configure interfaces: NodeB-side ATM interface and RNC-side ATM interface. 1. Configure the NodeB-side ATM interface. a. In the NE Explorer, select NE1 and choose Configuration > Interface Management > PDH Interface from the Function Tree. Then, configure the NodeBside interface. Select 3-L12-1(Port-1) to 3-L12-8(Port-8). Right-click the Port Mode field and choose Layer 2. Then, click Apply.
NOTE

b.

Before setting the port mode, make sure that the port DCN is disabled.

The configuration parameters are as follows:

Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-81

19 Configuring an ATM Service

l l

OptiX iManager T2000 Operation Guide for PTN NE Management

Port: 3-L12-1(Port-1) to 3-L12-8(Port-8) Name: NodeB ATM (Set the port name as required. The port name distinguishes the port from other ports and helps to query the port.) Port Mode: Layer 2 (The port transmits IMA signals.) Encapsulation: ATM

l l

c.

In the Advanced Attributes tab, set the Frame Format, Frame Mode of the 3L12-1(Port-1) to 3-L12-8(Port-8). Click Apply. The configuration parameters are as follows:
l l

Port: 3-L12(Port-1) to 3-L12-8(Port-8) Frame Format: CRC-4 Multiframe (Set the Frame Format as the same as the parameter of NodeB.) Frame Mode: 31

d. e.

Choose Configuration > Interface Management > ATM IMA Management from Function Tree, and click the Binding tab. In the Binding tab, click Configuration and set the ports to be bound with 1-CXP-1MD1-1(Trunk1) and 1-CXP-1-MD1-2(Trunk2). Then, click OK. Set the parameters related to 1-CXP-1-MD1-1(Trunk1) as follows:
l l l

Available Boards: 1-CXP Configuration Ports: 1-CXP-1-MD1-1(Trunk1) Available Bound Paths Level: E1

E1: In the case of the E1 boards, when the E1 level is selected, the entire E1 channel is used to transport ATM IMA signals. Fractional E1: In the case of the E1 boards, when the fractional E1 level is selected, certain 64k timeslots of the E1 channel are used to transport ATM IMA signals. In the case of the ATM STM-1 boards, when the fractional E1 level is selected, certain 64k timeslots of the VC-12 lower order path are used to transport ATM IMA signals. When the fractional E1 level is selected, you should ensure that the 64k serial port is already created. VC12-xv: In the case of the ATM STM-1 boards, the STM-1 VC-4 path contains 63xVC-12 lower order paths. When the VC12-xv level is selected, certain VC-12 lower order paths of the VC-4 path are used to transport ATM IMA signals.

l l

Direction: Bidirectional (Default) Optical Interface: - (This parameter need not be set for E1, but need be set for VC12-xv. Herein, the path level is E1.) Available Resources: 3-L12-1(Port-1) to 3-L12-4(Port-4) Available Timeslots: - (This parameter need not be set for E1, but need be set for VC12-xv.) Available Boards: 1-CXP Configuration Ports: 1-CXP-1-MD1-2(Trunk2) Available Bound Paths Level: E1 Direction: Bidirectional
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

l l

Set the parameters related to 1-CXP-1-MD1-2(Trunk2) as follows:

l l l l

19-82

OptiX iManager T2000 Operation Guide for PTN NE Management

l l l

19 Configuring an ATM Service

Optical Interface: Available Resources: 3-L12-5(Port-5) to 3-L12-8(Port-8) Available Timeslots: -

f.

In the IMA Group Management tab, double-click the IMA Protocol Enable Status field and select Enabled. Set the other parameters as required. Then, click Apply. The configuration parameters are as follows: Set the IMA Protocol Version, IMA Transmit Frame Length, IMA Symmetry Mode, Maximum Delay Between Links, Minimum Number of Active Transmitting Links, and Minimum Number of Active Receiving Links parameters as the same as these parameters of NodeB.

g.

In the ATM Interface Management tab, set the parameters such as Max. VPI Bits and Max. VCI Bits for the interface. Then, click Apply. The configuration parameters are as follows:
l

Port Type: UNI (A UNI interface is connected to the client equipment and an NNI interface is connected to ATM equipment in the core network.) ATM Cell Payload Scrambling: Enabled Max. VPI Bits: 8 (Set this parameter according to networking planning. Set Max. VPI Bits to specify the value range of VPI. The VPI ranges from 0 to 2MaxVPIbits-1.) Max. VCI Bits: 7 (Set this parameter according to networking planning. Set Max. VCI Bits to specify the value range of VCI. The VCI ranges from 0 to 2MaxVCIbits-1.) VCC-Supported VPI Count: 32 (Set this parameter according to networking planning.) Loopback: Non-Loopback

l l

2.

Configure the RNC-side ATM interface. a. In the NE Explorer, select NE3 and choose Configuration > Interface Management > SDH Interface from the Function Tree. Configure the RNC-side interface. In the Layer 2 Attributes tab, select 3-MP1-1-AD1-(1-AD1.PORT-1) and set the parameters such as Max. VPI Bits and Max. VCI Bits for the interface. Then, click Apply.

b.

The configuration parameters are as follows:

l l l l l

Port Type: UNI ATM Cell Payload Scrambling: Enabled Max.VPI Bits: 8 Max. VCI Bits: 7 VCC-Supported VPI Count: 32
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-83

Issue 01 (2009-06-30)

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 8 Configure three UNIs-NNI ATM services. 1. 2. In the NE Explorer, select NE1 and choose Configuration > ATM Service Management from the Function Tree. Then, create an R99 service from NE1 to NE3. In the Connection tab, click New. The New ATM Service window is displayed. Then, set Service ID, Service Name, Service Type, and Connection Type. The configuration parameters are as follows:
l l l l

Service ID: 1 Service Name: ATMService-R99 Service Type: UNIs-NNI Connection Type: PVC (PVC indicates that the VPI and VCI of the ATM connection can be modified; PVP indicates that only the VPI of the ATM connection can be modified.)

3.

Click the Connection tab and click Add. The Configure Connection window is displayed. Add connection 1 and connection 2.

The configuration parameters are as follows:

l

Connection 1

Connection Name: Connection 1 Source Board: 1-CXP Source Port: 1-MD1-1(Trunk1) Source VPI: 1 (the VPI information transmitted with the service from NodeB) Source VCI: 100 (the VCI information transmitted with the service from NodeB) PW ID: 35 Sink Board: Sink Port: Sink VPI: 50 (The VPI information transmitted with the service after VPI switching. The Sink VPI ranges from 0 to 2MaxVPIbits-1.)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

19-84

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Sink VCI: 32 (The VCI information transmitted with the service after VCI switching. The Sink VCI ranges from 0 to 2MaxVCIbits-1.) Uplink Policy: RT-VBR (Select the RT-VBR policy, because connection 1 is an R99 service.) Downlink Policy: RT-VBR (Select the RT-VBR policy, because connection 1 is an R99 service.) Connection Name: Connection 2 Source Board: 1-CXP Source Port: 1-MD1-2(Trunk2) Source VPI: 1 Source VCI: 100 PW ID: 35 Sink Board: Sink Port: Sink VPI: 60 Sink VCI: 32 Uplink Policy: RT-VBR (Select the RT-VBR policy, because connection 2 is an R99 service.) Downlink Policy: RT-VBR (Select the RT-VBR policy, because connection 2 is an R99 service.)

Connection 2

4.

Click the PW tab and click Add. The Configure PW window is displayed. In the window, set attributes of the PW.

Set the parameters related to PW1 as follows:

l

General Attributes

PW ID: 35 PW Signaling Type: Dynamic (Dynamic indicates that the LDP protocol distributes the PW labels; Static indicates that the ingress and egress labels are manually added.) PW Type: ATM n to one VCC cell transport (Select ATM n-to-one VPC cell transport if multiple ATM connections are mapped to one PW; select ATM oneHuawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-85

Issue 01 (2009-06-30)

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

to-one VCC Cell Mode if one ATM connection is mapped to one PW. Herein, two ATM connections are mapped to one PW.)
l

Direction: Bidirectional PW Ingress Label: PW Egress Label: Tunnel Type: MPLS Tunnel: 1(Tunnel-00001) Peer IP: 1.0.0.3 Control Word: Must use Control Channel Type: CW (CW realizes connectivity check of the PW.) VCCV Verification Mode: Ping ( PW Ping realizes connectivity check of the PW.) Max. Concatenated Cell Count: 10 (the maximum number of ATM cells that can be encapsulated in each packet) Packet Loading Time (us): 1000

Advanced Attributes

QoS Ingress

EXP: 1

5.

Click the CoS Mapping tab and set the QoS attribute of PW1. Set the QoS mapping for PW1 as follows:
l l

PW ID: 35 CoS Mapping: mapping1(1)

6.

In the NE Explorer, select NE3. Then, create an ATMService-R99 service by following 1 to 5. The configuration parameters are as follows:
l

Set the general attributes of the ATM service as follows:

Service ID: 1 Service Name: ATMService-R99 Service Type: UNIs-NNI Connection Type: PVC Connection 1

Configure ATM Connection:

Connection Name: Connection 1 Source Board: 3-MP1 Source Port: 1-AD1-1(1-AD1.PORT-1) Source VPI: 50 Source VCI: 32 PW ID: 35 Sink Board: Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

19-86

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Sink Port: Sink VPI: 50 Sink VCI: 32 Uplink ATM Policy Name (ID): RT-VBR Downlink ATM Policy Name (ID): RT-VBR Connection Name: Connection 2 Source Board: 3-MP1 Source Port: 1-AD1-1(1-AD1.PORT-1) Source VPI: 60 Source VCI: 32 PW ID: 35 Sink Board: Sink Port: Sink VPI: 60 Sink VCI: 32 Uplink ATM Policy Name (ID): RT-VBR Downlink ATM Policy Name (ID): RT-VBR

Connection 2

Set the parameters related to PW1 as follows:

General Attributes

PW ID: 35 PW Signaling Type: Dynamic PW Type: ATM n to 1 VCC cell transport Direction: Bidirectional PW Ingress Label: PW Egress Label: Tunnel Type: MPLS Tunnel: 2(Tunnel-0002) Peer IP: 1.0.0.1 Control Word: Must Use Control Channel Type: CW VCCV Verification Mode: Ping Max. Concatenated Cell Count: 10 Packet Loading Time (us): 1000

Advanced Attributes

QoS Ingress

EXP: 1

The CoS mapping of PW1 should be configured:

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-87

Issue 01 (2009-06-30)

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

PW ID: 35 CoS Mapping: 1(mapping1)

7.

Create an ATMService-HSDPA service by following 1 to 6. Set the parameters related to NE1 as follows:
l

Set the general attributes of the ATM service as follows:

Service ID: 2 Service Name: ATMService-HSDPA Service Type: UNIs-NNI Connection Type: PVC Connection 1

Configure ATM connections:

Connection Name: Connection 1 Source Board: 1-CXP Source Port: 1-MD1-1(Trunk1) Source VPI: 1 Source VCI: 101 PW ID: 36 Sink Board: Sink Port: Sink VPI: 51 Sink VCI: 32 Uplink Policy: UBR Downlink Policy: UBR Connection Name: Connection 2 Source Board: 1-CXP Source Port: 1-MD1-2(Trunk1) Source VPI: 1 Source VCI: 101 PW ID: 36 Sink Board: Sink Port: Sink VPI: 61 Sink VCI: 32 Uplink Policy: UBR Downlink Policy: UBR

Connection 2

Set the parameters related to PW2 as follows:

General Attributes
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

19-88

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

PW ID: 36 PW Signaling Type: Dynamic PW Type: ATM n to 1 VCC cell transport Direction: Bidirectional PW Ingress Label: PW Egress Label: Tunnel Type: MPLS Tunnel: 1(Tunnel-0001) Peer IP: 1.0.0.3 Control Word: Must Use Control Channel Type: CW VCCV Verification Mode: Ping Max. Concatenated Cell Count: 10 Packet Loading Time (us): 1000

Advanced Attributes

QoS Ingress

EXP: 3

The CoS mapping of PW2 should be configured:

PW ID: 36 CoS Mapping: 1(mapping1)

Set the parameters related to NE3 as follows:

l

Set the general attributes of the ATM service as follows:

Service ID: 2 Service Name: ATMService-HSDPA Service Type: UNIs-NNI Connection Type: PVC Connection 1

Configure ATM connections:

Connection Name: Connection 1 Source Board: 3-MP1 Source Port: 1-AD1-1(1-AD1.PORT-1) Source VPI: 51 Source VCI: 32 PW ID: 36 Sink Board: Sink Port: Sink VPI: 51
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-89

Issue 01 (2009-06-30)

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Sink VCI: 32 Uplink Policy: UBR Downlink Policy: UBR Connection Name: Connection 2 Source Board: 3-MP1 Source Port: 1-AD1-1(1-AD1.PORT-1) Source VPI: 61 Source VCI: 32 PW ID: 36 Sink Board: Sink Port: Sink VPI: 61 Sink VCI: 332 Uplink Policy: UBR Downlink Policy: UBR

Connection 2

Set the parameters related to PW2 as follows:

General Attributes

PW ID: 36 PW Signaling Type: Dynamic PW Type: ATM n to 1 VCC cell transport Direction: Bidirectional PW Ingress Label: PW Egress Label: Tunnel Type: MPLS Tunnel: 2(Tunnel-0002) Peer IP: 1.0.0.1 Control Word: Must Use Control Channel Type: CW VCCV Verification Mode: Ping Max. Concatenated Cell Count: 10 Packet Loading Time (us): 1000

Advanced Attributes

QoS Ingress

EXP: 3

The CoS mapping of PW2 should be configured:

PW ID: 36 CoS Mapping: 1(mapping1)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

19-90

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

8.

Create an ATMService-Signalling service by following 1 to 6. Set the parameters related to NE1 as follows:
l

Set the general attributes of the ATM service as follows:

Service ID: 3 Service Name: ATMService-Signalling Service Type: UNIs-NNI Connection Type: PVC Connection 1

Configure ATM connections:

Connection Name: Connection 1 Source Board: 1-CXP Source Port: 1-MD1-1(Trunk1) Source VPI: 1 Source VCI: 102 PW ID: 37 Sink Board: Sink Port: Sink VPI: 52 Sink VCI: 32 Uplink Policy: UBR Downlink Policy: UBR Connection Name: Connection 2 Source Board: 1-CXP Source Port: 1-MD1-2(Trunk1) Source VPI: 1 Source VCI: 102 PW ID: 37 Sink Board: Sink Port: Sink VPI: 62 Sink VCI: 32 Uplink Policy: CBR Downlink Policy: CBR

Connection 2

Set the parameters related to PW2 as follows:

General Attributes

PW ID: 37 PW Signaling Type: Dynamic

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-91

Issue 01 (2009-06-30)

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

PW Type: ATM n to 1 VCC cell transport Direction: Bidirectional PW Ingress Label: PW Egress Label: Tunnel Type: MPLS Tunnel: 1(Tunnel-0001) Peer IP: 1.0.0.3 Control Word: Must Use Control Channel Type: CW VCCV Verification Mode: Ping Max. Concatenated Cell Count: 10 Packet Loading Time (us): 1000

Advanced Attributes

QoS Ingress

EXP: 0

The CoS mapping of PW2 should be configured:

PW ID: 37 CoS Mapping: 1(mapping1)

Set the parameters related to NE3 as follows:

l

Set the general attributes of the ATM service as follows:

Service ID: 3 Service Name: ATMService-Signalling Service Type: UNIs-NNI Connection Type: PVC Connection 1

Configure ATM connections:

Connection Name: Connection 1 Source Board: 3-MP1 Source Port: 1-AD1-1(1-AD1.PORT-1) Source VPI: 52 Source VCI: 32 PW ID: 37 Sink Board: Sink Port: Sink VPI: 52 Sink VCI: 32 Uplink Policy: CBR
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

19-92

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

Downlink Policy: CBR Connection Name: Connection 2 Source Board: 3-MP1 Source Port: 1-AD1-1(1-AD1.PORT-1) Source VPI: 62 Source VCI: 32 PW ID: 37 Sink Board: Sink Port: Sink VPI: 62 Sink VCI: 32 Uplink Policy: CBR Downlink Policy: CBR

Connection 2

Set the parameters related to PW2 as follows:

General Attributes

PW ID: 37 PW Signaling Type: Dynamic PW Type: ATM n to 1 VCC cell transport Direction: Bidirectional PW Ingress Label: PW Egress Label: Tunnel Type: MPLS Tunnel: 2(Tunnel-0002) Peer IP: 1.0.0.1 Control Word: Must Use Control Channel Type: CW VCCV Verification Mode: Ping Max. Concatenated Cell Count: 10 Packet Loading Time (us): 1000

Advanced Attributes

QoS Ingress

EXP: 0

The CoS mapping of PW2 should be configured:

PW ID: 37 CoS Mapping: 1(mapping1)

----End
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-93

19 Configuring an ATM Service

OptiX iManager T2000 Operation Guide for PTN NE Management

19.9.5 Verifying the Correctness of Service Configuration

After the ATM service is configured, the correctness of service configuration should be verified. The ATM OAM is used for verifying the correctness of the ATM service configuration.

Case Description
This case describes the ATM service carried by PWs. To verify the correctness of the service, the working state of the PW should be queried and the ATM OAM should be configured. For details, see Figure 19-15. A UNIs-NNI ATM service from the base station to RNC is created. The service type is the N:1 VC switching. The source VPI/VCI is 32/33, and the sink VPI/VCI is 52/53. The correctness of the service should be verified. Figure 19-15 ATM service OAM
1-CXP-1MD1-Trunk1 2-MP1-1-AD1-1 (1-AD1.PORT-1)

Node B PW

NE1

NE2

RNC

Procedure
Step 1 On the T2000, choose Trail > Emulation Service Management > ATM Service Management from the Main Menu. Select the service to be verified. Click the PW tab, and then click Query Working Status. If the working status is UP, it indicates that the PW is normal. Step 2 On the T2000, configure the segment end attributes of NE1 and NE2. For the configuration method, refer to 25.5.4 Setting Segment End Attribute. The following parameters, which are related to the segment end attributes of NE1, should be configured.
l l l l

Source: 1-CXP-1-MD1-1(Trunk1)-32-33 Sink: PW20-52-53 Connection Direction: Forward Segment and End Attribute: Segment Point

The following parameters, which are related to the segment end attributes of NE2, should be configured.
l l l l

Source: 2-MP1-1-AD1-1(1-AD1.PORT-1)-52-53 Sink: PW20-52-53 Connection Direction: Forward Segment and End Attribute: Segment Point

Step 3 On the T2000, configure the CC activation status of NE1 and NE2. For the configuration method, refer to 25.5.5 Setting the CC Activation Status.
19-94 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

19 Configuring an ATM Service

The following parameters, which are related to the CC activation status of NE1, should be configured.
l l l l l

Source: 1-CXP-1-MD1-1(Trunk1)-32-33 Sink: PW20-52-53 Connection Direction: Forward Segment and End Attribute: Segment Point CC Activate Flag: Source Activate

The following parameters, which are related to the CC activation status of NE2, should be configured.
l l l l l

Source: 2-MP1-1-AD1-1(1-AD1.PORT-1)-52-53 Sink: PW20-52-53 Connection Direction: Forward Segment and End Attribute: Segment Point CC Activate Flag: Source Activate

Step 4 On the T2000, configure the LLID of NE1 and NE2 . For the configuration method, refer to 25.5.7 Setting Local Loopback ID. The following parameters, which are related to the LLID status of NE1, should be configured.
l l l

Country Code (Hexadecimal Code): [2BYTE]00 00 Network Code (Hexadecimal Code): [2BYTE]00 00 NE Code (Hexadecimal Code): [11BYTE]00 09 00 02 00 00 00 00 00 25 00

The following parameters, which are related to the LLID status of NE2, should be configured.
l l l

Country Code (Hexadecimal Code): [2BYTE]00 00 Network Code (Hexadecimal Code): [2BYTE]00 00 NE Code (Hexadecimal Code): [11BYTE]00 09 00 02 00 00 00 00 00 15 00

Step 5 On the T2000, configure the remote loopback test on NE1, and the NE looped back is NE2. For the configuration method, refer to 25.5.6 Setting Remote Loopback Test. The following parameters, which are related to the remote loopback test of NE1, should be configured.
l l l l l l

Source: 1-CXP-1-MD1-1(Trunk1)-32-33 Sink: PW20-52-53 Connection Direction: Forward Segment and End Attribute: Segment Point Loopback Point NE: NE2 Text Result: NOTE

If NE2 need initiate the remote loopback test to loop back NE1, the remote loopback test should be configured on NE2. The configuration method is the same as that of NE1.

----End
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 19-95

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

20

Configuring an Ethernet Service

About This Chapter

On the T2000, you can configure an E-Line , an E-LAN or an E-AGGR service. The user side uses ports and the port+VLANs mode to access Ethernet services. The network side uses PWs, QinQ Links or physical ports to carry the accessed services. On the T2000, you can create a VUNI group to perform QoS settings for several Ethernet services. 20.1 Basic Concepts Before configuring the Ethernet service, familiar yourself with the E-Line service, E-LAN service and E-AGGR service, and application scenarios of these services. 20.2 Configuring an E-Line Service On the T2000, you can configure an E-Line service to provide a point-to-point Ethernet service. The equipment transports packets of certain user-side ports or packets of specific VLANs in a port to physical ports, a PW or a QinQ Link at the network side. In this way, user data packets can be transparently transmitted in a point-to-point manner. Configuration of an E-Line service includes creation, modification and deletion of the E-Line service. 20.3 Configuring an E-LAN Service On the T2000, the user can configure the multipoint-to-multipoint E-LAN service. The configuration of the E-LAN service includes the service creation, modification and deletion. 20.4 Configuring an E-AGGR Service On the T2000, the user can configure the multipoint-to-point E-AGGR service. The equipment can aggregate the Ethernet data packets accessed from multiple ports to the sink node. The configuration of the E-AGGR service includes the service creation, modification and deletion. 20.5 L2VPN Service Management In the L2VPN service management, you can search for, filter, query, and modify the L2VPN services, and view the alarms and performance events relevant to the L2VPN services. This management function provides network administrators with a method to ensure the normal running of the L2VPN services. 20.6 Configuring the V-UNI Group When one user has multiple Ethernet service access points or one Ethernet service has multiple access points, the V-UNI group can be configured. The V-UNI group can realize the overall bandwidth restriction on group members, that is, the V-UNI in the group. On the T2000, the user can create, modify and delete the V-UNI group.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-1

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

20.7 Configuration Case of the UNI-UNI E-Line Service This section uses a case to show the configuration of the UNI-UNI E-Line service, and the configuration flow. The configuration case covers the service planning and configuration of the Ethernet service. 20.8 Configuration Case of the UNI-NNI E-Line Service Carried by Ports A case is provided here to show the configuration of the UNI-NNI E-Line service carried by ports, and the configuration flow. The configuration case covers the service planning, configuration and verification of the Ethernet service. 20.9 Configuration Case of the UNI-NNI E-Line Service Carried by the PW A case is provided here to show the configuration of the UNI-NNI E-Line service carried by the PW, and the configuration flow. The configuration case covers the service planning, configuration and verification of the Ethernet service. 20.10 Configuration Case of the UNI-NNI E-Line Service Carried by the QinQ Link The configuration case illustrates how to configure a UNI-NNI E-Line service carried by the QinQ link. You can understand the configuration further by viewing the configuration flow diagram. The configuration case covers the service planning, service configuration and verification of the E-Line service. 20.11 Configuration Case of the E-LAN Service This section describes a configuration example of the E-LAN service. A configuration flow diagram is provided to describe the process of service configuration. The configuration example includes the service planning and E-LAN service configuration. 20.12 Configuration Case of the E-AGGR Service A case is provided here to show the configuration of the E-AGGR service, and the configuration flow. The configuration case covers the service planning and configuration of the E-AGGR service.

20-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

20.1 Basic Concepts

Before configuring the Ethernet service, familiar yourself with the E-Line service, E-LAN service and E-AGGR service, and application scenarios of these services. 20.1.1 E-Line Service In the topology, the EPL service is a point-to-point service. The equipment transmits the packets of a specific port or of specific VLANs of a specific port at the user side to a certain port at the user or network side, a PW or a QinQ Link at the network side. In this way, the user data can be transparently transmitted in a point-to-point manner. 20.1.2 E-LAN Service In topology, the E-LAN service is a multipoint-to-multipoint service. The equipment forwards the packets of a specific port or of specific VLANs of a specific port at the user side to multiple ports at the network side, a PW or a QinQ Link at the network side. In this way, the user data can be transparently transmitted in a multipoint-to-multipoint manner. 20.1.3 E-AGGR Service In topology, the E-AGGR service is a multipoint-to-point service. The OptiX PTN equipment can aggregate the services accessed from multiple ports to one UNI port or aggregate the services accessed from multiple ports to an NNI port. In addition, the OptiX PTN equipment can aggregate the services carried by PWs of multiple NNI ports to one UNI port. 20.1.4 V-UNI Group A V-UNI group consists of several V-UNIs. The V-UNI group is created to limit the overall bandwidth for several services.

20.1.1 E-Line Service

In the topology, the EPL service is a point-to-point service. The equipment transmits the packets of a specific port or of specific VLANs of a specific port at the user side to a certain port at the user or network side, a PW or a QinQ Link at the network side. In this way, the user data can be transparently transmitted in a point-to-point manner. According to the service transmission mode, the E-Line service can be classified into the following types:
l l l l

UNI-UNI E-Line service UNI-NNI E-Line service carried by ports UNI-NNI E-Line service carried by a PW UNI-NNI E-Line service carried by a QinQ link

UNI-UNI E-Line Service

Figure 20-1 shows the networking diagram for the UNI-UNI E-Line service. In City 1, Company A and Company B, connected to the PTN equipment, need communication between each other. The communication requirement can be met by creating a UNI-UNI E-Line service. In this case, the equipment equals a Layer 2 switch, which only exchanges data of Company A and Company B. In the uplink direction of the user side at the two ends, complex traffic
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-3

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

classification can be performed for data packets, and different QoS policies can be used according to the traffic classification. Figure 20-1 UNI-UNI E-Line service
PE UNI
PE A Company

PE Package Switching Network

B Company City1

UNI PE

UNI-NNI E-Line Service Carried by Ports

Figure 20-2 shows the networking diagram for the UNI-NNI E-Line service carried by ports. In City 1 and City 2, Company A has branches, which need communication. The communication requirement can be met by creating a UNI-NNI E-Line service carried by ports. In this case, each branch of Company A can exclusively use the UNI. Each physical port involved in the E-Line service network can be exclusively used by the E-Line service. In City 1, if small branches in Company A need service isolation, services at the same UNI can be differentiated through "port + VLANs". For a single station, in the uplink direction of the user side, complex traffic classification can be performed for data packets, and different QoS policies can be used according to the traffic classification. Figure 20-2 UNI-NNI E-Line service carried by ports

Package Switching Network

A Company A Company

City1 UNI NNI NNI UNI

City2

UNI-NNI E-Line Service Carried by a PW

Figure 20-3 shows the networking diagram for the UNI-NNI E-Line service carried by a PW. In City 1 and City 2, Company A and Company B have branches. Communication between branches of the same company is needed, but services between the two companies need to be
20-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

isolated. In this case, the communication between branches of Company A and Company B can be realized by creating a UNI-NNI E-Line service carried by a PW. Services between the two companies are isolated because different services are carried by different PWs. Hence, the company service accessed at the user side is encapsulated into a PW, and then is carried by the Tunnel. Different E-Line services of different companies are carried by different PWs, and then are transmitted to the same NNI. As a result, the number of NNIs is saved, and the bandwidth utilization is increased. In the uplink direction of the user side, the hierarchical QoS can be performed for data packets. Figure 20-3 UNI-NNI E-Line service carried by a PW

NE 1
A Company

Package Switching Network

NE2

A Company

B Company B Company

City1

UNI

NNI

NNI

UNI

City2

Tunnel PW

UNI-NNI E-Line Service Carried by a QinQ Link

In the case of the QinQ link carrying, the packets with the C-VLAN in the user-side network are added with an S-VLAN header of the transport network. The packets then travel through the transport network with two VLANs. In this way, a simple L2-VPN tunnel is provided for the user. Figure 20-4 shows the networking diagram for the UNI-NNI E-Line service carried by a QinQ link. Both Company A and Company B have branches in City 1 and City 2. Branches of each company need to communicate with each other. The traffic from the two companies must be isolated. The internal VLANs of Company A range from 1 to 100 and the internal VLANs of Company B range from 1 to 200. In this case, you can configure a UNI-NNI E-Line service carried by a QinQ link to meet the communication requirements. As different services are carried by QinQ links of different values, traffic of different companies is isolated and the VLAN resources of the packet switch network (PSN) are also saved. In this case, different packets accessed at the user side from different companies are added with different VLANs, and then carried by the same link at the network side. As the E-Line services of different companies are added with one VLAN and transported to the same port, the network-side port resources are saved and the bandwidth utilization is increased. Also as only a small number of VLANs in the PSN are used, the VLAN resources of the network are saved. To realize the QoS for the service carried by a QinQ link, configure the QinQ policy.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-5

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 20-4 UNI-NNI E-Line service carried by a QinQ link

The internal network of A Company VLAN = 1-100 A VLAN tag (VLAN = 30) is added to the packet of A Company NE 1 Packet Switching Network NE2 The internal network of A Company VLAN = 1-100

A Company

City1

B Company

The internal network of B Company A VLAN tag (VLAN = 40) VLAN = 1-200 is added to the packet of B Company

A Company

City2

B Company

QinQ Link

The internal network of B Company VLAN = 1-200

20.1.2 E-LAN Service

In topology, the E-LAN service is a multipoint-to-multipoint service. The equipment forwards the packets of a specific port or of specific VLANs of a specific port at the user side to multiple ports at the network side, a PW or a QinQ Link at the network side. In this way, the user data can be transparently transmitted in a multipoint-to-multipoint manner. Figure 20-5 shows the networking diagram for the E-LAN service. The three user side networks respectively access the carrier networks through the FE. Each user side network has its own VLAN label. The user side networks require access between each other. The user side networks can communicate with each other through the configuration of the ELAN service. On each PE node, the accessed data is forwarded through the target MAC address or target MAC address + VLAN. At the network side, the data is transparently transmitted to the opposite PE equipment through the created MPLS tunnel. In this case, the entire transport network, which exchanges different data at the user sides, equals a Layer 2 switch. In other words, the transport network is transparent to the user network. In the uplink direction of user side of each PE node, complex traffic classification can be performed for data packets, and different QoS policies can be used according to the traffic classification.

20-6

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Figure 20-5 E-LAN service

CE 1 FE NE 1 MPLS Tunnel 2 NE 3 MPLS Tunnel 1 PSN MPLS Tunnel 3 FE CE 3

NE 2 FE CE 2

PE

At present, the equipment supports the C-VLAN packet, S-VLAN+C-VLAN packet, and Ethernet packet without VLAN. At the network side, the accessed packets can be flexibly processed through the configuration of PW attributes. For example, the dropping and addition of S-VLAN is available. According to the conditions of the accessed user side network, the port attributes, service attributes, and PW attributes of the E-LAN service can be flexibly configured to meet requirements of different application scenarios. At the network-side port, the service can be carried by ports, a PW or a QinQ link for transport. In the case of the QinQ link carrying, the packets with the C-VLAN in the user-side network are added with an S-VLAN header of the transport network. The packets then travel through the transport network with two VLANs. In this way, a simple L2-VPN tunnel is provided for the user. To realize the QoS for the service carried by a QinQ link, configure the QinQ policy.

20.1.3 E-AGGR Service

In topology, the E-AGGR service is a multipoint-to-point service. The OptiX PTN equipment can aggregate the services accessed from multiple ports to one UNI port or aggregate the services accessed from multiple ports to an NNI port. In addition, the OptiX PTN equipment can aggregate the services carried by PWs of multiple NNI ports to one UNI port. Figure 20-6 shows the networking diagram for the E-AGGR service. One operator wants to construct a 3G network. Services of each Node B are aggregated and transmitted to the RNC. At each station, the service of Node B that is connected to the station is aggregated to the PW at the network side. The Tunnel that aggregates the Node B service with multiple stations is aggregated again at the station that connects the RNC, and then the service is transmitted to the RNC.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-7

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 20-6 E-AGGR service

FE FE NE 1

MPLS Tunnel 1

NE 3 GE

RNC

MPLS Tunnel 2

FE

NE 2 FE Node B

20.1.4 V-UNI Group

A V-UNI group consists of several V-UNIs. The V-UNI group is created to limit the overall bandwidth for several services. If one user or Ethernet service has several service access points, these access points can be added into a V-UNI group. In a V-UNI group, the overall bandwidth for these access points can be limited. Bandwidth parameters include the committed bandwidth, extra maximum burst buffer size, peak bandwidth and extra burst buffer size. In the case of a V-UNI group, the group members can share the bandwidth of each other, while the overall bandwidth is fixed. If member A does not reach the committed information rate (CIR), member B can use the unused bandwidth of member A. If member A and member B do not reach the CIR, but the overall bandwidth of the V-UNI group is reached, member A or member B preempts the bandwidth according to the service priority. Several V-UNIs of the same board can be configured as a V-UNI group. V-UNIs in a V-UNI group can be modified or deleted at time. Bandwidth parameters can also be modified at any time.

20-8

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

20.2 Configuring an E-Line Service

On the T2000, you can configure an E-Line service to provide a point-to-point Ethernet service. The equipment transports packets of certain user-side ports or packets of specific VLANs in a port to physical ports, a PW or a QinQ Link at the network side. In this way, user data packets can be transparently transmitted in a point-to-point manner. Configuration of an E-Line service includes creation, modification and deletion of the E-Line service. 20.2.1 Configuration Flow for the E-Line Service The E-Line service includes the UNI-UNI E-Line service, UNI-NNI E-Line service carried by ports, UNI-NNI E-Line service carried by a PW and UNI-NNI E-Line service carried by QinQ Link. The configuration flow of the E-Line service include creating network, configuring the QoS policy, configuring interfaces, configuring the control plane and configuring the E-Line service. 20.2.2 Creating a UNI-UNI E-Line Service by Using the Trail Function In an operation interface of the T2000, you can directly configure the attributes of the source and sink nodes of an E-Line service by using the T2000 trail function. In this way, an E-Line service can be fast created. 20.2.3 Creating a UNI-NNI E-Line Service by Using the Trail Function The service is accessed at the user side, and transported to one PW at the network side for carrying. In this way, user data can be transparently transmitted in a point-to-point manner. This section describes how to configure the source node, sink node, and PW attributes of the UNINNI E-Line service carried by the PW in one user interface by using the tail function. Hence, the E-line service is fast created. 20.2.4 Creating a UNI-UNI E-Line Service on a Per-NE Basis A UNI-UNI E-Line service indicates that users can be interconnected through equipment. The Ethernet data packets do not pass the network side, but are transparently transmitted at the user side. 20.2.5 Creating a UNI-NNI E-Line Service Carried by a Port The service is accessed at the user side, and transported to one port at the network side for carrying. In this way, user data can be transparently transmitted in a point-to-point manner. In this way, this port is exclusively used. 20.2.6 Creating a UNI-NNI E-Line Service Carried by a PW by Using the Trail Function The service is accessed at the user side, and transported to one PW at the network side for carrying. In this way, user data can be transparently transmitted in a point-to-point manner. For such a application, create a UNI-NNI E-Line service carried by a PW. 20.2.7 Creating a QinQ Link The QinQ link indicates that a VLAN is added on the accessed packets by using the QinQ encapsulation mode. In this way, multiple VLAN packets from the user-side network are encapsulated into a VLAN in the transport network for transport. The VLAN resources in the transport network are saved. Both the E-Line service and E-LAN service can be carried by the QinQ link at the network side. 20.2.8 Creating a UNI-NNI E-Line Service Carried by the QinQ Link The services accessed on the user side are carried by the QinQ link on the network side. Multiple VLANs of the user network are encapsulated in the QinQ mode into one VLAN in the transport network. In this way, the VLAN resources in the transport network are saved. 20.2.9 Modifying an E-Line Service on a Per-NE Basis
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-9

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

For an E-Line service, some attributes can be modified, such as the service name, MTU, userside VLAN and QoS-related parameters. For the PW and QinQ Link that carries the service, only QoS-related parameters can be modified, such as the overall bandwidth and applied policy template. 20.2.10 Deleting an E-Line Service on a Per-NE Basis When a user-to-network E-Line service carried by a PW is deleted, the PW is also deleted. 20.2.11 Modifying an E-Line Service by Using the Trail Function You can modify the name, customized attributes, remarks, and VLAN of an E-Line service by using the trail function. 20.2.12 Deleting an E-Line Service by Using the Trail Function When the E-Line service is deleted by using the trail function, the PW that carries the service is deleted at the same time.

20.2.1 Configuration Flow for the E-Line Service

The E-Line service includes the UNI-UNI E-Line service, UNI-NNI E-Line service carried by ports, UNI-NNI E-Line service carried by a PW and UNI-NNI E-Line service carried by QinQ Link. The configuration flow of the E-Line service include creating network, configuring the QoS policy, configuring interfaces, configuring the control plane and configuring the E-Line service.

UNI-UNI E-Line service

The complete process of configuring a UNI-UNI E-Line service is shown in Figure 20-7. Figure 20-7 Configuration flow for the UNI-UNI E-Line service
Required Optional

Start

Creating Network

Configuring the QoS Policy Configuring Interfaces

Configuring UNI-UNI ELine Service

Creating a V-UNI Group End

20-10

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Table 20-1 Tasks for configuring the UNI-UNI E-Line service Task 1. Creating Network 2. Configure the QoS Policy 3. Configure the user-side Interface 4. Configure the UNI-UNI E-Line Service 5. Creating a VUNI Group Remarks To create a network, you need to create NEs, configure NE data, and create fibers. The QoS policy is used for traffic management of the E-Line service. The Ethernet interface accesses services from NodeB.

To configure the UNI-UNI E-Line service, you need to specify the service ID, service name and service VLan. Set parameters such as the peak bandwidth, maximum burst size, and member ports of the V-UNI group. The V-UNI group can realize the bandwidth sharing and restriction of multiple Ethernet services.

UNI-NNI E-Line Service Carried by Ports

The complete process of configuring a UNI-NNI E-Line service carried by ports is shown in Figure 20-8.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

20-11

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 20-8 UNI-NNI E-Line service carried by ports

Required Optional

Start

Creating Network

Configuring the QoS Policy Configuring Interfaces Configuring the UNI-NNI E-Line Service Carried by Ports Configuring the UNI-NNI E-Line Service Carried by Ports Creating a V-UNI Group End

(Source NE)

(Sink NE)

Table 20-2 Tasks for configuring the UNI-UNI E-Line service carried by a port Task 1. Creating Network 2. Configure the QoS Policy 3. Configure the Interface 4. Configure the UNI-NNI E-Line Service Remarks To create a network, you need to create NEs, configure NE data, and create fibers. The QoS policy is used for traffic management of the E-Line service. The Ethernet interface accesses services from NodeB. To configure the UNI-NNI E-Line service, you need to specify the service ID, service name and service VLan.

20-12

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Task 5. Creating a VUNI Group

Remarks Set parameters such as the peak bandwidth, maximum burst size, and member ports of the V-UNI group. The V-UNI group can realize the bandwidth sharing and restriction of multiple Ethernet services.

UNI-NNI E-Line Service Carried by PWs

The complete process of configuring a UNI-NNI E-Line service carried by PWs is shown in Figure 20-9.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

20-13

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 20-9 UNI-NNI E-Line service carried by PWs

Required Optional

Start

Creating Network

Configuring the LSR ID

Configuring the networkside Interfaces Configuring the Control Plane

Configuring a Tunnel

Configuring the QoS Policy Configuring the user-side Interfaces

Configuration Case of the UNI-NNI E-Line Service Carried by the PW Configuration Case of the UNI-NNI E-Line Service Carried by the PW Creating a V-UNI Group End

(Source NE)

(Sink NE)

20-14

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Table 20-3 Tasks for configuring the UNI-NNI E-Line service carried by PWs Task 1. Creating Network 2. Configure the LSR ID 3. Configure the network-side interface 4. Configure the control plane Remarks To create a network, you need to create NEs, configure NE data, and create fibers. Configure the LSR ID of the NE and start of global label space. Set the general attributes and Layer 3 attributes (tunnel enable status and IP address) for interfaces to carry the tunnel carrying. Set the protocol parameters related to the control plane to create the tunnel.
l

To create a static MPLS tunnel to transmit the E-Line service, the parameters related to the control plane need not be set. To create a dynamic MPLS tunnel to transmit the E-Line service, you need to set the following protocol parameters: 1. Set the IGP-ISIS protocol parameters. 2. Set the MPLS-RSVP protocol parameters. To create a dynamic PW to transmit the service, you need to set the parameters related to the MPLS-LDP protocol and the IGP-ISIS protocol.

To create an IP Tunnel or GRE Tunnel to transmit the E-Line service, you need to Configuring Static Routes.

5. Configure the Tunnel

A tunnel transmits the service.

l

If an static MPLS tunnel is required, configure an MPLS tunnel in the per-NE or per-trail mode. Specify the tunnel ID, set signaling type to static, name the service, and specify the ingress node, egress node, and transit node. If a dynamic MPLS Tunnel is required, name the service, set signaling type to dynamic, and specify the source node and sink node for the tunnel. If an IP Tunnel or GRE Tunnel is required, select the source board, source port, and IP address of the sink port.

6. Configure the QoS Policy 7. Configure the user-side Interface 8. Configure the UNI-NNI E-Line service

The QoS policy is used for traffic management of the E-Line service. The Ethernet interface accesses services from NodeB.

1. Create an E-Line service: Specify the service ID, name the service, and set service VLan. 2. Configure a PW: Set the PW type, label, and tunnel type. 3. Configure QoS: Set the QoS of UNI and PW.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

20-15

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Task 6. Creating a VUNI Group

Remarks Set parameters such as the peak bandwidth, maximum burst size, and member ports of the V-UNI group. The V-UNI group can realize the bandwidth sharing and restriction of multiple Ethernet services.

UNI-NNI E-Line Service Carried by QinQ Link

The complete process of configuring a UNI-NNI E-Line service carried by QinQ Link is shown in Figure 20-10. Figure 20-10 UNI-NNI E-Line service carried by QinQ Link
Required Optional

Start

Creating Network

Configuring the QoS Policy Configuring Interfaces Configuring QinQ Link Configuration Case of the UNI-NNI E-Line Service Carried by QinQ Link Configuration Case of the UNI-NNI E-Line Service Carried by QinQ Link Creating a V-UNI Group End

(Source NE)

(Sink NE)

20-16

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Table 20-4 Tasks for configuring the UNI-NNI E-Line service carried by QinQ Link Task 1. Creating Network 2. Configure the QoS Policy 3. Configure the Interface 4. Configure QinQ Link Remarks To create a network, you need to create NEs, configure NE data, and create fibers. The E-Line policy is used for traffic management of the E-Line service. The Ethernet interface accesses services from NodeB. Create the QinQ link, and set the ID, board, port, S-Vlan, and QoS information of the QinQ link. The QinQ link encapsulates multiple VLAN packets to a VLAN on the network side for transmission. This saves the VLAN resources on the network. 5. Configure the UNI-NNI E-Line service 6. Creating a VUNI Group Set the service ID, name, VLAN, and QinQ link ID.

Set parameters such as the peak bandwidth, maximum burst size, and member ports of the V-UNI group. The V-UNI group can realize the bandwidth sharing and restriction of multiple Ethernet services.

20.2.2 Creating a UNI-UNI E-Line Service by Using the Trail Function

In an operation interface of the T2000, you can directly configure the attributes of the source and sink nodes of an E-Line service by using the T2000 trail function. In this way, an E-Line service can be fast created.

Prerequisite
You must be an NM user with "NE operator" authority or higher. If a port need be exclusively used, disable the DCN function of the port that carries the service. For details, see 2.4.4 Enabling the Port DCN.

Procedure
Step 1 Choose Trail > PTN Service > Create L2VPN E-Line Service from the Main Menu. The Create L2VPN E-Line Service dialog box is displayed. Step 2 In the Create L2VPN E-Line Service dialog box, set attributes related to the E-Line service.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

20-17

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 3 Optional: In QoS, set Bandwidth Limit to Enable. According to the network recruitment, set CIR(kbit/s) and PIR(kbit/s) for the uplink and downlink. Step 4 Optional: Click Advanced, and then set the QoS policy on the UNI side in the displayed Advanced dialog box. Step 5 Click Finish. The Operation Result window is displayed. Click Close. ----End

20.2.3 Creating a UNI-NNI E-Line Service by Using the Trail Function

The service is accessed at the user side, and transported to one PW at the network side for carrying. In this way, user data can be transparently transmitted in a point-to-point manner. This section describes how to configure the source node, sink node, and PW attributes of the UNINNI E-Line service carried by the PW in one user interface by using the tail function. Hence, the E-line service is fast created.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must complete the creation of the MPLS tunnel that carries PWs. If a port need be exclusively used, disable the DCN function of the port that carries the service. For details, see 2.4.4 Enabling the Port DCN.
20-18 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Procedure
Step 1 Choose Trail > PTN Service > Create L2VPN E-Line Service from the Main Menu. The Create L2VPN E-Line Service dialog box is displayed. Step 2 In the Create L2VPN E-Line Service dialog box, set parameters of the source and sink related to the E-Line service.

NOTE

l l

When BPDU is set to Transparently Transmitted, you cannot set MTU(byte) and VLANs. The transparently transmitted service does not support configuring the alarm performance, OAM and QoS. For VLANs, you can set several VLANs. Separate consecutive VLANs with "-", and inconsecutive VLANs with ",". For example, "1,3,5,8-10".

Step 3 Click Next and set PW-related parameters. Select the uplink tunnel and downlink tunnel that carry the PW.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

20-19

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

Protocol Type can be set to Static of Dynamic.

l l

Static: ; Static indicates that the uplink and downlink labels are manually added. Dynamic: Dynamic indicates that the MPLS-LDP protocol distributes the PW labels. Ethernet: The original C/SVlan tag of user packets is encapsulated in a PW without any change and then is transparently transmitted to the downstream stations. Ethernet Tagged Mode: A VLAN tag is stuck to user packets. To stick the VLAN tag, set Request VLAN in Advanced Attributes.

PW Type can be set to Ethernet or Ethernet Tagged Mode.

l l

Step 4 Optional: In QoS, set Bandwidth Limit to Enable. According to the network recruitment, set CIR(kbit/s) and PIR(kbit/s) for the uplink and downlink. Step 5 Optional: Click Advanced, and then set the QoS on the UNI side, QoS policy of the PW, EXP, and LSP Mode in the displayed Advanced dialog box. Step 6 Click OK. Step 7 Click Finish. The Operation Result window is displayed. Click Close. ----End

20.2.4 Creating a UNI-UNI E-Line Service on a Per-NE Basis

A UNI-UNI E-Line service indicates that users can be interconnected through equipment. The Ethernet data packets do not pass the network side, but are transparently transmitted at the user side.
20-20 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Prerequisite
You must be an NM user with "NE operator" authority or higher. If a port need be exclusively used, disable the DCN function of the port that carries the service. For details, see 2.4.4 Enabling the Port DCN.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Ethernet Service Management > E-Line Service from Function Tree. Step 2 Click the UNI tab and click New. The New E-Line Service dialog box is displayed.

Step 3 Set parameters in the dialog box.

NOTE

When BPDU is set to Transparently Transmitted, you cannot set MTU(byte) and VLANs. The transparently transmitted service does not support configuring the alarm performance, OAM and QoS. For Direction, select UNI-UNI. For VLANs, you can set several VLANs. Separate consecutive VLANs with "-", and inconsecutive VLANs with ",". For example, "1,3,5,8-10".

Step 4 Optional: Click Configure QoS. The Configure QoS dialog box displayed. Step 5 Optional: Click the UNI tab in the Configure QoS dialog box. Set Default Forwarding Priority and Default Packet Relabeling Color for ports. Click OK. The New E-Line Service dialog box is displayed.
NOTE

If you select Enabled for Bandwidth Limit, you can set CIR (kbit/s), PIR (kbit/s). You can also select the QoS policy in Policy.

Step 6 Click OK. A dialog box is displayed for confirmation. Step 7 Optional: Click the Maintenance Association tab and MEP Point tab to set OAM-related parameters.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-21

20 Configuring an Ethernet Service

NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

Before setting OAM-related parameters, configure the MD.

----End

20.2.5 Creating a UNI-NNI E-Line Service Carried by a Port

The service is accessed at the user side, and transported to one port at the network side for carrying. In this way, user data can be transparently transmitted in a point-to-point manner. In this way, this port is exclusively used.

Prerequisite
You must be an NM user with "NE operator" authority or higher. If a port need be exclusively used, disable the DCN function of the port that carries the service. For details, see 2.4.4 Enabling the Port DCN.

Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from Function Tree. Step 2 Click the UNI tab and click New. The New E-Line Service dialog box is displayed.

Step 3 Set parameters in the dialog box.

NOTE

l l l l

When BPDU is set to Transparently Transmitted, you cannot set MTU(byte) and VLANs. The transparently transmitted service does not support configuring the alarm performance, OAM and QoS. For Direction, select UNI-NNI. For Bearer Type, select Port. For VLANs, you can set several VLANs. Separate consecutive VLANs with "-", and inconsecutive VLANs with ",". For example, "1,3,5,8-10".

20-22

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Step 4 Optional: Click Configure QoS. The Configure QoS dialog box displayed. Step 5 Optional: Click the UNI tab in the Configure QoS dialog box. Set Default Forwarding Priority and Default Packet Relabeling Color for ports. Click OK. The New E-Line Service dialog box is displayed.
NOTE

If you select Enabled for Bandwidth Limit, you can set CIR (kbit/s), PIR (kbit/s). You can also select the QoS policy in Policy.

Step 6 Click OK. A dialog box is displayed for confirmation. Step 7 Optional: Click the Maintenance Association tab and MEP Point tab to set OAM-related parameters.
NOTE

Before setting OAM-related parameters, configure the MD.

----End

20.2.6 Creating a UNI-NNI E-Line Service Carried by a PW by Using the Trail Function
The service is accessed at the user side, and transported to one PW at the network side for carrying. In this way, user data can be transparently transmitted in a point-to-point manner. For such a application, create a UNI-NNI E-Line service carried by a PW.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must complete the creation of the MPLS tunnel that carries PWs. If a port need be exclusively used, disable the DCN function of the port at the UNI side. For details, see 2.4.4 Enabling the Port DCN.

Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from Function Tree. Step 2 Click the UNI tab and click New. The New E-Line Service dialog box is displayed.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

20-23

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 3 Set parameters in the dialog box.

NOTE

l l l

When BPDU is set to Transparently Transmitted, you cannot set MTU(byte) and VLANs. The transparently transmitted service does not support configuring the alarm performance, OAM and QoS. For Direction, select UNI-NNI. Service Tag Role can be set to User orService. When Service Tag Role is set to Service, only one VLAN ID can be set for the VLANs field.
l l

User: The outer C/SVlan tag of user packets is used as the user VLAN tag. When the packets are forwarded, the packet forwarding is based on the user VLAN tag. Service: The outer C/SVlan tag of user packets is used as the service VLAN tag. When the packets are forwarded, the packet forwarding is not based on the service VLAN tag.

l l

For Bearer Type, select PW. For VLANs, you can set several VLANs. Separate consecutive VLANs with "-", and inconsecutive VLANs with ",". For example, "1,3,5,8-10".

Step 4 Click Configure PW. The Configure PW dialog box is displayed. In the dialog box, set PWrelated parameters.

20-24

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

NOTE

For PW ID, select the PW ID set in Step 3. PW Type can be set to Ethernet or Ethernet Tagged Mode.
l l

Ethernet: The original C/SVlan tag of user packets is encapsulated in a PW without any change and then is transparently transmitted to the downstream stations. Ethernet Tagged Mode: A VLAN tag is stuck to user packets. To stick the VLAN tag, set Request VLAN in Advanced Attributes.

Step 5 Click OK and close the Configure PW dialog box. Step 6 Click Configure QoS. The Configure QoS dialog box displayed. Step 7 In the UNItab, set Policy, Default Forwarding Priority and Default Packet Relabeling Color for the ingress direction. Step 8 Click the PW tab. Set EXP in the ingress direction and LSP Mode in the egress direction. Click OK. The New E-Line Service dialog box is displayed.
NOTE

If you select Enabled for Bandwidth Limit, you can set CIR (kbit/s) and PIR (kbit/s) for the PW. You can also select the QoS policy in Policy.

Step 9 Click OK to finish the creation. Step 10 Optional: Click the Maintenance Association tab and MEP Point tab to set OAM-related parameters.
NOTE

Before setting OAM-related parameters, configure the MD.

----End
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-25

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

20.2.7 Creating a QinQ Link

The QinQ link indicates that a VLAN is added on the accessed packets by using the QinQ encapsulation mode. In this way, multiple VLAN packets from the user-side network are encapsulated into a VLAN in the transport network for transport. The VLAN resources in the transport network are saved. Both the E-Line service and E-LAN service can be carried by the QinQ link at the network side.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The Layer 2 attributes of the port on the QinQ link must be set and the encapsulation mode must be the QinQ mode. If the QoS parameters of the QinQ link need be configured, the QinQ policy must be configured first.

Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Service Management > QinQ Link from the Function Tree. Step 2 Click New. The New QinQ Link window is displayed. Step 3 Click the General Attributes tab. Set QinQ Link ID, Board, Port and S-Vlan ID. Step 4 Click the QoS tab to set the QoS-related parameters.
NOTE

If Bandwidth Limit is set to Enabled, you can set CIR (kbit/s) and PIR (kbit/s) for the QinQ Link. You can also select a QinQ policy in Policy. Before selecting a policy, create a policy.

Step 5 Click OK. ----End

20.2.8 Creating a UNI-NNI E-Line Service Carried by the QinQ Link

The services accessed on the user side are carried by the QinQ link on the network side. Multiple VLANs of the user network are encapsulated in the QinQ mode into one VLAN in the transport network. In this way, the VLAN resources in the transport network are saved.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The QinQ link must be created for the network-side ports.

Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Step 2 Click the UNI tab and then click New. The New E-Line Service dialog box is displayed.
20-26 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Step 3 Set each parameter in the dialog box.

NOTE

l l l l

When BPDU is set to Transparently Transmitted, you cannot set MTU(byte) and VLANs. The transparently transmitted service does not support configuring the alarm performance, OAM and QoS. Set Direction to UNI-NNI. Set Bearer Type to QinQ Link. Select a created QinQ link in QinQ Link ID.

Step 4 Optional: Click Configure QoS. The Configure QoS dialog box displayed. Step 5 Optional: Click the UNI tab in the Configure QoS dialog box. Set Policy, Default Forwarding Priority and Default Packet Relabeling Color for ports. Click OK. The New E-Line Service dialog box is displayed. Step 6 Click OK. The Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Step 7 Click the QoS tab and click the QinQ Link tab. Step 8 Select the QinQ policy for the ingress and egress directions of the QinQ link. Click Apply. The Operation Result dialog box is displayed, indicating that the operation is successful.
NOTE

Before selecting the policy, the policy should be created. If Bandwidth Limit is set to enabled, CIR (kbit/ s) and Peak Bandwidth (kbit/s) can be set.

Step 9 Click Close, ----End

20.2.9 Modifying an E-Line Service on a Per-NE Basis

For an E-Line service, some attributes can be modified, such as the service name, MTU, userside VLAN and QoS-related parameters. For the PW and QinQ Link that carries the service, only QoS-related parameters can be modified, such as the overall bandwidth and applied policy template.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-27

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

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

Context

CAUTION
If you modify the E-Line service, the E-Line service may be interrupted.

Procedure
Step 1 Select the NE from NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from Function Tree. Step 2 Select the E-Line service to be modified. The Service Name and MTU can be modified. After the modification is complete, click Apply.
NOTE

After the service transmitted in a PW is created, the MTU value of the service cannot be changed. After the service transmitted through a port or in the QinQ is created, however, the MTU value of the service can be changed. The reason is as follows: In the case of the service transmitted in a PW, the MTU value needs to be negotiated when the PW is created and cannot be changed after creation.

Step 3 Click the UNI tab. In the tab, you can modify VLANS of ports. After the modification is complete, click Apply. A dialog box is displayed for confirmation, click OK. Step 4 Click the QoS tab. The QoS-related parameters for the UNI port, PW and QinQ Link can be modified. After the modification is complete, click Apply. A dialog box is displayed for confirmation, click OK. ----End

20.2.10 Deleting an E-Line Service on a Per-NE Basis

When a user-to-network E-Line service carried by a PW is deleted, the PW is also deleted.

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

Context

CAUTION
If you delete the E-Line service, the E-Line service is interrupted.

20-28

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Procedure
Step 1 Select the NE from NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Step 2 Select the E-Line service to be deleted and click Delete. A dialog box is displayed for confirmation. Click OK. A dialog box is displayed, indicating that the E-Line service is successfully deleted. Click Close. ----End

20.2.11 Modifying an E-Line Service by Using the Trail Function

You can modify the name, customized attributes, remarks, and VLAN of an E-Line service by using the trail function.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must complete the creation of the L2VPN service.

Procedure
Step 1 Choose Trail > PTN Service > L2VPN Service Mnagement from the Main Menu. Step 2 Select the E-Line service to be modified. Choose Details from the shortcut menu, and modify the basic attributes of the L2VPN service in the displayed Details dialog box. Step 3 Click OK. The Operation Result window is displayed. Click Close. Step 4 Optional: Click the UNI tab. In the tab, you can modify VLANS of ports. After the modification is complete, click Apply. A dialog box is displayed for confirmation, click OK. Step 5 Optional: Click the UNI QoS tab. The QoS-related parameters for the UNI port can be modified. After the modification is complete, click Apply. A dialog box is displayed for confirmation, click OK. Step 6 Optional: Click the PW QoS tab. The QoS-related parameters for the PW can be modified. After the modification is complete, click Apply. A dialog box is displayed for confirmation, click OK. ----End

20.2.12 Deleting an E-Line Service by Using the Trail Function

When the E-Line service is deleted by using the trail function, the PW that carries the service is deleted at the same time.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must complete the creation of the L2VPN service.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-29

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 Choose Trail > PTN Service > L2VPN Service Mnagement from the Main Menu. Step 2 Select the E-Line service to be deleted and click Delete. A dialog box is displayed for confirmation. Click OK. A dialog box is displayed, indicating that the E-Line service is successfully deleted. Click Close. ----End

20.3 Configuring an E-LAN Service

On the T2000, the user can configure the multipoint-to-multipoint E-LAN service. The configuration of the E-LAN service includes the service creation, modification and deletion. 20.3.1 Configuration Flow for E-LAN Service The configuration flow of the E-LAN service include creating network, configuring the QoS policy, configuring interfaces, configuring the control plane, configuring MPLS tunnel and configuring E-LAN service. 20.3.2 Creating a QinQ Link The QinQ link indicates that a VLAN is added on the accessed packets by using the QinQ encapsulation mode. In this way, multiple VLAN packets from the user-side network are encapsulated into a VLAN in the transport network for transport. The VLAN resources in the transport network are saved. Both the E-Line service and E-LAN service can be carried by the QinQ link at the network side. 20.3.3 Creating an E-LAN Service On the T2000, the E-LAN service can be created. Multiple types of E-LAN services can be realized by configuring the UNI and NNI ports. The NNI port can carry the service by using the port, PW or QinQ link. 20.3.4 Managing the Blacklist Managing the blacklist can prevent the illegal packets from the network side or user side from attacking the equipment. Hence, the equipment can run stably in the network. Managing the blacklist includes querying the blacklist, creating the blacklist, and deleting the blacklist. 20.3.5 Setting the Broadcast Storm Suppression The broadcast storm suppression function can restrain the broadcast traffic on the port that carries the ELAN service. Hence, the bandwidth resource of the equipment can be properly used. Setting the broadcast storm suppression function includes enabling the broadcast storm suppression and setting the broadcast suppression threshold. 20.3.6 Modifying E-LAN Service The attributes of the E-LAN service can be partially modified, including the service name, MTU, UNI and NNI ports, and QoS policy template used at the service access point. 20.3.7 Deleting E-LAN Service When configuring the E-LAN service, configure the PW that carries the service and the QoS for the service at the same time. When the E-LAN service is deleted, the PW that carries the service and related QoS parameters are deleted at the same time.

20-30

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

20.3.1 Configuration Flow for E-LAN Service

The configuration flow of the E-LAN service include creating network, configuring the QoS policy, configuring interfaces, configuring the control plane, configuring MPLS tunnel and configuring E-LAN service. Figure 20-11 shows the flow for configuring an E-LAN service. Figure 20-11 Flow diagram for configuring the E-LAN service
Required Optional

Start

Creating Network

Configuring the QoS Policy Configuring Interfaces

Configuring E-LAN Service Creating a V-UNI Group End

Configuring the Control Plane Configuring an MPLS Tunnel Configuring E-LAN Service Creating a V-UNI Group End

Configuring QinQ Link Configuring E-LAN Service Creating a V-UNI Group End

The columns in the figure shows the three sub processes. From left to right, the sub systems indicate the NNI carried by ports, NNI carried by PWs, and NNI carried by QinQ Link respectively.

Before configuring the E-LAN service, you should complete configuring network (including 1 Creating NEs, Links, and Topology Subnets, 2 Configuring Communications, 3 Configuring the NE Time, 4 Configuring Clocks, and 7 Configuring the Equipment-Level Protection), 9 Configuring the QoS Policy, and 10.3 Configuring Ethernet Interfaces. Perform the following operations according to the NNI bearer type.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

20-31

20 Configuring an Ethernet Service

l

OptiX iManager T2000 Operation Guide for PTN NE Management

In the case that the operations mentioned above are completed, when the port is set to Bearer Type, the E-LAN service can be configured. When the PW is set to Bearer Type, the MPLS tunnel need be configured. See the following contents according to the MPLS tunnel type.

When the static MPLS tunnel is used, the MPLS tunnel can be configured on a per-NE basis or by using the trail function. See 13.3.2 Creating a Static MPLS Tunnel by Using the Trail Function and 13.4.2 Creating an MPLS Tunnel on a Per-NE Basis. When the static MPLS tunnel is used, 8 Configuring the Control Plane can be skipped. When the dynamic MPLS tunnel is used, see 13.3.1 Creating a Dynamic MPLS Tunnel and the FRR Protection by Using the Trail Function.

If the network side is carried by the QinQ Link, 20.3.2 Creating a QinQ Link need be complete.

When configuring the E-LAN service, see 20.3 Configuring an E-LAN Service.

20.3.2 Creating a QinQ Link

The QinQ link indicates that a VLAN is added on the accessed packets by using the QinQ encapsulation mode. In this way, multiple VLAN packets from the user-side network are encapsulated into a VLAN in the transport network for transport. The VLAN resources in the transport network are saved. Both the E-Line service and E-LAN service can be carried by the QinQ link at the network side.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The Layer 2 attributes of the port on the QinQ link must be set and the encapsulation mode must be the QinQ mode. If the QoS parameters of the QinQ link need be configured, the QinQ policy must be configured first.

Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Service Management > QinQ Link from the Function Tree. Step 2 Click New. The New QinQ Link window is displayed. Step 3 Click the General Attributes tab. Set QinQ Link ID, Board, Port and S-Vlan ID. Step 4 Click the QoS tab to set the QoS-related parameters.
NOTE

If Bandwidth Limit is set to Enabled, you can set CIR (kbit/s) and PIR (kbit/s) for the QinQ Link. You can also select a QinQ policy in Policy. Before selecting a policy, create a policy.

Step 5 Click OK. ----End

20-32 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

20.3.3 Creating an E-LAN Service

On the T2000, the E-LAN service can be created. Multiple types of E-LAN services can be realized by configuring the UNI and NNI ports. The NNI port can carry the service by using the port, PW or QinQ link.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must complete the correct configuration of the port attributes. You must complete the creation of the MPLS tunnel that carries the PW. If the port need be exclusively used, disable the DCN function of the port that carries the service. For the operation steps, see 2.4.4 Enabling the Port DCN. If the service need be carried by a QinQ link, you must configure a QinQ link first. If a QoS policy is required for configuring the QoS, you must create a QoS policy first.

CAUTION
l l

The ML-PPP line should not carry any E-LAN service. On the network side, the E-LAN service does not support the LMSP, FRR, MPLS APS, and LAG protection.

Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 Click New to display the New E-LAN Service dialog box. Then, set Service ID, Service Name and MTU(byte).

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

20-33

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

Self-Learning MAC Address can be set to enabled or disabled. When Self-Learning MAC Address is set to enabled, the bridge supports the MAC address self-learning, the forwarding table items are generated through the MAC address self-learning. You can also manually configure the static MAC address forwarding table items. When Self-Learning MAC Address is set to disabled, the bridge does not support the MAC address self-learning and you can manually configure the static MAC address forwarding table items only. MAC Address Learning Mode can be set to SVL or IVL. SVL indicates the shared VLAN learning. All VLANs share a MAC address forwarding table. Any MAC address is unique in the forwarding table. IVL indicates the independent VLAN learning. The forwarding tables for different VLANs are independent from each other. It is acceptable that the MAC address forwarding tables for different VLANs have the same MAC address. Tag Type can be set to C-Awared, S-Awared or Tag Transparent. C-Awared corresponds to the accessed service packets with one C-VLAN. S-Awared corresponds to the accessed service packets with one C-VLAN and one S-VLAN. Tag Transparent corresponds to the accessed service packets without any VLAN. Now, the S-Awared cannot be supported. Service Tag Role can be set to User orService. When Service Tag Role is set to Service, MAC Address Learning Mode can be set to SVL, and only one VLAN ID can be set for the VLANs field.
l l

User: The outer C/SVlan tag of user packets is used as the user VLAN tag. When the packets are forwarded, the packet forwarding is based on the user VLAN tag. Service: The outer C/SVlan tag of user packets is used as the service VLAN tag. When the packets are forwarded, the packet forwarding is not based on the service VLAN tag.

Step 3 Click OK to display the Operation Result dialog box, which indicates that the operation is successful. Then, click Close. Step 4 Click the UNI tab. Then, click Configuration to display the Configure Port dialog box.
20-34 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Step 5 In the Available Ports list, select the port. Then, click Ports list.

to add the port to the Selected

Step 6 In the Selected Ports list, set VLANs of the port, and then click OK. Step 7 Click the NNI tab. l l If configuring the NNI interface carried by the port, click the Port tab. See Step 4 to Step 6 to add and configure the NNI port. Then, click OK. If configuring the NNI interface carried by the PW, click the PW tab. Click New, and set the parameters related to the PW. Then, click OK.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

20-35

20 Configuring an Ethernet Service

NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

PW Type can be set to Ethernet or Ethernet Tagged Mode.

l l

Ethernet: The original C/SVlan tag of user packets is encapsulated in a PW without any change and then is transparently transmitted to the downstream stations. Ethernet Tagged Mode: A VLAN tag is stuck to user packets. To stick the VLAN tag, set Request VLAN in Advanced Attributes.

If configuring the NNI interface carried by the QinQ link, click the QinQ Link tab. 1. 2. 3. Click Add. The QinQ Link Management window is displayed. Select a QinQ link ID and click OK. Click Apply. The Operation Result dialog box is displayed, indicating that the operation is successful. Click Close,

NOTE

The services carried by the QinQ link can not support to create MP.

Step 8 Click the Split Horizon Group tab. Then, click New to display the New Split Horizon Group dialog box. Step 9 Configure the split horizon group id, and add the interface that need be added into the split horizon group to the Selected Interfaces pane. Click OK to display the Operation Result dialog box, which indicates that the operation is successful. Then, click Close. Step 10 Click the MAC Address Learning Parameters tab. Set Aging Ability, Aging Time(min), Address Table Specified Capacity, Address Detection Upper Threshold(%) and Address Detection Lower Threshold(%).
NOTE

Address Detection Upper Threshold(%) and Address Detection Upper Threshold(%) indicate the upper threshold and lower threshold of the self-learning capacity. If the upper threshold is crossed, the equipment reports an alarm. If the lower threshold is crossed, the alarm is cleared.

Step 11 Click Apply. The Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Step 12 Click the Unknown Frame Processing tab. Set the processing modes for the unicast frames and multicast frames. The default value is broadcast.
20-36 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Step 13 Click Apply. The Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Step 14 Optional: Click QoS tab. Set the parameters of the QoS. l Click the UNI tab. Set Default Forwarding Priority and Default Packet Relabeling Color of the port. Click Apply to display the Operation Result dialog box, which indicates that the operation is successful. Then, click Close. Click the PW tab. Set EXP and LSP Mode. Click Apply to display the Operation Result dialog box, which indicates that the operation is successful. Then, click Close.
NOTE

If Bandwidth Limit is set to enabled, CIR (kbit/s) and PIR (kbit/s) can be set. The QoS policy can also be selected from Policy. Before selecting the policy, the policy should be created.

Click the QinQ Link tab. Enable the bandwidth limit and select the QinQ policy for the ingress and egress directions of the QinQ link. Click Apply. The Operation Result dialog box is displayed, indicating that the operation is successful. Click Close,
NOTE

Before selecting the policy, the policy should be created. If Bandwidth Limit is set to enabled, CIR (kbit/s) and PIR (kbit/s) can be set.

Step 15 Optional: Click the Static MAC Address tab. Manually bind the VLAN ID, MAC Address and Egress Interface.
NOTE

Set the VLAN ID only when MAC Address Learning Mode is set IVL.

Step 16 Optional: Click the Maintenance Association tab and the MEP Point tab. Set the OAM-related parameters.
NOTE

Before setting OAM-related parameters, configure the MD.

----End

20.3.4 Managing the Blacklist

Managing the blacklist can prevent the illegal packets from the network side or user side from attacking the equipment. Hence, the equipment can run stably in the network. Managing the blacklist includes querying the blacklist, creating the blacklist, and deleting the blacklist.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must complete the creation of E-LAN services.

Context
After the MAC address blacklist is created on a port that carries the ELAN service, if the destination MAC or source MAC information carried by a packet enters this port is consistent with a random MAC address created in the blacklist, this packet is discarded.
NOTE

The MAC address that is added to the static route should not be added to the MAC address of the blacklist.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

20-37

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 In the Disabled MAC Address tab page, select Query to query the added MAC address of the blacklist. Step 3 Click New and the Create Disabled MAC Address dialog box is displayed. Set VLAN ID and MAC Address.

Step 4 Click OK. Step 5 Optional: In the interface, select the information of a MAC address, and then click Delete. Hence, the MAC address information is deleted from the blacklist. ----End

20.3.5 Setting the Broadcast Storm Suppression

The broadcast storm suppression function can restrain the broadcast traffic on the port that carries the ELAN service. Hence, the bandwidth resource of the equipment can be properly used. Setting the broadcast storm suppression function includes enabling the broadcast storm suppression and setting the broadcast suppression threshold.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must complete the creation of E-LAN services.

Context
The broadcast suppression is enabled on a port that carries the ELAN service. In this case, when the packets that enter this port are unknown unicast packets, unknown multicast packets, or broadcast packets, if the traffic exceeds the broadcast suppression threshold set for the port, the packets that exceeds the bandwidth are discarded.
NOTE

Currently, the equipment supports the broadcast suppression function for the UNI only. The broadcast suppression function for the NNI is not supported.

20-38

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 In the UNI tab page, select the corresponding port. Double-click the Enabled Broadcast Packet Suppression parameter field, and then select Enabled.

Step 3 Double-click the Broadcast Suppression Threshold parameter field, and then set the threshold value. Step 4 Click Apply. ----End

20.3.6 Modifying E-LAN Service

The attributes of the E-LAN service can be partially modified, including the service name, MTU, UNI and NNI ports, and QoS policy template used at the service access point.

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

Context

CAUTION
If you modify the E-AN service, the E-LAN service may be interrupted.

Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 Select the E-LAN service to be modified. The service name and MTU can be modified. After the modification is complete, click Apply. Step 3 Click the UNI tab. Select the port to be modified. Click Configuration. After the attributes are modified, click OK to return to the UNI tab. Then, click Apply. Step 4 Click Port in the NNI tab. Click Configuration. After the attributes are modified, click OK to return to the NNItab. Click Apply.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-39

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 5 Click the QoS tab. The QoS parameters for the UNI port, PW and QinQ Link can be modified. After the modification is complete, click Apply. A dialog box is displayed for confirmation, click OK. ----End

20.3.7 Deleting E-LAN Service

When configuring the E-LAN service, configure the PW that carries the service and the QoS for the service at the same time. When the E-LAN service is deleted, the PW that carries the service and related QoS parameters are deleted at the same time.

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

Context

CAUTION
If you delete the E-LAN service, the E-LAN service is interrupted.

Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 Select the E-LAN service to be deleted and click Delete. A prompt dialog box is displayed. Click OK. ----End

20.4 Configuring an E-AGGR Service

On the T2000, the user can configure the multipoint-to-point E-AGGR service. The equipment can aggregate the Ethernet data packets accessed from multiple ports to the sink node. The configuration of the E-AGGR service includes the service creation, modification and deletion. 20.4.1 Configuration Flow for the E-AGGR Service Configuring an E-AGGR service contains creating the network, and configuring the QoS policy, interfaces, control plane, MPLS tunnel, and E-AGGR service. 20.4.2 Creating an E-AGGR Service on a Per-NE Basis On the T2000, the creation of an E-AGGR service can be complete in one interface. The equipment supports the multipoint-to-point service aggregation, and supports the service aggregation from the NNI carried by multiple PWs to one UNI port. 20.4.3 Modifying an E-AGGR Service on a Per-NE Basis The E-AGGR service supports the modification of some attributes, such as the service name, access port at the user side, VLAN table at the user side, and QoS policy template at the service access point.
20-40 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

20.4.4 Deleting an E-AGGR Service on a Per-NE Basis When the E-AGGR service is configured, the PW that carries the service, VLAN switching table items, and QoS and OAM parameters of the service, are configured at the same time. When the E-AGGR service is deleted, the PW that carries the service, VLAN switching table items, and related QoS and OAM parameters, are deleted at the same time.

20.4.1 Configuration Flow for the E-AGGR Service

Configuring an E-AGGR service contains creating the network, and configuring the QoS policy, interfaces, control plane, MPLS tunnel, and E-AGGR service. Figure 20-12 shows the flow for configuring an E-AGGR service. Figure 20-12 Configuration flow for the E-AGGR service
Required Optional

Start

Creating Network

Configuring the QoS Policy Configuring Interfaces

Configuring a UNIs-UNI E-AGGR Service for NEs

Configuring a UNIs-NNI E-AGGR Service for NEs

Configuring the Control Plane Configuring an MPLS Tunnel

Creating a V-UNI Group End

Configuring a NNIs-UNI E-AGGR Service for NEs

Creating a V-UNI Group End

Configuring a UNIs-NNI E-AGGR Service for NEs

Configuring a NNIs-UNI E-AGGR Service for NEs

Creating a V-UNI Group End

The columns in the figure shows the three sub processes, which are for the configuration of a UNI-UNI E-AGGR service, the configuration of an E-AGGR service carried by ports on the NNI side, and the configuration of an E-AGGR service carried by PWs on the NNI side from the left to right. Before configuring the UNI-UNI E-AGGR service, you should complete configuring network (including 1 Creating NEs, Links, and Topology Subnets, 2 Configuring Communications, 3 Configuring the NE Time, 4 Configuring Clocks, and 7 Configuring the Equipment-Level Protection), 9 Configuring the QoS Policy, 10 Configuring
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-41

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Interfaces, 8 Configuring the Control Plane, and 13 Configuring an MPLS Tunnel. When configuring the E-AGGR service, see 20.4 Configuring an E-AGGR Service. When the MPLS tunnel is configured, see the following contents according to the MPLS tunnel type.
l

When the static MPLS tunnel is used, the MPLS tunnel can be configured on a per-NE basis or by using the trail function. See 13.3.2 Creating a Static MPLS Tunnel by Using the Trail Function and 13.4.2 Creating an MPLS Tunnel on a Per-NE Basis. When the dynamic MPLS tunnel is used, see 13.3.1 Creating a Dynamic MPLS Tunnel and the FRR Protection by Using the Trail Function.

20.4.2 Creating an E-AGGR Service on a Per-NE Basis

On the T2000, the creation of an E-AGGR service can be complete in one interface. The equipment supports the multipoint-to-point service aggregation, and supports the service aggregation from the NNI carried by multiple PWs to one UNI port.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must complete the correct configuration of port attributes. You must complete the creation of the MPLS tunnel that carries the PW. If a port need be exclusively used, disable the DCN function of the port that carries the service. For detail, see 2.4.4 Enabling the Port DCN.

Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > Ethernet Service Management > E-AGGR Service from the Function Tree. Step 2 Click New to display the New E-AGGR Service dialog box. Then, configure Service ID, Service Name and MTU(byte). Step 3 Click the UNI tab. Then, click Configuration to display the Configure Port dialog box. Step 4 In the Available Port list, select the desired port and click Selected Port list.
NOTE

to add the port to the

The port of the E-AGGR service does not support the S-Aware attribute.

Step 5 In the Selected Port list, configure Location and VLANs of the port, and then click OK.
NOTE

Location can be set to the source end or the sink end. Multiple source ends can be set, but only one sink end can be set. Otherwise, the E-AGGR service cannot be correctly configured.

Step 6 Click the NNI tab. l To configure the NNI interface carried by the port, click the Port tab. When adding and setting the port at the NNI side, see Step 3 and Step 5. Then, click OK.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

20-42

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

To configure the NNI interface carried by the PW, click the PW tab. Click New to set related parameters of the PW. Then, click OK.
NOTE

l l

For PW Signaling Type, select Dynamic or Static. Dynamic indicates that the LDP signaling is used to create a PW. For PW Type, select Ethernet or Ethernet Tagged Mode.

Step 7 Select VLAN Forwarding Table Item. Click New to display the New VLAN Forwarding Table Item window to set the forwarding attributes. Then, click OK.

NOTE

The service is forwarded based on VLAN, and thus the forwarding attributes should be set in VLAN Forwarding Table Item from each source interface to sink interface.

Step 8 Click OK to display the confirmation dialog box. Then, close the dialog box. Step 9 Optional: Click QoS tab. Set the parameters of the QoS. l l Click the UNI tab to set Default Forwarding Priority and Default Packet Relabeling Color. Click the PW tab to set EXP and LSP Mode.
NOTE

If Bandwidth Limit is set to enabled, CIR (kbit/s) and PIR (kbit/s) can be set. The QoS policy can also be selected from Policy.

Step 10 Optional: Click the Maintenance Association tab and the MEP Point tab. Set the OAM-related parameters.
NOTE

Before setting OAM-related parameters, configure the MD.

----End

20.4.3 Modifying an E-AGGR Service on a Per-NE Basis

The E-AGGR service supports the modification of some attributes, such as the service name, access port at the user side, VLAN table at the user side, and QoS policy template at the service access point.

Prerequisite
You must be an NM user with "NE operator" authority or higher.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-43

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Context

CAUTION
If you modify the E-AGGR service, the E-AGGR service may be interrupted.

Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > Ethernet Service Management > E-AGGR Service from the Function Tree. Step 2 Select the E-AGGR service to modify the service name and MTU. After the modification, click Apply. Step 3 Click the UNI tab to select the port to be modified. Click Configuration. After the modification of attributes, click OK to return to the UNI tab. Then, click Apply. Step 4 Select the Port tab from the NNI tab. Click Configuration. After the modification of attributes, click OK to return to the NNI tab. Then, click Apply. Step 5 Click the QoS tab to modify the UNI port and QoS parameters of the PW. After the modification, click Apply. A dialog box is displayed for confirmation, click OK. ----End

20.4.4 Deleting an E-AGGR Service on a Per-NE Basis

When the E-AGGR service is configured, the PW that carries the service, VLAN switching table items, and QoS and OAM parameters of the service, are configured at the same time. When the E-AGGR service is deleted, the PW that carries the service, VLAN switching table items, and related QoS and OAM parameters, are deleted at the same time.

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

Context

CAUTION
If you delete the E-AGGR service, the E-AGGR service is interrupted.

Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > Ethernet Service Management > E-AGGR Service from the Function Tree.
20-44 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Step 2 Select the E-AGGR service to be deleted and click Delete. A dialog box is displayed for confirmation. Click OK. The Operation Result dialog box is displayed, indicating that the EAGGR service is successfully deleted. Click Close. ----End

20.5 L2VPN Service Management

In the L2VPN service management, you can search for, filter, query, and modify the L2VPN services, and view the alarms and performance events relevant to the L2VPN services. This management function provides network administrators with a method to ensure the normal running of the L2VPN services. 20.5.1 Searching for L2VPN Services When you search for discrete L2VPN services on the network, the T2000 saves and displays the L2VPN services that are searched out. 20.5.2 Filtering L2VPN Services You can query L2VPN services according to certain filter criteria. The T2000 displays the L2VPN services that meet the filter criteria. 20.5.3 Modifying the Attributes of an L2VPN Service You can modify the attributes of an L2VPN service, namely service name, customized information, remarks, and other information. 20.5.4 Configuring a UNI In the L2VPN Service Management window, you can modify and delete the relevant attributes of a UNI. 20.5.5 Configuring UNI QoS In the L2VPN Service Management window, you can set and query the parameters related to UNI QoS. 20.5.6 Configuring a PW In the L2VPN Service Management window, you can query the information about a PW, and enable or disable the PW. 20.5.7 Configuring PW QoS In the L2VPN Service Management window, you can set and query the parameters related to PW QoS. 20.5.8 Viewing the Alarms Related to an L2VPN Service You can query the alarms related to an L2VPN service to check whether the L2VPN service has any potential fault. 20.5.9 Viewing the Performance Data Related to an L2VPN Service You can query the performance data related to an L2VPN service to check the running status of the L2VPN service.

20.5.1 Searching for L2VPN Services

When you search for discrete L2VPN services on the network, the T2000 saves and displays the L2VPN services that are searched out.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

20-45

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

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

Procedure
Step 1 In the Main Topology, choose Trail > PTN Service > PTN Service Search from the Main Menu. The Emulation Service Search dialog box is displayed. Step 2 Select the Search L2VPN check box and click Next.

Step 3 When the progress bar stops, click Finish. ----End

20.5.2 Filtering L2VPN Services

You can query L2VPN services according to certain filter criteria. The T2000 displays the L2VPN services that meet the filter criteria.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The L2VPN services must be created.
20-46 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Procedure
Step 1 In the Main Topology, choose Trail > PTN Service > L2VPN Service Management from the Main Menu. The Set Trail Brows Filter Conditions dialog box is displayed. Step 2 Set filter criteria and click Filter. The L2VPN services are filtered according to the filter criteria.

----End

20.5.3 Modifying the Attributes of an L2VPN Service

You can modify the attributes of an L2VPN service, namely service name, customized information, remarks, and other information.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The L2VPN service must be created.

Procedure
Step 1 In the Main Topology, choose Trail > PTN Service > L2VPN Service Management from the Main Menu. The Set Trail Brows Filter Conditions dialog box is displayed.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-47

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 2 Set filter criteria and click Filter. Step 3 Select an L2VPN service, right-click, and then choose Details from the shortcut menu. The Details dialog box is displayed. Step 4 Modify the relevant attributes and click Apply. Step 5 Click OK. ----End

20.5.4 Configuring a UNI

In the L2VPN Service Management window, you can modify and delete the relevant attributes of a UNI.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The L2VPN service must be created.

Procedure
Step 1 In the Main Topology, choose Trail > PTN Service > L2VPN Service Management from the Main Menu. The Set Trail Brows Filter Conditions dialog box is displayed. Step 2 Set filter criteria and click Filter. Step 3 Select the corresponding service and click the UNI tab. Step 4 Set the attributes related to the UNI and click Apply. Step 5 The Confirm dialog box is displayed indicating that modifying a UNI may interrupt services.

CAUTION
l l

Modifying a UNI may interrupt services. When the value of BPDU is Transparently Transmitted, you cannot configure a UNI.

Step 6 Click OK and then click Close in the Operation Result dialog box. ----End

20.5.5 Configuring UNI QoS

In the L2VPN Service Management window, you can set and query the parameters related to UNI QoS.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The L2VPN service must be created.
20-48 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Procedure
Step 1 In the Main Topology, choose Trail > PTN Service > L2VPN Service Management from the Main Menu. The Set Trail Brows Filter Conditions dialog box is displayed. Step 2 Set filter criteria and click Filter. Step 3 Select the corresponding service and click the UNI QoS tab. Step 4 Set the attributes related to UNI QoS and click Apply.
NOTE

l l

If you set Bandwidth Limit to Enabled, you can set CIR (kbit/s) and PIR (kbit/s). You need to create a QoS policy before you configure a QoS policy.

Step 5 Click Apply and then click Close in the Operation Result dialog box. ----End

20.5.6 Configuring a PW
In the L2VPN Service Management window, you can query the information about a PW, and enable or disable the PW.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The L2VPN service must be created.

Procedure
Step 1 In the Main Topology, choose Trail > PTN Service > L2VPN Service Management from the Main Menu. The Set Trail Brows Filter Conditions dialog box is displayed. Step 2 Set filter criteria and click Filter. Step 3 Select the corresponding service and click the PW tab. Step 4 Set the parameters related to the PW and click Enable. Step 5 Optional: Click Query Work Status to query the working status of the PW. ----End

20.5.7 Configuring PW QoS

In the L2VPN Service Management window, you can set and query the parameters related to PW QoS.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The L2VPN service must be created.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-49

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 In the Main Topology, choose Trail > PTN Service > L2VPN Service Management from the Main Menu. The Set Trail Brows Filter Conditions dialog box is displayed. Step 2 Set filter criteria and click Filter. Step 3 Select the corresponding service and click the PW QoS tab. Step 4 Set the attributes related to the PW QoS and click Apply.
NOTE

l l

If you set Bandwidth Limit to Enabled, you can set CIR (kbit/s) and PIR (kbit/s). You need to create a QoS policy before configuring it.

Step 5 Optional: Click View QoS Policy to query the information about the QoS policy. ----End

20.5.8 Viewing the Alarms Related to an L2VPN Service

You can query the alarms related to an L2VPN service to check whether the L2VPN service has any potential fault.

Prerequisite
You must be an NM user with "NE operator" authority or higher. The L2VPN service must be created.

Procedure
Step 1 In the Main Topology, choose Trail > PTN Service > L2VPN Service Management from the Main Menu. The Set Trail Brows Filter Conditions dialog box is displayed. Step 2 Set filter criteria and click Filter. Step 3 Select the corresponding service, click Alarm, and then select Current Alarms from the dropdown list. Step 4 In the Current Alarms window, query and troubleshoot the current alarms related to the L2VPN service. Step 5 Optional: Select the corresponding service, click Alarm, and then select History Alarms from the drop-down list. Step 6 Optional: In the History Alarms window, view the history alarms related to the L2VPN service. ----End

20.5.9 Viewing the Performance Data Related to an L2VPN Service

You can query the performance data related to an L2VPN service to check the running status of the L2VPN service.

Prerequisite
You must be an NM user with "NE operator" authority or higher.
20-50 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

The L2VPN service must be created.

Procedure
Step 1 In the Main Topology, choose Trail > PTN Service > L2VPN Service Management from the Main Menu. The Set Trail Brows Filter Conditions dialog box is displayed. Step 2 Set filter criteria and click Filter. Step 3 Select an L2VPN service. Click Performance to query the performance data related to the L2VPN service. ----End

20.6 Configuring the V-UNI Group

When one user has multiple Ethernet service access points or one Ethernet service has multiple access points, the V-UNI group can be configured. The V-UNI group can realize the overall bandwidth restriction on group members, that is, the V-UNI in the group. On the T2000, the user can create, modify and delete the V-UNI group. 20.6.1 Creating a V-UNI Group The creation of the V-UNI group includes the selection of V-UNI group members and setting of overall bandwidth of V-UNI members. The overall bandwidth in the V-UNI group can be restrained by creating the V-UNI group. 20.6.2 Modifying a V-UNI Group The re-selection of V-UNI group members or modification of the bandwidth of the V-UNI group can be realized by modifying the V-UNI group. 20.6.3 Deleting a V-UNI Group When the overall bandwidth of members in the V-UNI is not expected to be restrained, delete the V-UNI group at any time.

20.6.1 Creating a V-UNI Group

The creation of the V-UNI group includes the selection of V-UNI group members and setting of overall bandwidth of V-UNI members. The overall bandwidth in the V-UNI group can be restrained by creating the V-UNI group.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must complete the creation of multiple Ethernet services. The PIR value of the V-UNI group should be set to a value that is higher than or equal to the total CIR value of the V-UNI members.

Procedure
Step 1 Select the NE in the NE Explorer . Choose Configuration > Ethernet Service Management > V-UNI Group from the Function Tree.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-51

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 2 Click New to display the NEW V-UNI Group window. Step 3 Set V-UNI Group ID, V-UNI Group Type, PIR(kbit/s) and PBS(byte).

Step 4 Select the interface to be added in Selecting Interface list. Click the Selected Interface list.
NOTE

to add the port to

The interfaces on the same interface board can be configured into the same V-UNI group. The former eight interfaces on the EG16 can be configured into the same V-UNI group, and the latter eight interfaces can be configured into the same V-UNI group.

Step 5 Click OK to display the Operation Result dialog box, which indicates the operation success. Then, click Close. ----End

20.6.2 Modifying a V-UNI Group

The re-selection of V-UNI group members or modification of the bandwidth of the V-UNI group can be realized by modifying the V-UNI group.

Prerequisite
You must be an NM user with "NE operator" authority or higher.
20-52 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > Ethernet Service Management > V-UNI Group from the Function Tree. Step 2 Select the V-UNI group to be modified. Click Modify to display the Modify V-UNI Group window. Step 3 Modify PIR(kbit/s) and PBS(byte) of the V-UNI group in the Modify V-UNI Group window. Step 4 Click Configure Interface to display the Configure Interface dialog box. Step 5 Select the interface, and then click OK to return to the Modify V-UNI Group window. Then, the selected interface is in Selecting Interface list of the Member Setting. Step 6 Select the interface to be added. Click Step 7 Select the interface to be deleted. Click Interface list. to add the port to the Selected Interface list. to delete the port from the Selected

Step 8 Click OK to display the Operation Result dialog box, which indicates the operation success. Then, click Close. ----End

20.6.3 Deleting a V-UNI Group

When the overall bandwidth of members in the V-UNI is not expected to be restrained, delete the V-UNI group at any time.

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

Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > Ethernet Service Management > V-UNI Group from the Function Tree. Step 2 Select the V-UNI group to be deleted. Click Delete to display a dialog box. Step 3 Click Yes to display the Operation Result dialog box, which indicates the operation success. Then, click Close. ----End

20.7 Configuration Case of the UNI-UNI E-Line Service

This section uses a case to show the configuration of the UNI-UNI E-Line service, and the configuration flow. The configuration case covers the service planning and configuration of the Ethernet service. 20.7.1 Networking Diagram This section describes the networking diagram for the service between Company A and Company B.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-53

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

20.7.2 Service Planning The voice service, video service, and common Internet access service are available between Company A and Company B. Hence, an E-Line service should be created. 20.7.3 Configuring the E-Line Service at an NE To configure the UNI-UNI E-Line service is to configure the E-Line service at an NE. This section describes how to configure the UNI-UNI E-Line service.

20.7.1 Networking Diagram

This section describes the networking diagram for the service between Company A and Company B.

Requirement and Networking Diagram

As shown in Figure 20-13, in City 1, Company A and Company B need communication between each other. The switches of the two companies are connected to the local OptiX PTN 3900. The switches of Company A and Company B support VLAN. The service available between Company A and Company B include the voice service, video service, and common Internet access service. The voice service and video service use the fixed bandwidth, and the common Internet access service can use all the bandwidth at a burst. Table 20-5 lists the service requirement. Figure 20-13 Networking diagram for the UNI-UNI E-Line service
UNI:1-EG16-19ETFC-1

A Company

Packet Switching Network

B Company City1

UNI:1-EG16-19ETFC-2

PTN

Table 20-5 Requirement of the E-Line service Service Type Voice service (VLAN=100) Video service (VLAN=200) Common Internet access service (VLAN=300)
20-54

Requirement Fixed bandwidth, CIR=PIR, 10 Mbit/s Fixed bandwidth, CIR=PIR, 40 Mbit/s CIR=10 Mbit/s, PIR=50 Mbit/s

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Service Type Total bandwidth

Requirement 80 Mbit/s

20.7.2 Service Planning

The voice service, video service, and common Internet access service are available between Company A and Company B. Hence, an E-Line service should be created. The three types of services should be differentiated through VLAN labels. In addition, different services use different QoS processing. Table 20-6 lists the configuration parameters of NE1. Table 20-6 Configuration parameters of NE1 NE Interface 19-ETFC-1(Port-1) NE1 Interface Attribute Port Mode: Layer 2 Tag: Tag Aware 19-ETFC-2(Port-2) Port Mode: Layer 2 Tag: Tag Aware

Table 20-7 lists the configuration parameters of QoS. Table 20-7 Configuration parameters of QoS Service Type Policy ID Traffic Classifi cation ID 1 2 3 Bandwi dth Limit Enabled Enabled Enabled CIR (kbit/s) PIR (kbit/ s) Coloration Mode

Voice service Video service Ordinary Internet access service

1 1 1

10000 40000 10000

10000 40000 50000

Color Blindness Color Blindness Color Blindness

Table 20-8 lists the planning of the Ethernet service.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

20-55

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Table 20-8 Planning of the UNI-UNI E-Line service Field Service ID Value 1 Description The service ID, ranges from 1 to 65535, can be manually input. The service created is a UNIUNI Ethernet service. 19-ETFC-1(Port-1) is connected to Company A, and 19-ETFC-2(Port-2) is connected to Company B. The VLAN value of the voice service is 100; the VLAN value of the video service is 200; the VLAN value of the common Internet access service is 300. BPDU, used to transport the protocol information of the MSTP, is a bridge protocol data unit. Normally, set to Not Transparently Transmitted. MTU is the maximum transport unit. -

Service Direction UNI

UNI-UNI 19-ETFC-1(Port-1) and -2 (Port-2)

VLANs

100, 200, 300

BPDU

Not Transparently Transmitted

MTU(byte) QoS Policy for Voice Service QoS Policy for Video Service QoS Policy for Common Internet Access Service

1526 Fixed bandwidth, CIR=PIR, 10000 kbit/s Fixed bandwidth, CIR=PIR, 40000 kbit/s CIR=10000 kbit/s, PIR=50000 kbit/s

20.7.3 Configuring the E-Line Service at an NE

To configure the UNI-UNI E-Line service is to configure the E-Line service at an NE. This section describes how to configure the UNI-UNI E-Line service.

Prerequisite
You must understand the networking, requirements and service planning of the example.

Procedure
Step 1 Configure the QoS policy
20-56 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

1. 2.

In the NE explorer, select NE1 and choose > > Policy Management from the Function Tree. Configuration > QoS Management > QoS Management . Select V-UNI Ingress Policy tab, and click New. Set the policy parameters in the Create V-UNI Ingress Policy dialog box displayed. The configuration parameters are as follows:
l l

Policy ID: 1 Policy Name: E-Line

3.

Click New in Traffic Classification Configuration. Set the parameters in Create Traffic Classification dialog box displayed. Click Add to add the math rules, and then click OK. Create three different traffic classification polices. The configuration parameters are as follows:
l

Voice service

Traffic Classification ID: 1 ACL Action: Permit Match Type: CVlan ID (The tag carried by the transmitted service packets is the CVlan tag. In this case, the mapping type is CVlan ID.) Match Value: 100 (The VLAN ID of the voice service is 100.) Wildcard: 0 (The number of digits of the wildcard is consistent with the number of digits of the match value. After the wildcard is converted to the binary format, digit 0 in the match value should be matched, but digit 1 need not be considered. When the wildcard is set to all "0"s, it indicates that the packets should strictly match the match value.) CoS: EF (The voice service is the real-time service. In this case, the CoS is set to EF to ensure the service quality.) Bandwidth Limit: Enable CIR(kbit/s): 10000 (Indicates the ensured bandwidth of the queue.) PIR(kbit/s): 10000 (Indicates the peak traffic rate.) CBS(byte): 16000 (Indicates the committed burst size. When the bandwidth is insufficient, certain packets cannot enter the queue for forwarding in time. In this case, a buffer, where these packets are stored, is required. Then, after the bandwidth is sufficient, these packets are forwarded. Hence, the CBS indicates the ensured size of the buffer space.) PBS(byte): 16000 (Indicates the peak burst size.) Coloration Mode: Color Blindness Traffic Classification ID: 2 ACL Action: Permit Match Type: CVlan ID Match Value: 200 Wildcard: 0 CoS: AF4 (The video service has high requirement for delay. In this case, the CoS is set to AF4.)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-57

Video service

Issue 01 (2009-06-30)

20 Configuring an Ethernet Service

l

OptiX iManager T2000 Operation Guide for PTN NE Management

Bandwidth Limit: Enable CIR(kbit/s): 40000 PIR(kbit/s): 40000 CBS(byte): 16000 PBS(byte): 16000 Coloration Mode: Color Blindness Traffic Classification ID: 3 ACL Action: Permit Match Type: CVlan ID Match Value: 300 Wildcard: 0 CoS: BE (The common Internet access service is not the real-time service. In this case, the CoS is set to BE, and thus the common Internet access service is transmitted as possible.) Bandwidth Limit: Enable CIR(kbit/s): 10000 PIR(kbit/s): 50000 CBS(byte): 16000 PBS(byte): 16000 Coloration Mode: Color Blindness

Data service

Step 2 Configure interfaces: 1. 2. In the NE Explorer, select NE1 and choose Configuration > Interface Management > Ethernet Interface from the Function Tree to configure the network-side interface. In the General Attributes tab, select the 19-ETFC-1(Port-1) and 19-ETFC-2(Port-2). Set the parameters such as Port Mode, Encapsulation Type as required, and click Apply. The configuration parameters are as follows:
l l l l l

Port: 19-ETFC-1(Port-1), 19-ETFC-2(Port-2) Enable Port: Enabled Port Mode: Layer 2 Encapsulation Type: 802.1Q Working Mode: Auto-Negotiation (Set the working modes of the local port and opposite port as the same.) Max Frame: 1620 (Set this parameter according to the length of data packets.)

3.

In the Layer 2 Attributes tab, select the 19-ETFC-1(Port-1) and 19-ETFC-2(Port-2). Set the TAG to Tag Aware. Click Apply. The configuration parameters are as follows:
l l

Port: 19-ETFC-1(Port-1), 19-ETFC-2(Port-2) Tag: Tag Aware

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

20-58

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

If a port is set to Tag Aware, this port can transparently transmits the data packet with the VLAN ID (Tag). If the data packet does not contain the VLAN ID (Untag), this packet is discarded. If the port is set to Access, the port adds the default VLAN ID to the signal packet without the VLAN ID (Untag). If the signal contains the VLAN ID (Tag), this packet is discarded. If the port is set to Hybrid, the port adds the default VLAN ID (Untag) to the signal packet without the VLAN ID (Untag). If the signal packet contains the VLAN ID (Tag), the packet is transparently transmitted.

Step 3 Create a UNI-UNI service. 1. 2. In the NE explorer, select NE1 and choose Ethernet Service Management > E-Line Service. Click New. Set the parameters such as Service ID, Service Name, Port, VLANs in the New E-Line Service dialog box displayed. Click Apply. The configuration parameters are as follows:
l l l l l l

Service ID: 1 Service Name: CompanyA-CompanyB Direction: UNI-UNI BPDU: Not Transparently Transmitted Port: 19-ETFC-1(Port-1) (Company A is connected to 19-ETFC-1(Port-1).) VLANs: 100, 200, 300 (The voice service, video service, and common Internet access service between Company A and Company B are differentiated through different VLAN values carried by the services. This port can transmit only the services whose VLAN values are 100, 200, and 300. Otherwise, the services are discarded. Port: 19-ETFC-2(Port-2) (Company B is connected to 19-ETFC-2(Port-2).) VLANs: 100, 200, 300

l l

3.

Click Configure QoS, set the parameters for the policy in the Configure QoS dialog box displayed. The configuration parameters are as follows:
l

Policy: 1

----End

20.8 Configuration Case of the UNI-NNI E-Line Service Carried by Ports

A case is provided here to show the configuration of the UNI-NNI E-Line service carried by ports, and the configuration flow. The configuration case covers the service planning, configuration and verification of the Ethernet service. 20.8.1 Networking Diagram This section describes the networking diagram for the service of the Company A between City 1 and City 2. 20.8.2 Service Planning
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-59

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

To transport the service between city 1 and city 2, an E-Line service must be created. 20.8.3 Configuring the E-Line Service at the Source NE To configure a UNI-NNI E-Line service carried by ports is to configure the E-Line service at the source NE and sink NE. This section describes how to configure the E-Line service at the source NE. 20.8.4 Verifying the Correctness of Service Configuration After the E-Line service is configured, the correctness of service configuration should be verified. The Ethernet OAM is used to verify the correctness of Ethernet service configuration.

20.8.1 Networking Diagram

This section describes the networking diagram for the service of the Company A between City 1 and City 2.

Requirement and Networking Diagram

As shown in Figure 20-14, Company A has departments in City 1 and City 2, which need communicate with each other. The service is data service. The user requires exclusive usage of the UNI port. Each physical port that the private line passes through is exclusively occupied by this private line. This example considers the direct communication of two cities as an example. All packets transported by the switch at the user egress carry VLANs, whose value is 100. Figure 20-14 Networking diagram for the UNI-NNI E-Line service carried by ports
UNI:1-EG16-19-ETFC-1 Packet Switching Network
A Company A Company

UNI:1-EG16-19-ETFC-1

NE 1

NE 2

City1 NNI:1-EG16-19-ETFC-2 NNI:1-EG16-19-ETFC-2

City2

20.8.2 Service Planning

To transport the service between city 1 and city 2, an E-Line service must be created. Table 20-9 lists the configuration parameters of NEs. Table 20-9 Configuration parameters of NEs NE NE1 Interface 19-ETFC-1(Port-1) Interface Attribute Port Mode: Layer 2 Encapsulation Type: 802.1Q Tag: Tag Aware

20-60

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

NE

Interface 19-ETFC-2(Port-2)

Interface Attribute Port Mode: Layer 2 Encapsulation Type: 802.1Q Tag: Tag Aware

19-ETFC-1(Port-1)

Port Mode: Layer 2 Encapsulation Type: 802.1Q Tag: Tag Aware

NE2

19-ETFC-2(Port-2)

Port Mode: Layer 2 Encapsulation Type: 802.1Q Tag: Tag Aware

Since the service is data service, and the ports are exclusively used, the QoS is not required. Table 20-10 lists details on the service planning. Table 20-10 Planning of the UNI-NNI E-Line service carried by ports Parameter Service ID Service Name Direction UNI NNI Bearer Type VLANs BPDU MTU(byte) NE 1 1 E-Line-1 UNI-NNI 1-EG16-19-ETFC-1(Port-1) 1-EG16-19-ETFC-2(Port-2) Port 100 Not Transparently Transmitted 1526 NE 2 1 E-Line-1 UNI-NNI 1-EG16-19-ETFC-1(Port-1) 1-EG16-19-ETFC-2(Port-2) Port 100 Not Transparently Transmitted 1526

20.8.3 Configuring the E-Line Service at the Source NE

To configure a UNI-NNI E-Line service carried by ports is to configure the E-Line service at the source NE and sink NE. This section describes how to configure the E-Line service at the source NE.

Prerequisite
You must understand the networking, requirements and service planning of the example. If a port need be exclusively used, disable the DCN function of the port that carries the service. For details, see 2.4.4 Enabling the Port DCN.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-61

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 Configure the interfaces. 1. 2. In the NE Explorer, select NE1 and choose Configuration > Interface Management > Ethernet Interface from the Function Tree to configure the network-side interface. In the General Attributes tab, select the 19-ETFC-1(Port-1) and 19-ETFC-2(Port-2). Set the parameters such as Port Mode, Encapsulation Type as required, and click Apply. The configuration parameters are as follows:
l l l l l

Port: 19-ETFC-1(Port-1), 19-ETFC-2(Port-2) Enable Port: Enabled Port Mode: Layer 2 Encapsulation Type: 802.1Q Working Mode: Auto-Negotiation (Set the working modes of the local port and opposite port as the same.) Max Frame: 1620 (Set this parameter according to the length of data packets.)

3.

In the Layer 2 Attributes tab, select the 19-ETFC-1(Port-1) and 19-ETFC-2(Port-2). Set the TAG to Tag Aware. Click Apply. The configuration parameters are as follows:
l l

Port: 19-ETFC-1(Port-1), 19-ETFC-2(Port-2) Tag: Tag Aware

If a port is set to Tag Aware, this port can transparently transmits the data packet with the VLAN ID (Tag). If the data packet does not contain the VLAN ID (Untag), this packet is discarded. If the port is set to Access, the port adds the default VLAN ID to the signal packet without the VLAN ID (Untag). If the signal contains the VLAN ID (Tag), this packet is discarded. If the port is set to Hybrid, the port adds the default VLAN ID (Untag) to the signal packet without the VLAN ID (Untag). If the signal packet contains the VLAN ID (Tag), the packet is transparently transmitted.

4.

In the NE Explorer, select NE2. Then, configure the interface attributes by following Step 1.1 to Step 1.3. In the NE explorer, select NE1 and choose Ethernet Service Management > E-Line Service. Click New. Set the parameters such as Service ID, Service Name, Port, VLANs in the New E-Line Service dialog box displayed. Click Apply. The configuration parameters are as follows:
l l l l l

Step 2 Configure a UNI-NNI E-Line service. 1. 2.

Service ID: 1 Service Name: E-Line-1 Direction: UNI-NNI BPDU: Not Transparently Transmitted Port: 19-ETFC-1(Port-1) (Company A in City 1 is connected to 19-ETFC-1(Port-1).)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

20-62

OptiX iManager T2000 Operation Guide for PTN NE Management

l l l

20 Configuring an Ethernet Service

VLANs: 100 Bear Type: Port Port: 19-ETFC-2(Port-2) (19-ETFC-2(Port-2) transmits the service to NE2.)

3.

In the NE Explorer, select NE2. Then, configure the E-Line service by following to . The configuration parameters are as follows:
l l l l l l l l

Service ID: 1 Service Name: E-Line-1 Direction: UNI-NNI BPDU: Not Transparently Transmitted Port: 19-ETFC-1(Port-1) (Company A in City 2 is connected to 19-ETFC-1(Port-1).) VLANs: 100 Bear Type: Port Port: 19-ETFC-2(Port-2) (19-ETFC-2(Port-2) transmits the service to NE1.)

----End

20.8.4 Verifying the Correctness of Service Configuration

After the E-Line service is configured, the correctness of service configuration should be verified. The Ethernet OAM is used to verify the correctness of Ethernet service configuration.

Context
The connectivity of the UNI-UNI E-Line service need no OAM verification. By default, the configuration is regarded as correct. In the case of the UNI-NNI E-Line service carried by a port, the OAM verification method is similar to that of the UNI-NNI E-Line service carried by PWs. The UNI-NNI E-Line service carried by PWs is taken as an example. As shown in Figure 20-15, to verify the correctness of service configuration, the Ethernet OAM should be configured. Figure 20-15 OAM of the E-Line service
MD MA

MEP A Company

NE 1

NE 2

MEP

A Company

MEP

MEP B Company

B Company

City2 MA

City1

Unicast Tunnel PW

MD: Maintenance Domain MA: Maintenance Association MEP: Maintenance End Point

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

20-63

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

As shown in the previous figure, E-Line services, which are carried and isolated by PWs, are available between branches of Company A and branches of Company B. To verify the configuration correctness of the two E-Line services, the Ethernet OAM should be configured. The verification of the E-Line service of Company A is taken as an example.

Procedure
Step 1 On the T2000, select NE1 to create the maintenance domain. For the creation method, see 25.2.4 Creating an MD. The parameters of the maintenance domain are as follows:
l l

Maintenance Domain Name: MD Maintenance Domain Level: 4

Step 2 On the T2000, select NE2 to create the maintenance domain. For the creation method, see 25.2.4 Creating an MD. The parameters of the maintenance domain are as follows:
l l

Maintenance Domain Name: MD Maintenance Domain Level: 4

NOTE

The maintenance domain names and levels of NE1 and NE2 should be consistent, and then NE1 and NE2 are in the same maintenance domain.

Step 3 On the T2000, select NE1 to create the maintenance association for Company A. For the creation method, see 25.2.5 Creating an MA. The parameters of the maintenance association are as follows:
l l l l

Maintenance Domain Name: MD Maintenance Association Name: MA Relevant Service: 1-E-Line-1 CC Test Transmit Period (ms): 3.33 ms

Step 4 On the T2000, select NE2 to create the maintenance association for Company A. For the creation method, see 25.2.5 Creating an MA. The parameters of the maintenance association are as follows:
l l l l

Maintenance Domain Name: MD Maintenance Association Name: MA Relevant Service: 1-E-Line-1 CC Test Transmit Period (ms): 3.33 ms

Step 5 On the T2000, select NE1 to create the MEP. For the creation method, see 25.2.6 Creating a MEP Maintenance Point. The parameters of the MEP are as follows:
l l l l

Maintenance Domain Name: MD Maintenance Association Name: MA Board: 19-ETFC Port: 1 (Port-1)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

20-64

OptiX iManager T2000 Operation Guide for PTN NE Management

l l l l

20 Configuring an Ethernet Service

VLAN: 100 MP ID: 1 Direction: Ingress CC Status: Active

Step 6 On the T2000, select NE2 to create the MEP. For the creation method, see 25.2.6 Creating a MEP Maintenance Point. The parameters of the MEP are as follows:
l l l l l l l l

Maintenance Domain Name: MD Maintenance Association Name: MA Board: 19-ETFC Port: 1 (Port-1) VLAN: 100 MP ID: 2 Direction: Ingress CC Status: Active

Step 7 On the T2000, select NE1 to add a remote MEP. For the operation method, see 25.2.7 Adding a Remote MEP of the MA. The parameters of the remote MEP are as follows:
l l l

Maintenance Domain Name: MD Maintenance Association Domain Name: MA Remote Maintenance Point ID: 2

Step 8 On the T2000, select NE2 to add a remote MEP. For the operation method, see 25.2.7 Adding a Remote MEP of the MA. The parameters of the remote MEP are as follows:
l l l

Maintenance Domain Name: MD Maintenance Association Domain Name: MA Remote Maintenance Point ID: 1

Step 9 On the T2000, select NE1 to perform the CC test. For the operation method, see 25.2.9 Performing a Continuity Check.
NOTE

If the MEP of NE2 does not receive the CC packets from NE1 in a period of time (for example, 3.25 times of the transmission period), the MEP automatically reports the ETH_CFM_LOC alarm. If the ETH_CFM_LOC alarm is not reported, the connectivity of the service from NE1 to NE2 is normal.

Step 10 On the T2000, select NE2 to perform the CC test. For the operation method, see 25.2.9 Performing a Continuity Check.
NOTE

If the MEP of NE1 does not receive the CC packets from NE2 in a period of time (for example, 3.25 times of the transmission period), the MEP automatically reports the ETH_CFM_LOC alarm. If the ETH_CFM_LOC alarm is not reported, the connectivity of the service from NE2 to NE1 is normal.

----End
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-65

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

20.9 Configuration Case of the UNI-NNI E-Line Service Carried by the PW

A case is provided here to show the configuration of the UNI-NNI E-Line service carried by the PW, and the configuration flow. The configuration case covers the service planning, configuration and verification of the Ethernet service. 20.9.1 Case Description The case description covers the requirement, networking diagram and service planning. 20.9.2 Service Planning The Ethernet services between branches of a company are carried by a PW. When planning such an Ethernet service, you need to plan the NE information, tunnel information, and service information. 20.9.3 Configuring the E-Line Service of the NE To configure a UNI-NNI E-Line service carried by ports is to configure the E-Line service at the source NE and sink NE. This section describes how to configure the E-Line service. 20.9.4 Verifying the Correctness of Service Configuration After the E-Line service is configured, the correctness of service configuration should be verified. The Ethernet OAM is used to verify the correctness of Ethernet service configuration.

20.9.1 Case Description

The case description covers the requirement, networking diagram and service planning. As shown in Figure 20-16, Company A and Company B have departments in City 1 and City 2, which need to communicate with each other respectively. The communication of Company A should be isolated from that of Company B. NE1 is connected to Company A and Company B in City 1. NE3 is connected to Company A and Company B in City 2. NE1 accesses the services from City 1 and transmits the services to NE2. Then, NE2 transparently transmits the services to NE3. Finally, NE3 transmits the services to City 2. Similarly, NE3 accesses the services from City 2 and transmits the services to NE2. Then, NE2 transparently transmits the services to NE1. Finally, NE1 transmits the services to City 1. For such an application, the UNI-NNI E-Line service carried by the PW should be created. Two PWs carry the services of Company A and Company B respectively. The two PWs share bandwidth of one tunnel. The service between departments of Company A is the ordinary Internet access service (CIR = 10 Mbit/s, PIR = 30 Mbit/s). The service between departments of Company B is the data service (CIR = 30 Mbit/s, PIR = 50 Mbit/s). NE1 is an OptiX PTN 1900 NE. NE2 and NE3 are OptiX PTN 3900 NEs.

20-66

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Figure 20-16 Networking diagram for the UNI-NNI E-Line service carried by the PW

NE4 NE5 Access layer

20-EFF8-1(Port-1) 10.0.0.2 3-EFF8-3(Port-3) 10.0.0.1 3-EFF8-2(Port-2)

10GE ring on convergence layer

5-EX2-1(Port-1) 10.0.1.2

NE3
20-EFF8-2(Port-2)

NE1
3-EFF8-1(Port-1)

NE2

5-EX2-1(Port-1) 10.0.1.1 20-EFF8-1(Port-1)

Company B Company A Company B Company A

20.9.2 Service Planning

The Ethernet services between branches of a company are carried by a PW. When planning such an Ethernet service, you need to plan the NE information, tunnel information, and service information. Table 20-11 lists the configuration parameters of NEs. Table 20-11 Configuration parameters of NEs NE LSR ID Port 3-EFF8-1(Port-1) Port Attribute Port Mode: Layer 2 Tag: Tag Aware NE1 1.0.0.1 3-EFF8-2(Port-2) Port Mode: Layer 2 Tag: Tag Aware 3-EFF8-3(Port-3) 20-EFF8-1(Port-1) NE2 1.0.0.2 5-EX2-1(Port-1) 20-EFF8-1(Port-1) Port Mode: Layer 3 Port Mode: Layer 3 Port Mode: Layer 3 Port Mode: Layer 2 Tag: Tag Aware NE3 1.0.0.3 20-EFF8-2(Port-2) Port Mode: Layer 2 Tag: Tag Aware 5-EX2-1(Port-1) Port Mode: Layer 3 10.0.1.2 255.255.255. 252 10.0.0.1 10.0.0.2 10.0.1.1 255.255.255. 252 255.255.255. 252 255.255.255. 252 Port IP Address IP Mask -

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

20-67

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Table 20-12 lists details on the planning of the tunnel carrying the PW. Table 20-12 Planning of the tunnel carrying the PW Parameter Tunnel ID Name Signal Type Scheduling Type Bandwidth (kbit/s) Source Node Sink Node Route Constraint Port IP Address Positive Tunnel 1 Tunnel-0001(Positive) Dynamic E-LSP 80 Mbit/s NE1 NE3 IP addresses of ingress port of NE2: 20-EFF8-1: 10.0.0.2 IP addresses of ingress port of NE3: 5-EX2-1: 10.0.1.2 Reverse Tunnel 2 Tunnel-0002(Reverse) Dynamic E-LSP 80 Mbit/s NE3 NE1 IP addresses of ingress port of NE2: 5-EX2-1: 10.1.2.2 IP addresses of ingress port of NE1: 3-EFF8-2: 10.1.1.2

Table 20-13 lists details on the planning of the E-Line service. Table 20-13 Planning of the UNI-NNI E-Line service carried by the PW Parameter Service ID Service Name Direction UNI VLANs Bearer Type PW ID BPDU MTU(byte) Company A 1 E-Line-1 UNI-NNI 3-EFF8-1(Port-1) 100 PW 35 Not Transparently Transmitted 1526 Company B 2 E-Line-2 UNI-NNI 3-EFF8-2(Port-2) 200 PW 45 Not Transparently Transmitted 1526

Table 20-14 lists details on the planning of the PW.

20-68 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Table 20-14 Planning of the PW Parameter PW Signaling Type PW Type Direction PW Ingress Label PW Egress Label Peer IP Tunnel Bandwidth Limit CIR(kbit/s) PIR(kbit/s) PW of Company A Static Ethernet Bidirectional 20 20 1.0.0.3 1(E-Line) Enabled 10000 30000 PW of Company B Static Ethernet Bidirectional 30 30 1.0.0.1 1(E-Line) Enabled 30000 50000

20.9.3 Configuring the E-Line Service of the NE

To configure a UNI-NNI E-Line service carried by ports is to configure the E-Line service at the source NE and sink NE. This section describes how to configure the E-Line service.

Prerequisite
You must understand the networking, requirements and service planning of the example.

Procedure
Step 1 Set LSR IDs. 1. 2. In the NE Explorer, select the NE1 and chooseConfiguration > MPLS Management > Basic Configuration from the Function Tree. Set LSR ID, Start of Global Label Space and Start of Multicast Label Space. Click Apply. The configuration parameters are as follows:
l l

LSR ID: 1.0.0.1 (The LSR ID must be unique in the entire network.) Start of Global Label Space: 0 (The minimum values of egress and ingress labels of the unicast tunnel.)

3.

Display the NE Explorer of NE2 and NE3 separately and perform the preceding two steps to set the parameters such as LSR ID. The configuration parameters are as follows:
l l

NE2 LSR ID: 1.0.0.2 NE3 LSR ID: 1.0.0.3

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-69

Issue 01 (2009-06-30)

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 2 Configure interfaces. 1. 2. In the NE Explorer, select NE1 and choose Configuration > Interface Management > Ethernet Interface from the Function Tree to configure the interface. In the General Attributes tab, select the 3-EFF8-1(Port-1) 3-EF8F-2(Port-2) and 3EFF8-3(Port-3). Set the parameters such as Port Mode, Working Mode, and click Apply. The configuration parameters are as follows:
l

Port: 3-EFF8-1(Port-1), 3-EFF8-2(Port-2)

Enable Port: Enabled Port Mode: Layer 2 (User-side interface, Company A is connected to 3-EFF8-1 (Port-1), and Company B is connected to 3-EFF8-2(Port-2).) Encapsulation Type: 802.1Q Working Mode: Auto-Negotiation (Set the working modes of the local port and opposite port as the same.) Max Frame: 1620 (Set this parameter according to the length of data packets.) Enable Port: Enabled Port Mode: Layer 3 (Network interface, the port carries a Tunnel.) Working Mode: Auto-Negotiation Max Frame: 1620

Port: 3-EFF8-3(Port-3)

3.

Select the 3-EFF8-3(Port-3) in the Layer 3 Attributes tab. Right click the Enable Tunnel field and select Enabled. Right-click the Specify IP field and choose Manually. Then, set the parameters such as IP Address and IP Mask. Click Apply. The configuration parameters are as follows:
l l

Enable Tunnel: Enabled TE Measurement: 10 (The link with a smaller TE measurement value is preferred for route selection of a tunnel. You can intervene in the route selection by adjusting the TE measurement of the link. The smaller the value of the TE measurement, the higher the priority of the link. ) Specify IP: Manually (Manually indicates that you can set the IP address of the port.) IP Address: 10.0.0.1 IP Mask: 255.255.255.252

l l l

4.

Display the NE Explorer for NE2, and NE3 separately. Perform Step 2.1 to Step 2.3 to set parameters of each related interface. The configuration parameters are as follows:
l

NE2

General Attribute

Port: 20-EFF8-1(Port-1), 5-EX2-1(Port-1) Enable Port: Enabled Port Mode: Layer 3 Working Mode: Auto-Negotiation
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

20-70

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Max Frame: 1620 Enable Tunnel: Enabled TE Measurement: 10 Specify IP: Manually 20-EFF8-1(Port-1) IP Address: 10.0.0.2 5-EX2-1(Port-1) IP Address: 10.0.1.1 IP Mask: 255.255.255.252

Layer 3 Attribute

NE3

General Attribute

Port: 20-EFF8-1(Port-1), 20-EFF8-2(Port-2)

Enable Port: Enabled Port Mode: Layer 2 Encapsulation Type: 802.1Q Working Mode: Auto-Negotiation Max Frame: 1620 Enable Port: Enabled Port Mode: Layer 3 Working Mode: Auto-Negotiation Max Frame: 1620

Port: 5-EX2-1(Port-1)

Layer 3 Attribute

Enable Tunnel: Enabled TE Measurement: 10 Specify IP: Manually IP Address: 10.0.1.2 IP Mask: 255.255.255.252

Step 3 Configure the control plane. 1. 2. In the NE Explorer, select an NE1 and choose Configuration > Control Plane Configuration > IGP-ISIS Configuration from the Function Tree. Choose the Port Configuration tab and then click New. Click Add in the dialog box displayed. Then Select 3-EFF8-3(Port-3) in the port tab. Click OK. The configuration parameters are as follows:
l l

Link Level: level-1-2 LSP Retransmission Interval(s): 5 (In the case of a point-to-point link, if the local equipment fails to receive any response in a period after transmitting the LSP, the local equipment considers that the LSP is lost or discarded. To ensure the transmission reliability, the local equipment transmits the LSP again.) Minimum LSP Transmission Interval (ms): 30
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-71

Issue 01 (2009-06-30)

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

3.

Display the NE Explorer for NE2, and NE3 separately. Set the parameters related to the control plane by following Step 3.1 to Step 3.2. Set the IS-IS parameters of NE2 and NE3 as the same as the IS-IS parameters of NE1.

Step 4 Creating MPLS Tunnels

NOTE

When creating a tunnel, you can create a dynamic tunnel or static tunnel. The dynamic tunnel is considered as an example in this case. For details on how to create a static tunnel, see 13.7 Configuration Case of the Static MPLS Tunnel.

1. 2.

On the Main Topology, choose Trail > Tunnel Creation. The Create Tunnel dialog box is displayed. Select Create Reverse Tunnel, and configure parameters for the positive tunnel and reverse tunnel in the General Attributes. The configuration parameters are as follows:
l l l

Tunnel ID: 1 (Positive), 2 (Reverse) Name: Tunnel-0001 (Positive), Tunnel-0002 (Reverse) Signal Type: Dynamic (If you set signal type to dynamic, the LDP distributes labels and the tunnel is a dynamic tunnel; if you set signal type to static, labels are manually added and the tunnel is a static tunnel.) Scheduling Type: E-LSP

E-LSP indicates that the tunnel determines the scheduling priority and discard priority of packets according to the EXP information. On one MPLS tunnel of the E-LSP type, there can be a maximum of eight types of PWs. L-LSP indicates that the tunnel determines the scheduling policy of packets according to the MPLS labels and determines the discard policy of packets according to the EXP information. On one MPLS tunnel of the L-LSP type, there can be a maximum of one type of PWs. Currently, the OptiX PTN equipment does not support the L-LSP type.

l l

EXP:Null (tunnel priority.) Bandwidth (kbit/s): 30000 (Set the bandwidth according to networking planning.)

3.

Click Next, and select Source Node and Sink Node. Click Add to add route restrictions. The configuration parameters are as follows:
l l l l

Source Node: NE1 Sink Node: NE3 Positive Route Constraint Port IP Address: 10.0.0.2, 10.0.1.2, Include Strict Reverse Route Constraint Port IP Address: 10.0.1.1, 10.0.0.1, Include Strict

4.

Click Next. Set the parameters such as Setup Priority and Hold Priority for the tunnel according to the planning. Then, click Next. Confirm the tunnel information and then click Finish. The configuration parameters are as follows:
l

Setup Priority: 7 (Setup priority is specified for an MPLS tunnel during creation. "0" indicates the highest priority. In the case insufficiency of resources, the MPLS tunnel of a higher setup priority can preempt the bandwidth of other MPLS tunnels and thus can be created successfully.)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

20-72

OptiX iManager T2000 Operation Guide for PTN NE Management

l

20 Configuring an Ethernet Service

Hold Priority: 0 (Hold priority is specified for an MPLS tunnel after creation. "0" indicates the highest priority. In the case of insufficiency of resources, the bandwidth for the MPLS tunnel of a higher hold priority is less likely to be preempted by other tunnels. When creating a dynamic tunnel, make sure that the hold priority is higher or equal to the setup priority.) Color(0x): 0 (Set the affinity attribute of a link. When the primary tunnel is faulty, the link with the same color is preferred during rerouting. When the affinity attribute of links is not required, adopt the default value.) Mask(0x): 0 (Set the number of bits of the mask. Match the number of bits of a mask with the link color. Select the route of a matching link color.) Tunnel Type: Primary Tunnel (You can set the tunnel type to primary tunnel or bypass tunnel. According to the planning, the tunnel is a primary tunnel in this case.)

Step 5 Configure two UNI-NNI E-Line service. 1. 2. In the NE explorer, select NE1 and choose Ethernet Service Management > E-Line Service. Click New. Set the parameters such as Service ID, Service Name, Port, VLANs in the New E-Line Service dialog box displayed. Click Apply. The configuration parameters are as follows:
l l l l l l l l

Service ID: 1 Service Name: E-Line-1 Direction: UNI-NNI BPDU: Not Transparently Transmitted Port: 3-EFF8-1(Port-1) (Company A is connected to 3-EFF8-1(Port-1).) VLANs: 100 Bearer Type: PW PW ID: 35

3.

Click Configure PW. Set the attributes of PW in Configure PW dialog box displayed, and click OK. The configuration parameters are as follows:
l

General Attributes

PW ID: 35 PW Signaling Type: Static PW Type: Ethernet Direction: Bidirectional PW Encapsulation Type: MPLS PW Ingress Label: 20 PW Egress Label: 20 Peer IP: 1.0.0.3 Tunnel: 1

4.

Click Configure QoS. Set QoS attributes of the PW in Configure QoS dialog box displayed, and click OK.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-73

Issue 01 (2009-06-30)

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

The configuration parameters are as follows:

l l

EXP: 4 (7 indicates the highest priority.) LSP Mode: Uniform (The CoS of user packets should be recovered when the tunnel label is stripped.)

5.

Create the E-Line service of Company B at the source NE by following Step 5.1 to Step 5.4. For details of E-Line2 service, see Table 20-13.

6.

In the NE Explore select NE3, create the E-Line service from NE3 to NE1, by following Step 5.1 to Step 5.5.

----End

20.9.4 Verifying the Correctness of Service Configuration

After the E-Line service is configured, the correctness of service configuration should be verified. The Ethernet OAM is used to verify the correctness of Ethernet service configuration.

Context
The connectivity of the UNI-UNI E-Line service need no OAM verification. By default, the configuration is regarded as correct. In the case of the UNI-NNI E-Line service carried by a port, the OAM verification method is similar to that of the UNI-NNI E-Line service carried by PWs. The UNI-NNI E-Line service carried by PWs is taken as an example. As shown in Figure 20-17, to verify the correctness of service configuration, the Ethernet OAM should be configured. Figure 20-17 OAM of the E-Line service
MD MA

MEP A Company

NE 1

NE 2

MEP

A Company

MEP

MEP B Company

B Company

City2 MA

City1

Unicast Tunnel PW

MD: Maintenance Domain MA: Maintenance Association MEP: Maintenance End Point

As shown in the previous figure, E-Line services, which are carried and isolated by PWs, are available between branches of Company A and branches of Company B. To verify the
20-74 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

configuration correctness of the two E-Line services, the Ethernet OAM should be configured. The verification of the E-Line service of Company A is taken as an example.

Procedure
Step 1 On the T2000, select NE1 to create the maintenance domain. For the creation method, see 25.2.4 Creating an MD. The parameters of the maintenance domain are as follows:
l l

Maintenance Domain Name: MD Maintenance Domain Level: 4

Step 2 On the T2000, select NE2 to create the maintenance domain. For the creation method, see 25.2.4 Creating an MD. The parameters of the maintenance domain are as follows:
l l

Maintenance Domain Name: MD Maintenance Domain Level: 4

NOTE

The maintenance domain names and levels of NE1 and NE2 should be consistent, and then NE1 and NE2 are in the same maintenance domain.

Step 3 On the T2000, select NE1 to create the maintenance association for Company A. For the creation method, see 25.2.5 Creating an MA. The parameters of the maintenance association are as follows:
l l l l

Maintenance Domain Name: MD Maintenance Association Name: MA Relevant Service: 1-E-Line-1 CC Test Transmit Period (ms): 3.33 ms

Step 4 On the T2000, select NE2 to create the maintenance association for Company A. For the creation method, see 25.2.5 Creating an MA. The parameters of the maintenance association are as follows:
l l l l

Maintenance Domain Name: MD Maintenance Association Name: MA Relevant Service: 1-E-Line-1 CC Test Transmit Period (ms): 3.33 ms

Step 5 On the T2000, select NE1 to create the MEP. For the creation method, see 25.2.6 Creating a MEP Maintenance Point. The parameters of the MEP are as follows:
l l l l l l

Maintenance Domain Name: MD Maintenance Association Name: MA Board: 19-ETFC Port: 1 (Port-1) VLAN: 100 MP ID: 1
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-75

Issue 01 (2009-06-30)

20 Configuring an Ethernet Service

l l

OptiX iManager T2000 Operation Guide for PTN NE Management

Direction: Ingress CC Status: Active

Step 6 On the T2000, select NE2 to create the MEP. For the creation method, see 25.2.6 Creating a MEP Maintenance Point. The parameters of the MEP are as follows:
l l l l l l l l

Maintenance Domain Name: MD Maintenance Association Name: MA Board: 19-ETFC Port: 1 (Port-1) VLAN: 100 MP ID: 2 Direction: Ingress CC Status: Active

Step 7 On the T2000, select NE1 to add a remote MEP. For the operation method, see 25.2.7 Adding a Remote MEP of the MA. The parameters of the remote MEP are as follows:
l l l

Maintenance Domain Name: MD Maintenance Association Domain Name: MA Remote Maintenance Point ID: 2

Step 8 On the T2000, select NE2 to add a remote MEP. For the operation method, see 25.2.7 Adding a Remote MEP of the MA. The parameters of the remote MEP are as follows:
l l l

Maintenance Domain Name: MD Maintenance Association Domain Name: MA Remote Maintenance Point ID: 1

Step 9 On the T2000, select NE1 to perform the CC test. For the operation method, see 25.2.9 Performing a Continuity Check.
NOTE

If the MEP of NE2 does not receive the CC packets from NE1 in a period of time (for example, 3.25 times of the transmission period), the MEP automatically reports the ETH_CFM_LOC alarm. If the ETH_CFM_LOC alarm is not reported, the connectivity of the service from NE1 to NE2 is normal.

Step 10 On the T2000, select NE2 to perform the CC test. For the operation method, see 25.2.9 Performing a Continuity Check.
NOTE

If the MEP of NE1 does not receive the CC packets from NE2 in a period of time (for example, 3.25 times of the transmission period), the MEP automatically reports the ETH_CFM_LOC alarm. If the ETH_CFM_LOC alarm is not reported, the connectivity of the service from NE2 to NE1 is normal.

----End

20-76

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

20.10 Configuration Case of the UNI-NNI E-Line Service Carried by the QinQ Link
The configuration case illustrates how to configure a UNI-NNI E-Line service carried by the QinQ link. You can understand the configuration further by viewing the configuration flow diagram. The configuration case covers the service planning, service configuration and verification of the E-Line service. 20.10.1 Case Description This section describes the networking diagram for transmission of isolated services between companies. 20.10.2 Service Planning The Ethernet services between branches of a company are carried by the QinQ. When planning such an Ethernet service, you need to plan the NE information, QinQ information, and service information. 20.10.3 Configuring the E-Line Service Configure the E-Line service at the source NE and sink NE to realize the UNI-NNI E-Line service carried by the QinQ link. 20.10.4 Verifying the Correctness of Service Configuration After the E-Line service is configured, the correctness of service configuration should be verified. The Ethernet OAM is used to verify the correctness of Ethernet service configuration.

20.10.1 Case Description

This section describes the networking diagram for transmission of isolated services between companies. As shown in Figure 20-18, both Company A and Company B have branches in City 1 and City 2. Branches of each company need to communicate with each other. The traffic from the two companies must be isolated. The internal VLANs of Company A range from 1 to 100 and the internal VLANs of Company B range from 1 to 200. To isolate the traffic of the two companies, different S-VLANs are added to packets from different companies at the network side. The branches of Company A require the common Internet access service (CIR = 10 Mbit/s, PIR = 30 Mbit/s). The branches of Company B require the data service (CIR = 30 Mbit/s, PIR = 50 Mbit/s).

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

20-77

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 20-18 Networking diagram for the UNI-NNI E-Line service carried by the QinQ link
The internal network of Company A VLAN = 1-100 V-UNI for A Company : 19-ETFC-1 V-UNI for B Company : 19-ETFC-2 NNI : 1-EG16-1 A VLAN tag (VLAN = 30) is added to the packet of Company A The internal network of Company A VLAN = 1-100 NE2 City2
A Company

A Company

NE 1

City1 PSN
B Company

The internal network of Company B VLAN = 1-200 A VLAN tag (VLAN = 40) is added to the packet of Company B NNI : 1-EG16-1

City2

B Company

V-UNI for A Company : 19-ETFC-1 V-UNI for B Company : 19-ETFC-2

The internal network of Company B VLAN = 1-200

20.10.2 Service Planning

The Ethernet services between branches of a company are carried by the QinQ. When planning such an Ethernet service, you need to plan the NE information, QinQ information, and service information. Table 20-15 lists the configuration parameters of NEs. Table 20-15 Configuration parameters of NEs NE Interface 19-ETFC-1(Port-1) Interface Attribute Port Mode: Layer 2 Encapsulation Type: 802.1Q NE1 Tag: Tag Aware 19-ETFC-2(Port-2) Port Mode: Layer 2 Encapsulation Type: 802.1Q Tag: Tag Aware

20-78

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

NE

Interface 1-EG16-1(Port-1)

Interface Attribute Port Mode: Layer 2 Encapsulation Type: QinQ Tag: Tag Aware

19-ETFC-1(Port-1)

Port Mode: Layer 2 Encapsulation Type: 802.1Q Tag: Tag Aware

19-ETFC-2(Port-2) NE2

Port Mode: Layer 2 Encapsulation Type: 802.1Q Tag: Tag Aware

1-EG16-1(Port-1)

Port Mode: Layer 2 Encapsulation Type: QinQ Tag: Tag Aware

Table 20-16 lists the planning details on the QinQ link that carries the service. Table 20-16 Planning of the QinQ link carrying the service Parameter QinQ Link ID Board Port S-Vlan ID Enable Bandwidth CIR (kbit/s) PIR (kbit/s) Service of Company A 1 1-EG16 1(Port-1) 30 Enable 10000 30000 Service of Company B 2 1-EG16 1(Port-1) 40 Enable 30000 50000

Table 20-17 shows the planning details on the E-Line service. Table 20-17 Planning of the UNI-NNI E-Line service carried by the QinQ link Parameter Service ID Service Name Direction
Issue 01 (2009-06-30)

Company A 1 E-Line-1 UNI-NNI

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Company B 1 E-Line-2 UNI-NNI

20-79

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Parameter UNI VLANs Bearer Type QinQ Link ID BPDU MTU(byte)

Company A 19-ETFC-1 1-100 QinQ Link 1 Not Transparently Transmitted 1526

Company B 19-ETFC-2 1-200 QinQ Link 2 Not Transparently Transmitted 1526

20.10.3 Configuring the E-Line Service

Configure the E-Line service at the source NE and sink NE to realize the UNI-NNI E-Line service carried by the QinQ link.

Prerequisite
You must understand the networking, requirements and service planning of the example.

Procedure
Step 1 Configure interfaces: 1. 2. In the NE Explorer, select NE1 and choose Configuration > Interface Management > Ethernet Interface from the Function Tree to configure the network-side interface. In the General Attributes tab, select the 19-ETFC-1(Port-1), 19-ETFC-2(Port-2) and 1EG16-1(Port-1). Set the parameters such as Port Mode, Encapsulation Type as required, and click Apply. The configuration parameters are as follows:
l

Port: 19-ETFC-1(Port-1), 19-ETFC-2(Port-2)

Enable Port: Enabled Port Mode: Layer 2 Encapsulation Type: 802.1Q Working Mode: Auto-Negotiation (Set the working modes of the local port and opposite port as the same.) Max Frame: 1620 (Set this parameter according to the length of data packets.) Enable Port: Enabled Port Mode: Layer 2 Encapsulation Type: QinQ Working Mode: Auto-Negotiation Max Frame: 1620
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

Port: 1-EG16-1(Port-1)

20-80

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

3.

In the Layer 2 Attributes tab, select the 19-ETFC-1(Port-1) and 19-ETFC-2(Port-2). Set the TAG to Tag Aware. Click Apply. The configuration parameters are as follows:
l l

Port: 19-ETFC-1(Port-1), 19-ETFC-2(Port-2) Tag: Tag Aware

If a port is set to Tag Aware, this port can transparently transmits the data packet with the VLAN ID (Tag). If the data packet does not contain the VLAN ID (Untag), this packet is discarded. If the port is set to Access, the port adds the default VLAN ID to the signal packet without the VLAN ID (Untag). If the signal contains the VLAN ID (Tag), this packet is discarded. If the port is set to Hybrid, the port adds the default VLAN ID (Untag) to the signal packet without the VLAN ID (Untag). If the signal packet contains the VLAN ID (Tag), the packet is transparently transmitted.

4.

In the NE Explorer select NE2, set the parameters of 1-EG16-1(Port-1), 19-ETFC-1(Port-1) and 19-ETFC-2(Port-2) by following Step 1.1 to Step 1.3. The configuration parameters are as follows:
l

General Attributes

Port: 1-EG16-1(Port-1)

Enable Port: Enabled Port Mode: Layer 2 Encapsulation Type: QinQ Working Mode: Auto-Negotiation Max Frame: 1620 Enable Port: Enabled Port Mode: Layer 2 Encapsulation Type: 802.1Q Working Mode: Auto-Negotiation Max Frame: 1620

Port: 19-ETFC-1(Port-1), 19-ETFC-2(Port-2)

Layer 2 Attributes

Port: 19-ETFC-1(Port-1), 19-ETFC-2(Port-2) TAG: Tag Aware

Step 2 Create QinQ Links. 1. 2. In the NE explorer, select NE1 and choose Ethernet Service Management > QinQ Link. Click New. Set the parameters of the link from NE1 to NE2 in Create QinQ Link dialog box displayed, and click Apply. The configuration parameters are as follows:
l

QinQ Link between branches of Company A

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-81

Issue 01 (2009-06-30)

20 Configuring an Ethernet Service

l

OptiX iManager T2000 Operation Guide for PTN NE Management

QinQ Link ID: 1 Board: 1-EG16 Port: 1-(Port-1) S-Vlan ID: 30 QinQ Link ID: 2 Board: 1-EG16 Port: 1-(Port-1) S-Vlan ID: 40

QinQ Link between branches of Company B

3.

In the NE Explorer select NE2. Create the link from NE2-NE1 by following the previous two steps. The configuration parameters are as follows:
l

QinQ Link between branches of Company A

QinQ Link ID: 1 Board: 1-EG16 Port: 1-(Port-1) S-Vlan ID: 30 (Add an S-Vlan tag with ID of 30 for the services between branches of Company A so that the services of Company A are isolated from the services of Company B.) QinQ Link ID: 2 Board: 1-EG16 Port: 1-(Port-1) S-Vlan ID: 40 (Add an S-Vlan tag with ID of 40 for the services between branches of Company B so that the services of Company B are isolated from the services of Company A.)

QinQ Link between branches of Company B

Step 3 Create two UNI-NNI E-Line services. 1. 2. In the NE explorer, select NE1 and choose Ethernet Service Management > E-Line Service. Click New. Set the parameters such as Service ID, Service Name, Port, VLANs in the New E-Line Service dialog box displayed. Click Apply. The configuration parameters are as follows:
l

Service between branches of Company A

Service ID: 1 Service Name: E-Line-1 Direction: UNI-NNI BPDU: Not Transparently Transmitted Port: 19-ETFC-1(Port-1) VLANs: 1-100 Bearer Type: QinQ Link
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

20-82

OptiX iManager T2000 Operation Guide for PTN NE Management

l

20 Configuring an Ethernet Service

QinQ Link ID: 1 Service ID: 2 Service Name: E-Line-2 Direction: UNI-NNI BPDU: Not Transparently Transmitted Port: 19-ETFC-2(Port-2) VLANs: 1-200 Bearer Type: QinQ Link QinQ Link ID: 2

Service between branches of Company B

3.

In the NE Explore select NE2. Create an E-Line service from NE2 to NE1, by following Step 3.1 to Step 3.2. The configuration parameters are as follows:
l

Service between branches of Company A

Service ID: 1 Service Name: E-Line-1 Direction: UNI-NNI BPDU: Not Transparently Transmitted Port: 19-ETFC-1(Port-1) VLANs: 1-100 Bearer Type: QinQ Link QinQ Link ID: 1 Service ID: 2 Service Name: E-Line-2 Direction: UNI-NNI BPDU: Not Transparently Transmitted Port: 19-ETFC-2(Port-2) VLANs: 1-200 Bearer Type: QinQ Link QinQ Link ID: 2

Service between branches of Company B

----End

20.10.4 Verifying the Correctness of Service Configuration

After the E-Line service is configured, the correctness of service configuration should be verified. The Ethernet OAM is used to verify the correctness of Ethernet service configuration.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

20-83

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Context
The connectivity of the UNI-UNI E-Line service need no OAM verification. By default, the configuration is regarded as correct. In the case of the UNI-NNI E-Line service carried by a port, the OAM verification method is similar to that of the UNI-NNI E-Line service carried by PWs. The UNI-NNI E-Line service carried by PWs is taken as an example. As shown in Figure 20-19, to verify the correctness of service configuration, the Ethernet OAM should be configured. Figure 20-19 OAM of the E-Line service
MD MA

MEP A Company

NE 1

NE 2

MEP

A Company

MEP

MEP B Company

B Company

City2 MA

City1

Unicast Tunnel PW

MD: Maintenance Domain MA: Maintenance Association MEP: Maintenance End Point

As shown in the previous figure, E-Line services, which are carried and isolated by PWs, are available between branches of Company A and branches of Company B. To verify the configuration correctness of the two E-Line services, the Ethernet OAM should be configured. The verification of the E-Line service of Company A is taken as an example.

Procedure
Step 1 On the T2000, select NE1 to create the maintenance domain. For the creation method, see 25.2.4 Creating an MD. The parameters of the maintenance domain are as follows:
l l

Maintenance Domain Name: MD Maintenance Domain Level: 4

Step 2 On the T2000, select NE2 to create the maintenance domain. For the creation method, see 25.2.4 Creating an MD. The parameters of the maintenance domain are as follows:
l l

Maintenance Domain Name: MD Maintenance Domain Level: 4

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

20-84

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

20 Configuring an Ethernet Service

The maintenance domain names and levels of NE1 and NE2 should be consistent, and then NE1 and NE2 are in the same maintenance domain.

Step 3 On the T2000, select NE1 to create the maintenance association for Company A. For the creation method, see 25.2.5 Creating an MA. The parameters of the maintenance association are as follows:
l l l l

Maintenance Domain Name: MD Maintenance Association Name: MA Relevant Service: 1-E-Line-1 CC Test Transmit Period (ms): 3.33 ms

Step 4 On the T2000, select NE2 to create the maintenance association for Company A. For the creation method, see 25.2.5 Creating an MA. The parameters of the maintenance association are as follows:
l l l l

Maintenance Domain Name: MD Maintenance Association Name: MA Relevant Service: 1-E-Line-1 CC Test Transmit Period (ms): 3.33 ms

Step 5 On the T2000, select NE1 to create the MEP. For the creation method, see 25.2.6 Creating a MEP Maintenance Point. The parameters of the MEP are as follows:
l l l l l l l l

Maintenance Domain Name: MD Maintenance Association Name: MA Board: 19-ETFC Port: 1 (Port-1) VLAN: 100 MP ID: 1 Direction: Ingress CC Status: Active

Step 6 On the T2000, select NE2 to create the MEP. For the creation method, see 25.2.6 Creating a MEP Maintenance Point. The parameters of the MEP are as follows:
l l l l l l l l

Maintenance Domain Name: MD Maintenance Association Name: MA Board: 19-ETFC Port: 1 (Port-1) VLAN: 100 MP ID: 2 Direction: Ingress CC Status: Active
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-85

Issue 01 (2009-06-30)

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 7 On the T2000, select NE1 to add a remote MEP. For the operation method, see 25.2.7 Adding a Remote MEP of the MA. The parameters of the remote MEP are as follows:
l l l

Maintenance Domain Name: MD Maintenance Association Domain Name: MA Remote Maintenance Point ID: 2

Step 8 On the T2000, select NE2 to add a remote MEP. For the operation method, see 25.2.7 Adding a Remote MEP of the MA. The parameters of the remote MEP are as follows:
l l l

Maintenance Domain Name: MD Maintenance Association Domain Name: MA Remote Maintenance Point ID: 1

Step 9 On the T2000, select NE1 to perform the CC test. For the operation method, see 25.2.9 Performing a Continuity Check.
NOTE

If the MEP of NE2 does not receive the CC packets from NE1 in a period of time (for example, 3.25 times of the transmission period), the MEP automatically reports the ETH_CFM_LOC alarm. If the ETH_CFM_LOC alarm is not reported, the connectivity of the service from NE1 to NE2 is normal.

Step 10 On the T2000, select NE2 to perform the CC test. For the operation method, see 25.2.9 Performing a Continuity Check.
NOTE

If the MEP of NE1 does not receive the CC packets from NE2 in a period of time (for example, 3.25 times of the transmission period), the MEP automatically reports the ETH_CFM_LOC alarm. If the ETH_CFM_LOC alarm is not reported, the connectivity of the service from NE2 to NE1 is normal.

----End

20.11 Configuration Case of the E-LAN Service

This section describes a configuration example of the E-LAN service. A configuration flow diagram is provided to describe the process of service configuration. The configuration example includes the service planning and E-LAN service configuration. 20.11.1 Case Description This section describes the functional requirement, networking diagram, and service planning. 20.11.2 Configuring E-LAN Service for the NE This section describes how to configure the E-LAN service for the NE.

20.11.1 Case Description

This section describes the functional requirement, networking diagram, and service planning.

Requirement and Networking Diagram

As shown in Figure 20-20, the three CE networks need communication with each other. Each CE network has the same VLAN value, that is, 100.
20-86 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Among the CE networks, three types of services, including the voice service, data service, and common Internet access service, are available. Each CE requires a network bandwidth of 100 Mbit/s. The complex traffic classification can be performed at the access side, and different QoS policies for assured bandwidth can be configured. Figure 20-20 Networking diagram for the E-LAN service
CE 1 UNI for CE1: 1-EG16-19-ETFC-1 NNI for CE2: 1-EG16-20-POD41-1 NNI for CE3: 1-EG16-20-POD41-2 FE NE 1 MPLS Tunnel 3 NE 3 MPLS Tunnel 1 PSN MPLS Tunnel 2 FE
VLAN=100

VLAN=100

UNI for CE3: 1-EG16-19-ETFC-1 NNI for CE1: 1-EG16-20-POD41-1 NNI for CE2: 1-EG16-20-POD41-2

CE 3

NE 2 FE CE 2 UNI for CE2: 1-EG16-19-ETFC-1 NNI for CE3: 1-EG16-20-POD41-1 NNI for CE1: 1-EG16-20-POD41-2

VLAN=100

Service Planning
In the network, the service is carried by a PW. Thus, the parameters related to the PW and MPLS tunnel should be planned. In this example, the tunnel is created in the manner of fast creation of a dynamic tunnel. Table 20-18 lists the planning of the tunnel that carries the PW. Table 20-18 Planning of the tunnel that carries the PW Field Tunnel ID Tunnel Name Signaling Type Schedulin g Type
Issue 01 (2009-06-30)

Forward Tunnel 1 1 E-LAN Dynamic E-LSP

Reverse Tunnel 1 2 E-LAN Dynamic E-LSP

Forward Tunnel 2 3 E-LAN Dynamic E-LSP

Reverse Tunnel 2 4 E-LAN Dynamic E-LSP

Forward Tunnel 3 5 E-LAN Dynamic E-LSP

Reverse Tunnel 3 6 E-LAN Dynamic E-LSP

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

20-87

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Field Bandwidt h Source NE Sink NE Route Constraint Port IP Address

Forward Tunnel 1 100 Mbit/s NE 1 NE 2 -

Reverse Tunnel 1 100 Mbit/s NE 2 NE 1 -

Forward Tunnel 2 100 Mbit/s NE 2 NE 3 -

Reverse Tunnel 2 100 Mbit/s NE 3 NE 2 -

Forward Tunnel 3 100 Mbit/s NE 1 NE 3 -

Reverse Tunnel 3 100 Mbit/s NE 3 NE 1 -

Table 20-19 lists the planning of the Ethernet service. Table 20-19 Planning of the E-LAN service carried by a PW Field Service ID Service Name BPDU Tag Type Self-Learning MAC Address MAC Address Learning Mode MTU (byte) NE 1 1 E-LAN Not Transparently Transmitted C-Awared Enabled SVL 1526 NE 2 1 E-LAN Not Transparently Transmitted C-Awared Enabled SVL 1526 NE 3 1 E-LAN Not Transparently Transmitted C-Awared Enabled SVL 1526

Table 20-20 lists the planning of the UNI port for each NE. Table 20-20 Planning of the UNI port Field Port VLAN Value NE 1 1-EG16-19-ETFC-1 100 NE 2 1-EG16-19-ETFC-1 100 NE 3 1-EG16-19-ETFC-1 100

Table 20-21 lists the planning of the NNI PW for each NE.
20-88 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Table 20-21 Planning of the PW Field PW ID PW Signaling Type PW Type Direction PW Ingress Label PW Egress Label Peer IP Tunnel NE 1 10 Static 20 Static NE 2 20 Static 30 Static NE 3 30 Static 10 Static

Ethernet Bidirectio nal 20

Ethernet Bidirectio nal 40

Ethernet Bidirectio nal 20

Ethernet Bidirectio nal 40

Ethernet Bidirectio nal 30

Ethernet Bidirectio nal 30

30 1.1.1.3 Tunnel 3

20 1.1.1.2 Tunnel 1

40 1.1.1.1 Tunnel 1

30 1.1.1.3 Tunnel 2

40 1.1.1.2 Tunnel 2

20 1.1.1.1 Tunnel 3

In the case of the split horizon group, the interfaces at the network side of each PE NE should be configured into a split horizon group. In this way, the broadcast storm caused by the mutually forwarded data of the network side port can be prevented. In the case of unknown frame processing, broadcast is planned.

20.11.2 Configuring E-LAN Service for the NE

This section describes how to configure the E-LAN service for the NE.

Prerequisite
You must understand the networking, requirements and service planning of the example.

Procedure
Step 1 On the T2000, configure the E-LAN service for NE1. For the configuration method, see 20.3.3 Creating an E-LAN Service. The parameters related to the E-LAN service are as follows:
l l l l l l

Service ID: 1 Service Name: E-LAN BPDU: Not Transparently Transmitted Tag Type: C-Awared Self-Learning MAC Address: Enabled MAC Address Learning Mode: SVL
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-89

Issue 01 (2009-06-30)

20 Configuring an Ethernet Service

l l l l

OptiX iManager T2000 Operation Guide for PTN NE Management

MTU (byte): 1526 Split Horizon Group: 20-POD41-1, 20-POD41-2 Unknown Frame Processing: Broadcast UNI:

Configure Port: 1-EG16-19-ETFC-1 VLANs: 100 PW ID: 10 PW Signaling Type: Static PW Type: Ethernet Direction: Bidirectional PW Ingress Label: 20 PW Egress Label: 30 Peer IP: 1.1.1.3 Tunnel: Tunnel 3 PW ID: 20 PW Signaling Type: Static PW Type: Ethernet Direction: Bidirectional PW Ingress Label: 40 PW Egress Label: 20 Peer IP: 1.1.1.2 Tunnel: Tunnel 1

NNI PW parameters:

Step 2 On the T2000, configure the E-LAN service for NE2. For the configuration method, see 20.3.3 Creating an E-LAN Service. The parameters related to the E-LAN service are as follows:
l l l l l l l l l l

Service ID: 1 Service Name: E-LAN BPDU: Not Transparently Transmitted Tag Type: C-Awared Self-Learning MAC Address: Enabled MAC Address Learning Mode: SVL MTU (byte): 1526 Split Horizon Group: 20-POD41-1, 20-POD41-2 Unknown Frame Processing: Broadcast UNI:

Configure Port: 1-EG16-19-ETFC-1 VLANs: 100

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

20-90

OptiX iManager T2000 Operation Guide for PTN NE Management

l

20 Configuring an Ethernet Service

Parameters of the PW for the NNI:

PW ID: 20 PW Signaling Type: Static PW Type: Ethernet Direction: Bidirectional PW Ingress Label: 20 PW Egress Label: 40 Peer IP: 1.1.1.1 Tunnel: Tunnel 1 PW ID: 30 PW Signaling Type: Static PW Type: Ethernet Direction: Bidirectional PW Ingress Label: 40 PW Egress Label: 30 Peer IP: 1.1.1.3 Tunnel: Tunnel 2

Step 3 On the T2000, configure the E-LAN service for NE3. For the configuration method, see 20.3.3 Creating an E-LAN Service. The parameters related to the E-LAN service are as follows:
l l l l l l l l l l

Service ID: 1 Service Name: E-LAN BPDU: Not Transparently Transmitted Tag Type: C-Awared Self-Learning MAC Address: Enabled MAC Address Learning Mode: SVL MTU (byte): 1526 Split Horizon Group: 20-POD41-1, 20-POD41-2 Unknown Frame Processing: Broadcast UNI:

Configure Port: 1-EG16-19-ETFC-1 VLANs: 100 PW ID: 10 PW Signaling Type: Static PW Type: Ethernet Direction: Bidirectional PW Ingress Label: 30 PW Egress Label: 20
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-91

Parameters of the PW for the NNI:

Issue 01 (2009-06-30)

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Peer IP: 1.1.1.1 Tunnel: Tunnel 3 PW ID: 30 PW Signaling Type: Static PW Type: Ethernet Direction: Bidirectional PW Ingress Label: 30 PW Egress Label: 40 Peer IP: 1.1.1.2 Tunnel: Tunnel 2

----End

20.12 Configuration Case of the E-AGGR Service

A case is provided here to show the configuration of the E-AGGR service, and the configuration flow. The configuration case covers the service planning and configuration of the E-AGGR service. 20.12.1 Case Description The case description covers the functional requirements, networking diagram and service planning. 20.12.2 Configuring a UNIs-NNI E-AGGR Service for NEs The E-AGGR service is accessed to the UNIs of multiple NEs and then aggregated at the NNI. This section describes how to configure the UNIs-NNI E-AGGR service for NEs. 20.12.3 Configuring an NNIs-UNI E-AGGR Service for NEs The E-AGGR service is accessed to the NNIs of multiple NEs and then aggregated at the UNI. This section describes how to configure the NNIs-UNI E-AGGR service for NEs.

20.12.1 Case Description

The case description covers the functional requirements, networking diagram and service planning.

Networking and Requirements

As shown in Figure 20-21, NE1 and Node B connected to NE2 need communicate with the RNC connected to NE3. In this case, NE1 and NE2 can aggregate the services accessed from Node B to two MPLS tunnels respectively. The two MPLS tunnel then transports the services to NE3, which then aggregates the services to the RNC. All services of Node B have VLAN, whose value is 100. Node B is connected to the equipment through the FE interface. RNC is connected to the equipment through the GE interface. The NEs are connected through the STM-4 POS interfaces for networking. Services on NodeB 1 are audio services (CIR = 15 Mbit/s, PIR = 30 Mbit/s). Services on NodeB 2 are data services (CIR = 30 Mbit/s, PIR = 50 Mbit/s).
20-92 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Services on NodeB 3 are audio services (CIR = 15 Mbit/s, PIR = 30 Mbit/s). Services on NodeB 4 are data services (CIR = 30 Mbit/s, PIR = 50 Mbit/s). Figure 20-21 E-AGGR service networking diagram
Node B 1 Node B 2 UNI for NodeB 1:1-EG16-19-ETFC-1 UNI for NodeB 2:1-EG16-19-ETFC-2 NNI:1-EG16-20-POD41-1 UNI for RNC:1-EG16-1 NE 1 NNI for NE 1:1-EG16-20-POD41-1 NNI for NE 2:1-EG16-20-POD41-2 NE 3 GE RNC

MPLS Tunnel 1

MPLS Tunnel 2 Node B 3

NE 2

Node B 4 UNI for NodeB 3:1-EG16-19-ETFC-1 UNI for NodeB 4:1-EG16-19-ETFC-2 NNI:1-EG16-20-POD41-1

Node B

Service Planning
Services are carried by the PW in the network. Configure related parameters of the PW and MPLS tunnel. In this case, a dynamic tunnel is quickly created by trail. Table 20-22 lists details on planning of the tunnel that carries the PW. Table 20-22 Planning of the tunnel carrying the PW Parameter Tunnel ID Tunnel Name Signaling Type Schedule Type Bandwidth
Issue 01 (2009-06-30)

Positive Tunnel 1 1 E-AGGR Dynamic E-LSP 45 Mbit/s

Reverse Tunnel 1 2 E-AGGR Dynamic E-LSP 45 Mbit/s

Positive Tunnel 2 3 E-AGGR Dynamic E-LSP 45 Mbit/s

Reverse Tunnel 2 4 E-AGGR Dynamic E-LSP 45 Mbit/s

20-93

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Parameter Source NE Sink NE Route Constraint Port IP Address

Positive Tunnel 1 NE1 NE3 -

Reverse Tunnel 1 NE3 NE1 -

Positive Tunnel 2 NE2 NE3 -

Reverse Tunnel 2 NE3 NE2 -

Table 20-23 lists details on the planning of the Ethernet service. Table 20-23 Planning of the E-AGGR service carried by the PW Parameter Service ID Service Name MTU(byte) NE1 1 E-Aggr-1 1526 NE2 2 E-Aggr-2 1526 NE3 3 E-Aggr-3 1526

Table 20-24 lists details on planning of the PW at NNI. Table 20-24 Planning of the PW Parameter Location PW ID PW Signaling Type PW Type Direction PW Ingress Label PW Egress Label Peer IP Tunnel NE1 Sink 10 Static Ethernet Mode Bidirectional 20 20 1.1.1.3 Tunnel 1 NE2 Sink 20 Static Ethernet Mode Bidirectional 30 30 1.1.1.3 Tunnel 2 NE3: NNI for NE1 Source 10 Static Ethernet Mode Bidirectional 20 20 1.1.1.1 Tunnel 1 NE3: NNI for NE2 Source 20 Static Ethernet Mode Bidirectional 30 30 1.1.1.2 Tunnel 2

20-94

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

20 Configuring an Ethernet Service

Parameter Bandwidth Limit CIR (kbit/s) PIR (kbit/s)

NE1 Enabled 45000 80000

NE2 Enabled 45000 80000

NE3: NNI for NE1 Enabled 45000 80000

NE3: NNI for NE2 Enabled 45000 80000

Table 20-25 and Table 20-26 lists details on the planning of the VLAN forwarding table of each NE. Table 20-25 Planning of the VLAN forwarding tables of NE1 and NE2 Parameter Source Interface Type Source Interface Source VLAN ID Sink Interface Type Sink Interface Sink VLAN ID NE1 V-UNI 1-EG16-19ETFC-1 100 V-NNI 1-EG16-20POD41-1 1 V-UNI 1-EG16-19ETFC-2 100 V-NNI 1-EG16-20POD41-1 2 NE2 V-UNI 1-EG16-19ETFC-1 100 V-NNI 1-EG16-20POD41-1 3 V-UNI 1-EG16-19ETFC-2 100 V-NNI 1-EG16-20POD41-1 4

Table 20-26 Planning of the VLAN forwarding table of NE3 Parameter Source Interface Type Source Interface Source VLAN ID Sink Interface Type Sink Interface NE3: NNI for NE1 V-NNI 1-EG16-20POD41-1 1 V-UNI 1-EG16-1 V-NNI 1-EG16-20POD41-1 2 V-UNI 1-EG16-1 NE3: NNI for NE2 V-NNI 1-EG16-20POD41-2 3 V-UNI 1-EG16-1 V-NNI 1-EG16-20POD41-2 4 V-UNI 1-EG16-1

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

20-95

20 Configuring an Ethernet Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Parameter Sink VLAN ID

NE3: NNI for NE1 100 200

NE3: NNI for NE2 300 400

20.12.2 Configuring a UNIs-NNI E-AGGR Service for NEs

The E-AGGR service is accessed to the UNIs of multiple NEs and then aggregated at the NNI. This section describes how to configure the UNIs-NNI E-AGGR service for NEs.

Prerequisite
You must understand the networking, requirements and service planning of the example.

Procedure
Step 1 On the T2000, configure a UNIs-NNI E-AGGR service for NE1. For details, see 20.4.2 Creating an E-AGGR Service on a Per-NE Basis. Parameters related to the UNIs-NNI E-AGGR service are as follows.
l

UNI:

Selected Port: 1-EG16-19-ETFC-1 and 1-EG16-19-ETFC-2 VLANs: 100 Location: Sink PW ID: 10 PW Signaling Type: Static PW Type: Ethernet Mode Direction: Bidirectional PW Ingress Label: 20 PW Egress Label: 20 Peer IP: 1.1.1.3 Bandwidth Limit: Enabled CIR (kbit/s): 45000 PIR (kbit/s): 80000

PW parameters of the NNI:

For details on parameters in the VLAN forwarding table, see Table 20-25.

Step 2 On the T2000, configure a UNIs-NNI E-AGGR service for NE2. For details, see 20.4.2 Creating an E-AGGR Service on a Per-NE Basis. Parameters related to the UNIs-NNI E-AGGR service are as follows.
l

UNI:

Selected Port: 1-EG16-19-ETFC-1 and 1-EG16-19-ETFC-2 VLANs: 100

PW parameters of the NNI:

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

20-96

OptiX iManager T2000 Operation Guide for PTN NE Management

l

20 Configuring an Ethernet Service

Location: Sink PW ID: 2 PW Signaling Type: Static PW Type: Ethernet Mode Direction: Bidirectional PW Ingress Label: 3 PW Egress Label: 3 Peer IP: 1.1.1.3 Bandwidth Limit: Enabled CIR (kbit/s): 45000 PIR (kbit/s): 80000

For details on parameters in the VLAN forwarding table, see Table 20-25.

----End

20.12.3 Configuring an NNIs-UNI E-AGGR Service for NEs

The E-AGGR service is accessed to the NNIs of multiple NEs and then aggregated at the UNI. This section describes how to configure the NNIs-UNI E-AGGR service for NEs.

Prerequisite
You must understand the networking, requirements and service planning of the example.

Procedure
Step 1 On the T2000, configure an NNIs-UNI E-AGGR service for NE3. For details, see 20.4.2 Creating an E-AGGR Service on a Per-NE Basis. Parameters related to the NNIs-UNI E-AGGR service are as follows:
l

UNI:

Selected Port: 1-EG16-1 VLANs: 100, 200, 300, 400 Location: Source PW ID: 10 PW Signaling Type: Static PW Type: Ethernet Mode Direction: Bidirectional PW Ingress Label: 20 PW Egress Label: 20 Peer IP: 1.1.1.1 Bandwidth Limit: Enabled CIR (kbit/s): 45000
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20-97

PW1 parameters of the NNI:

Issue 01 (2009-06-30)

20 Configuring an Ethernet Service

l

OptiX iManager T2000 Operation Guide for PTN NE Management

PIR (kbit/s): 80000 Location: Source PW ID: 20 PW Signaling Type: Static PW Type: Ethernet Mode Direction: Bidirectional PW Ingress Label: 30 PW Egress Label: 30 Peer IP: 1.1.1.2 Bandwidth Limit: Enabled CIR (kbit/s): 45000 PIR (kbit/s): 80000

PW2 parameters of the NNI:

For details on parameters in the VLAN forwarding table, see Table 20-26.

----End

20-98

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

21
About This Chapter

Configuring an L3VPN Service

On T2000, You can quickly configure the L3VPN service by using the trail function. 21.1 Introduction to L3VPN A VPN depends on Internet service providers (ISPs) and network service providers (NSPs) to build a virtual private communication network in a public network. The PTN equipment implements the L3VPN function through the BGP/MPLS protocol and other protocols. 21.2 Basic Concepts This topic describes the basic concepts related to L3VPN. 21.3 Application of the L3VPN L3VPN has three application scenarios, which are intranet VPN, extranet VPN, and Hub and Spoke. 21.4 L3VPN Service Configuration Flow This section describes the operation tasks for configuring the L3VPN service and relations among these tasks. When configuring and managing the L3VPN services, follow the configuration flow. 21.5 Configuring an L3VPN Service You can quickly configure the L3VPN services by using the trail function on the T2000. 21.6 L3VPN Service Management In the L3VPN service management, you can search for, filter, query, and modify the L3VPN services, and view the alarms and performance events relevant to the L3VPN services. This management function provides network administrators a method to ensure the normal running of the L3VPN services. 21.7 Configuration Example of an Intranet VPN Service This topic describes a configuration example of the intranet VPN service. A configuration flow diagram is provided to describe the process of service configuration. The configuration example describes the configuration networking diagram, service planning, and configuration process. 21.8 Configuration Example of an Extranet VPN Service This topic describes a configuration example of the extranet VPN service. A configuration flow diagram is provided to describe the process of service configuration. The configuration example describes the configuration networking diagram, service planning, and configuration process.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-1

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

21.9 Configuration Example of a Hub&Spoke VPN Service This topic describes the configuration example of the Hub&Spoke VPN service. A configuration flow diagram is provided to describe the process of service configuration. The configuration example describes the configuration networking diagram, service planning, and configuration process.

21-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

21.1 Introduction to L3VPN

A VPN depends on Internet service providers (ISPs) and network service providers (NSPs) to build a virtual private communication network in a public network. The PTN equipment implements the L3VPN function through the BGP/MPLS protocol and other protocols.

BGP/MPLS VPN
A BGP/MPLS VPN is a Layer-3 virtual private network (L3VPN). On a BGP/MPLS VPN, the Border Gateway Protocol (BGP) advertises VPN routes and the multiprotocol label switching (MPLS) forwards VPN packets on backbone networks of service providers (SPs). Figure 21-1 shows the basic model of a BGP/MPLS VPN. Figure 21-1 Model of a BGP/MPLS VPN
VPN 2 CE Service provider's backbone P P CE
Site

VPN 1
Site

PE PE PE CE VPN 1
Site

VPN 2
Site

P CE

The BGP/MPLS VPN model consists of the following parts:

l

Customer edge (CE): is an edge device on a customer network. A CE has one or more interfaces directly connected to an SP network. The CE can be a router, a switch, or a host. Generally, the CE cannot "sense" VPNs, and need not support MPLS. Provider edge (PE): is an edge device on an SP network. A PE is directly connected to the CE. On an MPLS network, VPN processing is performed on PEs; thus, an MPLS network is PE-intensive. Provider (P): is a backbone device in an SP. A P is not directly connected to CEs. A P need support only the MPLS forwarding capability and need not maintain VPN information.

PEs and Ps are managed by SPs. CEs are managed by users unless the users trust SPs with the management right. A PE can provide the access service for multiple CEs. A CE can access multiple PEs of the same SP or of different SPs.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-3

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

BGP
Different from the Interior Gateway Protocol (IGP), BGP focuses on controlling route transmission and selecting the optimal routes instead of discovering and calculating routes. VPNs use public networks to transmit the VPN data, and the public networks use IGP to discover and calculate their routes. The key to construct a VPN is how to control the transmission of VPN routes and select the optimal route between two PEs. BGP uses TCP with the port number 179 as the transport-layer protocol. The reliability of BGP is thus enhanced. Therefore, VPN routes can be directly exchanged between two non-directly connected PEs. BGP can transmit any information appended to a route. As the optional BGP attributes, the information is transparently forwarded by BGP devices that cannot identify those attributes. VPN routes, thus, can be conveniently transmitted between PEs. When routes are updated, BGP sends only updated routes rather than all the routes. This decreases the bandwidth consumed by the route transmission. The transmission of a great number of routes over a public network becomes possible.

21.2 Basic Concepts

This topic describes the basic concepts related to L3VPN. 21.2.1 Basic Concepts of L3VPN This topic describes the basic concepts of L3VPN, including site, VPN instance, address space overlapping, VPN-IPv4 addresses, and so on. 21.2.2 MP-BGP The PTN equipment uses the MP-BGP protocol to implement the L3VPN function. This topic describes the concepts related to MP-BGP. 21.2.3 Label Allocation of MP-BGP This topic describes how an MP-BGP label is distributed. 21.2.4 VPN Route Selection on PEs VPN route selection on PEs consists of two parts, which are route cross of a private network and tunnel iteration. In the first part, routing information between PEs are processed. In the second part, VPN packets are forwarded. 21.2.5 Advertisement of VPNv4 Routes This topic describes the concepts related to advertisement of VPNv4 routes. 21.2.6 Route Advertisement of a Basic BGP/MPLS VPN This topic describes how routes of a BGP/MPLS VPN are advertised by using a basic BGP/ MPLS VPN as an example. 21.2.7 Packet Forwarding in a Basic BGP/MPLS VPN This topic describes how BGP/MPLS VPN packets are forwarded by using a basic BGP/MPLS VPN as an example.

21.2.1 Basic Concepts of L3VPN

This topic describes the basic concepts of L3VPN, including site, VPN instance, address space overlapping, VPN-IPv4 addresses, and so on.
21-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

Site
The concept of site is frequently used in the VPN technology. The following describes a site from different aspects:
l

A site is a group of IP systems with IP connectivity. IP connectivity can be realized independent from SP networks. As shown in Figure 21-2, in the networks on the left side, the headquarters of X company in city A is a site; the branch of X company in city B is another site. IP devices in the two sites can communicate without through any carrier's network. Figure 21-2 Schematic diagram of sites
Tw o sites Site A One site Site X

CE Carrier's netw ork CE Headquarters of X company in City A Carrier's netw ork CE Headquarters of X company in City A

CE

Branch of X company in City B

Site B

Branch of X company in City B

Sites are classified according to the topology relationship between devices rather than the geographic positions of the devices although the devices in a site are geographically adjacent to each other in general. If two IP systems are geographically separated and connected through private lines, the two systems compose a site if they can communicate without the help of carrier's networks. As shown in Figure 21-2, in the networks on the right side, if the branch network of city B is connected with the headquarters network of city A through private lines instead of carrier's networks, the branch network and the headquarters network compose a site.

The devices in a site may belong to multiple VPNs. In other words, a site may belong to multiple VPNs. As shown in Figure 21-3, the decision-making department of X company in city A (Site A) is allowed to communicate with the research and development (R&D) department in city B (Site B) and the financial department in city C (Site C). Site B and Site C are not allowed to communicate. In this case, two VPNs, namely, VPN 1 and VPN 2 can be established. Site A and Site B belong to VPN 1; Site A and Site C belong to VPN 2. Site A, thus, belongs to multiple VPNs.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21-5

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 21-3 One site belonging to multiple VPNs

City A VPN 1 Site A X Company Decisionmaking department

City B CE X Company R&D department

CE

Site B

VPN 2 City C X Company Financial department Site C CE

Carrier's netw ork

A site is connected to an SP network through CEs. A site may contain more than one CE, but a CE belongs only to one site. According to different sites, you are recommended to use the following devices as CEs:

If the site is a host, use the host as the CE. If the site is a subnet, use switches as CEs. If the site comprises multiple subnets, use routers as CEs.

Sites connected to the same carrier's network can be divided into different sets based on policies. Only sites that belong to the same set can access each other. A set of sites is a VPN.
NOTE

l l l l

In this manual, if two PEs establish BGP sessions and exchange VPN routing information, for one PE, the other PE is called the peer PE. The CE that a PE accesses is called the local CE of the PE. The CE that the peer PE accesses is called the remote CE. In this chapter, IP addresses of the sites are IPv4 addresses.

VPN Instances
A VPN instance is also called a VPN Routing and Forwarding table (VRF). A PE has multiple forwarding tables, including a public routing and forwarding table and one or more VPN instances. That is, a PE has multiple instances, including a public instance and one or more VPN instances.

21-6

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

Figure 21-4 Schematic diagram of VPN instances

VPN1

Site1

CE VPN1 VPN-instance VPN2 VPN-instance

PE

Backbone

Public forwarding table

VPN2

Site2 CE

The differences between a public routing table and a VRF are as follows:
l

A public routing table contains the IPv4 routes of all the PEs and Ps, which are generated by routing protocols or static routes of backbone networks. A VRF contains the routes of all sites that belong to the VPN instance. The VRF is obtained through configuring static routes or by exchanging the VPN route information between a CE and a PE, and between two PEs. A public forwarding table contains the minimum forwarding information extracted from the corresponding public routing table; a VPN forwarding table contains the minimum forwarding information extracted from the corresponding VPN routing table according to the route management policies.

VPN instances on a PE are independent of each other. They are also independent of the public routing and forwarding table. Each VPN instance can be perceived as a virtual device, which maintains an independent address space and has one or more interfaces that connect the PE associated with the instance. In RFC 2547 (BGP/MPLS VPNs), a VPN instance is called the per-site forwarding table. To be more specific, every connection between a CE and a PE corresponds to a VPN instance (not a one-to-one mapping). The VPN instance is bound to the PE interface that connects the CE through manual configuration. The independent address space of a VPN instance is realized by using router distinguishers (RDs). A VPN instance manages VPN membership and routing principles of the directly connected sites by using the VPN target attributes. The following describes RDs and the VPN target in detail.

Relationship Between VPNs, Sites, and VPN Instances

The relationship between VPNs, sites, and VPN instances is as follows:
l

A VPN consists of multiple sites. A site may belong to multiple VPNs.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-7

Issue 01 (2009-06-30)

21 Configuring an L3VPN Service

l

OptiX iManager T2000 Operation Guide for PTN NE Management

A site on each PE is associated with a VPN instance. A VPN instance integrates the VPN member relationship and routing principles of the associated sites. Multiple sites compose a VPN based on the rule of VPN instances. VPN instances and VPNs do not have one-to-one mapping relationship.

Address Space Overlapping

After receiving private routes from a CE, a PE advertises them to other PEs. As a private network, a VPN independently manages an address realm, also called address space. Address spaces of different VPNs may overlap. For example, both VPN1 and VPN2 use addresses on the segment 10.110.10.0/24. Address space overlapping arises. VPNs can use overlapped address spaces in the following situations:
l l

The two VPNs do not have the same site. The two VPNs have the same site; however, the devices in the site and the devices using overlapped address spaces in the VPNs do not access each other.

VPN-IPv4 Addresses
Traditional BGP cannot process routes of VPNs with address spaces overlapping. Suppose both VPN1 and VPN2 use addresses on the segment 10.110.10.0/24, each of them advertises a route to this network segment, and no load balancing is performed between routes of different VPNs. BGP selects only one route from the two routes. The other route is thus lost. The cause to the forementioned problem is that BGP cannot distinguish VPNs with the same IP address prefix. To solve this problem, BGP/MPLS IP VPN uses the VPN-IPv4 address family. A VPN-IPv4 address consists of 12 bytes. The first 8 bytes represent the RD; the last 4 bytes stand for IPv4 address prefix, as shown in Figure 21-5. Figure 21-5 VPN-IPv4 address structure
Router distinguisher (8-byte)
Type field (2-byte) Administrator subfield Assigned number subfield IPv4 address prefix (4-byte)

The valid values of the Type field are as follows:

l

0 The Administrator subfield occupies 2 bytes and the Assigned Number subfield occupies 4 bytes. The Administrator subfield is a 16-bit Autonomous System (AS) number; the Assigned Number subfield is a 32-bit user-defined number.

1 The Administrator subfield occupies 4 bytes and the Assigned Number subfield occupies 2 bytes.

21-8

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

The Administrator subfield is a 32-bit IPv4 address; the Assigned Number subfield is a 16bit user-defined number.
NOTE

When configuring an RD, you only need to specify the Administrator subfield and the Assigned Number subfield. Two types of the configuration formats of an RD are as follows:
l l

The RD format is "16-bit AS number:32-bit user-defined number". For example, 100:1. The RD format is "32-bit IPv4 address:16-bit user-defined number". For example, 172.1.1.1:1.

In this chapter, an RD value does not contain the Type field.

IPv4 addresses with RDs are called the VPN-IPv4 addresses. After receiving IPv4 routes from a CE, a PE converts the routes into globally unique VPN-IPv4 routes and advertises the routes in the public network.

VPN Target
The VPN target, also called route target (RT),is a 32-bit BGP extension community attribute. BGP/MPLS IP VPN uses the VPN target to control the advertisement of VPN routing information. A VPN is associated with one or more VPN target attributes, which have the following types:
l

Export target: After learning the IPv4 routes from directly connected sites, a local PE converts the routes to VPN-IPv4 routes and sets the export target attribute for those routes. As the BGP extension community attribute, the export target attribute is advertised along with the routes. Import target: After receiving the VPN-IPv4 routes from other PEs, a PE checks the export target attribute of the routes. If the export target is identical with the import target of a VPN instance on the PE, the PE adds the route to the VPN routing table.

That is, the VPN target attribute defines the sites that can receive a VPN route, and the sites from which the PE can receive routes. After receiving a route from the directly connected CEs, a PE associates the route with one or more export target attributes. The process during which VPNv4 routes match the import targets of local VPN instances is called the private network route cross. For details, see the following sections. BGP advertises the attributes along with the VPN-IPv4 route to related PEs. After receiving the route, the PEs compare the export target attributes with the import target attributes of all the VPN instances on the PEs. If the export and import attributes are matched, the route is installed to the VPN routing tables. Similar to RDs, a VPN target shown in Figure 21-6 has the following formats:
l

0 The Administrator subfield occupies 2 bytes and the Assigned Number subfield occupies 4 bytes. The Administrator subfield is a 16-bit AS number; the Assigned Number subfield is a 32bit user-defined number.

1 The Administrator subfield occupies 4 bytes and the Assigned Number subfield occupies 2 bytes. The Administrator subfield is a 32-bit IPv4 address; the Assigned Number subfield is a 16bit user-defined number.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21-9

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 21-6 Format of a VPN target

VPN-Target (8-byte) Type field (2-byte) Administrator subfield Assigned number subfield

NOTE

When configuring a VPN target, you only need to specify the Administrator subfield and the Assigned Number subfield. Two types of the configuration format of a VPN target are as follows:
l l

The VPN-Target format is "16-bit AS number:32-bit user-defined number". For example, 100:1. The VPN-Target format is "32-bit IPv4 address:16-bit user-defined number". For example, 172.1.1.1:1.

In this chapter, a VPN target value does not contain the Type field.

The reasons that using VPN target instead of RDs as the extension community attributes are as follows:
l

A VPN-IPv4 route has only one RD, but can be associated with multiple VPN targets. With multiple extension community attributes, BGP can greatly improve the flexibility and scalability of a network. VPN targets are used in controlling route advertisement between different VPNs on a PE. That is, after being configured with the same VPN target, different VPNs on a PE can import routes between each other. On a PE, different VPNs have different RDs; however, the BGP extension community attributes are limited. Using RDs as the attributes to import routes confines the network scalability.

In a BGP/MPLS IP VPN, VPN targets are used to control the advertisement and receipt of VPN routing information between sites. VPN export targets are independent of import targets. An export target and an import target can be configured with multiple values; thus, flexible VPN access control and diversified VPN networking schemes can be implemented. For more information, see Application of the L3VPN.

Relationship Between RD and RT

A BGP/MPLS VPN uses RDs to distinguish the prefixes of IPv4 IP addresses that use the same address space, and uses RTs to control the release of VPN routing information. RDs and RTs are similar in structure, but RDs cannot be replaced with RTs. This is because the RT is an extended group attribute of BGP, the route cancellation packets of BGP do not carry the extended attribute. In this case, the received packets have no RT attribute and you need to define the RD attribute separately.

21.2.2 MP-BGP
The PTN equipment uses the MP-BGP protocol to implement the L3VPN function. This topic describes the concepts related to MP-BGP.

21-10

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

Introduction to MP-BGP
As previously mentioned, the traditional BGP-4 described in the RFC 1771 can manage only the IPv4 routing information, but cannot manage the routes of VPNs with overlapped address spaces. To correctly process VPN routes, VPNs use Multiprotocol Extensions for BGP-4 described in RFC 2858. MP-BGP supports multiple network layer protocols. In an MP-BGP Update message, information about the network layer protocol is described in the Network Layer Reachability Information (NLRI) and the Next Hop fields. MP-BGP uses the address family to differentiate network layer protocols. An address family can be a traditional IPv4 address family or other address families such as VPN-IPv4 address family. For the values of address families, refer to RFC 1700 (Assigned Numbers).
NOTE

The PTN supports multiple MP-BGP extension applications such as VPN extension, which are configured in the corresponding views of the address families. By default, for an IPv4 address family, after the peer address and the AS to which the peer belongs are specified, the local device has the capability of setting up sessions with its peer. For other address families, the capability of setting up sessions must be manually enabled on the local device.

The transmission of VPN member information and VPN-IPv4 routes between PEs is implemented by importing extension community attributes into BGP. The following attributes are introduced in MP-BGP:
l l

MP_REACH_NLRI MP_UNREACH_NLRI

The two attributes are optional non-transitive. BGP speakers without the multiprotocol capability ignore the two attributes and do not pass them to peers. In a VPN, PEs with the multiprotocol capability advertise the VPN routing information to the peer PEs or ASBR PEs supporting multiprotocol through MP-BGP. BGP peers without the multiprotocol capability ignore the attributes, and do not identify and store the VPN routing information.
NOTE

Optional non-transitive is a BGP attribute type. If a BGP device does not support this attribute type, the Update messages with the attributes of this type are ignored, and the messages are not advertised to other peers.

IBGP and EBGP

BGP has two running modes, which are shown in Figure 21-7.
l l

Internal BGP (IBGP) External BGP (EBGP)

When BGP runs in the interior of the autonomous system, it is referred to as IBGP. When BGP runs between different autonomous systems, it is referred to as EBGP.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21-11

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 21-7 BGP running mode

IBGP EBGP EBGP

CE Internet

CE

MP_REACH_NLRI
Multiprotocol Reachable NLRI (MP_REACH_NLRI) is used to advertise reachable routes and information about the next hop. The attribute consists of three parts: Address Family Information, Next Hop Network Address Information, and Network Layer Reachable Information. Figure 21-8 shows the format of the attribute. Figure 21-8 Format of MP_REACH_NLRI
Address Family Information (3bytes) Next Hop Network Address Information (variable length) Network Layer Reachable Information (variable length)

Address Family Information: consists of 2-byte Address Family Identifier (AFI) and 1-byte Subsequent Address Family Identifier (SAFI). An AFI identifies a network layer protocol. The values of network layer protocols are described in RFC 1700 (Address Family Number). For example, 1 indicates IPv4. An SAFI indicates the type of the NLRI field. If the AFI is 1 and the SAFI is 128, it indicates that the address in the NLRI field is an MPLS-labeled VPN-IPv4 address.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

l l

21-12

OptiX iManager T2000 Operation Guide for PTN NE Management

l

21 Configuring an L3VPN Service

Next Hop Network Address Information: consists of the 1-byte length of the next-hop network address and next-hop network address of variable length. A next-hop network address refers to the network address of the next device on the path to the destination. In MP-BGP, before advertising MP_REACH_NLRI to EBGP peers, BGP speakers set the next-hop network addresses as the addresses of the interface that connects the local device and the remote device. The next-hop network address remains unchanged when MP_REACH_NLRI is advertised to IBGP peers. NLRI: consists of three parts: length, label, and prefix. Figure 21-9 shows the format of the NLRI field.

Figure 21-9 Format of the NLRI field with a Label subfield

Length (1 byte) Label (variable length) Prefix (variable length)

l l

Length: indicates the total bits of the label and prefix. Label: consists of one or more labels. The length of a label is 3 bytes. The label format is the same as the MPLS label format. The highest bit indicates whether the label is at the bottom of the label stack; the following three bits are 0; the last 20 bits are labels. Prefix: In a BGP/MPLS IP VPN, the prefix field consists of an RD and IPv4 address prefix.

VPNv4 update messages exchanged between PEs or ASBR PEs carry MP_REACH_NLRI. An Update message can carry multiple reachable routes with the same routing attributes.

MP_UNREACH_NLRI
Multiprotocol Unreachable NLRI (MP_UNREACH_NLRI) is used to inform a peer to delete unreachable routes. Figure 21-10 shows the format of the attribute. Figure 21-10 Format of MP_UNREACH_NLRI
Address Family Identifier (2 bytes) Subsequent Address Family Identifier (1 byte) Withdraw n Routes (variable length)

AFI: Corresponding to the address family values defined in RFC 1700 (Address Family Number), an AFI identifies a network layer protocol. SAFI: Similar to SAFI in MP_REACH_NLRI, an SAFI indicates the NLRI type. Withdrawn Routes: Indicates an unreachable route list, which consists of one or more NLRI fields. In the Withdrawn Routes field, BGP speakers can fill the NLRI field the same as the reachable route advertised before to withdraw the route.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-13

l l

Issue 01 (2009-06-30)

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Update messages carrying MP_UNREACH_NLRI are sent to withdraw the VPN-IPv4 routes. An Update message can carry information about multiple unreachable routes. If the labels of routes to be withdrawn are specified in the messages, the routes with specified labels are withdrawn. If the labels are not specified, only the routes without labels are withdrawn. Update messages with MP_UNREACH_NLRI do not carry any path-attributes. A peer can delete routes based on labels because different routes are assigned with different labels.

Negotiation of the MP-BGP Capability

A BGP device gets to know the negotiation capability of its peer by checking the capability parameters in the Open messages. If the BGP device and its peer support the same function, the BGP device and its peer communicate through the function. The optional parameters of negotiation capability in an Open message consist of three parts: Capability Code, Capability Length, and Capability Value. Figure 21-11 shows the format of the capability parameters. Figure 21-11 Format of BGP capability parameters
Capability Code (1 byte) Capability Length (1 byte) Capability Value (variable length)

Capability Code: uniquely identifies the capability type. The value 1 indicates that the BGP speaker has the MP-BGP capability. Capability Length: indicates the length of the capability field. For MP-BGP, the length of the capability field is 4. Capability Value: indicates the value of the capability field. The length is variable and depends on the type specified in Capability Code. Figure 21-12 shows the format of the Capability Value field in MP-BGP.

The meanings of 2-byte AFI and 1-byte SAFI are the same as those of MP_REACH_NLRI. Res. is a 1-byte reserved field. A sender sets the value to 0, and the receiver ignores the field.

Figure 21-12 Format of the Capability Value field in MP-BGP

AFI Res. SAFI

At present, BGP does not support dynamic capability negotiation. After a BGP speaker advertises an Open message with optional capability fields,
l

If the speaker receives a Notification message from its peer, it indicates the peer does not support the capability. Then the BGP speaker tears down the session with its peer, and
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

21-14

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

sends an Open message without optional capability field to the peer, attempting a new BGP connection.
l

If the peer supports the capability advertisement; however, the capability fields are unknown or unsupported, negotiation fails. Then the BGP speaker tears down the session with its peer, and sends an Open message without the optional capability fields (but may carry other optional capability fields) to the peer, attempting a new BGP connection.

After any change of BGP capability, such as enabling or disabling label-routing capability, enabling or disabling address family capability (IPv4, and VPNv4), and enabling GR capability, the BGP speaker tears down the session with its peer, and then re-negotiates the capability with its peer.

Conditions of Exchanging BGP Routes

MP-BGP peers can exchange routes between each other only if the following conditions are satisfied:
l

The MP-BGP peers have routes to each other. The operation of BGP is triggered by messages that are transmitted through TCP with the port number as 179. To set up the TCP connection between the peers, the MP-BGP peers must be routable. A BGP peer is not necessarily a directly connected device. After a virtual link is set up between a local device and a remote device that run BGP, the remote device becomes a BGP peer of the local device. To improve the stability of a BGP connection, 32-bit LSR ID interface addresses are used to set up the connection. Instead of discovering routes within an AS, BGP generally imports IGP routes, static routes, or direct routes into BGP routing tables.

MP-BGP peers set up and maintain BGP sessions. After a TCP connection is established, an Open message is sent to the peer to attempt a session. After receiving the Open message, the peer responds with a Keepalive message to keep the connection valid. Then the peers begin to exchange messages of other types. MPBGP peers can exchange routes between each other only if the peers can set up and maintain BGP sessions.

Update of VPN-IPv4 Routes

A PE must require its peer to re-send BGP Update messages to refresh routes in the following situations:
l l l

The import policy on the PE changes. VPN instances are added or deleted on the PE. The import VPN targets of the VPN instances are added or deleted on the PE.

In these situations, the PE sends Route Refresh messages carrying AFI and SAFI to the peers, which have successfully negotiated the capability with the PE. If the peers do not support the Route Refresh messages, the PE resets the sessions of the peers. After receiving the messages, the peers re-transmit all the routes that satisfy AFI and SAFI.

21.2.3 Label Allocation of MP-BGP

This topic describes how an MP-BGP label is distributed.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-15

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

In a BGP/MPLS IP VPN, before advertising private routes to related PEs in the backbone network through MP-BGP, a PE must associate the private routes with MPLS labels. The packets transmitted over a backbone network carry MPLS labels. Before being allocated labels, a PE advertises a route that identifies itself to other PEs in the backbone network through IGP. To reduce the number of LSPs on a network, it is recommended to allocate labels only to 32-bit mask loopback interface and configure the LSR ID and the BGP session to use the IP address of the same loopback interface. Several methods of allocating labels exist. The PTN supports the following methods:
l

MPLS label allocation based on routes By default, the PTN allocates a label to each route in a VRF. This method is called one label per route. When the number of the routes is great, the Incoming Label Map (ILM) maintains a great number of entries, which requires high router capacity.

MPLS label allocation based on VPNs A VPN instance is assigned one label. All the routes of the instance share the same label. Thus, a great number of labels are saved.

21.2.4 VPN Route Selection on PEs

VPN route selection on PEs consists of two parts, which are route cross of a private network and tunnel iteration. In the first part, routing information between PEs are processed. In the second part, VPN packets are forwarded.

Route Cross of a Private Network

The routes exchanged between two PEs through MP-BGP are VPNv4 routes. After receiving VPNv4 routes, a PE processes the routes as follows:
l

The PE checks whether the next hop of a route is reachable. If the next hop is unreachable, the route is discarded. The PE discards the routes that do not pass the filtering of the BGP routing policy.

Then the PE matches the remaining routes with the import targets of VPN instances on the PE. The matching process is called route-cross of private networks. The PE matches the VPNv4 routes with local VPN instances without selecting the optimal routes and checking whether the tunnels exist. For a route from the local CE of different VPNs, if the next hop is reachable or can be iterated, the PE also matches the route with the import targets of local VPN instances. The matching process is called local route cross.
NOTE

To correctly forward a packet, a BGP device must find out a directly reachable address, through which the packet can be forwarded to the next hop in the routing table. The route to the directly reachable address is called the dependent route because BGP guides the packet forwarding based on the route. The searching for a dependent route based on the next-hop address is called route iteration.

Tunnel Iteration
To transmit traffic of private networks across a public network, a tunnel is required to transmit the traffic. After the private cross-routes are generated, route iteration based on destination IPv4 prefixes is performed. The proper tunnels (except for the local cross routes) are searched out.
21-16 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

Then the tunnel iteration is performed. The routes are injected into the VPN routing table only after the tunnel iteration succeeds. The process that the routes are iterated to corresponding tunnels is called tunnel iteration.
NOTE

For the details of VPN tunnels, refer to the chapter "VPN Tunnel" in this manual.

After the tunnel iteration succeeds, the tunnel IDs are reserved for subsequent packet forwarding. A tunnel ID uniquely identifies a tunnel. In VPN packet forwarding, the transmission tunnel is searched out according to the tunnel ID.

Selection Rules of Private Routes

Not all the crossed routes that are processed by tunnel iteration are installed to VPN routing tables. Similarly, not all the routes received from the local CE and the local cross routes are injected into VPN routing tables. For multiple routes to the same destination, choose one route based on the following rules if load balancing is not carried out:
l

If a route from the local CE and a crossed route to the same destination exist at the same time, choose the route received from the local CE. If a local crossed route and a crossed route from other PEs to the same destination exist, choose the local crossed route.

For multiple routes to the same destination, choose one route based on the following rules if load balancing is carried out:
l

Preferentially choose the route from the local CE. When one route from the local CE and multiple crossed routes exist, choose the route from the local CE. Load balancing is performed between the routes from the local CE or between the crossed routes instead of between the routes from the local CE and the crossed routes.

21.2.5 Advertisement of VPNv4 Routes

This topic describes the concepts related to advertisement of VPNv4 routes. The PE equipment advertises the IPv4 routes received from the local CE through MP-BGP to VPNv4 routes of the peer PE. The rules of advertising VPN-IPv4 routes of MP-BGP are the same as that of BGP.
l l l

When multiple valid routes exist, a BGP speaker advertises only the best route to its peer. A BGP speaker advertises only the routes used by itself to its peer. A BGP speaker advertises the routes obtained through EBGP to all the BGP peers, both EBGP peers and IBGP peers. A BGP speaker does not advertise the IBGP routes to its IBGP peers. A BGP speaker advertises the IBGP routes to its EBGP peers when the synchronization between BGP and IGP is not enabled. After a connection is set up, a BGP speaker advertises all the BGP routes to its new peer.

l l

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21-17

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

21.2.6 Route Advertisement of a Basic BGP/MPLS VPN

This topic describes how routes of a BGP/MPLS VPN are advertised by using a basic BGP/ MPLS VPN as an example.
NOTE

A basic BGP/MPLS VPN refers to a VPN in which only one carrier exists, the MPLS backbone network is located within an AS, LSPs serve as tunnels, and PEs, Ps, and CEs do not assume multi-roles. (No device assumes the role of both a PE and a CE.)

Introduction
In a basic BGP/MPLS PN, advertisement of VPN routing information involves CEs and PEs. Ps need to maintain the routes of only the backbone network, and they need not know VPN routing information. Generally, PEs maintain the routing information about the VPNs that the PEs access, and they need not maintain all VPN routes. The advertisement of VPN routing information consists of the following parts:
l l l

Route advertisement from the local CE to the ingress PE Route advertisement from the ingress PE to the egress PE Route advertisement from the egress PE to the remote CE

After the whole process of route advertisement, the local CE and the remote CE can set up reachable routes, and VPN routing information can be advertised in the backbone network. The following describes the three parts of the route advertisement.

Route Advertisement from the Local CE to the Ingress PE

After the neighbor or peer relationship is set up between a CE and the directly connected PE, the CE advertises the local routes to the PE. CEs and PEs can run the Routing Information Protocol (RIP), the open shortest path first (OSPF) protocol, or EBGP, or use static routes. The routes advertised by CEs to PEs are standard IPv4 routes regardless of which routing protocol is run. VPN routing and forwarding tables on a PE are isolated from each other and independent of public routing and forwarding tables. After learning routes from a CE, a PE decides to which table the routes should be installed. Static routes and routing protocols cannot enable the PE to make the decision. The decision capability can be realized only through the configuration described as follows.
l

If static routes are used between CEs and PEs, you need to specify VPN instances when you configure the static routes. Generally, static routes are used when CEs are located within a stub VPN, or when CEs are hosts or switches. If CEs are hosts or switches, generally, static routes to the sites to which the CEs belong are configured on the connected PEs, and routing protocols are not required.
NOTE

l l

If a VPN receives the routes outside the VPN or the routes advertised by non-PEs, and then advertises the routes to a PE, the VPN is called a transit VPN. A VPN that receives only the routes within the VPN and the routes advertised by PEs is called a stub VPN.

21-18

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

Using static routes between PEs and CEs features simple configurations, and can prevent route flapping of CEs from affecting the stability of BGP VPNv4 routes of PEs in the backbone network.
l

If IGP is used between CEs and PEs, each VPN uses a process. Different VPNs use different processes. Hence, you need specify VPN instances when you configure the IGP processes. If a site contains backdoor links, the configuration is complicated. For the detailed configuration, see Extension. In addition, there are some restrictions on the usage of IGP between CEs and PEs. If EBGP is run between CEs and PEs, MP-EBGP peers must be configured in the corresponding BGP VPN instance views. When EBGP is run between PEs and CEs, to ensure that routing information is correctly transmitted, nodes located in different places must be assigned with different AS numbers because BGP detects route loops based on AS numbers. However, different VPN sites may use the same AS number because VPN sites use private AS numbers. The AS number of a transit VPN is globally unique.

Route Advertisement from the Ingress PE to the Egress PE

Route advertisement from the ingress PE to the egress PE consists of the following parts:
l

After learning VPN routes from a CE, a PE adds RDs and VPN targets to these standard IPv4 routes. The VPN-IPv4 routes are thus generated. The ingress PE advertises the MP-BGP Update messages containing VPN-IPv4 routes to the egress PE. The Update messages also contain RDs, VPN targets, and MPLS labels. Before the next-hop PE receives the VPN-IPv4 routes, the routes are first filtered by policybased routing (PBR) and then by BGP routing policies.

After receiving the routes, the egress PE performs route cross, tunnel iteration, and route filtering; then decides whether to inject the routes into the VRF or not. For the routes that are received from other PEs and are added to the VPN routing table, the local PE stores the following information, which is used in subsequent packet forwarding:

Values of MPLS labels contained in MP-BGP Update messages Tunnel IDs generated after tunnel iteration succeeds

Route Advertisement from the Egress PE to the Remote CE

A remote CE can learn routes from an egress PE through static routes, RIP, OSPF, and EBGP. The route advertisement from the egress PE to the remote CE is the same as that from the local CE to the ingress PE. Note that the routes advertised by the egress PE to the remote CE is common IPv4 routes.

Example for VPN Route Advertisement

The following takes Figure 21-13 (BGP runs between CEs and PEs, and the tunnels are LSPs) as an example to describe the advertisement of a route from CE2 to CE1.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21-19

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 21-13 Advertisement of a route from CE2 to CE1

CE1 Ingress PE P Egress PE CE2

IGP routing table Import BGP routing table BGP Update VPN routing table

VPN backbone Import

IGP routing table BGP routing table VPN routing table BGP Update

Route cross& tunnel iteration

BGP Update Carrying label,RD, and export RT

Routing table Message

1. 2.

IGP routes are imported into the BGP IPv4 unicast address family of CE2. CE2 advertises an EBGP Update message containing the route to the egress PE. After receiving the message, the egress PE converts the route to a VPN-IPv4 route, and then installs the route to the VPN routing table. If the egress PE has a VPN routing table of another VPN instance, and the import RT of the instance and the export RT of the route are the same, the route is added to the VPN routing table of the instance. At the same time, the egress PE allocates an MPLS label to the route. Then the egress PE adds the label and VPN-IPv4 routing information to the NLRI field and the export target to the extension community attribute field of the MP-IBGP Update message. After that, the egress PE sends the Update message to the ingress PE. After receiving the message, the ingress PE filters the route based on BGP routing policies. If the route fails to pass the filtering, the ingress PE discards the route. If the route passes the filtering, the ingress PE performs the route cross. After the route cross succeeds, the ingress PE performs tunnel iteration based on the destination IPv4 address to find the proper tunnel. If the iteration succeeds, the ingress PE stores the tunnel ID and label, and then adds the route to the VPN routing table of the VPN instance. The ingress PE advertises a BGP Update message containing the route to CE2. The advertised route is a common IPv4 route. After receiving the route, CE2 installs the route to the BGP routing table. CE2 can import the route to the IGP routing table by importing BGP routes to IGP. The preceding process describes the advertisement of a route from CE2 to CE1. To ensure that CE1 and CE2 can communicate, routes need also be advertised from CE1 to CE2. Similar to the preceding process, the advertisement of a route from CE1 to CE2 is not mentioned here.

3.

4.

5. 6.

21.2.7 Packet Forwarding in a Basic BGP/MPLS VPN

This topic describes how BGP/MPLS VPN packets are forwarded by using a basic BGP/MPLS VPN as an example.
21-20 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

NOTE

A basic BGP/MPLS VPN refers to a VPN in which only one carrier exists, the MPLS backbone network is located within an AS, LSPs serve as tunnels, and PEs, Ps, and CEs do not assume multi-roles (No device is a PE and a CE at the same time.)

In a BGP/MPLS VPN backbone network, a P does not know VPN routing information because VPN packets are transmitted between PEs through tunnels. The following takes Figure 21-14 as an example to describe the forwarding of a packet from CE1 to CE2 in the BGP/MPLS VPN. As shown in Figure 21-14, I-L indicates an inner label; O-L indicates an outer label. Figure 21-14 Forwarding of a VPN packet from CE1 to CE2
CE1 Ingress PE P Egress PE CE2

data Push

data

data I-L O-L1

data I-L O-L1

data I-L O-L2

data I-L O-L2

data Pop

data

Out-Label Switch

1. 2.

CE1 sends a VPN packet. After receiving the packet on the interface bound with a VPN instance, the ingress PE processes the packet as follows:
l

Searching for the corresponding VPN forwarding table based on the RD of the VPN instance Matching the destination IPv4 prefix and searching for the corresponding tunnel ID Searching out the tunnel based on the tunnel ID and labeling the packet with I-L Sending the packet through the tunnel and labeling the packet with O-L1 Then the packet with double MPLS labels is transmitted across the backbone network. Each P in the backbone network switches the outer label of the packet.

l l l l

3.

After receiving the packet with double labels, the egress PE delivers the packet to MPLS for processing. MPLS strips off the outer label. In this example, the remaining outer label is O-L2. At this time, the egress PE can identify the inner label. Finding the label is at the bottom of the label stack, the egress PE strips off the inner label. The egress PE sends the packet to CE2. At this time, the packet is a pure IP packet. The packet, thus, is successfully transmitted from CE1 to CE2. CE2 transmits the packet to the destination according to the IP forwarding process.

4. 5.

21.3 Application of the L3VPN

L3VPN has three application scenarios, which are intranet VPN, extranet VPN, and Hub and Spoke.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-21

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Intranet VPN
In the simplest intranet, all the users in a VPN form a closed user group. The users within the group can transmit packets between each other; however, the users cannot communicate with users outside the VPN. This networking mode is called an intranet VPN. The sites within a VPN generally belong to the same organization. In this networking mode, each VPN must be allocated a VPN target as the export target and import target. In addition, the VPN target cannot be used by other VPNs. Figure 21-15 Networking diagram of an intranet VPN
VPN1 VPN1 Import: 100:1 Export: 100:1 Backbone VPN2 Import: 200:1 Export: 200:1 VPN2

CE
Site1

CE
Site3

VPN2

PE VPN2 Import: 200:1 Export: 200:1

PE VPN1 Import: 100:1 Export: 100:1

VPN1

CE
Site2

CE

Site4

As shown in Figure 21-15, PEs allocate the VPN target of 100:1 to VPN1 and the target of 200:1 to VPN2. The two sites in VPN1 can access each other. The two sites in VPN2 can also access each other. The sites in VPN1 and those in VPN2 cannot communicate.

Extranet VPN
If a VPN user needs to access some sites of another VPN, the extranet networking mode can be used. In extranet mode, if a VPN needs to access a shared site, the export target of the VPN must be contained in the import target of the VPN instance on the shared site; the import target of the VPN must be contained in the export target of the VPN instance on the shared site.

21-22

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

Figure 21-16 Networking diagram of an extranet

Site1

CE

VPN1 Import: 100:1 Export: 100:1 VPN1 PE1

Site3

VPN1

PE2

PE3

CE VPN1 Import: 100:1, 200:1 Export: 100:1, 200:1

VPN2 CE
Site2

VPN2 Import: 200:1 Export: 200:1

As shown in Figure 21-16, VPN1 and VPN2 can access Site3 of VPN1.
l l l

PE3 can receive the VPN-IPv4 routes advertised by PE1 and PE2. PE1 and PE2 can receive the VPN-IPv4 routes advertised by PE3. Thus, Site1 and Site3 of VPN1 can access each other; Site2 of VPN2 and Site3 of VPN1 can access each other. PE3 does not advertise the VPN-IPv4 routes from PE1 to PE2 and does not advertise the VPN-IPv4 routes from PE2 to PE1. Therefore, Site1 of VPN1 and Site2 of VPN2 cannot access each other.

Hub&Spoke
In a Hub&Spoke networking model, all users access a center device of access control. The site where the access control device is located is called Hub site; other sites are called Spoke sites. On the side of the Hub site, a device that accesses the VPN backbone network is called HubCE; on the side of spoke sites, a device that accesses the VPN backbone network is called SpokeCE. On the side of the VPN backbone network, a device that accesses the Hub site is called HubPE; a device that accesses Spoke sites is called Spoke-PE. A Spoke site advertises routes to the Hub site; then the Hub site advertises the routes to other Spoke sites. No direct route exists between the Spoke sites. Communications between all Spoke sites are controlled by the Hub site. In networking model of Hub&Spoke, two VPN targets are configured to stand for Hub and Spoke respectively. The configuration of a VPN target on a PE must comply with the following rules:
l

The export target and the import target of the Spoke-PE in the Spoke site are Spoke and Hub respectively. A Hub-PE requires two interfaces or sub-interfaces. One interface or sub-interface receives the routes from Spoke-PEs, and the import target of the VPN instance on the interface is
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-23

Issue 01 (2009-06-30)

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Spoke. The other interface or sub-interface advertises the routes to Spoke-PEs, and the export target of the VPN instance on the interface is Hub. Figure 21-17 Route advertisement from Site2 to Site1 in Hub&Spoke networking model
VPN1 7 CE 6 Spoke-PE Hub-PE Spoke-PE Hub-CE
Site1

5 VPN1 4
Site3

Spoke-CE VPN1 CE 2 1 3

Site2

As shown in Figure 21-17, communications between Spoke sites are controlled by the Hub site. The lines with arrowheads show the process of advertising a route from Site2 to Site1.
l l l

The Hub-PE can receive the VPN-IPv4 routes advertised by all the Spoke-PEs. All the Spoke-PEs can receive the VPN-IPv4 routes advertised by the Hub-PE. The Hub-PEs advertise the routes from the Spoke-PEs to the spoke-CE, and advertise the routes from the Hub-CE to all the Spoke-PEs. The Spoke sites, therefore, can access each other through the Hub site. The import target of any Spoke-PE is not the same as the export targets of other SpokePEs. Therefore, any two Spoke-PEs do not directly advertise VPN-IPv4 routes to each other. The Spoke sites cannot directly access each other.

The transmission path between Site1 and Site2 is shown in Figure 21-18. The lines with arrowheads show the path of transmitting customer traffic from Site2 to Site1.

21-24

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

Figure 21-18 Path of transmitting customer traffic from Site1 to Site2

VPN1 Spoke-PE 3 2 Spoke-PE 4 Hub-PE Hub-CE VPN1
Site3

1 CE

Site1

Spoke-CE VPN1 CE 6 7 5

Site2

21.4 L3VPN Service Configuration Flow

This section describes the operation tasks for configuring the L3VPN service and relations among these tasks. When configuring and managing the L3VPN services, follow the configuration flow. Figure 21-19 shows the configuration flow of an L3VPN service. For details of each step, see the related section.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21-25

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 21-19 Configuration flow of an L3VPN service

Required Optional Create the network Start

Configure the NNI interface

Configure LSR ID

Configure the control plane

Configure the tunnel

Configure the UNI lnterface

Configure the L3VPN service End

Table 21-1 Configuration of an L3VPN service Operation 1.Creating a network 2. Configuring a network-side interface 3. Configuring a user-side interface 4. Configuring the LSR ID of an NE Remarks Creates NEs, configures NE data, creates fibers, and configures clocks. Sets the basic attributes and layer 3 attributes (including the status of a tunnel and IP address) of an interface for carrying a tunnel. Sets the basic attributes and layer 3 attributes of an interface for accessing services. Configures the LSR ID of an NE and the start value of the global label space.

21-26

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

Operation 5. Configuring the control plane

Remarks Configures the protocol parameters related to the control plane to implement the creation of a tunnel.
l

If you create the static MPLS tunnel for carrying L3VPN services, you need not configure the control plane. If you create the dynamic MPLS tunnel for carrying L3VPN services, you need to configure the following: 1. Configure the parameters of the IGP-ISIS protocol.

Configure the protocol parameters related to the control plane to implement the protocol of advertised routes on the PE-CE side. 6. Creating a tunnel The tunnel is created to carry services.
l

If a static MPLS tunnel is used, you can configure the tunnel on the per-NE and per-trail basis. You can set the relevant information such as the tunnel ID, service name, ingress node, egress node, and transit node, and set the signal type to static. If dynamic MPLS tunnel is used, you need to set the relevant information such as the service name, tunnel source and tunnel sink, and set the signal type to dynamic.

7. Configuring the UNI Interface

The OptiX PTN 910 supports the following UNI interfaces: Ethernet interface, ML-PPP, xDSL interface, microwave interface, LAG, and VLAN sub-interface. The OptiX PTN 950 supports the following UNI interfaces: Ethernet interface, ML-PPP, xDSL interface, microwave interface, LAG, and VLAN sub-interface. The OptiX PTN 1900 supports the following UNI interfaces: Ethernet interface, ML-PPP, SDH interface, LAG, and VLAN sub-interface. The OptiX PTN 3900 supports the following UNI interfaces: Ethernet interface, SDH interface, LAG, and VLAN sub-interface.

8. Creating an L3VPN service

Creates an L3VPN service by using the end-to-end function. 1. Configure the basic attributes of the L3VPN service. 2. Configure information about the route target and tunnels. 3. Configure the service access port. 4. Configure the protocols of advertised routes between PEs and CEs.

21.5 Configuring an L3VPN Service

You can quickly configure the L3VPN services by using the trail function on the T2000. 21.5.1 Creating an L3VPN Service On the T2000, the creation of the L3VPN service includes configuring VPN instances, selecting tunnels, configuring service access ports, and configuring the routing protocols between the PE and CE. 21.5.2 Deleting an L3VPN Service
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-27

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

If there is any unwanted L3VPN service, delete the L3VPN service to release resources. You can quickly delete an L3VPN service in the L3VPN Service Management window.

21.5.1 Creating an L3VPN Service

On the T2000, the creation of the L3VPN service includes configuring VPN instances, selecting tunnels, configuring service access ports, and configuring the routing protocols between the PE and CE.

Prerequisite
l l l l l

You must be an NM user with "NE operator" authority or higher. The IBGP protocol must be configured for the public network. The UNI interfaces must be configured for accessing services. If a dynamic tunnel is used to carry the L3VPN service, the IS-IS protocol must be enabled. Before configuring the L3VPN service, make sure that the port DCN is disabled.

Procedure
Step 1 On the Main Topology, choose Trail > PTN Service > L3VPN Service Creation from the Main Menu. The L3VPN Service Creation window is displayed. Step 2 Configure the basic attributes of the L3VPN service.

Take the following precautions when setting these parameters.

21-28 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

The Label Distribution Policy can be set to Per-VPN or Per-Route. Per-VPN: Distributes MPLS labels on a per-VPN basis. A VPN instance is assigned with a label. That is, all routes in a VPN instance share a label. With this distribution policy, the labels required are relatively less.Per-Route: Distributes MPLS labels on a per-route basis. Each route in the VPN routing table is assigned with a label. The disadvantage of this policy is that routers with high capacity are required, because when there are a considerable number of routes, the entries to be maintained in the ingress label mapping tables of a router increase. Step 3 Click Add to add the PE equipment for the L3VPN service and configure the router distinguisher value. Take the following precautions when setting these parameters.
l

Router Distinguisher Format can be set to AS:Number or IP:Number.AS:Number: The Administrator subfield occupies two bytes. The Assigned Number subfield occupies four bytes. Specifically, the value of subfield Administrator is a 16-bit AS number; the value of subfield Assigned Number is a 32-bit user-defined number.IP:Number: The Administrator subfield occupies four bytes. The Assigned Number subfield occupies two bytes. Specifically, the value of subfield Administrator is a 32-bit IPv4 address; the value of subfield Assigned Number is a 16-bit user-defined number. Router Distinguisher Value: Only values of the Administrator and Assigned Number subfields need to be set. If the Router Distinguisher Format is set to Router Distinguisher Format, the display format is 16-bit AS number:32-bit user-defined number (for example: 100:1). If the Router Distinguisher Format is set to IP:Number, the display format is 32bit IPv4 address:16-bit user-defined number (for example: 172.1.1.1:1). VPN Max. Routes Count: the maximum number of routes allowed in a VPN instance.
NOTE

In the case of the OptiX PTN 950, the value of VPN Max. Routes Count ranges from 16 to 512. In the case of the OptiX PTN 910, the value of VPN Max. Routes Count ranges from 16 to 512. In the case of the OptiX PTN 3900, the value of VPN Max. Routes Count ranges from 128 to 32768. In the case of the OptiX PTN 1900, the value of VPN Max. Routes Count ranges from 128 to 32768. In a backbone network, if the OptiX PTN 950 and OptiX PTN 910 function as PE equipment, the number of VPNs of all the PE equipment cannot exceed the smaller VPN Max. Routes Count of the OptiX PTN 950 and OptiX PTN 910.

Step 4 Click Next to configure information about the route target and tunnels.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21-29

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

1.

In the Configure RT window, click Add to configure the import and export RT values of each PE equipment. Take the following precautions when setting these parameters.
l

Router Target Format can be set to AS:Number or IP:Number.AS:Number: The Administrator subfield occupies two bytes. The Assigned Number subfield occupies four bytes. Specifically, the value of subfield Administrator is a 16-bit AS number; the value of subfield Assigned Number is a 32-bit user-defined number.IP:Number: The Administrator subfield occupies four bytes. The Assigned Number subfield occupies two bytes. Specifically, the value of subfield Administrator is a 32-bit IPv4 address; the value of subfield Assigned Number is a 16-bit user-defined number. Router Target Value: Only values of the Administrator and Assigned Number subfields need to be set. If the Route Target Format is set to AS:Number, the display format is 16-bit AS number:32-bit user-defined number (for example: 200:1). If the Router Target Format is set to IP:Number, the display format is 32-bit IPv4 address: 16-bit user-defined number (for example: 172.1.1.1:1). Export PEs: Selects all PEs that have the same export value. Import PEs: Selects all PEs that have the same import value.

l l

2.

Optional: In the Configure Tunnel Selection window, click Add. In the Add Tunnel Selection Policy dialog box, configure the tunnels between PEs. If a tunnel is configured between the PE equipment, you can skip this step, because the tunnel is selected automatically.

21-30

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

21 Configuring an L3VPN Service

Take the following precautions when setting these parameters.

l l

Source: specifies the PE equipment that transmits L3VPN services as the source of a tunnel. The Select Type can be set to Manually Selected and Automatically Selected. In manually selected mode, you can bind a certain tunnel with certain VPN services. The bound tunnel is used exclusively by the VPN services. In automatically selected mode, the system automatically selects a tunnel that meets the bandwidth requirement. The tunnel that is manually selected must exist and must not be occupied by other services. Sink: specifies the sink of the tunnel that transmits L3VPN services. The sink can be an NE inside management domain or an IP address outside management domain. Tunnel Name(ID): When Select Type is set to Manually Selected, the created tunnel can be selected. Demanded Bandwidth(kbit/s): refers to the bandwidth of the tunnel required by the L3VPN service. This bandwidth can be set only when Select Type is set to Automatically Selected. Use Mode: If Select Type is set to Automatically Selected, Use Mode is Shared. If Select Type is set to Manually Selected, Use Mode is Engross.

l l l l

Step 5 Click Next and click Add to configure the service access port.

Step 6 Click Next to configure the protocols of advertised routes between PEs and CEs. 1. Configure the EBGP protocol. The EBGP protocol is used among different networks consisting of the equipment from different vendors and meanwhile a direct route or static route is required. Click the EBGP tab. In Config Protocol, click Add to add PE equipment. Set EBGP Instance ID, AS No., and Router ID.

2.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21-31

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

3. 1. 2.

In EBGP Peer, click Add to add IP address and the AS number of the remote CE equipment. Configure the RIP protocol. The RIP protocol is used in a small scale network. Click the RIP tab. In Config Protocol, click Add to add PE equipment. Set RIP Instance ID, Update Timer, Aging Timer, and Garbage Collection Timer.

3. 1.

In the Protocol Interface area, click Add to configure the interface. Configure the OSPF protocol. The OSPF protocol, which is dynamically adaptive, flexible, and stable, is used in a large network. Click the OSPF tab. In Config Protocol, click Add to add PE equipment.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

21-32

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

2.

Set OSPF Instance ID.

3. 1.

In the Protocol Interface area, click Add to set Interface and Hello Timer. Configure the static route. The static route is used in a simple network. Specifically, a route is manually configured from the source IP address to the destination IP address. The two IP addresses must be directly connected, or the route may traverse NEs. What's more, the two IP addresses can be in the same network segment or in different network segments. Click the Static tab. In Config Protocol, click Add to add PE equipment. Set Destination IP/Mask, Outbound Interface, Next Hop IP, and Preference.

2.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21-33

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 7 Click Finish. A dialog box is displayed, indicating that the operation is successful. ----End

21.5.2 Deleting an L3VPN Service

If there is any unwanted L3VPN service, delete the L3VPN service to release resources. You can quickly delete an L3VPN service in the L3VPN Service Management window.

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

Procedure
Step 1 On the Main Topology, choose Trail > PTN Service > L3VPN Service Management from the Main Menu. The Set Trail Browse Filter Conditions dialog box is displayed. Step 2 Set filter conditions and click Filter. Step 3 Select an L3VPN service, right-click, and then choose Delete from the shortcut menu. A dialog box is displayed, indicating that the deletion of the service will interrupt services. Step 4 Click OK. Another dialog box is displayed, warning that the deletion of the service is risky. Step 5 Click OK. A dialog box is displayed, indicating that the operation is successful. Then, click Close. ----End

21.6 L3VPN Service Management

In the L3VPN service management, you can search for, filter, query, and modify the L3VPN services, and view the alarms and performance events relevant to the L3VPN services. This management function provides network administrators a method to ensure the normal running of the L3VPN services. 21.6.1 Synchronizing an L3VPN Service By synchronizing the L3VPN services, you can synchronize the corresponding NE data to the T2000, and form end-to-end L3VPN services on the user interface. 21.6.2 Filtering the L3VPN Services You can query L3VPN services according to certain filter conditions. On the T2000, information about L3VPN services that meet the filter conditions is displayed. 21.6.3 Configuring a PE Node In the L3VPN Service Management window, you can add and delete the PE equipment for an L3VPN service, and perform Ping and Traceroute operations. 21.6.4 Configuring a UNI Interface In the L3VPN Service Management window, you can create, delete, and modify a UNI interface. 21.6.5 Configuring the Tunnel Selection Policy In the L3VPN Service Management window, you can create a tunnel between PE equipment and query the information about the tunnel.
21-34 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

21.6.6 Configuring RT Rules In the L3VPN Service Management window, you can create, delete, and modify RT rules. 21.6.7 Configuring the ARP Table In the L3VPN Service Management window, you can query, create, and delete ARP entries. 21.6.8 Querying the FIB Table In the L3VPN Service Management window, you can query the routing information in the FIB table. 21.6.9 Querying the Routing Table In the L3VPN Service Management window, you can query the routing forwarding table of an L3VPN service. 21.6.10 Viewing the Alarms Related to an L3VPN Service You can query the alarms related to an L3VPN service to check whether the L3VPN service has any potential fault. 21.6.11 Viewing the Performance Data Related to an L3VPN Service You can query the performance data related to an L3VPN service to check the running status of the L3VPN service.

21.6.1 Synchronizing an L3VPN Service

By synchronizing the L3VPN services, you can synchronize the corresponding NE data to the T2000, and form end-to-end L3VPN services on the user interface.

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

Procedure
Step 1 On the Main Topology, choose Trail > PTN Service > L3VPN Service Management from the Main Menu. The Set Trail Browse Filter Conditions dialog box is displayed. Step 2 Click Filter. Step 3 Click Synchronize. A dialog box is displayed, indicating that the operation is successful. ----End

21.6.2 Filtering the L3VPN Services

You can query L3VPN services according to certain filter conditions. On the T2000, information about L3VPN services that meet the filter conditions is displayed.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The L3VPN services must be created.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21-35

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 On the Main Topology, choose Trail > PTN Service > L3VPN Service Management from the Main Menu. The Set Trail Browse Filter Conditions dialog box is displayed. Step 2 Set filter conditions and click Filter. The L3VPN services are filtered according to the filter conditions. ----End

21.6.3 Configuring a PE Node

In the L3VPN Service Management window, you can add and delete the PE equipment for an L3VPN service, and perform Ping and Traceroute operations.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The L3VPN service must be created.

Procedure
Step 1 On the Main Topology, choose Trail > PTN Service > L3VPN Service Management from the Main Menu. The Set Trail Browse Filter Conditions dialog box is displayed. Step 2 Set filter criteria and click Filter. Step 3 Select an L3VPN service. Click the PE tab. You can modify the values of Router Distinguisher Value, Router Distinguisher Format, and VPN Max. Routes Count. Step 4 Optional: If you add the PE equipment for the L3VPN service, click New to add the PE equipment and set the relevant parameters.

Step 5 Optional: If you delete the PE equipment for the L3VPN service, click Delete. ----End
21-36 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

21.6.4 Configuring a UNI Interface

In the L3VPN Service Management window, you can create, delete, and modify a UNI interface.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The L3VPN service must be created.

Procedure
Step 1 On the Main Topology, choose Trail > PTN Service > L3VPN Service Management from the Main Menu. The Set Trail Browse Filter Conditions dialog box is displayed. Step 2 Set filter criteria and click Filter. Step 3 Select an L3VPN service. Click the UNI tab. You can modify the values of Interface, IP Designated Format, and IP/Mask of the PE equipment. Step 4 Optional: If you add a PE interface for the L3VPN service, click New to add the PE interface to the PE equipment and set the relevant parameters.

Step 5 Optional: If you delete a PE interface for the L3VPN service, click Delete. Step 6 Click Apply. The Operation Result dialog box is displayed, indicating that the operation is successful. ----End

21.6.5 Configuring the Tunnel Selection Policy

In the L3VPN Service Management window, you can create a tunnel between PE equipment and query the information about the tunnel.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-37

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The L3VPN service must be created.

Context
To transmit VPN service packets from the local PE to the peer PE, by default, the equipment automatically selects an available MPLS tunnel from the local PE to the peer PE without considering the bandwidth of the tunnel. In this case, the QoS may not be assured. To ensure the QoS, the function of manually selecting a tunnel is provided. By using this function, select the idle tunnel that is not occupied by another service and, after binding, the tunnel is exclusively occupied by the service. In automatic tunnel selection mode, if you set a required tunnel bandwidth, the tunnel whose remaining bandwidth is equal to or greater than the required tunnel bandwidth can also be selected automatically. In manual tunnel selection mode, you need to create a tunnel or select a tunnel that does not transmit services. Before setting the required bandwidth for the tunnel that is automatically selected, you need to ensure that the qualified tunnel exists.

Procedure
Step 1 On the Main Topology, choose Trail > PTN Service > L3VPN Service Management from the Main Menu. The Set Trail Browse Filter Conditions dialog box is displayed. Step 2 Set filter criteria and click Filter. Step 3 Select an L3VPN service. Click the Tunnel tab. Step 4 In the left-hand pane, click New to automatically or manually select the existing tunnels between PE equipment.

21-38

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

Step 5 In the right-hand pane, click Query. The Operation Result dialog box is displayed, indicating that the operation is successful. ----End

21.6.6 Configuring RT Rules

In the L3VPN Service Management window, you can create, delete, and modify RT rules.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The L3VPN service must be created.

Context
RT is used to determine whether the local PE accepts the VPN route that another PE transmits. There are export RT and import RT. After a PE changes the VPN route, the PE transmits the new VPN route to its IBGP peers. The MP-BGP packets carry the routing information and the export RT list of the VPN. After an IBGP peer receives the routing information, the peer checks all import RTs on the local PE. If a certain import RT exits in the export RT list, the peer receives the new VPN route and saves it to the VPN routing table of the import RT. Otherwise, the VPN route is discarded. The connectivity between PEs of a VPN depends on the RT configuration. Moreover, a maximum of 16 RTs are supported on each PE of a service.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-39

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 On the Main Topology, choose Trail > PTN Service > L3VPN Service Management from the Main Menu. The Set Trail Browse Filter Conditions dialog box is displayed. Step 2 Set filter criteria and click Filter. Step 3 Select an L3VPN service. Click the Route Target tab. You can modify the values of Route Target Value, Route Target Format, Export PEs, and Import PEs. Step 4 Optional: If you add an RT rule for the L3VPN service, click New to add the RT rule and set the relevant parameters.

Step 5 Optional: If you delete an RT rule for the L3VPN service, click Delete. Step 6 Optional: If you modify an RT rule for the L3VPN service, click Modify. ----End

21.6.7 Configuring the ARP Table

In the L3VPN Service Management window, you can query, create, and delete ARP entries.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The L3VPN service must be created.

Context
In a LAN, each equipment has a 32-bit IP address. The IP address is used in all communication of the equipment. An IP address is allocated independently of the hardware address of a computer. In an Ethernet, the equipment transmits and receives Ethernet data frames based on the 48-bit MAC address. The MAC address is referred to as a physical address or hardware address, and is allocated to an Ethernet interface when the equipment is manufactured. Hence, in an actual network, an address resolution mechanism is required to provide mapping between the two different address formats. The ARP is used to map an IP address to the correct MAC address so that packets can be forwarded. The ARP is classified into dynamic ARP and static ARP. The equipment can create the dynamic ARP and adjust certain parameters for the dynamic ARP. You can configure the static ARP in the following cases:
21-40 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

l

21 Configuring an L3VPN Service

You can enable packets whose destination IP address is not on the local network segment and that pass through a certain gateway on the network segment to be forwarded through the gateway. When you need to filter certain packets whose destination IP addresses are illegal, you can bind the IP addresses to a certain nonexistent MAC address.

In the L3VPN Service Management window, you can query and configure the ARP entries related to a VRF. The ARP entries include dynamically-learned ARP entries and statically-bound ARP entries.

Procedure
Step 1 On the Main Topology, choose Trail > PTN Service > L3VPN Service Management from the Main Menu. The Set Trail Browse Filter Conditions dialog box is displayed. Step 2 Set filter criteria and click Filter. Step 3 Select an L3VPN service. Click the ARP tab. Click Query to query ARP entries.
NOTE

You can query ARP entries for only one service.

Step 4 Optional: If you add the PE equipment for the L3VPN service, click New. In the Add ARP dialog box, click New to add an ARP and set related parameters.

NOTE

You can set multiple static ARP entries at the same time for only one service.

Step 5 Optional: If you delete the PE equipment for the L3VPN service, click Delete. ----End

21.6.8 Querying the FIB Table

In the L3VPN Service Management window, you can query the routing information in the FIB table.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-41

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The L3VPN service must be created.

Context
When a user queries the forwarding table for each PE of an L3VPN, the equipment selects the best route from the routing table and record it in the forwarding table according to certain selection principles. That is to say, there may be multiple routes to the same destination, but the equipment selects only one route for forwarding. The forwarding table refers to the route table that is actually used for forwarding. The total number of forwarding tables depends on the scale of the VPN, but must be smaller than the number of route tables.

Procedure
Step 1 On the Main Topology, choose Trail > PTN Service > L3VPN Service Management from the Main Menu. The Set Trail Browse Filter Conditions dialog box is displayed. Step 2 Set filter criteria and click Filter. Step 3 Select an L3VPN service. Click the FIB tab. Step 4 Click Query. The Filter Criteria dialog box is displayed.

Step 5 Set parameters as required. Step 6 Click Query. The Operation Result dialog box is displayed, indicating that the operation is successful. ----End

21.6.9 Querying the Routing Table

In the L3VPN Service Management window, you can query the routing forwarding table of an L3VPN service.
21-42 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The L3VPN service must be created.

Context
You can query the routing table for each PE of the L3VPN service. The routing table includes the static routes that you configure and the routes that the routing protocol learns. The number of the routing tables depends on the scale of the VPN. Generally, there is a large number of routing tables. Therefore, filter criteria are provided for query, including the PE, destination IP address, destination mask, and routing protocol type (or static route). By querying routing tables, you can prevent, discover, or locate faults during the running of services.

Procedure
Step 1 On the Main Topology, choose Trail > PTN Service > L3VPN Service Management from the Main Menu. The Set Trail Browse Filter Conditions dialog box is displayed. Step 2 Set filter criteria and click Filter. Step 3 Select an L3VPN service. Click the Route Table tab. Step 4 Click Query. The Filter Criteria dialog box is displayed.

Step 5 Set parameters as required. Step 6 Click Query. The Operation Result dialog box is displayed, indicating that the operation is successful. ----End

21.6.10 Viewing the Alarms Related to an L3VPN Service

You can query the alarms related to an L3VPN service to check whether the L3VPN service has any potential fault.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-43

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The L3VPN service must be created.

Procedure
Step 1 On the Main Topology, choose Trail > PTN Service > L3VPN Service Management from the Main Menu. The Set Trail Browse Filter Conditions dialog box is displayed. Step 2 Set filter criteria and click Filter. Step 3 Select an L3VPN service. Click Alarm. Select Current Alarm or History Alarm to query the alarms related to the L3VPN service. ----End

21.6.11 Viewing the Performance Data Related to an L3VPN Service

You can query the performance data related to an L3VPN service to check the running status of the L3VPN service.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The L3VPN service must be created.

Procedure
Step 1 On the Main Topology, choose Trail > PTN Service > L3VPN Service Management from the Main Menu. The Set Trail Browse Filter Conditions dialog box is displayed. Step 2 Set filter criteria and click Filter. Step 3 Select an L3VPN service. Click Performance to query the performance data related to the L3VPN service. ----End

21.7 Configuration Example of an Intranet VPN Service

This topic describes a configuration example of the intranet VPN service. A configuration flow diagram is provided to describe the process of service configuration. The configuration example describes the configuration networking diagram, service planning, and configuration process. 21.7.1 Configuration Networking Diagram This topic describes the networking diagram of the sites on VPN1 and VPN2. 21.7.2 Service Planning Site1, Site2, and Site3 form VPN1, and Site4, Site5, and Site6 form VPN2. 21.7.3 Configuration Process This topic describes how to configure the intranet VPN services described in the configuration example.
21-44 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

21.7.1 Configuration Networking Diagram

This topic describes the networking diagram of the sites on VPN1 and VPN2.

Requirements and Networking Diagram

Figure 21-20 shows the networking diagram of the intranet VPN services. A service provider provides different BGP/MPLS VPN services for two enterprise users. Three sets of PE equipment exist in this network. Each set of the PE equipment is connected to two sites of different users. The OptiX PTN 3900 is used for PE1, PE2, and PE3. The following shows the connectivity between any two sites.
l l l

The equipment on Site1, Site2, and Site3 can communicate with each other on VPN1. The equipment on Site4, Site5, and Site6 can communicate with each other on VPN2. The equipment on Site1, Site2, or Site3 cannot communicate with the equipment on Site4, Site5, or Site6.

Figure 21-20 Networking of the intranet VPN service

AS: 65420 VPN1
Site2

VPN2
Site5

CE AS: 65410 VPN1 CE

Site1 192.168.0.4 192.168.1.4 192.168.1.3
RD 100:1 RT Export 100:1 RT Import 100:1 RD 100:1 RT Export 100:1 RT Import 100:1

CE
192.168.3.4
RD 100:2 RT Export 100:2 RT Import 100:2

AS: 65430 VPN1 CE

Site3 192.168.2.4

PE2 Backbone

RD 100:1 RT Export 100:1 RT Import 100:1

CE
Site4

PE1
RD 100:2 RT Export 100:2 RT Import 100:2

AS: 100

PE3
RD 100:2 RT Export 100:2 RT Import 100:2

192.168.0.2

CE
Site6

VPN2

VPN2

OptiX PTN Router

Figure 21-21 shows the NE planning diagram.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21-45

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 21-21 NE planning diagram

1-EG16-1 ( PORT - 1 )
192.168.1.2

1-EG16-2 ( PORT - 2 )
192.168.3.3

3-EG16-1 ( PORT - 1 )
192.168.2.1

3-EG16-2 ( PORT - 2 )
192.168.4.2

VPN1
Site2

VPN2
Site5

CE

CE

VPN1 CE
Site1

VPN1 PE2 CE
Site3

CE
Site4

PE1

Backbone

PE3 CE
Site6

VPN2
192.168.0.1 1-EG16-1 ( PORT - 1 ) 192.168.1.1 1-EG16-2 ( PORT - 2 )
192.168.2.1 192.168.4.1

192.168.2.3

VPN2

3-EG16-1 ( PORT-1 ) 3-EG16-1 ( PORT-1 ) 192.168.3.1

192.168.3.2

1-EG16-1 ( PORT - 1 )
192.168.0.3

3-EG16-2 ( PORT-2 ) 3-EG16-2 ( PORT-2 )

1-EG16-2 ( PORT - 2 )

21.7.2 Service Planning

Site1, Site2, and Site3 form VPN1, and Site4, Site5, and Site6 form VPN2.

Service Planning
In the case of an intranet, all CE sites in the same VPN can communicate with each other. Site1, Site2, and Site3 belong to VPN1, and Site4, Site5, and Site6 belong to VPN2. Therefore, you need to create two L3VPN services. Table 21-2 shows the planning of the parameters for VPN1. Table 21-3 shows the planning of the parameters for VPN2. Table 21-2 VPN1 parameter planning Parameter General Attributes Service ID Name Label Distribution Policy
21-46 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Description Automatically Assigned L3VPN-0001 Per-VPN

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

Parameter Select PE PE

Description PE1 PE2 PE3 Router Distinguisher Value Router Distinguisher Format VPN Max. Routes Count 100:1 AS:Number 32000 100:1 AS:Number PE1, PE2, PE3 PE1, PE2, PE3 PE1, PE1, PE2 PE2, PE3, PE3 Manually Selected Tunnel-0001, Tunnel-0003, Tunnel-0005 Shared PE1, PE2, PE3 PE1, PE2, PE3: 1-EG16-1 (Port-1) Manually Specified 192.168.0.1/24, 192.168.1.2/24, 192.168.2.3/24 PE1, PE2, PE3 Automatically Assigned 100 1.1.1.1, 1.1.1.2, 1.1.1.3 192.168.0.4, 192.168.1.3, 192.168.2.4 65410, 65420, 65430

Configure RT

Route Target Value Route Target Format Export PEs Import PEs

Configure Tunnel Selection

Source Sink Select Type Tunnel Name(ID) Demanded Bandwidth(kbit/ s) Use Mode

Configure Service Access Port

PE Interface IP Designated Format IP/Mask

Configure Protocol

PE EBGP Instance ID AS No. Router ID

EBGP Peer

Remote IP Remote AS No.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21-47

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Table 21-3 VPN2 parameter planning Parameter General Attributes Service ID Name Label Distribution Policy Select PE PE Description Automatically Assigned L3VPN-0002 Per-VPN PE1 PE2 PE3 Router Distinguisher Value Router Distinguisher Format VPN Max. Routes Count Configure RT Route Target Value Route Target Format Export PEs Import PEs Configure Tunnel Selection Source Sink Select Type Tunnel Name(ID) Demanded Bandwidth(kbit/ s) Use Mode Configure Service Access Port PE Interface IP Designated Format IP/Mask 200:1 AS:Number 32000 200:1 AS:Number PE1, PE2, PE3 PE1, PE2, PE3 PE1, PE1, PE2 PE2, PE3, PE3 Manually Selected Tunnel-0001, Tunnel-0003, Tunnel-0005 Shared PE1, PE2, PE3 PE1, PE2, PE3: 1-EG16-2 (Port-2) Manually Specified 192.168.1.1/24, 192.168.3.3/24, 192.168.0.3/24 PE1, PE2, PE3 Automatically Assigned 100

Configure Protocol

PE EBGP Instance ID AS No.

21-48

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

Parameter Router ID EBGP Peer Remote IP Remote AS No.

Description 1.1.1.1, 1.1.1.2, 1.1.1.3 192.168.1.4, 192.168.3.4, 192.168.0.2 65410, 65420, 65430

21.7.3 Configuration Process

This topic describes how to configure the intranet VPN services described in the configuration example.

Prerequisite
You must learn about the networking requirements and service planning described in the example. The network must be created. Before configuring the L3VPN service, make sure that the port DCN is disabled.

Procedure
Step 1 Configure network-side ports for PE1, PE2, and PE3. 1. 2. In the NE Explorer, select PE1 and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Configure the network-side port. On the General Attributes tab page, select the 3-EG16-1(Port-1) and 3-EG16-2(Port-2), and set Port Mode to Layer 3. Set parameters as required. Click Apply.

Set the related parameters as follows:

l l l

Enable Port: Enabled Port Mode: Layer 3(The port carries a tunnel.) Working Mode: Auto-Negotiation (Set the working modes of the local port and opposite port as the same.) Max Frame Length(byte): 1620 (Set this parameter according to the length of data packets. All the received data packets that contain more bytes than the maximum frame length are discarded.)

3.

On the Layer 3 Attributes tab page, select the 3-EG16-1(Port-1) and 3-EG16-2(Port-2), set Enabled Tunnel to Enabled and Specify IP to Manually, and set IP Address and IP Mask. Click Apply. Set the related parameters as follows:
l

Enabled Tunnel: Enabled

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-49

Issue 01 (2009-06-30)

21 Configuring an L3VPN Service

l

OptiX iManager T2000 Operation Guide for PTN NE Management

Max Reserved Bandwidth(kbit/s): 102400 (The maximum reserved bandwidth should not exceed the physical bandwidth of the bearer port.) TE Measurement: 10 (You can intervene in the route selection by adjusting the TE measurement of the link. The smaller the value of the TE measurement, the higher the priority of the link.) Specify IP: Manually (Manually indicates that you can set the IP address of the port.) IP Address: 3-EG16-1(Port-1) set to 192.168.2.1, 3-EG16-2(Port-2) set to 192.168.3.1 IP Mask: 255.255.255.0

l l l

4.

In the NE Explorer, select PE2. To configure the attributes of the 3-EG16-1(Port-1) and 3EG16-2(Port-2) , refer to Step 1.1 through Step 1.3. Set the related parameters as follows: The parameter settings of the PE2-3-EG16-1(Port-1) are consistent with the parameter settings of the PE1-3-EG16-1(Port-1) and the IP address is set to 192.168.2.2. The parameter settings of the PE2-3-EG16-2(Port-2) are consistent with the parameter settings of the PE1-3-EG16-1(Port-1) and the IP address is set to 192.168.4.2.

5.

In the NE Explorer, select PE3. To configure the attributes of the 3-EG16-1(Port-1) and 3EG16-2(Port-2), refer to Step 1.1 through Step 1.3. Set the related parameters as follows: The parameter settings of the PE3-3-EG16-1(Port-1) are consistent with the parameter settings of the PE1-3-EG16-1(Port-1) and the IP address is set to 192.168.4.1. The parameter settings of the PE3-3-EG16-2(PORT-2) are consistent with the parameter settings of the PE1-3-EG16-1(Port-1) and the IP address is set to 192.168.3.2.

Step 2 Configure client-side ports for PE1, PE2, and PE3. 1. In the NE Explorer, select PE1. To configure the port attributes of 1-EG16-1(Port-1) and 1-EG16-2(Port-2), refer to Step 1.1 through Step 1.3. Set the related parameters as follows: Set the general attributes of PE1-1-EG16-1(Port-1) to the same as the general attributes of PE1-3-EG16-1(Port-1). Set Specify IP to Unspecified for Layer 3 attributes of PE1-1EG16-1(Port-1). Set the general attributes of PE1-1-EG16-2(Port-2) to the same as the general attributes of PE1-3-EG16-1(Port-1). Set Specify IP to Unspecified for Layer 3 attributes of PE1-1EG16-1(Port-2). 2. In the NE Explorer, select PE2. To configure the port attributes of 1-EG16-1(Port-1) and 1-EG16-2(Port-2), refer to Step 1.1 through Step 1.3. Set the related parameters as follows: Set the general attributes of PE2-1-EG16-1(Port-1) to the same as the general attributes of PE1-3-EG16-1(Port-1). Set Specify IP to Unspecified for Layer 3 attributes of PE1-1EG16-1(Port-1). Set the general attributes of PE2-1-EG16-2(Port-2) to the same as the general attributes of PE1-3-EG16-1(Port-1). Set Specify IP to Unspecified for Layer 3 attributes of PE1-1EG16-1(Port-2). 3. In the NE Explorer, select PE3. To configure the port attributes of 1-EG16-1(Port-1) and 1-EG16-2(Port-2), refer to Step 1.1 through Step 1.3.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

21-50

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

Set the related parameters as follows: Set the general attributes of PE3-1-EG16-1(Port-1) to the same as the general attributes of PE1-3-EG16-1(Port-1). Set Specify IP to Unspecified for Layer 3 attributes of PE1-1EG16-1(Port-1). Set the general attributes of PE3-1-EG16-2(Port-2) to the same as the general attributes of PE1-3-EG16 Set Specify IP to Unspecified for Layer 3 attributes of PE3-1-EG16-1 (Port-2). Step 3 Specify LSR IDs for NEs. 1. 2. In the NE Explorer, select PE1 and choose Configuration > MPLS Management > Basic Configuration from the Function Tree. Set the parameters, such as LSR ID and Start of Global Label Space, for the NE. Click Apply. Set the related parameters as follows:
l l

LSR ID: 1.1.1.1 (The LSR ID must be unique in the network.) Start of Global Label Space: 0 (The minimum value of the ingress and egress labels of a unicast tunnel.)

3.

In the NE Explorer, select PE2. To set the parameters, such as LSR ID, for PE2, refer to Step a and Step b. Set the related parameters as follows:
l l

LSR ID: 1.1.1.2 (The LSR ID must be unique in the network.) Start of Global Label Space: 0 (The minimum value of the ingress and egress labels of a unicast tunnel.)

4.

In the NE Explorer, select PE3. To set the parameters, such as LSR ID, for PE3, refer to the Step a and Step b. Set the related parameters as follows:
l l

LSR ID: 1.1.1.3 (The LSR ID must be unique in the network.) Start of Global Label Space: 0 (The minimum value of the ingress and egress labels of a unicast tunnel.)

Step 4 Configure control planes for NEs. 1. 2. In the NE Explorer, select PE1 and choose Configuration > Control Plane Configuration > IGP-ISIS Configuration from the Function Tree. Choose the Port Configuration tab and then click New. Click Add in the dialog box displayed. Then Select 3-EG16-1(Port-1) and 3-EG16-2(Port-2) in the port tab. Click OK. The configuration parameters are as follows:
l

IS-IS Enable: Enabled (If the IS-IS routing protocol is enabled, the MPLS LSP can be dynamically created.) Link Level: level-1-2 LSP Retransmission Interval(s): 5 (In the case of a point-to-point link, if the local router fails to receive any response in a period after transmitting the LSP, the local router considers that the LSP is lost or discarded. To ensure the transmission reliability, the local router transmits the LSP again.) Minimum LSP Transmission Interval (ms): 30
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-51

l l

Issue 01 (2009-06-30)

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

3. 4. 5.

Choose Configuration > Control Plane Configuration > MP-BGP Configuration from the Function Tree. Click the MP-BGP Configuration tab. Click New. In the Create MP-BGP Protocol Instance dialog box, set MP-BGP Instance ID to 1 and AS Number to 100. Click Apply. Select the Peer Configuration tab. Click New. In the Create Peer dialog box, set parameters. For example, set MP-BGP Instance ID to 1 and AS Number to 100. Set the following parameters to configure PE2 as an MP-BGP peer.
l l l

MP-BGP Instance: 1 Remote IP Address: 192.168.2.2 AS Number: 100

Set the following parameters to configure PE3 as an MP-BGP peer.

l l l

MP-BGP Instance: 1 Remote IP Address: 192.168.3.2 AS Number: 100

6.

In the NE Explorer, select PE2. To set the parameters of the control plane for PE2, refer to Step a through Step e. The IS-IS protocol settings of 3-EG16-1(PORT-1) port and 3-EG16-2(PORT-2) port for PE2 are consistent with the IS-IS protocol settings of PE1. The MP-BGP protocol settings of PE2 are consistent with the IBGP protocol settings of PE1. Set following parameters to configure PE1 as an MP-BGP peer.
l l l

MP-BGP Instance: 1 Remote IP Address: 192.168.2.1 AS Number: 100

Set following parameters to configure PE3 as an MP-BGP peer.

l l l

MP-BGP Instance: 1 Remote IP Address: 192.168.4.1 AS Number: 100

7.

In the NE Explorer, select PE3. To set the parameters of the control plane for PE3, refer to Step a through Step e. The IS-IS protocol settings of 3-EG16-1(PORT-1) port and 3-EG16-2(PORT-2) port for PE3 are consistent with the IS-IS protocol settings of PE1. The MP-BGP protocol settings of PE3 are consistent with the IBGP protocol settings of PE1. Set following parameters to configure PE1 as an MP-BGP peer.
l l l

MP-BGP Instance: 1 Remote IP Address: 192.168.3.1 AS Number: 100

Set following parameters to configure PE2 as an MP-BGP peer.

21-52 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

l l l

21 Configuring an L3VPN Service

MP-BGP Instance: 1 Remote IP Address: 192.168.4.2 AS Number: 100

Step 5 Create dynamic tunnels. 1. 2. On the Main Topology, choose Trail > Tunnel > Tunnel Creation from the Main Menu. The Create Tunnel dialog box is displayed. Configure the dynamic tunnel between PE1 and PE2. Select the Create Reverse Tunnel check box. In the General Attributes area, configure the positive and reverse tunnels.

Set the related parameters as follows:

l l l l l

Tunnel ID: 1 (for the positive tunnel), 2 (for the reverse tunnel) Name: Tunnel-0001 (for the positive tunnel), Tunnel-0002 (for the reverse tunnel) Signal Type: Dynamic Scheduling Type: E-LSP Bandwidth(kbit/s): 4096 (Set this value based on the networking planning.)

3.

Click Next, select source and sink nodes, and then click Add to set route constraints.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21-53

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Set the related parameters as follows:

l l l

Source Node: PE1 Sink Node: PE2 Route Constraint Port IP Address: 192.168.2.2 (for the positive tunnel), 192.168.2.1 (for the reverse tunnel) Rerouting Mode: Include Strict

4. 5.

Click Next. Use the default values of parameters, such as Setup Priority and Hold Priority, for the tunnels. Click Finish. To configure the dynamic tunnel between PE1 and PE3, refer to Step a through Step d. Set the related parameters as follows:
l l l l l l l

Tunnel ID: 3 (for the positive tunnel), 4 (for the reverse tunnel) Name: Tunnel-0003 (for the positive tunnel), Tunnel-0004 (for the reverse tunnel) Signal Type: Dynamic Scheduling Type: E-LSP Bandwidth(kbit/s): 4096 (Set this value based on the networking planning.) Source Node: PE1 Sink Node: PE3
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

21-54

OptiX iManager T2000 Operation Guide for PTN NE Management

l

21 Configuring an L3VPN Service

Route Constraint Port IP Address: 192.168.3.2 (for the positive tunnel), 192.168.3.1 (for the reverse tunnel) Rerouting Mode: Include Strict Other parameters use default values.

l l

6.

To configure the dynamic tunnel between PE2 and PE3, refer to Step a through Step d. Set the related parameters as follows:
l l l l l l l l

Tunnel ID: 5 (for the positive tunnel), 6 (for the reverse tunnel) Name: Tunnel-0005 (for the positive tunnel), Tunnel-0006 (for the reverse tunnel) Signal Type: Dynamic Scheduling Type: E-LSP Bandwidth(kbit/s): 4096 (Set this value based on the networking planning.) Source Node: PE2 Sink Node: PE3 Route Constraint Port IP Address: 192.168.4.1 (for the positive tunnel), 192.168.4.2 (for the reverse tunnel) Rerouting Mode: Include Strict Other parameters use default values.

l l

Step 6 Create the L3VPN services: VPN1 and VPN2. 1. 2. On the Main Topology of the T2000, choose Trail > PTN Service > L3VPN Service Creation from the Main Menu. The L3VPN Service Creation dialog box is displayed. Click Add. Add PE1, PE2, and PE3 in the Select PE area.

Set the related parameters as follows:

l

Service ID: Automatically Assigned

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-55

Issue 01 (2009-06-30)

21 Configuring an L3VPN Service

l l l l l l

OptiX iManager T2000 Operation Guide for PTN NE Management

Name: L3VPN-0001 Label Distribution Policy: Per-VPN PE: PE1, PE2 and PE3 Router Distinguisher Value: 100:1 Router Distinguisher Format: AS:Number VPN Max. Routes Count: 320 00

3.

Click Next. In the Config RT area, click Add. Set the parameters related to the RT.

Set the parameters related to RT as follows:

l l l l

Router Target Value: 200:1 Router Target Format: AS:Number Export PEs: PE1,PE2,PE3 Import PEs: PE1,PE2,PE3

4.

In the Config Tunnel Selection area, click Add to add three tunnels and set the parameters related to the tunnels. Set parameters related to the tunnel between PE1 and PE2 as follows:
l l l l l

Source: PE1 Sink: PE2 Select Type: Manually Selected Tunnel Name(ID): Tunnel-0001 Demanded Bandwidth(kbit/s): Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

21-56

OptiX iManager T2000 Operation Guide for PTN NE Management

l

21 Configuring an L3VPN Service

Use Mode: Shared

Set parameters related to the tunnel between PE1 and PE3 as follows:
l l l l l l

Source: PE1 Sink: PE3 Select Type: Manually Selected Tunnel Name(ID): Tunnel-0003 Demanded Bandwidth(kbit/s): Use Mode: Shared

Set parameters related to the tunnel between PE2 and PE3 as follows:
l l l l l l

Source: PE2 Sink: PE3 Select Type: Manually Selected Tunnel Name(ID): Tunnel-0005 Demanded Bandwidth(kbit/s): Use Mode: Shared

5. 6.

Click Next and configure the service access ports. Click Add to add three service access ports of the PE equipment.

Set the related parameters as follows:

l l l l

PE: PE1, PE2, PE3 Interface: 1-EG16-1(Port-1) IP Designated Format: Manually Specified IP/Mask: 192.168.0.1/24, 192.168.1.2/24, 192.168.2.3/24

7.

Click Next to configure protocols.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21-57

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

8.

In the Config Protocol area, click EBGP tab. Then, click Add to configure protocols for the three PEs. Set the related parameters as follows:
l l l l

PE: PE1, PE2, PE3 EBGP Instance ID: Automatically Assigned AS No.: 100 Router ID: 1.1.1.1, 1.1.1.2, 1.1.1.3

9.

In the EBGP Peer area, click Add to add three pairs of peers. Set the related parameters as follows:
l l

Remote IP: 192.168.0.4, 192.168.1.3, 192.168.2.4 Remote AS No.: 65410, 65420, 65430

10. Click Finish. L3VPN-0001 is successfully created. 11. To create VPN2, refer to Step a to Step j. Set the related parameters. The parameters related to general attributes are as follows:
l l l l l l l

Service ID: Automatically Assigned Name: L3VPN-0001 Label Distribution Policy: Per-VPN PE: PE1, PE2 and PE3 Router Distinguisher Value: 200:1 Router Distinguisher Format: AS:Number VPN Max. Routes Count: 320
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

21-58

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

00 The parameters related to RT are as follows:

l l l l

Router Target Value: 200:1 Router Target Format: AS:Number Export PEs: PE1,PE2,PE3 Import PEs: PE1,PE2,PE3

The parameters related to the tunnel between PE1 and PE2 are as follows:
l l l l l l

Source: PE1 Sink: PE2 Select Type: Manually Selected Tunnel Name(ID): Tunnel-0001 Demanded Bandwidth(kbit/s): Use Mode: Shared

The parameters related to the tunnel between PE1 and PE3 are as follows:
l l l l l l

Source: PE1 Sink: PE3 Select Type: Manually Selected Tunnel Name(ID): Tunnel-0003 Demanded Bandwidth(kbit/s): Use Mode: Shared

The parameters related to the tunnel between PE2 and PE3 are as follows:
l l l l l l

Source: PE2 Sink: PE3 Select Type: Manually Selected Tunnel Name(ID): Tunnel-0005 Demanded Bandwidth(kbit/s): Use Mode: Shared

The parameters related to the service access port are as follows:

l l l l

PE: PE1, PE2, PE3 Interface: 1-EG16-2(PORT-2) IP Designated Format: Manually Specified IP/Mask: 192.168.1.1/24, 192.168.3.3/24, 192.168.0.3/24

The parameters related to the protocol configuration are as follows:

l l l l

PE: PE1, PE2, PE3 EBGP Instance ID: Automatically Assigned AS No.: 100 Router ID: 1.1.1.1, 1.1.1.2, 1.1.1.3
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-59

Issue 01 (2009-06-30)

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

The parameters related to the EBGP peer are as follows:

l l

Remote IP: 192.168.1.4, 192.168.3.4, 192.168.0.2 Remote AS No.: 65410, 65420, 65430

----End

21.8 Configuration Example of an Extranet VPN Service

This topic describes a configuration example of the extranet VPN service. A configuration flow diagram is provided to describe the process of service configuration. The configuration example describes the configuration networking diagram, service planning, and configuration process. 21.8.1 Configuration Networking Diagram This topic describes the networking diagram of the sites on VPN1 and VPN2. 21.8.2 Service Planning This topic describes how to configure VPN1 between Site1 and Site3. In addition, Site 2 can communicate with Site3. 21.8.3 Configuration Process This topic describes how to configure the extranet VPN services described in the configuration example.

21.8.1 Configuration Networking Diagram

This topic describes the networking diagram of the sites on VPN1 and VPN2.

Requirements and Networking Diagram

Figure 21-22 shows the networking diagram of the extranet VPN services. If a VPN user wants to provide another VPN user with certain site resources of the local VPN, the extranet networking scheme can be used. In an extranet, if a certain VPN wants to access shared sites, the Export Target of the VPN must be contained in the Import Target of the VPN instances of the shared sites. Three sets of PE equipment exist in this network. Each set of the PE equipment is connected to one site of different users. The OptiX PTN 3900 is used for PE1, PE2, and PE3. The following shows the connectivity between any two sites.
l l l

The equipment on Site1 and Site3 can communicate with each other on VPN1. The equipment on Site2 and Site3 can communicate with each other on VPN2. The equipment on Site1 cannot communicate with the equipment on Site2.

21-60

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

Figure 21-22 Networking of the extranet VPN service

VPN1 RD 100:1 RT Export 100:1 RT Import 100:1

AS: 65410 VPN1 CE1

Site1 192.168.0.2 192.168.0.6

PE1 PE2

VPN1 RD 100:1 RT Export 100:1,200:1 RT Import 100:1,200:1

AS: 65430 VPN1 CE3

Backbone PE3 AS: 100

Site3

192.168.0.4

CE2
Site2

VPN2 AS: 65420

VPN2 RD 100:1 RT Export 200:1 RT Import 200:1

OptiX PTN Router

Figure 21-23 shows the NE planning diagram. Figure 21-23 NE planning diagram
1-EG16-1 ( PORT 4-EG16-1 ( PORT 1) 1) 192.168.0.1 192.168.1.1 CE1 3-EG16-1 ( PORT 1) Site1 192.168.0.2 192.168.1.2

PE1 PE2

Backbone PE3

Site3 192.168.0.4

CE2

Site2 192.168.0.6 1-EG16-1 ( PORT - 3-EG16-1 ( PORT 1) 1) 192.168.2.1 192.168.0.5

CE3
3-EG16-2 ( PORT - 1-EG16-1 ( PORT 1) 2) 192.168.2.2 192.168.0.3

21.8.2 Service Planning

This topic describes how to configure VPN1 between Site1 and Site3. In addition, Site 2 can communicate with Site3.

Service Planning
In the case of an extranet, the user of a VPN can access certain sites of another VPN. The VPN1 and VPN2 can communicate with Site3 of VPN1. Site1 and Site3 of VPN1 can communicate
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-61

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

with each other. Site2 of VPN2 and Site3 of VPN1 can communicate with each other. Site1 of VPN1 and Site2 of VPN2 , however, cannot communicate with each other. Table 21-4 shows the planning of parameters. Table 21-4 Parameter planning Parameter General Attributes Service ID Name Label Distribution Policy Select PE PE Description Automatically Assigned L3VPN-0001 Per-VPN PE1 PE2 PE3 Router Distinguisher Value Router Distinguisher Format VPN Max. Routes Count Configure RT Route Target Value Route Target Format Export PEs Import PEs Configure Tunnel Selection Source Sink Select Type Tunnel Name(ID) Demanded Bandwidth(kbit/ s) Use Mode Configure Service Access Port PE Interface IP Designated Format IP/Mask 100:1 AS:Number 32000 100:1, 200:1 AS:Number PE1 and PE3, PE2 and PE3 PE1 and PE3, PE2 and PE3 PE1, PE2 PE3, PE3 Manually Selected No Limit Shared PE1, PE2, PE3 PE1, PE2, PE3: 1-EG16-1 (PORT-1) Manually Specified 192.168.0.1/30, 192.168.0.5/30, 192.168.0.3/30 PE1, PE2, PE3
Issue 01 (2009-06-30)

Configure Protocol
21-62

PE

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

Parameter OSPF Instance ID Protocol Interface Interface Hello Timer(s)

Description Manually Specified PE1, PE2, PE3: 1-EG16-1 (PORT-1) 100

21.8.3 Configuration Process

This topic describes how to configure the extranet VPN services described in the configuration example.

Prerequisite
You must learn about the networking requirements and service planning described in the example. The network must be created. Before configuring the L3VPN service, make sure that the port DCN is disabled.

Procedure
Step 1 Configure network-side interfaces for PE1, PE2, and PE3. 1. 2. In the NE Explorer, select PE1 and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Configure the network-side interface. On the General Attributes tab page, select the 3-EG16-1(PORT-1) port and set Port Mode to Layer 3. Set parameters as required. Click Apply.

Set the related parameters as follows:

l l l

Enable Port: Enabled Port Mode: Layer 3(The port carries a tunnel.) Working Mode: Auto-Negotiation (Set the working modes of the local port and opposite port as the same.) Max Frame Length(byte): 1620 (Set this parameter according to the length of data packets. All the received data packets that contain more bytes than the maximum frame length are discarded.)

3.

On the Layer 3 Attributes tab page, select the 3-EG16-1(PORT-1) port, set Enabled Tunnel to Enabled and Specify IP to Manually, and set IP Address and IP Mask. Click Apply. Set the related parameters as follows:
l

Enabled Tunnel: Enabled

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-63

Issue 01 (2009-06-30)

21 Configuring an L3VPN Service

l

OptiX iManager T2000 Operation Guide for PTN NE Management

Max Reserved Bandwidth(kbit/s): 102400 (The maximum reserved bandwidth should not exceed the physical bandwidth of the bearer port.) TE Measurement: 10 (You can intervene in the route selection by adjusting the TE measurement of the link. The smaller the value of the TE measurement, the higher the priority of the link.) Specify IP: Manually (Manually indicates that you can set the IP address of the port.) IP Address: 192.168.1.1 IP Mask: 255.255.255.252

l l l

4.

In the NE Explorer, select PE2. To configure the attributes of the 3-EG16-1(PORT-1) port, refer to Step Step 1.1 through Step Step 1.3. Set the related parameters as follows: The parameter settings of the PE2-3-EG16-1(PORT-1) port are consistent with the parameter settings of the PE1-3-EG16-1(PORT-1) port and the IP address is set to 192.168.2.1.

5.

In the NE Explorer, select PE3. To configure the attributes of the 3-EG16-1(PORT-1) port and 3-EG16-2(PORT-2), refer to Step 1.1 through Step 1.3. Set the related parameters as follows: The parameter settings of the PE3-3-EG16-1(PORT-1) port are consistent with the parameter settings of the PE1-3-EG16-1(PORT-1) port and the IP address is set to 192.168.1.2. The parameter settings of the PE3-3-EG16-2(PORT-2) port are consistent with the parameter settings of the PE1-3-EG16-1(PORT-1) port and the IP address is set to 192.168.2.2.

Step 2 Configure client-side ports for PE1, PE2, and PE3. 1. In the NE Explorer, select PE1. To configure the port attributes of 1-EG16-1(Port-1), refer to Step 1.1 through Step 1.3. Set the related parameters as follows: Set the general attributes of PE1-1-EG16-1(Port-1) to the same as the general attributes of PE1-3-EG16-1(Port-1). Set Specify IP to Unspecified for Layer 3 attributes of PE1-1EG16-1(Port-1). 2. In the NE Explorer, select PE2. To configure the port attributes of 1-EG16-1(Port-1), refer to Step 1.1 through Step 1.3. Set the related parameters as follows: Set the general attributes of PE2-1-EG16-1(Port-1) to the same as the general attributes of PE1-3-EG16-1(Port-1). Set Specify IP to Unspecified for Layer 3 attributes of PE2-1EG16-1(Port-1). 3. In the NE Explorer, select PE3. To configure the port attributes of 1-EG16-1(Port-1), refer to Step 1.1 through Step 1.3. Set the related parameters as follows: Set the general attributes of PE3-1-EG16-1(Port-1) to the same as the general attributes of PE1-3-EG16-1(Port-1). Set Specify IP to Unspecified for Layer 3 attributes of PE3-1EG16-1(Port-1). Step 3 Specify LSR IDs for NEs.
21-64 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

1. 2.

In the NE Explorer, select PE1 and choose Configuration > MPLS Management > Basic Configuration from the Function Tree. Set the parameters, such as LSR ID and Start of Global Label Space, for the NE. Click Apply. Set the related parameters as follows:
l l

LSR ID: 1.1.1.1 (The LSR ID must be unique in the network.) Start of Global Label Space: 0 (The minimum value of the ingress and egress labels of a unicast tunnel.)

3.

In the NE Explorer, select PE2. To set the parameters, such as LSR ID, for PE2, refer to Step a and Step b. Set the related parameters as follows:
l l

LSR ID: 1.1.1.2 (The LSR ID must be unique in the network.) Start of Global Label Space: 0 (The minimum value of the ingress and egress labels of a unicast tunnel.)

4.

In the NE Explorer, select PE3. To set the parameters, such as LSR ID, for PE3, refer to the Step a and Step b. Set the related parameters as follows:
l l

LSR ID: 1.1.1.3 (The LSR ID must be unique in the network.) Start of Global Label Space: 0 (The minimum value of the ingress and egress labels of a unicast tunnel.)

Step 4 Configure control planes for NEs. 1. 2. In the NE Explorer, select PE1 and choose Configuration > Control Plane Configuration > IGP-ISIS Configuration from the Function Tree. Choose the Port Configuration tab and then click New. Click Add in the dialog box displayed. Then Select 3-EG16-1(PORT-1) in the port tab. Click OK. The configuration parameters are as follows:
l l

Link Level: level-1-2 LSP Retransmission Interval(s): 5 (In the case of a point-to-point link, if the local router fails to receive any response in a period after transmitting the LSP, the local router considers that the LSP is lost or discarded. To ensure the transmission reliability, the local router transmits the LSP again.) Minimum LSP Transmission Interval (ms): 30

3. 4. 5.

Choose Configuration > Control Plane Configuration > MP-BGP Configuration from the Function Tree. Click the MP-BGP Configuration tab. Click New. In the Create MP-BGP Protocol Instance dialog box, set MP-BGP Instance ID to 1 and AS Number to 100. Click Apply. Select the Peer Configuration tab. Click New. In the Create Peer dialog box, set parameters. For example, set MP-BGP Instance ID to 1 and AS Number to 100. Set the following parameters to configure PE3 as an MP-BGP peer.
l l l

MP-BGP Instance: 1 Remote IP Address: 192.168.1.2 AS Number: 100

6.

In the NE Explorer, select PE2. To set the parameters of the control plane for PE2, refer to Step a through Step e.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-65

Issue 01 (2009-06-30)

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

The IS-IS protocol settings of 3-EG16-1(PORT-1) for PE2 are consistent with the IS-IS protocol settings of PE1. The MP-BGP protocol settings of PE2 are consistent with the MP-BGP protocol settings of PE1. Set following parameters to configure PE3 as an MP-BGP peer.
l l l

MP-BGP Instance: 1 Remote IP Address: 192.168.2.2 AS Number: 100

7.

In the NE Explorer, select PE3. To set the parameters of the control plane for PE3, refer to Step a through Step e. The IS-IS protocol settings of 3-EG16-1(PORT-1) port and 3-EG16-2(PORT-2) port for PE3 are consistent with the IS-IS protocol settings of PE1. The MP-BGP protocol settings of PE3 are consistent with the MP-BGP protocol settings of PE1. Set following parameters to configure PE1 as an MP-BGP peer.
l l l

MP-BGP Instance: 1 Remote IP Address: 192.168.1.1 AS Number: 100

Set following parameters to configure PE2 as an MP-BGP peer.

l l l

MP-BGP Instance: 1 Remote IP Address: 192.168.2.1 AS Number: 100

Step 5 Create dynamic tunnels. 1. 2. On the Main Topology of the T2000, choose Trail > Tunnel > Tunnel Creation from the Main Menu. The Create Tunnel dialog box is displayed. Configure the dynamic tunnel between PE1 and PE3. Select the Create Reverse Tunnel check box. In the General Attributes area, configure the positive and reverse tunnels.

21-66

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

Set the related parameters as follows:

l l l

Tunnel ID: 1 (Positive), 2 (Reverse) Name: Tunnel-0001 (Positive), Tunnel-0002 (Reverse) Signal Type: Dynamic (Dynamic indicates that the labels are distributed through the LSP signaling; Static indicates that the labels are manually added.) Scheduling Type: E-LSP Bandwidth (kbit/s): 4096 (Set the bandwidth according to networking planning.)

l l

3.

Click Next, select source and sink nodes, and then click Add to set route constraints.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21-67

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Set the related parameters as follows:

l l l

Source Node: PE1 Sink Node: PE3 Route Constraint Port IP Address: 192.168.1.2 (for the positive tunnel), 192.168.0.1 (for the reverse tunnel) Rerouting Mode: Include Strict

4. 5.

Click Next. Use the default values of parameters, such as Setup Priority and Hold Priority, for the tunnels. Click Finish. To configure the dynamic tunnel between PE2 and PE3, refer to Step a through Step d. Set the related parameters as follows:
l l l l l l l l

Tunnel ID: 3 (for the positive tunnel), 4 (for the reverse tunnel) Name: Tunnel-0003 (for the positive tunnel), Tunnel-0004 (for the reverse tunnel) Signal Type: Dynamic Scheduling Type: E-LSP Bandwidth(kbit/s): 4096 (Set this value based on the networking planning.) Source Node: PE2 Sink Node: PE3 Route Constraint Port IP Address: 192.168.2.2 (for the positive tunnel), 192.168.2.1 (for the reverse tunnel)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

21-68

OptiX iManager T2000 Operation Guide for PTN NE Management

l l

21 Configuring an L3VPN Service

Rerouting Mode: Include Strict Other parameters use default values.

Step 6 Create the L3VPN services: VPN1 and VPN2. 1. 2. On the Main Topology of the T2000, choose Trail > PTN Service > L3VPN Service Creation from the Main Menu. The L3VPN Service Creation dialog box is displayed. click Add. Add PE1, PE2, and PE3 in the Select PE area.

Set the related parameters as follows:

l l l l l l l

Service ID: Automatically Assigned Name: L3VPN-0001 Label Distribution Policy: Per-VPN PE: PE1, PE2 and PE3 Router Distinguisher Value: 100:1 Router Distinguisher Format: AS:Number VPN Max. Routes Count: 32000

3.

Click Next. In the Config RT area, click Add. Set the parameters related to the two RTs. Set the parameters related to RT1 as follows:
l l l l

Router Target Value: 100:1 Router Target Format: AS:Number Export PEs: PE1, PE3 Import PEs: PE1, PE3

Set the parameters related to RT2 as follows:

l

Router Target Value: 200:1

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-69

Issue 01 (2009-06-30)

21 Configuring an L3VPN Service

l l l

OptiX iManager T2000 Operation Guide for PTN NE Management

Router Target Format: AS:Number Export PEs: PE2, PE3 Import PEs: PE2, PE3

4.

In the Config Tunnel Selection area, click Add to add two tunnels and set the parameters related to the tunnels. Set parameters related to the tunnel between PE1 and PE3 as follows:
l l l l l l

Source: PE1 Sink: PE3 Select Type: Manually Selected Tunnel Name(ID): Tunnel-0001 Demanded Bandwidth(kbit/s): Use Mode: Shared

Set parameters related to the tunnel between PE2 and PE3 as follows:
l l l l l l

Source: PE2 Sink: PE3 Select Type: Manually Selected Tunnel Name(ID): Tunnel-0003 Demanded Bandwidth(kbit/s): Use Mode: Shared

5. 6.

Click Next and configure the service access ports. Click Add to add three service access ports of the PE equipment.

Set the related parameters as follows:

l l l l

PE: PE1, PE2, PE3 Interface: 1-EG16-1(PORT-1) IP Designated Format: Manually Specified IP/Mask: 192.168.0.1/30, 192.168.0.5/30, 192.168.0.3/30

7. 8.

Click Next to configure protocols. In the Config Protocol area, click Add to configure protocols for the three PEs. Set the related parameters as follows:
l l

PE: PE1, PE2, PE3 OSPF Instance ID: Manually Specified

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

21-70

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

9.

In the Protocol Interface area, click OSPF tab. Then, click Add to add three pairs of peers. Set the related parameters as follows:
l l

Interface: 1-EG16-1(PORT-1) Hello Timer((s): 100

10. Click Finish. L3VPN-0001 is successfully created. ----End

21.9 Configuration Example of a Hub&Spoke VPN Service

This topic describes the configuration example of the Hub&Spoke VPN service. A configuration flow diagram is provided to describe the process of service configuration. The configuration example describes the configuration networking diagram, service planning, and configuration process. 21.9.1 Configuration Networking Diagram This topic describes the networking diagram of the sites of the Hub&Spoke VPN service. 21.9.2 Service Planning Site1 and Site2 are Spoke-CE sites and Site3 is a Hub-CE site. 21.9.3 Configuration Process This topic describes how to configure the Hub&Spoke VPN services described in the configuration example.

21.9.1 Configuration Networking Diagram

This topic describes the networking diagram of the sites of the Hub&Spoke VPN service.

Requirements and Networking Diagram

Figure 21-24 shows the networking diagram of the Hub&Spoke VPN services. The communication between the two Spoke-CE sites are controlled by the central site Hub-CE. That is, all Spoke-CE sites can communicate with site Hub-CE, but the Spoke-CE sites cannot directly communicate with each other. Three sets of PE equipment exist in this network. Each set of the PE equipment is connected to a CE site. The OptiX PTN 3900 is used for PE1, PE2, and PE3. The following shows the connectivity between any two sites.
l l l

Site Spoke-CE1 and site Hub-CE can communicate with each other. Site Spoke-CE2 and site Hub-CE can communicate with each other. Site Spoke-CE1 and site Spoke-CE2 can communicate with each other.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21-71

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 21-24 Networking of the Hub&Spoke VPN service

AS: 65410 Spoke-CE1
Site1 192.168.0.2 RD 100:1 RT Export 100:1 RT Import 200:1

AS: 100 Spoke-PE1 Spoke-PE2

RD 100:1 RT Export 100:1 RT Import 200:1

RD 100:1 RT Export 200:1 RT Import 100:1

AS: 65430 Hub-CE

Backbone Hub-PE
Site3 192.168.0.4

AS: 65420
Site2

Spoke-CE2
192.168.0.6

OptiX PTN Router

Figure 21-25 shows the NE planning diagram. Figure 21-25 NE planning diagram
1-EG16-1 ( PORT -1) 3-EG16-1 (PORT -1)

Spoke-CE1
Site1 192.168.0.2

192.168.0.1 192.168.1.1

3-EG16-1 ( PORT 1) 192.168.1.2

Spoke-PE1 Spoke-PE2

Backbone Hub-PE

Site3 192.168.0.4

Spoke-CE2

Site2 192.168.0.6 1-EG16-1 ( PORT 1) 192.168.0.5

Hub-CE
3-EG16-1 ( PORT - 3-EG16-2 ( PORT 1) 2) 192.168.2.1 192.168.2.2 1-EG16-1 ( PORT 1) 192.168.0.3

21.9.2 Service Planning

Site1 and Site2 are Spoke-CE sites and Site3 is a Hub-CE site.

Service Planning
In the case of the Hub&Spoke networking, the communication between the Spoke-CE sites in the same VPN is controlled by the central site Hub-CE. That is, the traffic between the SpokeCE sites is forwarded by the central site Hub-CE and the Hub-PE sites. Table 21-5 shows the planning of the parameters for VPN.
21-72 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

Table 21-5 VPN parameter planning Parameter General Attributes Service ID Name Label Distribution Policy Select PE PE Description Automatically Assigned L3VPN-0001 Per-VPN Spoke-PE1 Spoke-PE2 Hub-PE Router Distinguisher Value Router Distinguisher Format VPN Max. Routes Count Configure RT Route Target Value Route Target Format Export PEs Import PEs Configure Tunnel Selection Source Sink Select Type Tunnel Name(ID) Demanded Bandwidth(kbit/ s) Use Mode Configure Service Access Port PE Interface IP Designated Format IP/Mask 100:1 AS:Number 32000 100:1, 200:1 AS:Number Spoke-PE1 and Spoke-PE2, Hub-PE Hub-PE, Spoke-PE1 and Spoke-PE2 Spoke-PE1, Spoke-PE2 Hub-PE Manually Selected No Limit Shared Spoke-PE1, Spoke-PE2, Hub-PE PE1, PE2, PE3: 1-EG16-1 (PORT-1) Manually Specified 192.168.0.1/30, 192.168.0.5/30, 192.168.0.3/30 Spoke-PE1, Spoke-PE2, Hub-PE

Configure Protocol

PE

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21-73

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Parameter EBGP Instance ID AS No. Router ID EBGP Peer Remote IP Remote AS No.

Description Automatically Assigned 100 1.1.1.1, 1.1.1.2, 1.1.1.3 100.1.1.2, 100.2.1.2, 110.1.1.2 65410, 65420, 65430

21.9.3 Configuration Process

This topic describes how to configure the Hub&Spoke VPN services described in the configuration example.

Prerequisite
You must learn about the networking requirements and service planning described in the example. The network must be created. Before configuring the L3VPN service, make sure that the port DCN is disabled.

Procedure
Step 1 Configure network-side ports for Spoke-PE1, Spoke-PE2, and Hub-PE. 1. In the NE Explorer, select Spoke-PE1 and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Configure the network-side interface. On the General Attributes tab page, select the 3-EG16-1(PORT-1) port and set Port Mode to Layer 3. Set parameters as required. Click Apply.

2.

Set the related parameters as follows:

l l l

Enable Port: Enabled Port Mode: Layer 3(The port carries a tunnel.) Working Mode: Auto-Negotiation (Set the working modes of the local port and opposite port as the same.) Max Frame Length(byte): 1620 (Set this parameter according to the length of data packets. All the received data packets that contain more bytes than the maximum frame length are discarded.)

3.

On the Layer 3 Attributes tab page, select the 3-EG16-1(PORT-1) port, set Enabled Tunnel to Enabled and Specify IP to Manually, and set IP Address and IP Mask. Click Apply.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

21-74

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

Set the related parameters as follows:

l l

Enabled Tunnel: Enabled Max Reserved Bandwidth(kbit/s): 102400 (The maximum reserved bandwidth should not exceed the physical bandwidth of the bearer port.) TE Measurement: 10 (You can intervene in the route selection by adjusting the TE measurement of the link. The smaller the value of the TE measurement, the higher the priority of the link.) Specify IP: Manually (Manually indicates that you can set the IP address of the port.) IP Address: 192.168.1.1 IP Mask: 255.255.255.252

l l l

4.

In the NE Explorer, select Spoke-PE2. To configure the attributes of the 3-EG16-1 (PORT-1) port, refer to Step 1.1 through Step 1.3. Set the related parameters as follows: The parameter settings of the Spoke-PE2-3-EG16-1(PORT-1) port are consistent with the parameter settings of the Spoke-PE1-3-EG16-1(PORT-1) port and the IP address is set to 192.168.2.1.

5.

In the NE Explorer, select Hub-PE. To configure the attributes of the 3-EG16-1(PORT-1) and 3-EG16-2(PORT-2) ports, refer to Step 1.1 through Step 1.3. Set the related parameters as follows: The parameter settings of the Hub-PE-3-EG16-1(PORT-1) and Hub-PE-3-EG16-2 (PORT-2) ports are consistent with the parameter settings of the Spoke-PE1-3-EG16-1 (PORT-1) port and the corresponding IP addresses are set to 192.168.1.2 and 192.168.2.2.

Step 2 Configure client-side ports for PE1, PE2, and PE3. 1. In the NE Explorer, select PE1. To configure the port attributes of 1-EG16-1(Port-1), refer to Step 1.1 through Step 1.3. Set the related parameters as follows: Set the general attributes of PE1-1-EG16-1(Port-1) to the same as the general attributes of PE1-3-EG16-1(Port-1). Set Specify IP to Unspecified for Layer 3 attributes of PE1-1EG16-1(Port-1). 2. In the NE Explorer, select PE2. To configure the port attributes of 1-EG16-1(Port-1), refer to Step 1.1 through Step 1.3. Set the related parameters as follows: Set the general attributes of PE2-1-EG16-1(Port-1) to the same as the general attributes of PE1-3-EG16-1(Port-1). Set Specify IP to Unspecified for Layer 3 attributes of PE2-1EG16-1(Port-1). 3. In the NE Explorer, select PE3. To configure the port attributes of 1-EG16-1(Port-1), refer to Step 1.1 through Step 1.3. Set the related parameters as follows: Set the general attributes of PE3-1-EG16-1(Port-1) to the same as the general attributes of PE1-3-EG16-1(Port-1). Set Specify IP to Unspecified for Layer 3 attributes of PE3-1EG16-1(Port-1). Step 3 Specify LSR IDs for NEs.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 21-75

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

1. 2.

In the NE Explorer, select Spoke-PE1 and choose Configuration > MPLS Management > Basic Configuration from the Function Tree. Set the parameters, such as LSR ID and Start of Global Label Space, for the NE. Click Apply. Set the related parameters as follows:
l l

LSR ID: 1.1.1.1 (The LSR ID must be unique in the network.) Start of Global Label Space: 0 (The minimum value of the ingress and egress labels of a unicast tunnel.)

3.

In the NE Explorer, select Spoke-PE2. To set the parameters, such as LSR ID, for SpokePE2, refer to Step a and Step b. Set the related parameters as follows:
l l

LSR ID: 1.1.1.2 (The LSR ID must be unique in the network.) Start of Global Label Space: 0 (The minimum value of the ingress and egress labels of a unicast tunnel.)

4.

In the NE Explorer, select Hub-PE. To set the parameters, such as LSR ID, for Hub-PE, refer to Step a and Step b. Set the related parameters as follows:
l l

LSR ID: 1.1.1.3 (The LSR ID must be unique in the network.) Start of Global Label Space: 0 (The minimum value of the ingress and egress labels of a unicast tunnel.)

Step 4 Configure control planes for NEs. 1. 2. In the NE Explorer, select Spoke-PE1 and choose Configuration > Control Plane Configuration > IGP-ISIS Configuration from the Function Tree. Choose the Port Configuration tab and then click New. Click Add in the dialog box displayed. Then Select 3-EG16-1(PORT-1) in the port tab. Click OK. The configuration parameters are as follows:
l l

Link Level: level-1-2 LSP Retransmission Interval(s): 5 (In the case of a point-to-point link, if the local router fails to receive any response in a period after transmitting the LSP, the local router considers that the LSP is lost or discarded. To ensure the transmission reliability, the local router transmits the LSP again.) Minimum LSP Transmission Interval (ms): 30

3. 4. 5.

Choose Configuration > Control Plane Configuration > MP-BGP Configuration from the Function Tree. Click the MP-BGP Configuration tab. Click New. In the Create MP-BGP Protocol Instance dialog box, set MP-BGP Instance ID to 1 and AS Number to 100. Click Apply. Select the Peer Configuration tab. Click New. In the Create Peer dialog box, set parameters. For example, set MP-BGP Instance ID to 1 and AS Number to 100. Set the following parameters to configure Hub-PE as an MP-BGP peer.
l l l

MP-BGP Instance: 1 Remote IP Address: 192.168.1.2 AS Number: 100

6.

In the NE Explorer, select Spoke-PE2. To set the parameters of the control plane for SpokePE2, refer to Step a through Step e.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

21-76

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

The IS-IS protocol settings of 3-EG16-1(PORT-1) port for Spoke-PE2 are consistent with the IS-IS protocol settings of Spoke-PE1. The MP-BGP protocol settings of Spoke-PE2 are consistent with the MP-BGP protocol settings of Spoke-PE1. Set the following parameters to configure Hub-PE as an MP-BGP peer.
l l l

MP-BGP Instance: 1 Remote IP Address: 192.168.2.2 AS Number: 100

7.

In the NE Explorer, select Hub-PE. To set the parameters of the control plane for Hub-PE, refer to Step a through Step e. The IS-IS protocol settings of 3-EG16-1(PORT-1) port and 3-EG16-2(PORT-2) port for Hub-PE are consistent with the IS-IS protocol settings of Spoke-PE1. The MP-BGP protocol settings of Hub-PE are consistent with the MP-BGP protocol settings of Spoke-PE1. Set following parameters to configure Spoke-PE1 as an MP-BGP peer.
l l l

MP-BGP Instance: 1 Remote IP Address: 192.168.1.1 AS Number: 100

Set following parameters to configure Spoke-PE2 as an MP-BGP peer.

l l l

MP-BGP Instance: 1 Remote IP Address: 192.168.2.1 AS Number: 100

Step 5 Create dynamic tunnels. 1. 2. On the Main Topology of the T2000, choose Trail > Tunnel > Tunnel Creation from the Main Menu. The Create Tunnel dialog box is displayed. Configure the dynamic tunnel between Spoke-PE1 and Hub-PE. Select the Create Reverse Tunnel check box. In the General Attributes area, configure the positive and reverse tunnels.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21-77

21 Configuring an L3VPN Service

OptiX iManager T2000 Operation Guide for PTN NE Management

Set the related parameters as follows:

l l l

Tunnel ID: 1 (Positive), 2 (Reverse) Name: Tunnel-0001 (Positive), Tunnel-0002 (Reverse) Signal Type: Dynamic (Dynamic indicates that the labels are distributed through the LSP signaling; Static indicates that the labels are manually added.) Scheduling Type: E-LSP Bandwidth (kbit/s): 4096 (Set the bandwidth according to networking planning.)

l l

3.

Click Next, select source and sink nodes, and then click Add to set route constraints.

21-78

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

21 Configuring an L3VPN Service

Set the related parameters as follows:

l l l

Source Node: Spoke-PE1 Sink Node: Hub-PE Route Constraint Port IP Address: 192.168.2.1 (for the positive tunnel, 192.168.1.1 (for the reverse tunnel) Rerouting Mode: Include Strict

4. 5.

Click Next. Use the default values of parameters, such as Setup Priority and Hold Priority, for the tunnels. Click Finish. To configure the dynamic tunnel between Spoke-PE2 and Hub-PE, refer to Step a through Step d. Set the related parameters as follows:
l l l l l l l

Tunnel ID: 3 (for the positive tunnel), 4 (for the reverse tunnel) Name: Tunnel-0003 (for the positive tunnel), Tunnel-0004 (for the reverse tunnel) Signal Type: Dynamic Scheduling Type: E-LSP Bandwidth(kbit/s): 4096 (Set this value based on the networking planning.) Source Node: Spoke-PE2 Sink Node: Hub-PE

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21-79

21 Configuring an L3VPN Service

l

OptiX iManager T2000 Operation Guide for PTN NE Management

Route Constraint Port IP Address: 192.168.2.1 (for the positive tunnel, 192.168.2.2 (for the reverse tunnel) Rerouting Mode: Include Strict Other parameters use default values.

l l

Step 6 Create L3VPN services. 1. 2. On the Main Topology of the T2000, choose Trail > PTN Service > L3VPN Service Creation from the Main Menu. The L3VPN Service Creation dialog box is displayed. click Add. Add Spoke-PE1, Spoke-PE2, and Hub-PE in the Select PE area.

Set the related parameters as follows:

l l l l l l l

Service ID: Automatically Assigned Name: L3VPN-0001 Label Distribution Policy: Per-VPN PE: Spoke-PE1, Spoke-PE2 and Hub-PE Router Distinguisher Value: 100:1 Router Distinguisher Format: AS:Number VPN Max. Routes Count: 32000

3.

Click Next. In the Config RT area, Click Add to add two RTs. Set the parameters related to the RTs. Set the parameters related to the two RTs.
l l l l

Router Target Value: 100:1 Router Target Format: AS:Number Export PEs: Spoke-PE1, Spoke-PE2 Import PEs: Hub-PE
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

21-80

OptiX iManager T2000 Operation Guide for PTN NE Management

l l l l

21 Configuring an L3VPN Service

Router Target Value: 200:1 Router Target Format: AS:Number Export PEs: Hub-PE Import PEs: Spoke-PE1, Spoke-PE2

4.

In the Config Tunnel Selection area, click Add to add three tunnels and set the parameters related to the tunnels. Set parameters related to the tunnel between Spoke-PE1 and Hub-PE as follows:
l l l l l l

Source: Spoke-PE1 Sink: Hub-PE Select Type: Manually Selected Tunnel Name(ID): Tunnel-0001 Demanded Bandwidth(kbit/s): Use Mode: Shared

Set parameters related to the tunnel between Spoke-PE2 and Hub-PE as follows:
l l l l l l

Source: Spoke-PE2 Sink: Hub-PE Select Type: Manually Selected Tunnel Name(ID): Tunnel-0003 Demanded Bandwidth(kbit/s): Use Mode: Shared

5. 6.

Click Next and configure the service access ports. Click Add to add three service access ports of the PE equipment.

Set the related parameters as follows:

l l l l

PE: Spoke-PE1, Spoke-PE2, Hub-PE Interface: 1-EG16-1(PORT-1) IP Designated Format: Manually Specified IP/Mask: 192.168.0.1/30, 192.168.0.5/30, 192.168.0.3/30

7. 8.

Click Next to configure protocols. In the Config Protocol area, click EBGP tab. Then, click Add to configure protocols for the three PEs. Set the related parameters as follows:

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

21-81

21 Configuring an L3VPN Service

l l l l

OptiX iManager T2000 Operation Guide for PTN NE Management

PE: Spoke-PE1, Spoke-PE2, Hub-PE EBGP Instance ID: Automatically Assigned AS No.: 100 Router ID: 1.1.1.1, 1.1.1.2, 1.1.1.3

9.

In the EBGP Peer area, click Add to add three pairs of peers. Set the related parameters as follows:
l l

Remote IP: 192.168.0.2, 192.168.0.6, 192.168.0.4 Remote AS No.: 65410, 65420, 65430

10. Click Finish. L3VPN-0001 is successfully created. ----End

21-82

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

22 Configuring the IGMP Snooping

22

Configuring the IGMP Snooping

About This Chapter

The IGMP Snooping enhances the capability of managing the multicast of the Layer 2 switching services. The IGMP Snooping avoids the broadcast of the service flow on the Layer 2 equipment, and thus increases the resource utilization of the equipment and links. 22.1 Overview of the IGMP Snooping This section describes the IGMP Snooping, in terms of the aim, compliant standard and protocol, and related concepts. 22.2 Basic Concepts This section describes the basic concepts of the IGMP Snooping, which is used for understanding and applying the IGMP Snooping. The basic concepts covers the enabling of the IGMP snooping protocol, router port, member port, aging time of the router port, maximum non-response times for multicast group members, multicast strategy, and quick deletion of member port. 22.3 Application of the IGMP Snooping The IGMP Snooping enhances the resource utilization through multicast forwarding, enhances the security of the T2000 through restriction on user access, and enhances the network reliability through quick response to the link change. 22.4 Configuring the IGMP Snooping Parameters Parameters related to the IGMP Snooping include Enabled Protocol, Router Port Aging Time (min), Maximum times of No Response from Multicast Members and Maximum Number of Multicast Groups. Configure these parameters for the IGMP Snooping to work normally. After configuring the IGMP Snooping parameters for multicast services that are created, you can set some ports for the multicast service as quick leave ports. The multicast user on each quick leave port can then switch the multicast service channels quickly. 22.5 Configuring the Router Management The user manually creates the router port, through which the equipment responds to the packets of the router for querying the IGMP Snooping. The router port is not aged automatically, and thus always exists unless manually deleted. 22.6 Configuring the Route Member Port Management To define the multicast scope, configure the route member ports. The static multicast member ports are not aged automatically, and thus always exist unless manually deleted.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 22-1

22 Configuring the IGMP Snooping

OptiX iManager T2000 Operation Guide for PTN NE Management

22.7 Configuring the Packet Statistics Set the status of the protocol packet statistics to start, stop or clear the packet statistics. The packet statistics data indicates the running status of multicast services. 22.8 IGMP Snooping Configuration Case A case is provided here to show how to configure the IGMP Snooping parameters for provision of the IGMP Snooping function.

22-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

22 Configuring the IGMP Snooping

22.1 Overview of the IGMP Snooping

This section describes the IGMP Snooping, in terms of the aim, compliant standard and protocol, and related concepts.

Objectives and Benefits

The IGMP protocol applies to the router and host, such as the switch, hub, or DSLAM. It is used to manage the addition and deletion of group members. The PTN equipment with the IGMP Snooping enabled dynamically learns the router port, multicast group and group members through snooping of the IGMP protocol packets between the multicast management router and host. Thus, the multicast packets are prevent from being broadcast in the Layer 2 switch. The equipment can transmit the multicast services, such as the IPTV or conference call, through the IGMP Snooping. The IGMP Snooping has a strong capability of managing the multicast services, such as dynamic response to IGMP Join/Leave requests of customers. Thus, it is applied to the equipment at the edge/access and convergence layers. Figure 22-1 shows the networking diagram of the multicast services with the IGMP protocol. The networking diagram consists of the multicast service source, multicast management router, PTN equipment, and hosts In the actual networking, the PTN equipment and multicast management router, and the multicast management router and the service source may be connected through complex networks respectively. Figure 22-1 Application of the IGMP Snooping-Supported Equipment in the Network

Multicast management router

Host (Non-multicast member)

Host Host (Multicast member)(Multicast member)

Host (Non-multicast member)

Physical connection Flow direction of the multicast service

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

22-3

22 Configuring the IGMP Snooping

OptiX iManager T2000 Operation Guide for PTN NE Management

The advantages of the application of the IGMP Snooping are as follows:

l l l

The network bandwidth can be saved. Signals are forwarded based on the VLAN. Hence, the information security is increased. Quick response is made to the link fault. Hence, the reliability is enhanced.

Compliant Standard and Protocol

The IGMP complies with RFC 4541, Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches

22.2 Basic Concepts

This section describes the basic concepts of the IGMP Snooping, which is used for understanding and applying the IGMP Snooping. The basic concepts covers the enabling of the IGMP snooping protocol, router port, member port, aging time of the router port, maximum non-response times for multicast group members, multicast strategy, and quick deletion of member port.

Enabling of the IGMP Snooping Protocol

After the IGMP Snooping protocol is enabled, the equipment begins to perform the multicast group learning and aging. Then, the multicast services are multicast in corresponding multicast groups. If the IGMP Snooping is disabled, the equipment does not perform the multicast group learning and aging. In addition, the equipment deletes all the learned dynamic multicast groups.

Router Port
The router port refers to the port that faces the multicast router. The E-LAN service of the PTN equipment takes the port that receives the IGMP query packets as the router port. The router port consists of the following two types:
l

Dynamic router port, which relies on the protocol packets exchanged between the router and host, and can be dynamically maintained. Each of this port can enable a router port aging timer. When the timer times out, this router port is invalid. Static router port, which is specified by users by using configuration commands, cannot be aged.

Member Port
The multicast member port refers to the port that faces the host of the member. The switch transmits the multicast packets from this port. The multicast group member port, referred to as member port for short, consists of the following two types:
l

Dynamic member port, which can receive the IGMP report packets. This port, relies on the protocol packets exchanged between the router and host, can be dynamically maintained. Each of this port can enable a member port aging timer. When the timer times out, that is, when the times of not receiving the IGMP report packets exceed certain times, this member port becomes invalid.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

22-4

OptiX iManager T2000 Operation Guide for PTN NE Management

l

22 Configuring the IGMP Snooping

Static member port, which is specified by users by using configuration commands, cannot be aged.

Aging Time of the Router Port

The IGMP protocol requires that the router periodically transmit the IGMP query packets, which are used to obtain the information indicating whether the host is added to the multicast group. After the E-LAN service of the PTN equipment learns the router port in a broadcast domain, the aging timer should be enabled for this port. When the aging timer of the router port times out but this port does not receive any query packet, the IGMP Snooping sub-system takes that this port is invalid, and then the sub-system ages this port. If this port receives the query packet, including the query packet of the specified group, before the aging timer times out, the aging timer of the router port should be re-set.

Maximum Non-Response Times for Multicast Group Members

The equipment should learn the deletion information on the multicast members in a timely manner. Otherwise, the equipment continuously transmits service packets to the multicast group members deleted from the multicast group, which consumes the resources of the PTN equipment and downstream equipment. Thus, when the response packet of the first member in the multicast group is received, the response packet is unicast to the router port instead of being multicast in the multicast group. In this way, the PTN equipment can snoops whether the query packet is responded on each group member. When the equipment receives the IGMP response packet sent by a port for the first time, the equipment first adds the port to the corresponding multicast group, and then enables the count of the query non-response times for this multicast member. When the query packet is sent to a multicast member and the response packet is not received within the required response period, the count of the query non-response times for this multicast member is started. When the count value reaches a threshold, the equipment considers that the multicast member leaves the multicast group, and thus deletes the multicast member. In this case, the equipment connected to this port cannot receive the multicast services. If the member receives the response packet within the aging time, re-set the count value.

Multicast Strategy
The PTN equipment determines the member relation in this network section according to the received IGMP group member report packet. The range of the multicast groups can be restrained through the ACL. By default, the ACL is not set. Thus, the host can be added to any multicast groups.

Quick Deletion of the Member Port

When only one multicast service receive end is connected to the multicast member port, the quick deletion function can be set on this port. In other words, when the member port receives the deletion packet, it immediately deletes the member port, and it stops forwarding the query packet for a specified group. During the channel switching, the multicast service management equipment that should be connected to the terminal of the IPTV service such as the set top box has this function. If the port with the enabled quick deletion function connects to multiple multicast receive members, when a member is deleted from the multicast group, the PTN equipment cuts the multicast services. In this way, other members cannot continue to receive the multicast services.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 22-5

22 Configuring the IGMP Snooping

OptiX iManager T2000 Operation Guide for PTN NE Management

Thus, when this function is used, you should make sure that only one multicast service receive end is connected to this port.

22.3 Application of the IGMP Snooping

The IGMP Snooping enhances the resource utilization through multicast forwarding, enhances the security of the T2000 through restriction on user access, and enhances the network reliability through quick response to the link change.

Multicast Forwarding
The IGMP Snooping is configured on PTN-1 and PTN-2. When the multicast packets reach PTN-1 or PTN-2, the packets are distributed at the port, which has the group member host in the downstream. Figure 22-2 Multicast forwarding

Internet /Intranet Source

Host 1

Host 2

Host3

Host 4

Host 5

Group member

Group member

Group member
Multicast packets

Restriction on the User Access

Illegal users are prevent from using multicast services by configuring the attributes of the multicast strategy, static multicast group, static router port and unknown multicast service forwarding. As shown in Figure 22-2, the multicast group strategy is configured on PTN-1 and PTN-2. In this way, the range of the group addresses that can be accessed by users through the
22-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

22 Configuring the IGMP Snooping

access control list (ACL) is set. Thus, the multicast packets that can be received by the user host can be controlled.

Quick Response to the Link Change

When the topology of the network where the PTN equipment resides changes, the switching equipment in the downstream of the PTN equipment should set up new forwarding table items in minutes after receiving the subsequent multicast query packet. As a result, the multicast services are interrupted for a long time. The IGMP Snooping notifies the change of the response spanning tree topology and fast transmits the query packets for the router. In this way, the switching equipment in the downstream can fast learn the multicast information and decrease the service interruption time.

22.4 Configuring the IGMP Snooping Parameters

Parameters related to the IGMP Snooping include Enabled Protocol, Router Port Aging Time (min), Maximum times of No Response from Multicast Members and Maximum Number of Multicast Groups. Configure these parameters for the IGMP Snooping to work normally. After configuring the IGMP Snooping parameters for multicast services that are created, you can set some ports for the multicast service as quick leave ports. The multicast user on each quick leave port can then switch the multicast service channels quickly.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The E-LAN service is already created.

Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function Tree. Step 2 Click the Protocol Configuration tab to configure the required parameters. Click Apply.

NOTE

When setting parameters, note the following:

l l l l l

Enabled Protocol: Enable or disable the IGMP Snooping function. Router Port Aging Time(min): The value ranges from 1 to 120, and defaults to 8. Set this parameter when the IGMP Snooping function is enabled. Maximum times of No Response from Multicast Members: The value ranges from 1 to 4, and defaults to 3. Set this parameter when the IGMP Snooping function is enabled. Maximum Number of Multicast Groups: The value range depends on the maximum specification of the equipment. Set this parameter when the IGMP Snooping function is enabled. Maximum Number of Multicast Groups Member: The value range depends on the maximum specification of the equipment. Set this parameter when the IGMP Snooping function is enabled.

Step 3 Select the multicast service that requires setting of the quickly delete member port. The lower pane lists the multicast service.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 22-7

22 Configuring the IGMP Snooping

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 4 Configure the parameters related to the quickly delete member port for the multicast service. The parameters include VLAN ID, Port Type and Port. Double-click the parameters to modify them.
NOTE

To set a port for a multicast service as a quickly delete member port, the port should have only one multicast service user. Otherwise, different users on the port affect each other when receiving multicast services.

Step 5 Click Apply. ----End

22.5 Configuring the Router Management

The user manually creates the router port, through which the equipment responds to the packets of the router for querying the IGMP Snooping. The router port is not aged automatically, and thus always exists unless manually deleted.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. You must complete creation of the E-LAN service.

Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function Tree. Step 2 Click the Router Management tab. Click New to display the Create Router Port dialog box. In the dialog box, set the required parameters and select the multicast router ports to be added.

22-8

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

22 Configuring the IGMP Snooping

NOTE

When setting parameters, note the following:

l l l

Service ID: Select the ID of the service that belongs to the router port. In other words, Service ID is the ID of the E-LAN service. VLAN ID: Set the VLAN ID according to the application. The VLAN ID ranges from 1 to 4094. Available Port: Select the corresponding port. The added ports must belong to the VLAN of the service.

Step 3 Click OK. ----End

22.6 Configuring the Route Member Port Management

To define the multicast scope, configure the route member ports. The static multicast member ports are not aged automatically, and thus always exist unless manually deleted.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. E-LAN service is created.

Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function Tree. Step 2 Click the Route Member Port Management tab, and then click New to display the Create Member Port dialog box. Step 3 Set parameters in the dialog box.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

22-9

22 Configuring the IGMP Snooping

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

When setting parameters, note the following:

l l l l

Service ID: Select the ID of the service that belongs to the router interface. In other words, Service ID is the ID of the E-LAN service. VLAN ID: Set the VLAN ID according to the application. The VLAN ID ranges from 1 to 4094. Multicast MAC Address: The value ranges from 01-00-5E-00-01-00 to 01-00-5E-7F-FF-FF. Available Port: Select the corresponding port. The added ports must belong to the VLAN of the service.

Step 4 Click OK. ----End

22.7 Configuring the Packet Statistics

Set the status of the protocol packet statistics to start, stop or clear the packet statistics. The packet statistics data indicates the running status of multicast services.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The route member port is configured.

Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function Tree. Step 2 Click the Packet Statistics tab, and set parameters for the IGMP protocol packet statistics. Then, click Apply.

22-10

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

22 Configuring the IGMP Snooping

NOTE

When setting parameters, note the following:

l l l l l l l l l l l l l l

Service ID is the ID of the E-LAN service. The VLAN ID ranges from 1 to 4094. Port Type: The port type is V-UNI or V-NNI. This parameter cannot be set. Port: Select the corresponding port. Packet Statistic Status: The status is Stop, Start or Clear. The default status is Stop. IGMPv1 Query Packet Count: This parameter is of the query result, and thus cannot be set. IGMPv2 Query Packet Count: This parameter is of the query result, and thus cannot be set. IGMPv3 Query Packet Count: This parameter is of the query result, and thus cannot be set. IGMP Leaving Packet Count: This parameter is of the query result, and thus cannot be set. IGMPv1 Member Report Packet Count: This parameter is of the query result, and thus cannot be set. IGMPv2 Member Report Packet Count: This parameter is of the query result, and thus cannot be set. IGMPv3 Member Report Packet Count: This parameter is of the query result, and thus cannot be set. Unrecognized or Unprocessed Packet Count: This parameter is of the query result, and thus cannot be set. Discarded Incorrect Packet Count: This parameter is of the query result, and thus cannot be set.

Step 3 Click Apply. The Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. ----End

22.8 IGMP Snooping Configuration Case

A case is provided here to show how to configure the IGMP Snooping parameters for provision of the IGMP Snooping function. 22.8.1 Case Description The case description covers the functional requirements, networking diagram and service planning. To plan a service is to design the details of a service to be created according to the service requirements. Service planning provides guidelines for service configuration. The service planning covers details such as the networking, requirements, and configuration data. 22.8.2 Configuration Flow This section describes how to configure the IGMP Snooping parameters.

22.8.1 Case Description

The case description covers the functional requirements, networking diagram and service planning. To plan a service is to design the details of a service to be created according to the
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 22-11

22 Configuring the IGMP Snooping

OptiX iManager T2000 Operation Guide for PTN NE Management

service requirements. Service planning provides guidelines for service configuration. The service planning covers details such as the networking, requirements, and configuration data.

Networking and Requirements

As shown in Figure 22-3, the PTN equipment multicasts the data packets from the router interface (11-EG16-1) to the multicast member interfaces (11-EG16-2, 11-EG16-3 and 11EG16-4). Figure 22-3 IGMP Snooping networking application

11-EG16-1

PTN 11-EG16-2 11-EG16-4 11-EG16-3

host 1

host 2

host 3

group member

group member

group member

multicast packets

Service Planning
The engineering planning department should plan the engineering according to the related requirements, and output detailed planning information. Figure 22-3 is considered as an example to show the service planning. Table 22-1, Table 22-2, Table 22-3 and Table 22-4 list the parameters planned for the IGMP Snooping configuration. Table 22-1 Configuration parameters for enabling the IGMP Snooping Attribute Enabled Protocol Router Port Aging Time (min)
22-12

Value Enabled 8
Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX iManager T2000 Operation Guide for PTN NE Management

22 Configuring the IGMP Snooping

Attribute Maximum times of No Response from Multicast Members Maximum Number of Multicast Groups

Value 3 Unlimited

Table 22-2 Configuration parameters for managing the IGMP Snooping routes Attribute Service ID VLAN ID Selected Port Value 101 30 11-EG16-1 (PORT-1)[30]

Table 22-3 Configuration parameters for managing the IGMP Snooping route member ports Attribute Service ID VLAN ID Multicast MAC Address Selected Port Value 101 30 01-00-5E-00-01-02 11-EG16-2(PORT-2)[30], 11-EG16-3(PORT-3)[30], 11-EG16-4(PORT-4)[30]

Table 22-4 Configuration parameters for packet statistics on the IGMP Snooping Attribute Packet Statistic Status Value Start

22.8.2 Configuration Flow

This section describes how to configure the IGMP Snooping parameters.

Prerequisite
You must understand the networking, requirements and service planning of the example. The E-LAN service is already created.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

22-13

22 Configuring the IGMP Snooping

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 On the T2000, set the IGMP Snooping parameters. For details, see 22.4 Configuring the IGMP Snooping Parameters. Parameters related to the IGMP Snooping are as follows:
l l l l

Enabled Protocol: Enabled Router Port Aging Time(min): 8 Maximum times of No Response from Multicast Members: 3 Maximum Number of Multicast Groups: Unlimited

Step 2 On the T2000, configure the route management. For details, see 22.5 Configuring the Router Management. Parameters related to the route management are as follows:
l l l

Service ID: 101 VLAN ID: 30 Selected Port: 11-EG16-1(PORT-1)[30]

Step 3 On the T2000, configure the route member port. For details, see 22.6 Configuring the Route Member Port Management. Parameters related to the route member ports are as follows:
l l l l

Service ID: 101 VLAN ID: 30 Multicast MAC Address: 01-00-5E-00-01-02 Selected Port: 11-EG16-2(PORT-2)[30], 11-EG16-3(PORT-3)[30], 11-EG16-4(PORT-4) [30]

Step 4 On the T2000, configure the packet statistics status. For details, see 22.7 Configuring the Packet Statistics. Parameters related to the packet statistics status are as follows:
l

Packet Statistic Status: Start

----End

22-14

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

23 Configuring the MSTP

23
About This Chapter

Configuring the MSTP

The MSTP is one of the spanning tree protocols. It is compatible with the spanning tree protocol (STP) and rapid spanning tree protocol (RSTP), and it also fixes the defects of the STP and RSTP. 23.1 Overview of the MSTP This section describes the MSTP, in terms of the aim and compliant standard and protocol. 23.2 Basic Concepts This section describes related concepts of the MSTP. 23.3 MSTP Application In the case of the Ethernet user network where loops exist, the MSTP generates the tree topology according to VLAN IDs of the Ethernet packets. Thus, the broadcast storm is avoided and the network traffic is balanced according to the VLAN IDs of the Ethernet packets. 23.4 Configuring a Port Group When both the PTN equipment and the user network need run the MSTP, configure the ports as one port group. As a network bridge (switch), where the MSTP protocol is running, the port group is involved in calculation of the spanning tree of the user network. 23.5 Configuring Bridge Parameters The bridge parameters include the bridge parameters and port parameters. The bridge parameters define the parameters of the port group as the MST bridge, and the port parameters define the role of each port in the MSTP protocol. 23.6 Configuring CIST and MSTI Parameters Configure the bridge priority of the port group to specify the root of the spanning tree. Configure the MSTI port parameters to specify the MSTI priority and active/standby protection of the root bridges. 23.7 Querying the CIST Running Information Query the CIST running information to know the operation status of the MSTP protocol on the port group. 23.8 Configuring Protocol Transfer for Ports When a network has a switch where the STP protocol is running, the ports of the PTN equipment connected to the switch are automatically switched to the STP-compatible mode. When such a
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 23-1

23 Configuring the MSTP

OptiX iManager T2000 Operation Guide for PTN NE Management

switch becomes absent in the network, these ports still work in the STP-compatible mode. In this case, manually configure the port to recover the running of the MSTP protocol on the port. 23.9 Querying the MSTI Running Information Query the MSTI running information to know the status of any MSTI in the port group. 23.10 MSTP Configuration Case A case is provided here to describe the MSTP networking scheme and method of configuring the MSTP.

23-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

23 Configuring the MSTP

23.1 Overview of the MSTP

This section describes the MSTP, in terms of the aim and compliant standard and protocol.

Overview of the STP/RSTP/MSTP

The MSTP is one of the spanning tree protocols. It is compatible with the spanning tree protocol (STP) and rapid spanning tree protocol (RSTP), and it also fixes the defects of the STP and RSTP. For the Ethernet network with physical loops, IEEE puts forward the STP protocol (IEEE 802.1D, 1998 Edition) to prevent the generation of the network storm. In addition, IEEE puts forward the RSTP protocol (IEEE 802.1w-2001) to fix the defects of the STP, which result in slow convergence rate. The STP/RSTP aims to divide a bridged LAN into a single spanning tree on the logical topology. Thus, the network storm can be avoided. See Figure 23-1. Figure 23-1 STP/RSTP
Switch A Switch B Switch A Switch B

Switch C

Switch D

Switch C

Switch D

Switch E

Switch F

Switch E

Switch F Root: Switch F

Limitations of the STP/RSTP

During the fast development of the VLAN technology (IEEE 802.1Q), the limitations of the STP/RSTP gradually emerge. The STP/RSTP protocol divides the network topology into a single spanning tree, and thus the following problems occur:
l l

When the link is congested, it cannot bear any traffic. Thus, the bandwidth is wasted. When the network structure is dissymmetrical, a portion of the VLAN packets may not be forwarded.

As shown in Figure 23-2, Host B and Host C belong to VLAN 2. The VLAN tag with 2 as the VID is added to the Ethernet frames sent by Host B and Host C after the frames enter the switch. Host A and Host D belong to VLAN 3. The VLAN tag with 3 as the VID is added to the Ethernet frames sent by Host A and Host D after the frames enter the switch. As shown in Figure 23-2,
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 23-3

23 Configuring the MSTP

OptiX iManager T2000 Operation Guide for PTN NE Management

the corresponding VLAN packets can only pass through links marked with VLAN 2 or VLAN 3. Packets of VLAN 2 and VLAN 3 cannot pass through other links. After the STP/RSTP protocol is enabled, the network topology is divided into a single spanning tree, which congests other ports. The link between Switch C and Switch D is congested, and other links cannot forward packets of VLAN 2. Thus, communication between Host B and Host C is unavailable. Figure 23-2 Limitations of the STP/RSTP
Host A Switch A Switch B Host B

VLAN 3 Switch C VLAN 2 VLAN 3 VLAN 3 VLAN 2

VLAN 2 Switch D

Host C

Switch E

Switch F

Host D Ethernet link Spanning tree Root switch

Improvement of the MSTP

The MSTP fixes the defects of the STP and RSTP. The convergence rate of the MSTP is fast. In addition, traffic of different VLANs passes through corresponding trails, which provides a well load balancing mechanism. The MSTP divides a switching network into different regions, each of which is called an MST region. Within each region, there are multiple spanning trees, which are independent from each other. Each spanning tree is a multiple spanning tree instance (MSTI). The MSTP sets the VLAN mapping table, which specifies the mapping relation between VLAN and MSTI.
NOTE

Each VLAN corresponds to one MSTI. In other words, the data in the same VLAN can only be transmitted on one MSTI. One MSTI, however, may correspond to multiple VLANs.

23-4

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

23 Configuring the MSTP

The network shown in Figure 23-2 can be considered as an MST region when MSTP is used. Thus, Figure 23-3 shows the result. It is computed that two spanning trees are generated for VLAN 2 and VLAN 3 respectively.
l l

MSTI 1 takes Switch B as the root switch to forward packets of VLAN 2. MSTI 2 takes Switch F as the root switch to forward packets of VLAN 3.

In this way, all VLAN packets can be properly forwarded. In addition, different VLAN packets are forwarded through different paths. Thus, the load is balanced. Figure 23-3 MSTI in an MST region
Host A Switch A Switch B Host B

VLAN 3 Switch C VLAN 2 VLAN 3 VLAN 3 VLAN 2

VLAN 2 Switch D

Host C

Switch E

Switch F

Host D

Switch A

Switch B (Root)

Switch A

Switch B

VLAN 2 Switch C VLAN 2 VLAN 3 VLAN 2 Switch D

VLAN 3 Switch C VLAN 2 VLAN 3 VLAN 3

VLAN 2 Switch D

Switch E

Switch F

Switch E MSTI 2 -> VLAN 3

Switch F (Root)

MSTI 1 -> VLAN 2

Compliant Standard and Protocol

The MSTP complies with IEEE 802.1s, Virtual Bridged Local Area Networks - Amendment 3: Multiple Spanning Trees.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

23-5

23 Configuring the MSTP

OptiX iManager T2000 Operation Guide for PTN NE Management

23.2 Basic Concepts

This section describes related concepts of the MSTP. In this section, examples in Figure 23-4 and Figure 23-5 show the related concepts of the MSTP. Figure 23-4 Example of the MSTP
A0 A0 VLAN1 -> MSTI 1 VLAN2 -> MSTI 2 Other VLAN ->MSTI 0

D0

B0

VLAN1 -> MSTI 1 VLAN2 -> MSTI 2 VLAN3 -> MSTI 2 Other VLAN ->MSTI 0

C0 A0

VLAN1 -> MSTI 1 VLAN2 -> MSTI 2 Other VLAN ->MSTI 0

VLAN1--> MSTI 1 Other VLAN-->MSTI 0

CST

23-6

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

23 Configuring the MSTP

Figure 23-5 Example of the MST region

D0

Switch A

MSTI 1 Root: Switch B MSTI 2 Root: Switch D

Switch D

Switch B

MSTI 0 (IST) Root: Switch A

VLAN 1 VLAN 2 VLAN 3 Switch C

-> MSTI 1 -> MSTI 2 -> MSTI 2

Other VLAN -> MSTI 0

MST Region
The MST region consists of switches that support the MSTP in the LAN and network sections among them. Switches physically and directly connected and configured with the same MST region attributes belong to the same MST region. The attributes for the same MST region are as follows:
l l l

Same region name Same revision level Same mapping relation between the VLAN ID to MSTI

Within a LAN, there can be multiple MST regions, which are physically and directly or indirectly connected to each other. For example, as shown in Figure 23-4, there are four MST regions, A0, B0, C0 and D0.

MSTI
Within an MST region, there can be multiple spanning trees, which are independent from each other and correspond to different VLANs. Each spanning tree is an MSTI. For example, in the MST region D0, there are three MSTIs, MSTI 0, MSTI 1 and MSTI 2. See Figure 23-5.

CIST
The common and internal spanning tree (CIST), computed by using the RSTP algorithm, is a single spanning tree connecting all the switches within a switching network. In the CIST, the common spanning tree (CST) is the portion connected to each MST region. In the CIST, the portion in each MST region is the internal spanning tree (IST) of each MST region.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 23-7

23 Configuring the MSTP

OptiX iManager T2000 Operation Guide for PTN NE Management

CST
The CST, a spanning tree connected to all MST regions in a switching network, is the portion responsible for connecting each MST region in the CIST. If each MST region is considered as a switch, the CST is a spanning tree for the switch. For example, as shown in Figure 23-4, the dashed lines indicate the CST of the network.

IST
The IST, a spanning tree in each MST region, is a section of the CIST in an MST region. Normally, it is considered as the MSTI 0. For example, the MSTI 0 is shown in Figure 23-5. When a packet with a VLAN tag is transmitted in an MST region, if the VLAN ID has no corresponding MSTI, the packet is transmitted in the IST.

VLAN Mapping Table

The VLAN mapping table is an attribute of the MST region. It describes the mapping relation between the VLAN and MSTI in this MST region.

Regional Root
The regional root consists of the CIST regional root and MSTI regional root.
l

The CIST regional root is the root of the IST. For example, as shown in Figure 23-5, Switch A is the CIST regional root of the MST region D0. The MSTI regional root is the root of each MSTI. For example, as shown in Figure 23-5, Switch B is the MSTI regional root of the MSTI 1, and Switch D is the MSTI regional root of the MSTI 2.

CIST Root
The CIST root is the root switch of the CIST.

23.3 MSTP Application

In the case of the Ethernet user network where loops exist, the MSTP generates the tree topology according to VLAN IDs of the Ethernet packets. Thus, the broadcast storm is avoided and the network traffic is balanced according to the VLAN IDs of the Ethernet packets. At the client side, the PTN equipment supports the MSTP. At the network side, it does not support the MSTP, but it can transparently transmit the MST bridge protocol data unit (BPDU). There are three application scenarios of the MSTP.
l

When multiple ports of the PTN equipment are connected to the same user network, these ports should enable the MSTP protocol with the user network to avoid loops. These ports connected to the user network should be first divided into a port group, which equals a network bridge (switch) where the MSTP protocol is running. One CE equipment of the user is connected to two PTN NEs. Then, the channel switching is performed by using the MSTP protocol. In this way, the two PTN NEs only transparently transmit the BPDU packets, but they are not involved in the topology computation of the MSTP protocol.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

23-8

OptiX iManager T2000 Operation Guide for PTN NE Management

l

23 Configuring the MSTP

When the user network requires that the STP be enabled across networks of different carriers, the PTN equipment only transparently transmits the BPDU packets without the involvement of the MSTP computation.

23.4 Configuring a Port Group

When both the PTN equipment and the user network need run the MSTP, configure the ports as one port group. As a network bridge (switch), where the MSTP protocol is running, the port group is involved in calculation of the spanning tree of the user network.

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

Precautions
NOTE

l l

The sum of Ethernet ports enabled MSTP on one PTN equipment do not exceed one hundred. If an Ethernet port service is configured, this port can not be added to the port group.

Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Step 2 Click the Port Group Parameters tab. Click Create to display the Create Port Group dialog box. Step 3 Set Protocol Type and Enable Protocol for the port group as required. Step 4 Click Board and select the boards, to which the ports to be added to the port group belong, from the drop-down list. Step 5 Select the ports to be added to the port group from Available Port List. Click the ports to Selected Port List. to add

Step 6 When all ports to be added to the port group are added to Selected Port List, click OK. and the Operation Result dialog box is displayed, indicating that the operation is successful. Step 7 Click Close. The created port group is then listed in the port group list. ----End

23.5 Configuring Bridge Parameters

The bridge parameters include the bridge parameters and port parameters. The bridge parameters define the parameters of the port group as the MST bridge, and the port parameters define the role of each port in the MSTP protocol.

Prerequisite
l

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

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 23-9

Issue 01 (2009-06-30)

23 Configuring the MSTP

l

OptiX iManager T2000 Operation Guide for PTN NE Management

You must complete the creation of a port group.

Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Step 2 Click the Bridge Parameters tab, and select the port group. Configure MST Domain Name and Redaction Level. Click Apply. Step 3 If the mapping relation of the VLAN of the port group and MSTI need be modified, doubleclick Mapping List of the port group to display the Mapping List dialog box. In the Mapping List dialog box, set the mapping relation of the VLAN ID and MSTI ID. Then, click Apply.
NOTE

Two means are available for setting the mapping relation between the VLAN ID and MSTI ID.
l l

Click the Set Mapping List tab, and enter the VLAN ID in the text box behind the MSTI ID. By default, all VLAN IDs are mapped to MSTI 0. Click the Set Mapping Model tab, and enter the mapping module value (1-48) in the text box. Then, the equipment distributes VLAN IDs (1-4094) equally to the MSTI whose mapping module ranges from 1 to the mapping module value (1-16).

Two VLAN IDs (0, 4095) always map with MSTI 0.

Step 4 Select the port group and click the Bridge Parameters tab. Then, set MST Domain Max Hop Count, Network Diameter, Hello Time, Max Age and Forward Delay for the port group. Click Apply when the settings are completed. Step 5 Select the port group and click the Port Parameter tab. Then, set Enable Edge Attribute, Point-to-Point Attribute and Max Transmit Packet Count for each member port in the port group. Click Apply when the settings are completed. ----End

23.6 Configuring CIST and MSTI Parameters

Configure the bridge priority of the port group to specify the root of the spanning tree. Configure the MSTI port parameters to specify the MSTI priority and active/standby protection of the root bridges.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. You must complete the creation of a port group.

Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Step 2 Click the CIST&MSTI Parameters tab, and select the port group to be configured in Port Group.
23-10 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

23 Configuring the MSTP

Step 3 Each MSTI list of the port group is displayed in the upper pane. Double-click Bridge Priority for the MSTI to modify the bridge priority of the MSTI. Click Apply when the setting is completed. Step 4 Each member port list of the port group is displayed in the lower pane. Double-click Priority and Path Cost for Port to modify the port priority and path cost of the member port. Click Apply when the setting is completed. ----End

23.7 Querying the CIST Running Information

Query the CIST running information to know the operation status of the MSTP protocol on the port group.

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

Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Step 2 Click the CIST Running Information tab. The upper pane lists information on the bridge status of the port group, which works as a bridge where the MSTP is running. The lower pane lists information on the status of each port in the port group. ----End

23.8 Configuring Protocol Transfer for Ports

When a network has a switch where the STP protocol is running, the ports of the PTN equipment connected to the switch are automatically switched to the STP-compatible mode. When such a switch becomes absent in the network, these ports still work in the STP-compatible mode. In this case, manually configure the port to recover the running of the MSTP protocol on the port.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. You must complete the creation of a port group.

Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Step 2 Click the Port Group Parameters tab, and click the port group that contains the ports requiring protocol transfer in the upper pane. Step 3 Click the ports requiring protocol transfer in the lower pane. Click Protocol Transfer. ----End
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 23-11

23 Configuring the MSTP

OptiX iManager T2000 Operation Guide for PTN NE Management

23.9 Querying the MSTI Running Information

Query the MSTI running information to know the status of any MSTI in the port group.

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

Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Step 2 Click the MSTI Running Information tab. Step 3 Select the required port group for Port Group. The upper pane lists information on the status of each MSTI in the port group. Step 4 When you click one MSTI in the upper pane, the lower pane lists information on the status of each port of the MSTI. ----End

23.10 MSTP Configuration Case

A case is provided here to describe the MSTP networking scheme and method of configuring the MSTP. 23.10.1 Case Description The case description covers details such as the service networking, requirements and configuration data planning. 23.10.2 Configuration Flow This section describes the flow of configuring MSTP on the PE equipment.

23.10.1 Case Description

The case description covers details such as the service networking, requirements and configuration data planning.

Networking and Requirements

As shown in Figure 23-6, the PE is an OptiX PTN 3900 NE, and CE1 and CE2 are the Ethernet switches with the MSTP protocol.
l

The Ethernet interface, Eth1, of CE1 is connected to the first GE optical interface of the EG16 housed in slot 17 of the PE. The Ethernet interface, Eth1, of CE2 is connected to the first FE electrical interface of the ETFC housed in slot 35 of the PE. The Ethernet interface, Eth 2, of CE1 is connected to the Ethernet interface, Eth2, of CE2.

The requirements are as follows.

23-12 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

l l

23 Configuring the MSTP

The MSTP protocol should run on the PE and Layer 2 switches in the user network. The PE, CE1 and CE2 should be configured in the same MST domain, where PE is the root node. The VLAN 1 packets pass through the FE electrical interface between CE2 and the PE, and finally arrive at the PE. The other VLAN packets pass through the GE optical interface between CE1 and the PE, and finally arrive at the PE.

Figure 23-6 MSTP networking application

CE1 Eth1 Eth2 PE

Eth2 Eth1 CE2

CE1 PE

CE1 PE

CE2 VLAN 1 -> MSTI 1

CE2 Other VLAN -> MSTI 0

Service Planning
The engineering planning department should plan the engineering according to the related requirements, and output detailed planning information. Figure 23-6 is considered as an example to show the service planning. Table 23-1 shows how to plan the parameters for the MSTP configuration. Table 23-1 Parameters planned for the MSTP configuration Attribute Equipment MST Domain Name
Issue 01 (2009-06-30)

Value PE MST Region 01 CE1 MST Region 01 CE2 MST Region 01

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

23-13

23 Configuring the MSTP

OptiX iManager T2000 Operation Guide for PTN NE Management

Attribute Redaction Level VLAN Mapping List

Value 0 VLAN 1->MSTI 1 Other VLAN->MSTI 0 0 0 VLAN 1->MSTI 1 Other VLAN->MSTI 0 32768 0 VLAN 1->MSTI 1 Other VLAN->MSTI 0 32768

Bridge Priority for MSTI 0 Bridge Priority for MSTI 1 Path Cost for MSTI 0 Path Cost for MSTI 1

32768

32768

20000 (17-EG16-1) 20000 (35-ETFC-1) 20000 (17-EG16-1) 20000 (35-ETFC-1)

20000 (Eth1) 20000 (Eth2) 100000 (Eth1) 20000 (Eth2)

100000 (Eth1) 20000 (Eth2) 20000 (Eth1) 20000 (Eth2)

NOTE

To meet the service requirements in this case, configure the MSTP at the PE, CE1 and CE2. This manual only describes how to configure the MSTP on the PTN equipment. Configure the MSTP on CE1 and CE2 according to the requirements of the switches.

23.10.2 Configuration Flow

This section describes the flow of configuring MSTP on the PE equipment.

Prerequisite
You must understand the networking, requirements and service planning of the example.

Procedure
Step 1 On the T2000, create a port group for the PE equipment. For details, see 23.4 Configuring a Port Group. The port group contains two member ports.
l l

17-EG16-1(PORT 1) 35-ETFC-1(PORT 1)

Set Protocol Type and Enable Protocol for the port group as follows.
l l

Protocol Type: MSTP Enable Protocol: Enabled

Step 2 On the T2000, set the bridge parameters for PE equipment. For details, see 23.5 Configuring Bridge Parameters.
23-14 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

23 Configuring the MSTP

Set the parameters as follows.

l l l

MST Domain Name: MST Region 01 Redaction Level: 0 Mapping List: VLAN 1->MSTI 1, VLAN 0, 2-4095->MSTI 0

Step 3 On the T2000, set the MSTI 0 parameters for the port group of the PE equipment. For details, see 23.6 Configuring CIST and MSTI Parameters. Set the parameters as follows.
l l l

Bridge Priority: 0 Path Cost of 17-EG16-1(PORT 1): 20000 Path Cost of 35-ETFC-1(PORT 1): 20000

Step 4 On the T2000, set the MSTI 1 parameters for the port group of the PE equipment. For details, see 23.6 Configuring CIST and MSTI Parameters. Set the parameters as follows.
l l l

Bridge Priority: 0 Path Cost of 17-EG16-1(PORT 1): 20000 Path Cost of 35-ETFC-1(PORT 1): 20000

----End

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

23-15

OptiX iManager T2000 Operation Guide for PTN NE Management

24 Configuring Services for the Offload Solution

24

Configuring Services for the Offload Solution

About This Chapter

To provide high speed downlink packet access (HSDPA) services in a mobile communication network, the offload solution can be used to transmit data services through a xDSL wholesale managed service (WMS) network. In this way, the transmission cost is reduced. 24.1 Basic Concepts This section describes the three offload solutions, that is, ATM-based solution, ETH-based solution, and IP-based solution. In addition, this section covers the packet encapsulation format and signal flow. 24.2 Service Configuration Flow for the Offload Solution This section describes the operational tasks for configuring services in the offload scenario and the sequence in performing these tasks. When configuring or management services in the offload scenario, see this section. 24.3 ATM-Based Service Configuration Case This section describes the offload solution for the case where ATM-based services traverse the wholesale ADSL network. 24.4 ETH-Based Service Configuration Case This section describes the offload solution for the case where ETH-based services traverse the wholesale ADSL network. 24.5 IP-Based Service Configuration Case This section describes the offload solution for the case where IP-based services traverse the wholesale ADSL network.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

24-1

24 Configuring Services for the Offload Solution

OptiX iManager T2000 Operation Guide for PTN NE Management

24.1 Basic Concepts

This section describes the three offload solutions, that is, ATM-based solution, ETH-based solution, and IP-based solution. In addition, this section covers the packet encapsulation format and signal flow.

Offload Solution
In the mobile backhaul domain, there is one application scenario called offload. In the case of offload, the base station shunts the accessed service flow. The traditional audio service, such as the 2G or 3G R99 CS service, is transported over the E1 private line. In this way, high QoS, low delay, and high reliability are achieved. In the case of the packet service that requires high bandwidth but no delay guarantee, such as the high speed downlink packet access (HSDPA) service, the ADSL-based mode is adopted for backhaul. For example, the ADSL wholesale managed service (WMS) is applicable. The ADSL network provides high bandwidth and costs little. Hence, the ADSL network is well applicable to the packet service such as the HSDPA service. Generally, the PDH/SDH microwave is used or the TDM E1 private line is leased from the fixed network operator to transmit the backhaul service between the base station and base station controller (BSC). This is the reason why the Offload solution is adopted. With service development, the base station backhaul requires increasing bandwidth and the traditional audio service takes a decreasing proportion. In this case, it is not economical to lease more E1 links to increase the backhaul bandwidth, because the E1 links cost much. The offload solution is applicable to transmission of the ATM services, CES services, and Ethernet services. Figure 24-1 shows a typical scenario where the offload solution is applied. Node B connects to the OptiX PTN 1900 through the ATM IMA interface. The IMA E1 module of the OptiX PTN 1900 accesses the services and distinguishes various service flows according to the VPI/VCI values carried by the packets.
l

In the case of the HSDPA service flow, the OptiX PTN 1900 emulates the ATM PWE3 for the service flow on the access side and then encapsulates the emulated service into the tunnel as required by the WMS network. Finally, the OptiX PTN 1900 transports the service to the ADSL modem through the FE interface. When the encapsulated service enters the ADSL network, the service is transported to the OptiX PTN 3900. Then, the OptiX PTN 3900 decapsulates the service and transports the service to the radio network controller (RNC). The OptiX PTN 1900 at the access station transports the signaling flow and R99 service flow in the form of IMA E1 to the OptiX PTN 3900 at the convergence station.

24-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

24 Configuring Services for the Offload Solution

Figure 24-1 Offload solution

Wholesale ADSL service HSDPA flow IMA Node B OptiX PTN 1900 ADSL modem DSLAM ATM STM-1

R99 flow Backhaul network

OptiX PTN 3900

RNC

In the Wholesale ADSL network, packets are transported in three modes, that is, ATM-based forward, ETH-based forward, and IP-based forward.

ATM-Based Services for the Offload Solution

Figure 24-2 shows the offload scenario for the ATM-based service. Figure 24-2 Offload scenario for the ATM-based service
ATM E1 ATM PWE3 PW Label LSP Label Ethernet ATM PWE3 PW Label LSP Label Ethernet AAL5 ATM ADSL ATM PWE3 PW Label LSP Label Ethernet AAL5 ATM STM-1 ATM PWE3 PW Label LSP Label Ethernet AAL5 ATM STM-1 ATM STM-1

ATM based

Wholesale ADSL service HSDPA flow IMA Node B OptiX PTN 1900 ADSL modem DSLAM ATM STM-1

R99 flow PTN

OptiX PTN 3900

RNC

In the application scenario for ATM-based forward services, the WMS works as an ATM switch network. The OptiX PTN 1900 encapsulates the ATM packets into Ethernet packets. Then, the ADSL modem performs the AAL5 adaptation and ATM encapsulation. Finally, the DSLAM terminates the ADSL and transports the encapsulated ATM packets into the ATM switch
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 24-3

24 Configuring Services for the Offload Solution

OptiX iManager T2000 Operation Guide for PTN NE Management

network. The OptiX PTN 3900 terminates the AAL5 layer, recovers the Ethernet packets, and decapsulates the packets to obtain ATM packets.

ETH-Based Services for the Offload Solution

Figure 24-3 shows the offload scenario for the ETH-based forward service. Figure 24-3 Offload scenario for the ETH-based service
ATM E1 ATM PWE3 PW Label LSP Label Ethernet ATM PWE3 PW Label LSP Label Ethernet AAL5 ATM ADSL ATM PWE3 PW Label LSP Label Ethernet ATM PWE3 PW Label LSP Label Ethernet ATM STM-1

Eth based

Wholesale ADSL service HSDPA flow IMA Node B OptiX PTN 1900 ADSL modem DSLAM ATM STM-1

R99 flow PTN

OptiX PTN 3900

RNC

In the application scenario for ETH-based forward services, the WMS works as a Layer 2 ETH switch network. The OptiX PTN 1900 encapsulates the ATM packets into Ethernet packets. Then, the ADSL modem performs the AAL5 adaptation and ATM encapsulation. Finally, the DSLAM terminates the ADSL and ATM, and transports the encapsulated ATM packets into the Layer 2 ETH switch network. The OptiX PTN 3900 receives Ethernet packets and decapsulates the Ethernet packets to obtain ATM packets.

IP-Based Services for the Offload Solution

Figure 24-4 shows the offload scenario for the IP-based forward service.

24-4

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

24 Configuring Services for the Offload Solution

Figure 24-4 Offload scenario for the IP-Based services

ATM E1 ATM PWE3 PW Label GRE IP Ethernet ATM PWE3 PW Label GRE IP Ethernet AAL5 ATM ADSL ATM PWE3 PW Label GRE IP Ethernet ATM PWE3 PW Label GRE IP Ethernet ATM STM-1

IP based

Wholesale ADSL service HSDPA flow IMA Node B OptiX PTN 1900 ADSL modem DSLAM ATM STM-1

R99 flow PTN

OptiX PTN 3900

RNC

In the application scenario for IP-based forward services, the WMS works as an IP switch network. The OptiX PTN 1900 encapsulates the ATM packets into Ethernet packets. Then, the ADSL modem performs the AAL5 adaptation and ATM encapsulation. Finally, the DSLAM terminates the ADSL and ATM, and forwards (Layer 3) the packets to the OptiX PTN 3900. The OptiX PTN 3900 receives Ethernet packets and decapsulates the Ethernet packets to obtain ATM packets. In this scenario, an IP/GRE tunnel should be set up between the OptiX PTN 1900 and OptiX PTN 3900 to carry the PW. In this figure, IP in the packet encapsulation format indicates that the packets are carried by the IP tunnel. In the case of PW carrying over the GRE tunnel, IP is replaced with GRE.

24.2 Service Configuration Flow for the Offload Solution

This section describes the operational tasks for configuring services in the offload scenario and the sequence in performing these tasks. When configuring or management services in the offload scenario, see this section. Figure 24-5, Figure 24-6, Figure 24-7 show the configuration flow of services in the offload solution. For details of each step, see the related section.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

24-5

24 Configuring Services for the Offload Solution

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 24-5 Configuration flow of the ATM-based service in the offload solution

Required Start Optional Creat the network

Configure the interface

Creat the IMA group

Configure the control plane Create MPLS/IP/GRE tunnel Create the ATM policy Create the ATM service Create the ATM connection End

24-6

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

24 Configuring Services for the Offload Solution

Figure 24-6 Configuration flow of the ETH-based service in the offload solution

Required Start Optional Creat the network

Configure the interface Configure the control plane Create MPLS/IP/ GRE tunnel Configure the QoS policy

Create the service

End

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

24-7

24 Configuring Services for the Offload Solution

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 24-7 Configuration flow of the IP-based service in the offload solution

Required Optional

Start

Creat the network

Configure the interface Create the static route Create the static ARP table entry Create IP/GRE tunnel Configure the QoS policy

Create the service

End

24.3 ATM-Based Service Configuration Case

This section describes the offload solution for the case where ATM-based services traverse the wholesale ADSL network. 24.3.1 Case Description This section describes the offload solution to the wholesale ADSL network, which is forwarded according to the ATM. 24.3.2 Configuration Process This section describes the configuration process of the Offload application in an ATMforwarding-based network.

24-8

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

24 Configuring Services for the Offload Solution

24.3.1 Case Description

This section describes the offload solution to the wholesale ADSL network, which is forwarded according to the ATM.

Networking and Requirement

Two Node Bs are accessed through two IMA groups of the OptiX PTN 1900, and the two Node Bs communicate with the RNC connected to the OptiX PTN 3900 at the opposite end through the network. Services of Node B include the R99 voice service and high speed downlink packet access (HSDPA) service. The voice service, which is carried by the backhaul network constructed by the OptiX PTN equipment, requires QoS guarantee, low delay and bandwidth guarantee. The HSDPA service does not require low delay, but it only requires bandwidth guarantee. Hence, the ATM network of a third party operator is leased. The OptiX PTN 1900 differentiates services according to the VPI and VCI values, and then distributes the services to two different routes for transmission.
l

HSDPA service: The HSDPA service is converged to the DSLAM equipment through the ADSL modem, and then it enters the leased ATM network of the third party operator for transmission. The HSDPA service requires only bandwidth guarantee, and thus the lease cost is low. R99 voice service: The R99 voice service is transported through the backhaul network. The equipment in the network is the OptiX PTN equipment series. The R99 voice service requires QoS guarantee, low delay and bandwidth guarantee.

Figure 24-8 shows the networking diagram.

l

HSDPA service: On the OptiX PTN 1900, perform the VPI/VCI switching on the service with a VPI/VCI value of 1/101, and then transport the service to the FE interface of the ETFC. After added with a new VPI/VCI through the ADSL modem, the service is transported to the OptiX PTN 3900 through the ATM network. The OptiX PTN 3900 rearranges the service and then converges the service to the ATM STM-1 interface. Then, the service is transported to RNC. MPLS Tunnel 1 is set up between the OptiX PTN 1900 and OptiX PTN 3900 for carrying the service. Figure 24-8 shows the encapsulation format of packets at the interface of each equipment. The red lines indicate the VPI/VCI values at ATM layers in the packets. R99 voice service: On the OptiX PTN 1900, perform the VPI/VCI switching on the service with a VPI/VCI value of 1/100, and then transport the service to the POS interface of the POD41. The service is carried by MPLS Tunnel 2, and then is transported to the OptiX PTN 3900. The OptiX PTN 3900 rearranges the service and then converges the service to the ATM STM-1 interface. Then, the service is transported to RNC.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

24-9

24 Configuring Services for the Offload Solution

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 24-8 Networking diagram of the offload application scenario based on the ATM forwarding and packet encapsulation format
ATM E1 ATM PWE3 PW Label LSP Label Ethernet ATM PWE3 PW Label LSP Label Ethernet AAL5 ATM ADSL ATM PWE3 PW Label LSP Label Ethernet AAL5 ATM STM-1 ATM PWE3 PW Label LSP Label Ethernet AAL5 ATM STM-1 3-MP1-ASD1-1 4-MP1-AD1-1
20/40 1/100 1/101 46/80 46/81

ATM STM-1

CXP-1-MD1-3-L75:1-4

7-ETFC-1

Node B 1
1/100 1/101

ADSL modem HSDPA flow R99 flow

56/80 56/81

DSLAM

Wholesale ADSL service

20/40 46/80 46/81 56/80 56/81

56/80 56/81

ATM STM-1

RNC

Node B 2 4-POD41-1 CXP-1-MD1-3-L75:5-8

PTN 1-EG16-19-POD41-1

MPLS Tunnel 1 MPLS Tunnel 2 OptiX PTN 1900 OptiX PTN 3900

The ADSL modem can work in the bridge or router mode.

l

When the ADSL modem works in the bridge mode, the ADSL modem performs the EoA encapsulation on the accessed FE signals. The access node uses the MPLS tunnel or IP tunnel. When the ADSL modem works in the router mode, the ADSL modem performs the IPoA encapsulation on the accessed FE signals. The access node uses the IP tunnel or GRE tunnel.

In this example, the OptiX PTN 1900 uses the MPLS tunnel, and the ADSL modem works in the bridge mode. If the ADSL modem works in the router mode, the configuration method is the same. The difference is that the IP tunnel or GRE tunnel, instead of the MPLS tunnel, is used to carry the HSDPA service.
NOTE

The ASD1 supports four AAL5 encapsulation types, that is, LLC bridge, LLC route, VCMUX bridge and VCMUX route. In the actual application, the encapsulation type should be consistent with the working mode of the ADSL Modem.

Service Planning
The offload is a solution instead of a service or feature. Hence, according to the user requirement and networking diagram of this example, this example uses the offload solution to perform the following tasks.
24-10 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

24 Configuring Services for the Offload Solution

1.

Configure the member interfaces and create the IMA group. On the OptiX PTN 1900, create two IMA groups for accessing the IMA services of two Node Bs.

2.

Create the Ethernet virtual interface. On the OptiX PTN 3900, set the interface of the ASD1 to the Ethernet virtual interface, set the port mode to Layer 3. In addition, the setting of the AAL5 encapsulation type should be consistent with the working mode of the ADSL modem. After the Ethernet virtual interface is created, the ATM interface of the ASD1 can be carried in the tunnel on the network side.

3.

Create MPLS tunnel 1. This tunnel is used for carrying the HSDPA service. Normally, the static MPLS tunnel is created on the OptiX PTN 1900 and OptiX PTN 3900, because the network is a leased network of the third party operator.

4.

Create MPLS tunnel 2. This tunnel is used for carrying the R99 voice service, which resides on the POS interfaces of the OptiX PTN 1900 and OptiX PTN 3900.

5.

Create the ATM policy (CBR and UBR). Create the ATM policy before creating the ATM service. On the OptiX PTN 1900 and OptiX PTN 3900, create two ATM policies respectively. CBR is used for the R99 voice service, and UBR is used for the HSDPA service.

6.

Create the ATM service.

l l

On the OptiX PTN 1900, create two ATM services, and access the services of Node B. On the OptiX PTN 3900, create two ATM services, and access the services of RNC. On the OptiX PTN 1900, create two ATM connections in each ATM service, and encapsulate the services to different PWs according to the VPI/VCI value, and select different MPLS tunnels for carrying the services. On the OptiX PTN 3900, create two ATM connections in each ATM service, and encapsulate the services to different PWs according to the VPI/VCI value, and select different MPLS tunnels for carrying the services.

7.

Create the ATM connection.

l

NOTE

In the leased network of the third party operator, the services are configured by the third party operator.

The parameter planning is as follows: Table 24-1 lists the planning of the voice service and data service in the network.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

24-11

24 Configuring Services for the Offload Solution

OptiX iManager T2000 Operation Guide for PTN NE Management

Table 24-1 VPI/VCI values of the Node B service Service Service Bandwidt h User-Side VPI/VCI Value NetworkSide VPI/ VCI Value VPI/VCI Value Added at the ATM Layer After the AAL5 Adaptatio n 20/40 20/40 VPI/VCI Value on the RNC Side

R99 voice service of Node B 1 HSDPA service of Node B 1 R99 voice service of Node B 2 HSDPA service of Node B 2

2 Mbit/s 5 Mbit/s 2 Mbit/s 5 Mbit/s

1/100 1/101 1/100 1/101

56/80 46/80 56/81 46/81

56/80 46/80 56/81 46/81

Table 24-2 lists the planning of the UNIs. The OptiX PTN 1900 needs to create two IMA groups to access two Node B services. The OptiX PTN 3900 needs to interconnect 4-MP1-AD1-1 to RNC. Table 24-2 Planning of the UNIs Equipment Interface OptiX PTN 1900:1-MD1-1 (Trunk-1) OptiX PTN 1900:1-MD1-2 (Trunk-2) OptiX PTN 3900:4-MP1AD1-1 Binding Interface 3-L75-1 to 3-L75-4 Interface Attribute The port mode of the PDH interface is set to Layer 2, and the encapsulation type is ATM by default. The port mode of the PDH interface is set to Layer 2, and the encapsulation type is ATM by default. The port mode of the SDH interface is set to Layer 2, and the encapsulation type is ATM by default.

3-L75-5 to 3-L75-8

Table 24-3 lists the planning of the NNIs.

24-12

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

24 Configuring Services for the Offload Solution

Table 24-3 Planning of the NNIs Equipment Interface Interface Type Port Mode IP Address and Subnet Mask of the Interface 192.168.1.5/30 192.168.1.6/30 VPI/VCI Value (Only for the EOA Virtual Interface) 20/40

OptiX PTN 1900:7-ETFC-1 OptiX PTN 3900:3-MP1ASD1-1 OptiX PTN 1900:4POD41-1

Ethernet interface EOA virtual interface SDH interface

Layer 3 Layer 3

Layer 3

192.168.2.5/30 (In the backhaul network, the IP address and mask of the interface of the OptiX PTN equipment interconnected to this SDH interface is 192.168.2.6/30. ) 192.168.10.6/30 (In the backhaul network, the IP address and mask of the interface of the OptiX PTN equipment interconnected to this SDH interface is 192.168.10.5/30 .)

OptiX PTN 3900:19POD41-1

SDH interface

Layer 3

NOTE

ADSL The modem performs the AAL5 adaptation on the accessed services, and then adds a VPI/VCI to the services. The VPI/VCI value for the Ethernet EOA virtual interface should be consistent with the preceding VPI/VCI value.

Table 24-4 and Table 24-5 list the planning of the MPLS tunnel and related PW.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

24-13

24 Configuring Services for the Offload Solution

OptiX iManager T2000 Operation Guide for PTN NE Management

Table 24-4 Planning of the MPLS tunnel MPLS Tunnel MPLS Tunnel ID Interface of the Tunnel Carried by the OptiX PTN 1900 7-ETFC Interface of the Tunnel Carried by the OptiX PTN 3900 Ethernet virtual interface: 3MP1ASD1-1 19-POD41-1 MPLS Tunnel Type Tunnel Bandwidth

MPLS Tunnel 1

Forward: 50 Reverse: 51

Static

No restriction

MPLS Tunnel 2

Dynamic distribution

4-POD41-1

Dynamic

No restriction

NOTE

If the type of the MPLS tunnel 1 is static, manually specify the IP address of the next hop and the IP addresses of the source and sink nodes. If the type of the MPLS tunnel 2 is dynamic, manually specify the restriction condition. Hence, the tunnel passes through the specified interfaces.

Table 24-5 Planning of the PW P W PW Signali ng Type PW Type PW Labe l Opposite IP Address Max. Conca tenate d Cell Count Packe tisatio n Buffer ing Time (us) 1000 QoS Policy of the ATM Connection

P W 1

Static

ATM n to one VCC cell transpor t ATM n to one VCC cell transpor t

100

OptiX PTN 1900:192.1 68.1.6 OptiX PTN 3900:192.1 68.1.5

10

Service Type: UBR Traffic Type: NoTrafficDescriptor

P W 2

Dynami c

Dyna mic distri butio n

OptiX PTN 1900:192.1 68.10.6 OptiX PTN 3900:192.1 68.2.5

Service Type: CBR. Traffic Type: NoClpNoScr Clp01Pcr(cell/s): 10000

Table 24-6 and Table 24-7 list the planning of the ATM services on the OptiX PTN 1900 and OptiX PTN 3900.
24-14 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

24 Configuring Services for the Offload Solution

Table 24-6 Planning of the ATM service on the OptiX PTN 1900 Attribute Node B of the Service Source Port ATM Connection (Two ATM Connections for Each ATM Service) Source VPI/ VCI Sink VPI/VCI PW Carrying the Service Tunnel Carrying the PW Uplink Policy Downlink Policy ATM Service 1 Node B 1 1-MD1-1 (Trunk-1) HSDPA 1 Node B 2 1-MD1-2 (Trunk-2) HSDPA 2 ATM Service 2 Node B 1 1-MD1-1 (Trunk-1) R99 1 Node B 2 1-MD1-2 (Trunk-2) R99 2

1/101 46/80 PW1 MPLS Tunnel 1

1/101 46/81 PW1 MPLS Tunnel 1

1/100 56/80 PW2 MPLS Tunnel 2

1/100 56/81 PW2 MPLS Tunnel 2

UBR UBR

UBR UBR

CBR CBR

CBR CBR

Table 24-7 Planning of the ATM service on the OptiX PTN 3900 Attribute Source Port ATM Connection (Two ATM Connections for Each ATM Service) Source VPI/ VCI Sink VPI/VCI PW Carrying the Service ATM Service 1 4-MP1-AD1-1 HSDPA 1 HSDPA 2 R99 1 R99 2 ATM Service 2

46/80 46/80 PW1

46/81 46/81 PW1

56/80 56/80 PW2

56/81 56/81 PW2

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

24-15

24 Configuring Services for the Offload Solution

OptiX iManager T2000 Operation Guide for PTN NE Management

Attribute Tunnel Carrying the PW Uplink Policy Downlink Policy

ATM Service 1 MPLS Tunnel 1 MPLS Tunnel 1

ATM Service 2 MPLS Tunnel 2 MPLS Tunnel 2

UBR UBR

UBR UBR

CBR CBR

CBR CBR

24.3.2 Configuration Process

This section describes the configuration process of the Offload application in an ATMforwarding-based network.

Prerequisite
l l l

You must be an NM user with "NE operator" authority or higher. You must know the networking and data planning of this case. Because the Offload solution involves configuration of many operation tasks, you are supposed to learn how to configure interfaces and tunnels, how to create the QoS policy, and how to configure ATM services before the configuration.

Procedure
Step 1 In the NE Explorer, select OptiX PTN 1900. Choose Configuration > Interface Management > PDH Interface. Set Port Mode to Layer 2 and Encapsulation Type to ATM for eight interfaces ranging from 3-L75-1 to 3-L75-8. Step 2 Choose Configuration > Interface Management > ATM IMA Management , and click the Binding tab. Bind interfaces ranging from 3-L75-1 to 3-L75-4 and interfaces ranging from 3L75-5 to 3-L75-8 to Trunk 1 and Trunk 2 respectively. Step 3 Choose IMA Group Management. Then, set IMA Protocol Enable Status to Enabled for 1CXP-1-MD1-1(Trunk-1) and 1-CXP-1-MD1-2(Trunk-2). Step 4 In the NE Explorer, select OptiX PTN 3900. Choose Configuration > Interface Management > Ethernet Virtual Interface. Click New, set 3-MP1-ASD1-1 to EOA Virtual Interface in the Create Ethernet Virtual Interface dialog box. Then, set the parameters as follows:
l

Basic attributes

Set Port Mode to Layer 3. Set AAL5 Encapsulation Type to LLC BRIDGE. Set VPI to 20. Set VCI to 40. Set IP Address to 192.168.1.6.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

Layer 3 attributes

24-16

OptiX iManager T2000 Operation Guide for PTN NE Management

24 Configuring Services for the Offload Solution

Set IP Mask to 255.255.255.252. Set Enable Tunnel to Enabled.

NOTE

The AAL5 encapsulation type should be consistent with the working mode of the ADSL modem.

Step 5 Choose Configuration > Interface Management > SDH Interface . Set 19-POD41-1 as an network-side interface. Then, set the parameters as follows:
l

Basic attributes

Set Encapsulation Type to PPP. Use the default values for other parameters. Set Enable Tunnel to Enabled. Set Specify IP to Manually. Set IP Address to 192.168.10.6. Set IP Mask to 255.255.255.252.

Layer 3 attributes

Step 6 In the NE Explorer, select OptiX PTN 1900. Choose Configuration > Interface Management > Ethernet Interface. Set 7-ETFC-1 as an network-side interface. Then, set the parameters as follows:
l

Basic attributes

Set Port Mode to Layer 3. Use the default values for other parameters.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 24-17

Issue 01 (2009-06-30)

24 Configuring Services for the Offload Solution

l

OptiX iManager T2000 Operation Guide for PTN NE Management

Layer 3 attributes

Set Enable Tunnel to Enabled. Set Specify IP to Manually. Set IP Address to 192.168.1.5. Set IP Mask to 255.255.255.252.

Step 7 Choose Configuration > Interface Management > SDH Interface . Set 4-POD41-1 as an network-side interface. Then, set the parameters as follows:
l

Basic attributes

Set Encapsulation Type to PPP. Use the default values for other parameters. Set Enable Tunnel to Enabled. Set Specify IP to Manually. Set IP Address to 192.168.1.6. Set IP Mask to 255.255.255.252.

Layer 3 attributes

Step 8 Create MPLS tunnel 1 between the OptiX PTN 1900 and the OptiX PTN 3900. Because the type of the tunnel is Static, you need to create a static MPLS tunnel on the OptiX PTN 1900 and OptiX PTN 3900 respectively. For the method of creating the tunnel in this case, see 13.4.2 Creating an MPLS Tunnel on a Per-NE Basis. Step 9 Create MPLS tunnel 2 between the OptiX PTN 1900 and OptiX PTN 3900. You can dynamically create the MPLS tunnel because tunnel 2 passes the PTN equipment. Set attributes of each interface of the NEs involved properly before the creation. For the method of the tunnel in this case, see 13.3.1 Creating a Dynamic MPLS Tunnel and the FRR Protection by Using the Trail Function. Step 10 Create two ATM policies on the OptiX PTN 1900 and OptiX PTN 3900 respectively. In the NE Explorer, choose Configuration > QoS Management > Policy Management. Then, select ATM Policy and click New.
l l

The ATM policies on the OptiX PTN 1900 and the OptiX PTN 3900 should be consistent. In the case of the CBR policy, set the parameters as follows:

Set Service Type to CBR. Set Traffic Type to NoClpNoScr. Set Clp01Pcr(cell/s) to 10000. Set Service Type to UBR. Set Traffic Type to NoTrafficDescriptor.

In the case of the UBR policy, set the parameters as follows:

Step 11 Create ATM service 1 on the OptiX PTN 1900. Create two ATM connections in ATM service 1. Change the VPI/VCI values of the two services accessed by the two IMA groups from 1/101 to respectively 46/80 and 46/81, encapsulate the services, and then send the services to MPLS tunnel 1 carried by the 7-ETFC-1 interface. In the NE Explorer, choose Configuration > ATM Service Management. Click the Connection tab, and click New. Set the parameters as follows:
l

Set Service Type to UNIs-NNI.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

24-18

OptiX iManager T2000 Operation Guide for PTN NE Management

l l

24 Configuring Services for the Offload Solution

Set Connection Type to PVC. Set the parameters for connection 1 as follows:

Set Source Board to 1-CXP. Set Source Port to 1-MD1-1(Trunk-1). Set Source VPI to 1. Set Source VCI to 101. Set Sink VPI to 46. Set Sink VCI to 80. Set Uplink Policy and Downlink Policy to the created UBR policy. Set Source Board to 1-CXP. Set Source Port to 1-MD1-2(Trunk-2). Set Source VPI to 1. Set Source VCI to 101. Set Sink VPI to 46. Set Sink VCI to 81. Set Uplink Policy and Downlink Policy to the created UBR policy.

Set the parameters for connection 2 as follows:

Setting the parameters of PW1 as follows: General Attributes:

Set PW ID to 1. Set PW Signaling Type to Static. Set PW Type to ATM n-to-one VCC cell transport. Set PW Ingress Label and PW Egress Label to 100. Set Peer IP to 192.168.1.6. Set Tunnel Type to MPLS. Set Tunnel to created MPLS Tunnel 1. Set Max. Concatenated Cell Count to 10. Set Packet Loading Time(us) to 1000. Ingress

QoS

Bandwidth Limit: Enabled CIR (kbit/s): 10240 CBS (byte): PIR (kbit/s): 15000 PBS (byte): Policy: EXP: 1

Advanced Attributes:

Control Word: Must use

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 24-19

Issue 01 (2009-06-30)

24 Configuring Services for the Offload Solution

OptiX iManager T2000 Operation Guide for PTN NE Management

Control Channel Type: CW (CW realizes connectivity check of the PW.) VCCV Verification Mode: Ping ( PW Ping realizes connectivity check of the PW.) Max. Concatenated Cell Count: 10 (the maximum number of ATM cells that can be encapsulated in each packet) Packet Loading Time (us): 1000

NOTE

PW advanced attributes such as Control Word, Control Channel Type and VCCV Verification Mode need be set according to the user requirements. For detailed configuration steps, refer to 19.5.1 Creating ATM Services on a Per-NE Basis.

Step 12 Create ATM service 2 on the OptiX PTN 1900. Create two ATM connections in ATM service 2. Change the VPI/VCI values of the two services accessed by the two IMA groups from 1/100 to respectively 56/80 and 56/81, encapsulate the services, and then send the services to MPLS tunnel 2 carried by the 4-POD41-1 interface. For the configuration parameters, see the service planning in the case description. Set the parameters according to Step 11. In the case of PW2, PW Signaling Type should be set to Dynamic. In addition, PW Ingress Label and PW Egress Label need not be set. Step 13 Create ATM service 1 on the OptiX PTN 3900. Create two ATM connections in ATM service 1. The VPI/VCI exchange need not be performed. Send the services whose VPI/VCI values are respectively 46/80 and 46/81 and accessed by the 4-MP1-AD1-1 interface to MPLS tunnel 1 carried by the Ethernet virtual interface on the network side. For the configuration parameters, see the service planning in the case description. Set the parameters according to Step 11. Step 14 Create ATM service 2 on the OptiX PTN 3900. Create two ATM connections in ATM service 2. The VPI/VCI exchange need not be performed. Send the services whose VPI/VCI values are respectively 56/80 and 56/81 and accessed by the 4-MP1-AD1-1 interface to MPLS tunnel 2 carried by the POS interface on the network side. For the configuration parameters, see the service planning in the case description. Set the parameters according to Step 11.In the case of PW2, PW Signaling Type should be set to Dynamic. In addition, PW Ingress Label and PW Egress Label need not be set. ----End

24.4 ETH-Based Service Configuration Case

This section describes the offload solution for the case where ETH-based services traverse the wholesale ADSL network. 24.4.1 Case Description This section describes the offload solution to the wholesale ADSL network, which is forwarded according to the ETH. 24.4.2 Configuration Process This section describes the configuration process of the Offload application in an ETHforwarding-based network.

24-20

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

24 Configuring Services for the Offload Solution

24.4.1 Case Description

This section describes the offload solution to the wholesale ADSL network, which is forwarded according to the ETH.

Networking and Requirement

Two Node Bs are accessed through two IMA groups of the OptiX PTN 1900, and the two Node Bs communicate with the RNC connected to the OptiX PTN 3900 at the opposite end through the network. Services of Node B include the R99 voice service and high speed downlink packet access (HSDPA) service. The voice service, which is carried by the backhaul network constructed by the OptiX PTN equipment, requires QoS guarantee, low delay and bandwidth guarantee. The HSDPA service does not require low delay, but it only requires bandwidth guarantee. Hence, the Layer 2 switching network of a third party operator is leased. The OptiX PTN 1900 differentiates services according to the VPI and VCI values, and then distributes the services to two different routes for transmission.
l

HSDPA service: The HSDPA service is converged to the DSLAM equipment through the ADSL modem, and then it enters the leased ETH network of the third party operator for transmission. The HSDPA service requires only bandwidth guarantee, and thus the lease cost is low. R99 voice service: The R99 voice service is transported through the backhaul network. The equipment in the network is the OptiX PTN equipment series. The R99 voice service requires QoS guarantee, low delay and bandwidth guarantee.

Figure 24-9 shows the networking diagram.

l

HSDPA service: On the OptiX PTN 1900, perform the VPI/VCI switching on the service with a VPI/VCI value of 1/101, and then transport the service to the FE interface of the ETFC. The ADSL modem completes the AAL5 adaptation and ATM encapsulation, and the DSLAM removes the ADSL and ATM layers. Then, the Ethernet packets are sent to the ETH switching network. The ETH switching network sends the service to the OptiX PTN 3900. The OptiX PTN 3900 rearranges the service and then converges the service to the ATM STM-1 interface. Then, the service is transported to RNC. MPLS Tunnel 1 is set up between the OptiX PTN 1900 and OptiX PTN 3900 for carrying the service. Figure 24-9 shows the encapsulation format of packets at the interface of each equipment. The red lines indicate the VPI/VCI values at ATM layers in the packets. R99 voice service: On the OptiX PTN 1900, perform the VPI/VCI switching on the service with a VPI/VCI value of 1/100, and then transport the service to the POS interface of the POD41. The service is carried by MPLS Tunnel 2, and then is transported to the OptiX PTN 3900. The OptiX PTN 3900 rearranges the service and then converges the service to the ATM STM-1 interface. Then, the service is transported to RNC.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

24-21

24 Configuring Services for the Offload Solution

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 24-9 Networking diagram of the offload application scenario based on the ETH forwarding and packet encapsulation format
ATM E1 ATM PWE3 PW Label LSP Label Ethernet ATM PWE3 PW Label LSP Label Ethernet AAL5 ATM ADSL ATM PWE3 PW Label LSP Label Ethernet ATM PWE3 PW Label LSP Label Ethernet ATM STM-1

CXP-1-MD1-3-L75:1-4

7-ETFC-1

1-EG16-1
20/30

4-MP1-AD1-1

1/100 1/101

46/80 46/81

Node B 1
1/100 1/101

ADSL modem HSDPA flow R99 flow

56/80 56/81

DSLAM

Wholesale ADSL service

46/80 46/81 56/80 56/81 56/80 56/81

ATM STM-1

RNC

Node B 2 4-POD41-1 CXP-1-MD1-3-L75:5-8

PTN 1-EG16-19-POD41-1

MPLS Tunnel 1 MPLS Tunnel 2 OptiX PTN 1900 OptiX PTN 3900

The ADSL modem can work in the bridge or router mode.

l

When the ADSL modem works in the bridge mode, the ADSL modem performs the EoA encapsulation on the accessed FE signals. The OptiX PTN 1900 on the access node uses the MPLS Tunnel or IP Tunnel. When the ADSL modem works in the router mode, the ADSL modem performs the IPoA encapsulation on the accessed FE signals. The OptiX PTN 1900 at the access node uses the IP Tunnel or GRE Tunnel.

In this example, the OptiX PTN 1900 uses the MPLS Tunnel, and the ADSL modem works in the bridge mode. If the ADSL modem works in the router mode, the configuration method is the same. The difference is that the IP Tunnel or GRE Tunnel, instead of the MPLS Tunnel, is used to carry the HSDPA service. When the IP Tunnel or GRE Tunnel is used, you should configure the static route and static ARP on the OptiX PTN 1900 and OptiX PTN 3900. If the equipment cannot dynamically obtain the ARP, the static ARP still needs to be configured.

Service Planning
The offload is a solution instead of a service or feature. Hence, according to the user requirement and networking diagram of this example, this example uses the offload solution to perform the following tasks.
24-22 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

24 Configuring Services for the Offload Solution

1.

Create the IMA group and configure the member interfaces. On the OptiX PTN 1900, create two IMA groups for accessing the IMA services of two Node Bs.

2.

Configure attributes of the NNI. After the NNI is configured, you can create the MPLS Tunnel on the OptiX PTN 1900 and OptiX PTN 3900.

3.

Configure the control plane.

l

Before creating a dynamic tunnel, configure the IS-IS protocol and set the parameters related to the RSPF protocol. To create a dynamic tunnel, you need to configure a static ARP. After the static ARP is configured, the equipment finds the corresponding MAC address in the ARP table entry according to the destination IP address, and then writes the MAC address as the destination MAC to the ETH layer of the packet. The Layer 2 switching network forwards the packet to the destination according to this MAC address. Static MPLS Tunnel 1 should use this table entry.

4.

Create MPLS tunnel 1. This tunnel is used for carrying the HSDPA service. Normally, the static MPLS tunnel is created on the OptiX PTN 1900 and OptiX PTN 3900, because the network is a leased network of the third party operator.

5.

Create MPLS Tunnel 2. This tunnel is used for carrying the R99 voice service, which resides on the POS interfaces of the OptiX PTN 1900 and OptiX PTN 3900.

6.

Create the QoS policy (CBR and UBR). Create the ATM policy before creating the ATM service. On the OptiX PTN 1900 and OptiX PTN 3900, create two ATM policies respectively. CBR is used for the R99 voice service, and UBR is used for the HSDPA service.

7.

Create the ATM service.

l l

On the OptiX PTN 1900, create two ATM services, and access the services of Node B. On the OptiX PTN 3900, create two ATM services, and access the services of RNC. On the OptiX PTN 1900, create two ATM connections in each ATM service, and encapsulate the services to different PWs according to the VPI/VCI value, and select different MPLS Tunnels for carrying the services. On the OptiX PTN 3900, create two ATM connections in each ATM service, and encapsulate the services to different PWs according to the VPI/VCI value, and select different MPLS Tunnels for carrying the services.

8.

Create the ATM connection.

l

NOTE

In the leased network of the third party operator, the services are configured by the third party operator.

The parameter planning is as follows: Table 24-8 lists the planning of the voice service and data service in the network.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

24-23

24 Configuring Services for the Offload Solution

OptiX iManager T2000 Operation Guide for PTN NE Management

Table 24-8 VPI/VCI values of the Node B service Service Service Bandwidt h User-Side VPI/VCI Value NetworkSide VPI/ VCI Value VPI/VCI Value Added at the ATM Layer After the AAL5 Adaptatio n 20/30 20/30 VPI/VCI Value on the RNC Side

R99 voice service of Node B 1 HSDPA service of Node B 1 R99 voice service of Node B 2 HSDPA service of Node B 2

2 Mbit/s 5 Mbit/s 2 Mbit/s 5 Mbit/s

1/100 1/101 1/100 1/101

56/80 46/80 56/81 46/81

56/80 46/80 56/81 46/81

Table 24-9 lists the planning of the UNIs. The OptiX PTN 1900 needs to create two IMA groups to access two Node B services. The OptiX PTN 3900 needs to interconnect 4-MP1-AD1-1 to RNC. Table 24-9 Planning of the UNIs Equipment Interface OptiX PTN 1900:1-MD1-1 (Trunk-1) OptiX PTN 1900:1-MD1-2 (Trunk-2) OptiX PTN 3900:4-MP1AD1-1 Binding Interface 3-L75-1 to 3-L75-4 Interface Attribute The port mode of the PDH interface is set to Layer 2, and the encapsulation type is ATM by default. The port mode of the PDH interface is set to Layer 2, and the encapsulation type is ATM by default. The port mode of the SDH interface is set to Layer 2, and the encapsulation type is ATM by default.

3-L75-5 to 3-L75-8

Table 24-10 lists the planning of the NNIs.

24-24

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

24 Configuring Services for the Offload Solution

Table 24-10 Planning of the NNIs Equipment Interface Interface Type Port Mode IP Address and Subnet Mask of the Interface 192.168.1.5/30 MAC Address of the Interface 00-00-00-00-00 -01 (for creating the static ARP) 00-00-00-00-00 -02 (for creating the static ARP) -

OptiX PTN 1900:7-ETFC-1 OptiX PTN 3900:1-EG16-1 OptiX PTN 1900:4POD41-1

Ethernet interface Ethernet interface SDH interface

Layer 3

Layer 3

192.168.1.6/30

Layer 3

192.168.2.5/30 (In the backhaul network, the IP address and mask of the interface of the OptiX PTN equipment interconnected to this SDH interface is 192.168.2.6/30. ) 192.168.10.6/30 (In the backhaul network, the IP address and mask of the interface of the OptiX PTN equipment interconnected to this SDH interface is 192.168.10.5/30 .)

OptiX PTN 3900:19POD41-1

SDH interface

Layer 3

Table 24-11 and Table 24-12 list the planning of the MPLS Tunnel and related PW.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

24-25

24 Configuring Services for the Offload Solution

OptiX iManager T2000 Operation Guide for PTN NE Management

Table 24-11 Planning of the MPLS Tunnel MPLS Tunnel MPLS Tunnel ID Interface of the Tunnel Carried by the OptiX PTN 1900 7-ETFC Interface of the Tunnel Carried by the OptiX PTN 3900 1-EG16-1 MPLS Tunnel Type Tunnel Bandwidth

MPLS Tunnel 1 MPLS Tunnel 2

Forward: 50 Reverse: 51 Dynamic distribution

Static

No restriction No restriction

4-POD41-1

19-POD41-1

Dynamic

NOTE

If the type of the MPLS Tunnel 1 is static, manually specify the IP address of the next hop and the IP addresses of the source and sink nodes. If the type of the MPLS Tunnel 2 is dynamic, manually specify the restriction condition. Hence, the tunnel passes through the specified interfaces.

Table 24-12 Planning of the PW P W PW Signali ng Type PW Type PW Labe l Opposite IP Address Max. Conca tenate d Cell Count Packe tisatio n Buffer ing Time (us) 1000 QoS Policy of the ATM Connection

P W 1

Static

ATM n to one VCC cell transpor t ATM n to one VCC cell transpor t

100

OptiX PTN 1900:192.1 68.1.6 OptiX PTN 3900:192.1 68.1.5

10

Service Type: UBR Traffic Type: NoTrafficDescriptor

P W 2

Dynami c

Dyna mic distri butio n

OptiX PTN 1900:192.1 68.10.6 OptiX PTN 3900:192.1 68.2.5

Service Type: CBR. Traffic Type: NoClpNoScr Clp01Pcr(cell/s): 10000

Table 24-13 and Table 24-14 list the planning of the ATM services on the OptiX PTN 1900 and OptiX PTN 3900.

24-26

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

24 Configuring Services for the Offload Solution

Table 24-13 Planning of the ATM service on the OptiX PTN 1900 Attribute Node B of the Service Source Port ATM Connection (Two ATM Connections for Each ATM Service) Source VPI/ VCI Sink VPI/VCI PW Carrying the Service Tunnel Carrying the PW Uplink Policy Downlink Policy ATM Service 1 Node B 1 1-MD1-1 (Trunk-1) HSDPA 1 Node B 2 1-MD1-2 (Trunk-2) HSDPA 2 ATM Service 2 Node B 1 1-MD1-1 (Trunk-1) R99 1 Node B 2 1-MD1-2 (Trunk-2) R99 2

1/101 46/80 PW1 MPLS Tunnel 1

1/101 46/81 PW1 MPLS Tunnel 1

1/100 56/80 PW2 MPLS Tunnel 2

1/100 56/81 PW2 MPLS Tunnel 2

UBR UBR

UBR UBR

CBR CBR

CBR CBR

Table 24-14 Planning of the ATM service on the OptiX PTN 3900 Attribute Source Port ATM Connection (Two ATM Connections for Each ATM Service) Source VPI/ VCI Sink VPI/VCI PW Carrying the Service ATM Service 1 4-MP1-AD1-1 HSDPA 1 HSDPA 2 R99 1 R99 2 ATM Service 2

46/80 46/80 PW1

46/81 46/81 PW1

56/80 56/80 PW2

56/81 56/81 PW2

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

24-27

24 Configuring Services for the Offload Solution

OptiX iManager T2000 Operation Guide for PTN NE Management

Attribute Tunnel Carrying the PW Uplink Policy Downlink Policy

ATM Service 1 MPLS Tunnel 1 MPLS Tunnel 1

ATM Service 2 MPLS Tunnel 2 MPLS Tunnel 2

UBR UBR

UBR UBR

CBR CBR

CBR CBR

24.4.2 Configuration Process

This section describes the configuration process of the Offload application in an ETHforwarding-based network.

Prerequisite
l l

You must know the networking and data planning of this case. Because the Offload solution involves configuration of many operation tasks, you are supposed to learn how to configure interfaces and tunnels, how to create the QoS policy, and how to configure ATM services before the configuration.

Procedure
Step 1 In the NE Explorer, select OptiX PTN 1900. Choose Configuration > Interface Management > PDH Interface. Set Port Mode to Layer 2 and Encapsulation Type to ATM for eight interfaces ranging from 3-L75-1 to 3-L75-8. Step 2 Choose Configuration > Interface Management > ATM IMA Management, and click the Binding tab. Bind interfaces ranging from 3-L75-1 to 3-L75-4 and interfaces ranging from 3L75-5 to 3-L75-8 to Trunk 1 and Trunk 2 respectively. Step 3 Choose IMA Group Management. Then, set IMA Protocol Enable Status to Enabled for 1CXP-1-MD1-1(Trunk-1) and 1-CXP-1-MD1-2(Trunk-2). Step 4 In the NE Explorer, select OptiX PTN 3900. Choose Configuration > Interface Management > Ethernet Interface. Set 1-EG16-1 as an network-side interface. Then, set the parameters as follows:
l

Basic attributes

Set Port Mode to Layer 3. Use the default values for other parameters Set Enable Tunnel to Enabled. Set Specify IP to Manually. Set IP Address to 192.168.1.6. Set IP Mask to 255.255.255.252.

Layer 3 attributes

Step 5 Choose Configuration > Interface Management > SDH Interface. Set 19-POD41-1 as an network-side interface. Then, set the parameters as follows:
24-28 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

l

24 Configuring Services for the Offload Solution

Basic attributes

Set Encapsulation Type to PPP. Use the default values for other parameters Set Enable Tunnel to Enabled. Set Specify IP to Manually. Set IP Address to 192.168.10.6. Set IP Mask to 255.255.255.252.

Layer 3 attributes

Step 6 In the NE Explorer, select OptiX PTN 1900. Choose Configuration > Interface Management > Ethernet Interface. Set 7-ETFC-1 as an network-side interface. Then, set the parameters as follows:
l

Basic attributes

Set Port Mode to Layer 3. Use the default values for other parameters Set Enable Tunnel to Enabled. Set Specify IP to Manually. Set IP Address to 192.168.1.5. Set IP Mask to 255.255.255.252.

Layer 3 attributes

Step 7 Choose Configuration > Interface Management > SDH Interface. Set 4-POD41-1 as an network-side interface. Then, set the parameters as follows:
l

Basic attributes

Set Encapsulation Type to PPP. Use the default values for other parameters Set Enable Tunnel to Enabled. Set Specify IP to Manually. Set IP Address to 192.168.1.6. Set IP Mask to 255.255.255.252.

Layer 3 attributes

Step 8 Create static ARP on the OptiX PTN 1900 and OptiX PTN 3900. In the NE Explorer, choose Configuration > Control Plane Configuration > Address Parse . Click Create.
l

OptiX PTN 1900

Set ARP List IP to 192.168.10.6. Set ARP List MAC to 00-00-00-00-00-02. Set ARP List IP to 192.168.1.5. Set ARP List MAC to 00-00-00-00-00-01.

OptiX PTN 3900

Step 9 Create MPLS tunnel 1 between the OptiX PTN 1900 and the OptiX PTN 3900. Because the type of the tunnel is Static, you need to create a static MPLS tunnel on the OptiX PTN 1900 and
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 24-29

24 Configuring Services for the Offload Solution

OptiX iManager T2000 Operation Guide for PTN NE Management

OptiX PTN 3900 respectively. For the method of creating the tunnel in this case, see 13.4.2 Creating an MPLS Tunnel on a Per-NE Basis. Step 10 Create MPLS tunnel 2 between the OptiX PTN 1900 and OptiX PTN 3900. You can dynamically create the MPLS tunnel because tunnel 2 passes the PTN equipment. Set attributes of each interface of the NEs involved properly before the creation. For the method of the tunnel in this case, see 13.3.1 Creating a Dynamic MPLS Tunnel and the FRR Protection by Using the Trail Function. Step 11 Create two ATM policies on the OptiX PTN 1900 and OptiX PTN 3900 respectively. In the NE Explorer, choose Configuration > QoS Management > Policy Management . Then, select ATM Policy and click New.
l l

The ATM policies on the OptiX PTN 1900 and the OptiX PTN 3900 should be consistent. In the case of the CBR policy, set the parameters as follows:

Set Service Type to CBR. Set Traffic Type to NoClpNoScr. Set Clp01Pcr(cell/s) to 10000. Set Service Type to UBR. Set Traffic Type to NoTrafficDescriptor.

In the case of the UBR policy, set the parameters as follows:

Step 12 Create ATM service 1 on the OptiX PTN 1900. Create two ATM connections in ATM service 1. Change the VPI/VCI values of the two services accessed by the two IMA groups from 1/101 to respectively 46/80 and 46/81, encapsulate the services, and then send the services to MPLS tunnel 1 carried by the 7-ETFC-1 interface. In the NE Explorer, choose Configuration > ATM Service Management. Click the Connection tab, and click New. Set the parameters as follows:
l l l

Set Service Type to UNIs-NNI. Set Connection Type to PVC. Set the parameters for connection 1 as follows:

Set Source Board to 1-CXP. Set Source Port to 1-MD1-1(Trunk-1). Set Source VPI to 1. Set Source VCI to 101. Set Sink VPI to 46. Set Sink VCI to 80. Set Uplink Policy and Downlink Policy to the created UBR policy Set Source Board to 1-CXP. Set Source Port to 1-MD1-2(Trunk-2). Set Source VPI to 1. Set Source VCI to 101. Set Sink VPI to 46. Set Sink VCI to 81. Set Uplink Policy and Downlink Policy to the created UBR policy
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

Set the parameters for connection 2 as follows:

24-30

OptiX iManager T2000 Operation Guide for PTN NE Management

l

24 Configuring Services for the Offload Solution

Setting the parameters of PW1 as follows: General Attributes:

Set PW ID to 1. Set PW Signaling Type to Static. Set PW Type to ATM n-to-one VCC cell transport. Set PW Ingress Label and PW Egress Label to 100. Set Peer IP to 192.168.1.6. Set Tunnel Type to MPLS. Set Tunnel to created MPLS Tunnel 1. Set Max. Concatenated Cell Count to 10. Set Packet Loading Time(us) to 1000. Ingress

QoS

Bandwidth Limit: Enabled CIR (kbit/s): 10240 CBS (byte): PIR (kbit/s): 15000 PBS (byte): Policy: EXP: 1

Advanced Attributes:

Control Word: Must use Control Channel Type: CW (CW realizes connectivity check of the PW.) VCCV Verification Mode: Ping ( PW Ping realizes connectivity check of the PW.) Max. Concatenated Cell Count: 10 (the maximum number of ATM cells that can be encapsulated in each packet) Packet Loading Time (us): 1000

NOTE

PW advanced attributes such as Control Word, Control Channel Type and VCCV Verification Mode need be set according to the user requirements. For detailed configuration steps, refer to 19.5.1 Creating ATM Services on a Per-NE Basis.

Step 13 Create ATM service 2 on the OptiX PTN 1900. Create two ATM connections in ATM service 2. Change the VPI/VCI values of the two services accessed by the two IMA groups from 1/100 to respectively 56/80 and 56/81, encapsulate the services, and then send the services to MPLS tunnel 2 carried by the 4-POD41-1 interface. For the configuration parameters, see the service planning in the case description. Set the parameters according to Step 12. In the case of PW2, PW Signaling Type should be set to Dynamic. In addition, PW Ingress Label and PW Egress Label need not be set. Step 14 Create ATM service 1 on the OptiX PTN 3900. Create two ATM connections in ATM service 1. The VPI/VCI exchange need not be performed. Send the services whose VPI/VCI values are respectively 46/80 and 46/81 and accessed by the 4-MP1-AD1-1 interface to MPLS tunnel 1 carried by the Ethernet virtual interface on the network side.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 24-31

24 Configuring Services for the Offload Solution

OptiX iManager T2000 Operation Guide for PTN NE Management

For the configuration parameters, see the service planning in the case description. Set the parameters according to Step 12. Step 15 Create ATM service 2 on the OptiX PTN 3900. Create two ATM connections in ATM service 2. The VPI/VCI exchange need not be performed. Send the services whose VPI/VCI values are respectively 56/80 and 56/81 and accessed by the 4-MP1-AD1-1 interface to MPLS tunnel 2 carried by the POS interface on the network side. For the configuration parameters, see the service planning in the case description. Set the parameters according to Step 12. In the case of PW2, PW Signaling Type should be set to Dynamic. In addition, PW Ingress Label and PW Egress Label need not be set. ----End

24.5 IP-Based Service Configuration Case

This section describes the offload solution for the case where IP-based services traverse the wholesale ADSL network. 24.5.1 Case Description This section describes the offload solution to the wholesale ADSL network, which is forwarded according to the IP. 24.5.2 Configuration Process This section describes the configuration process of the Offload application in an IP-forwardingbased network.

24.5.1 Case Description

This section describes the offload solution to the wholesale ADSL network, which is forwarded according to the IP.

Networking and Requirement

Two Node Bs are accessed through two IMA groups of the OptiX PTN 1900, and the two Node Bs communicate with the RNC connected to the OptiX PTN 3900 at the opposite end through the network. Services of Node B include the R99 voice service and high speed downlink packet access (HSDPA) service. The voice service, which is carried by the backhaul network constructed by the OptiX PTN equipment, requires QoS guarantee, low delay and bandwidth guarantee. The HSDPA service does not require low delay, but it only requires bandwidth guarantee. Hence, the IP network of a third party operator is leased. The OptiX PTN 1900 differentiates services according to the VPI and VCI values, and then distributes the services to two different routes for transmission.
l

HSDPA service: The HSDPA service is converged to the DSLAM equipment through the ADSL modem, and then it enters the leased IP network of the third party operator for transmission. The HSDPA service requires only bandwidth guarantee, and thus the lease cost is low. R99 voice service: The R99 voice service is transported through the backhaul network. The equipment in the network is the OptiX PTN equipment series. The R99 voice service requires QoS guarantee, low delay and bandwidth guarantee.

Figure 24-10 shows the networking diagram.

24-32 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

l

24 Configuring Services for the Offload Solution

HSDPA service: On the OptiX PTN 1900, perform the VPI/VCI switching on the service with a VPI/VCI value of 1/101, and then transport the service to the FE interface of the ETFC. The ADSL modem completes the AAL5 adaptation and ATM encapsulation, and the DSLAM removes the ADSL and ATM layers. Then, the Ethernet packets are sent to the IP switching network. The OptiX PTN 3900 rearranges the service and then converges the service to the ATM STM-1 interface. Then, the service is transported to RNC. IP Tunnel 1 is set up between the OptiX PTN 1900 and OptiX PTN 3900 for carrying the service. Figure 24-10 shows the encapsulation format of packets at the interface of each equipment. The red lines indicate the VPI/VCI values at ATM layers in the packets. R99 voice service: On the OptiX PTN 1900, perform the VPI/VCI switching on the service with a VPI/VCI value of 1/100, and then transport the service to the POS interface of the POD41. The service is carried by MPLS Tunnel 2, and then is transported to the OptiX PTN 3900. The OptiX PTN 3900 rearranges the service and then converges the service to the ATM STM-1 interface. Then, the service is transported to RNC.

Figure 24-10 Networking diagram of the offload application scenario based on the IP forwarding and packet encapsulation format
ATM E1 ATM PWE3 PW Label IP Ethernet ATM PWE3 PW Label IP Ethernet AAL5 ATM ADSL ATM PWE3 PW Label IP Ethernet ATM PWE3 PW Label IP Ethernet ATM STM-1

CXP-1-MD1-3-L75:1-4

7-ETFC-1

1-EG16-1 4-MP1-AD1-1 Wholesale ADSL service

46/80 46/81 56/80 56/81 56/80 56/81

1/100 1/101

46/80 46/81

Node B 1
1/100 1/101

ADSL modem HSDPA flow R99 flow

56/80 56/81

DSLAM

ATM STM-1

RNC

Node B 2 4-POD41-1 CXP-1-MD1-3-L75:5-8

PTN 1-EG16-19-POD41-1

IP Tunnel 1 MPLS Tunnel 2 OptiX PTN 1900 OptiX PTN 3900

The ADSL modem can work in the bridge or router mode.

l

When the ADSL modem works in the bridge mode, the ADSL modem performs the EoA encapsulation on the accessed FE signals. The OptiX PTN 1900 on the access node uses the MPLS Tunnel or IP Tunnel.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 24-33

Issue 01 (2009-06-30)

24 Configuring Services for the Offload Solution

l

OptiX iManager T2000 Operation Guide for PTN NE Management

When the ADSL modem works in the router mode, the ADSL modem performs the IPoA encapsulation on the accessed FE signals. The OptiX PTN 1900 at the access node uses the IP Tunnel or GRE Tunnel.

In this example, the OptiX PTN 1900 uses the MPLS Tunnel, and the ADSL modem works in the bridge mode. If the ADSL modem works in the router mode, the configuration method is the same. In this case, the GRE Tunnel is created to carry the HSDPA service.

Service Planning
The offload is a solution instead of a service or feature. Hence, according to the user requirement and networking diagram of this example, this example uses the offload solution to perform the following tasks. 1. Create the IMA group and configure the member interfaces. On the OptiX PTN 1900, create two IMA groups for accessing the IMA services of two Node Bs. 2. Configure attributes of the interface. The attributes of the interface carry the tunnel should be configured on the OptiX PTN 1900 and OptiX PTN 3900. 3. Create the static route. Create the static route on the OptiX PTN 1900 and OptiX PTN 3900. The static route is used for creating the IP Tunnel. 4. Create the static ARP table entry. After the static ARP is configured, the equipment finds the corresponding MAC address in the ARP table entry according to the destination IP address, and then writes the MAC address as the destination MAC to the ETH layer of the packet. The Layer 2 switching network forwards the packet to the destination according to this MAC address. Static MPLS Tunnel should use this table entry. 5. Create IP Tunnel 1. This tunnel is used for carrying the HSDPA service. The ports where the tunnel resides are the FE interface of the OptiX PTN 1900 and the GE interface of the OptiX PTN 3900. 6. Create MPLS Tunnel 2. This tunnel is used for carrying the R99 voice service, which resides on the POS interfaces of the OptiX PTN 1900 and OptiX PTN 3900. 7. Create the QoS policy (CBR and UBR). Create the ATM policy before creating the ATM service. On the OptiX PTN 1900 and OptiX PTN 3900, create two ATM policies respectively. CBR is used for the R99 voice service, and UBR is used for the HSDPA service. 8. Create the ATM service.
l l

On the OptiX PTN 1900, create two ATM services, and access the services of Node B. On the OptiX PTN 3900, create two ATM services, and access the services of RNC. On the OptiX PTN 1900, create two ATM connections in each ATM service, and encapsulate the services to different PWs according to the VPI/VCI value, and select different Tunnel for carrying the services.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

9.

Create the ATM connection.

l

24-34

OptiX iManager T2000 Operation Guide for PTN NE Management

l

24 Configuring Services for the Offload Solution

On the OptiX PTN 3900, create two ATM connections in each ATM service, and encapsulate the services to different PWs according to the VPI/VCI value, and select different Tunnel for carrying the services.

NOTE

In the leased network of the third party operator, the services are configured by the third party operator.

The parameter planning is as follows: Table 24-15 lists the planning of the voice service and data service in the network. Table 24-15 VPI/VCI values of the Node B service Service Service Bandwidth 2 Mbit/s 5 Mbit/s 2 Mbit/s 5 Mbit/s User-Side VPI/VCI Value 1/100 1/101 1/100 1/101 NetworkSide VPI/ VCI Value 56/80 46/80 56/81 46/81 VPI/VCI Value on the RNC Side 56/80 46/80 56/81 46/81

R99 voice service of Node B 1 HSDPA service of Node B 1 R99 voice service of Node B 2 HSDPA service of Node B 2

Table 24-16 lists the planning of the UNIs. The OptiX PTN 1900 needs to create two IMA groups to access two Node B services. The OptiX PTN 3900 needs to interconnect 4-MP1AD1-1 to RNC. Table 24-16 Planning of the UNIs Equipment Interface OptiX PTN 1900:1-MD1-1 (Trunk-1) OptiX PTN 1900:1-MD1-2 (Trunk-2) OptiX PTN 3900:4-MP1AD1-1 Binding Interface 3-L75-1 to 3-L75-4 Interface Attribute The port mode of the PDH interface is set to Layer 2, and the encapsulation type is ATM by default. The port mode of the PDH interface is set to Layer 2, and the encapsulation type is ATM by default. The port mode of the SDH interface is set to Layer 2, and the encapsulation type is ATM by default.

3-L75-5 to 3-L75-8

Table 24-17 lists the planning of the NNIs.

Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 24-35

24 Configuring Services for the Offload Solution

OptiX iManager T2000 Operation Guide for PTN NE Management

Table 24-17 Planning of the NNIs Equipment Interface OptiX PTN 1900:7ETFC-1 OptiX PTN 3900:1EG16-1 OptiX PTN 1900:4POD41-1 Interface Type Port Mode IP Address and Subnet Mask of the Interface 192.168.1.5/30 192.168.20.6/30 192.168.2.5/30 (In the backhaul network, the IP address and mask of the interface of the OptiX PTN equipment interconnected to this SDH interface is 192.168.2.6/30.) 192.168.10.6/30 (In the backhaul network, the IP address and mask of the interface of the OptiX PTN equipment interconnected to this SDH interface is 192.168.10.5/30.)

Ethernet interface Ethernet interface SDH interface

Layer 3 Layer 3 Layer 3

OptiX PTN 3900:19POD41-1

SDH interface

Layer 3

Table 24-18 lists the planning of the static routing table entries. Table 24-18 Planning of the static routing table entries Parameter Route List ID Board Port Next Hop IP Address OptiX PTN 1900 1 7-ETFC 1(PORT-1) 192.168.1.6 (IP address of the interface of the equipment interconnected to the DSLAM in the leased network) 192.168.20.6 OptiX PTN 3900 1 1-EG16 1(PORT-1) 192.168.20.5 (IP address of the interface of the equipment interconnected to the OptiX PTN 3900 in the leased network) 192.168.1.5

Destination Node IP

24-36

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

24 Configuring Services for the Offload Solution

Parameter Destination Node Subnet Mask

OptiX PTN 1900 255.255.255.255

OptiX PTN 3900 255.255.255.255

Table 24-19 and Table 24-20 list the planning of the tunnel and related PW. Table 24-19 Planning of the Tunnel Tunnel Tunnel ID Interface of the Tunnel Carried by the OptiX PTN 1900 7-ETFC Interface of the Tunnel Carried by the OptiX PTN 3900 1-EG16-1 Tunnel Type Sink Port IP Address Tunnel Bandwid th

IP Tunnel 1

50

Static IP Tunnel

OptiX PTN 1900:192. 168.20.6 OptiX PTN 3900:192. 168.1.5

No restriction

MPLS Tunnel 2

Dynamic distributio n

4POD41-1

19POD41-1

Dynamic MPLS Tunnel

No restriction

NOTE

As the type of the IP Tunnel 1 is static, you need to create the static ARP and manually specify Sink Port IP Address of the IP Tunnel. If the type of the MPLS Tunnel 2 is dynamic, manually specify the restriction condition. Hence, the tunnel passes through the specified interfaces.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

24-37

24 Configuring Services for the Offload Solution

OptiX iManager T2000 Operation Guide for PTN NE Management

Table 24-20 Planning of the PW P W PW Signali ng Type PW Type PW Labe l Opposite IP Address Max. Conca tenate d Cell Count Packe tisatio n Buffer ing Time (us) 1000 QoS Policy of the ATM Connection

P W 1

Static

ATM n to one VCC cell transpor t ATM n to one VCC cell transpor t

100

OptiX PTN 1900:192.1 68.20.6 OptiX PTN 3900:192.1 68.1.5

10

Service Type: UBR Traffic Type: NoTrafficDescriptor

P W 2

Dynami c

Dyna mic distri butio n

OptiX PTN 1900:192.1 68.10.6 OptiX PTN 3900:192.1 68.2.5

Service Type: CBR. Traffic Type: NoClpNoScr Clp01Pcr(cell/s): 10000

Table 24-21 and Table 24-22 list the planning of the ATM services on the OptiX PTN 1900 and OptiX PTN 3900. Table 24-21 Planning of the ATM service on the OptiX PTN 1900 Attribute Node B of the Service Source Port ATM Connection (Two ATM Connections for Each ATM Service) Source VPI/ VCI Sink VPI/VCI PW Carrying the Service ATM Service 1 Node B 1 1-MD1-1 (Trunk-1) HSDPA 1 Node B 2 1-MD1-2 (Trunk-2) HSDPA 2 ATM Service 2 Node B 1 1-MD1-1 (Trunk-1) R99 1 Node B 2 1-MD1-2 (Trunk-2) R99 2

1/101 46/80 PW1

1/101 46/81 PW1

1/100 56/80 PW2

1/100 56/81 PW2

24-38

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

24 Configuring Services for the Offload Solution

Attribute Tunnel Carrying the PW Uplink Policy Downlink Policy

ATM Service 1 MPLS Tunnel 1 MPLS Tunnel 1

ATM Service 2 MPLS Tunnel 2 MPLS Tunnel 2

UBR UBR

UBR UBR

CBR CBR

CBR CBR

Table 24-22 Planning of the ATM service on the OptiX PTN 3900 Attribute Source Port ATM Connection (Two ATM Connections for Each ATM Service) Source VPI/ VCI Sink VPI/VCI PW Carrying the Service Tunnel Carrying the PW Uplink Policy Downlink Policy ATM Service 1 4-MP1-AD1-1 HSDPA 1 HSDPA 2 R99 1 R99 2 ATM Service 2

46/80 46/80 PW1 MPLS Tunnel 1

46/81 46/81 PW1 MPLS Tunnel 1

56/80 56/80 PW2 MPLS Tunnel 2

56/81 56/81 PW2 MPLS Tunnel 2

UBR UBR

UBR UBR

CBR CBR

CBR CBR

24.5.2 Configuration Process

This section describes the configuration process of the Offload application in an IP-forwardingbased network.

Prerequisite
l

You must know the networking and data planning of this case.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

24-39

24 Configuring Services for the Offload Solution

l

OptiX iManager T2000 Operation Guide for PTN NE Management

Because the Offload solution involves configuration of many operation tasks, you are supposed to learn how to configure interfaces and tunnels, how to create the QoS policy, and how to configure ATM services before the configuration.

Procedure
Step 1 In the NE Explorer, select OptiX PTN 1900. Choose Configuration > Interface Management > PDH Interface. Set Port Mode to Layer 2 and Encapsulation Type to ATM for eight interfaces ranging from 3-L75-1 to 3-L75-8. Step 2 Choose Configuration > Interface Management > ATM IMA Management, and click the Binding tab. Bind interfaces ranging from 3-L75-1 to 3-L75-4 and interfaces ranging from 3L75-5 to 3-L75-8 to Trunk 1 and Trunk 2 respectively. Step 3 Choose IMA Group Management. Then, set IMA Protocol Enable Status to Enabled for 1CXP-1-MD1-1(Trunk-1) and 1-CXP-1-MD1-2(Trunk-2). Step 4 In the NE Explorer, select OptiX PTN 3900. Choose Configuration > Interface Management > Ethernet Interface. Set 1-EG16-1 as an network-side interface. Then, set the parameters as follows:
l

Basic attributes

Set Port Mode to Layer 3. Use the default values for other parameters Set Enable Tunnel to Enabled. Set Specify IP to Manually. Set IP Address to 192.168.20.6. Set IP Mask to 255.255.255.252.

Layer 3 attributes

Step 5 Choose Configuration > Interface Management > SDH Interface. Set 19-POD41-1 as an network-side interface. Then, set the parameters as follows:
l

Basic attributes

Set Encapsulation Type to PPP. Use the default values for other parameters. Set Enable Tunnel to Enabled. Set Specify IP to Manually. Set IP Address to 192.168.10.6. Set IP Mask to 255.255.255.252.

Layer 3 attributes

Step 6 In the NE Explorer, select OptiX PTN 1900. Choose Configuration > Interface Management > Ethernet Interface. Set 7-ETFC-1 as an network-side interface. Then, set the parameters as follows:
l

Basic attributes

Set Port Mode to Layer 3. Use the default values for other parameters.

Layer 3 attributes
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

24-40

OptiX iManager T2000 Operation Guide for PTN NE Management

24 Configuring Services for the Offload Solution

Set Enable Tunnel to Enabled. Set Specify IP to Manually. Set IP Address to 192.168.1.5. Set IP Mask to 255.255.255.252.

Step 7 Choose Configuration > Interface Management > SDH Interface. Set 4-POD41-1 as an network-side interface. Then, set the parameters as follows:
l

Basic attributes

Set Encapsulation Type to PPP. Use the default values for other parameters. Set Enable Tunnel to Enabled. Set Specify IP to Manually. Set IP Address to 192.168.2.5. Set IP Mask to 255.255.255.252.

Layer 3 attributes

Step 8 Create static routes on the OptiX PTN 1900 and OptiX PTN 3900. In the NE Explorer, choose Configuration > Control Plane Configuration > Static Route Management . Click Create.
l

OptiX PTN 1900

Set Board to 7-ETFC-1. Set Port to 1(PORT-1). Set Next Hop IP Address to 192.168.1.6. Set Destination Node IP to 192.168.20.6. Set Destination Node Subnet Mask to 255.255.255.255. Set Board to 1-EG16-1. Set Port to 1(PORT-1). Set Next Hop IP Address to 192.168.20.5. Set Destination Node IP to 192.168.1.5. Set Destination Node Subnet Mask to 255.255.255.255.

OptiX PTN 3900

Step 9 Create static ARP on the OptiX PTN 1900 and OptiX PTN 3900. In the NE Explorer, choose Configuration > Control Plane Configuration > Address Parse . Click Create.
l

OptiX PTN 1900

Set ARP List IP to 192.168.10.6. Set ARP List MAC to 00-00-00-00-00-02. Set ARP List IP to 192.168.1.5. Set ARP List MAC to 00-00-00-00-00-01.

OptiX PTN 3900

Step 10 Create IP tunnel 1 between the OptiX PTN 1900 and the OptiX PTN 3900. Because the type of the tunnel is Static, you need to create the IP tunnels on the OptiX PTN 1900 and OptiX PTN
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 24-41

24 Configuring Services for the Offload Solution

OptiX iManager T2000 Operation Guide for PTN NE Management

3900 respectively. For the method of creating the tunnel in this case, see 14.3 Creating IP Tunnels. Step 11 Create MPLS tunnel 2 between the OptiX PTN 1900 and OptiX PTN 3900. You can dynamically create the MPLS tunnel because tunnel 2 passes the PTN equipment. Set attributes of each interface of the NEs involved properly before the creation. For the method of the tunnel in this case, see 13.3.1 Creating a Dynamic MPLS Tunnel and the FRR Protection by Using the Trail Function. Step 12 Create two ATM policies on the OptiX PTN 1900 and OptiX PTN 3900 respectively. In the NE Explorer, choose Configuration > QoS Management > Policy Management . Then, select ATM Policy and click New.
l l

The ATM policies on the OptiX PTN 1900 and the OptiX PTN 3900 should be consistent. In the case of the CBR policy, set the parameters as follows:

Set Service Type to CBR. Set Traffic Type to NoClpNoScr. Set Clp01Pcr(cell/s) to 10000. Set Service Type to UBR. Set Traffic Type to NoTrafficDescriptor.

In the case of the UBR policy, set the parameters as follows:

Step 13 Create ATM service 1 on the OptiX PTN 1900. Create two ATM connections in ATM service 1. Change the VPI/VCI values of the two services accessed by the two IMA groups from 1/101 to respectively 46/80 and 46/81, encapsulate the services, and then send the services to MPLS tunnel 1 carried by the 7-ETFC-1 interface. In the NE Explorer, choose Configuration > ATM Service Management. Click the Connection tab, and click New. Set the parameters as follows:
l l l

Set Service Type to UNIs-NNI. Set Connection Type to PVC. Set the parameters for connection 1 as follows:

Set Source Board to 1-CXP. Set Source Port to 1-MD1-1(Trunk-1). Set Source VPI to 1. Set Source VCI to 101. Set Sink VPI to 46. Set Sink VCI to 80. Set Uplink Policy and Downlink Policy to the created UBR policy. Set Source Board to 1-CXP. Set Source Port to 1-MD1-2(Trunk-2). Set Source VPI to 1. Set Source VCI to 101. Set Sink VPI to 46. Set Sink VCI to 81. Set Uplink Policy and Downlink Policy to the created UBR policy.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

Set the parameters for connection 2 as follows:

24-42

OptiX iManager T2000 Operation Guide for PTN NE Management

l

24 Configuring Services for the Offload Solution

Setting the parameters of PW1 as follows: General Attributes:

Set PW ID to 1. Set PW Signaling Type to Static. Set PW Type to ATM n-to-one VCC cell transport. Set PW Ingress Label and PW Egress Label to 100. Set Peer IP to 192.168.1.6. Set Tunnel Type to MPLS. Set Tunnel to created MPLS Tunnel 1. Set Max. Concatenated Cell Count to 10. Set Packet Loading Time(us) to 1000. Ingress

QoS

Bandwidth Limit: Enabled CIR (kbit/s): 10240 CBS (byte): PIR (kbit/s): 15000 PBS (byte): Policy: EXP: 1

Advanced Attributes:

Control Word: Must use Control Channel Type: CW (CW realizes connectivity check of the PW.) VCCV Verification Mode: Ping ( PW Ping realizes connectivity check of the PW.) Max. Concatenated Cell Count: 10 (the maximum number of ATM cells that can be encapsulated in each packet) Packet Loading Time (us): 1000

NOTE

PW advanced attributes such as Control Word, Control Channel Type and VCCV Verification Mode need be set according to the user requirements. For detailed configuration steps, refer to 19.5.1 Creating ATM Services on a Per-NE Basis.

Step 14 Create ATM service 2 on the OptiX PTN 1900. Create two ATM connections in ATM service 2. Change the VPI/VCI values of the two services accessed by the two IMA groups from 1/100 to respectively 56/80 and 56/81, encapsulate the services, and then send the services to MPLS tunnel 2 carried by the 4-POD41-1 interface. For the configuration parameters, see the service planning in the case description. Set the parameters according to Step 13. In the case of PW2, PW Signaling Type should be set to Dynamic. In addition, PW Ingress Label and PW Egress Label need not be set. Step 15 Create ATM service 1 on the OptiX PTN 3900. Create two ATM connections in ATM service 1. The VPI/VCI exchange need not be performed. Send the services whose VPI/VCI values are respectively 46/80 and 46/81 and accessed by the 4-MP1-AD1-1 interface to MPLS tunnel 1 carried by the Ethernet virtual interface on the network side.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 24-43

24 Configuring Services for the Offload Solution

OptiX iManager T2000 Operation Guide for PTN NE Management

For the configuration parameters, see the service planning in the case description. Set the parameters according to Step 13. Step 16 Create ATM service 2 on the OptiX PTN 3900. Create two ATM connections in ATM service 2. The VPI/VCI exchange need not be performed. Send the services whose VPI/VCI values are respectively 56/80 and 56/81 and accessed by the 4-MP1-AD1-1 interface to MPLS tunnel 2 carried by the POS interface on the network side. For the configuration parameters, see the service planning in the case description. Set the parameters according to Step 13. In the case of PW2, PW Signaling Type should be set to Dynamic. In addition, PW Ingress Label and PW Egress Label need not be set. ----End

24-44

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

25
About This Chapter

OAM Management

Operation, administration and maintenance (OAM) is a network monitoring tool. Based on the feedback of OAM, network administrators can find and locate network faults in time. 25.1 Configuring the Ethernet Port OAM This section describes how to configure the Ethernet port OAM. 25.2 Configuring the Ethernet Service OAM This section describes how to configure Ethernet service OAM. 25.3 Configuring the MPLS OAM You can configure the MPLS OAM. 25.4 Configuring the PW OAM This section describes how to configure the PW OAM. 25.5 Configuring ATM OAM How to use the T2000 to configure ATM OAM is described. 25.6 Configuration Case of the Ethernet Port OAM The configuration case of the Ethernet port OAM describes how to configure the Ethernet port OAM. 25.7 Configuration Case of the Ethernet Service OAM The configuration case of the Ethernet service OAM describes how to configure the Ethernet OAM. 25.8 Configuration Case of the MPLS OAM The configuration case of MPLS OAM describes how to configure the MPLS OAM. 25.9 Configuration Case of the ATM OAM The configuration case of the ATM OAM describes how to configure the ATM OAM. 25.10 Configuration Case of the PW OAM This section describes how to configure the PW OAM through a configuration case.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

25-1

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

25.1 Configuring the Ethernet Port OAM

This section describes how to configure the Ethernet port OAM. 25.1.1 Overview of the Ethernet Port OAM The Ethernet port OAM is mainly used to automatically check the connectivity and performance and locate the faults of the physical links at the MAC layer and under the MAC layer. It is applicable when the physical Ethernet ports are directly connected. 25.1.2 Basic Concepts Basic concepts of the Ethernet port OAM include discovery, Link Monitoring, remote loopback and OAM working mode. 25.1.3 Application of the Ethernet Port OAM The Ethernet port OAM is mainly used to check the connectivity of the physical link between two Ethernet ports that are directly connected. 25.1.4 Querying the Remote OAM Parameters To check the Ethernet by using the Ethernet OAM function, which is stipulated in IEEE 802.3ah, make sure that the OAM parameters are configured as the same for equipment at both ends of the Ethernet link. You can browse the remote OAM parameters to know the configuration of parameters at the remote equipment. 25.1.5 Setting the OAM Parameters Set the OAM parameters of the local equipment according to the parameter configuration of the remote equipment. In this way, functions such as the link event notification and remote loopback are available. 25.1.6 Setting OAM Error Frame Monitor Parameters Set the OAM error frame monitor parameters to customize the performance threshold and performance monitor range of the link, and thus to facilitate the monitoring of the link performance. 25.1.7 Starting the Remote Loopback Perform the remote loopback to check the connectivity of the physical link and thus to locate and then rectify faults.

25.1.1 Overview of the Ethernet Port OAM

The Ethernet port OAM is mainly used to automatically check the connectivity and performance and locate the faults of the physical links at the MAC layer and under the MAC layer. It is applicable when the physical Ethernet ports are directly connected.

Objective and Benefits

The Ethernet port OAM, based on 802.3ah, is used to handle the "last mile" problem for the Ethernet OAM. The Ethernet port OAM can also be used to check the connectivity and performance of the physical Ethernet links between two equipments. The Ethernet port OAM, based on port, is applicable in scenarios where the physical Ethernet ports are directly connected. The Ethernet port OAM has the following functions:
l

Discovery: Check whether the opposite equipment supports the 802.3ah OAM function.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

25-2

OptiX iManager T2000 Operation Guide for PTN NE Management

l l l l

25 OAM Management

Link monitoring: Check the link performance. Remote fault detection: Detect the remote fault through notifications from the remote end. Remote loopback: Check the bidirectional connectivity of the link. Link performance event notification: The local end can notify the remote end of the performance events that exceed the configured threshold.

Compliant Standard and Protocol

The Ethernet port OAM complies IEEE 802.3ah (Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications).

25.1.2 Basic Concepts

Basic concepts of the Ethernet port OAM include discovery, Link Monitoring, remote loopback and OAM working mode.

Discovery
Discovery is the first phase of the 802.3 ah OAM protocol. Discovery identifies the supporting situation of the 802.3 ah protocol for the equipment directly connected to the local end through network cables.

Link Monitoring
Link monitoring is used to detect and discover faults at the link layer. When the port detects performance events indicating the error frame threshold crossing, error frame second threshold crossing, and period error frame threshold crossing, this port notifies the faults by transmitting performance event notifications, that is, OAM PDU (OAM protocol data unit) packets, to the opposite equipment. The related concepts of link monitoring are as follows:
l l

Error frame: In a period, the number of error frames that exceeds the threshold value. Number of period error frames: It indicates the number of error frames that exceeds the threshold value within the specified number of frames. Number of error frame seconds: It indicates the number of seconds where error frames occur within the specified seconds. Number of period error signals: It indicates the number of error signals within the specified period.

Remote Loopback
To request for remote loopback at the opposite port, the local port transmits the remote loopback OAM PDU to the opposite port. This function provides necessary help during the equipment installation and fault rectification. In the loopback mode, all the packets, excluding the OAM PDU and suspending packets, are returned to the original route. The loopback check is periodically performed to ensure that the existing links are available. In addition, the specific faulty area can be located through multi-period loopback check. When the link status is changed, the remote loopback automatically stops.

OAM Working Mode

The OAM working modes include the active and passive modes.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 25-3

25 OAM Management
l l

OptiX iManager T2000 Operation Guide for PTN NE Management

Active: Active mode, in which the port can initiate OAM packets. Passive: Passive mode, in which the port cannot initiate OAM packets. In this case, the port only responds to the OAM PDUs in the active mode transmitted by the opposite port.

25.1.3 Application of the Ethernet Port OAM

The Ethernet port OAM is mainly used to check the connectivity of the physical link between two Ethernet ports that are directly connected.

Remote Loopback
The Ethernet port OAM provides the remote loopback function. The local end can initiate or cancel the remote loopback. When the remote loopback is initiated, the PDU (protocol data unit) packets are transmitted to the opposite end. If the opposite end receives the PDU packets, and the opposite port, which can support the remote loopback, is in the OAM enabled state, the opposite port loops back all the Ethernet packets, excluding the OAM PDU packets and flow control frames. The remote loopback is initiated or cancelled only when the working state of the port is Active.

Application
The Ethernet port OAM is a method of checking the connectivity and performance of the physical link. As shown in Figure 25-1, the Ethernet port OAM is mainly used for customer layer, Ethernet ports that are directly connected through network cables. The end-to-end inter-NE check is not provided. Figure 25-1 Application scenario of the Ethernet port OAM
Access Layer P CE PE CE P P CE PSN P PE CE Access Layer

Custom Layer

Core Layer
LSP

Custom Layer

25.1.4 Querying the Remote OAM Parameters

To check the Ethernet by using the Ethernet OAM function, which is stipulated in IEEE 802.3ah, make sure that the OAM parameters are configured as the same for equipment at both ends of the Ethernet link. You can browse the remote OAM parameters to know the configuration of parameters at the remote equipment.
25-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. You must enable the IEEE 802.3ah OAM function at the remote equipment.

Procedure
Step 1 Click the NE in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Port OAM Management from the Function Tree. Step 2 Click the Remote OAM Parameter tab. Step 3 Select a port and click Query. A dialog box is displayed, indicating that the operation is successful. Click Close. ----End

25.1.5 Setting the OAM Parameters

Set the OAM parameters of the local equipment according to the parameter configuration of the remote equipment. In this way, functions such as the link event notification and remote loopback are available.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. You must enable the IEEE 802.3ah OAM function at the remote equipment.

Procedure
Step 1 Click the NE in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Port OAM Management from the Function Tree. Step 2 Click the OAM Parameter tab. Step 3 Select one port and set the OAM parameters of the port. Step 4 Click Apply. A dialog box is displayed, indicating that the operation is successful. Click Close. ----End

25.1.6 Setting OAM Error Frame Monitor Parameters

Set the OAM error frame monitor parameters to customize the performance threshold and performance monitor range of the link, and thus to facilitate the monitoring of the link performance.

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

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

25-5

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Ethernet OAM Management > Ethernet Port OAM Management from the Function Tree. Step 2 Click the OAM Error Frame Monitor tab. Step 3 Select a port and set the OAM parameters of the port.
NOTE

l l l

Error Frame Monitor Window: If the number of error frames on the link crosses the error frame monitor threshold in the specified error frame monitor time window, the performance event is reported. Error Frame Period Window: If the number of error frames on the link crosses the error frame period monitor threshold in the error frame period monitor window, the performance event is reported. Error Frame Second Window: If the number of error frame seconds on the link crosses the error frame second monitor threshold in the specified error frame second monitor time window, the performance event is reported. Error Frame Signal Periodic Monitor Window: In a specified number of signals, if the number of error signals on the link crosses the defined threshold, the performance event is reported.

Step 4 Click Apply. A dialog box is displayed, indicating that the operation was successful. Click Close. ----End

25.1.7 Starting the Remote Loopback

Perform the remote loopback to check the connectivity of the physical link and thus to locate and then rectify faults.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The two ports directly connected by the network cable must support the IEEE 802.3ah OAM. The OAM must be enabled at the local port and opposite port. The local working mode must be the active mode. The opposite must support the remote loopback.

l l

Procedure
Step 1 Click the NE in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Port OAM Management from the Function Tree. Step 2 Select the ports where you want to perform the remote loopback, click the OAM Parameter tab. Step 3 Choose OAM > Enable Remote Loopback. A dialog box is displayed, indicating that the operation is successful. Click Close.
NOTE

Loopback packets do not contain DCN packets.

----End
25-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

25.2 Configuring the Ethernet Service OAM

This section describes how to configure Ethernet service OAM.

Context
Ethernet service OAM configuration flow describes the operation tasks and their relations in the flow for configuring Ethernet OAM. See Figure 25-2. It is recommended to configure and manage Ethernet service OAM according to the Ethernet service OAM configuration flow. Figure 25-2 Ethernet OAM configuration flow
Required Optional Creating an MD Start

Creating an MA

Creating a MEP

Add a Remote MEP

Creating a MIP

Start CC Test

Start LB Test

Start LT Test

End

25.2.1 Overview of the Ethernet Service OAM The Ethernet service OAM, based on the Ethernet service traffic, is used to provide the automatic check, fault location and performance check for the connectivity of the Ethernet link.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 25-7

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

25.2.2 Basic Concepts The basic concepts of the Ethernet service OAM includes the maintenance domain, maintenance association, maintenance end point and maintenance intermediate point. 25.2.3 Application of the Ethernet Service OAM Ethernet service OAM includes three detection methods: CC, LB and LT. 25.2.4 Creating an MD Maintenance domain (MD) defines the range and level of Ethernet OAM. MDs of different ranges and levels can provide differential OAM services for users. 25.2.5 Creating an MA An maintenance domain (MD) can be divided into several independent maintenance associations (MA). By creating MAs, operators can associate specific Ethernet services with the MAs for easy Ethernet OAM operation. 25.2.6 Creating a MEP Maintenance Point Ethernet OAM detects the connectivity of an channel based on the maintenance end points (MEP) at two ends of the channel. MEP is the source and sink of all the Ethernet OAM packets and it is the end point that forms the maintenance association (MA). After an MEP is successfully created, users can check the connectivity of a segment within an MA. 25.2.7 Adding a Remote MEP of the MA This section describes how to add a remote maintenance end point (MEP) of the maintenance association (MA). When processing OAM packets, the remote MEP checks whether the OAM packets are transmitted by the MEP in the same MA. 25.2.8 Creating a Maintenance Intermediate Point A maintenance intermediate point (MIP) can respond to only specific OAM packets. By creating MIPs, you can perform an OAM detection to all spans of an MA. 25.2.9 Performing a Continuity Check You can perform a continuity check (CC) on Ethernet services to check the connectivity of services for fault location and repairing. 25.2.10 Performing an LB Test You can perform a loopback (LB) test on Ethernet services without interrupting the services, to check the connectivity of services for fault location and repairing. 25.2.11 Performing an LT Test You can perform a link trace (LT) test on Ethernet services to detect the MIP information in the link for fault location and repairing.

25.2.1 Overview of the Ethernet Service OAM

The Ethernet service OAM, based on the Ethernet service traffic, is used to provide the automatic check, fault location and performance check for the connectivity of the Ethernet link.

Objective and Benefits

With the growth of data services, more Ethernet services are applied to metropolitan area networks (MANs) and wide area networks (WANs). Therefore, the maintainability of Ethernet services gains increasing attention. Currently, the ways of Ethernet layer 2 maintenance are limited, and thus operating, managing, and maintaining Ethernet services over a transport network are restricted. The Ethernet service OAM has the following functions:
25-8 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

l l l l

25 OAM Management

Check the connectivity of the Ethernet service. Detect the faults of the Ethernet service. Locate the faults of the Ethernet service. Check the Ethernet performance events.

Compliant Standard and Protocol

The Ethernet service OAM complies IEEE 802.1ag and ITU-T Y.1731.
l l

IEEE 802.1ag Connectivity Fault Management (CFM) ITU-T Y.1731 OAM functions and mechanisms for Ethernet based networks

25.2.2 Basic Concepts

The basic concepts of the Ethernet service OAM includes the maintenance domain, maintenance association, maintenance end point and maintenance intermediate point. As a protocol based on the MAC layer, the Ethernet service OAM detects Ethernet links by transmitting OAM packets. The OAM packets are processed at only the MAC layer. The Ethernet service OAM defines the following concepts:
l

Maintenance domain (MD): The MD is a network that requires the OAM. An important attribute of the MD is level, which restricts the range of OAM operations. The MD can be embedded but not overlapped. A basic idea of OAM packet operations is the low level block, high level transparent transmission, and current level processing. Maintenance association (MA): The MA can be considered as a service-related domain, which consists of many maintenance end points (MEPs). Maintenance end point (MEP): The MEP is the transmitting and terminating points of all OAM packets. It is relevant to services. The MEP has a unique MEP ID in the MA. In a network, the MA and MEP ID can uniquely determine an MEP. Maintenance intermediate point (MIP): The MIP is relevant to the MD but irrelevant to the MA. The MIP can respond to and forward LB and LT packets, but can only forward CC packets.

Figure 25-3 shows the relation among the MD, MA, MEP, and MIP. Two MAs, which respectively belong to two MDs with the priorities of 5 and 3, are available. These two MDs form a nested relation. Two PE nodes perform as the MEP and MIP in the two MDs respectively.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

25-9

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 25-3 Relation among the MD, MA, MEP, and MIP
CE PE PE CE

Packet Switching Network

Customer MD Level 5 Service Provider MD Level 3 3 5

3 5

MEP (number is MD Level) MIP

MA

In this figure, two MD application scenarios are described: 1. 2. MD for customers: Create an MEP on NE CE, and create an MIP on the V-UNI of NE PE. In this way, you can detect the entire link that carries customer services. MD for carriers: Create an MEP on the V-UNI of NE PE. In this way, you can neglect the link quality on the user access side but focus on the network of carriers.

25.2.3 Application of the Ethernet Service OAM

Ethernet service OAM includes three detection methods: CC, LB and LT.

CC
Perform unidirectional connectivity check (CC). The source MEP regularly forms and sends CC frames. After receiving the CC frames sent by the source MEP, the sink MEP directly enables the CC detection function. If the sink MEP fails to receive the CC frames from the source end within a certain period of time, commonly 3.5 times the regular period, it automatically reports the ETH_CFM_LOC alarm. See Figure 25-4. Figure 25-4 CC detection
CC CC

MEP

MIP

MIP

MIP

MIP

MEP

25-10

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

LB
Perform the loopback (LB) detection. The source MEP forms and sends LB management frames and enable the timer for timing. If the sink MEP receives the LB management frames, it forms and sends LBR frames back to the source MEP. The loopback succeeds. If the timer times out at the source MEP, the loopback fails. See Figure 25-5. Figure 25-5 LB detection
LBR LBM MEP

MIP

MIP

MIP

MIP

MEP

LT
Perform the link trace (LT) detection. The source MEP forms and sends LT management frames and enable the timer for timing. All the MEPs and MIPs on the link send LTR frames back to the source end after receiving LT management frames. Moreover, all the MIPs can forward LTM frames. Based on the LTR frames, the number of MIPs on a link from the source MEP to the sink MEP can be determined. If the timer times out at the source MEP, the LT fails. See Figure 25-6. Figure 25-6 LT detection
LTR LTM MEP LTM MIP LTR LTM MIP LTR LTM MIP LTR LTM MIP LTR LTM MEP

Application
As Ethernet service OAM provides end-to-end detection methods for specific services, it is mainly applied to the core layer. See Figure 25-7.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

25-11

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 25-7 Application Scenarios of Ethernet Service OAM

Access Layer P CE PE CE P P CE PSN P PE CE Access Layer

Custom Layer

Core Layer
LSP

Custom Layer

Table 25-1 lists different application scenarios of the CC, LB and LT. Table 25-1 Application scenarios of Ethernet OAM OAM Type CC LB LT Usage Unidirectional connectivity check Bidirectional connectivity check Fault location Application Scenario Real-time detection of the link state Fault location or detection at a single end On-site fault location

25.2.4 Creating an MD
Maintenance domain (MD) defines the range and level of Ethernet OAM. MDs of different ranges and levels can provide differential OAM services for users.

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

Procedure
Step 1 In the NE Explorer interface, select an NE, and choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Step 2 Click New. Select New Maintenance Domain to display the New Maintenance Domain dialog box.
25-12 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

Step 3 Configure Maintenance Domain Name and Maintenance Domain Level.

NOTE

When configuring parameters, note the following: Maintenance Domain Level: 0-7 (7: highest priority)

Step 4 Click Apply. The Operation Result dialog box is displayed, indicating that the operation was successful. Step 5 Click Close. ----End

25.2.5 Creating an MA
An maintenance domain (MD) can be divided into several independent maintenance associations (MA). By creating MAs, operators can associate specific Ethernet services with the MAs for easy Ethernet OAM operation.

Prerequisite
l l l

You must be an NM user with "NE operator" authority or higher. Ethernet services must be already created. The MD must be created.

Procedure
Step 1 In the NE Explorer interface, select an NE, and choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Step 2 Click New. Select New Maintenance Association to display the New Maintenance Association dialog box.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

25-13

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 3 Click

to display the Select Service dialog box. Select the service and Click OK.

Step 4 Set the parameters.

NOTE

Take the following precautions when setting the parameters.

l

CC Test Transmit Period: It indicates the period of a CC test and is optional.

Step 5 Click Apply. The Operation Result dialog box is displayed, indicating that the operation was successful. Step 6 Click Close. ----End

25.2.6 Creating a MEP Maintenance Point

Ethernet OAM detects the connectivity of an channel based on the maintenance end points (MEP) at two ends of the channel. MEP is the source and sink of all the Ethernet OAM packets and it is the end point that forms the maintenance association (MA). After an MEP is successfully created, users can check the connectivity of a segment within an MA.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The MA must be already created.

Procedure
Step 1 In the NE Explorer interface, select an NE, and choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Step 2 Click New. Select New MEP Point to display the New MEP Maintenance Point dialog box.

25-14

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

Step 3 Set the parameters.

NOTE

Take the following precautions when setting each parameter.

l l

Direction: Ingress indicates that packets are transported to the network side. Egress indicates that packets are transported to the user side. CC Status: When it is set as Active, the link can be checked in a real-time manner.

Step 4 Click Apply. The Operation Result dialog box is displayed, indicating that the operation was successful. Step 5 Click Close. ----End

25.2.7 Adding a Remote MEP of the MA

This section describes how to add a remote maintenance end point (MEP) of the maintenance association (MA). When processing OAM packets, the remote MEP checks whether the OAM packets are transmitted by the MEP in the same MA.

Prerequisite
l l

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Step 2 Click OAM and choose Manage Remote MEP Point from the drop-down menu. The Manage Remote Maintenance Point dialog box is displayed. Step 3 Click New and the Add Maintenance Association Remote Maintenance Point dialog box is displayed.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 25-15

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 4 Set the parameters. Step 5 Click Apply. The Operation Result dialog box is displayed, indicating that the operation is successful. Step 6 Click Close. ----End

25.2.8 Creating a Maintenance Intermediate Point

A maintenance intermediate point (MIP) can respond to only specific OAM packets. By creating MIPs, you can perform an OAM detection to all spans of an MA.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. A maintenance domain must be created.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Step 2 Click MIP Point and click New. The New MIP Maintenance Point dialog box is displayed.

Step 3 Set the parameters. Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful.
25-16 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

Step 5 Click Close. ----End

25.2.9 Performing a Continuity Check

You can perform a continuity check (CC) on Ethernet services to check the connectivity of services for fault location and repairing.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. An OAM maintenance node must be created.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Step 2 Select Maintenance Domain, and select Maintenance Association. Select MEP Point. Step 3 Click OAM and choose Activate CC from the drop-down menu, The Operation Result dialog box is displayed indicating that the operation is successful. Step 4 Click Close. ----End

25.2.10 Performing an LB Test

You can perform a loopback (LB) test on Ethernet services without interrupting the services, to check the connectivity of services for fault location and repairing.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. An OAM maintenance node must be created.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Step 2 Select Maintenance Domain, and select Maintenance Association. Select MEP Point. Step 3 Click OAM and choose Start LB from the drop-down menu. The LB Test dialog box is displayed. Step 4 Set the parameters.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

25-17

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 5 Click Start Test. The Operation Result dialog box is displayed, indicating that the operation is successful. Step 6 Click Close. View the test result. ----End

25.2.11 Performing an LT Test

You can perform a link trace (LT) test on Ethernet services to detect the MIP information in the link for fault location and repairing.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. An OAM maintenance node must be created.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Step 2 Select Maintenance Domain, and select Maintenance Association. Select MEP Point. Step 3 Click OAM and choose Start LT from the drop-down menu. The LT Test dialog box is displayed. Step 4 Set the parameters.
25-18 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

Step 5 Click Start Test. The Operation Result dialog box is displayed, indicating that the operation is successful. Step 6 Click Close. View the test result. ----End

25.3 Configuring the MPLS OAM

You can configure the MPLS OAM. 25.3.1 Overview of the MPLS OAM Based on the MPLS OAM mechanism, you can effectively detect, confirm, and locate internal defects from the network of the MPLS layer. The equipment uses the OAM detection state to trigger the protection switching. As a result, fast fault detection and service protection can be realized. The monitoring of network performance includes packet loss ratio, delay and delay variation. Thus, a carrier-class quality of service (QoS) in a packet transport network (PTN) can be ensured. 25.3.2 Basic Concepts The basic concepts of MPLS OAM include CV/FFD, Ping and Traceroute. 25.3.3 Application of the MPLS OAM MPLS OAM provides end-to-end detection methods in the MPLS network. 25.3.4 Enabling the MPLS OAM of a Tunnel You need to enable the OAM function of the corresponding tunnel before performing the MPLS OAM operation. 25.3.5 Setting the MPLS OAM Parameters of a Tunnel
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 25-19

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

Based on different MPLS OAM parameters, the MPLS OAM operation results are different. You need to set the MPLS OAM parameters before performing the MPLS OAM operation. 25.3.6 Starting the CV/FFD for a Tunnel You can test the unidirectional connectivity of a tunnel by performing a connectivity verification (CV)/fast failure detection (FFD). 25.3.7 Performing an LSP Ping Test You can check whether a label switch path (LSP) is successfully created by performing an LSP ping test. 25.3.8 Performing an LSP Traceroute Test You can locate the place where a fault occurs by performing an LSP traceroute test.

25.3.1 Overview of the MPLS OAM

Based on the MPLS OAM mechanism, you can effectively detect, confirm, and locate internal defects from the network of the MPLS layer. The equipment uses the OAM detection state to trigger the protection switching. As a result, fast fault detection and service protection can be realized. The monitoring of network performance includes packet loss ratio, delay and delay variation. Thus, a carrier-class quality of service (QoS) in a packet transport network (PTN) can be ensured.

Objectives and Benefits

The MPLS is a key carrying technology of the extended next generation network (NGN). This technology provides a QoS-ensured multi-service capability and introduces a unique network layer, which may cause some faults. Therefore, an MPLS network must have the OAM capability. The MPLS supports many layer 3 and layer 2 protocols, such as the IP, ATM, and Ethernet protocols. By providing an OAM mechanism independent of any upper layer or lower layer, the MPLS OAM supports the following features:
l

Provide the query based on requirements and the consecutive detection so that at any moment you can learn whether the monitored LSP has defects. Detect, analyze, and locate any defect that occurs, and notify the T2000 of the relevant information. Trigger a protection switching immediately after a defect or fault occurs on a link. Performance events indicating packet loss ratio, delay and delay variation are monitored in time and reported to the T2000.

l l

Compliant Standard and Protocol

The MPLS OAM complies ITU-T Y.1711 and ITU-T Y.1731.
l l

ITU-T Y.1711 Operation & Maintenance mechanism for MPLS networks ITU-T Y.1731 OAM functions and mechanisms for Ethernet based networks

25.3.2 Basic Concepts

The basic concepts of MPLS OAM include CV/FFD, Ping and Traceroute.
25-20 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

CV/FFD
You can check the connectivity of a label switch path (LSP) by performing a connectivity verification (CV) or fast failure detection (FFD). The process of a CV is consistent with that of an FFD. The difference lies in that the CV transmits CV packets at the frequency of 1 frame per second and the frequency cannot be set, but the FFD transmits FFD packets at a frequency that can be self-defined. Figure 25-8 shows the process of a CV and an FFD. Figure 25-8 Connectivity check of the MPLS OAM
Transit LSR
CV/FFD

Transit LSR
CV/FFD CV/FFD

Transit LSR
CV/FFD

Ingress LSR

Egress LSR
BDI

BDI

Transit LSR

BDI

BDI

Transit LSR

Transit LSR

1. 2.

The ingress node transmits CV or FFD packets, and the transit node transparently transmits packets. The packets reach the egress node through the detected LSP. The egress node compares the received information fields, such as packet type, frequency, and TTSI, with the fields recorded in the local to check the correctness of the packets. It also performs statistics to the numbers of correct packets and incorrect packets during the detection period, which is 3s for a CV and three times as long as the transmission period for an FFD. In this way, the connectivity of an LSP is monitored in real time. When detecting a defect of the LSP, the egress node analyzes the defect type, and then transmits the backward defect indication (BDI) packets that carry the defect information to the ingress node through a reverse channel so that the ingress node can learn the defect status in time. If a protection group is correctly configured, the corresponding protection switching is also triggered.

3.

When configuring basic detection functions of the OAM, you can bind a reverse channel for the detected LSP. The reverse channel is an LSP that has opposite ingress and egress nodes to the detected LSP, or is a non-MPLS path that can connect to the ingress and egress nodes of the detected LSP. The reverse channel that carries BDI packets can be one of the following types:
l

Dedicated reverse LSP: Each forward LSP has a corresponding reverse LSP. This method is relatively stable but may waste resources. Shared reverse LSP: Many forward LSPs share a reverse LSP. All LSPs return BDI packets through this reverse LSP. This method saves resources, but a congestion may occur on the reverse LSP when many forward LSPs have defects at the same time.

At present, only the dedicated reverse LSP is supported.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

25-21

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

Ping/Traceroute
In MPLS, if the LSP fails to forward data, the MPLS control plane responsible for constructing the tunnel cannot detect this fault. Thus, the network maintenance is difficult. The MPLS Ping/ Traceroute provides a mechanism for detecting the LSP faults and locating the invalid nodes in a timely manner. The MPLS Ping/Traceroute uses the MPLS Echo Request and MPLS Echo Reply to detect the usability of the LSP. The MPLS Echo Request carries the information of the forwarding equivalence class (FEC) for detection, which is transmitted along the LSP with other packets belonging to this FEC. In this way, the LSP is checked.
l

The MPLS Ping and Echo Request messages should reach the Egress node of the tunnel. Then, the control plane of the Egress node determines whether this node is the Egress of this FEC. Whether the LSP is successfully created can be checked by the MPLS Ping. The MPLS Traceroute and Echo Request messages should be transmitted to each Transit node. The control plane of the Transit node determines whether the local node is an intermediate node on this path. The location of the network fault can be determined through the Traceroute function.

25.3.3 Application of the MPLS OAM

MPLS OAM provides end-to-end detection methods in the MPLS network. MPLS OAM is mainly applied to the LSP of the core layer in the PSN network. See Figure 25-9. Figure 25-9 Application scenarios of MPLS OAM
Access Layer P CE PE CE P P CE PSN P PE CE Access Layer

Custom Layer

Core Layer
LSP

Custom Layer

Table 25-2 lists different application scenarios of the CV/FFD, Ping and Traceroute.

25-22

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

Table 25-2 Application scenarios of MPLS OAM detection methods OAM Type CV/FFD Ping Traceroute Usage Unidirectional connectivity check Unidirectional connectivity check Fault location Application Scenario Real-time detection of the tunnel state Fault location or detection at a single end Tunnel route detection

25.3.4 Enabling the MPLS OAM of a Tunnel

You need to enable the OAM function of the corresponding tunnel before performing the MPLS OAM operation.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. An MPLS tunnel must be created.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the OAM Parameters tab. In the OAM Status area, click Enabled. Step 3 Click Apply. The Operation Result dialog box is displayed indicating that the operation is successful. Step 4 Click Close. ----End

25.3.5 Setting the MPLS OAM Parameters of a Tunnel

Based on different MPLS OAM parameters, the MPLS OAM operation results are different. You need to set the MPLS OAM parameters before performing the MPLS OAM operation.

Prerequisite
l l l

You must be an NM user with "NE operator" authority or higher. An MPLS tunnel must be created. You must enable the Tunnel OAM function.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 25-23

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 2 Select the tunnel, click the OAM Parameters tab and set the parameters.
NOTE

Note the following during parameter settings:

l

Detection Packet Period: When the Detection Packet Type is set to CV, the Detection Packet Period is 1 s and cannot be set. When the Detection Packet Type is set to FFD, the Detection Packet Period can be set. Reverse Tunnel: Send the BDI packets that carry the defect information to the ingress node so that the ingress node can learn the defect status in time. When the Tunnel Type is set to Egress, you can set the SD Threshold and SF Threshold. The SD Threshold is smaller than or equal to the SF Threshold.

l l

Step 3 Click Apply. The Operation Result dialog box is displayed, indicating that the operation is successful. Step 4 Click Close. ----End

25.3.6 Starting the CV/FFD for a Tunnel

You can test the unidirectional connectivity of a tunnel by performing a connectivity verification (CV)/fast failure detection (FFD).

Prerequisite
l l l

You must be an NM user with "NE operator" authority or higher. An MPLS tunnel must be created. You must enable the MPLS OAM function.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the OAM Parameters tab and select a tunnel. Click OAM Operation and choose Start CV/FFD from the drop-down menu. The Operation Result dialog box is displayed, indicating that the operation is successful.

NOTE

When the Node Type of the tunnel is Ingress, the CV/FFD can be enabled.

25-24

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

Step 3 Click Close. ----End

25.3.7 Performing an LSP Ping Test

You can check whether a label switch path (LSP) is successfully created by performing an LSP ping test.

Prerequisite
l l l

You must be an NM user with "NE operator" authority or higher. An MPLS tunnel must be created. In the case of a static MPLS tunnel, enable the IS-IS protocol at both the source and sink ports of the MPLS tunnel, for details, see 8.2.2 Setting Port Attributes. Also, you can start a ping test at the local end and configure a static route on the opposite NE.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the OAM Parameters tab and select a tunnel. Click OAM Operation and choose Ping Test from the drop-down menu. The Ping Test dialog box is displayed.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

25-25

25 OAM Management
NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

When the Node Type of the tunnel is Ingress, you can perform the ping test.

Step 3 Set the parameters. Step 4 Click Start Test. View the ping test result. ----End

25.3.8 Performing an LSP Traceroute Test

You can locate the place where a fault occurs by performing an LSP traceroute test.

Prerequisite
l l l

You must be an NM user with "NE operator" authority or higher. An MPLS tunnel must be created. In the case of a static MPLS tunnel, enable the IS-IS protocol at both the source and sink ports of the MPLS tunnel. Also, you can start a ping test at the local end and configure a static route on the opposite NE.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the OAM Parameters tab and select a tunnel. Click OAM Operation and choose Traceroute Test from the drop-down menu. The Traceroute Test dialog box is displayed.

25-26

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

25 OAM Management

To support the traceroute test, the Tunnel Type of the tunnel must be Ingress.

Step 3 Set the parameters. Step 4 Click Start Test and view the traceroute test result. ----End

25.4 Configuring the PW OAM

This section describes how to configure the PW OAM. 25.4.1 Overview of the PW OAM As an mechanism for maintaining and managing PWs, PW OAM detects the connectivity of PWs by using ping packets. 25.4.2 Basic Concepts The basic concept of the PW OAM is Ping. 25.4.3 Application of the PW OAM The PW OAM provides end-to-end detection at the PW layer. 25.4.4 Performing the PW Ping Test By performing the PW Ping test, you can check whether the PW runs normally.

25.4.1 Overview of the PW OAM

As an mechanism for maintaining and managing PWs, PW OAM detects the connectivity of PWs by using ping packets.

Objectives and Benefits

The OptiX PTN equipment encapsulates service packets into PWs and then transmits the services over a tunnel. On the PTN, there are two layers, that is, tunnel layer and PW layer. The MPLS tunnels can be maintained and managed by MPLS OAM. The PWs can be maintained and managed by PW OAM. Currently, the OptiX PTN equipment can detect the connectivity of a PW by using the PW packets and can report the detection result to the T2000. The local equipment encapsulates the ping packets into PWs and then transmits the packets over a tunnel. When receiving the over-tunnel packets, the opposite equipment decapsulates the packets, processes the packets, and responds to the packets. Then, the opposite equipment transmits the response packets back to the local equipment. In this manner, the local equipment determines the connectivity of the PW according to whether it can receive the response packets from the opposite equipment.

Compliant Standards and Protocols

The PW OAM complies with the RFC 4379 Detecting MPLS Data Plane Failures.

25.4.2 Basic Concepts

The basic concept of the PW OAM is Ping.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 25-27

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

Ping
PW Ping is a tool for manually checking the connection status of virtual circuits, which is similar to the LSP Ping. When the PW fails to forward data, the control plane that is responsible to create the PW cannot detect this fault. This makes the network maintenance difficult. PW Ping provides the mechanism of detecting faults of PWs to users. During the PW forwarding, the Ping packets are encapsulated into the PW at the ingress and are transmitted along the virtual circuit. Thus, the PW is checked.

25.4.3 Application of the PW OAM

The PW OAM provides end-to-end detection at the PW layer. The main detection method of the PW OAM is PW Ping, as shown in Figure 25-10. Between NE1 and NE2, a CES service that is carried by a PW exists. NE1 initiates the PW Ping test. You can view the test result and check the running status of the PW. Figure 25-10 Application scenario of the PW OAM

IMA

CES PW NE1 PW ping NE2

ATM STM-1

NodeB

RNC

25.4.4 Performing the PW Ping Test

By performing the PW Ping test, you can check whether the PW runs normally.

Prerequisite
l l l

You must be an NM user with "NE operator" authority or higher. The PW that carries services must be created. In the case of a static MPLS tunnel, enable the IS-IS protocol at both the source and sink ports of the MPLS tunnel. Also, you can start a ping test at the local end and configure a static route on the opposite NE.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > MPLS Management > PW Management from the Function Tree. Step 2 Right-click a PW and choose PW Ping Test from the shortcut menu. The Ping Test dialog box is displayed.

25-28

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

Step 3 Configure corresponding parameters.

NOTE

A PW can only initialize a Ping test at a time. The value of Packet length ranges from 64 to 1400. If the value is not within the range, the Ping fails. When service type is set to Ethernet, the PW Ping test is not supported on the PTN 912 equipment.

Step 4 Click Start Test. View the Ping test result. ----End

25.5 Configuring ATM OAM

How to use the T2000 to configure ATM OAM is described. 25.5.1 Overview of the ATM OAM The ATM OAM is an end-to-end OAM function for services. It can detect the quality of an ATM link that transits multiple NEs. 25.5.2 Basic Concepts This section describes basic concepts about the ATM OAM. 25.5.3 Application of the ATM OAM
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 25-29

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

ATM OAM includes two detection methods: CC and LB. 25.5.4 Setting Segment End Attribute You need to set the segment end attribute of the port before performing ATM OAM maintenance. The segment end attributes determines how the port handles the OAM cell. 25.5.5 Setting the CC Activation Status You can perform continuity check (CC) on the ATM service to check the continuity of the service for troubleshooting. 25.5.6 Setting Remote Loopback Test You can perform remote loopback (LB) check on the ATM service without interrupting the service. In this way, you can check the connectivity of the service for troubleshooting. 25.5.7 Setting Local Loopback ID You must set the local loopback ID (LLID) for an NE before performing the loopback (LB) test on it.

25.5.1 Overview of the ATM OAM

The ATM OAM is an end-to-end OAM function for services. It can detect the quality of an ATM link that transits multiple NEs.

Objective and Benefits

As an OAM function based on the ATM layer, the ATM OAM supports the following functions:
l l l

Verify the connectivity of ATM services. Detect faults. Locate faults.

Compliant Standard and Protocol

The ATM OAM complies with the ITU-T I.610 recommendations-B-ISDN operation and maintenance principles and functions.

25.5.2 Basic Concepts

This section describes basic concepts about the ATM OAM. You can use the ATM OAM function to detect an ATM link by inserting OAM cells with standard cell structure into the user cell flow. In an ATM network, the OAM function is classified into five layers. See Table 25-3. Table 25-3 Classification of the OAM function layers Layer F1: regenerator section layer F2: digital section layer Description Physical layer OAM: The physical layer OAM flow depends on the transmission mechanism of a specific transmission system. An ATM network contains the following three types of transmission mechanisms: 1. SDH-based transmission system
Issue 01 (2009-06-30)

25-30

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

Layer F3: transmission channel layer

Description 2. Cell-based transmission system 3. PDH-based transmission system

F4: virtual path (VP) layer F5: virtual channel (VC) layer

ATM OAM: The ATM OAM is based on the VP/VC and independent of the transmission system.

At the ATM layer, the operation flows of F4 and F5 are defined. The F4 flow is an OAM cell flow in the virtual path connect (VPC) and provides the operation management and maintenance functions of the VP level. The F5 flow is an OAM cell flow in the virtual channel connect (VCC) and provides the operation management and maintenance functions of the VC level. After the OAM is activated at the F4 and F5, the specific OAM cell is inserted into user cells. As a result, the functions of continuity check (CC) and loopback (LB) check without service interruption are realized. The ATM OAM defines the following concepts:
l l l l

Endpoint: Only the OAM cells at the end can be terminated. Segment point: Only the OAM cells at the segment can be terminated. Segment and Endpoint: The OAM cells at the segment and end can be terminated. Non segment and Endpoint: The OAM cells are not terminated.
NOTE

Endpoint and Segment and Endpoint are not available for the OptiX PTN 912.

25.5.3 Application of the ATM OAM

ATM OAM includes two detection methods: CC and LB. As ATM OAM provides end-to-end detection methods for specific services, it is mainly applied to the CE and PE NEs that ATM services pass. See Figure 25-11. In the case of the UNIs-NNI ATM service, you can check the service connectivity between the UNI and the NNI. In the case of the UNI-UNI ATM service, you can check the service connectivity between the two UNIs.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

25-31

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 25-11 Application scenarios of ATM OAM

Access Layer P CE PE CE P P CE PSN P PE CE Access Layer

Custom Layer

Core Layer
LSP

Custom Layer

CC
After the CC detection function at the source end and sink end is enabled, the source end regularly forms and sends CC cells. If the sink end fails to receive CC cells from the source end within thirty seconds, it automatically reports the LOC alarm and inserts the corresponding AIS cells to the downstream.

LB
Perform the remote loopback (LB) detection. The source end forms and sends LB cells and enable the timer for timing. If the sink end receives the LB cells, it sends the cells back to the source end. If the source end detects the returned LB cells within the given time, the loopback succeeds; otherwise, the loopback fails. Table 25-4 lists different application scenarios of the CC and LB. Table 25-4 Application scenarios of ATM OAM detection methods OAM Type CC LB Usage Unidirectional connectivity check Bidirectional connectivity check Application Scenario Real-time detection of the link state Fault location or detection at a single end

25.5.4 Setting Segment End Attribute

You need to set the segment end attribute of the port before performing ATM OAM maintenance. The segment end attributes determines how the port handles the OAM cell.
25-32 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The ATM service must be created and activated.

Context
The segment end attribute of a port contains Segment point, Endpoint, Segment and Endpoint, and Non segment and Endpoint. The ways that the port handles the OAM cell in different segment end attributes are described as follows:
l

If the segment end attribute is set to Endpoint, only the OAM cell at the end can be terminated. If the segment end attribute is set to Segment point, only the OAM cell at the segment can be terminated. If the segment end attribute is set to Segment and Endpoint, the OAM cells at the segment and end can be terminated. If the segment end attribute is set to Non segment and Endpoint, the OAM cell is not terminated.

CAUTION
You cannot set OAM segment endpoint or activate CC at the protection connection to which 1 +1 source or 1+1 sink protection group is applied. You cannot set segment end attribute at the connection that is added to a protection group.

Procedure
Step 1 In the NE Explore, select the NE and choose Configuration > ATM OAM Management . Step 2 Set the Segment and End Attribute of the port. Step 3 Click Apply and then click Close in the Operation Result dialog box. ----End

25.5.5 Setting the CC Activation Status

You can perform continuity check (CC) on the ATM service to check the continuity of the service for troubleshooting.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. Segment end attribute of the port must be set.

Context
After you activate the CC check at the source and sink ends of a service, the source ends periodically builds and sends a CC cell. If the sink end does not receive the CC cell from the
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 25-33

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

source in 3-4 seconds, it automatically reports a CCLOS alarm and inserts an e-to-e_VP_AIS alarm to the downstream.

CAUTION
When activating the CC, you need to activate the source and sink ends almost at the same time in a short period. You are recommended to activate the sink first and then the source. Otherwise, the NE may report timeout.

Procedure
Step 1 In the NE Explore, select the NE and choose Configuration > ATM OAM Management . Click the CC Activation Status tab. Step 2 Set the CC Activate Flag of the port and the Segment and End Attribute of the CC cell.
NOTE

l l

Segment and End Attribute sets the segment end attribute of the CC cell. It corresponds to the segment end attribute of the port. The CC cell terminates at the port of the same segment attribute. After the CC Activate Flag is activated, the CC check is started.

Step 3 Click Apply and then click Close in the Operation Result dialog box. ----End

25.5.6 Setting Remote Loopback Test

You can perform remote loopback (LB) check on the ATM service without interrupting the service. In this way, you can check the connectivity of the service for troubleshooting.

Prerequisite
l l l

You must be an NM user with "NE operator" authority or higher. Segment end attribute must be set. The LLID of the remote loopback node must be configured.

Context
During the remote loopback check, the source end builds a LB cell, sends the cell and starts the timer. If the sink end receives the LB cell, it sends the cell back to the source. If the source end detects the returned LB cell in a specified time, the loopback is successful. Otherwise, the loopback fails.

Procedure
Step 1 In the NE Explore, select the NE and choose Configuration > ATM OAM Management . Click the Remote Loopback Test tab. Step 2 Set the Loopback Point NE and Segment and End Attribute. Step 3 Click Test to start the remote loopback test.
25-34 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

Step 4 Click Test Result to view the test result. ----End

25.5.7 Setting Local Loopback ID

You must set the local loopback ID (LLID) for an NE before performing the loopback (LB) test on it.

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

Context
The LB test recognizes an NE by LLID, so the LLID must be unique in the network. After the LLID is set for an NE, the LLID value is sent to all the boards to keep consistency of LLID values on all the boards.

Procedure
Step 1 In the NE Explore, select the NE and choose Configuration > ATM OAM Management . Click the LLID tab. Step 2 Set the Country Code, Network Code, and NE Code. Step 3 Click Apply and then click Close in the Operation Result dialog box. ----End

25.6 Configuration Case of the Ethernet Port OAM

The configuration case of the Ethernet port OAM describes how to configure the Ethernet port OAM. 25.6.1 Case Description Ethernet OAM is an OAM function for physical links. The Ethernet OAM checks the connectivity of the physical links between two ports directly connected by network cables. 25.6.2 Service Planning According to engineering requirements, the engineering department makes engineering planning and then outputs the detailed planning information. 25.6.3 Configuration Process This topic describes the configuration process of the Ethernet port OAM in the configuration case.

25.6.1 Case Description

Ethernet OAM is an OAM function for physical links. The Ethernet OAM checks the connectivity of the physical links between two ports directly connected by network cables.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

25-35

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

Networking and Requirement

As shown in Figure 25-12, NE1 and NE3 carry the Ethernet services of Company A and Company B. NE 1 uses the OptiX OSN 1900 to provide the access at the user side. NE 2 and NE 3 use the OptiX OSN 3900 to provide the transmission at the network side. Set the OAM parameters of ports among NE1, NE2, and NE3 and perform the remote loopback on NE2 to detect the NE link status. Figure 25-12 Networking of the Ethernet port OAM

NE4 NE5 Access layer

20-EFF8-1(Port-1) 10.0.0.2 3-EFF8-3(Port-3) 10.0.0.1 3-EFF8-2(Port-2)

10GE ring on convergence layer

5-EX2-1(Port-1) 10.0.1.2

NE3
20-EFF8-2(Port-2)

NE1
3-EFF8-1(Port-1)

NE2

5-EX2-1(Port-1) 10.0.1.1 20-EFF8-1(Port-1)

Company B Company A Company B Company A

25.6.2 Service Planning

According to engineering requirements, the engineering department makes engineering planning and then outputs the detailed planning information. The service shown in Figure 25-12 is taken as an example. You need to check the connectivity of physical links between NE1 and NE2 and between NE2 and NE3. Table 25-5 lists the OAM parameters of Ethernet ports on each NE. Table 25-5 NE parameter list Attribute OAM Paramet er Port NE1 3-EFF8-1(PORT-1) NE2 20-EFF8-1(PORT-1) 5-EX2-1(PORT-1) Enable OAM Protocol OAM Working Mode Enabled Enabled Enabled NE3 5-EX2-1(PORT-1)

Active

Active

Active

25-36

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

Attribute Link Event Notificat ion Remote Side Loopbac k Respons e OAM Error Frame Monitor Port

NE1 Enabled

NE2 Enabled

NE3 Enabled

Enabled

Enabled

Enabled

3-EFF8-1(PORT-1)

20-EFF8-1(PORT-1) 5-EX2-1(PORT-1)

5-EX2-1(PORT-1)

Error Frame Monitor Window (ms) Error Frame Monitor Threshol d (frame) Error Frame Period Window (frame) Error Frame Period Threshol d (frame) Error Frame Second Window (s) Error Frame Second Threshol d (s)

1000

1000

1000

1488000

1488000

1488000

60

60

60

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

25-37

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

Attribute Error Frame Signal Periodic Monitor Window (Entries) Error Frame Signal Periodic Monitor Threshol d (Entries)

NE1 1

NE2 1

NE3 1

25.6.3 Configuration Process

This topic describes the configuration process of the Ethernet port OAM in the configuration case.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must understand the networking, requirements and service planning of the example.

Procedure
Step 1 Configure the Ethernet port OAM among NE1, NE2, and NE3. 1. 2. In the NE Explorer, click the NE1 and choose Configuration > Ethernet OAM Management > Ethernet Port OAM Management. Choose the OAM Parameter tab, configure the related parameters and click Apply. The following OAM parameters of NE1 should be configured.
l l l

Port: 3-EFF8-1(Port-1) Enable OAM Protocol: Enabled OAM Working Mode: Active (When the port works in the active mode, the port can start the OAM packets.) Link Event Notification: Enabled (If the performance events cross the threshold at the local port, the local port notifies the opposite port by using the link events.) Remote Side Loopback Response: Enabled (Indicates the response to the enabling of remote loopback. OAM packets of the opposite port can be responded.) Port: 3-EFF8-1(Port-1)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

The following OAM error frame monitoring parameters of NE1 should be configured.
l

25-38

OptiX iManager T2000 Operation Guide for PTN NE Management

l l

25 OAM Management

Error Frame Monitor Window (ms) : 1000 Error Frame Monitor Threshold (frame): 1 (An alarm is reported if Error Frame Monitor Window (ms) is one more than Error Frame Monitor Threshold (frame) within 1000 ms.) Error Frame Period Window (frame): 1488000 Error Frame Period Threshold (frame): 1 (An alarm is reported if the number of Error Frame Period Window (frame) is one more than Error Frame Period Threshold (frame) within 1,488,000 frames.) Error Frame Second Window (s): 60 Error Frame Second Threshold (s): 1 (An alarm is reported if Error Frame Second Window (s) is one second more than Error Frame Second Threshold (s) within 60 seconds.) Error Frame Signal Periodic Monitor Window (Entries): 1 Error Frame Signal Periodic Monitor Threshold (Entries) : 1 (An alarm is reported if Error Frame Signal Periodic Monitor Window (Entries) is one more than Error Frame Signal Periodic Monitor Threshold (Entries) within a monitoring period.)

l l

l l

l l

3.

Refer to Step 1.1 to Step 1.2 to configure the OAM parameters of 20-EFF8-1(Port-1) and 5-EX2-1(Port-1) of NE2 and 5-EX2-1(Port-1) of NE3. The related parameters must be the same as those of NE1.

Step 2 On NE2, configure the remote loopback test. 1. 2. In the NE Explorer, click the NE2 and choose Configuration > Ethernet OAM Management > Ethernet Port OAM Management. Choose the OAM Parameter tab, click the OAM button, choose Enable Remote Loopback.
NOTE

Enable the remote loopback on NE2 to check the connectivity of physical links between NE2 and NE1 and between NE2 and NE3. Alternatively, you can perform this operation on NE1 and NE3.

----End

25.7 Configuration Case of the Ethernet Service OAM

The configuration case of the Ethernet service OAM describes how to configure the Ethernet OAM. 25.7.1 Case Description The Ethernet service OAM is an end-to-end OAM function for services. This function can check the quality of Ethernet links that involves multiple NEs. The test methods include CC (connectivity check), LB (loopback), and LT (link trace). 25.7.2 Service Planning Two services from Company A and Company B correspond to two maintenance associations. 25.7.3 Configuration Process This topic describes the configuration process of the Ethernet service OAM in the configuration case.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

25-39

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

25.7.1 Case Description

The Ethernet service OAM is an end-to-end OAM function for services. This function can check the quality of Ethernet links that involves multiple NEs. The test methods include CC (connectivity check), LB (loopback), and LT (link trace).

Networking and Requirement

As shown in Figure 25-13, both Company A and Company B have branches in City 1 and City 2. The branches of each company need to communicate with each other and the services from the two companies need to be isolated. Two services (E-Line-1 and E-Line-2) are created between NE1 and NE3 for the communication between Company A and Company B. NE1 uses the OptiX OSN 1900 to provide the access at the user side. NE2 and NE3 use the OptiX OSN 3900 to provide the transmission at the network side. NE1, NE2, and NE3 form the maintenance domain MD1. In addition, two maintenance associations MA1 and MA2 are created to bind the E-Line-1 and E-Line-2 services. You can perform the CC, LB, or LT test in the corresponding maintenance association to verify the running status of the two Ethernet services. Figure 25-13 Networking of the Ethernet service OAM

NE4 NE5 Access layer

20-EFF8-1(Port-1) 10.0.0.2 3-EFF8-3(Port-3) 10.0.0.1 3-EFF8-2(Port-2)

10GE ring on convergence layer

5-EX2-1(Port-1) 10.0.1.2

NE3
20-EFF8-2(Port-2)

NE1
3-EFF8-1(Port-1)

NE2

5-EX2-1(Port-1) 10.0.1.1 20-EFF8-1(Port-1)

Company B Company A Company B Company A

25.7.2 Service Planning

Two services from Company A and Company B correspond to two maintenance associations. The service shown in Figure 25-13 is taken as an example.
l

Maintenance association MA 1 binds the E-Line-1 service of Company A and maintenance association MA2 binds the E-Line-2 service of Company B. NE1, NE2, and NE3 form a maintenance domain (MD). The ports of NE1 and NE3 are configured as MEP points. The ports of NE2 are configured as MIP points.

l l l

The following table lists the planned configuration parameters of the Ethernet service OAM.
25-40 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

Table 25-6 Configuration of the MD Attribute NE Maintenance Domain Name Maintenance Domain Level Value NE1 MD1 4 NE2 MD1 4 NE3 MD1 4

Table 25-7 Configuration of the MA 1 Attribute NE Maintenance Domain Name Maintenance Association Name Relevant Service CC Test Transmit Period(ms) Value NE1 MD1 MA1 E-Line-1 3.33 ms NE2 MD1 MA1 E-Line-1 3.33 ms NE3 MD1 MA1 E-Line-1 3.33 ms

Table 25-8 Configuration of the MA 2 Attribute NE Maintenance Domain Name Maintenance Association Name Relevant Service CC Test Transmit Period(ms) Value NE1 MD1 MA2 E-Line-2 3.33 ms NE2 MD1 MA2 E-Line-2 3.33 ms NE3 MD1 MA2 E-Line-2 3.33 ms

Table 25-9 Configuration of the MEP point Attribute NE Value NE1 NE1 NE3 NE3

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

25-41

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

Attribute Maintenance Domain Name Maintenance Association Name Board Port VLAN MP ID Direction CC Status

Value MD1 MA1 MD1 MA2 MD1 MA1 MD1 MA2

3-EFF8 3-EFF8-1 (PORT-1) 100 1 Ingress Active

3-EFF8 3-EFF8-2 (PORT-2) 200 1 Ingress Active

20-EFF8 20-EFF8-1 (PORT-1) 100 3 Ingress Active

20-EFF8 20-EFF8-1 (PORT-1) 200 3 Ingress Active

Table 25-10 Configuration of the MIP point Attribute NE Maintenance Domain Name Board Port MP ID Value NE2 MD1 5-EX21(PORT-1) 1(PORT-1) 2

25.7.3 Configuration Process

This topic describes the configuration process of the Ethernet service OAM in the configuration case.

Prerequisite
You must be an NM user with "NE operator" authority or higher. You must understand the networking, requirements and service planning of the examples.

Procedure
Step 1 Configure an MD. 1. Select the NE1 in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from Function Tree.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

25-42

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

2.

Click New Maintenance Domain. The New Maintenance Domain dialog box is displayed.

3. 4.

Set Maintenance Domain Name to MD1 and Maintenance Domain Level to 4, and click Apply. Refer to Step 1.1 to Step 1.3 to cofeature maintenance domains of NE2 and NE3. The parameters of the maintenance domains are the same as those of NE1.

Step 2 Configure an MA. 1. 2. Select NE1 in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from Function Tree. Select MD1, click Maintenance Association tab, and then select New Maintenance Association from New. The New Maintenance Association dialog box is displayed.

3.

Set the related parameters of MA1, click Apply. The related parameters of MA1 are as follows.
l l l l

Maintenance Domain Name: MD1 Maintenance Association Name: MA1 Relevant Service: 1-E_Line-1 CC Test Transmit Period(ms): 3.33ms

4. 5.

Select New Maintenance Association from New. The New Maintenance Association dialog box is displayed. Set the related parameters of MA2, click Apply. The related parameters of MA2 are as follows.
l l l l

Maintenance Domain Name: MD1 Maintenance Association Name: MA2 Relevant Service: 2-E_Line-2 CC Test Transmit Period(ms): 3.33ms

6.

Refer to Step 2.1 to Step 2.5 to configure MA1 and MA2 of NE2 and NE3. The parameters of the MAs are the same as those of NE1.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 25-43

Issue 01 (2009-06-30)

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 3 Configure NE1 and NE2 as MEP points. 1. 2. Select NE1 in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Select MD1 and then MA1, and select New MEP Point from New. The New MEP Maintenance Point dialog box is displayed.

3.

Set the related parameters of NE1 (MEP point) in the MD1 of MA1, and click Apply. The related parameters of NE1 (MEP point) in the MD1 of MA1 are as follows:
l l l l l l

Board: 3-EFF8 Port: 3-EFF8-1(Port-1) VLAN: 100 MP ID: 1 Direction: Ingress CC Status: Active

4. 5.

Select MD1 and then MA2, and select New MEP Point from New. The New MEP Maintenance Point dialog box is displayed. Set the related parameters of NE1 in the MD1 of MA2, and click Apply. The related parameters of NE1 (MEP point) in the MD1 of MA2 are as follows:
l l l l l l

Board: 3-EFF8 Port: 3-EFF8-2(Port-2) VLAN: 200 MP ID: 1 Direction: Ingress CC Status: Active

6.

Refer to Step 3.1 to Step 3.5 to configure NE3 as MEP points in the MD1s of MA1 and MA2. The related parameters of NE3 (MEP point) in the MD1 of MA1 are as follows:
l

Board: 20-EFF8
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

25-44

OptiX iManager T2000 Operation Guide for PTN NE Management

l l l l l

25 OAM Management

Port: 20-EFF8-1(Port-1) VLAN: 100 MP ID: 3 Direction: Ingress CC Status: Active

The related parameters of NE1 (MEP point) in the MD1 of MA2 are as follows:
l l l l l l

Board: 20-EFF8 Port: 20-EFF8-2(Port-2) VLAN: 200 MP ID: 3 Direction: Ingress CC Status: Active

Step 4 Configure NE2 as an MIP point. 1. 2. Select NE2 in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from Function Tree. Select MD1, and click the MIP Point tab. Then, click New. The New MIP Maintenance Point dialog box is displayed.

3.

Set the related parameters of NE2 (MIP point), and click Apply. The related parameters of NE2 (MIP point) are as follows:
l l l

Board: 5-EX2 Port: 1(Port-1) MP ID: 2

Step 5 Optional: Perform the CC test on NE1. 1. 2. 3. 4. Select NE1 in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from Function Tree. Select MD1 and then MA1, select MEP point 3-EFF8-1(Port-1), and then select Activate CC from OAM. Refer to Step 5.1 to Step 5.2 to activate the CC test on NE3 (MEP point). Refer to Step 5.1 to Step 5.2 to activate the CC test on the MD1 of MA2.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

25-45

25 OAM Management
NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

After the CC is activated at the source and sink of a service, the source periodically builds and sends CC cells. The end automatically reports the ETH_CFM_LOC alarm if it does not receive the CC cells from the source within the required time. Activating the CC test occupies certain bandwidth. Therefore, you can deactivate the CC test when the test is not required.

Step 6 Optional: Perform the LB test on NE1. 1. 2. 3. Select NE1 in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from Function Tree. Select MD1 and then MA1, select 3-EFF8-1(Port-1), and then select Start LB from OAM. The LB Test dialog box is displayed. Set the parameters related to the LB test, and click Start Test. The parameters related to the LB test are as follows:
l l l l l

Source Maintenance Point ID: 1 Destination Maintenance Point MAC Address: 1A-2B-3C-4D (MAC address of NE3) Transmitted Packet Count: 3 Transmitted Packet Length: 64 Transmitted Packet Priority: 4

4.

Refer to Step 6.1 to Step 6.3 to configure the LB test on the MD1 of MA2.

Step 7 Optional: Perform the LT test on NE1. 1. 2. 3. Select NE1 in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from Function Tree. Select MD1 and then MA1, select 3-EFF8-1(Port-1), and then select Start LT from OAM. The LT Test dialog box is displayed. Set the parameters related to the LT test, and click Start Test. The parameters related to the LT test are as follows:
l l

Source Maintenance Point ID: 1 Destination Maintenance Point MAC Address: 1A-2B-3C-4D (MAC address of NE3)

4.

Refer to Step 7.1 to Step 7.3 to configure the LT test on the MD1 of MA2.

----End

25.8 Configuration Case of the MPLS OAM

The configuration case of MPLS OAM describes how to configure the MPLS OAM. 25.8.1 Case Description The MPLS OAM is an OAM function for the tunnel. The check methods include CV/FFD, LSP Ping and LSP Traceroute. 25.8.2 Configuration Process This section describes the configuration process of the MPLS OAM in the configuration case.
25-46 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

25.8.1 Case Description

The MPLS OAM is an OAM function for the tunnel. The check methods include CV/FFD, LSP Ping and LSP Traceroute.

Networking and Requirement

In the MPLS network shown in Figure 25-14, NE1, NE2, NE3 and NE4 are the Optix PTN 3900 NEs.
l

A static LSP tunnel, that is, Tunnel 1, is available on the path of NE1-NE2-NE4. The CV, LSP Ping and LSP Traceroute check methods are used on Tunnel 1 through the MPLS OAM mechanism. A static reverse LSP tunnel, that is, Tunnel 3, is available on the path of NE4-NE2-NE1. This tunnel is used to transmit the check results. A static LSP tunnel, that is, Tunnel 2, is available on the path of NE4-NE3-NE1. The FFD, LSP Ping and LSP Traceroute check methods are used on Tunnel 2 through the MPLS OAM mechanism. A static reverse LSP tunnel, that is, Tunnel 4, is available on the path of NE1-NE3-NE4. This tunnel is used to transmit the check results.

Figure 25-14 Networking diagram of the MPLS OAM

NE2

Node B

NE1

NE4

Node B

Forward LSP Tunnel Reverse LSP Tunnel

NE3

Service Planning
The service shown in Figure 25-14 is taken as an example.
l

NE1 initiates the CV, LSP Ping, and LSP Traceroute check. NE4 notifies NE1 of the faults through the reverse LSP tunnel, that is, Tunnel 3. NE4 initiates the FFD check. NE1 notifies NE4 of the faults through the reverse LSP tunnel, that is, Tunnel 4.

Table 25-11 lists the configuration parameters of the MPLS OAM.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

25-47

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

Table 25-11 Configuration parameters of the MPLS OAM Attribute NE OAM Status Detection Mode Detection Packet Type Detection Packet Period(ms) Value NE1 Enabled Manual CV 1000 NE4 Enabled Manual FFD 3.3

25.8.2 Configuration Process

This section describes the configuration process of the MPLS OAM in the configuration case.

Prerequisite
You must understand the networking, requirements and service planning of the example.

Procedure
Step 1 On the T2000, configure the MPLS OAM. For the configuration method, see 25.3.5 Setting the MPLS OAM Parameters of a Tunnel. The parameters of NE1 are as follows:
l l l l

OAM Status: Enabled Detection Mode: Manual Detection Packet Type: CV Detection Packet Period(ms): 1000

The parameters of NE4 are as follows:

l l l l

OAM Status: Enabled Detection Mode: Manual Detection Packet Type: FFD Detection Packet Period(ms): 500

Step 2 On NE1, enable the CV/FFD check for the tunnel. For details, see 25.3.6 Starting the CV/FFD for a Tunnel. Step 3 On NE4, enable the CV/FFD check for the tunnel. For details, see 25.3.6 Starting the CV/FFD for a Tunnel. Step 4 On NE1, perform the LSP Ping check. For details, see 25.3.7 Performing an LSP Ping Test. Step 5 On NE1, perform the LSP Traceroute check. For details, see 25.3.8 Performing an LSP Traceroute Test. ----End
25-48 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

25.9 Configuration Case of the ATM OAM

The configuration case of the ATM OAM describes how to configure the ATM OAM. 25.9.1 Case Description This section describes the functional requirement, networking diagram and service planning. 25.9.2 Configuration Process This section describes the configuration process of the ATM OAM.

25.9.1 Case Description

This section describes the functional requirement, networking diagram and service planning.

Networking and Requirement

The ATM OAM is an end-to-end OAM function for services. It can check the quality of the ATM link. The ATM OAM function is used to insert some OAM cells with standard cell structure to the user cell flow to provide some specific information of the network. The CC and LB tests are available. As shown in Figure 25-15, a UNIs-NNI ATM service from the base station to RNC is created. The service is connected to Node B through NE1, and is connected to RNC through NE2. The service type is N:1 VC switching. The source VPI/VCI is 32/33, and the sink VPI/VCI is 52/53. The ATM service should be checked. The connectivity of services only in the direction from Node B to NE1 and from RNC to NE2 can be checked. Enable the CC and LB function to check whether the link is normal. If the services are unavailable, an alarm is reported. NE1 uses the OptiX PTN 1900, and NE2 uses the OptiX PTN 3900. Figure 25-15 Networking of the ATM OAM
1-CXP-1MD1-Trunk1 2-MP1-1-AD1-1 (1-AD1.PORT-1)

Node B PW

NE1

NE2

RNC

Service Planning
In the case of the ATM service, the segment end attributes, CC activation status or remote loopback test of each connection should be set. In this case, the ATM service has only one connection. The related parameters are set in the forward direction of the source NE and sink NE. The forward direction is from the user side to the network side, that is, the direction from Node B to NE1 and from RNC to NE2 as shown in Figure 25-15. The service shown in Figure
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 25-49

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

25-15 is taken as an example. Table 25-12 shows the configuration parameters of the ATM OAM. Table 25-12 Configuration parameters of the ATM OAM Attribute NE Segment End Attributes Source Sink Connection Direction Segment and End Attribute CC Activation Status Source Sink Connection Direction Segment and End Attribute CC Activate Flag LLID Country Code (Hexadecimal Code) Network Code (Hexadecimal Code) NE Code (Hexadecimal Code) Remote Loopback Test Source Sink Connection Direction Segment and End Attribute Value NE1 1-CXP-1-MD1-1 (Trunk1)-32-33 PW20-52-53 Source End Point 1-CXP-1-MD1-1 (Trunk1)-32-33 PW20-52-53 Source End Point Source Activate [2BYTE]00 00 NE2 2-MP1-1-AD1-1(1AD1.PORT-1)-52-53 PW20-52-53 Source End Point 2-MP1-1-AD1-1(1AD1.PORT-1)-52-53 PW20-52-53 Source End Point Source Activate [2BYTE]00 00

[2BYTE]00 00

[2BYTE]00 00

[11BYTE]00 09 00 02 00 00 00 00 00 12 00 1-CXP-1-MD1-1 (Trunk1)-32-33 PW20-52-53 Source End Point

[11BYTE]00 09 00 02 00 00 00 00 00 15 00 -

25-50

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

Attribute Loopback Point NE Test Result

Value NE2 -

25.9.2 Configuration Process

This section describes the configuration process of the ATM OAM.

Prerequisite
You must understand the networking, requirements and service planning of the example.

Procedure
Step 1 On the T2000, configure the segment end attributes of NE1 and NE2. For the configuration method, refer to Setting Segment End Attribute. The following parameters, which are related to the segment end attributes of NE1, should be configured.
l l l l

Source: 1-CXP-1-MD1-1(Trunk1)-32-33 Sink: PW20-52-53 Connection Direction: Source Segment and End Attribute: End Point

The following parameters, which are related to the segment end attributes of NE2, should be configured.
l l l l

Source: 2-MP1-1-AD1-1(1-AD1.PORT-1)-52-53 Sink: PW20-52-53 Connection Direction: Source Segment and End Attribute: End Point

Step 2 On the T2000, configure the CC activation status of NE1 and NE2. For the configuration method, refer to Setting the CC Activation Status. The following parameters, which are related to the CC activation status of NE1, should be configured.
l l l l l

Source: 1-CXP-1-MD1-1(Trunk1)-32-33 Sink: PW20-52-53 Connection Direction: Source Segment and End Attribute: End Point CC Activate Flag: Source Activate

The following parameters, which are related to the CC activation status of NE2, should be configured.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 25-51

25 OAM Management
l l l l l

OptiX iManager T2000 Operation Guide for PTN NE Management

Source: 2-MP1-1-AD1-1(1-AD1.PORT-1)-52-53 Sink: PW20-52-53 Connection Direction: Source Segment and End Attribute: End Point CC Activate Flag: Source Activate

Step 3 On the T2000, configure the LLID of NE1 and NE2. For the configuration method, refer to Setting Local Loopback ID. The following parameters, which are related to the LLID of NE1, should be configured.
l l l

Country Code (Hexadecimal Code): [2BYTE] 00 00 Network Code (Hexadecimal Code): [2BYTE] 00 00 NE Code (Hexadecimal Code): [11BYTE] 00 09 00 02 00 00 00 00 00 12 00

The following parameters, which are related to the LLID of NE2, should be configured.
l l l

Country Code (Hexadecimal Code): [2BYTE] 00 00 Network Code (Hexadecimal Code): [2BYTE] 00 00 NE Code (Hexadecimal Code): [11BYTE] 00 09 00 02 00 00 00 00 00 15 00

Step 4 On the T2000, configure the remote loopback check of NE1. For the configuration method, refer to Setting Remote Loopback Test. The following parameters, which are related to the remote loopback test of NE1, should be configured.
l l l l l l

Source: 1-CXP-1-MD1-1(Trunk1)-32-33 Sink: PW20-52-53 Connection Direction: Source Segment and End Attribute: End Point Loopback Point NE: NE2 Text Result: NOTE

If NE2 need initiate the remote loopback test to loop back NE1, the remote loopback test should be configured on NE2. The configuration method is the same as that of NE1.

----End

25.10 Configuration Case of the PW OAM

This section describes how to configure the PW OAM through a configuration case. 25.10.1 Case Description The PW OAM is an end-to-end OAM function especially for the PW. The checking method is the Ping test. 25.10.2 Configuration Process This sections describes the configuration procedures of the PW Ping test in the case.
25-52 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

25 OAM Management

25.10.1 Case Description

The PW OAM is an end-to-end OAM function especially for the PW. The checking method is the Ping test.

Networking and Requirement

As shown in Figure 25-16, suppose that CES services already exist between NE1 and NE2. The packets that NodeB sends to RNC are encapsulated into the PW at NE1 for transport and decapsulated at NE2 from the PW and forwarded to RNC. NE1 is the OptiX PTN 1900 and NE2 is the OptiX PTN 3900. Figure 25-16 Application of the PW OAM networking

IMA

CES PW NE1 PW ping NE2

ATM STM-1

NodeB

RNC

Service Planning
Figure 25-16 is considered as an example to show the service planning, basic attributes of the PW are as follows:
l l l l l

PW ID: 55 Enable State: Enabled PW Signaling Type: Dynamic Service Type: CESoPSN Direction: Bidirectional

NE1 initiates the Ping test. Planning of configuration parameters of the PW Ping test. Table 25-13 Configuration of the Ping test Attribute Site Packet Count EXP Value TTL Transmit Interval(10ms)
Issue 01 (2009-06-30)

Value NE1 3 7 255 100

25-53

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

25 OAM Management

OptiX iManager T2000 Operation Guide for PTN NE Management

Attribute Packet Length Wait-to-Response Timeout Time(10ms) Response Mode

Value 64 300 IPv4 UDP Response

25.10.2 Configuration Process

This sections describes the configuration procedures of the PW Ping test in the case.

Prerequisite
You must know information about networking, requirement and service planning of this case.

Procedure
Step 1 On the T2000, configure the PW Ping test. For details, see 25.4.4 Performing the PW Ping Test. The parameters of NE1 are as follows:
l l l l l l l

Packet Count: 3 EXP Value: 7 TTL: 255 Transmit Interval(10ms): 100 Packet Length: 64 Wait-to-Response Timeout Time(10ms): 300 Response Mode: IPv4 UDP Response

Step 2 On NE1, start the Ping test. For details, see 25.4.4 Performing the PW Ping Test. ----End

25-54

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

26 Configuring the BFD

26
About This Chapter

Configuring the BFD

The BFD is a protocol that uses the UDP packets to quickly detect the link status. The detection time can reach Milliseconds. 26.1 Overview of the BFD Similar to a simple Hello protocol, the BFD is adopted to detect faults on the route layer. 26.2 Basic Concepts This section describes the basic BFD-related concepts such as session, single-hop detection, bound port and diagnosis word. 26.3 Creating a BFD Session The BFD session is the main part of the configuration, management and check. Before the BFD check, you need to create a BFD session to test the link state. 26.4 Configuring Parameters of the BFD Session After creating the BFD session, configure parameters for the BFD session. 26.5 Querying the BFD Session Information Query the BFD session information as required. 26.6 Deleting a BFD Session In the case of many BFD sessions, delete some BFD sessions to release resources. 26.7 Configuration Case A case is provided here to describe how to configure the BFD.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

26-1

26 Configuring the BFD

OptiX iManager T2000 Operation Guide for PTN NE Management

26.1 Overview of the BFD

Similar to a simple Hello protocol, the BFD is adopted to detect faults on the route layer.

Objective and Benefit

The BFD can fast detect the communication failure between the two adjacent systems. In other words, a pair of systems periodically sends detection packets on the channel on which session between the two systems is created. If a system does not receive any detection packet from the opposite end in a specific time, the system regards that a failure occurs in some part of the bidirectional channel to the adjacent system. In this way, when a fault occurs, a substitute channel can be created quickly or the services are quickly switched to another link. The BFD is similar to the neighbor check of many protocols in many aspects, but the BFD takes a shorter detection time. The BFD sends the user datagram protocol (UDP) packets. The BFD has the following functions:
l

Performs fault detection that brings light load and lasts for a short time for the channel where the BFD session is set up. Adopts a uniform mechanism to detect faults for any medium and any protocol layer in a real-time manner, and supports different detection time and overheads. Reduces the lost data. Compared with the hello mechanism, the BFD detects faults in milliseconds. When the data is transmitted at a high rate, the BFD can effectively reduce the lost data.

Compliant Standards and Protocols

The BFD complies with IETF: draft-ietf-bfd-base-04, IETF: draft-ietf-bfd-v4v6-1hop-04 and IETF: draft-ietf-bfd-multihop-04.

26.2 Basic Concepts

This section describes the basic BFD-related concepts such as session, single-hop detection, bound port and diagnosis word.

Session
Before performing the BFD detection, set up the peer session at both ends of the channel. After the session is set up, each end transmits the BFD control packets to the opposite end at the negotiated rate.

Single-Hop Detection
The single-hop detection quickly detects and monitors the connectivity of the link of direct connection. Single-hop detection is applicable to the scenario where the link between BFD peers does not traverse the third-party equipment.

Bound Port
The BFD session status is bound with the port status. If the BFD session status is DOWN, the bound port is also in the DOWN status.
26-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

26 Configuring the BFD

Diagnosis Word
The diagnosis word indicates the cause of the state change of the latest session in the local BFD system.

26.3 Creating a BFD Session

The BFD session is the main part of the configuration, management and check. Before the BFD check, you need to create a BFD session to test the link state.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The port where the BFD session can be created must be a VLAN sub-port or Ethernet port configured with Layer 3 attributes. In the case of a Lay 3 port, you must enable the MPLS. The Port enable tunnel. The IP address of the VLAN sub-port in the system must be configured. To configure the VLAN sub interface, see10.9 Configuring an Ethernet Virtual Interface.

l l

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > BFD management from the Function Tree. Step 2 Click New. The Create BFD dialog box is displayed.

Step 3 Set the parameters related to the BFD session.

NOTE

Take the following precautions when setting these parameters. If Session Type is set to Single-Hop, select Board and Port, that is, select a port on a board that transmits the BFD packets. The PTN only supports the single hop check.

Step 4 Click OK. ----End

Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 26-3

26 Configuring the BFD

OptiX iManager T2000 Operation Guide for PTN NE Management

26.4 Configuring Parameters of the BFD Session

After creating the BFD session, configure parameters for the BFD session.

Prerequisite
l l

You must be an NM user with "NE operator" authority or higher. The BFD session must be created.

Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > BFD management from the Function Tree. Step 2 Select a BFD session, and configure parameters for the BFD session. It is recommended that you set the following parameters:
l l l l

Admin Status: Up Local Send Interval of Packets: 1000 Local Receive Interval of Packets: 1000 Local Detection Multiple of Packets: 3
NOTE

For OptiX PTN 1900 and OptiX PTN 3900, configure the bound port only when you configure association between the BFD and LPT.

Step 3 Click Apply. ----End

26.5 Querying the BFD Session Information

Query the BFD session information as required.

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

Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > BFD management from the Function Tree. Step 2 Select a BFD session and click Query. Check the BFD session information.
NOTE

If Admin Status is set to Down, Session Status is displayed only as Down.

----End
26-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

26 Configuring the BFD

26.6 Deleting a BFD Session

In the case of many BFD sessions, delete some BFD sessions to release resources.

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

Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > BFD management from the Function Tree. Step 2 Select a BFD session and click Delete. Step 3 A dialog box is displayed for confirmation. Click OK. ----End

26.7 Configuration Case

A case is provided here to describe how to configure the BFD. 26.7.1 Case Description The case description covers the requirement, networking and data planning. 26.7.2 Configuration Process The configuration case illustrates the process of configuring the BFD.

26.7.1 Case Description

The case description covers the requirement, networking and data planning.

Networking and Requirement

The BFD is mainly used to detect the link status. As shown in Figure 26-1, NE1 and NE2 are connected to the broadband network gateway (BNG) to access broadband TV (BTV) services. NE1 and NE2 are the OptiX PTN 3900 NEs. Link1 and link2 are of mutual backup. The BFD detects any fault in the link between NE1 and BNG1, and the link between NE2 and BNG2. Assume that the link segment between BNG1 and NE1 on link1 is faulty and NE1 detects the link fault through BFD. If the port that is bound is configured with the LPT function, disable the port. When detecting the fault, the opposite access node selectively receives services from link2.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

26-5

26 Configuring the BFD

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 26-1 BFD networking application

23-ETFC-2(PORT-2) to 23-ETFC-4(PORT-4) BFD

Access Node 23-ETFC-1(PORT-1) BFD Access Node

BNG1

NE1

23-ETFC-1(PORT-1) BNG2 link 1 link 2

NE2

23-ETFC-2(PORT-2) to 23-ETFC-4(PORT-4) Access Node

Data Planning
The engineering planning department should plan the engineering according to the related requirements, and output detailed planning information. Figure 26-1 is considered as an example to show the service planning. Table 26-1 list the planned configuration parameters of NE1 and NE2 respectively. Table 26-1 Planned configuration parameters of NE1 Attribute NE Session Type Board Port Sink Port IP Address Admin Status Local Detection Multiple of Packets Value NE1 Single Hop 23-ETFC 1(PORT-1) 192.168.1.6 Up 3 NE2 Single Hop 23-ETFC 1(PORT-1) 192.168.1.5 Up 3

26.7.2 Configuration Process

The configuration case illustrates the process of configuring the BFD.

Prerequisite
You must know information about networking, requirement and data planning of this case.
26-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

26 Configuring the BFD

Procedure
Step 1 On the T2000, configure the BFD session of NE1 and NE2. For details, see 26.3 Creating a BFD Session. To configure the BFD session of NE1, set the parameters as follows:
l l l l

Session: Single Hop Board: 23-ETFC Port: 1(PORT-1) Sink Port IP Address: 192.168.1.6

To configure the BFD session of NE2, set the parameters as follows:

l l l l

Session: Single Hop Board: 23-ETFC Port: 1(PORT-1) Sink Port IP Address: 192.168.1.5

Step 2 On the T2000, set the BFD session parameters of NE1 and NE2. For details, see 26.4 Configuring Parameters of the BFD Session. Set the BFD session parameters of NE1 as follows:
l l

Admin Status: Up Local Detection Multiple of Packets: 3

Set the BFD session parameters of NE2 as follows:

l l

Admin Status: Up Local Detection Multiple of Packets: 3

----End

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

26-7

OptiX iManager T2000 Operation Guide for PTN NE Management

27 Configuring the LPT

27
About This Chapter

Configuring the LPT

In the case of the link state pass through (LPT) function, the far end link state is returned to the near end. In this way, the near end equipment performs operations according to the far end link state to realize network-level protection. 27.1 Overview of the LPT In the case of the link state pass through (LPT) function, the far end link state is returned to the near end. In this way, the near end equipment performs operations according to the far end link state to realize network-level protection. 27.2 LPT Application The LPT function is used to detect the faults that occur on the access links or in the service network. 27.3 Creating the LPT When the access link or transmission network becomes faulty, the LPT ensures that the equipment at both ends starts the backup network to retain normal communication. 27.4 Configuration Case A case is provided here to describe how to configure the LPT.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

27-1

27 Configuring the LPT

OptiX iManager T2000 Operation Guide for PTN NE Management

27.1 Overview of the LPT

In the case of the link state pass through (LPT) function, the far end link state is returned to the near end. In this way, the near end equipment performs operations according to the far end link state to realize network-level protection.

Objective and Benefit

The LPT detects any fault that occurs at the service access point or in the intermediate transmission network, and asks the equipment at both ends to start up the backup network immediately to retain communication. In this way, important data can still be normally transmitted.

27.2 LPT Application

The LPT function is used to detect the faults that occur on the access links or in the service network. Figure 27-1 shows how the LPT function is used. Figure 27-1 LPT networking application scenario
Backup network

Port1 NE2 Port3 Server network Port1 Router A NE1 Port2 Port1

Port2

Router B

Port2 Port3 NE3 Backup network Router C

Protection link Working link

Router D

Normally, the data among router A, router B, router C and router D is transmitted through a server network. When the link between router A and NE1 becomes faulty, router A fails to communicate with router B, router C and router D. When the link fault occurs, the important data of VIP users must still be normally transmitted. Hence, the system should detect and notify the fault in time, and start the backup network to retain communication. The backup network can be of many forms, such as a microwave network or another leased link.
27-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

27 Configuring the LPT

27.3 Creating the LPT

When the access link or transmission network becomes faulty, the LPT ensures that the equipment at both ends starts the backup network to retain normal communication.

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

Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > LPT Management from the Function Tree. Step 2 Click New. The Create LPT dialog box is displayed.

Step 3 In the dialog box, set related parameters.

NOTE

l l

One port should belong to only one LPT group. Multiple ports can be selected as access ports.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

27-3

27 Configuring the LPT

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 4 Click Apply. ----End

27.4 Configuration Case

A case is provided here to describe how to configure the LPT. 27.4.1 Case Description The LPT detects any fault that occurs at the service access point or in the intermediate transmission network, and asks the equipment at both ends to start up the backup network immediately to retain communication. In this way, important data can still be normally transmitted. 27.4.2 Configuration Process The configuration case illustrates how to configure the LPT.

27.4.1 Case Description

The LPT detects any fault that occurs at the service access point or in the intermediate transmission network, and asks the equipment at both ends to start up the backup network immediately to retain communication. In this way, important data can still be normally transmitted.

Networking and Requirement

As shown in Figure 27-2, the headquarters of a company need communicate data with the three branches through a server network. In addition, the backup network connections provide protection for the data communication among them. NE1, NE2 and NE3 are the OptiX PTN 3900 NEs. In the case of the LPT function, when a link fault occurs, the link fault information is transmitted to the opposite end to realize pass-through of the link state. In this way, the equipment at both ends of the network re-establishes communication by using the backup network. Figure 27-2 LPT networking diagram
Backup network

Port1 NE2 Port3 Server network Port1 Headquarters NE1 Port2 Port1

Port2

Branch A

Port2 Port3 NE3

Branch C

Protection link Working link

Backup network Branch B

27-4

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

27 Configuring the LPT

Service Planning
The following case is based on Figure 27-2. If the link between the headquarters and NE1 is faulty, the service of each access point must be switched to the backup network immediately and then the branches can communicate with the headquarters normally. The LPT should be configured at NE1, NE2 and NE3.
l l l

At NE1, Port1 is the convergence port, Port2 and Port3 are access ports. At NE2, Port1 is the convergence port, Port2 is the access port. At NE3, Port1 is the convergence port, Port2 and Port3 are access ports.

Table 27-1 lists the planned parameters for the LPT configuration. Table 27-1 Planned parameters for the LPT configuration Attribute Station Convergence Port Access Port Board Port Board Port Value NE1 3-EG16 1(PORT-1) 1-EG16 2(PORT-2), 3 (PORT-3) NE2 3-EG16 1(PORT-1) 26-EFFC 2(PORT-2) NE3 3-EG16 1(PORT-1) 26-EFFC 2(PORT-2), 3 (PORT-3)

27.4.2 Configuration Process

The configuration case illustrates how to configure the LPT.

Prerequisite
You must know information about networking, requirement and service planning of this case.

Procedure
Step 1 On the T2000, configure the LPT of NE1. For details, see 27.3 Creating the LPT. The parameters of the convergence port are as follows:
l l

Board: 3-EG16 Port: 1(PORT-1)

The parameters of the access port are as follows:

l l

Board: 1-EG16 Port: 2(PORT-2), 3(PORT-3)

Step 2 On the T2000, configure the LPT of NE2. For details, see 27.3 Creating the LPT.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 27-5

27 Configuring the LPT

OptiX iManager T2000 Operation Guide for PTN NE Management

The parameters of the convergence port are as follows:

l l

Board: 3-EG16 Port: 1(PORT-1)

The parameters of the access port are as follows:

l l

Board: 26-EFFC Port: 2(PORT-2)

Step 3 On the T2000, configure the LPT of NE3. For details, see 27.3 Creating the LPT. The parameters of the convergence port are as follows:
l l

Board: 3-EG16 Port: 1(PORT-1)

The parameters of the access ports are as follows:

l l

Board: 26-EFFC Port: 2(PORT-2), 3(PORT-3)

----End

27-6

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

28 Configuring Orderwire

28
About This Chapter

Configuring Orderwire

You can configure orderwire for NEs by using the T2000. 28.1 Configuring Orderwire To provide the maintenance personnel with a dedicated express orderwire channel, you can configure orderwire for NEs. 28.2 Configuring F1 Data Port Services You can use the T2000 to configure F1 Data port services.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

28-1

28 Configuring Orderwire

OptiX iManager T2000 Operation Guide for PTN NE Management

28.1 Configuring Orderwire

To provide the maintenance personnel with a dedicated express orderwire channel, you can configure orderwire for NEs.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Orderwire from the Function Tree. Click the General tab.

Step 2 Click Query to query information from the NE. Step 3 Set Call Waiting Time(s), Telephone No. and orderwire ports.
NOTE

l l l

Call Waiting Time(s) should be set to the same value for all NEs with orderwire communication. When the number of NEs is smaller than 30, set the value to 5 seconds. Otherwise, set it to 9 seconds. The telephone number must be unique in an orderwire subnet. Set the length of the telephone number according to the actual requirements. The maximum length is eight digits and the minimum length is three digits. In the same orderwire subnet, the number length must be the same.

Step 4 Click Apply. ----End

28-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

28 Configuring Orderwire

28.2 Configuring F1 Data Port Services

You can use the T2000 to configure F1 Data port services. 28.2.1 F1 Data Port Services The F1 Data Port Services is a point-to-point (P2P) service that is transparently transmitted by using the F1 byte. 28.2.2 Creating F1 Data Port Services The F1 Data Port Services uses the F1 byte (section user channel byte) to transparently transmit services. If a maintenance engineer requires extra overhead bytes to temporarily set up orderwire connections, the engineer can create F1 data port services.

28.2.1 F1 Data Port Services

The F1 Data Port Services is a point-to-point (P2P) service that is transparently transmitted by using the F1 byte. The F1 data port is a transparent data port that transports codirectional P2P services at the rate of 64 kbit/s. It does not support data broadcast. Hence, only the P2P services can be turned up at an F1 data port. When you use the F1 data port, you only need to configure routes for the 64 kbit/s data, that is, whether the data is added to, dropped from or passes through the port. If you manually configure the port, you need to use the T2000 to configure each node along the communication channel. After the configurations take effect, the data can be transmitted.

Example for Configuring the F1 Data Port Services

Figure 28-1 shows how a F1 Data Port Services is configured. Figure 28-1 Configuring the Node A and node C transmit data through the F1 data port. You can use the T2000 to configure each node as follows:
l

Configure added or dropped services at node A. Select the F1 data port and a port on the intermediate frequency (IF) board as two data channel ports. In this case, the F1 data port service from the client side is added or dropped from the F1 data port of the orderwire board, and is transmitted through the a port on the intermediate frequency (IF) board. Configure pass-through services at node B. Select two a port on the intermediate frequency (IF) board as the data channel ports. In this case, the F1 data port service passes through the two a port on the intermediate frequency (IF) board at this node. Configure added or dropped services at node C. Select the F1 data port and a port on the intermediate frequency (IF) board as two data channel ports. In this case, the F1 data port service is cross-connected from the a port on the intermediate frequency (IF) board to the orderwire board, and then added or dropped from the F1 data port of the orderwire board.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

28-3

28 Configuring Orderwire

OptiX iManager T2000 Operation Guide for PTN NE Management

28.2.2 Creating F1 Data Port Services

The F1 Data Port Services uses the F1 byte (section user channel byte) to transparently transmit services. If a maintenance engineer requires extra overhead bytes to temporarily set up orderwire connections, the engineer can create F1 data port services.

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

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Orderwire from the Function Tree. Step 2 Click the F1 Data Port tab. Step 3 Optional: Click Query to query the information on the NE. Step 4 Select two data channels from the Available Data Channel pane, and click Step 5 Optional: Select the route to delete from the right-hand pane, and click Step 6 Click Apply. In the Operation Result dialog box displayed, click Close. ----End . .

28-4

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

29 Common Maintenance Operations

29

Common Maintenance Operations

About This Chapter

To ensure that the transmission equipment can be normally running for long, you need to periodically maintain the transmission equipment or perform some simple operations of troubleshooting on existing problems. 29.1 Setting a Scheduled Task The T2000 can automatically executing certain tasks in a scheduled time without manual intervention. The scheduled tasks that the T2000 provides contains backing up the database, loading software package periodically, exporting the script file, collecting the performance data, and refreshing the ASON status. You can set and modify these scheduled tasks as required. 29.2 Checking Networkwide Maintenance Status By checking the networkwide maintenance status, network maintenance personnel can learn the running status of a network in a timely manner, to avoid impact on services due to misconfiguration. 29.3 Checking Protection Switching Status You can configure board protection and other protection modes for the OptiX equipment. To detect faults that cause the protection facility to be unavailable, you need to regularly check the protection switching status. 29.4 Performing a PRBS Test You can perform a PRBS test on a path to check the quality of the path. The test result is displayed in the coordinates pane. 29.5 Disabling Service-Affecting Settings Automatically Loopback and laser shutdown are useful NE maintenance functions. Performing these functions may interrupt services at the port and may also interrupt the communication between the NE and the T2000. Hence, you can set automatic disabling before performing loopback or laser shutdown so that the NE automatically cancels the loopback or laser shutdown. 29.6 Checking the Network Communication Status On some occasions, the T2000 cannot manage some NEs during the running of the network. By checking the communication status of the network, you can learn the communication status between the T2000 and NEs. 29.7 Performing a Loopback
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 29-1

29 Common Maintenance Operations

OptiX iManager T2000 Operation Guide for PTN NE Management

The loopback is a common and effective way to locate equipment faults. By using the T2000 you can set a loopback for equipment. 29.8 Replacing the Board Type The PTN equipment supports the function of board type replacement between boards with the same port rate. 29.9 Resetting Boards You can reset a board by using the T2000 by following the instructions below.

29-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

29 Common Maintenance Operations

29.1 Setting a Scheduled Task

The T2000 can automatically executing certain tasks in a scheduled time without manual intervention. The scheduled tasks that the T2000 provides contains backing up the database, loading software package periodically, exporting the script file, collecting the performance data, and refreshing the ASON status. You can set and modify these scheduled tasks as required.

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

Background Information
If a large number of performance data need to be collected, this may cause communication congestion and thus the communication between the T2000 and NEs stops. Hence, observe the following rules to collect the performance data:
l

When creating a single performance data collection task, the number of NEs related to the same GNE does not exceed 5. Run the performance data collection task when network traffic is low.

Procedure
Step 1 Choose System > Scheduled Task Management from the Main Menu. Step 2 Optional: Create a scheduled task. 1. 2. Click New and the Task Creation Wizard is displayed. Select the task type of the scheduled task and enter a task name. Then, click Next.

3.

Follow the task creation wizard to set the parameters of the scheduled task and click Next for several times until the Finish button is displayed.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

29-3

29 Common Maintenance Operations

OptiX iManager T2000 Operation Guide for PTN NE Management

4.

Click Finish. A scheduled task is successfully created.

Step 3 Optional: Select a scheduled task and click Modify to modify the parameters of the task. Step 4 Optional: To disable the task, click Disable. To enable the task, click Enable. Step 5 Optional: Click Run to start executing the task.
NOTE

Run means to immediately execute the task, no matter the scheduled time comes or not. Enable means to start the scheduled task. The task is executed at the scheduled time.

----End

29.2 Checking Networkwide Maintenance Status

By checking the networkwide maintenance status, network maintenance personnel can learn the running status of a network in a timely manner, to avoid impact on services due to misconfiguration. To check the networkwide maintenance status, check the following:
l l l l l l l

Which ports are looped back. Which lasers are off. Which paths are in Non-loaded state. Which alarms are suppressed. Which alarms are inserted. Which alarms are reversed. Which ports have disabled DCCs.

29.2.1 Checking Path Loopback Status You can view all optical or electrical ports for which you configure loopback in the network and view the loopback status. You can also cancel the loopback, to avoid impact on services due to a loopback that should not be performed. 29.2.2 Checking Port Laser Status
29-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

29 Common Maintenance Operations

You can view all lasers that are in the off state in the network and modify their status, to avoid impact on services due to misconfiguration. 29.2.3 Checking Path Alarm Suppression Status You can view all alarms for which you configure alarm suppression in the network. You can also restore the suppression status of an alarm to the default value, so that the alarm monitoring of the service is not affected by improper settings.

29.2.1 Checking Path Loopback Status

You can view all optical or electrical ports for which you configure loopback in the network and view the loopback status. You can also cancel the loopback, to avoid impact on services due to a loopback that should not be performed.

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

Procedure
Step 1 Click the networkwide maintenance status icon Maintenance Status dialog box is displayed. on the toolbar, and the Networkwide

Step 2 Choose Maintenance Status > Loopback Status and view the loopback status for a path.

NOTE

If the queried information is null, it indicates that no path is set to loopback.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

29-5

29 Common Maintenance Operations

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 3 Optional: Select a loopback status and then click Apply. A prompt is displayed indicating that the operation is successful. Click Close.

CAUTION
Setting a loopback may interrupt services. Exercise caution when you perform this operation.
NOTE

You must be an NM user with "NE operator" authority or higher to set loopback for a path.

----End

29.2.2 Checking Port Laser Status

You can view all lasers that are in the off state in the network and modify their status, to avoid impact on services due to misconfiguration.

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

Procedure
Step 1 Click the networkwide maintenance status icon Maintenance Status dialog box is displayed. on the toolbar, and the Networkwide

Step 2 Choose Maintenance Status > Laser Status and view the laser status for an optical port.

29-6

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

29 Common Maintenance Operations

NOTE

If the queried information is null, it indicates that the laser of the equipment is not shut down.

Step 3 Optional: Set the laser status and then click Apply. If you want to enable the laser, in the OK dialog box displayed, click OK. A prompt is displayed indicating that the operation is successful. Click Close.

WARNING
Enabling a laser is a dangerous operation. Misoperation may cause injuries to human eyes. Exercise caution when you perform this operation.

CAUTION
Close the Laser will interrupt the service.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

29-7

29 Common Maintenance Operations

NOTE

OptiX iManager T2000 Operation Guide for PTN NE Management

l l

You must be an NM user with "NE operator" authority or higher to set the laser status for an optical port. You must be an NM user with "NE maintainer" authority or higher to set the laser status for an optical port of the UHBA boards.

----End

29.2.3 Checking Path Alarm Suppression Status

You can view all alarms for which you configure alarm suppression in the network. You can also restore the suppression status of an alarm to the default value, so that the alarm monitoring of the service is not affected by improper settings.

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

Procedure
Step 1 Click the networkwide maintenance status icon Maintenance Status dialog box is displayed. on the toolbar, and the Networkwide

Step 2 Choose Maintenance Status > Alarm Suppression and view the alarm suppression status for a path.

29-8

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

29 Common Maintenance Operations

If the queried information is null, it indicates that the alarm suppression is not set for any path.

Step 3 Optional: To restore the suppression status to the default value, right-click and choose Default from the shortcut menu. Click Apply. A prompt is displayed indicating that the operation is successful. Click Close.
NOTE

You must be an NM user with "NE operator" authority or higher to set the alarm suppression status for a path.

----End

29.3 Checking Protection Switching Status

You can configure board protection and other protection modes for the OptiX equipment. To detect faults that cause the protection facility to be unavailable, you need to regularly check the protection switching status.

Context
The following tasks are described: 29.3.1 Checking the Subcard TPS Status When a tributary protection switching (TPS) occurs, it indicates that the protected working board fails. You can check the TPS status to timely find faults so that services are not affected. 29.3.2 Checking 1+1 Board Switching Status If board 1+1 protection switching is triggered, it indicates that the protected board has failed. The network maintenance engineers can check 1+1 board switching status to detect the faults that caused the failure. 29.3.3 Checking Linear MSP Switching Status To detect faults in NEs or in the fibers of a linear MSP protection subnet, the maintenance engineers can check the switching status of the linear MSP. The engineers can then locate the point where the fault is generated, according to the switching status of each NE in the protection subnet. 29.3.4 Checking GNE Switching Status If the active GNE of an NE fails, and the NE has a standby GNE, the NE automatically communicates with the T2000 through the standby GNE. To detect the GNE communication failure in time, you need to check the GNE switching status to ensure that the NEs communicate correctly with the T2000 through the GNE. 29.3.5 Checking the Clock Switching Status Clock failure may interrupt services. To detect failure of the clock source in time, you need to check the clock switching status. 29.3.6 Checking the FRR Protection Status By checking the FRR protection status, you can learn the protection statuses of all PLR nodes of the FRR tunnel in time.

29.3.1 Checking the Subcard TPS Status

When a tributary protection switching (TPS) occurs, it indicates that the protected working board fails. You can check the TPS status to timely find faults so that services are not affected.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 29-9

29 Common Maintenance Operations

OptiX iManager T2000 Operation Guide for PTN NE Management

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. A TPS protection group must be correctly configured.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > TPS Protection from the Function Tree. Step 2 Click Query to check the subcard TPS status. ----End

29.3.2 Checking 1+1 Board Switching Status

If board 1+1 protection switching is triggered, it indicates that the protected board has failed. The network maintenance engineers can check 1+1 board switching status to detect the faults that caused the failure.

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. The protection board must be created.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Board 1+1 Protection from the Function Tree. Step 2 Click Query to query the 1+1 board switching status. Step 3 Click Close. ----End

29.3.3 Checking Linear MSP Switching Status

To detect faults in NEs or in the fibers of a linear MSP protection subnet, the maintenance engineers can check the switching status of the linear MSP. The engineers can then locate the point where the fault is generated, according to the switching status of each NE in the protection subnet.

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. The linear MSP must be created.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Linear MS from the Function Tree.
29-10 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

29 Common Maintenance Operations

Step 2 Click Query. Select Query Switching Status to query the switching status of the nodes. ----End

29.3.4 Checking GNE Switching Status

If the active GNE of an NE fails, and the NE has a standby GNE, the NE automatically communicates with the T2000 through the standby GNE. To detect the GNE communication failure in time, you need to check the GNE switching status to ensure that the NEs communicate correctly with the T2000 through the GNE.

Prerequisite
The active and standby GNEs must be created for an NE. You must be an NM user with "NE maintainer" authority or higher.

Procedure
Step 1 Choose System > DCN Management from the Main Menu. Step 2 Click the NE tab. Step 3 Click Refresh to query the GNE switching status. ----End

29.3.5 Checking the Clock Switching Status

Clock failure may interrupt services. To detect failure of the clock source in time, you need to check the clock switching status.

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. The reference clock source must be set.

Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Clock > Clock Source Switching from the Function Tree. Step 2 Click the Clock Source Switching tab, and click Query to query the current switching status of the current clock source. Step 3 In the Operation Result dialog box, click Close. ----End

29.3.6 Checking the FRR Protection Status

By checking the FRR protection status, you can learn the protection statuses of all PLR nodes of the FRR tunnel in time.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 29-11

29 Common Maintenance Operations

OptiX iManager T2000 Operation Guide for PTN NE Management

Prerequisite
l l

You must be an NM user with "NE monitor" authority or higher. The FRR tunnel must be created.

Procedure
Step 1 Choose Trail > Tunnel Management > Dynamic Tunnel Management from the Main Menu. The Set Dynamic Tunnel Filter Criteria window is displayed. Step 2 Set the filter criteria and click Filter to filter dynamic tunnels. Step 3 In the dynamic tunnel list, select a FRR tunnel and click the FRR Switch Status tab. Step 4 Click Query to query the switching status of FRR nodes. ----End

29.4 Performing a PRBS Test

You can perform a PRBS test on a path to check the quality of the path. The test result is displayed in the coordinates pane.

Prerequisite
l l l

You must be an NM user with "NE operator" authority or higher. A service must be configured for the port for which you want to perform a PRBS test. The opposite port must be looped back before you perform a PRBS test.

Precaution

CAUTION
Performing a PRBS test interrupts services.

Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > PRBS Test from the Function Tree. Step 2 Select a channel or a port and set Duration and Measured in Time in the Set Test Parameters area. Step 3 Optional: Select Accumulating Mode. The test result is displayed in the coordinates pane in an accumulative manner. Step 4 Click Start to Test. A dialog box is displayed, indicating that this operation may interrupt the service.
29-12 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

29 Common Maintenance Operations

Step 5 Click Yes to start the PRBS test. After the test is complete, view the test result in the coordinates pane. ----End

Postrequisite
You need to release loopback on the opposite port after the test is complete.

29.5 Disabling Service-Affecting Settings Automatically

Loopback and laser shutdown are useful NE maintenance functions. Performing these functions may interrupt services at the port and may also interrupt the communication between the NE and the T2000. Hence, you can set automatic disabling before performing loopback or laser shutdown so that the NE automatically cancels the loopback or laser shutdown.

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

Context
If a port is the only way for an NE to communicate with the T2000, performing a loopback or laser shutdown at the port results in the loss of communication. Before performing a loopback or laser shutdown, you must set automatic disabling for this NE. Otherwise, after the communication is lost, you cannot use the T2000 to log in to the NE to disable the loopback or laser shutdown.

Procedure
Step 1 Choose Configuration > Automatic Disabling of NE Function from the Main Menu. Step 2 Select an NE and click the double-right-arrow button (red). Step 3 Select a value in the Auto Disabling and Auto Disabling Time(min). Step 4 Click Apply. ----End

29.6 Checking the Network Communication Status

On some occasions, the T2000 cannot manage some NEs during the running of the network. By checking the communication status of the network, you can learn the communication status between the T2000 and NEs.

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

Background Information
l

In the case of NEs that are configured with IP over DCC, you can choose File > Ping from the Main Menu, to use the ping function to check the NE communication status.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 29-13

Issue 01 (2009-06-30)

29 Common Maintenance Operations

l

OptiX iManager T2000 Operation Guide for PTN NE Management

In the case of NEs that are configured with OSI over DCC and the OSI software is installed on the computer where the T2000 is installed, you can use the ping function.

Procedure
l Check the communication status between the T2000 and a non-gateway NE. 1. 2. 3. 4. l Choose System > DCN Management from the Main Menu. Click the NE tab. Click Refresh to view the communication status of all NEs. Select an NE. Right-click in the Communication Status column and choose Test NE from the shortcut menu. The Operation Result dialog box is displayed indicating the test result of the nongateway NE. Choose System > DCN Management from the Main Menu. Click the GNE tab. Click Refresh to view the communication status of the GNE. Right-click an NE and choose Test GNE from the shortcut menu. The Operation Result dialog box is displayed indicating the test result of the GNE.

Check the communication status between the T2000 and the GNE. 1. 2. 3. 4.

----End

29.7 Performing a Loopback

The loopback is a common and effective way to locate equipment faults. By using the T2000 you can set a loopback for equipment. The support for loopback functions depends on equipment types. For details, refer to the specific equipment manuals. A loopback can be performed for different objects. 29.7.1 Looping Back SDH interface This section describes how to set the loopback for the SDH interface on the T2000. Looping back the SDH interface is a common method of locating faults during the test and maintenance of the boards that supports the SDH interface. Through looping back the SDH interface, whether the SDH interface, cables and fibers connected to the SDH interface, service processing module of the board that supports the SDH interface, and the cross-connect board are normal can be determined. 29.7.2 Looping Back PDH interface This section describes how to set the loopback for the PDH interface on the T2000. Looping back the PDH interface is a common method of locating faults during the test and maintenance of the PDH related boards. Through looping back the PDH interface, whether the PDH interface, cables and fibers connected to the PDH interface, service processing module of the board that supports the PDH interface, and the cross-connect board are normal can be determined. 29.7.3 Setting a Loopback for an Ethernet Interface You can set a loopback for an Ethernet interface by using the T2000. The Ethernet interface loopback is a common fault location method used to test and maintain the Ethernet interface board. The Ethernet interface loopback is used to test whether the fiber connections on the Ethernet board, physical layer and MAC layer of the Ethernet interface, and layers over the MAC layer are normal. 29.7.4 Looping Back ATM Interface
29-14 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

29 Common Maintenance Operations

This section describes how to set the loopback for the ATM interface on the T2000. In the case of the ATM interface, the bound channels in the related IMA group of the ATM interface are looped back. Looping back the ATM interface is a common method of locating faults during the test and maintenance of the IMA group. Through looping back the ATM interface, whether the ATM interface, cables and fibers connected to the ATM interface, service processing module of the board that supports the ATM interface, and the cross-connect board are normal can be determined.

29.7.1 Looping Back SDH interface

This section describes how to set the loopback for the SDH interface on the T2000. Looping back the SDH interface is a common method of locating faults during the test and maintenance of the boards that supports the SDH interface. Through looping back the SDH interface, whether the SDH interface, cables and fibers connected to the SDH interface, service processing module of the board that supports the SDH interface, and the cross-connect board are normal can be determined.

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

Context
The loopback modes of the SDH interface include outloop and inloop.
l

As shown in Figure 29-1, outloop indicates that the services received by the NE are returned at the SDH interface without traveling through the cross-connect board. Outloop is used to determine whether the SDH interface, and cables and fibers connected to the SDH interface are normal. Figure 29-1 Outloop
Crossconnection Processing Processing Board Board Board

As shown in Figure 29-2, inloop indicates that the services transmitted by the NE are returned to the cross-connect board at the SDH interface. Inloop is used to determine whether the service processing module of the board and the cross-connect board are normal.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

29-15

29 Common Maintenance Operations

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 29-2 Inloop

CrossProcessing connection Processing Board Board Board

CAUTION
Loopback can interrupt services at the interface. Thus, the loopback operation is only used for locating faults. After the faults are rectified, the loopback at the interface must be cleared.

Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Interface Management > SDH Interface from the Function Tree. Step 2 Then, click the Advanced Attributes tab. Step 3 In the list, select an SDH interface, and set Loopback Mode to Non-Loopback, Inloop, or Outloop according to requirements. Step 4 Click Apply, a warning prompt is displayed. Click Yes, a prompt is displayed indicating that the operation is successful. Step 5 Click Close. ----End

29.7.2 Looping Back PDH interface

This section describes how to set the loopback for the PDH interface on the T2000. Looping back the PDH interface is a common method of locating faults during the test and maintenance of the PDH related boards. Through looping back the PDH interface, whether the PDH interface, cables and fibers connected to the PDH interface, service processing module of the board that supports the PDH interface, and the cross-connect board are normal can be determined.

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

Context
The loopback modes of the PDH interface include outloop and inloop.
29-16 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

l

29 Common Maintenance Operations

As shown in Figure 29-3, outloop indicates that the services received by the NE are returned at the PDH interface without traveling through the cross-connect board. Outloop is used to determine whether the PDH interface, and cables and fibers connected to the PDH interface are normal. Figure 29-3 Outloop
CrossProcessing connection Processing Board Board Board

As shown in Figure 29-4, inloop indicates that the services transmitted by the NE are returned to the cross-connect board at the PDH interface. Inloop is used to determine whether the service processing module of the board and the cross-connect board are normal. Figure 29-4 Inloop
CrossProcessing connection Processing Board Board Board

CAUTION
Loopback can interrupt services at the interface. Thus, the loopback operation is only used for locating faults. After the faults are rectified, the loopback at the interface must be cleared.

Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > Interface Management > E1/ T1 Interface from the Function Tree. Step 2 Then, click the Advanced Attributes tab. Step 3 In the list, select a PDH interface, and set Loopback Mode to Non-Loopback, Inloop, or Outloop according to requirements.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 29-17

29 Common Maintenance Operations

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 4 Click Apply, a warning prompt is displayed. Click Yes, a prompt is displayed indicating that the operation is successful. Step 5 Click Close. ----End

29.7.3 Setting a Loopback for an Ethernet Interface

You can set a loopback for an Ethernet interface by using the T2000. The Ethernet interface loopback is a common fault location method used to test and maintain the Ethernet interface board. The Ethernet interface loopback is used to test whether the fiber connections on the Ethernet board, physical layer and MAC layer of the Ethernet interface, and layers over the MAC layer are normal.

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

Context
You can perform an inloop for an Ethernet interface by using the T2000. The inloop indicates that the Ethernet service transmitted by the NE is returned to the crossconnect board at the Ethernet interface, as shown in Figure 29-5. The inloop at the physical layer is used to test whether the MAC layer and layers over the MAC layer are normal. The inloop at the MAC layer is used to test whether the layers over the MAC layer are normal. Figure 29-5 Inloop
Physical Layer MAC Layer

The outloop indicates that the Ethernet service received by the NE is returned at the Ethernet interface, as shown in Figure 29-6. The outloop at the physical layer is used to test whether the physical layer and the fiber connected to the Ethernet board are normal. Figure 29-6 Outloop

29-18

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

29 Common Maintenance Operations

CAUTION
As a loopback interrupts services, it is only used for fault location and must be released after the fault is removed.

Procedure
Step 1 In the NE Explorer, select the board, and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Select an Ethernet interface from the list and double-click MAC Loopback or PHY Loopback to choose the loopback mode. Step 4 Click Apply, a warning prompt is displayed. Click Yes, a prompt is displayed indicating that the operation is successful. Click Close. ----End

29.7.4 Looping Back ATM Interface

This section describes how to set the loopback for the ATM interface on the T2000. In the case of the ATM interface, the bound channels in the related IMA group of the ATM interface are looped back. Looping back the ATM interface is a common method of locating faults during the test and maintenance of the IMA group. Through looping back the ATM interface, whether the ATM interface, cables and fibers connected to the ATM interface, service processing module of the board that supports the ATM interface, and the cross-connect board are normal can be determined.

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

Context
The loopback modes of the ATM interface include outloop and inloop.
l

As shown in Figure 29-7, outloop indicates that the services received by the NE are returned at the ATM interface without traveling through the cross-connect board. Outloop is used to determine whether the ATM interface, and cables and fibers connected to the ATM interface are normal.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

29-19

29 Common Maintenance Operations

OptiX iManager T2000 Operation Guide for PTN NE Management

Figure 29-7 Outloop

CrossProcessing connection Processing Board Board Board

As shown in Figure 29-8, inloop indicates that the services transmitted by the NE are returned to the cross-connect board at the ATM interface. Inloop is used to determine whether the service processing module of the board and the cross-connect board are normal. Figure 29-8 Inloop
CrossProcessing connection Processing Board Board Board

CAUTION
Loopback can interrupt services at the interface. Thus, the loopback operation is only used for locating faults. After the faults are rectified, the loopback at the interface must be cleared.

Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Step 2 Click the ATM Interface Management tab. Step 3 In the list, select an ATM interface, and set Loopback Mode to No Loopback, Inloop, or Outloop according to requirements. Step 4 Click Apply, a warning prompt is displayed. Click Yes, a prompt is displayed indicating that the operation is successful. Step 5 Click Close. ----End
29-20 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

29 Common Maintenance Operations

29.8 Replacing the Board Type

The PTN equipment supports the function of board type replacement between boards with the same port rate.

Prerequisite
l l l

You must be an NM user with "NE operator" authority or higher. The physical board of the target board for replacement must be in position. The OptiX PTN 3900 supports the ability to replace the TN81XCS board with the TN82XCS board, replace the TN81EG16 board with the TN82EG16 board and replace the TN81SCA board with the TN82SCA board. The OptiX PTN 1900 supports the ability to replace the TN71CXP board with the N72CXP board.

Procedure
Step 1 In the NE Panel, select a board to be replaced, right-click, and then choose Replace Board Type from the shortcut menu.

Step 2 In the dialog box that is displayed, click OK to delete the fibers of the board.

Step 3 In the Replace Board Type dialog box, select the target board from the Usable Board Type drop-down list, and then click OK.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 29-21

29 Common Maintenance Operations

OptiX iManager T2000 Operation Guide for PTN NE Management

Step 4 The Replace Board Type dialog box is displayed, indicating that the board type is being replaced.

Step 5 A dialog box is displayed, indicating that the operation is successful. Then, click Close. ----End

29.9 Resetting Boards

You can reset a board by using the T2000 by following the instructions below. 29.9.1 Reset Reset is a protection scheme for applications and data files on the equipment. When a board is not running properly, you can reset the board so that it returns to the normal state. Reset is of two types: warm reset and cold reset. A cold reset takes more time than a warm reset. After a board is reset, the data on the board is not lost, but the resetting process may interrupt services. 29.9.2 Resetting a Board You can reset a board by using the T2000. Resetting a board is a maintenance method used in the case of an improper board working status.

29.9.1 Reset
Reset is a protection scheme for applications and data files on the equipment. When a board is not running properly, you can reset the board so that it returns to the normal state. Reset is of two types: warm reset and cold reset. A cold reset takes more time than a warm reset. After a board is reset, the data on the board is not lost, but the resetting process may interrupt services.

29-22

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

NOTE

29 Common Maintenance Operations

l l

Performing a warm reset restores the applications and data to the normal state. Warm reset usually does not affect services. Performing a cold reset restores the applications and data to the normal state before a CPU power failure. Cold reset usually affects services.

29.9.2 Resetting a Board

You can reset a board by using the T2000. Resetting a board is a maintenance method used in the case of an improper board working status.

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

Context
Performing a cold reset usually affects services. You can reset a board in the following two ways:
l l

Performing a warm or cold reset to the board by using the T2000. Performing a cold reset to the board by removing and inserting it.

Procedure
Step 1 Double-click an NE on the Main Topology and the Slot Layout is displayed. Step 2 Right-click a non-SCC board and choose Cold Reset or Warm Reset from the shortcut menu. Click OK in the Warning dialog box to confirm the reset. Step 3 Click Close in the prompt dialog box. ----End

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

29-23

OptiX iManager T2000 Operation Guide for PTN NE Management

A Glossary

A
1 1+1 optical path protection

Glossary

At the place where the signals are input, the same channel of optical signals are input to two boards or ports of the WDM equipment through two fibers. The two boards or ports are backed up mutually. When a fault occurs to the working path, the input end of the WDM equipment switches to the protection path. If the working path recovers, the input end of the WDM equipment switch back to the working path.

A Access Control List (ACL) Access Control List (ACL) is a list of IP address. The addresses listed in the ACL are used for authentication. If the ACL for the user is not null, it indicates that the address where the user logged in is contained in the list. For SDH, the virtual containers (VC) to carry concatenated services are consecutive in terms of their service in the frame structures, so that they use the same path overhead (POH). A visible or an audible indication to notify the person concerned that a failure or an emergency has occurred. See also Event. Alarm Indication Signal. A signal sent downstream in a digital network if an upstream failure has been detected and persists for a certain time.

Adjacent Concatenation

Alarm

AIS

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

A-1

A Glossary

OptiX iManager T2000 Operation Guide for PTN NE Management

Alarm acknowledgement

The process during which when an alarm is generated, the operator needs to acknowledge the alarm and take the right step to clear the alarm. If there are excessive errors in a channel, AIS can be inserted in this channel to indicate it is unavailable. For a line board, you can set whether to insert AIS when there are excessive errors in the B1, B2 and B3 bytes. For a tributary board at the E1 or T1 level, you can set whether to insert AIS when there are excessive errors in BIP-2. For a tributary board at the E3 level or higher, you can set whether to insert AIS when there are excessive errors in the B3 byte. Alarm delay includes start delay and end delay. An alarm is not regarded as being generated until the NE has been detecting it for a period of time, and this period of time is the alarm start delay time. An alarm is not regarded as being cleared until the NE has been detecting the ending of it for a period of time, and this period of time is the alarm end delay time. Setting the delay time can avoid the generation of unnecessary alarms due to misreport or jitter. For the port that has already been configured but has no service, this function can be used to avoid generating relevant alarm information, thus preventing alarm interference. The suppressed alarm of a specific object is not reported. The object here may be the networkwide equipment, a specific NE, a specific board and even a specific function module of a specific board. Automatic Level Control. A technique (procedure) to automatically reduce the output power of optical amplifiers to avoid exposure to hazardous levels. The entire capacity of the adapted or characteristic information is set to logic "1". The ALS function of an optical line system automatically switches off the transmitter of a regenerator section in case of cable break in this section.

AIS insertion

Alarm delay time

Alarm reversion

Alarm suppression

ALC

All-ONEs ALS

A-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

A Glossary

APS

Automatic Protection Switching. Autonomous switching of a signal between and including two MS_TT, Sn_TT, or Sm_TT functions, from a failed working trail/ SNC to a protection trail/SNC and subsequent restoration using control signals carried by the K-bytes in the MSOH, HO POH, or LO POH. The rate/work mode of the communication party set as self-negotiation is specified through negotiation according to the transmission rate of the opposite party. Property of an object.

Auto-negotiation

Attribute B Bidirectional (protection) switching

For a unidirectional fault, both directions (of the trail, subnetwork connection, and so on), including the affected and unaffected direction, are switched. When the bit error reaches a specific limit, the equipment will report an alarm. This limit is the bit error alarm threshold. The threshold can be divided into crossing threshold and defect threshold. The unidirectional services from one service source to multiple service sinks are called the broadcast service.

Bit error alarm threshold

Broadcast service

C Concatenation When the standard virtual containers (including VC4/VC3/VC12/VC11) are incapable of carrying the volume of a SDH signal, the containers can be concatenated to function as a larger container. Class of Service. CoS keeps the priority mapping rules. It works in internal ports, especially when there is congestion, CoS is even more important. The services at different levels are processed according to the corresponding priorities. The service with higher priority is processed first and the service with lower priority is discarded when the bandwidth is insufficient.

CoS

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

A-3

A Glossary

OptiX iManager T2000 Operation Guide for PTN NE Management

Client trail

There is an inclusion relation between the trails of different levels, for example, a trail of a certain level contains multiple trails of lower levels. In such a structure, the lower level trail is called the client trail. Characteristic Information. The information passing across a CP or TCP. It is a signal with a specific format, which is transferred on "network connections". The specific formats will be defined in the technology specific Recommendations. A kind of terminal (PC or workstation) connected to a network that can send instructions to a server and get results through a user interface. See also server. The data of a trail at the NE layer is changed. After the trail is re-searched, the original trail becomes a collision trail. Class of Service. CoS keeps the priority mapping rules. It works in internal ports, especially when there is congestion, CoS is even more important. The services at different levels are processed according to the corresponding priorities. The service with higher priority is processed first and the service with lower priority is discarded when the bandwidth is insufficient. Network services are realized through the cross-connections of NEs. The crossconnection is the connection of channels between the tributary board and the line board, or between line boards inside the NE. Alarms that do not clear, or has cleared but is not acknowledged. The performance data stored in the current register is called current performance data. The current 15-minute or 24-hour register (only one for each) is applied to collect the performance data in the current monitoring period. It changed within the monitor period.

CI

Client

Collision trails

CoS

Cross-Connection

Current alarms Current performance data

A-4

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

A Glossary

Custom view

The user-defined view is a subset on the Main Topology. Included network entities can be NE, network management system, link and subnetwork. Generally, the network management personnel need to customize some views and select the network entity under their management from the Main Topology. The Clock View provides a visible platform to implement the clock management function.

Clock View

D Data interface service The service that uses the F1 byte in an SDH frame or some undefined bytes to transmit information such as call charge, network management system information and power supply monitoring. Data Communications Channel. The data channel that uses the D1D12 bytes in the overhead of an STM-N signal to transmit information on operation, management, maintenance and provision (OAM&P) between NEs. The DCC channels that are composed of bytes D1D3 is referred to as the 192 kbit/s DCC-R channel. The other DCC channel that are composed of bytes D4D12 is referred to as the 576 kbit/s DCC-M channel. The cross-connection that exists on an NE but cannot form trails on the network management system. A procedure that involves duplicating data from a NetWare partition on one hard disk to the NetWare partition on another disk. Disk mirroring pairs multiple hard disks on the same channel, and like disk duplexing, writes data to both the original and secondary disk. If the original disk fails, the secondary disk automatically takes over. Disk mirroring cannot protect against failures that occur along the channel between the disks and the NetWare server, because the duplicate disks exist on the same channel.

DCC

Discrete service

Disk Mirroring

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

A-5

A Glossary

OptiX iManager T2000 Operation Guide for PTN NE Management

DNI

Dual node interconnection is an architecture between two rings where two nodes in each ring are interconnected. The two interconnections between the two rings can be arranged to provide protection of the traffic crossing from one ring to the other.

E Extra traffic During fault-free conditions, it is possible to use the protection channels to carry additional traffic. This additional traffic, which is referred to as extra traffic, has lower priority than the normal traffic on the working channels and has no means for protection. An aggregate of multiple managed equipment. Equipment set facilitates the user authority management on equipment in the management domain of the network management system. If some operation authorities over one equipment set are assigned to a user (user group), these operation authorities over all equipment of the equipment set are assigned to the user (user group). Embedded Control Channel. An ECC provides a logical operations channel between SDH NEs,utilizing a data communications channel (DCC) as its physical layer. Environment Monitoring Unit. A type of power and environment monitoring unit that is used to monitor the environment variables, such as the power supply and temperature. With external signal input through the relay, fire alarm, smoke alarm, burglary alarm, and so on can be monitored as well. This command tests whether a switching protocol can work normally without completing the actual switching operation. This command exercises ring protection switching of the requested channel without completing the actual bridge and switch. The command is issued and the responses are checked, but no working traffic is affected.

Equipment set

ECC

EMU

Exercise switching

Exerciser - Ring

A-6

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

A Glossary

Exerciser - Span

This command exercises span protection of the requested channel without completing the actual bridge and switch. The command is issued and the responses are checked, but no working traffic is affected. The serial number of a subnetwork where an NE resides, which is usually used to distinguish different network segments. An extended ID and an ID form the physical ID of an NE. An unprotected chain like ADM-ADM-TM or ADM-ADM-ADM. The end-point NEs of a link is of the ADM type. As this type of protection subnetwork can be extended, we name it extended protection subnetwork.

Extended ID of NE

Extended protection subnet

F Failure The fault cause persisted long enough to consider the ability of an item to perform a required function to be terminated. The item may be considered as failed; a fault has now been detected. A fault is the inability of a function to perform a required action. This does not include an inability due to preventive maintenance, lack of external resources, or planned actions. The user path byte, which is reserved for the user but usually it is special for network providers. The F1 byte is mainly used to provide the temporary data or voice path for special maintenance objectives. It belongs to the regenerator section overhead byte. The user channel bytes. These two bytes provide the user with the communication between path units related to payload. They belong to the higher order path overhead byte. The general name of optical fiber and cable. The physical entity that connects transport equipment in a transport network, bears the transmitted object (user information, network management information) and implements the transport function.

Fault

F1 byte

F2,F3 bytes

fiber/cable

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

A-7

A Glossary

OptiX iManager T2000 Operation Guide for PTN NE Management

Forced switching

This command performs the ring switch from working channels or boards to the protection channels or boards. This switch occurs regardless of the state of the protection channels or boards, unless the protection channels or boards are satisfying a higher priority bridge request. The system that can transmit information in both directions on a communication link. In this search mode, the network management system first deletes all the trail data on the network management system and reserves the service configuration data of respective NEs, and then re-searches for the service configuration data of respective NEs on the network management system to form the new trail information. In the full search mode, all the trail information on the network management system will be deleted first (Only the trail information at the network layer on the network management system is deleted, while the service configuration information of NE in NE layer on the network management system and on the NE still remain). Then the service configuration information of respective NEs in the NE layer on the network management system is researched to form the trail information in the network layer on the network management system.

Full duplex Full filtering trail

Full search

G Gateway The equipment that is used to connect two independent networks that use different communication protocols. IP address is used for TCP/IP communication between an NE and the network management system, which is effective only when it is used for TCP/IP communication. That is, only the gateway NE needs the IP address. IP address cannot be used to identify an NE uniquely. NEs in different TCP/IP networks may have the same IP address. And one NE may have several IP addresses (for example: an IP address of a dial-up network, an IP address of the Ethernet port and so on).

Gateway IP

A-8

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

A Glossary

Gateway NE

The NE that communicates with the NMS and other NEs through a data communication network. Through the GUI Cut-Through (GCT) function, you can view the GUI of the T2000 client and operate the T2000 directly on the T2100 client, thus to realize centralized monitoring and management of the network.

GUI Cut-Through (GCT)

H Host name Name of the computer that functions as a main controlling point in a network and provides special service to the users. The system that transmits information in only one direction on the communication link at any time. The ability of a system to continuously perform its functions during a long period, which may exceeds the suggested working time of the independent components. You can obtain the high availability (HA) by using the error tolerance method. Based on learning cases one by one, you must also clearly understand the limitations of the system that requires an HA ability and the degree to which the ability can reach. Alarms that have cleared and been acknowledged. The performance data stored in the history register and the auto-report performance data stored on the network management system are called history performance data in a unified way. The hotline phone number can be called immediately by picking up only, but not by dialing.

Half duplex

High Availability

History alarms History performance data

Hotline phone

I Idle resource optical NE When the T2000 is started successfully, an NE icon called "Idle ONE" will be displayed on the topological view. In this NE, the subracks and boards that are not divided to other optical NEs (such as OTM, OADM and other NEs) are retained.

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

A-9

A Glossary

OptiX iManager T2000 Operation Guide for PTN NE Management

In-Service Trail Modifying

A way of trail modification that allows you to configure new routes for a trail and enables the system to automatically delete the original trail after you apply the settings to the NE. In this search mode, the network management system first reserves the trail data of the current client and then re-searches the service configuration data of respective NEs on the network management system according to the newly given search condition to form the new trail data and combine it with the original trail data to get the result. The increment search mode compares the trail information in network layer on the network management system with the service configuration information of respective NEs on the network management system. If they are inconsistent, the trail information will be fed back into the list as an "Inconsistent Trail". When the user has deleted the inconsistent trail information, the system will re-search for the service configuration information that has not formed the trail in the NE layer on the network management system. An output signal is returned back to the corresponding input port. This function is implemented by the wavelength conversion boards that are capable of dual fed and selective receiving. The dual fed is implemented by adding a passive optical splitter to the tributary. The signal selection is implemented by the SCC turning off the laser at the tributary side with poorer signal quality according to the signal quality of the lines of two wavelength conversion boards, and letting the channel of light with higher quality pass through the coupler. The coupler is also a passive device and only one channel of light can pass through it. If there are two channels of light passing through the coupler, they interferes each other that would cause bit error to the service. Hence, it is necessary to ensure that only the channel of light with higher quality pass through the coupler at the same time. A concept in the telecommunications area. A site that manages fiber/cable or grooms services

Incremental filtering trail

Incremental search

Inloop Inter-board wavelength protection

Intermediate office

A-10

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

A Glossary

Intra-Board wavelength protection

The intra-board wavelength protection is mainly implemented by the wavelength conversion board with dual fed and signal selection function. The dual fed is implemented by the optical divider inside the board, while the signal selection is implemented by the board turning off the laser of one of the receiving optical interfaces. Hence, this protection mode is also called optical wavelength intra-board path protection. The switching in this protection mode can be completed within a short time, but the services must be interrupted during the maintenance of the damaged board or equipment. Hence, this protection mode has a relatively lower reliability. Internet Protocol Address. A 32-bit address that uniquely identifies a node in an IP Internet network. An IP address consists of a network ID and a unique host ID. An IP address consists of the decimal values of its eight bytes, separated with periods; for example,192.168.7.27. A type of special NE or an optical port on an NE. Logically, an isolated node does not comprise an SDH NE of any types, which are TM, ADM, REG and DXC

IP address

Isolated node

L Layer A concept used to allow the transport network functionality to be described hierarchically as successive levels; each layer being solely concerned with the generation and transfer of its characteristic information. Local Craft Terminal. The terminal software that is used for local maintenance and the management of NEs in the singer-user mode, to realize integrated management of multiservice transmission network. See also T2000. A permission provided by a vendor to authorize the use of specific functions of a product. Usually the license consists of encrypted codes, and the operation authority varies with different level of license.

LCT

License

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

A-11

A Glossary

OptiX iManager T2000 Operation Guide for PTN NE Management

Lock status

Services are not switched to the protection board or channel when a fault occurs, if currently no switching takes place. If currently the switching takes place, after the working board or channel recovers to normal, the services are not switched back to the working board or channel. When the switching condition is satisfied, this function disables the service from being switched from the working channel to the protection channel. When the service has been switched, the function enables the service to be restored from the protection channel to the working channel. The client login mode includes single-user and multi-user login modes. The multi-user mode is the default mode.

Lockout of Switching

Login mode

M Management flag A check box helps you to determine whether the trail is a managed object of the trail management function at the network layer. By default, trails are managed objects. If choosing not to manage it through the trail management function, you can manage the cross-connections of an individual NE through the service configuration function performed at a node. The information that is used for network management in a transport network. When the protection channel is efficient and there is no higher-level switching request, services are manually switched from the working channel to the protection channel, thus testing whether the network still has the protection capability. The WDM network node that has the spectrum analysis unit in the link for which the ALC function is configured.

Management information Manual switching

MS node

A-12

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

A Glossary

Multi-trail protection service

It is a protection mode in which multiple services with different trails but with the same sink protect an important service with the same sink. This protection mode supports protecting important services through nonoptical network trails, such as microwave. It presently supports that three protection trails protect one service trail. At the trail sink, it monitors the quality of protection trail signals and protects important services according to the priority and the signal quality. The default network management system client interface, and all topology management functions are accessed here.

Main Topology

N NE Network Element. NE includes the hardware unit and the software running on it. Usually, one NE has at least an SCC (system control and communication) board which responsible for the management and monitoring of the NE. The NE software runs on the SCC board. The NE configuration data saved on the SCC board of the equipment, which can be uploaded to the network management system and then stored in databases on the network management system NE side. The logical layer of the network management system that saves the network data. The configuration data related to a network is saved in databases. Network Node Interface. The interface at a network node which is used to interconnect with another network node. See also SDH NNI. In non-revertive switching, there is a working and protection line, board and so on. Services remain on the protection line or board if the switch requests are terminated; that is, when the fault that caused them to switch to the protection line or board is cleared. The databases that are saved in an NE. Usually, the databases are saved in the SCC board of an NE.

NE side

Network layer

NNI

Non-revertive

NE database

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

A-13

A Glossary

OptiX iManager T2000 Operation Guide for PTN NE Management

NE ID

In a network, each NE corresponds to a unique identifier, that is, the NE ID. In the OptiX transmission equipment, it is specified that the NE ID is a 24-bit binary digit, that is, three bytes. The DIP switch on the SCC board of the NE constitutes the lower 16 bits of the NE ID. The higher eight bits of the NE ID is the extended ID (default value: 9), which is also called the subnetwork number. The extended ID is usually used to identify different subnetworks. The NE configuration data saved in the T2000 databases. If data exists in an NE, the T2000 uploads the data in an NE and saves it at the NE layer. If data does not exist in an NE, the T2000 downloads the data at the NE layer to the NE. Consistency between the data on the T2000 and the data on the NE is the precondition of efficient running of the transmission equipment. The network configuration data that is saved in T2000 databases and is the data source for the network function of the T2000. The network layer data on the T2000 includes three parts: fiber connection data, protection subnetwork and SDH NNI data and trail information. Network Management. See T2000. A subnet that has no protection. The range of IP addresses in which the gateway NE functions. The main operation interface, of the T2000, which is used to manage the OptiX equipment. In the NE Explorer, the user can configure, manage and maintain the NE, boards, and ports on a per-NE basis. A graphical user interface, of the network management system, which displays subracks, boards, and ports on an NE. In the NE Panel, the user can complete most of the configuration, management and maintenance functions for an NE.

NE layer data on the T2000

Network layer data on the T2000

NM Non-protection subnet Network segment NE Explorer

NE Panel

O Outloop An input signal is directly returned back to the corresponding output port.

A-14

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

A Glossary

OWSP

Optical Wavelength Shared Protection. OWSP is a bidirectional ring, where each node is equipped with an OWSP. There are two channels (1 and 2) in the main optical path on the internal and external rings in each span on a ring. The fibre and the OWSP on the main optical path are connected with the optical ports inputting 1 and 2 on the mux/ demux board (unnecessary to be connected with the OTU), and thus 1 and 2 can be added and dropped at every node.

P Path Path protection A trail in a path layer. The working principle of path protection: When the system works in path protection mode, the PDH path uses the dual fed and signal selection mode. Through the tributary unit and cross-connect unit, the tributary signal is sent simultaneously to the east and west lines. Meanwhile, the cross-connect unit sends the dual fed signals from the opposite end to the tributary unit, and the tributary unit selectively receive the signal from the two signals. The memory space that is used to store performance events. A thresholding mechanism can be used to generate an autonomous event report when the performance of a transport entity falls below a predetermined level. The unit that is used to monitor power supply in the equipment. In case the service route provides multiple service protections, different protection strategies can be selected as required. Protection strategy refers to the protection mode given the priority in use for the trail: protection, no protection, and extra traffic. Of the above, the protection preference is divided into trail protection and sub-network connection protection. A network concept in the network management system. A protection subnet is not an MSP ring or a path protection ring. A protection subnet consist of NEs and fiber connections.

Performance register Performance threshold

PMU Protection policy

Protection subnet

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

A-15

A Glossary

OptiX iManager T2000 Operation Guide for PTN NE Management

Protocol controller status

The status of the protocol controller of the protection subnet of the MSP or SNCP type. The statuses are not started, started, starting, partially started. A major separate area of a window or dialog box, usually used for display rather than data entry. The user interface, of the network management system, which is used to manage protection in the network.

Pane

Protection View

R Remote Network Monitoring (RMON) A manage information base (MIB) defined by the Internet Engineering Task Force (IETF). RMON is mainly used to monitor the data flow of one network segment or the entire network. In revertive operation, the traffic signal (service) always returns to (or remains on) the working SNC/trail if the switch requests are terminated; i.e. when the working SNC/trail has recovered from the defect or the external request is cleared. Resource sharing means that a physical link resource may belong to multiple protection subnetworks. The path that a trail passes through. The constraint conditions for calculating a route. When creating a trail, the user can specify the explicit route and the NEs that the trail cannot pass. The explicit route and the NEs are the constraints for calculating the route. The 25-pin interface standard that is defined by EIA. In the asynchronous transfer mode and there is no hand-shaking signal. It can communicate with RS232 and RS422 of other stations in point-to-point mode and the transmission is transparent. Its highest speed is 19. 2 kbit/s. The specification that defines the electrical characteristics of balanced voltage digital interface circuits. The interface can change to RS232 via the hardware jumper.

Revertive switching

Resource sharing

Route Route constraint

RS232

RS422

A-16

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

A Glossary

ROADM

Reconfiguration Optical Add/Drop Multiplexing. ROADM helps you to terminate or pass through any one wavelength at every node without affecting the existing services. At the same time, ROADM can change wavelengths through the network management system remotely, to adjust wavelengths added or dropped in a quick and convenient manner. In addition, ROADM enables power equalization at path level through a built-in power equalization function, and thus adjusts power for passthrough paths in a better way than a bandbased dynamic gain equalizer (DGE) does.

S Section S1 byte A trail in a section layer. To implement protection switching of clocks in the whole network, the NE must learn about the clock quality information of the clock reference source it traces. Therefore, ITU-T defines S1 byte to transmit the network synchronization status information. The IPA safe switch is set in consideration of the long-span networking requirement, which cannot allow too low output optical power. If the safe control switch is turned off, IPA restarting optical power is the specified output power of the OAU. Otherwise, the IPA restarting optical power is restricted to less than 10 dBm. It is the text file describing the physical information and configuration information of the entire network, including the Networkwide Configuration File, NE Port Naming File , NE Configuration File, NE List File, NM Computer Information File, Service Actualization Script, Network Layer Information File, Network Modeling and Design Information File and ASON Information File. SD refers to signal degradation. The multiplex section protocol defaults to start switching in case of signal loss. In practice, signal degradation severely affects some services, so protection switching is needed. Or, you can turn off this trigger condition through the switch to avoid MS switching when the signal degrades.

Safe control switch

Script file

SD trigger condition

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

A-17

A Glossary

OptiX iManager T2000 Operation Guide for PTN NE Management

SD

Signal Degrade. A signal indicating the associated data has degraded in the sense that a degraded defect (dDEG) condition is active. A trail that spans both the SDH and ASON domains. Signal Fail. A signal indicating the associated data has failed in the sense that a near-end defect condition (not being the degraded defect) is active. SDH Network Node Interface. It is applied to build communications connection with the equipment beyond the management area of the network management system. Usually, the NM creates an SDH NNI by creating a logical system on the port of an idle line board, and the NE must be a TM without protection and fiber connection. The range of searching for NEs. There is an inclusion relation between the trails of different levels, for example, a trail of a certain level contains multiple trails of lower levels. In such a structure, the bearer trail that bears another trail of lower level is called the server trail. In this search mode, the NM re-searches the trail data displayed by the current client according to the given search conditions, helping the customer find the trail data which interests him the most. A menu that is displayed when right-clicking an objects name or icon. Also called a context menu. The ECC channel realized by means of serial port. The route of a service clock from the source to the sink in a WDM system. The working route can be in the form of point-to-point or broadcast (That is, an input clock source corresponds to multiple output clock sources).

SDH-ASON Trail SF

SDH NNI

Search domain Server trail

Secondary filter trail

Shortcut menu

Serial port extended ECC Service clock working route

A-18

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

A Glossary

Service configuration policy

When pass-through services are configured on the newly added nodes, the mode of highorder or low-order to pass through can be selected. When the VC12 service over a VC4 exceeds a preset threshold, higher order cross-connect is selected, otherwise lower order cross-connect is selected. When the services are not VC12 ones, they are converted into VC12 equivalents. For example: if there are two VC3 and four VC12 services on a VC4, there should be 21x2+4 = 46 VC12 services. To indicate the status of loading services in an SDH frame by using the C2 or V5 byte in the SDH path overhead. An agreement signed between the network carrier and the client, concerning the treatments that the client can receive when services are transferred in the network. The agreement contains the information on technology and commerce. Usually, SLA refers to a specific QoS. Serial Line Interface Protocol, defines the framing mode over the serial line to implement transmission of messages over the serial line and provide the remote host interconnection function with a known IP address. The network that consists of a group of interconnected or correlated NEs, according to different functions. For example, protection subnet, clock subnet and so on. Subnetwork connection protection uses the 1 +1 mode. SNCP is of 1+1 protection mode. Payloads are transmitted simultaneously on both the working and the protection subnetwork connections. When the working subnetwork connection fails, or when its performance deteriorates to a certain level, at the receiving end of the sub-network connection, the signal from the protection sub-network connection is selected according to the preference rule. Switching usually takes the single-end switching mode, thus no protocol is needed.

Service loading indication

SLA (Service Level Agreement)

SLIP

Subnet

Subnet connection protection

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

A-19

A Glossary

OptiX iManager T2000 Operation Guide for PTN NE Management

Subnet mask

Also referred to as the network mask off code, it is used to define network segments, so that only the computers in the same network segment can communicate with one another, thus suppressing broadcast storm between different network segments. Subnetwork number is used to differentiate the different network sections in the subnetwork conference. Actually it is the first several digits (one or two) of the user phone number. An orderwire phone number is composed of the sub-network number and the user number. The SNCP node of a ring subnet that can support the ability to dually feed and selectively receive trails. In this way, subnet connection protection is realized . Usually, the node of the path protection type is set as an SNCP node. The spread type of ATM service includes point-to-point (p2p) and point-to-multipoint (including p2mpRoot and p2mpLeaf). There may be the case that several protected boards need to be switched; thus the tributary board switching priority should be set. If the switching priority of each board is set the same, the tributary board that fails later cannot be switched. The board with higher priority can preempt the switching of that with lower priority. When synchronizing the alarms, the network management system checks the alarms in the network management system database and the alarms in the NE. If they are inconsistent, the alarms in the NE are uploaded to the network management system database and overwrite the old ones. To re-upload all services carried on the physical fiber links. To apply the system time of the network management system server to NEs so as to keep the time of all NEs consistent.

Subnet number

SNCP node

Spread type

Switching priority

Synchronize Alarm

Synchronize Fiber Service Synchronize NE time

A-20

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

A Glossary

T2000

The subnetwork management system (SNMS) in the telecommunication management network (TMN) hierarchy. The T2000 is located between the NE level and network level. The T2000 provides all management functions at the NE layer and some of the management functions at the network layer. See also NM. The network level management system for the optical transport network, and is located in the network management layer (NML) in the TMN hierarchy. The NE layer management system for the optical transport network. It can manage a maximum of 37 NEs. The T2000 LCT can uniformly manage OptiX series transmission equipment from Huawei, such as SDH, WDM, PTN equipment. See also LCT.

T2100

T2000 LCT

Tag/Untag

The Ethernet port that can identify and transmit the packets with an 802.1q tag header is referred to as a Tag port; otherwise it is referred to as an Untag port. A source NE or a sink trail. The network management system topology is a basic component of the man-machine interactive interface. The topology clearly shows the structure of the network, the alarms of different NEs,sub-networks in the network, the communication status as well as the basic network operation status. It is the traffic frame discard control. Two options are provided: enable and disable. It indicates the means by which the NE discards cells when the network is congested. When the frame discard mark is closed, the cells will be discarded at the cell level; when it is opened, they will be discarded at the frame level. Here, "frame" refers to the AAL protocol data unit. A "transport entity" which consists of an associated pair of "unidirectional trails" capable of simultaneously transferring information in opposite directions between their respective inputs and outputs.

Terminal NE Topology

Traffic frame discard flag

Trail

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

A-21

A Glossary

OptiX iManager T2000 Operation Guide for PTN NE Management

Trail consistency check

Check whether the circuit route and the activation status of the NM side and NE side are the same, clear the superfluous MOs and combine some of the circuits. During network expansion, such an operation as adding fibers to the SDH NNI or configuring/deleting services through the configuration layer will result in circuit inconsistency. A network level management function of the network management system. Through trail management, you can configure end-to-end services, view graphic interface and visual routes of a trail, query detailed information of a trail, filter, search and locate a trail quickly, manage and maintain trails in a centralized manner, manage alarms and performance data by trail, and print a trail report. The user interface of the network management system, that is used to manage trails based on topologies. The Trail View helps the user to quickly configure and maintain trails. See also Protection View, Clock View. The route that consists of the physical media (such as fibers and NEs)that a trail passes through. A route that bears Ethernet services in the network management system. The equipment level protection that uses one standby tributary board to protect N tributary boards . When a fault occurs on the working board, the SCC issues the switching command, and the payload of the working board can be automatically switched over to the specified protection board and the protection board takes over the job of the working board . After the fault is cleared, the service is automatically switched to the original board

Trail management function

Trail View

Transmission media layer route

Trunk link TPS protection

U Upper threshold The value that can generate a performance threshold crossing if exceeded.

A-22

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

A Glossary

UAT

Unavailable Time. A UAT event is reported when the monitored object generates 10 consecutive severely errored seconds (SES) and the SESs begin to be included in the unavailable time. The event will end when the bit error ratio per second is better than 10-3 within 10 consecutive seconds. Unidirectional (Protection) Switching . For a unidirectional fault (that is, a fault affecting only one direction of transmission), only the affected direction (of the trail, subnetwork connection) is switched. User Network Interface. The interface between the user and a network node. Services transmitted through an ordinary way, once a failure or interruption occurs, the data cannot be restored for lack of protection mechanism. The service that is not terminated within the management domain of the network management system. Usage Parameter Control/Network Parameter Control.During the communication, the UPC is implemented to monitor the actual traffic on each virtual circuit that is input to the network. Once the specified parameter is exceeded, measures will be taken to control. NPC is similar to the UPC in function. The difference is that the incoming traffic monitoring function is divided into UPC and NPC according to their positions. The UPC locates at the user/ network interface, while the NPC at the network interface. To query all or some of the configuration data of the NE to the network management system and overwrite the configuration data saved at the NE layer of the network management system. The user of the network management system client or NE user.The user and password define the corresponding authority of operation and management.

Unidirectional (protection) switching

UNI Unprotected

Unterminated Service

UPC/NPC

Upload

User

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

A-23

A Glossary

OptiX iManager T2000 Operation Guide for PTN NE Management

User group

User set refers to the set of NMS users with the same management authorities. The default user group includes: system administrator, system maintainer, system operator and system supervisor. The attributes of user set include name and detailed description.

V Virtual fiber The fiber that is created between different equipments. A virtual fiber is used to represent the optical path that bears SDH services in a WDM system. The channels (that is trail group) provided for trail-layer network nodes (such as a switch) in a path-layer network, and act as the basic unit of transport capacity of paths between trail-layer network nodes. The path rate of the VC4 server trail is 150.336 Mbit/s. The VC4 server trail provides transparent channels (that is, circuit group) for circuit-layer network nodes (for example, a switch) in a path-layer network, and acts as the basic unit of inter-office communication path. When the VC4 server trail is configured, only the higher order cross-connection of VC4 is generated in the intermediate NE, but no cross-connection is generated at the two ends, that is, no service is added/dropped. Therefore, the VC4 server trail is not a traditional service. It is only the basis for VC3 and VC12 trail creation. Virtual Channel Connection. The VC logical trail that carries data between two end points in an ATM network. Virtual Channel Identifier . The identifier in the ATM (Asynchronous Transfer Mode) cell header that identifies to which virtual channel the cell belongs. The field in the ATM (Asynchronous Transfer Mode) cell header that identifies to which VP (Virtual Path) the cell belongs. For SDH, the virtual containers (VC) to carry concatenated services are independent in terms of their location in the frame structures, so that they can be located flexibly.

VC12,VC3 trail

VC4 server trail

VCC

VCI

VPI

Virtual concatenation

A-24

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

A Glossary

Virtual NE

Like a normal NE, a virtual NE is also displayed with an icon on a window , but it is only an NE simulated according to the practical situation, which does not represents an actual NE. Therefore, the actual status of this NE cannot be queried and its alarm status cannot be displayed with colors. Usually, when the trail management function is used for the NEs or subnets the network management system cannot manage, or the equipment is interconnected to the equipment from other vendors for service configuration, the end-to-end service configuration method and the trail management capability are provided.

W Wave band A board like the MB2 divides the wavelength resources into such fixed wavelength groups as 1 4, 5 8 and 9 12, and so on. A wavelength group is called a wave band, and a wave band carrying services to be added or dropped is called add/drop wave band. Wait to Restore. This command is issued when working channels meet the restore threshold after an SD or SF condition. It is used to maintain the state during the WTR period unless it is preempted by a higher priority bridge request. A period of time that must elapse before a trail/connection that is recovered from a fault can be used again to transport the normal traffic signal and/or to select the normal traffic signal. The wavelength path protection ring comprises the working ring and the protection ring. Service signals are transmitted in the two rings in opposite directions. In the wavelength path protection ring, service signals from one node (such as node A) to another node (such as node C) are transmitted via the working ring and the protection ring at one time. Node C receives the signals from the two rings at the same time and selects the signal with higher quality.

WTR

WTR time

Wavelength path protection ring

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

A-25

A Glossary

OptiX iManager T2000 Operation Guide for PTN NE Management

Wavelength protection group

The important data that is used to describe the wavelength protection structure. The wavelength path protection can only work with the correct configuration of the wavelength protection group. The ring-chain structure that is used to describe wavelength protection . The wavelength protection subnet is the basic network-level information and the basic network-level data oriented to user . The user can create or delete a protection subnet, set parameters for the protection subnet as required. In this way, the management at the network layer is realized. A specific path that is part of a protection group and is labeled working. Wavelength Cross-Connection Protection. The services that have path protection on a ring network. Services are dually fed and selectively received. The working service and the protection services are switched by using the cross-connection function.

Wavelength protection subnet

Working path WXCP service

A-26

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

B Acronyms and Abbreviations

B
A ADM AIS ALC ALS AMI APE APS ATM AUX B BIOS BITS BWS C CDE CRC D DCC DCN DDN DNI

Acronyms and Abbreviations

Add/Drop Multiplexer Alarm Indication Signal Automatic Level Control Automatic Laser Shutdown Alternate Mark Inversion code Automatic Optical Power Equalization Automatic Protection Switching Asynchronous Transfer Mode Auxiliary Equipment

Basic Input/Output System Building Integrated Timing Supply System Backbone WDM System

Common Desktop Environment Cyclic Redundancy Code

Data Communication Channel Data Communication Network Digital Data Network Dual Node Interconnection

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

B-1

B Acronyms and Abbreviations

OptiX iManager T2000 Operation Guide for PTN NE Management

DGE DPC DSE DWDM E ECC EGT EML EMS EPL EPLAN ESCON EVPL EVPLAN F FEC FTP G GCM GE GNE GUI H HA HTTP I ID IGMP IMA iMAP IP

Dynamic Gain Equalizer Destination (signalling) Point Code Dispersion Slope Equalizer Dense Wavelength Division Multiplexing

Embedded Control Channel Gigabit Ethernet Transparent Transmission Board Element Management Layer Element Management System Ethernet Private Line Ethernet Private LAN Enterprise System Connection Ethernet Virtual Private Line Ethernet Virtual Private LAN

Forward Error Correction File Transfer Protocol

Global Cluster Manager Gigabit Ethernet Gate Network Element Graphical User Interface

High-Availability Hyper-Text Transmission Protocol

Identification/Identity Internet Group Management Protocol Inverse Multiplexing for ATM Integrated Management Application Platform Internet Protocol

B-2

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

B Acronyms and Abbreviations

IPA ISDN ITL ITU-T L LAN LCAS LCS LCT LOS LPT LSP M MAC MCA MDI MDP Mgr MIB MML MO MODEM MOIT MON MPLS MS MSP N NE NEL

Intelligent Power Adjustment Integrated Services Digital Network Interleaver Unit International Telecommunication Union - Telecommunication Standardization Sector

Local Area Network Link Capacity Adjustment Scheme Leased Circuit Service Local Craft Terminal Loss Of Signal Link-state Pass Through Label Switching Path

Media Access Control Multi-channel Spectrum Analyzer Unit Medium Dependent Interface Message Dispatch Process Manager Management Information Base Man Machine Language Managed Object Modulator-Demodulator Managed Object Instance Tree MONitor Multi-Protocol Label Switching Multiplex Section Multiplex Section Protection

Network Element Network Element Level

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

B-3

B Acronyms and Abbreviations

OptiX iManager T2000 Operation Guide for PTN NE Management

NM NML NMS NNI NSAP NTP O OA OADM OAM OAMS OCh OCP OD ODU ODUk OEQ OIF OLA OLP OM OMS OMU ONE OPUk OSC OSF OSI OSN OSNR OSPF

Network Management Network Management Layer Network Management System Network-network Interface Network Service Access Point Network Time Protocol

Optical Amplifier Optical Add/Drop Multiplexer Operations, Administration and Maintenance Optical fibre line Automatic Monitoring System Optical Channel Optical Channel Protection Optical Demultiplexing Optical Demultiplexing Unit Optical Channel Data Unit-k Optical Equalizer Optical Internetworking Forum Optical Line Amplifier Optical Line Protection Optical Multiplexing Optical Multiplexing Section Optical Multiplexer Unit Optical Network Element Optical Channel Payload Unit-k Operation Supervisory Channel Operation System Function Open Systems Interconnection Optical Switch Node Optical Signal to Noise Ratio Open Shortest Path First

B-4

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

B Acronyms and Abbreviations

OTDR OTM OTN OTS OTU OTUk P P2P PC PDH PE PP PSTN PVP Q QoS R RAS RDMS RMON RPR RS RSTP RSVP RTN RUP S SAN SCC SCS SD

Optical Time-Domain Reflectometer Optical Terminal Multiplexer Optical Transmit Network Optical Transmission Section Optical Transponder Unit Optical Channel Transport Unit-k

Point To Point Personal Computer Plesiochronous Digital Hierarchy Provider Edge Path Protection Public Switched Telephone Network Permanent Virtual Path

Quality of Service

Remote Access Server Relational Database Management System Remote Monitoring Resilient Packet Ring Regenerator Section Rapid Spanning Tree Protocol Resource Reservation Protocol Radio Transmission Node Rational Unified Process

Storage Area Network System Control & Communication Unit Sync Optical Channel Separator Board Signal Degradation

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

B-5

B Acronyms and Abbreviations

OptiX iManager T2000 Operation Guide for PTN NE Management

SDH SF SMC SML SMS SMTP SNCMP SNCP SNCTP SNML SNMS SONET SRLG SSM SSU T TCM TCP/IP TDA TDC TE TIM TMN TPS TU U UAT UML UPC/NPC UPSR UTC

Synchronous Digital Hierarchy Signal Failure Optical Supervisory Channel Unit Service Management Layer Service Management System Simple Mail Transfer Protocol Sub-Network Connection Multiple Protection Sub-Network Connection Protection Sub-Network Connection Tunnel Protection Sub-Network Management Layer Subnetwork Management System Synchronous Optical Network Shared Risk Link Group Synchronization Status Message Synchronization Supply Unit

Time Compressed Multiplex Transmission Control Protocol/ Internet Protocol Tone & Data Access Unit Tunable Dispersion Compensator Traffic Engineering Trail trace Identifier Mismatch Telecommunication Management Network Tributary Protection Switching Tributary Unit

Unavailable Time Unified Modeling Language Usage Parameter Control/Network Parameter Control Unidirectional Path Switched Ring Universal Time Coordinated

B-6

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Issue 01 (2009-06-30)

OptiX iManager T2000 Operation Guide for PTN NE Management

B Acronyms and Abbreviations

V VB VCI VCS VLAN VOA VPI VPN VVR W WAN WBA WDM WSF WTR WXCP Wide Area Network WDM Optical Booster Amplifier Unit Wavelength Division Multiplexing Work Station Function Wait-to-Restore Wavelength Cross-Connection Protection Virtual Bridge Virtual Channel Identifier Veritas Cluster Server Virtual Local Area Network Variable Optical Attenuator Unit Virtual Path Identifier Virtual Private Network Veritas Volume Replicator

Issue 01 (2009-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

B-7