Operation Guide For PTN End-To-End Management: Imanager U2000 Unified Network Management System V100R002C01

iManager U2000 Unified Network Management System
V100R002C01
Operation Guide for PTN End-to-End
Management
Issue 01
Date 2010-08-16
HUAWEI TECHNOLOGIES CO., LTD.

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

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

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

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

Intended Audience
The Manager U2000 Operation Guide for PTN End-to-End Management describes the
operations, such as how to configure the communication, clock and service of the PTN
equipment on the U2000. This document also provides the acronyms and abbreviations.
This document guides the user to understand basic operations of the U2000.
The intended audiences of this document are:
l Network Monitoring Engineer
l Data Configuration Engineer
l NM Administrator
l System Maintenance Engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
DANGER
Indicates a hazard with a high level of risk
which, if not avoided, will result in death or
serious injury.
WARNING
Indicates a hazard with a medium or low level
of risk which, if not avoided, could result in
minor or moderate injury.
iManager U2000
Operation Guide for PTN End-to-End Management About This Document
iii
Symbol Description
CAUTION
Indicates a potentially hazardous situation
that, if not avoided, could cause equipment
damage, data loss, and performance
degradation, or unexpected results.
NOTE
Provides additional information to emphasize
or supplement important points of the main
text.
TIP
Indicates a tip that may help you solve a
problem or save you time.

Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Boldface The keywords of a command line are in
boldface.
Italic Command arguments are in italic.
[ ] Items (keywords or arguments) in square
brackets [ ] are optional.
{ x | y | ... } Alternative items are grouped in braces and
separated by vertical bars. One is selected.
[ x | y | ... ] Optional alternative items are grouped in
square brackets and separated by vertical
bars. One or none is selected.
{ x | y | ... } * 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 | ... ] * Optional alternative items are grouped in
square brackets and separated by vertical
bars. A maximum of all or none can be
selected.

About This Document
iManager U2000
Operation Guide for PTN End-to-End Management
iv Huawei Proprietary and Confidential
Issue 01 (2010-08-16)
GUI Conventions
Convention Description
Boldface Buttons, menus, parameters, tabs, window,
and dialog titles are in boldface. For example,
click OK.
> Multi-level menus are in boldface and
separated by the ">" signs. For example,
choose File > Create > Folder.

Change History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Updates in Issue 01 (2010-08-16) Based on Product Version V100R002C01
The first release.
Updates in Issue 01 (2010-04-15) Based on Product Version V100R002C00
The first release.
iManager U2000
Operation Guide for PTN End-to-End Management About This Document
v
Contents
About This Document...................................................................................................................iii
1 Process of Configuring PTN Services....................................................................................1-1
2 Automatically Searching PTN Services.................................................................................2-1
3 Managing Tunnel.......................................................................................................................3-1
3.1 Introduction to the Tunnel...............................................................................................................................3-2
3.1.1 Introduction to the Tunnel......................................................................................................................3-2
3.1.2 Standards and Protocols Compliance of the Tunnel..............................................................................3-3
3.1.3 Principles................................................................................................................................................3-5
3.2 Tunnel Configuration Flow...........................................................................................................................3-11
3.3 Configuring a Tunnel....................................................................................................................................3-12
3.3.1 Creating a Tunnel.................................................................................................................................3-13
3.3.2 Creating Tunnels in Batches................................................................................................................3-16
3.3.3 Creating a Protection Group.................................................................................................................3-17
3.3.4 Automatic Search for Protection Groups.............................................................................................3-19
3.3.5 Deploying a Tunnel..............................................................................................................................3-20
3.3.6 Reoptimizing an RSVP TE Tunnel......................................................................................................3-21
3.3.7 Viewing a Discrete Tunnel...................................................................................................................3-21
3.3.8 Checking the Correctness of the Tunnel Configuration.......................................................................3-22
3.3.9 Perform Tunnel Protection Group Switching.......................................................................................3-22
3.4 Monitoring a Tunnel......................................................................................................................................3-23
3.4.1 Configuring OAM for a Tunnel...........................................................................................................3-24
3.4.2 Viewing the VPN Service Carried on a Tunnel...................................................................................3-25
3.4.3 Viewing the Topology of a Tunnel......................................................................................................3-26
3.4.4 Viewing the Performance of a Tunnel.................................................................................................3-26
3.4.5 Viewing the Alarms of a Tunnel..........................................................................................................3-27
3.4.6 Monitoring the Running Status of a Tunnel.........................................................................................3-27
3.4.7 Viewing the LSP Topology of a Tunnel..............................................................................................3-28
3.4.8 Diagnosing a Tunnel............................................................................................................................3-28
3.5 Tunnel Configuration Example.....................................................................................................................3-29
3.5.1 Configuration Example (Static CR Tunnel).........................................................................................3-30
3.5.2 Configuration Example (RSVP TE Tunnel)........................................................................................3-40
3.5.3 Configuration Example (IP and LDP Tunnels)....................................................................................3-52
iManager U2000
Operation Guide for PTN End-to-End Management Contents
vii
4 Configuring a Service Template.............................................................................................4-1
4.1 Creating a Service Template...........................................................................................................................4-2
4.2 Creating a Service by Using a Template.........................................................................................................4-2
5 Viewing a Service Resource.....................................................................................................5-1
5.1 Querying Public Resources.............................................................................................................................5-2
5.2 Querying SAI Resources.................................................................................................................................5-2
6 Managing PWE3 Services.........................................................................................................6-1
6.1 Overview of PWE3.........................................................................................................................................6-2
6.1.1 Introduction............................................................................................................................................6-2
6.1.2 Reference Standards and Protocols........................................................................................................6-3
6.1.3 Principle.................................................................................................................................................6-4
6.1.4 Overview of IP Line.............................................................................................................................6-20
6.1.5 Principle of IP Line..............................................................................................................................6-21
6.1.6 The Application of PWE3 Service.......................................................................................................6-24
6.2 PWE3 Configuration Process........................................................................................................................6-25
6.3 Configuration Flow for the PWE3 Service Protection..................................................................................6-32
6.4 PWE3 Operation Tasks.................................................................................................................................6-38
6.4.1 Creating a CES Service........................................................................................................................6-39
6.4.2 Creating an ETH Service......................................................................................................................6-43
6.4.3 Creating an ATM Service....................................................................................................................6-47
6.4.4 Creating an IP Line Service.................................................................................................................6-52
6.4.5 Creating a PWE3 Service Through Duplication..................................................................................6-54
6.4.6 Deploying a PWE3 Service..................................................................................................................6-56
6.4.7 Adjusting a Discrete PWE3 Service.....................................................................................................6-57
6.4.8 Configure PWE3 Protection Service....................................................................................................6-58
6.4.9 Checking the Correctness of the Service Configuration......................................................................6-60
6.4.10 Performing a PW APS Protection Switching.....................................................................................6-60
6.4.11 Managing ATM Connections.............................................................................................................6-61
6.5 PWE3 Service Monitoring............................................................................................................................6-62
6.5.1 Configuring Ethernet OAM.................................................................................................................6-63
6.5.2 Configuring PW OAM.........................................................................................................................6-64
6.5.3 Viewing the PWE3 Service Topology.................................................................................................6-64
6.5.4 Monitoring Performance of a PWE3 Service.......................................................................................6-65
6.5.5 Monitoring Alarms of a PWE3 Service...............................................................................................6-66
6.5.6 Viewing the Alarms of a PWE3 Service..............................................................................................6-67
6.5.7 Diagnosing a PWE3 Service................................................................................................................6-67
6.6 Managing PWE3 Service Authority..............................................................................................................6-69
6.6.1 Configuring the Rights of a User on PWE3 Services..........................................................................6-69
6.6.2 Viewing the Rights of a User on PWE3 Services................................................................................6-70
6.7 Examples for Configuring PWE3 Services...................................................................................................6-70
6.7.1 Example for Configuring a CES Emulation Service............................................................................6-70
6.7.2 Example for Configuring an ATM Service..........................................................................................6-93
Contents
iManager U2000
viii Huawei Proprietary and Confidential
Issue 01 (2010-08-16)
6.7.3 Example for Configuring an Ethernet Private Line Service...............................................................6-121
6.7.4 Example of Configuring an End-to-End IP Line Service...................................................................6-139
7 Managing VPLS Services..........................................................................................................7-1
7.1 VPLS Overview.............................................................................................................................................. 7-2
7.1.1 Introduction to VPLS.............................................................................................................................7-2
7.1.2 Reference Standards and Protocols........................................................................................................7-2
7.1.3 VPLS Principle.......................................................................................................................................7-3
7.1.4 VPLS Application..................................................................................................................................7-6
7.2 Configuration Flow for a VPLS Service.........................................................................................................7-7
7.3 VPLS Operation Tasks....................................................................................................................................7-9
7.3.1 Creating a VPLS Service......................................................................................................................7-10
7.3.2 Deploying a VPLS Service..................................................................................................................7-12
7.3.3 Adjusting the VSI Resource.................................................................................................................7-12
7.4 Monitoring a VPLS Service..........................................................................................................................7-14
7.4.1 Configuring Ethernet OAM.................................................................................................................7-15
7.4.2 Viewing the Topology of a VPLS Service...........................................................................................7-16
7.4.3 Monitoring the Performance of a VPLS Service.................................................................................7-17
7.4.4 Monitoring the Alarms of a VPLS Service..........................................................................................7-18
7.4.5 Viewing the Alarms of a VPLS Service...............................................................................................7-18
7.4.6 Diagnosing a VPLS Service.................................................................................................................7-19
7.5 Managing VPLS Service Authority..............................................................................................................7-20
7.5.1 Configuring the Rights of a User on VPLS Services...........................................................................7-20
7.5.2 Viewing the Rights of a User on VPLS Services.................................................................................7-21
7.6 Configuration Case of the VPLS Service......................................................................................................7-21
7.6.1 Configuration Networking Diagram....................................................................................................7-22
7.6.2 Service Planning...................................................................................................................................7-22
7.6.3 Configuration Process..........................................................................................................................7-23
8 Managing an L3VPN Service...................................................................................................8-1
8.1 Introduction to L3VPN....................................................................................................................................8-2
8.2 Basic Concepts................................................................................................................................................8-3
8.2.1 Basic Concepts of L3VPN..................................................................................................................... 8-4
8.2.2 MP-BGP...............................................................................................................................................8-10
8.2.3 Label Allocation of MP-BGP...............................................................................................................8-15
8.2.4 VPN Route Selection on PEs...............................................................................................................8-15
8.2.5 Advertisement of VPNv4 Routes.........................................................................................................8-16
8.2.6 Route Advertisement of a Basic L3VPN.............................................................................................8-17
8.2.7 Packet Forwarding in a Basic L3VPN.................................................................................................8-19
8.2.8 IP DSCP Overview...............................................................................................................................8-20
8.2.9 Introduction to DHCP Relay................................................................................................................8-21
8.2.10 Principle of DHCP Relay...................................................................................................................8-24
8.3 Application of the L3VPN............................................................................................................................8-28
iManager U2000
ix
8.4 Configuration Flow of L3VPN Services.......................................................................................................8-32
8.5 L3VPN Operation Tasks...............................................................................................................................8-34
8.5.1 Creating the L3VPN Service................................................................................................................8-35
8.5.2 Deploying the L3VPN Service.............................................................................................................8-37
8.5.3 Adjusting the Discrete L3VPN Service...............................................................................................8-38
8.5.5 Configuring DHCP Relay....................................................................................................................8-40
8.6 L3VPN Service Monitoring..........................................................................................................................8-41
8.6.1 Viewing the L3VPN Service Topology...............................................................................................8-42
8.6.2 Monitoring Performance of the L3VPN Service..................................................................................8-43
8.6.3 Monitoring Alarms of the L3VPN Service..........................................................................................8-43
8.6.4 Viewing the Alarms of an L3VPN Service..........................................................................................8-44
8.6.5 Diagnosing an L3VPN Service............................................................................................................8-45
8.7 Managing L3VPN Service Authority............................................................................................................8-45
8.7.1 Configuring the Rights of a User on L3VPN Services........................................................................8-46
8.7.2 Viewing the Rights of a User on L3VPN Services..............................................................................8-46
8.8 Example for Configuring the L3VPN Service..............................................................................................8-47
8.8.1 Example for Configuring an Intranet VPN Service.............................................................................8-47
8.8.2 Example for Configuring the Hub&Spoke VPN Service.....................................................................8-77
9 Configuring Dual-Homing Protection...................................................................................9-1
9.1 Configuration Flow of Dual-Homing Protection............................................................................................9-2
9.2 Operation Tasks for Configuring the Dual-Homing Protection......................................................................9-4
9.2.1 Configuring the MC-LAG......................................................................................................................9-5
9.2.2 Operation Tasks for Configuring MC-PW APS..................................................................................9-15
9.3 Example of Dual-Homing Protection with 1:1 MC-PW APS and MC-LAG...............................................9-17
9.3.1 Example Description............................................................................................................................9-18
9.3.2 Configuration Process..........................................................................................................................9-22
10 Configuring VRRP.................................................................................................................10-1
10.1 Overview of VRRP.....................................................................................................................................10-2
10.2 Configuration Flow for VRRP....................................................................................................................10-3
10.3 Operation Tasks of Configuring VRRP......................................................................................................10-3
10.3.1 Configuring and Deploying an L3VPN Service................................................................................10-3
10.3.2 Configuring VRRP VR Information..................................................................................................10-5
10.3.3 Configuring Information About Objects Under Tracking of a VRRP VR .......................................10-6
10.4 Testing VRRP.............................................................................................................................................10-7
10.5 Configuration Case of VRRP......................................................................................................................10-8
10.5.1 Example Description..........................................................................................................................10-8
10.5.2 Configuration Process......................................................................................................................10-10
11 Composite Service Management.........................................................................................11-1
11.1 Composite Service Overview......................................................................................................................11-2
11.1.1 Composite Service Functions.............................................................................................................11-2
Contents
iManager U2000
x Huawei Proprietary and Confidential
Issue 01 (2010-08-16)
11.1.2 Basic Concepts...................................................................................................................................11-3
11.1.3 Application of Composite Services....................................................................................................11-3
11.2 Process of Configuring a Composite Service..............................................................................................11-6
11.3 Operation Tasks of Composite Services.....................................................................................................11-7
11.3.1 Automatically Discovering Composite Services................................................................................11-8
11.3.2 Creating a Composite Service............................................................................................................11-8
11.3.3 Deploying a Composite Service.........................................................................................................11-9
11.4 Monitoring a Composite Service...............................................................................................................11-10
11.4.1 Viewing the Status of a Composite Service.....................................................................................11-10
11.4.2 Viewing the Topology of a Composite Service...............................................................................11-11
11.5 Example for Configuring Composite Services..........................................................................................11-12
11.5.1 Example for Configuring the PWE3+VPLS Composite Service.....................................................11-12
11.5.2 Example for Configuring the PWE3+PWE3 Composite Service....................................................11-20
12 Modifying Configurations...................................................................................................12-1
12.1 Modifying the Basic Information About Services in Batches.....................................................................12-2
12.2 Modifying Tunnel Attributes......................................................................................................................12-2
12.2.1 Modifying a Tunnel............................................................................................................................12-3
12.2.2 Deleting a Tunnel...............................................................................................................................12-3
12.2.3 Deleting a tunnel from the network Side...........................................................................................12-4
12.2.4 Undeploying a tunnel.........................................................................................................................12-4
12.3 Modifying PWE3 Attributes.......................................................................................................................12-5
12.3.1 Modifying a PWE3 Service................................................................................................................12-5
12.3.2 Modifying the Tunnel Carrying PWE3 Services...............................................................................12-6
12.3.3 Deleting a PWE3 Service...................................................................................................................12-6
12.3.4 Deleting a PWE3 Service on the Network Side.................................................................................12-7
12.3.5 Undeploying a PWE3 Service............................................................................................................12-7
12.4 Modifying VPLS Attributes........................................................................................................................12-8
12.4.1 Modifying a VPLS Service................................................................................................................12-8
12.4.2 Modifying the Tunnel Carrying VPLS Services................................................................................12-9
12.4.3 Deleting a VPLS Service....................................................................................................................12-9
12.4.4 Deleting a VPLS Service from the U2000 Side...............................................................................12-10
12.4.5 Undeploying a VPLS Service..........................................................................................................12-10
12.5 Modifying the Attributes of a L3VPN Service.........................................................................................12-11
12.5.1 Modifying a L3VPN Service............................................................................................................12-11
12.5.2 Deleting an L3VPN Service.............................................................................................................12-12
12.5.3 Deleting a L3VPN Service from the Network.................................................................................12-12
12.5.4 Undeploying a L3VPN Service........................................................................................................12-13
Index.................................................................................................................................................i-1
iManager U2000
xi
Figures
Figure 1-1 Process of configuring PTN services..................................................................................................1-1
Figure 3-1 MPLS tunnel on the MPLS network..................................................................................................3-2
Figure 3-2 ATM PWE3 over IP tunnel................................................................................................................3-3
Figure 3-3 Process of creating a tunnel................................................................................................................3-7
Figure 3-4 Working process of a tunnel...............................................................................................................3-7
Figure 3-5 Principles of the tunnel protection......................................................................................................3-9
Figure 3-6 Transparent transmission of point-to-point data packets..................................................................3-10
Figure 3-7 Tunnel configuration flow................................................................................................................3-11
Figure 3-8 The figure of tunnel protection group...............................................................................................3-18
Figure 3-9 Networking diagram of an MPLS tunnel.........................................................................................3-30
Figure 3-10 NE planning....................................................................................................................................3-31
Figure 3-11 Networking diagram of an RSVP TE tunnel..................................................................................3-40
Figure 6-1 Basic transmission components of the PWE3....................................................................................6-4
Figure 6-2 PWE3 single-hop topology.................................................................................................................6-5
Figure 6-3 PWE3 multi-hop topology..................................................................................................................6-6
Figure 6-4 Network of the static and dynamic hybrid multi-hop PW..................................................................6-8
Figure 6-5 PW redundancy protection.................................................................................................................6-9
Figure 6-6 CE symmetrical access dual-homing protection.................................................................................6-9
Figure 6-7 Backup protection.............................................................................................................................6-10
Figure 6-8 PW APS protection...........................................................................................................................6-10
Figure 6-9 Ethernet raw mode (with user VLAN tags)......................................................................................6-15
Figure 6-10 Ethernet tagged mode (with user VLAN tags)...............................................................................6-16
Figure 6-11 VLAN raw mode (with service VLAN tags)..................................................................................6-18
Figure 6-12 VLAN tagged mode (with service VLAN tags).............................................................................6-19
Figure 6-13 Deployment of IP line services.......................................................................................................6-20
Figure 6-14 Encapsulation process of IP line services.......................................................................................6-21
Figure 6-15 Dual-homing protection for IP line services...................................................................................6-22
Figure 6-16 Dual-homing protection switching for IP line services in case of an equipment fault...................6-22
Figure 6-17 Dual-homing protection switching for IP line services in case of a link fault...............................6-23
Figure 6-18 Application of the PWE3................................................................................................................6-24
Figure 6-19 CES service configuration process.................................................................................................6-25
iManager U2000
Operation Guide for PTN End-to-End Management Figures
xiii
Figure 6-20 ATM service configuration process................................................................................................6-27
Figure 6-21 E-Line service configuration process............................................................................................. 6-29
Figure 6-22 Flow of configuring an IP line service........................................................................................... 6-31
Figure 6-23 Single source and dual sink............................................................................................................6-32
Figure 6-24 Dual source and single sink............................................................................................................6-33
Figure 6-25 Process of configuring PW redundancy dual-homing protection...................................................6-33
Figure 6-26 Dual-Homing protection for CEs symmetric access...................................................................... 6-34
Figure 6-27 Process of configuring the dual-Homing protection for CEs symmetric access............................6-35
Figure 6-28 PW Backup Protection....................................................................................................................6-35
Figure 6-29 Process of configuring the PW backup protection......................................................................... 6-36
Figure 6-30 Single source and dual sink............................................................................................................6-36
Figure 6-31 Dual source and single sink............................................................................................................6-37
Figure 6-32 Process of configuring the PW APS protection..............................................................................6-37
Figure 6-33 Network of the CES service........................................................................................................... 6-71
Figure 6-35 Network of the ATM services........................................................................................................6-94
Figure 6-36 NE planning diagram......................................................................................................................6-95
Figure 6-37 Network of the Ethernet private line service................................................................................6-121
Figure 6-38 Network where an IP line service is deployed..............................................................................6-140
Figure 7-1 VPLS forwarding model.....................................................................................................................7-3
Figure 7-2 Basic VPLS transport components.....................................................................................................7-4
Figure 7-3 Typical VPLS networking..................................................................................................................7-7
Figure 7-4 Flowchart for configuring a VPLS service.........................................................................................7-8
Figure 7-5 Networking diagram for the VPLS service...................................................................................... 7-22
Figure 8-1 Model of a L3VPN.............................................................................................................................8-2
Figure 8-2 Schematic diagram of sites.................................................................................................................8-4
Figure 8-3 One site belonging to multiple VPNs.................................................................................................8-5
Figure 8-4 Schematic diagram of VPN instances.................................................................................................8-6
Figure 8-5 VPN-IPv4 address structure...............................................................................................................8-7
Figure 8-6 Format of a VPN target......................................................................................................................8-9
Figure 8-7 BGP running mode...........................................................................................................................8-11
Figure 8-8 Format of MP_REACH_NLRI.........................................................................................................8-11
Figure 8-9 Format of the NLRI field with a Label subfield...............................................................................8-12
Figure 8-10 Format of MP_UNREACH_NLRI.................................................................................................8-12
Figure 8-11 Format of BGP capability parameters............................................................................................8-13
Figure 8-12 Format of the Capability Value field in MP-BGP..........................................................................8-13
Figure 8-13 Advertisement of a route from CE2 to CE1...................................................................................8-19
Figure 8-14 Forwarding of a VPN packet from CE1 to CE2.............................................................................8-20
Figure 8-15 Structure of the IPv4 packet head...................................................................................................8-21
Figure 8-16 Application of DHCP relay............................................................................................................ 8-22
Figure 8-17 Application scenario of DHCP relay on a Layer 2 network...........................................................8-22
Figures
iManager U2000
xiv Huawei Proprietary and Confidential
Issue 01 (2010-08-16)
Figure 8-20 DHCP packet format......................................................................................................................8-24
Figure 8-21 L2VPN DHCP relay mode.............................................................................................................8-27
Figure 8-22 IPoE service scenario......................................................................................................................8-27
Figure 8-23 FE service scenario.........................................................................................................................8-27
Figure 8-24 Networking diagram of an intranet VPN........................................................................................8-29
Figure 8-25 Networking diagram of an extranet................................................................................................8-30
Figure 8-26 Route advertisement from Site2 to Site1 in Hub&Spoke networking model.................................8-31
Figure 8-27 Path of transmitting customer traffic from Site1 to Site2...............................................................8-32
Figure 8-28 L3VPN service configuration flow.................................................................................................8-33
Figure 8-29 Network of the intranet VPN service..............................................................................................8-48
Figure 8-31 Networking of the Hub&Spoke VPN service.................................................................................8-78
Figure 9-1 Configuration flow for dual-homing protection.................................................................................9-2
Figure 9-2 Link Aggregation Group....................................................................................................................9-5
Figure 9-3 LAG networking.................................................................................................................................9-6
Figure 9-4 MC-LAG for dual-homing protection................................................................................................9-7
Figure 9-5 Configuring an MC-LAG in a Dual-Homing Protection Scenario...................................................9-11
Figure 9-6 Networking diagram of MC-PW APS for dual-homing protection..................................................9-16
Figure 9-7 Networking diagram for the dual-homing protection with 1:1 MC-PW APS and MC-LAG..........9-18
Figure 10-1 VRRP networking...........................................................................................................................10-2
Figure 10-2 Network with VRRP for an RNC...................................................................................................10-9
Figure 11-1 Networking diagram of the static VLL+VPLS composite service.................................................11-4
Figure 11-2 Networking diagram of the dual-homed static VLL+VPLS composite service.............................11-5
Figure 11-3 Networking diagram of the PWE3+PWE3 composite service.......................................................11-6
Figure 11-4 Flowchart of configuring a composite service................................................................................11-6
Figure 11-5 Networking diagram of the PWE3+VPLS composite service......................................................11-12
Figure 11-6 Networking diagram of the PWE3+PWE3 composite service.....................................................11-20
iManager U2000
Operation Guide for PTN End-to-End Management Figures
xv
Tables
Table 3-1 Tunnel configuration tasks.................................................................................................................3-11
Table 3-2 Planning of Tunnel parameters..........................................................................................................3-31
Table 3-3 Planning of protection group parameters...........................................................................................3-33
Table 3-4 Configuration parameters of NEs.......................................................................................................3-41
Table 3-5 Configuration parameters of Tunnels.................................................................................................3-42
Table 3-6 Configuration parameters of NEs.......................................................................................................3-53
Table 3-7 Static route.........................................................................................................................................3-53
Table 3-8 Planning of the IGP-ISIS...................................................................................................................3-54
Table 3-9 Planning of the MPLS-LDP...............................................................................................................3-54
Table 3-10 Planning of the working IP tunnel...................................................................................................3-54
Table 3-11 Planning of the protection LDP tunnel.............................................................................................3-55
Table 6-1 Features of the ATM cell transparent transmission services..............................................................6-13
Table 6-2 Applicable scenarios of various connection types.............................................................................6-13
Table 6-3 Comparison between 1-to-1 and N-to-1 modes.................................................................................6-14
Table 6-4 Tasks for configuring a CES service..................................................................................................6-25
Table 6-5 Tasks for configuring an ATM service..............................................................................................6-27
Table 6-6 Tasks for configuring an E-Line service............................................................................................6-29
Table 6-7 Operation tasks for configuring an IP line service.............................................................................6-31
Table 6-8 NE parameters....................................................................................................................................6-72
Table 6-9 Tunnel parameters..............................................................................................................................6-73
Table 6-10 CES service parameters: NE1-NE3 (E1 timeslots partially used)...................................................6-75
Table 6-11 CES service parameters: NE1-NE3 (E1 timeslots fully used).........................................................6-76
Table 6-12 Parameters of general attributes.......................................................................................................6-82
Table 6-13 Parameters of the source node..........................................................................................................6-83
Table 6-14 Parameters of the sink node.............................................................................................................6-85
Table 6-15 PW parameters.................................................................................................................................6-86
Table 6-16 Parameters of advanced attributes....................................................................................................6-88
Table 6-17 Parameters of general attributes.......................................................................................................6-89
Table 6-18 Parameters of the source node..........................................................................................................6-90
Table 6-19 Parameters of the sink node.............................................................................................................6-90
Table 6-20 PW parameters.................................................................................................................................6-91
Table 6-21 Parameters of advanced attributes....................................................................................................6-92
Table 6-22 Configuration parameters of NEs.....................................................................................................6-95
iManager U2000
Operation Guide for PTN End-to-End Management Tables
xvii
Table 6-23 Tunnel parameters............................................................................................................................6-96
Table 6-24 Configuration parameters of the ATM service on NE1...................................................................6-97
Table 6-25 Configuration parameters of NE2....................................................................................................6-97
Table 6-26 Parameters of general attributes.....................................................................................................6-106
Table 6-27 Parameters of the source node........................................................................................................6-106
Table 6-28 Parameters of the sink node...........................................................................................................6-106
Table 6-29 PW parameters...............................................................................................................................6-107
Table 6-30 Parameter for configuring a connection.........................................................................................6-108
Table 6-31 Parameters of advanced attributes..................................................................................................6-110
Table 6-32 PW QoS parameters.......................................................................................................................6-110
Table 6-47 Configuration parameters of NEs...................................................................................................6-122
Table 6-48 Planning of the tunnel carrying the PW.........................................................................................6-122
Table 6-49 Planning of the UNI-NNI E-Line service carried by the PW........................................................6-123
Table 6-50 Planning of the PW........................................................................................................................6-123
Table 6-51 Tunnel parameters..........................................................................................................................6-127
Table 6-53 Parameters of the source and sink node.........................................................................................6-131
Table 6-55 QoS parameters..............................................................................................................................6-133
Table 6-59 Parameters of the source and sink node.........................................................................................6-135
Table 6-61 Service parameters.........................................................................................................................6-137
Table 6-62 QoS parameters..............................................................................................................................6-138
Tables
iManager U2000
xviii Huawei Proprietary and Confidential
Issue 01 (2010-08-16)
Table 6-65 Planning of parameters for NEs.....................................................................................................6-140
Table 6-66 Planning of bearer tunnels for the PWs..........................................................................................6-141
Table 6-67 VRF configuration planning..........................................................................................................6-141
Table 6-68 PW configuration planning............................................................................................................6-142
Table 6-69 Parameter settings for a static tunnel.............................................................................................6-145
Table 6-70 Service parameter settings..............................................................................................................6-148
Table 6-71 General attributes of VRF..............................................................................................................6-148
Table 6-72 Service access interface..................................................................................................................6-149
Table 6-73 Route configuration........................................................................................................................6-150
Table 6-74 QoS parameter settings for the service access port........................................................................6-152
Table 6-75 PW QoS parameter settings...........................................................................................................6-152
Table 7-1 VPLS packets and encapsulation types................................................................................................7-5
Table 7-2 Tasks for Configure a VPLS service....................................................................................................7-8
Table 7-3 General planning of VPLS services...................................................................................................7-22
Table 7-4 Planning of VPLS services.................................................................................................................7-23
Table 7-5 Planning of UNI ports........................................................................................................................7-23
Table 7-6 General planning of VPLS services...................................................................................................7-24
Table 7-7 Planning of VPLS services.................................................................................................................7-25
Table 7-8 Planning of SAI..................................................................................................................................7-27
Table 7-9 Parameter configuration of a tunnel...................................................................................................7-28
Table 8-1 Description of each field in a DHCP packet......................................................................................8-24
Table 8-2 Tasks for configuring the L3VPN service......................................................................................... 8-33
Table 8-3 VPN1 parameter planning..................................................................................................................8-49
Table 8-4 VPN2 parameter planning..................................................................................................................8-50
Table 8-5 Basic parameters................................................................................................................................ 8-58
Table 8-6 Affinity object parameters..................................................................................................................8-59
Table 8-7 Parameters of explicit hops information object..................................................................................8-59
Table 8-8 FRR attribute parameters................................................................................................................... 8-59
Table 8-9 QoS parameters..................................................................................................................................8-60
Table 8-10 Setup attribute parameters................................................................................................................8-60
Table 8-11 Basic parameters.............................................................................................................................. 8-61
Table 8-12 NE list parameters............................................................................................................................8-62
Table 8-13 Basic parameters of advanced attribute............................................................................................8-62
Table 8-14 Affinity object parameters................................................................................................................8-62
Table 8-15 Parameters of explicit hops information object................................................................................8-63
Table 8-16 Parameters of fast rerouting attribute...............................................................................................8-63
Table 8-17 QoS parameters................................................................................................................................8-64
Table 8-19 Basic parameters.............................................................................................................................. 8-64
Table 8-21 Basic parameters of advanced attribute............................................................................................8-65
iManager U2000
xix
Table 8-23 Parameters of explicit hops information object................................................................................8-66
Table 8-24 Parameters of fast rerouting attribute...............................................................................................8-66
Table 8-25 QoS parameters................................................................................................................................8-67
Table 8-27 Service information parameters.......................................................................................................8-68
Table 8-29 PE1 parameters.................................................................................................................................8-69
Table 8-32 Service information parameters.......................................................................................................8-73
Table 8-37 VPN parameter planning..................................................................................................................8-79
Table 8-38 General information.........................................................................................................................8-87
Table 8-40 Parameters of the explicit hop information object...........................................................................8-88
Table 8-41 FRR attributes..................................................................................................................................8-88
Table 8-42 QoS configuration parameters..........................................................................................................8-89
Table 8-43 Setup attributes.................................................................................................................................8-89
Table 8-44 General information.........................................................................................................................8-90
Table 8-45 NE list...............................................................................................................................................8-90
Table 8-46 Basic information about the advanced attributes.............................................................................8-90
Table 8-48 Parameters of the explicit hop information object...........................................................................8-91
Table 8-49 FRR attributes..................................................................................................................................8-91
Table 8-50 QoS configuration parameters..........................................................................................................8-92
Table 8-51 Setup attributes.................................................................................................................................8-92
Table 8-52 Service information..........................................................................................................................8-93
Table 8-53 NE list...............................................................................................................................................8-94
Table 8-54 Hub-PE parameters..........................................................................................................................8-94
Table 8-55 Spoke-PE1 parameters.....................................................................................................................8-95
Table 8-56 Spoke-PE2 parameters.....................................................................................................................8-96
Table 9-1 Description of tasks in the configuration flow for dual-homing protection.........................................9-3
Table 9-2 Application of MC-LAG for dual-homing protection.........................................................................9-9
Table 9-3 Support for MC-LAG application scenario I (SC LAGs on dual-homing nodes in non-load-sharing mode)
.............................................................................................................................................................................9-10
Table 9-4 Support for MC-LAG application scenario II (SC LAGs on dual-homing nodes in load-sharing mode)
.............................................................................................................................................................................9-10
Table 9-5 Parameter planning for the PWs of NNI-side MC-PW APS (dual-homing protection with 1:1 MC-PW
APS and MC-LAG in the example)....................................................................................................................9-19
Tables
iManager U2000
xx Huawei Proprietary and Confidential
Issue 01 (2010-08-16)
Table 9-6 Parameter planning for NNI-side MC-PW APS (dual-homing protection with 1:1 MC-PW APS and
MC-LAG in the example)...................................................................................................................................9-20
Table 9-7 Parameter planning for MC synchronization communication (dual-homing protection with 1:1 MC-PW
APS and MC-LAG in the example)....................................................................................................................9-21
Table 9-8 Parameters for LAG1 on PE1 and LAG2 on PE2 (dual-homing protection with 1:1 MC-PW APS and
MC-LAG in the example)...................................................................................................................................9-21
Table 9-9 Parameters for the MC-LAG protection groups on PE1 and PE2 (dual-homing protection with 1:1 MC-
PW APS and MC-LAG in the example).............................................................................................................9-21
Table 10-1 Planning of VRRP VR information................................................................................................. 10-9
Table 10-2 Planning of Advanced VRRP VR Information................................................................................10-9
Table 10-3 Planning of Information About Objects Under Tracking of a VRRP VR ....................................10-10
Table 10-4 Planning of Advanced VRRP VR Information..............................................................................10-12
Table 10-5 Parameters for Tracking More BFD Sessions or Interfaces...........................................................10-14
Table 11-1 Configuration tasks of a composite service..................................................................................... 11-7
Table 11-2 NE parameters................................................................................................................................11-13
Table 11-3 Planning of parameters for configuring the PWE3 service............................................................11-13
Table 11-4 Planning of parameters for configuring the VPLS service............................................................11-14
Table 11-5 Planning of parameters for configuring the composite service......................................................11-15
Table 11-7 Planning of parameters for configuring the VPLS service............................................................11-17
Table 11-8 Planning of parameters for configuring the LAG..........................................................................11-20
Table 11-10 Planning of parameters for configuring the composite service....................................................11-21
Table 11-11 Planning of parameters for configuring the LAG........................................................................11-22
Table 11-12 Planning of parameters for configuring the PWE3 service..........................................................11-22
iManager U2000
xxi
1 Process of Configuring PTN Services
This topic describes the process of configuring PTN services in terms of network deployment,
service discovery, service deployment, and service assurance.
Figure 1-1 shows the process of configuring PTN services.
Figure 1-1 Process of configuring PTN services
Network deployment Service deployment
Add equipment to
the NMS
Configure basic
routes
Configure control
plane
Configure tunnels
Service assurance
Discover single
services
Create a service
through a template
Create a service with
defined parameters
Monitor alarms in
centralized mode
Service discovery
Discover composite
services
Discover tunnels
Monitor performance
services
S
e
r
v
i
c
e

m
o
n
i
t
o
r
i
n
g
View service
resources
P
r
e
d
e
p
l
o
y
m
e
n
t
Deploy the service
Monitor service
alarms
Locate faults with the
test and check
F
a
u
l
t

l
o
c
a
t
i
o
n
View the service
topology
Optional
Mandatory
Upload/Synchronize
data
Configure interface

l Network deployment: is the prerequisite for the service deployment and includes adding
equipment to the NMS, upload/synchronize data, and configuring basic routes, configuring
control plane, and tunnels.
l Service discovery: discovers the existing services on the NMS for unified management and
includes the discovery of tunnels, single services, and composite services.
l Service deployment
iManager U2000
Operation Guide for PTN End-to-End Management 1 Process of Configuring PTN Services
1-1
Viewing service resources: Before deployment services, you can view the service
resources to check the available service resources.
Predeploying services: Predeploying services refers to creating services on the NMS.
After services are predeployed, the configuration data of the services are not deployed
to equipment. To create services, you can either manually enter the parameters of the
services or use a template to create the services in batches.
Service deployment: deploys the configuration data of services to equipment.
l Service assurance: includes service monitoring and fault location. Service monitoring
includes service alarm monitoring and service performance monitoring. By monitoring
service alarms, you can view affected services, and then locate the failure point through
the test diagnosis tool.
Service monitoring: monitors the alarms and performance of services and views the
service topology. The service topology provides rich service operation accesses.
According to the topology color, you can discover alarms according to the topology
color and view the related alarms in the topology view.
Fault location: By monitoring service alarms, you can view affected services, and then
locate the failure point through the test and check.
1 Process of Configuring PTN Services
iManager U2000
1-2 Huawei Proprietary and Confidential
Issue 01 (2010-08-16)
2 Automatically Searching PTN Services
This topic describes how to automatically search IP services. With this function, you can recover
the services existing on the current network to the end to end management module of the NMS
for monitoring. In this manner, you can ensure the normal running of these services.
Prerequisite
Data synchronization must be complete on the related equipment.
Procedure
Step 1 Choose Service > Search for IP Service from the main menu.
Step 2 On the Discovery Policy tab page, set the discovery policy.
1. Specify the equipment range for automatically searching IP services.
l Click the All option button to discover all the NEs on the entire network.
l Click the Select NE option button, and then click Add. In the dialog box that is
displayed, select one or more NEs, and then click OK to discover the specified NEs.
2. In the Discover Service navigation tree, select the check box to the left of the related service
to specify the type of the services to be searched.
3. On the lower-right part, click each service tab to configure the customer policy and
discovery policy.
Customer association policies are classified into the following types:
l Set Customer: The searched services are automatically associated with the specified
customer.
l Do Not Set Customer: The automatically searched services are not associated with any
customer.
NOTE
Only support discovering L3VPN service by VRF ID or VRF connectivity for PTN equipment.
4. After the configuration, click Start.
Step 3 Click the Discovery Result tab. A progress bar is displayed indicating the progress of
automatically discovering services.
You can view the automatically searched services on the Add Service, Modify Service, and
Discrete Service tab pages, as shown in the following figure. After selecting a record and
clicking Jump Service, you can access the service management user interface for this service.
iManager U2000
Operation Guide for PTN End-to-End Management 2 Automatically Searching PTN Services
2-1
----End
2 Automatically Searching PTN Services
iManager U2000
Issue 01 (2010-08-16)
3 Managing Tunnel
About This Chapter
By using the tunnel technology, you can create private data transmission channels on a PSN
network to transparently transmit packets.
3.1 Introduction to the Tunnel
Different tunnel technologies are used in different scenarios and use different protocols to
transparently transmit data packets.
3.2 Tunnel Configuration Flow
This section describes the operation tasks for configuring the Tunnel, and relations among these
tasks. When configuring and managing the Tunnel, follow the configuration flow.
3.3 Configuring a Tunnel
This topic describes how to configure a tunnel, such as creating a tunnel, creating a protection
group, deploying a tunnel, viewing discrete tunnels, and deleting a tunnel.
3.4 Monitoring a Tunnel
This topic describes how to monitor a tunnel to facilitate tunnel services management.
3.5 Tunnel Configuration Example
This topic describes configuration examples of creating tunnels in the end-to-end mode. In
addition to the examples, the configuration flow diagrams are provided for you to learn the
service configuration processes. A configuration example describes a networking scenario and
the corresponding process of creating a tunnel on an actual network. A configuration example
includes information about the configuration networking diagram, service planning, and
configuration process.
iManager U2000
Operation Guide for PTN End-to-End Management 3 Managing Tunnel
3-1
3.1 Introduction to the Tunnel
Different tunnel technologies are used in different scenarios and use different protocols to
transparently transmit data packets.
3.1.1 Introduction to the Tunnel
OptiX equipment supports the MPLS tunnel, which is a tunneling technology using the MPLS-
protocol-based encapsulation, and the IP tunnel, which is a tunneling technology using the IP-
protocol-based encapsulation.
3.1.2 Standards and Protocols Compliance of the Tunnel
This topic describes the standards Compliance and the two protocols that the tunneling
technology uses. They are the MPLS-LDP protocol and the MPLS-RSVP protocol.
3.1.3 Principles
Multi-protocol label switching (MPLS) is a tunnel technology and enables a routing and
switching platform that integrates the switching and forwarding technologies of labels and
network-layer routing technologies. In the MPLS architecture, the control plane is
connectionless and uses the powerful and flexible routing function of the IP network to meet the
network requirements of new application; the data plane is connection-oriented and uses short
and fixed-length labels to encapsulate packets for implementation of fast forwarding.
3.1.1 Introduction to the Tunnel
OptiX equipment supports the MPLS tunnel, which is a tunneling technology using the MPLS-
protocol-based encapsulation, and the IP tunnel, which is a tunneling technology using the IP-
protocol-based encapsulation.
MPLS 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 3-1 shows how the MPLS tunnel is used as the service transmission channel.
Figure 3-1 MPLS tunnel on the MPLS network
IMA E1
FE
ATM STM-1
MPLS tunnel
Ingress node Transit node Egress node IMA E1
FE
ATM STM-1
PW

3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
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.
Based on signaling types, MPLS tunnels can be classified into three types, that is, the static CR
tunnel, RSVP TE tunnel, and LDP tunnel. These three types of tunnels are different and the
details are as follows:
l Static CR tunnel: You need to specify the nodes that a static CR tunnel traverses. In addition,
you can also specify the bandwidth and QoS of the tunnel.
l RSVP TE tunnel: You need to specify only the ingress and egress nodes for an RSVP TE
tunnel. The MPLS protocol automatically calculates a route for the tunnel. In addition, you
can specify constraint nodes to plan a specific route for the tunnel. You can configure FRR
protection and the QoS function for an RSVP TE tunnel. Therefore, an RSVP tunnel is
more flexible and safer than a static CR tunnel.
l LDP: You only need to specify the ingress and egress nodes for an LDP tunnel. Then, the
LDP protocol sets up a route for the tunnel. An LDP tunnel functions on the network that
supports the MPLS domain and thus is more flexible.
IP Tunnel
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. Figure 3-2 shows the protocol stack model
of the ATM service. In the case of the IP tunnel, the situation is similar to that where "IP header"
replaces the MPLS external label (MPLS tunnel label) to establish a tunnel in the IP network.
An ATM emulation service can be provided between NE A and NE B, even though the IP
network between NE A and NE B does not support the MPLS.
Figure 3-2 ATM PWE3 over IP tunnel
ATM
switch
IP network
ATM
E1/STM-1
ATM
PWE3
PW Label
Ethernet
ATM
E1/STM-1
ATM
switch
PTN Router PTN Router
NE A NE B
I P
ATM
PWE3
PW Label
Ethernet
I P

3.1.2 Standards and Protocols Compliance of the Tunnel
This topic describes the standards Compliance and the two protocols that the tunneling
technology uses. They are the MPLS-LDP protocol and the MPLS-RSVP protocol.
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
iManager U2000
3-3
the resource reservation information, used as a signaling protocol to create, delete or modify the
tunnel in the MPLS network.
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.
l 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.
NOTE
Currently, OptiX equipment supports only the SE resource reservation style.
MPLS-RSVP Message Type
The MPLS-RSVP uses the following message types:
l Path message: The transmit end sends this type of message in the transmission direction of
data packets. In addition, the path state is saved on all the nodes along the trail.
l 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.
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.
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
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.
l Remote MPLS-LDP session, in which the two NEs used to set up the session is not directly
connected.
MPLS-LDP Message Types
The MPLS-LDP protocol mainly uses the following four types of messages:
l Discovery message, which is used to notify and maintain the existence of the equipment
in the network.
l Session message, which is used to set up, maintain and end the session between MPLS-
LDP peer entities.
l Advertisement message, which is used to create, change and delete the label mapping.
l Notification message, which is used to provide the constructive message and error
notification.
Standards and Protocols Compliance
The tunneling technology is mainly compliant with the following:
l ITU-T G.8110 MPLS layer network architecture
l ITU-T G.8110.1 Application of MPLS in the transport network
l ITU-T G.8121 Characteristics of transport MPLS equipment functional blocks
l RFC 3031 MPLS architecture
l RFC 3032 MPLS label stack encoding
3.1.3 Principles
Multi-protocol label switching (MPLS) is a tunnel technology and enables a routing and
switching platform that integrates the switching and forwarding technologies of labels and
network-layer routing technologies. In the MPLS architecture, the control plane is
connectionless and uses the powerful and flexible routing function of the IP network to meet the
network requirements of new application; the data plane is connection-oriented and uses short
and fixed-length labels to encapsulate packets for implementation of fast forwarding.
Basic Concepts of the Tunnel
This topic describes basic concepts of the tunnel.
iManager U2000
3-5
FEC
Forwarding equivalence class (FEC) is a class of packets that are forwarded in the same way on
an MPLS network.
Label
Label is a short and length-fixed identifier. The label identifies the FEC that a packet belongs
to and functions only in the MPLS domain. One FEC may involve multiple labels but one label
can only indicate one FEC.
LDP
Label distribution protocol (LDP) is the control protocol for MPLS. Similar to the signaling
protocol of a traditional network, the LDP protocol is responsible for creation and maintenance
of LSPs and PWs, FEC classification, and label distribution. MPLS can use the following label
distribution protocols:
l Protocols exclusive for label distribution, such as LDP.
l Existing protocols extended to support label distribution, such as RSVP-TE.
LSP
On an MPLS network, the trail that an FEC traverses is a label switched path (LSP), that is, a
unidirectional trail from the ingress to egress. LSPs are classified into static LSPs and dynamic
LSPs. Static LSPs should be manually configured and dynamic LSPs are dynamically generated
by the LDP protocol.
LSR
Label switching router (LSR) is the basic element in an MPLS domain. All LSRs support the
MPLS protocol. Each node on an LSP is an LSR. An edge LSR (LER) is at the edge of an MPLS
domain and connects to other user networks. The core LSR is in the center of an MPLS domain.
Packets travel along an LSP and enter an MPLS domain. The incoming LER is the ingress, the
outgoing LER is the egress, and the intermediate nodes are the transit nodes.
An LSR consists of the control unit and forward unit.
l The control unit is responsible for label distribution, route selection, setup of label forward
tables, and setup and removal of LSPs.
l The forward unit forwards received packets according to the label forward tables.
NHLFE
Next hop label forwarding entry (NHLFE) describes the operations that an LSR performs on
labels, including push, swap, and pop.
Working Principles
This topic describes how to create a tunnel and the working principles of a tunnel.
Process of Creating a Tunnel
Figure 3-3 shows the process of creating a tunnel. Meanwhile, the working principles of a tunnel
are described.
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
Figure 3-3 Process of creating a tunnel
Ingress node
Label request
packet
Label mapping
packet
Transit node Egress node
Set up the
forward entry
Allocate the ingress label
and set up the forward entry
Allocate the ingress label
and set up the forward entry
Label request
packet
Label mapping
packet

A tunnel is created as follows:
1. The ingress node uses the encapsulation protocol to calculates a path to the egress node
and transmits a label request packet to the egress node in the direction of the path.
2. After receiving the label request packets, the transit node forwards them to the egress node.
3. After receiving the label request packet, the egress node allocates an ingress label for the
tunnel, sets up a forward entry, and transmits a label mapping packet to the ingress node.
4. After receiving the label mapping packet, the transit node allocates an ingress label for the
tunnel, sets up a forward entry, and forwards the label mapping packet to the ingress node.
5. After receiving the label mapping packet, the ingress node sets up a forward entry. The
tunnel is created successfully between the ingress node and egress node.
Working Process of a Tunnel
Figure 3-4 shows the working process of a tunnel.
Figure 3-4 Working process of a tunnel
IMA E1
FE
ATM STM-1
MPLS Tunnel
Ingress
node
Transit node
Egress
node
IMA E1
FE
ATM STM-1
PW
Packet
FEC
Push
Swap
Pop
Tunnel

At each LSR, the LDP protocol and traditional routing protocol work together to set up the route
table and label mapping table for the FEC as required. Each LSR node receives packets and
performs the NHLFE operations for the packets:
l Push: The ingress node receives packets and checks for the FEC that the packets belong
to. Then, the ingress node adds labels on the packets and transmits the encapsulated MPLS
packets to the next hop through the egress interface.
iManager U2000
3-7
l Swap: A transit node uses the forward unit to forward the packets only according to packet
labels and the label forward table. A transit node does not perform any Layer 3 operation
for the packets.
l Pop: The egress node stripes the labels from the packets and forwards the packets.
Tunnel Protection Group
Automatic protection switching (APS) of the MPLS tunnel is a network protection mechanism.
The protection MPLS tunnel protects the services transmitted in the working MPLS tunnel.
When the working MPLS tunnel is faulty, the services are switched to the protection MPLS
tunnel. In this way, the services transmitted in the working tunnel are protected. OptiX PTN
equipment supports the 1+1 and 1:1 APS protection of the MPLS tunnel.
Basic Information
APS (Automatic Protection Switching)
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.
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.
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
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.
Application of the Tunnel Protection
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.
By using the U2000, the user can configure 1+1 or 1:1 protection for MPLS tunnels that carry
important services.
Figure 3-5 shows the protection principle for unicast tunnels.
Figure 3-5 Principles of the tunnel protection
CE
CE
Ingress
node
Egress
node
Working
tunnel
Protection
tunnel
Configuration of source
protection group
Configuration of sink
protection group

iManager U2000
3-9
Application of the 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 CES services, ATM/IMA
services, Ethernet service and protocol packets. The MPLS Tunnel is mainly used for transparent
transmission of point-to-point data service packets.
Transparent Transmission of Point-to-Point Data Packets
Commonly, the tunnel is used to provide a point-to-point channel for services such as EPL
service. In this way, PEs on a PTN network can transparently transmit services. Figure 3-6
shows how point-to-multipoint data packets are transparently transmitted on a network.
Figure 3-6 Transparent transmission of point-to-point data packets
Third-party IP
network
Node B
RNC
PE
PE
Static CR tunnel
RSVP TE tunnel
LDP tunnel
IP tunnel
MPLS network
RSVP TE
network

An edge node on one network receives services from Node B, and transmits the services to the
RNC connected to another PE. In this case, a point-to-point MPLS tunnel can be used. The
application scenarios of different tunnels are as follows:
l When an IP tunnel transmits services, the service can be transparently transmitted on a
third-party IP network. Therefore, IP tunnels are used mainly when the services that the
PTN equipment transmits need to be transparently transmitted on a third-party IP network.
l When a static CR tunnel transmits services, the service can be transparently transmitted on
an entire MPLS network. Therefore, static CR tunnels are used mainly when high QoS is
not required and the routes are specified.
l When an RSVP TE tunnel transmits services, the service can be transparently transmitted
on an entire RSVP TE network. RSVP TE tunnels are used when high QoS and resource
usage are required on a network.
l When an LDP tunnel transmits services, the service can be transparently transmitted on an
entire MPLS network. LDP tunnels are widely used on MPLS VPNs. To prevent traffic
congestion on a certain node of a VPN, you can configure the LDP over RSVP feature.
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
That is, the LSP of an LDP tunnel traverses the RSVP TE domain and thus the LDP tunnel
can transmit VPN services.
When all the preceding tunnels traverse the third-party equipment, you can set the third-party
equipment as a virtual node to ensure that the tunnels are created properly.
3.2 Tunnel Configuration Flow
This section describes the operation tasks for configuring the Tunnel, and relations among these
tasks. When configuring and managing the Tunnel, follow the configuration flow.
Configure and manage Tunnels by following the configuration flow shown in Figure 3-7.
Figure 3-7 Tunnel configuration flow
Creating Network
Start
Required
End
Create the Tunnel
Optional
Configure the
network-side interface
Configure the LSR ID
Configure the
control plane

For the detailed configuration tasks shown in Figure 3-7, see Table 3-1.
Table 3-1 Tunnel configuration tasks
Task Remarks
1. Create Network To create a network, you need to create NEs, configure
NE data, create fibers and crate level 2 link.
2. Configure the network-side
interface
Set the general attributes and Layer 3 attributes (tunnel
enable status and IP address) for interfaces to carry the
tunnel carrying.
iManager U2000
3-11
Task Remarks
3. Configure the LSR ID Specifies the LSR ID for each NE that a service
traverses and the start value of the global label space.
Each LSR ID is unique on a network.
4. Configure the control plane Set the protocol parameters related to the control plane
to create the tunnel.
l When you create a static CR tunnel to carry services,
you do not need to set the parameters relevant to the
control plane but you need to manually add labels.
l When you create an RSVP TE tunnel to carry
services, the LDP automatically distributes labels. In
this case, you need to set the parameters relevant to
the control plane.
1. Set the IGP-ISIS protocol parameters.
2. Set the MPLS-RSVP protocol parameters.
l When you create an LDP Tunnel to carry services,
the LDP automatically distributes labels. In this case,
you need to set the parameters relevant to the control
plane.
1. Set the IGP-ISIS protocol parameters.
2. Create the MPLS-LDP.
l When you create an IP tunnel to carry services, the
label distribution protocol automatically allocates
the forwarding label value. In addition, you need to
configure parameters relevant to the control plane.
Create a static route table.
NOTE
To configure parameters relevant to the control plane, refer to
the descriptions of configuring the control plane in the
Operation Guide for PTN NE Management.
5. Create the Tunnel Configure the basic information, equipment list,
advanced attributes of the tunnel.

3.3 Configuring a Tunnel
This topic describes how to configure a tunnel, such as creating a tunnel, creating a protection
group, deploying a tunnel, viewing discrete tunnels, and deleting a tunnel.
3.3.1 Creating a Tunnel
This topic describes how to create a tunnel in the end-to-end mode. You can create a tunnel
easily and efficiently.
3.3.2 Creating Tunnels in Batches
In certain commonly used networks, the U2000 provides the function of creating tunnels in
batches. Currently, you can create only LDP and RSVP-TE tunnels in batches.
3.3.3 Creating a Protection Group
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
This topic describes how to create a tunnel protection group. If a tunnel protection group is
created, the services carried over the active tunnel is switched over to the protection tunnel when
the working tunnel is faulty.
3.3.4 Automatic Search for Protection Groups
This topic describes automatic search for protection groups. With this function, you can recover
the protection group existing on the current network to the end to end management module of
the NMS for monitoring. In this manner, you can ensure the normal running of these protection
group.
3.3.5 Deploying a Tunnel
This topic describes how to apply the settings of a tunnel to NEs.
3.3.6 Reoptimizing an RSVP TE Tunnel
When you reoptimize a tunnel, the trails of the tunnel are recalculated.
3.3.7 Viewing a Discrete Tunnel
To view a discrete tunnel facilitates the management of discrete tunnels.
3.3.8 Checking the Correctness of the Tunnel Configuration
After configuring a tunnel, you can check the connectivity of the tunnel by using the Test and
Check function.
3.3.9 Perform Tunnel Protection Group Switching
On the U2000, you can perform tunnel protection switching.
3.3.1 Creating a Tunnel
This topic describes how to create a tunnel in the end-to-end mode. You can create a tunnel
easily and efficiently.
Prerequisite
You must be an NM user with "network 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.
The control plane must be configured for the RSVP-TE, and IP tunnels.
Procedure
Step 1 Choose Service > Tunnel > Create Tunnel from the main menu.
iManager U2000
3-13
Step 2 Configure basic information.
NOTE
l When you create a reverse tunnel, the U2000 automatically allocates different Tunnel Name to the
forward and reverse tunnels. If you manually set Tunnel Name for the forward tunnel, the U2000
automatically set Tunnel Name to Forward Tunnel Name+_Reverse for the reverse tunnel.
l When "Signaling Type" is set to be Static CR. In this case, if you select Create Reverse Tunnel, the
U2000 creates two unidirectional tunnels in two opposite directions. If you select Create Bidirectional
Tunnel, the U2000 creates a bidirectional tunnel, which has two opposite directions.
l When "Signaling Type" is set to be Static CR, You can select the "Create Protection Group", the tunnel
and the protection group of tunnel are created at the same time.
l The "Template" parameter is available only when the "Signaling Type" parameter is set to RSVP
TE. You can configure the detailed information of a tunnel by using a template.
l When you create a RSVP-TE tunnel, you can select the "Configure As Bypass Tunnel" check box
to create a bypass protection tunnel.
l A static CR tunnel is created on the basis of certain constraints. The mechanism for creating and
managing those constraints are constraint-based routing (CR). Different from a static tunnel, the
establishment of a CR tunnel depends on the routing information and other conditions, for example,
the specified bandwidth, the fixed route, and QoS parameters. The PTN supports only the static CR
tunnel.
Step 3 Configure the NE list.
1. Select the source and sink NEs or the transit NE and configure the NE location in a tunnel
in the NE Role column.
You can select an NE in the following methods:
l Manner 1: In the physical topology in the upper right pane, select the required NE, right-
click and choose Add from the shortcut menu.
l Manner 2: In the physical topology in the upper right pane, double-click the required
NE.
l Manner 3:
a. Click Add and select NE from the drop-down list.
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
b. In the dialog box that is displayed, select the required NE and click OK.
NOTE
In the case of an RSVP-TE, LDP, or IP tunnel, you need to specify only the source and sink nodes
of the tunnel. In the case of a static CR tunnel, you need to specify the source node, sink node, and
transit nodes of the tunnel.
You can choose Add and select Virtual Node from the drop-down list to specify virtual nodes
through which a tunnel travels. A virtual node simulates an NE beyond the management range of the
U2000. The virtual node is used for creating a tunnel whose source NE is on the U2000 but the sink
NE is not on the U2000.
2. Optional: In the case of a static CR tunnel.
Set the route calculation for the U2000 as follows:
a. Select Auto-Calculate route. Then, the U2000 automatically calculates the routes for
a tunnel after you finish steps 2 and 3.
b. Set Restriction Bandwidth(Kbit/s) and specify the source and sink nodes.
c. Specify route constraint. Specifically, you can click Route Restriction and specify
route constraint in the dialog box that is displayed. Alternatively, you can specify the
explicit and excluded restriction through shortcut menu items in the physical topology.
NOTE
You can set NEs or ports as route constraints as required.
d. If you do not select Auto-Calculate route, you can click Calculate Route to calculate
the routes for a tunnel in the U2000.
NOTE
A layer 2 link must be configured before route calculation, refer the chapter of topology management
to configure the layer 2 link.
By default, the shortest route is selected from the routes that are calculated according to Restriction
Bandwidth(Kbit/s) and route constraints.
You select Create Protection Group and click Configure Protection Group to configure
parameters relevant to the protection group.
Step 4 Click Details to configure details of the tunnel.
NOTE
l It is recommended that you configure details of an RSVP-TE tunnel by using a template.
l In the case of a static CR tunnel, Next Hop is the IP address of the ingress port of the next node in the
direction of the tunnel.
l In the case of a static CR tunnel, double-click Out Interface or In Interface. In the dialog box that is
displayed, select an interface and click Configure to configure the attributes of the interface or click
Add Virtual Interface to create Ethernet virtual interface.
Step 5 Optional: In the case of static CR tunnel, if you select Create Protection Group, you can click
Configure Protection Group to configure parameters relevant to the protection group and click
Configure OAM to configure OAM parameters relevant to the protection group.
Step 6 Select the Deploy check box and click OK.
iManager U2000
3-15
NOTE
l If you clear the Deploy check box, the configuration data information is stored only on the U2000. If
you select the Deploy check box, the configuration data information is stored on the U2000 and applied
to NEs. By default, the Deploy check box is selected.
l When you select the Deploy and Enable check box, A tunnel is available on NEs only when it is
enabled.
----End
3.3.2 Creating Tunnels in Batches
In certain commonly used networks, the U2000 provides the function of creating tunnels in
batches. Currently, you can create only LDP and RSVP-TE tunnels in batches.
Prerequisite
Configuration of the port attributes must be correct.
Settings of the LSR ID for each NE must be correct.
Configuration of the control plan for each NE must be correct.
Procedure
Step 1 Choose Service > Tunnel > Batch Create Tunnel from the main menu.
Step 2 Configure basic information. In the Basic Information field, set the Network Type, Protocol
Type and Signaling Type parameters.
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
NOTE
Currently, the U2000 supports the following networking modes:
l 1. Full-Mesh: The equipment is bidirectionally and fully connected.
l 2. Hub-Spoke: All spoke nodes and hub nodes are directionally connected. In addition, the hub nodes
are bidirectionally and fully connected.
l 3. Ring: Bidirectional connections are generated based on rings.
You can set the Template parameter when the Signaling Type parameter is set to RSVP TE.
Step 3 Configure the NE list.
1. Select the source and sink NEs or the transit NE and configure the NE location in a tunnel
in the NE Role column.
You can select an NE in the following manners:
l Manner 1: In the physical topology in the upper right pane, select the required NE, right-
click and choose Add from the shortcut menu.
l Manner 2: In the physical topology in the upper right pane, double-click the required
NE.
l Manner 3:
a. Click Add and select NE from the drop-down list.
b. In the dialog box that is displayed, select the required NE and click OK.
2. Optional: You can set the NE Role parameter when the Network Type parameter is set
to Hub-Spoke.
Step 4 Click Auto-Assign. Then, the U2000 automatically assigns IDs to the tunnels created in batches.
NOTE
You can also enter tunnel IDs.
Step 5 Configure details of tunnels.
l In the case of RSVP-TE tunnels, set the General, TE Information, Trail Information,
Protection Attribute, QoS Information, and Advance Information parameters.
l In the case of LDP tunnels, set the EXP parameter.
NOTE
If you select the Deploy check box, the tunnel information is stored on the U2000 and applied to NEs. By
default, the Deploy check box is selected.
When you select the Deploy and Enable check box, A tunnel is available on NEs only when it is enabled.
----End
3.3.3 Creating a Protection Group
This topic describes how to create a tunnel protection group. If a tunnel protection group is
created, the services carried over the active tunnel is switched over to the protection tunnel when
the working tunnel is faulty.
Prerequisite
iManager U2000
3-17
The working and protection tunnels of an MPLS tunnel must be created.
Context
Figure 3-8 shows the window for creating a tunnel protection group.
Figure 3-8 The figure of tunnel protection group

Precautions:
l The MPLS APS protection must not be coupled with the FRR, LMSP, LAG, and microwave
1+1 protection.
l The protection tunnel should not carry any extra service.
Procedure
Step 1 Choose Service > Tunnel > Create Protection Group from the main menu.
Step 2 Configure basic information of a tunnel protection group.
NOTE
If a tunnel protection group is of the 1+1 protection type, services are dually fed on the source and selectively
received on the sink. If a tunnel protection is of the 1:1 protection type, services are processed in the single
fed single receiving mode.
Single-ended switching refers to the scenario wherein only the local end is switched but the peer end is not
notified to switch when a fault occurs at one end. Single-ended switching does not negotiate by using
negotiation packets. Therefore, it is fast and reliable.
Dual-ended switching refers to the scenario wherein the local end is switched and the peer end is notified
to switch when a fault occurs at one end. In the case of dual-ended switching, the come-and-go path of a
service is the same. This facilitates service management.
Step 3 Click Add. In the dialog box that is displayed, select the working tunnel and the protection tunnel
and click OK.
Step 4 Optional: Select a required tunnel, click Configure OAM, and then configure the OAM
information of the tunnel. An OAM packet is used to detect the connectivity of a link. When a
fault occurs on the working tunnel, services are switched to the protection tunnel.
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
NOTE
By default, the OAM status is enabled for the protection tunnel, to ensure that the duration of switching to
the protection tunnel is less than 50 ms, set the detect type to FFD and the frequency to 3.3.
It is optional to configure OAM. If you do not configure it, the U2000, by default, enables the OAM of the
tunnel protection group when you configure the tunnel protection group.
You can set other OAM parameters only when you set OAM Status to Enabled. You can set Detection
Packet Type and Detection Packet Period(ms) only when you set Detection Mode of the sink to
Manual. The value of SF Threshold must be equal to or greater than the value of SD Threshold.
Step 5 Configure attributes of the tunnel protection group.
Step 6 Choose Deploy. Click OK.
----End
3.3.4 Automatic Search for Protection Groups
This topic describes automatic search for protection groups. With this function, you can recover
the protection group existing on the current network to the end to end management module of
the NMS for monitoring. In this manner, you can ensure the normal running of these protection
group.
iManager U2000
3-19
Prerequisite
Procedure
Step 1 Choose Service > Tunnel > Search for Protection Group from the main menu.
Step 2 In the dialog box that is displayed, click Add, select required equipment, and then click OK.
Step 3 Click OK. A dialog box is displayed indicating the number of protection groups.
Step 4 Click OK in the Prompt dialog box.
----End
3.3.5 Deploying a Tunnel
This topic describes how to apply the settings of a tunnel to NEs.
Prerequisite
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the main menu.
Step 2 In the Set Filter Criteria dialog box, set the filter criteria. Then, click Filter. The services
meeting the filter criteria are displayed in the query result area.
Step 3 Right-click a tunnel whose settings are not applied to NEs and choose Deploy from the shortcut
menu.
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
Step 4 Click Close in the dialog box displayed.
----End
3.3.6 Reoptimizing an RSVP TE Tunnel
When you reoptimize a tunnel, the trails of the tunnel are recalculated.
Prerequisite
Only deployed RSVP TE tunnels can be reoptimized.
Procedure
Step 3 Right-click the required tunnel and choose Reoptimize from the shortcut menu. The
Reoptimization dialog box is displayed.
Step 4 Click Add or Delete to set the route constraints for the reoptimization of the tunnel.
NOTE
When you reoptimize a tunnel, the service may be interrupted.
Step 5 Click OK. In the dialog box that is displayed, click OK.
Step 6 Right-click the tunnel and choose View LSP Topology from the shortcut menu to view the
actual route of the tunnel after optimization.
----End
3.3.7 Viewing a Discrete Tunnel
To view a discrete tunnel facilitates the management of discrete tunnels.
Prerequisite
A discrete tunnel must exist on the U2000.
Procedure
Step 1 Choose Service > Tunnel > Manage Discrete Tunnel from the main menu.
Step 2 Click Filter Criteria. In the dialog box that is displayed, set filtering criteria and click Filter.
Step 3 On the discrete tunnel management window, select a discrete tunnel, click the corresponding
tab to view details.
Step 4 Optional: Select a discrete tunnel, click Delete button and click Yes in the dialog box displayed.
----End
iManager U2000
3-21
3.3.8 Checking the Correctness of the Tunnel Configuration
After configuring a tunnel, you can check the connectivity of the tunnel by using the Test and
Check function.
Prerequisite
The tunnel must be deployed.
Procedure
Step 3 Right-click a service and choose Test and Check from the shortcut menu.
Step 4 In the window that is displayed, select the trail to be checked.
Step 5 Set Diagnosis Option.
Set diagnosis parameters based on the requirements of operation and maintenance. The meaning
of each option is as follows:
1. Service Check:to check the connectivity of a static CR tunnel, you can verify that the labels
of the NEs that the tunnel traverses are consistent.
2. OAM Tool: check the connectivity by performing the ping operation on each layer.
3. Tracert: location is used to find out the fault position.
Step 6 Click Run.
Step 7 View the running results.
----End
3.3.9 Perform Tunnel Protection Group Switching
On the U2000, you can perform tunnel protection switching.
Prerequisite
You must complete the creation of the tunnel protection group and you must have enable the
protocol status.
Context
l 1+1 protection
Services are transmitted over the working tunnel and protection tunnel at the same time.
Then, the receive end selects a tunnel according to the status of the two tunnels and receives
the services from the tunnel. That is, the services are dually fed and selectively received.
When the receive end detects loss of signals over the working tunnel or when the working
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
tunnel is detected as faulty by the MPLS OAM, the receive end receives the signals from
the protection tunnel. In this manner, the services are switched.
l 1:1 protection
Normally, services are transmitted over the working tunnel. That is, the services are singly
fed and received. When the working tunnel is faulty, the equipment at the two ends
negotiates through the APS protocol. Then, the transmit end transmits the services over the
protection tunnel and the receive end receives the services from the protection tunnel. In
this manner, the services are switched.
CAUTION
When other switching operations, excluding the exercise switching, are performed, the services
may be interrupted.
Procedure
Step 1 Choose Service > Tunnel > Manage Protection Group from the main menu.
Step 2 Check the switching status of the tunnel protection group. Right-click the protection group under
test, and choose Query Switching Status from the shortcut menu to refresh the status of the
tunnel protection group.
Step 3 Optional: When the Protocol Status is Disabled for the protection group, click Hop
Information tab, set Protocol Status to Enabled for the device of protection group, click
Apply.
NOTE
When the Protocol Status is Enabled, you can perform tunnel protection switching.
Step 4 Perform tunnel protection group switching.
1. Optional: Right-click the protection group under test, and choose Switch > Clear.
2. Optional: Right-click the protection group under test, and choose Switch > Force
Switching.
3. Optional: Right-click the protection group under test, and choose Switch > Manual
Switching To Working.
4. Optional: Right-click the protection group under test, and choose Switch > Manual
Switching To Protection.
5. Optional: Right-click the protection group under test, and choose Switch > Exercise
Swtiching.
6. Optional: Right-click the protection group under test, and choose Switch > Lockout of
Protection.
Step 5 Repeat step 2, Query the switching status of the protection group.
----End
3.4 Monitoring a Tunnel
This topic describes how to monitor a tunnel to facilitate tunnel services management.
iManager U2000
3-23
3.4.1 Configuring OAM for a Tunnel
This topic describes how to configure OAM for a tunnel.
3.4.2 Viewing the VPN Service Carried on a Tunnel
TAfter viewing VPN services that are transmitted in a tunnel, you can conveniently manage the
tunnel and the VPN services.
3.4.3 Viewing the Topology of a Tunnel
This topic describes how to view the tunnel topology. By viewing the topology of a tunnel, you
can learn the topology structure and running status of the tunnel in real time
3.4.4 Viewing the Performance of a Tunnel
This topic describes how to view the performance of a tunnel.
3.4.5 Viewing the Alarms of a Tunnel
This topic describes how to view the alarms of a tunnel.
3.4.6 Monitoring the Running Status of a Tunnel
By using this function, you can view the running status of a tunnel in real time.
3.4.7 Viewing the LSP Topology of a Tunnel
This topic describes how to view the LSP topology of a tunnel. To view the actual routing
information of a tunnel, you can perform this operation.
3.4.8 Diagnosing a Tunnel
This topic describes how to diagnose a tunnel by performing the LSP ping and LSP tracert tests.
3.4.1 Configuring OAM for a Tunnel
This topic describes how to configure OAM for a tunnel.
Prerequisite
l You must be an NM user with "network operator" authority or higher.
l The running status of RSVP TE tunnel is UP.
l OAM cannot be configured for an IP and LDP tunnel.
Procedure
Step 3 Right-click a required tunnel and choose OAM > Configure OAM from the shortcut menu.
Step 4 In the dialog box that is displayed, set OAM parameters of the tunnel.
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
Step 5 Click OK.
Step 6 Select one or more tunnel, right click and choose OAM > Enable OAM to enable the OAM of
tunnel.
----End
3.4.2 Viewing the VPN Service Carried on a Tunnel
TAfter viewing VPN services that are transmitted in a tunnel, you can conveniently manage the
tunnel and the VPN services.
Prerequisite
You must be an NM user with "NM monitor" authority or higher.
Procedure
iManager U2000
3-25
Step 3 Right-click a required tunnel and choose View VPN from the shortcut menu.
NOTE
You can view the VPN service of only one tunnel at a time.
You can view the end-to-end services that are transmitted in a tunnel, but not the discrete services that are
transmitted in the tunnel.
Step 4 View information of the VPN service carried on the tunnel in View VPN window.
Step 5 Optional: Select a required VPN service, click View Details. In the relevant service
management window, you can view or modify parameters of the VPN service.
----End
3.4.3 Viewing the Topology of a Tunnel
This topic describes how to view the tunnel topology. By viewing the topology of a tunnel, you
can learn the topology structure and running status of the tunnel in real time
Prerequisite
Procedure
Step 3 Select a required tunnel and view the topology of the tunnel.
Perform the following operations as required.
l In the topology, right-click an NE and choose View Real-Time Performance or NE
Explorer from the shortcut menu.
l In the topology, right-click a link and choose Fast Diagnose, View VPN, View LSP
Topology, or Alarm from the shortcut menu.
NOTE
You can view the real-time performance of only the tunnels that are in the deployed states. You can view
the LSP topology of the RSVP TE tunnel that is in the UP running state.
Step 4 Optional: On the window for creating a tunnel, click the Service Topology tab to view topology
information of the new tunnel.
Step 5 Optional: In the Main Topology, click Current View, select Tunnel View from the drop-down
list, and then view the topology of the tunnel in the network-side tunnel topology view.
----End
3.4.4 Viewing the Performance of a Tunnel
This topic describes how to view the performance of a tunnel.
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
Prerequisite
Procedure
Step 3 View the runtime performance of a tunnel. Right-click the NE and choose View Real-Time
Performance from the shortcut menu in the topology view.
Step 4 Create a monitoring instance for a tunnel. For details, refer to the chapter of monitoring instance
management in Performance Management System (PMS).
Step 5 View the history performance of a tunnel. Right-click a required tunnel and choose
Performance > View History Data from the shortcut menu.
----End
3.4.5 Viewing the Alarms of a Tunnel
This topic describes how to view the alarms of a tunnel.
Prerequisite
Procedure
Step 3 View the Alarm Status parameter of a tunnel.
Step 4 Right-click a required tunnel and choose Alarm > View Current Alarm from the shortcut menu
to view current alarms of the tunnel.
Step 5 Right-click a required tunnel and choose Alarm > View History Alarm from the shortcut menu
to view history alarms of the tunnel.
----End
3.4.6 Monitoring the Running Status of a Tunnel
By using this function, you can view the running status of a tunnel in real time.
Prerequisite
iManager U2000
3-27
Procedure
Step 3 Right-click the tunnel and select Update Running Status, view the Running Status parameter
of a tunnel.
----End
3.4.7 Viewing the LSP Topology of a Tunnel
This topic describes how to view the LSP topology of a tunnel. To view the actual routing
information of a tunnel, you can perform this operation.
Prerequisite
The RSVP-TE tunnel and the LDP tunnel must support this operation and the running status of
tunnel is UP.
The function of viewing a tunnel must be supported.
Procedure
Step 3 Right-click a required tunnel and choose View LSP Topology from the shortcut menu. Click
the link in the dialog box that is displayed, view the actual routing information of the tunnel.
----End
3.4.8 Diagnosing a Tunnel
This topic describes how to diagnose a tunnel by performing the LSP ping and LSP tracert tests.
Prerequisite
In the case of a static CR tunnel, the IS-IS protocol must be enabled on the source and sink ports
of an MPLS tunnel. Alternatively, a diagnose test must be initiated at the local NE and a static
route in control plane must be configured on the opposite NE.
Procedure
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
Step 3 Configure a scheduled test.
1. Right-click a required tunnel and choose Diagnose > Create Test Suite from the shortcut
menu.
2. Select the Select check box and click Next.
3. Select the LSP Ping check box and click Details. In the dialog box that is displayed, set
advance test parameters and click OK.
4. Set parameters in the Test Time field, click Add, and then click Finish.
Step 4 View the test strategy.
1. Right-click a required tunnel and choose Diagnose > View Test Strategy from the shortcut
menu.
2. Click Condition. In the dialog box that is displayed, set relevant criteria and click OK.
Click Query.
3. Select a record and click Task Information and Associated Test Suite to view relevant
information.
Step 5 View the result of a scheduled test.
1. Right-click a required tunnel and choose Diagnose > View Test Result from the shortcut
menu.
2. Click Query to view the result of a scheduled test.
3. Optional: Click Export Result to export the result of the scheduled test to local computer.
NOTE
The result of a scheduled test can be exported in a .cvs, .html, .xls, .pdf or .txt file.
Step 6 Configure a manual test.
1. Right-click a required tunnel and choose Test and Check from the shortcut menu.
2. Optional: Select the LSP Ping or ICMP Ping check box and click . In the dialog
box that is displayed, set parameters of the ping test and click OK.
3. Optional: Select the LSP Tracert or ICMP Tracert check box and click . In the
dialog box that is displayed, set parameters of the LSP tracert test and click OK.
4. Click Run and view the test result on the right pane.
----End
3.5 Tunnel Configuration Example
This topic describes configuration examples of creating tunnels in the end-to-end mode. In
addition to the examples, the configuration flow diagrams are provided for you to learn the
service configuration processes. A configuration example describes a networking scenario and
the corresponding process of creating a tunnel on an actual network. A configuration example
includes information about the configuration networking diagram, service planning, and
configuration process.
3.5.1 Configuration Example (Static CR Tunnel)
This topic describes a networking diagram and the corresponding example of configuring a static
CR tunnel on the network.
3.5.2 Configuration Example (RSVP TE Tunnel)
iManager U2000
3-29
RSVP TE tunnel on the network.
3.5.3 Configuration Example (IP and LDP Tunnels)
This topic describes a networking diagram and the corresponding example of configuring an IP
tunnel and an LDP tunnel on the network.
3.5.1 Configuration Example (Static CR Tunnel)
CR tunnel on the network.
Example Description
This topic describes O&M scenarios and networking diagrams.
As shown in Figure 3-9, the service between NodeB and RNC is to be carried by static CR
tunnels. 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.
l Working tunnel: NE1-NE2-NE3. NE2 is a transit node.
l 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 3-9 Networking diagram of an MPLS tunnel
Working Tunnel
Protection Tunnel
OptiX PTN 3900 OptiX PTN 1900
NodeB
RNC
NE1
NE2
NE3
NE4
NE5
NE6
GE ring on
access layer
10GE ring on
convergence
layer

NE1 and NE6 are OptiX PTN 1900 NEs. NE2, NE3, NE4 and NE5 are OptiX PTN 3900 NEs.
Figure 3-10 shows the planning details of boards on the NE and interfaces on the boards.
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
Figure 3-10 NE planning
Working Tunnel
Protection Tunnel
NodeB
4-EFG2-1(Port-1)
10.0.5.2
RNC
NE1
NE2 NE3
NE4
NE5
NE6
4-EFG2-1(Port-1)
10.0.0.1
4-EFG2-2(Port-2)
10.0.5.1
3-EG16-1(Port-1)
10.0.0.2
1-EX2-1(Port-1)
10.0.1.2
1-EX2-1(Port-1)
10.0.1.1
1-EX2-2(Port-2)
10.0.2.1
4-EFG2-2(Port-2)
10.0.4.1
3-EG16-1(Port-1)
10.0.4.2
1-EX2-1(Port-1)
10.0.3.2 1-EX2-1(Port-1)
10.0.2.2
1-EX2-2(Port-2)
10.0.3.1
GE ring on
access layer
10GE ring on
convergence
layer

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 3-2 lists the planned tunnel parameters.
Table 3-2 Planning of Tunnel parameters
Parameter
Working Tunnel
Protection
Tunnel

Tunnel ID 100 101 120 121
Tunnel Name Working
Tunnel
Working
Tunnel_Reverse
Protection
Tunnel
Protection
Tunnel_Reverse
Signaling Type Static CR Static CR Static CR Static CR
Protocol Type MPLS MPLS MPLS MPLS
LSP Type E-LSP E-LSP E-LSP E-LSP
EXP None None None None
Bandwidth
(Kbit/s)
10000 10000 10000 10000
CBS(byte) 10000 10000 10000 10000
PIR(Kbit/s) 20000 20000 20000 20000
PBS(byte) 20000 20000 20000 20000
MTU 1620 1620 1620 1620
iManager U2000
3-31
Parameter
Working Tunnel
Protection
Tunnel

NE Role NE1: Ingress
NE2: Transit
NE3: Egress
NE3: Ingress
NE2: Transit
NE1: Egress
NE1: Ingress
NE6, NE5, NE4:
Transit
NE3: Egress
NE3: Ingress
NE4, NE5, NE6:
Transit
NE1: Egress
Ingress Node
Route
Information
NE1
l Out
Interface: 4-
EFG2-1
l Out Label:
20
NE3
l Out Interface:
1-EX2-1
l Out Label: 21
NE1
l Out Interface:
4-EFG2-2
l Out Label: 22
NE3
l Out Interface:
1-EX2-2
l Out Label: 23
Transit Node
Route
Information
NE2
l In Interface:
3-EG16-1
l In Label: 20
l Out
Interface: 1-
EX2-1
l Out Label:
30
NE2
l In Interface: 1-
EX2-1
l In Label: 21
l Out Interface:
3-EG16-1
l Out Label: 31
NE6
l In Interface:
4-EFG2-1
l In Label: 22
l Out Interface:
4-EFG2-2
l Out Label: 32
NE5
l In Interface:
3-EG16-1
l In Label: 32
l Out Interface:
1-EX2-1
l Out Label: 42
NE4
l In Interface:
1-EX2-2
l In Label:42
l Out Interface:
1-EX2-1
l Out Label: 52
NE4
l In Interface:
1-EX2-1
l In Label: 23
l Out Interface:
1-EX2-2
l Out Label: 33
NE5
l In Interface:
1-EX2-1
l In Label: 33
l Out Interface:
3-EG16-1
l Out Label: 43
NE6
l In Interface:
4-EFG2-2
l In Label: 43
l Out Interface:
4-EFG2-1
l Out Label: 53
Egress Node
Route
Information
NE3
l In Interface:
1-EX2-1
l In Label: 30
NE1
l In Interface: 4-
EFG2-1
l In Label: 31
NE3
l In Interface:
1-EX2-2
l In Label: 52
NE1
l In Interface:
4-EFG2-2
l In Label: 53

3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
Table 3-3 Planning of protection group parameters
Parameter Vlaue
Group Name Protection Group
Protection Type 1:1
Switch Mode Double-Ended
Protocol Status Enabled
Revertive Mode Revertive
WTR Time(min) 5
Hold-off Time(100ms) 0
Tunnel Type Forward Working (Working Tunnel)
Forward Protecting (Protection Tunnel)
Backward Working (Working
Tunnel_Reverse)
Backward Protecting (Protection
Tunnel_Reverse)

Configuration Process
This topic describes how to configure the static CR tunnel.
Prerequisite
You must understand the networking, requirements and service planning of the example.
A network must be created and Allocate IP addresses to ports automatically. Allocating IP
addresses to ports automatically refer to Allocating IP Addresses to Ports Automatically.
Procedure
Step 1 Set LSR IDs.
1. In the NE Explorer, select NE1 and choose Configuration > MPLS Management > Basic
Configuration from the Function Tree.
2. Set LSR ID, Start of Global Label Space, and other parameters. Click Apply.
Parameter Example Value Principle for Value
Selection
LSR ID NE1: 1.0.0.1 Set this parameter
according to the network
planning. In addition, this
value is unique on the entire
network.
iManager U2000
3-33
Selection
Start of Global Label Space 0 Set this parameter
planning.

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.
Selection
LSR ID 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
Set this parameter
network.
planning.

Step 2 Create the working tunnel.
1. Choose Service > Tunnel > Create Tunnel from the main menu.
2. Set the basic information about the working tunnel.
Selection
Tunnel Name Working Tunnel Set this parameter
according to the service
planning.
Protocol Type MPLS Set this parameter
planning.
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
Selection
Signaling Type Static CR Set this parameter
planning.
Create Reverse Tunnel Selected This parameter is selected
when a reverse tunnel needs
to be created.

3. Configure the NE list. On the physical topology, double-click NE1, NE2, and NE3 to add
them to the NE list and set the corresponding NE roles.
Selection
NE2: Transit
NE3: Egress
An ingress is the incoming
node of a network. In this
example, NE1 is an ingress
node.
A transit is a pass-through
node. In this example, NE2
is a transit node.
An egress is the outgoing
example, NE3 is an egress
node.
Deploy Selected When this parameter is
selected, a tunnel is saved
on the U2000 and applied
to the corresponding NEs

4. Click Details to set the advanced parameters of the reverse tunnel. Click OK.
Selection
Tunnel ID l Forward Tunnel: 100
l Reverse Tunnel: 101
Set this parameter
planning.
iManager U2000
3-35
Selection
Bandwidth(Kbit/s) Forward and Reverse
Tunnels: 10000
Set this parameter
planning.
CBS(byte) Forward and Reverse
Tunnels: 10000
Set this parameter
planning.
PIR(Kbit/s) Forward and Reverse
Tunnels: 20000
Set this parameter
planning.
PBS(byte) Forward and Reverse
Tunnels: 20000
Set this parameter
planning.
MTU Forward and Reverse
Tunnels: 1620
Set this parameter
planning.
LSP Type Forward and Reverse
Tunnels: E-LSP
Currently, this parameter
can be set to E-LSP only.
EXP Forward and Reverse
Tunnels: None
Set this parameter
planning.
Out Interface Forward Tunnel:
l NE1: 4-EFG2-1
l NE2: 1-EX2-1
Reverse Tunnel:
l NE3: 1-EX2-1
l NE2: 3-EG16-1
Set this parameter
planning. Only this
parameter needs to be set
for only the ingress node
and transit node.
Out Label Forward Tunnel:
l NE1: 20
l NE2: 30
Reverse Tunnel:
l NE3: 21
l NE2: 31
Set this parameter
planning.
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
Selection
In Interface Forward Tunnel:
l NE2: 3-EG16-1
l NE3: 1-EX2-1
Reverse Tunnel:
l NE2: 1-EX2-1
l NE1: 4-EFG2-1
Set this parameter
planning. Only this
for only the egress node and
transit node.
In Label Forward Tunnel:
l NE2: 20
l NE3: 30
Reverse Tunnel:
l NE2: 21
l NE1: 31
Set this parameter
planning.
Next Hop Forward Tunnel:
l NE1: 10.0.0.2
l NE2: 10.0.1.2
Reverse Tunnel:
l NE3: 10.0.1.1
l NE2: 10.0.0.1
Set this parameter
planning. Only this
and transit node.

Step 3 Create the protection tunnel.
1. Create the protection tunnel by referring to Step 2.1 through Step 2.4.
Set the basic Information as follows:
Selection
planning.
planning.
planning.
to be created.

iManager U2000
3-37
Set the node information as follows:
Selection
NE6, NE5, NE4: Transit
NE3: Egress
node.
node. In this example, NE6,
NE5, and NE4 are transit
nodes.
node.
on the U2000 and delivered

For route details, see the descriptions of route settings in Table 3-2.
Step 4 Creating the protection group.
1. Choose Service > Tunnel > Create Protection Group from the main menu.
2. Configure basic information of a tunnel protection group.
Selection
Group Name Protection Group Set this parameter
planning.
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
Selection
Protection Type 1:1 Set this parameter
planning.
Switch Mode Double-Ended This parameter is selected
to be created.

3. Click Add. In the dialog box that is displayed, select the working tunnel and the protection
tunnel and click OK.
4. Configure the type of tunnel.
Selection
Tunnel Type Forward Working
(Working Tunnel)
Forward Protecting
(Protection Tunnel)
Backward Working
(Working
Tunnel_Reverse)
Backward Protecting
(Protection
Tunnel_Reverse)
Set this parameter
planning.

5. Configure attributes of the tunnel protection group, choose Deploy, click OK.
Selection
Protocol Status Enabled Set this parameter
planning.
Revertive Mode Revertive Set this parameter
planning.
WTR Time(min) 5 This parameter is selected
to be created.
Hold-off Time(100ms) 0 Set this parameter
planning.

----End
iManager U2000
3-39
3.5.2 Configuration Example (RSVP TE Tunnel)
RSVP TE tunnel on the network.
Example Description
As shown in Figure 3-11, 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 reliability. Hence, FRR protection should also be
configured for the MPLS tunnel between NE1 and NE3.
l The NE1-to-NE3 working tunnel is along the NE1-NE2-NE3 trail. NE2 is the transit node.
l 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 working tunnel.
l 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 working tunnel.
Figure 3-11 Networking diagram of an RSVP TE tunnel
A Company
City1
A Company
City2
NE1
NE2
Bypass Tunnel 2
Bypass Tunnel 1
NE4
NE3
Working Tunnel

Figure 3-12 shows the NE planning. NE1 is an OptiX PTN 1900 NE. NE2, NE3 and NE4 are
OptiX PTN 3900 NEs.
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
A Company
City1
A Company
City2
NE1
NE2
NE3
NE4
Bypass Tunnel 2
Bypass Tunnel 1
4-EFG2-2
4-EFG2-1
1-EG16-2 1-EG16-1
1-EG16-2
1-EG16-1
1-EG16-1
1-EG16-2
1-
EG16-3
1-
EG16-3
10.1.1.1 10.1.2.2
10.1.2.1
10.1.5.1
10.1.5.2
10.1.4.1
10.1.3.1
10.1.3.2
10.1.1.2
10.1.4.2
Working Tunnel

Service Planning
The services between the branches of Company A are carried by the working tunnel. Bypass
tunnel 1 and bypass tunnel 2 provide FRR protection for the working tunnel.
On the NNI side of the NEs, the GE boards are used and a GE ring is built on the boards. Assume
that the IP addresses of the ports of NEs are the same as those listed in Table 3-4 after the U2000
automatically allocates the IP addresses of ports.
Table 3-4 Configuration parameters of NEs
NEs LSR ID Interface IP Address of the
Interface
Subnet Mask of
the Interface
NE1 1.0.0.1
4-EFG2-1(Port-1) 10.1.1.2 255.255.255.252
4-EFG2-2(Port-2) 10.1.3.2 255.255.255.252
NE2 1.0.0.2
1-EG16-1(Port-1) 10.1.1.1 255.255.255.252
1-EG16-2(Port-2) 10.1.2.2 255.255.255.252
1-EG16-3(Port-3) 10.1.4.2 255.255.255.252
NE3 1.0.0.3
1-EG16-1(Port-1) 10.1.2.1 255.255.255.252
1-EG16-2(Port-2) 10.1.5.1 255.255.255.252
NE4 1.0.0.4
1-EG16-1(Port-1) 10.1.3.1 255.255.255.252
1-EG16-2(Port-2) 10.1.5.2 255.255.255.252
1-EG16-3(Port-3) 10.1.4.1 255.255.255.252

Since the service bandwidth is 10Mbit/s, the bypass tunnel should have bandwidth more than
10Mbit/s. In addition, the service travels through several NEs. Hence, several bypass tunnels
iManager U2000
3-41
are required to completely protect the tunnel for the service. According to the actual condition,
two bypass tunnels are planned for the FRR.
Table 3-5 lists the planned parameters of the working tunnel and the two bypass tunnels.
Table 3-5 Configuration parameters of Tunnels
Parameter Working Tunnel Bypass Tunnel 1 Bypass Tunnel 2
Tunnel ID Positive: 1
Revers: 2
Positive: 3
Revers: 4
Positive: 5
Revers: 6
Tunnel Name Positive:
Tunnel-0001
Positive:
Tunnel-0003
Positive:
Tunnel-0005
Protocol Type MPLS MPLS MPLS
Signaling Type RSVP TE RSVP TE RSVP TE
LSP Type E-LSP E-LSP E-LSP
Bandwidth(Kbit/s) 10000 10000 10000
Tunnel Source
Node
NE1 NE1 NE2
Tunnel Sink Node NE3 NE3 NE3
Enable Affinity Selected (Forward
and Reverse Tunnels)
Selected (Forward
and Reverse
Tunnels)
Selected (Forward
and Reverse Tunnels)
Color(0x) 0 (Forward and
Reverse Tunnels)
0 (Forward and
Reverse Tunnels)
0 (Forward and
Reverse Tunnels)
Mask(0x) 0 (Forward and
Reverse Tunnels)
0 (Forward and
Reverse Tunnels)
0 (Forward and
Reverse Tunnels)
Route Restriction
Object (Positive)
IP Address:
l NE2: 10.1.1.1
l NE3: 10.1.2.1
Hop Type: Strictly
include
IP Address:
l NE4: 10.1.3.1
l NE3: 10.1.5.1
Hop Type: Strictly
include
IP Address:
l NE4: 10.1.4.1
l NE3: 10.1.5.1
Hop Type: Strictly
include
Route Restriction
Object (Revers)
IP Address:
l NE2: 10.1.2.2
l NE1: 10.1.1.2
Hop Type: Strictly
include
IP Address:
l NE4: 10.1.5.2
l NE1: 10.1.3.2
Hop Type: Strictly
include
IP Address:
l NE4: 10.1.5.2
l NE2: 10.1.4.2
Hop Type: Strictly
include
Enable FRR Yes (Forward and
Reverse Tunnels)
Yes (Forward and
Reverse Tunnels)
Yes (Forward and
Reverse Tunnels)
FRR BW Type facility (Forward and
Reverse Tunnels)
facility (Forward and
Reverse Tunnels)
facility (Forward and
Reverse Tunnels)
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
Parameter Working Tunnel Bypass Tunnel 1 Bypass Tunnel 2
FRR Protect Type Node Protection
(Forward and
Reverse Tunnels)
Node Protection
(Forward and
Reverse Tunnels)
Node Protection
(Forward and Reverse
Tunnels)
FRR Bandwidth
(Kbit/s)
10000 (Forward and
Reverse Tunnels)
10000 (Forward and
Reverse Tunnels)
10000 (Forward and
Reverse Tunnels)
LSP Type E-LSP (Forward and
Reverse Tunnels)
E-LSP (Forward and
Reverse Tunnels)
E-LSP (Forward and
Reverse Tunnels)
EXP 4 (Forward and
Reverse Tunnels)
E-LSP (Forward and
Reverse Tunnels)
E-LSP (Forward and
Reverse Tunnels)
Protect Interface - Positive: NE1-4-
EFG2-1
Reverse: NE3-1-
EFG16-1
Positive: NE2-1-
EFG16-2
Reverse: NE3-1-
EFG16-1
NOTE
In this example, the subnet mask for each network-side port is 255.255.255.252.

This topic describes how to configure the RSVP TE tunnel in the example.
Prerequisite
Procedure
Step 1 Set LSR IDs.
Selection
network.
iManager U2000
3-43
Selection
Start of Global Label Space 0 This parameter indicates
the minimum value for the
ingress or egress label. You
need to set this parameter
planning.

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.
Selection
LSR ID l NE2: 1.0.0.2
l NE3: 1.0.0.3
l NE4: 1.0.0.4
Set this parameter
network.
planning.

Step 2 Configure the control plane.
1. In the NE Explorer, select NE1 and choose Configuration > Control Plane
Configuration > IGP-ISIS Configuration from the Function Tree.
2. Click the Node Configuration tab page. Click New. Configure the related parameters in
the dialog box displayed.
Selection
IGP-ISIS Instance ID 1 The value of IGP-ISIS
Instance ID must be one
and only.
Node Level level-1-2 The node takes part in the
route computation of L1
and L2, and also maintains
the link state databases
(LSDBs) of L1 and L2

3. Click the Port Configuration tab page. Click New. In the dialog box displayed, click
Add. Select 4-EFG2-1(Port-1) and 4-EFG2-2(Port-2), and click OK.
Set parameters as follows:
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
Selection
Link Level level-1-2 The port can establish both
the level-1 neighboring
relationship and level-2
neighboring relationship.
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 an 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)
100 Sets the minimum delay
between two consecutive
LSPs.

4. Display the NE Explorers of NE2, NE3, and NE4 separately and refer to Step 2.1 through
Step 2.3 to set control plane parameters for NE2, NE3, and NE4.
The parameters of NE2, NE3, and NE4 are the same as those of NE1, except that the ports
specified for NE2, NE3, and NE4 are different as follows:
Selection
Port NE2:
l 1-EG16-1(Port-1)
l 1-EG16-2(Port-2)
l 1-EG16-3(Port-3)
NE3:
l 1-EG16-1(Port-1)
l 1-EG16-2(Port-2)
NE4:
l 1-EG16-1(Port-1)
l 1-EG16-2(Port-2)
l 1-EG16-3(Port-3)
Set this parameter
planning.

Step 3 Create an active tunnel.
2. Set the basic information about a tunnel.
iManager U2000
3-45
Selection
Tunnel Name Tunnel-0001 Set this parameter
planning.
planning.
Signaling Type RSVP TE Set this parameter
planning.
to be created.

3. Configure the NE list. On the physical topology, double-click NEs to add them to the NE
list. Then, specify the ingress and egress NEs.
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
Selection
NE3: Egress
node.
node.

4. Click Details to configure details of the tunnel management.
The general information is as follows:
Selection
Tunnel ID Forward Tunnel: 1
Reverse Tunnel: 2
Set this parameter
planning.

Choose Trail InformationAffinity Information, right-click, and choose Insert
Instance.
The parameters of the affinity object are as follows:
Selection
Enable Affinity Forward and Reverse
Tunnels: Yes
After you select Enable
Affinity, when the active
tunnel is faulty, the links
with the same route color
are preferred during a
rerouting.
Color(0x) Forward and Reverse
Tunnels: 0
The forward and reverse
tunnels are set to the same
value.
Mask(0x) Forward and Reverse
Tunnels: 0
value.

iManager U2000
3-47
Choose Trail Information > Route Restriction, right-click, and choose Insert
Instance.
The parameters of a hop-by-hop object are as follows:
Selection
IP Address Forward Tunnel: 10.1.1.1,
10.1.2.1
Reverse Tunnel: 10.1.2.2,
10.1.1.2
Set the IP address that a
tunnel traverses. For the
forward tunnel, use the IP
address of the NE2-1-
EG16-1(Port-1) and
NE3-1-EG16-1(Port-1)
ports. For the reverse
tunnel, use the IP addresses
of the NE2-1-EG16-2
(Port-2) and NE1-4-
EFG2-1(port-1) ports.
Hop Type Forward and Reverse
Tunnels: Strictly include
When this parameter is set
to Strictly include, the
tunnel is created strictly in
the sequence of the set IP
addresses.

Choose Protection Attribute > FRR.Attribute.
Fast reroute attributes are as follows:
Selection
Enable FRR Forward and Reverse
Tunnels: Yes
Select this parameter to
enable the FRR function.
FRR BW Type Forward and Reverse
Tunnels: facility
Currently, only facility is
supported. In this mode, a
protection tunnel can
protect multiple LSPs.
FRR Protect Type Forward and Reverse
Tunnels: Node Protection
The bypass tunnel that a
PLR selects is required to
protect the adjacent
downstream node of the
PLR and the link between
the adjacent downstream
node and the PLR.
FRR Bandwidth(Kbit/s) Forward and Reverse
Tunnels: 10000
Set this parameter
planning.

3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
The QoS configuration is as follows:
Selection
Tunnels: E-LSP
Tunnels: 4
Set this parameter
planning.

Step 4 Create bypass tunnel 1.
1. Refer to Step 3.1 through Step 3.2 to configure the basic attributes of bypass tunnel 1.
Selection
planning.
planning.
planning.
to be created.
Configure As Bypass
Tunnel
Selected This parameter needs to be
selected because the tunnel
is a bypass tunnel.

2. Configure the NE list. On the physical topology, double-click NEs to add them to the NE
list. Then, specify the ingress and egress NEs.
iManager U2000
3-49
Selection
NE3: Egress
node.
node.

3. Click Details to configure details of the tunnel management.
The basic Information is as follows:
Selection
Reverse Tunnel: 4
Set this parameter
planning.

Choose Trail Information > Affinity Information, right-click, and choose Insert
Instance.
The parameters of the affinity object are as follows:
Selection
Enable Affinity Forward and Reverse
Tunnels: Yes
rerouting.
Color(0x) Forward and Reverse
Tunnels: 0
value.
Mask(0x) Forward and Reverse
Tunnels: 0
value.

3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
Choose Trail Information > Route Restriction, right-click, and choose Insert
Instance.
The parameters of route restriction object are as follows:
Selection
10.1.5.1
10.1.3.2
addresses of the NE4-1-
EG16-2(Port-2) and
of the NE4-1-EG16-1
(Port-1) and NE1-4-
EFG2-2(Port-2) ports.
Hop Type Forward and Reverse
Tunnels: Strictly include
to Strictly include, the
addresses.

Choose QoS.Information.
The QoS configuration is as follows:
Selection
Tunnels: E-LSP
Tunnels: 4
Set this parameter
planning.

4. In the tunnel management window, configure the protection interface for a bypass tunnel
after the bypass tunnel 1 is successfully created and its running status is in UP state.
The Bypass attribute is as follows:
Selection
Protect Interface Forward: 4-EFG2-1
Reverse: 1-EG16-1
Set this parameter
planning.

iManager U2000
3-51
5. Refer to Step 4.1 through Step 4.4 to create bypass tunnel 2.
The parameters of bypass tunnel 2 are the same as those of bypass tunnel 2, except the
tunnel names, tunnel IDs, IP addresses and protection interface.
Selection
planning.
Reverse Tunnel: 6
Set this parameter
planning.
10.1.5.1
10.1.4.2
addresses of the NE4-1-
EG16-3(Port-3) and
of the NE4-1-EG16-1
(Port-1) and NE2-1-
EG16-3(Port-3) ports.
Protect Interface Forward: 1-EG16-2
Reverse: 1-EG16-1
Set this parameter
planning.

----End
3.5.3 Configuration Example (IP and LDP Tunnels)
This topic describes a networking diagram and the corresponding example of configuring an IP
tunnel and an LDP tunnel on the network.
Example Description
As shown in Figure 3-13, NE1 receives services transmitted from Node B. Then, the services
are carried in two tunnels, that is, an IP tunnel and an LDP tunnel, between Node B and the
RNC. Specifically, the IP tunnel traverses a third-party IP network and the LDP tunnel traverses
an MPLS network. The services are converged on NE3 and then transmitted to the RNC.
l IP tunnel: NE1-a third-party IP network-NE3.
l LDP tunnel: NE1-an MPLS network-NE3.
In Figure 3-13, NE1 is the OptiX PTN 950 and NE3 is the OptiX PTN 3900. The Figure
3-13 shows the planning of boards and ports on each NE.
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
Node B
RNC
2-EG2-1(Port-1)
1-EX2-1(Port-1)
I P Tunnel
DSLAM
Third-Party
IP Network
MPLS Network
LDP Tunnel
10.0.0.1
4-SHD4-1(Port-1)
10.0.5.1
10.0.0.2
3-EG16-1(Port-1)
10.0.2.1
NE1
NE3
10.0.5.2
10.0.2.2

Service Planning
To transmit services between Node B and the RNC, you need to create an IP tunnel and an LDP
tunnel.
Assume that the IP addresses of the ports of NEs are the same as those listed in Table 3-6 after
the U2000 automatically allocates the IP addresses of ports.
NE LSR ID Port Port IP Address Mask
NE1 1.0.0.1
2-EG2-1(Port-1) 10.0.0.1 255.255.255.252
4-SHD4-1(Bind-1) 10.0.5.1 255.255.255.252
NE3 1.0.0.3
1-EX2-1(Port-1) 10.0.1.2 255.255.255.252
3-EG16-1(Port-1) 10.0.2.1 255.255.255.252

Table 3-7 lists the planned static routes of the NEs.
Table 3-7 Static route
Parameter Value
Station NE1 NE3
Route List ID 1 1
Board Virtual Ethernet 3-EG16
iManager U2000
3-53
Parameter Value
Port 1(VEther-1) 1(Port-1)
Next Hop IP Address 10.0.5.2 10.0.2.2
Destination Node IP
Address
10.0.2.1 10.0.5.1
Destination Node
Subnet Mask
255.255.255.252 255.255.255.252

Table 3-8 lists the planned parameters of IGP-ISIS.
Table 3-8 Planning of the IGP-ISIS
Parameter Value
Station NE1 NE3
Port 2-EG2-1(Port-1) 1-EX2-1(Port-1)
Link Level level-1-2 level-1-2
LSP Retransmission
Interval(s)
5 5
Minimum LSP
Transmission Interval
(ms)
30 30

Table 3-9 lists the planned parameters of MPLS-LDP.
Table 3-9 Planning of the MPLS-LDP
Parameter Value
Station NE1 NE3
Enable LDP 2-EG2-1(Port-1): Enabled 1-EX2-1(Port-1): Enabled
Opposite LSR ID 1.0.0.3 1.0.0.1

Table 3-10 lists the planned parameters of the IP tunnel.
Table 3-10 Planning of the working IP tunnel
Parameter Positive Tunnel Value Reverse Tunnel Value
Tunnel Name Working Tunnel Working Tunnel_Reverse
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
Parameter Positive Tunnel Value Reverse Tunnel Value
Protocol Type IP IP
Tunnel ID 90 91
Out interface 1(VEther-1) 3-EG16-1
Destination IP Address 10.0.2.1 10.0.5.1

Table 3-11 lists the planned parameters of the LDP tunnel.
Table 3-11 Planning of the protection LDP tunnel
Parameter Value
Tunnel Name Protecting Tunnel Protecting Tunnel_Reverse
Protocol Type MPLS MPLS
Signaling Type LDP LDP
NE Role(NE1) Ingress Egress
NE Role(NE3) Egress Ingress
EXP 2 2

This topic describes how to configure the IP tunnel and LDP tunnel.
Prerequisite
Procedure
Step 1 Set LSR IDs.
2. Set LSR ID, Start of Global Label Space and Start of Multicast Label Space. Click
Apply.
iManager U2000
3-55
Selection
network.
planning.

3. In the NE Explorer of NE3, refer to the preceding two steps to set the parameters, such as
the LSR ID.
Selection
network.
planning.

Step 2 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.
2. Click Create to create the static route between NE1 and NE3.
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
Selection
Route List ID 1 Set this parameter
planning.
Board Virtual Ethernet When you configure a static
route on the ATM cards,
you need to set this
parameter to Virtual
Ethernet.
Port 1(VEther-1) When you configure a static
route on the ATM ports,
you need to set the port type
to 1(VEther-1).
Next Hop IP Address 10.0.5.2 Set this parameter
planning.
Destination Node IP
Address
10.0.2.1 Set this parameter
planning.
Destination Node Subnet
Mask
planning.

3. Click Apply. The Operation Result dialog box is displayed indicating that the operation
is successful.
4. Enable the IGP-ISIS protocol of the protection MPLS tunnel. In the NE Explorer, select
NE1 and choose Configuration > Control Plane Configuration > IGP-ISIS
5. Click the Node Configuration tab page. Click New. Configure the related parameters in
the dialog box displayed.
iManager U2000
3-57
Selection
IGP-ISIS Instance ID 1 The value of IGP-ISIS
Instance ID must be one
and only.
Node Level level-1-2 The port can establish both

6. Click the Port Configuration tab and then click New. Click Add in the dialog box
displayed. Then, select 2-EG2-1(Port-1) on the port tab page. Click OK.
Selection
Link Level level-1-2 The port can establish both
LSP Retransmission
Interval(s)
point link, if the local
equipment fails to receive
any response in a period
after transmitting an LSP,
the local equipment
the local equipment
Minimum LSP
30 Specify the minimum delay
between two consecutive
LSPs.

is successful.
8. Choose Session Configuration and click Create. Set Opposite LSR ID to 1.0.0.3 in the
Create LDP Peer Entity dialog box. Click OK.
9. Configure the MPLS-LDP peer for the protection LDP tunnel. Choose Configuration >
Control Plane Configuration > MPLS-LDP Configuration from the Function Tree.
Click Port Configure and set Enable LDP of 2-EG2-1(Port-1) to Enabled.
Selection
Enable LDP 2-EG2-1(Port-1): Enabled Enable the LDP function of
a port.
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)

is successful.
11. In the NE Explorer of NE3, refer to Step 2.1 through Step 2.3 to configure the static routes
for NE3.
Selection
Route List ID 1 Set this parameter
planning.
Board 3-EG16 Set this parameter
planning.
Port 1(Port-1) Set this parameter
planning.
planning.
Destination Node IP
Address
planning.
Destination Node Subnet
Mask
planning.

12. In the NE Explorer of NE3, refer to Step 2.4 through Step 2.7 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.
13. In the NE Explorer of NE3, refer to Step 2.8 through Step 2.10 to configure the peer of
NE3.
Selection
Enable LDP 1-EX2-1(Port-1): Enabled Enable the LDP function of
a port.
Hello Send Interval(s) 10 The same value as the hello
send interval of NE1.
KeepAlive Send Interval(s) 10 The same value as the
keepalive send interval of
NE1.
iManager U2000
3-59
Selection
Opposite LSR ID 1.0.0.1 This parameter indicates
the LSR ID of the peer NE
of the PW. In this example,
this parameter indicates the
LSR ID of NE1.

Step 3 Create an IP tunnel.
2. Configure the basic information about the IP tunnel.
Selection
planning.
Protocol Type IP Set this parameter
planning.
to be created.

3. On the physical topology, double-click NE1 and NE3 and set relevant parameters in the
NE list.
Selection
NE3: Egress
Set this parameter
planning.

4. Click Details to configure details of the IP tunnel.
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
Selection
Reverse Tunnel: 91
Set this parameter
planning.
Out Interface Forward Tunnel: 1
(VEther-1)
Reverse Tunnel: 3-EG16-1
Set this parameter
planning.
Destination IP Address Forward Tunnel: 10.0.2.1
Reverse Tunnel: 10.0.5.1
Set this parameter
planning.

5. Select Deploy and click Apply. In the dialog box displayed, click Close.
NOTE
If you select Deploy, the created tunnel is saved on the U2000 and applied to the corresponding NEs.
By default, Deploy is selected.
Step 4 Create an LDP tunnel.
2. Configure the general information about a tunnel.
Selection
Tunnel Name Protection Tunnel Set this parameter
planning.
planning.
Signaling Type LDP Set this parameter
planning.
to be created.

3. On the physical topology, double-click NE1 and NE3 and set relevant parameters in the
NE list.
Selection
NE3: Egress
Set this parameter
planning.
iManager U2000
3-61

4. Click Details and set EXP of the forward and reverse tunnels to 2.
5. Select Deploy and click Apply. In the dialog box displayed, click Close.
NOTE
If you select Deploy, the created tunnel is saved on the U2000 and applied to the corresponding NEs.
By default, Deploy is selected.
----End
3 Managing Tunnel
iManager U2000
Issue 01 (2010-08-16)
4 Configuring a Service Template
About This Chapter
By using a service template, you can create services more quickly and easily. You can customize
a service template according to actual O&M requirements.
4.1 Creating a Service Template
This topic describes how to create a service template. There are service templates as follows:
VPLS service template, L3VPN service template, PWE3 service template, and RSVP-TE Tunnel
template.
4.2 Creating a Service by Using a Template
This topic describes how to create a service by using a template.
iManager U2000
Operation Guide for PTN End-to-End Management 4 Configuring a Service Template
4-1
4.1 Creating a Service Template
This topic describes how to create a service template. There are service templates as follows:
VPLS service template, L3VPN service template, PWE3 service template, and RSVP-TE Tunnel
template.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 Choose Service > Service Template from the main menu.
Step 3 Click Create and select the required type of the service template from the drop-down list.
Step 4 Set the parameters relevant to the service template.
NOTE
To set the new service template as the default template, select Set as Default Template.
Step 5 Click OK. The service template is created successfully.
Step 6 Optional: In the service template management window, select the new service template, and
click the Configure Template tab to view the details of the template.
Step 7 Optional: In the service template management window, select the new service template, click
Modify to modify the details of the template.
----End
4.2 Creating a Service by Using a Template
This topic describes how to create a service by using a template.
Prerequisite
Context
The following example describes how to create a tunnel service by using an RSVP TE Tunnel
Template.
Procedure
Step 1 Choose Service > Tunnel > Create Tunnel from the main menu.
Step 2 Configure the general information about a tunnel.
1. Set Protocol Type to MPLS and set Signaling Type to RSVP TE.
4 Configuring a Service Template
iManager U2000
Issue 01 (2010-08-16)
2. Click . In the dialog box displayed, select the service template to be used.
3. Click OK. A dialog box is displayed, indicating that the parameters not contained in the
new template may be lost.
4. Click Confirm.
5. Select Create Reverse Tunnel or Configure As Bypass Tunnel as required.
Step 3 Configure the NE list. Select source and sink NEs. In NE List, set the location of an NE in a
tunnel as follows:
You can select an NE by using any of the following three methods:
l Method 1: On the physical topology in the upper right portion, select an NE, right-click, and
choose Add from the shortcut menu.
l Method 2: On the physical topology in the upper right portion, double-click an NE.
l Method 3:
1. Click Add and select NE from the drop-down list.
2. In the dialog box displayed, select an NE and click OK.
Step 4 Select Deploy and click OK.
NOTE
If Deploy is not selected, the tunnel is saved only on the U2000. If Deploy is selected, the tunnel is save
on the U2000 and delivered to corresponding NEs. By default, Deploy is selected.
When Deploy is selected, Enable is selected accordingly. A tunnel on the NE side can be used only when
the tunnel is enabled.
----End
iManager U2000
Operation Guide for PTN End-to-End Management 4 Configuring a Service Template
4-3
5 Viewing a Service Resource
About This Chapter
This topic describes how to view the usage of a service resource.
5.1 Querying Public Resources
This topic describes how to view the details about a service resource. Service resources include
PW IDs, VSI IDs, RDs, RTs, and IP addresses.
5.2 Querying SAI Resources
This topic describes how to view the interface resources bound to a service.
iManager U2000
Operation Guide for PTN End-to-End Management 5 Viewing a Service Resource
5-1
5.1 Querying Public Resources
This topic describes how to view the details about a service resource. Service resources include
PW IDs, VSI IDs, RDs, RTs, and IP addresses.
Procedure
Step 1 Choose Service > Service Resource > Common Resource Management from the main menu.
NOTE
You can set the filter criteria, such as Resource Type and NE Name. In this manner, only the information
meeting the filter criteria is displayed in the query result area.
Step 3 In the query result area, you can view the Resource Type, Resource Value, and Service
Sum information about a resource.
Step 4 After selecting a resource that is already added to a service, you can click the Details tab to view
the details about the resource, such as Resource Value, NE Name, Service Name, Service
Type, Customer, and Service Deployment Status.
Step 5 On the Details tab page, right-click a resource and choose View Service from the shortcut menu.
The service management user interface for the service corresponding to the selected resource is
displayed.
Step 6 Optional: Click Print to set the print parameters and prints the related data on the current user
interface.
Step 7 Optional: Click Save to export all the service resources in the query result area to a file of the
specified format.
NOTE
The file can be saved in .xls, .txt, .html, .csv.
----End
5.2 Querying SAI Resources
This topic describes how to view the interface resources bound to a service.
Procedure
Step 1 Choose Service > Service Resource > SAI from the main menu.
NOTE
You can set the filter criteria, such as Service Type and NE name. In this manner, only the information
meeting the filter criteria is displayed in the query result area.
Step 3 In the query result area, you can view the details about the interface.
5 Viewing a Service Resource
iManager U2000
Issue 01 (2010-08-16)
Step 4 Right-click an interface that is already bound to a service and choose View Service from the
shortcut menu. The service management user interface for the service corresponding to the
selected interface is displayed.
Step 5 Optional: Click Print to set the print parameters and prints the related data on the current user
interface.
Step 6 Optional: Click Save to export all the interface resources in the query result area to a file of the
specified format.
NOTE
The file can be saved in .xls, .txt, .html, .csv.
----End
iManager U2000
Operation Guide for PTN End-to-End Management 5 Viewing a Service Resource
5-3
6 Managing PWE3 Services
About This Chapter
This section describes how to configure PWE3 services.
6.1 Overview of PWE3
This topic describes basic concepts of the PWE3.
6.2 PWE3 Configuration Process
The configuration process of the PWE3 consists of configure the CES services, ATM services,
IP line service and Ethernet services. This section describes the operation tasks for configuring
the services, and relations between the tasks. When configure and managing the PWE3 service,
follow the configuration process.
6.3 Configuration Flow for the PWE3 Service Protection
This topic describes how to easily and fast create protection for a PWE3 service when you
configure the PWE3 service.
6.4 PWE3 Operation Tasks
This topic describes all operation tasks relevant to a PWE3 service.
6.5 PWE3 Service Monitoring
The PWE3 service monitoring enables you to view the service topology, monitor service
performance, and monitor service alarms.
6.6 Managing PWE3 Service Authority
This topic describes how to manage the PWE3 service authority.
6.7 Examples for Configuring PWE3 Services
This topic describes several examples of configuring PWE3 services, including the TDM, ATM,
and Ethernet services.
iManager U2000
Operation Guide for PTN End-to-End Management 6 Managing PWE3 Services
6-1
6.1 Overview of PWE3
This topic describes basic concepts of the PWE3.
6.1.1 Introduction
In a packet switched network (PSN), PWE3 is a Layer 2 service bearing technology that emulates
as faithfully as possible the basic behaviors and characteristics of ATM services, Ethernet
services, low-rate time division multiplexing (TDM) circuit services, and other services. Such
a technology can interconnect the traditional network with PSN network to share resources and
expand the network.
6.1.2 Reference Standards and Protocols
This topic describes the compliant standards and protocols for various technologies used in the
PWE3.
6.1.3 Principle
This topic describes the basic principle and various technologies used to implement the PWE3.
6.1.4 Overview of IP Line
IP line services are private line services provided by the PTN equipment. In the case of IP line
services, IP packets are encapsulated into PWs for transmission.
6.1.5 Principle of IP Line
The PTN equipment supports UNI-NNI IP line services and transports the services in a point-
to-point manner. In addition, the PTN equipment supports dual-homing protection for IP line
services.
6.1.6 The Application of PWE3 Service
This topic describes a typical application of the PWE3.
6.1.1 Introduction
In a packet switched network (PSN), PWE3 is a Layer 2 service bearing technology that emulates
as faithfully as possible the basic behaviors and characteristics of ATM services, Ethernet
services, low-rate time division multiplexing (TDM) circuit services, and other services. Such
a technology can interconnect the traditional network with PSN network to share resources and
expand the network.
Definition
PWE3 is a Layer 2 service bearing technology, mainly used to emulate essential behaviors and
characteristics of services such as ATM, frame relay, Ethernet, low-rate TDM circuit, and
synchronous optical network (SONET)/synchronous digital hierarchy (SDH) as faithfully as
possible in a PSN.
PWE3 is a point-to-point L2 VPN(Virtual Private Network) technology. PWE3 has the following
features: Adding new signaling; reducing cost of signaling; regulating the auto-negotiation mode
of multiple hops; achieving flexible networking diagrams. The PWE3 protocol can reduce packet
exchange, avoid repeated PW creations and deletions caused by network unstabilities.
Objectives
With development of the IP network, the IP network has great compatibility and great capabilities
for expansion, upgrade, and interoperation. The traditional communication network, which has
iManager U2000
Issue 01 (2010-08-16)
poor capabilities for expansion, upgrade, and interoperation, is restricted by the transmission
mode and service type. In addition, newly built networks support few services and are unsuitable
for interoperation management. Hence, during the upgrade and expansion of traditional
communication networks, you should consider whether to build duplicated networks or use
existing or common network resources. PWE3 is a solution that combines traditional
communication networks with the existing packet networks.
PWE3 has certain advantages of MPLS L2VPN. In addition, PWE3 can be used to interconnect
traditional networks with PSNs. Hence, resources can be shared and networks can be expanded.
PWE3.
The reference documents of this feature are as follows:
Document Description Remark
s
RFC3916 Requirements for Pseudo-Wire Emulation Edge-to-
Edge (PWE3)

RFC3985 Pseudo Wire Emulation Edge-to-Edge (PWE3)
Architecture

RFC4446 IANA Allocations for Pseudowire Edge to Edge
Emulation (PWE3)

draft-ietf-pwe3-
control-protocol-17
Pseudo wire Setup and Maintenance using the Label
Distribution Protocol

draft-martini-pwe3-
pw-switching-03
Pseudo Wire Switching
draft-ietf-pwe3-cw-00 PWE3 Control Word for use over an MPLS PSN
draft-ietf-pwe3-
vccv-03
Pseudo Wire Virtual Circuit Connectivity Verification
(VCCV)

draft-ietf-pwe3-
ethernet-encap-10
Encapsulation Methods for Transport of Ethernet Over
MPLS Networks

draft-ietf-pwe3-atm-
encap-11
Encapsulation Methods for Transport of ATM Over
MPLS Networks

draft-ietf-pwe3-cell-
transport-05
PWE3 ATM Transparent Cell Transport Service
RFC 5085 Pseudowire Virtual Circuit Connectivity Verification
(VCCV) A Control Channel for Pseudowires
VCCV of
PWs in
L2TP V3
mode is
not
supporte
d.

iManager U2000
6-3
6.1.3 Principle
This topic describes the basic principle and various technologies used to implement the PWE3.
PWE3 Basic Principle
This topic describes the implementation principle for the PWE3 to carry various Layer 2 services
on the customer edge (CE) side.
Basic Transmission Components of the PWE3
As shown in Figure 6-1, the basic transmission components of the PWE3 network are as follows:
l Virtual link pseudo wire (PW)
l Forwarder
l Tunnels
l PW signaling protocol
Figure 6-1 Basic transmission components of the PWE3
PE1 PE2
CE1
CE2
CE3
CE4
P
VPN1
Site1
VPN2
Site1
VPN1
Site2
VPN2
Site2
MPLS
Network
AC
PW
PW Signal
Tunnel
Forwarder
Forwarder

The VPN1 packet flow from CE1 to CE3 is taken as an example. The basic data flow is as
follows:
l Layer 2 packets are sent to CE1 first, and the packets gain access to PE1 through the link.
l After PE1 receives the packets, the forwarder selects the PWs for forwarding packets.
l PE1 generates two MPLS labels (a private network label and a public network label)
according to the PW forwarding table entries. The private network label is used to identify
the PW, and the public network label is used for a service to traverse over the tunnel to
PE2.
iManager U2000
Issue 01 (2010-08-16)
l The Layer 2 packets reach PE2 through the public network. Then, the system prompts
private network labels (on the P equipment, public network labels are prompted in the last
hop but one).
l The forwarder of PE2 selects the link for forwarding packets, and then forwards the Layer
2 packets to CE3.
PWE3 Network Mode
The PWE3 network can be in single-hop mode or multi-hop mode.
l Single-hop PWE3 network
Single-hop PW indicates that only one PW is available between U-PEs, and the label
switching of the internal label is not required.
Figure 6-2 shows the typical network topology of the single-hop PW.
Figure 6-2 PWE3 single-hop topology
MPLS Network
PE1 PE2 P
PW
CE1 CE2

l Multi-hop PWE3 network in LDP mode
In most cases, the single-hop PW can meet the actual requirement. In the following three
cases, however, the single-hop PW cannot meet the requirement and the multi-hop PW
needs to be used:
Two PEs are not in the same AS domain. In addition, the signaling connection or tunnel
between the two PEs cannot be constructed.
The signaling types on the two PEs are different. For example, one end runs the LDP,
and the other end runs the RSVP.
The access equipment can run the MPLS, but it cannot construct a large number of LDP
sessions. In this case, the user facing provider equipment (UFPE) is used as the U-PE,
and the high-performance S-PE is used as the switching node (similar to the signaling
reflector) of the LDP sessions.
The multi-hop PW indicates that multiple PWs are available between U-PEs. The
forwarding mechanisms of the U-PE in the case of multi-hop forwarding and the U-PE
in the case of single-hop forwarding are the same. In the case of multi-hop forwarding,
the label switching of the PW label should be performed on the S-PE.
Figure 6-3 shows the typical network topology of the multi-hop PW using the LDP as the
signaling.
iManager U2000
6-5
Figure 6-3 PWE3 multi-hop topology
MPLS Network
U-PE1 U-PE2 S-PE1
PW1
CE1 CE2
S-PE2
PW2 PW3

Static PW
The static PW does not use the signaling protocol for parameter negotiation. The information
required by the static PW is manually specified through commands, and the data is transmitted
between PEs through the tunnel.
Dynamic PW
The dynamic PW is a PW constructed through signaling protocol. The U-PE switches the PW
label through the LDP, and bundles the corresponding CE through PW ID. After the tunnel that
connects two PEs is successfully constructed and the label switching and bundling are complete,
if the link of the two PEs is up, a PW is constructed.
The message packets of the dynamic PW consist of:
l Request: Requests for label allocation from the opposite end.
l Mapping: Notifies the opposite end of the label at the local end and determines whether to
contain the status message according to the default signaling action. (The default Martini
mode does not support the status message.)
l Notification: Notifies status to negotiate the PW status, and thus reducing the count of
packets for interaction.
l Withdraw: Contains the relevant label and status to inform the opposite end to cancel the
label.
l Release: As a response to the Withdraw packet, informs the opposite end that sends the
Withdraw packet to cancel the label.
Extension at the PWE3 Control Plane
l Signaling extension
The Notification mode is added to the LDP signaling. In this manner, only status is notified
and the signaling is not cleared unless the configuration is deleted or the signaling protocol
is interrupted. This mode reduces packet interaction and signaling overheads, and is
compatible with the original LDP and Martini modes.
iManager U2000
Issue 01 (2010-08-16)
l Multi-hop extension
The multi-hop PW function is added, which extends the network mode.
The multi-hop PW lowers the requirement on the count of LDP connections of the access
equipment, that is, lowers the overheads of the LDP session of the access nodes.
Multi-hop access nodes meet the PW convergence requirement, which facilitates the
network flexibility and is applicable to different levels (access, convergence, and core).
l TDM interface extension
Supports more telecommunication low-speed TDM interfaces. The functions of TDM
packet sequencing, and clock extraction and synchronization are added through the control
word (CW) and the forwarding plane Real-time Transport Protocol (RTP).
The advantages of the low-speed TDM interfaces are as follows:
The encapsulation type is added to support the encapsulation of low-speed TDMs.
Supports integration of the PSTN, TV, and data networks.
It is a mode to substitute the traditional DDN service.
l Other extensions
Other extensions at the control plane are as follows:
The negotiation mechanism of the fragmentation capability is added to the control plane.
The PW connectivity check, such as the virtual circuit connectivity verification (VCCV)
and PW operation administration and maintenance (OAM), is added, which improves
the quick convergence capability and reliability of the network.
Extension at the PWE3 Data Plane
l Real-time information extension.
l Clock extraction and time synchronization through the Real-time Transport Protocol
(RTP).
l Assurance of the bandwidth, jitter, and delay of telecommunication signals.
l Re-transmission of out-of-order packets.
VCCV
Virtual circuit connectivity verification (VCCV) is a technology that is used to verify and
diagnose the connectivity of a PW forwarding trail.
VCCV is an end-to-end PW fault detection and diagnosis mechanism. That is, the VCCV is the
control channel on which connectivity verification messages are sent between the PW ingress
and egress nodes.
The objective of the VCCV is to verify and further diagnose the connectivity of the PW
forwarding trail.
The VCCV PING is a tool that help you to manually check the connection status of the virtual
circuit. The VCCV PING is achieved through the extended LSP-PING. The VCCV defines a
serial of messages exchanged between PEs to verify the connectivity of the PW. To ensure that
the packets of the VCCV and data packets in the PW pass through the same trail, the VCCV
packets and the PW packets must have the same encapsulation mode and pass through the same
tunnel.
iManager U2000
6-7
Static and Dynamic Hybrid Multi-Hop PW
This topic describes the static and dynamic hybrid multi-hop PW.
Hybrid multi-hop PW refers to a PW with one end being the static PW and the other end being
the dynamic PW (LDP). Either the static PW or the dynamic PW can have multiple hops. The
static and dynamic PWs, however, cannot have multiple hops in interleaved mode.
As shown in Figure 6-4, the PW between U-PE1 and S-PE is a dynamic PW and that between
U-PE2 and S-PE is a static PW.
Figure 6-4 Network of the static and dynamic hybrid multi-hop PW
CE-A CE-B
U-PE1 U-PE2
S-PE P1 P2
D
y
n
a
m
ic
P
W
S
t
a
t
ic
P
W

PW Protection
To implement quick data switching, the PW protection mechanism ensures that services can be
quickly switched to another PW when one PW fails.
PW Redundancy
As shown in Figure 6-5, CE1 is connected to PE1 through a single link. CE2 is connected to
PE2 and PE3 in dual-homing mode.
NOTE
PWs between PE equipment must be created by using the LDP signaling.
l Create a PW between PE1 and PE3. This PW is the working PW.
l Create a PW between PE1 and PE2. This PW is the protection PW.
l Detect faults between CE and PE.
l When the active trail CE2- PE3- PE1- CE1 is faulty, the service traffic can be quickly
switched to the standby trail CE2- PE2- PE1- CE1.
l After the fault on the active trail CE2- PE3- PE1- CE1 is rectified, the service traffic is
switched to the original trail.
iManager U2000
Issue 01 (2010-08-16)
Figure 6-5 PW redundancy protection
W
P
Working PW
PE1
PE2
PE3
CE1
CE2

CE Symmetrical Access Dual-Homing Protection
As shown in Figure 6-6, CE1 is connected to PE1 and PE2 through the dual-homing mode, and
CE1 is connected to PE2 and PE4 through the dual-homing mode.
l Connect CE1 and CE2 to PE.
l Between PE1 and PE3 and between PE2 and PE4, create PWs.
l Trail CE2- PE3- PE1- CE1 and trail CE2- PE4- PE2- CE1 serve as mutual backups for each
other. When a tail is faulty, the service traffic can be quickly switched to the other trail. By
default, use trail CE2- PE3- PE1- CE1 as the working trail.
Figure 6-6 CE symmetrical access dual-homing protection
P
W
P
Working PW
Protection PW
CE1 CE2
PE1
PE2
PE3
PE4

Backup Protection
As shown in Figure 6-7, CE1 is connected to PE1 and CE2 is connected to PE2.
iManager U2000
6-9
l Between PE1 and PE3, create two dynamic PWs.
l The two PWs on trail PE1- PE2 serve as mutual backups. When a trail is faulty, the service
traffic can be quickly switched to the other trail.
Figure 6-7 Backup protection
Protection PW
Working PW
CE1 CE2
PE1 PE2

PW APS Protection
As shown in Figure 6-8, CE1 is connected to PE1 and CE2 is connected to PE2 and PE3.
l Between PE1 and PE2, create a PW.
l Between PE1 and PE3 and between PE2 and PE3, create PWs.
l When trail CE1- PE1- PE2- CE2 is faulty, the service traffic can be quickly switched to
the protection trail CE1- PE1- PE3- PE2- CE2.
Figure 6-8 PW APS protection
W
P
P
Working PW
Protection PW
CE1
CE2
PE1
PE2
PE3

iManager U2000
Issue 01 (2010-08-16)
ATM Cell Transparent Transmission
This topic describes the ATM cell transparent transmission technology.
Definition
ATM cell transparent transmission is a technology that is used to bear ATM cells on the PWE3
virtual circuit.
Objective
The ATM cell transparent transmission uses the PSN network to connect traditional ATM
network resources and emulates traditional ATM services on the PSN network. In this case,
traditional ATM network services are emulated to the maximum when traversing the PSN
network. Therefore, end users can rarely sense any difference and the existing investment of
customers and operators are fully utilized in the network integration and construction.
Implementation of the ATM Cell Transparent Transmission
The objective of the PWE3 is to use the PSN network to connect traditional network resources
(ATM/FR/LAN) and provide the emulation of the traditional services on the PSN network. In
this case, traditional network services are emulated to the maximum when traversing the PSN
network. Therefore, end users can rarely sense any difference and the existing investment of
customers and operators are fully utilized in the network integration and construction.
By creating P2P tunnels, bearing data packets, cells, and bit streams, Layer 2 emulation service
on the PSN traverses the public or private PSN. The original services are emulated to the
maximum between two PEs that a PW connects.
l Port-based ATM cell transparent transmission
In this mode, the connection between two remote ATM ports is emulated.
The port-based ATM cell transparent transmission can be classified into port-based remote
ATM cell transparent transmission and port-based local ATM cell transparent transmission.
l ATM cell transparent transmission in 1-to-1 virtual circuit connection (VCC) mode
In this mode, a PW bears an ATM VCC cell. This mode supports all ATM adaptation layer
(AAL) types. Because a PW bears only one ATM VCC cell, the tunnel packet does not
contain the values of virtual path identifier (VPI) or virtual channel identifier (VCI).
In addition, the permanent virtual circuits (PVCs) for the PEs are mapped through the PW,
that is, the MPLS PW functions as the ATM switch to support the VPI/VCI switching
without configuring the switching relation on the PE. The ATM cell transparent
transmission in 1-to-1 VCC mode can be classified into remote ATM cell transparent
transmission in 1-to-1 VCC mode and local ATM cell transparent transmission in 1-to-1
VCC mode.
l ATM cell transparent transmission in N-to-1 VCC mode
In this mode, a PW bears multiple ATM VCC cells. This mode supports all AAL types.
Because a PW bears multiple ATM VCC cells, the tunnel packet contains the values of
VPI and VCI.
This encapsulation mode supports the function of mapping multiple VCs in the same ATM
sub-interface to a PW, and does not support the function of mapping multiple VCs in
different ATM interfaces to a PW or the function of mapping multiple inter-board VCs to
a PW.
iManager U2000
6-11
The ATM cell transparent transmission in N-to-1 VCC mode can be classified into remote
ATM cell transparent transmission in N-to-1 VCC mode and local ATM cell transparent
transmission in N-to-1 VCC mode.
l ATM cell transparent transmission in 1-to-1 virtual path connection (VPC) mode
In this mode, a PW bears an ATM VPC cell. This mode supports all AAL types. Compared
with the ATM cell transparent transmission in 1-to-1 VCC mode, the tunnel packet of this
mode contains only the value of VCI. The output equipment then determines the destination
CE based on the value of VCI.
Because a PW bears only one ATM VPC cell, the PVCs for the PEs are mapped through
the PW, that is, the MPLS PW functions as the ATM switch to support the VPI switching
without configuring the switching relation on the PE.
The ATM cell transparent transmission in 1-to-1 VPC mode can be classified into remote
ATM cell transparent transmission in 1-to-1 VPC mode and local ATM cell transparent
transmission in 1-to-1 VPC mode.
l ATM cell transparent transmission in N-to-1 VPC mode
In this mode, a PW bears multiple ATM VPC cells. This mode supports all AAL types.
Because a PW bears multiple ATM VPC cells, the tunnel packet contains the value of VPI
and VCI. The encapsulation modes of the ATM cell transparent transmission in N-to-1
VPC and N-to-1 VCC modes are the same.
The ATM cell transparent transmission in N-to-1 VPC mode can be classified into remote
ATM cell transparent transmission in N-to-1 VPC mode and local ATM cell transparent
transmission in N-to-1 VPC mode.
Encapsulation Modes of the ATM Cell Transparent Transmission
The ATM cell transparent transmission covers the following transparent transmission services:
l PVC-based transparent transmission service
l Permanent virtual path (PVP)-based transparent transmission service
l Interface-based transparent transmission service
The encapsulation modes of the ATM cell transparent transmission are as follows:
l 1-to-1
l N-to-1
The ATM cell transparent transmission has the following transparent transmission modes:
l Cell
l Frame
Table 6-1 describes the features of the ATM cell transparent transmission services of different
levels.
iManager U2000
Issue 01 (2010-08-16)
Table 6-1 Features of the ATM cell transparent transmission services
Encapsulati
on Mode
Transpa
rent
Transmi
ssion
Mode
AAL Type Supported
Connection
Type
Encapsulation Method
N-to-1 VCC Cell All AALs VC Contains the VPI and VCI.
The control word (CW) is
optional. Supports the VPI/
VCI switching.
1-to-1 VCC Cell All AALs VC Not contain the VPI or VCI.
The CW is mandatory.
Supports the VPI/VCI
switching.
N-to-1 VPC Cell All AALs VP Contains the VPI and VCI.
The CW is optional.
1-to-1 VPC Cell All AALs VP Contains the VPI and not
contain the VCI. The CW is
mandatory.
Interface
transparent
transmission
Cell All AALs Interface Contains the VPI and VCI.
The CW is optional.

Table 6-2 describes the applicable scenarios of various connection types.
Table 6-2 Applicable scenarios of various connection types
Connection Type Applicable Scenario
VCC cell transparent
transmission
Virtual channel connection, which is a basic unit on the ATM
network.
Applicable to transmission of various ATM network services.
VPC cell transparent
transmission
Virtual path connection, a group of VCCs with the same destination.
Applicable to transmission of various ATM network services,
especially when multiple services with the same destination exist in
the transmission direction. The VPC cell transparent transmission is
quicker and easier for management and configuration than VCC cell
transparent transmission.
Whole port
transparent
transmission
Applicable to the scenario that the VP and VC do not need to be
processed and the equipment functions an ATM transmission private
line.

Table 6-3 describes the comparison between 1-to-1 and N-to-1 modes.
iManager U2000
6-13
Table 6-3 Comparison between 1-to-1 and N-to-1 modes
Mode Description Applicable Scope Difference
1-to-1 A VCC or VPC maps one PW. All AAL types The VPI and VCI are not
contained.
N-to-1 Multiple VCCs or VPCs map
one PW. (N >= 1)
All AAL types The VPI and VCI must
be contained in the
encapsulation regardless
whether N = 1 or N > 1.

Service Demarcation Tag
This topic describes the basic information about service demarcation tags and implementation
principles.
Packet Encapsulation on an AC
Packet encapsulation mode on an AC is determined by the user access mode. User access modes
can be VLAN access and Ethernet access. Each user access mode is described as follows:
l VLAN access: In VLAN access mode, the header of each Ethernet frame sent between CEs
and PEs carries a VLAN tag. This tag is a service delimiter that is used to identify users in
an ISP network. It is called provider-tag (P-tag).
l Ethernet access: In Ethernet access mode, the header of each Ethernet frame sent between
CEs and PEs does not carry any P-tag. If the frame header carries a VLAN tag, the VLAN
tag is the internal VLAN tag of the user packet, and is called user-tag (U-tag). The U-tag
is carried in a packet before the packet is sent to a CE and is thus not added by the CE. The
U-tag is used by the CE to identify which VLAN the packet belongs to, and is meaningless
to PEs.
Packet Encapsulation on a PW
Packet encapsulation modes on a PW can be Raw mode and Tagged mode, as shown follows:
l Raw mode
The P-tag is not transmitted on the PW. If a PE receives the packet with a P-tag from a CE,
the PE strips the P-tag, adds double MPLS labels (outer label and inner label) to the packet,
and then forwards the packet. If a PE receives the packet without a P-tag from a CE, the
PE directly adds double MPLS labels to the packet, and then forwards the packet. If a PE
sends a packet to a CE, the PE adds or does not add the P-tag to the packet as required, and
then forwards the packet to the CE. Note that the PE is not allowed to rewrite or remove
any existing tag.
l Tagged mode
The frame sent to a PW must carry the P-tag. If a PE receives the packet with a P-tag from
a CE, the PE directly adds double MPLS labels to the packet without stripping the P-tag,
and then forwards the packet; if a PE receives the packet without a P-tag from a CE, the
PE adds a null tag and double MPLS labels to the packet, and then forwards the packet. If
a PE sends a packet to a CE, the PE rewrites, removes, or preserves the service delimiter
of the packet as required, and then forwards the packet to the CE.
iManager U2000
Issue 01 (2010-08-16)
Service Demarcation Tag
After you set the access port of an Ethernet service to the C-aware tag or S-aware tag, at least
one C-VLAN tag or S-VLAN tag is added to the user packet that is transmitted through the
access port. Then, you can set a service demarcation tag to identify the access mode of the user
packet and the method of handling the outermost C-VLAN tag or S-VLAN tag of the user packet
during packet forwarding.
l User: Services gain access to the AC in Ethernet access mode. The outermost C-VLAN
tag or S-VLAN tag of a user packet functions as the user VLAN tag (U-TAG) for the
forwarding of the user packet.
l Service: Services gain access to the AC in VLAN access mode. The outermost C-VLAN
tag or S-VLAN tag of a user packet functions as the service VLAN tag (P-TAG) and is not
involved in the forwarding of the user packet.
Application of the Service Demarcation Tag: Ethernet Access Mode - Raw
Figure 6-9 Ethernet raw mode (with user VLAN tags)
PE1
AC
PW
AC
IP
Header
Data
L2
Header
IP
Header
Data
User
Vlan Tag
L2
Header
VC
Label
Tunnel
Label
L2
Header
PE2
CE1
CE2
IP
Header
Data
L2
Header
User
Vlan Tag
User
Vlan Tag

As shown in Figure 6-9, when you set the service demarcation tag to User, the AC adopts the
Ethernet encapsulation mode and the PW adopts the raw mode. Therefore, packets transmitted
from the CE to the PE contains the user VLAN tags (U-TAGs) but no service VLAN tags (P-
TAGs).
iManager U2000
6-15
Interaction of packets with U-TAGs in the Ethernet raw mode is described as follows:
1. CE1 transmits packets with Layer 2 encapsulation to PE1. The packets contains U-TAGs
but no P-TAGs.
2. When PE1 receives the packets that contain U-TAGs but no P-TAGs, PE1 considers the
U-TAGs as user data without processing them because the U-TAGs are useless to PE1.
3. When PE1 receives the packets that contain P-TAGs but no U-TAGs, PE1 deletes the P-
TAGs from the packets because PWs require raw encapsulation and frames transmitted in
the PWs cannot contain P-TAGs.
4. According to the routing table, PE1 selects tunnels and PWs for the packets.
5. According to the selected tunnels and PWs, PE1 directly adds two types of MPLS tags
(outer tunnel tags and inner VC tags) to the packets, performs Layer 2 encapsulation, and
then forwards the packets.
6. PE2 receives the packets from PE1 and decapsulates the packets. Specifically, PE2 strips
the Layer 2 encapsulation and the two MPLS tags from the packets.
7. PE2 transmits the decapsulated Layer 2 packets from CE1 to CE2. The packets contain U-
TAGs but no P-TAGs.
Application of the Service Demarcation Tag: Ethernet Access Mode - Tagged
Figure 6-10 Ethernet tagged mode (with user VLAN tags)
PE1
AC
PW
AC
IP
Header
Data
L2
Header
IP
Header
Data
User
Vlan Tag
L2
Header
VC
Label
Tunnel
Label
L2
Header
PE2
CE1
CE2
IP
Header
Data
L2
Header
User
Vlan Tag
User
Vlan Tag
Service
Vlan Tag

iManager U2000
Issue 01 (2010-08-16)
As shown in Figure 6-9, when you set the service demarcation tag to User, the AC adopts the
Ethernet encapsulation mode and the PW adopts the tagged mode. Therefore, packets transmitted
from the CE to the PE contains the user VLAN tags (U-TAGs) but no service VLAN tags (P-
TAGs).
Interaction of packets with U-TAGs in the Ethernet raw mode is described as follows:
but no P-TAGs.
2. When PE1 receives the packets that contain U-TAGs but no P-TAGs, PE1 considers the
U-TAGs as user data without processing them because the U-TAGs are useless to PE1.
3. When PE1 receives the packets that contain no P-TAGs, PE1 adds the P-TAGs in the
packets because PWs require tagged encapsulation and frames transmitted in the PWs must
contain P-TAGs.
the Layer 2 encapsulation and the two MPLS tags from the packets and then adds the P-
TAGs that is deleted by PE1 to the packets.
7. PE2 transmits the decapsulated Layer 2 packets from CE1 to CE2. The packets contain U-
TAGs but no P-TAGs.
iManager U2000
6-17
Application of the Service Demarcation Tag: VLAN Access Mode - Raw
Figure 6-11 VLAN raw mode (with service VLAN tags)
PE1
AC
PW
AC
IP
Header
Data
L2
Header
IP
Header
Data
L2
Header
VC
Label
Tunnel
Label
L2
Header
PE2
CE1
CE2
Service
Vlan Tag
IP
Header
Data
L2
Header
Service
Vlan Tag

As shown in Figure 6-9, when you set the service demarcation tag to Service, the AC adopts
the VLAN encapsulation mode and the PW adopts the raw mode. Therefore, packets transmitted
from the CE to the PE contains the service VLAN tags (P-TAGs) but no user VLAN tags (U-
TAGs).
Interaction of packets with U-TAGs in the VLAN raw mode is described as follows:
1. CE1 transmits packets with Layer 2 encapsulation to PE1. The packets contains P-TAGs
but no U-TAGs.
2. When PE1 receives the packets that contain P-TAGs but no U-TAGs, PE1 deletes the P-
TAGs from the packets because PWs require raw encapsulation and frames transmitted in
the PWs cannot contain P-TAGs.
the Layer 2 encapsulation and the two MPLS tags from the packets and then adds the P-
TAGs that is deleted by PE1 to the packets.
iManager U2000
Issue 01 (2010-08-16)
6. PE2 transmits the decapsulated Layer 2 packets from CE1 to CE2. The packets contain P-
TAGs but no U-TAGs.
Application of the Service Demarcation Tag: VLAN Access Mode - Tagged
Figure 6-12 VLAN tagged mode (with service VLAN tags)
PE1
AC
PW
AC
IP
Header
Data
L2
Header
IP
Header
Data
L2
Header
VC
Label
Tunnel
Label
L2
Header
PE2
CE1
CE2
Service
Vlan Tag
IP
Header
Data
L2
Header
Service
Vlan Tag
Service
Vlan Tag

As shown in Figure 6-9, when you set the service demarcation tag to Service, the AC adopts
the VLAN encapsulation mode and the PW adopts the tagged mode. Therefore, packets
transmitted from the CE to the PE contains the service VLAN tags (P-TAGs) but no user VLAN
tags (U-TAGs).
Interaction of packets with P-TAGs in the VLAN tagged mode is described as follows:
but no P-TAGs.
2. When PE1 receives the packets that contain P-TAGs but no U-TAGs, PE1 do nothing with
the P-TAGs in the packets because PWs require tagged encapsulation and frames
transmitted in the PWs must contain P-TAGs.
iManager U2000
6-19
the Layer 2 encapsulation and the two MPLS tags from the packets.
6. PE2 transmits the decapsulated Layer 2 packets from CE1 to CE2. The packets contain P-
TAGs but no U-TAGs.
6.1.4 Overview of IP Line
IP line services are private line services provided by the PTN equipment. In the case of IP line
services, IP packets are encapsulated into PWs for transmission.
Feature Overview
With the growth of wireless networks, the number of base stations that support IP interfaces is
greatly increased, and therefore mobile backhaul networks need to access base station services
through IP packets.
If services are accessed through a traditional L3VPN solution, the restrictions are as follows:
l The access equipment at the edge of a backhaul network must have strong routing
capability. This increases the cost of the access equipment.
l An L3VPN network relies on dynamic routing protocols, and therefore networking is
complex and the protection mechanism cannot satisfy network requirements.
On a mobile backhaul network, the trail between a base station and an RNC is fixed. Therefore,
if you create IP line services between the base station and RNC, the services can fully satisfy
service bearing requirements. In the case of IP line services, IP packets are encapsulated into
PWs. In this manner, IP services from base station are accessed. In addition, features of private
line services such as simple networking, easy management, and complete protection are
maintained.
Networking
As shown in Figure 6-13, an IP line service is created between the OptiX PTN 910/950 and
OptiX PTN 1900/3900/3900-8 for each base station.
The OptiX PTN 910/950 encapsulates IP packets from base stations into a PW, and sends the
PW over an IP line to the OptiX PTN 1900/3900/3900-8. The OptiX PTN 1900/3900/3900-8
decapsulates the packets and sends the packets to an RNC. In this manner, UNI-NNI service
transmission is implemented.
Figure 6-13 Deployment of IP line services
OptiX PTN 3900/
OptiX PTN 1900
OptiX PTN 910/950
RNC
NodeB
IP Line
IP Line
IP Line
iManager U2000
Issue 01 (2010-08-16)

NOTE
IP line services for PTN equipment support the DHCP relay function. That is, a base station can obtain its
IP address through DHCP.
A complete protection mechanism for IP line services on PTN equipment is available. For details,
see Dual-Homing Protection for IP Line Services.
6.1.5 Principle of IP Line
The PTN equipment supports UNI-NNI IP line services and transports the services in a point-
to-point manner. In addition, the PTN equipment supports dual-homing protection for IP line
services.
Implementation Principle
The IP line feature is based on the MPLS technology. In the case of IP line, the accessed IP
packets are encapsulated into PWs, and then the packets are transported in point-to-point manner.
The PTN equipment supports UNI-NNI IP line services. Figure 6-14 shows the service
encapsulation process.
Figure 6-14 Encapsulation process of IP line services
A B
RNC
IP Line
IP
MPLS Label
PW Label
Ethernet
IP
Ethernet
IP
Ethernet
NodeB
OptiX PTN
910/950
OptiX PTN
1900/3900

The encapsulation process is as follows:
l Equipment A encapsulates the packets from the base station into a PW, and then sends the
packets to equipment B.
l After terminating the PW, equipment B transmits the packets to an RNC.
iManager U2000
6-21
Dual-Homing Protection for IP Line Services
The IP line feature implements dual-homing protection for active and standby routes through
PW OAM.
Normal Running
As shown in Figure 6-15, nodes A and B are connected through PW1. Nodes A and C are
connected through PW2. PW OAM is enabled for PW1 and PW2 to detect PW faults.
In normal cases, packets are sent to node B over PW1 and then to the RNC.
Figure 6-15 Dual-homing protection for IP line services
OptiX PTN 3900/
OptiX PTN 1900
OptiX PTN 910/950
RNC
NodeB
PW1
PW2
Service Route
A
B
C

Equipment Fault
Figure 6-16 shows the situation where switching occurs when node B is faulty.
Figure 6-16 Dual-homing protection switching for IP line services in case of an equipment fault
OptiX PTN 3900/
OptiX PTN 1900
OptiX PTN 910/950
RNC
NodeB
PW1
PW2
Service Route
A
B
C
PW1
PW2
A
B
C
iManager U2000
Issue 01 (2010-08-16)

The switching process is as follows:
l When node B is faulty, node A detects the fault through PW OAM, and then node A switches
to PW2.
l Node C detects the fault of node B through the routing protocol, and then node C updates
the route information and accepts the packets sent by node A.
l The route of services from NodeB changes to A-C-RNC.
Link Fault
Figure 6-17 shows the situation where switching occurs when the link between nodes A and B
is faulty.
Figure 6-17 Dual-homing protection switching for IP line services in case of a link fault
OptiX PTN 3900/
OptiX PTN 1900
OptiX PTN 910/950
RNC
NodeB
PW1
PW2
Service Route
A
B
C
PW1
PW2
A
B
C

The switching process is as follows:
l Node A detects that PW1 is faulty through PW OAM, and therefore node A switches
services to PW2.
l Through the routing protocol, node B updates route information and accepts the packets
sent by node C.
l The route of services from NodeB changes to A-C-B-RNC.
To prevent service interruption over the link between node B and the RNC or between node C
and the RNC, you can configure VRRP protection for the RNC. For details on VRRP, see VRRP.
iManager U2000
6-23
6.1.6 The Application of PWE3 Service
This topic describes a typical application of the PWE3.
As an end-to-end Layer 2 service transmission technology, the PWE3 provides end-to-end
virtual emulation links on edges of packet switched networks (PSNs) for transmitting various
services (ATM, Ethernet, and CES) on PSN networks. Such a technology can interconnect the
traditional network and PSN to share resources and expand the network.
Figure 6-18 Application of the PWE3
BTS
RNC
PE
PE
PE
Node B
CE
CE
AC
AC
PW1
PW2
PW3
CE
CE
CE
BSC
BITS
E1 interface
IMA E1
interface
FE interface
NMS
CE

Figure 6-18 shows a PWE3 single-hop mobile carrier network. On this network, the following
types of services are transmitted:
l BTS is connected to the PSN network through the E1 interface and TDM signals are
transmitted to the BSC by using CES services.
l Node B is connected to the PSN network through the IMA E1 interface and ATM cells are
transmitted to the RNC by using ATM services.
l Node B is connected to the PSN network through the FE interface and Ethernet packets are
transmitted to the NMS by using Ethernet services.
iManager U2000
Issue 01 (2010-08-16)
All the preceding services are emulated by using the PWE3 technology and transmitted on PSN
networks. By using the PWE3 technology, carriers can smoothly migrate original access schemes
to PSN networks. This helps to reduce repeated network constructions and lower OPEX.
6.2 PWE3 Configuration Process
The configuration process of the PWE3 consists of configure the CES services, ATM services,
IP line service and Ethernet services. This section describes the operation tasks for configuring
the services, and relations between the tasks. When configure and managing the PWE3 service,
follow the configuration process.
CES Service Configuration Process
Figure 6-19 shows the recommended configuration process for configuring and managing a
CES service.
Figure 6-19 CES service configuration process
Configure the network-
side interface
Start
Required
Optional
End
Set the NE LSR ID
Configure Control Plane
Configure Tunnel
Configure CES Service
Create a Network

Table 6-4 Tasks for configuring a CES service
Operation Description
1. Create a network Complete creating the NE, configure the NE data, and creating fibers.
2. Set the NE LSR
ID
Specifies the LSR ID for each NE that a service traverses and the start
value of the global label space. Each LSR ID is unique on a network.
iManager U2000
6-25
3. Configure the
network-side
interface
Set the basic attributes and Layer 3 attributes (such as tunnel enabling
status and IP address) for the interface to bear tunnels.
4. Configure
Control Plane
Set the associated protocol parameters of the control plane for creating
tunnels.
l To create the static MPLS tunnel to bear the CES service, you do
not need to set the associated parameters of the control plane.
l To create the dynamic MPLS tunnel to bear the CES service, you
need to set the following parameters:
1. IGP-ISIS protocol parameters
2. MPLS-RSVP protocol parameters
To create the dynamic PW to bear services, you need to set the IGP-
ISIS and MPLS-LDP protocol parameters.
l To create the IP tunnel or GRE tunnel to bear the CES service, you
need to add a static route.
5. Configure Tunnel The tunnel is used to bear services.
l In the case of the static MPLS tunnel, you can create the tunnel in
either NE or trail mode. Select the signaling type as static and set
the relevant information about the tunnel, including the tunnel ID,
service name, ingress node, egress node, and transit node.
l In the case of the dynamic MPLS tunnel, you need to select the
signaling type as dynamic and set the relevant information about the
tunnel, including service name, and sink and source nodes of the
tunnel.
l In the case of the IP tunnel or GRE tunnel, set the source board,
source port, and IP address of the sink port.
6. Configure the
service interface
Use the CD1 board or tributary card to access the base station services.
7. Configure CES
Service
1. Create the CES service, including setting the service ID and service
name.
2. Set the source and sink information, including setting the board and
channel.
3. Configure the PW, including setting the PW type, label, and tunnel
type.
4. Configure the advanced attributes, including setting the jitter buffer
time, packet loading time, and clock mode.

ATM Service Configuration Process
Figure 6-20 shows the flowchart for configuring an ATM service. For details of each step, see
the relevant section.
iManager U2000
Issue 01 (2010-08-16)
Figure 6-20 ATM service configuration process
Create Network
Configure the ATM
Interface
Configure the control
plane
Configure the UNIs-
NNI ATM service
Start
Required
End
Configure the ATM
Policy
Configure Tunnel
Optional
Configure the
network-side interface

Table 6-5 Tasks for configuring an ATM service
1. Create Network Complete creating the NE, configure the NE data, and creating fibers.
2. Configure the
LSR ID
3. Configure the
network-side
interface
iManager U2000
6-27
4. Configure the
control plane
tunnels.
l To create the static MPLS tunnel to bear the ATM service, you do not
need to set the associated parameters of the control plane.
l To create the dynamic MPLS tunnel to bear the ATM service, you
To create the dynamic PW to bear the service, you need to set the IGP-
l To create the IP tunnel or GRE tunnel to bear the ATM service, you
5. Configure
Tunnel
The tunnel is used to bear services.
either NE or trail mode. Select the signaling type as static and set the
relevant information about the tunnel, including the tunnel ID, service
name, ingress node, egress node, and transit node.
tunnel.
l In the case of the IP tunnel or GRE tunnel, set the source board, source
port, and IP address of the sink port.
6. Configure the
ATM Policy
The ATM policy is used to perform the traffic management on the ATM
service.
7. Configure the
ATM interface
The ATM interface is used to access the base station services.
8. Configure the
UNIs-NNI ATM
service
1. Create the ATM service, including setting the service ID and service
name, and selecting the service type and connection type.
2. Configure the connection, including setting the source information,
PW ID, sink information, and policy.
type.
4. Configure the CoS mapping and CoS policy of the PW.

E-Line Service Configuration Process
Figure 6-21 shows the flowchart for configuring an E-Line service.
iManager U2000
Issue 01 (2010-08-16)
Figure 6-21 E-Line service configuration process
Create Network
Configure the Control
Plane
Configure the QoS
Policy
Start
Required
Optional
End
Configure Tunnel
Configure the
network-side
Interfaces
Configure the user-
side Interfaces
Configure the UNI-
NNI E-Line Service
Carried by the PW
in the per-trail mode

Table 6-6 Tasks for configuring an E-Line service
1. Create Network Complete creating the NE, configure the NE data, creating fibers, and
configure clocks.
2. Configure the
LSR ID
3. Configure the
network-side
Interface
iManager U2000
6-29
4. Configure the
Control Plane
tunnels.
l To create the static MPLS tunnel to bear the E-Line service, you do
l To create the dynamic MPLS tunnel to bear the E-Line service, you
l To create the IP tunnel or GRE tunnel to bear the E-Line service, you
5. Configure
Tunnel
either NE or trail mode. Select the signaling type as static and set the
relevant information about the tunnel, including the tunnel ID, service
name, ingress node, egress node, and transit node.
tunnel.
6. Configure the
QoS Policy
The QoS policy is used to perform the traffic management on the E-Line
service.
7. Configure the
user-side
Interface
The user-side interface is used to access the base station services.
8. Configure the
UNI-NNI E-Line
Service Carried
by the PW in the
per-trail mode
1. Create the E-Line service, including setting the service ID and service
name, and selecting the service type and bearer type.
type.
3. Configure the QoS, including setting the UNI and QoS of the PW.

IP Line Service Configuration Flow
Figure 6-22 shows the recommended flow for configuring an IP line service.
iManager U2000
Issue 01 (2010-08-16)
Figure 6-22 Flow of configuring an IP line service
Create a network
Configure interfaces
Configure an IP line
service
Configure a QoS
policy
Start
Mandatory
Optional
End
Configure a Layer 3
virtual interface
Create a static MPLS
tunnel

Table 6-7 Operation tasks for configuring an IP line service
Task Remarks
1. Create a network. Create NEs and fibers, and configure NE data.
2. Configure
interface.
l Configure a UNI port, which is used from service access from a base
station.
l Configure an NNI port. That is, set the general attributes and Layer
3 attributes (such as Enable Tunnel and IP Address) for the port
so that the port can carry tunnels.
3. Configure a Layer
3 virtual interface.
Configure a Layer 3 virtual interface as the sink port for the IP line
service.
4. Configure a static
MPLS tunnel.
An IP line service can be carried only by a static MPLS tunnel.
l You can create a static MPLS tunnel site by site or end to end. When
creating a static MPLS tunnel, you need to set the signaling type to
static and specify the service name, ingress node, egress node, and
transit node.
iManager U2000
6-31
Task Remarks
5. Configure an IP
line service.
1. Create an IP line service. That is, set the service ID and specify the
service name.
2. Set the source and sink. That is, choose boards and a tunnel.
3. Configure a PW. That is, set the PW type, PW label, and tunnel type.
4. Set advanced attributes. That is, set parameters such as QoS for the
UNI port.

6.3 Configuration Flow for the PWE3 Service Protection
This topic describes how to easily and fast create protection for a PWE3 service when you
configure the PWE3 service.
Protection types for PWE3 services are as follows: PW redundancy protection, Dual-Homing
protection for CEs of symmetric access, PW backup protection, and PW APS protection.
PW Redundancy Protection
The PW redundancy protection can be implemented either in the single source and dual sink
mode or in the dual source and single sink mode. To configure the single source and dual sink
shown in Figure 6-23, you need to set PE1 to the source, PE3 the working sink, and PE2 the
protection sink by using the NMS. To configure the dual source and single sink shown in Figure
6-24, you need to set PE3 to the sink, PE1 the working source, and PE2 the protection source
by using the NMS.
Figure 6-23 Single source and dual sink
W
P
Source
Working PW
Protection PW
Working Sink
Protection Sink
PE1
PE2
PE3
CE
CE

iManager U2000
Issue 01 (2010-08-16)
Figure 6-24 Dual source and single sink
W
P
Sink
Working PW
Protection PW
Working Source
Protection Source
CE
CE
PE2
PE1
PE3

Figure 6-25 shows the process of configuring the PW redundancy protection. In the PWE3
service creation window, set Protection Type to PW redundancy. After the protection is
configured, proceed with the configuration of other parameters. A PWE3 service with the dual-
homing protection is created successfully.
Figure 6-25 Process of configuring PW redundancy dual-homing protection
Select Protection Type
PW Redundancy Protection
Start
End
Select single source and dual
sink or dual source and single
sink
Single source and
dual sink
Dual source and
single sink
Configure Source
Configure Working
Sink
Configure Protection
Sink
Configure Sink
Configure Working
Source
Source

iManager U2000
6-33
Dual-Homing Protection for CEs Symmetric Access
To configure the dual-Homing protection for CEs symmetric access shown in Figure 6-26, you
need to set PE1 as the working source, PE3 the working sink, PE2 the protection source, and
PE4 the protection sink.
Figure 6-26 Dual-Homing protection for CEs symmetric access
W
P
Working PW
Protection PW
Working Source
Protection Source
Working Sink
Protection Sink
CE CE
PE1
PE2
PE3
PE4

Figure 6-27 shows the process of configuring the dual-Homing protection for CEs symmetric
access. In the PWE3 service creation window, set Protection Type to Dual-Homing protection
for CEs symmetric access. After the protection is configured, proceed with the configuration
of other parameters. A PWE3 service with the dual-homing protection is created successfully.
iManager U2000
Issue 01 (2010-08-16)
Figure 6-27 Process of configuring the dual-Homing protection for CEs symmetric access
Dual-Homing Protection
for CEs of Asymmetric
Access
End
Configure Working
Source
Configure Working Sink
Source
Sink
Start

PW Backup Protection
To configure the PW backup protection shown in Figure 6-28, you need to set PE1 as the FRR
source and PE2 the FRR sink.
Figure 6-28 PW Backup Protection
Protection PW
Source
Sink
Working PW
CE CE
PE1 PE2

Figure 6-29 shows the process of configuring the PW backup protection. In the PWE3 service
creation window, set Protection Type to PW backup protection. After the protection is
configured, proceed with the configuration of other parameters. A PWE3 service with the PW
backup protection is created successfully.
iManager U2000
6-35
Figure 6-29 Process of configuring the PW backup protection
PW Backup Protection
End
Configure Source
Configure Sink
Start
PW APS Protection
The PW APS protection can be implemented either in the single source and dual sink mode or
in the dual source and single sink mode. To configure the single source and dual sink shown in
Figure 6-30, you need to set PE1 as the source, PE2 the working sink, and PE3 the protection
sink. To configure the dual source and single sink shown in Figure 6-31, you need to set PE1
as the working source, PE2 the sink, and PE3 the protection source.
Figure 6-30 Single source and dual sink
W
P
Source
Working Sink
Protection Sink
P
Working PW
Protection PW
CE
CE
PE1
PE2
PE3

iManager U2000
Issue 01 (2010-08-16)
Figure 6-31 Dual source and single sink
W
P
Sink
Working PW
Protection PW
Working Source
Protection Source
P
CE
CE
PE1
PE2
PE3

Figure 6-32 shows the process of configuring the PW APS protection. In the PWE3 service
creation window, set Protection Type to PW APS protection. After the protection is
configured, proceed with the configuration of other parameters. A PWE3 service with the PW
APS protection is created successfully.
Figure 6-32 Process of configuring the PW APS protection
PW APS Protection
Start
Select single source
and dual sink or dual
source and single sink
End
Single source and
dual sink
Dual source and
single sink
Configure Source
Configure Working
Sink
Sink
Configure Sink
Configure Working
Source
Source
iManager U2000
6-37
6.4 PWE3 Operation Tasks
This topic describes all operation tasks relevant to a PWE3 service.
6.4.1 Creating a CES Service
This topic describes how to create a CES service. You can create a CES PWE3 service tunnel
for transmitting TDM signals in trail configuration mode. By using the trail configuration mode,
you can directly configure the source and sink nodes of a CES service and the PW attributes on
the GUI of the U2000. In this manner, the CES service can be created quickly.
6.4.2 Creating an ETH Service
This topic describes how to create an ETH service. The service is connected to the user side,
and transmitted to one PW at the network side. In this manner, user data can be transparently
transmitted in a point-to-point manner. By using the trail configuration mode, you can directly
configure the source and sink nodes of an ETH service and the PW attributes on the GUI of the
U2000. In this manner, the ETH service can be created quickly.
6.4.3 Creating an ATM Service
This topic describes how to create an ATM service. You can create an ATM PWE3 service
tunnel for transmitting ATM signals in trail configuration mode. By using the trail configuration
mode, you can directly configure the source and sink nodes of an ATM service and the PW
attributes on the GUI of the U2000. In this manner, the ATM service can be created quickly.
6.4.4 Creating an IP Line Service
By using the end-to-end service management function, you can directly configure the source
and sink nodes of an IP line service and the PW attributes on the U2000. In this manner, the IP
line service can be quickly created.
6.4.5 Creating a PWE3 Service Through Duplication
This topic describes how to create a PWE3 service through duplication. You can duplicate a
PWE3 service and change certain parameters to create another PWE3 service.
6.4.6 Deploying a PWE3 Service
This topic describes how to deploy a PWE3 service. When you deploy a PWE3 service, the
service is applied from the U2000 to NEs.
6.4.7 Adjusting a Discrete PWE3 Service
This topic describes how to adjust a discrete PWE3 service. The U2000 searches out all discrete
services on the network automatically. Then, the U2000 converts these services to unterminated
services or delete these services.
6.4.8 Configure PWE3 Protection Service
You can configure network protection for a PWE3 service without protection in the U2000.
6.4.9 Checking the Correctness of the Service Configuration
After configuring a service, you can check the connectivity of the service by using the Test and
Check function.
6.4.10 Performing a PW APS Protection Switching
On the U2000, you can perform MPLS tunnel protection switching. The protection switching
operations include forced switching, exercise switching, manual to working, and manual to
protection.
6.4.11 Managing ATM Connections
iManager U2000
Issue 01 (2010-08-16)
This topic describes how to manage ATM connections, including the operations of adding and
deleting an ATM connection.
6.4.1 Creating a CES Service
This topic describes how to create a CES service. You can create a CES PWE3 service tunnel
for transmitting TDM signals in trail configuration mode. By using the trail configuration mode,
you can directly configure the source and sink nodes of a CES service and the PW attributes on
the GUI of the U2000. In this manner, the CES service can be created quickly.
Prerequisite
l The DCN function must be disabled for the port that carries the CES service.
l The CES service interface must be configured. Specifically, the interface mode must be
configured to Layer 1 and the frame format and frame mode of the interface must be
configured.
l If the service need be carried by an MPLS Tunnel, you must configure a tunnel first..
l If the service need be carried by an IP or GRE Tunnel, you must configure a tunnel first. .
l To create the dynamic PW to bear the service, you need to set the IGP-ISIS and MPLS-
LDP protocol parameters.
Context
When the interface is used to carry the CES service, you need to set the frame format, to 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 UNI interface is used to carry the CES service, you need to set the frame mode.
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Step 2 Set the parameters on the General Attributes tab page.
iManager U2000
6-39
NOTE
l You can use a template to configure a service. Specifically, you can select a template in the Service
template field. Alternatively, you can create another template.
l Set Service Type to CES.
l If you set Protection Type to PW redundancy or PW APS protection, select Single source and
dual sink or Dual source and single sink on the Node List. You need to configure one source node
and two sink nodes for Single source and dual sink, and two source nodes and one sink node for Dual
source and single sink. One of the corresponding two PWs is the working trail and the other is the
protection trail. PW APS protection supports to be set as the Single source and single sink.
l If Protection Type is CE Dual-homing protection for CEs of symmetric access, you need to
configure two source nodes and two sink nodes. The corresponding two PWs protect each other.
l If Protection Type is PW backup protection, two dynamic PWs are automatically created between
the source node and sink node. The two PWs protect each other.
Step 3 Selects the source and sink NEs for a service.
1. Click Configure Source And Sink. A dialog box is displayed.
2. Select a source NE from Physical Topology on the left. Then, the selected NE is displayed
in the upper-right pane.
3. In the right portion of NE Panel, all slots and available cards of the NE are displayed.
According to the service type to be created, select the appropriate card.
4. Select an interface.
5. Set the SAI attribute of the CES service in the SAI configuration. After you complete the
setting, click Add Node, In the lower portion of the window, the new source and sink NEs
are displayed,click OK.
6. Configure the sink NE, protection NE and transit NE with the same method and based on
different protection types.
NOTE
The configuration method is the same for the sink NE, transit NE, and source NE. Hence, only the example
for configuring a source NE is provided as follows.
In the dialog box for configuring the source and sink, you can select multiple lower order timeslots and
create CES services in batches.
iManager U2000
Issue 01 (2010-08-16)
Step 4 Optional: Click Configure Source And Sink,select the Unterminated on the left,specify the
LSR ID of unterminated node and click Add Node,In the lower portion of the window, the
unterminated source and sink NEs are displayed, click OK.
NOTE
On a network, if the equipment at one end of a service can be managed by the U2000, and the equipment
at the other end of the service is from another vendor and cannot be managed by the U2000, select
Unterminated to set the LSR ID of the opposite end of the service.
Currently, the PTN equipment in the same management domain can be used to configure unterminated
trails.
If Protection Type is PW backup protection or PW APS protection, the unterminated node cannot be
set.
Step 5 Optional: Click Configure PW Switch Node to add Working and Protection transit NEs
between the source NE and sink NE.
Step 6 Set parameters for the source and sink NEs that are displayed in Node List. To view the topology
of a configured service, click the Service Topology tab in the upper-right area.
Step 7 In the PW pane in lower left portion of the window, configure parameters. Configure general
attributes of the PW.
iManager U2000
6-41
NOTE
l The PW ID can be automatically allocated.
l You can set Signaling Type to Dynamic or Static. If you set Signaling Type to Dynamic, the Forward
Label and Reverse Label are assigned automatically. If you set Signaling Type to Static, the Forward
Label and Reverse Label can be assigned automatically or manually.
l You can set Forward Type and Reverse Type to Static Binding or Select policy. If you set Forward
Type to Static Binding, you need to manually specify a tunnel in the Forward Tunnel field. If you
set Forward Type to Select Policy, you need to set the tunnel priority in the Forward Type field so
that the system selects a tunnel according to the priority.
l You may also set the forward tunnel and reverse tunnel by clicking the Service Topology tab in the
upper-right area. Select a tunnel between the source NE and sink NE, right-click, and then choose
Select Forward Tunnel or Select Reverse Tunnel. In the dialog box that is displayed, select the tunnel
for static binding.
Step 8 Optional: Click Detail. A pane is displayed in the lower-right area.
Step 9 Optional: Click the Advanced PW Attribute tab to set parameters for a PW and set the clock
mode of the source and sink NEs.
NOTE
Generally, Packet Loading Time (us) for packets that carry the CES service is 1 ms.
The value of Jitter Compensation Buffering Time(us) must be greater than the value of Packet Loading
Time (us) at the peer end.
Step 10 Optional: If the protection type of service are PW redundancy, PW backup protection or
PW APS protection,click Protection Parameter to set the Protection parameters.
l the protection type of service are PW redundancy or PW backup protection: Set
Protection Mode as 1:1 or 1+1.
l the protection type of service are PW APS Protection: Set the parameters as follows.
NOTE
Currently, the PTN supports PW APS protection with the dual-ended protection switching in 1:1
revertive mode.
Protection Type supports to be set as the Slave protection pair, If the working PWs, protection PWs,
and DNI-PWs of multiple MC-PW APS to be created share the same source and sink with the working
PW, protection PW, and DNI-PW of an MC-PW APS, you can attach these multiple MC-PW APS to
be created to the MC-PW APS (master MC-PW APS). Then, these PWs are considered as being in one
MC-PW APS for synchronous detection and switching. In this manner, the switching time is reduced,
and the OAM resources and APS resources are saved. Then, the entire MC-PW APS performs
protection switching according to the status of the PWs in the master MC-PW APS. The Protection
Group ID of slave protection pair refers to the ID of the protection group configured on PE3 as the
master PW APS protection group.
iManager U2000
Issue 01 (2010-08-16)
NOTE
l When you select the Deploy and Enable check box, A service is available on NEs only when it is
enabled.
----End
6.4.2 Creating an ETH Service
This topic describes how to create an ETH service. The service is connected to the user side,
and transmitted to one PW at the network side. In this manner, user data can be transparently
transmitted in a point-to-point manner. By using the trail configuration mode, you can directly
configure the source and sink nodes of an ETH service and the PW attributes on the GUI of the
U2000. In this manner, the ETH service can be created quickly.
Prerequisite
l If you need to use the port exclusively, disable the DCN function of the UNI port.
l The MPLS tunnel for carrying services must be created if it is used.
l The IP/GRE tunnel for carrying services must be created if it is used.
Procedure
iManager U2000
6-43
NOTE
template field. Alternatively, you can create another template.
l Set Service Type to ETH.
5. Set the SAI attribute of the Ethernet service in the SAI configuration. After you complete
the setting, click Add Node, In the lower portion of the window, the new source and sink
NEs are displayed. Click OK.
NOTE
iManager U2000
Issue 01 (2010-08-16)
Step 4 Optional: Click Configure Source And Sink, select the Unterminated on the left, specify the
LSR ID of unterminated node, and click Add Node, In the lower portion of the window, the
NOTE
trails.
set.
Step 5 Optional: Click Configure PW Switch Node to add working and protection transit NEs
iManager U2000
6-45
NOTE
for static binding.
Step 9 Optional: Click the SAI QoS tab to view the Local QoS Policy or configure the global
template and service bandwidth of SAI. Alternatively, you can select one of the policies that are
configured in the Global QoS Policy Template field. After you set Bandwidth Limited to
Enabled, the CIR (kbit/s) and PIR (kbit/s) can be set.
Step 10 Optional: Click Service Parameter tab to configure the service parameter. If you set BPDU
to Transparent Transmission, the MTU(byte) cannot be set.
Step 11 Optional: Click the PW QoS tab to configure the global template and service bandwidth of a
PW. Alternatively, you can click Global QoS Policy Template and select the global template
of QoS from the drop-down list. Then, set parameters. After you set Bandwidth Limited of a
PW to Enabled, the CIR (kbit/s) and PIR (kbit/s) can be set.
Step 12 Optional: Click the Advanced PW Attribute tab to set parameters for a PW. When the PW
Type is set to Ethernet Tagged Mode, the TPID and Request VLAN is available.
Step 13 Optional: If the protection type of service is PW redundancy, PW backup protection or PW
APS protection, Click Protection Parameter to set the Protection parameters.
l The protection type of service is PW redundancy or PW backup protection: Set Protection
Mode as 1:1 or 1+1.
l The protection type of service is PW APS Protection: Set the parameters as follows.
iManager U2000
Issue 01 (2010-08-16)
NOTE
revertive mode.
NOTE
enabled.
----End
6.4.3 Creating an ATM Service
This topic describes how to create an ATM service. You can create an ATM PWE3 service
tunnel for transmitting ATM signals in trail configuration mode. By using the trail configuration
mode, you can directly configure the source and sink nodes of an ATM service and the PW
attributes on the GUI of the U2000. In this manner, the ATM service can be created quickly.
Prerequisite
l The control plane must be configured.
l The interface must be configured. If IMA services are connected, the IMA group must be
configured.
l The ATM policy must be configured.
l The MPLS tunnel for carrying services must be created if it is used.
l The IP/GRE tunnel for carrying services must be created if it is used.
Procedure
iManager U2000
6-47
NOTE
Template field. Alternatively, you can create another template.
l Set Service Type to ATM.
iManager U2000
Issue 01 (2010-08-16)
5. Set the SAI attribute of the ETH service in the SAI configuration. After you complete the
setting, click Add Node, In the lower portion of the window, the new source and sink NEs
are displayed,click OK.
7. To configure multiple ATM connections for an ATM service at the same time, select
multiple ports for an NE by using the same method.
NOTE
Step 4 Optional: Click Configure Source And Sink,select the Unterminated on the left,specify the
LSR ID of unterminated node and click Add Node,In the lower portion of the window, the
NOTE
trails.
set.
Step 5 Optional: Click Configure PW Switch Node to add Working and Protection transit NEs
iManager U2000
6-49
iManager U2000
Issue 01 (2010-08-16)
NOTE
for static binding.
Step 8 Click ATM Link. In the dialog box that is displayed, add the ATM connection, and set relevant
parameters of the ATM connection.
NOTE
After you finishing configuring VPI/VCI of the source and sink, the U2000 assigns the transit VPI/VCI
automatically. In the case of a network consisting of PTN equipment, the transit VPI/VCI can be set.
Moreover, the transit VPI/VCI can be set be different from the VPI/VCI of the source and sink.
Step 10 Optional: Click the PW QoS tab to configure the global template of a PW. Alternatively, you
can select one of the templates that are configured in the Global QoS Policy Template field,
and set parameters.
Step 11 Optional: Click the Advanced PW Attribute tab to set parameters for a PW.
Step 12 Optional: If the protection type of service are PW redundancy, PW backup protection or
PW APS protection,click Protection Parameter to set the Protection parameters.
l the protection type of service are PW redundancy or PW backup protection: Set
Protection Mode as 1:1 or 1+1.
l the protection type of service are PW APS protection: Set the parameters as follows.
iManager U2000
6-51
NOTE
revertive mode.
NOTE
enabled.
----End
Postrequisite
After the service is created successful, the service is displayed in the PWE3 service management
window.
6.4.4 Creating an IP Line Service
By using the end-to-end service management function, you can directly configure the source
and sink nodes of an IP line service and the PW attributes on the U2000. In this manner, the IP
line service can be quickly created.
Prerequisite
You must be an NM user with "NE administrator" authority or higher.
If you need to use a UNI port exclusively, disable the DCN function at the port.
You need to create an MPLS tunnel for carrying services if it is used.
You need to create an IP/GRE tunnel for carrying services if it is used.
NOTE
You must configure a VRF UNI port before configuring a UNI port for an IP line service.
Procedure
Step 2 On the General Attributes tab page, set relevant parameters.
iManager U2000
Issue 01 (2010-08-16)
NOTE
l Set Service Type to IP E-line.
l For configuration principles of Protection Type, see PW Protection.
l By default, Service ID is set to Auto-Assign. Service ID can also be assigned according to actual
service planning, and the value range of Service ID is 1 to 4294967295.
l Set Service Name according to actual service planning. If Service Name is not set, it will be
automatically generated after the IP line service configuration is completed.
l By default, Protection is set to Protection-Free. If you need to configure PW protection for the IP
line service, select PW Redundancy.
Step 3 Configure the source and sink NEs for a service.
1. Click Configure Source and Sink. Then, the Configure Node dialog box is displayed.
2. Choose an NE from the Navigation Tree on the left and choose a corresponding port from
the pane on the right. Then, click Add Node. Set Location to Source or Sink. After the
settings are completed, click OK.
NOTE
The sink of the IP line service must be a Layer 3 port.
Step 4 Configure a PW switching node. Click Configure PW Switch Node, and then choose a PW
switching node between the source and sink NEs. Then, click OK.
iManager U2000
6-53
NOTE
A PW switching node cannot be the source or sink NE.
Step 5 Configure a PW. Click the PW tab page, and configure basic attributes for the PW.
l PW ID can be Automatically Allocated. The PW ID is networkwide unique. That is, one
PW ID indicates only one PW.
l Set Forward Type and Reverse Type to Static Binding.
l Select a created forward tunnel for Forward Tunnel.
l Select a created reverse tunnel for Reverse Tunnel.
l Set Signaling Type to Dynamic.
NOTE
In the case of an IP line service, only Dynamic signaling is supported.
l Set MPLS to Encapsulation.
NOTE
Forward Label and Reverse Label are stuck to packet headers when Ethernet frames are encapsulated to
PWs. These labels are used for label switching.
Step 6 Click Deploy to deploy the service to NEs. In this case, If you click Enable, the service is
available. Otherwise, the service is only saved on the U2000 but not deployed to NEs. By default,
the U2000 deploys and enables the service.
Step 7 Optional: Set QoS for the service access port. Click Advanced to display a pane on the lower
right side. Click the SAI QoS tab. Set Bandwidth Enabled to Enabled. Then, you can set
parameters such as CIR, PIR, CBS, and PBS. You can also select a configured QoS template by
clicking in QoS Template.
Step 8 Optional: Set PW QoS. Click the PW QoS tab and set a PW QoS policy. Set Bandwidth
Enabled to Enabled. Then, you can set parameters such as CIR, PIR, CBS, and PBS. You can
also select a configured QoS template by clicking in QoS Template.
Step 9 Click OK.
----End
6.4.5 Creating a PWE3 Service Through Duplication
This topic describes how to create a PWE3 service through duplication. You can duplicate a
PWE3 service and change certain parameters to create another PWE3 service.
iManager U2000
Issue 01 (2010-08-16)
Prerequisite
l PWE3 services that are created successfully must exist.
Context
To create a PWE3 services through duplication, you can specify the source, sink, and transit
nodes again, or change certain parameters only.
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
Step 2 Set the query criteria and click Filter.
Step 3 Create a PWE3 service by duplicating either a protected PWE3 service or an unprotected PWE3
service.
l Methods of duplicating different protected PWE3 services and the corresponding windows
are similar. The following example describes how to duplicate a PWE3 service with the PW
backup protection.
1. Select a PWE3 service with PW backup protection, right-click, and choose Copy from
the shortcut menu.
2. In the Copy PWE3 Service window, modify the attributes relevant to the new service
based on service planning, and click OK.
NOTE
In the Copy PWE3 Service window, all parameters of the original PWE3 service are retained,
including parameters of the access ports. You must change an original access port to another idle
access port before a duplicate service can be created successfully.
l If you want to change the access port to another port of the same NE, change the port directly
in the node list on the left.
l If you want to change the access port to a port of another NE, change the port by any of the
two methods. Method 1: In the topology view, right-click the NE where the required port
resides and choose the corresponding shortcut menu (change source, sink or transit node). In
the dialog box that is displayed, change the service access port. Method 2: In the node list
on the left, delete the corresponding NE. Then configure another NE for the access port.
iManager U2000
6-55
l Methods of duplicating unprotected Ethernet services, IP E-line services and CES services
and the corresponding windows are similar. The following example describes how to
duplicate a CES service.
1. Select one CES service to be duplicated, right-click, and choose Copy from the shortcut
menu.
2. In the Copy PWE3 Service dialog box, click Add.
3. In the Add Service dialog box, set the source and sink nodes, and then click OK.
NOTE
On a network, if the equipment at one end of a service can be managed by the U2000, and the
equipment at the other end of the service is from another vendor and cannot be managed by the
U2000, select Unterminated to set the LSR ID of the opposite end of the service.
Currently, the PTN equipment in the same management domain can be used to configure
unterminated trails.
NOTE
In the Add Service dialog box, you can set multiple source and sink nodes to create the
corresponding services through duplication. Those services can share intermediate NEs. The
following describes the details.
l The mapping between the source and sink NEs is 1:N or N:1. In this case, only one source
node exists, and a service is created between the source node and a sink node. In this way,
N services are created.
l The mapping between the source and sink NEs is N:N. In this case, a service is created
between a source node and the sink node with the same number. For example, a service is
created between source node 1 and sink node 1 and a service is created between source node
2 and sink node 2. In this way, N services are created.
l The mapping between the source and sink NEs is N:M and M is greater than N. In this case,
a service is created between the source node whose number is smaller than or equal to N and
the sink node with the same number. For the remaining sink nodes, a service is created
between source node N and each remaining sink node. In this way, M services are created.
Select an NE of the same type as the original NE when you select the source, sink, or transit node
for the duplication.
4. Click Advanced and Modify SAI tabs respectively to modify relevant parameters of
the service.
5. Click OK.
l The following describes how to duplicate an unprotected ATM service.
1. Configure the general attributes of the service created through duplication. For details,
see 3.1 through 3.4.
2. In the Service Parameter area, modify the attributes relevant to the ATM connection
of the new service.
3. Click Add Link to add an ATM connection to the new service.
4. Click OK.
----End
6.4.6 Deploying a PWE3 Service
This topic describes how to deploy a PWE3 service. When you deploy a PWE3 service, the
service is applied from the U2000 to NEs.
iManager U2000
Issue 01 (2010-08-16)
Prerequisite
l A PWE3 service must be created.
Procedure
Step 2 In the Set Filter Criteria dialog box that is displayed, set the filter criteria, and click Filter.
The NMS displays the PWE3 services that meet the filter criteria.
Step 3 Select one PWE3 service that is configured, right-click, and then choose Deploy from the
shortcut menu.
NOTE
l If you deploy a service, the service configuration data is applied to NEs.
l If you do not deploy a service, the service configuration data is saved in the U2000.
l After the service is created successful, in the PWE3 service management window, Deployment
Status of the service is displayed as Deployed.
----End
Postrequisite
When you need to delete the service, select the service and click Delete, click Yes in the dialog
box displayed.
NOTE
Deleting a service is to delete a service on a per-NE basis and an end-to-end tunnel. When you choose
Delete from Network Side, only the data about end-to-end services is deleted.
6.4.7 Adjusting a Discrete PWE3 Service
This topic describes how to adjust a discrete PWE3 service. The U2000 searches out all discrete
services on the network automatically. Then, the U2000 converts these services to unterminated
services or delete these services.
Prerequisite
l Discrete services must exist on the network.
Context
NOTE
You cannot convert a discrete service that has no LSR IDs for both the source and sink ends to an
unterminated service.
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Discrete Service from the main menu.
iManager U2000
6-57
Step 2 Set the query criteria and click Filter.
NOTE
Currently, only the router supports the function of filtering services by port name.
Step 3 Select one or more discrete services, click Convert to Unterminated. Alternatively, right-click
and choose Convert to Unterminated from the shortcut menu.
Step 4 Set the parameters in the dialog box, click OK.
Step 5 In the Confirm dialog box, click OK.
The adjusted discrete PWE3 service is displayed in the service list in the PWE3 Service
Management window.
Step 6 Optional: Delete a discrete PWE3 service.
1. Select one or more discrete services, click Delete Discrete. Alternatively, right-click and
choose Delete Discrete rom the shortcut menu.
2. In the Confirm dialog box, click OK.
----End
6.4.8 Configure PWE3 Protection Service
You can configure network protection for a PWE3 service without protection in the U2000.
Prerequisite
l At least a PWE3 service without protection must exist.
Procedure
Step 3 Right-click a PWE3 service without protection and choose Protect > Configure Protection
from the shortcut menu.
Step 4 Click Protection Type and select the required service protection type from the drop-down list.
l If you set Protection Type to PW redundancy or PW APS protection, select Single source
and dual sink or Dual source and single sink on the Node List. You need to configure one
source node and two sink nodes for Single source and dual sink, and two source nodes and
one sink node for Dual source and single sink. One of the corresponding two PWs is the
working trail and the other is the protection trail. PW APS protection supports to be set as
the Single source and single sink.
l If Protection Type is CE Dual-homing protection for CEs of symmetric access, you need
to configure two source nodes and two sink nodes. The corresponding two PWs protect each
other.
l If Protection Type is PW backup protection, two dynamic PWs are automatically created
between the source node and sink node. The two PWs protect each other.
iManager U2000
Issue 01 (2010-08-16)
Step 5 Click Configure Source And Sink. In the dialog box that is displayed, configure a protection
NE and click OK.
Step 6 Set parameters for the source, sink and protect NEs that are displayed in Node List. To view the
topology of a configured service, click the Service Topology tab in the upper-right area.
NOTE
for static binding.
Step 9 Optional: If you configure protection for an Ethernet or ATM service, click the SAI QoS tab
to view the Local QoS Policy or configure the global template and service bandwidth of SAI.
Alternatively, you can select one of the policies that are configured in the Global QoS Policy
Template field. After you set Bandwidth Limited to Enabled, the CIR (kbit/s) and PIR (kbit/
s) can be set.
Step 10 Optional: Click the PW QoS tab to configure the global template and service bandwidth of a
PW. Alternatively, you can click Global QoS Policy Template and select the global template
of QoS from the drop-down list. Then, set parameters. After you set Bandwidth Limited of a
PW to Enabled, the CIR (kbit/s) and PIR (kbit/s) can be set.
Step 11 Optional: Click the Advanced PW Attribute tab to set parameters for a PW.
Step 12 Optional: If the protection type of service is PW redundancy, PW backup protection or PW
APS protection, Click Protection Parameter to set the Protection parameters.
l The protection type of service is PW redundancy: Set Protection Mode as 1:1 or 1+1.
l The protection type of service is PW APS Protection: Set the parameters as follows.
NOTE
revertive mode.
Step 13 Click OK.
----End
iManager U2000
6-59
Check function.
Prerequisite
Procedure
Step 4 In the dialog box that is displayed, select the trail to be checked.
1. Service Check: check list all service configuration parameters.
3. Collect Information: view the information about the public route, LDP peer, LDP session,
and LSP.
4. Tracert: location is used to find out the fault position.
Step 6 Click Run.
----End
6.4.10 Performing a PW APS Protection Switching
On the U2000, 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 You must have created the PW APS protection service and you must have enabled the APS
protocol status.
iManager U2000
Issue 01 (2010-08-16)
Context
CAUTION
When other switching operations, excluding the exercise switching, are performed, the services
may be interrupted.
Procedure
Step 3 Select a PWE3 service with the PW APS protection. In the lower portion, information about
associated attributes is displayed.
Step 4 Click the PW tab.
Step 5 Click the Protection Parameter tab. You can query the current status of the PW APS protection
switching.
Step 6 Select a protection record and click Function in the lower right corner.
Step 7 Select a required switching operation from the drop-down list. For details of switching
operations, see PWE3 Service Management.
----End
6.4.11 Managing ATM Connections
This topic describes how to manage ATM connections, including the operations of adding and
deleting an ATM connection.
Prerequisite
Procedure
Step 3 In the service list, select a ATM service.
Step 4 Click the Service Parameter tab. The ATM link list is displayed.
Step 5 Optional: Add an ATM connection.
1. Click Create Link. The Create Link dialog box is displayed.
iManager U2000
6-61
2. Click Add Link to add an ATM connection.
3. Set the name of the connection and the VPI/VCI for the source and sink of the connection.
NOTE
In the case of a PTN NE, you need to configure the ATM policy. Otherwise, an error message is
displayed.
4. Click OK.
Step 6 Optional: Delete an ATM connection.
1. Select an ATM connection and click Delete.
2. In the confirmation dialog box, click Yes.
NOTE
A service must have at least an ATM connection.
----End
6.5 PWE3 Service Monitoring
The PWE3 service monitoring enables you to view the service topology, monitor service
performance, and monitor service alarms.
6.5.1 Configuring Ethernet OAM
This topic describes how to configure Ethernet OAM. The Ethernet OAM is used to check the
connectivity of Ethernet services in real time. This helps to locate and recover from faults.
6.5.2 Configuring PW OAM
This topic describes how to configure PW OAM. The PW OAM is used to check the connectivity
of PWE3 services in real time. This helps to locate and recover from faults.
6.5.3 Viewing the PWE3 Service Topology
This topic describes how to view the PWE3 service topology. By viewing the service topology
of a PWE3 service, you can learn the topology structure and running status of the service in real
time.
6.5.4 Monitoring Performance of a PWE3 Service
This topic describes how to monitor performance of a PWE3 service. While a PWE3 service is
running, abnormal status may occur. By viewing the performance data of a PWE3 service, you
may learn the abnormal status in time. In this manner, the maintenance personnel can take timely
measures to avoid faults.
6.5.5 Monitoring Alarms of a PWE3 Service
iManager U2000
Issue 01 (2010-08-16)
This topic describes how to monitor alarms of a PWE3 service. By creating a service monitoring
template, the maintenance personnel can monitor alarms of services that important to customers,
and learn the running status of services in real time, thus ensuring the normal running of services.
6.5.6 Viewing the Alarms of a PWE3 Service
This topic describes how to view the alarms of a PWE3 service.
6.5.7 Diagnosing a PWE3 Service
This topic describes how to diagnose a PWE3 service by using the ping and tracert.
This topic describes how to configure Ethernet OAM. The Ethernet OAM is used to check the
connectivity of Ethernet services in real time. This helps to locate and recover from faults.
Prerequisite
The equipment must communicate with the U2000 in the normal state.
A PWE3 service must be created.
Context
The Ethernet 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. The OAM packet processing principle of the MD is as
follows: Block the low level, transparently transmit the high level, and process the same
level.
l Maintenance association (MA): The MA can be considered as a service-related domain,
which consists of many maintenance end points (MEPs).
l Maintenance end point (MEP): The MEP is the transmitting and terminating points of all
OAM packets. It is relevant to services. The MEP has one unique MEP ID in the MA. In
a network, the MA and MEP ID can determine a unique MEP.
l Maintenance intermediate point (MIP): The MIP is relevant to the MD but irrelevant to the
MA. The MIP cannot initiate the OAM packets. The MIP can respond to and forward LB
and LT packets, but the MIP can forward the CC packets only.
The Ethernet OAM sends CC packets periodically to check the connectivity of services in real
time. The source MEP constructs and sends CC frames periodically. The destination MEP
receives the CC frames and directly starts the CC function. If the destination MEP does not
receive the CC frames from the source in a period of time (for example, 3.5 times transmit
period), the MEP reports the CCLOS alarm automatically.
You can perform the LB test on Ethernet services without interrupting the services, to check the
connectivity of the services for locating and rectifying faults.
Procedure
iManager U2000
6-63
Step 3 Optional: Perform a CC test.
1. In the service list, select a service where you want to configure the OAM, right-click, and
choose Ethernet OAM > Enable CC from the shortcut menu.
2. Select a link and click OK. The source MEP starts the CC check. If the link fails, the
destination MEP reports the CCLOS alarm.
Step 4 Optional: Perform an LB test.
choose Ethernet OAM > LB Test from the shortcut menu.
2. Select a link and right-click, choose Configure and set the LB check parameter information.
3. Click Run to start an LB test. The Operation Result dialog box is displayed, indicating
that the operation is successful.
4. Click Close. View the test result in the LB Check Information tab and LB Statistic
Information tab.
----End
6.5.2 Configuring PW OAM
This topic describes how to configure PW OAM. The PW OAM is used to check the connectivity
of PWE3 services in real time. This helps to locate and recover from faults.
Prerequisite
The equipment must communicate with the U2000 in the normal state.
A PWE3 service must be created and deployed.
Procedure
Step 3 In the service list, select a service to be configured with the PW OAM.
Step 4 Click the PW tab. Then, click the Basic tab.
Step 5 Select one PW and click PW OAM. A dialog box is displayed.
Step 6 After you configure the PW OAM, click OK. The configuration is applied to NEs and the current
dialog box is closed.
----End
6.5.3 Viewing the PWE3 Service Topology
This topic describes how to view the PWE3 service topology. By viewing the service topology
of a PWE3 service, you can learn the topology structure and running status of the service in real
time.
iManager U2000
Issue 01 (2010-08-16)
Prerequisite
l PWE3 services that are created must exist.
Procedure
Step 3 In the service list, select a service to be viewed.
Step 4 View the topology structure of a service.
In the service topology, you can learn PE information of the source and sink ends, and interface
information for connecting to CE.
Step 5 Check alarm information of a service.
If a fault occurs, the corresponding interface and PW of the PE in the service topology is
displayed with fault identifier.
Step 6 You can perform the following operations in the service topology.
l In the service topology, select a PE, right-click, and then choose the following menu items
from the shortcut menu respectively.
Choose NE Explorer to view the NE Explorer of the equipment.
Choose View Real-Time Performance to view the real-time performance of the PW.
l In the service topology, select one interface, right-click, and then choose View Real-Time
Performance to view the real-time performance of the interface.
l In the topology view, select a PW between PEs, right-click, and then choose the following
menu items from the shortcut menu respectively.
Choose Fast Diagnose. In the LSP Ping window that is displayed, diagnose the PW.
Choose View Real-Time Performance to view the real-time performance of the PW.
Choose View Tunnel. In the Tunnel Management dialog box that is displayed, view
the Tunnel information.
----End
6.5.4 Monitoring Performance of a PWE3 Service
This topic describes how to monitor performance of a PWE3 service. While a PWE3 service is
running, abnormal status may occur. By viewing the performance data of a PWE3 service, you
may learn the abnormal status in time. In this manner, the maintenance personnel can take timely
measures to avoid faults.
Procedure
iManager U2000
6-65
Step 3 View the runtime performance of a service. Right-click the NE and choose View Real-Time
Step 4 Create a monitoring instance for a service. For details, refer to the chapter of monitoring instance
Step 5 View the history performance of a service. Right-click a required service and choose
----End
6.5.5 Monitoring Alarms of a PWE3 Service
This topic describes how to monitor alarms of a PWE3 service. By creating a service monitoring
template, the maintenance personnel can monitor alarms of services that important to customers,
and learn the running status of services in real time, thus ensuring the normal running of services.
Procedure
Step 1 Choose Fault > Service Monitoring > Service Monitoring Template from the main menu.
Step 2 In the Centralized Monitoring dialog box, expand the All Service branch to view alarm
information of all services.
Step 3 Click Select Monitoring Group.
Step 4 In the Select Monitoring Group dialog box, click Add from the shortcut menu.
Step 5 In the Add Monitoring Group dialog box, enter the name of the monitoring group and click
OK.
The newly-added monitoring group is displayed in the monitoring group list.
iManager U2000
Issue 01 (2010-08-16)
Step 6 Select the monitoring group that is added, right-click, and then choose Add Monitoring
Service from the shortcut menu.
Step 7 In the Add Monitoring Service dialog box, select the corresponding service tab and select the
service to be added. Then, click Add.
Step 8 Click Close.
----End
6.5.6 Viewing the Alarms of a PWE3 Service
This topic describes how to view the alarms of a PWE3 service.
Context
When a service alarm is generated, certain phenomena occur, including but not limited to:
l The alarm panel blinks.
l The color of the alarm status column in the service list changes.
l The color of the NE, interface, or link in the service topology changes.
If you find a service alarm through preceding phenomena, perform the following operations to
view the detailed alarm information.
Procedure
Step 3 Right-click the service with the alarm and choose Alarm > Current Alarm from the shortcut
menu.
You can also choose Alarm > History Alarm from the shortcut menu to view the history alarms
of the service.
Step 4 Select the service alarm in the alarm list and view the detailed alarm information in the details
area.
----End
Postrequisite
Primarily determine the possible cause of the alarm based on the detailed alarm information,
and then locate the fault by using the debugging tool.
6.5.7 Diagnosing a PWE3 Service
This topic describes how to diagnose a PWE3 service by using the ping and tracert.
Prerequisite
iManager U2000
6-67
Procedure
Step 3 Set a scheduled test.
1. Right-click a PWE3 service and choose Diagnose > Create Test Suite from the shortcut
menu.
2. Select NO. and click Next.
3. Select LSP Ping and click Detail. In the dialog box that is displayed, set advanced
parameters for the test and click OK.
4. Set Test Time, click Add, and then click Finish.
Step 4 View the scheduled test result.
1. Right-click the PWE3 service and choose Diagnose > View Test Result from the shortcut
menu.
2. Click Query to view the scheduled test result.
3. Optional: Click Export Result to export the result to the local computer.
NOTE
The result can be exported to a .cvs, .html, , .xls, .pdf, or .txt file.
Step 5 View the test strategy.
1. Right-click the corresponding PWE3 service and choose Diagnose > View Test
Strategy from the shortcut menu.
2. Click Create. In the dialog box that is displayed, set information relevant to the strategy
and click OK to create a diagnosis strategy.
3. Click the Associated Test Suite tab. Click Bind.
iManager U2000
Issue 01 (2010-08-16)
4. In the dialog box that is displayed, select an existing test suite and click OK to bind the test
strategy and test suite.
5. Click Run to implement the preset diagnosis strategy.
Step 6 Set the manual test.
1. Right-click a PWE3 service and choose Test And Check from the shortcut menu.
2. Optional: Select LSP Ping and click . In the dialog box that is displayed, set
parameters relevant to the LSP ping test and click OK.
3. Optional: Select LSP Tracert and click . In the dialog box that is displayed, set
parameters relevant to the LSP tracert test and click OK.
NOTE
If you select Reply mode, details of an error are displayed only when the error occurs in the reply
mode.
4. Click Run and then view test result in the pane on the right.
----End
6.6 Managing PWE3 Service Authority
This topic describes how to manage the PWE3 service authority.
6.6.1 Configuring the Rights of a User on PWE3 Services
You can configure operation rights on PWE3 services for different users. This enhances the
NMS security.
6.6.2 Viewing the Rights of a User on PWE3 Services
This topic describes how to view the rights of a user on PWE3 services.
6.6.1 Configuring the Rights of a User on PWE3 Services
You can configure operation rights on PWE3 services for different users. This enhances the
NMS security.
Prerequisite
A user that requires rights allocation must exist.
Procedure
Step 2 Click Filter. In the dialog box that is displayed, set the filter criteria, and click Filter.
Step 3 Select the required service, right-click, and then choose Confer Service Authority from the
shortcut menu.
Step 4 In Useable User, select the required user and click to add the user to Selected
User.
iManager U2000
6-69
Step 5 Click OK.
----End
6.6.2 Viewing the Rights of a User on PWE3 Services
This topic describes how to view the rights of a user on PWE3 services.
Prerequisite
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service Authority from the main menu.
Step 2 In the dialog box that is displayed, select the required user and view its manageable services in
the right pane.
NOTE
In the right pane, after selecting the required services, you can adjust its service authorization.
Step 3 Click OK.
----End
6.7 Examples for Configuring PWE3 Services
This topic describes several examples of configuring PWE3 services, including the TDM, ATM,
and Ethernet services.
6.7.1 Example for Configuring a CES Emulation Service
This topic describes the example of configuring a CES emulation service. Specifically, the
example description, service planning, and configuration process are provided.
6.7.2 Example for Configuring an ATM Service
This topic describes the example of configuring an ATM service. Specifically, the example
description, service planning, and configuration process are provided.
6.7.3 Example for Configuring an Ethernet Private Line Service
This topic describes the example of configuring an Ethernet private line service. Specifically,
the example description, service planning, and configuration process are provided.
6.7.4 Example of Configuring an End-to-End IP Line Service
This section describes an example of configuring an end-to-end IP line service and provides a
flowchart to illustrate the service configuration process. The configuration example involves
networking, service planning, and service configuration.
6.7.1 Example for Configuring a CES Emulation Service
This topic describes the example of configuring a CES emulation service. Specifically, the
example description, service planning, and configuration process are provided.
iManager U2000
Issue 01 (2010-08-16)
Example Description
Networking and Requirements
As shown in Figure 6-33, the CES service is transmitted through the PTN equipment between
BTS and BSC. Two TDM services are transmitted between the BTS and BSC that are connected
to NE1. NE1 is the OptiX PTN 1900 and functions as a base station to access services. NE2,
NE3, NE4, and NE5 are the OptiX PTN 3900. NE6 is the OptiX PTN 1900. A tunnel is required
between NE1 and NE3.
You can create the MPLS APS protection to transmit the services that required high network
security.
l Active tunnel: NE1-NE2-NE3, in which NE2 is a transit node.
l Bypass tunnel: NE1-NE6-NE5-NE4-NE3, in which NE6, NE5, and NE4 are transit nodes.
When the active tunnel is faulty, the services are switched to the bypass tunnel.
Figure 6-33 Network of the CES service
Woking Tunnel
Protection Tunnel
BTS
BSC
NE1
NE2
NE3
NE4
NE5
NE6
GE Ring On
Access Layer
10 GE Ring On
Convergence Layer

Figure 6-34 shows the planning of the boards and ports on each NE.
iManager U2000
6-71
Working Tunnel
Protection Tunnel
BTS
BSC
NE1
NE2
NE3
NE4
NE5
NE6
4-EFG2-1(port-1)
10.0.0.1
6-L12
3-EG16-1(port-1)
10.0.0.2
1-EX2-1(port-1)
10.0.1.2
1-EX2-1(port-1)
10.0.1.1
6-MP1-1-CD1-1port-1
10.0.6.1
4-EFG2-2(port-2)
10.0.4.1
GE Ring On
Access Layer
10 GE Ring On
Convergence Layer
1-EX2-2(port-2)
10.0.2.1
1-EX2-1(port-1)
10.0.2.2
1-EX2-2(port-2)
10.0.3.1
1-EX2-2(port-2)
10.0.3.2
3-EG16-1(port-1)
10.0.4.2
4-EFG2-1(port-1)
10.0.5.2
4-EFG2-2(port-2)
10.0.5.1

Service Planning
This topic describes the planning of the parameters, such as IP addresses, interfaces, and protocol
types involved in this example in table format.
Table 6-8 NE parameters
NE1 1.0.0.1
4-EFG2-1(Port-1) 10.0.0.1 255.255.255.252
4-EFG2-2(Port-2) 10.0.5.1 255.255.255.252
NE2 1.0.0.2
3-EG16-1(Port-1) 10.0.0.2 255.255.255.252
1-EX2-1(Port-1) 10.0.1.1 255.255.255.252
NE3 1.0.0.3
1-EX2-1(Port-1) 10.0.1.2 255.255.255.252
1-EX2-2(Port-2) 10.0.2.1 255.255.255.252
NE4 1.0.0.4
1-EX2-1(Port-1) 10.0.2.2 255.255.255.252
1-EX2-2(Port-2) 10.0.3.1 255.255.255.252
NE5 1.0.0.5
1-EX2-2(Port-2) 10.0.3.2 255.255.255.252
3-EG16-1(Port-1) 10.0.4.2 255.255.255.252
NE6 1.0.0.6 4-EFG2-1(Port-1) 10.0.5.2 255.255.255.252
iManager U2000
Issue 01 (2010-08-16)
4-EFG2-2(Port-2) 10.0.4.1 255.255.255.252

Table 6-9 lists the planning details of tunnel parameters.
Table 6-9 Tunnel parameters
Parameter Working Tunnel Protection Tunnel
Tunnel ID 100 101 120 121
Tunnel Name Working
Tunnel-
Forward
Working
Tunnel-Reverse
Protection
Tunnel-
Forward
Protection
Tunnel-
Reverse
Signaling Type Static CR Static CR Static CR Static CR
Bandwidth(Kbit/s) No Limit No Limit No Limit No Limit
Ingress Node NE1 NE3 NE1 NE3
Transit Node NE2 NE2 NE6, NE5,
NE4
NE4, NE5,
NE6
Egress Node NE3 NE1 NE3 NE1
Ingress Node Route
Information
NE1
l Out
Interface:
4-EFG2-1
(Port-1)
l Out Label:
20
NE3
l Out Interface:
1-EX2-1
(Port-1)
l Out Label: 21
NE1
l Out
Interface: 4-
EFG2-2
(Port-2)
l Out Label:
22
NE3
l Out
Interface: 1-
EX2-2
(Port-2)
l Out Label:
23
iManager U2000
6-73
Transit Node Route
Information
NE2
l In
Interface:
3-EG16-1
(Port-1)
l In Label: 20
l Out
Interface:
1-EX2-1
(Port-1)
l Out Label:
30
NE2
l In Interface:
1-EX2-1
(Port-1)
l In Label: 21
l Out Interface:
3-EG16-1
(Port-1)
l Out Label: 31
NE6
l In Interface:
4-EFG2-1
(Port-1)
l In Label: 22
l Out
Interface: 4-
EFG2-2
(Port-2)
l Out Label:
32
NE5
l In Interface:
3-EG16-1
(Port-1)
l In Label: 32
l Out
Interface: 1-
EX2-2
(Port-2)
l Out Label:
42
NE4
l In Interface:
1-EX2-2
(Port-2)
l In Label: 42
l Out
Interface: 1-
EX2-1
(Port-1)
l Out Label:
52
NE4
l In Interface:
1-EX2-1
(Port-1)
l In Label: 23
l Out
Interface: 1-
EX2-2
(Port-2)
l Out Label:
33
NE5
l In Interface:
1-EX2-2
(Port-2)
l In Label: 33
l Out
Interface: 3-
EG16-1
(Port-1)
l Out Label:
43
NE6
l In Interface:
4-EFG2-2
(Port-2)
l In Label: 43
l Out
Interface: 4-
EFG2-1
(Port-1)
l Out Label:
53
Egress Node Route
Information
NE3
l In
Interface:
1-EX2-1
(Port-1)
l In Label: 30
NE1
l In Interface:
4-EFG2-1
(Port-1)
l In Label: 31
NE3
l In Interface:
1-EX2-2
(Port-2)
l In Label: 52
NE1
l In Interface:
4-EFG2-2
(Port-2)
l In Label: 53

Table 6-10 and Table 6-11 list the planning details of CES service parameters.
iManager U2000
Issue 01 (2010-08-16)
Table 6-10 CES service parameters: NE1-NE3 (E1 timeslots partially used)
Parameter Value
Service Type CES
Service ID 4
Service Name CES Remote Service1
Protection Type Protection-Free
Set as Source NE1
Set as Sink NE3
Port NE1: 6-L12
NE3: 6-MP1-1-CD1-1(Port-1)
Channelized YES
64k timeslot 1-14, 20
High-order timeslot NE1: -
NE3: 1
Low-order timeslot NE1: 2
NE3: 2
PW ID 8
Signaling Type Static
PW Type CESoPSN
Forward Label 36
Reverse Label 36
Forward Type Static Binding
Forward Tunnel Working Tunnel-Forward(Tunnel-0100)
Reverse Type Static Binding
Reverse Tunnel Working Tunnel-Reverse(Tunnel-0101)
RTP Header Disabled
Jitter Compensation Buffering Time(us) 8000
Packet Loading Time (us) 1000
Clock Mode External Clock Mode
EXP 4

iManager U2000
6-75
Table 6-11 CES service parameters: NE1-NE3 (E1 timeslots fully used)
Parameter Value
Service Type CES
Service ID 5
Service Name CES Remote Service2
Protection Type Protection-Free
Set as Source NE1
Set as Sink NE3
Port NE1: 6-L12
NE3: 6-MP1-1-CD1-1(Port-1)
High-order timeslot NE1: -
NE3: -
Low-order timeslot NE1: 3
NE3: 3
PW ID 9
PW Type SAToP
Forward Label 37
Reverse Label 37
Forward Type Static Binding
Forward Tunnel Working Tunnel-Forward(Tunnel-0100)
Reverse Type Static Binding
Reverse Tunnel Working Tunnel-Reverse(Tunnel-0101)
RTP Header Disabled
Jitter Compensation Buffering Time(us) 8000
Packet Loading Time (us) 1000
Clock Mode External Clock Mode
EXP 4

NOTE
To create an MPLS APS, you can refer to the descriptions of how to create an MPLS tunnel protection
group.
iManager U2000
Issue 01 (2010-08-16)
This topic describes how to configure a CES emulation service.
Prerequisite
You must learn about the networking requirements and service planning described in the
example.
Procedure
Step 1 Set LSR IDs.
Selection
network.
planning.

Selection
LSR ID 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
Set this parameter
network.
planning.

iManager U2000
6-77
Selection
planning.
planning.
planning.
to be created.

Selection
NE2: Transit
NE3: Egress
node.
is a transit node.
node.
iManager U2000
Issue 01 (2010-08-16)
Selection

Selection
Set this parameter
planning.
Tunnels: 10000
Set this parameter
planning.
Tunnels: 10000
Set this parameter
planning.
Tunnels: 20000
Set this parameter
planning.
Tunnels: 20000
Set this parameter
planning.
Tunnels: 1620
Set this parameter
planning.
Tunnels: E-LSP
Tunnels: None
Set this parameter
planning.
iManager U2000
6-79
Selection
l NE1: 4-EFG2-1
l NE2: 1-EX2-1
Reverse Tunnel:
l NE3: 1-EX2-1
l NE2: 3-EG16-1
Set this parameter
planning. Only this
and transit node.
l NE1: 20
l NE2: 30
Reverse Tunnel:
l NE3: 21
l NE2: 31
Set this parameter
planning.
l NE2: 3-EG16-1
l NE3: 1-EX2-1
Reverse Tunnel:
l NE2: 1-EX2-1
l NE1: 4-EFG2-1
Set this parameter
planning. Only this
transit node.
l NE2: 20
l NE3: 30
Reverse Tunnel:
l NE2: 21
l NE1: 31
Set this parameter
planning.
l NE1: 10.0.0.2
l NE2: 10.0.1.2
Reverse Tunnel:
l NE3: 10.0.1.1
l NE2: 10.0.0.1
Set this parameter
planning. Only this
and transit node.

Step 3 Optional: Create the protection tunnel.
iManager U2000
Issue 01 (2010-08-16)
Selection
planning.
planning.
planning.
to be created.

Selection
NE3: Egress
node.
nodes.
node.

Step 4 Configure the E1 interface at the BTS side.
1. In the NE Explorer, select NE1 and choose Configuration > Interface Management >
PDH Interface from the Function Tree.
2. Click the General Attributes tab. Select 6-L12-2(Port-2) and 6-L12-3(Port-3) and set Port
Mode to Layer 1.
iManager U2000
6-81
NOTE
Before setting the port mode, ensure that the DCN of the port is disabled.
3. Click Apply. The Operation Result dialog box is displayed, indicating that the operation
is successful. Click Close.
4. Click the Advanced Attributes tab. Select 6-L12-2(Port-2) and set Frame Format to
CRC-4 Multiframe. Select 6-L12-3(Port-3) and set Frame Format to Unframe.
is successful. Click Close.
Step 5 Configure the STM-1 interface on the BSC side.
1. In the NE Explorer, select the 6-MP1 of NE3 and choose Configuration > Interface
Management > Path Configuration from the Function Tree.
2. 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.
is successful.
Step 6 Create remote CES service 1.
1. Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
2. Set the parameters of the CES service.
Table 6-12 Parameters of general attributes
Selection
Service Type CES Set this parameter
planning.
Service ID 4 A service ID uniquely
identifies a service on the
entire network.
Service Name CES Remote Service 1 Set this parameter
planning.
Protection Type Protection-Free Set this parameter
planning.
iManager U2000
Issue 01 (2010-08-16)

3. Click Configure Source And Sink. A dialog box is displayed. On the Physical
Topology in the upper left portion of the window, set NE1 as the source NE, set NE3 as
the sink NE. Set relevant parameters and click OK.
Table 6-13 Parameters of the source node
Selection
Channelized Checked l When working in
channelized mode, the
CE1 port is divided into
32 timeslots physically.
You can bind any of the
timeslots except timeslot
0. The bound timeslots
work as a single port
whose logical features
are the same as those of
a synchronous serial
port.
l When working in clear
channel mode, the CE1
port does not support
timeslotting.
iManager U2000
6-83
Selection
64k timeslot 1-14,20 This parameter indicates
the timeslot compression
list for structured CES
emulation services.
Services are loaded in the
timeslots that are included
in the timeslot compression
list, encapsulated into PW
packets, and then
transmitted to the peer end
on an Ethernet. Services
loaded in the timeslots that
are not included in the
timeslot compression list
are not encapsulated into
PW packets and thus the
network bandwidth is
saved. After receiving the
PW packets, the peer end
restores the services to the
corresponding timeslot
based on its own timeslot
compression list. The
timeslot lists at the two ends
can be different, but the
number of timeslots must
be the same. Otherwise,
services are unavailable.
Low-order timeslot 2 You can set the lower order
timeslot after you set
channelization. In the case
of an E1 port, set the E1 port
number. In the case of a line
port, set the VC-12 lower
order path number.

iManager U2000
Issue 01 (2010-08-16)
Table 6-14 Parameters of the sink node
Selection
Channelized Checked l When working in
CE1 port is divided into
32 timeslots physically.
You can bind any of the
whose logical features
are the same as those of
a synchronous serial
port.
timeslotting.
64k timeslot 1-14,20 This parameter indicates
the timeslot compression
list for structured CES
emulation services.
Services are loaded in the
timeslots that are included
in the timeslot compression
list, encapsulated into PW
packets, and then
transmitted to the peer end
on an Ethernet. Services
loaded in the timeslots that
are not included in the
timeslot compression list
are not encapsulated into
PW packets and thus the
network bandwidth is
saved. After receiving the
PW packets, the peer end
restores the services to the
corresponding timeslot
based on its own timeslot
compression list. The
timeslot lists at the two ends
can be different, but the
number of timeslots must
be the same. Otherwise,
services are unavailable.
iManager U2000
6-85
Selection
of an E1 port, set the E1 port
order path number.
High-order timeslot 1 You can set the higher order
of a line port, set the VC-4
higher order path number.

4. In PW in the lower left portion of the window, set relevant parameters.
Table 6-15 PW parameters
Selection
Forward Type Static Binding l If you set Forward
Type to Static Binding,
you need to manually
specify a tunnel in
theForward Tunnel
area.
l If you set Forward
Type, you need to set the
tunnel priority in the
Forward Tunnel area
so that the system selects
a tunnel according to the
priority.
Forward Tunnel Working Tunnel-Positive
(Tunnel-0100)
Set this parameter
planning.
iManager U2000
Issue 01 (2010-08-16)
Selection
Reverse Type Static Binding l If you set Reverse
specify a tunnel in the
Reverse Tunnel area.
l If you set Reverse
Type to Select Policy,
you need to set the
Reverse Tunnel area so
that the system selects a
tunnel according to the
priority.
Reverse Tunnel Working Tunnel-Reverse
(Tunnel-0101)
Set this parameter
planning.
PW ID 8 A PW ID uniquely
identifies a PW on the
entire network.
Signaling Type Static This parameter specifies
whether a PW is dynamic
or static. In the case of a
dynamic PW, services are
available after a signaling
negotiation is successful.
In the case of a static PW, a
signaling negotiation is not
required. In addition, you
need to configure Forward
Label and Reverse Label
for a static PW.
Forward Label 36 An Forward Label is
attached to the packet
header when a CES frame
is encapsulated into a PW.
An Forward Label is used
for label switching.
Reverse Label 36 A Reverse Label is
header when a CES frame
is encapsulated into a PW.
A Reverse Label is used for
label switching.
iManager U2000
6-87
Selection
Encapsulation Type MPLS Set this parameter
planning.

5. Click Advanced and configure Advanced PW Attribute.
Table 6-16 Parameters of advanced attributes
Selection
PW Type CESoPSN CESoPSN is the structured
emulation, for which the
timeslot compression can
be set. SAToP is the non-
structured emulation, for
which the timeslot
compression cannot be set.
Control Word Must Use On an MPLS PSN network,
a control word carries the
packet information. A
control word is the
encapsulation packet
header that consists of four
bytes. A control word can
be used to identify the
packet sequence or used for
bit stuffing.
Control Channel Type CW Set this parameter
planning.
VCCV Verification Mode Ping The VCCV verification
mode is used to detect the
connectivity of a PW.
RTP Header Disabled Set this parameter
planning.
iManager U2000
Issue 01 (2010-08-16)
Selection
Jitter Compensation
Buffering Time(us)
8000 Sets the size of the buffer in
the receive direction. The
size of the buffer is
measured based on time.
When a PW carries CES
emulation service, you can
set this parameter.
Packet Loading Time (us) 1000 Set the packet loading time.
Emulation Level E1 Set this parameter
planning.

6. Click OK.
Step 7 Create remote CES service 2. For details, refer to Step 6.1 through Step 6.6.
Selection
Service Type CES Set this parameter according
to the network planning.
entire network.
Service Name CES Remote Service 2 Set this parameter according
Protection Type Protection-Free Set this parameter according

iManager U2000
6-89
Selection
Channelized Unchecked l When working in
CE1 port is divided into 32
timeslots physically. You
can bind any of the
whose logical features are
the same as those of a
synchronous serial port.
timeslotting.
channelization. In the case of
an E1 port, set the E1 port
order path number.

Selection
Channelized Unchecked l When working in
CE1 port is divided into 32
timeslots physically. You
can bind any of the
whose logical features are
the same as those of a
synchronous serial port.
timeslotting.
iManager U2000
Issue 01 (2010-08-16)
Selection
an E1 port, set the E1 port
order path number.
High-order timeslot 1 You can set the higher order
a line port, set the VC-4
higher order path number.

Selection
Forward Type Static Binding l If you set Forward Type
to Static Binding, you
need to manually specify a
tunnel in theForward
Tunnel area.
l If you set Forward Type,
you need to set the tunnel
priority in the Forward
Tunnel area so that the
system selects a tunnel
according to the priority.
Forward Tunnel Working Tunnel-Positive
(Tunnel-0100)
Set this parameter according
Reverse Type Static Binding l If you set Reverse Type to
Static Binding, you need
to manually specify a
tunnel in the Reverse
Tunnel area.
l If you set Reverse Type to
Select Policy, you need to
set the tunnel priority in
the Reverse Tunnel area
so that the system selects a
tunnel according to the
priority.
iManager U2000
6-91
Selection
Reverse Tunnel Working Tunnel-reverse
(Tunnel-0101)
PW ID 9 A PW ID uniquely identifies
a PW on the entire network.
whether a PW is dynamic or
static. In the case of a
negotiation is successful. In
the case of a static PW, a
Label and Reverse Label for
a static PW.
Forward Label 37 An Forward Label is attached
to the packet header when a
CES frame is encapsulated
into a PW. An Forward
Label is used for label
switching.
Reverse Label 37 A Reverse Label is attached
to the packet header when a
CES frame is encapsulated
into a PW. A Reverse Label
is used for label switching.
Encapsulation Type MPLS Set this parameter according

Selection
PW Type SAToP CESoPSN is the structured
emulation, for which the
timeslot compression can be
set. SAToP is the non-
structured emulation, for
which the timeslot
compression cannot be set.
iManager U2000
Issue 01 (2010-08-16)
Selection
Control Word No Use On an MPLS PSN network, a
control word carries the
control word is the
encapsulation packet header
that consists of four bytes. A
control word can be used to
identify the packet sequence
or used for bit stuffing.
Control Channel Type None Set this parameter according
RTP Header Disabled Set this parameter according
Jitter Compensation
Buffering Time(us)
8000 Sets the size of the buffer in
the receive direction. The
size of the buffer is measured
based on time. When a PW
carries CES emulation
service, you can set this
parameter.
Packet Loading Time (us) 1000 Set the packet loading time.
Emulation Level E1 Set this parameter according

----End
6.7.2 Example for Configuring an ATM Service
This topic describes the example of configuring an ATM service. Specifically, the example
description, service planning, and configuration process are provided.
Example Description
Figure 6-35 shows the networking diagram of the ATM services. The 3G R99, signaling, and
HSDPA services are required between the two base stations and RNC. NE1 accesses the MPLS
iManager U2000
6-93
network that consists of PTN equipment. NodeB1 is connected to NE1 through IMA1, and
NodeB2 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, signaling, and HSDPA services respectively. At the remote
end, to transparently transmit the ATM services on the MPLS network, NE2 is connected to
RNC through STM-1.NE1 is the OptiX PTN 1900; NE2, NE3, NE4, and NE5 are the OptiX
PTN 3900; NE6 is the OptiX PTN 950. ATM services are carried in the active tunnel. In addition,
you can create a bypass tunnel to protect real-time services.
The active tunnel is as follows: NE1-NE2-NE3. The bypass tunnel is as follows: NE1-NE6-
NE5-NE4-NE3.
Figure 6-35 Network of the ATM services
Tunnel
NodeB 1
RNC
NE1
NE2
NE3
NE4
NE5
NE6
GE Ring On
Access Layer
10 GE Ring On
Convergence Layer
NodeB 2
pw1
pw3
pw2
IMA1
IMA2
ATM
STM-1
UNI NNI
VPI
1
VCI
100
1 101
Connect1 R99
HSDPA
VPI
50
VCI
32
51 32
Singal 1 102
52 32
UNI
VPI
50
VCI
32
51 32
52 32
IMA1:
UNI NNI
VPI
1
VCI
100
1 101
R99
HSDPA
VPI
60
VCI
32
61 32
1 102
62 32
UNI
VPI
60
VCI
32
61 32
62 32
IMA2:
NNI
VPI
50
VCI
32
51 32
52 32
NNI
VPI
60
VCI
32
61 32
62 32
PW
Protection Tunnel
Connect2
Connect3
Singal
Connect1
Connect2
Connect3

Figure 6-36 shows the planning of NEs.
iManager U2000
Issue 01 (2010-08-16)
Figure 6-36 NE planning diagram
Working Tunnel
Protection Tunnel
NE1
NE2
NE3
NE4
NE5
NE6
4-EFG2-1(Port-1)
10.0.0.1
3-EG16-1(Port-1)
10.0.0.2
1-EX2-1(-1)
10.0.1.2
1-EX2-1(Port-1)
10.0.1.1
3-MP1-1-AD1-1Port-1
10.0.6.1
2-EG2-2(Port-2)
10.0.4.1
GE Ring On
Access Layer
10 GE Ring On
Convergence Layer
1-EX2-2(Port-2)
10.0.2.1
1-EX2-1(Port-1)
10.0.2.2
1-EX2-2(Port-2)
10.0.3.1
1-EX2-2(Port-2)
10.0.3.2
3-EG16-1(Port-1)
10.0.4.2
2-EG2-1(Port-1)
10.0.5.2
4-EFG2-2(Port-2)
10.0.5.1
RNC
NodeB 1
NodeB 2
1-CXP-MD1-3-L12

Service Planning
Between NE1 and NE3, PW1 transmits R99 services, PW2 transmits HSDPA services, and PW3
transmits signaling services. Therefore, you need to create three ATM services. The two base
stations converge R99 services and access signaling and HSDPA services. Therefore, you need
to create two ATM services connected to the N:1 VCC.
NE LSR ID Port Port IP Address IP Mask
NE1 1.0.0.1
4-EFG2-1(Port-1) 10.0.0.1 255.255.255.252
4-EFG2-2(Port-2) 10.0.5.1 255.255.255.252
NE2 1.0.0.2
3-EG16-1(Port-1) 10.0.0.2 255.255.255.252
1-EX2-1(Port-1) 10.0.1.1 255.255.255.252
NE3 1.0.0.3
1-EX2-1(Port-1) 10.0.1.2 255.255.255.252
1-EX2-2(Port-2) 10.0.2.1 255.255.255.252
NE4 1.0.0.4
1-EX2-1(Port-1) 10.0.2.2 255.255.255.252
1-EX2-2(Port-2) 10.0.3.1 255.255.255.252
NE5 1.0.0.5 1-EX2-2(Port-2) 10.0.3.2 255.255.255.252
iManager U2000
6-95
NE LSR ID Port Port IP Address IP Mask
3-EG16-1(Port-1) 10.0.4.2 255.255.255.252
NE6 1.0.0.6
4-EFG2-1(Port-1) 10.0.5.2 255.255.255.252
4-EFG2-2(Port-2) 10.0.4.1 255.255.255.252

Tunnel ID 100 101 120 121
Tunnel Name Working
Tunnel-
Forward
Working Tunnel-
Reverse
Protection
Tunnel-Forward
Protection
Tunnel-Reverse
Signaling
Type
Static CR Static CR Static CR Static CR
Bandwidth
(Kbit/s)
No Limit No Limit No Limit No Limit
Source Node NE1 NE1 NE3
Sink Node NE3 NE3 NE1
Route
Constraint
Port IP
Address
IP address of
the ingress port
of NE2: 3-
EG16-1(Port-1)
10.0.0.2
IP address of
the ingress port
of NE3: 1-
EX2-1(Port-1)
10.0.1.2
IP address of the
ingress port of
NE2: 1-EX2-2
(Port-2) 10.1.2.2
IP address of the
ingress port of
NE1: 4-EFG2-1
(Port-1) 10.1.1.2
IP address of the
ingress port of
NE6: 2-EG2-1
(Port-1) 10.0.5.2
IP address of the
ingress port of
NE5: 3-EG16-1
(Port-1) 10.0.4.2
IP address of the
ingress port of
NE4: 1-EX2-2
(Port-2) 10.0.3.1
IP address of the
ingress port of
NE3: 1-EX2-2
(Port-2) 10.0.2.1
IP address of the
ingress port of
NE4: 1-EX2-1
(Port-1) 10.0.2.2
IP address of the
ingress port of
NE5: 1-EX2-2
(Port-2) 10.0.3.2
IP address of the
ingress port of
NE6: 2-EG2-2
(Port-2) 10.0.4.1
IP address of the
ingress port of
NE1: 4-EFG2-2
(Port-2) 10.0.5.1

iManager U2000
Issue 01 (2010-08-16)
Table 6-24 Configuration parameters of the ATM service on NE1
Parameter Description
Base
Station of
Service
NodeB1 NodeB2
IMA Group IMA1 IMA2
Source Port 1-CXP-1-MD1-1(Trunk1) 1-CXP-1-MD1-2(Trunk2)
Service R99 HSDPA Signalin
g
R99 HSDPA Signaling
Source
VPI/VCI
1/100 1/101 1/102 1/100 1/101 1/102
Sink VPI/
VCI
50/32 51/32 52/32 60/32 61/32 62/32
PW of
Service
PW1 PW2 PW3 PW1 PW2 PW3
PW ID 35 36 37 35 36 37

Table 6-25 lists the planning of the configuration parameters of NE3.
Table 6-25 Configuration parameters of NE2
Parame
ter
Description Description
Service R99 HSDPA Signaling R99 HSDPA Signalin
g
Source
(VPI/
VCI)
50/32 51/32 52/32 60/32 61/32 62/32
Sink
(VPI/
VCI)
50/32 51/32 52/32 60/32 61/32 62/32
PW of
Service
PW1 PW2 PW3 PW1 PW2 PW3
PW ID 35 36 37 35 36 37
Sink
Port
3-MP1-1-AD1-1(1-AD1.PORT-1)

iManager U2000
6-97
This topic describes how to configure an ATM emulation service.
Prerequisite
example.
Procedure
Step 1 Set LSR IDs.
Selection
network.
planning.

Selection
LSR ID 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
Set this parameter
network.
planning.

Step 2 Configure control planes for NEs.
iManager U2000
Issue 01 (2010-08-16)
2. Click the Port Configuration tab and click New. In the dialog box that is displayed, click
Add. Select the 4-EFG2-1(Port-1) and 4-EFG2-2(Port-2) ports and click OK.
Set relevant parameters as follows:
l Link Level: level-1-2
l 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 an LSP, the local
router considers that the LSP is lost or discarded. To ensure the transmission reliability,
the local equipment transmits the LSP again.)
l Minimum LSP Transmission(ms): 30
3. Choose Configuration > Control Plane Configuration > MPLS-LDP Configuration
from the Function Tree.
NOTE
When using a PW to carry services, you need to set the parameters relevant to the MPLS-LDP.
4. Click New. In the Create LDP Peer Entity dialog box, set the LSR ID of the peer end.
Click OK.
l Opposite LSR ID: 1.0.0.3 (The parameter indicates the LSR ID of the terminal NE on
the PW, that is, NE3 in this example.)
l Hello Send Interval(s): 10 (Hello packets are periodically sent to establish the neighbor
relationship.)
l KeepAlive Send Interval(s): 10 (Keepalive packets are periodically sent to maintain the
LDP session.)
5. In the NE Explorer, select NE3 and set the parameters relevant to the control plane. For
details, refer to Step 2.1 through Step 2.4.
The parameters of the IS-IS protocol are set to the same values as those of NE 1. For the
LDP parameters, set the LSR ID to 1.0.0.1.
iManager U2000
6-99
Selection
planning.
planning.
planning.
to be created.

Selection
NE2: Transit
NE3: Egress
node.
is a transit node.
node.

iManager U2000
Issue 01 (2010-08-16)
Selection
Set this parameter
planning.
Tunnels: 10000
Set this parameter
planning.
Tunnels: 10000
Set this parameter
planning.
Tunnels: 20000
Set this parameter
planning.
Tunnels: 20000
Set this parameter
planning.
Tunnels: 1620
Set this parameter
planning.
Tunnels: E-LSP
Tunnels: None
Set this parameter
planning.
l NE1: 4-EFG2-1
l NE2: 1-EX2-1
Reverse Tunnel:
l NE3: 1-EX2-1
l NE2: 3-EG16-1
Set this parameter
planning. Only this
and transit node.
l NE1: 20
l NE2: 30
Reverse Tunnel:
l NE3: 21
l NE2: 31
Set this parameter
planning.
iManager U2000
6-101
Selection
l NE2: 3-EG16-1
l NE3: 1-EX2-1
Reverse Tunnel:
l NE2: 1-EX2-1
l NE1: 4-EFG2-1
Set this parameter
planning. Only this
transit node.
l NE2: 20
l NE3: 30
Reverse Tunnel:
l NE2: 21
l NE1: 31
Set this parameter
planning.
l NE1: 10.0.0.2
l NE2: 10.0.1.2
Reverse Tunnel:
l NE3: 10.0.1.1
l NE2: 10.0.0.1
Set this parameter
planning. Only this
and transit node.

Step 4 Create the protection tunnel.
Selection
planning.
planning.
planning.
to be created.

iManager U2000
Issue 01 (2010-08-16)
Selection
NE3: Egress
node.
nodes.
node.

Step 5 Configure ports, including ATM ports on Node B and RNC.
1. Configure ATM ports on Node B.
a. In the NE Explorer, select NE1 and choose Configuration > Interface
Management > PDH Interface from the Function Tree to configure ports on Node
B.
b. Select the ports from 3-L12-1(Port-1) to 3-L12-8(Port-8). In the Port Mode field,
right-click, and choose Layer 2 from the shortcut menu. Click Apply.
NOTE
Before setting the frame format, ensure that the DCN of the port is disabled.
l Port: ports from 3-L12-1(Port-1) to 3-L12-8(Port-8)
l Name: NodeB ATM (You can set port names to distinguish different service ports
for easy location and query.)
l Port Mode: Layer 2 (IMA signals are carried.)
l Encapsulation Type: ATM
c. On the Advanced tab page, set Frame Format and Frame Mode for the ports from
3-L12-1(Port-1) to 3-L12-8(Port-8). Click Apply.
l Port: ports from 3-L12-1(Port-1) to 3-L12-8(Port-8)
l Frame Format: CRC-4 multiframe (The frame format must be same as the cell
format on Node B.)
iManager U2000
6-103
l Frame Mode: 31
d. Choose Configuration > Interface Management > ATM IMA Management from
the Function Tree. Click the Binding tab.
e. On the Binding tab page, click Configuration. Then, set the bound ports for 1-CXP-1-
MD1-1(Trunk1) and 1-CXP-1-MD1-2(Trunk2). Click OK.
Set the parameters relevant to 1-CXP-1-MD1-1(Trunk1) as follows:
l Available Boards: 1-CXP
l Configurable Ports: 1-CXP-1-MD1-1(Trunk1)
l Level: E1
E1: For the E1 card, when the E1 level is selected, the entire E1 channel is used
to transmit ATM IMA signals.
Fractional E1: For the E1 card, when the fractional E1 level is selected, certain
64 kbit/s timeslots of an E1 channel are used to transmit ATM IMA signals.
For the ATM STM-1 card, when the fractional E1 level is selected, certain 64
kbit/s timeslots of a VC12 lower order path are used to transmit ATM IMA
signals. Before selecting the fractional E1 level, ensure that the serial port for
the 64 kbit/s timeslot is created.
VC12-xv: For the ATM STM-1 card, the VC4 path of an STM-1 contains 63
VC12 lower order paths. When the VC12-xv level is selected, certain VC12
lower order paths of a VC4 path is used to transmit ATM IMA signals.
l Direction: Bidirectional (default)
l Optical Interface: - (In the case of the E1 and fractional E1 levels, you need not
set this parameter. In the case of the VC12-xv level, you need to select the
corresponding optical port, that is, the E1 level in this example.)
l Available Resources: ports from 3-L12-1(Port-1) to 3-L12-4(Port-4)
l Available Timeslots: - (In the case of the E1 and fractional E1 levels, you need not
set this parameter. In the case of the VC12-xv level, you need to select the
corresponding timeslot.)
Set the parameters relevant to 1-CXP-1-MD1-2(Trunk2) as follows:
l Available Boards: 1-CXP
l Configurable Ports: 1-CXP-1-MD1-2(Trunk2)
l Level: E1
l Direction: Bidirectional
l Optical Interface: -
l Available Resources: ports from 3-L12-5(Port-5) to 3-L12-8(Port-8)
l Available Timeslots: -
f. On the IMA Group Management tab page, double-click the IMA Protocol Enable
Status field to enable the IMA protocol. Set other relevant parameters as required.
Click Apply.
The settings of parameters need to be the same as those on Node B.
g. On the ATM Interface Management tab page, set the parameters, such as Max.
VPI and Max. VCI. Click Apply.
iManager U2000
Issue 01 (2010-08-16)
l Port Type: UNI (A UNI port is used to connect to the client-side equipment, and
an NNI port is used to connect the ATM equipment on a core network.)
l ATM Cell Payload Scrambling: Enabled
l Max. VPI: 8 (Set this parameter according to the networking planning. You can
determine the value range of VPIs by setting Max. VPI. The value of the VPI
ranges between 0 and (2
MaxVPIbits
- 1).)
determine the value range of VCIs by setting Max. VCI. The value of the VCI
MaxVCIbits
- 1).)
l VCC-Supported VPI Count: 32 (Set this parameter according to the networking
planning.)
l Loopback: No Loopback
2. Configure ATM ports on RNC.
a. In the NE Explorer, select NE3 and choose Configuration > Interface
Management > SDH Interface from the Function Tree to configure ports on RNC.
b. On the Layer 2 Attributes tab page, select 3-MP1-1-AD1-1(Port-1) and set the
parameters, such as Max. VPI and Max. VCI, for the port. Click Apply.
l Port Type: UNI (A UNI port is used to connect to the client-side equipment, and
an NNI port is used to connect the ATM equipment on a core network.)
l ATM Cell Payload Scrambling: Enabled
determine the value range of VPIs by setting Max. VPI. The value of the VPI
MaxVPIbits
- 1).)
determine the value range of VCIs by setting Max. VCI. The value of the VCI
MaxVCIbits
- 1).)
l VCC-Supported VPI Count: 32 (Set this parameter according to the networking
planning.)
Step 6 Create three UNI-NNI ATM services.
1. Choose Service > PWE3 Service > Create PWE3 Service from the main menu. Create
the R99 service from NE1 to NE3.
iManager U2000
6-105
Selection
Service Type ATM Set this parameter
planning.
entire network.
Service Name ATMService-R99 Set this parameter
planning.
Protection Type Protection-free Set this parameter
planning.
Link Type ATM N-to-1 VCC Cell
Transport
Set this parameter
planning.

Topology in the upper left portion of the window, set NE1 as the source NE, set NE3 as
the sink NE. Set relevant parameters and click OK.
Selection
SAI Type ATM Set this parameter
planning.

Selection
planning.

iManager U2000
Issue 01 (2010-08-16)
Selection
specify a tunnel in
theForward Tunnel
area.
Forward Tunnel area
priority.
Forward Tunnel Tunnel-001 Set this parameter
planning.
priority in the Reverse
Reverse Tunnel Tunnel-001_Reverse Set this parameter
planning.
entire network.
iManager U2000
6-107
Selection
Signaling Type Dynamic This parameter specifies
for a static PW.
planning.

4. Click ATM Link. In the dialog box that is displayed, set the parameters relevant to the
connection.
Table 6-30 Parameter for configuring a connection
Selection
Connection Name Connection1 and
Connection2
Set this parameter
planning.
Role Working Set this parameter
planning.
Source SAI Connection1: NE1-1-
CXP-1-MD1-1(Trunk1)
Connection2: NE1-1-
CXP-1-MD1-2(Trunk2)
Set this parameter
planning.
Source VPI Connection1: 1
Connection2: 1
VPI information carried by
the service from a base
station.
Source VCI Connection1: 100
Connection2: 100
VCI information carried by
station.
iManager U2000
Issue 01 (2010-08-16)
Selection
Source ATM Policy Connection1: RT-VBR
Connection2: RT-VBR
Connection1 is an R99
service and you need to
select the RT-VBR policy
for it.
for it.
Sink SAI Connection1: NE3-3-
MP1-1-AD1-1(Port-1)
Connection2: NE3-3-
MP1-1-AD1-1(Port-1)
Set this parameter
planning.
Sink VPI Connection1: 50
Connection2: 60
the service after a VPI
switching. Max. VPI of an
ATM port is 255 according
to the planning and thus the
value of the VPI on the sink
ranges between 0 and 255.
Sink VCI Connection1: 32
Connection2: 32
the service after a VCI
switching. Max. VCI of an
Sink ATM Policy Connection1: RT-VBR
Connection2: RT-VBR
for it.
for it.
Transit VPI - Set this parameter
planning.
Transit VCI - Set this parameter
planning.

5. Click Advanced and configure PW QoS and Advanced PW Attribute.
iManager U2000
6-109
Selection
Control Word Must use On an MPLS PSN network,
control word is the
bit stuffing.
Control Channel Type CW A CW control word is used
to detect the connectivity of
a PW.
Source ATM CoS Map 1(mapping1) Set this parameter
planning.
Sink ATM CoS Map 1(mapping1) Set this parameter
planning.
Max. Concatenated Cells
Count
10 Maximum number of ATM
cells that can be
encapsulated into a packet.
Packet Loading Time (us) 1000 Set this parameter
planning.

Table 6-32 PW QoS parameters
Selection
Bandwidth Limited Enabled Set this parameter
planning.
CIR (kbit/s) 30000 Set the bandwidth based on
the service traffic.
PIR (kbit/s) 50000 Set the bandwidth based on
iManager U2000
Issue 01 (2010-08-16)
Selection
EXP 1 Set this parameter
planning.

6. Click OK. The ATMService-R99 service is created successfully.
7. Create the ATMService-HSDPA service. For details, refer to the preceding steps.
Selection
planning.
entire network.
Service Name ATMService-HSDPA Set this parameter
planning.
planning.
Transport
Set this parameter
planning.

Selection
planning.

Selection
planning.
iManager U2000
6-111

Selection
specify a tunnel in
theForward Tunnel
area.
Forward Tunnel area
priority.
planning.
planning.
entire network.
iManager U2000
Issue 01 (2010-08-16)
Selection
for a static PW.
planning.

Selection
Connection2
Set this parameter
planning.
planning.
Source SAP Connection1: NE1-1-
CXP-1-MD1-1(Trunk1)
Connection2: NE1-1-
CXP-1-MD1-2(Trunk2)
Set this parameter
planning.
Connection2: 1
station.
Connection2: 101
station.
Source ATM Policy Connection1: UBR
(policy)
Connection2: UBR
(policy)
Connection1 is an HSDPA
select the UBR policy for it.
iManager U2000
6-113
Selection
Sink SAP Connection1: NE1-3-
MP1-1-AD1-1(1-
AD1.PORT-1)
Connection2: NE1-3-
MP1-1-AD1-1(1-
AD1.PORT-1)
Set this parameter
planning.
Connection2: 61
Connection2: 32
Sink ATM Policy Connection1: UBR
(policy)
Connection2: UBR
(policy)
planning.
planning.

iManager U2000
Issue 01 (2010-08-16)
Selection
control word is the
bit stuffing.
a PW.
planning.
planning.
Count
cells that can be
planning.

Selection
planning.
iManager U2000
6-115
Selection
planning.

8. Create the ATMService-Signaling service. For details, refer to the preceding steps.
Selection
planning.
entire network.
Service Name ATMService-Signaling Set this parameter
planning.
planning.
Transport
Set this parameter
planning.

Selection
planning.

Selection
planning.
iManager U2000
Issue 01 (2010-08-16)

Selection
specify a tunnel in
theForward Tunnel
area.
Forward Tunnel area
priority.
planning.
planning.
entire network.
iManager U2000
6-117
Selection
for a static PW.
planning.

Selection
Connection2
Set this parameter
planning.
planning.
Source SAP Connection1: NE1-1-
CXP-1-MD1-1(Trunk1)
Connection2: NE1-1-
CXP-1-MD1-2(Trunk2)
Set this parameter
planning.
Connection2: 1
station.
Connection2: 102
station.
Source ATM Policy Connection1: CBR (policy)
Connection2: CBR (policy)
Connection1 is a signaling
select the CBR policy for it.
iManager U2000
Issue 01 (2010-08-16)
Selection
Sink SAP Connection1: NE1-3-
MP1-1-AD1-1(1-
AD1.PORT-1)
Connection2: NE1-3-
MP1-1-AD1-1(1-
AD1.PORT-1)
Set this parameter
planning.
Connection2: 62
Connection2: 32
Sink ATM Policy Connection1: CBR (policy)
Connection2: CBR (policy)
planning.
planning.

iManager U2000
6-119
Selection
control word is the
bit stuffing.
a PW.
planning.
planning.
Count
cells that can be
planning.

Selection
planning.
iManager U2000
Issue 01 (2010-08-16)
Selection
planning.

----End
6.7.3 Example for Configuring an Ethernet Private Line Service
This topic describes the example of configuring an Ethernet private line service. Specifically,
the example description, service planning, and configuration process are provided.
Example Description
As shown in Figure 6-37, both company A and company B have branches in city 1 and city 2.
Branches of each company need to communicate with each other. Services from the two
companies must be isolated. NE1 is connected to company A and Company B in city 1 and NE3
is connected to company A and Company B in city 2. NE1 accesses services from city 1, NE2
transparently transmits the services, and NE3 transmits the services to city 2. Similarly, NE3
accesses services from city 2, NE2 transparently transmits the services, and NE1 transmits the
services to city 1.
You can configure Ethernet private line services to meet the requirements of communication
between the branches of company A and between the branches of company B. Two PWs carry
the services of company A and company B respectively and share bandwidth of a same tunnel.
In the case of Company A, the branches require the common Internet access service, CIR=10
Mbit/s, PIR=30 Mbit/s, VLAN ID=100.
In the case of Company B, the branches require the data service, CIR=30 Mbit/s, PIR=50 Mbit/
s, VLAN ID=200.
NE1 is the OptiX PTN 1900; NE2 and NE3 are the OptiX PTN 3900.
Figure 6-37 Network of the Ethernet private line service
NE1
NE2
NE3
NE4
NE5
Access
Layer
10 GE Ring On
Convergence Layer
Compnay A
Compnay B
3-EFF8-1Port-1
3-EFF8-2Port-2
20-EFF8-1Port-1
10.0.0.2
5-EX2-1Port-1
10.0.1.1
5-EX2-1Port-1
10.0.1.2
20-EFF8-2Port-2
3-EFF8-3Port-3
10.0.0.1
Compnay B
Compnay A
20-EFF8-1Port-1
iManager U2000
6-121

Service Planning
Table 6-47 lists the planning details of NE parameters.
NE LSR
ID
Port Port Attribute Port IP
Address
Mask
NE1 1.0.0.1
3-EFF8-1(Port-1) Port Mode: Layer 2
TAG: Tag Aware
- -
TAG: Tag Aware
- -
3-EFF8-3(Port-3) Port Mode: Layer 3 10.0.0.1 255.255.255.
252
NE2 1.0.0.2
20-EFF8-1(Port-1) Port Mode: Layer 3 10.0.0.2 255.255.255.
252
5-EX2-1(Port-1) Port Mode: Layer 3 10.0.1.1 255.255.255.
252
NE3 1.0.0.3
TAG: Tag Aware
- -
TAG: Tag Aware
- -
5-EX2-1(Port-1) Port Mode: Layer 3 10.0.1.2 255.255.255.
252

Table 6-48 lists the planning details of the tunnel that carries a PW.
Table 6-48 Planning of the tunnel carrying the PW
Parameter Forward Tunnel Reverse Tunnel
Tunnel ID 1 2
Tunnel Name Tunnel-0001 Tunnel-0001_Reverse
Signaling Type Dynamic Dynamic
LSP Type E-LSP E-LSP
Bandwidth(Kbit/s) 80 Mbit/s 80 Mbit/s
iManager U2000
Issue 01 (2010-08-16)
Parameter Forward Tunnel Reverse Tunnel
Source Node NE1 NE3
Sink Node NE3 NE1
Route Constraint
Port IP Address
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
IP address of the ingress port of
NE2:
5-EX2-1: 10.0.1.1
IP address of the ingress port of
NE1:
3-EFF8-3: 10.0.0.1

Table 6-49 lists the planning details of the Ethernet service.
Table 6-49 Planning of the UNI-NNI E-Line service carried by the PW
Parameter Company A Company B
Service ID 1 2
Service Name E-Line-1 E-Line-2
Service Direction UNI-NNI UNI-NNI
UNI 3-EFF81(Port-1) 3-EFF8-2(Port-2)
VLANs 100 200
Bearer Type PW PW
Protection Type Protection-Free Protection-Free
BPDU Non-transparent
transmission
Non-transparent
transmission
MTU(byte) 1526 1526
Service Tag User User

Table 6-50 lists the planning details of a PW.
Table 6-50 Planning of the PW
Parameter PW of Company A PW of Company B
PW ID 35 45
PW Signaling Type Static Static
PW Type Ethernet Ethernet
Direction Bidirectional Bidirectional
iManager U2000
6-123
Parameter PW of Company A PW of Company B
PW Ingress Label 20 30
PW Egress Label 20 30
Opposite LSR ID 1.0.0.3 1.0.0.3
Tunnel 1(E-Line) 1(E-Line)
Bandwidth Limit Enabled Enabled
CIR (kbit/s) 10000 30000
PIR (kbit/s) 30000 50000

This topic describes how to configure an Ethernet private line emulation service.
Prerequisite
example.
Procedure
Step 1 Set LSR IDs for NEs.
2. Set the parameters, such as LSR ID and Start of Global Label Space, for the NE. Click
Apply.
Selection
network.
planning.

3. Display the NE Explorers of NE2 and NE3 and perform the preceding two steps to set the
parameters, such as the LSR ID.
iManager U2000
Issue 01 (2010-08-16)
Selection
LSR ID NE2: 1.0.0.2
NE3: 1.0.0.3
Set this parameter
network.
planning.

Step 2 Configure ports.
1. In the NE Explorer, select NE1 and choose Configuration > Interface Management >
Ethernet Interface from the Function Tree to configure ports.
2. On the General Attributes tab page, select 3-EFF8-1(Port-1), 3-EFF8-2(Port-2), and 3-
EFF8-3(Port-3) and set the parameters, such as Port Mode and Working Mode, for those
ports. Click Apply.
l Port: 3-EFF8-1(Port-1) and 3-EFF8-2(Port-2)
Enable Port: Enabled
Port Mode: Layer 2 (UNI port for accessing services of company A and company
B.)
Encapsulation Type: 802.1Q
Working Mode: Auto-Negotiation
Max Frame Length: 1620
l Port: 3-EFF8-3(Port-3)
Port Mode: Layer 3 (NNI port for carrying tunnels)
Max Frame Length(byte): 1620
3. On the Layer3 Attributes tab page, select 3-EFF8-3(Port-3). In the Enable Tunnel field,
right-click, and choose Enabled from the shortcut menu. In the Specify IP Address field,
right-click, and choose Manually from the shortcut menu. Set the parameters, such as IP
Address and IP Mask. Click Apply.
l Enable Tunnel: Enabled
l 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 a link. The smaller the value of the TE measurement, the higher the
priority of the link is.)
l Specify IP Address: Manually (You can set the IP address for a port when Manually
is selected.)
iManager U2000
6-125
l IP Address: 10.0.0.1
l IP Mask: 255.255.255.252
4. Display the NE Explorers of NE2 and NE3 and set the parameters relevant to each port.
For details, refer to Step 2.1 through Step 2.3.
l NE2
General Attributes
Port: 20-EFF8-1(Port-1), 5-EX2-1(Port-1)
Working Mode: Auto-Negotiation (The working mode of this port must be set
to the same value as that of the interconnected port.)
Max Frame Length (byte): 1620 (Set this parameter according to the lengths of
data packets. All received data packets whose lengths are greater than the
parameter value are discarded.)
Layer 3 Attributes
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 a link. The smaller the value of the TE
measurement, the higher the priority of the link is.)
Specify IP Address: Manually (You can set the IP address for a port when
Manually is selected.)
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
l NE3
General Attributes
Port: 20-EFF8-1(Port-1), 20-EFF8-2(Port-2)
Port Mode: Layer 2 (UNI port for accessing services of company A and
company B.)
Encapsulation Type: 802.1Q
Max Frame Length: 1620
Port: 5-EX2-1(Port-1)
Max Frame Length(byte): 1620
Layer 3 Attributes
iManager U2000
Issue 01 (2010-08-16)
Port: 5-EX2-1(Port-1)
TE Measurement: 10
Specify IP Address: Manually
IP Address: 10.0.1.2
IP Mask: 255.255.255.252
Add. Select the 3-EFF8-3(Port-3) port and click OK.
l Link Level: level-1-2
l 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 an LSP, the local
router 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. Display the NE Explorers of NE2 and NE3 and set the parameters relevant to the control
planes. For details, refer to Step 3.1 through Step 3.2. The settings of the IS-IS protocol
for NE3 are the same as those for NE1.
Step 4 Create a tunnel.
2. Set the parameters for a tunnel. For configuration details, refer to 3.3.1 Creating a
Tunnel.
Selection
Tunnel Name Tunnel-0001(Positive),
Tunnel-0001_Reverse
(Reverse)
Set this parameter
planning.
Protocol Type MPLS A service ID uniquely
entire network.
iManager U2000
6-127
Selection
Signaling Type RSVP TE When the signal type is set
to RSVP TE, labels are
distributed by using the
LSP signaling and the
tunnel is of the dynamic
type. When the signal type
is set to static, you need to
manually attach labels and
the tunnel is of the static
type.
Create Reverse Tunnel Checked The positive and reverse
tunnels are created at the
same time.
NE NE1 and NE3 Set this parameter
planning.
LSR ID NE1: 1.0.0.1
NE3: 1.0.0.3
Set this parameter
planning.
NE3: Egress
Set this parameter
planning.
Bandwidth(Kbit/s) 80000 Set this parameter
planning.
Color(0x) 0 Set the link affinity
attribute of a link. When an
active tunnel is faulty, the
links with the same route
color are preferred during a
rerouting. When there is no
restriction on the link
affinity attribute, it is
recommended that you use
the default value.
Mask(0x) 0 Set the link affinity
attribute of a link. When an
active tunnel is faulty, the
links with the same route
color are preferred during a
rerouting. When there is no
restriction on the link
affinity attribute, it is
the default value.
iManager U2000
Issue 01 (2010-08-16)
Selection
LSP Type E-LSP E-LSP indicates that a
tunnel determines the
scheduling priority and
discard priority of packets
according to the EXP
information. In one MPLS
tunnel of the E-LSP type,
there can be a maximum of
eight types of PWs.
L-LSP indicates that a
tunnel determines the
scheduling policy of
packets according to the
MPLS labels and
determines the discard
policy of packets according
to the EXP information. In
one MPLS tunnel of the L-
LSP type, there is only one
type of PWs. Currently, the
OptiX PTN equipment does
not support the L-LSP type.
EXP None Priority of a tunnel.
IP Address Positive: 10.0.0.2, 10.0.1.2
Reverse: 10.0.1.1, 10.0.0.1
Set this parameter
planning.
Hop Type Strictly include Set this parameter
planning.
Setup Priority 7 Priority specified for a
dynamic MPLS tunnel
during the creation of the
tunnel. 0 indicates the
highest priority. The tunnel
of higher setup priority can
preempt the bandwidth
resources of other tunnels
when the resources are
insufficient.
iManager U2000
6-129
Selection
Hold Priority 0 Priority used by a dynamic
MPLS tunnel after the
creation of the tunnel. 0
indicates the highest
priority. When resources
are insufficient, it is of the
low probability that the
bandwidth resources of a
tunnel of higher hold
priority are preempted by
other tunnels. The hold
priority of a tunnel should
be higher than or equal to
the corresponding setup
priority.

3. Click OK. The tunnel is created successfully.
Step 5 Configure an Ethernet private line (EPL) service.
2. Set the parameters of the E-Line-1 Ethernet service.
Selection
Service Type ETH Set this parameter
planning.
entire network.
Service Name E-Line-1 Set this parameter
planning.
iManager U2000
Issue 01 (2010-08-16)
Selection
planning.

Topology in the upper left portion of the window, set NE1-3-EFF8-1 as the source NE,
NE3-20-EFF8-1 as the sink NE. Set relevant parameters and click OK.
Table 6-53 Parameters of the source and sink node
Selection
SAI Type ETH Set this parameter
planning.
Connect Type VLAN Set this parameter
planning.
VLAN ID NE1-3-EFF8-1:100
NE3-20-EFF8-1:200
Set this parameter
planning.

iManager U2000
6-131
Selection
specify a tunnel in
theForward Tunnel
area.
Forward Tunnel area
priority.
Forward Tunnel Tunnel-0001(Positive) Set this parameter
planning.
Reverse Tunnel Tunnel-0001_Reverse
(Reverse)
Set this parameter
planning.
entire network.
iManager U2000
Issue 01 (2010-08-16)
Selection
for a static PW.
header when an Ethernet
frame is encapsulated into a
PW. An Forward Label is
used for label switching.
to the packet header when
an Ethernet frame is
encapsulated into a PW. A
Reverse Label is used for
label switching.
planning.

5. Click Advanced and configure SAI QoS, PW QoS, Advanced PW Attributes, and
Service parameter. Use the default value for SAI QoS.
Table 6-55 QoS parameters
Selection
planning.
Default Forwarding
Priority
BE
iManager U2000
6-133
Selection
Default Packet Re-Marking
Color
Yellow

Selection
planning.
planning.
LSP Mode Uniform The CoS of user packets
needs to be restored when
the tunnel labels are
stripped.

Selection
PW Type Ethernet Set this parameter
planning.
Control Word No Use On an MPLS PSN network,
control word is the
bit stuffing.
iManager U2000
Issue 01 (2010-08-16)
Selection
a PW.

6. Click OK. The E-Line-1 Ethernet service is created.
7. Create the E-Line-2 Ethernet service. For details, refer to the preceding steps.
Selection
Service Type ETH Set this parameter
planning.
entire network.
Service Name E-Line-2 Set this parameter
planning.
planning.

Table 6-59 Parameters of the source and sink node
Selection
SAI Type ETH Set this parameter
planning.
Connect Type VLAN Set this parameter
planning.
VLAN ID NE1-3-EFF8-2:200
NE3-20-EFF8-2:100
Set this parameter
planning.

iManager U2000
6-135
Selection
specify a tunnel in
theForward Tunnel
area.
Forward Tunnel area
priority.
Forward Tunnel Tunnel-0001(Positive) Set this parameter
planning.
Reverse Tunnel Tunnel-0001_Reverse
(Reverse)
Set this parameter
planning.
entire network.
iManager U2000
Issue 01 (2010-08-16)
Selection
for a static PW.
header when an Ethernet
frame is encapsulated into a
PW. An Forward Label is
used for label switching.
to the packet header when
an Ethernet frame is
encapsulated into a PW. A
Reverse Label is used for
label switching.
planning.

Table 6-61 Service parameters
Selection
MTU(byte) 1526 Set this parameter
planning.
BPDU Not Transparently
Transmitted
Set this parameter
planning.
Service Tag User Set this parameter
planning.

iManager U2000
6-137
Selection
planning.
Default Forwarding
Priority
BE
Default Packet Re-Marking
Color
Yellow

Selection
planning.
planning.
LSP Mode Uniform The CoS of user packets
needs to be restored when
the tunnel labels are
stripped.

iManager U2000
Issue 01 (2010-08-16)
Selection
PW Type Ethernet Set this parameter
planning.
Control Word Must Use On an MPLS PSN network,
control word is the
bit stuffing.
a PW.

----End
6.7.4 Example of Configuring an End-to-End IP Line Service
This section describes an example of configuring an end-to-end IP line service and provides a
flowchart to illustrate the service configuration process. The configuration example involves
networking, service planning, and service configuration.
Example Description
This section describes the function requirement, network diagram, and service planning of an
example.
Requirement and Network Diagram
The IP line solution needs to be adopted to achieve IP access based on the capabilities of the
access equipment at the edge of a PTN network.
Figure 6-38 shows deployment of an IP line service. NE1 is an OptiX PTN 1900 NE and NE2
is an OptiX PTN 3900 NE.
A Layer 3 virtual port needs to be created on NE2, and this port serves as the sink port for the
IP line service.
A VRF needs to be configured on NE2. The IP line service corresponds to a VRF UNI port on
NE2. This UNI port serves as one VRF UNI port on NE2. Port 1-EG16-2 on NE2, which is
directly connected to the RNC, needs to be configured as another VRF UNI port. In this manner,
iManager U2000
6-139
IP packets from the NodeB travel through the IP line, NE2, and finally reaches the RNC through
the VRF.
Figure 6-38 Network where an IP line service is deployed
RNC
IP-LINE 1
Node B
NE1 NE2
L3 Virtual Interface
IP:10.1.3.1
4-EG2-1
10.1.1.2
1-EG16-1
10.1.1.1
Interface IP:10.1.3.2
VRF
1-EG16-2
UNI UNI
Service IP:10.10.1.1

NOTE
A VRF instance synchronizes route information. NE2 does not store the IP address of NodeB (the IP line
is static and no protocol synchronizes routes), and thus the DIP with the packets sent to the RNC is the IP
address of NodeB.
To ensure that the packets are sent from the RNC to NodeB, the IP address of the UNI port on NE2 and
the port IP address of the NodeB must be in the same network segment. Note that a NodeB may have two
IP addresses, that is, service IP address and port IP address.
The IP address of the Layer 3 virtual port and the IP address of NodeB must be in the same network segment.
NOTE
Service configuration on the OptiX PTN 3900-8 is the same as that on the OptiX PTN 3900, except for the
slots for service boards. For details on service configuration on the OptiX PTN 3900-8, see this example
about service configuration on the OptiX PTN 3900.
Service Planning
Table 6-65 lists the planning of parameters for NEs.
Table 6-65 Planning of parameters for NEs
NE LSR ID Port Port IP Address Port Subnet
Mask
NE1 1.1.1.1 4-EG2-1 (Port-1) 10.1.1.2 255.255.255.252
NE2 1.1.1.2
1-EG16-1(port-1) 10.1.1.1 255.255.255.252
1-EG16-2(port-2) 10.1.2.2 255.255.255.252
10(Vinter01) 10.1.3.1 255.255.255.0

Table 6-66 lists the planning of bearer tunnels for the PWs.
iManager U2000
Issue 01 (2010-08-16)
Table 6-66 Planning of bearer tunnels for the PWs
Paramet
er
Forward Tunnel Reverse Tunnel
Tunnel ID 01 01
Tunnel
Name
Tunnel01 Tunnel01
Signaling Static CR Static CR
LSP Type E-LSP E-LSP
Bandwidt
h(Kbit/s)
No Limit No Limit
Ingress
Node
NE1 NE2
Transit
Node
None. None.
Egress
Node
NE2 NE1
Ingress
Node
NE1:
l Egress Port: 4-EFG2-1
l Egress Label: 20
l Next Hop IP Address: 10.1.1.1
NE2:
l Egress Port: 1-EX16-1
l Egress Label: 30
l Next Hop IP Address: 10.1.1.2
Egress
Node
NE2:
l Ingress Port: 1-EX16-1
l Ingress Label: 20
NE1:
l Ingress Port: 4-EFG2-1
l Ingress Label: 30

Table 6-67 VRF configuration planning
Service Information Service Name L3VPN01
Service Template Full-Mesh
VRF ID 1
VRF Name VRF01
RD 100:1
RT 100:1
IP DSCP Pass Through Not supported
Node List Node Name NE2
iManager U2000
6-141
Node IP Address NE2: 1.1.1.2
SAI Interface Name NE2: 1-EG16-2
IP AdInterface Namedress/
Mask
NE2: 10.1.2.2/30
Interface Name NE2: 10(Vinter01)
IP Address/Mask NE2: 10.1.3.1/24
Static Route Destination IP Address Node B Service IP: 10.10.1.1
Mask 255.255.255.252
Outbound Interface NE2: 10(Vinter01)
Next Hop IP Address Node B Interface IP: 10.1.3.2
Priority Default: 60

Table 6-68 PW configuration planning
PW ID Automatically Allocated
Forward Type/Reverse Type Static Binding
Forward Tunnel/Reverse Tunnel Tunnel01/Tunnel01 Reverse
Signaling Type Dynamic
Forward Label 20
Reverse Label 30
Encapsulation MPLS

This section describes how to configure an end-to-end IP line service.
Prerequisite
If an MPLS tunnel is used to carry services, you need to crate a static MPLS tunnel. .
If an IP/GER tunnel is used to carry services, you need to create an IP/GRE tunnel..
If you need to use a UNI port exclusively, disable the DCN function at the port. .
iManager U2000
Issue 01 (2010-08-16)
Procedure
1. Navigate to the NE Explorer of NE1, and choose Configuration > MPLS Management
> Basic Configuration from the Function Tree.
2. Set parameters such as LSR ID and Start of Global Label Space for NE1. Then, click
Apply.
Parameter Value (for This
Example)
Setting Rule
LSR ID NE1: 1.1.1.1 An LSR ID must be unique
on the entire network. Set
this parameter according to
network planning.
according to network
planning.

3. Navigate to the NE Explorer of NE2 and repeat the preceding steps to set parameters
(including LSR ID) for NE2.
Example)
Setting Rule
LSR ID NE2: 1.1.1.2 An LSR ID must be unique
on the entire network. Set
network planning.
planning.

Step 2 Configure ports.
1. In the NE Explorer, click NE1 and choose Configuration > Interface Management >
Ethernet Interface from the Function Tree.
2. Click the General Attributes tab, select 4-EG2-1(Port-1), 4-EG2-2(Port-2), and then set
parameters such as Port Mode and Working Mode. Click Apply.
Set the related parameters as follows:
l Port: 4-EG2-2 (Port-2)
Port Mode: Layer 3 (UNI, for access to NodeB)
Max Frame Length (byte): 1620
l Port: 4-EG2-1 (Port-1)
iManager U2000
6-143
Port Mode: Layer 3 (NNI, for carrying a tunnel)
Max Frame Length (byte): 1620
3. Click the Layer 3 Attributes tab, select 4-EG2-1(Port-1), right-click the Tunnel Enabling
Status field, and then choose Enabled. Right-click the Specify IP field and choose
Manually. Then, set parameters such as IP Address and IP Mask. Click Apply.
l Enable Tunnel: Enabled
l TE Measurement: 10 (This parameter indicates link cost. A link with less link cost is
selected for a tunnel with preference. You can intervene in route selection by adjusting
TE measurement. A smaller TE measurement value indicates a higher priority.)
l Specify IP Address: Manually (When you set this parameter to Manually, you can set
an IP address for the port.)
l IP Address: 10.1.1.2
l IP Mask: 255.255.255.252
4. Navigate to the NE Explorer of NE2 and set the parameters related to the NNI port with
reference to Step 2.1 to Step 2.3.
Set the related parameters as follows:
l NE2
Port: 1-EG16-1 (Port-1)
General attributes
Port: 1-EG16-1 (Port-1)
Port Mode: Layer 3 (NNI, for carrying a tunnel)
Working Mode: Auto-Negotiation (The working modes of the local port and
opposite port must be the same.)
Max Frame Length (byte): 1620 (Set this parameter according to the length of
service data packets. All the received packets with a length exceeding the
maximum frame length are discarded.)
Layer 3 attributes
TE Measurement: 10 (This parameter indicates link cost. A link with less link
cost is selected for a tunnel with preference. You can intervene in route selection
by adjusting TE measurement. A smaller TE measurement value indicates a
higher priority.)
Specify IP Address: Manually (When you set this parameter to Manually, you
can set an IP address for the port.)
IP Address: 10.1.1.1
IP Mask: 255.255.255.252
Step 3 Create a static MPLS tunnel.
2. Set general parameters for the static tunnel.
iManager U2000
Issue 01 (2010-08-16)
l For this example, set Protocol Type to MPLS. When you set Protocol Type to IP,
Signaling Type and Template are unavailable.
l For this example, set Signaling Type to Static CR.
l For this example, select only Create Reverse Tunnel. When you select Create Reverse
Tunnel, a forward tunnel and a reverse tunnel are created. Otherwise, only a forward
tunnel is created. When you select Create Bidirectional Tunnel, a bidirectional tunnel
is created. When you select Create Protection, a protection tunnel is also created.
l
NOTE
he OptiX PTN equipment supports only static constraint-based routing (CR) tunnels. A static CR
tunnel is based on certain constraints, which are established and managed through the CR
mechanism. Unlike a static tunnel, a static CR tunnel can be created when the routing information
is available and certain constraints, such as specified bandwidth, selected path, and QoS
parameters, are met. When you set Signaling Type to Static CR, you can select Create Reverse
Tunnel. When you set Signaling Type to RSVP TE, you can set Template to copy tunnel details
from a template.
l For this example, select only Create Reverse Tunnel. When you select Create Reverse
Tunnel, a forward tunnel and a reverse tunnel are created. Otherwise, only a forward
tunnel is created. When you select Create Bidirectional Tunnel, a bidirectional tunnel
is created. When you select Create Protection, a protection tunnel is also created.
Table 6-69 Parameter settings for a static tunnel
Example)
Setting Rule
Tunnel ID l Forward Tunnel:
Tunnel - 01
l Reverse Tunnel:
Tunnel - 02
Set this parameter according to
service planning.
Bandwidth(Kbit/s) Forward Tunnel or
Reverse Tunnel:
10000
service planning.
CBS(byte) Forward Tunnel or
Reverse Tunnel:
10000
service planning.
PIR(Kbit/s) Forward Tunnel or
Reverse Tunnel:
20000
service planning.
PBS(byte) Forward Tunnel or
Reverse Tunnel:
20000
service planning.
MTU Forward Tunnel or
Reverse Tunnel:
2000
service planning.
LSP Type Forward Tunnel or
Reverse Tunnel: E-
LSP
Currently, only E-LSPs are
supported.
iManager U2000
6-145
Example)
Setting Rule
EXP Forward Tunnel or
Reverse Tunnel:
None
network planning.
Out Interface Forward Tunnel
l NE1: 4-EG2-1
Reverse Tunnel
l NE2: 1-EG16-1
Set egress ports according to
service planning. You need to set
egress ports only for the ingress
node and transit nodes.
Out Label Forward Tunnel
l NE1: 20
Reverse Tunnel
l NE2:30
Set the parameters according to
service planning.
In Interface Forward Tunnel
l NE2: 3-EG16-1
Reverse Tunnel
l NE1: 4-EG2-1
Set ingress ports according to
service planning. You need to set
ingress ports only for the egress
node and transit nodes.
In Label Forward Tunnel
l NE2:20
Reverse Tunnel
l NE1:30
network planning.
Next Hop Forward Tunnel
l NE1:10.1.1.1
Reverse Tunnel
l NE2:10.1.1.2
network planning.

3. Click OK. Then, creating a static tunnel is complete.
Step 4 Create a Layer 3 virtual port.
1. In the NE Explorer, click NE2 and choose ConfigurationInterface ManagementEthernet
Virtual Interface from the Function Tree.
2. Click the General Attributes tab and then choose New > Create Ethernet L3 Virtual
Interface to display the Create Ethernet L3 Virtual Interface dialog box.
3. In the Create Ethernet L3 Virtual Interface dialog box, set the related parameters.
iManager U2000
Issue 01 (2010-08-16)
Step 5 Set parameters associated with the VRF on NE2.
Configure a Layer 3 virtual port as a VRF UNI port and port 1-EG16-2 on NE2, which is directly
connected to the RNC, as another VRF UNI port.
1. Choose Service > L3VPN Service > Create L3VPN Service from the Main Menu.
2. Set service parameters.
iManager U2000
6-147
Table 6-70 Service parameter settings
Example)
Setting Rule
Service Name L3VPN01 Set this parameter
according to service
planning.
Service Template Full-Mesh Set this parameter
planning.
VRF ID 1 Set this parameter
planning.
VRF Name VRF01 Set this parameter
planning.
RD 100:1 Set this parameter
planning.
RT 100:1 Set this parameter
planning.

3. Add NE2 where a service is to be created to NE List. You can also right-click NE2 in
Physical Topology and choose Add NE to Service.
4. In VRF Configuration, select General to set basic attributes of VRF.
Table 6-71 General attributes of VRF
Example)
Setting Rule
VRF Name VRF01 Set this parameter
planning.
planning.
Import RT VRF01: 100:1 Set this parameter
planning.
Export RT VRF01: 100:1 Set this parameter
planning.
iManager U2000
Issue 01 (2010-08-16)
Example)
Setting Rule
IP DSCP Pass Through NO Set this parameter
planning.

5. In VRF Configuration, select SAI to configure a service access interface.
Table 6-72 Service access interface
Example)
Setting Rule
Interface Name 10(Vinter01) Set this parameter to the
Layer 3 virtual port on the
sink NE of the IP line
service.
IP Address/Mask 10.1.3.1 Set this parameter
planning.
Interface Name 1-EG16-2 Set this parameter to a
Layer 3 port connected to
the RNC.
IP Address/Mask 10.1.2.2 Set this parameter
planning.

6. In VRF Configuration, choose Router Configuration > Static Router > Static Router
Object, and set static router objects.
iManager U2000
6-149
Table 6-73 Route configuration
Example)
Setting Rule
Destination 10.10.1.1 Set this parameter
planning.
Mask 255.255.255.252 Set this parameter
planning.
Outbound Interface 10(Vinter01) Set this parameter
planning.
planning.
Priority 60 When multiple routes are
configured, routes are
selected according to their
priorities.
Track Event Type - Set this parameter
planning.
BFD Index - Set this parameter
planning.
iManager U2000
Issue 01 (2010-08-16)
Example)
Setting Rule
VRRP ID - Set this parameter
planning.

Step 6 Configure an IP line service.
1. Choose Service > PWE3 Service > Create PWE3 Service from the Main Menu.
2. Set parameters on the Attribute tab.
l Set Service Type to IP E-line.
l For details on how set Protection Type, see PW Protection.
l Service ID is set to Auto-Assign by default. You can also specify a number in the range
of 1 to 4294967295 for Service ID.
l Set Service Name according to service planning. If you do not set Service Name, the
IP line service is automatically named when the configuration is complete.
l Protection Type is set to Protection-Free by default. When dual-homing protection is
required for the IP line service, select PW redundancy.
3. Configure the source node and sink node for the IP line service. Click Configure Source
And Sink to display the Configure Source and Sink Node dialog box. In the navigation
tree on the left, select the source NE; in the pane on the right, select the port. Then, set
Role to Source or Sink for the port. When the setting is complete, click OK.
NOTE
The sink port of an IP line service must be a virtual IP port, that is, a Layer 3 virtual port.
4. Configure a PW. Click the PW tab and set general attributes of the PW.
l PW ID can be Automatically Allocated. The PW ID is networkwide unique. That is,
one PW ID indicates only one PW.
l Set Forward Type and Reverse Type to Static Binding.
l Select a created forward tunnel for Forward Tunnel.
l Select a created reverse tunnel for Reverse Tunnel.
l Set Signaling Type to Dynamic.
NOTE
In the case of an IP line service, only Dynamic signaling is supported.
l Set Forward Label to 20.
l Set Reverse Label to 30.
NOTE
Forward Label and Reverse Label are stuck to packet headers when IP packets are encapsulated
to PWs. These labels are used for label switching.
l Set Encapsulation to MPLS.
5. Apply the service configuration to NEs. Click Deploy to apply the service configuration
to NEs and also select Enable to provision the service.
6. Click Advanced and then set SAI QoS, PW QoS, and Advanced PW Attribute.
iManager U2000
6-151
Table 6-74 QoS parameter settings for the service access port
Example)
Setting Rule
Bandwidth Limited Enabled It is recommended to set
network planning.
CIR (kbit/s) 10000 Set bandwidth according to
service traffic.
PIR (kbit/s) 30000 Set bandwidth according to
service traffic.

Table 6-75 PW QoS parameter settings
Example)
Setting Rule
EXP 4 It is recommended to set
network planning.
LSP Mode Uniform The CoS of user packets is
restored when the tunnel
label is stripped.

----End
iManager U2000
Issue 01 (2010-08-16)
7 Managing VPLS Services
About This Chapter
This topic describes how to configure VPLS services.
7.1 VPLS Overview
When configuring VPLS services, you need to learn the protocols relevant to the VPLS services
and the application scenarios of these protocols.
7.2 Configuration Flow for a VPLS Service
The configuration flow of the VPLS service includes creating networks, configuring the LSR
ID, configuring QoS policies, configuring interfaces, configuring the control plane, configuring
MPLS tunnel, and configuring VPLS service.
7.3 VPLS Operation Tasks
This topic describes the VPLS operation tasks, which includes creating and deploying a VPLS
service and adjusting VSI resource.
7.4 Monitoring a VPLS Service
This topic describes how to monitor a VPLS service.
7.5 Managing VPLS Service Authority
This topic describes how to manage the VPLS service authority.
7.6 Configuration Case of the VPLS Service
This section describes a configuration example of the VPLS service. A configuration flow
diagram is provided to describe the process of service configuration. The configuration example
includes the service planning and VPLS service configuration.
iManager U2000
Operation Guide for PTN End-to-End Management 7 Managing VPLS Services
7-1
7.1 VPLS Overview
When configuring VPLS services, you need to learn the protocols relevant to the VPLS services
and the application scenarios of these protocols.
7.1.1 Introduction to VPLS
This topic describes basic concepts of the VPLS.
VPLS.
7.1.3 VPLS Principle
VPLS is an L2VPN technology based on MPLS and Ethernet technologies. VPLS can provide
the multipoint-to-multipoint VPN services, which is better than the earlier point-to-point L2VPN
services, and L3VPN services requiring carriers to manage the routing information.
7.1.4 VPLS Application
This topic describes a typical application of the VPLS.
7.1.1 Introduction to VPLS
This topic describes basic concepts of the VPLS.
Definition
The Virtual Private LAN Service (VPLS), also called the Transparent LAN Service (TLS) or
virtual private switched network service, is a Layer 2 VPN (L2VPN) technology that is based
on Multi-Protocol Label Switching (MPLS) and Ethernet technologies.
Purpose
The primary goal of VPLS is to interconnect multiple Ethernet LANs through the Packet
Switched Network (PSN). In this manner, these LANs can function as one LAN. VPLS can
implement the multipoint-to-multipoint VPN networking; therefore, by using the VPLS
technology, service providers (SPs) can provide the Ethernet-based multipoint services through
MPLS backbone networks. In addition, by utilizing the VPLS solution in which MPLS virtual
circuits (VCs) function as the Ethernet bridge links, SPs can transparently transmit LAN services
on the MPLS network.
VPLS.
The following table lists the references of this document.
Document No. Description
draft-ietf-l2vpn-signaling-08 Provisioning, auto-discovery, and signaling in
VPLS.
iManager U2000
Issue 01 (2010-08-16)
Document No. Description
draft-ietf-l2vpn-oam-req-frmk-01 VPLS requirements and framework.
RFC 4664 Framework for layer 2 virtual private networks
(VPLS).

7.1.3 VPLS Principle
VPLS is an L2VPN technology based on MPLS and Ethernet technologies. VPLS can provide
the multipoint-to-multipoint VPN services, which is better than the earlier point-to-point L2VPN
services, and L3VPN services requiring carriers to manage the routing information.
VPLS Forwarding Model
The VPLS forwarding model is displayed Figure 7-1. In the VPLS forwarding model, PEs utilize
the Virtual Switch Instance (VSI) for VPLS forwarding; PEs forward Ethernet frames through
the fully-meshed Ethernet emulation circuits or PWs.
PEs of the same VPLS network must be fully meshed. That is, PEs are interconnected with PWs.
In this manner, packets can be sent directly from the ingress provider edge (PE) to the egress
PE, and the transit PE needs not be passed. As a result, no loop occurs between PEs, and the
Spanning Tree Protocol (STP) is not needed.
Figure 7-1 VPLS forwarding model
CE
VLAN2
CE
VLAN1
CE
VLAN2
CE
VLAN1
VSI 1
VSI 2
PE
VSI 1
VSI 2
PE
VSI 2 VSI 1
PE
CE
VLAN1
CE
VLAN2

Basic VPLS Transport Components
The whole VPLS network is similar to a switch. In the VPLS network, PWs are set up between
VPN sites of each VPN through MPLS tunnels, and Layer 2 packets are transparently transmitted
iManager U2000
7-3
between sites; PEs learn the source MAC addresses and create MAC forwarding entries when
forwarding packets, and then maps the MAC addresses to attachment circuits (ACs) and PWs.
The basic VPLS transport components include ACs, virtual circuits (VCs), forwarders, tunnels,
encapsulation, PW signaling protocol, and Quality of Service (QoS).
Figure 7-2 shows the location of each basic VPLS transport component in the VPLS network.
Figure 7-2 Basic VPLS transport components
VPN2
Site1
MPLS
Network
CE2
AC
PW
PW Signal
Tunnel
PE1
PE2
Forwarder
PE3
VPN1
Site3
CE5
VPN1
Site2
CE3
VPN2
Site2
CE4
VPN1
Site1
CE1

The following takes the flow direction of VPN1 packets from CE1 to CE3 as an example to
show the basic direction of the data flow. CE1 forwards Layer 2 packets to PE1. After PE1
receives these packets, the forwarder selects a PW to forward these packets to PE2. Then the
forwarder of PE2 forwards these packets to CE3.
VPLS Loop Avoidance
On Ethernet, STP is often enabled in Layer 2 networks to avoid loops. STP, as a private network
protocol, however, can only avoid loops between devices of the private network, but not in the
ISP network.
Therefore, in a VPLS network, full mesh and split horizon are used to avoid loops. To be specific,
in each VPLS forwarding instance, each PE must create a tree to all the other PEs; each PE must
support split horizon to avoid loops (that is, PEs cannot forward packets between PWs in the
same VSI). Usually, PEs in the same VSI are interconnected through PWs. In this sense, split-
horizon forwarding means that packets received from the PW on the public network side are
forwarded only to the private network side, but not to other PWs.
The full mesh between PEs and split horizon ensure the reachability and loop-free in VPLS
forwarding. When a customer edge (CE) is connected to multiple PEs, or CEs that are connected
to the same VPLS network are interconnected, VPLS cannot ensure that no loop occurs. In such
a situation, other methods such as STP must be used to avoid loops.
iManager U2000
Issue 01 (2010-08-16)
Note that STP can run in the private network of the L2VPN, and all the BPDUs of STP are
transparently transmitted in the ISP network.
Packet Encapsulation on an AC
Packet encapsulation mode on an AC is determined by the user access mode. User access modes
can be VLAN access and Ethernet access. Each user access mode is described as follows:
l VLAN access: In VLAN access mode, the header of each Ethernet frame sent between CEs
and PEs carries a VLAN tag. This tag is a service delimiter that is used to identify users in
an ISP network. It is called provider-tag (P-tag).
l Ethernet access: In Ethernet access mode, the header of each Ethernet frame sent between
CEs and PEs does not carry any P-tag. If the frame header carries a VLAN tag, the VLAN
tag is the internal VLAN tag of the user packet, and is called user-tag (U-tag). The U-tag
is carried in a packet before the packet is sent to a CE and is thus not added by the CE. The
U-tag is used by the CE to identify which VLAN the packet belongs to, and is meaningless
to PEs.
Packet Encapsulation on a PW
Packet encapsulation modes on a PW can be Raw mode and Tagged mode, as shown follows:
l Raw mode
The P-tag is not transmitted on the PW. If a PE receives the packet with a P-tag from a CE,
the PE strips the P-tag, adds double MPLS labels (outer label and inner label) to the packet,
and then forwards the packet. If a PE receives the packet without a P-tag from a CE, the
PE directly adds double MPLS labels to the packet, and then forwards the packet. If a PE
sends a packet to a CE, the PE adds or does not add the P-tag to the packet as required, and
then forwards the packet to the CE. Note that the PE is not allowed to rewrite or remove
any existing tag.
l Tagged mode
The frame sent to a PW must carry the P-tag. If a PE receives the packet with a P-tag from
a CE, the PE directly adds double MPLS labels to the packet without stripping the P-tag,
and then forwards the packet; if a PE receives the packet without a P-tag from a CE, the
PE adds a null tag and double MPLS labels to the packet, and then forwards the packet. If
a PE sends a packet to a CE, the PE rewrites, removes, or preserves the service delimiter
of the packet as required, and then forwards the packet to the CE.
VPLS Packets and Encapsulation Types
According to the preceding packet encapsulation modes on a AC and a PW, the VPLS packets
and encapsulations can be classified into eight types, as listed in Table 7-1.
Table 7-1 VPLS packets and encapsulation types
AC PW U-tag Carried Type
Ethernet Raw No Ethernet access in raw mode (without
the U-tag)
Ethernet Raw Yes Ethernet access in raw mode (with the
U-tag)
iManager U2000
7-5
AC PW U-tag Carried Type
Ethernet Tagged No Ethernet access in tagged mode
(without the U-tag)
Ethernet Tagged Yes Ethernet access in tagged mode (with
the U-tag)
VLAN Raw No VLAN access in raw mode (without the
U-tag)
VLAN Raw Yes VLAN access in raw mode (with the U-
tag)
VLAN Tagged No VLAN access in tagged mode (without
the U-tag)
VLAN Tagged Yes VLAN access in tagged mode (with the
U-tag)

7.1.4 VPLS Application
This topic describes a typical application of the VPLS.
Typical VPLS Networking
Figure 7-3 shows the typical networking of VPLS.
VPLS-A and VPLS-B access different UPEs respectively and communicate with each other
through the ISP network. From the following figure, it is similar that the user networks of VPLS
are in the same LAN. The interfaces used by VPLS must support the ability to broadcast, forward,
and filter Ethernet frames. The UPEs are connected through pseudo wires (PWs) and form an
emulation LAN to users. Each PE learns both the MAC addresses of Ethernet packets from PW
and those from CE. A PW can use either MPLS tunnel or other tunnels, such as GRE and L2TP.
A PE is usually a set of MPLS edge equipment and can create tunnels to other PEs.
iManager U2000
Issue 01 (2010-08-16)
Figure 7-3 Typical VPLS networking
NPE
UPE
UPE
UPE
UPE
VPLS-B
CE-4
ISP Network
VPLS-B
CE-1
CE-2
VPLS-A
VPLS-B
CE-2
VPLS-A
CE-3
VPLS-B
CE-3
VPLS-A
CE-4
VPLS-A
CE-1

7.2 Configuration Flow for a VPLS Service
The configuration flow of the VPLS service includes creating networks, configuring the LSR
ID, configuring QoS policies, configuring interfaces, configuring the control plane, configuring
MPLS tunnel, and configuring VPLS service.
Figure 7-4 shows the flow for configuring the VPLS service.
iManager U2000
7-7
Figure 7-4 Flowchart for configuring a VPLS service
Create a network
Configure
interface
Configure the
control plane
Configure VPLS
Service
Start
Required
Optional
End
Configure the QoS
Policy
Configure Tunnel
Configure the LSR
ID

Table 7-2 Tasks for Configure a VPLS service
1. Create Network Complete creating the NE, Configure the NE data, creating fibers, and
Configure clocks.
2. Configure the
LSR ID
3. Configure the
network-side
Interface
iManager U2000
Issue 01 (2010-08-16)
4. Configure the
Control Plane
tunnels.
l To create the static MPLS tunnel to bear the VPLS service, you do
l To create the dynamic MPLS tunnel to bear the VPLS service, you
l To create the IP tunnel or GRE tunnel to bear the VPLS service, you
5. Configure
Tunnel
l In the case of the static MPLS tunnel, you can create the tunnel either
on the per-NE basis or by using the end-to-end management function.
Select the signaling type as static and set the relevant information
about the tunnel, including the tunnel ID, service name, ingress node,
egress node, and transit node.
tunnel.
6. Configure the
QoS Policy
The QoS policy is used to perform the traffic management on the VPLS
service.
7. Configure the
VPLS Service
1. Create the VPLS service, including setting the service ID and service
name, and selecting the service type and bearer type.
2. Configure the user-side interface is used to access the base station
services.
type.
4. Configure the QoS, including setting the UNI and QoS of the PW.

7.3 VPLS Operation Tasks
This topic describes the VPLS operation tasks, which includes creating and deploying a VPLS
service and adjusting VSI resource.
7.3.1 Creating a VPLS Service
This topic describes how to create a VPLS service.
7.3.2 Deploying a VPLS Service
iManager U2000
7-9
This topic describes how to deploy a VPLS service.
7.3.3 Adjusting the VSI Resource
The U2000 can automatically search out all VSI Resource in the network. In addition, the
U2000 supports the ability to create a new service, convert a VSI resource to a normal service,
and delete a VSI resource in the VSI resource Management window.
Check function.
7.3.1 Creating a VPLS Service
This topic describes how to create a VPLS service.
Prerequisite
The port attributes must be configured correctly.
A tunnel for carrying PWs must be created.
The DCN function of a port carrying services must be disabled if the port need be exclusively
used.
A QoS policy must be created for configuring the QoS if required.
Context
NOTE
The parameters with are mandatory.
Procedure
Step 1 Choose Service > VPLS Service > Create VPLS Service from the main menu.
Step 2 Set the parameters in Attributes List.
iManager U2000
Issue 01 (2010-08-16)
NOTE
When setting parameters, pay attention to the following points:
l Service Template: When creating services, you can use an existing template to improve the efficiency
of applying service configuration. It is recommended that you create a service template for typical
services or services with same or similar parameters.
l Networking Mode: The scenario of typical networking involves common networking scenarios. In
special scenarios, you can customize a networking scenario.
l Service Type: The values Service VPLS and Management VPLS are the same for the PTN equipment.
l VSI Name: The PTN equipment does not support this parameter.
l VSI ID: By default, the U2000 automatically allocates VSI IDs. You can click Auto-Assign to re-
allocate VSI IDs.
Step 3 Select service nodes.
l Manner 1: In NE List, click Add and select the required PE type for service deployment.
In the dialog box that is displayed, select the required equipment.
l Manner 2: In the Physical Topology view, right-click an NE and then choose the required
PE type.
NOTE
If the typical scenario defined by the U2000 is selected, you can click the Add drop-down button to select
the defined PE type as required.
Step 4 In NE List, select an NE, and click Details. On the VSI Configuration tab page, set the relevant
VSI parameters.
NOTE
l You need to set the parameters for all the NEs in NE List.
l It is recommended that you set Split Horizon Group parameters to prevent multicast storms.
Specifically, add the PWs of NEs to split horizon groups.
Step 5 Configure a PW for carrying services.
l If Networking Mode is set to Full-Mesh VPLS, the U2000 automatically creates a PW
between NEs, but you need to configure the tunnel for carrying PWs.
Click the PW Configuration tab. Set In/Out Tunnel binding type and relevant
parameters.
NOTE
l When Binding Type is set to Static Binding, you need to select the tunnel to bind.
l When Binding Type is set to Select Policy, the U2000 automatically selects the required tunnel
according to the policy.
l By default, the U2000 automatically allocates PW IDs.
l If Networking Mode is set to Customized, you need to create a PW between NEs.
1. In the NE List, select all NEs and click the PW Configuration tab.
2. Click Create and choose Bidirectional PW or Unterminated PW as required. In the
dialog box that is displayed, set the relevant information for the PW.
Step 6 Configure SAI.
1. In the NE List, select an NE and click the SAI Configuration tab.
2. Click Create. In the dialog box that is displayed, set the relevant information for the SAI,
and click OK.
iManager U2000
7-11
3. Click the SAI QoS tab, select an SAI, click Configure, and then choose QoS Policy or
QoS CAR Template. In the dialog box that is displayed, set the relevant information for
the SAI QoS.
NOTE
enabled.
----End
Postrequisite
After the service is created successful, the service is displayed in the VPLS service management
window.
7.3.2 Deploying a VPLS Service
This topic describes how to deploy a VPLS service.
Prerequisite
A VPLS service that is created but not deployed exists.
Procedure
Step 1 Choose Service > VPLS Service > Manage VPLS Service from the main menu.
The NMS displays the VPLS services that meet the filter criteria.
Step 3 Select the required VPLS service to be deployed, right-click, and then choose Deploy from the
shortcut menu.
Step 4 Select the required VPLS service to be enabled, right-click, and then choose Enable from the
shortcut menu.
----End
7.3.3 Adjusting the VSI Resource
The U2000 can automatically search out all VSI Resource in the network. In addition, the
U2000 supports the ability to create a new service, convert a VSI resource to a normal service,
and delete a VSI resource in the VSI resource Management window.
Prerequisite
VSI resource must exist in the network and can be discovered on the U2000.
iManager U2000
Issue 01 (2010-08-16)
Context
Discrete VSI resource are mainly classified into the following two types:
l Services created incompletely on NEs but discovered on the U2000
l Discrete services manually created on the U2000
NOTE
In the Manage VSI Resource list, the service whose Service Name is empty is a discrete service.
Purpose of creating a new service: When you need to modify a service running in the existing
network but the specific configuration of the service is not determined, you can create a new
service based on the current configuration. If the new service meets the requirement, you can
add the created new service to the service running in the existing network. This improves the
efficiency of service deployment.
Purpose of converting to services: After a VPLS VPN network runs for a period, certain discrete
VSIs may be generated. With the function of adjusting a discrete service, you can add the discrete
VSIs to existing services.
Procedure
Step 1 Choose Service > VPLS Service > Manage VSI Resource from the main menu.
Step 2 Click Filter. In the dialog box that is displayed, set the filter criteria and filter the VSI resource.
Step 3 Optional: Create new service.
1. Select one or more VSI resource, right-click, and then choose Create New Service from
the shortcut menu.
2. In the dialog box that is displayed, set basic information and general VSI information of
the service and click OK.
The new service is displayed in the service list of the Manage VPLS Service window.
Step 4 Optional: Convert to service.
1. Select one or more VSI resource, right-click, and then choose Convert to Service from the
shortcut menu.
2. In the dialog box that is displayed, click Filter and set the filter criteria.
3. Click OK. Then, select a required service in the query result, and then click OK.
Step 5 Optional: Delete the VSI resource.
1. Select one or more VSI resource, and click Delete.
2. In the dialog box that is displayed, click Yes.
----End
Check function.
Prerequisite
VPLS services must be created and deployed on NEs.
iManager U2000
7-13
Procedure
1. Service Check: It checks whether the configuration data of the source is consistent with
that of the sink.
and LSP.
4. Traceroute: location is used to find out the fault position.
Step 6 Click Run.
----End
7.4 Monitoring a VPLS Service
This topic describes how to monitor a VPLS service.
This topic describes how to configure Ethernet OAM. Ethernet OAM checks the connectivity
of a VPLS service through CC and LB tests. This facilitates the locating of a service fault and
the recovery of the service.
7.4.2 Viewing the Topology of a VPLS Service
This topic describes how to view the topology of a VPLS service and configure the VPLS service
in the topology view. The topology view helps you to directly configure a service in a visual
manner.
7.4.3 Monitoring the Performance of a VPLS Service
This topic describes how to monitor the performance of a VPLS service.
7.4.4 Monitoring the Alarms of a VPLS Service
This topic describes how to monitor the alarms of a VPLS service.
7.4.5 Viewing the Alarms of a VPLS Service
This topic describes how to view the alarms of a VPLS service.
7.4.6 Diagnosing a VPLS Service
Through the service diagnosis function, the NMS can periodically perform the ping operation.
This helps users to learn the connectivity of service links.
iManager U2000
Issue 01 (2010-08-16)
This topic describes how to configure Ethernet OAM. Ethernet OAM checks the connectivity
of a VPLS service through CC and LB tests. This facilitates the locating of a service fault and
the recovery of the service.
Prerequisite
NEs must communicate with the NMS in the normal state.
Context
Ethernet OAM defines the following concepts:
l MD: short for maintenance domain. It refers to the network that requires OAM. An
important attribute of MDs is the level, which defines the OAM scope. MDs can be nested
but cannot be overlapped. MDs process OAM packets by following the rule of blocking
low-level packets, transparent transmitting high-level packets, and processing same-level
packets.
l MA: short for maintenance association. It can be considered as a service-related domain
that is composed of several MEPs.
l MEP: short for maintenance end point. It is the originating and terminating points of all
OAM packets and is related to services. Each MEP has a unique MEP ID in the MA. On a
network, an MA and an MEP ID can uniquely identify an MEP.
l MIP: short for maintenance intermediate point. MIP is related to an MD but irrelevant to
an MA. An MIP cannot send OAM packets. An MIP can respond to and forward LB packets
and LT packets, and can only forward CC packets.
Ethernet OAM checks the service connectivity in real time by periodically sending CC packets.
The source MEP periodically constructs and sends CC packets. After receiving the CC packets
from the source MEP, the destination MEP directly starts the CC check. If the destination MEP
does not receive any CC packets from the source MEP within a certain period, such as 3.5 times
the sending period, the destination MEP reports the CCLOS alarm.
Ethernet OAM checks the connectivity of a service through LB tests. The source MEP constructs
and transmits an LBM frame and starts the timer for timing. If the destination MEP or MIP
receives the LBM frame, it constructs and transmits an LBR frame to the source MEP. The LB
detection is successful. If the source MEP timer times out, the LB detection fails.
Procedure
Step 3 Optional: Perform an CC test.
choose Ethernet OAM > Start CC from the shortcut menu.
iManager U2000
7-15
2. In the Set Filter Criteria dialog box, set the filter criteria. Then, click Filter. The services
3. Select a link and click OK, the source MEP starts the CC check. If the link falls, the
destination MEP reports the CCLOS alarm.
Step 4 Optional: Perform an LB test.
choose Ethernet OAM > LB Test from the shortcut menu.
2. In the Set Filter Criteria dialog box, set the filter criteria. Then, click Filter. The services
3. Select a link and click Run to start an LB test.
----End
7.4.2 Viewing the Topology of a VPLS Service
This topic describes how to view the topology of a VPLS service and configure the VPLS service
in the topology view. The topology view helps you to directly configure a service in a visual
manner.
Prerequisite
Created VPLS services must exist.
Procedure
Step 3 Select a service in the service list. The Topology tab page displays the topology of this service.
Step 4 You can perform the following operations in the topology view:
1. Right-click an NE and then perform one of the following operations:
a. Choose Current Alarm from the shortcut menu to browse current alarm of the NE.
b. Choose History Alarm from the shortcut menu to history current alarm of the NE.
c. Choose NE Explore from the shortcut menu to jump to the NE explore window of
the selected NE.
d. Choose Fast Diagnose from the shortcut menu to diagnose the selected VSI.
2. Right-click an interface and then perform one of the following operations:
a. Choose Current Alarm from the shortcut menu to browse current alarm of the
interface.
b. Choose History Alarm from the shortcut menu to history current alarm of the
interface.
c. Choose View Real-Time Interface Performance from the shortcut menu. In the real-
time performance window that is displayed, set the related parameters to view the real-
iManager U2000
Issue 01 (2010-08-16)
time performance of the selected interface. If you view the real-time performance for
the first time, you need to select the real-time performance indicators to be viewed.
3. Right-click a PW and then perform one of the following operations:
a. Choose Current Alarm from the shortcut menu to browse current alarm of the PW.
b. Choose History Alarm from the shortcut menu to history current alarm of the PW.
c. Choose View Tunnel from the shortcut menu to view the tunnel used by the selected
PW.
d. Choose View Real-Time PW Performance from the shortcut menu. In the real-time
performance window that is displayed, set the related parameters to view the real-time
performance of the selected PW. If you view the real-time performance for the first
time, you need to select the real-time performance indicators to be viewed.
e. Choose Fast Diagnose from the shortcut menu to diagnose the selected PW.
4. Perform one of the following operations without selecting any node or link:
l Right-click in the blank area and choose Legend from the shortcut menu, The legend
is displayed in the topology view.
l Right-click in the blank area and choose Toolbar from the shortcut menu, The toolbar
is displayed in the topology view.
l Right-click in the blank area and choose Synchronize the Main Topology to refresh
the current topology view according to the NE layout in the Main Topology.
l Right-click in the blank area and choose Save to save the current NE layout in the
topology.
l Right-click in the blank area and choose Hide Interface from the shortcut menu.
Interfaces are not displayed in the topology view.
l Right-click in the blank area and choose Hide CE from the shortcut menu. CEs are not
displayed in the topology view.
----End
7.4.3 Monitoring the Performance of a VPLS Service
This topic describes how to monitor the performance of a VPLS service.
Prerequisite
Context
By viewing the performance data, you can know whether the VPLS service is normally running
in a certain period.
Procedure
iManager U2000
7-17
Step 3 View the runtime performance of a service. Right-click the PW and choose View Runtime
----End
7.4.4 Monitoring the Alarms of a VPLS Service
This topic describes how to monitor the alarms of a VPLS service.
Prerequisite
Context
You can monitor the alarm status of the specified services by customizing the monitoring
template.
Procedure
Step 2 Right-click in the monitoring list and choose Select Monitoring Groupfrom the shortcut menu.
Step 3 In the dialog box that is displayed, click Add. In the dialog box that is displayed, set the name
of the monitoring group and click OK.
Step 4 Right-click a monitoring group to be configured and choose Add Monitoring Service from the
shortcut menu. In the dialog box that is displayed, select a service to be monitored and click
Add to add the service to the monitoring group.
Step 5 Click Close.
----End
7.4.5 Viewing the Alarms of a VPLS Service
This topic describes how to view the alarms of a VPLS service.
iManager U2000
Issue 01 (2010-08-16)
Context
l The color of the status column in the service list changes.
Procedure
menu, view the current alarms of the service.
of the service.
area.
----End
Postrequisite
7.4.6 Diagnosing a VPLS Service
Prerequisite
The services to be diagnosed must be deployed.
Procedure
Step 3 Right-click a service and choose Diagnose > Create Test Suit from the shortcut menu.
Step 4 In the wizard dialog box, select the link to be diagnosed and click Next.
iManager U2000
7-19
Step 5 Select the test case type.
Step 6 Set Test Time
1. Set Period Type and Run Time.
2. Click Add.
NOTE
l In the VPLS Service Management window, right-click in the blank area and choose Diagnose > View
Test Strategy from the shortcut menu to view the running policy of test cases.
l You can add multiple diagnosis times for a period type.
Step 7 Click Finish.
----End
Postrequisite
In daily operation and maintenance, you can do as follows to view the diagnosis result and know
the service connectivity:
1. Right-click a service in the VPLS Service Management window and choose Diagnose >
View Test Result from the shortcut menu.
2. In the dialog box that is displayed, view the history data of the service diagnosis result.
3. Determine the service connectivity based on the diagnosis result.
7.5 Managing VPLS Service Authority
This topic describes how to manage the VPLS service authority.
7.5.1 Configuring the Rights of a User on VPLS Services
You can configure operation rights on VPLS services for different users. This enhances the NMS
security.
7.5.2 Viewing the Rights of a User on VPLS Services
This topic describes how to view the rights of a user to VPLS services.
7.5.1 Configuring the Rights of a User on VPLS Services
You can configure operation rights on VPLS services for different users. This enhances the NMS
security.
Prerequisite
Procedure
iManager U2000
Issue 01 (2010-08-16)
shortcut menu.
User.
Step 5 Click OK.
----End
7.5.2 Viewing the Rights of a User on VPLS Services
This topic describes how to view the rights of a user to VPLS services.
Prerequisite
Procedure
Step 1 Choose Service > VPLS Service > Manage VPLS Service Authority from the main menu.
the right pane.
NOTE
l In the right pane, you can adjust the authorization of a service after selecting it. To be specific, the
selected user has the right to a service after you select the service.
l The selected user has the rights to all VPLS services after you select All Services.
Step 3 Click OK.
----End
7.6 Configuration Case of the VPLS Service
This section describes a configuration example of the VPLS service. A configuration flow
includes the service planning and VPLS service configuration.
7.6.1 Configuration Networking Diagram
The sample description includes the information, such as overview of operation & maintenance
(O&M) scenario and networking diagram.
7.6.2 Service Planning
The engineering planning department plans a project according to project requirements and then
outputs the planning details.
7.6.3 Configuration Process
This topic describes the configuration process of VPLS services.
iManager U2000
7-21
7.6.1 Configuration Networking Diagram
The sample description includes the information, such as overview of operation & maintenance
(O&M) scenario and networking diagram.
As shown in Figure 7-5, the three CE networks need communicate with each other. Each CE
network VPLS service has the same VLAN value, that is, 100. MPLS Tunnel 1, MPLS Tunnel
2, and MPLS Tunnel 3 exist among the three PEs.
Among the CE networks, three types of services, including the voice service, data service, and
common Internet access service, are available. The complex traffic classification can be
performed at the access side, and different QoS policies for assured bandwidth can be configured.
The Network can prevents multicast storms.
Figure 7-5 Networking diagram for the VPLS service
NE 1
FE
MPLS Tunnel 3
MPLS Tunnel 2
NE 2
NE 3
CE 2
FE
FE
MPLS
Tunnel 1
CE 1
CE 3
UNI for CE1: 1-EG16-19-ETFC-1
NNI for CE2: 1-EG16-20-POD41-1
PSN
VLAN=100
VLAN=100
VLAN=100

7.6.2 Service Planning
The engineering planning department plans a project according to project requirements and then
outputs the planning details.
Table 7-3 provides the configuration parameters of NEs.
Table 7-3 General planning of VPLS services
Attribute
Service Name VPLS_1
iManager U2000
Issue 01 (2010-08-16)
Attribute
VSI ID 1
Networking Mode Full-Mesh VPLS

Table 7-4 provides the planning of VPLS services.
Table 7-4 Planning of VPLS services
Attribute NE 1 NE 2 NE 3
Tag Type C-Awared C-Awared C-Awared
Enable MAC
Address Learning
Enable Enable Enable
Learning Mode Quailty(SVL) Quailty(SVL) Quailty(SVL)
Enable BPDU
Transparent
Transmission
Disable Disable Disable

Table 7-5 provides the SAI planning of each NE.
Table 7-5 Planning of UNI ports
Attribute NE 1 NE 2 NE 3
Port 19-ETFC-1 19-ETFC-1 19-ETFC-1
ID 1 1 1
Sub Interface Type VLAN Sub Interface VLAN Sub Interface VLAN Sub Interface
VLAN ID 100 100 100

This topic describes the configuration process of VPLS services.
Prerequisite
You must learn the sample network and requirement, and the relevant service planning.
A network must be created.
iManager U2000
7-23
Procedure
Step 2 Set the parameters in Attribute List.
Table 7-6 General planning of VPLS services
Parameter Example Value Guideline
Service Name VPLS_1 Set this value based on the
service planning.
VSI ID 1 The VSI ID of each NE must
be unique.
Networking Mode Full-Mesh VPLS For VPLS services, it is
the Full-Mesh network or
customize a network
characteristics.
Deploy Selected After this parameter is
selected, the tunnel is saved
on the U2000 and deployed
to NEs. If the tunnel for
carrying VPLS services is not
deployed, the tunnel is
deployed when VPLS
services are deployed.

Step 3 Select a VPLS service node. To be specific, select NE1, NE2, and NE3 respectively in Physical
Topology at the upper right corner of the window, right-click, and then choose NPE from the
shortcut menu.
Step 4 Set parameters for a VPLS service node. To be specific, select NEs from the NE list in the left
pane, and click Details. Then, set the relevant parameters in VSI Configuration at the lower
right corner of the window.
iManager U2000
Issue 01 (2010-08-16)
Table 7-7 Planning of VPLS services
Tag Type C-Awared C-Awared indicates that the
learning is based on the C-
TAG (client-side VLAN
tag). S-Awared indicates that
the learning is based on the S-
TAG (operator service-layer
VLAN tag). Tag-Transparent
indicates that only the
Ethernet packets without
VLAN tags can be accessed.
Now, the S-Awared cannot
be supported.
iManager U2000
7-25
Enable MAC Address
Learning
Enable If the function of MAC
address learning is enabled, it
indicates that the network
bridge supports the ability to
learn MAC addresses. In
addition, the network bridge
supports the ability to
generate forward table items
and manually configure the
forward table items of static
MAC addresses.
If the function of MAC
address learning is disabled,
it indicates that the network
bridge does not support the
ability to learn MAC
addresses but only support
the ability to manually
configure the forward table
items of static MAC
addresses.
Learning Mode Quailty(SVL) 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.
Enable BPDU Transparent
Transmission
Disable If the BPDU transparent
transmission identifier of the
Ethernet service of an NE is
enabled, the port where the
service VUNI resides cannot
process the BPDU packets,
and the MSTP cannot be
enabled on this port. After the
BPDU transparent
transmission is enabled, the
BPDU packets are
transmitted as service
packets.
iManager U2000
Issue 01 (2010-08-16)
Split Horizon Group Indicates the PW on the NNI
side of an NE.
For example, you need to add
the PWs between NE1 and
NE2 between NE1 and NE3
to a split horizon group.
After you configure Split
Horizon Group, ports and
links can be isolated. This
setting prevents multicast
storms.

Step 5 Set NE SAI parameters. Right-click the SAI Configuration tab in the lower right corner, select
the three NEs, and then click Create.
Table 7-8 Planning of SAI
Port 19-ETFC-1 Set this value based on the
service planning.
ID 1 Set this value based on the
service planning.
Sub Interface Type VLAN Sub Interface Set this value based on the
service planning.
VLAN ID 100 Set this value based on the
VLANs permitted by VPLS.
iManager U2000
7-27

Step 6 Select a tunnel for carrying VPLS services manually. To be specific, click the PW
Configuration tab at the lower right corner of the window. Then, select the PWs of the NEs
respectively, and click Modify.
Table 7-9 Parameter configuration of a tunnel
Tunnel Binding Type Static Binding After selecting Static
Binding, you can manually
specify a tunnel. After
selecting Select Policy, the
NMS can automatically
select a tunnel according to
the preset priority in the
policy.
Tunnel MPLS Tunnel 1
MPLS Tunnel 2
MPLS Tunnel 3
Set this value based on the
service planning.

Step 7 Click OK.
----End
iManager U2000
Issue 01 (2010-08-16)
8 Managing an L3VPN Service
About This Chapter
On U2000, You can quickly configure the L3VPN service by using the trail function.
8.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.
8.2 Basic Concepts
This topic describes the basic concepts related to L3VPN.
8.3 Application of the L3VPN
L3VPN has three application scenarios, which are intranet VPN, extranet VPN, and Hub &
Spoke.
8.4 Configuration Flow of L3VPN Services
This section describes the operation tasks for configuring L3VPN services, and relations among
these tasks. When configuring or managing L3VPN services, follow the configuration flows.
8.5 L3VPN Operation Tasks
This topic describes the operations tasks of quickly deploying L3VPN services by using the trail
management function on the U2000.
8.6 L3VPN Service Monitoring
This topic describes how to monitor the L3VPN service.
8.7 Managing L3VPN Service Authority
This topic describes how to manage the L3VPN service authority.
8.8 Example for Configuring the L3VPN Service
This topic describes the configuration example of the L3VPN services, including the intranet
VPN and Hub&Spoke VPN services.
iManager U2000
Operation Guide for PTN End-to-End Management 8 Managing an L3VPN Service
8-1
8.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.
L3VPN
On a L3VPN, 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 8-1 shows the basic model of a BGP/MPLS VPN.
Figure 8-1 Model of a L3VPN
CE
CE
CE
Service provider's
backbone
CE VPN 1
Site
Site
Site
Site
VPN 1
VPN 2
PE
PE
PE
P P
VPN 2
P
P

The L3VPN 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.
l 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.
l 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.
iManager U2000
Issue 01 (2010-08-16)
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.
8.2 Basic Concepts
This topic describes the basic concepts related to L3VPN.
8.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.
8.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.
8.2.3 Label Allocation of MP-BGP
This topic describes how an MP-BGP label is distributed.
8.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.
8.2.5 Advertisement of VPNv4 Routes
This topic describes the concepts related to advertisement of VPNv4 routes.
8.2.6 Route Advertisement of a Basic L3VPN
This topic describes how routes of a L3VPN are advertised by using a basic L3VPN as an
example.
8.2.7 Packet Forwarding in a Basic L3VPN
This topic describes how L3VPN packets are forwarded by using a basic L3VPN as an example.
8.2.8 IP DSCP Overview
In a Diff-Serv network, the differentiated services code point (DSCP) is used to identify QoS
priority.
8.2.9 Introduction to DHCP Relay
On an IP-oriented 3G network, after a base station (running the DHCP client) is powered on,
the IP address can be automatically obtained from the DHCP server (usually a component of the
iManager U2000
8-3
base station controller) through the DHCP protocol. The PTN equipment on a mobile carrier
network can transmit DHCP packets between a base station and a base station controller.
8.2.10 Principle of DHCP Relay
This section describes how the PTN equipment implements relay of DHCP packets between a
mobile network base station (running the DHCP client) and a DHCP server (usually a component
of a base station controller) in two DHCP relay modes.
8.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.
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 8-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 8-2 Schematic diagram of sites
CE Carrier's
network
CE
Two sites One site
Site A
Carrier's
network
Headquarters of
X company in City
A
Site X
Branch of
X company
in City B
Headquarters
of X company
in City A
Branch of X
company in
City B
CE
Site B
CE

l 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.
iManager U2000
Issue 01 (2010-08-16)
As shown in Figure 8-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.
l The devices in a site may belong to multiple VPNs. In other words, a site may belong to
multiple VPNs.
As shown in Figure 8-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.
Figure 8-3 One site belonging to multiple VPNs
Carrier's
network
CE
CE
Site B
Site C
X Company
Decision-
making
department
CE
Site A
City A
City B
City C
VPN 2
VPN 1
X Company
R&D
department
X Company
Financial
department

l 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.
iManager U2000
8-5
NOTE
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.
l The CE that a PE accesses is called the local CE of the PE.
l The CE that the peer PE accesses is called the remote CE.
l 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.
Figure 8-4 Schematic diagram of VPN instances
VPN2
Site2 CE
VPN1
Site1 CE
PE
VPN1
VPN-instance
VPN2
VPN-instance
Public
forwarding table
Backbone

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.
l 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.
l 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.
iManager U2000
Issue 01 (2010-08-16)
In RFC 2547 (L3VPNs), 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.
l 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.
l 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 The two VPNs do not have the same site.
l 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 8-5.
Figure 8-5 VPN-IPv4 address structure
Type field
(2-byte)
IPv4 address prefix
(4-byte)
Administrator
subfield
Assigned
number subfield
Router distinguisher (8-byte)
iManager U2000
8-7

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.
l 1
2 bytes.
The Administrator subfield is a 32-bit IPv4 address; the Assigned Number subfield is a 16-
bit 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 The RD format is "16-bit AS number:32-bit user-defined number". For example, 100:1.
l 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.
l 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 8-6 has the following formats:
iManager U2000
Issue 01 (2010-08-16)
l 0
4 bytes.
The Administrator subfield is a 16-bit AS number; the Assigned Number subfield is a 32-
l 1
2 bytes.
The Administrator subfield is a 32-bit IPv4 address; the Assigned Number subfield is a 16-
Figure 8-6 Format of a VPN target
Type field
(2-byte)
Administrator
subfield
Assigned number
subfield
VPN-Target (8-byte)

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 The VPN-Target format is "16-bit AS number:32-bit user-defined number". For example, 100:1.
l 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.
l 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.
l 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 L3VPN.
Relationship Between RD and RT
A L3VPN 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.
iManager U2000
8-9
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.
8.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.
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 NE 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 NE.
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 MP_REACH_NLRI
l 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 NE 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 8-7.
l Internal BGP (IBGP)
iManager U2000
Issue 01 (2010-08-16)
l 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.
Figure 8-7 BGP running mode
CE CE
Internet
EBGP
EBGP
IBGP

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 8-8 shows the format of the attribute.
Figure 8-8 Format of MP_REACH_NLRI
Address Family Information (3bytes)
Next Hop Network Address Information
(variable length)
Network Layer Reachable Information
(variable length)

l Address Family Information: consists of 2-byte Address Family Identifier (AFI) and 1-byte
Subsequent Address Family Identifier (SAFI).
iManager U2000
8-11
l 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.
l An SAFI indicates the type of the NLRI field.
l 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.
l 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 NE 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 NE and the
remote NE. The next-hop network address remains unchanged when MP_REACH_NLRI
is advertised to IBGP peers.
l NLRI: consists of three parts: length, label, and prefix. Figure 8-9 shows the format of the
NLRI field.
Figure 8-9 Format of the NLRI field with a Label subfield
Length (1 byte)
Label (variable length)
Pref ix (variable length)

l Length: indicates the total bits of the label and prefix.
l 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.
l 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 8-10 shows the format of the attribute.
Figure 8-10 Format of MP_UNREACH_NLRI
Address Family Identifier
(2 bytes)
Subsequent Address Family Identifier
(1 byte)
Withdrawn Routes
(variable length)

iManager U2000
Issue 01 (2010-08-16)
l AFI: Corresponding to the address family values defined in RFC 1700 (Address Family
Number), an AFI identifies a network layer protocol.
l SAFI: Similar to SAFI in MP_REACH_NLRI, an SAFI indicates the NLRI type.
l 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.
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 NE gets to know the negotiation capability of its peer by checking the capability
parameters in the Open messages. If the BGP NE and its peer support the same function, the
BGP NE 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 8-11 shows the format of the
capability parameters.
Figure 8-11 Format of BGP capability parameters
Capability Code
(1 byte)
Capability Length
(1 byte)
Capability Value
(variable length)

l Capability Code: uniquely identifies the capability type. The value 1 indicates that the BGP
speaker has the MP-BGP capability.
l Capability Length: indicates the length of the capability field. For MP-BGP, the length of
the capability field is 4.
l Capability Value: indicates the value of the capability field. The length is variable and
depends on the type specified in Capability Code. Figure 8-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 8-12 Format of the Capability Value field in MP-BGP
AFI Res. SAFI
iManager U2000
8-13

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
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 NE. After a virtual link is set up between
a local NE and a remote NE that run BGP, the remote NE becomes a BGP peer of the local
NE. 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.
l 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. MP-
BGP 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 The import policy on the PE changes.
l VPN instances are added or deleted on the PE.
l 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
iManager U2000
Issue 01 (2010-08-16)
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.
8.2.3 Label Allocation of MP-BGP
This topic describes how an MP-BGP label is distributed.
In a L3VPN, 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.
l 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.
8.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.
l 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.
iManager U2000
8-15
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.
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.
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.
l 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.
l 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.
8.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 When multiple valid routes exist, a BGP speaker advertises only the best route to its peer.
l A BGP speaker advertises only the routes used by itself to its peer.
l A BGP speaker advertises the routes obtained through EBGP to all the BGP peers, both
EBGP peers and IBGP peers.
l A BGP speaker does not advertise the IBGP routes to its IBGP peers.
l A BGP speaker advertises the IBGP routes to its EBGP peers when the synchronization
between BGP and IGP is not enabled.
l After a connection is set up, a BGP speaker advertises all the BGP routes to its new peer.
iManager U2000
Issue 01 (2010-08-16)
8.2.6 Route Advertisement of a Basic L3VPN
This topic describes how routes of a L3VPN are advertised by using a basic L3VPN as an
example.
NOTE
A basic L3VPN 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 Route advertisement from the local CE to the ingress PE
l Route advertisement from the ingress PE to the egress PE
l 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.
l 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 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.
l A VPN that receives only the routes within the VPN and the routes advertised by PEs is called
a stub VPN.
iManager U2000
8-17
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.
l 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.
l 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.
l 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 policy-
based routing (PBR) and then by BGP routing policies.
l 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 8-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.
iManager U2000
Issue 01 (2010-08-16)
Figure 8-13 Advertisement of a route from CE2 to CE1
IGP
routing table
Ingress PE CE1 Egress PE CE2
Import
BGP
routing table
VPN routing
table
Carrying label,RD,
and export RT
Route cross&
tunnel iteration
VPN routing
table
BGP
routing table
IGP
routing table
Import
BGP
Update
BGP
Update
BGP
Update
Routing table
Message
VPN backbone
P

1. IGP routes are imported into the BGP IPv4 unicast address family of CE2.
2. 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.
3. 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.
4. 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.
5. The ingress PE advertises a BGP Update message containing the route to CE2. The
advertised route is a common IPv4 route.
6. 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.
8.2.7 Packet Forwarding in a Basic L3VPN
This topic describes how L3VPN packets are forwarded by using a basic L3VPN as an example.
iManager U2000
8-19
NOTE
A basic L3VPN 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 L3VPN backbone network, a P does not know VPN routing information because VPN
packets are transmitted between PEs through tunnels. The following takes Figure 8-14 as an
example to describe the forwarding of a packet from CE1 to CE2 in the L3VPN. As shown in
Figure 8-14, I-L indicates an inner label; O-L indicates an outer label.
Figure 8-14 Forwarding of a VPN packet from CE1 to CE2
Ingress PE CE1
Egress PE CE2
data
P
I-L
data
O-L1
I-L
data
O-L1
I-L
data
O-L2
Out-Label Switch
I-L
data
O-L2
data
data
data
Push
Pop

1. CE1 sends a VPN packet.
2. 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
l Matching the destination IPv4 prefix and searching for the corresponding tunnel ID
l Searching out the tunnel based on the tunnel ID and labeling the packet with I-L
l Sending the packet through the tunnel and labeling the packet with O-L1
l 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.
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.
4. 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.
5. 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.
8.2.8 IP DSCP Overview
In a Diff-Serv network, the differentiated services code point (DSCP) is used to identify QoS
priority.
To perform simple flow classification on IP packets in an IP network, you can use the DSCP
labels in the ToS fields of IP packet heads, as shown in Figure 8-15.
iManager U2000
Issue 01 (2010-08-16)
Figure 8-15 Structure of the IPv4 packet head
Version
Length
ToS
1 Byte
Len
ID Offset TTL Proto FCS IP-DA Data IP-SA
1 2 3 4 5 6 7
0
DSCP Not Used
RFC2474
IPV4 packet head
If you use the first six bits, that is, IP precedence, in the type of service (ToS) byte in an IP packet
head to identify the packet, you can classify all packets into 64 types. After packets are classified,
other QoS features can be used for different classes. In this way, the class-based congestion
management and flow shaping are implemented.
When packets are classified at the edge of a network, DSCP labels are normally added to the
packets. Then, the packets can be classified inside the network according to the DSCP labels.
On the basis of the priority, queuing technologies, such as WFQ and CBWFQ, process the
packets in different ways. A downstream network can either use the classification of an upstream
network or re-classify data packets according to its own standards.
After packets are classified and labeled at the edge of a network, differentiated services are
provided according to labels on the intermediate nodes of the network.
8.2.9 Introduction to DHCP Relay
On an IP-oriented 3G network, after a base station (running the DHCP client) is powered on,
the IP address can be automatically obtained from the DHCP server (usually a component of the
base station controller) through the DHCP protocol. The PTN equipment on a mobile carrier
network can transmit DHCP packets between a base station and a base station controller.
Application of DHCP Relay
At the early stage, the DHCP protocol is applicable to only the situation where the DHCP client
and server are at the same network section. Hence, to perform dynamic host configuration, a
DHCP server must be configured at each network section. This costs a lot.
Through DHCP relay, DHCP client packets can be sent to DHCP servers at other network
sections, or DHCP server packets can be transparently transmitted to DHCP clients at other
network sections. Finally, DHCP clients obtain legal IP addresses. This reduces costs and is easy
for centralized management.
As shown in Figure 8-16, after being powered on, the base station must automatically obtain
the IP address through DHCP. The PTN equipment on the transmission line between the base
station and the base station controller transmits DHCP packets between the base station and the
base station controller to complete DHCP packet exchange.
iManager U2000
8-21
Figure 8-16 Application of DHCP relay
PTN A
PSN
PTN B
FE/GE
NodeB 1
NodeB 4
DHCP server A
NodeB 2
NodeB 3
DHCP server B
FE/GE
Carrier A
Carrier B

NOTE
As shown in Figure 8-16, carrier A and carrier B share the same bearer network, but networks of different
carriers must be isolated. The DHCP relay functions on networks of two carriers are performed
independently but the processes are the same.
Application Scenarios of DHCP Relay
As shown in Figure 8-16, the application scenarios of the DHCP relay of the PTN equipment
are as follows:
l As shown in Figure 8-17, the bearer network between the PTN equipment is a Layer 2
network.
Figure 8-17 Application scenario of DHCP relay on a Layer 2 network
PTN A
L2VPN
PTN B
FE/GE
NodeB 1
NodeB 2
DHCP Server
FE
FE
(DHCP Client)
(DHCP Client)
(DHCP Relay)

iManager U2000
Issue 01 (2010-08-16)
The PTN equipment transmits DHCP packets through L2VPN services. The equipment
attaches labels to only client request packets or server reply packets and then forwards the
packets in MPLS mode, but the equipment does not identifies DHCP packets.
l As shown in Figure 8-18Figure 8-19, the bearer network between the PTN equipment is
a Layer 3 network.
PTN A
L3VPN
PTN B
FE/GE
NodeB 1
NodeB 2
DHCP Server
E1/FE
E1/FE
(DHCP Client)
(DHCP Client)
(DHCP Relay)

PTN A
L3VPN
PTN B
FE/GE
NodeB 1
NodeB 2
DHCP Server
FE
FE
(DHCP Client)
(DHCP Client)
(DHCP Relay)

In this scenario, the following DHCP relay modes are available:
DHCP relay based on VRFs: The equipment is configured and then enabled with the
DHCP relay function. In this case, the equipment identifies and processes the DHCP
request packets from all NodeBs.
DHCP relay based on interfaces: The interfaces on the equipment where NodeB services
are accessed are configured and then enabled with the DHCP relay function. In this
case, communication between each NodeB connected to the equipment through each
interface and the DHCP server can be controlled in an accurate manner.
NOTE
If a NodeB must communicate with a specific DHCP server, you can adopt the latter mode, DHCP
relay based on interfaces.
iManager U2000
8-23
8.2.10 Principle of DHCP Relay
This section describes how the PTN equipment implements relay of DHCP packets between a
mobile network base station (running the DHCP client) and a DHCP server (usually a component
of a base station controller) in two DHCP relay modes.
DHCP relay can implement relay of DHCP packets through an L2VPN or L3VPN network.
Before learning the two modes of DHCP relay, you must understand the DHCP packet format,
which helps you understand the DHCP relay principle.
DHCP Packet Format
DHCP is a protocol based on IP/UDP. Figure 8-20 shows the DHCP packet structure.
NOTE
As shown in Figure 8-20, numbers in the brackets indicate the length of each field. The unit is byte.
Figure 8-20 DHCP packet format

Table 8-1 lists each field in a DHCP packet.
Table 8-1 Description of each field in a DHCP packet
Field Length Meaning
OP 1 byte Indicates the packet type:
l 1: client request packet
l 2: server response packet
iManager U2000
Issue 01 (2010-08-16)
Hardware Type 1 byte Indicates the hardware address type:
l 1: Ethernet
l 17: HDLC
Hardware
Length
1 byte Indicates the length of the hardware address. The unit is byte.
For Ethernet, the value of this field is 6.
Hops 1 byte Indicates the number of DHCP relays that the current DHCP
packets traverse. This filed is set to 0 on the client. Each time
when the packets traverse a DHCP relay, the value of this
field is increased by 1. This field is used to restrict the number
of DHCP relays that the DHCP packets traverse.
Transaction ID 4 bytes Sets to a random value. Hence, the response packets of the
server match the request packets of the user.
Seconds 2 bytes Indicates the time that elapses after the client starts the DHCP
request. The unit is second.
Flags 2 bytes Indicates a label field in DHCP. The format is:
.
Only the most significant bit of this field is meaningful, and
other bits are set to 0. The most left bit is the broadcast
response label bit, and the values of this bit are as follows:
l 0: The client requires that the server unicast response
packets.
l 1: The client requires that the server broadcast response
packets.
Client IP
Address
(ciaddr)
4 bytes Indicates the IP address of the client. The IP address can be
an IP address assigned by the server to the client or an
existing IP address of the client. In the initialization state, the
client does not have an IP address. In this case, the value of
this field is 0.0.0.0.
Your (Client) IP
Address
(yiaddr)
4 bytes Indicates the IP address assigned by the server to the client.
When performing a DHCP response, the server fills the IP
address assigned to the client into this field.
Server IP
Address
(siaddr)
4 bytes Indicates the IP address of the server.
iManager U2000
8-25
Relay Agent IP
Address
(giaddr)
4 bytes Indicates the IP address of the first DHCP relay. When the
client sends a DHCP request, if the server and client are not
on the same network, the first DHCP relay fills its IP address
into this field during forwarding of this DHCP request
packet. The server determines the network section address
according to this field, and then selects the address pool for
assigning addresses to users. The server also uses this field
to send a response packet to this DHCP relay, and forwards
the packet to the client through a DHCP relay.
NOTE
If the packet traverses more than one DHCP relay before reaching
the DHCP server, this field of a DHCP relay behind the first DHCP
relay does not change and only the number of hops is increased by
1.
Client Hardware
Address
(chaddr)
16 bytes Indicates the MAC address of the client. This field must be
consistent with the hardware type and hardware length fields.
When sending a DHCP request, the client fills its hardware
address into this field. For example, in the case of Ethernet,
if the hardware type and hardware length are 1 and 6
respectively, this field must be filled in with a 6-byte
Ethernet MAC address.
Server Host
Name
64 bytes Indicates the name of the server whose configuration
information is obtained by the client. This field is filled in
by the DHCP server and it is optional. If this field is filled
in, it must be a character string ended with 0.
File Name 128 bytes Indicates the name of the start configuration file of the client.
This field is filled in by the DHCP server and it is optional.
If this field is filled in, it must be a character string ended
with 0.
Options Variable Indicates the option field of DHCP, and it contains at least
312 bytes. This field contains the configuration information
assigned by the server to the client, such as the IP address of
a gateway NE, IP address of a DNS server, and valid leasing
period when the client can use the IP address.

Processing Flow of L2VPN DHCP Relay of the PTN Equipment
As shown in Figure 8-21, the equipment attaches labels to only client request packets or reply
packets of the server and then forwards them in MPLS mode, but the equipment does not
identifies DHCP packets.
Through an L2VPN, the PTN equipment sends the DHCP request packets from NodeB to the
server, and sends the DHCP response packets from the server to NodeB.
iManager U2000
Issue 01 (2010-08-16)
Figure 8-21 L2VPN DHCP relay mode
PTN 1 PTN 2
FE/GE
NodeB
DHCP Server
FE
IP
ETH
IP
ETH
L2VPN

The processing flow of L2VPN DHCP relay is as follows:
1. The PTN equipment receives DHCP packets from the client or server through a physical
port.
2. The PTN equipment detects that the port through which the packets are received is a Layer
2 port, the PTN equipment performs Layer 2 forwarding for the DHCP packets without
identifying them.
Processing Flow of L3VPN DHCP Relay of the PTN Equipment
On an L3VPN network, the PTN equipment or an interface on the PTN must be enabled with
the DHCP relay function to relay the DHCP packets.
The first port (generally the first UNI port connected to the DHCP client) that processes the
DHCP request packets is considered as the DHCP gateway port. Only the gateway port needs
to identify and process the DHCP request packets and reply packets.
L3VPN DHCP relay has two service transmission scenarios.is used to transmit DHCP packets
in Ethernet services. Figure 8-23 shows the FE service scenario.
l For details on the IPoE service scenario, see Figure 8-22.
Figure 8-22 IPoE service scenario
PTN 1
FE/GE
NodeB
DHCP Server
E1
IP
E1
IP
ETH
ML-PPP PTN 2
L3VPN

l For details on the FE service scenario, see Figure 8-23.
Figure 8-23 FE service scenario
PTN 1
FE/GE
NodeB
DHCP Server
FE
IP
ETH
PTN 2
L3VPN
IP
ETH

iManager U2000
8-27
The transmission scenarios shown in Figure 8-22 and Figure 8-23 are considered as examples.
The processing flows for L3VPN DHCP relay of the equipment as follows:
l The processing procedure of DHCP relay based on VPN routing and forwarding tables
(VRFs) is as follows:
1. When PTN A, which is enabled with DHCP relay, receives DHCP request packets
from a certain logical port of NodeB.
2. PTN A determines whether the number of relays that the current DHCP packets
traverse exceeds the limit. If yes, the packets are discarded. Otherwise, the number of
relays is added with 1.
3. PTN A selects the IP address of the server as the destination IP address, and sets the
IP address of the packet egress port as the source IP address.
NOTE
When the IP address of the server is selected as the destination IP address, the following modes
are available:
l Sharing mode: The server is selected according to the sharing algorithm.
l Broadcast mode: The packets are sent to each server in the VRF.
4. PTN A performs link-layer encapsulation on the packets, performs routing based on
the destination IP address, and sends the packets.
5. After receiving the request packets, the DHCP server sends response packets to the
client. These response packets carry the information about the IP address distributed
to the client.
6. PTN A receives the response packets and sends the packets to NodeB after performing
IP encapsulation on them.
l The processing procedure of DHCP relay based on interfaces is as follows:
1. On PTN A, the UNI interface through which PTN A is connected to a NodeB is enabled
with DHCP relay, and the IP address of the corresponding server is set at the interface.
2. After the DHCP request packets reach PTN A, the IP address of the server set at the
interface is considered as the destination IP address.
3. PTN A performs link-layer encapsulation (such as ETH encapsulation) and routing
based on the destination IP address. Then, PTN A sends the packets to the server.
NOTE
After the DHCP server receives the request packets, the remaining processing procedure is the same
as that in the case of DHCP relay based on VRFs.
8.3 Application of the L3VPN
L3VPN has three application scenarios, which are intranet VPN, extranet VPN, and Hub &
Spoke.
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.
iManager U2000
Issue 01 (2010-08-16)
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 8-24 Networking diagram of an intranet VPN
VPN1
Site3
Site4
CE
VPN2
CE
PE VPN2
Site2
CE
VPN1
Site1
CE
PE P
VPN1
Import: 100:1
Export: 100:1
VPN2
Import: 200:1
Export: 200:1
VPN1
Import: 100:1
Export: 100:1
VPN2
Import: 200:1
Export: 200:1
Backbone

As shown in Figure 8-24, 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.
iManager U2000
8-29
Figure 8-25 Networking diagram of an extranet
PE3
VPN2
Site2
CE
VPN1
Site1
CE
PE1
VPN1
Import: 100:1
Export: 100:1
PE2
VPN2
Import: 200:1
Export: 200:1
VPN1
Import: 100:1, 200:1
Export: 100:1, 200:1
VPN1
Site3
CE

As shown in Figure 8-25, VPN1 and VPN2 can access Site3 of VPN1.
l PE3 can receive the VPN-IPv4 routes advertised by PE1 and PE2.
l PE1 and PE2 can receive the VPN-IPv4 routes advertised by PE3.
l Thus, Site1 and Site3 of VPN1 can access each other; Site2 of VPN2 and Site3 of VPN1
can access each other.
l 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 Hub-
CE; on the side of spoke sites, a device that accesses the VPN backbone network is called Spoke-
CE. On the side of the VPN backbone network, a device that accesses the Hub site is called Hub-
PE; 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.
l 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
iManager U2000
Issue 01 (2010-08-16)
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 8-26 Route advertisement from Site2 to Site1 in Hub&Spoke networking model
VPN1
Site3
Spoke-CE
Hub-CE
Hub-PE
VPN1
Site2
CE
VPN1
Site1
CE
Spoke-PE
Spoke-PE
7
6
5
4
3 2
1

As shown in Figure 8-26, 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 The Hub-PE can receive the VPN-IPv4 routes advertised by all the Spoke-PEs.
l All the Spoke-PEs can receive the VPN-IPv4 routes advertised by the Hub-PE.
l 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.
l The import target of any Spoke-PE is not the same as the export targets of other Spoke-
PEs. Therefore, any two Spoke-PEs do not directly advertise VPN-IPv4 routes to each
other. The Spoke sites cannot directly access each other.
Figure 8-27 shows the transmission path for data communication between Site 1 and Site 2 in
Figure 8-26. (The direction for data transmission is indicated by arrowheads of lines in the
figure.).
iManager U2000
8-31
Figure 8-27 Path of transmitting customer traffic from Site1 to Site2
VPN1
Site3
Spoke-CE
Hub-CE
Hub-PE
VPN1
Site2
CE
VPN1
Site1
CE
Spoke-PE
Spoke-PE
1
2
3
4
5 6
7

8.4 Configuration Flow of L3VPN Services
This section describes the operation tasks for configuring L3VPN services, and relations among
these tasks. When configuring or managing L3VPN services, follow the configuration flows.
Configure and manage L3VPN services by following the configuration flow shown in Figure
8-28.
iManager U2000
Issue 01 (2010-08-16)
Figure 8-28 L3VPN service configuration flow
Create the network
Configure the control
plane
Configure the L3VPN
service
Start
Required
End
Configure the NNI
interface
Configure the tunnel
Optional
Configure LSR ID
Configure the UNI
lnterface

Table 8-2 Tasks for configuring the L3VPN service
Task Remarks
1. Create the
network
To create a network, you need to create NEs, configure NE data, and
create fibers.
2. Configure the
LSR ID
3. Configure the
NNI interface
Set the general attributes and Layer 3 attributes (tunnel enable status and
IP address) for interfaces to carry the tunnel carrying.
iManager U2000
8-33
Task Remarks
4. Configure 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.
interface, ML-PPP, xDSL interface, microwave interface, LAG, and
VLAN sub-interface.
interface, ML-PPP, SDH interface, LAG, and VLAN sub-interface.
interface, SDH interface, LAG, and VLAN sub-interface.
NOTE
The equipment can access the IP-over-E1 L3VPN service through ML-PPP on the
UNI side.
5. Configure the
control plane
Set protocol parameters relevant to the control plane for the tunnel
creation.
l When you create a static MPLS tunnel to carry L3VPN services, you
need not configure the parameters relevant to the control plane.
l When you create a dynamic MPLS tunnel to carry BGP/MPLS
services, you need to configure IGP-ISIS protocol parameters.
Configure the protocol relevant to the control plane to implement the
protocol of the advertised route on the PE-PE side.
l Create an MP-BGP instance and the MP-BGP peer.
6. 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 End to End mode. Specify the tunnel ID, set signaling type
to static, name the tunnel, and specify the ingress node, egress node,
and transit node.
l If a dynamic MPLS tunnel is used, you need to set relevant
information, for example, the service name and the source and sink
of the tunnel, and select the dynamic signaling type.
7. Configure the
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.

8.5 L3VPN Operation Tasks
This topic describes the operations tasks of quickly deploying L3VPN services by using the trail
management function on the U2000.
8.5.1 Creating the L3VPN Service
iManager U2000
Issue 01 (2010-08-16)
This topic describes how to create the L3VPN service.
8.5.2 Deploying the L3VPN Service
This topic describes how to deploy the L3VPN configuration data to NEs.
8.5.3 Adjusting the Discrete L3VPN Service
This topic describes how to adjust the discrete L3VPN service.
Check function.
8.5.5 Configuring DHCP Relay
This section describes how to deploy the DHCP Relay function for equipment and interfaces.
8.5.1 Creating the L3VPN Service
This topic describes how to create the L3VPN service.
Prerequisite
The MP-BGP protocol must be configured for the public network.
If a dynamic tunnel is used to carry the L3VPN service, the IS-IS protocol must be enabled.
The DCN must be disabled on the port of the L3VPN service.
Data must be synchronized between the equipment relevant to the service.
Procedure
Step 1 Choose Service > L3VPN Service > Create L3VPN Service from the main menu.
Step 2 In the Service Information area, set the basic information of the L3VPN service.
iManager U2000
8-35
l Specify Network Type. Then, the U2000 automatically generates the VRF for each
equipment according to the specified network type. By default, the network type is Full-
Mesh.
l By selecting the Service Template check box, you can create a service quickly and
conveniently. Here, only the general procedure for creating a service is described. For details
about how to create a template and use the template to create a service, see 4 Configuring
a Service Template.
NOTE
You can create a service template according to the requirement of service deployment. For example,
you can select the concerned parameters in the template and set the default values of certain parameters.
By applying the template in service creation, you can quickly and efficiently create a service. The
parameter list contains only the selected parameters and their values.
l Set VRF Name, RD, and RT. After you add the equipment, RD, and RT are displayed in
the parameter list for the equipment on the right.
NOTE
l You can enter a value for the VRF ID. Otherwise, the U2000 automatically allocate an ID. In
addition, you can enter a value for the VRF ID only on the PTN equipment.
l The Service Name Auto Relate Description and Description Auto Relate VRF
Description check box is selected by default on the U2000.
Step 3 In the NE List area, add the equipment for creating a service.
To select the equipment, you can also right-click in the physical topology and choose Add Node
to Service from the shortcut menu.
Step 4 Click the Service Topology tab to view the change of the configuration in real time.
Now, you can view the topology that is displayed based on the network type and VRF
information.
Step 5 Set the VRF parameters for each equipment in the parameter list.
1. Configure General.
Double-click to expand General. The values of the general attributes RD and RT are
automatically set to the values that you set in Step 2 (if those values are set). In addition,
you can also change the values of those parameters.
Set the IP DSCP, VRF Description, Routing Policy, Label Distribution Policy , Tunnel
Binding and Max.Route Count parameters.
NOTE
You can also click and to extend and collapse all VRF parameters respectively.
In the case of the static tunnel that is bound, you can press the Delete key to unbind the tunnel.
When you set IP DSCP to Yes, the PTN transparently transmits the DSCP of IP packets. When you
set IP DSCP to No, the PTN modifies the DSCP of IP packets.
You must configure the bandwidth of tunnel when dynamically binding a tunnel.
2. Configure DHCP Relay.
Double-click to expand DHCP Relay. Configure the parameters of Enabled, Server IP
Address, Relay Hops, and Selection Policy.
If you configure and enable a DHCP relay based on VRFs, you can recognize and process
the DHCP request packets that are transmitted from client-side ports.
iManager U2000
Issue 01 (2010-08-16)
3. Configure SAI.
Right click and select Insert Instance to add the service access interface.
You can bind multiple interfaces and set the parameters relevant to the interfaces.
In addition, CE Information and QoS of the interfaces are optional.
Double-click to expand DHCP Relay. Configure the parameters of Enabled and Server
IP Address.
NOTE
You can also click the SAI Configuration tab to add, modify, or delete an SAI or configure the SAI QoS.
If you configure and enable a DHCP relay based on ports, you can accurately control the interaction
between the equipment connected to each port and the DHCP server.
4. Configure Route Configuration.
Set the basic information, such as the BGP peer. In addition, the Route Aggregation and
Route Import parameters are optional.
You can select the routing protocol and set relevant parameters according to actual O&M
requirements.
NOTE
The private BGP protocol is configured in this step.
The ID of BGP instance here cannot be the same as the ID of the MP BGP instance of the control
plane.
You must configure the Instance ID for the ISIS and RIP.
You must configure the Instance ID and Area No for the OSPF.
5. Optional: Configure ARP List.
Right click and select Insert Instance to add the ARP list.
You can configure the parameters of IP Address and MAC Address.
NOTE
enabled.
----End
Postrequisite
After the service is created successful, the service is displayed in the L3VPN service management
window.
8.5.2 Deploying the L3VPN Service
This topic describes how to deploy the L3VPN configuration data to NEs.
iManager U2000
8-37
Prerequisite
l Data must be synchronized between the equipment relevant to the service.
l The L3VPN service must be created but not deployed.
Context
After you create the L3VPN service, the service configuration data is saved in the database of
the U2000, instead of being applied to NEs, before deployment. In this case, the service is in the
Undeployment state and you can deploy such a service to apply the service configuration data
to NEs.
Procedure
Step 1 Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
Step 3 Select the service to be deployed, right-click, and choose Deploy from the shortcut menu.
Step 4 Click Close in the dialog box displayed.
----End
8.5.3 Adjusting the Discrete L3VPN Service
This topic describes how to adjust the discrete L3VPN service.
Prerequisite
l Data must be synchronized between the equipment relevant to the service.
iManager U2000
Issue 01 (2010-08-16)
Context
After the L3VPN network runs for a period, certain discrete VRFs may exist on the network.
By using the function of adjusting discrete services, you can add those VRFs to the existing
services or directly delete those VRFs.
In the Manage VRF Resource list, if the value of the Service Name field is empty, it indicates
that the VRF is a discrete VRF.
Procedure
Step 1 Choose Service > L3VPN Service > Manage VRF Resource from the main menu.
Step 3 Optional: Convert to service.
1. Select one or more discrete services, right-click, and then choose Convert to Service from
the shortcut menu.
2. In the dialog box that is displayed, click Filter and set the filter criteria.
3. Click OK. Then, select a required service in the query result, and then click OK.
Step 4 Optional: Delete the VRF resource.
1. Select one or more VRF resource, and click Delete.
2. In the dialog box that is displayed, click OK.
----End
Check function.
Procedure
1. Service Check: list all service configuration parameters.
and LSP.
4. Traceroute: location is used to find out the fault position.
iManager U2000
8-39
Step 6 Click Run.
----End
8.5.5 Configuring DHCP Relay
This section describes how to deploy the DHCP Relay function for equipment and interfaces.
Prerequisite
l You must be an NM user with "NE operator" authority or higher.
l The MP-BGP protocol must be configured on the public network.
l If L3VPN services are carried over dynamic tunnels, the IS-IS protocol must be enabled.
l The DCN function must be disabled for the ports with the L3VPN services.
l The service-related equipment must synchronize data.
Precautions
NOTE
Configuring the DHCP Relay is optional for configuring a L3VPN service. The parameters related to DHCP
Relay are available only when you configure a L3VPN service.
Procedure
Step 1 Choose Service > L3VPN Service > Create L3VPN Service from the Main Menu.
Step 2 Configure the DHCP Relay function.
You can set the parameters related to DHCP Relay either in a template or in a VRF.
l Configure the DHCP Relay function for equipment in the template.
1. Choose Service Template in Service Information.
NOTE
You can create a service template according to the service deployment requirement. For
example, you can define (by selecting items) the related parameters and set the default values
for certain parameters. When creating a service, you can use the template. In this case, the
parameter table lists only the selected parameters and the default values of the parameters. This
ensures quick and effective service creation.
2. Click to display the Select Template dialog box.
3. Click New to display the Create L3VPN Service Template dialog box.
4. In Create L3VPN Service Template, set Template name. In Parameter Setting,
set DHCP Relay.
5. After you set DHCP Relay, click OK.
l Configure the DHCP Relay function for equipment in the VRF table.
1. Add the equipment where a service is to be created to NE List,
or right-click the equipment in Physical and choose Add NE to Service.
2. Click Details, VRF Configuration is displayed.
iManager U2000
Issue 01 (2010-08-16)
3. In VRF Configuration, select DHCP Relay and set the parameters related to DHCP
Relay.
Set the following parameters about DHCP Relay:
Enable: Enable or disable the DHCP Relay function. To enable the DHCP Relay
function, select Yes.
Service IP Address: Set the IP address of the DHCP server.
Relay Hops: Set the relay hops for the DHCP relay server within a range of 1 to 16, the
default value is 4.
Selection Policy: When the PTN relay equipment selects the server IP address as the
DIP (destination IP address), there are two selection policies, that is, Share and
Broadcast.
Share: The PTN equipment selects a server by running a sharing algorithm.
Broadcast: The PTN equipment broadcasts packets to each server in the VPN
routing and forwarding table (VRF).
l Deploy the DHCP function for interfaces.
1. Add the equipment where a service is to be created to NE List,
or right-click the equipment in Physical and choose Add NE to Service.
2. Click Details, VRF Configuration is displayed.
3. In VRF Configuration, select SAI > Interface > DHCP Relay and set the parameters
related to DHCP Relay.
Set the following parameters about DHCP Relay:
Enable: Enable or disable the DHCP Relay function. To enable the DHCP Relay
function, select Yes.
Service IP Address: Set the IP address of the DHCP server.
----End
8.6 L3VPN Service Monitoring
This topic describes how to monitor the L3VPN service.
8.6.1 Viewing the L3VPN Service Topology
A service topology displays the topology structure of L3VPN services. By viewing the service
topology, you can learn the topology structure and the running status of the service in real time.
8.6.2 Monitoring Performance of the L3VPN Service
iManager U2000
8-41
While the L3VPN service is running, abnormal status may occur. By viewing the performance
data of the L3VPN service, you may learn the abnormal status in time. In this manner, the
maintenance personnel can take timely measures to avoid faults.
8.6.3 Monitoring Alarms of the L3VPN Service
By creating a service monitoring template, the maintenance personnel can monitor alarms of
services that important to customers, and learn the running status of services in real time, thus
ensuring the normal running of the services.
8.6.4 Viewing the Alarms of an L3VPN Service
This topic describes how to view the alarms of an L3VPN service.
8.6.5 Diagnosing an L3VPN Service
8.6.1 Viewing the L3VPN Service Topology
A service topology displays the topology structure of L3VPN services. By viewing the service
topology, you can learn the topology structure and the running status of the service in real time.
Prerequisite
l You must be an NM user with "NM monitor" authority or higher.
l The L3VPN service must be created successfully.
Procedure
Step 3 In the service list, select a service to be viewed.
Step 4 View the topology structure of a service.
In the service topology, you can learn PE information about the source and sink, and interface
information about the connection to the CE.
Step 5 View alarm information about a service.
If a fault occurs, the corresponding interface and VRF of the PE in the service topology is
displayed in red.
Step 6 You can perform the following operations in the service topology.
l In the service topology, select a PE, right-click, and then choose the following menu items
from the shortcut menu respectively.
Choose Open NE Explorer, then, the NE Explorer of the equipment is displayed.
Choose VRF Details to view the details information of VRF.
Choose View Real-Time VRF Performance to view the real-time VRF performance of
the service.
Choose Alarm > Current Alarm to view the current alarm of the PE.
Choose Alarm > History Alarm to view the history alarm of the PE.
iManager U2000
Issue 01 (2010-08-16)
l In the service topology, select one interface, right-click, and then choose the following menu
items from the shortcut menu respectively.
Choose Configure SAI to view or modify the configurations of the service access
interface.
Choose View Real-Time SAI Performance to view or modify the real-time performance
of the service access interface.
Choose Fast Diagnosis to diagnose the connectivity of the selected VRF. You can use
the VRF Ping or VRF Trace tool in fast diagnosis.
Choose Alarm > Current Alarm to view the current alarm of the service access interface.
Choose Alarm > History Alarm to view the history alarm of the service access interface.
----End
8.6.2 Monitoring Performance of the L3VPN Service
While the L3VPN service is running, abnormal status may occur. By viewing the performance
data of the L3VPN service, you may learn the abnormal status in time. In this manner, the
maintenance personnel can take timely measures to avoid faults.
Context
By viewing the performance data, the maintenance personnel can determine whether a service
runs in the normal state within a period of time.
Procedure
Step 3 View the real-time VRF performance of a service. Right-click the NE and choose View Real-
Time VRF Performance from the shortcut menu in the topology view.
----End
8.6.3 Monitoring Alarms of the L3VPN Service
By creating a service monitoring template, the maintenance personnel can monitor alarms of
services that important to customers, and learn the running status of services in real time, thus
ensuring the normal running of the services.
Procedure
Step 2 In the Centralized Monitoring dialog box, expand the All Service branch to view alarm
information of all services.
iManager U2000
8-43
Step 3 Click Select Monitoring Group.
Step 4 In the Select Monitoring Group dialog box, right-click and choose Add Monitoring Group
from the shortcut menu.
Step 5 In the Add Monitoring Group dialog box, enter the name of the monitoring group and click
OK.
The newly-added monitoring group is displayed in the central monitoring list.
Step 6 Select the monitoring group that is added, right-click, and then choose Add Monitoring
Service from the shortcut menu.
Step 7 In the Add Monitoring Service dialog box, select the L3VPN Service tab and select the service
to be added. Then, click Add.
Step 8 Click Close.
----End
8.6.4 Viewing the Alarms of an L3VPN Service
This topic describes how to view the alarms of an L3VPN service.
Context
Procedure
menu, view the current alarms of the service.
of the service.
area.
----End
Postrequisite
iManager U2000
Issue 01 (2010-08-16)
8.6.5 Diagnosing an L3VPN Service
Prerequisite
The services to be diagnosed must be deployed.
Procedure
Step 3 Right-click a service and choose Diagnose > Create Test Suit from the shortcut menu.
Step 4 In the wizard dialog box, select the link to be diagnosed and click Next.
Step 5 Select the test case type.
Step 6 Set Test Time
1. Set Period Type and Run Time.
2. Click Add.
NOTE
l In the L3VPN Service Management window, right-click in the blank area and choose Diagnose >
View Test Strategy from the shortcut menu to view the running policy of test cases.
l You can add multiple diagnosis times for a period type.
Step 7 Click Finish.
----End
Postrequisite
In daily operation and maintenance, you can do as follows to view the diagnosis result and know
the service connectivity:
1. Right-click a service in the L3VPN Service Management window and choose
Diagnose > View Test Result from the shortcut menu.
2. In the dialog box that is displayed, view the history data of the service diagnosis result.
3. Determine the service connectivity based on the diagnosis result.
8.7 Managing L3VPN Service Authority
This topic describes how to manage the L3VPN service authority.
8.7.1 Configuring the Rights of a User on L3VPN Services
You can configure operation rights on L3VPN services for different users. This enhances the
NMS security.
iManager U2000
8-45
8.7.2 Viewing the Rights of a User on L3VPN Services
This topic describes how to view the rights of a user on L3VPN services.
8.7.1 Configuring the Rights of a User on L3VPN Services
You can configure operation rights on L3VPN services for different users. This enhances the
NMS security.
Prerequisite
Procedure
shortcut menu.
User.
Step 5 Click OK.
----End
8.7.2 Viewing the Rights of a User on L3VPN Services
This topic describes how to view the rights of a user on L3VPN services.
Prerequisite
Procedure
Step 1 Choose Service > L3VPN Service > Manage L3VPN Service Authority from the main menu.
the right pane.
NOTE
l In the right pane, you can adjust the authorization of a service after selecting it. To be specific, the
selected user has the right to a service after you select the service.
l The selected user has the rights to all VPLS services after you select All Services.
Step 3 Click OK.
----End
iManager U2000
Issue 01 (2010-08-16)
8.8 Example for Configuring the L3VPN Service
This topic describes the configuration example of the L3VPN services, including the intranet
VPN and Hub&Spoke VPN services.
8.8.1 Example for Configuring an Intranet VPN Service
This topic describes a configuration example of the intranet VPN service. A configuration flow
describes the configuration networking diagram, service planning, and configuration process.
8.8.2 Example for Configuring the Hub&Spoke VPN Service
This topic provides an example for configuring 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.
8.8.1 Example for Configuring an Intranet VPN Service
This topic describes a configuration example of the intranet VPN service. A configuration flow
describes the configuration networking diagram, service planning, and configuration process.
Networking Configuration Diagram
This topic describes the networking diagram of the sites on VPN1 and VPN2.
Requirement and Networking Diagram
Figure 8-29 shows the networking diagram of the intranet VPN services. A service provider
provides different L3VPN 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 The equipment on Site1, Site2, and Site3 can communicate with each other on VPN1.
l The equipment on Site4, Site5, and Site6 can communicate with each other on VPN2.
l The equipment on Site1, Site2, or Site3 cannot communicate with the equipment on Site4,
Site5, or Site6.
iManager U2000
8-47
Figure 8-29 Network of the intranet VPN service
PE1
PE2
PE3
CE
CE
CE
CE
VPN1
VPN1
VPN2
VPN2
Backbone
VPN1
VPN2
CE
CE
RD 100:1
Export RT 100:1
Import RT 100:1
RD 100:2
Export RT 100:2
Import RT 100:2
RD 100:1
Export RT 100:1
Import RT 100:1
RD 100:2
Export RT 100:2
Import RT 100:2
RD 100:1
Export RT 100:1
Import RT 100:1
RD 100:2
Export RT 100:2
Import RT 100:2
Site1
Site2
Site3
Site4
Site6
Site5
192.168.0.4
192.168.1.
3
192.168.3.
4
AS: 65410
AS: 65420
AS: 65430
AS: 100
192.168.1.
4
192.168.0.
2
192.168.2.4

Figure 8-30 shows the NE planning diagram.
PE1
PE2
PE3
CE
CE
CE
CE
VPN1
VPN1
VPN2
VPN2
Backbone
VPN1
VPN2
CE
CE
Site1
Site2
Site3
Site4 Site6
Site5
1-EG16-1Port-1
1-EG16-2Port-2
1-EG16-1Port-1 1-EG16-2Port-2
3-EG16-1Port-1
3-EG16-2 Port-2
3-EG16-1Port-1 3-EG16-2 Port-2
1-EG16-1Port-1
1-EG16-2 Port-2
3-EG16-1Port-1
3-EG16-2 Port-2
192.168.2.1 192.168.0.1
192.168.2.2
192.168.4.1
192.168.1.2
192.168.3.2
192.168.2.3
192.168.0.3 192.168.1.1 192.168.3.1
192.168.3.3
192.168.4.2
iManager U2000
Issue 01 (2010-08-16)

Service Planning
Site1, Site2, and Site3 belong to VPN1, and Site4, Site5, and Site6 belong to 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 BPG/MPLS VPN services.
Table 8-3 shows the planning of the parameters for VPN1.
Table 8-4 shows the planning of the parameters for VPN2.
Table 8-3 VPN1 parameter planning
Service Information Service Name L3VPN-0001
Network Type Full-Mesh
VRF ID 1
VRF Name vrf1
RD 100:1
RT 100:1
NE List Node Name PE1: NE(9-1)
PE2: NE(9-2)
PE3: NE(9-3)
Node IP Address/Node ID PE1: 9-1
PE2: 9-2
PE3: 9-3
Tunnel Binding (Static) Tunnel Name PE1: Tunnel-0001
PE2: Tunnel-0002
PE3: Tunnel-0003
SAI Interface Interface Name PE1, PE2, PE3: 1-EG16-1
(Port-1)
IP Address/Mask PE1: 192.168.0.1/24
PE2: 192.168.1.2/24
PE3: 192.168.2.3/24
BGP Instance ID 3
AS No. 100
iManager U2000
8-49
Router ID PE1: 192.168.0.1
PE2: 192.168.1.2
PE3: 192.168.2.3
Peer Peer IP Address PE1: 192.168.0.4
PE2: 192.168.1.3
PE3: 192.168.2.4
Peer AS No. PE1: 65410
PE2: 65420
PE3: 65430

Table 8-4 VPN2 parameter planning
Service Information Service Name L3VPN-0002
Network Type Full-Mesh
VRF ID 2
VRF Name vrf1
RD 200:1
RT 200:1
NE List Node Name PE1: NE(9-1)
PE2: NE(9-2)
PE3: NE(9-3)
PE2: 9-2
PE3: 9-3
Tunnel Binding (Static) Tunnel Name PE1: Tunnel-0001
PE2: Tunnel-0002
PE3: Tunnel-0003
SAI Interface Interface Name PE1, PE2, PE3: 1-EG16-2
(Port-2)
IP Address/Mask PE1: 192.168.1.1/24
PE2: 192.168.3.3/24
PE3: 192.168.0.3/24
BGP Instance ID 4
iManager U2000
Issue 01 (2010-08-16)
AS No. 100
Router ID PE1: 192.168.1.1
PE2: 192.168.3.3
PE3: 192.168.0.3
Peer Peer IP Address PE1: 192.168.1.4
PE2: 192.168.3.4
PE3: 192.168.0.2
Peer AS No. PE1: 65410
PE2: 65420
PE3: 65430

This topic describes how to configure the intranet VPN services described in the configuration
example.
Prerequisite
example.
The network must be created.
Procedure
1. In the NE Explorer, select PE1 and choose Configuration > MPLS Management > Basic
Apply.
Selection
LSR ID PE1: 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 and PE3. To set the parameters, such as LSR ID, for PE2
and PE3, see the preceding two steps.
iManager U2000
8-51
Selection
LSR ID PE2: 1.1.1.2
PE3: 1.1.1.3
The LSR ID must be unique
in the network.
a unicast tunnel.

Step 2 Configure network-side interfaces for PE1, PE2, and PE3.
1. In the NE Explorer, select PE1 and choose Configuration > Interface Management >
Ethernet Interface from the Function Tree. Then, configure network-side interfaces.
2. On the General Attributes tab page, select 3-EG16-1(Port-1) and 3-EG16-2(Port-2), and
set Port Mode to Layer 3. Set the parameters as required. Then, click Apply.
Selection
Enable Port Enabled Enable the port to carry a
tunnel.
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 3-EG16-1(Port-1) and 3-EG16-2(Port-2), and
set Enable Tunnel to Enabled and Specify IP Address to Manually. Set IP Address and
IP Mask. Then, click Apply.
Selection
Enable Tunnel Enabled Set this parameter
planning.
Max Reserved Bandwidth
(Kbit/s)
102400 The maximum reserved
bandwidth should not
exceed the physical
bandwidth of the bearer
port.
iManager U2000
Issue 01 (2010-08-16)
Selection
TE Measure 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 Address Manually Manually indicates that you
can set the IP address of the
port.
IP Address 3-EG16-1(Port-1):
192.168.2.1
3-EG16-2(port-2):
192.168.3.1
Set this parameter
planning.
IP Mask 255.255.255.0 Set this parameter
planning.

4. In the NE Explorer, select PE2. To set the attributes of the 3-EG16-1(Port-1) and 3-EG16-2
(Port-2) interfaces for PE2, see Step 2.1 to Step 2.3.
The settings of the PE2-3-EG16-1(Port-1) port are the same as those of the PE1-3-EG16-1
(Port-1) port. The IP address is 192.168.2.2.
Step 3 Configure user-side interfaces for PE1, PE2, and PE3.
The basic attributes of the PE1-1-EG16-1(Port-1) port are the same as those of the PE1-3-
EG16-1(Port-1) port. Specify IP Address of the layer 3 attribute is Unspecified and Enable
Tunnel is Disabled.
iManager U2000
8-53
Tunnel is Disabled.
Tunnel is Disabled.
Tunnel is Disabled.
Tunnel is Disabled.
Tunnel is Disabled.
1. In the NE Explorer, select PE1 and choose Configuration > Control Plane
Add. Select 3-EG16-1(Port-1) and 3-EG16-2(Port-2) and click OK.
Selection
Port 3-EG16-1(Port-1)
3-EG16-2(Port-2)
Set this parameter
planning.
Link Level level-1-2 Set this parameter
planning.
LSP Retransmission
Interval(s)
5 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
the local router transmits
the LSP again.
iManager U2000
Issue 01 (2010-08-16)
Selection
Minimum LSP
30 Set this parameter
planning.

3. Choose Configuration > Control Plane Configuration > MP-BGP Configuration from
the Function Tree. Click the MP-BGP Configuration tab.
4. Click New. In the Create MP-BGP Protocol Instance dialog box, set MP-BGP Instance
ID to 1 and MP-BGP Instance ID to 100. Click Apply.
5. Click the Peer Configuration tab. Click New. In the Create Peer dialog box, set the
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.
Selection
MP-BGP Instance 1 Set this parameter
planning.
Remote IP Address 1.1.1.2 The Remote IP Address
indicates the LSR ID of the
remote NE.
AS Number 100 Set this parameter
planning.

Selection
planning.
remote NE.
planning.

6. In the NE Explorer, select PE2. To set the parameters of the control plane for PE2, see the
preceding steps.
iManager U2000
8-55
The IS-IS protocol parameters of the 3-EG16-1(Port-1) and 3-EG16-2(Port-2) ports are the
same as those of PE1.
The MP-BGP protocol parameters are the same as those of PE1.
Selection
planning.
remote NE.
planning.

Selection
planning.
remote NE.
planning.

7. In the NE Explorer, select PE3. To set the parameters of the control plane for PE3, see the
preceding steps.
same as those of PE1.
The MP-BGP protocol parameters are the same as those of PE1.
iManager U2000
Issue 01 (2010-08-16)
Selection
planning.
remote NE.
planning.

Selection
planning.
Remote IP Address 1.1.1.2 The remote IP address is the
LSR ID of the remote NE.
planning.

Step 5 Create dynamic tunnels.
iManager U2000
8-57
Selection
planning.
planning.
planning.
to be created.

3. Configure the equipment list, double-click the equipment in the physical topology, and
select the source and sink equipment.
Selection
NE Role PE1: Ingress
PE2: Egress
node.
node.
Deploy Selected Select this check box when
you need to save the tunnel
on the U2000 and
meanwhile deploy the
tunnel to NEs.

4. Click Advanced and configure the details of tunnel management.
Table 8-5 Basic parameters
Selection
Tunnel ID Forward tunnel: 1
Reverse tunnel: 2
Set this parameter
planning.

iManager U2000
Issue 01 (2010-08-16)
Table 8-6 Affinity object parameters
Selection
Enable Affinity Forward and reverse
tunnels: Yes
are preferred during
rerouting.
Color Forward and reverse
tunnels: 0
value.
Mask Forward and reverse
tunnels: 0
value.

Table 8-7 Parameters of explicit hops information object
Selection
IP Address Forward tunnel:
192.168.2.2
Reverse tunnel:
192.168.2.1
Set the IP address passed by
a tunnel.
Hop Type Forward and reverse
tunnels: Include Strict
to Include Strict, the tunnel
is created strictly in the
sequence of the set IP
addresses.

Table 8-8 FRR attribute parameters
Selection
Enable FRR Forward and reverse
tunnels: Yes
FRR.BW.Type Forward and reverse
tunnels: Facility
iManager U2000
8-59
Selection
FRR Protect Type Forward and reverse
tunnels: Node Protection
node and the PLR.
Enable FRR.BW.Protect Forward and reverse
tunnels: Yes
enable the FRR bandwidth
protection.
FRR Bandwidth(Kbit/s) Forward and reverse
tunnels: 10000
Set this parameter
planning.

Selection
LSP Type Forward and reverse
tunnels: E-LSP
Level Forward and reverse
tunnels: 4
Set this parameter
planning.

Table 8-10 Setup attribute parameters
Selection
Enable Rerouter Forward and reverse
tunnels: Yes
Setup Priority Forward and reverse
tunnels: 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.
iManager U2000
Issue 01 (2010-08-16)
Selection
Hold Priority Forward and reverse
tunnels: 0
The hold priority must be
higher than the setup
priority. 0 indicates the
highest priority.
After a tunnel with a higher
hold priority is established,
the resources of this tunnel
are less likely to be
preempted when the
are insufficient.

5. Click OK. The dynamic tunnel is created.
6. To configure the dynamic tunnel between PE1 and PE3, see the preceding steps.
Selection
planning.
planning.
planning.
to be created.

iManager U2000
8-61
Table 8-12 NE list parameters
Selection
PE3: Egress
node.
node.
on the U2000 and
tunnel to NEs.

Table 8-13 Basic parameters of advanced attribute
Selection
Reverse tunnel: 4
Set this parameter
planning.

Selection
tunnels: Yes
rerouting.
tunnels: 0
value.
tunnels: 0
value.

iManager U2000
Issue 01 (2010-08-16)
Selection
192.168.3.2
Reverse tunnel:
192.168.3.1
a tunnel.
tunnels: Strictly Include
to Strictly Include, the
addresses.

Table 8-16 Parameters of fast rerouting attribute
Selection
tunnels: Yes
FRR Type Forward and reverse
tunnels: Facility
node and the PLR.
tunnels: Yes
protection.
FRR Bandwidth Forward and reverse
tunnels: 10000
Set this parameter
planning.

iManager U2000
8-63
Selection
tunnels: E-LSP
tunnels: 4
Set this parameter
planning.

Selection
tunnels: Yes
tunnels: 7
When resources are
insufficient, the tunnel with
a higher setup priority can
during establishment based
on network planning.
tunnels: 0
highest priority.
preempted when the
are insufficient.

7. To configure the dynamic tunnel between PE2 and PE3, see the preceding steps.
Selection
planning.
iManager U2000
Issue 01 (2010-08-16)
Selection
planning.
planning.
to be created.

Selection
PE3: Egress
node.
node.
on the U2000 and
tunnel to NEs.

Table 8-21 Basic parameters of advanced attribute
Selection
Reverse tunnel: 6
Set this parameter
planning.

iManager U2000
8-65
Selection
tunnels: Yes
rerouting.
tunnels: 0
value.
tunnels: 0
value.

Selection
192.168.4.1
Reverse tunnel:
192.168.4.2
a tunnel.
to Strictly Include, the
addresses.

Table 8-24 Parameters of fast rerouting attribute
Selection
tunnels: Yes
tunnels: Facility
iManager U2000
Issue 01 (2010-08-16)
Selection
node and the PLR.
tunnels: Yes
protection.
tunnels: 10000
Set this parameter
planning.

Selection
tunnels: E-LSP
tunnels: 4
Set this parameter
planning.

Selection
tunnels: Yes
tunnels: 7
When resources are
insufficient, the tunnel with
a higher setup priority can
during establishment based
on network planning.
iManager U2000
8-67
Selection
tunnels: 0
highest priority.
preempted when the
are insufficient.

Step 6 Create VPN1 and VPN2.
1. Choose Service > L3VPN Service > Create L3VPN Service from the main menu.
2. Configure VPN1 service parameters.
Table 8-27 Service information parameters
Selection
Service Name L3VPN-0001 Set this parameter
planning.
Network Type Full-Mesh Set this parameter
planning.
iManager U2000
Issue 01 (2010-08-16)
Selection
planning.
VRF Name vrf1 Set this parameter
planning.
RD 100: 1 Set this parameter
planning.
RT 100: 1 Set this parameter
planning.

Selection
Node Name PE1: NE(9-1)
PE2: NE(9-2)
PE3: NE(9-3)
Set this parameter
planning.
PE2: 9-2
PE3: 9-3
Set this parameter
planning.

3. Set the required parameters of PE1, PE2, and PE3 on the VRF configuration tab page at
the lower right corner.
Table 8-29 PE1 parameters
Selection
planning.
planning.
Import RT 100: 1 Set this parameter
planning.
iManager U2000
8-69
Selection
Export RT 100: 1 Set this parameter
planning.
Tunnel Name Tunnel-0001 and
Tunnel-0003
Set this parameter
planning.
Label Distribution Policy Per VPN Set this parameter
planning.
Interface Name 1-EG16-1(Port-1) Set this parameter
planning.
IP Address/Mask 192.168.0.1/24 Set this parameter
planning.
Instance ID(BGP) 3 The ID of BGP instance
here cannot be the same as
the ID of the MP BGP
instance of the control
plane.
AS No. 100 Set this parameter
planning.
Router ID 192.168.0.1 Set this parameter
planning.
Peer IP Address 192.168.0.4 Set this parameter
planning.
Peer AS No. 64510 Set this parameter
planning.

Selection
planning.
iManager U2000
Issue 01 (2010-08-16)
Selection
planning.
planning.
planning.
Tunnel-0005
Set this parameter
planning.
planning.
planning.
planning.
plane.
planning.
planning.
planning.
planning.

iManager U2000
8-71
Selection
planning.
planning.
planning.
planning.
Tunnel-0006
Set this parameter
planning.
planning.
planning.
planning.
plane.
planning.
planning.
planning.
iManager U2000
Issue 01 (2010-08-16)
Selection
planning.

4. Click OK. L3VPN-0001 is successfully created.
5. Create VPN2. For relevant parameter configuration, see the preceding steps.
Table 8-32 Service information parameters
Selection
planning.
Network Type Full-Mesh Set this parameter
planning.
planning.
planning.
planning.
RT 200: 1 Set this parameter
planning.

Selection
Node Name PE1: NE(9-1)
PE2: NE(9-2)
PE3: NE(9-3)
Set this parameter
planning.
iManager U2000
8-73
Selection
PE2: 9-2
PE3: 9-3
Set this parameter
planning.

Selection
planning.
planning.
planning.
planning.
Tunnel-0003
Set this parameter
planning.
planning.
planning.
planning.
plane.
planning.
iManager U2000
Issue 01 (2010-08-16)
Selection
planning.
planning.
planning.

Selection
planning.
planning.
planning.
planning.
Tunnel-0005
Set this parameter
planning.
planning.
planning.
planning.
iManager U2000
8-75
Selection
plane.
planning.
planning.
planning.
planning.

Selection
planning.
planning.
planning.
planning.
Tunnel-0006
Set this parameter
planning.
planning.
iManager U2000
Issue 01 (2010-08-16)
Selection
planning.
planning.
plane.
planning.
planning.
planning.
planning.

----End
8.8.2 Example for Configuring the Hub&Spoke VPN Service
This topic provides an example for configuring 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.
Networking Configuration Diagram
This topic provides the networking diagram of the sites of the Hub&Spoke VPN service.
Requirement and Networking Diagram
Figure 8-31 shows the networking diagram of the Hub&Spoke VPN service. The
communication between the Spoke-CE sites is controlled by the central site Hub-CE.
Specifically, all the Spoke-CE sites can communicate with site Hub-CE, but the Spoke-CE sites
cannot communicate with each other directly, the traffic between the Spoke-CE sites are
forwarded by the central site Hub-CE in addition to the Hub-PE sites. Three sets of PE equipment
iManager U2000
8-77
exist in this network. Each set of the PE equipment is connected to a CE site.Spoke-PE1, Spoke-
PE2, and Hub-PE are OptiX PTN 3900 NEs.The following shows the connectivity between any
two sites.
l Site Spoke-CE1 and site Hub-CE can communicate with each other.
l Site Spoke-CE2 and site Hub-CE can communicate with each other.
l Site Spoke-CE1 and site Spoke-CE2 cannot communicate with each other directly, the
traffic between the Spoke-CE sites are forwarded by the central site Hub-CE in addition to
the Hub-PE sites.
Figure 8-31 Networking of the Hub&Spoke VPN service
Spoke-CE1
Backbone
RD 100:1
Export RT
100:1
Import RT 200:1
RD 100:1
Export RT
200:1
Import RT
100:1
Site1
Site3
Site2
192.168.0.2
192.168.0.10
192.168.0.6
AS: 65410
AS: 65430
AS: 100
AS: 65420
Spoke-CE2
Spoke-PE1
Spoke-PE2
Hub-PE
Hub-CE
RD 100:1
Export RT
100:1
Import RT 200:1
VRF-IN
VRF-OUT

Figure 8-32 shows the NE planning diagram.
Spoke-CE1
Backbone
Site1
Site3
Site2
Spoke-CE2
Spoke-PE1
Spoke-PE2
Hub-PE
Hub-CE
1-EG16-1 ( Port -1) 3-EG16-1 ( Port -1)
192.168.1.1 192.168.0.1
1-EG16-1 ( Port -1) 3-EG16-1 ( Port -1)
192.168.2.1 192.168.0.5
1-EG16-1 ( Port -1)
3-EG16-1 ( Port -1)
192.168.2.2
192.168.0.9 3-EG16-2 ( Port -2)
192.168.1.2
VRF-IN
VRF-OUT
1-EG16-2 ( Port -2)
192.168.3.8
192.168.0.3
192.168.3.7
192.168.0.2
192.168.0.4

Service Planning
Site1 and Site2 are Spoke-CE sites and Site3 is a Hub-CE site.
iManager U2000
Issue 01 (2010-08-16)
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. Specifically, the traffic between the
Spoke-CE sites are forwarded by the central site Hub-CE in addition to the Hub-PE sites.
Table 8-37 shows the VPN parameter planning.
Table 8-37 VPN parameter planning
Service Name Service Name L3VPN-0001
Network Type Hub-Spoke
VRF ID Auto-Assign
RD 100:1
Hub RT 100:1
Spoke RT 200:1
NE List Node Name Spoke-PE1: NE(9-1)
Spoke-PE2: NE(9-2)
Hub-PE: NE(9-3)
Node IP Address/Node ID Spoke-PE1: 9-1
Spoke-PE2: 9-2
Hub-PE: 9-3
Tunnel Binding(Static) Tunnel Name Spoke-PE1: Tunnel-0001
Spoke-PE2: Tunnel-0003
Hub-PE: Tunnel-0001 and
Tunnel-0003
SAI Interface Interface Name Spoke-PE1: 1-EG16-1
(Port-1)
Spoke-PE2: 1-EG16-1
(Port-1)
Hub-PE3(VRF-IN): 1-
EG16-1(Port-1)
Hub-PE3(VRF-OUT): 1-
EG16-2(Port-2)
IP Address/Mask Spoke-PE1: 192.168.0.1/24
Spoke-PE2: 192.168.0.5/24
Hub-PE(VRF-IN):
192.168.0.9/24
Hub-PE(VRF-OUT):
192.168.3.8/24
iManager U2000
8-79
BGP Instance ID Spoke-PE1: 2
Spoke-PE2: 2
Hub-PE(VRF-IN): 2
Hub-PE(VRF-OUT): 3
AS No. 100
Router ID Spoke-PE1: 192.168.0.1
Spoke-PE2: 192.168.0.5
Hub-PE(VRF-IN):
192.168.0.9
Hub-PE(VRF-OUT):
192.168.3.8
Peer Destination IP Address Spoke-PE1: 192.168.0.2
Spoke-PE2: 192.168.0.4
Hub-PE: 192.168.0.3 and
192.168.3.7
Peer AS No. Spoke-PE1: 65410
Spoke-PE2: 65420
Hub-PE: 65430

This topic describes how to configure the Hub&Spoke VPN service described in the example.
Prerequisite
example.
The network must be created.
Procedure
Step 1 Specify LSR IDs for NEs.
1. In the NE Explorer, select Spoke-PE1 and choose Configuration > MPLS
Management > Basic Management from the Function Tree.
Apply.
iManager U2000
Issue 01 (2010-08-16)
Selection
LSR ID Spoke-PE1: 1.1.1.1 The LSR ID must be unique
in the network.
a unicast tunnel.

3. In the NE Explorer, select Spoke-PE2 and Hub-PE. To set the parameters, such as LSR ID,
for Spoke-PE2 and Hub-PE, see Step a and Step b.
Selection
LSR ID Spoke-PE2: 1.1.1.2
Hub-PE: 1.1.1.3
The LSR ID must be unique
in the network.
a unicast tunnel.

Step 2 Configure NNI 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 NNI port.
2. On the General Attributes tab page, select 3-EG16-1(Port-1) and set Port Mode to Layer
3. Set parameters as required. Click Apply.
Selection
Enable Port Enabled Enable the port to carry
tunnels.
Port Mode Layer 3 The port in the Layer 3
mode can carry channels.
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.

iManager U2000
8-81
3. On the Layer 3 Attributes tab page, select 3-EG16-1(Port-1), set Enable Tunnel to
Enabled and Specify IP Address to Manually, and set IP Address and IP Mask. Click
Apply.
Selection
planning.
(Kbit/s)
exceed the physical
port.
TE Measurement 10 You can intervene in the
link.
port.
IP Address 3-EG16-1(Port-1):
192.168.1.1
Set this parameter
planning.
planning.

4. In the NE Explorer, select Spoke-PE2. To configure the attributes of the 3-EG16-1(Port-1)
port, see Step Step 2.1 through Step Step 2.3.
Set the required parameters as follows:
The parameter settings of the Spoke-PE2-3-EG16-1(Port-1) port are the same as 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, see Step Step 2.1 through Step Step 2.3.
Selection
planning.
iManager U2000
Issue 01 (2010-08-16)
Selection
(Kbit/s)
exceed the physical
port.
TE Measurement 10 You can intervene in the
link.
port.
IP Address Hub-PE-3-EG16-1
(Port-1): 192.168.1.2
Hub-PE-3-EG16-2
(Port-2): 192.168.2.2
Set this parameter
planning.
planning.

Step 3 Configure UNI ports for Spoke-PE1, Spoke-PE2, and Hub-PE.
The basic attributes of the Spoke-PE1-1-EG16-1(Port-1) port are the same as the basic
attributes of the Spoke-PE1-3-EG16-1(Port-1) port, and the Specify IP Address parameter
in Layer 3 attributes is set to Unspecified and Enable Tunnel is Enabled.
The basic attributes of the Spoke-PE2-1-EG16-1(Port-1) port are the same as the basic
3. In the NE Explorer, select Hub-PE. To configure the attributes of the 1-EG16-1(Port-1)
The basic attributes of the Hub-PE-1-EG16-1(Port-1) port are the same as the basic
iManager U2000
8-83
1. In the NE Explorer, select Spoke-PE1 and choose Configuration > Control Plane
Add. Select the 3-EG16-1(Port-1) port and click OK.
Selection
Port 3-EG16-1(Port-1) Set this parameter
planning.
Link Level level-1-2 Set this parameter
planning.
LSP Retransmission
Interval(s)
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
LSP Retransmission
Interval(ms)
30 Set this parameter
planning.

3. Choose Configuration > Control Plane Configuration > MP-BGP Configuration from
the Function Tree. Click the MP-BGP Configuration tab.
4. Click New. In the Create MP-BGP Protocol Instance dialog box, set MP-BGP Instance
ID to 1 and AS No. to 100. Click Apply.
5. Click the Peer Configuration tab. Click New. In the Create Peer dialog box, set the
parameters.
Selection
BGP Instance ID 1 Set this parameter
planning.
remote NE.
planning.
iManager U2000
Issue 01 (2010-08-16)

6. In the NE Explorer, select Spoke-PE2. To set the parameters of the control plane for Spoke-
PE2, see the preceding steps.
The IS-IS protocol parameters of the 3-EG16-1(Port-1) port are the same as the IS-IS
protocol parameters of Spoke-PE1.
The MP-BGP protocol parameters are the same as the MP-BGP protocol parameters of
Spoke-PE1.
Set the following parameters to configure Hub-PE as an MP-BGP peer.
Selection
BGP Instance 1 Set this parameter
planning.
remote NE.
planning.

7. In the NE Explorer, select Hub-PE. To set the parameters of the control plane for Hub-PE,
see the preceding steps.
same as the IS-IS protocol parameters of Spoke-PE1.
The MP-BGP protocol parameters are the same as the MP-BGP protocol parameters of
Spoke-PE1.
Set the following parameters to configure Spoke-PE1 as an MP-BGP peer.
Selection
planning.
remote NE.
planning.

Set the following parameters to configure Spoke-PE2 as an MP-BGP peer.
iManager U2000
8-85
Selection
planning.
remote NE.
planning.

Step 5 Create dynamic tunnels.
Selection
planning.
planning.
planning.
to be created.
iManager U2000
Issue 01 (2010-08-16)

3. Configure the equipment list, double-click the equipment in the physical topology, and
select the source and sink equipment.
Selection
NE Role Spoke-PE1: Ingress
Hub-PE: Egress
Ingress indicates an
ingress node. In this
example, NE1 is the ingress
node.
Egress indicates an egress
is the egress node.
on the U2000 and
tunnel to the NEs.

4. Click Advance and configure the details of tunnel management.
Table 8-38 General information
Selection
Reverse tunnel: 2
Set this parameter
planning.

Selection
tunnels: Yes
rerouting.
tunnels: 0
The colors of the forward
and reverse tunnels are the
same.
tunnels: 0
The masks of the forward
same.

iManager U2000
8-87
Table 8-40 Parameters of the explicit hop information object
Selection
192.168.2.1
Reverse tunnel:
192.168.1.1
a tunnel.
When you set Hop Type to
Strictly Include, the tunnel
strictly follows the
sequence of set IP
addresses during
establishment.

Table 8-41 FRR attributes
Selection
tunnels: Yes
Select this check box to
enable FRR.
tunnels: Facility
Only Facility can be
selected. In this mode, one
bypass tunnel can protect
multiple LSPs.
It is required that the bypass
tunnel selected for a PLR
protect the downstream
neighboring nodes of the
PLR and the links between
the PLR and its
downstream neighboring
nodes.
Enable FRR BW Protect Forward and reverse
tunnels: Yes
enable FRR bandwidth
protection.
tunnels: 10000
Set this parameter
planning.

iManager U2000
Issue 01 (2010-08-16)
Table 8-42 QoS configuration parameters
Selection
tunnels: E-LSP
Currently, you can set LSP
Type to only E-LSP.
tunnels: 4
Set this parameter
planning.

Table 8-43 Setup attributes
Selection
tunnels: Yes
Set this parameter
planning.
tunnels: 7
Set this parameter
planning. When resources
are insufficient, the tunnel
with a higher setup priority
can preempt the bandwidth
during establishment.
tunnels: 0
The hold priority should be
priority. The value 0
priority.
is less likely to be
preempted when the
are insufficient.

5. Click OK. The dynamic tunnel is created.
6. To configure the dynamic tunnel between Spoke-PE2 and Hub-PE, see the preceding steps.
iManager U2000
8-89
Table 8-44 General information
Selection
planning.
planning.
planning.
Create Reverse Tunnel Selected Select this check box when
you need to create a reverse
tunnel.

Table 8-45 NE list
Selection
NE Role Spoke-PE2: Ingress
Hub-PE: Egress
Ingress indicates an
ingress node. In this
example, NE1 is the ingress
node.
Egress indicates an egress
is the egress node.
on the U2000 and
tunnel to the NEs.

Table 8-46 Basic information about the advanced attributes
Selection
Reverse tunnel: 4
Set this parameter
planning.

iManager U2000
Issue 01 (2010-08-16)
Selection
tunnels: Yes
rerouting.
tunnels: 0
The colors of the forward
same.
tunnels: 0
The masks of the forward
same.

Table 8-48 Parameters of the explicit hop information object
Selection
192.168.2.1
Reverse tunnel:
192.168.2.2
a tunnel.
When you set Hop Type to
Strictly Include, the tunnel
strictly follows the
sequence of set IP
addresses during
establishment.

Table 8-49 FRR attributes
Selection
tunnels: Yes
enable FRR.
tunnels: Facility
Only Facility can be
selected. In this mode, one
bypass tunnel can protect
multiple LSPs.
iManager U2000
8-91
Selection
It is required that the bypass
tunnel selected for a PLR
protect the downstream
neighboring nodes of the
PLR and the links between
the PLR and its
downstream neighboring
nodes.
Enabled FRR BW Protect Forward and reverse
tunnels: Yes
enable FRR bandwidth
protection.
tunnels: 10000
Set this parameter
planning.

Table 8-50 QoS configuration parameters
Selection
tunnels: E-LSP
Currently, you can set LSP
Type to only E-LSP.
tunnels: 4
Set this parameter
planning.

Table 8-51 Setup attributes
Selection
tunnels: Yes
Set this parameter
planning.
tunnels: 7
Set this parameter
planning. When resources
are insufficient, the tunnel
with a higher setup priority
can preempt the bandwidth
during establishment.
iManager U2000
Issue 01 (2010-08-16)
Selection
tunnels: 0
The hold priority should be
priority. The value 0
priority.
is less likely to be
preempted when the
are insufficient.

Step 6 Create VPN services.
1. Choose Service > L3VPN Service > Create L3VPN Service from the main menu.
2. Set the parameters of the BPG/MPLS VPN service.
Table 8-52 Service information
Selection
planning.
Network Type Hub-Spoke Set this parameter
planning.
planning.
VRF Name VRF-IN Set this parameter
planning.
planning.
Hub RT 200:1 Set this parameter
planning.
Spoke RT 100:1 Set this parameter
planning.

iManager U2000
8-93
Table 8-53 NE list
Selection
Node Name Spoke-PE1: NE(9-1)
Spoke-PE2: NE(9-2)
Hub-PE: NE(9-3)
Set this parameter
planning.
Node IP Address/Node ID Spoke-PE1: 9-1
Spoke-PE2: 9-2
Hub-PE: 9-3
Set this parameter
planning.

3. Set the required parameters on the VRF Configure tab page in the lower right corner.
Table 8-54 Hub-PE parameters
Selection
RD VRF-IN: 100: 1
VRF-OUT: 200: 1
Set this parameter
planning.
Import RT VRF-IN: 100: 1 Set this parameter
planning.
Export RT VRF-OUT: 200: 1 Set this parameter
planning.
Tunnel Name VRF-IN: Tunnel-0001,
Tunnel-0003
Set this parameter
planning.
planning.
Interface Name VRF-IN: 1-EG16-1
(Port-1)
VRF-OUT: 1-EG16-2
(Port-2)
Set this parameter
planning.
IP Address/Mask VRF-IN: 192.168.0.9/24
VRF-OUT: 192.168.3.8/24
Set this parameter
planning.
iManager U2000
Issue 01 (2010-08-16)
Selection
Instance ID(BGP) VRF-IN: 2
VRF-OUT: 3
The ID of BGP instance
plane.
AS No. VRF-IN: 100
VRF-OUT: 200
Set this parameter
planning.
Router ID VRF-IN: 192.168.0.9
VRF-OUT: 192.168.3.8
Set this parameter
planning.
Destination IP Address VRF-IN: 192.168.0.3
VRF-OUT: 192.168.3.7
Set this parameter
planning.
Peer AS No. VRF-IN: 65430
VRF-OUT: 65430
Set this parameter
planning.

Table 8-55 Spoke-PE1 parameters
Selection
planning.
planning.
planning.
planning.
planning.
planning.
iManager U2000
8-95
Selection
planning.
plane.
planning.
planning.
Destination IP Address 192.168.0.2 Set this parameter
planning.
planning.

Table 8-56 Spoke-PE2 parameters
Selection
planning.
planning.
planning.
planning.
planning.
iManager U2000
Issue 01 (2010-08-16)
Selection
planning.
planning.
plane.
planning.
planning.
Destination IP Address 192.168.0.4 Set this parameter
planning.
planning.

4. Click OK. L3VPN-0001 is successfully created..
----End
iManager U2000
8-97
9 Configuring Dual-Homing Protection
About This Chapter
The PTN can fast implement dual-homing protection for an E-Line service when a dual-homing
node, the AC link of a dual-homing node, or the PW of a network-side service is faulty. This
topic describes the concept, application, and configuration method of dual-homing protection.
9.1 Configuration Flow of Dual-Homing Protection
This section describes the configuration flow of dual-homing protection with the focuses on
each task included in the configuration and details on each task.
9.2 Operation Tasks for Configuring the Dual-Homing Protection
The operation tasks for configuring the dual-homing protection include the configuration of AC-
side cross-equipment link protection group and the configuration of network-side MC-PW APS
protection.
9.3 Example of Dual-Homing Protection with 1:1 MC-PW APS and MC-LAG
This section provides an example of dual-homing protection with NNI-side 1:1 MC-PW APS
and UNI-side MC-LAG with focuses on example description and configuration process.
iManager U2000
Operation Guide for PTN End-to-End Management 9 Configuring Dual-Homing Protection
9-1
9.1 Configuration Flow of Dual-Homing Protection
This section describes the configuration flow of dual-homing protection with the focuses on
each task included in the configuration and details on each task.
Prerequisites
You must configure the services to be protected by dual-homing protection.
Configuration Flow
Figure 9-1 shows the configuration flow for dual-homing protection.
NOTE
l In the figure, attachment circuit (AC) indicates the access side. In the following description, AC is used to
describe the access side.
l In the figure, MC represents multi-chassis. In the following description, MC is used to describe multi-chassis.
Figure 9-1 Configuration flow for dual-homing protection
Start
Configure AC-side
MC protection
Configure network-
side protection
Configure MC
synchronization
protocol
communication
End
MC-LMSP Configure MC-LMSP
protection groups
Configure MC-LAG
protection
Required
Optional
AC-side
protection
scheme?
Configure
MC-PW APS
protection
Configure
PW redundancy
protection
Configure the MAC
address withdrawal
function
MC-PW APS
PW redundancy
protection
MAC address
withdrawal
Network-side
protection
scheme?
MC-LAG

Configuration Flow
Table 9-1 provides description of each task in the configuration flow for dual-homing protection.
iManager U2000
Issue 01 (2010-08-16)
Table 9-1 Description of tasks in the configuration flow for dual-homing protection
Configuration Task Remarks
Configuring AC-
Side MC
Protection
Configuring MC Synchronization
Communication
By means of MC synchronization
communication, dual-homing nodes
periodically notify the status of AC-
side links to each other, and
coordinate actions in response to
faults.
Before configuring MC-LAG or
MC-LMSP, you must configure the
opposite information about MC
synchronization communication on
the two dual-homing nodes.
Configuring an MC-LAG
Protection
When configuring MC-LAG
protection, you must complete the
following configuration tasks in
order:
1. Configure SC-LAG protection
groups on two dual-homing
nodes.
2. Configure MC-LAG protection
nodes.
Configuring MC-LMSP
Protection Group
When configuring MC-LMSP
protection group, you must
complete the following
configuration task:
l Configure MC-LMSP protection
nodes.
iManager U2000
9-3
Configuration Task Remarks
Configuring
NNI-Side
Protection
Configuring MC-PW APS
Protection
When configuring MC-PW APS
order:
1. Configure a PW APS protection
group on a non-dual-homing
node.
2. Configure service to be protected
on the protection dual-homing
node.
3. Configure an MC-PW APS
protection group on the slave
dual-homing node.
4. Configure an MC-PW APS
protection group on the master
dual-homing node.
5. Bundle slave MC-PW APS.
If a new MC-PW APS needs to
be bound to an existing MC-PW
APS, this configuration task is
mandatory.
Configuring PW Redundancy
Protection
When configuring PW redundancy
order:
1. Configure service to be protected
on the protection dual-homing
node.
2. Configure a PW redundancy
protection group on a non-dual-
homing node.

9.2 Operation Tasks for Configuring the Dual-Homing
Protection
The operation tasks for configuring the dual-homing protection include the configuration of AC-
side cross-equipment link protection group and the configuration of network-side MC-PW APS
protection.
9.2.1 Configuring the MC-LAG
This topic describes the basic concept of the LAG and how to configure the MC-LAG.
9.2.2 Operation Tasks for Configuring MC-PW APS
MC-PW APS protection and AC-side MC-LAG protection work together to implement dual-
homing protection for E-Line services. This topic describes how to configure the network-side
iManager U2000
Issue 01 (2010-08-16)
MC-PW APS protection in the dual-homing protection scenario. Specifically, how to configure
the MC-PW APS and bind the slave MC-PW APS.
9.2.1 Configuring the MC-LAG
This topic describes the basic concept of the LAG and how to configure the MC-LAG.
Introduction to the LAG
Link aggregation indicates that a group of Ethernet links are bound to form a logic link, that is,
link aggregation group (LAG). This helps to provide higher bandwidth and link reliability. PTN
equipment supports LAG protection for UNI Ethernet links. In addition, manual aggregation
and static aggregation are supported.
Definition
Link aggregation indicates that a group of physical Ethernet interfaces are bound together to
form a logical interface (that is, a LAG). Link aggregation increases bandwidth and provides
link protection. As shown in Figure 9-2, a LAG works between adjacent sets of equipment and
is irrelevant to the entire network structure. On an Ethernet, a link corresponds to a port, so the
link aggregation is also called the port aggregation.
Figure 9-2 Link Aggregation Group
Ethernet Message
Link 1
LAG
Ethernet Message
Link 2
Link 3

Equipment supports two aggregation modes, that is, manual aggregation and static aggregation.
There are two service sharing modes for each aggregation mode, that is, loading sharing and
non-load sharing.
Manual aggregation: In this mode, you need to manually create a LAG and add member links
to the LAG. In addition, the link aggregation control protocol (LACP) is not required in this
mode. Therefore, when equipment is interconnected with the equipment that does not support
LACP, the link aggregation still works. As a result, if a unidirectional fault occurs on a member
link (for example, a fiber cut occurs in one direction of an Ethernet optical interface), the transmit
end of the cut fiber cannot detect the fault, and the service is affected (in the load sharing mode)
or interrupted (in the non-load sharing mode).
Static aggregation: In this mode, you need to manually create a LAG and add member links to
the LAG. The LACP protocol is required in this mode. The LACP protocol does not change the
configuration information. Exchanging LACP packets allows the systems at the two ends of a
LAG to negotiate the aggregation instead of fully depending on the configuration of a single
end. As a result, the aggregation is controlled in a more accurate and effective manner.
Load sharing mode: In this mode, service traffic is available on each member link of the LAG,
and the member links share service transmission. To ensure that packets on member links are
iManager U2000
9-5
in order and that the service traffic is evenly distributed on each member link, on the receive
side, the LAG algorithm is used to re-arrange the disordered packets, and the sharing algorithm
is used to distribute packets to each link of the LAG based on a certain feature value of the
packets (for example, source MAC address or sink MAC address). When LAG members change,
or certain links fail, the system automatically reallocates traffic. This brings many benefits of
the link aggregation, such as higher bandwidth that is increased in a linear manner.
Non-load sharing: There are a maximum of two members in an LAG. One member, which is in
the active state, is used as an active link to carry the service traffic. The other member is in the
standby state. When the active link is faulty, the system activates the link in the standby state to
carry the service traffic.
Purposes and Benefits
LAG works between the MAC sub-layer and the LLC sub-layer and belongs to the data link
layer.
LAG has the following functions:
l Improving the link reliability: In a LAG, member links dynamically back up each other.
Once a member link is interrupted, another member link takes over its work immediately.
The backup process of a LAG is associated with the member links in this LAG, but is not
associated with the links outside this LAG.
l Increasing the link capability: A LAG can provide an economic method of increasing the
link transmission rate. When multiple physical links are bound, you can obtain a data link
with higher bandwidth, without upgrading the existing equipment. The capacity of a LAG
equals the sum of the capacity of all member links. According to a certain algorithm, the
aggregation module allocates traffic to different member links, to realize the link-level load
sharing.
l Using LAG without modifying the higher-layer protocol or applications: LAG works at the
data link layer, and is irrelevant to the higher-layer protocol and applications.
Networking Application
The equipment supports the LAG application on the UNI side. As shown in Figure 9-3, a LAG
is created. In addition , the intra-card LAG and inter-card LAG are supported. The bandwidth
for Ethernet services between the adjacent equipment is increased in a linear manner. What's
more, link reliability is improved.
Figure 9-3 LAG networking
Intra-card LAG
Inter-card LA
Ethernet
card
NE NE
Ethernet
card
Ethernet
card
Ethernet
card
iManager U2000
Issue 01 (2010-08-16)
MC-LAG
Multi-chassis link aggregation group (MC-LAG) is an extension of LAG defined in IEEE 802.3.
In the case of MC-LAG, the links on multiple NEs are aggregated as one group to increase
bandwidth. When one link or one NE in the group is faulty, MC-LAG functions to switch the
data flow to other available links in the MC-LAG. This section describes the MC-LAG in aspects
of the working principle, application for dual-homing protection, and support of the PTN
equipment.
Working Principle of MC-LAG
As shown in Figure 9-4, the services from BTS/NodeB are transported to BSC/RNC over the
PTN network. PE1, PE2, and BSC/RNC interoperate with each other to achieve MC-LAG
protection for services.
Figure 9-4 MC-LAG for dual-homing protection
PE3
PE1
PE2
BTS/NodeB
A
S
LAG3
LAG1
LAG2
MC synchronization communication Active (carrying services)
Standby (not carrying services)
A
S
MC-LAG
Note:
LAG1 and LAG2 may have one member link.
BSC/RNC

The MC-LAG consists of single-chassis (SC) LAGs (LAG1 and LAG2) on PE1 and PE2, MC-
LAG between PE1 and PE2, and LAG (LAG3) on BSC/RNC. By means of MC synchronization
communication of MC-LAG, PE1 and PE2 periodically notify the status of LAG1 and LAG2
to each other, and coordinate actions in response to faults. In addition, when the working status
of the AC-side link changes, PE1 and PE2 notify the status change to the NNI-side protection
protocol.
MC synchronization communication can be shared by all MC-LAG and MC-LMSP between
PE1 and PE2. Hence, you need to configure MC synchronization communication tunnel for only
one time. To ensure quick switching and to improve reliability of MC-LAG or MC-LMSP, you
must set up a direct MC synchronization communication tunnel between PE1 and PE2 and
configure protection for the tunnel.
The PTN equipment supports non-load-sharing MC-LAG. That is, only either LAG1 or LAG2
carries services and is active. The PTN equipment supports static SC-LAG and manual SC-LAG
iManager U2000
9-7
in the MC-LAG. The aggregation modes of the SC-LAGs on the two dual-homing nodes and
BSC/RNC must be the same. In addition, if the MC-LAG contains more than two member links,
the SC-LAG on BSC/RNC must work in load-sharing mode.
1. Static Aggregation
In static aggregation mode, the equipment exchanges the LACP protocol packets to select LAG1
or LAG2 to carry services. The selection process is as follows:
l LAG1, LAG2, and LAG3 exchange protocol packets between each other. Then, LAG1,
LAG2, or LAG3 is selected to determine which link (non-load-sharing MC-LAG) or links
(load-sharing MC-LAG) in the MC-LAG carry services according to the LAG system
priority or system MAC address.
The LAG with the highest system priority is preferred. When the system priorities of the
LAGs are the same, the LAG with the smallest MAC address is preferred. The system MAC
address indicates the system MAC address of the equipment with the LAG.
l When an LAG is selected, the LAG chooses one (non-load-sharing LAG) or more (load-
sharing LAG) member links to carry services according to the priorities and status of its
member ports, and then the LAG negotiates with the opposite end to reach an agreement.
Generally, configure a higher system priority for the SC-LAG on a dual-homing node than that
for the SC-LAG on BSC/RNC so that LAG1 or LAG2 with higher bandwidth carries services.
PE1 and PE2 notify their available bandwidth to each other by means of MC communication.
MC-LAG selects LAG1 or LAG2 with higher available bandwidth to carry services. When the
available bandwidth of LAG1 is the same as that of LAG2, LAG1 or LAG2 is selected in the
preceding process.
2. Manual Aggregation
In manual aggregation mode, LAG1 or LAG2 contains only one member link, and there are the
following conditions:
A. BSC/RNC supports manual LAG and an SC LAG is configured for interconnection
with dual-homing nodes.
When configuring system priorities for LAG1 and LAG2, make sure that the dual-homing nodes
and BSC/RNC carry services over the same link. To ensure normal switching of MC-LAG in
case of a unidirectional fiber cut, configure Ethernet port OAM so that it monitors the working
status of LAG member links. In this case, you need to enable Ethernet port OAM (IEEE 802.3ah)
for the member links of LAG1 and LAG2, and set Link Trace Protocol to 802.3ah for LAG1
and LAG2.
The two dual-homing nodes exchange information by means of MC synchronization
communication, and select LAG1 or LAG2 to carry services according to the system priority or
MAC address of equipment. The dual-homing nodes select the LAG with a higher priority with
preference. When the two LAGs are of the same system priority, the dual-homing nodes select
the LAG on the equipment with a smaller MAC address. Then, BSC/RNC selects a link in LAG3
to carry services according to a certain rule.
B. BSC/RNC does not support LAG but supports extension of IEEE 802.3ah.
In this case, you need to enable Ethernet port OAM (IEEE 802.3ah) and extension of IEEE
802.3ah for the two links in the MC-LAG. For LAG1 and LAG2, set Link Trace Protocol to
IEEE 802.3ah, Switch Protocol to extension of IEEE 802.3ah, and Switch Mode to Passive
(passive only for an LAG). For BSC/RNC, set the switch mode to active.
In this case, BSC/RNC periodically transmits IEEE 802.3ah extension packets over the selected
active link and standby link. The packets contain information about the working status of the
iManager U2000
Issue 01 (2010-08-16)
links (active or standby). When receiving the IEEE 802.3ah extension packets, the dual-homing
nodes select LAG1 or LAG2 to carry service packets.
3. MC-LAG Switching Rule
An LAG, static or manual, must be in line with the following switching principles:
l When LAG1 and LAG2 are in non-load-sharing mode, protection of LAG1 or LAG2 takes
place first in case of a link fault. If the member ports of LAG1 or LAG2 are faulty, the
services are switched to the LAG on the opposite equipment.
l When LAG1 and LAG2 are in load-sharing mode, the NEs notify the available bandwidth
of LAG1 and LAG2 to each other. Then, either LAG1 or LAG2 with higher available
bandwidth is selected to carry services.
l When the working status of the AC-side LAG changes, PE1 and PE2 notify the status
change to the NNI-side protection protocol.
Application of MC-LAG for Dual-Homing Protection and Support for MC-LAG
Table 9-2 lists the details on application of MC-LAG for dual-homing protection.
Table 9-2 Application of MC-LAG for dual-homing protection
Protected Service Protection Scheme Protection Point
E-Line service 1:1 MC-PW APS and MC-
LAG
Dual-homing nodes, AC-side
links of dual-homing nodes,
and service PWs
1:1 PW redundancy
protection and MC-LAG
Dual-homing nodes and AC-
side links of dual-homing
nodes
E-LAN service MAC address withdrawal
and MC-LAG
Dual-homing nodes and AC-
side links of dual-homing
nodes

Currently, the PTN equipment supports only non-load-sharing MC-LAG. It is recommended to
configure LAGs in the same load-sharing mode on dual-homing nodes, that is, PE1 and PE2.
Hence, there are two application scenarios of MC-LAG. In one scenario, the SC-LAGs on dual-
homing nodes are in non-load-sharing mode. In the other scenario, the SC LAGs on dual-homing
nodes are in load-sharing mode. Table 9-3 andTable 9-4 list the details on how the PTN
equipment supports the two application scenarios of MC-LAG.
NOTE
In case of discrepancy between the load-sharing modes on the dual-homing nodes (PE1 and PE2), the available
bandwidth of the SC LAGs of the nodes are different. When the services are switched from one SC LAG to the
other, service packets may be lost.
iManager U2000
9-9
Table 9-3 Support for MC-LAG application scenario I (SC LAGs on dual-homing nodes in non-
load-sharing mode)
Position
of LAG
Load
Sharing
Mode
Revertive
Mode
Aggregation Mode Remarks
LAG1 on
PE1
Non-
load-
sharing
Revertive or
non-revertive
Manual aggregation or
static aggregation
NOTE
l The aggregation
modes of the LAGs on
PE1, PE2, and BSC/
RNC must be the
same.
l In static aggregation
mode, the LAG is
highly reliable and
thus is recommended.
In the case of
interconnection with
the equipment that
does not support the
LACP protocol,
manual aggregation
mode is applicable to
SC-LAGs in an MC-
LAG.
For details on load-
sharing mode,
revertive mode, and
aggregation mode,
see Introduction to
the LAG.
LAG2 on
PE2
Non-
load-
sharing
Revertive or
non-revertive
MC-LAG Non-
load-
sharing
Revertive or
non-revertive
-

Table 9-4 Support for MC-LAG application scenario II (SC LAGs on dual-homing nodes in
load-sharing mode)
Position of
LAG
Load Sharing
Mode
Revertive
Mode
Aggregation
Mode
Remarks
LAG1 on
PE1
Load sharing - Same as that for
application scenario
I.
For details on
load-sharing
mode, revertive
mode, and
aggregation
mode, see
Introduction to
the LAG.
LAG2 on
PE2
Load sharing -
MC-LAG Non-load-
sharing
Revertive or
non-revertive
-

Configuring the MC-LAG Protection
An MC-LAG can inter-cooperate with NNI-side MC-PW APS or PW redundancy to implement
dual-homing protection for E-Line services; an MC-LAG can also inter-cooperate with NNI-
side MAC address withdrawal technology to implement dual-homing protection for E-LAN
iManager U2000
Issue 01 (2010-08-16)
services. This topic describes how to configure MC-LAG protection when the AC-side links are
Ethernet links in a dual-homing scenario.
Prerequisite
Configuration Networking Diagram
As shown in Figure 9-5, services from BTS/NodeB are transported to BSC/RNC, and PE1, PE2,
and BSC/RNC inter-cooperate to implement MC-LAG protection for the services.
Figure 9-5 Configuring an MC-LAG in a Dual-Homing Protection Scenario
PE3
PE1
PE2
BTS/NodeB
A
S
LAG3
LAG1
LAG2
MC synchronization communication Active (carrying services)
A
S
MC-LAG
Note:
LAG1 and LAG2 may have one member link.
BSC/RNC

Configuration Guide
l For details on how the PTN equipment supports MC-LAG, see Table 9-3 and Table 9-4
in MC-LAG.
l If a service on a dual-homing node is configured with protection, the UNI port accessing
the service must be configured as the master port in the SC-LAG on the dual-homing node.
l It is recommended that you set load-sharing modes of the SC-LAGs on dual-homing nodes
PE1 and PE2 as the same.
NOTE
If the load-sharing modes are different, the available bandwidths of the two SC-LAGs are different. When
services are switched from an SC-LAG to another, packet loss may occur.
l You must configure SC-LAGs on the two dual-homing nodes and then configure MC-LAG
protection groups on the two dual-homing nodes.
iManager U2000
9-11
l The aggregation modes of the SC-LAGs on the two dual-homing nodes and BSC/RNC
must be the same.
l Restoration Mode of the MC-LAG protection groups on the two dual-homing nodes must
be the same.
l Reliability of LAGs in static aggregation mode is higher than that of LAGs in manual
aggregation mode and thus the static aggregation mode is usually recommended. If MC-
LAG is based on interconnection with the equipment that does not support the LACP
protocol, only the manual aggregation mode is applicable.
l If the SC-LAG on BSC/RNC contains more than two member links, the load-sharing mode
of the SC-LAG on BSC/RNC must be set to load sharing.
l For convenient management, maintenance, and fault identification, it is recommended to
configure AC-side MC-LAG as follows:
Set related parameters for all AC-side MC-LAGs so that all the active links in MC-LAG
are on the same dual-homing node.
Set related parameters for AC-side MC-LAGs and configure the working PW (that is,
Service PW) of NNI-side MC-PW APS so that the active AC-side links and the NNI-
side working PW are on the same dual-homing node.
Procedure
Step 1 Display the interface where you can create the services to be protected.
l In the case of a PWE3 service, Choose Service > PWE3 Service > Create PWE3 Service
from the main menu.
l In the case of a VPLS service, Choose Service > VPLS Service > Create VPLS Service
from the main menu.
Step 2 Create a PWE3 service and configure the basic information, source NE, and sink NE of the
service. Click the Service Topology tab page.
Step 3 In the Service Topology view, select two NEs, right-click, and choose ETrunk from the
shortcut menu. The Create Cross-Equipment Link Aggregation Management Group dialog
box is displayed.
Step 4 On the left NE, configure LAG1, the intra-NE link aggregation group. Click .... The Link
Aggregation Group Management window is displayed.
iManager U2000
Issue 01 (2010-08-16)
1. Select an existing LAG and click OK.
2. Optional: Click New. In the Create Link Aggregation Group dialog box, set relevant
attributes and click OK.
iManager U2000
9-13
NOTE
l After you select the Automatically Assign check box, the U2000 automatically assigns the LAG
No. Otherwise, you need to manually enter the LAG No.
l When LAG Type is Static, the link aggregation control protocol (LACP) is running. When LAG
Type is Manual, the LACP is not running.
l Sharing means that each member link of the LAG carries the services at the same time and shares
the load together. Non-Sharing indicates that only one member link of the LAG has traffic.
l After creating a LAG of the static aggregation mode, you can query the Link Aggregation Group
Details and Link LACP Packet Statistics of this LAG.
Step 5 On the right NE, configure LAG2, the intra-NE LAG. For details, see descriptions in the
preceding step.
Step 6 On the left NE, configure the inter-NE synchronization communication between the two NEs.
Click .... The Synchronization Protocol Management window is displayed.
1. Select an existing inter-NE protocol channel and click OK.
2. Optional: Click New. In the Create Cross-Equipment Synchronization Protocol dialog
box, set relevant attributes and click OK.
iManager U2000
Issue 01 (2010-08-16)
Step 7 On the right NE, configure the inter-NE synchronization communication between the two NEs.
For details, see descriptions in the preceding step.
Step 8 Set relevant attributes and click OK. A dialog box is displayed indicating that the operation is
successful.
Step 9 Click Close.
----End
9.2.2 Operation Tasks for Configuring MC-PW APS
MC-PW APS protection and AC-side MC-LAG protection work together to implement dual-
homing protection for E-Line services. This topic describes how to configure the network-side
MC-PW APS protection in the dual-homing protection scenario. Specifically, how to configure
the MC-PW APS and bind the slave MC-PW APS.
Configuring MC-PW APS
This topic describes how to configure the network-side MC-PW APS and bind the slave MC-
PW APS for dual-homing nodes and non-dual-homing nodes in the dual-homing protection
scenario.
Prerequisite
l The MPLS tunnel that carries the PW must be created. For how to create a tunnel, see 3.3.1
Creating a Tunnel.
l All equipment resources, including logical ports, QoS, and PW templates, must be
available.
Networking Diagram
As shown in Figure 9-6, the services from BTS/NodeB are transported to BSC/RNC through
the PTN network. The MC-PW APS consists of the PW APS protection group on PE3 and MC-
PW APS protection groups on PE1 and PE2.
iManager U2000
9-15
Figure 9-6 Networking diagram of MC-PW APS for dual-homing protection
W
P
PE3
PE1
PE2
BTS/NodeB
1:1 PW APS
MC-PW
APS
BSC/RNC
AC side
DNI-PW
Working
Protection
W
P
AC side
MC protection
MC synchronization communication

MC-PW APS
MC-PW APS protection involves the working PW, protection PW, and DNI-PW. In the case of
PW APS, PW OAM functions to detect the status of the working PW, protection PW and DNI-
PW. When PE equipment detects a fault on the working PW, the PE equipment at both ends
performs PW APS protection switching by exchanging the APS protocol. Then, the services on
the working PW are switched to the protection PW. In this manner, the services are protected.
The APS protocol is transported over the protection PW. After dual-homing protection switching
occurs in case of certain faults, the DNI-PW in MC-PW APS carries service packets. In addition,
the DNI-PW is also used for MC communication of status information between dual-homing
nodes. MC-PW ASP achieves MC status communication over DNI-PW so that PE1 and PE2
perform coordinated switching.
Binding a Slave MC-PW APS
If the working PWs, protection PWs, and DNI-PWs of multiple MC-PW APS to be created share
the same source and sink with the working PW, protection PW, and DNI-PW of an MC-PW
APS, you can bind these multiple MC-PW APS to be created to the MC-PW APS (master MC-
PW APS). Then, the protection switching is performed for all the slave MC-PW APS according
to the PW status of the master MC-PW APS. These PWs are considered as being in one MC-
PW APS for synchronous detection and switching. In this manner, the switching time is reduced,
and the OAM resources and APS resources are saved.
Currently, the PTN supports the revertive and non-revertive dual-ended 1:1 PW APS protection.
Procedure
Step 2 Create an E-Line service and configure information relevant to the service. For how to configure
a test group, see 6.4.2 Creating an ETH Service.
Step 3 Configure the MC-PW APS protection and slave MC-PW APS protection.
iManager U2000
Issue 01 (2010-08-16)
1. In the case of the general attributes of the service, set Protection Type to PW APS
protection.
2. On the Node List tab page, select Single source and dual sink or Dual source and single
sink and configure the corresponding source and sink NEs.
3. In the PW pane. Configure the working PW, protection PW, and DNI-PW.
4. Click Advanced. In the lower right portion, a pane is displayed.
5. Optional: Click the Advanced Attributes tab. Configure advanced PW attributes.
6. Click the Protection Parameter tab. Select a protection type.
l If you set Protection Type to Protection group, the master MC-PW APS protection
is created.
l If you set Protection Type to Slave protection pair, the slave MC-PW APS protection
is created. You need to set ID of the master MC-PW APS protection group that the slave
MC-PW APS protection is bound with.
NOTE
You must configure the protection types for the NEs that are involved in the dual-homing protection.
You must configure the master MC-PW APS protection group before binding a slave MC-PW APS
protection group. The working PW, protection PW, and DNI-PW of a slave MC-PW APS protection group
and those of the master MC-PW APS protection group must share the same sources, sinks, and physical
trails. If the physical trails are different, a switching may be performed on the PW in the slave MC-PW
APS protection group that is normal due to the faulty PW of the master MC-PW APS protection group.
Step 4 After a service is successfully created, you need to configure the PW OAM for the service. For
how to configure a test group, see 6.5.2 Configuring PW OAM.
----End
9.3 Example of Dual-Homing Protection with 1:1 MC-PW
APS and MC-LAG
This section provides an example of dual-homing protection with NNI-side 1:1 MC-PW APS
and UNI-side MC-LAG with focuses on example description and configuration process.
9.3.1 Example Description
This section describes an example of dual-homing protection with NNI-site 1:1 MC-PW APS
and AC-side MC-LAG, and focus on the function requirement, networking diagram, and
parameter planning.
iManager U2000
9-17
This topic describes how to configure 1:1 MC-PW APS and MC-LAG dual-homing protection
for E-Line services through an example.
This section describes an example of dual-homing protection with NNI-site 1:1 MC-PW APS
and AC-side MC-LAG, and focus on the function requirement, networking diagram, and
parameter planning.
Function Requirement and Networking Diagram
An E-Line service from NodeB needs to be transported to RNC over the PTN network. NodeB
carries services over FE interfaces and RNC carries services over an SC-LAG. Dual-homing
protection must be provided on the RNC side for the services from NodeB.
As shown in Figure 9-7, the OptiX PTN 950 is deployed on PE3, which accesses the E-Line
services from NodeB through FE interfaces. To provide dual-homing protection for the services
on the RNC side, PE1, PE2, and RNC are connected in dual-homing mode. The equipment that
supports PW APS and MC-LAG is deployed on PE1 and PE2, each of which accesses E-Line
services through an LAG.
Figure 9-7 Networking diagram for the dual-homing protection with 1:1 MC-PW APS and MC-
LAG
BSC/RNC
PE1
PE2
A
S
LAG3
LAG1
LAG2
MC-LAG
W
P
PE3
BTS/NodeB
1:1
PW APS
BTS/NodeB
MC-PW
APS
MC synchronization
communication
DNI-PW
Service flow
Working
Protection
W
P
Active (carrying services)
A
S

Parameter Planning
Table 9-5 lists the parameter planning for the PWs of NNI-side MC-PW APS.
iManager U2000
Issue 01 (2010-08-16)
Table 9-5 Parameter planning for the PWs of NNI-side MC-PW APS (dual-homing protection
with 1:1 MC-PW APS and MC-LAG in the example)
Parameter
MC-PW APS PW
PW 1 PW 2 DNI-PW 3
PW ID 10 20 30
PW Type Ethernet
Direction Bidirectional(PE3<-
>PE1)
Bidirectional(PE3<-
>PE2)
Bidirectional(PE1<-
>PE2)
Opposite LSR
ID of PE1
10.0.0.3 - 10.0.0.2
Opposite LSR
ID of PE2
- 10.0.0.3 10.0.0.1
Opposite LSR
ID of PE3
10.0.0.1 10.0.0.2 -
PW ingress label
PE1
10 - 50
PW egress label
on PE1
20 - 60
PW ingress label
on PE2
- 30 60
PW egress label
on PE2
- 40 50
PW ingress label
on PE3
20 40 -
PW egress label
on PE3
10 30 -
Tunnel selection
mode
Manually
Tunnel Type MPLS
Tunnel (tunnel
ID)
1 2 3

Table 9-6 lists the parameter planning for the NNI-side MC-PW APS.
iManager U2000
9-19
Table 9-6 Parameter planning for NNI-side MC-PW APS (dual-homing protection with 1:1
MC-PW APS and MC-LAG in the example)
Parameter PE3 PE2 PE1
Protection
binding
relation
Master PW APS
protection group
Master MC-PW APS
protection group
Master MC-PW APS
protection group
Protection
Type
Protection group Protection group Protection group
Protection
Group ID
30 20 10
Peer
Protection
Group ID
- 10 20
Working PW
name (PW
ID)
PW 1(10) - PW 1(10)
Protection
PW name
(PW ID)
PW 2(20) PW 2(20) -
DNI-PW
name (PW
ID)
- DNI-PW 3(30) DNI-PW 3(30)
Role DNI Protection Working
Enable APS Enabled Enabled Enabled
Protection
Mode
1:1 1:1 1:1
Switching
Mode
Dual-End Switching Dual-End Switching Dual-End Switching
Revertive
Mode
Revertive Mode Revertive Mode Revertive Mode
Switching
Restoration
time
1 1 1
Switching
Delay Time
0 0 0

4. Parameter Planning for AC-Side (RNC-Side) MC-LAG
Table 9-7 lists the parameter planning for MC synchronization communication of AC-side
(RNC-side).
iManager U2000
Issue 01 (2010-08-16)
Table 9-7 Parameter planning for MC synchronization communication (dual-homing protection
with 1:1 MC-PW APS and MC-LAG in the example)
NE LSR ID Protocol
Channel ID
Peer Device
IP
Hello
Packet
Sending (s)
Timeout
Times
PE1 10.0.0.1 10 10.0.0.2 1 3
PE2 10.0.0.2 10 10.0.0.1

Table 9-8 lists the parameter planning for the AC-side (RNC-side) MC-LAG.
Table 9-8 Parameters for LAG1 on PE1 and LAG2 on PE2 (dual-homing protection with 1:1
MC-PW APS and MC-LAG in the example)
Parameter LAG1 LAG2
LAG No. 1 2
LAG Name LAG1 LAG2
LAG Type Static
Load Sharing Sharing
Load Sharing
Hash Algorithm
Automatic
System Priority 100 200
Master port [Port
Priority]
1-EG16-10 (port-10) [10] 2-EG16-10 (port-10) [10]
Slave port 1 [Port
Priority]
1-EG16-11 (port-11) [11] 2-EG16-11 (port-11) [11]
Slave port 2 [Port
Priority]
1-EG16-12 (port-12) [12] 2-EG16-12 (port-12) [12]

Table 9-9 lists the parameters for the MC-LAG protection groups on PE1 and PE2.
Table 9-9 Parameters for the MC-LAG protection groups on PE1 and PE2 (dual-homing
protection with 1:1 MC-PW APS and MC-LAG in the example)
Parameter Left Equipment Right Equipment
NE PE1 PE2
Link Aggregation Group
ID
1 2
Cooperative Channel ID 10 10
iManager U2000
9-21
Parameter Left Equipment Right Equipment
Load Grouping Type Non-load-sharing
Restoration Mode Restoration Mode

This topic describes how to configure 1:1 MC-PW APS and MC-LAG dual-homing protection
for E-Line services through an example.
Prerequisite
Procedure
Step 2 Create an E-Line service and configure information relevant to the service.
Step 3 Configure the network-side MC-PW APS protection.
1. In the case of the general attributes of the service, set Protection Type to PW APS
protection.
2. In the Node List area, select Single source and dual sink. Configure a non-dual-homing
node PE3 and two active dual-homing nodes PE1 and PE2. In the normal state, PE1 receives
and transmits services and PE2 provides dual-homing protection for PE1.
3. In the PW area. Configure general PW parameters according to the service planning.
4. Click Advanced. In the lower right portion, a pane is displayed.
5. Click the Advanced PW Attribute tab. Set PW Type to Ethernet and Control Word to
Used first.
6. Click the Protection Parameter tab. Configure parameters for dual-homing protection
according to the service planning.
Step 4 Configure the AC-side MC-LAG protection.
iManager U2000
Issue 01 (2010-08-16)
1. Click the Service Topology tab. In the service topology, select PE1 and PE2, right-click,
and choose E-Trunk from the shortcut menu. The Create Cross-Equipment Link
Aggregation Management Group window is displayed.
2. Configure the peer ends for inter-NE synchronization communication on both PE1 and
PE2. On PE1, set Cooperative Channel ID and click .... The Synchronization Protocol
Management window is displayed.
3. Click New. In the Create Cross-Equipment Synchronization Protocol dialog box, set
relevant attributes and click OK.
4. Click OK. A dialog box is displayed indicating that the operation is successful. Click
Close.
5. On PE2, configure the inter-NE synchronization communication between PE1 and PE2.
For details, see Step 4.2 to Step 4.4.
6. Configure intra-NE LAG1 for PE1 and intra-NE LAG2 for PE2. On PE1, set Link
Aggregation Group ID and click .... The Link Aggregation Group Management
window is displayed.
7. Click New. In the Create Link Aggregation Group dialog box, set relevant attributes and
click OK.
iManager U2000
9-23
NOTE
l After you select the Automatically Assign check box, the U2000 automatically assigns the LAG
No. Otherwise, you need to manually enter the LAG No.
l When LAG Type is Static, the link aggregation control protocol (LACP) is running. When LAG
Type is Manual, the LACP is not running.
l Sharing means that each member link of the LAG carries the services at the same time and shares
the load together. Non-Sharing indicates that only one member link of the LAG has traffic.
l After creating a LAG of the static aggregation mode, you can query the Link Aggregation Group
Details and Link LACP Packet Statistics of this LAG.
Close.
9. On PE2, configure LAG2, the intra-NE LAG. For details, see Step 4.6 to Step 4.8.
10. After configuring the inter-NE synchronization communication and intra-NE LAGs for
PE1 and PE2, configure other parameters.
Close.
iManager U2000
Issue 01 (2010-08-16)
Step 5 Click OK to complete the creation of the E-Line service and apply the configuration of dual-
homing protection.
Step 6 Configure the PW OAM detection mechanism for a service.
1. Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2. Click Filter. In the dialog box that is displayed, set the filter criteria, and click OK.
3. The NMS displays the PWE3 services that meet the filter criteria, select a service to be
configured with the PW OAM.
4. Click the PW tab. Then, click the Basic tab.
5. Select one PW and click PW OAM. A dialog box is displayed.
6. Configure the PW OAM. Set the OAM status as Enabled.
7. Click OK. The configuration is applied to NEs and the current dialog box is closed.
Complete the configuration of PW OAM.
----End
iManager U2000
9-25
10 Configuring VRRP
About This Chapter
PTN equipment can achieve dual-homing protection for Layer 3 services by using VRRP. This
chapter describes the concepts, application, and configuration method of VRRP.
10.1 Overview of VRRP
The VRRP protocol is an error tolerance protocol. The VRRP protocol is used to group several
routing devices as one virtual router. The VRRP feature adopts a certain mechanism to switch
services to other routing devices when the next-hop routing device of an NE is faulty. In this
manner, continuous and reliable communication is guaranteed.
10.2 Configuration Flow for VRRP
This section describes the configuration flow for VRRP, with focuses on the configuration tasks
included in the configuration of VRRP and the details on each configuration task.
10.3 Operation Tasks of Configuring VRRP
This section describes the operation tasks of configuring VRRP, which include configuring
VRRP VR information and configuring VRRP VR tracking.
10.4 Testing VRRP
After configuring VRRP, you need to test whether the VRRP is working normally. This section
describes how to test VRRP.
10.5 Configuration Case of VRRP
This section describes a configuration case of VRRP, involving a configuration network
diagram, service planning, and configuration process.
iManager U2000
Operation Guide for PTN End-to-End Management 10 Configuring VRRP
10-1
10.1 Overview of VRRP
The VRRP protocol is an error tolerance protocol. The VRRP protocol is used to group several
routing devices as one virtual router. The VRRP feature adopts a certain mechanism to switch
services to other routing devices when the next-hop routing device of an NE is faulty. In this
manner, continuous and reliable communication is guaranteed.
With development of the Internet, people require more reliable networks. A LAN user expects
contact with external networks at any time. In normal cases, all NEs on a LAN are configured
with the same default route, which leads to an egress gateway NE. In this manner, the NEs can
communicate with external networks. When the egress gateway NE is faulty, communication
between the NEs and external networks is interrupted.
The VRRP protocol, put forward by the Internet Engineering Task Force (IETF), aims to ensure
reliability in the situation where NEs on a LAN communicate with external networks.
As shown in Figure 10-1, two OptiX PTN 1900/3900 are configured as a VRRP backup group,
which is a virtual router (containing a master device and a backup device). An RNC needs to
know only the IP address of the virtual router device so as to communicate with external
networks. At this time, the master device is responsible for forwarding services. When the master
device is faulty, services on the master device are switched to the backup device. In this manner,
continuous and reliable services are guaranteed
Figure 10-1 VRRP networking
OptiX PTN 3900/
OptiX PTN 1900
OptiX PTN 910/950
RNC
NodeB
L
in
k
B
F
D
A
R
P
p
a
c
k
e
ts
A
R
P
p
a
c
k
ts
V
R
R
P
Master
Backup
A
c
tiv
e
lin
k
S
ta
n
d
b
y
lin
k
E-Line/E-LAN
E-Line/E-LAN
L
in
k
B
F
D
Peer
BFD

The VRRP protocol enables communication between a master device and a backup device
through an independent channel between them. When the master device is working normally, it
sends a VRRP multicast packet to the backup device at certain intervals
(Advertisement_Interval) to notify the backup device of its normal state. If the backup device
does not receive the VRRP packet from the master device after a period of time
(Master_Down_Interval), the backup device becomes the master device. Then, the new master
device sends an ARP packet to an RNC to update ARP table entries. Therefore, services are
switched to the new master device.
In addition, the VRRP protocol can be bundled with the BFD detection mechanism. Faults can
be detected through BFD sessions, and therefore VRRP quick switching is implemented.
10 Configuring VRRP
iManager U2000
Issue 01 (2010-08-16)
10.2 Configuration Flow for VRRP
This section describes the configuration flow for VRRP, with focuses on the configuration tasks
included in the configuration of VRRP and the details on each configuration task.
10.3 Operation Tasks of Configuring VRRP
This section describes the operation tasks of configuring VRRP, which include configuring
VRRP VR information and configuring VRRP VR tracking.
10.3.1 Configuring and Deploying an L3VPN Service
An L3VPN service must be configured before VRRP is configured. This section mainly
describes how to configure and deploy an L3VPN service.
10.3.2 Configuring VRRP VR Information
This section describes how to create a VRRP VR. The configuration of a VRRP VR involves
setting the VR ID, VR IP address, VRRP priority, VRRP authentication mode, function of
periodically transmitting ARP packets, VRRP preemption mode, and VRRP delay
10.3.3 Configuring Information About Objects Under Tracking of a VRRP VR
This section describes how to configure tracked peer BFD, tracked link BFD, and objects under
tracking of the VR source and VR sink.
10.3.1 Configuring and Deploying an L3VPN Service
An L3VPN service must be configured before VRRP is configured. This section mainly
describes how to configure and deploy an L3VPN service.
Prerequisite
Context
NOTE
When configuring basic VRRP information, you must take the following precautions:
l VRRP can be configured only at a Layer 3 interface and the IP address of the interface must be available.
l A maximum of 512 VRs can be configured for one set of equipment.
l A maximum of four VRRP VRs can be configured at a Layer 3 interface.
Procedure
Step 1 Configure an L3VPN service. If no L3VPN service is configured, perform Step 1.1 to create an
L3VPN service. If L3VPN services are configured, perform Step 1.2 to select an L3VPN service.
1. Choose Service > L3VPN Service > Manage L3VPN Service from the Main Menu. Then,
the Manage L3VPN Service tab page is displayed. In this tab page, click Create to display
the Create L3VPN Service tab page. Then, set Service Information and select a node
from Node List. Then, click Details to set General and SAI for VRF.
iManager U2000
10-3
NOTE
l Service Name: It is set according to service planning.
l VRF ID: It is automatically assigned or set according to service planning.
l Interface Name: In the case of an Ethernet Layer 3 interface, the IP address of the interface can
be set by using only VRF.
l IP Address/Mask: It is set according to service planning. IP addresses of all service access
interfaces must be set in the same network segment.
2. If L3VPN services have already been created, quickly select a created L3VPN service by
setting Set Filter Criteria.
Step 2 Deploy an L3VPN service. Right-click a configured L3VPN service, and then choose Deploy.
In this case, you can configure VRRP only after successfully deploying the L3VPN service.
10 Configuring VRRP
iManager U2000
Issue 01 (2010-08-16)
----End
10.3.2 Configuring VRRP VR Information
This section describes how to create a VRRP VR. The configuration of a VRRP VR involves
setting the VR ID, VR IP address, VRRP priority, VRRP authentication mode, function of
periodically transmitting ARP packets, VRRP preemption mode, and VRRP delay
Prerequisite
l You must configure an L3VPN service.
Procedure
Step 1 Configure VRRP VR information. Choose Service > L3VPN Service > Manage L3VPN
Service from the Main Menu. Right-click a created and deployed L3VPN service, and then
choose Configure VRRP to display the VRRP-Based Detection Configuration
Management pane. In this pane, click Create to display the Create VRRP dialog box. Then,
configure the associated parameters in the dialog box. For details on the parameters for basic
VRRP VR information, see Table 1.
Step 2 Configure advanced VRRP VR information. Click Advanced to display the Advanced VRRP
Configuration dialog box. For details on the parameters for advanced VRRP VR information,
see Table 2.
iManager U2000
10-5
----End
10.3.3 Configuring Information About Objects Under Tracking of
a VRRP VR
This section describes how to configure tracked peer BFD, tracked link BFD, and objects under
tracking of the VR source and VR sink.
Prerequisite
l The configuration of VRRP VR information must be complete.
Procedure
Step 1 In the Create VRRP dialog box, click Next to go to Step 2: Configure the information about
the VRRP VR monitoring.
Step 2 Optional: Configure tracked peer BFD. Select Tracked Peer BFD and then click Configure
to configure a tracked peer BFD session for testing the link between the master and backup.
Step 3 Configure tracked link BFD. In Tracked Link BFD, configure Link BFD Path and Link
BFD.
Step 4 Optional: Configure objects under tacking of the VR source and VR sink.
10 Configuring VRRP
iManager U2000
Issue 01 (2010-08-16)
NOTE
l The objects under tracking of the VR source and VR sink are as follows:
l BFD Session: You can specify a BFD session under tracking of the VR source and VR sink.
l Interface: You can specify an interface under tracking of the VR source and VR sink.
l OAM: You can specify an Ethernet OAM interface under tracking of the VR source and VR sink.
l PRI Change: You can increase or reduce the equipment priority by setting this parameter.
l Value: You can set the change of equipment priority, and the value range is 1 to 255.
----End
10.4 Testing VRRP
After configuring VRRP, you need to test whether the VRRP is working normally. This section
describes how to test VRRP.
Prerequisite
l You must complete the configuration of basic VRRP VR information.
Context
When testing whether VRRP is working normally by using the VIP ping function, you need to
test the following items:
l Working situation of the master on the VR.
l Whether a VIP address can be used as a default gateway IP address for communication
with the outside.
NOTE
VIP ping may cause ICMP attacks to a VR. Therefore, you need to disable the VIP ping function each time
after testing VRRP. This prevents a VR from being attacked by ICMP packets.
iManager U2000
10-7
Procedure
Step 1 Enable the VIP ping function. Choose Service > L3VPN Service > Manage L3VPN Service
from the Main Menu. In the displayed Create VRRP dialog box, select Step 1:Configure
VRRP VR Information. Then, click Advanced to display the Advanced VRRP
Configuration dialog box. Set VIP ping to None, Master or Both.
NOTE
l Master: indicates that VIP ping can be performed when the VRRP status machine is in master state.
l Both: indicates that VIP ping can be performed when the VRRP status machine is in any state.
Step 2 On the opposite equipment, ping the VR IP address.
----End
10.5 Configuration Case of VRRP
This section describes a configuration case of VRRP, involving a configuration network
diagram, service planning, and configuration process.
This section describes the requirements, network diagram, and service planning of VRRP.
This section describes the configuration process of a configuration case of VRRP.
This section describes the requirements, network diagram, and service planning of VRRP.
Requirements and Network Diagram
As shown in Figure 10-2, NE1 and NE2 form a VRRP VR to protect the RNC.
The requirements of VRRP are as follows:
l NE1 works as the master of the VRRP VR. When NE1 is faulty, NE2 becomes the master.
l BFD sessions need to be configured at interfaces on NE1 and NE2 to monitor both NE1
and link NE1-RNC-NE2. Therefore, when NE1 is faulty or link NE1-RNC is faulty, the
master/backup switching is performed within one second.
l After NE1 is restored, it becomes the master within 20 seconds. Preemption is enabled for
NE1. That is, NE1 preempts NE2 5 seconds after NE1 is restored.
l To avoid attacks on the network, you must configure VRRP packet authentication.
10 Configuring VRRP
iManager U2000
Issue 01 (2010-08-16)
Figure 10-2 Network with VRRP for an RNC
OptiX PTN 3900
OptiX PTN 1900
OptiX PTN 910/950
RNC
NodeB
V
R
R
P
Master
Backup
Peer BFD
5-EG16-1
5-EG16-1
5
-
E
G
1
6
-
2
5
-
E
G
1
6
-
2
Link BFD
NE1
NE2
VR IP:10.1.1.1
NOTE
Service configuration on the OptiX PTN 3900-8 is the same as that on the OptiX PTN 3900, except for the
slots for service boards. For details on service configuration on the OptiX PTN 3900-8, see this example
about service configuration on the OptiX PTN 3900.

Service Planning
To implement VRRP, you must configure VRRP VR information and information about objects
under tracking of a VRRP VR. Table 10-1, Table 10-2, and Table 10-3 show the planning.
Table 10-1 Planning of VRRP VR information
Parameter Value
Source equipment NE1
Source interface 5-EG16-1
Sink equipment NE2
Sink interface 5-EG16-1
VR Type Management VR
VR ID 10
VR IP addres 10.1.1.1

Table 10-2 Planning of Advanced VRRP VR Information
Parameter NE1 NE2
Whether to Preempt Selected Selected
iManager U2000
10-9
Parameter NE1 NE2
Delay 5s 5s
Configuration
Priority
120 (NE1 as the master) 100 (NE2 as the backup)
Advertisement
Interval
1s 1s
Management VR
Interface
5-EG16-1 5-EG16-1
Management VR
ID
10 10
Enable VRRP
Group
Selected Selected
VIP ping None None
Interface 5-EG16-2 5-EG16-2
Set MAC Selected Selected
Authen type Simple Simple
Authen Code 1 1

Table 10-3 Planning of Information About Objects Under Tracking of a VRRP VR
Parameter Object Under Tracking of the
VR Sink
Object Under Tracking of the
VR Source
Object under
tracking
BFD Session BFD Session
PRI Change Increase Increase
Value 20 10

This section describes the configuration process of a configuration case of VRRP.
Prerequisite
l You must configure an L3VPN service.
10 Configuring VRRP
iManager U2000
Issue 01 (2010-08-16)
Procedure
Step 1 Configure basic VRRP VR information. Choose Service > L3VPN Service > Manage L3VPN
Service from the Main Menu. In the displayed Create VRRP dialog box, select Step 1:
Configure VRRP VR information to configure the basic VRRP VR information.
Parameter Value Guideline
Source equipment NE1 Whether the source equipment is
the master or backup is
determined by the equipment
priority configured.
If the priority is high, the source
equipment is the master.
Otherwise, the source equipment
is the backup.
Source interface 5-EG16-1 This parameter indicates a Layer
3 interface.
Sink equipment NE2 Whether the sink equipment is the
master or backup is determined
by the equipment priority
configured.
If the priority is high, the sink
equipment is the master.
Otherwise, the sink equipment is
the backup.
Sink interface 5-EG16-1 This parameter indicates a Layer
3 interface.
VR Type Management VR l Management VR: indicates a
management VR group.
l Service VR: indicates a VR
backup group.
VR ID 10 The value range is 1 to 255.
VR IP addres 10.1.1.1 You can set the VR IP address to
the same as the IP address of an
interface on an actual router. In
this case, the preemption mode of
the router is always preemption.
NOTE
When both VRRP and static ARP are
configured on equipment, you
cannot use the mapping IP addresses
of static ARP table entries associated
with the interfaces on the equipment
as the VR IP address. Otherwise,
incorrect routes between equipment
will be generated, which affects
normal service forwarding between
NEs.
iManager U2000
10-11

Step 2 Configure advanced VRRP VR information. Click Advanced to display the Advanced VRRP
Configuration dialog box. In the dialog box, configure advanced VRRP VR information.
Table 10-4 Planning of Advanced VRRP VR Information
Parameter NE1 NE2 Remarks
Whether to
Preempt
Preemption Preemption After the preemption
mode of the backup is
set to preemption, if the
priority of the backup is
higher than that of the
master, the backup will
become the master
automatically.
Delay 5s 5s If delay is 0, it indicates
immediate preemption.
In other cases, the
backup becomes the
master within specified
delay.
Configuratio
n Priority
120 (NE1 as the master) 100 (NE2 as the
backup)
A greater value
indicates a higher
priority.
l The value 0 indicates
that the current
master on a VR
disables VRRP.
l The value 255 is
reserved for the
equipment whose
VR IP address is the
same as the IP
address of an
interface.
Advertiseme
nt Interval
1s 1s This parameter
indicates the period for
the Adver_Timer timer
to transmit VRRP
advertisement packets.
When this period is due,
the timer triggers
transmission of VRRP
advertisement packets.
Management
VR Interface
5-EG16-1 5-EG16-1 -
10 Configuring VRRP
iManager U2000
Issue 01 (2010-08-16)
Parameter NE1 NE2 Remarks
Management
VR ID
10 10 -
Enable
VRRP Group
Selected Selected -
VIP ping None None VIP ping may cause
ICMP attacks to a VR.
Therefore, VIP ping is
generally disabled.
Interface 5-EG16-2 5-EG16-2 -
Set MAC Selected Unselected This parameter
indicates that the MAC
address of the current
interface serves as the
virtual MAC address of
VRRP.
Authen type Simple Simple l Disable: indicates
that the packets
received by the
equipment are
authentic and legal
VRRP packets.
l Simple: indicates
simple character
authentication.
l MD5: indicates
MD5 authentication.
Authen Code 1 1 l 0: indicates no
authentication.
l 1: indicates simple
text password
authentication.
l 2: indicates MD5
authentication.

Step 3 Configure a tracked BFD session. In the Create VRRP dialog box, click Next to enter Step 2:
Configure the information about the VRRP VR monitoring. Select Track more BFD
session or interface. Ensure quick VRRP switching by tracking a BFD session.
iManager U2000
10-13
Table 10-5 Parameters for Tracking More BFD Sessions or Interfaces
Parameter Tracking Object of the VR
Sink
Tracking Object of the VR
Source
Tracking object BFD Session BFD Session
PRI Change Increase Increase
Value 20 10

----End
10 Configuring VRRP
iManager U2000
Issue 01 (2010-08-16)
11 Composite Service Management
About This Chapter
This topic describes composite service management. A composite service refers to a service
composed of two or more associated services. With composite service management, you can
flexibly combine PWE3, VPLS, and L3VPN services, automatically calculate service
connection points, and manage different services in a centralized manner. Composite service
management applies to the scenarios not supported by single services and meets the requirements
of the Metro Ethernet and bear network solutions.
11.1 Composite Service Overview
This topic describes the functions, basic concepts, and application scenarios of the composite
service.
11.2 Process of Configuring a Composite Service
This topic describes the operation tasks related to configuring a composite service and the
process relations between these operation tasks. It is recommended that you create and configure
a composite service according to the service configuration process.
11.3 Operation Tasks of Composite Services
This topic describes the operation tasks of composite services, such as automatically discovering,
creating, and deploying composite services.
11.4 Monitoring a Composite Service
This topic describes how to monitor a composite service. By monitoring the running and
deployment status of a composite service, viewing the topology of the composite service in real
time, and obtaining the alarms about this composite service, you can ensure the normal running
of the services in this composite service.
11.5 Example for Configuring Composite Services
This topic describes the networking modes and configuration methods for composite services
with examples.
iManager U2000
Operation Guide for PTN End-to-End Management 11 Composite Service Management
11-1
11.1 Composite Service Overview
This topic describes the functions, basic concepts, and application scenarios of the composite
service.
11.1.1 Composite Service Functions
This topic describes the functions of composite service management.
11.1.2 Basic Concepts
This topic describes the basic concepts of the composite service in terms of service components
and connection points. Before you use the composite service function, you need to know these
concepts for smooth configuration.
11.1.3 Application of Composite Services
This topic describes the application of composite services. The composite service supports
multiple types of service combinations. By monitoring services through the composite service,
the NMS can better satisfy the requirements of the Metro Ethernet solution, bear network
solution, and other solutions.
11.1.1 Composite Service Functions
This topic describes the functions of composite service management.
Composite service management supports the following functions:
l Automatically discovering composite services
With this function, the NMS can automatically discover the services on the current network
that meet composite service relations. Requiring only a few operations, this function
enables the NMS to quickly load composite services through a two-step wizard for unified
management and monitoring.
l Creating composite services
Adding services to the composite service and then establishing connection points
between services
Automatically calculating connection points to simplify configuration operations
Providing the navigation paths for creating, modifying, and deleting services to facilitate
service management
l Monitoring composite services
The NMS allows you to perform operations such as querying composite services, viewing
the deployment status and alarm status of composite services, and viewing the topology of
composite services and their associated services in real time
l Deleting composite services
The NMS allows you to perform the following operations:
Delete Only Composite Service: In this case, only the composite services are deleted
from the NMS. The services associated with these composite services still exist on NEs.
Delete Cascaded Service: In this case, the composite services are deleted from the NMS
and the services associated with these composite services are deleted from NEs.
iManager U2000
Issue 01 (2010-08-16)
11.1.2 Basic Concepts
This topic describes the basic concepts of the composite service in terms of service components
and connection points. Before you use the composite service function, you need to know these
concepts for smooth configuration.
Composite Service
The composite service is a combination of associated services. Composite service management
is used to support the scenarios that single services cannot support, such as PWE3+PWE3 and
PWE3+VPLS, so as to implement complicated service combinations. The services in the
composite service are associated with each other through service components and connection
points.
On the NMS, the management of composite services complies with the following principles:
l A composite service can contain only basic service information, without service
components or connection points.
l A service belongs to only one composite service.
l A connection point embodies the association between two services.
l When you delete a service component, the related connection points are also deleted.
Service Component
Service components refer to the services to be associated with the composite service. The types
of service components include PWE3, and VPLS.
Connection Point
Connection points represent the association relations between service components. Two or more
services can be associated with each other through connection points. There are two types of
connection points: PW connection points and interface connection points.
The details are as follows:
l Interface connection point: connects the interfaces of service components. Interface
connection points are used to support the PWE3+PWE3 composite services.
l PW connection point: connects the PWs of service components. PW connection points are
used to support the PWE3+VPLS composite service.
11.1.3 Application of Composite Services
This topic describes the application of composite services. The composite service supports
multiple types of service combinations. By monitoring services through the composite service,
the NMS can better satisfy the requirements of the Metro Ethernet solution, bear network
solution, and other solutions.
The common application scenarios of composite services are as follows.
PWE3+VPLS Composite Services
l Static VLL+VPLS composite service
As shown in Figure 11-1, in the HVPLS, SPE 1 and SPE 2 support VPLS. The VSIs of
the SPEs adopt LDP as the signaling protocol of the VPLS.
iManager U2000
11-3
In practical networks, such as MAN access networks, if a UPE does not support the dynamic
VLL, the UPE needs to access SPEs through the static VLL. A UPE and an SPE generally
set up an SVC between each other to create a VLL.
Figure 11-1 Networking diagram of the static VLL+VPLS composite service
SPE1 SPE2
UPE1
UPE2
CE1 CE2
CE3 CE4
PW
VPLS
Network
V
L
L V
L
L

As shown in Figure 11-1, the UPEs add double MPLS labels to the packets sent by the
CEs. The outer layer is the static LSP label and is switched when a packet passes through
the equipment on the access network. The inner label is the VC label that identifies the VC.
The inner label remains unchanged when a packet is transmitted along the LSP.
The packets received by the SPEs contain double labels. The outer label, which is a
statically-configured public network label, is popped up. The inner label decides which
VSI the SVC accesses.
l Dual-homed static VLL+VPLS composite service
To ensure reliable VLL access, the UPE accessing the SPE in dual-homed mode is
introduced. In dual-homed mode, if a PW fails, the data traffic is immediately switched to
another PW, as shown in Figure 11-2.
In VPLS, the bidirectional transmission paths are consistent because the routing
information about Layer 2 forwarding is automatically learned through the MAC addresses
of the data traffic. If a fault occurs, the VPLS traffic of a UPE is switched to another LSP.
The SPE equipment belonging to the VSI deletes the MAC entries of this VSI. After the
switchover or the deletion, the MAC entries need to be learned afresh.
iManager U2000
Issue 01 (2010-08-16)
Figure 11-2 Networking diagram of the dual-homed static VLL+VPLS composite service
SPE1
SPE2
SPE3
SPE4
UPE1 UPE2
CE1
CE2
x
LDP Message

As shown in Figure 11-2, if a fault occurs on the LSP between UPE 1 and SPE 1, SPE 1
detects the fault and asks the other SPEs to delete the related MAC addresses by sending
LDP messages.
The UPEs detect the LSP status through MPLS OAM. If a fault is detected, the traffic
switchover is performed. After the switchover, the related VSIs on the SPEs learn the MAC
addresses afresh; thus, the traffic can return through the new SPEs. Before other SPEs learn
the MAC addresses, traffic must be broadcast.
After the fault is removed, the UPE receives double VLL broadcast traffic: one from the
SPEs before the switchover, the other from the SPEs after the switchover. The UPE decides
which broadcast traffic to be thrown away. After the fault is rectified, the traffic of the UPE
is not switched back to the original LSP. This is because the SPE is not triggered to send
LDP packets to other SPEs to delete MAC addresses before detecting LSP failures.
PWE3+PWE3
In this application scenario, protection for the services between rings is enhanced. Fibers in each
section of a service are protected, so that the service is well protected.
For example, a PWE3 service between PE1 and PE4 can be divided into three sections, as shown
in Figure 11-3. PW APS protection is configured for the sections from PE1 to PE2 and from
PE3 to PE4 and LAG protection is configured for the section from PE2 to PE3. In this way, each
fiber has its protection link in each section of the service and thus the protection capability of
the PWE3 service is enhanced.
iManager U2000
11-5
Figure 11-3 Networking diagram of the PWE3+PWE3 composite service

11.2 Process of Configuring a Composite Service
This topic describes the operation tasks related to configuring a composite service and the
process relations between these operation tasks. It is recommended that you create and configure
a composite service according to the service configuration process.
Figure 11-4 shows the process of configuring a composite service.
Figure 11-4 Flowchart of configuring a composite service
Create the composite
service
Deploy the composite
service
Start
Automatically discover
the composite service
Mandatory
Optional
View the status of
View the topology of
End

iManager U2000
Issue 01 (2010-08-16)
Table 11-1 Configuration tasks of a composite service
Operation Remarks
11.3.1
Automaticall
y Discovering
Composite
Services
Combine the services associated with interface connection points or PW
connection points into a composite service and discover this composite
service on the NMS.
Do as follows:
1. Select NEs.
You can choose to discover networkwide NEs or specify certain NEs for
discovery.
2. Configure the customer policy.
Specify the customer of the services to be discovered, so that only the
services of this customer can be discovered.
3. Set the service type.
Set the type of the composite service to be automatically discovered.
11.3.2
Creating a
Composite
Service
Besides automatically discovering a composite service, you can also create
a composite service as required.
Do as follows:
1. Configure the basic information about the composite service, such as the
name and customer of the composite service.
2. Configure service components. Add the services to be managed, such as
PWE3, VPLS services, to the composite service. You can either select
existing services or create services as required.
3. Configure connection points between services to combine these services.
You can either create connection points or use the NMS to automatically
calculate connection points.
11.3.3
Deploying a
Composite
Service
If you need to deploy the service components associated with a component
service to an NE, you can perform this operation.
11.4.1
Viewing the
Status of a
Composite
Service
View the deployment status and alarm status of a composite service.
11.4.2
Viewing the
Topology of a
Composite
Service
The topology view displays the topology of services in a visual manner. By
viewing the topology of a composite service, you can learn the topology of
the composite service and its associated services and the running status of
its associated services.

11.3 Operation Tasks of Composite Services
This topic describes the operation tasks of composite services, such as automatically discovering,
creating, and deploying composite services.
iManager U2000
11-7
11.3.1 Automatically Discovering Composite Services
This topic describes how to automatically discover composite services. With this function, you
can discover composite services on the NMS. The composite service consists of the services
that are associated with interface connection points or PW connection points.
11.3.2 Creating a Composite Service
This topic describes how to create a composite service. By associating multiple services through
connection points, you can create a composite service to support the scenarios not supported by
single services. In this manner, you can better satisfy the requirements of the Metro Ethernet
and bearer network solutions.
11.3.3 Deploying a Composite Service
This topic describes how to deploy a composite service. Deploying a composite service is to
deploy the service components associated with the composite service from the NMS to the NE.
11.3.1 Automatically Discovering Composite Services
This topic describes how to automatically discover composite services. With this function, you
can discover composite services on the NMS. The composite service consists of the services
that are associated with interface connection points or PW connection points.
Prerequisite
IP services must be automatically discovered. For details, see Automatically Discovering IP
Services.
Procedure
Step 1 Choose Service > Composite Service > Search for Composite Service from the main menu.
Step 2 On the Discovery Policy tab page, set the discovery policy.
1. Specify the equipment range for discovering composite services.
l Click the All option button to discover all the NEs on the entire network.
l Click the Select NE option button, and then click Add. In the dialog box that is
displayed, select one or more NEs, and then click OK to discover the specified NEs.
2. Optional: Specifies the customer of the services to be discovered. Only the services of this
customer can be discovered. In this manner, the efficiency of automatic discovery is
increased.
Click the ... button to the right of the Customer Name field. In the dialog box that is
displayed, query customers and select one. Then, click OK.
3. Set the type of the composite services to be discovered, and then click Start.
Step 3 Click the Discovery Result tab. A progress bar is displayed indicating the progress of
automatically discovering services.
You can view the automatically discovered composite services on the Add Service tab page.
After selecting a record and clicking Jump Service, you can access the composite service
management user interface for this service.
----End
11.3.2 Creating a Composite Service
This topic describes how to create a composite service. By associating multiple services through
connection points, you can create a composite service to support the scenarios not supported by
iManager U2000
Issue 01 (2010-08-16)
single services. In this manner, you can better satisfy the requirements of the Metro Ethernet
and bearer network solutions.
Procedure
Step 1 Choose Service > Composite Service > Create Composite Service from the main menu.
Step 2 In the General area, set Service Name, Customer Name, and Remarks.
Step 3 In the Service Component area, click Select to select the related type of service. In the window
that is displayed, select one or more services, and then click Select. The selected services are
displayed in both the service component list area and the service topology.
The selected services must meet the following conditions:
l PWE3+VPLS
The PWE3 service and VPLS service both have unterminated PWs.
The PW IDs of the two PWs are the same. The peer IP address of the unterminated PW
of the VPLS service is the local IP address of the unterminated PW of the PWE3 service.
The local IP address of the unterminated PW of the VPLS service is the peer IP address
of the unterminated PW of the PWE3 service.
If the unterminated PWs are static, the outgoing label of the PW for one of the two services
is the incoming label of the PW for the other service.
If no eligible services are displayed, you can click Create to create a service.
Step 4 In the Connection Point area, configure the connection point for the composite service. The
configured connection point is displayed in both the connection point list area and the service
topology.
The PW connection point is used for the PWE3+VPLS composite service. The interface
connection point is used for the PWE3+PWE3 composite service.
l Click Auto-Calculate to obtain the connection points automatically calculated by the NMS
for the composite service.
NOTE
The PWE3+PWE3 composite service do not support Auto-Calculate.
l You can also do as follows to create the required connection points:
1. Click Create to create the required connection point.
2. In the dialog box that is displayed for creating the connection point, set Name or select
the Auto-Name check box.
3. Set Type for the composite service.
4. In the information list, click to select the PW or interface.
5. Click OK to close the dialog box.
Step 5 After the configuration, click OK.
If the operation is successful, the created composite service is displayed in the service list.
----End
11.3.3 Deploying a Composite Service
This topic describes how to deploy a composite service. Deploying a composite service is to
deploy the service components associated with the composite service from the NMS to the NE.
iManager U2000
11-9
Prerequisite
The composite service to be deployed must exist.
Context
Before a created service is deployed, the configurations of the service are stored in the database
of the U2000 instead of being deployed to equipment. The service is in the Undeployed state.
After the service is deployed, the configurations of the service can be deployed to equipment.
Procedure
Step 1 Choose Service > Composite Service > Manage Composite Service from the main menu.
Step 3 Right-click the composite service to be deployed and choose Deploy from the shortcut menu.
After the composite service is deployed, the deployment status of this composite service changes
to Deployed.
----End
11.4 Monitoring a Composite Service
This topic describes how to monitor a composite service. By monitoring the running and
deployment status of a composite service, viewing the topology of the composite service in real
time, and obtaining the alarms about this composite service, you can ensure the normal running
of the services in this composite service.
11.4.1 Viewing the Status of a Composite Service
This topic describes how to view the deployment and alarm status of a composite service.
11.4.2 Viewing the Topology of a Composite Service
This topic describes how to view the topology of a composite service. The topology view displays
the topology of services in a visual manner. By viewing the topology of a composite service,
you can learn the topology of the composite service and its associated services and the running
status of its associated services.
11.4.1 Viewing the Status of a Composite Service
This topic describes how to view the deployment and alarm status of a composite service.
Procedure
Step 3 In the service list, you can view the deployment status of each composite service.
Step 4 Select a composite service and click the Service Component tab. Then, you can view the
deployment and alarm status of this composite service in the Deployment Status and Alarm
Status columns.
iManager U2000
Issue 01 (2010-08-16)
Step 5 Right-click the service component with the alarm and choose Current Alarm from the shortcut
menu. You can view the detailed alarm information of the service in the details area
----End
Postrequisite
Preliminarily determine the possible cause of the alarm based on the detailed alarm information,
and then locate the fault position by referencing the handling suggestions.
11.4.2 Viewing the Topology of a Composite Service
This topic describes how to view the topology of a composite service. The topology view displays
the topology of services in a visual manner. By viewing the topology of a composite service,
you can learn the topology of the composite service and its associated services and the running
status of its associated services.
Procedure
Step 3 In the service list, select the composite service to be viewed, and then click the Topology tab.
In the topology view, you can view the topology of the composite service. The service
components are connected to each other through connection points. Each service component is
displayed as a submap. By clicking on the toolbar of the Main Topology, you can view the
legend information.
Step 4 You can perform the following operations in the topology view.
l Right-click a service component and then you can perform the following operations:
Choose Current Alarm from the shortcut menu to check whether the composite service
is normal.
Choose Details from the shortcut menu to access the service management user interface.
Then, you can view the details about this composite service and modify this composite
service as required.
Choose Open from the shortcut menu to view the topology of this service component.
By choose Close, you can collapse the topology structure of the service.
l Right-click a connection point and choose Details from the shortcut menu to view the details
about this connection point.
----End
iManager U2000
11-11
11.5 Example for Configuring Composite Services
This topic describes the networking modes and configuration methods for composite services
with examples.
11.5.1 Example for Configuring the PWE3+VPLS Composite Service
This topic describes the networking application and configuration method of the PWE3+VPLS
composite service with an example.
11.5.2 Example for Configuring the PWE3+PWE3 Composite Service
This topic describes the networking application and configuration method of the PWE3+PWE3
11.5.1 Example for Configuring the PWE3+VPLS Composite
Service
This topic describes the networking application and configuration method of the PWE3+VPLS
Example Description
When an Ethernet service is connected to a VPLS service, the two services affect the VLAN
service that is transmitted in them. Therefore, the two services need to be combined as a
composite service for management.
For details, see Figure 11-5.
l The PWE3 service is transmitted from UPE1 to NPE1.
l The PWE3 service is transmitted from UPE2 to NPE2.
l The VPLS service is transmitted from NPE1 to NPE2.
l The services between UPE1, NPE1, NPE2, and UPE2 are combined as a composite service .
Figure 11-5 Networking diagram of the PWE3+VPLS composite service
NPE 2
UPE 1
FE
UPE 2
UNI for UPE2: 19-ETFC-1
NNI for NPE1: 1-EG16-1
UNI for UPE1: 19-ETFC-1
NNI for NPE2: 1-EG16-1
VPLS
NPE 1
PWE3
PWE3
PW
19-ETFC-1
19-ETFC-1

iManager U2000
Issue 01 (2010-08-16)
Service Planning
This topic describes the service planning of the PWE3+VPLS networking.
The configuration roadmap is as follows:
1. Configure PWE3 services
Configure on the UPEs and enable the UPEs to access the NPEs through static PWE3.
2. Configure VPLS services
Configure bidirectional PWs between the NPEs. On the NPEs, configure unidirectional
PWs that point to the UPEs.
3. Configure connection points to combine the PWE3 service and the VPLS service into a
composite service.
Plan the following data:
Table 11-2 NE parameters
NE Interface IP Address LSR ID Opposite LSR ID
(Session
Configuration for
MPLS-LDP )
UPE1 19-ETFC-1:
100.1.1.1/24
1.1.1.9
NPE1 19-ETFC-1:
100.1.1.2/24
2.2.2.9 3.3.3.9
1-EG16-1:
100.1.1.3/24
NPE2 19-ETFC-1:
100.1.1.4/24
3.3.3.9 2.2.2.9
1-EG16-1:
100.1.1.5/24
UPE2 19-ETFC-1:
100.1.1.6/24
4.4.4.9

Table 11-3 Planning of parameters for configuring the PWE3 service
Service
Attribute
PWE3 Service 1 PWE3 Service 2
Service
Type
ETH ETH
Service
Name
pwe3_upe1 pwe3_upe2
Node List
iManager U2000
11-13
Service
Attribute
Source UPE1:19-ETFC-1 UPE2:19-ETFC-1
Unterminat
ed > Sink
2.2.2.9 3.3.3.9
PW
PW ID 100 100
Signaling
Type
Static Static
Uplink
Label
1001 1002
Downlink
Label
1002 1001

Table 11-4 Planning of parameters for configuring the VPLS service
Service
Attribute
Value
Service
Name
vpls
Network
Type
Full-Mesh-VPLS
VSI Name vsi1
VSI ID 100
NPE NPE 1 and NPE 2
Bidirection
al PW
Parameters are set as follows:
l Source NE: NPE 1
l Sink NE: NPE 2
l PW Type: Dynamic
Unterminat
ed PW 1
l Source NE: NPE 1
l Sink NE: UPE 1
l PW Type: Static
l Incoming Label: 1002
l Outgoing Label: 1001
iManager U2000
Issue 01 (2010-08-16)
Unterminat
ed PW 2
l Source NE: NPE 2
l Sink NE: UPE 2
l PW Type: Static

Table 11-5 Planning of parameters for configuring the composite service
Service
Attribute
Value
Service
Name
PWE3+VPLS
Customer
Name
customer 1
Service
Componen
t
Select the following service components:
l VPLS: vpls
l PWE3: pwe3_upe1 and pwe3_upe2
PW
Connection
Point 1
pwe3_upe1+vpls
l Name: connection1
l Selected PW 1:
PW ID: 100
Equipment Name: UPE 1
Service Name: pwe3_upe1
Service Type: PWE3
l Selected PW 2:
PW ID: 100
Equipment Name: NPE 1
Service Name: vpls
Service Type: VPLS
iManager U2000
11-15
Service
Attribute
Value
PW
Connection
Point 2
pwe3_upe2+vpls
l Name: connection2
l Selected PW 1:
PW ID: 100
Service Type: PWE3
l Selected PW 2:
PW ID: 100
Service Name: vpls
Service Type: VPLS

This topic describes the configuration process of the PWE3+VPLS composite service. The
configuration process of the PWE3+VPLS composite service includes configuring PWE3
services, configuring VPLS services, and configuring the PWE3+VPLS composite service.
Prerequisite
l IP addresses of all interfaces must be set.
l The parameters of control planes must be set.
l The dynamic tunnel carried service must created.
Procedure
Step 1 Configure PWE3 services.
Configure static PWE3 service 1 on UPE 1 and configure UPE 1 to access NPE 1 through PWE3.
Configure static PWE3 service 2 on UPE 2 and configure UPE 2 to access NPE 2 through static
PWE3.
2. Configure PWE3 services according the following data planning. After the configuration,
click OK to make the parameter settings take effect.
iManager U2000
Issue 01 (2010-08-16)
Service
Attribute
Service
Type
ETH ETH
Service
Name
pwe3_upe1 pwe3_upe2
Node List
Source UPE1:19-ETFC-1 UPE2:19-ETFC-1
Untermina
ted > Sink
2.2.2.9 3.3.3.9
PW
PW ID 100 100
Signaling
Type
Static Static
Uplink
Label
1001 1002
Downlink
Label
1002 1001

Step 2 Configure VPLS services.
Configure bidirectional PWs between the NPEs. On the NPEs, configure unidirectional PWs
that point to the UPEs.
1. Choose Service > VPLS Service > Create VPLS Service from the main menu.
2. Configure VPLS services according the following data planning. After the configuration,
click OK to make the configured parameters take effect.
Table 11-7 Planning of parameters for configuring the VPLS service
Service
Attribute
Value
Service
Name
vpls
Network
Type
Full-Mesh-VPLS
VSI Name vsi1
VSI ID 100
NPE NPE 1 and NPE 2
iManager U2000
11-17
Service
Attribute
Value
Bidirectio
nal PW
l Source NE: NPE 1
l Sink NE: NPE 2
l PW Type: Dynamic
Untermina
ted PW 1
l Source NE: NPE 1
l Sink NE: UPE 1
l PW Type: Static
Untermina
ted PW 2
l Source NE: NPE 2
l Sink NE: UPE 2
l PW Type: Static

Step 3 Configure the PWE3+VPLS composite service.
1. Choose Service > Composite Service > Create Composite Service from the main menu.
2. Configure basic information about the composite service.
l Service Name: PWE3+VPLS
l Customer Name: customer1
3. In the Service Component area, select the created service components.
l Choose Select > VPLS. On the tab page that is displayed, select vpls.
l Choose Select > PWE3. On the tab page that is displayed, select pwe3_upe1 and
pwe3_upe2.
4. In the Connection Point area, choose Create > PW, and then configure connection points.
iManager U2000
Issue 01 (2010-08-16)
Service
Attribute
Value
PW
connectio
n point 1
pwe3_upe1+vpls
l Name: connection1
l Selected PW 1:
PW ID: 100
Service Type: PWE3
l Selected PW 2:
PW ID: 100
Service Name: vpls
Service Type: VPLS
PW
connectio
n point 2
pwe3_upe2+vpls
l Name: connection2
l Selected PW 1:
PW ID: 100
Service Type: PWE3
l Selected PW 2:
PW ID: 100
Service Name: vpls
Service Type: VPLS

5. After the preceding configurations are complete, click OK to complete the creation of the
composite service.
----End
Postrequisite
Monitor the composite service in real time on the NMS.
In the Composite Service Management service list, select the created composite service. Click
the Topology tab to view the topology of the composite service and obtain the alarms in real
time.
iManager U2000
11-19
11.5.2 Example for Configuring the PWE3+PWE3 Composite
Service
This topic describes the networking application and configuration method of the PWE3+PWE3
Example Description
In this application scenario, protection for the services between rings is enhanced. Fibers in each
section of a service are protected, so that the service is well protected.
For example, a PWE3 service between PE1 and PE4 can be divided into three sections, as shown
in Figure 11-6. PW APS protection is configured for the sections from PE1 to PE2 and from
PE3 to PE4 and LAG protection is configured for the section from PE2 to PE3. In this way, each
fiber has its protection link in each section of the service and thus the protection capability of
the PWE3 service is enhanced.
Figure 11-6 Networking diagram of the PWE3+PWE3 composite service
LAG
PWE3
Service
Protection PW
Working PW Working PW
Protection PW
PWE3
Service
PE1 PE2
PE3
PE4
1-EG16-1
1-EG16-2
1-EG16-1
1-EG16-2
19-ETFC-1
19-ETFC-2
19-ETFC-3
1-EG16-1
1-EG16-2
1-EG16-1
1-EG16-2
19-ETFC-1
Node B
RNC
19-ETFC-1

Service Planning
This topic describes the service planning of the PWE3+PWE3 networking.
Table 11-8 Planning of parameters for configuring the LAG
Parameters Attribute PE2 Value PE3 Value
LAG Name LAG1 LAG1
Revertive Mode Revertive Revertive
Load Sharing Non-Sharing Non-Sharing
Load Sharing Hash
Algorithm
Automatic Automatic
System Priority 0 0
Main Port 19-ETFC-1 19-ETFC-1
iManager U2000
Issue 01 (2010-08-16)
Slave Port 19-ETFC-2
19-ETFC-3
19-ETFC-2
19-ETFC-3

Service
Attribute
Service
Name
pwe3_pe1 pwe3_pe2
Service
Type
ETH ETH
Protection
Type
PW backup protection PW backup protection
Node List
Source PE1: 19-ETFC-1 PE3: 19-ETFC-1
Sink PE2: 19-ETFC-1 PE4: 19-ETFC-1

Table 11-10 Planning of parameters for configuring the composite service
Service
Attribute
Value
Service
Name
PWE3+PWE3
Customer
Name
customer1
Service
Componen
t
PWE3 Service: pwe3_pe1, pwe3_pe2
Interface
Connection
Point
l Name: connection1
l Type: PWE3+PWE3
l Interface Name: 19-ETFC-1
l Equipment Name: PE2, PE3

This topic describes how to configure the PWE3+PEW3 composite services.
iManager U2000
11-21
Prerequisite
Port attributes must be configured.
Procedure
Step 1 Configure the LAG.
Configure parameters relevant to the LAG on both PE2 and PE3.
1. In the NE Explorer, select the NE and choose Configuration > Interface Management >
Link Aggregation Group Management from the Function Tree.
2. Click New, Configure relevant parameters and click OK.
Table 11-11 Planning of parameters for configuring the LAG
LAG Name LAG1 LAG1
Revertive Mode Revertive Revertive
Load Sharing Non-Sharing Non-Sharing
Load Sharing Hash
Algorithm
Automatic Automatic
System Priority 0 0
Main Port 19-ETFC-1 19-ETFC-1
Slave Port 19-ETFC-2
19-ETFC-3
19-ETFC-2
19-ETFC-3

Step 2 Configure PWE3 services.
2. Configure PWE3 services according the following data planning. After the configuration,
click OK to make the parameter settings take effect.
Service
Attribute
Service
Name
pwe3_pe1 pwe3_pe2
Service
Type
ETH ETH
Protection
Type
PW backup protection PW backup protection
iManager U2000
Issue 01 (2010-08-16)
Service
Attribute
Node List
Source PE1: 19-ETFC-1 PE3: 19-ETFC-1
Sink PE2: 19-ETFC-1 PE4: 19-ETFC-1

Step 3 Configure the PWE3+PWE3 composite service.
1. Choose Service > Composite Service > Create Composite Service from the main menu.
2. Configure basic information about the composite service.
l Service Name: PWE3+PWE3
l Customer Name: customer1
3. In the Service Component area, select the created service components.
Choose Select > PWE3. On the tab page that is displayed, select pwe3_pe1 and
pwe3_pe2.
4. In the Connection Point area, choose Create > Interface, and then configure connection
points.
Service
Attribute
Value
Interface
Connectio
n Point
pwe3+pwe3
l Name: connection1
l Type: PWE3+PWE3
l Interface Name: 19-ETFC-1
l Equipment Name: PE2, PE3

5. After the preceding configurations are complete, click OK to complete the creation of the
composite service.
----End
Postrequisite
Monitor the composite service in real time on the NMS.
In the Composite Service Management service list, select the created composite service. Click
the Topology tab to view the topology of the composite service and obtain the alarms in real
time.
iManager U2000
11-23
12 Modifying Configurations
About This Chapter
This topic describes how to modify service configurations, which includes modifying and
deleting service configurations.
12.1 Modifying the Basic Information About Services in Batches
This topic describes how to modify services in batches. If the basic information about certain
existing services needs to be adjusted, you can modify these services.
12.2 Modifying Tunnel Attributes
This topic describes how to modify tunnel attributes, which includes modifying and deleting
tunnels.
12.3 Modifying PWE3 Attributes
This topic describes how to modify PWE3 attributes. When certain existing PWE3 services need
to be adjusted, you need to modify the related attributes.
12.4 Modifying VPLS Attributes
This topic describes how to modify VPLS attributes. When certain existing VPLS services need
12.5 Modifying the Attributes of a L3VPN Service
This topic describes how to modify the attributes of a L3VPN service, which includes modifying,
deleting, and undeploying a L3VPN service.
iManager U2000
Operation Guide for PTN End-to-End Management 12 Modifying Configurations
12-1
12.1 Modifying the Basic Information About Services in
Batches
This topic describes how to modify services in batches. If the basic information about certain
existing services needs to be adjusted, you can modify these services.
Prerequisite
In this example, the modification of the basic information about VPLS services is taken as an
example.
l The communication between the NMS and NEs must be normal.
l You must be an NMS user with NE operator rights or higher.
l The VPLS services must be created.
Procedure
Step 3 Right-click the VPLS services to be modified and choose Details from the shortcut menu.
Modify the basic information about the selected services. Parameters that can be modified are
Service Name, Customer, Customized Attribute 1, Customized Attribute 2, and
Remarks.
NOTE
Parameters that cannot be modified are grayed out.
Step 4 Click OK to return to the main user interface.
----End
12.2 Modifying Tunnel Attributes
This topic describes how to modify tunnel attributes, which includes modifying and deleting
tunnels.
12.2.1 Modifying a Tunnel
This topic describes how to modify a tunnel.
12.2.2 Deleting a Tunnel
This topic describes how to delete a tunnel.
12.2.3 Deleting a tunnel from the network Side
This topic describes how to delete a tunnel from the network side.
12.2.4 Undeploying a tunnel
This topic describes how to undeploy a tunnel.
iManager U2000
Issue 01 (2010-08-16)
12.2.1 Modifying a Tunnel
This topic describes how to modify a tunnel.
Prerequisite
Context
CAUTION
Modifying configurations of a service may interrupt the service running. Exercise caution with
this operation.
Procedure
Step 3 Select a tunnel, and then click the related tabs to modify the related parameters.
NOTE
If you need to modify only the basic information about a tunnel, right-click the tunnel and choose
Details from the shortcut menu. In the dialog box that is displayed, modify basic information about the
tunnel.
Step 4 Click Apply.
----End
12.2.2 Deleting a Tunnel
This topic describes how to delete a tunnel.
Prerequisite
Context
Deleting a tunnel is to delete a configured tunnel from the NMS and equipment at the same time.
Procedure
Step 3 Right-click one or more services and choose Delete from the shortcut menu.
iManager U2000
12-3
Step 4 In the Confirm dialog box, click Yes.
----End
12.2.3 Deleting a tunnel from the network Side
This topic describes how to delete a tunnel from the network side.
Prerequisite
Context
Deleting a tunnel from the NMS is to delete a tunnel from only the NMS. In this case, the tunnel
data configured on the equipment still exists. The deleted tunnel is displayed as a discrete tunnel
on the NMS.
Procedure
Step 3 Right-click one or more services and choose Delete from Network Side from the shortcut menu.
----End
12.2.4 Undeploying a tunnel
This topic describes how to undeploy a tunnel.
Prerequisite
Procedure
Step 3 Right-click a service with Deployment Status being Deployed and choose Undeploy from the
shortcut menu.
After the service is undeployed, the value of Deployment Status changes from Deployed to
Undeployed.
----End
iManager U2000
Issue 01 (2010-08-16)
Postrequisite
After the service is undeployed, you can redeploy the service. If the service fails to be
undeployed, you can modify the service according to the error message, and then undeploy the
service again.
12.3 Modifying PWE3 Attributes
This topic describes how to modify PWE3 attributes. When certain existing PWE3 services need
12.3.1 Modifying a PWE3 Service
This topic describes how to modify a PWE3 service. When certain existing PWE3 services need
12.3.2 Modifying the Tunnel Carrying PWE3 Services
After creating a PWE3 service, you can modify the tunnel that carries a PW online.
12.3.3 Deleting a PWE3 Service
This topic describes how to delete a PWE3 service. You can delete a PWE3 service if it is
inapplicable, for example, when the network is adjusted.
12.3.4 Deleting a PWE3 Service on the Network Side
This topic describes how to delete a PWE3 service from the network side. After a PWE3 service
is deleted from the network side, the information about the PWE3 service is deleted from the
NMS, the VSI in the PWE3 service changes to a discrete service, but the configurations on the
NE side are not affected.
12.3.5 Undeploying a PWE3 Service
This topic describes how to undeploy a PWE3 service. Undeploying a PWE3 service is deleting
the PWE3 service from the NE side only. The service data still exists on the NMS side, and the
service status changes from Deployed to Undeployed.
12.3.1 Modifying a PWE3 Service
This topic describes how to modify a PWE3 service. When certain existing PWE3 services need
Context
CAUTION
this operation.
Procedure
iManager U2000
12-5
Step 3 Select a PWE3, and then click the related tabs to modify the related parameters.
NOTE
If you need to modify only the basic information about a PWE3, right-click the PWE3 and choose
Details from the shortcut menu.
Step 4 Click Apply.
----End
12.3.2 Modifying the Tunnel Carrying PWE3 Services
After creating a PWE3 service, you can modify the tunnel that carries a PW online.
Prerequisite
Context
CAUTION
Modifying the tunnel that carries a PW may interrupt services.
Procedure
Step 3 Select a required service and click the PW tab in the lower portion of the window.
Step 4 On the PW tab page, select the required PW and modify Forward Tunnel or Reverse
Tunnel.
NOTE
l When you set the tunnel policy to Static Binding, you can manually select the MPLS/IP tunnel or GRE
tunnel to be bound.
l When you set the tunnel policy to Select Policy, you can manually adjust the policy selection priority.
The only tunnel policy supported by routers is Select policy.
----End
12.3.3 Deleting a PWE3 Service
This topic describes how to delete a PWE3 service. You can delete a PWE3 service if it is
inapplicable, for example, when the network is adjusted.
Procedure
iManager U2000
Issue 01 (2010-08-16)
----End
12.3.4 Deleting a PWE3 Service on the Network Side
This topic describes how to delete a PWE3 service from the network side. After a PWE3 service
is deleted from the network side, the information about the PWE3 service is deleted from the
NMS, the VSI in the PWE3 service changes to a discrete service, but the configurations on the
NE side are not affected.
Procedure
----End
Postrequisite
After a PWE3 service is deleted from the network side, the information about the PWE3 service
is deleted from the NMS and cannot be viewed in PWE3 service management. The PW
information related to the PWE3 service, however, can be viewed in discrete service
management.
12.3.5 Undeploying a PWE3 Service
This topic describes how to undeploy a PWE3 service. Undeploying a PWE3 service is deleting
the PWE3 service from the NE side only. The service data still exists on the NMS side, and the
service status changes from Deployed to Undeployed.
Procedure
shortcut menu.
Undeployed.
----End
iManager U2000
12-7
Postrequisite
service again.
12.4 Modifying VPLS Attributes
This topic describes how to modify VPLS attributes. When certain existing VPLS services need
12.4.1 Modifying a VPLS Service
This topic describes how to modify a VPLS service. When certain existing VPLS services need
12.4.2 Modifying the Tunnel Carrying VPLS Services
After creating a VPLS service, you can modify the tunnel that carries a PW online.
12.4.3 Deleting a VPLS Service
This topic describes how to delete a VPLS service. When the created VPLS service is not used
any more and you need to adjust the network, you can delete the VPLS service.
12.4.4 Deleting a VPLS Service from the U2000 Side
This topic describes how to delete a VPLS service form the U2000 side. After a VPLS service
is deleted from the U2000 side, the VPLS service is deleted from the U2000 and the VSI in the
VPLS service becomes a discrete service; the configurations on the NE side, however, are not
affected.
12.4.5 Undeploying a VPLS Service
This topic describes how to undeploy a VPLS service. if a VPLS service is undeployed, it is
undeployed only from the NE side and the service data still remains on the NMS side. In addition,
the service status changes from Deployed to Undeployed.
12.4.1 Modifying a VPLS Service
This topic describes how to modify a VPLS service. When certain existing VPLS services need
Context
CAUTION
this operation.
Procedure
iManager U2000
Issue 01 (2010-08-16)
Step 3 Right-click a service and choose Modify from the shortcut menu.
Step 4 Set the related parameters as required.
----End
12.4.2 Modifying the Tunnel Carrying VPLS Services
After creating a VPLS service, you can modify the tunnel that carries a PW online.
Prerequisite
Context
CAUTION
Modifying the tunnel that carries a PW may interrupt services.
Procedure
Step 3 Select a required service and click the PW tab in the lower portion of the window. Select the
PW to be modified Then, click Details.
Step 4 Optional: For the undeployed VPLS service, in the dialog box that is displayed, select a binding
type from the Tunnel Binding Type drop-down list.
NOTE
l When you set the Tunnel Binding Type to Static binding, you can manually select the MPLS/IP
tunnel or GRE tunnel to be bound.
l When you set the Tunnel Binding Type to Select policy, you can manually adjust the policy selection
priority.
The only tunnel policy supported by routers is Select policy.
Step 5 Click the ... button to the right of the Tunnel field, and then select the required tunnel.
Step 6 Click OK.
----End
12.4.3 Deleting a VPLS Service
This topic describes how to delete a VPLS service. When the created VPLS service is not used
any more and you need to adjust the network, you can delete the VPLS service.
iManager U2000
12-9
Context
This operation is used to delete the VPLS service configurations from the NMS and NEs.
Procedure
----End
12.4.4 Deleting a VPLS Service from the U2000 Side
This topic describes how to delete a VPLS service form the U2000 side. After a VPLS service
is deleted from the U2000 side, the VPLS service is deleted from the U2000 and the VSI in the
VPLS service becomes a discrete service; the configurations on the NE side, however, are not
affected.
Procedure
----End
Postrequisite
After a VPLS service is deleted from the network side, the information about the VPLS service
is deleted from the U2000 and cannot be viewed in the VPLS service management window. The
VSI information related to the VPLS service, however, can be viewed in the VSI resource
management window.
12.4.5 Undeploying a VPLS Service
This topic describes how to undeploy a VPLS service. if a VPLS service is undeployed, it is
undeployed only from the NE side and the service data still remains on the NMS side. In addition,
the service status changes from Deployed to Undeployed.
Context
Only VPLS services are undeployed, whereas the tunnels that bearer the services are not
undeployed.
iManager U2000
Issue 01 (2010-08-16)
Procedure
shortcut menu.
Undeployed.
----End
Postrequisite
service again.
12.5 Modifying the Attributes of a L3VPN Service
This topic describes how to modify the attributes of a L3VPN service, which includes modifying,
deleting, and undeploying a L3VPN service.
12.5.1 Modifying a L3VPN Service
This topic describes how to modify a L3VPN service.
12.5.2 Deleting an L3VPN Service
This topic describes how to delete an L3VPN service.
12.5.3 Deleting a L3VPN Service from the Network
This topic describes how to delete a L3VPN service from a network. Deleting a L3VPN service
from a network is to break the association between a VRF and a service. Then, the VRF becomes
a discrete VRF.
12.5.4 Undeploying a L3VPN Service
This topic describes how to undeploy a L3VPN service. L3VPN services are undeployed from
the NE side rather than the NMS side. After a L3VPN service is undeployed from the NE side,
the status of the L3VPN service is changed from Deployed to Undeployed.
12.5.1 Modifying a L3VPN Service
This topic describes how to modify a L3VPN service.
Context
CAUTION
this operation.
iManager U2000
12-11
Procedure
Step 3 Right-click a service and choose Modify from the shortcut menu.
Step 4 Set the related parameters as required.
----End
12.5.2 Deleting an L3VPN Service
This topic describes how to delete an L3VPN service.
Prerequisite
The user must be an NMS user with NE operator rights or higher.
The L3VPN service must be created.
Context
This operation will delete service configuration data from both the NMS and NEs.
Procedure
----End
12.5.3 Deleting a L3VPN Service from the Network
This topic describes how to delete a L3VPN service from a network. Deleting a L3VPN service
from a network is to break the association between a VRF and a service. Then, the VRF becomes
a discrete VRF.
Procedure
iManager U2000
Issue 01 (2010-08-16)
----End
Postrequisite
After the L3VPN service is deleted from the network, the service information is deleted from
the NMS. Therefore, you cannot view the record in L3VPN service management list. The VRF
information to which the service corresponds, however, can be viewed in the discrete service
management list.
12.5.4 Undeploying a L3VPN Service
This topic describes how to undeploy a L3VPN service. L3VPN services are undeployed from
the NE side rather than the NMS side. After a L3VPN service is undeployed from the NE side,
the status of the L3VPN service is changed from Deployed to Undeployed.
Procedure
shortcut menu.
Undeployed.
----End
Postrequisite
service again.
iManager U2000
12-13
Index
A
Advertisement of VPNv4 Routes, 8-16
L
Label Allocation of MP-BGP, 8-15
M
MP-BGP, 8-10
P
Packet Forwarding in a Basic L3VPN, 8-19
PW APS
protection switching, 6-60
R
Route Advertisement of a Basic BGP/MPLS PN, 8-17
V
VPN Route Selection on PEs, 8-15
iManager U2000
Operation Guide for PTN End-to-End Management Index
i-1

Operation Guide For PTN End-To-End Management: Imanager U2000 Unified Network Management System V100R002C01

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Operation Guide For PTN End-To-End Management: Imanager U2000 Unified Network Management System V100R002C01

Uploaded by

Copyright:

Available Formats

iManager U2000 Unified Network Management System

You might also like