v7.0 HP Intelligent Management Center MPLS VPN Manager ...h20628. › km-ext › kmcsdirect › emr_na-c03939884-1.pdf · v7.0HPIntelligentManagementCenter MPLSVPNManagerAdministratorGuide

v7.0 HP Intelligent Management CenterMPLS VPN Manager Administrator Guide

AbstractThis guide provides conceptual and procedural information about MPLS VPN Manager (MVM), a service module that can beadded to an IMC base platform installation to provide full MPLS, L3VPN, L2VPN, and MPLS TE management functionality. Itis aimed at IT network administrators, network planners, and other trusted personnel.

HP Part Number: 5998-4705Software Version: IMC MVM 7.0 (E0101)Published: September 2013Edition: 1

© Copyright 2013 Hewlett-Packard Company.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, CommercialComputer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government undervendor's standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the expresswarranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shallnot be liable for technical or editorial errors or omissions contained herein.

Acknowledgements

Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries

in the United States and other countries.

Microsoft®, Windows®, Windows® XP, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

Java and Oracle are registered trademarks of Oracle and/or its affiliates.

Contents1 Introduction to MPLS VPN Manager............................................................13

MPLS VPN Management.........................................................................................................13MPLS Management.................................................................................................................14MPLS TE Management............................................................................................................15MPLS Management.................................................................................................................15

2 Planning and installation...........................................................................17Introduction............................................................................................................................17Installation requirements..........................................................................................................17Installation types.....................................................................................................................17

Centralized deployment model............................................................................................17Distributed deployment model..............................................................................................18

Accessing the MVM package...................................................................................................18Installing MVM.......................................................................................................................18

Installing MVM in a centralized deployment..........................................................................18Installing MVM in a distributed deployment...........................................................................21L2VPN Management deployment guidelines..........................................................................23

Upgrading MVM....................................................................................................................25Uninstalling MVM...................................................................................................................26

3 Using MPLS VPN Management..................................................................28Overview..............................................................................................................................28Basic VPN concepts................................................................................................................28Quick guide...........................................................................................................................29VPN resource management......................................................................................................31

VPN resource general view.................................................................................................32Region management..........................................................................................................33

Viewing the AS list........................................................................................................33Adding an AS..............................................................................................................34Modifying an AS..........................................................................................................34Deleting an AS.............................................................................................................34Adding a region...........................................................................................................35Modifying a region.......................................................................................................35Deleting a region..........................................................................................................35Viewing the sub-region/PE list.........................................................................................35Importing P devices.......................................................................................................36

Adding devices by view............................................................................................37Adding devices by advanced query............................................................................37

Importing PE devices......................................................................................................38Synchronizing devices....................................................................................................39Switching PEs between regions........................................................................................39Removing P and PE devices............................................................................................39

Group management...........................................................................................................40Viewing the group list....................................................................................................40Adding a group............................................................................................................41Modifying a group........................................................................................................41Deleting a group...........................................................................................................41Importing VPNs............................................................................................................42Modifying a VPN..........................................................................................................42Removing VPNs............................................................................................................42Auditing VPNs or groups...............................................................................................42

VPN management..............................................................................................................43

Contents 3

Viewing the BGP/MPLS VPN list......................................................................................43Querying a BGP/MPLS VPN..........................................................................................44Adding a VPN..............................................................................................................44Modifying a VPN..........................................................................................................44Removing VPNs............................................................................................................45Auditing VPNs..............................................................................................................45Modifying audit intervals................................................................................................45Editing VPN details.......................................................................................................45Viewing VPN connectivity audit information......................................................................50Troubleshooting............................................................................................................51

SA management................................................................................................................52Viewing the SA list........................................................................................................52Querying SAs...............................................................................................................53Adding/Modifying an SA..............................................................................................53Removing SAs...............................................................................................................55Deploying SAs..............................................................................................................55Undeploying SAs..........................................................................................................56

Management VPN.............................................................................................................56Configuring a management VPN.....................................................................................56

VPN devices..........................................................................................................................56VPN device general view....................................................................................................56PE device list.....................................................................................................................57

Viewing the PE device list...............................................................................................57Querying PE devices......................................................................................................58Synchronizing PE devices...............................................................................................58Switching PEs between regions........................................................................................58Removing PE devices.....................................................................................................58

CE device list....................................................................................................................59Viewing the CE device list..............................................................................................59Querying CE devices.....................................................................................................59Importing CE devices.....................................................................................................60Adding/Modifying a non-managed CE...........................................................................60Synchronizing CE devices...............................................................................................61Removing CE devices.....................................................................................................61

Auto discovery.......................................................................................................................61Global topology.....................................................................................................................64

Entering global topology.....................................................................................................64Entering access topology....................................................................................................64Entering service topology....................................................................................................65Topology operations...........................................................................................................65

Viewing device VPN information.....................................................................................66Viewing VPN link information.........................................................................................66Highlighting/Canceling highlight a VPN..........................................................................67Deploying a service.......................................................................................................68Deploying all links.........................................................................................................68Removing deployment configurations...............................................................................68Removing devices from a VPN........................................................................................68Testing VPN connectivity between devices........................................................................69Adding link connectivity.................................................................................................69Querying connectivity information...................................................................................69Troubleshooting............................................................................................................70Auto discovery..............................................................................................................71Auditing all VPN connectivity..........................................................................................71Analyzing MPLS VPN traffic............................................................................................71

Alarm TopN...........................................................................................................................72

4 Contents

Viewing alarm TopN information.........................................................................................72Traffic monitor........................................................................................................................73

Traffic general view............................................................................................................73Setting thresholds...............................................................................................................74

Viewing default threshold list...........................................................................................74Modifying SA inbound/outbound traffic threshold.............................................................75Modifying SA inbound/outbound bandwidth utilization thresholds.......................................75

Setting VPN traffic monitor..................................................................................................76Viewing VPN traffic monitor settings................................................................................76Querying VPNs............................................................................................................76Adding monitor............................................................................................................76Removing monitor.........................................................................................................76

Setting SA traffic monitor....................................................................................................77Viewing SA traffic monitor settings...................................................................................77Querying SAs...............................................................................................................77Adding monitor............................................................................................................77Removing monitor.........................................................................................................77

VPN traffic report...............................................................................................................78Viewing VPN traffic list..................................................................................................78Querying reports...........................................................................................................78Viewing details.............................................................................................................78

SA traffic report.................................................................................................................79Viewing SA traffic list.....................................................................................................79Querying reports...........................................................................................................79Viewing details.............................................................................................................80

Applications..........................................................................................................................81Managing carrier's MPLS VPN............................................................................................81

Adding VPN 1..............................................................................................................82Creating AS 100......................................................................................................82Importing PEs and P devices.......................................................................................82Discovering VPN 1 automatically................................................................................83Verifying the configuration.........................................................................................83

Adding a VCE..............................................................................................................84Adding a new VCE...................................................................................................84Verifying the configuration.........................................................................................84

Monitoring and viewing the traffic of VPN 1 and the traffic between PE 1 and CE 1..............84Adding VPN 1 to be monitored..................................................................................84Viewing the VPN traffic report....................................................................................85Adding the PE1-VCE1 SA to be monitored...................................................................85Viewing the SA traffic report......................................................................................85

Managing enterprise's MPLS VPN........................................................................................85Configuring the management VPN..................................................................................86Adding VPN 2..............................................................................................................87

Adding AS 100........................................................................................................87Importing PEs and P devices.......................................................................................87Importing CEs..........................................................................................................87Adding VPN 2.........................................................................................................87Adding an SC..........................................................................................................88Adding the PE2-CE2 SA............................................................................................88Deploying SAs.........................................................................................................89Verifying the configuration.........................................................................................89

Troubleshooting............................................................................................................894 Using MPLS Management..........................................................................91

MPLS management overview....................................................................................................91

Contents 5

Basic concepts..................................................................................................................91FEC.............................................................................................................................91Label...........................................................................................................................91LSR..............................................................................................................................91LER..............................................................................................................................91LSP..............................................................................................................................92LFIB.............................................................................................................................92Control plane and forwarding plane................................................................................92

Functions..........................................................................................................................93Getting started with MPLS management.....................................................................................93Typical application.................................................................................................................94

Application scenario..........................................................................................................94Scenario analysis...............................................................................................................94Operation procedure..........................................................................................................95

Using MPLS management components ......................................................................................96Device management...........................................................................................................96

Importing devices..........................................................................................................96Deleting devices............................................................................................................98Querying devices..........................................................................................................98Synchronizing devices....................................................................................................99Enabling MPLS and MPLS LDP for devices.........................................................................99Batch enabling MPLS and MPLS LDP for devices................................................................99Device advanced configuration.....................................................................................100Device Traffic Configuration..........................................................................................100Viewing device label statistics.......................................................................................101Querying device interface information...........................................................................101Enabling MPLS or MPLS LDP for interfaces......................................................................101Batch enable MPLS or MPLS LDP for interfaces................................................................102

LDP Management............................................................................................................102Querying LDP peers....................................................................................................102Adding LDP peers.......................................................................................................103Deleting LDP peers......................................................................................................103Configuring LDP peers parameters.................................................................................103Viewing session information..........................................................................................104Viewing LDP peer details..............................................................................................105

LSP Management.............................................................................................................105Querying LSPs............................................................................................................106Adding a static LSP.....................................................................................................106

Configuration procedure..........................................................................................106Configuring a path for the static LSP manually............................................................106Configuring a path for the static LSP automatically......................................................107Assigning values to outgoing labels..........................................................................107Checking labels (optional).......................................................................................108Deploying an LSP...................................................................................................108

Undeploying one or more LSPs......................................................................................108Deleting one or more LSPs............................................................................................108Auditing LSPs..............................................................................................................109Managing an established static LSP...............................................................................109Viewing detailed information about an LSP.....................................................................109

Topology Management.....................................................................................................110MPLS topology tool bar................................................................................................110Using Topology Management.......................................................................................110Highlighting an LSP.....................................................................................................110Viewing an LSP...........................................................................................................111

Label statistics..................................................................................................................111

6 Contents

Querying label usage statistics for a device....................................................................112Viewing device label statistics.......................................................................................112

LSP Traffic Statistics..........................................................................................................112Traffic monitoring information.......................................................................................112Setting default thresholds..............................................................................................113Setting LSP traffic monitoring.........................................................................................113LSP traffic reports........................................................................................................114

5 Using L2VPN Management.....................................................................116Basic VPN concepts..............................................................................................................116

VPLS overview.................................................................................................................116Basic concepts of VPLS................................................................................................116VPLS VPN types..........................................................................................................117

Operation of VPLS...........................................................................................................117VLL overview...................................................................................................................117

Basic concepts of VLL...................................................................................................117PBB overview..................................................................................................................118

Basic concepts of PBB..................................................................................................118Terminology.........................................................................................................................118Using L2VPN Management with non-BGP protocols..................................................................118Managing VPN resources......................................................................................................119

Managing VPNs..............................................................................................................161Viewing the VPN list ...................................................................................................164Querying a VPN.........................................................................................................120Adding a VPN............................................................................................................120Modifying basic VPN settings.......................................................................................169Undeploying VPNs......................................................................................................169Enabling a VSI............................................................................................................169Deleting VPNs............................................................................................................169Auditing VPNs............................................................................................................169

Managing ACs................................................................................................................122Viewing the AC list......................................................................................................123Querying ACs............................................................................................................123Deleting ACs..............................................................................................................123

Deploying VPNs...................................................................................................................123Deploying a VPLS VPN.....................................................................................................123

Defining VPN.............................................................................................................123Configuring PEs..........................................................................................................124Configuring NPEs........................................................................................................124Configuring UPEs........................................................................................................125Configuring CEs..........................................................................................................125Deploying the VPLS VPN..............................................................................................125

Deploying a VLL VPN.......................................................................................................126Defining VPN.............................................................................................................126Configuring the local PE...............................................................................................126Configuring the remote PE............................................................................................127Deploying the VLL VPN................................................................................................127

Deploying a PBB VPN......................................................................................................127Defining VPN.............................................................................................................127Configuring PEs..........................................................................................................128Configuring CEs..........................................................................................................128Deploying the PBB VPN...............................................................................................128

Undeploying VPNs...........................................................................................................129Undeploying a VPN....................................................................................................129Undeploying PEs.........................................................................................................129

Contents 7

Undeploying ACs........................................................................................................129Managing deployment tasks..............................................................................................129

Viewing the deployment task list....................................................................................129Querying deployment tasks..........................................................................................130Performing deployment tasks.........................................................................................130Deleting deployment tasks............................................................................................130

VPN devices........................................................................................................................161PE devices.......................................................................................................................164

Viewing PE devices......................................................................................................131Querying PE devices....................................................................................................131Importing PE devices....................................................................................................132Viewing L2VPN information on a PE..............................................................................163Synchronizing PE devices.............................................................................................166Removing PE devices...................................................................................................169

CE devices......................................................................................................................164Viewing the CE device list............................................................................................134Querying CE devices...................................................................................................135Importing CE devices...................................................................................................135Adding/Modifying a VCE............................................................................................136Synchronizing CE devices.............................................................................................166Removing CE devices...................................................................................................169

Automatic discovery..............................................................................................................137L2VPN topology...................................................................................................................139

Entering L2VPN topology..................................................................................................139Viewing a specific VPN topology.......................................................................................139Topology operations.........................................................................................................139

Viewing device VPN information...................................................................................139Viewing PW information..............................................................................................139Viewing AC information...............................................................................................139Removing an AC.........................................................................................................139Auditing a VPN..........................................................................................................140

Applications........................................................................................................................140Configuring an LDP VPLS VPN................................................................................................140

Network requirements......................................................................................................140Configuring PEs and the P device.......................................................................................140

Configuring PE 1.........................................................................................................140Configuring the P device..............................................................................................141Configuring PE 2.........................................................................................................142

Configuring L2VPN Management......................................................................................142Importing CE 1 and CE 2............................................................................................142Importing PE 1 and PE 2..............................................................................................143Deploying a VPLS VPN................................................................................................143Viewing the VPN topology...........................................................................................144

Configuring an LDP H-VPLS VPN.............................................................................................145Network requirements......................................................................................................145Configuring UPE and NPEs...............................................................................................146

Configuring UPE.........................................................................................................146Configuring NPE 1......................................................................................................146Configuring NPE 3......................................................................................................147

Configuring L2VPN Management......................................................................................147Importing CE 1 and CE 3............................................................................................147Importing UPE, NPE 1, and NPE 3.................................................................................147Deploying a hierarchical VPLS VPN...............................................................................148Viewing the VPN topology...........................................................................................149

Configuring a VLL VPN..........................................................................................................150

8 Contents

Network requirements......................................................................................................150Configuring devices.........................................................................................................151

Configuring CE 1........................................................................................................151Configuring PE 1.........................................................................................................151Configuring the P device..............................................................................................152Configuring PE2..........................................................................................................152Configuring CE 2........................................................................................................153

Configuring L2VPN Management......................................................................................153Importing CE 1 and CE 2............................................................................................153Importing PE 1 and PE 2..............................................................................................153Deploying a VLL VPN..................................................................................................154Viewing the VPN topology...........................................................................................155

Configuring a PBB network....................................................................................................156Network requirements......................................................................................................156Configuring BEBs.............................................................................................................157

Configuring BEB 1......................................................................................................157Configuring BEB 2......................................................................................................157

Configuring L2VPN Management......................................................................................157Importing Device A and Device B..................................................................................157Importing BEB 1 and BEB 2..........................................................................................157Deploying a PBB network.............................................................................................158Viewing the VPN topology...........................................................................................159

Using L2VPN Management with BGP protocol..........................................................................160VPN devices........................................................................................................................161

PE devices.......................................................................................................................164Viewing PE devices......................................................................................................161Querying PE devices....................................................................................................161Importing PE devices....................................................................................................162Viewing L2VPN information on a PE..............................................................................163Synchronizing PE devices.............................................................................................166Removing PE devices...................................................................................................169

CE devices......................................................................................................................164Viewing the CE device list............................................................................................164Querying CE devices...................................................................................................164Importing CE devices...................................................................................................165Adding/Modifying a VCE............................................................................................165Synchronizing CE devices.............................................................................................166Removing CE devices...................................................................................................169

Managing VPN resources......................................................................................................166Managing VPNs..............................................................................................................166

Viewing the VPN list....................................................................................................169Querying a VPN.........................................................................................................169Modifying basic VPN settings.......................................................................................169Enabling a VSI............................................................................................................169Deleting VPNs............................................................................................................168Auditing VPNs............................................................................................................168

Managing ACs................................................................................................................168Viewing the VPN list....................................................................................................169Querying ACs............................................................................................................169Deleting ACs..............................................................................................................169

Automatic discovery..............................................................................................................169L2VPN topology...................................................................................................................171

Entering L2VPN topology..................................................................................................171Viewing a specific VPN topology.......................................................................................171Topology operations.........................................................................................................171

Contents 9

Viewing device VPN information...................................................................................171Viewing PW information..............................................................................................171Auditing a VPN..........................................................................................................171

Application..........................................................................................................................171Managing an BGP VPLS VPN................................................................................................172

Network requirements......................................................................................................172Importing CE 1 and CE 2.................................................................................................172Importing PE 1 and PE 2...................................................................................................172Auto Discovering BGP VPLS VPN.......................................................................................173Viewing the VPN topology................................................................................................173

6 Using MPLS TE Management...................................................................175MPLS TE Management overview.............................................................................................175

TE and MPLS...................................................................................................................175MPLS TE Management......................................................................................................175Basic concepts................................................................................................................176

LSP and MPLS TE tunnel...............................................................................................176MPLS TE implementation...................................................................................................177

Advertising TE attributes...............................................................................................177Calculating paths........................................................................................................177Establishing paths.......................................................................................................177Forwarding packets.....................................................................................................177

MPLS TE Management workflow........................................................................................177Configuring traffic engineering in MPLS TE Management...........................................................179

Configuring MPLS basic capabilities...................................................................................179Configuring MPLS TE basic capabilities...............................................................................179

Configuration prerequisites...........................................................................................179Managing devices...........................................................................................................179

Importing devices into MPLS TE Management.................................................................180Device auto-discovery.............................................................................................180Import function.......................................................................................................180

Querying for a device..................................................................................................181Synchronizing devices..................................................................................................182Deleting devices..........................................................................................................182Configuring imported devices.......................................................................................182

Managing device interfaces..............................................................................................183Querying for an interface.............................................................................................184Configuring an interface..............................................................................................184Querying for available bandwidth.................................................................................185Configuring interface traffic parameters..........................................................................185Enabling interfaces......................................................................................................186Disabling interfaces.....................................................................................................186

Advanced RSVP-TE features...............................................................................................186RSVP and RSVP-TE.......................................................................................................186Prerequisites for configuring RSVP TE advanced features...................................................186Querying for RSVP TE device features............................................................................187Configuring RSVP for a device......................................................................................187Configuring device RSVP HELLO extension information.....................................................188Querying for interface RSVP TE information....................................................................189Configuring and modifying interface RSVP attributes........................................................189

Configuring an MPLS TE tunnel using static CR-LSP...............................................................190Configuration prerequisites...........................................................................................191Configuration procedure..............................................................................................191Managing static CR-LSP nodes......................................................................................193

Configuring an MPLS TE tunnel using dynamic signaling protocol...........................................194

10 Contents

Configuration prerequisites...........................................................................................194Configuring an MPLS TE explicit path.............................................................................194Managing an explicit path...........................................................................................196

Querying for an explicit path...................................................................................196Configuring a dynamic MPLS TE tunnel..........................................................................196

Managing MPLS TE tunnels...............................................................................................201Querying for an MPLS TE tunnel....................................................................................201Deleting an MPLS TE tunnel..........................................................................................201Modifying an MPLS TE tunnel.......................................................................................201Viewing the network topology of an MPLS TE tunnel........................................................201Viewing detailed information about the ingress device of an MPLS TE tunnel.......................201Viewing detailed information about the MPLS TE tunnel....................................................201

Configuring traffic access..................................................................................................202Configuring traffic access procedure..............................................................................202Managing traffic access...............................................................................................206

Protection management....................................................................................................207CR-LSP backup protection.............................................................................................207Configuring CR-LSP backup protection............................................................................207

Configuration prerequisites......................................................................................207Querying for a tunnel for CR-LSP backup...................................................................207

FRR...........................................................................................................................208Basic concepts.......................................................................................................208FRR link protection and node protection.....................................................................208

Deploying FRR............................................................................................................209Configuring FRR..........................................................................................................209

Configuration prerequisites......................................................................................210Typical applications..............................................................................................................211

Usage scenario 1............................................................................................................211Operation procedure...................................................................................................211






7 Frequently Asked Questions.....................................................................246MPLS VPN Management.......................................................................................................246L2VPN Management.............................................................................................................250MPLS TE Management..........................................................................................................251MPLS Management...............................................................................................................251

8 Support and other resources....................................................................253Contacting HP......................................................................................................................253Subscription service..............................................................................................................253Related information...............................................................................................................253

Documents......................................................................................................................253Websites........................................................................................................................253

Typographic conventions.......................................................................................................253Document conventions......................................................................................................254GUI conventions..............................................................................................................254Symbols..........................................................................................................................254

Contents 11

9 Documentation feedback.........................................................................255Glossary..................................................................................................256Index.......................................................................................................260

12 Contents

1 Introduction to MPLS VPN ManagerMultiprotocol Label Switching (MPLS) is a highly scalable networking technology that works withlabel switching routers (LSR) to create end-to-end circuits for high-speed transmission of virtuallyany kind of digital data.To manage MPLS networks and associated equipment, HP offers MPLS VPN Manager (MVM), anoptional service module that can be added to your HP Intelligent Management Center (IMC)deployment. MVM includes four applications that, together, offer comprehensive MPLS servicemanagement and monitoring, device management, and traffic engineering capabilities from aconvenient single platform. The four MVM function modules are:

• MPLS VPN Management

• L2VPN Management

• MPLS TE Management

• MPLS Management

MPLS VPN ManagementMPLS VPN Management (Figure 1) is the base MVM module. With MPLS VPN Managementinstalled and deployed, you can deploy and use the other MVM modules.

Figure 1 MPLS VPN Management Quick Guide page

MPLS VPN Management offers scalable and centralized enterprise management tools for VPNnetwork devices from HP (H3C), Cisco, and Huawei. These tools include:

• VPN resource management

• VPN device lists

MPLS VPN Management 13

• Fault detection

• Traffic monitoringFor complete information about MPLS VPN Management, see “Using MPLS Management.”

MPLS ManagementThe MPLS Management application (Figure 2) provides tools for administering Layer 2 VPNnetworks, including MPLS-based VPLS networks (using BGP or LDP), MPLS-based VLL networks, andlink layer-based provider backbone bridge (PBB) networks. By operating VPN networks on Layer2, you can deliver point-to-point and point-to-multipoint services on wide area networks (WAN) asif they were on the same local area network (LAN).

Figure 2 L2VPN Management Quick Guide page (using non-BGP protocols)

Supporting the VPLS, VLL, and PBB protocols, L2VPN Management enables scalable, multiple-pointVPN services, rather than the point-to-point services that traditional VPNs provide. Specifically,L2VPN Management offers the following capabilities:

• Importing VPN devices

• Managing VPN lists and attachment circuits

• Deploying VPLS, VLL, or PBB VPN (not supported in BGP protocol)

• Discovering devices with VPN that have not been added to L2VPN Management

• Displaying L2VPN topologyFor complete information about L2VPN Management, see "Using MPLS Management."L2VPN Management offers less capabilities if you select the BGP protocol during MVM deployment.For more information about the deployment, see "L2VPN Management deployment guidelines."

MPLS TE ManagementEnterprise networks are typically complex, offering a variety of services to network users. Sometimes,network load distribution can become out of balance, causing some network resources to become

14 Introduction to MPLS VPN Manager

overloaded while others are underused. The MPLS TE Management (Figure 3) provides trafficengineering tools that enable the administrator to solve network imbalance issues.

Figure 3 MPLS TE Management Quick Guide page

Traffic engineering (TE) is the process of steering traffic across the network backbone to enableefficient use of available bandwidth between two routers. MPLS TE is a technology that enablesservice providers to more precisely control data transmission paths to avoid network congestion.The MPLS TE Management provides easy access to a variety of TE tools, specifically:

• TE topology

• Resource management

• RSVP TE advanced device and interface functionality

• MPLS TE tunnel management

• Explicit path management

• Protection management

• Traffic access managementFor complete information about MPLS TE Management, see “Using MPLS TE Management.”

MPLS ManagementThe MPLS Management application (Figure 4) provides a comprehensive set of tools that enablesadministrators to manage and monitor MPLS networks from IMC.

MPLS Management 15

Figure 4 MPLS Management Quick Start page

Tools provided by MPLS Management include:

• Device management

• LDP management

• LSP management

• Topology management

• Label statistics

• LSP traffic statisticsFor complete information about MPLS TE Management, see “Using MPLS Management.”

16 Introduction to MPLS VPN Manager

2 Planning and installationIntroduction

The following information describes how to install and deploy MPLS VPN Manager (MVM) as partof an IMC system. You can install and deploy MVM in a centralized or distributed IMCconfiguration.

Installation requirementsTo prepare for installation of the MVM module, make sure that you have met the followingrequirements:

• IMC is already installed and deployed on your enterprise network or in your lab environment.For more information, see HP Intelligent Management Center deployment guides.

• You have administrator access to the IMC base platform servers on which you intend to installMVM.

• IMC Base Platform servers have adequate disk space to accommodate the installation.

• A connection to a supported database is available for the MVM deployment.For more information about the installation requirements, see MVM readme .

Installation typesThe type of MVM installation to perform depends on your IMC deployment model.

• Centralized—MVM is installed on the same machine as the IMC base platform.

• Distributed—In IMC distributed deployment, first install the IMC Platform to the master server,and then deploy MVM components to the subordinate server.

Centralized deployment modelIn a centralized deployment, as shown in Figure 5, the MVM service module is installed on theIMC base platform. The IMC database can be installed on the same server as the base platformor on a remote server. The database for MVM can also reside on the base platform or on a remoteserver.

Figure 5 MVM centralized deployment model diagram

Introduction 17

Distributed deployment modelIn the distributed deployment model, as shown in Figure 6, one IMC base platform server operatesand communicates as a master server to one or more subordinate server on which the the MVMcomponent is deployed. Operators access MVM functionality through the master server.A distributed deployment of MVM addresses the need for IMC scalability and is ideal forgeographically dispersed environments with a large number of network nodes and services to bemanaged.

Figure 6 MVM distributed deployment model diagram

You can install the databases for IMC on the same servers as the base platform or on remoteservers. The IMC installation program creates the database files that the MVM components connectto on the same base platform servers or remote servers as the IMC database.

Accessing the MVM packageIf the MVM service module is not available in your IMC package, consult with your authorized HPrepresentative to obtain the software.

Installing MVMWith IMC already installed and deployed on your network, use one of the following proceduresto install MVM.

Installing MVM in a centralized deploymentTo install MVM in a centralized deployment (one IMC Base Platform server), use the followingprocedure:

18 Planning and installation

1. Log on to the IMC master server as an administrator and launch the HP Intelligent DeploymentMonitoring Agent.• On Windows, select Start > All Programs > HP Intelligent Management Center > HP

Deployment Monitoring Agent.• On Linux, run the dma.sh script from a command window. The script is available in the

<installdir>/iMC/deploy folder (where <installdir> is the directory into whichyou installed IMC).

The HP Intelligent Deployment Monitoring Agent window appears, as shown in Figure 7.

Figure 7 HP Intelligent Deployment Monitoring Agent window

2. Click the Install button.The Choose folder dialog box appears, as shown in Figure 8, with the directory path for lastIMC component that you installed.

Figure 8 Choose folder dialog box

NOTE: If no location appears in the dialog box, or the location is incorrect for the MVMfiles, click Browse to select the correct directory path on the local machine.

3. In the Choose folder dialog box, when the location containing the MVM package appears,click OK.The HP IMC Installation Wizard appears.

4. Click Next.

Installing MVM 19

5. Read and accept the License Agreement, and then click Next.The installation wizard displays a Choose Target Folder window with a scrolling list of IMCservice components and their installation status (Figure 9).

Figure 9 Choose Target Folder window

6. Select the check boxes for the four MPLS VPN Manager components, and then click Next.7. In the Deployment and Upgrade Options screen, select Deploy or Upgrade at once, and then

click Next.8. In the Installation Summary screen, click Install.

The installation wizard installs the MVM service module, and then displays the Batch deploydialog box (Figure 10).

Figure 10 Batch deploy dialog box


9. Click all four MVM component check boxes, and then click OK.The installation wizard goes through a series of steps to deploy the MVM components. Ifdeployment is successful, it displays the Batch deploy succeeded dialog box.

10. Click OK.If the Readme check box is selected, the document opens up in your web browser and theIMC services restart. MVM is now functional and you can browse to the IMC console to beginusing its many features.

Installing MVM in a distributed deploymentIn a distributed deployment, as shown in Figure 6, servers include the following types:

• Master server—The server on which IMC Platform subcomponents are deployed.

• Subordinate server—Server on which service components are deployed.HP recommends that you install and deploy MVM on a subordinate server.To install and deploy MVM:1. Log on to the server as an administrator and start the Remote Installation Wizard.

• On Windows, run the installslave.bat file in the install directory of the IMCdownloaded installation package.

• On Linux, run the installslave.sh file in the install directory of the IMC downloadedinstallation package.The Address of Master window appears.

2. Type the IP address of the master server, and then click OK.The Checking Database Connectivity dialog box appears, as shown in Figure 11.

Figure 11 Checking Database Connectivity dialog box

3. Connect and authenticate to the local or remote IMC database.a. Specify the database type, instance name, and administrator password created during

database installation.b. Specify database location as local host if the IMC database is installed on the base

platform server, or as other server if installed on a remote server.c. If the database is installed on a remote server, specify the IP address.d. Click OK to verify database connectivity.

Installing MVM 21

When you successfully connect to the database, the main screen of the Remote InstallationWizard appears.

4. Specify the IP address of the master server, and then click OK.The Remote Installation Wizard displays a Choose Target Folder window, as shown inFigure 12, enabling you to specify a location for the installation of the Intelligent DeploymentMonitoring Agent for this server.

Figure 12 Choose Target Folder window

5. Browse to a new deployment location, or accept the default location, and then click Install todownload the necessary files from the master server.After the files are downloaded, the Installation Completed dialog box appears.

6. Click Finish to close the Remote Installation Wizard and start the Intelligent DeploymentMonitoring Agent on the subordinate server.The Intelligent Deployment Monitoring Agent window appears.

7. Select the Deploy tab to view component information, as shown in Figure 13.


Figure 13 IMC components and deployment status

8. Right-click the MPLS VPN Manager — MPLS VPN Management component, and then clickBatch Deploy.The Batch Deploy dialog box appears.

9. Click all MVM component check boxes, and then click OK.The Intelligent Deployment Monitoring Agent downloads the necessary files. When downloadingis complete, the Database Configuration Info window appears.

10. Specify the necessary database configuration information.a. Specify the database type, instance name, administrator password, and database location

for the master database.b. Specify a data file location for the MVM database instance.

11. Click Deploy.The wizard goes through a series of steps to deploy the MVM components. When deploymentis successful, it displays the Batch deploy succeeded dialog box.

12. Click OK.13. On the Intelligent Deployment Monitoring Agent screen, select the Deploy tab to confirm that

the MVM components are deployed on the local server.14. On the master server, start IMC processes.

a. Select Start > All Programs > HP Intelligent Management Center > HP DeploymentMonitoring Agent

b. In the displayed window, select the Monitor tab, and then click Start IMC.c. In the confirmation dialog box, click OK.After all processes are started, IMC is ready for use. MVM is now functional and you canbrowse to the IMC console to begin using its many features.

L2VPN Management deployment guidelinesWhen you deploy L2VPN Management, following these guidelines:

• Select the type of the L2VPN to be managed, as shown in Figure 14

Installing MVM 23

Figure 14 Selecting the VPN type to be managed

• If you select VLL, PBB, and select LDPfor VPLS, L2VPN Management provides the functions onthe left navigation tree as shown in Figure 15. For more information, see "Using L2VPNManagement with non-BGP protocols."

Figure 15 Left navigation tree when VLL, PBB, and LDP VPLS are selected

• If you select BGP for VPLS, you cannot select other options on the page for selecting VPN type.When you select BGP, L2VPN Management provides the functions on the left navigation treeas shown in Figure 16. For more information, see " Using L2VPN Management with BGPprotocol."


Figure 16 Left navigation tree when BGP is selected for VPLS

Upgrading MVMIf a later version of MVM is available, you can upgrade your base platform with the latest version.To upgrade MVM:1. Log on to the IMC Base Platform server as an administrator.2. Obtain the updated MVM service module from your authorized HP representative, and

download it onto the server.3. Launch the HP Intelligent Deployment Monitoring Agent.

• On Windows, select Start > All Programs > HP Intelligent Management Center > HPDeployment Monitoring Agent.

• On Linux, run the dma.sh script from a command window. The script is available in the<installdir>/iMC/deploy folder (where <installdir> is the directory into whichyou originally installed IMC).The Intelligent Deployment Monitoring Agent window appears.

4. Click Install.The Choose folder dialog box appears, displaying the default directory path for IMCcomponents.

5. Browse to the folder that contains the downloaded MVM upgrade components, and makesure that the correct path appears in the Components location.

6. Click OK.The HP IMC Installation Wizard appears.

7. Click Next.8. Read and accept the License Agreement, and then click Next.9. The installation wizard displays a Choose Target Folder window with a scrolling list of IMC

service components and their installation status, as shown in Figure 13.The Choose Target Folder window displays the MVM components to be upgraded. The systeminstalls the upgrade files in the location where the IMC platform is installed.

10. Make sure the check box for MPLS VPN Manager — MPLS VPN Management is selected, andthen click Next.

11. In the Deployment and Upgrade Options screen, select Deploy or upgrade at once, and thenclick Next.

Upgrading MVM 25

12. In the Installation Summary screen, click Install.The installation wizard installs the MVM service module, and then displays the Batch Deploydialog box.

13. Click all MVM component check boxes, and then click OK.The installation wizard goes through a series of steps to deploy the upgraded MVMcomponents. If deployment is successful, it displays a Batch deploy succeeded dialog box.

14. Click OK.If the Readme check box is selected, the document opens in your web browser, and the IMCservices are restarted. The MVM components are now upgraded, and you can browse to theIMC console to begin using the latest features.

Uninstalling MVMThe MPLS VPN Manager includes four related applications:• MPLS VPN Manager — MPLS VPN Management

• MPLS VPN Manager — MPLS Management

• MPLS VPN Manager — L2VPN Management

• MPLS VPN Manager — MPLS TE ManagementTo uninstall MVM entirely from your IMC deployment, you need to undeploy all four componentsin the correct order, then remove them from all IMC Base Servers on which they are installed.

NOTE: Before you can uninstall MVM from your IMC Base Platform, you must stop IMC processes.Therefore, HP recommends that you consider uninstalling MVM during off-peak business hours.

To uninstall MVM:1. Log on to the IMC Base Platform server as an administrator and launch the HP Intelligent

Deployment Monitoring Agent.• On Windows, select Start > All Programs >HP Intelligent Management Center > HP

Deployment Monitoring Agent.• On Linux, run the dma.sh script from a command window. The script is available in the

<installdir>/iMC/deploy folder (where <installdir> is the directory into whichIMC was installed).

The Intelligent Deployment Monitoring Agent window appears.2. In the Monitor tab of the agent window, select Stop IMC to stop all IMC processes.3. In the Intelligent Deployment Monitoring Agent window, select the Deploy tab.4. Scroll down to the two MVM components.

NOTE: Make sure to undeploy and remove the components in the exact order described inthe following steps.

5. Undeploy the components in this order: MPLS TE Management, L2VPN Management, MPLSManagement, and MPLS VPN Management, as follows:a. Right-click the component and from the context menu, select Undeploy the Component.b. If a message appears asking if you want to delete database data used by the component,

click Yes. A progress dialog appears, and after the component is undeployed, anOperation succeeded message appears.

c. Click OK.d. Repeat steps a to c to undeploy each remaining component.

6. Remove the MVM components in the same order as follows:


a. Right-click the component and from the context menu, select Remove this Component. Amessage informs you that the component is to be removed from the server.

b. Click Yes. A progress dialog appears, and after the component is removed, an Operationsucceeded message appears.

c. Click OK.d. Repeat steps a to c to remove each remaining MVM component.

7. Select the Monitor tab of the Intelligent Deployment Monitoring Agent, and then click the StartIMC button to restart the IMC services.

Uninstalling MVM 27

3 Using MPLS VPN ManagementOverview

This chapter describes the MPLS L3VPN management features of MPLS VPN Management.MPLS L3VPN supports various networking modes and has excellent scalability. However, MPLSL3VPN is complicated to deploy and maintain, and only qualified engineers can design and deployMPLS L3VPN networks. To simplify MPLS L3VPN deployment and maintenance, MVM providesthe following functions:

• Automatic discovery of VPNs running on networks—MVM can automatically discover MPLSL3VPNs deployed on a network, and guide network administrators to complete linkconfiguration.

• VPN service deployment wizard—MPLS VPN Management provides a wizard to simplify VPNdeployment. For example, you can add an MPLS L3VPN site by following the SA wizardwithout needing to know the commands and parameters.

• Visualized VPN services—VPN logically isolates services on a physical network. It is difficultto manage services on the VPN network. MPLS VPN Management provides the VPN globaltopology, access topology, and service topology. These topologies show the physical andlogical connections of the whole MPLS VPN network and the connections of each MPLS VPN.

• Visualized VPN traffic—MPLS VPN Management can monitor the inbound and outbound trafficof an MPLS L3VPN or of a site access link (an SA). For an SA, MPLS VPN Management canmonitor the bandwidth usage of the inbound and outbound traffic. When the traffic exceedsthe threshold, the system generates an alarm. In addition, MPLS VPN Management cancooperate with NTA to allow network administrators to view traffic information on topologies.

• Various VPN audit functions—MPLS VPN Management provides VPN configuration andconnectivity audit functions. The configuration audit can display the configuration changeson PE devices. The connectivity audit can display the connectivity status of a VPN and displaythe positions of faults in a graph.

• Intelligent troubleshooting—MPLS VPN Management can automatically find the faults andcauses for broken VPN links.

Basic VPN conceptsTypically, enterprises must find ways to communicate both internally and externally using increasinglycomplex, and potentially insecure, Internet and LAN technologies. One solution is to use dedicatedprivate lines, which can be expensive, and cannot accommodate mobile offices. A more attractivesolution is using a VPN. Using a VPN allows private networks to run on public networks whileproviding the secure and reliable communication of a private network. VPN uses specific tunnelingprotocols to transmit VPN packets over different tunnels.Carriers can make full use of the available network resources to increase services by providingVPN services to enterprises. And enterprises can select different service levels as needed, thereforegetting the services they need and reducing their networking cost at the same time. Additionally,the scalability of VPN provides support and convenience for your mobile offices. VPN allowsenterprises to connect with remote offices, staff traveling on business, and business partners at alow cost while improving utility of network resources.

28 Using MPLS VPN Management

VPNs can be classified by:• Networking model

VPDN—Point-to-point VPN.◦◦ Leased line VPN (VPRN, VPLS, VLL).

• Service application

Access VPN—Allows users and small offices to establish private network connections withthe intranet or extranet of their enterprise over a public network.

◦

◦ Intranet VPN—Interconnects points distributed inside an enterprise.

◦ Extranet VPN—Extends an enterprise network to co-operators by using VPN.

• Operation mode

CPE-based VPN CPN—IPsec, VPN, GRE VPN, and VPDN.◦◦ Network-based CPN—Includes CLL, CPRN, CPLS and L3VPN, conducted by ISP. All

functions are implemented at network device side.

• Working layer

L2VPN◦◦ L3VPN

Quick guideThis chapter provides a quick guide that helps you use MPLS VPN Management to add and maintainVPNs.

Figure 17 MPLS VPN Management service flowchart

Quick guide 29

1. Add regions and devices:a. (Required.) Add an AS to MPLS VPN Management according to the BGP AS planning

on your network or the BGP AS configurations on the P and PE devices. For moreinformation, see "Adding an AS."

b. Add regions.When an AS is too large to manage, you can divide the AS into multiple regions, andmanage P and PE devices by region. Region is a logical concept in MPLS VPNManagement. Region configurations are not deployed to devices. For information abouthow to add a region, see "Adding a region."

c. Enter an AS or enter a region of an AS to import P and PE devices. For more information,see "Importing P devices" and "Importing PE devices."

d. Add CEs to MPLS VPN Management.• CE—A CE that can be managed by MPLS VPN Management.

• Non-managed CE—A CE from a third-party vendor that MPLS VPN Managementcannot manage. MPLS VPN Management creates a virtual CE (VCE) to represent anon-managed CE.

• MCE—A CE that is connected to multiple VPNs. A router that supports the MCEfunction can serve as an MCE device.

• VMCE—VLAN isolation of MCE, an MCE implemented by a Layer 3 switch thatsupports multiple VLAN interfaces.

• VMCE—Virtual MCE, an MCE from a third-party vendor that MPLS VPN Managementcannot manage.

For more information about CE devices, see "CE device list."

After you complete the previous operations, you can view information about regions, PEdevices, and CE devices on the region list, PE device list, and CE device list, respectively.

2. Add VPNs:After you add regions and devices to MPLS VPN Management, you can add VPNs by usingthe following methods.

• Automatic discoveryUse this method to add existing VPNs on the network to MPLS VPN Management. Selectone or more PE devices as seed devices. MPLS VPN Management uses the seed devicesto discover the VPNs that have been deployed, and add these VPNs. For more information,see "Auto discovery."

• Manual deploymentUse this method to add a new VPN to the network. You can configure the VPN auditperiod, SC attributes (import RT and export RT), SA links (CE-PE links), and CE-CE links.For more information, see "Adding a VPN" and "Editing VPN details."

After you add VPNs to MVM, you can view and modify VPN information on the VPN list.


3. Maintain VPNs:MPLS VPN Management provides various management functions to maintain VPN services.• Access topology and service topology for each VPN service. The access topology for a

VPN displays the CE-PE links in the VPN. The service topology for a VPN displays thelogical links between CEs in the VPN. For more information, see "Global topology."

• TopN alarms. You can view the top-N VPN services, CE devices, and PE devices by alarmseverity. For more information, see "Alarm TopN."

• VPN configuration audit and connectivity audit. By using the configuration audit, youcan view configuration changes on PE devices. By using the connectivity audit, you canview the connectivity status of a VPN service. For more information, see "VPNmanagement."

• Troubleshooting. For disconnected links discovered by connectivity audit, MPLS VPNManagement can automatically check configurations, and find the faults and causes. Formore information, see "Troubleshooting."

• Traffic monitoring. You can monitor the traffic for a VPN and view the traffic monitoringreport. For more information, see "Traffic monitor."

VPN resource managementMPLS VPN resource management includes region management, group management, VPNmanagement, SA management, and management VPN, as shown in Figure 18. You can query,view, add, modify, delete, and reuse the resources.

Figure 18 Resource relationships

• Region management includes AS, region, P device, and PE device resources. With the regionmanagement function, you can add multiple ASs to an MPLS VPN to manage network devicesby AS. To further narrow the scope of management, you can add multiple regions to an ASand add multiple subregions to a region according to network devices' locations. After youadd the ASs or regions, import the P and PE devices to the ASs or regions.

• Group management includes subgroup and VPN resources. With the group managementfunction, you can group VPNs by department or service. The group-based managementimproves the efficiency of the VPN service management.

VPN resource management 31

• VPN management manages a single MPLS VPN service, which consists of SC, SA, PE, andCE resources. You can use the VPN management function to add, view, and audit a VPNservice. In addition, you can view the access topology and service topology for the VPNservice, and configure and modify the VPN information.

• SA management manages the access link between a CE and a PE. You can add, deploy,view, and modify an access link.

• After you add a management VPN to MVM, the system automatically filters traffic of themanagement VPN so that MVM manages only MPLS VPN services.

VPN resource general viewMPLS VPN Management provides the general view of the statistics for VPN resources, VPNdisconnectivity, VPN alarms, and SA deployment.To enter the VPN resource general view page:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources.

The VPN Resource General View displays four VPN charts.

Figure 19 VPN resource general view

You can obtain the statistics of the existing resource deployment and failures in this page.

• The VPN resource bar chart shows the number of ASs, groups, SAs, and VPNs.

• The VPN disconnectivity Top 5 bar chart shows the top 5 VPN services by disconnectivity.

• The VPN alarm pie chart shows the number and proportion of the VPN services in each alarmstate.

• The SA deployment pie chart shows the number of SAs in each deployment state.


Region managementThis function manages the ASs and regions in an MPLS VPN. A region supports a maximum offour layers of subregions. After adding ASs and regions, you can import P and PE devices into theASs, regions, or subregions.

Figure 20 Region management operation process

1. Add an AS. For more information, see "Adding an AS."2. Import P and PE devices to the AS. For more information, see "Importing P devices" and

"Importing PE devices."3. Add regions to a large-scale AS or add subregions to a region. For more information, see

"Adding a region."4. Import P and PE devices to the corresponding regions or subregions. For more information,

see "Importing P devices" and "Importing PE devices."5. When a device's location changes, use the switch PEs between regions function to switch PEs

between regions. For more information, see "Switching PEs between regions."After you create ASs and regions/subregions, and import P and PE devices, you can synchronizeor delete devices in the sub-region/PE list.

Viewing the AS list1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Region management.

The AS List page displays all ASs.AS List contents

• AS Name—Name of the AS. Click the name of the AS to view its details.

• AS Number—Number of the AS.

• Operation—Provides the Modify icon to modify the AS and the Delete icon todelete the AS.


3. Click Refresh to refresh the AS list.Navigating the AS List

• Click the Next Page icon to page forward in the AS List.

• Click the Last Page icon to page forward to the end of the AS List.

• Click the Previous Page icon to page backward in the AS List.

• Click the First Page icon to page backward to the front of the AS List.Click 8, 15, 50, 100, or 200 at the upper right of the AS List to configure how many itemsper page you want to display.

NOTE: You can sort the AS List by every field except the Operation field. Click the column labelto sort the list by the selected field. The column label is a toggle switch that allows you to togglebetween the various sort options specific to each field.

Adding an AS1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Region management.

The AS List page displays all ASs.3. Click Add on top of the AC List area.

The Add AS dialog box appears.4. Enter the AS name and the AS number for an AS, which must be unique in MVM.5. Click OK.

Modifying an AS1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Region management.

The AS List page displays all ASs.

3. Click the Modify icon for the AS you want to modify.The Modify AS dialog box appears.

4. Modify the AS name and the AS number for the AS, which must be unique in MVM.5. Click OK.

Deleting an ASYou cannot delete an AS when a P device, a PE device, or a region exists in the AS. To delete theAS, delete the P device, PE device, and the region first.To delete an AS:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Region management.

The AS List page displays all ASs.

3. Click the Delete icon for the AS you want to delete.A confirmation dialog box appears.

4. Click OK.


Adding a region1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Region management.

The AS List page displays all ASs.3. Click the name link of an AS.

The Sub-region/PE Device List page appears.4. Click the Add Region link on top of the Sub-region/PE Device List area.

The Add Region dialog box appears.5. Enter the region name that must be unique in MVM.6. Click OK.

Modifying a region1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Region management.


The Sub-region/PE Device List page appears.

4. Click the Modify icon in the Operation field for the region to be modified.The Modify Region dialog box appears.

5. Enter the region name that must be unique in MPLS VPN Management.6. Click Add.

Deleting a regionYou cannot delete a region when a device or a subregion exists in the region.To delete a region:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Region management.



4. Click the Delete icon in the Operation field for the region to be deleted.A confirmation dialog box appears.

5. Click OK.

Viewing the sub-region/PE listYou can view the sub-region/PE list when you enter an AS, a region, or a subregion. Take thesub-region/PE list for an AS as an example:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Region management.




Sub-region/PE List Device contents

• Status—Alarm state of the P or PE device. This filed displays hyphens (--) for a region.

• Sub-region/Device Name—Region name of a region, or the device name and IP addressof a device.

• Type—Type for each item in the AS list, Region, P, PE, SPE, UPE.

• AS Number—AS number for the PE device. This field displays hyphens (--) for a regionand a P device.

• Device IP/Mask—IP address and mask of the device. This field displays hyphens (--) fora region.

• Last Synchronization Time—Last time when the PE device is synchronized, in the formatYYYY-MM-DD hh:mm:ss.

• Synchronization Status—Results of the last synchronization, Synchronizing, Success, orFailure.

• Operation—Provides links for the modify, view, and delete operations.

◦ Click the Modify icon to modify a region and the Delete icon to delete aregion.

◦ Click the Details icon to view detailed VPN information for a PE device.

◦ Click the Delete icon to delete a P device.

4. Click Refresh to view the latest Sub-region/PE Device List.

NOTE: You can sort the Sub-region/PE Device List by every field except the Operation field. Clickthe column label to sort the list by the selected field. The column label is a toggle switch that allowsyou to toggle between the various sort options specific to each field.

Importing P devicesPerform this task to import P devices to an AS or a region. Before importing the devices, make surethe devices to be imported meet the following conditions:

• Enabled with SNMP.

• Added into IMC, and recognized and managed by IMC.

• Not imported as PE or CE devices.To import P devices:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Region management.


The Sub-region/PE Device List page appears.4. Click Import P on top of the Sub-region/PE Device List area.

The Import Device page appears.5. Click Select to select the P devices to be imported.

There are two methods for selecting devices, By View or using the Advanced option. See"Adding devices by view" and "Adding devices by advanced query."


6. Check the imported devices.• To add more devices, repeat step 5.

• To delete devices, select one or multiple devices in the list, and click Remove.7. Click OK.

The page for import progress appears. You can view the import process and result in thispage.

Adding devices by view1. From the Select Devices dialog box, click the By View tab.2. Expand the view you want to select devices from by clicking on the arrow to the left of the

three view options, IP View, Device View, or Custom View.3. From the navigation tree, click the view you want to select devices.

The devices from the group you click on will appear in the Devices Found field to the right ofthe navigation tree. You can select devices from more than one group simply by clicking onmore than one group.

4. Highlight the devices you want to select from the Devices Found list and click the Add selected

button to add them to the selected devices list.

5. To remove one or more devices, select them and click the Remove selected button .6. Confirm that the devices you have found have been added by reviewing the Selected Devices

list.7. Click OK. Confirm that the devices now appear in the Import Device page.

Adding devices by advanced queryYou can also add devices using the Advanced Query option to search IMC using various criteriaand use the results of the search to add devices. To do so,1. Click Select on the right of the Selected Devices field.2. From the Select Devices dialog box, click the Advanced tab.

Enter values in one or more of the search parameters listed:

• Device IP—Enter the IP address you want to query for. Click on the Exact Query checkboxif you want IMC to search for the exact IP address you have entered. Leave the ExactQuery box unchecked if you want IMC to match only a certain portion of the IP address.

• Device IP List—Configure multiple device IP addresses to be searched. Click the link.Then, the Device IP List Configuration window appears. Enter one or multiple device IPaddresses in the Input Device IP field (if you enter multiple IP addresses, enter one IPaddress on each line), and then click Add to add the entered IP addresses to the DeviceIP List field below. Repeat the steps above to add all device IP addresses to be searched.To delete an IP address in the Device IP List field, select the IP address and then clickDelete. Click OK to complete the operation. Make sure that the device IP addresses to besearched have been added to the Device IP List field. To clear the Device IP List field, clickthe link.

• Device Label—Enter the device name for the devices you want to add. MVM supportsfuzzy matching for device labels. Therefore, you can enter the entire device label for thedevice you want to locate, or you can enter just a portion of it. IMC will display all matchesthat contain the portion you enter.

• Device Status—Select a device state from the Device Status list.

• Device Category—Select a device category from the Device Category list.

• Device Series—Select a device series from the Device Series list.


• Contact—Enter the contact name information you want to search by. MVM supports fuzzymatching for this field. Therefore, you can enter a partial string for the contact or thecomplete string for the contact.

• Location—Enter the location information you want to search by. MVM supports fuzzymatching for this field. Therefore, you can enter a partial string for location or the completestring for location.

• Device Reachability—Select a device reachability state from the Device Reachability list.3. Click Query to begin your search.

The results of your search will appear in the Devices Found field.

4. Highlight the devices you want to select and click on the Add selected button to add themto the selected devices list.

5. To remove one or more devices, select them and click on the Remove selected button .6. Confirm that the devices you have found have been added.7. Click OK to enter the Import Device page. The selected devices now appear in the page.

Importing PE devicesPerform this task to import PE devices to an AS or a region. Before importing the devices, makesure the devices to be imported meet the following conditions:

• Enables with SNMP and are enabled with SNMP.


• Not imported as P or CE devices.

• Configured with BGP.

• Enabled with MPLS or configured with VRF.To import PE devices:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Region management.


The Sub-region/PE Device List page appears.4. Click Import PE on top of the Sub-region/PE Device List area.

The Import Device page appears.5. Enable or disable Filter devices according to AS number. If it is enabled, the system compares

the AS number of the imported device with the AS number of the current region. If the two ASnumbers are not the same, the device is not allowed to be imported.

6. Click Select to select the PE devices to be imported.There are two methods for selecting devices, By View or using the Advanced option. See"Adding devices by view" and "Adding devices by advanced query."

7. Highlight the devices you want to select and do one of the followings:

• To add them to the Selected Devices list, click Add selected .

• To select all of the devices displayed in the Devices Found list, click Add all .

• To remove one or more, select them and click Remove selected .

• To remove all of the selected devices, click Remove all .


8. Confirm that the devices you have found have been added.9. Click OK to enter the Import Device page.

The selected devices now appear in the page.10. Check the imported devices.

• To add more devices, repeat step 6.


The page for import progress appears. You can view the import process and result.

Synchronizing devicesPerform this task to synchronize the current device configurations to MPLS VPN Managgement. Pdevices do not support this function.To synchronize devices:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Region management.



4. Select one or multiple devices to be synchronized in the list and click Synchronize.The Synchronization Status field in the list displays the synchronization process of the devices.

5. Click Refresh to view the latest synchronization result.

Switching PEs between regionsPerform this task to move PE devices from a region to another region in the same AS. P devicesdo not support this function.To switch PEs between regions:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Region management.



4. Select one or multiple devices to be switched in the list and click Switch.The AS/Region window appears.

5. Select a region.6. Click OK.

Removing P and PE devicesPerform this task to remove P or PE devices from MPLS VPN Management.To remove P and PE devices:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Region management.




4. Select one or multiple devices to be removed in the list and click Remove.A confirmation dialog box appears.

5. Click OK.

Group managementMPLS VPN Management supports managing VPNs by group.

Figure 21 Group management structure

Use the group management function as follows:1. Add a group.2. Import one or multiple VPNs to the group.3. Perform the following operations for the VPNs in the group as needed:

• Remove the VPNs.

• Audit the VPNs.

• Display the access topology and service topology.4. Add subgroups to the group, and import VPNs to the subgroups.

Viewing the group listThe group list includes the groups and the VPN information.To view the group list:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Group management.

The Group List page displays all groups.Group List contents

• Status—Highest level alarm state for a PE or a CE. This field displays hyphens (--) for agroup.

• Group/VPN Name—Name of a group or a VPN.

• Type—Type for an entry in the list, Group or BGP/MPLS VPN.

• Access Topology—Provides a link to access the VPN access topology. This field displayshyphens (--) for a group.


• Service Topology—Provides a link to access the VPN service topology. This field displayshyphens (--) for a group.

• Operation—Click the Modify icon to modify a group, and click the Delete iconto delete a group.

3. Click Refresh on top of the Group List to view the latest Group List.

Adding a group1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Group management.

The Group List page displays all groups.3. Click the Add Group link on the upper right of the list. Or, click a group name to enter the

lower level group list, and then click the Add Group link on the upper right of that list.The Add Group dialog box appears.

4. Enter the group name.5. Click OK.

NOTE:• You can add subgroups in a group. MVM supports six levels of groups at most.

• Names of groups in the same level must be unique. Names of groups in different levels canbe the same.

Modifying a group1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Group management.

The Group List page displays all groups.

3. Click the Modify icon for the group to be modified. Or, click a group name to enter the

lower level group list, and click the Modify icon for the group to be modified.The Modify Group dialog box appears.

4. Enter the new group name.5. Click OK.

Deleting a groupPerforming this task does not affect devices or delete VPNs in a group. When a group containssubgroups or VPNs, you can still use this function to delete the group.To delete a group:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Group management.


3. Click the Delete icon for the group you want to delete. Or, click a group name to enter

the lower level group list, and then click the Delete icon for the group to be deleted.A confirmation dialog box appears.

4. Click OK.


Importing VPNsPerform this task to import one or multiple VPNs to a group or its subgroups. A VPN can belongto multiple groups.To import VPNs:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Group management.

The Group List page displays all groups.3. Click Import VPN on top of the Group List area. Or, click a group name to enter the lower

level group list, and click Import VPN on top of the Group List area.The Import VPN dialog box appears.

4. Enter a VPN name and click Query.5. Select the VPNs to be imported and click OK.

Modifying a VPN1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Group management.


3. Click the Modify icon for the VPN that you want to modify. Or, click a group name to

enter the lower level group list, and then click the Modify icon for the VPN to be modified.The Modify VPN dialog box appears.

4. Modify the following parameters as needed:• VPN Name—Enter a new VPN name that must be unique in MPLS VPN Management.

• Connectivity Audit—Set whether to enable connectivity audit. Options are Periodical auditand Not Audit. If Periodical audit is set, you can modify the audit interval in the range of2 to 168 hours. The default setting is 8 hours.

• Description—Modify descriptive information for the VPN.5. Click OK.

Removing VPNs1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Group management.

The Group List page displays all groups.3. Select the VPNs to be removed and click Remove VPN. Or, click a group name to enter the

lower level group list, select the VPNs to be removed, and click Remove VPN.A confirmation dialog box appears.

4. Click OK.

Auditing VPNs or groupsPerform this task to audit the connectivity of VPNs or groups containing VPNs. You cannot performthis task for empty groups.To audit VPNs or groups:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Group management.



3. Select the VPNs or groups to be audited and click Audit. Or, click a group name to enter thelower level group list, select the VPNs or groups to be audited, and click Audit.

You can view the real-time audit results in the topology or view the audit results in the VPN list aftera short period of time.

VPN managementMPLS VPN Management can manage each MPLS VPN, including the Service Communities (SCs),Service Accesses (SAs), PE devices, CE devices, and service topology link for the VPN. An SC,the basic unit of a VPN, defines the VPN networking type (Full_Mesh or Hub_Spoke) and routetargets (import RT and export RT). When multiple SCs share the same sites, the SCs can be combinedto a VPN. An SA defines a link between a PE and a CE and indicates that a CE site is connectedto the VPN. A service topology link defines the connectivity between a CE and another CE.VPN management enables you to view, add, modify, and delete an MPLS VPN. You can manuallyadd an MPLS VPN or automatically discover existing VPNs on the network. Then, you can displaythe access topology and service topology for the VPN. VPN management also supports auditingthe configuration and connectivity for a VPN. The configuration audit discovers the configurationchange of a device, and the connectivity audit discovers the connectivity change of a link.

Figure 22 VPN management operation process

Viewing the BGP/MPLS VPN list1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > VPN management.

The BGP/MPLS VPN List page displays all VPNs.BGP/MPLS VPN List contents

• Status—Alarm state for a VPN, which is the highest level alarm state for the CE and PEdevices that belong to the VPN. Options are All, Unmanaged, Unknown, Normal,Warning, Minor, Major, and Critical.

• VPN Name—Name of a VPN. Click the name link of a VPN to view its details.

• Access Topology—Provides a link to access the VPN access topology.

• Service Topology—Provides a link to access the VPN service topology.

• Audit Status—Latest audit state for VPN connectivity. Options are All, Initial status, Auditis running, and Audit completed.

• Audit Time—Time when the VPN connectivity was last audited.

• Audit Result—Result of the last VPN connectivity audit. Options are All, Normal, Abnormal,and Unknown. When the result is normal, click the Normal icon to enter the VPN AuditDetails page. When the result is abnormal or unknown, a number link is displayed next


to the status icon. The number in the link indicates how many links are failed. Click thenumber link to enter the VPN Audit Details page.

• Modify—Click the Modify icon to modify a VPN.3. Click Refresh on top of the BGP/MPLS VPN List area to view the latest BGP/MPLS VPN List.

Querying a BGP/MPLS VPN1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > VPN management.

The BGP/MPLS VPN List page displays all VPNs.3. Enter or select one or more of the following query criteria to search for BGP/MPLS VPNs.

• VPN Name—Enter a VPN name. MPLS VPN Management supports fuzzy matching forthis field.

• Audit Status—Select an audit state from the list. Options are All, Initial status, Audit isrunning, and Audit completed.

• Status—Select an alarm state from the list. Options are All, Critical, Major, Minor, Normal,Warning, Unknown, and Unmanaged.

• Audit Result—Select an audit result from the list. Options are All, Normal, Abnormal, andUnknown.

4. Click Query.The BGP/MPLS VPN List displays all VPNs matching the query criteria.

5. Click Reset to clear the query criteria and display all VPNs.

Adding a VPN1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > VPN management.

The BGP/MPLS VPN List page displays all VPNs.3. Click Add on top of the BGP/MPLS VPN List area.

The Add VPN dialog box appears.4. Configure the following parameters as needed:

• VPN Name—Enter a VPN name, which must be unique in MPLS VPN Management.

• Connectivity Audit—Set whether to enable connectivity audit. You can select Periodicalaudit, and then modify the audit interval and set whether to enable Audit Inter-SpokeUnconnectivity. Or, you can directly choose Not Audit.

• Description—Enter the descriptive information for the VPN.5. Click OK.

Modifying a VPN1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > VPN management.

The BGP/MPLS VPN List page displays all VPNs.3. Click the link in the Modify field for the VPN to be modified.

The Modify VPN dialog box appears.


4. Modify the following parameters as needed:• VPN Name—Enter a VPN name, which must be unique in MPLS VPN Management.

• Connectivity Audit—Set whether to enable connectivity audit. You can select Periodicalaudit, and then modify the audit interval and set whether to enable Audit Inter-SpokeUnconnectivity. Or, you can directly choose Not Audit.

• Description—Enter the descriptive information for the VPN.5. Click OK.

Removing VPNs1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > VPN management.

The BGP/MPLS VPN List page displays all VPNs.3. Select the VPNs to be removed.4. Click Remove on top of the BGP/MPLS VPN List area.

A confirmation dialog box appears.5. Click OK.

Auditing VPNs1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > VPN management.

The BGP/MPLS VPN List page displays all VPNs.3. Select the VPNs to be audited.4. Click Audit on top of the BGP/MPLS VPN List area.5. You can view the audit results in the topology, the VPN list, or the operation log after the audit

is finished.

Modifying audit intervals1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > VPN management.

The BGP/MPLS VPN List page displays all VPNs.3. Select one ore multiple VPNs whose audit intervals need to be modified.4. Click Modify Audit Interval on top of the BGP/MPLS VPN List area.

The Modify Audit Interval dialog box appears.5. Set whether to enable Connectivity Audit. Options are Periodical audit and Not Audit. If

Periodical audit is set, you can modify the audit interval and set whether to enable AuditInter-Spoke Unconnectivity. The value range for the audit interval is 2 to 168 hours, and thedefault is 8 hours.

6. Click OK.

Editing VPN detailsPerform this task to display detailed information about an MPLS VPN, including SAs, SCs, PEs,CEs, and links.To edit a VPN:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > VPN management.

The BGP/MPLS VPN List page displays all VPNs.


3. Click the name link of a VPN to enter the VPN details page. The page consists of four areas,topology and audit information links, VPN basic information, VPN components, and recent10 unrecovered alarms.Area 1: Topology and audit information linksThis area provides the operation links for viewing the access topology, service topology, andaudit information.

• To view the access topology, click the Access Topology link on the upper right of thepage. For information about the access topology, see "Global topology."

• To view the service topology, click the Service Topology link on the upper right of thepage. For information about the service topology, see "Global topology."

• To view the audit information, click the Audit information link on the upper right of thepage. For information about the audit information, see "Viewing VPN connectivity auditinformation" and "Troubleshooting."

Area 2: VPN basic information

• VPN Name—Name of the VPN.

• Audit Period—If you have set an audit period, this field displays the VPN audit period inhours. If the audit period is not set, this field displays Not audit.

• Abnormal Links—Number of abnormal links.

• Description—Description of the VPN.

• Audit Inter-Spoke Unconnectivity—This field is displayed when the audit period isconfigured. Yes indicates that inter-spoke unconnectivity is audited. No indicates thatinter-spoke unconnectivity is not audited.

• Last Audit Time—Time when the last audit occurred, in the format YYYY-MM-DD hh:mm:ss.To modify VPN basic information, click Modify. The Modify VPN page appears. For moreinformation, see "Modifying a VPN."

Area 3: VPN componentsThis area consists of six tabs, SC List, PE List, CE List, SA List, Performance, and CE-CE Link.Click the link to view the corresponding list.

• SC listThe SC List tab is used to view, add, modify, and delete an SC.SC List contents

◦ SC Name—Name of the SC.

◦ SC Networking Type—Network type of the SC, Hub-Spoke and Full-Mesh.

◦ HUB's Import RT—Import RT value of the hub.

◦ HUB's Export RT—Export RT value of the hub.

◦ Modify—Click the Modify icon for the SC to be modified. When you modify anSC, you cannot modify SC Networking Type, HUB's Import RT, and HUB's ExportRT.

To add an SC, click Add on top of the list. On the page that appears, configure theparameters as needed and click OK.To remove an SC or SCs, select one or multiple SCs and click Remove on top of the list.

• PE listThe PE List tab is used to view, synchronize, and delete PE devices.


PE List contents

◦ Status—Alarm state of the device, Critical, Major, Minor, Warning, Normal, Unknown,or Unmanaged.

◦ Device Name—Name of the device. Click the name link to enter the device detailspage.

◦ PE Type—Type of the PE device, PE, SPE, UPE, or MPE.

◦ AS Number—Number of the AS to which the PE device belongs.

◦ Region—Name of the region where the PE device resides.

◦ Device IP/Mask—IP address and mask of the device.

◦ Last Synchronization Time—Time when the last synchronization occurred.

◦ Synchronization Status—State of the last synchronization, Synchronizing, Success,or Failure. Click the Failed link to view the failure reasons.

To synchronize a PE or PEs, select one or multiple devices to be synchronized and clickSynchronize. When the synchronization fails, click the Failed link to view the failurereasons.To delete a PE or PEs, select one or multiple devices to be deleted, and click Remove.To refresh the list, click Refresh to view the latest PE List.

• CE listThe CE List tab is used to view, synchronize, and delete CE devices.CE List contents

◦ Status—Alarm state of the device, Critical, Major, Minor, Warning, Normal, Unknown,or Unmanaged.

◦ Device Name—Name of the device. Click the name link to enter the device detailspage.

◦ CE Type—Type of the CE device, CE, VMCE, or MCE.

◦ Device IP—IP address of the device.

◦ Mask—Mask of the device.

◦ Last Synchronization Time—Time when the last synchronization occurred.

◦ Synchronization Status—Last synchronization state, Synchronizing, Success, or Failure.Click the Failed link to view the failure reasons.

To synchronize a CE or CEs, select one or multiple devices to be synchronized and clickSynchronize. When the synchronization fails, click the Failed link to view the failurereasons.To delete a CE or CEs, select one or multiple devices to be deleted, and click Remove.To refresh the list, click Refresh to view the latest CE List.


• SA listThe SA List tab is used to view, add, deploy, undeploy, and delete SA links.SA List contents

◦ SA Name—Name of the SA.

◦ Attached VPN—Name of the VPN to which the SA belongs.

◦ Link Status—State of the link, Normal, Configuration changed, Configuration changes,Link invalid, Undeployed, Deploying, Deployment failure, or Undeployment failure.

◦ PE Name—Name of the PE device. You can click the name link of the PE to view itsdetails.

◦ CE Name—Name of the CE device. You can click the name link of the CE to viewits details.

To add an SA, click Add. For more information, see "Adding/Modifying an SA."To remove an SA or SAs, select one or multiple SAs, click Remove.To deploy an SA or SAs, select one or multiple SAs, click Deploy.To undeploy an SA or SAs, select one or multiple SAs, click Undeploy.


• PerformanceThe Performance tab consists of two graphs for the incoming traffic report and the outgoingtraffic report, and supports exporting the reports. The incoming traffic report displays thefollowings:Graph type switch buttonsOn the upper left of the graph are the Table, Line Chart, Bar Chart, and Sampling Pointbuttons. Click the buttons to view the report in different charts. The default setting isdisplaying data in a line chart.Export report linksClick the Export as Excel link on the upper right of the graph to export the report to theexcel format. (You can also click the Export as PDF, Export as HTML, or Export as TXTlink to export the report to the corresponding format.) The Download Traffic Report windowprompts. Click the Traffic Report link and select a save path. After the report is saved,click Close in the Download Traffic Report window to return to the Performance tab.Incoming traffic graphThe x coordinate in the line chart represents the time and the y coordinate represents thetraffic. The report shows the trend of the incoming traffic for the MPLS VPN.Incoming traffic list contents

◦ Monitored Object—Name of the VPN that is monitored.

◦ Min. Value—Minimum value of the monitored traffic.

◦ Max. Value—Maximum value of the monitored traffic.

◦ Current Value—Current value of the monitored traffic.

◦ Average Value—Average value of the monitored traffic.

◦ Min. Value at—Time when the minimum value of the monitored traffic appears.

◦ Max. Value at—Time when the maximum value of the monitored traffic appears.

◦ Valid Sampling Point—Number of the monitored valid sampling points.

The function and format of the outgoing traffic report are the same as those of the incomingtraffic report. Details are not shown.


• CE-CE linkCE-CE Link contents

◦ Attached SC of the link—SC to which the CE-CE link belongs.

◦ Local CE—Name and IP address of the local CE.

◦ Opposite CE—Name and IP address of the remote CE.

To add a CE-CE link to the service topology:1. Click Add on top of the CE-CE list. The Add Topology Link page appears.2. For the Left Node field, click Select. The Select CE window appears. Select a CE

device and click OK to return to the Add Topology Link page.3. For the SC field, click Select. The Select SC window appears. Enter the SC name in

the SC Name field and click Query. Select an SC in the SC List and click OK to returnto the Add Topology Link page.

4. Click Add on top of the Right Node List area. The Select CE window appears. Selectthe CE name in the CE Name field and click Query. Select one or multiple CE devicesin the CE List and click OK to return to the Add Topology Link page. Repeat this stepto add multiple right nodes.

5. Click OK.To remove a CE-CE link or links, select one or multiple links and click Remove.

Area 4: Recent 10 unrecovered alarmsThis area is always displayed no matter which tab you click.Recent 10 unrecovered alarms contents

• Severity—Alarm level, Critical, Major, Minor, Warning, or Info.

• Source—Device that sends an alarm message.

• Alarm Information—Detailed information about the alarm.

• Alert Time—Time when the alarm occurred.

• Device Role—Role of the device that sends the alarm message, P, NPE, SPE, UPE, MPE,VPE, CE, VMCE, or MCE.

To view all alarms, click the All Alarms link on the upper right of the area. For informationabout the all alarms function, see HP IMC Base Platform Administrator Guide.

Viewing VPN connectivity audit informationMPLS VPN Management supports auditing VPN connectivity and auditing the inter-spokeunconnectivity for a VPN if the VPN networking type is Hub-Spoke.To view VPN connectivity audit information:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > VPN management.

The BGP/MPLS VPN List page displays all VPNs.3. Click the name link of a VPN to enter the VPN details page.4. Click the Audit Information link on the upper right of the page. The VPN Audit Details page

appears.5. The VPN Link Audit Information list and the Inter-Spoke Unconnectivity Audit Information list

display detailed information about the VPN audit. If you have disabled Audit Inter-SpokeUnconnectivity when adding the VPN, this page does not display the Inter-Spoke UnconnectivityAudit Information list.


6. Enable Display All Links on the upper right of the lists. The two lists display all links with theconnectivity state being Normal, Unknown, or Disconnected. If you do not enable Display AllLinks, the two lists only display links with the connectivity state being Unknown or Disconnected.VPN Link Audit Information contents

• Audit Result—Result of the last connectivity audit, Normal, Abnormal, or Unknown.

• Connectivity Status—Connectivity state of the link, Connected, Disconnected, or Unknown.

• Attached SC of the link—SC to which the link belongs.

• Local CE—Name and IP address of the local CE.

• Opposite CE—Name and IP address of the remote CE.

• Audit Status—Audit state for the link, Initial Status, Audit Completed, or Audit is running.

• Last Audit Time—Time when the last audit occurred.

• Troubleshooting—Click the Troubleshooting icon in this field for the disconnected linkto enter the Troubleshooting page. For information about troubleshooting, see"Troubleshooting."To audit a link, select the link to be audited and click Audit.Inter-Spoke Unconnectivity Audit Information contents

• Audit Result—Result of the last connectivity audit, Normal, Abnormal, or Unknown.

• Connectivity Status—Connectivity state of the link, Connected, Disconnected, or Unknown.

• Attached SC of the link—SC to which the link belongs.

• Local CE—Name and IP address of the local CE.

• Opposite CE—Name and IP address of the remote CE.

• Audit Status—Audit state for the link, Initial Status, Audit Completed, or Audit is running.

• Last Audit Time—Time when the last audit occurred.7. Click the VPN Details link on the upper right of the page to return to the VPN details page.

TroubleshootingPerform this task to automatically find the faults and causes for disconnected links discovered byconnectivity audit.This function is supported on H3C Comware V3 devices, Huawei devices, and some Cisco devices,and it is applicable only when OSPF is used between a PE and a CE.To do troubleshooting:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > VPN management.

The BGP/MPLS VPN List page displays all VPNs.3. Click the name link of a VPN to enter the VPN details page.

4. Click the Troubleshooting icon for a disconnected link in the VPN Link Audit Informationlist.

5. The Troubleshooting List displays the operation and result for troubleshooting.Troubleshooting List contents

• Time—Time when the troubleshooting began.

• Source—Source device for the troubleshooting.


• Destination—Destination device for the troubleshooting.

• Result—Result of the troubleshooting, which provides troubleshooting recommendations.6. Click Back to return to the VPN Audit Details page.

SA managementThis function manages the link between a CE and a PE. You can use this function to add, modify,remove, deploy, and undeploy an SA.

Figure 23 SA management operation process

1. Add an SA when a customer site is connected to a VPN.2. Deploy the newly added SA to the PE and CE devices.3. View detailed information and configuration changes for the SA, and modify the SA, as

needed.4. Undeploy the SA when the customer site is not used any more.5. Remove one or multiple SAs from MPLS VPN Management.

Viewing the SA list1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > SA management.

The SA List page displays all SAs.SA List contents

• SA Name—Name of the SA, in the format of PE device name (PE device's IP address)-CEdevice name (CE device's IP address).

• Attached VPN—VPN to which the SA belongs.

• Link Status—State of the link, Normal, Configuration changed, Configuration changes,Link invalid, Undeployed, Deploying, Deployment failure, or Undeployment failure.

• PE Name—Name of the PE device. You can click the name link of the PE to view its details.

• CE Name—Name of the CE device. You can click the name link of the CE to view itsdetails.

• Operation—Provides the following operation links:

◦ Click the Details icon to view detailed SA information.

◦ Click the Modify icon to modify an SA.

◦ Click the Change icon to view the change of the SA configuration.

3. Click Refresh to view the latest SA List.


Querying SAs1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > SA management.

The SA List page displays all SAs.3. Enter or select one or more of the following query criteria:

• Query Type—Select one query type from All, SA Name, Attached VPN, and Link Status.

• Query Condition—Enter information about the selected query type in the query criteriafield.

4. Click Query.The SA List displays all SAs matching the query criteria.

5. Click Reset to clear the query criteria and display all SAs.

Adding/Modifying an SAHP recommends that you perform auto discovery to make sure the link is not deployed in thenetwork before deploying a link. Before you perform auto discovery, synchronize devices to makesure you obtain the most recent configuration of the devices.To add/modify an SA:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > SA management.

The SA List page displays all SAs.

3. Click Add on top of the SA List area. Or, click the Modify icon in the Operation filed forthe SA to be modified.

4. Select a PE for the SA:a. Click Select PE on the Select PE and VPN page. The Select Devices page appears. There

are two methods for selecting devices, By View or using the Advanced option. See "Addingdevices by view" and "Adding devices by advanced query."

b. Highlight the devices you want to select and do one of the following:




• To remove all of the selected devices, click Remove all .c. Confirm that the devices you have found have been added.d. Click OK to return to the Select PE and VPN page.

5. Select a VPN for the SA:a. Click Select VPN on the Select PE and VPN page.

The Select VPN page appears.b. Enter the VPN name and click Query.c. Select a VPN from the list.d. Click OK to return to the Select PE and VPN page.

6. Click Next.


7. Select an SC for the SA and the join type for the PE device to connect to the VPN.The page consists of two lists, SC of Current VPN and Selected SC.SC of Current VPN contents

• SC Name—Name of the SC.

• Networking Type—Networking type of the SC, Hub-Spoke or Full-Mesh.

• HUB's Import RT—Import RT value of the hub.

• HUB's Export RT—Export RT value of the hub.Selected SC contents


• Join Type—Join type for the SC, Hub or Spoke.

• Networking Type—Networking type of the SC, Hub-Spoke or Full-Mesh.


• HUB's Export RT—Export RT value of the hub.To select an SC:a. Select one or multiple SCs in the SC of Current VPN list.b. Select a handling method, Add by HUB, Add by Spoke, or Release SC. The selected SC

is added to the Selected SC list.c. Click Next.

8. Configure the PE and CE:a. To configure the PE:

i. Select an interface from the Interface Description list.ii. Enter the interface's IP address and subnet mask in the Interface IP/Mask field.

b. (Optional.) Configure a non-managed CE manually or automatically. MPLS VPNManagement supports virtual CEs (VCEs) to represent CEs that cannot be managed.To automatically configure a non-managed CE, enable Create Non-managed CEautomatically. The system automatically creates a non-managed CE for the link that noCE is connected to.To manually configure a non-managed CE, click the Add Non-Managed CE link on theupper right of the page. The Add Non-Managed CE page appears.i. Enter the device name in the Device Name field.ii. Select the CE type from the Type list. Options are CE and VMCE.iii. Click Add on the upper right of the interface configuration page. Enter the interface

description, and interface IP address and mask in the dialog box that appears. ClickOK to return to the Add Non-Managed CE page.

iv. Click OK to return to the Interface Configuration page.c. To configure the CE:

i. Select a CE from the Device Name list. The CE can be a manageable CE or thecreated non-managed CE.

ii. Select an interface from the Interface Description list.iii. Enable Auto filter interface. The Interface Description list displays only the interfaces

of the CE that is in the same subnet as the PE.iv. Enable Filter out interface without IP address. The Interface Description list displays

only the interfaces that have IP addresses.v. Enter the IP address and subnet mask for the selected interface in the Interface IP/Mask

field.


d. Click Next.9. Configure the VRF information:

a. The system automatically generates a default VRF name in the VRF Name field. You canchange the VRF name. To restore the default VRF name, click the Restore Default link.

b. The system automatically generates a default RD value in the RD Value field. You canchange the value.

c. The system uses the VRF in the Existing VRF list as the newly deployed VRF.d. The Configure route filed appears when the selected CE is a manageable CE. You can

configure a static route or the OSPF routing protocol in this field. Enable Configure routeand click Next to go to step 10. Disable configure route and click Next to step 11.

e. Click Next.10. Configure the route between the PE and the CE:

a. Select a routing protocol. Options are Static and OSPF.b. Configure the PE.

i. Enter the destination IP and mask in the Destination IP/Mask field.ii. Click Add. Repeat the steps to add multiple routes.

c. Configure the CE.i. Enter the destination IP and mask in the Destination IP/Mask field.ii. Click Add. Repeat the steps to add multiple routes.

d. Click Next.The Summary page consists of the Basic Information, Configuration command, and DeployImmediately areas. The Basic Information and Configuration command areas help you verifythe configuration before you execute the configuration commands.The Basic Information area displays the names of the PE device and the CE device. If youconfigure a route between the PE and the CE, this area also displays the route type.The Configuration command area displays the configuration commands to be executed onthe PE and the CE.

11. If you enable Deploy Immediately, the configuration is deployed immediately onto the devices.Return to the SA List page, and an SA with the link state being Deploying appears. If youdisable Deploy Immediately, click OK to return to the SA List page. An SA with the link statebeing Undeployed appears. You need to manually deploy it.

12. Click OK.

Removing SAs1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > SA management.

The SA List page displays all SAs.3. Select the SAs to be removed.4. Click Remove.


Deploying SAs1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > SA management.

The SA List page displays all SAs.3. Select the SAs to be deployed.


4. Click Deploy.5. Click OK.

The Deployment Status field displays the deployment result. The link indicates a deploymentfailure. Click the link to view which commands are failed to be executed.

Undeploying SAs1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > SA management.

The SA List page displays all SAs.3. Select one or multiple SAs to be undeployed.4. Click Undeploy.


Management VPNAfter a management VPN is configured, the system automatically filters the RT attributes of themanagement VPN when the system performs auto discovery and adds an SA.

Configuring a management VPNPerform this task to configure the SC information for a management VPN.To configure a management VPN:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Management VPN.

The Management VPN Configuration page appears.3. Configure the following parameters:

• Status—Select whether to enable management VPN filtering. Options are Enabled andDisabled. If you enable filtering management VPNs, configure the hub's import RT andexport RT. If you disable filtering management VPNs, go to step 4.

• HUB's Import RT—Enter the import RT value for the management VPN.

• HUB's Export RT—Enter the export RT value for the management VPN.4. Click OK.

VPN devicesThis function manages PE and CE devices. You can synchronize, view, and query the devices. Inaddition, you can switch regions for a PE device, and manages manageable CEs and non-managedCEs.

VPN device general viewMPLS VPN Management provides the general view of the statistics about devices counted by devicetype and alarm level.To enter the VPN device general view page:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Devices.

The VPN Device General View displays the VPN device charts.


Figure 24 VPN devices

You can view the statistics of all devices and failures on this page.

• The device type pie charts show the number of PEs, SPEs, UPEs, MPEs, CEs, MCEs, andVMCEs.

• The device view chart shows the device type by number in descending order and the numberof devices that belong to each type.

• The PE device alarm pie chart shows the number of the PE devices in each alarm state.

• The CE device alarm pie chart shows the number of the CE devices in each alarm state.You can click a chart to enter the device list and manage the devices in the list.

PE device listUse this function to query, synchronize, switch, remove a PE device, and view the VPN informationfor the device.

NOTE: The initial PE device list is blank. Before you view and manage PE devices, use the regionmanagement function to import PE devices to MPLS VPN Management.

Viewing the PE device list1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Devices > PE Device List.

The PE Device List page displays all PE devices.PE Device List contents

• Status—Alarm state of the device, Critical, Major, Minor, Warning, Normal, Unknown,or Unmanaged.

• Device Name—Name of the device. Click the name link of the device to view its details.

• PE Type—Type of the PE device, PE, SPE, UPE, or MPE.

• AS Number—Number of the AS to which the PE device belongs.

• Region—Name of the region.

• Device IP/Mask—Management IP and mask of the PE device.

VPN devices 57

• Last Synchronization Time—Time when the last synchronization occurred.

• Synchronization Status—Synchronization state of the PE device, Synchronizing, Success,or Failure.

• View—Click the View icon to view the SA information and alarm information for thedevice in the PE VPN Information page.

3. Click Refresh to view the latest PE Device List.

Querying PE devices1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Devices > PE Device List.

The PE Device List page displays all PE devices.3. Enter or select one or more of the following query criteria:

• Device Name—Enter a PE name. MPLS VPN Management supports fuzzy matching forthis field.

• Status—Select the alarm state of the PEs to be queried. Options are All, Critical, Major,Minor, Warning, Normal, Unknown, and Unmanaged.

• Device IP—Enter the PE IP address. MPLS VPN Management supports fuzzy matching forthis field.

• PE Type—Select a PE type. Options are All, PE, SPE, UPE, and MPE.4. Click Query.

The PE Device List displays all PE devices matching the query criteria.5. Click Reset to clear the query criteria and display all PE devices.

Synchronizing PE devices1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Devices > PE Device List.

The PE Device List page displays all PE devices.3. Select one or multiple devices to be synchronized and click Synchronize.4. The Synchronization Status field in the list displays the synchronization process of the devices.5. Click Refresh to view the latest synchronization result.

Switching PEs between regionsPerform this task to move PE devices from a region to another region in the same AS. P devicesdo not support this function.To switch PEs between regions:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Devices > PE Device List.

The PE Device List page displays all PE devices.3. Select one or multiple devices to be switched and click Switch.

The AS/Region window appears.4. Select a region.5. Click OK.

Removing PE devicesPerform this task to remove PE devices from MPLS VPN Management.


To remove PE devices:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Devices > PE Device List.

The PE Device List page displays all PE devices.3. Select one or multiple devices to be removed in the list and click Remove.


CE device listUse this function to query, synchronize, switch, and remove a CE device. You cannot synchronizea non-managed CE.

Viewing the CE device list1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Devices > CE Device List.

The CE Device List page displays all CE devices.CE Device List contents

• Status—Alarm state of the device, Critical, Major, Minor, Warning, Normal, Unknown,or Unmanaged.

• Device Name—Name of the device. Click the name link of the device to view its details.

• CE Type—Type of the CE device, CE, VMCE, or MCE.

• Device IP—IP address of the CE device.

• Mask—Mask of the CE device.

• Last Synchronization Time—Time when the last synchronization occurred.

• Synchronization Status—State of the last synchronization, Synchronizing, Success, orFailure. Click the Failed link, and a prompt that indicates the failure reasons appears.

• Modify—Click the Modify icon to modify a non-managed CE. This icon is notdisplayed for a manageable CE.

3. Click Refresh to view the latest CE Device List.

Querying CE devices1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Devices > CE Device List.

The CE Device List page displays all CE devices.3. Enter or select one or more of the following query criteria:

• Device Name—Enter the name of the CE. MPLS VPN Management supports fuzzy matchingfor this field.

• Status—Select the alarm state of the CEs to be queried. Options are All, Critical, Major,Minor, Warning, Normal, Unknown, and Unmanaged.

• Device IP—Enter the IP address of the CE. MPLS VPN Management supports fuzzy matchingfor this field.

• CE Type—Select the type of the CE. Options are All, CE, VMCE, and MCE.4. Click Query.

The CE Device List displays all CE devices matching the query criteria.

VPN devices 59

5. Click Reset to clear the query criteria and display all CE devices.

Importing CE devicesPerform this task to import CE devices to MPLS VPN Management. Before importing the devices,make sure the devices to be imported meet the following conditions:

• Enables with SNMP and are enabled with SNMP.


• Not imported as P or PE devices.To import CE devices:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > CE Device List.

The CE Device List page displays all CE devices.3. Click Import on top of the CE Device List area.

The Import Device page appears.4. Select the CE type from the box next to Please select CE type to be imported. Options are CE,

VMCE, and MCE.5. Click Select to select the CE devices to be imported.






• To remove all of the selected devices, click Remove all .7. Confirm that the devices you have found have been added.8. Click OK to enter the Import Device page.

The selected devices now appear in the page.9. Check the imported devices.




Adding/Modifying a non-managed CESome CE devices cannot be managed by IMC. Perform this task to create a virtual CE to representa non-managed CE in the MPLS VPN topology to keep the topology complete.To add/modify a non-managed CE:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Devices > CE Device List.

The CE Device List page displays all CE devices.


3. Click Add Non-Managed CE on the upper right of the CE Device List area to enter the Add

Non-Managed CE page. Or, click the Modify icon in the Operation filed for the CE to bemodified to enter the Modify Non-Managed CE page.

4. Enter the device name in the Device Name field.5. Select the CE type from the Type list. Options are CE and VMCE.

You cannot select the CE type when you enter the Modify Non-Managed CE page.6. Click Add in the Interface List area.

The Add Non-Managed CE Interface page appears.7. Perform the following configurations on the Add Non-Managed CE Interface page:

a. Enter the interface description in the Interface Description field.b. Enter the interface's IP address and mask in the Interface IP/Mask field.c. Click OK to return to the Add/Modify Non-Managed CE page.Repeat the steps to add multiple CE interfaces. To remove an interface or interfaces, selectone or multiple interfaces in the Interface List and click Remove. You cannot remove an interfacethat is already connected to the PE device.

8. Click OK to return to the CE Device List.

Synchronizing CE devices1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Devices > CE Device List.

The CE Device List page displays all CE devices.3. Select one or multiple devices to be synchronized and click Synchronize.4. The Synchronization Status field in the list displays the synchronization process of the devices.5. Click Refresh to view the latest synchronization result.

Removing CE devicesPerform this task to remove CE devices, including non-managed CEs, from MPLS VPN Management.To remove CE devices:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Devices > CE Device List.

The CE Device List page displays all CE devices.3. Select one or multiple devices to be removed in the list and click Remove.


Auto discoveryThe auto discovery function collects VPN information from devices, uses model calculation to obtainthe existing VPNs and links, and draws the topology. VPNs that are discovered automatically areadded to MPLS VPN Management. You can modify and delete them. Also, you can perform thelink deployment and removing, and traffic monitoring operations.To discover VPNs automatically:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Auto Discovery.

The auto discovery configuration guide page appears.

Auto discovery 61

3. Select PE devices:a. Configure auto discovery parameter settings:

i. Select the Remove all invalid links box.ii. Select the Synchronize PE device before auto discovery box.

b. Configure auto discovery range settings:i. Click Select PE.

The Select Devices dialog box appears.There are two methods for selecting devices, By View or using the Advanced option.See "Adding devices by view" and "Adding devices by advanced query."

ii. Highlight the devices you want to select and do one of the following:

—To add them to the Selected Devices list, click Add selected .

—To select all of the devices displayed in the Devices Found list, click Add all .

—To remove one or more, select them and click Remove selected .

—To remove all of the selected devices, click Remove all .iii. Confirm that the devices you have found have been added.iv. Click OK.

v. Click the Delete icon for the device to be removed from the device list.vi. Click Remove All for all devices to be removed from the device list.

c. Click Auto Discovery.4. Discover VPNs automatically.

A process bar for VPN auto discovery appears. When the auto discovery is finished, youdirectly enter the page for VPN selection.

5. Select the VPNs whose links are to be configured.a. View the VPN List Found.

VPN List Found contents

• Status—State of the VPN, Existing, New VPN, or Conflict. Existing indicates that anew link for the VPN is found. New VPN indicates that the VPN is new. Conflictindicates that the VPN has different SC information from that discovered last time.


• VPN Type—Type of the VPN. The value can be BGP/MPLS VPN.

• VPN Description—Description of the VPN.b. Select one or multiple VPNs in the VPN List Found.c. Click Next.

6. Configure VRF bindings.a. Enable Create Non-managed CE automatically. Then, the system automatically creates a

non-managed CE for a link without any CE device.b. View the New Link List.

New Link List contents

• Device Name—Name and IP address of the PE device.

• VRF Name—Name of the found VRF.

• Attached VPN of Link—Name of the VPN to which the link belongs.


• PE Interface—Name of the interface on the PE device.

• MCE Name—Name of the MCE. This field is blank for a non-MCE network.

• CE Name—Name of the CE device.

• Configure—Click the Configure icon to enter the page for configuring a link. Formore information, see step 7.

c. Select one or multiple links to be added to MPLS VPN Management.d. Click Finish.

A confirmation dialog box appears.e. Click OK.

The Summary page appears.

7. Configure a link.You can use this step to configure the CE devices for the new link. The configuration waysvary with the network types.a. Method 1: Add a non-managed CE manually.

i. Click the Add Non-Managed CE link on the upper right of the Configure Link page.The Add Non-Managed CE page appears.

ii. Enter the name of the CE device in the Device Name field.iii. Select the type of the CE device from the Type list. Options are CE and VMCE.iv. Click Add on the top of the Interface List area. The Add Interface page appears.v. Enter the interface description in the Interface Description field.vi. Enter the IP address and mask of the interface in the Interface IP/Mask field.vii. Click OK to return to the Add Non-Managed CE page.

b. Method 2: Add a VMCE.i. Click the Add VMCE Configuration link on the upper right of the Configure Link page.

The VMCE Configuration section appears.ii. Select a VMCE device from the Device Name list.iii. Select the interface that connects to the PE device from the Interface connected to

upper device list.iv. Select the interface that connects to the CE device from the Interface connected to

down device list.

v. Click the Add icon below Interface connected to down device to add a VMCE.Click the Delete icon to delete a VMCE.

c. Configure a CE:i. Select a CE device from the Device Name list. The Device Name lists the existing CEs

in the system and the non-managed CEs that you added to MPLS VPN Management.ii. Select an interface from the Interface Description list.

There are two filtering rules below Interface Description: Automatically Filter Interfaceand Filter Interface without IP Address. If you enable Automatically Filter Interface,the Interface Description lists only the CE's interfaces that are in the same subnet asthe PE's interfaces. If you enable Filter Interface without IP Address, the InterfaceDescription lists only interfaces that have IP addresses.

iii. Enter the interface's IP address and mask in the Interface/Mask field.

Auto discovery 63

8. Click OK to return to the VRF Binding Relationship Configuration page.The Configured VPN Link Result displays the VPN link configuration results.Configured VPN Link Result contents

• Device Name—Name of the PE device.

• VRF Name—Name of the VRF.

• PE Interface—Name of the PE device's interface that connects to the VPN link.

• MCE Interface—Name of the MCE. This field is blank for a non-MCE network.


• Result—Result of the VPN link configuration, Success or Failure.

Global topologyMPLS VPN Management provides the global topology for the entire MPLS VPN, and the accesstopology and service topology for each VPN. An access topology shows the connections betweenPEs and CEs, and a service topology shows the connections between CEs for an MPLS VPN.Through MPLS VPN Management, you not only can view the connections in an MPLS VPN, butalso can perform some visible operations, such as connectivity detection, highlighting an MPLSVPN, and service deployment.

Entering global topologyGlobal topology shows the entire MPLS VPN, including the connection state of CEs, PEs, ASs,regions, and subregions.To enter the VPN global topology page:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Global Topology.

The VPN Global Topology page appears.

Entering access topologyYou can view the VPN information for a PE, test the connectivity, and remove a PE and a CE froma VPN. MPLS VPN Management provides you multiple methods to enter the access topology.Method 1: From the global topology1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Global Topology.

The VPN Global Topology page appears.3. From the navigation tree on the page, select MPLS VPN > VPNFullMesh > Access Topology.

Double-click the access topology node below an MPLS VPN.Method 2: From the BGP/MPLS VPN list1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > VPN management.

The BGP/MPLS VPN List page displays all VPNs.3. Click the Access Topology link for a VPN.Method 3: From the VPN details page1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > VPN management.

The BGP/MPLS VPN List page displays all VPNs.3. Click the name link of a VPN to enter the VPN details page.


4. Click the Access Topology link on the upper right of the page.

Entering service topologyYou can remove a CE from a VPN and test the connectivity. MPLS VPN Management provides youmultiple methods to enter the service topology.Method 1: From the global topology1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Global Topology.

The VPN Global Topology page appears.3. From the navigation tree on the page, select MPLS VPN > VPNFullMesh > Service Topology.

Double-click the service topology node below an MPLS VPN.Method 2: From the BGP/MPLS VPN list1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > VPN management.

The BGP/MPLS VPN List page displays all VPNs.3. Click the Service Topology link for a VPN.Method 3: From the VPN details page1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > VPN management.

The BGP/MPLS VPN List page displays all VPNs.3. Click the name link of a VPN to enter the VPN details page.4. Click the Service Topology link on the upper right of the page.

Topology operationsTable 1 shows the operations that you can perform for MPLS VPN on the topologies. For informationabout other operations that can be performed on the topologies, see HP IMC Base PlatformAdministrator Guide.

Table 1 Support for MPLS VPN operations on topologies

Service topologyAccess topologyGlobal topologyOperations

NoYesYesView device VPN information

NoYesYesView VPN link information

NoNoYesHighlight/Cancel highlight a VPN

NoNoYesAuto discovery

NoNoYesDeploy a service

NoNoYesDeploy all links

NoNoYesRemove deployment configurations

YesYesYesRemove a device from a VPN

YesYesYesTest VPN connectivity betweendevices

YesNoNoAudit link connectivity

YesNoNoQuery connectivity information

YesNoNoTroubleshoot

Global topology 65

Table 1 Support for MPLS VPN operations on topologies (continued)

Service topologyAccess topologyGlobal topologyOperations

YesNoNoAudit all VPN connectivity

YesYesNoAnalyze MPLS VPN traffic

Viewing device VPN informationPerform this task to go to the device VPN information page from the VPN global topology page,and to view detailed VPN information for a device. This function is available on the global topologyand an access topology. Take the global topology for example:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Global Topology.

The VPN Global Topology page appears.3. Right-click a PE device and select Device VPN Information from the shortcut menu.

The PE VPN Information page appears.4. The page consists of the Found SA List area and the Recent 10 unrecovered alarms area.

Found SA List contents

• VRF—VRF information, including VPN instance name, RD, import RTs, and export RTs.

• Bound Interface—Name and IP address of the interface that is bound with the VRF.

• Connected MCE—Name and IP address of the MCE that connects to the VRF.

• Connected CE—Name and IP address of the CE that connects to the VRF.

• Configure Audit Status—Last audit configuration result. Options are Link invalid,Configuration unchanged, and Configuration changed.

Recent 10 unrecovered alarms contents

• Severity—Alarm level, Critical, Major, Minor, Warning, or Info.

• Alarm Information—Detailed information about the alarm.

• Alert Time—Time when the alarm occurred.

Viewing VPN link informationPerform this task to view detailed information about a link in the global topology or an accesstopology. Take a global topology for example:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Global Topology.

The VPN Global Topology page appears.3. Right-click a link and select VPN Link Information from the shortcut menu.

The VPN Link Details page appears.


4. The tabs displayed on the page vary with the link types.For a link between a PE and an MPLS network, the VPN Link Details page displays only theLink Information tab that consists of the CORE area and the PE end area.The CORE area displays information about the core.PE end area contents

• Device Name—From left to right, this filed displays the alarm status, device name, anddevice IP address.

• Interface Description—Description of the interface that connects to the core.

• Interface IP/Mask—IP address and mask of the interface that connects to the core.For a link between a CE and a PE, the VPN Link Details page displays the Link Informationtab, the Attached VPN tab, and the SC List tab.The Link Information tab consists of the PE end area and the CE end area.PE end area contents


• Interface Description—Description of the interface that connects to the CE.

• Interface IP/Mask—IP address and mask of the interface that connects to the CE.CE end area contents


• Interface Description—Description of the interface that connects to the PE.

• Interface IP/Mask—IP address and mask of the interface that connects to the PE.The Attached VPN tab displays VRF information, including the following contents:

• VRF Name—Name of the VRF.

• RD Value—Value of the RD.

• VPN Name—Name of the VPN to which the VRF belongs.

• VPN Type—Type of the VPN to which the VRF belongs, for example, BGP/MPLS VPN.The SC List tab displays SC information, including the following contents:


• SC Networking Type—Networking type of the SC, full-mesh and hub-spoke.


• HUB's Export RT—Export RT value of the hub.

• Description—Description of the SC.

Highlighting/Canceling highlight a VPNPerform this task to highlight an MPLS VPN on the global topology so that you can quickly locatethe MPLS VPN that you search for.To highlight or cancel highlight a VPN:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Global Topology.


Global topology 67

3. Click a CE device and click the Highlight Vpn icon in the tool bar on top of the topology.Devices and links that belong to the VPN are highlighted. Others are grayed.

4. Click the Cancel Highlight icon to cancel highlighting the VPN.

Deploying a servicePerform this task to deploy an SA for a PE device on the global topology.To deploy a service:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Global Topology.

The VPN Global Topology page appears.3. Right-click a PE device and select Service Deploy from the shortcut menu.

The Add SA page appears. For more information, see "Adding/Modifying an SA."

Deploying all linksPerform this task to deploy all links that are not deployed on the global topology. Undeployed linksare displayed as dotted lines on the topology. Deployed links are displayed as full lines.To deploy all links:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Global Topology.

The VPN Global Topology page appears.3. Right-click the blank and select Deploy All from the shortcut menu.

Deployment information is displayed in the log area below the topology.

Removing deployment configurationsPerform this task to remove an SA link from the global topology.To remove deployment configurations:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Global Topology.

The VPN Global Topology page appears.3. Right-click an SA link and select Remove Deployment Configuration from the shortcut menu.

The Remove Deployment page appears.4. Select a removal method. Options are Only remove VRF binding relationship and If the VRF

is used by only this interface, the VRF definition will be removed too (Suggest that synchronizedevices before carry out this process).

5. Click OK.You can view the SA list to verify that the SA link is removed.

Removing devices from a VPNPerform this task to remove one or multiple CEs or PEs from the global topology or a servicetopology. Take a global topology for example:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Global Topology.



3. Press the Ctrl key and click one or multiple PE or CE devices. Right-click a selected device andselect Remove from VPN from the shortcut menu.A confirmation dialog box appears.

4. Click OK.

Testing VPN connectivity between devicesPerform this task to test the VPN connectivity between CEs, and is available for a global topology,an access topology, and a service topology. Take a global topology for example.Before you perform this task, ensure the followings:

• The source device for the test must be a physical device that supports Telnet and pingoperations.

• The destination interface for the test must have an IP address.To test the connectivity between devices:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Global Topology.

The VPN Global Topology page appears.3. Press the Ctrl key and click two CE devices. Right-click a selected device and select P2P Ping

from the shortcut menu.The P2P Ping page appears.

4. Configure the following parameters:• Source—Verify the selected source device from the list.

• VPN Instance—Select a VPN instance to be tested from the list.

• Destination—Verify the interface of the destination device from the list.5. Click OK.

You can view the result of the P2P ping in the log area below the topology.

Adding link connectivityPerform this task to audit CE-CE link connectivity on a service topology.To audit the connectivity for a CE-CE link:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Global Topology.

The VPN Global Topology page appears.3. From the navigation tree on the page, select Topology > MPLS VPN. Select a VPN, and then

double-click Service Topology.The Service Topology page for the selected VPN appears.

4. Right-click a link and select Connectivity Audit from the shortcut menu.A message about the link connectivity audit is displayed in the log area below the topology.

5. Return to the Service tab.6. From the navigation tree, select MPLS VPN Manager > VPN Resources > VPN Management.In the VPN Management page, you can view the audit result in the Audit Result field of theBGP/MPLS VPN List area.

Querying connectivity informationPerform this task to query the connectivity information for the link between the specified CEs in aservice topology. MPLS VPN Management displays the connectivity information for the three-segment

Global topology 69

link with four points. The points are local end CE, local end PE, opposite end PE, and oppositeend CE from left to right.To query connectivity information1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Global Topology.

The VPN Global Topology page appears.3. In the page, from the navigation tree, select Topology > MPLS VPN. Select a VPN, and then


4. Right-click a link and select Query Connectivity Information from the shortcut menu.The Inter-CE Connectivity Audit page appears.

5. The page consists of the link status graph and the connectivity audit results.The link status graph displays the names of the devices, and marks the device status and link

status in different colors. For the description of an Legend, click the Illustration icon in thetool bar on top of the topology.The connectivity result list below the link status graph displays detailed information about thethree links.Connectivity result list contents

• Connectivity Result—Connectivity audit result, Connected or Disconnected.

• Source—Device name and IP address of the link source node.

• Destination—Device name and IP address of the link destination node.

• Audit Operation—Description of the audit operation. The format is Interface XXX of XXXpings interface XXX of XXX.

TroubleshootingPerform this task to troubleshoot a failed link in a service topology.To troubleshoot a link:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Global Topology.



4. Right-click a failed link (in red color) and select Troubleshooting from the shortcut menu.The Troubleshooting page appears.

5. MPLS VPN Management troubleshoots the link hop-by-hop, and the Troubleshooting pagedisplays the troubleshooting result in a list.Troubleshooting result list contents

• Time—Time when the troubleshooting began, in the format YYYY-MM-DD hh:mm:ss.

• Source Device—Source device for the troubleshooting.

• Destination Device—Destination device for the troubleshooting.

• Result—Result of the troubleshooting.


NOTE: This function is supported on H3C Comware V3 devices, some Huawei devices, andsome Cisco devices, and it is applicable only when OSPF is used between a PE and a CE.

Auto discoveryThis function performs auto discovery on a selected PE in the global topology.To discover VPNs automatically:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Global Topology.

The VPN Global Topology page appears.3. Right-click a PE and select Auto Discovery from the shortcut menu.

The auto discovery configuration guide page appears. For more information about theconfigurations, see "Auto discovery."

Auditing all VPN connectivityPerform this task to audit all VPN connectivity from a local end CE to a local end PE to an oppositeend PE to an opposite end CE. It is available for a service topology.To audit all VPN connectivity:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Global Topology.



4. Right-click the blank and select All VPN Connectivity Audit from the shortcut menu.A message about the VPN connectivity audit is displayed in the log area below the topology.

5. Return to the Service tab.6. From the navigation tree, select MPLS VPN Manager > VPN Resources > VPN Management.

In the VPN Management page, you can view the audit result in the Audit Result field of theBGP/MPLS VPN List area.

Analyzing MPLS VPN trafficMPLS VPN Management can cooperate with NTA to allow you to view traffic information on accessor service topologies.Before you perform this task, ensure the followings:

• NTA is installed and run in IMC.

• Create a VPN traffic analysis task for the VPN to be viewed. For more information, see HPIMC Network Traffic Analyzer Administrator Guide.

To analyze the traffic:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Global Topology.


double-click Access Topology or Service Topology for a VPN to enter the topology page.4. Right-click the blank and select Traffic Analysis from the shortcut menu.

The VPN Traffic Details page appears.

Global topology 71

5. The page consists of two lists and a description area.Inbound and outboundtraffic analysis list contents

• Direction—Direction of the traffic that are analyzed, Inbound Traffic or Outbound Traffic.

• Total Traffic—Total traffic for the VPN, in bytes.

• Maximum Rate—Maximum rate of the traffic, in bps.

• Minimum Rate—Minimum rate of the traffic, in bps.

• Average Rate—Average rate of the traffic, in bps.Application traffic analysis list contents

• Application—Application running on the VPN.

• Traffic—Traffic of the application.

• Inbound Traffic—Incoming traffic of the application.

• Outbound Traffic—Outgoing traffic of the application.

• Rate—Rate of the traffic.

• Percentage—Percentage of the application traffic to the traffic in the whole VPN.Traffic monitoring description area contents

• PEs not supporting flow monitoring—PE devices that do not support traffic monitoring inthe VPN.

• PEs not or partially monitored by NTA—PE devices not monitored or partially monitoredby NTA in the VPN.

You can also view the previous information by clicking a PE device in the service topology.

Alarm TopNThis function displays the top N VPNs, PE devices, and CE devices by alarm severity. You canview the MPLS VPN problems and alarm messages, and set the value of N.

Viewing alarm TopN information1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Alarm TopN.

The Alarm TopN page appears.


3. The page consists of four areas.Parameters areaYou can view and set the value of N in this area.a. Select 5, 10, 15, or 20 from the N for TopN list.b. Click OK.VPN Fault areaThis area displays the top N VPNs by alarm severity. You can view detailed information aboutthe VPNs.VPN Fault area contents

• Status—Alarm state of the VPN, Critical, Major, Minor, Normal, Warning, Unknown, orUnmanaged.

• VPN Name—Name of the VPN. You can click the name link of the VPN to enter the VPNdetails page for troubleshooting.

PE Fault areaThis area displays the top N PEs by alarm severity. You can view detailed information aboutthe alarm messages.PE Fault area contents

• Status—Alarm state of the PE, Critical, Major, Minor, Normal, Warning, Unknown, orUnmanaged.

• Device Name—Name of the PE. You can click the name link of the PE to enter the DeviceDetails page.

• PE Type—Type of the PE, PE, SPE, UPE, or MPE.

• View—Click the View icon to enter the All Alarms page. You can view all unrecoveredalarms for the PE. For information about the all alarms function, see HP IMC Base PlatformAdministrator Guide.

CE Fault areaThis area displays the top N CEs by alarm severity. You can view detailed information aboutthe alarm messages.CE Fault area contents

• Status—Alarm state of the CE, Critical, Major, Minor, Normal, Warning, Unknown, orUnmanaged.

• Device Name—Name of the CE. You can click the name link of the CE to enter the DeviceDetails page.

• CE Type—Type of the CE, CE, VMCE, or MCE.

• View—Click the View icon to enter the All Alarms page. You can view all unrecoveredalarms for the CE. For information about the all alarms function, see HP IMC Base PlatformAdministrator Guide.

Traffic monitorThis function provides monitoring information for the inbound traffic, outbound traffic, inboundbandwidth utilization, and outbound bandwidth utilization of VPNs and SAs.

Traffic general viewMPLS VPN Management traffic general view displays the VPN monitor chart, SA monitor chart,VPN traffic top 5 lists, and SA traffic top 5 lists.

Traffic monitor 73

To enter the traffic general view page:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Traffic Monitor.

The Traffic General View page appears.

Figure 25 Traffic general view

This page displays two kinds of monitoring information:

• VPN Monitor Information—MPLS VPN Management displays the number of monitored andunmonitored VPNs in a pie chart, and top 5 VPNs by inbound traffic and that by outboundtraffic.

• SA Monitor Information—MPLS VPN Management displays the number of monitored andunmonitored SAs in a pie chart, and top 5 SAs by inbound traffic and that by outbound traffic.

Figure 26 Traffic monitor operation process

Setting thresholdsThe system predefines four traffic alarm thresholds. They are thresholds of SA incoming traffic, SAoutgoing traffic, SA incoming bandwidth utilization, and SA outgoing bandwidth utilization. Youcan modify but cannot add or delete the thresholds.

Viewing default threshold list1. Click the Service tab.


2. From the navigation tree, select MPLS VPN Manager > Traffic Monitor > Threshold Setting.The Threshold Setting page appears.Default Threshold List contents

• Name—Name of the threshold.

• Level-1 Alarm Status—Whether the level-1 alarm for the threshold is Enabled or Disabled.

• Level-1 Alarm Threshold—If the level-1 alarm is enabled, this field displays the threshold.If the level-1 alarm is disabled, this field displays hyphens (--).

• Level-1 Alarm Severity—Critical, Major, Minor, Warning, or Info.

• Level-2 Alarm Status—Whether the level-2 alarm for the threshold is Enabled or Disabled.

• Level-2 Alarm Threshold—If the level-2 alarm is enabled, this field displays the threshold.If the level-2 alarm is disabled, this field displays hyphens (--).

• Level-2 Alarm Severity—Critical, Major, Minor, Warning, or Info.

• Modify—Click the Modify icon to enter the page for modifying the threshold.3. Click Refresh to view the latest Default Threshold List.

Modifying SA inbound/outbound traffic threshold1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Traffic Monitor > Threshold Setting.

The Threshold Setting page appears.

3. Click the Modify icon for SA Incoming Traffic (bytes/s) or that for SA Outgoing Traffic(bytes/s).The page for modifying the threshold appears.

4. Enable Enable level-1 alarm. Enter a value in bytes/s in the When the value is greater thanfield, and select an alarm severity from the list between Send and Alarm. Options for the alarmseverity include Critical, Major, Minor, Warning, and Info.

5. Enable Enable level-2 alarm. Enter a value in bytes/s in the When the value is greater thanfield, and select an alarm severity from the list between Send and Alarm. Options for the alarmseverity include Critical, Major, Minor, Warning, and Info.

6. Click OK.

Modifying SA inbound/outbound bandwidth utilization thresholds1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Traffic Monitor > Threshold Setting.

The Threshold Setting page appears.

3. Click the Modify icon for SA Incoming Bandwidth Utilization (bytes/s). Or, click the Modify

icon for SA Outgoing Bandwidth Utilization (bytes/s).The page for modifying the threshold appears.

4. Enable Enable level-1 alarm. Enter a value in % in the When the value is greater than field,and select an alarm severity from the list between Send and Alarm. Options for the alarmseverity include Critical, Major, Minor, Warning, and Info.

5. Enable Enable level-2 alarm. Enter a value in % in the When the value is greater than field,and select an alarm severity from the list between Send and Alarm. Options for the alarmseverity include Critical, Major, Minor, Warning, and Info.

Traffic monitor 75

6. Click OK.

Setting VPN traffic monitor

Viewing VPN traffic monitor settings1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Traffic Monitor > VPN Traffic Monitor

Setting.The VPN List page appears.VPN List contents

• VPN Name—Name of the manageable VPN.

• VPN Type—Type of the VPN. The value is BGP/MPLS VPN.

• Monitor Status—Monitor state of the VPN. Options are Monitored and Not Monitored.

• Monitored SA Ratio—Ratio of the monitored SAs to the total SAs in the VPN.

• Modify—Click the Modify icon to enter the VPN information page. You can viewthe SA information and alarm information in the page.

Querying VPNs1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Traffic Monitor > VPN Traffic Monitor

Setting.The VPN List page appears.

3. In the VPN Query area, select a query type from the Query Type list. Options are All, VPNName, and Monitor Status.

4. Enter the query criterion in the Query Condition field according to the query type you selected.5. Click Query.

The VPN List displays all VPNs matching the query criterion.

Adding monitor1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Traffic Monitor > VPN Traffic Monitor


3. Select one or multiple VPNs to be monitored.4. Click Add Monitor.

Removing monitor1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Traffic Monitor > VPN Traffic Monitor


3. Select one or multiple VPNs and click Remove Monitor.A confirmation dialog box appears.

4. Click OK.


Setting SA traffic monitor

Viewing SA traffic monitor settings1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Traffic Monitor > SA Traffic Monitor

Setting.The SA List page appears.SA List contents

• SA Name—Name of the SA.

• Attached VPN—Name of the VPN to which the SA belongs.

• Monitor Status—Monitor state of the SA. Options are Monitored and Not Monitored.

• Attached PE—Name and IP address of the PE device to which the SA belongs.

• PE Interface—Description of the PE interface.

• Attached CE—Name and IP address of the CE device to which the SA belongs.

• CE Interface—Description of the CE interface.

Querying SAs1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Traffic Monitor > SA Traffic Monitor

Setting.The SA List page appears.

3. In the SA Query area, select a query type from the Query Type list. Options are All, SA Name,Monitor Status, and Attached VPN.


The SA List displays all SAs matching the query criterion.

Adding monitor1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Traffic Monitor > SA Traffic Monitor


3. Select one or multiple SAs to be monitored.4. Click Add Monitor.

Removing monitor1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Traffic Monitor > SA Traffic Monitor


3. Select one or multiple SAs and click Remove Monitor.A confirmation dialog box appears.

4. Click OK.

Traffic monitor 77

VPN traffic reportYou can view the VPN traffic statistics in the VPN traffic report after VPN traffic monitor is enabled.The report shows the incoming traffic and outgoing traffic trends of a VPN.

Viewing VPN traffic list1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Traffic Monitor > VPN Traffic Report.

The VPN Traffic List page appears.VPN Traffic List contents

• VPN Name—Name of the monitored VPN.

• VPN Type—Type of the VPN. The value is BGP/MPLS VPN.

• Incoming Traffic (bytes/s)—Incoming traffic of the VPN.

• Outgoing Traffic (bytes/s)—Outgoing traffic of the VPN.

• View Details—Click the View icon to enter the VPN traffic report details page.

Querying reports1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Traffic Monitor > VPN Traffic Report.

The VPN Traffic List page appears.3. In the Report Query area, select a query type from the Query Type list. Options are All and

VPN Name.4. Enter the query criterion in the Query Condition field according to the query type you selected.5. Click Query.

The VPN Traffic List displays all VPNs matching the query criterion.

Viewing details

1. Click the View icon in the View Details field for the VPN to be viewed.The report page appears.

2. In the Query Condition area, select a time range from the Time Range list. Options are Dataof last one hour (the default setting), Data of today, Data of this week, Data of this month,Data of this year, Customized data.

3. Click OK. The report is displayed below the Query Condition area.Incoming Traffic report

• Graph type switch buttonsOn the upper left of the graph are the Table, Line Chart, Bar Chart, and Sampling Pointbuttons. Click the buttons to view the report in different charts. The default setting isdisplaying data in a line chart.

• Export report linksClick the Export as Excel link on the upper right of the graph to export the report to theexcel format. (You can also click the Export as PDF, Export as HTML, or Export as TXTlink to export the report to the corresponding format.) The Download Traffic Report windowprompts. Click the Traffic Report link and select a save path. After the report is saved,click Close in the Download Traffic Report window to return to the Incoming Traffic graph.


• Incoming traffic graphThe x coordinate in the line chart represents the time and the y coordinate represents thetraffic. The report shows the trend of the incoming traffic for the MPLS VPN.

• Incoming traffic list contents

Monitored Object—Name of the VPN that is monitored.◦◦ Min. Value—Minimum value of the monitored traffic.







The function and format of the outgoing traffic report are the same as those of the incomingtraffic report. Details are not shown.

4. Click any option from the navigation tree to exit the page.

SA traffic reportYou can view the SA traffic statistics in the SA traffic report after SA traffic monitor is enabled. Thereport shows the trends of the incoming traffic, outgoing traffic, incoming bandwidth utilization,and outgoing bandwidth utilization of an SA.

Viewing SA traffic list1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Traffic Monitor > SA Traffic Report.

The SA Traffic List page appears.SA Traffic List contents

• SA Name—Name of the monitored SA.

• Attached VPN—Name of the VPN to which the SA belongs.

• Attached PE—Name and IP address of the PE device to which the SA belongs.

• PE Interface—Interface description of the PE.

• Attached CE—Name and IP address of the CE device to which the SA belongs.

• CE Interface—Interface description of the CE.

• Incoming Traffic (bytes/s)—Incoming traffic of the SA.

• Incoming bandwidth utilization (%)—Incoming bandwidth utilization of the SA.

• Outgoing Traffic (bytes/s)—Outgoing traffic of the SA.

• Outgoing bandwidth utilization (%)—Outgoing bandwidth utilization of the SA.

• View Details—Click the View icon to enter the SA traffic report details page.

Querying reports1. Click the Service tab.

Traffic monitor 79

2. From the navigation tree, select MPLS VPN Manager > Traffic Monitor > SA Traffic Report.The SA Traffic List page appears.

3. In the Report Query area, select a query type from the Query Type list. Options are All, VPNName, and Attached VPN.


The SA Traffic List displays all SAs matching the query criterion.

Viewing details

1. Click the View icon in the View Details field for the SA to be viewed.The report page appears.

2. In the Query Condition area, select a time range from the Time Range list. Options are Dataof last one hour (the default setting), Data of today, Data of this week, Data of this month,Data of this year, Customized data.

3. Click OK. The Incoming Traffic, Outgoing Traffic, Incoming bandwidth utilization, and Outgoingbandwidth utilization reports are displayed below the Query Condition area.Incoming Traffic report

• Graph type switch buttonsOn the upper left of the graph are the Table, Line Chart, Bar Chart, and Sampling Pointbuttons. Click the buttons to view the report in different charts. The default setting isdisplaying data in a line chart.

• Export report linksClick the Export as Excel link on the upper right of the graph to export the report to theexcel format. (You can also click the Export as PDF, Export as HTML, or Export as TXTlink to export the report to the corresponding format.) The Download Traffic Report windowprompts. Click the Traffic Report link and select a save path. After the report is saved,click Close in the Download Traffic Report window to return to the Incoming Traffic graph.

• Incoming traffic graphThe x coordinate in the line chart represents the time and the y coordinate represents thetraffic. The report shows the change trend of the incoming traffic for the MPLS VPN.

• Incoming traffic list contents

Monitored Object—Name of the VPN that is monitored.◦◦ Min. Value—Minimum value of the monitored traffic.







◦ Times of Beyond Threshold Level 1—Number of times that the monitored trafficexceeds the level-1 threshold.


◦ Proportion of Beyond Threshold Level 1—Percentage of the sampling points thatexceed the level-1 threshold to all sampling points.



The function and format of the outgoing traffic report are the same as those of the incomingtraffic report. Details are not shown.Incoming bandwidth utilization reportThe graph type switch buttons and the export report links are the same as those of the incomingtraffic report.

• Incoming bandwidth utilization graphThe x coordinate in the line chart represents the time and the y coordinate represents thebandwidth utilization. The report shows the trend of the incoming bandwidth utilizationfor the MPLS VPN.

• Incoming bandwidth utilization list contents

Monitored Object—Name of the SA that is monitored.◦◦ Min. Value—Minimum value of the bandwidth utilization.

◦ Max. Value—Maximum value of the bandwidth utilization.

◦ Current Value—Current value of the bandwidth utilization.

◦ Average Value—Average value of the bandwidth utilization.

◦ Min. Value at—Time when the minimum value of the bandwidth utilization appears.

◦ Max. Value at—Time when the maximum value of the bandwidth utilization appears.






The function and format of the outgoing bandwidth utilization report are the same as thoseof the incoming bandwidth utilization report. Details are not shown.

4. Click any option from the navigation tree to exit the page.

Applications

Managing carrier's MPLS VPNAs shown in Figure 27, the provider uses MPLS VPN Management to manage full-mesh VPN 1.MPLS VPN Management accesses the network through a P device, and manages the PEs and P

Applications 81

devices through public addresses. MPLS VPN Management does not manage the CEs, which aremaintained by the customer.

Figure 27 Network diagram

Perform the following tasks to manage VPN 1 with MPLS VPN Management:1. Add VPN 1. See "Adding VPN 1."2. Add a VCE. See "Adding a VCE."3. Monitor and view the traffic of VPN 1 and the traffic between PE 1 and CE 1. See "Monitoring

and viewing the traffic of VPN 1 and the traffic between PE 1 and CE 1."

Adding VPN 1Use the auto-discovery function to add VPN 1 that has been deployed. After VPN 1 is discovered,create virtual CEs (VCEs) to represent the physical CEs.Before you add VPN 1 to MPLS VPN Management, make sure BGP, MPLS, and SNMP have beenconfigured on the devices, and the P devices and PEs have been added to IMC.

Creating AS 1001. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Region management.

The AS List page displays all ASs.3. Click Add on top of the List area.

The Add AS dialog box appears.4. Enter AS 100 in the AS Name field and enter 100 in the AS Number field.5. Click OK.

Importing PEs and P devices1. Click the Service tab.


2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Region management.The AS List page displays all ASs.

3. Click the AS 100 link.The Sub-region/PE Device List page appears.

4. Click Import PE on top of the Sub-region/PE Device List area.The Import Device page appears.

5. Enable Filter devices according to AS number.6. Click Select, and select PE 1, PE 2, and PE 3.7. Click OK to return to the Sub-region/PE Device List page.8. Click Import P on top of the Sub-region/PE Device List area.

The Import Device page appears.9. Click Select and select the four P devices.10. Click OK to return to the Sub-region/PE Device List page.

Discovering VPN 1 automatically1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Auto Discovery.

The auto discovery configuration guide page appears.3. Select PEs:

a. In the Auto Discovery Parameter Settings area, enable Remove all invalid links andSynchronize PE device before auto discovery.

b. Click Select PE.The Select Devices dialog box appears.

c. Select PE 1, PE 2, and PE 3, and click OK to return to the PE Selection page.d. Click Auto Discovery.

4. A process bar for VPN auto discovery appears. When the loading is finished, you directlyenter the page for VPN selection.

5. Select the VPN:a. Select VPN 1 in the VPN List Found.b. Click Next.

6. To configure VRF binding relationships, enable Create Non-managed CE automatically andclick OK.

You can see three links from the PEs to the corresponding VMCEs in the Configured VPN LinkResult.

Verifying the configuration1. From the navigation tree, select MPLS VPN Manager > VPN Resources > VPN management.

The BGP/MPLS VPN List page displays all VPNs.You can view the VPN topology and the audit status for VPN 1 in the list.

2. From the navigation tree, select MPLS VPN Manager > VPN Resources > SA management.The SA List page displays all SAs.The PE1-VCE1, PE2-VCE2, and PE3-VMCE3 SAs are in the SA List.

Applications 83

Adding a VCE

Adding a new VCE1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > SA management.

The SA List page displays all SAs.3. Click Add on top of the SA List area.4. Select a PE and a VPN for the SA:

a. Click Select PE on the Select PE and VPN page.The Select Devices page appears.

b. Select PE 3 and click OK to return to the Select PE and VPN page.c. Click Select VPN on the Select PE and VPN page.

The Select VPN page appears.d. Select VPN 1 and click OK to return to the Select PE and VPN page.e. Click Next.

5. Select an SC:a. Select SC(100:1) in the SC of Current VPN list.b. Select the Add by HUB handling method.c. Click Next.

6. Configure the PE and CE.a. To configure the PE's interface that connects to the CE, select Eth1/1 from the Interface

Description drop-down list.The interface's IP address and subnet mask of Ethernet 1/1 automatically appear in theInterface IP/Mask field.

b. To configure the CE, enable Create Non-managed CE automatically, and then click Next.7. Configure the VRF information.

The system automatically generates a default VRF name in the VRF Name field.The system automatically generates a default RD value in the RD Value field.Click Next.

8. The Summary page includes the Basic Information, Configuration command, and DeployImmediately areas. The Basic Information and Configuration command areas help you verifythe configuration before you execute the configuration commands.a. Enable Deploy Immediately.b. Click OK to return to the SA List page.

Verifying the configurationFrom the navigation tree, select MPLS VPN Manager > VPN Resources > SA management.The SA List page displays all SAs.You can see the link deployment status for the newly added SA is Deploying. After the SA isdeployed, the status changes to Normal. You can view the PE3-VCE4 SA in the topology for VPN1.

Monitoring and viewing the traffic of VPN 1 and the traffic between PE 1 and CE 1

Adding VPN 1 to be monitored1. Click the Service tab.


2. From the navigation tree, select MPLS VPN Manager > Traffic Monitor > VPN Traffic MonitorSetting.The VPN List page appears.

3. Select VPN1 in the list and click Add Monitor.

Viewing the VPN traffic report1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Traffic Monitor > VPN Traffic Report.

The VPN Traffic List page appears.

3. Click the View icon in the View Details field for VPN 1.The report page appears.

4. In the Query Condition area, select a time range from the Time Range drop-down list.Options are Data of last one hour (the default setting), Data of today, Data of this week, Dataof this month, Data of this year, and Customized data.

5. Click OK.The report data is displayed below the Query Condition area.

Adding the PE1-VCE1 SA to be monitored1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Traffic Monitor > SA Traffic Monitor


3. Select PE1-VCE1 in the list and click Add Monitor.

Viewing the SA traffic report1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > Traffic Monitor > SA Traffic Report.

The SA Traffic List page appears.

3. Click the View icon in the View Details field for the PE1-VCE1 SA.The report page appears.

4. In the Query Condition area, select a time range from the Time Range drop-down list.Options are Data of last one hour (the default setting), Data of today, Data of this week, Dataof this month, Data of this year, and Customized data.

5. Click OK.The report data is displayed below the Query Condition area.

Managing enterprise's MPLS VPNAs shown in Figure 28, the enterprise uses MPLS VPN Management to manage its own MPLSVPNs. MPLS VPN Management accesses the network through a management CE, manages the Pand PE devices through public addresses, and manages the CEs through the management VPN.Fully meshed VPN 1 and VPN 2 carry VPN traffic. The hub-spoke management VPN carriesmanagement traffic between MPLS VPN Management and devices, and isolates sites at Layer 3.On the management PE (hub of the management VPN), configure the import RT value as 200:1and the export RT value as 200:2. On each PE, configure a service VPN and a management VPN.

Applications 85

On each spoke of the management VPN, configure the import RT value as 200:2 and the exportRT value as 200:1.


Perform the following tasks to manage enterprise MPLS VPNs with MPLS VPN Management:1. Configure the management VPN. See "Configuring the management VPN."2. Add VPN 2. See "Adding VPN 2."3. Troubleshoot. See "Troubleshooting."

Configuring the management VPNAssume that the management VPN has been deployed on the network.To configure the management VPN:1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Management VPN.

The Management VPN Configuration page appears.3. Configure the following parameters:

• Status—Select Enabled from the drop-down list.

• HUB's Import RT—Enter 200:1.

• HUB's Export RT—Enter 200:2.4. Click OK.


Adding VPN 2

Adding AS 1001. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Region management.

The AS List page displays all ASs.3. Click Add on top of the AS List area.

The Add AS dialog box appears.4. Enter AS 100 in the AS Name field and enter 100 in the AS Number field.5. Click OK.

Importing PEs and P devices1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > Region management.

The AS List page displays all ASs.3. Click the AS 100 link.

The Sub-region/PE Device List page appears.4. Click Import PE on top of the Sub-region/PE Device List area.

The Import Device page appears.5. Enable Filter devices according to AS number.6. Click Select, and select PE 1, PE 2, PE 3 and PE 4.7. Click OK to return to the Sub-region/PE Device List page.8. Click Import P on top of the Sub-region/PE Device List area.

The Import Device page appears.9. Click Select and select the four P devices.10. Click OK to return to the Sub-region/PE Device List page.

Importing CEs1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Devices > CE Device List.

The CE Device List page displays all CE devices.3. Click Import on top of the CE Device List area.

The Import Device page appears.4. Click Select and select CE 1, CE 2, CE 3, and CE 4.5. Click OK to return to the Import Device page.6. Click OK.


Adding VPN 21. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > VPN management.

The BGP/MPLS VPN List page displays all VPNs.3. Click Add on top of the BGP/MPLS VPN List area.

The Add VPN dialog box appears.

Applications 87

4. Configure the following parameters as needed:• VPN Name—Enter VPN2.

• Connectivity Audit—Enable Periodical audit, use the default audit interval (8 hours), andenable Audit Inter-Spoke Unconnectivity.

• Description—Enter Add VPN2 as needed.5. Click OK.

Adding an SC1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > VPN management.

The BGP/MPLS VPN List page displays all VPNs.3. Click the VPN2 link to enter the VPN details page.4. Click the SC List tab on the page.5. Click Add.6. Configure the following parameters:

VPN Name—Enter SC(300:1, 300:1).SC Networking Type—Select Full-Mesh.HUB's Import RT—Enter 300:1.HUB's Export RT—Enter 300:1.

7. Click OK.

Adding the PE2-CE2 SA1. Click the SA List tab on the VPN details page.2. Click Add on top of the SA List area.3. Select a PE and a VPN for the SA:

a. Click Select PE on the Select PE and VPN page.The Select Devices page appears.

b. Select PE2 and click OK to return to Select PE and VPN page.c. Click Select VPN.

The Select VPN page appears.d. Select VPN2 and click OK to return to Select PE and VPN page.e. Click Next.

4. Select an SC for the SA:• Select SC(300:1, 300:1) in the SC of Current VPN list.

• Select Add by HUB.

• Click Next.


5. Configure the interfaces on the PE and the CE.a. To configure the PE 2's interface that connects to the CE:

i. Select Eth1/1 from the Interface Description drop-down list.ii. The IP address and subnet mask for the interface automatically appear in the Interface

IP/Mask field.b. To configure the CE 2's interface that connects to the PE:

i. Select CE2 from the Device Name drop-down list.ii. Select Eth1/1 from the Interface Description drop-down list.

The IP address and subnet mask for the interface automatically appear in the InterfaceIP/Mask field.

iii. Click Next.

6. Configure the VRF information.The system automatically generates a default VRF name in the VRF Name field.The system automatically generates a default RD valuein the RD Value field.a. Enable Configure Route.b. Click Next.

7. Configure routing between PE 2 and CE 2:a. Select the OSPF routing protocol.b. Click Next.

8. The Summary page includes the Basic Information, Configuration command, and DeployImmediately areas. The Basic Information and Configuration command areas help you verifythe configuration before you execute the configuration commands.a. Disable Deploy Immediately. After you add the PE4-CE4 SA, deploy the PE2-CE2 SA and

the PE4-CE4 SA together.b. Click OK to return to the SA List page.

Add the PE4-CE4 SA in the same way that the PE2-CE2 SA is added.

Deploying SAs1. Click the SA List tab on the VPN details page.2. Select the PE2-CE2 SA and the PE4-CE4 SA in the list.3. Click Deploy on top of the SA List area.

Verifying the configurationAfter the deployment, the link status for the two SAs is Normal, which indicates that CE 2 and CE4 can communicate with each other.

Troubleshooting1. Click the Service tab.2. From the navigation tree, select MPLS VPN Manager > VPN Resources > VPN management.

The BGP/MPLS VPN List page displays all VPNs.3. Click the link in the Audit Result field for VPN1 whose Audit Status is Disconnected.

The page for connectivity audit appears.

4. Click the Troubleshooting icon for the failed link in the VPN Link Audit Information list.

Applications 89

5. The Troubleshooting List displays the operation and result for troubleshooting.Troubleshooting List contents

• Time—Time when the troubleshooting began, in seconds.

• Source—Source device.

• Destination—Destination device.

• Result—Result, which helps you fix the network problems.


4 Using MPLS ManagementMPLS management overview

MPLS management provides a comprehensive MPLS network management solution for metropolitanarea networks. It cooperates with H3C devices to manage MPLS networks. MPLS managementprovides various functions, including Device Management, LDP Management, LSP Management,Topology Management, Label Statistics, and LSP Traffic Statistics.MPLS management is based on the IMC platform. It adopts the B/S structure. Operators canmanage and monitor MPLS networks anytime and anywhere from the local area network or Internetby using a browser without having to install any client.

Basic concepts

FECAs a forwarding technology based on classification, MPLS groups packets with the samecharacteristics (such as packets with the same destination or service class) into a class, called aforwarding equivalence class (FEC). Packets of the same FEC are handled in the same way on anMPLS network. The device supports classifying FECs according to the network layer destinationaddresses of packets.

LabelA label is a short, fixed length identifier for identifying a single FEC. A label is locally significantand must be locally unique.

Figure 29 Format of a label

As shown in Figure 29, a label is encapsulated between the Layer 2 header and Layer 3 headerof a packet. A label is four bytes in length and consists of the following fields:

• Label—20 bits in length. Label value for identifying a FEC.

• Exp—Three bits in length. Reserved field, usually used for CoS.

• S—One bit in length. MPLS supports multiple levels of labels. This field is used to indicatewhether a label is at the bottom of the label stack. 1 indicates that the label is at the bottomof the label stack.

• TTL—Eight bits in length. Like the homonymous IP header field, it is used to prevent loops.

LSRA label switching router (LSR) is a fundamental component on an MPLS network. LSRs support labeldistribution and label swapping.

LERA label edge router (LER) is an LSR that resides at the edge of an MPLS network and is connectedto another network.

MPLS management overview 91

LSPA label switched path (LSP) is the path along which packets of a FEC travel through an MPLSnetwork. An LSP is a unidirectional path from the ingress of an MPLS network to the egress. Onan LSP, in the packet transfer direction, two neighboring LSRs are called the “upstream LSR” and“downstream LSR”, respectively. As shown in Figure 30, LSR B is the downstream LSR of LSR A;LSR A is the upstream LSR of LSR B.

Figure 30 Diagram for an LSP

LFIBOn an MPLS network, labeled packets are forwarded according to the Label Forwarding InformationBase (LFIB), which is like the FIB for IP packet forwarding on an IP network.

Control plane and forwarding planeAn MPLS node consists of two planes, control plane and forwarding plane.

• Control plane—Assigns labels, selects routes, establishes the LFIB, establishes and removesLSPs.

• Forwarding plane—Forwards packets according to the LFIBAs shown in Figure 31, the element of an MPLS network is LSR. LSRs in the same routing oradministrative domain form an MPLS domain.

Figure 31 Diagram for the MPLS network structure

92 Using MPLS Management

An MPLS domain consists of the following types of LSRs:

• Ingress LSRs for receiving and labeling packets coming into the MPLS domain.

• Transit LSRs for forwarding packets along LSPs to their egress LERs according to the labels.

• Egress LSRs for removing labels from packets and IP forwarding the packets to their destinationnetworks.

In other words, transit LSRs perform MPLS forwarding based on labels of packets, and the ingressand egress LSRs deal with the switch-over between MPLS and IP forwarding.

FunctionsTo access main functions, click the Service tab from the tabular navigation system on the top of theIMC main page, and then select MPLS Management > Quick Start from the left navigation tree.Main functions appear in the Quick Start page.

• Device Management—Allows operators to import devices from the IMC platform to the MPLSmanagement component, to configure device LSR IDs, and to enable MPLS or MPLS LDP fordevices and interfaces. Provides batch operations to facilitate device and interface management.

• LDP Management—Allows operators to manually create remote LDP peers and view sessioninformation between peers. In addition, the system can automatically discover local peers.

• LSP Management—Allows operators to manually add static LSPs on the topology, deploy,undeploy, delete, and audit LSPs. The system can also automatically add static LSPs andautomatically discover LSPs.

• Topology Management—Displays the MPLS global network topology and LSPs between devices,and highlights LSPs.

• Label Statistics—Collects device label usage statistics and displays the top 5 devices with thehighest dynamic or static label usage percentages in charts.

• LSP Traffic Statistics—Collects and displays LSP traffic statistics, allows operators to set LSPtraffic thresholds, and generates outgoing traffic statistics reports from multiple perspectives.

Getting started with MPLS managementIf you are using the MPLS management component for the first time:1. Import devices.

Import the devices to be managed to the MPLS Management component, configure deviceLSR IDs, and enable MPLS and MPLS LDP for devices and interfaces. Only devices that havebeen added to IMC platform can be imported to MPLS Management component.

2. Create LDP peers.Create remote LDP peers based on service requirement. Local LDP peers are automaticallydiscovered, and session information between peers can be displayed. After LDP peers aresuccessfully created, dynamic LSPs are generated. Remote peers mainly apply to Martini MPLSL2VPN, Martini VPLS, and MPLS LDP over MPLS TE.

3. Create LSPs.The LSP management and topology functions allow you to manually create static LSPs. Thesystem can also automatically create LSPs and discover LSP paths between devices. After LSPsare successfully created, you can deploy, undeploy, delete, and audit the LSPs.

4. View LSP traffic statistics.Monitor LSPs, set LSP traffic alert thresholds, collect and view LSP traffic statistics, and viewthe outgoing traffic statistics report from different points of views.

Getting started with MPLS management 93

Common operations:

• View device label statisticsView label usage statistics on devices and view the top 5 devices by label usage percentagein graphs and tables.

• Highlight an LSP on the topologyView the MPLS global network topology, view LSPs between devices, and highlight an LSPon the topology.

Typical application

Application scenarioA corporation has two data centers: one primary and one backup. To connect the two data centersat Layer 2 using the MPLS technology, build an MPLS network based on the current networkstructure, and create a static LSP for label forwarding and label statistics.The two data centers are connected at Layer 2 through the MPLS network constructed by devicesP1, P2, and P3, as shown in Figure 32.

Figure 32 Connecting data centers at Layer 2 by using MPLS

Scenario analysisTo meet the application requirements, you can use the MPLS management component to createand manage the MPLS network. Import P1, P2, and P3 to the MPLS Management, and batch enableMPLS and MPLS LDP for these devices. The system automatically maps out a network topology ofthe MPLS network constructed by the imported devices. Based on the topology, create and deploya static LSP. Then, you can view the label usage statistics, learn the LSP traffic statistics, and setLSP traffic thresholds.


Operation procedure1. Create an MPLS network.

a. Click Service > MPLS Management > Device Management from the tabular navigationsystem on the top of the IMC main page.

b. Click the Import Devices button. Import P1, P2, and P3 to the MPLS management. (Assumethat the devices are already imported to the IMC platform.)

c. Select P1, P2, and P3 in the Device Management page, and then click the EnableMPLS/LDP button to batch enable MPLS and MPLS LDP for P1, P2, and P3.

2. Create and deploy LSPs.a. Click Service > MPLS Management > LSP Management from the tabular navigation system

on the top of the IMC main page.b. Click the Add Static LSP button.c. Click the Manual Deployment tab.d. In the Topology pane, right click P1 and then click Set as Ingress.e. Double click the link between P1 and P2, and then double click the link between P2 and

P3. In this way, P2 is specified as transit LSR.f. Right click P3 and then click Set as Egress.g. Fill in LSP Name and LSP Description.h. Click the Pre-Allocate Label button. Valid values are assigned to outgoing labels.i. Click OK.The path between P1 and P2 can be manually selected, or automatically generated by thesystem. You can create more static LSPs in the same way.

3. View label statistics.Click Service > MPLS Management > Label Statistics from the tabular navigation system onthe top of the IMC main page. On the page, you can view the top 5 devices by static labelsused, top 5 devices by dynamic labels used, and device label usage percentage.

4. View LSP traffic statistics.a. Click Service > MPLS Management > LSP Traffic Statistics from the tabular navigation

system on the top of the IMC main page.b. Select Default Threshold Settings from the left navigation tree under LSP Traffic Statistics.c. Set the alert thresholds for outgoing LSP traffic by clicking the Modify icon in the Default

Threshold List. Select Enable level-1 alert and enter 10000000 Kb/s as a Major alert.Select Enable level-2 alert and enter 100000 Mb/s as a Critical alert. Click OK.

d. Select LSP Traffic Monitoring from the left navigation tree under LSP Traffic Statistics. Selectthe newly deployed LSP from the LSP List, and then click the Monitor button in the upper-leftcorner. The monitoring status changes to Monitored. You can view in real time the top 5LSPs by outgoing traffic and the LSP monitoring status by clicking Service > MPLSManagement from the tabular navigation system.

e. Select LSP Traffic Report from the left navigation tree under LSP Traffic Statistics. Query

the newly deployed LSP by LSP name, and then locate and click the LSP Details iconin the LSP Traffic List. You can view the latest outgoing traffic statistics and detailed LSPtraffic reports in forms of a table, line chart, and bar chart.

Typical application 95

Using MPLS management components

Device managementThis function enables you to manage devices in an MPLS network. You can import, synchronize,delete devices, and enable MPLS/MPLS LDP for devices and interfaces. Devices that can bemanaged by this system must meet the following conditions:• Support MPLS

• Can be accessed by Telnet or SSH

• Have been added to IMC platform

Importing devicesTo import a device to the MPLS management:1. Click Service > MPLS Management > Device Management from the tabular navigation system

on the top of the IMC main page.2. Click the Import Devices button in the upper-left corner of the Device List.


3. Click the Select Devices button. In the pop-up page, select the devices by performing thefollowing procedure:a. Select devices from the Query Conditions pane with the following methods:

• Click the By View tab and select a network under the IP View to import devices inthis network.

• Click the By View tab and select a device type under the Device View to importdevices of a specific type, such as Routers, Switches, Servers, Desktops, and Others.

• Click the By View tab and select My Network View or Devices Not in Views.

• Click the Advanced Query tab and entering searching conditions, as shown inFigure 33.

Figure 33 Select Devices page

◦ Device IP— Indicates the device IP address. This field supports fuzzy match.Select Exact Query to perform exact query.

◦ Device IP List—Click the IP List icon to display the Device IP List Configurationpage. In this page, enter one or more device IP addresses in the Input DeviceIP text box, and then click the Add button. Click OK to confirm and go back tothe previous page.

◦ Device Label—Indicates the device name or label.

◦ Device Status—Indicates the device status. Values includes Unmanaged,Unknown, Normal, Warning, Minor, Major, and Critical. Device Status isdetermined by the highest severity or alarm level for the device, when a devicehas more than one current alarm that has not been cleared or recovered. Devicesthat are added to but not managed by IMC are categorized as unmanaged.Devices whose information cannot be obtained by IMC are categorized asunknown.

◦ Device Category—Indicates the device type. Options include: Routers, Switches,Servers, Security, Storage, Wireless, Voice, Surveillance, Video, Virtual Devices,Module, Application Controller, Printers, UPS, Desktops, and Others.

Using MPLS management components 97

◦ Device Series—Indicates devices series.

◦ Contact—Indicates the contact information, such as user names or mobile phonenumbers, of the operators who are responsible for the selected devices.

◦ Location—Indicates where the devices are located.

◦ Device Reachability—Indicates whether a device can be reached. Optionsinclude: Reachable and Unreachable.

◦ Query—Click the Query button to display devices meeting the searchingconditions in the Device Found pane.

b. To add one device to the importing list, highlight a single device entry in the Device Found

pane, and then click the Add selected icon . To add all devices into the importing list,

click the Add all icon . Selected devices appear in the Selected Devices pane.c. Click OK at the bottom of the page.

4. Click OK to start importing devices. During the importing process, the system displays theimporting result showing when and whether a device has been successfully imported. Youcan stop the importing by clicking the Quit Device Importing link in the Operation box.

5. Click the Back button to go back to the Device List view and examine the imported devices.

NOTE: Only devices that have been added to the IMC platform can be imported to the MPLSmanagement.

Deleting devicesTo delete one or more devices from the MPLS management:1. Click Service > MPLS Management > Device Management from the tabular navigation system

on the top of the IMC main page.2. Select one or more devices to be deleted.3. Click the Delete Devices button in the upper-left corner of the Device List.

Querying devicesTo query a device from the MPLS management:1. Click Service > MPLS Management > Device Management from the tabular navigation system

on the top of the IMC main page.2. Enter searching conditions in the Query Devices pane:

• Device Name—Indicates the device names or IP addresses.

• Device Status—Indicates the device status. Values include All, Unmanaged, Unknown,Normal, Warning, Minor, Major, and Critical. Device Status is determined by the highestseverity or alarm level for the device when a device has more than one current alarm thathas not been cleared or recovered. Devices that are added to but not managed by IMCare categorized as unmanaged. Devices whose information cannot be obtained by IMCare categorized as unknown.

• MPLS LDP Status—Indicates the MPLS LDP status. Values include: All, Enabled and Disabled.

• LSR ID—Indicates the LSR ID.

• MPLS Status—Indicates the MPLS status. Values include: All, Enabled and Disabled.3. Click the Query Devices button. The Device List displays all the devices that match the searching

conditions. Click the Reset button to clear the searching conditions.

NOTE: The Device Name and LSR ID fields support fuzzy match.


Synchronizing devicesThe synchronization function enables the system to obtain configuration information from thespecified devices immediately, and to manage the device information in MPLS management. Youcan determine whether the current device configuration is valid by checking the last synchronizationtime and synchronization status of the device.To synchronize one or more devices from the MPLS management:1. Click Service > MPLS Management > Device Management from the tabular navigation system

on the top of the IMC main page.2. Select one or more devices to be synchronized.3. Click the Synchronize button in the upper-left corner of the Device List.

NOTE:• The synchronization process may take a while. You may need to click the Refresh button to

display the latest synchronization status.• Do not synchronize devices when adding LSPs. Synchronize devices before you add LSPs to

avoid possible errors.

Enabling MPLS and MPLS LDP for devicesThis function enables you to configure the LSR ID for a device, and to decide whether to enableMPLS and MPLS LDP for the device. In an MPLS domain, you need to enable MPLS on all devicesfor MPLS forwarding before you can configure other MPLS features.To enable MPLS and MPLS LDP for a device:1. Click Service > MPLS Management > Device Management from the tabular navigation system

on the top of the IMC main page.

2. Locate and click the Operation icon of a device entry. The operation menu appears andlists all the operations that you can perform.

3. Select Enable MPLS/LDP from the menu. The Configure MPLS/MPLS LDP for Device pageappears.

4. Select Enabled for MPLS Status and MPLS LDP Status, respectively.5. Click OK.

NOTE:• If a device has been already configured with an LSR ID before or after it is added to the MPLS

management, you cannot change the LSR ID for the device in MPLS management. Tore-configure a device LSR ID, an administrator must log into the device and execute relatedcommands.

• If no LSR ID is configured for a device, you can use the IP address of the loopback interfaceon the device as the device LSR ID.

• You cannot enable MPLS and MPLS LDP for a device when the device LSR ID is not configured.

• You cannot enable MPLS LDP for a device when the MPLS Status of the device is set to Disabled.

Batch enabling MPLS and MPLS LDP for devicesUse this function to enable MPLS and MPLS LDP for multiple devices in bulk. Before you use thisfunction, make sure the device LSR IDs have been configured.To batch enable MPLS and MPLS LDP for devices:1. Click Service > MPLS Management > Device Management from the tabular navigation system

on the top of the IMC main page.2. Select the target devices from the Device List, and then click Enable MPLS/LDP in the upper-left

corner.



NOTE:• You cannot enable MPLS/LDP for a device when the device LSR ID is not configured.

• To enable MPLS LDP for a device, you must enable MPLS for the device first.

Device advanced configurationThis function enables you to configure the GR for Session, Reconnect Timer (s), FT Reconnect Timer,and Neighbor Liveness Timer (s) for a device that has been imported to the MPLS management.

NOTE: The Advanced Configuration option appears in the operation menu only after deviceMPLS/LDP are enabled.

To enter the device Advanced Configuration page:1. Click Service > MPLS Management > Device Management from the tabular navigation system



3. Select Advanced Configuration from the menu. The Advanced Configuration page appears.4. Modify the related parameters:

• GR for Session—LDP Graceful Restart (GR) enables an LSR to keep MPLS forwardingentries during an LDP restart, ensuring continuous MPLS forwarding. It is disabled bydefault.

• Recovery Timer (s)—LDP recover timers. During the LDP recovery time, LSRs use there-established LDP session to exchange label bindings, update label forwarding entries,and clear the stale tags for the entries. When the Recovery timer expires, the GR helperdeletes the label forwarding entries still marked stale. The value range for the LDP RecoveryTimer is 3 to 300 seconds.

• FT Reconnect Timer—When an LDP session is down, the GR helper marks the FEC-labelmappings learned from the session as stale and keeps these FEC-label bindings for aperiod of time defined as the Fault Tolerant (FT) reconnect timer. If the LDP session is notset up before the reconnect timer expires, the GR helper deletes the stale FEC-labelmappings and the corresponding MPLS forwarding entries. If the LDP session is successfullyre-established, the GR helper starts the recovery timer. The value range for the FT ReconnectTimer is 60 to 300 seconds.

• Neighbor Liveness Timer (s)—The maximum time that a GR helper maintains the neighborrelationship with the GR restarter and helps the GR restarter restore its LFIB informationwhen a session is down.

5. Click OK.

NOTE: You can configure the LDP Recovery Timer and FT Reconnect Timer for a device only whenthe GR for Session feature is enabled for the device.

Device Traffic ConfigurationThis function enables you to enable or disable Traffic Statistics, and to set Traffic Statistics Interval(s).To configure device traffic statistics:1. Click Service > MPLS Management > Device Management from the tabular navigation system


2. Locate and click the Operation icon of a device entry. The operation menu appears andlists all the operations that you can do.


3. Click Traffic Configuration in the operation menu to display the Configure Device TrafficStatistics page of the device.

4. Select Enable or Disable.5. Enter statistics interval in the Traffic Statistics Interval (s) text box.6. Click OK.

Viewing device label statisticsThis function enables you to view label usage statistics of a device, including the Number of UsedLabels, Number of Unused Labels, and the Label Usage Percentage.To view device label statistics:1. Click Service > MPLS Management > Device Management from the tabular navigation system



3. Click Label Statistics in the operation menu to display the Label Usage Statistics page of thedevice.

4. Click a link in the Number of Used Labels column to view detailed label usage information.Three rows in the Label Type field are: Static, Dynamic, and Static and Dynamic. Static labels areassigned manually to establish a static LSP. Dynamic labels are assigned through label distributionprotocols to establish a dynamic LSP. The value of Static and Dynamic is the sum of Static andDynamic.

Querying device interface informationThis function enables you to query interfaces of a specific device by Interface Description, InterfaceIP Address, MPLS Status, and MPLS LDP Status.1. Click Service > MPLS Management > Device Management from the tabular navigation system


2. Locate and click the Operation icon of a device entry, and then select Configure MPLS/LDPfor Interface from the operation menu. The interface configuration page for the selected deviceappears.

3. Enter searching conditions:• Interface Description—Indicates the description of an interface.

• Interface IP—Indicates the interface IP address.

• MPLS LDP Status—Indicates the MPLS LDP status. Values include: All, Enabled and Disabled.

• MPLS Status—Indicates the MPLS status. Values include: All, Enabled and Disabled.4. Click the Query button. The Interface Information List displays all the interfaces that match the

searching conditions. Click the Reset button to clear the searching conditions.

NOTE: The Interface Description and Interface IP fields support fuzzy match.

Enabling MPLS or MPLS LDP for interfacesUse this function to enable MPLS and MPLS LDP for an interface of a device that has been importedto the MPLS management.1. Click Service > MPLS Management > Device Management from the tabular navigation system




3. Click the Configure MPLS/LDP for Interface icon of an interface entry.4. Select Enabled for MPLS Status and MPLS LDP Status, respectively.5. Click OK.

NOTE: You cannot enable MPLS LDP for an interface when the MPLS status of the interface isDisabled.

Batch enable MPLS or MPLS LDP for interfacesUse this function to batch enable MPLS/MPLS LDP for multiple interfaces on a device. Before youuse this function, make sure the device has been imported to the MPLS management.1. Click Service > MPLS Management > Device Management from the tabular navigation system



3. Select one or more target interfaces, and then click the Enable MPLS/LDP button in the upper-leftcorner of the Interface Information List.


NOTE: You cannot enable MPLS LDP for an interface when the MPLS status of the interface isDisabled. You must enable the MPLS first.

LDP ManagementLDP management is used to manage LDP peers which include local peers and remote peers. Byenabling MPLS LDP for devices, remote LDP peers must be created on devices manually, whilelocal LDP peers can be created through automatic discovery. Local peers are discovered throughthe basic discovery mechanism defined in the LDP protocol. Remote peers are discovered throughthe extended discovery mechanism. Basic discovery mechanism discovers directly connected LSRs,and establishes link hello adjacencies with them. Extended discovery mechanism discovers indirectlyconnected LSRs and establishes targeted hello adjacencies. In LDP management, you can query,add, configure, delete LDP peers, and view LDP session information established between LDP peers.

Querying LDP peersThis function enables you to query LDP peers by Local Device, Peer Device, Session Status, Status(whether the peer relationship is normal), and Type (type of the LDP peers).To query LDP peers:1. Click Service > MPLS Management > LDP Management from the tabular navigation system on

the top of the IMC main page.2. Enter searching conditions in the Query LDP Peers pane:

• Local Device—Indicates the local device name or IP address.

• Peer Device—Indicates the peer device name or IP address.

• Session Status—Indicates the session status. Values include: All, NonExistent, Initialized,Open-Received, Open-Sent, and Operational.

• Status—Indicates the peer status. Values include: All, Normal, and Abnormal.

• Type—Indicates the peer types. Values include: All, Local, and Remote.3. Click the Query button. The Peer List displays all the peers that match the searching conditions.

Click the Reset button to clear the searching conditions.


NOTE: The Local Device and Peer Device fields support fuzzy match.

Adding LDP peersThis function enables you to create an LDP peer relationship between two devices so that the devicescan generate label forwarding entries, and dynamically establish and maintain LSPs. After youcreate a peer relationship between two devices, the two devices are called a pair of LDP peers,which are uniquely identified by the peer relationship name.To add LDP peers:1. Click Service > MPLS Management > LDP Management from the tabular navigation system on

the top of the IMC main page.2. Click the Add button in the upper-left corner.3. Enter the Local Device Name, the Peer Device Name, and the Peer Relationship Name.4. Click OK.

NOTE:• When you enter the local device name or the peer device name (including the device IP

addresses), the system automatically displays all devices with names containing the providedcharacters in the list. You can select the target device from the list. For example, if you enterTest, the system displays all devices with names containing Test in the list.

• The peer relationship name can contain up to 32 characters and must be unique in the system.

Deleting LDP peersThis function enable you to delete LDP peers from MPLS management. After you delete a peerrelationship, the corresponding peers and the LDP session established between the peers are alsodeleted from the MPLS management component.To delete LDP peers:1. Click Service > MPLS Management > LDP Management from the tabular navigation system on

the top of the IMC main page.2. Select one or more pairs of peers from the Peer List, and then click the Delete button in the

upper-left corner.3. Click OK in the pop-up confirmation page.

NOTE:• You can only delete remote LDP peers. Local LDP peers are generated through automatic

negotiation and cannot be deleted.• After an LDP peer relationship between two devices is deleted, the LDP session established

between the devices is also deleted, and the devices can no longer advertise labels anddynamically create LSPs.

Configuring LDP peers parametersThis function enables you to configure specific parameters for existing LDP peers to facilitate dynamicestablishment of LSPs.To configure LDP peers parameters:1. Click Service > MPLS Management > LDP Management from the tabular navigation system on

the top of the IMC main page.

2. Locate and click the Operation icon of a pair of LDP peers, and then select AdvancedConfiguration from the operation menu. The Advanced Configuration page for the selectedpeers appears.


3. Modify parameters:• Keepalive Timer (s)—Maximum time allowed for receiving an LDP PDU (one LDP PDU can

carry one or more LDP messages). When the timer expires, the LSR closes the TCPconnection and terminates the LDP session. The Keepalive timer value ranges from 1 to65535 seconds.

• Hello Timer (s)—Maximum time an LSR waits for receiving a hello message. LDP peersperiodically send Hello messages to indicate that they intend to keep the Hello adjacency.If an LSR does not receive any Hello message from a peer before the Hello timer expires,it deletes the Hello adjacency with this peer. When the last Hello adjacency for the sessionis deleted, the LSR sends a Notification message to terminate the LDP session. The Hellotimer value ranges from 1 to 65535 seconds.

• MD5 Authentication—To improve the security of LDP sessions, you can configure MD5authentication for the underlying TCP connections, so that the TCP connections can beestablished only if the peers have the same authentication password. Values include:Disable and Enable. If you select Enable, the password text box appears.

• Label Advertisement Mode—Only the Downstream Unsolicited (DU) mode is supported.In this mode, an LSR automatically assigns a label to an FEC and then distributes theFEC-label binding to its upstream LSR.

• Peer Path Vector Length—Maximum number of hops of an LSP contained in a label requestmessage or label mapping message. An LSR terminates the establishment of an LSP whenthe hop count of the path, or the length of the path vector, reaches the upper limit.

NOTE: The Advanced Configuration option is available for a pair of peers only when the peerStatus is Normal and the Session Status is Operational. Otherwise, you can only view the peerdetails.

Viewing session informationLDP sessions are established between LSRs based on TCP connections and used to exchangemessages for label binding, label releasing, and error notification. This viewing function enablesyou to view the session information and configuration of a pair of LDP peers.To view session information:1. Click Service > MPLS Management > LDP Management from the tabular navigation system on


2. Locate and click the Operation icon of a pair of LDP peers, and then select SessionInformation from the operation menu.


3. You can view the following parameters in the Session Information page:• Local LSR ID—Indicates local LSR ID.

• Peer LSR ID—Indicates peer LSR ID.

• TCP Connection—Indicates the TCP connection based on which the LDP session is created.

• Session Status—Indicates session status. Values include: All, NonExistent, Initialized,Open-Received, Open-Sent, and Operational.

• Local Device’s Role in Session—Indicates device role in session. Values include: Activeand Passive.

• Keepalive Timer (s)—Maximum time allowed for receiving an LDP PDU (one LDP PDU cancarry one or more LDP messages). When the timer expires, the LSR closes the TCPconnection and terminates the LDP session. The Keepalive timer value ranges from 1 to65535 seconds.

• Hello Timer (s)—Maximum time an LSR waits for receiving a hello message. LDP peersperiodically send Hello messages to indicate that they intend to keep the Hello adjacency.If an LSR does not receive any Hello message from a peer before the Hello timer expires,it deletes the Hello adjacency with this peer. When the last Hello adjacency for the sessionis deleted, the LSR sends a Notification message to terminate the LDP session. The Hellotimer value ranges from 1 to 65535 seconds.

• MD5 Authentication—Values include: Disable and Enable.

• Label Advertisement Mode—Only the DU mode is supported. In this mode, an LSRautomatically assigns a label to an FEC and then distributes the FEC-label binding to itsupstream LSR.

• Label Resource Status (Peer/Local)—Indicates the label resource status.

• Peer Discovery Mechanism—Local peers are discovered through the Basic discoverymechanism. Remote peers are discovered through the Extended discovery mechanism.

• Session Up Time—Indicates the connection time of a session.

• Label Acceptance Policy—The policy for filtering received label bindings. An upstreamLSR filters the label bindings received from the specified downstream LSR and acceptsonly those permitted by the specified prefix list.

NOTE: You can view the session information of a pair of peers only when the Session Status isOperational.

Viewing LDP peer detailsTo view LDP peer details:1. Click Service > MPLS Management > LDP Management from the tabular navigation system on


2. Locate and click the Operation icon of a pair of LDP peers, and then select Details fromthe operation menu. The LDP Peer Details page for the selected peers appears.

NOTE: You can view detailed information about a pair of LDP peers only when the status of thepeer relationship is Abnormal or the session status of the peers is not Operational.

LSP ManagementWith the LSP Management function, you can deploy MPLS LSPs in a simple and user-friendly way.You do not need to go to various device equipment rooms or execute bald command lines to setup or maintain LSPs. The network maintenance time and difficulties are highly reduced.


With basic network information well configured, you can deploy an entire LSP network or adjustsome deployments of an LSP network. After an LSP is deployed, you can highlight an LSP for intuitiveobservation. You can also manually add static LSPs on the topology, automatically add static LSPs,automatically discover LSPs, and delete and audit LSPs.

Querying LSPsOver time, the LSP list can grow large, making it more difficult for you to find an LSP at an glance.The Query capability enables you to query LSPs by LSP name, ingress device name, egress devicename, audit status, deployment status, and LSP type.To query an LSP:1. Click Service > MPLS Management > LSP Management from the tabular navigation system on

the top of the IMC main page.2. In the Query LSPs section of the page, specify the following query conditions:

• LSP Name—Indicates the LSP name.

• Ingress Device Name—Indicates the name of the ingress device.

• Egress Device Name—Indicates the name of the egress device.

• Audit Status—Indicates the audit status of the LSP. Values include All, Up, Down, Unknown,Auditing, Testing, Dormant, Not Present, and Lower Layer Down.

• Deployment Status—Indicates the deployment status of the LSP. Values include All, Normal,Undeployed, Deploying, Undeploying, Deployment failed, and Undeployment failed.

• LSP Type—Indicates the type of the LSP. Values include All, Static, Dynamic and CR-LSP.MPLS Management supports fuzzy query function, which allows you to specify intact or partialquery condition.

3. Click the Query button. All LSPs that match the query criteria are displayed in the LSP Listsection of the page.

4. To clear the query criteria and display all LSPs, click the Reset button.

Adding a static LSPYou can establish an LSP between specified devices either manually or automatically. You candeploy the LSP immediately after the LSP is generated or deploy all LSPs in a batch.

Configuration procedure1. Configure a path, either manually or automatically, for the static LSP.2. Assign values to outgoing labels.3. Check labels (optional).4. Deploy the LSP.

Configuring a path for the static LSP manuallyYou can manually configure the path and basic information for the LSP.To manually configure a path for the static LSP:1. Click Service > MPLS Management > LSP management from the tabular navigation system on

the top of the IMC main page.2. In the LSP List section of the page, click the Add Static LSP button.3. Scroll down to the bottom of the page, and then click the Manual Deployment.4. In the Topology section of the page, right-click the device on the topology that you want to

specify as the LSP ingress, and then select Set as Ingress that appears. The device is set asthe ingress of the LSP and an icon S appears on the topology next to the device. Informationabout this ingress appears in the Path List section of the page.


5. On the topology, double-click the link between the ingress device and a device that you wantto select as the transit device, to select a path segment for the LSP. The link is highlighted onthe topology and the transit device is displayed in the Path List section.

6. To select the next segment of the path for the LSP, double-click the next link. The next link youselect must be directly connected to the link you have previously selected. You can select morelinks in the same way.

7. When you have selected all segments of the LSP, right-click the end device of the last link, andthen select Set as Egress that appears. The device is set as the egress of the LSP and an iconD appears on the topology next to the device. The whole path you select for the LSP must startfrom the LSP ingress and end at the LSP egress. All devices on this LSP are displayed in thePath List section of the page.

8. In the Define LSP section of the page, enter the name for the LSP in the LSP Name field. TheLSP name can contain only letters, digits, and underscores.

9. Enter a description for the LSP in the LSP Description field, if needed.

NOTE: Do not select a loop path for the LSP.

TIP: You must specify links for the LSP in sequence. If an error occurs, click the Reset icon onthe topology tool bar to cancel all the path configuration, or click the Cancel icon on the topologytool bar to cancel the last step configuration.

Configuring a path for the static LSP automaticallyYou can automatically configure the path and basic information for the LSP.To configure a path for the static LSP automatically:1. Click Service > MPLS Management > LSP management from the tabular navigation system on

the top of the IMC main page.2. In the LSP List section of the page, click the Add Static LSP button.3. Scroll down to the bottom of the page, and then click the Auto Deployment tab.4. In the Topology section of the page, right-click the device on the topology that you want to

specify as the LSP ingress, and then select Set as Ingress that appears. The device is set asthe ingress of the LSP and an icon S appears on the topology next to the device.

5. Right-click the device on the topology that you want to specify as the LSP egress, and thenselect Set as Egress that appears. The device is set as the egress of the LSP and an icon Dappears on the topology next to the device.

6. Click Preview. The system automatically calculates the paths available for the LSP.7. If more than one path are found available, the system displays them on the topology.8. To specify the generated LSP to include or exclude a path, right-click the path and select Include

or Exclude, and then click Preview. The generated LSP is highlighted on the topology and alldevices on this LSP are displayed in the Path List section of the page.

9. In the Define LSP section of the page, enter the name for the LSP in the LSP Name field. TheLSP name can contain only letters, digits, and underscores.

10. Enter a description for the LSP in the LSP Description field, if needed.

TIP: To re-select the ingress and egress, you can click the Reset icon on the topology tool barto cancel all the configurations.

Assigning values to outgoing labelsYou can assign values to outgoing labels on devices along the LSP either manually or automatically.To assign values to outgoing labels manually:


1. After the LSP path is configured, the path list displays the devices along the path in the PathList section.

2. Click the Change Label Value icon in the Operation column of a device.3. In the Change Label Value dialog box that appears, enter the value for the label. Make sure

that the outgoing label specified on a device is the same as the incoming label specified onthe downstream device. The ingress device has no incoming label. The value of a label mustbe an integer. The minimum value is 16 and the maximum value is the maximum static labelvalue supported by device, which varies with device models.

4. Make sure that you have configured labels for all devices along the LSP. Click OK.To assign values to outgoing labels automatically:1. After the LSP path is configured, the path list displays the devices along the path in the Path

List section.2. Click the Pre-Allocate Label button. Valid values are assigned to outgoing labels.3. Click OK.

Checking labels (optional)You can use this function to verify the validity of labels that you have configured manually for thedevices.After you have manually configured labels for all devices along the LSP, click the Check Labelbutton. The system checks whether the labels have already been used on the device. If the labelsare not in use, you can see the icon in the Check Result column. If labels have not been checked,

is displayed in the Check Result column.

Deploying an LSP1. To deploy the LSP immediately, select the Deploy Immediately check box in the Define LSP

section, and then click OK. To deploy the LSP later, you do not need to select the DeployImmediately check box.

2. Click OK.3. To deploy the LSP later, click Service > MPLS Management > LSP Management.4. In the LSP List section of the page, select one or more LSPs that you want to deploy, and then

click the Deploy button. If the deployment is successful, the Normal status appears in theDeployment Status column on the LSP Management page.

NOTE: Synchronize the devices before deployment to get the latest configuration.

Undeploying one or more LSPsYou can undeploy one or more static LSPs whose deployment status is Normal or Undeploymentfailed.To undeploy one or more LSPs:1. Click Service > MPLS Management > LSP Management from the tabular navigation system on

the top of the IMC main page.2. Select one or more static LSPs that you want to undeploy.3. Click the Undeploy button.4. Click OK.

Deleting one or more LSPsYou can delete one or more LSPs at a time. You can only delete LSPs whose deployment status isUndeployed or Deployment failed.To delete one or more LSPs:


1. Click Service > MPLS Management > LSP Management from the tabular navigation system onthe top of the IMC main page.

2. Select one or more LSPs that you want to delete.3. Click the Delete button.4. Click OK.

Auditing LSPsYou can audit the connectivity of LSPs whose deployment status is Normal or Undeployment failed.To audit one or more LSPs:1. Click Service > MPLS Management > LSP Management from the tabular navigation system on

the top of the IMC main page.2. Select one or more LSPs that you want to audit.3. Click the Audit button.

Managing an established static LSPYou can manage an established static LSP, including modifying its description, its LSP configurationinformation, and highlighting its paths and nodes on the MPLS topology. If the deployment statusof an LSP is Undeployed or Deployment failed, you can view the reason for such failures.To manage an LSP:1. Click Service > MPLS Management > LSP Management from the tabular navigation system on


2. Click the Operation icon in the same line as the LSP that you want to modify, as showninFigure 34.

Figure 34 Manage an LSP

3. You can do the following operations:• Click Modify Description to modify description of the LSP.

• Click Modify LSP to modify configurations for the LSP, including paths, outgoing labelvalues, LSP name, and LSP description.

• Click Highlight to highlight all links and nodes of an LSP on the MPLS topology, so thatyou can intuitively know the devices that the LSP traverses. If the LSP is not complete, forexample, some devices are lost, the highlight information may also be incomplete.

• Click Failure Reason to view the reason why an LSP deployment or undeployment hasfailed. You can only view LSPs whose deployment status is Deployment failed orUndeployment failed.

Viewing detailed information about an LSPYou can view detailed information about an LSP, including the topology diagram, path list, pathoutgoing interface, incoming interface, outgoing label, incoming label, and the next hop IP address.


To view detailed information about an LSP:1. Click Service > MPLS Management > LSP Management from the tabular navigation system on

the top of the IMC main page.2. Click an LSP name in the LSP List section of the page.

NOTE: If an LSP is discontinuous, some of the LSP path sequence numbers are not displayed.On the topology, the discontinuous links of the LSP are displayed as red broken lines.

Topology ManagementWith the Topology Management function, you can display the MPLS global network topology,display LSPs between devices, and highlight LSPs.To access the Topology Management function:• Click Service > MPLS Management > Topology Management from the tabular navigation

system on the top of the IMC main page.

MPLS topology tool bar

Figure 35 MPLS topology tool bar

You can use the following tools to view the topology:• Displays the LSP List section on the topology view page, including LSP status and LSP name.

You can also query for existing LSPs by their names.• Allows you to add a link on the topology view.

• Allows you to unhighlight a highlighted link.For more information, see HP Intelligent Management Center Base Platform Administrator Guide.

Using Topology ManagementThe Topology Management function provides you with a visual tool to view the MPLS networkstructure. With the Topology Management function, you can do the following:• Manage links on the topology.

• Manage devices on the topology.

• Deploy LSPs on the topology.For more information about managing links on the topology and managing devices on the topology,see HP Intelligent Management Center Base Platform Administrator Guide.

Highlighting an LSPTo highlight an LSP on the MPLS topology:1. Click Service > MPLS Management > Topology Management from the tabular navigation

system on the top of the IMC main page.2. To the right of the topology, click the LSP List tab.3. Enter part or the full name of the LSP that you want to highlight in the Name field, and then

click Query. All LSPs that match the query criterion are displayed in the LSP List section of thepage.

4. double-click the LSP that you want to highlight in the LSP List section of the page. The regions,devices, and links between the devices associated with the LSP are highlighted on the topology,and other nodes and links are grayed out.


Viewing an LSPYou can use this function to view an LSP on the MPLS topology, and highlight an LSP between twodevices on the MPLS topology.To view an LSP:1. Click Service > MPLS Management > Topology Management from the tabular navigation

system on the top of the IMC main page.2. Use Ctrl with the mouse to select two devices.3. Click the Display LSP List icon on the tool bar. A window pops up, listing all LSPs between

the two devices.4. Select an LSP, and then click OK. The system highlights the selected LSP on the MPLS topology.

Label statisticsWith the Label Statistics function, you can display label usage statistics on devices, including thenumber of static labels being used, number of dynamic labels being used, and the label usagepercentage to see which devices have high label utilization, in order to lighten burden for thesedevices in time. You can also query for a specific device, and view label usage statistics informationabout the device.

Figure 36 Label Statistics page

In Figure 36, the Top 5 Devices by Static Labels Used section displays the top 5 devices with thehighest static label utilization. The Top 5 Devices by Dynamic Labels Used section displays the top5 devices with the highest dynamic label utilization. The y-axis indicates the number of used labels,and the x-axis indicates the device names. To view the label usage information of the device thatranks among the top 5 devices by static labels used or dynamic labels used, click the bar chart ofthe device.The Label Usage Statistics section of the page displays label usage statistics of devices. The followinglist gives information for each title in this section:• Device Name—Indicates the name of the device that uses static label or dynamic label. You

can click the name of the device to see detailed information about this device.• Static Labels Used—Indicates the number of static labels used by the device. You can click a

number to see the label usage information in the Label Usage Information section. In thissection, you can see label value in the Label column, label type in the Label Type column, andthe LSP using this label in the Label Used by column. Click the LSP name in the Label Used bycolumn to see detailed information about the LSP.


• Dynamic Labels Used—Indicates the number of dynamic labels used by the device. You canclick a number to see the label usage information in the Label Usage Information section. Inthis section, you can see label value in the Label column, label type in the Label Type column,and the LSP using this label in the Label Used by column. Click the LSP name in the Label Usedby column to see detailed information about the LSP.

• Label Usage Percent—Indicates the percent of label usage.

Querying label usage statistics for a deviceTo query label usage statistics for a device:1. Click Service > MPLS Management > Label Statistics from the tabular navigation system on

the top of the IMC main page.2. In the Query Device Label Usage Statistics section of the page, enter part or the full name of

the device in the Device Name field, and then click Query. The label statistics of the deviceare displayed in the Label Usage Statistics section.

3. To clear the query criterion and display the label statistics of all devices, click Reset.

Viewing device label statisticsTo view device label statistics:1. Query label usage statistics for a device. For more information, see "Querying label usage

statistics for a device."2. Click a number in the Static Labels Used column or Dynamic Labels Used column of the device

to view the device label usage details, including the LSP that is using the label.

TIP: To view the label usage information of the device that ranks among the top 5 devices bystatic labels used or dynamic labels used, click the bar chart of the device in the Top 5 Devices byStatic Labels Used section or the Top 5 Devices by Dynamic Labels Used section.

LSP Traffic StatisticsThis function collects and displays the current and long-term LSP traffic statistics. With the statistics,you can observe the LSP traffic trends, learn the LSP running status and performance status, findthe bottleneck that impacts the performance, and thus, make better plans for adjusting the existingMPLS network.The traffic monitoring function allows you to set LSP traffic alert thresholds, set the traffic monitoringstatus, and view LSP traffic reports.With the LSP Traffic Statistics function, you can collect and display LSP traffic statistics, set LSPtraffic thresholds, and generate LSP outgoing traffic statistics reports from multiple perspectives.

Traffic monitoring informationThe TopN LSPs by Outgoing Traffic section provides a bar chart to display the topN (N<=5) LSPsby outgoing traffic. The LSP Monitoring Status Chart section provides a pie chart to display thelatest statistics on the number of monitored and unmonitored LSPs. The LSP traffic topN bar chartand the pie chart both support data drilling. You can click the bar chart or pie chart to view detailedLSP traffic and monitoring information.To view traffic monitoring information:1. Click Service > MPLS Management > LSP Traffic Statistics from the tabular navigation system

on the top of the IMC main page.2. Click a bar in the TopN LSPs by Outgoing Traffic section to view the traffic report of an LSP.3. Click a sector in the LSP Monitoring Status Chart section to enter the LSP traffic monitoring

configuration page.


Setting default thresholdsYou can use this function to set default thresholds for outgoing traffic. If the traffic exceeds athreshold, the system generates the corresponding alert information.To set default thresholds:1. Click Service > MPLS Management > LSP Traffic Statistics from the tabular navigation system

on the top of the IMC main page.2. Click Default Threshold Settings in the left navigation tree.

3. Click the Modify icon to display the Modify Traffic Monitoring Thresholds page, as shownin Figure 37.

Figure 37 Modify Traffic Monitoring Thresholds page

4. Adjust the parameters.Thresholds include level-1 alert threshold and level-2 alert threshold. You can set the level-2alert threshold only when the level-1 alert threshold is valid. If the traffic exceeds a threshold,the system generates the corresponding alert information. The level-2 alert severity must behigher than the level-1 alert severity. If the traffic rate drops from the level-2 alert threshold tothe level-1 alert threshold, the system generates a recovery message.

Setting LSP traffic monitoringThe LSP Traffic Monitoring page displays all LSPs that can be monitored in the system, LSP type,and monitoring status. You can monitor or unmonitor LSPs. LSP traffic reports are generated formonitored LSPs only.To query for one or more LSPs for LSP traffic monitoring:1. Click Service > MPLS Management > LSP Traffic Statistics from the tabular navigation system

on the top of the IMC main page.2. Click LSP Traffic Monitoring in the left navigation tree.3. Enter query conditions in the Query LSPs pane:

• LSP Name—Indicates the LSP name.

• Audit Status—Indicates the audit status of the LSP. Values include Up, Down, Unknown,Auditing, Testing, Dormant, Not Present, and Lower Layer Down.

• Monitoring Status—Indicates the LSP is monitored or not monitored. Values includeMonitored and Not monitored.

• LSP Type—Indicates the type of the LSP. Values include Static, Dynamic and CR-LSP.MPLS Management supports fuzzy query function, which allows you to specify intact or partialquery condition.

4. Click Query. All LSPs matching this criteria are displayed in the LSP List section of the page.


5. Select the LSPs whose monitoring status is Not Monitored, and then click Monitor to monitorthe selected LSPs, or select LSPs whose monitoring status is Monitored, and then click Unmonitorto unmonitor the selected LSPs.

6. To clear the query criteria and display all LSPs, click Reset.

NOTE: An LSP that can be monitored refers to an LSP that has been successfully deployed. TheLSP Traffic Monitoring page only displays the deployed LSPs with the auditing status of UP.

LSP traffic reportsThe MPLS Management component supports the query and export of LSP traffic reports. You canview the traffic data of each LSP by viewing the LSP traffic reports. LSP traffic reports display trafficperformances and statistics for an LSP in forms of a table, line chart, and bar chart. The default isline chart.To query LSP traffic reports:1. Click Service > MPLS Management > LSP Traffic Statistics from the tabular navigation system

on the top of the IMC main page.2. Click LSP Traffic Reports in the left navigation tree.3. Enter query conditions In the Query Devices pane:

• LSP Name—Indicates the name of the LSP.

• LSP Type—Indicate the type of the LSP. Values include All, Static, Dynamic and CR-LSP.MPLS Management supports fuzzy query function, which allows you to specify intact or partialquery condition.

4. Click Query. All LSPs matching this query criteria are displayed in the LSP Traffic List section.The following list gives information for each item in the LSP Traffic List:• LSP Name—Indicates the name of the LSP.

• LSP Type—Indicate the type of the LSP.

• Outgoing Traffic—Indicates the outgoing traffic in bytes per second.

• Operation—Indicates the operation that you can perform on this page.

5. Click the Details icon .6. In the Query Criteria section, select Last 1 hour, This day, This week, This month, This year,

or Customize from the Time Range list.• Last 1 hour—Specifies a time range of the recent hour. For example, if you select Last 1

hour and the current time is 15:30:30 2006–12–24, the system generates a reportdisplaying the performance data converged during 14:30:30 2006–12–24 to 15:30:302006–12–24. The system generates a 5–minute interval data report.

• This day—Specifies a time range from 00:00:00 of the current day to the current time.For example, if you select This day and the current time is 15:30:30 2006–12–24, thesystem generates a report displaying the performance data converged during 00:00:002006–12–24 to 15:30:30 2006–12–24. The system generates a 5–minute interval datareport.

• This week—Specifies a time range from 00:00:00 of this Sunday to the current time. Forexample, if you select This week and the current time is 15:30:30 Friday 2006–12–22,the system generates a report displaying the performance data converged during 00:00:00Sunday 2006–12–17 to 15:30:30 Friday 2006–12–22. The system generates an hourlyreport.

• This month—Specifies a time range from 00:00:00 of the first day of the current monthto the current time. For example, if you select This month and the current time is 15:30:302006–12–24, the system generates a report displaying the performance data converged


during 00:00:00 2006–12–1 to 15:30:30 2006–12–24. The system generates an hourlyreport.

• This year—Specifies a time range from 00:00:00 January 1st of the current year to thecurrent time. For example, if you select This year and the current time is 15:30:302006–12–24, the system generates a report displaying the performance data convergedduring 00:00:00 2006–01–01 to 15:30:30 2006–12–24. The system generates a dailyreport.

• Customize—Customizes a time range. The system generates a report displaying theperformance data converged during the customized time range.

7. Select a display mode in the Outgoing Traffic section.The available modes are:• Table—Displays the data in a table.

• Line Chart—Displays the data in a line chart.

• Bar Chart—Displays the data in a bar chart.

• Sampling Point—Displays every sampling point in the line chart. To hide the samplingpoints, click Sampling Point again. You can click the Sampling Point to display thesampling points only when you display data in a line chart.

The following list gives information for each title item:• Monitored Object—Indicates the LSP that is being monitored.

• Current Value—Indicates the current outgoing traffic value within time range.

• Min. Value—Indicates the minimum outgoing traffic value that has been sampled withintime range.

• Max. Value—Indicates the maximum outgoing traffic value that has been sampled withintime range.

• Average Value—Indicates the average outgoing traffic value within time range.

• Min. Value Sampled at—Indicates the time when the minimum outgoing traffic value wassampled within time range.

• Max. Value Sampled at—Indicates the time when the maximum outgoing traffic valuewas sampled within time range.

• Valid Sampling Points—Indicates the number of valid sampling points within time range.

8. On the current page, you can also export the report to different formats: Excel, PDF, HTML,and TXT.

NOTE: The system only saves data of the recent year.Double hyphens in the data table indicate that the system failed to collect any performance data.


5 Using L2VPN ManagementL2VPN Management allows for building and managing VPLS, VLL, and PBB Layer 2 VPNs. L2VPNManagement supports both LDP and BGP signaling for VPLS VPN, supports LDP signaling for VLLVPN, and supports PBB + VPLS VPN.L2VPN Management brings the following benefits:

• Simplified VPN deployment—L2VPN Management provides wizards for deploying VPLS, VLL,and PBB Layer 2 VPNs, simplifying your configurations.

• Auto discovery—L2VPN Management can automatically discover existing VPNs and add theVPNs into IMC. You can add/delete PEs and ACs for the discovered VPNs.

• VPN monitoring—L2VPN Management provides alarms, audit state, and configurationinformation. The alarms help you troubleshoot device problems. The audit state informationshows the connectivity of VPN links. An audit operation can be performed one time orperiodically. The configuration information shows detailed VPN settings, including the VSI ID,I-SID, PW ID, VPN type, and B-VLAN.

• VPN topology—L2VPN Management shows a topology for each VPN where you can performoperations such as viewing VPN information, ACs, and PWs, deploying and undeployingVPNs, and auditing connectivity for a whole VPN.

Basic VPN concepts

VPLS overviewVirtual Private LAN Service (VPLS), also called Transparent LAN Service (TLS) or Virutal PrivateSwitched Network Service, can deliver a point-to-multipoint Layer 2 VPN (L2VPN) service overpublic networks. With VPLS, geographically-dispersed sites can interconnect and communicateover metropolitan area network (MAN) or wide area network (WAN) as if they were on the sameLocal Area Network (LAN). VPLS supports multipoint services, rather than the point-to-point servicesthat traditional VPN supports. With VPLS, service providers can create on the PEs a series of virtualswitches for customers, allowing customers to build their LANs across the MAN or WAN.

Basic concepts of VPLS

• CE (Customer Edge)— Customer edge device that is directly connected with the service providernetwork.

• PE (Provider Edge)—Provider edge device that connects one or more CEs to the service providernetwork, mainly for access to VPN services

• VSI (Virtual Switch Instance)—Virtual switch instance that maps actual VPLS access links tovirtual links. As shown in the above figure, to ensure connectivity between devices, PE 1 andPE 2 are configured with a VSI respectively, and the VSI ID is 1.

• PW (Pseudo Wire)—A pseudo wire is the bidirectional virtual connection between two VSIs.A pseudo wire consists of two unidirectional virtual circuits (VCs).

• AC (Attachment Circuit)—Attachment circuit that connects a CE to a PE. It can use physicalinterfaces or virtual interfaces.

• Tunnel—A tunnel, usually an MPLS tunnel, used to carry one or more PWs. It is a direct channelbetween a local PE and the peer PE for transparent transmission in-between.

A typical H-VPLS network involves the following basic concepts:

116 Using L2VPN Management

• UPE (User Facing-Provider Edge)— User facing provider edge device that functions as the useraccess convergence device.

• NPE (Network Provider Edge)—Network provider edge device that functions as the networkcore PE. An NPE resides at the edge of a VPLS network core domain and provides transparentVPLS transport services between core networks.

• U-PW—PW link between a UPE and an NPE.

• N-PW—PW link between two NPEs.

VPLS VPN types

• LDP VPN—Uses the Label Distribution Protocol (LDP) to establish virtual circuits by establishingpoint-to-point sessions between a pair of PEs.

• BGP VPN—Uses the Border Gateway Protocol (BGP) to establish signaling sessions throughroute reflectors (RRs) and supports networking across ASs.

Operation of VPLSVPLS operation includes these elements:• L2-pdu—Data link layer packet

• Dmac—MAC address of the next hop device

• Smac—MAC address of the local device

• L—Public network label

• V—Private network label

• L'—Public network label after the packet is forwarded along the LSPData forwarding procedure:1. A PE receives a data packet from a CE through the AC. According to the VSI, the PE pushes

its own MAC address, the MAC address of the next hop, the public network label, and theprivate network label into the packet. Then the PE forwards the packet to the core networkaccording to the address of the next hop.

2. After receiving the packet, the core network encapsulates the packet with the new publicnetwork label and the MAC address of the new next hop device, and then forwards the packetto the specified PE accordingly.

3. The PE sends the packet to the right CE through the AC according to the private network label.

VLL overviewVLL (Virtual Leased Line): VLL provides point-to-point L2VPN services over the public network. WithVLL, two sites can communicate as if they were directly connected. VLL is a form of MPLS L2VPN.It uses inner labels to identify virtual lines (Layer 2 tunnels), hereinafter referred to as virtual circuits(VCs), and uses outer labels to identify public tunnels. The network devices of the service providerdo not need to maintain any Layer 2 information but perform MPLS forwarding on the publicneworks based on MPLS labels. In VLL, a Forwarding Equivalence Class (FEC) is about the VCindentifier and some Layer 2 information.

Basic concepts of VLLWith the existing technologies, VLL can be implemented mainly in two methods, which use differentsignaling protocols to exchange VC information. One method is called Martini (the L2VPNManagement only support this method). The Martini method uses a standard two-layer label stack.The inner labels (VC labels) are exchanged through the extended LDP. The Martini draft extendsthe standard LDP, adding a new FEC type, the VC FEC, for exchanging VC labels. A VC FECidentifies a VC by VC Type and VC ID. VC Type indicates the link layer encapsulation type and

Basic VPN concepts 117

VC ID uniquely indentifies a VC of the same type on a PE. The PEs that connect two CEs switchVC labels through LDP and bind the corresponding CEs by the VC ID. A VC between the two CEsare then established and the two CEs can transport Layer 2 data over the VC. The Martini methoddoes not provide the local switching function. Outer labels is used to transport VC data over theservice provider network. Because PEs can identify data of different VCs by inner label, multipleVCs can share the public tunnel.

PBB overviewPBB meets the Metro Ethernet Network (MEN) requirements. In the MEN service hierarchy model,PBB is at the carrier level, used to establish MAC tunnels to separate services of different customerson the backbone. A network employing 802.1ah is called a Provider Backbone Bridge Network(PBBN).

Basic concepts of PBBIn a typical PBBN, the two types of devices are:• BEB (Backbone Edge Bridge)—Like a PE in an MPLS network. It performs MAC-in-MAC

encapsulation for the incoming packets and then delivers the encapsulated packets tosubsequent devices, which forwards the packets according to the B-MAC and B-VID. It alsode-encapsulates the received MAC-in-MAC packets to standard Ethernet packets and thenlooks up the forwarding table and sends the packets from the corresponding outgoinginterfaces.

• BCB (Backbone Core Bridge)—Like a P device in an MPLS network. It forwards the receivedMAC-in-MAC packets according to the outer B-MAC and B-VID. A BCB only performs packetbridging, learning the MAC addresses on the backbone. It does not need to learn the hugenumber of MAC addresses in the customer networks. This reduces the network deploymentexpenses and provides better expansibility for the PBBN.

TerminologyThis section clarifies some VPN operations and concepts.

• Layer VPN—L2VPN Management provides basic and detailed information for a Layer VPN.Basic information includes the VPN name, contact, description, and audit interval. Detailedinformation includes PEs, ACs, alarms, and audit information besides basic information.

• Add and Deploy—An Add operation adds a configuration task on L2VPN Management butit does not deploy the configuration task to devices. Therefore, an Add operation does notchange the network. You can view and modify added configuration tasks only on L2VPNManagement. A Deploy operation deploys a configuration task to devices and thus changesthe network. You can also add and then deploy a configuration task.

• Delete and Undeploy—A Delete operation deletes the selected configuration from L2VPNManagement but not from the network. For example, after you delete a VPN, the VPN stillexists on the network. You can re-add this VPN to L2VPN Management through auto discovery.An Undeploy operation deletes the selected configuration from the network. For example,after you undeploy a VPN, the VPN is removed from the network, and you cannot re-add thisVPN to L2VPN Management through auto discovery.

• Modify—A Modify operation can only change information configured on L2VPN Management,such as the VPN name, contact, description, audit interval, VCE label, and VCE MAC address.It cannot change information on physical CEs. L2VPN Management can only read informationfrom physical CEs.

Using L2VPN Management with non-BGP protocolsThis section provides a quick start for deploying and managing L2VPNs using non-BGP protocols,including LDP VPLS, VLL, PBB.


Figure 38 Quick start

As shown in Figure 38, the quick start includes the following steps.1. Make preparations:

• Import PE, BEB, and CE devices into IMC Platform, and configure correct SNMP parametersfor the devices and IMC Platform. For details, see HP IMC Platform Administrator Guide.

• To build VPLS or VLL VPNs, you must enable MPLS, L2VPN, and MPLS L2VPN on PEs. Tobuild PBB VPNs, you must enable L2VPN on BEBs. For details, see the correspondingconfiguration guides and command references.

2. Import devices into L2VPN Management:• For VPLS and VLL VPNs, import PEs. For PBB VPNs, import BEBs. For details, see “Importing

PE devices.”• Import physical CEs. For details, see "Importing CE devices."

• Import virtual CEs (VCEs). For details, see "Adding/Modifying a VCE."3. Add VPNs:

• Add existing VPNs to L2VPN Management through auto discovery. For details, see"Adding a VPN" or "Automatic discovery.”

• Deploy new VPNs. For details, see "Deploying VPNs."4. Maintain VPNs

You can view VPN topology, alarms, and audit information, and modify or undeploy ACs,PWs, PEs, and CEs.

The following content will introduce how to use L2VPN Management deployed non-BGP protocol.

Managing VPN resourcesVPN resources include VPNs services and Attachment Circuit (ACs). A VPN service is a Layer 2VPN. An AC is a link that connects a PE to a CE. L2VPN Management provides a VPN list andan AC list for you to manage all VPNs and ACs.

Managing VPNsThe VPN list shows all VPN services, including VPLS, VLL, PBB, and VPLS+PBB VPN services. Youcan add, modify, delete, and audit VPN services from the VPN list.

Viewing the VPN list1. Click the Service tab.

Managing VPN resources 119

2. From the navigation tree, select L2VPN Manager > VPN Resources > VPN List.VPN List contents

• Status—State of the VPN. Options are Critical, Major, Minor, Warning, Normal, Unknown,and Unmanaged.

• VSI Admin Status—State of the VSI, Enabled or Disabled.

• VPN name—Name of the VPN. You can click a VPN name to view details about thatVPN.

• VSI ID—VSI ID for a VLL or VPLS VPN.

• I-SID—I-SID for a PBB VPN.

• PW ID—PW ID for a VLL or VPLS VPN.

• VPN Type—VPN type. Options are VPLS, VLL, PBB, and VPLS+PBB.

• B-VLAN—B-VLAN for a PBB or VPLS+PBB VPN.

• Topology—Provides a Topology link for you to view L2VPN topology.

• Audit Time—Time when the last VPN connectivity audit was performed, in the formatYYYY-MM-DD hh:mm:ss.

• Audit Result—Result of the last VPN connectivity audit. Options are Unaudited, Normal,Auditing, Unknown, Unconnected, and Error. If the result is Unconnected, you can clickthe Unconnected link to view the cause.

• Modify—Provides a Modify icon for you to modify basic settings for a VPN.3. Click Refresh to view the latest VPN list.

Querying a VPN1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Resources > VPN List.

Enter or select one or more of the following query criteria:

• VPN name—Enter the name of a VPN. This field supports fuzzy matching.

• I-SID—Enter the I-SID of a PBB VPN. This field supports fuzzy matching.

• VPN Type—Select a VPN type. Options are VPLS, VLL, PBB, and VPLS+PBB.

• Audit Result—Select an audit result. Options are Unaudited, Normal, Auditing, Unknown,Unconnected, and Error.

• VSI ID—Enter the VSI ID of a VLL or VPLS VPN. This field supports fuzzy matching.

• PW ID—Enter the PW ID of a VPN. This field supports fuzzy matching.

• VPN Status—Select a VPN state. Options are All, Critical, Major, Minor, Warning, Normal,Unknown, and Unmanaged.

• VSI Admin Status—Select a VSI state. Options are All, Enabled, and Disabled.3. Click Query.The VPN list displays all the matching VPNs. To clear the query results, click Reset.

Adding a VPNThis function supports adding VPLS, VLL, and PBB VPNs.To add a VPN:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Resources > VPN List.


3. Click Add.4. Click one of the following options.

• Deploy VPLS VPN. For information about deploying a VPLS VPN, see "Deploying a VPLSVPN.”

• Deploy VLL VPN. For information about deploying a VLL VPN, see "Deploying a VLL VPN."

• Deploy PBB VPN. For information about deploying a PBB VPN, see "Deploying a PBBVPN."

Modifying basic VPN settingsL2VPN Management provides basic and advanced VPN settings. Basic settings include the VPNname, contact, description, and audit interval. Advanced settings include information about PEs,ACs, VLAN mappings, and alarms.To modify basic VPN settings:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Resources > VPN List.

3. Click the Modify icon of the target VPN.4. Modify the following settings:

• VPN Name—Enter a new VPN name.

• Contact—Enter a new contact.

• Description—Enter a new description.

• Audit Interval (in hours)—Enter a new audit interval in the range of 0 to 24. An auditinterval of 0 disables audit function.

5. Click OK.

Undeploying VPNsYou can undeploy an entire VPN or some devices and links in a VPN.To undeploy VPNs:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Resources > VPN List.3. Select one or more VPNs from the VPN list.4. Click More Operations.5. Select Undeployment.

For more information, see "Undeploying VPNs."

Enabling a VSIYou can undeploy an entire VPN or some devices and links in a VPN.To undeploy VPNs:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Resources > VPN List.3. Select one or more VPNs from the VPN list.4. Click More Operations.5. Select Enable VSI.6. Click OK in the popup window.


Deleting VPNsThis task deletes VPNs from L2VPN Management but the deleted VPNs still exist in the network.You can perform VPN auto-discovery to add the deleted VPNs to L2VPN Management. To deletea VPN from the network, you need to undeploy the VPN.To delete a VPN:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Resources > VPN List.3. Select one or more VPNs from the VPN list.4. Click Delete.5. Click OK in the popup window.

Auditing VPNsTo audit a VPN:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Resources > VPN List.3. Select one or more VPNs from the VPN list.4. Click Audit.5. After a while, click Refresh to view the audit result.

Managing ACsThe AC list shows all ACs. You can view, query, and delete ACs from the AC list.

Viewing the AC listThis function allows you to view information about all ACs recorded in the L2VPN Manager, andquery or delete specific AC records.1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Resources > AC List.

AC list contents

• PE Name—Name of the PE. You can click a PE name to view details about that PE.

• PE Interface Description—Displays the PE's interface connected to the CE.

• CE Name—Name of the CE. You can click a CE name to view details about that CE.

• Attached VPN—VPN to which the AC belongs.

• Details—Provides a Details icon for you to view details about the AC.3. Click Refresh to view the latest AC list.

Querying ACsThis function allows you to view information about all ACs recorded in the L2VPN Manager, andquery or delete specific AC records.1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Resources > AC List.3. Enter or select the following query criteria:

• PE Name—Enter a PE name. This field supports fuzzy matching.

• Attached VPN—Enter a VPN name. This field supports fuzzy matching.

• CE Name—Enter a CE name. This field supports fuzzy matching.4. Click Query.


The VPN list displays all the matching ACs. To clear the query results, click Reset.

Deleting ACsThis task deletes ACs from L2VPN Management but the deleted ACs still exist in the network.1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Resources > AC List.3. Select ACs from the AC list.4. Click Delete.5. Click OK in the popup window.

Deploying VPNsThe section describes tasks for deploying and undeploying LDP-based VPLS and VLL VPNs andPBB VPNs. You can create and deploy a VPN by following the deployment wizard, and view thedeployment results.

Deploying a VPLS VPNYou can deploy a new VPLS VPN or deploy new ACs or PWs for an existing VPLS VPN. HierarchicalVPLS is supported.To deploy a VPLS VPN:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Deployment > Deploy VPLSs.

Figure 39 shows the wizards for deploying a VPLS VPN and a Hierarchical VPLS VPN.

Figure 39 Wizards for deploying VPLS VPN and Hierarchical VPLS VPN

3. Complete the configurations in the wizards.The following sections describe these configurations.

Defining VPN1. Configure the following settings:

• PE Type—Select PE or Hierarchical PE. To configure a PE, see "Configuring PEs." Toconfigure a hierarchical PE, see "Configuring NPEs".

• VPN Operation Type—Select Add VPN or Select VPN. If you select Select VPN, you mustenter the name of an existing VPN. The system automatically fills in the VSI ID, PWTransport Mode, and Audit Interval, which cannot be modified.

• VPN Name—Enter a name for the VPN.

• VSI ID—Enter a VSI ID or use the default VSI ID.

• PW Transport Mode—Select VLAN or Ethernet.

• Audit Interval (in hours)—Enter an audit interval, which is an integer in the range of 0 to24, or use the default audit interval. A value of 0 disables audit.

• Description—Enter a description for the VPN.

• Contact—nter a contact. The default contact is the current operator.

Deploying VPNs 123

2. Click OK.

Configuring PEs1. Add ACs:

a. Click Add under AC List.b. Select the PE's interface that connects to the CE, and click OK.

If the selected interface is a Layer 3 interface, perform step c. If the selected interface isa Layer 2 interface, perform step d.

c. Under Config UNI Interface, select an access type.d. Under Config UNI Interface, enter the service instance, bandwidth, encapsulation VLAN,

and select the encapsulation type and access type.e. Click OK.f. Repeat the above steps to add more ACs.

2. Add PEs:A PE configured when you add an AC is automatically added to the PE Device List. You canalso manually add a PE as follows:a. Click Add under PE Device List.b. Select one or more PEs and click OK.

3. Select a tunnel policy for each PW in the PW List.Tunnel policies include default, use GRE tunnel first, and create and use GRE tunnel.

4. Configure VLAN mappings:The Configure VLAN Mapping option exists if you selected a physical CE when you addedan AC. It does not exist if you selected only VCEs.

5. Click Next.The CE Configuration page appears if you selected the Configure VLAN Mapping option, orthe Configuration Summary page appears if you did not select the Configure VLAN Mappingoption.

Configuring NPEs1. Add ACs:

a. Click Add under AC List.b. Select the NPE's interface that connects to the CE, and click OK.




2. Add NPEs:An NPE configured when you add an AC is automatically added to the NPE Device List. Youcan also manually add an NPE as follows:a. Click Add under NPE Device List.b. Select one or more NPEs and click OK.

3. Click Next to enter the UPE Configuration page.


Configuring UPEs1. Add ACs:





2. Add UPEs:A UPE configured when you add an AC is automatically added to the UPE Device List. Youcan also manually add a UPE as follows:a. Click Add under UPE Device List.b. Select one or more UPEs and click OK.

3. Specify the main/backup NPE for UPEs:a. Select one or more UPEs from the UPE Device List, and click Main NPE or Backup NPE.b. Select an NPE in the popup window.c. Click OK.

4. Select a tunnel policy for each PW from the Tunnel Policy column in the PW List.Tunnel policies include default, user GRE tunnel first, and create and use GRE tunnel.



Configuring CEs1. Click Add under VLANMapping List, and configure the following settings in the popup window:

• Device Label—Select a device label.

• Interface Description—Enter a description for the interface.

• VLAN Mappings—Enter a CVLAN-SVLAN mapping.2. Click OK.

You can repeat the above steps to add more VLAN mappings.3. Click Next to enter the Configuration Summary page.

Deploying the VPLS VPN1. Verify the VPN, PE, and CE settings in the Configuration Summary page.2. Select Deploy Immediately.3. Click OK to view the deployment result.IMC deploys your settings to devices. If you did not select Deploy Immediately, IMC only generatesVPLS VPN information and commands, but does not deploy the settings to devices.

Deploying VPNs 125

Deploying a VLL VPN1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Deployment > Deploy VLLs.3. Complete the configurations in the Define VPN, Local PE Configuration, Remote PE

Configuration, and Configuration Summary pages.The following sections describe these configurations.



• PW ID—Enter a PW ID or use the default PW ID.


• Tunnel Policy—Select a tunnel policy. Options are default, use GRE tunnel first, and createand use GRE tunnel.



• Contact—Enter a contact. The default contact is the current operator.2. Click Next to enter the Local PE Configuration page.

Configuring the local PE1. Configure the following settings:

• UNI Interface—Click Select and select the PE' interface that connects to the local CE.If the selected interface is a Layer 3 interface, click OK and select a CE. If the selected interfaceis a Layer 2 interface, click OK and complete the following settings:

• Service Instance—Enter the ID of the service instance.

• Bandwidth (Mbps)—Enter the maximum bandwidth for the AC.

• Encap Type—Select an encapsulation type. Options are S-VID, S-VID Only Tagged,Port-based, Tagged, and Untagged.

• Encapsulation VLAN—Enter a VLAN ID or VLAN ID range.

• Access Type—Select VLAN or Ethernet.

• CE Device—Click Select and select a CE or VCE. A VCE is selected by default.

• UNI Interface—Click Select and select the local PE' interface that connects to the localCE.

• CE Device—Click Select and select a CE or VCE. A VCE is selected by default.2. Click Next to enter the Remote PE Configuration page


Configuring the remote PE1. Configure the following settings:

• UNI Interface—Click Select and select the PE' interface that connects to the remote CE.If the selected interface is a Layer 3 interface, click OK and select a CE. If the selected interfaceis a Layer 2 interface, click OK and complete the following settings:

• Service Instance—Enter the ID of the service instance.

• Bandwidth (Mbps)—Enter the maximum bandwidth for the AC.

• Encap Type—Select an encapsulation type. Options are S-VID, S-VID Only Tagged,Port-based, Tagged, and Untagged.

• Encapsulation VLAN—Enter a VLAN ID or VLAN ID range.

• Access Type—Select VLAN or Ethernet.

• CE Device—Click Select and select a CE or VCE. A VCE is selected by default.2. Click Next to enter the Configuration Summary page.

Deploying the VLL VPN1. Verify the VPN information and device settings in the Configuration Summary page.2. Select Deploy Immediately.3. Click OK to view the deployment result.IMC deploys your settings to devices. If you did not select Deploy Immediately, IMC only generatesVLL VPN information and commands, but does not deploy the settings to devices.

Deploying a PBB VPNYou can deploy a new PBB VPN or deploy new ACs or PWs for an existing PBB VPN.To deploy a PBB VPN:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Deployment > Deploy PBBs.3. Complete the configurations in the Define VPN, PE Configuration, CE Configuration, and

Configuration Summary pages.The following sections describe these configurations.


• VPN Operation Type—Select Add VPN or Select VPN. If you select Select VPN, you mustenter the name of an existing VPN. The system automatically fills in the I-SID, B-VLAN,PW Transport Mode, and Audit Interval, which cannot be modified.


• I-SID—Enter an I-SID or use the default I-SID. An I-SID uniquely identifies a PBB VSI.

• B-VLAN—Enter a B-VLAN ID or use the default B-VLAN ID. The B-VLAN ID is used toforward PBB packets over the PBB backbone.




• Contact—Enter a contact. The default contact is the current operator.2. Click Next to enter the PE Configuration page.

Deploying VPNs 127

Configuring PEs1. Add ACs:



c. Under Config UNI Interface, select an access type.d. Under Configure Interface, enter the service instance, bandwidth, encapsulation VLAN,

and select the encapsulation type, access type, and CE.e. Click OK.f. Repeat the above steps to add more ACs.

2. Add PEs:A PE configured when you add an AC is automatically added to the PE Device List. You canalso manually add a PE as follows:a. Click Add under PE Device List.b. Select one or more PEs and click OK.

3. Configure NNI interfaces:a. Click the Tunnel policies include default, use GRE tunnel first, and create and use GRE

tunnel. link in the PE Device List.b. Select one or more interfaces and click OK.Tunnel policies include default, use GRE tunnel first, and create and use GRE tunnel.



Configuring CEs1. Click Add under VLANMapping List, and configure the following settings in the popup window:

• Device Label—Select a device label.

• Interface Description—Enter a description for the interface.

• VLAN Mappings—Enter a CVLAN-SVLAN mapping.2. Click OK.

You can repeat the above steps to add more VLAN mappings.3. Click Next to enter the Configuration Summary page.

Deploying the PBB VPN1. Verify the VPN, PE, and CE settings in the Configuration Summary page.2. Select Deploy Immediately.3. Click OK to view the deployment result.

IMC deploys your settings to devices. If you did not select Deploy Immediately, IMC onlygenerates VPLS VPN information and commands, but does not deploy the settings to devices.


Undeploying VPNsYou can undeploy a VPN, or the PEs and ACs of a VPN from the network.

Undeploying a VPN1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Deployment > Undeploy.3. Click Select to select a VPN.4. Select Undeploy VPN from the Operation list.5. Click Next.6. Verify the VPN settings on the Configuration Summary page.7. Select Also Delete VPN to delete the VPN information.

If you do not select Also Delete VPN, the system will keep the VPN information.8. Click OK to view the undeployment result.

Undeploying PEs1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Deployment > Undeploy.3. Click Select to select a VPN.4. Select Undeploy PE from the Operation list.5. Click Next.6. Click Add under PE List.7. Select one or more PEs to be undeployed, and click OK.

To delete selected PEs, click Delete under PE List, select one or more PEs, and click OK.8. Click Next.9. Verify the VPN settings on the Configuration Summary page.10. Click OK to view the undeployment result.

Undeploying ACs1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Deployment > Undeploy.3. Click Select to select a VPN.4. Select Undeploy AC from the Operation list.5. Click Next.6. Click Add under AC List.7. Select one or more ACs to be undeployed, and click OK.

To delete selected ACs, click Delete under AC List, select one or more ACs, and click OK.8. Click Next.9. Verify the VPN settings on the Configuration Summary page.10. Click OK to view the undeployment result.

Managing deployment tasksL2VPN Management provides a task list for you to manage all deployment tasks. You can viewtask status, re-deploy a failed task, deploy multiple tasks, and delete obsolete tasks.

Viewing the deployment task list1. Click the Service tab.

Deploying VPNs 129

2. From the navigation tree, select L2VPN Manager > VPN Deployment > Task List.Deployment Task List contents• Deployment Status—Displays the state of the task. Options include Success, Undeployed,

Being Applied, and Failure.• VPN Name—Name of the VPN.

• VPN Type—Type of the VPN. Options include VPLS, VLL, and PBB.

• Operation Type—Operation type for the VPN. Options include Add VPN, Modify VPN,and Undploy VPN.

• Performed At—Shows the time when the task will be deployed, in the format ofYYYY-MM-DD hh:mm:ss.

• Operation—Provides links for you to view details about task deployment, modify the task,and view the reason for a deployment failure.

3. Click Refresh to view the latest task list.

Querying deployment tasks1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Deployment > Task List.3. Enter the following query criteria under Query Deployment Task:

• VPN Name—Enter a VPN name.

• VPN Type—Select a VPN type. Options include All, VPLS, VLL, PBB, and VPLS+PBB.

• Deployment Status—Select a deployment status. Options include All, Success, Undeployed,Being Applied, and Failure.

• Operation Type—Select an operation type. Options include All, Add VPN, Modify VPN,and Undploy VPN.

4. Click Query.The Deployment Task List shows the matching tasks. To clear the query results, click Reset.

Performing deployment tasks1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Deployment > Task List.3. Select the tasks to be deployed.4. Click Deploy.5. Click OK in the popup window.The Deployment Status column shows the deployment result. If the deployment fails, the Failure

icon appears. You can click this icon to view the commands failed to deploy.

Deleting deployment tasks1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Deployment > Task List.3. Select the tasks to be deleted.4. Click Delete.5. Click OK in the popup window.

VPN devicesVPN devices include PEs and CEs in MPLS Layer 2 VPNs. A PE provides VPN access by translatingdata link layer frames to Layer 2 VPN packets. A CE only needs to establish a link layer connection


with a PE. You can import, synchronize, view, and query PEs and CEs. In addition, you can createnon-managed CEs (or called VCEs) to represent CEs that cannot be managed by L2VPNManagement.

PE devicesThe first step to deploy a VPN is to import PEs to L2VPN Management. Then, you can synchronizeand delete PEs, and view VPN information on the PEs. To enhance management, you can use theconfiguration comparison function to discover configuration changes on the PEs.

Viewing PE devices1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > PE Devices.

The PE Devices page displays all PE devices.PE Devices contents

• Status—Alarm state of the device. Options are Critical, Major, Minor, Warning, Normal,Unknown, and Unmanaged.

• Device Label—Label and IP address of the device. Click the device label link to view itsdetails.

• LSR ID—LSR ID of the PE device. An LSR ID uniquely identifies an LSR in an MPLS network.

• Last Synchronization Time—Time when the last synchronization occurred, in the formatYYYY-MM-DD hh:mm:ss.

• Synchronization Status—Synchronization state of the PE. Options are Synchronizing,Success, or Failure. When the synchronization fails, click the Failure link to view thecauses in the prompt box that appears.

• Config Comparison—Configuration comparison results. Options are Same Config andDifferent Config. When the synchronization begins, L2VPN Management compares thePE's configuration with the baseline configuration. When they are different, you can clickthe Different Config link to view the differences in the configuration comparison resultpage.

• Details—Click the Details icon to view the LDP, PBB, VLL, and GRE tunnel informationfor the device in the page for the device's VPN information.

3. Click Refresh to view the latest PE Devices.

Querying PE devices1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > PE Devices.

The PE Devices page displays all PE devices.3. Enter or select one or more of the following query criteria:

• Device Label—Enter the label of the PE to be queried. L2VPN Management supports fuzzymatching for this field.

• LSR ID—Enter the LSR ID of the PE to be queried. L2VPN Management supports fuzzymatching for this field.

• Device IP—Enter the IP address of the PE to be queried. L2VPN Management supportsfuzzy matching for this field.

• Device Status—Select the alarm state of the PE to be queried. Options are All, Unmanaged,Unknown, Normal, Warning, Minor, Major, and Critical.

VPN devices 131

4. Click Query.The PE Devices displays all PEs matching the query criteria.

5. Click Reset to clear the query criteria and display all PEs.

Importing PE devicesBefore importing PE devices, make sure the PE devices meet the following conditions:


• Added into IMC and managed by IMC.

• Not imported as CE devices.

• Enabled with MPLS, L2VPN, and MPLS L2VPN (not necessary for a PBB network), andconfigured with LSR IDs.

To import PE devices:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > PE Devices.

The PE Devices page displays all PE devices.3. Click Import PE on top of the PE Devices area.

The Import Device page appears.4. Click Select Device to select the PEs to be imported.




• To select all of the devices displayed in the Devices Found list, click Add all.



The selected devices appear in the page.8. Verify the imported devices.


• To delete devices, select one or multiple devices in the PE Devices and click Delete.9. Click OK.

You can view the import process and results in the Import Device page.

Viewing L2VPN information on a PE1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > PE Devices.

The PE Devices page displays all PE devices.


3. Click the Details icon for a PE to enter the L2VPN information page for the PE.The output varies with the configured global L2VPN parameters. The page displays the LDPInfo, PBB Info, VLL Info, and GRE Tunnel Info tabs for VLL+PBB+LDP VPLSs.LDP Info tabThis tab consists of the VSI Query area and the Discovered VSI List area. You can query a VSIin the Discovered VSI List by its VSI ID and VSI name that you entered in the VSI ID field andthe VSI Name field. The Discovered VSI List area displays all configured VSIs.Discovered VSI List contents

• VSI ID—ID of the VSI.

• VSI Name—Name of the VSI.

• MAC Learning Status—MAC address learning state. Options are Enabled or Disabled.

• MAC Learning Capability—The maximum number of MAC addresses that the VSI canlearn.

• Tunnel Policy—Tunnel policy that the VSI uses.

• Wtr Time—Wait time for switching traffic from the backup PW to the primary PW whenthe primary PW recovers.

• Binding Information—Click the Binding Information icon to enter the BindingInformation page. You can view the binding interface, encapsulation type, service instanceID, bandwidth, and VLAN ID on the page.

To configure MAC address learning, select one or multiple VSIs and click MAC Learning ontop of the Discovered VSI List to modify the MAC learning status and MAC learning capability.PBB Info tabThis tab consists of the VSI Query area and the Discovered VSI List area. You can query a VSIin the Discovered VSI List by its I-SID and VSI name that you enter in the I-SID field and theVSI Name field. The Discovered VSI List area displays all configured PBB VSIs.Discovered VSI List contents

• PW ID—ID of the PW.

• Peer Address—IP address of the peer PE.

• PW Transport Mode—PW transport mode, VLAN and Ethernet.

• Interface Description—Interface that connects to the CE.

• Service Instance ID—ID of the service instance to which the PW is bound.

• Bandwidth (Mbps)—Limited value of bandwidth for the AC.

• AC Encapsulation Type—Encapsulation type of the AC to which the PW is bound. Optionsare S-VID, S-VID Only Tagged , Port-based, Tagged, and Untagged.

• AC Access Type—Access type for the AC to which the PW is bound. Options are VLANand Ethernet.

• VLAN ID—ID of the SVLAN.

• Tunnel Policy—Tunnel policy that the PW uses.GRE Tunnel Info tabThis tab consists of the GRE Tunnel Query area and the Discovered GRE Tunnel List area. Youcan query a GRE tunnel in the Discovered GRE Tunnel List by the tunnel number, tunnel IPaddress/mask, source address, and destination address. The Discovered GRE Tunnel List areadisplays all configured GRE tunnels.

VPN devices 133

Discovered GRE Tunnel List contents

• Tunnel Number—Number of the tunnel.

• Tunnel IP Address/Mask—IP address and mask of the tunnel interface.

• Source Address—Source address of the tunnel, which is the source address of GRE packets.

• Destination Address—Destination address of the tunnel, which is the destination addressof GRE packets.

To add a GRE tunnel, click Add on top of the Discovered GRE Tunnel List and configure a GREtunnel on the Add GRE Tunnel page that appears.To undeploy GRE tunnels:a. Select one or multiple GRE tunnels and click Undeploy.

A confirmation dialog box appears.b. Click OK.

Synchronizing PE devicesThis function immediately synchronizes device configurations to L2VPN Management. L2VPNManagement compares the device configurations with the baseline configurations, and displaysthe differences in the PE Devices page.To synchronize PE devices:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > PE Devices.

The PE Devices page displays all PE devices.3. Select one or multiple PEs to be synchronized and click Synchronize.

The synchronization results are displayed in the Synchronization Status field.4. Click Refresh to view the latest PE Devices and view the final synchronization results.

Removing PE devicesThis function removes the PE devices from L2VPN Management.To remove PE devices:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > PE Devices.

The PE Devices page displays all PE devices.3. Select one or multiple PEs to be deleted and click Delete.


CE devicesCE devices include common CEs and virtual CEs (VCEs). Common CEs are physical CEs that canbe managed by IMC. You can import and synchronize common CEs, and configure VLAN mappingsfor them. VCEs represent the physical CEs that cannot be managed by IMC. You can add,synchronize, and modify VCEs.

Viewing the CE device list1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > CE Devices.



CE Devices List contents


• Device Label—Label for the CE/VCE. For a CE, this field displays its device label and IPaddress. Click the device label link to view its details. For a manually configured VCE,this field displays its device label. For an automatically generated VCE, this field displaysVCE-(Sequence number). For example, VCE-1. Click the VCE device label to view itsdevice label and MAC address.

• CE Type—Type of the CE. Options are CE, and VCE.

• MAC Address—MAC address of the CE.

• Last Synchronization Time—ime when the last synchronization occurred, in the formatYYYY-MM-DD hh:mm:ss.

• Synchronization Status—Synchronization state of the CE. Options are Synchronizing,Success, or Failure.

• Operation—For a physical CE, this field displays the VLAN mapping icon . Click theicon to enter the VLAN Mapping List page where you can configure the CVLAN-SVLAN

mapping. For a VCE, this field displays the Modify icon . Click the icon to enter theModify CE page.


Querying CE devices1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > CE Devices.

The CE Devices page displays all CE devices.3. Enter or select one or more of the following query criteria:

• Device Label—Enter the label of the CE to be queried. L2VPN Management supportsfuzzy matching for this field.

• Device Status—Select the alarm state of the CE to be queried. Options are All, Unmanaged,Unknown, Normal, Warning, Minor, Major, and Critical.

• Device IP—Enter the IP address of the CE to be queried. L2VPN Management supportsfuzzy matching for this field.

• CE Type—Select the type of the CE to be queried. Options are All, CE, and VCE.4. Click Query.

The CE Device List displays all CEs matching the query criteria.5. Click Reset to clear the query criteria and display all CEs.

Importing CE devicesBefore importing CE devices, make sure the CE devices meet the following conditions:



• Not imported as PE devices.To import CE devices:1. Click the Service tab.

VPN devices 135

2. From the navigation tree, select L2VPN Manager > VPN Devices > CE Devices.The CE Devices page displays all CE devices.

3. Click Import CE on top of the CE Devices List area.The Import Device page appears.

4. Click Select Device to select the CEs to be imported.There are two methods for selecting devices, By View or using the Advanced option. See"Adding devices by view" and "Adding devices by advanced query."



• To select all of the devices displayed in the Devices Found list, click Add all





• To delete devices, select one or multiple devices in the CE Devices List and click Delete.9. Click OK.


Adding/Modifying a VCE1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > CE Devices.

The CE Devices List page displays all CE devices.3. Click Add VCE on top of the CE Device List area to enter the Add Non-managed CE page. Or,

click the Modify icon in the Operation field for the VCE to be modified to enter the ModifyVCE page.

4. Configure the following parameters as needed:• Device Label—Enter the device label.

• MAC Address—Enter the MAC address of the device.5. Click OK.

Synchronizing CE devicesThis function synchronizes the VLAN mappings on the CEs to L2VPN Management.To synchronize CE devices:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > CE Devices.

The CE Devices page displays all CE devices.3. Select one or multiple CEs to be synchronized and click Synchronize.

The synchronization results are displayed in the Synchronization Status field.


4. Click Refresh to view the latest CEs Devices List and view the final synchronization results.

Removing CE devicesThis function removes the CE devices from L2VPN Management.To remove CE devices:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > CE Devices.

The CE Devices List page displays all CE devices.3. Select one or multiple CEs to be deleted and click Delete.


Automatic discoveryThe auto discovery function collects configuration information from PE devices to obtain all existingL2VPNs and links, draws the L2VPN topology, and adds the VPNs to L2VPN Management. Youcan modify, delete, or removing the VPNs, and deploy links for the VPNs.To automatically discover a VPN:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > Auto Discovery.


a. Enable Synchronize PE device before auto discovery for Auto Discovery Parameter Settings.b. Click Select PE for Auto Discovery Range Settings.

The Select Devices dialog box appears.There are two methods for selecting devices, By View or using the Advanced option. See"Adding devices by view" and "Adding devices by advanced query."

c. Highlight the devices you want to select and do one of the following:




• To remove all of the selected devices, click Remove all .d. Confirm that the devices you have found have been added.e. Click OK to return to the page for selecting a PE.

f. Click the Delete icon for the device to be deleted. To delete multiple devices, selectthe devices and click Delete.

4. Click Auto Discovery.A progress bar for VPN auto discovery appears.

5. Click Next when the loading is finished.The VPN selection page appears.

Automatic discovery 137

6. Select VPNs whose links are to be configured:a. View the VPN List Found.


• Status—Status of the found VPN, Existed or New VPN. Existed indicates that thefound VPN already exists in L2VPN Management. New VPN indicates that a newVPN is found.

• VPN Name—Name of the found VPN.

• VPN Protocol Type—Type of the found VPN. Options are VPLS, VLL, PBB, andVPLS+PBB. If the VPN is a BGP VPN, this field displays BGP.

• ID Value—The ID value in this field depends on the VPN type. It might be the VSI ID,PW ID, or I-SID. If the VPN type is VPLS+PBB, this field displays the VSI ID and I-SID.

• PW Transport Mode—Options are VLAN and Ethernet.

• VPN Description—Description of the found VPN.b. Select one or multiple VPNs in the VPN List Found.c. Click Next.

7. Configure VRF binding relationships.This step configures CE information for the new links.a. Select or clear the Create non-managed CE automatically box.

If you select the Create non-managed CE automatically box, the system automaticallycreates a non-managed CE for a link without any CE device. If you clear the Create

non-managed CE automatically box, click the Modify icon in the New Link List tomanually specify a CE device for a link.

b. View the New Links List.New Links List contents

• Device Label—Label and IP address of the PE device.


• PE Interface—Name of the PE's interface that connects to the CE device.

• Service Instance ID—ID of the service instance.


• Modify—Click the Modify icon to enter the Select Device page. Select a CEdevice and click OK to return to the New Links List.

c. Select multiple links to be added to L2VPN Management.d. Click Finish.The Summary page displays the VPN link configuration results.VPN Link Configuration Result contents



• PE Interface—Name of the PE device's interface that connects to the CE device.


• Result—Result of the VPN configuration, Success or Failure.


L2VPN topologyThe L2VPN topology shows connections between PEs and CEs for each L2VPN. You can viewL2VPN information for a PE device, view information about an AC, remove an AC, and audit aVPN.

Entering L2VPN topology1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > L2VPN Topology.

The L2VPN topology page appears.

Viewing a specific VPN topology1. On the toolbar at the top of the topology page, click the VPN List icon.

The VPN List tab appears at the right of the topology.2. Enter or select one or more of the following query criteria:

• Name—Enter the VPN name.

• Type—Select a VPN type from the drop-down list. Options are All, VPLS, VLL, PBB, andVPLS+PBB.

3. Click Query.The VPN List displays all VPNs matching the query criteria.

4. Click Reset to clear the query criteria, and display all VPNs.5. Double click a VPN in the VPN List. The topology for the VPN is displayed.

Topology operations

Viewing device VPN information1. Right-click a PE device.2. Select L2VPN Info from the shortcut menu.

The page for the L2VPN information appears. For information about L2VPN information, see"Viewing L2VPN information on a PE."

Viewing PW information1. Right-click the PW between two PEs.2. Select PW Info from the shortcut menu.

The page for the PW information appears. You can view the PW connectivity status, left device,right device, PW type, PW encapsulation type, and failure reason on the page.

Viewing AC information1. Right-click the AC between a PE and a CE.2. Select AC Info from the shortcut menu.

The page for the AC information appears. For information about AC information, see"Managing ACs."

Removing an AC1. Right-click the AC between a PE and a CE.2. Select Undeploy from the shortcut menu.

A confirmation dialog box appears.

L2VPN topology 139

3. Click OK.The line that represents the AC changes to a dotted line, which indicates that the AC is beingundeployed.

4. After a short period of time, right-click the blank and select Reload from the shortcut menu.The AC is removed.

Auditing a VPNRight-click the blank and select Audit from the shortcut menu.The message Start VPN Auditing is displayed in the log area below the topology. After a periodof time, you can view the audit results in the VPN List.

ApplicationsIn this chapter, PEs are H3C S95 and S75 series switches.Configuration commands executed on the devices depend on the device model and softwareversion. For more information about the commands in this chapter, see the manual for the device.

Configuring an LDP VPLS VPN

Network requirementsAs shown in Figure 27, a customer has two sites CE 1 and CE 2 that connect to PE 1 and PE 2through VLAN 100. Configure an LDP VPLS VPN so that the customer sites can communicate inVLAN 100 over the MPLS network.


Configuring PEs and the P device

Configuring PE 11. Configure a loopback interface and its IP address.

<Sysname> system-view[Sysname] sysname PE1[PE1] interface loopback 0[PE1-LoopBack0] ip address 1.1.1.9 32[PE1-LoopBack0] quit

2. Configure the LSR ID and enable MPLS globally.


[PE1] mpls lsr-id 1.1.1.9[PE1] mpls[PE1-mpls] quit

3. Enable L2VPN and MPLS L2VPN.[PE1] l2vpn[PE1-l2vpn] mpls l2vpn[PE1-l2vpn] quit

4. Enable LDP globally.[PE1] mpls ldp[PE1-mpls-ldp] quit

5. Configure VLAN-interface 2 that connects to the P device, and enable LDP on the interface.[PE1] interface vlan-interface 2[PE1-Vlan-interface2] ip address 23.1.1.1 24[PE1-Vlan-interface2] mpls[PE1-Vlan-interface2] mpls ldp[PE1-Vlan-interface2] quit

6. Configure OSPF for LSP establishment.[PE1] ospf[PE1-ospf-1] area 0[PE1-ospf-1-area-0.0.0.0] network 23.1.1.1 0.0.0.255[PE1-ospf-1-area-0.0.0.0] network 1.1.1.9 0.0.0.0[PE1-ospf-1-area-0.0.0.0] quit[PE1-ospf-1] quit

7. Configure Ethernet 1/1 as a trunk port, and configure the port to permit packets from VLAN100 to pass through.[PE1] interface ethernet 1/1[PE1-Ethernet1/1] port link-type trunk[PE1-Ethernet1/1] port trunk permit vlan 100

Configuring the P device1. Configure a loopback interface and its IP address.

<Sysname> system-view[Sysname] sysname P[P] interface loopback 0[P-LoopBack0] ip address 2.2.2.9 32[P-LoopBack0] quit

2. Configure the LSR ID and enable MPLS globally.[P] mpls lsr-id 2.2.2.9[P] mpls[P-mpls] quit

3. Enable LDP globally.[P] mpls ldp[P-mpls-ldp] quit

4. Configure VLAN-interface 2 that connects to PE 1, and enable LDP on the interface.[P] interface vlan-interface 2[P-Vlan-interface2] ip address 23.1.1.2 24[P-Vlan-interface2] mpls[P-Vlan-interface2] mpls ldp[P-Vlan-interface2] quit

5. Configure VLAN-interface 3 that connects to PE 2, and enable LDP on the interface.[P] interface vlan-interface 3[P-Vlan-interface3] ip address 26.2.2.2 24[P-Vlan-interface3] mpls

Configuring an LDP VPLS VPN 141

[P-Vlan-interface3] mpls ldp[P-Vlan-interface3] quit

6. Configure OSPF for LSP establishment.[P] ospf[P-ospf-1] area 0[P-ospf-1-area-0.0.0.0] network 23.1.1.2 0.0.0.255[P-ospf-1-area-0.0.0.0] network 26.2.2.2 0.0.0.255[P-ospf-1-area-0.0.0.0] network 2.2.2.9 0.0.0.0[P-ospf-1-area-0.0.0.0] quit[P-ospf-1] quit



2. Configure the LSR ID and enable MPLS globally.[PE2] mpls lsr-id 3.3.3.9[PE2] mpls[PE2-mpls] quit



5. Configure VLAN-interface 3 that connects to the P device, and enable LDP on the interface.[PE2] interface vlan-interface 3[PE2-Vlan-interface3] ip address 26.2.2.1 24[PE2-Vlan-interface3] mpls[PE2-Vlan-interface3] mpls ldp[[PE2-Vlan-interface3] quit


7. Configure Ethernet 1/1 as a trunk port, and configure the port to permit packets from VLAN100 to pass through.[PE2] interface ethernet 1/1[PE2-Ethernet1/1] port link-type trunk[PE2-Ethernet1/1] port trunk permit vlan 100

Configuring L2VPN Management

Importing CE 1 and CE 21. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > CE Devices.



3. Click Import CE on top of the CE Device List area.The Import Device page appears.

4. Click Select Device to select CE 1 and CE 2.5. Click OK to enter the Import Device page.6. Click OK.The page for import results appears. You can see that the two CEs are imported.

Importing PE 1 and PE 21. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > PE Devices.

The PE Device page displays all PE devices.3. Click Import PE on top of the PE Device area.

The Import Device page appears.4. Click Select Device to select PE 1 and PE 2.5. Click OK to enter the Import Device page.6. Click OK.The page for import results appears. You can see that the two PEs are imported.

Deploying a VPLS VPN1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > Deploy VPLSs.

The VPLS deployment guide page appears.3. Define a VPN:

a. In the PE Type area, select PE.b. In the VPN Configuration area, configure the following parameters:

• VPN Operation Type—Select Add VPN.

• VPN Name—Enter VPN name VPLS001.

• VSI ID—Use the default value.

• PW Transport Mode—Select VLAN from the list.

• Audit Interval (in hours)—Use the default value 24.

• Description—Enter This is a common VPLS VPN as the description.

• Contact—Enter Use the default value admin.c. Click Next.

4. Add the AC from CE 1 to PE 1:a. Click Add on top of the AC List area.

The Select Interfaces window appears.b. Select PE 1 in the Device List, and click OK.

The Interface List tab automatically appears.c. Select Eth 1/1 that connects to CE 1, and click OK.

The Config UNI Interface page automatically appears.

Configuring an LDP VPLS VPN 143

d. Configure the following parameters:• Service Instance—Enter service instance ID 1000.

• Bandwidth (Mbps)—his field is not required. If you enter a value, L2VPN Managementmonitors the AC traffic from CE 1 to PE 1.

• Encap Type—Select S-VID from the list.

• Encap VLAN—Enter a value of 100.

• Access Type—Select VLAN from the list.

• CE Device—Click Select next to the CE device box. On the Select Interfaces windowthat appears, select CE 1 and click OK to return to the Config UNI Interface page.

e. Click OK to return to the PE Configuration page.5. Add the AC from CE 2 to PE 2 in the same way that CE 1-PE 1 AC is configured.

L2VPN Management automatically generates a PWbetween PE 1 and PE 2. The PW informationis displayed in the PW List area.The system uses the default tunnel policy that only one tunnel is selected (no load balancing)in this order: LSP tunnel, GRE tunnel, and CRLSP tunnel.

6. Click Next.The Configuration Summary page appears. On that page, you can view VPN information,and configurations to be deployed to PE 1 and PE 2.

7. Select Deploy Immediately and click OK.The Task List page appears. On that page, you can view the VPN deployment results.

Figure 41 VPN deployment results

Viewing the VPN topology1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > L2VPN Topology.

The L2VPN topology page appears.3. On the toolbar at the top of the topology page, click the VPN List icon.

The VPN List tab appears at the right of the topology.4. Configure the following query criteria:

• Name—Enter VPN name VPLS001.

• Type—Select VPLS from the list.


5. Click Query.All matching devices are displayed in the VPN List area.

6. Double click a VPN in the VPN List.The topology for the VPN is displayed.

Figure 42 VPLS001 topology

Configuring an LDP H-VPLS VPN

Network requirementsAs shown in Figure 43, a customer has two sites CE 1 and CE 3. Configure an LDP H-VPLS VPNso that the customer sites can communicate with each other.


Configuring an LDP H-VPLS VPN 145

Configuring UPE and NPEs

Configuring UPE1. Configure basic MPLS.

<Sysname> system-view[Sysname] sysname UPE[UPE] interface loopback 0[UPE-LoopBack0] ip address 1.1.1.9 32[UPE-LoopBack0] quit[UPE] mpls lsr-id 1.1.1.9[UPE] mpls[UPE-mpls] quit[UPE] mpls ldp[UPE-mpls-ldp] quit

2. Configure basic MPLS on the interface that connects to NPE 1.[UPE] interface vlan-interface 10[UPE-Vlan-interface10] ip address 10.1.1.1 24[UPE-Vlan-interface10] mpls[UPE-Vlan-interface10] mpls ldp[UPE-Vlan-interface10] quit

3. Configure an LDP session with NPE 1.[UPE] mpls ldp remote-peer 1[UPE-mpls-remote-1] remote-ip 2.2.2.9[UPE-mpls-remote-1] quit

4. Enable L2VPN and MPLS L2VPN.[UPE] l2vpn[UPE-l2vpn] mpls l2vpn[UPE-l2vpn] quit

Configuring NPE 11. Configure basic MPLS.

<Sysname> system-view[Sysname] sysname NPE1[NPE1] interface loopback 0[NPE1-LoopBack0] ip address 2.2.2.9 32[NPE1-LoopBack0] quit[NPE1] mpls lsr-id 2.2.2.9[NPE1] mpls[NPE1–mpls] quit[NPE1] mpls ldp[NPE1–mpls-ldp] quit

2. Configure basic MPLS on the interface that connects to UPE.[NPE1] interface vlan-interface 10[NPE1-Vlan-interface10] ip address 10.1.1.2 24[NPE1-Vlan-interface10] mpls[NPE1-Vlan-interface10] mpls ldp[NPE1-Vlan-interface10] quit

3. Configure basic MPLS on the interface that connects to NPE 3.[NPE1] interface vlan-interface 20[NPE1-Vlan-interface20] ip address 11.1.1.1 24[[NPE1-Vlan-interface20] mpls[NPE1-Vlan-interface20] mpls ldp[NPE1-Vlan-interface20] quit


4. Enable L2VPN and MPLS L2VPN.[NPE1] l2vpn[NPE1-l2vpn] mpls l2vpn[NPE1-l2vpn] quit

Configuring NPE 31. Configure basic MPLS.

<Sysname> system-view[Sysname] sysname NPE3[NPE3] interface loopback 0[NPE3-LoopBack0] ip address 3.3.3.9 32[NPE3-LoopBack0] quit[NPE3] mpls lsr-id 3.3.3.9[NPE3] mpls[NPE3–mpls] quit[NPE3] mpls ldp[NPE3–mpls-ldp] quit

2. Configure basic MPLS on the interface that connects to NPE 1.[NPE3] interface vlan-interface 20[NPE3-Vlan-interface20] ip address 11.1.1.2 24[NPE3-Vlan-interface20] mpls[NPE3-Vlan-interface20] mpls ldp[NPE3-Vlan-interface20] quit

3. Enable L2VPN and MPLS L2VPN.[NPE3] l2vpn[NPE3-l2vpn] mpls l2vpn[NPE3-l2vpn] quit



The CE Device List page displays all CE devices.3. Click Import CE on top of the CE Device List area.

The Import Device page appears.4. Click Select Device to select CE 1 and CE 3.5. Click OK to enter the Import Device page.6. Click OK.The page for import results appears. You can see that the two CEs are imported.

Importing UPE, NPE 1, and NPE 31. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > PE Devices.


The Import Device page appears.4. Click Select Device to select UPE, NPE 1, and NPE 3.5. Click OK to enter the Import Device page.6. Click OK.The page for import results appears. You can see that the three PEs are imported.


Deploying a hierarchical VPLS VPN1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > Deploy VPLSs..

The VPLS deployment guide page appears.3. Define a VPN:

a. In the PE Type area, select Hierarchical PE.b. In the VPN Configuration area, configure the following parameters:

• VPN Operation Type—Select Add VPN.

• VPN Name—Enter VPN name VPLS002.

• VSI ID—Use the default value.


• Audit Interval (in hours)—Use the default value 24

• Description—Enter This is a hierarchical VPLS VPN as the description.

• Contact—Use the default value admin.c. Click Next.

4. Add the AC from CE 3 to NPE 3:a. Click Add on top of the AC List area.

The Select Interfaces window appears.b. Select NPE 3 in the Device List, and click OK.


The Config UNI Interface page automatically appears.d. Configure the following parameters:

• Service Instance—Enter service instance ID 500.

• Bandwidth (Mbps)—This field is not required. If you enter a value, L2VPNManagement monitors the AC traffic from CE 3 to NPE 3.





e. Click OK to return to the PE Configuration page.f. Click Next.

5. Add the AC from CE 1 to UPE:a. Click Add on top of the AC List area.

The Select Interfaces window appears.b. Select UPE in the Device List, and click OK.


The Config UNI Interface page automatically appears.


d. Configure the following parameters:• Service Instance—Enter service instance ID 500.

• Bandwidth (Mbps)—This field is not required. If you enter a value, L2VPNManagement monitors the AC traffic from CE 1 to UPE.





e. Click OK to return to the PE Configuration page.f. Select a UPE from the UPE Device List, and click Main NPE.g. On the page that appears, click OK.

L2VPN Management automatically generates a PW between UPE and NPE 1, and betweenNPE 1 and NPE 3. The PW information is displayed in the PW List area.Each PW uses the default tunnel policy that only one tunnel is selected (no load balancing)in this order: LSP tunnel, GRE tunnel, and CRLSP tunnel.

h. Click Next.The Configuration Summary page appears. On that page, you can view VPN information,and configurations to be deployed to UPE, NPE 1, and NPE 3.


Figure 44 VPN deployment results


The L2VPN topology page appears.3. On the toolbar at the top of the topology page, click VPN List.

The VPN List tab appears at the right of the topology.


4. Configure the following query criteria:• Name—Enter VPN name VPLS002.

• Type—Select VPLS from the list.5. Click Query.

All matching devices are displayed in the VPN List area.6. Double click a VPN in the VPN List.

The topology for the VPN is displayed.


Configuring a VLL VPN

Network requirementsAs shown in Figure 46, a customer has two sites CE 1 and CE 2 that connect to PE 1 and PE 2through VLAN 10. Configure a VLL VPN so that the customer sites can communicate with eachother.



Configuring devices

Configuring CE 1# Configure an IP address for VLAN-interface 10 that connects to PE 1.<Sysname> system-view[Sysname] sysname CE1[CE1] interface vlan-interface 10[CE1-Vlan-interface10] ip address 100.1.1.1 24



2. Configure the LSR ID and enable MPLS globally.[PE1] mpls[PE1] interface loopback 0[PE1-mpls] quit


4. Enable LDP globally.[[PE1] mpls ldp[[PE1-mpls-ldp] quit

5. Establish a remote LDP session to PE 2.[PE1] mpls ldp remote-peer 1[PE1-mpls-ldp-remote-1] remote-ip 192.3.3.3[PE1-mpls-ldp-remote-1] quit

6. Configure VLAN-interface 23 that connects to the P device, and enable LDP on the interface.[PE1] interface vlan-interface 23[PE1-Vlan-interface23] ip address 23.1.1.1 24[PE1-Vlan-interface23] mpls

Configuring a VLL VPN 151

[PE1-Vlan-interface23] mpls ldp[PE1-Vlan-interface23] quit


Configuring the P device1. Configure a loopback interface and its IP address.

<Sysname> system-view[Sysname] sysname P[P] interface loopback 0[P-LoopBack0] ip address 192.4.4.4 32[P-LoopBack0] quit

2. Configure the LSR ID and enable MPLS globally.[P] mpls lsr-id 192.4.4.4[P] mpls[P-mpls] quit

3. Enable LDP globally.[P] mpls ldp[P-mpls-ldp] quit



6. Configure OSPF for LSP establishment.[P] ospf[P-ospf-1] area 0[P-ospf-1-area-0.0.0.0] network 23.1.1.2 0.0.0.255[P-ospf-1-area-0.0.0.0] network 26.2.2.2 0.0.0.255[P-ospf-1-area-0.0.0.0] network 192.4.4.4 0.0.0.0[P-ospf-1-area-0.0.0.0] quit[P-ospf-1] quit

Configuring PE21. Configure a loopback interface and its IP address.


2. Configure the LSR ID and enable MPLS globally.


[PE2] mpls lsr-id 192.3.3.3[PE2] mpls[PE2-mpls] quit



5. Establish a remote LDP session to PE 1.[PE2] mpls ldp remote-peer 2[PE2-mpls-ldp-remote-2] remote-ip 192.2.2.2[PE2-mpls-ldp-remote-2] quit

6. Configure VLAN-interface 26 that connects to the P device, and enable LDP on the interface.[PE2] interface vlan-interface 26[PE2-Vlan-interface26] ip address 26.2.2.1 24[PE2-Vlan-interface26] mpls[PE2-Vlan-interface26] mpls ldp[PE2-Vlan-interface26] quit


Configuring CE 2# Configure an IP address for VLAN-interface 10 that connects to PE 2.<Sysname> system-view[Sysname] sysname CE2[CE2] interface vlan-interface 10[CE2-Vlan-interface10] ip address 100.1.1.2 24





Importing PE 1 and PE 21. Click the Service tab.


2. From the navigation tree, select L2VPN Manager > VPN Devices > PE Devices.The PE Device page displays all PE devices.

3. Click Import PE on top of the PE Device area.The Import Device page appears.

4. Click Select Device to select PE 1 and PE 2.5. Click OK to enter the Import Device page.6. Click OK.The page for import results appears. You can see that the two PEs are imported.

Deploying a VLL VPN1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > Deploy VLLs.

The VLL deployment guide page appears.3. Define a VPN:

a. Configure the following parameters:• VPN Name—Enter VPN name VLL001.

• PW ID—Use the default value.


• Tunnel Policy—Select default from the list.

• Audit Interval—Use the default value 24. The interval is in hours.

• Description—Enter This is a VLL VPN as the description.

• Contact—Enter Use the default value admin.b. Click Next.

4. Configure the local PE:a. Click Select next to the UNI Interface box.

• On the window that appears, select PE 1 in the Device List, and click OK.The Interface List tab automatically appears.

• Select Eth 1/1 that connects to CE 1, and click OK to return to the Local PEConfiguration page.

b. Configure the following parameters:• Service Instance—Enter service instance ID 2000.

• Bandwidth (Mbps)—This field is not required. If you enter a value, L2VPNManagement monitors the AC traffic from CE 1 to PE 1.


• Encapsulation VLAN—Enter a value of 10.



c. Click Next.


5. Configure the remote PE:a. Click Select next to the UNI Interface box.

• On the window that appears, select PE 1 in the Device List, and click OK.The Interface List tab automatically appears.

• Select Eth 1/1 that connects to CE 1, and click OK to return to the Remote PEConfiguration page.

b. Configure the following parameters:• Service Instance—Enter service instance ID 2000.

• Bandwidth (Mbps)—This field is not required. If you enter a value, L2VPNManagement monitors the AC traffic from CE 1 to PE 1.


• Encapsulation VLAN—Enter a value of 10.


• CE Device—Click Select next to the CE device box. On the Select Interfaces windowthat appears, select CE 2 and click OK to return to the Remote PE Configuration page.

c. Click Next.The Configuration Summary page appears. On that page, you can view VPN information,and configurations to be deployed to PE 1 and PE 2.


Figure 47 VLL001 deployment results



The VPN List tab appears at the right of the topology.


4. Configure the following query criteria:• Name—Enter VPN name VLL001.

• Type—Select VLL from the list.5. Click Query.



Figure 48 VLL001topology

Configuring a PBB network

Network requirementsAs shown in Figure 49, a customer has two sites Customer network A and Customer network Bthat connect to BEB 1 and BEB 2. Configure a PBB network so that the customer sites cancommunicate with each other at Layer 2.



Configuring BEBs

Configuring BEB 1# Create VLAN 20.<BEB1> system-view[BEB1] vlan 20[BEB1-vlan20] quit

# Enable L2VPN.[BEB1] l2vpn[BEB1-l2vpn] quit

# Configure the uplink port Ethernet 1/1 as a trunk port, and configure the port to permit packetsfrom VLAN 20 to pass.[BEB1] interface ethernet 1/1[BEB1-Ethernet1/1] port link-type trunk[BEB1-Ethernet1/1] port trunk permit vlan 20[BEB1-Ethernet1/1] quit

# # Configure the downlink port Ethernet 1/2 as a trunk port, and configure the port to permitpackets from all VLANs to pass.[BEB1] interface ethernet 1/2[BEB1-Ethernet1/2] port link-type trunk[BEB1-Ethernet1/2] port trunk permit vlan all[BEB1-Ethernet1/2] quit

Configuring BEB 2Configure BEB 2 in the same way that BEB 1 is configured. Details not shown.


Importing Device A and Device B1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > CE Devices.


The Import Device page appears.4. Click Select Device to select Device A and Device B.5. Click OK to enter the Import Device page.6. Click OK.The page for import results appears. You can see that the two devices are imported.

Importing BEB 1 and BEB 21. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > PE Devices.


The Import Device page appears.4. Click Select Device to select BEB 1 and BEB 2.5. Click OK to enter the Import Device page.6. Click OK.The page for import results appears. You can see that the two PEs are imported.

Configuring a PBB network 157

Deploying a PBB network1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > Deploy PBBs.

The PBB deployment guide page appears.3. Define a VPN:

a. Configure the following parameters:• VPN Operation Type—Select Add VPN.

• VPN Name—Enter VPN name PBB001.

• I-SID—Use the default value.

• B-VLAN—Enter 20.

• PW Transport Mode—Select Ethernet from the list.

• Audit Interval (in hours)—Use the default value 24

• Description—Enter This is a PBB network as the description.

• Contact—Use the default value admin.b. Click Next.

4. Add the AC from Device A to BEB 1:a. Click Add on top of the AC List area.

The Select Interfaces window appears.b. Select BEB 1 in the Device List, and click OK.

The Interface List tab automatically appears.c. Select Eth 1/2 that connects to Device A, and click OK.

The Configure Interface page automatically appears.d. Configure the following parameters:

• Service Instance—Enter service instance ID 3000.

• Bandwidth (Mbps)—This field is not required. If you enter a value, L2VPNManagement monitors the AC traffic from Device A to BEB 1.

• Encap Type—Select Port-based from the list.

• Access Type—Select Ethernet from the list.

• CE Device—Click Select next to the CE device box. On the Select Interfaces windowthat appears, select Device A and click OK to return to the Configure Interface page.

e. Click OK to return to the PE Configuration page.5. Add the AC from Device B to BEB 2 in the same way that Device A-BEB 1 AC is configured.6. Configure the NNI interfaces on the PEs:

a. On the PE Device List area, click the Configuration icon for BEB 1.b. On the window that appears, select Eth 1/1 and click OK.c. On the PE Device List area, click the Configuration icon for BEB 2.d. On the window that appears, select Eth 1/1 and click OK.

7. Click Next.The Configuration Summary page appears. On that page, you can view VPN information,and configurations to be deployed to BEB 1 and BEB 2.



Figure 50 PBB001deployment results




• Name—Enter VPN name PBB001.

• Type—Select PBB from the list.5. Click Query.



Configuring a PBB network 159

Figure 51 PBB001topology

Using L2VPN Management with BGP protocolThis section provides a quick start for deploying and managing BGP VPLS VPNs.

Figure 52 BGP VPLS VPNs quick start

As shown above, the quick start includes the following steps.1. Make preparations:

• Import PE and CE devices into IMC Platform, and configure correct SNMP parametersand BGP VPLS for the devices.

• To build BGP VPLS, you must enable MPLS, and MPLS L2VPN on PEs. For details, see thecorresponding configuration guides and command references.

2. Import devices into L2VPN Management:• For VPLS VPNs, import PEs. For details, see "Importing PE devices."

• Import physical CEs. For details, see "Importing CE devices."

• Import virtual CEs (VCEs). For details, see "Adding/Modifying a VCE."3. Add VPNs:

Add existing VPNs to L2VPN Management through auto discovery. For details, see "Automaticdiscovery."


4. Maintain VPNsYou can view VPN topology, alarms, and audit information.

The following content will introduce how to use L2VPN Management deployed BGP protocol.

VPN devicesVPN devices include PEs and CEs in MPLS Layer 2 VPNs. A PE provides VPN access by translatingdata link layer frames to Layer 2 VPN packets. A CE only needs to establish a link layer connectionwith a PE. You can import, synchronize, view, and query PEs and CEs. In addition, you can createnon-managed CEs (or called VCEs) to represent CEs that cannot be managed by L2VPNManagement.

PE devicesThe first step to deploy a VPN is to import PEs to L2VPN Management. Then, you can synchronizeand delete PEs, and view VPN information on the PEs. To enhance management, you can use theconfiguration comparison function to discover configuration changes on the PEs.

Viewing PE devices1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > PE Devices.

The PE Devices page displays all PE devices.PE Devices contents


• Device Label—Label and IP address of the device. Click the device label link to view itsdetails.

• LSR ID—LSR ID of the PE device. An LSR ID uniquely identifies an LSR in an MPLS network.

• Last Synchronization Time—Time when the last synchronization occurred, in the formatYYYY-MM-DD hh:mm:ss.

• Synchronization Status—Synchronization state of the PE. Options are Synchronizing,Success, or Failure. When the synchronization fails, click the Failure link to view thecauses in the prompt box that appears.

• Config Comparison—Configuration comparison results. Options are Same Config andDifferent Config. When the synchronization begins, L2VPN Management compares thePE's configuration with the baseline configuration. When they are different, you can clickthe Different Config link to view the differences in the configuration comparison resultpage.

• Details—Click the Details icon to view the LDP, PBB, VLL, and GRE tunnel informationfor the device in the page for the device's VPN information.

3. Click Refresh to view the latest PE Devices.

Querying PE devices1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > PE Devices.


VPN devices 161

3. Enter or select one or more of the following query criteria:• Device Label—Enter the label of the PE to be queried. L2VPN Management supports fuzzy

matching for this field.• LSR ID—Enter the LSR ID of the PE to be queried. L2VPN Management supports fuzzy

matching for this field.• Device IP—Enter the IP address of the PE to be queried. L2VPN Management supports

fuzzy matching for this field.• Device Status—Select the alarm state of the PE to be queried. Options are All, Unmanaged,

Unknown, Normal, Warning, Minor, Major, and Critical.4. Click Query.

The PE Devices displays all PEs matching the query criteria.5. Click Reset to clear the query criteria and display all PEs.

Importing PE devicesBefore importing PE devices, make sure the PE devices meet the following conditions:



• Not imported as CE devices.

• Enabled with MPLS, L2VPN, and MPLS L2VPN (not necessary for a PBB network), andconfigured with LSR IDs.

To import PE devices:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > PE Devices.

The PE Devices page displays all PE devices.3. Click Import PE on top of the PE Devices area.

The Import Device page appears.4. Click Select Device to select the PEs to be imported.









• To delete devices, select one or multiple devices in the PE Devices and click Delete.


9. Click OK.You can view the import process and results in the Import Device page.

Viewing L2VPN information on a PE1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > PE Devices.


3. Click the Details icon for a PE to enter the L2VPN information page for the PE.The output varies with the configured global L2VPN parameters. The page displays the LDPInfo, PBB Info, VLL Info, and GRE Tunnel Info tabs for VLL+PBB+LDP VPLSs.LDP Info tabThis tab consists of the VSI Query area and the Discovered VSI List area. You can query a VSIin the Discovered VSI List by its VSI ID and VSI name that you entered in the VSI ID field andthe VSI Name field. The Discovered VSI List area displays all configured VSIs.Discovered VSI List contents

• VSI Name—Name of the VSI.

• Protocol Type—Protocol type for the VSI.

• Import RT—Value of the import RT with which the VSI associates.

• Export RT—Value of the export RT with which the VSI associates.

• RD—RD value of the VSI.

• MAC Learning Status—Whether MAC address learning is Enabled or Disabled.

• Tunnel Policy—Tunnel policy that the VSI uses.

• Binding Information—Click the Binding Information icon to enter the BindingInformation page. You can view the binding interface, encapsulation type, service instanceID, bandwidth, and VLAN ID on the page.

Synchronizing PE devicesThis function immediately synchronizes device configurations to L2VPN Management. L2VPNManagement compares the device configurations with the baseline configurations, and displaysthe differences in the PE Devices page.To synchronize PE devices:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > PE Devices.

The PE Devices page displays all PE devices.3. Select one or multiple PEs to be synchronized and click Synchronize.

The synchronization results are displayed in the Synchronization Status field.4. Click Refresh to view the latest PE Devices and view the final synchronization results.

Removing PE devicesThis function removes the PE devices from L2VPN Management.To remove PE devices:1. Click the Service tab.

VPN devices 163

2. From the navigation tree, select L2VPN Manager > VPN Devices > PE Devices.The PE Devices page displays all PE devices.

3. Select one or multiple PEs to be deleted and click Delete.A confirmation dialog box appears.

4. Click OK.

CE devicesCE devices include common CEs and virtual CEs (VCEs). Common CEs are physical CEs that canbe managed by IMC. You can import and synchronize common CEs, and configure VLAN mappingsfor them. VCEs represent the physical CEs that cannot be managed by IMC. You can add,synchronize, and modify VCEs.

Viewing the CE device list1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > CE Devices.

The CE Device List page displays all CE devices.CE Devices List contents


• Device Label—Label for the CE/VCE. For a CE, this field displays its device label and IPaddress. Click the device label link to view its details. For a manually configured VCE,this field displays its device label. For an automatically generated VCE, this field displaysVCE-(Sequence number). For example, VCE-1. Click the VCE device label to view itsdevice label and MAC address.

• CE Type—Type of the CE. Options are CE, and VCE.

• MAC Address—MAC address of the CE.

• Last Synchronization Time—ime when the last synchronization occurred, in the formatYYYY-MM-DD hh:mm:ss.

• Synchronization Status—Synchronization state of the CE. Options are Synchronizing,Success, or Failure.

• Operation—For a physical CE, this field displays the VLAN mapping icon . Click theicon to enter the VLAN Mapping List page where you can configure the CVLAN-SVLAN

mapping. For a VCE, this field displays the Modify icon . Click the icon to enter theModify CE page.


Querying CE devices1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > CE Devices.

The CE Devices page displays all CE devices.3. Enter or select one or more of the following query criteria:

• Device Label—Enter the label of the CE to be queried. L2VPN Management supportsfuzzy matching for this field.

• Device Status—Select the alarm state of the CE to be queried. Options are All, Unmanaged,Unknown, Normal, Warning, Minor, Major, and Critical.


• Device IP—Enter the IP address of the CE to be queried. L2VPN Management supportsfuzzy matching for this field.

• CE Type—Select the type of the CE to be queried. Options are All, CE, and VCE.4. Click Query.

The CE Device List displays all CEs matching the query criteria.5. Click Reset to clear the query criteria and display all CEs.

Importing CE devicesBefore importing CE devices, make sure the CE devices meet the following conditions:



• Not imported as PE devices.To import CE devices:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > CE Devices.

The CE Devices page displays all CE devices.3. Click Import CE on top of the CE Devices List area.

The Import Device page appears.4. Click Select Device to select the CEs to be imported.









• To delete devices, select one or multiple devices in the CE Devices List and click Delete.9. Click OK.


Adding/Modifying a VCE1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > CE Devices.

The CE Devices List page displays all CE devices.

VPN devices 165

3. Click Add VCE on top of the CE Device List area to enter the Add Non-managed CE page. Or,

click the Modify icon in the Operation field for the VCE to be modified to enter the ModifyVCE page.

4. Configure the following parameters as needed:• Device Label—Enter the device label.

• MAC Address—Enter the MAC address of the device.5. Click OK.

Synchronizing CE devicesThis function synchronizes the VLAN mappings on the CEs to L2VPN Management.To synchronize CE devices:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > CE Devices.

The CE Devices page displays all CE devices.3. Select one or multiple CEs to be synchronized and click Synchronize.

The synchronization results are displayed in the Synchronization Status field.4. Click Refresh to view the latest CEs Devices List and view the final synchronization results.

Removing CE devicesThis function removes the CE devices from L2VPN Management.To remove CE devices:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > CE Devices.

The CE Devices List page displays all CE devices.3. Select one or multiple CEs to be deleted and click Delete.


Managing VPN resourcesVPN resources include VPNs services and Attachment Circuit (ACs). A VPN service is a Layer 2VPN. An AC is a link that connects a PE to a CE. L2VPN Management provides a VPN list andan AC list for you to manage all VPNs and ACs.

Managing VPNsThe VPN list shows all VPN services. You can add, modify, delete, and audit VPN services fromthe VPN list.

Viewing the VPN list1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Resources > VPN List.

VPN List contents

• Status—State of the VPN. Options are Critical, Major, Minor, Warning, Normal, Unknown,and Unmanaged.

• VSI Admin Status—State of the VSI, Enabled or Disabled.


• VPN name—Name of the VPN. You can click a VPN name to view details about thatVPN.

• Topology—Provides a Topology link for you to view L2VPN topology.

• Audit Time—Time when the last VPN connectivity audit was performed, in the formatYYYY-MM-DD hh:mm:ss.

• Audit Result—Result of the last VPN connectivity audit. Options are Unaudited, Normal,Auditing, Unknown, Unconnected, and Error. If the result is Unconnected, you can clickthe Unconnected link to view the cause.

• Modify—Provides a Modify icon for you to modify basic settings for a VPN.3. Click Refresh to view the latest VPN list.

Querying a VPN1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Resources > VPN List.3. Enter or select one or more of the following query criteria:

• VPN name—Enter the name of a VPN. This field supports fuzzy matching.

• Audit Result—Select an audit result. Options are All, Unaudited, Normal, Auditing,Unknown, Unconnected, and Error.

• VPN Status—Select a VPN state. Options are All, Critical, Major, Minor, Warning, Normal,Unknown, and Unmanaged.

• VSI Admin Status—Select a VSI state. Options are All, Enabled, and Disabled.4. Click Query.

The VPN list displays all the matching VPNs. To clear the query results, click Reset.

Modifying basic VPN settingsL2VPN Management provides basic and advanced VPN settings. Basic settings include the VPNname, contact, description, and audit interval. Advanced settings include information about PEs,ACs, VLAN mappings, and alarms.To modify basic VPN settings:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Resources > VPN List.

3. Click the Modify icon of the target VPN.4. Modify the following settings:

• VPN Name—Enter a new VPN name.

• Contact—Enter a new contact.

• Description—Enter a new description.

• Audit Interval (in hours)—Enter a new audit interval in the range of 0 to 24. An auditinterval of 0 disables audit function.

5. Click OK.

Enabling a VSI1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Resources > VPN List.3. Select one or more VPNs from the VPN list.


4. Click More Opertions.5. Select Enable VSI.6. Click OK in the popup window.

Deleting VPNsThis task deletes VPNs from L2VPN Management but the deleted VPNs still exist in the network.You can perform VPN auto-discovery to add the deleted VPNs to L2VPN Management. To deletea VPN from the network, you need to undeploy the VPN.To delete a VPN:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Resources > VPN List.3. Select one or more VPNs from the VPN list.4. Click Delete.5. Click OK in the popup window.

Auditing VPNs1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Resources > VPN List.3. Select one or more VPNs from the VPN list.4. Click Audit.5. After a while, click Refresh to view the audit result.

Managing ACsThe AC list shows all ACs. You can view, query, and delete ACs from the AC list.

Viewing the VPN list1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Resources > AC List.

AC list contents

• PE Name—Name of the PE. You can click a PE name to view details about that PE.

• PE Interface Description—Displays the PE's interface connected to the CE.

• CE Name—Name of the CE. You can click a CE name to view details about that CE.

• Attached VPN—VPN to which the AC belongs.

• Details—Provides a Details icon for you to view details about the AC.3. Click Refresh to view the latest AC list.

Querying ACs1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Resources > AC List.3. Enter or select the following query criteria:

• PE Name—Enter a PE name. This field supports fuzzy matching.

• Attached VPN—Enter a VPN name. This field supports fuzzy matching.

• CE Name—Enter a CE name. This field supports fuzzy matching.4. Click Query.

The VPN list displays all the matching ACs. To clear the query results, click Reset.


Deleting ACsThis task deletes ACs from L2VPN Management but the deleted ACs still exist in the network.1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Resources > AC List.3. Select ACs from the AC list.4. Click Delete.5. Click OK in the popup window.

Automatic discoveryThe auto discovery function collects configuration information from PE devices to obtain all existingL2VPNs and links, draws the L2VPN topology, and add the VPNs to L2VPN Management.To automatically discover a VPN:1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > Auto Discovery.


a. Enable Synchronize PE device before auto discovery for Auto Discovery Parameter Settings.b. Click Select PE for Auto Discovery Range Settings.

The Select Devices dialog box appears.There are two methods for selecting devices, By View or using the Advanced option. See"Adding devices by view" and "Adding devices by advanced query."

c. Highlight the devices you want to select and do one of the following:




• To remove all of the selected devices, click Remove all .d. Confirm that the devices you have found have been added.e. Click OK to return to the page for selecting a PE.

f. Click the Delete icon for the device to be deleted. To delete multiple devices, selectthe devices and click Delete.

4. Click Auto Discovery.A progress bar for VPN auto discovery appears.


Automatic discovery 169

6. Select VPNs whose links are to be configured:a. View the VPN List Found.


• Status—Status of the found VPN, Existed or New VPN. Existed indicates that thefound VPN already exists in L2VPN Management. New VPN indicates that a newVPN is found.

• VPN Name—Name of the found VPN.

• VPN Protocol Type—Type of the found VPN. Options are VPLS, VLL, PBB, andVPLS+PBB. If the VPN is a BGP VPN, this field displays BGP.

• ID Value—The ID value in this field depends on the VPN type. It might be the VSI ID,PW ID, or I-SID. If the VPN type is VPLS+PBB, this field displays the VSI ID and I-SID.

• PW Transport Mode—Options are VLAN and Ethernet.

• VPN Description—Description of the found VPN.b. Select one or multiple VPNs in the VPN List Found.c. Click Next.

7. Configure VRF binding relationships.This step configures CE information for the new links.a. Select or clear the Create non-managed CE automatically box.

If you select the Create non-managed CE automatically box, the system automaticallycreates a non-managed CE for a link without any CE device. If you clear the Create

non-managed CE automatically box, click the Modify icon in the New Link List tomanually specify a CE device for a link.

b. View the New Links List.New Links List contents



• PE Interface—Name of the PE's interface that connects to the CE device.

• Service Instance ID—ID of the service instance.


• Modify—Click the Modify icon to enter the Select Device page. Select a CEdevice and click OK to return to the New Links List.

c. Select multiple links to be added to L2VPN Management.d. Click Finish.The Summary page displays the VPN link configuration results.VPN Link Configuration Result contents



• PE Interface—Name of the PE device's interface that connects to the CE device.


• Result—Result of the VPN configuration, Success or Failure.


L2VPN topologyThe L2VPN topology shows connections between PEs and CEs for each L2VPN. You can viewL2VPN information for a PE device, view information about an AC, remove an AC, and audit aVPN.

Entering L2VPN topology1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > L2VPN Topology.

The page that shows the topology appears.

Viewing a specific VPN topology1. On the toolbar at the top of the topology page, click the VPN List icon.

The VPN List tab appears at the right of the topology.2. Enter or select one or more of the following query criteria:

• Name—Enter the VPN name.

• Type—Select a VPN type from the drop-down list. Options are All and BGP.3. Click Query.

The VPN List displays all VPNs matching the query criteria.4. Click Reset to clear the query criteria, and display all VPNs.5. Double click a VPN in the VPN List.


Topology operations

Viewing device VPN information1. Right-click a PE device.2. Select L2VPN Info from the shortcut menu.

The page for the L2VPN information appears. For information about L2VPN information, see"Viewing L2VPN information on a PE."

Viewing PW information1. Right-click the PW between two PEs.2. Select PW Info from the shortcut menu.

The page for the PW information appears. You can view the PW connectivity status, left device,right device, PW type, PW encapsulation type, and failure reason on the page.

Auditing a VPNRight-click the blank and select Audit from the shortcut menu.The message Start VPN Auditing is displayed in the log area below the topology. After a periodof time, you can view the audit results in the VPN List.

ApplicationIn this chapter, PEs are H3C S95 and S75 series switches.Configuration commands executed on the devices depend on the device model and softwareversion. For more information about the commands in this chapter, see the manual for the device.

L2VPN topology 171

Managing an BGP VPLS VPN

Network requirementsAs shown in Figure 53, a customer has two sites CE 1 and CE 2 that connect to PE 1 and PE 2through VLAN 100. Configure an LDP VPLS VPN so that the customer sites can communicate inVLAN 100 over the MPLS network.





Importing PE 1 and PE 21. Click the Service tab.2. From the navigation tree, select L2VPN Manager > VPN Devices > PE Devices.


The Import Device page appears.4. Click Select Device to select PE 1 and PE 2.5. Click OK to enter the Import Device page.6. Click OK.The page for import results appears. You can see that the two PEs are imported.


Auto Discovering BGP VPLS VPN1. Click the Service tab.2. From the navigation tree, select L2VPN Manager > Auto Discovery.


a. Enable Synchronize PE device before auto discovery for Auto Discovery Parameter Settings.b. Click Select PE to select PE1 and PE2.

4. Click Auto Discovery.A process bar for VPN auto discovery appears.


6. Select VPNs whose links are to be configured:a. Select VPN bbb in the VPN List Found.b. Click Next.

7. Configure VRF binding relationships.

a. Click the Modify icon of the PE1 to enter the Select Device page. Select CE1 andclick OK to return to the New Links List.

b. Click the Modify icon of the PE2 to enter the Select Device page. Select CE2 andclick OK to return to the New Links List.

c. Select those two links to be added to L2VPN Management.d. Click Finish.




• Name—Enter VPN name VPLS001.

• Type—Select VPLS from the list.5. Click Query.

All matching devices are displayed in the VPN List area.

Managing an BGP VPLS VPN 173

6. Double click a VPN in the VPN List.The topology for the VPN is displayed.



6 Using MPLS TE ManagementMPLS TE Management overview

TE and MPLSNetwork congestion is one of the major problems that can degrade your network performance. Itmay occur either when network resources are inadequate or load distribution is unbalanced.TE can best utilize network resources and avoid uneven load distribution by real-time monitoringtraffic and traffic load on each network element. The purpose is to dynamically tune trafficmanagement attributes, routing parameters and resources constraints.To implement TE, you can use interior gateway protocols (IGPs) or Multiprotocol Label Switching(MPLS). Because IGPs are topology-driven and include only network connectivity, they fail to presentsome dynamic factors such as bandwidth and traffic characteristics. MPLS TE remedies this IGPdisadvantage, and for a large-scale backbone network, it is an excellent TE solution for its greatextensibility and ease of implementation.MPLS is better than IGPs in implementing traffic engineering for the following reasons:• MPLS supports explicit label switched path (LSP) routing.

• LSP routing is easy to manage and maintain compared with traditional packet-by-packet IPforwarding.

• Constraint-based Routed Label Distribution Protocol (CR-LDP) is suitable for implementing avariety of traffic engineering policies.

• MPLS TE uses less system resources compared with other traffic engineering implementations.

MPLS TE ManagementThe MPLS TE Management component is a simple, efficient, visual management tool. It helps youmanage network operations and assign network resources reasonably. The MPLS TE Managementprovides these functions: MPLS TE topology, resource management, advanced RSVP-TE features,MPLS TE tunnel Management, explicit path management, protection management, and trafficaccess management.• TE Topology—This function provides a graphical view of all MPLS TE tunnel information, visually

reflecting the current network performance. You can use the information to optimize the networkperformance.

• Resource Management

Device Management—This function allows you to import and synchronize MPLS TE devices.Devices to be imported must support MPLS TE. The devices support manual synchronizationand automatic synchronization.

◦

◦ Interface Management—This function allows you to configure interfaces of devices toimplement MPLS TE.

• RSVP TE Advanced Features

Device Features—This function allows you to perform device RSVP TE configurations onMPLS TE devices.

◦

◦ Interface Features—This function allows you to perform interface RSVP TE configurationson MPLS TE devices.

• MPLS TE Tunnel Management—This function helps you establish MPLS TE tunnels, includingstatic and dynamic tunnels. This allows traffic to bypass congested nodes to achieve appropriateload distribution.

MPLS TE Management overview 175

• Explicit Path Management—This function allows you to configure explicit paths for dynamictunnels.

• Protection Management—This function helps you with dynamic tunnel protection, includingCR-LSP backup and FRR, so that traffic is switched to another path when the current linkencounters a problem or congestion occurs on a network node.

• Traffic Access Management—This function allows you to manage traffic of MPLS TE tunnels tokeep the system performance stable.

Basic concepts

LSP and MPLS TE tunnelFigure 55 shows the LSPs and MPLS TE tunnels.

Figure 55 LSP and MPLS TE tunnel

• LSP—A label switched path (LSP) is a path through an MPLS network, set up by a signalingprotocol such as LDP, RSVP TE, BGP or CR-LDP. The path is set up based on criteria in theforwarding equivalence class (FEC), a term used in MPLS to describe a set of packets withsimilar or identical characteristics which may be forwarded the same way so they may bebound to the same MPLS label.

• MPLS TE tunnel—Reroute and transmission over multiple paths may involve multiple LSP tunnels.A set of such LSP tunnels is called a traffic engineered tunnel (TE tunnel).

In Figure 55, the LSP along Router B —> Router J —> Router D is a static LSP. It is created to bypassRouter C, which might be a congested node. A static LSP is created along fixed route with fixednodes, so that the traffic is forced to go along Router B —> Router J —> Router D.The tunnel from Router C to Router F is a dynamic tunnel created using dynamic signaling protocolRSVP-TE. Between Router C and Router F there are several LSPs. Unlike the traditional networksthat perform routing based on only cost values, MPLS TE calculates the shortest path to a nodebased on cost values and constraints on the LSP with respect to bandwidth, color, setup/holdpriority, explicit path and other constraints, as well as TEDB. LSP along Router G —> Router I —>Router H is a dynamic LSP. It is created to protect the link between Router G and Router H so thatonce the link between Router G and Router H breaks down, traffic can travel along Router G —>Router I —> Router H.In Figure 55, tunnel 1 is a static tunnel and tunnel 2 is a dynamic tunnel.

176 Using MPLS TE Management

MPLS TE implementationMPLS TE mainly accomplishes the following functions:• Static Constraint-based Routed LSP (CR-LSP) processing to create and remove static CR-LSPs.

The bandwidth of a static CR-LSP must be configured manually.• Dynamic CR-LSP processing to handle three types of CR-LSPs: basic CR-LSPs, backup CR-LSPs

and fast rerouted CR-LSPs.Static CR-LSP processing is simple, while dynamic CR-LSP processing involves four phases: advertisingTE attributes, calculating paths, establishing paths, and forwarding packets.

Advertising TE attributesMPLS TE must be aware of dynamic TE attributes of each link on the network. This is achieved byextending link state-based IGPs such as OSPF and IS-IS.OSPF and IS-IS extensions add to link states such TE attributes as link bandwidth, color, amongwhich maximum reservable link bandwidth and non-reserved bandwidth with a particular priorityare most important.Each node collects the TE attributes of all links on all routers within the local area or at the samelevel to build up a TE database (TEDB).

Calculating pathsLink state-based routing protocols use Shortest Path First (SPF) to calculate the shortest path to eachnetwork node.In MPLS TE, the Constraint-based Shortest Path First (CSPF) algorithm is used to calculate the shortest,TE compliant path to a node. It is derived from SPF and makes calculation based on two conditions:• Constraints on the LSP to be set up with respect to bandwidth, color, setup/hold priority,

explicit path and other constraints. They are configured at the LSP ingress.• TE database (TEDB)CSPF first prunes TE attribute incompliant links from the TEDB, and then performs SPF calculationto identify the shortest path to an LSP egress.

Establishing pathsThe head-end node establishes a tunnel to the tail-end node using a signaling protocol called RSVPTE. It can carry constraints such as LSP bandwidth, some explicit route information, and color.

Forwarding packetsPackets are forwarded over established tunnels.

MPLS TE Management workflowTo use MPLS TE Management effectively in your network environment, it is helpful to understandthe recommended workflow, as shown in Figure 56.

MPLS TE Management overview 177

Figure 56 MPLS TE Management workflow

Workflow tasks are summarized as follows:1. Import and configure network devices, such as routers, switches, and other devices that support

MPLS TE. To ensure that a device can be imported to the MPLS TE system properly, performthe following operations on the device:a. Configure the loopback address and the LSR ID IP address.b. Configure a static route or an IGP protocol (such as OSPF) to make sure that the device

is reachable on the network and the LSR ID of the device is advertised to the networkthrough the routing protocol.

c. Make sure that MPLS TE basic capabilities have been enabled on devices. Commandsfor enabling MPLS TE basic capabilities differ from device to device, for detailedinformation about how to enable MPLS TE basic capabilities on your device, see theconfiguration guide of the device.

2. Adjust device configurations, such as the device CR-LSP arbitrage policy and the trafficforwarding parameters.

3. Configure explicit path (optional). This step is not necessary in static CR-LSP tunnel configuration,and is optional in dynamic tunnel configuration. An explicit path consists of a series of nodesand is used to restrict the path that a tunnel is to pass. When configuring a tunnel, you canbind a configured explicit path.

4. Create a tunnel. You can configure an MPLS TE tunnel using static CR-LSP, a dynamic signalingprotocol RSVP TE or CR-LDP. Configuring an MPLS TE tunnel through a static CR-LSP requiresno tunnel constraints and involves no TE extension of any IGP or CSPF calculation. Configuringa tunnel through a dynamic signaling protocol is more complicated. The dynamic signalingprotocol can dynamically adjust the path of the TE tunnel according to the network performance,and supports advanced features such as backup and Fast Reroute (FRR).

5. Configure protection (optional). MPLS TE Management allows you to configure a backup pathand FRR protection for a network node or link. Once the node or link fails, traffic is reroutedto the backup path for forwarding.

6. Configure traffic access. Data can be forwarded along the tunnel only after you introduce thetraffic to the tunnel.


7. View the MPLS TE network topology (optional). You can zoom in or out of the topology view,display the vertical view of the topology, display the TE link information, and filter links bytunnel and by administrative group.

Configuring traffic engineering in MPLS TE ManagementMPLS TE Management works with the devices that form the basis of your network infrastructure.After you install and deploy MPLS TE Management through the HP Intelligent Deployment MonitoringAgent, you can launch IMC in your browser, access MPLS TE Management, and work with supporteddevices.You need to make sure that the devices have been imported into IMC basic platform and that MPLSand MPLS TE basic capabilities are enabled on your devices before you can manage your TEnetworks using MPLS TE Management. The configuration instructions for enabling MPLS and MPLSTE basic capabilities may differ from device to device. For detailed configuration instructions, seethe configuration guide of your device.

Configuring MPLS basic capabilitiesBefore you configure MPLS basic capabilities, complete the following tasks:• Configure link layer protocols to ensure the connectivity at the link layer.

• Assign IP addresses to interfaces, making all neighboring nodes reachable at the networklayer.

• Configure static routes or an IGP protocol, ensuring that LSRs can communicate with eachother at the network layer.

Configuring MPLS TE basic capabilitiesAfter configuring the basic capabilities, you need to make additional configurations in order touse MPLS TE depending on the actual requirements.

Configuration prerequisitesBefore you configure MPLS TE basic capabilities, do the following:• Configure Static Routing or IGPs to make sure all LSRs are reachable.

• Configure MPLS basic capabilities.

Managing devicesWith the Device Management function, as shown in Figure 57, you can import MPLS TE devices,synchronize and query for imported devices, configure the CR-LSP arbitrage policy, traffic forwardingparameters, Fast Reroute (FRR) scanning intervals, and automatically adjust bandwidth for theimported devices.

Figure 57 Device Management page

Configuring traffic engineering in MPLS TE Management 179

Importing devices into MPLS TE ManagementTo work with MPLS TE devices in MPLS TE Management, first import them to the IMC basic platformusing the device auto-discovery function provided by the IMC basic platform, after that, manuallyimport them into MPLS TE Management using the MPLS TE Management Import function.

Device auto-discoveryWhen you first install and deploy IMC, you can access the Auto Discovery command from theResource menu to find the supported devices on your network.If you install and deploy MPLS TE Management before running Resource > Auto Discovery, supporteddevices are discovered and shown in the main IMC device list. Then you can import them manuallyinto MPLS TE. However, if you install and deploy MPLS TE Management after running AutoDiscovery, import supported devices into MPLS TE Management as a separate step. You can onlyimport devices that support MPLS TE into MPLS TE Management.To ensure that a device can be imported to the MPLS TE system properly, perform the followingoperations on the device:• Configure the loopback address and the LSR ID IP address.

• Configure a static route or an IGP protocol (such as OSPF) to make sure that the device isreachable on the network and the LSR ID of the device is advertised to the network throughthe routing protocol.

• Make sure that the MPLS TE basic capabilities are enabled on your devices.

Import functionWhen you install and deploy MPLS TE Management after having installed and deployed IMC,devices are not automatically imported into the MPLS TE Management device list. In this case, youcan use the MPLS TE Management Import function to populate the device list.To import a device into MPLS TE Management:1. Click Service > MPLS TE Manager from the tabular navigation system on the top of the IMC

main page.2. Click Resource Mng > Device Mng in the left navigation tree. The Device Management screen

appears, as shown in Figure 58.

Figure 58 Device Management screen

3. In the Device List section of the page, click Import Device > Select Device. The Select Devicesscreen appears, as shown in Figure 59.


Figure 59 Select Devices screen

4. Specify the devices that you want to import.• To specify a range of devices by IP address, select IP View in the left panel. In the Devices

Found panel, select a range of IP addresses and click the Add selected icon to copy

the devices to the Selected Devices panel. Alternatively, select the Add all icon tocopy all devices to the Selected Devices panel.

• To specify devices directly, select Device View in the left panel. In the Devices Found

panel, select a range of devices and click the Add selected icon to copy the devices

to the Selected Devices panel. Alternatively, select the Add all icon to copy all devicesto the Selected Devices panel.

5. After all devices are displayed correctly in the Selected Devices panel, click OK to return tothe Import Device page.

6. Click OK to enter the import result page.7. Click Result to return to the Device Management page to view the imported devices.

NOTE: Only devices that support MPLS TE are imported to the MPLS TE Management. Theseinclude many HP routers and switches.

Querying for a deviceOver time, the device list can grow large, making it more difficult to find a device at a glance. TheQuery capability enables you to search for devices by device name or device IP address. Fuzzymatching is supported, allowing you to enter a partial or complete string for the device name ordevice IP address.To query for a device:1. Click Service > MPLS TE Manager > Resource Mng > Device Mng.2. In the Device Query section of the page, enter all or part of the entire device name or IP

address/mask.


3. Click the Query button.The device list is narrowed to the devices that meet the search criteria.

4. To clear the search criteria, click the Reset button.

Synchronizing devicesSynchronizing devices assures you that the configuration information of a device you are viewingin the Device List section of the MPLS TE Management has been synchronized with the latestconfiguration on the device. By synchronizing devices, the system updates the configuration of thedevice in the MPLS TE Management system.To synchronize one or more devices:1. Click Service > MPLS TE Manager from the tabular navigation system on the top of the IMC

main page.2. Click Resource Mng > Device Mng in the left navigation tree.3. In the Device List section of the page, select one or more devices that you want to synchronize,

and then click the Synchronize button. The synchronization status is displayed in theSynchronization Status column.

Deleting devicesYou can delete one or more devices from the MPLS TE Management system.To delete one or more devices:1. Click Service > MPLS TE Manager from the tabular navigation system on the top of the IMC

main page.2. Click Resource Mng > Device Mng in the left navigation tree.3. In the Device List section of the page, select one or more devices that you want to delete, and

then click the Delete button.4. Click OK.

NOTE: Deleting a device from the system also deletes the interfaces related to the device.Devices referenced by MPLS TE tunnels cannot be deleted.

Configuring imported devicesThis function helps you configure the CR-LSP arbitrage policy, configure traffic forwardingparameters, set the FRR scanning interval, configure auto bandwidth adjustment, enable or resetauto bandwidth adjustment, and enable MPLS TE for devices that are already imported to the MPLSTE Management. You can decide which configurations to make according to real needs.To configure an imported device:1. Click Service > MPLS TE Manager from the tabular navigation system on the top of the IMC

main page.2. Click Resource Mng > Device Mng in the left navigation tree.

3. In the Device List section of the page, click the Operation icon on the same line as thedevice that you want to configure. A list appears, as shown in Figure 60.


Figure 60 List for device operation

4. In the list, you can:a. Select the Configure CR-LSP Arbitrage Policy option to configure the CR-LSR arbitrage

policy for the device.CR-LSP Arbitrage Policy—When CSPF is calculating the shortest path to the end of atunnel, if multiple paths are present with the same metric value, only one is selectedaccording to the CR-LSP arbitrage policy. CR-LSP arbitrage policy prioritizes the selectionin the following order: Min Bandwidth (path with the lowest bandwidth usage ratio ispreferred), Max Bandwidth (path with the highest bandwidth usage ratio is preferred),and Random (one of the remaining paths is picked at random. This rule tends to placean equal number of LSPs on each link, regardless of the available bandwidth ratio).

b. Select the Configure Traffic Forwarding Parameters option to configure the invalid linktimer and the link metric type for the device. The invalid link timer starts once a link goesdown. If IGP removes or modifies the link before the timer expires, CSPF is informed ofthe change and it then updates information about the link in TEDB and stops the timer. IfIGP does not remove or modify the link before the timer expires, the state of the link inTEDB changes to up. The default value of the invalid link timer is 10 seconds and thevalid range is 0 to 300 seconds. The link metric type is used when no metric type isexplicitly configured for a tunnel. Link metric type can be configured as TE or IGP, andthe default option is TE.

c. Select the Configure FRR Scanning Interval option to configure the interval of FRR scanningfor the device. The protection provided by FRR is temporary. Once a protected LSPbecomes available again or a new LSP is established, traffic is switched to the protectedor new LSP. After this switchover, the point of local repair (PLR), the ingress of the bypassLPS, polls available bypass tunnels for the best one at the regular interval. You canconfigure this regular interval here.

d. Select the Enable Auto Bandwidth Adjustment option to set the output rate samplinginterval for the device. As data traffic increases or decreases due to the size and type ofdata being transmitted, there is therefore a general need that allows automatic bandwidthadjustment in optimizing bandwidth usage and thereby improving bandwidth efficiency.The valid range of output rate sampling interval is 1 to 604800. If the value is null thenundo this function on device.

e. Select the Reset Auto Bandwidth Adjustment option to reset the auto bandwidth adjustmentconfiguration for the device. You can reset the auto bandwidth configuration only afteryou have configured the auto bandwidth adjustment function.

Managing device interfacesWith the interface management function, you can manage all MPLS TE enabled interfaces of thedevices imported to the MPLS TE Management system. You can query for an interface, configure


an interface, query for available bandwidth, configure interface traffic parameters, and disablean enabled interface.

Querying for an interfaceA device may have many interfaces, thus making the interface list quite large. Therefore, it becomesmore difficult for you to find an interface at a glance. The Query capability enables you to searchfor an interface by its device name, interface description, interface IP, and interface status.To query for an interface:1. Click Service > MPLS TE Manager from the tabular navigation system on the top of the IMC

main page.2. Click Resource Mng > Interface Mng in the left navigation tree.3. In the Interface Query field, enter information about the interface you want to query, and then

click the Query button to display only interfaces that match the description.4. To clear the search criteria, click the Reset button.

Configuring an interfaceYou can configure the MPLS TE interface information, including the management group information,maximum connection bandwidth and maximum reserved bandwidth.Management Group—The management group is also called resource class/color. Resource classattributes are administratively assigned parameters which express some notion of “class” forresources. You can view resource class attributes as “colors” assigned to resources such that theset of resources with the same “color” conceptually belong to the same class. You can use resourceclass attributes to implement a variety of policies. When you apply them to links, the resource classattribute effectively becomes an aspect of the “link state” parameters.You can use the concept of resource class attributes to implement many policies with regard toboth traffic and resource oriented performance optimization. You can use resource class attributesto:• Apply uniform policies to a set of resources that do not need to be in the same topological

region.• Specify the relative preference of sets of resources for path placement of traffic trunks.

• Explicitly restrict the placement of traffic trunks to specific subsets of resources.

• Implement generalized inclusion/exclusion policies.

• Enforce traffic locality containment policies, that is, policies that seek to contain local trafficwithin specific topological regions of the network.

Additionally, resource class attributes can be used for identification purposes.Maximum reserved bandwidth—By default, a QoS policy applied in internetwork operating system(IOS) only reserves up to 75% of the available bandwidth of a link. The reason is to leave someheadroom for routing protocols and other critical traffic that might not otherwise be accounted forin a QoS policy. While this is effective for low-speed links, it leaves potential for a large amountof wasted bandwidth on high-speed links. For example, on a 10 Mbps Ethernet link, only 7.5Mbps is available for use.You can use maximum reserved bandwidth on an MPLS TE tunnel interface to configure thebandwidth constraints of the tunnel interface by changing the default limit of 75% to somethingbetter suited to your needs. The router determines whether there is enough bandwidth to establishan MPLS TE tunnel.To configure an interface:1. Click Service > MPLS TE Manager from the tabular navigation system on the top of the IMC

main page.2. Click Resource Mng > Interface Mng in the left navigation tree.


3. In the Interface List section of the page, select an interface that you want to configure, andthen click the Configure button.

4. On the Device Interface Configuration page, enter information in the Management Group Infofield, Max Connect Bandwidth(kbps) field and Max Reserve Bandwidth(kbps) field. Make surethat the maximum reserved bandwidth is less than or equal to the maximum connectedbandwidth. The valid range of the management group info is 00000000 to FFFFFFFF. Thevalid range for max connect bandwidth and max reserve bandwidth is 1 to 32000000.

5. Click OK.

Querying for available bandwidthYou can view the available bandwidth information, which helps you with the interface configuration.To query for available bandwidth:1. Click Service > MPLS TE Manager from the tabular navigation system on the top of the IMC


3. In the Interface List section of the page, click the Operation icon on the same line as theinterface that you want to view bandwidth about. A list of options appears.

4. Select the Query Available Bandwidth option to view all available bandwidth.5. To return to the previous screen, click Back.

Configuring interface traffic parametersTo configure traffic parameters for an interface:1. Click Service > MPLS TE Manager from the tabular navigation system on the top of the IMC


3. In the Interface List section of the page, click the Operation icon on the same line as theinterface that you want to configure interface traffic parameters for. A list of options appears.

4. Select the Configure Interface Traffic Parameters option.5. In the Configure Interface Traffic Parameters page, enter information in the IGP flood upper

limit of bandwidth diversification (%) field andIGP flood lower limit of bandwidth diversification(%) field to configure the upper and lower thresholds for IGP to flood bandwidth changes,and enter information in the TE Metric of a Link field to assign TE metric to the link. The validrange of IGP flood upper limit of bandwidth diversification and IGP flood lower limit ofbandwidth diversification is 0 to 100 and the default value is 10. The valid range of TE metricof a link is from 0 to 4294967295, and the default value is 0.IGP flooding—After the bandwidth of links regulated by MPLS TE changes, CSPF may needto recalculate paths. This tends to be resource consuming as recalculation involves IGP flooding.To reduce recalculations and flood only significant changes, you may configure the followingtwo IGP flooding thresholds in percentages so that IGP flooding is triggered only when thethresholds are reached:• IGP flood upper limit of bandwidth diversification (%)—When the percentage of

available-bandwidth increase to the maximum reservable bandwidth exceeds the threshold,the change is flooded.

• IGP flood lower limit of bandwidth diversification (%)—When the percentage ofavailable-bandwidth decrease to the maximum reservable bandwidth exceeds thethreshold, the change is flooded.

6. Click OK.


Enabling interfacesWith this function, you can enable MPLS TE on a disabled interface.To enable MPLS TE on a disabled interface:1. Click Service > MPLS TE Manager from the tabular navigation system on the top of the IMC


3. In the Interface List section of the page, click the Operation icon on the same line as thedisabled interface that you want to enable. A list of options appears.

4. Select the Enable Interface option. This interface is enabled with MPLS TE.

Disabling interfacesWith this function, you can disable MPLS TE from an enabled interface.To disable MPLS TE capabilities from an enabled interface:1. Click Service > MPLS TE Manager from the tabular navigation system on the top of the IMC


3. In the Interface List section of the page, click the Operation icon on the same line as theenabled interface that you want to enable. A list of options appears.

4. Select the Disable Interface option. MPLS TE capabilities are disabled from this interface.

Advanced RSVP-TE features

RSVP and RSVP-TEResource Reservation Protocol (RSVP) is used for reserving resources on each node along a path.RSVP operates at the transport layer but does not participate in data transmission.The following are features of RSVP:• Unidirectional

• Receiver oriented. The receiver initiates resource reservation requests and is responsible formaintaining the reservation information.

• Using soft state mechanism to maintain resource reservation information.Extended RSVP can support MPLS label distribution and allow resource reservation information tobe transmitted with label bindings. This extended RSVP is called RSVP-TE, which is operating as asignaling protocol for LSP tunnel setup in MPLS TE. RSVP-TE provides many configuration optionswith respect to reliability, network resources, and other advanced features of MPLS TE.

Prerequisites for configuring RSVP TE advanced featuresBefore configuring RSVP-TE advanced features, do the following:1. Configure MPLS basic capabilities.2. Configure MPLS TE basic capabilities.3. Establish an MPLS TE tunnel with RSVP-TE.You need to make sure that MPLS and MPLS TE basic capabilities are enabled on your devicesbefore you can manage your TE networks using MPLS TE Management. The configuration instructionsfor enabling MPLS and MPLS TE basic capabilities may differ from device to device. For detailedconfiguration instructions, see the configuration guide of your device.


Querying for RSVP TE device featuresOver time, the device features list can grow large, making it more difficult to find features of adevice at a glance. The Query capability enables you to search for RSVP TE device features of adevice by device name or device IP address/mask.To query for RSVP TE features of a device:1. Click Service > MPLS TE Manager from the tabular navigation system on the top of the IMC

main page.2. Click RSVP TE Advanced Features > Device Features in the left navigation tree.3. Specify part or all of the device name or IP address, and then click the Query button to display

only devices that match the description.4. To clear the query criteria, click the Reset button.

Configuring RSVP for a deviceYou can configure RSVP information for a device.To configure RSVP information for a device:1. Click Service > MPLS TE Manager from the tabular navigation system on the top of the IMC

main page.2. Click RSVP TE Advanced Features > Device Features in the left navigation tree.

3. Click the Configuration icon on the same line as the RSVP device that you want to configure.The Configure Device RSVP page appears, as shown in Figure 61.

Figure 61 Configure Device RSVP page


4. Enter the following parameters:• Path/Reserve Message Refresh Interval(s)

RSVP maintains path and reservation state by periodically retransmitting two types ofmessages: Path message and Reserve message. These periodically retransmitted Pathand Reserve messages are called refresh messages. They are sent along the path the lastPath or Reserve message travels to synchronize state between RSVP neighbors and recoverlost RSVP messages.Where many RSVP sessions are present, periodically sent refresh messages become anetwork burden. In addition, for some delay sensitive applications, the refreshing delaythey must wait for recovering lost RSVP messages may be unbearable. Therefore, youcan set the Path/Reserve message refresh interval(s) to address such problems.The valid range of Path/Reserve message refresh interval is from 10 seconds to 65535seconds, and the default value is 30 seconds.

• PSB and RSB Timeout MultiplierTo create an LSP tunnel, the sender sends a Path message with a LABEL_REQUEST object.After receiving this Path message, the receiver assigns a label for the path and puts thelabel binding in the LABEL object in the returned Resv message. The LABEL_REQUESTobject is stored in the path state block (PSB) on the upstream nodes, while the LABELobject is stored in the reservation state block (RSB) on the downstream nodes. The statestored in the PSB or RSB object times out and is removed after the number of consecutivenon-refreshing times exceeds the PSB or RSB timeout keep-multiplier. The valid range ofPSB and RSB timeout multiplier is from 3 to 255, and the default value is 3.

• Blockade Timeout MultiplierYou may sometimes want to store the resource reservation state for a reservation requestthat does not pass the admission control on some node. This however should not preventthe resources reserved for the request from being used by other requests. To handle thissituation, the node transits to the blockade state and a blockade state block (BSB) iscreated on each downstream node. When the number of non-refreshing times exceedsthe blockade multiplier, the state in the BSB is removed. The default value is 4.

• Resource Reservation ConfirmationIf you select Enabled from the Resource Reservation Confirmation list, you enable the RSVPconfirmation feature, which is used for improving the reliability of message transfer.

Configuring device RSVP HELLO extension informationThe RSVP HELLO extension is configured to detect node failures. You can use this function to detectthe reachability of RSVP neighboring nodes.To configure device RSVP HELLO extension information:1. Click Service > MPLS TE Manager from the tabular navigation system on the top of the IMC

main page.2. Click RSVP TE Advanced Features > Device Features in the left navigation tree.

3. Configure the Modify icon on the same line as the RSVP device that you want to configure.The Configure Device RSVP HELLO Extension Info page appears, as shown in Figure 62.


Figure 62 Configure Device RSVP Hello Extension Info page

4. In the Max Number of Consecutive Hello Messages Allowed to Be Lost field, configure themaximum number of consecutive hellos that should be lost before the link is considered failed.The valid range is 3 to 10, and the default value is 3.

5. In the Interval Between sending Hello messages (s) field, configure the hello interval. The validrange is from 1 to 60, and the default value is 3.

6. Click OK.

Querying for interface RSVP TE informationOver time, the RSVP TE interface features list can grow large, making it more difficult to find featuresof an interface at a glance. The Query capability enables you to search for RSVP TE informationof an interface by its device name or device IP address.To query for interface RSVP TE information:1. Click Service > MPLS TE Manager from the tabular navigation system on the top of the IMC

main page.2. Click RSVP TE Advanced Features > Interface Features in the left navigation tree.3. In the Interface Features Query section of the page, enter the information about the interface,

and then click the Query button to display only interfaces that match the description.4. To clear the query criteria, click the Reset button.

NOTE: The interface you want to query for must be an MPLS TE enabled interface.

Configuring and modifying interface RSVP attributesTo configure and modify interface RSVP attributes:1. Click Service > MPLS TE Manager from the tabular navigation system on the top of the IMC

main page.2. Click RSVP TE Advanced Features > Interface Features in the left navigation tree.3. In the Interface Features List section of the page, select the interface that you want to configure,

and then click the Configure button. The Configure Interface RSVP TE Attributes page appears,as shown in Figure 63.


Figure 63 Configure Interface RSVP TE Attributes page

4. Configure the following parameters:• Retransmission Increment Value and Retransmission Period (ms).

You may configure RSVP message retransmission. After the interface sends an RSVPmessage, it waits for acknowledgment. If no acknowledgment is received before the initialretransmission interval expires, the interface resends the message. After that, the interfaceresends the message at an exponentially increased retransmission interval. The validrange of retransmission increment value is from 1 to 10. If the value is null, then shutdown the retransmission function on the device. The valid range of retransmission periodis from 500 to 3000. If the value is null, then shut down the retransmission function onthe device.

• Summary RefreshSend summary refreshes rather than retransmit standard Path or Resv messages to refreshrelated RSVP state. This reduces refresh traffic and allows nodes to make faster processing.You can select Enabled from the Summary Refresh list to enable the summary refresh.

• RSVP Hello ExtensionThe RSVP Hello Extension attribute detects the reachability of RSVP neighboring nodes.You can select Enabled from the RSVP Hello Extension list to enable the reachabilitydetection.

5. Click OK.

Configuring an MPLS TE tunnel using static CR-LSPUnlike ordinary LSPs established based on routing information, CR-LSPs are established based oncriteria such as bandwidth, selected path, and QoS parameters in addition to routing information.The mechanism setting up and managing constraints is called Constraint-based Routing (CR). Ifyou want to create an MPLS TE tunnel along a fixed route with fixed nodes, you can create it usingstatic CR-LSP. Creating MPLS TE tunnels using static CR-LSPs does not involve configuration of tunnelconstraints or the issue of IGP TE extension or CSPF.Despite its ease of configuration, the application of MPLS TE tunnels using static CR-LSPs is restrictedbecause they cannot dynamically adapt to network changes.


Configuration prerequisitesBefore making the configuration, do the following:• Configure Static Routing or an IGP protocol to make sure that all LSRs are reachable.


• Configure MPLS TE basic capabilities.You need to make sure that MPLS and MPLS TE basic capabilities are enabled on your devicesbefore you can manage your TE networks using MPLS TE Management. The configuration instructionsfor enabling MPLS and MPLS TE basic capabilities may differ from device to device. For detailedconfiguration instructions, see the configuration guide of your device.

Configuration procedureTo configure an MPLS TE tunnel using static CR-LSP:1. Import devices into MPLS TE Management.2. Click Service > MPLS TE Manager > MPLS TE Tunnel Mng from the tabular navigation system

on the top of the IMC main page.3. In the MPLS TE Tunnel Query List section, click Add.

The Configure Static CR-LSP page appears, as shown in Figure 64.

Figure 64 Configure Static CR-LSP page

4. Specify the configuration information for the static CR-LSP.a. Select the ingress device for the MPLS TE tunnel. Click Select next to Select Device. On

the Select Device page, specify part or the entire name of the ingress device, and thenclick Query. Devices that match the description appear in the Device Query List sectionof the page. Select the ingress device, and then click OK.

b. On the Configure Static CR-LSP page, click Select next to MPLS TE Tunnel Name. Enterthe name of the tunnel, and then click OK.

c. Select Static CR-LSP from the Protocol list.d. Enter the loopback address of the egress device in the field of Destination IP Address

(A.B.C.D), and then click Next.5. In the Configure Static CR-LSP page, click Add.

The Add Static CR-LSP Node screen with Ingress selected as the role appears, as shown inFigure 65.


Figure 65 Add Static CR-LSP Node screen with Ingress selected as the role

6. Add an ingress device node.a. Click Select next to Select Device. In the Select Device page, specify part or the entire

name of the ingress device, and then click Query. Devices that match the descriptionappear in the Device Query List section of the page. Select the ingress device, and thenclick OK.

b. Select Ingress from the Select Role list.c. In the Destination Address (A.B.C.D) field, enter the loopback address of the egress device.d. In the Next Hop (A.B.C.D) field, enter the IP address of your next hop.e. Next to Out Label, enter the out label value, and then click Detect to see if this value is

available.f. Click OK. The information of the ingress device appears in the Configure Static CR-LSP

section of the page.7. Add a transit device node.

a. In the Configure Static CR-LSP section of the page, click Add.The Add Static CR-LSP Node screen with Transit selected as the role appears, as shownin Figure 66.

Figure 66 Add Static CR-LSP Node screen with Transit selected as the role

b. Click Select next to Select Device. In the Select Device page, specify part or the entirename of the transit device that is immediately connected to the ingress device, and thenclick Query. Devices that match the description appear in the Device Query List sectionof the page. Select the transit device, and then click OK.

c. Select Transit from the Select Role list. The In Interface field is populated with theinformation of the interface connecting to the ingress device.


d. In the In Label field, enter the in label value, and then click Detect to see if this value isavailable. Make sure that the in label value is the same as the out label value of theprevious node.

e. In the Next Hop (A.B.C.D) field, enter the IP address of the next hop.f. In the Out Label field, enter the out label value of the transit device, and then click Detect

to see if this value is available.g. Click OK. The information of the transit device appears in the Configure Static CR-LSP

section of the page.8. Add an egress device node.

a. In the Configure Static CR-LSP section of the page, click Add.The Add Static CR-LSP Node screen with Egress selected as the role appears, as shownin Figure 67.

Figure 67 Add Static CR-LSP Node screen with Egress selected as the role

b. Click Select next to Select Device. In the Select Device page, specify part or the entirename of the egress device, and then click Query. Devices that match the descriptionappear in the Device Query List section of the page. Select the egress device, and thenclick OK.

c. Select Egress from the Select Role list. The In Interface field is populated with the informationof the interface connecting to the transit device.

d. In the In Label field, enter the in label value, and then select Detect to see if this value isavailable. Make sure that the in label value is the same as the out label value of theprevious node.

e. Click OK. The information of the egress device appears in the Configure Static CR-LSPsection of the page.

9. A complete LSP is established. Click Finish.

Managing static CR-LSP nodesYou can move, modify and delete a static CR-LSP node that you have added. By moving staticCR-LSP nodes you change the position of these nodes on an LSP route.To move a static CR-LSP node record:1. Click Service > MPLS TE Manager > MPLS TE Tunnel Mng. from the tabular navigation system

on the top of the IMC main page.2. In the Configure Static CR-LSP section of the page, click the radio button in front of the node

that you want to move.3. Click the Upwards button or the Downwards button to move the node record up or down in

the node list.To modify a static CR-LSP node that you have added:


1. Click Service > MPLS TE Manager > MPLS TE Tunnel Mng from the tabular navigation systemon the top of the IMC main page.

2. In the Configure Static CR-LSP section of the page, click the Modify icon to modify thebasic information of a node.

To delete a static CR-LSP node that you have added:1. Click Service > MPLS TE Manager > MPLS TE Tunnel Mng from the tabular navigation system


2. In the Configure Static CR-LSP section of the page, click the Delete icon to delete the node.

Configuring an MPLS TE tunnel using dynamic signaling protocolDynamic signaling protocol allows you to create an MPLS TE tunnel that can adapt to networkchanges and implement redundancy, FRR, and other advanced features. Unlike the MPSL TE tunnelcreated using static CR-LSP, the nodes along the tunnel created using dynamic signaling protocolare not necessarily fixed. However, if you want to specify certain nodes for your tunnel to traverse,you can specify them in an explicit path.The following describes how to create an MPLS TE tunnel with a dynamic signaling protocol:• Configure MPLS TE properties for links and advertise them through IGP TE extension to form

a TEDB.• Configure tunnel constraints.

• Use the CSPF algorithm to calculate a preferred path based on the TEDB and tunnel constraints.

• Establish the path using the signaling protocol RSVP-TE.

NOTE: To form a TEDB, you must configure the IGP TE extension for the nodes on the networkto send TE LSAs. If the IGP TE extension is not configured, the CR-LSP is created based on IGProuting rather than computed by CSPF.

Configuration prerequisitesBefore making the configuration, do the following:• Configure Static Routing or an IGP protocol to make sure that all LSRs are reachable.


• Configure MPLS TE basic capabilities.You need to make sure that MPLS and MPLS TE basic capabilities are enabled on your devicesbefore you can manage your TE networks using MPLS TE Management. The configuration instructionsfor enabling MPLS and MPLS TE basic capabilities may differ from device to device. For detailedconfiguration instructions, see the configuration guide of your device.

Configuring an MPLS TE explicit pathAn explicit path is a set of nodes. You can create an explicit path for an MPLS TE tunnel byspecifying the nodes for the tunnel to traverse. Configuring an explicit path is not necessary instatic CR-LSP tunnel configuration, and is optional in dynamic tunnel configuration.To configure an MPLS TE explicit path:1. Click Service > MPLS TE Manager > Explicit Path Mng from the tabular navigation system on

the top of the IMC main page.2. In the Explicit Path List section of the page, click Add.

The Add Explicit Path page appears, as shown in Figure 68.


Figure 68 Add Explicit Path page

3. Click Select next to Device Name, specify part or the entire name of the ingress device, andthen click Query. Devices that match the description appear in the Device Query List sectionof the page. Select it and click OK.

4. In the Explicit Path Name field, enter the name of the explicit path.5. Select Enabled from the Enable State list.6. Click Next.7. On the Next Hop Info List page, click Add.

The Next Hop Info page appears, as shown in Figure 69.

Figure 69 Next Hop Info page

8. In the Next Hop Address field, enter the IP address of your next hop.9. Select either Include or Exclude from the Next Hop Include Policy list. If you select the Include

option, the path traverses your next hop. If you select the Exclude option, the path bypassesyour next hop.

10. Select Strict or Loose from the Next Hop Strict Loose Policy list. The Strict option means twonodes are directly connected, and the Loose option means the two nodes have other devicesin between. If you select the Strict option, the next hop is directly connected to its previoushop. If you select the Loose option, you allow devices exist between the next hop and itsprevious hop.

11. Click OK. Information about your next hop is displayed in the Next Hop Info List section ofthe page. You can add more hops in the same way.

12. If you want to move a node that you already added, click the radio button in front of the node,and then click the Upwards button or the Downwards button to move the node upwards ordownwards.

13. When all hops needed are added, click Finish. The explicit path is created and is displayedin the Explicit Path List section of the Explicit Path Management page.


Managing an explicit pathYou can query, add, delete, and modify explicit paths that you have created. You can only modifyunbound explicit paths. Unbound explicit paths are not referred by tunnels.

Querying for an explicit pathOver time, the explicit path list can grow large, making it more difficult to find an explicit path ata glance. The Query capability enables you to search for explicit paths by explicit path name, itsdevice name, device LSR ID, enable state, and binding state.To query for an explicit path:1. Click Service > MPLS TE Manager > Explicit Path Mng from the tabular navigation system on

the top of the IMC main page.2. In the Explicit Path Query section of the page, enter the query criteria.3. Click Query. All explicit paths that match the query criteria display in the Explicit Path List

section of the page.4. To clear the query criteria and display all explicit paths, click Reset.To modify an explicit path:1. Click Service > MPLS TE Manager > Explicit Path Mng from the tabular navigation system on


2. In the Explicit Path List section of the page, click the Modify icon of an unbound explicitpath to enter the explicit path configuration page.

3. Modify the parameters as needed.

NOTE: You can only modify unbound explicit paths. You cannot modify the device nameor the explicit path name.

To delete one or more explicit paths:1. Click Service > MPLS TE Manager > Explicit path Mng from the tabular navigation system on

the top of the IMC main page.2. In the Explicit Path List section of the page, select one or more explicit paths, and then click

Delete.3. Click OK.

NOTE: Explicit paths that are in Bound state cannot be deleted.

Configuring a dynamic MPLS TE tunnelTo configure a dynamic MPLS TE tunnel:1. Click Service > MPLS TE Manager > MPLS TE Tunnel Mng from the tabular navigation system

on the top of the IMC main page.2. In the MPLS TE Tunnel Query List section of the page, click Add.

The Add Tunnel page appears, as shown in Figure 70.


Figure 70 Add Tunnel page


3. Specify the configuration information for the dynamic MPLS TE tunnel.a. Click Select next to Select Device, enter part or the entire name of the ingress device, and

then click Query. All devices that match the description appear in the Device Query Listsection of the page. Select the ingress device, and then click OK.

b. Click Select next to MPLS TE Tunnel Name, specify the tunnel name, and then click OK.c. Select RSVP-TE from the Protocol list.d. In the Destination IP Address (A.B.C.D) field, enter the loopback address of the egress

device, and then click Next. You are directed to the Configure Basic Attributes page, asshown in Figure 71.

Figure 71 Configure Basic Attributes page

e. Configure the parameters on this page as needed.Bandwidth (Kbps) and Backup Bandwidth (Kbps)—If one of the two parameters isconfigured, the other must be also configured, and the backup bandwidth must be greaterthan or equal to the bandwidth. The valid range of bandwidth and backup bandwidthis from 1 to 32000000.Setup Priority (0–7) and Hold Priority (0–7)—CR-LDP signals the resources required by apath on each hop of the route. If a route with sufficient resources cannot be found, existingpaths may be rerouted to reallocate resources to the new path. This is called pathpreemption. Two priorities, setup priority and hold priority, are assigned to paths formaking a preemption decision. Both setup and hold priorities range from 0 to 7, with alower numerical number indicating a higher priority.For a new path to preempt an existing path, the setup priority of the new path must begreater than the hold priority of the existing path. To initiate preemption, the Resv messageof RSVP-TE is sent.To avoid flapping caused by improper preemptions between CR-LSPs, the setup priorityof a CR-LSP should not be set higher than its hold priority.Reservation Style—Each LSP set up using RSVP-TE is assigned a resource reservation style.During an RSVP session, the receiver decides which reservation style can be used for thissession and which LSPs can be used.Two reservation styles are available:• Fixed-filter style (FF)—Where resources are reserved for individual senders and

cannot be shared among senders on the same session.• Shared-explicit style (SE)—Where resources are reserved for senders on the same

session and shared among them.


f. Click Next.You are directed to the Configure Path Policy page, as shown in Figure 72.

Figure 72 Configure Path Policy page

g. Configure the parameters as needed.Affinity (0–FFFFFFFF) and Affinity Mask (0–FFFFFFFF):The affinity attribute of an MPLS TE tunnel identifies the properties of the links that thetunnel can use. Together with the link administrative group, it decides which links theMPLS TE tunnel can use. This is done by ANDing the 32-bit affinity attribute with the 32-bitlink administrative group attribute. When doing that, a 32-bit mask is used. The affinitybits corresponding to the 1s in the mask are “do care” bits which must be consideredwhile those corresponding to the 0s in the mask are “don’t care” bits.For a link to be used by a TE tunnel, at least one considered affinity bit and itscorresponding administrative group bit must be set to 1.Suppose the affinity of an MPLS TE tunnel is 0xFFFFFFFF and the mask is 0x0000FFFF.For a link to be used by the tunnel, the leftmost 16 bits of its administrative group attributecan be 0s or 1s, but at least one of the rest bits must be 1.The affinity of an MPLS TE tunnel is configured at the first node on the tunnel, and thensignaled to the rest nodes through CR-LDP or RSVP-TE.

NOTE: The associations between administrative groups and affinities may vary byvendor. To ensure the successful establishment of a tunnel between two devices of differentvendors, correctly configure their respective administrative groups and affinities accordingto their configuration guides.

h. If you want the tunnel to refer to an explicit path that you have configured, click Selectnext to Explicit Path, enter part or the entire name of the explicit path, and then clickQuery. Explicit paths matching this description appear in the Explicit Path Query Listsection of the page. Select the explicit path you want, and then click OK.


i. Click Next. You are directed to the Configure Advanced Attributes page where you cansee the following parameters:Metric Type—Specify the metric type to use when no metric type is explicitly configuredfor a tunnel. You can select TE or IGP. TE metrics of links are used by default.When Multiprotocol Label Switching TE is configured in a network, the IGP floods twometrics for every link: normal IGP (OSPF or IS-IS) link metric and TE link metric.The IGP uses the IGP link metric in the normal way to compute routes for destinationnetworks, and MPLS TE used the TE link metric to calculate and verify paths for TE tunnels.You can specify the path calculation for a given tunnel based on either of these metrics.You can configure the TE link metrics so that they represent the needs of a particularapplication, for example, the TE link metrics can be configured to represent linktransmission delay.When TE tunnels are used to carry two types of traffic, you can tailor tunnel path selectionto the requirements of each type of traffic. For example, suppose certain tunnels are tocarry voice traffic (which requires low delay) and other tunnels are to carry data. Youcan use the TE link metric to represent link delay and do the following:• Configure tunnels that carry voice to use the TE link metric set to represent link delay

for path calculation.• Configure tunnels that carry data to use the IGP metric for path calculation.Unless explicitly configured, the TE link metric for a given link is the IGP link metric. Whenthe TE link metric is used to represent a link property that is different from cost/distance,you must configure every network link that can be used for TE tunnels with a TE link metricthat represents that property. Failure to do so might cause tunnels to use unexpectedpaths.Forwarding Type—You can select the traffic flow type of the tunnel. It limits the usage ofthe tunnel. Values include ACL, VPN Instance and No Limit.Loop Check—You can check if a loop exists.Tunnel Rebuild Times—You can configure the system to attempt setting up a tunnel multipletimes until it is established successfully or until the number of attempts reaches the upperlimit. The valid range is from 10 to 4294967295.Tunnel Rebuild interval(s)—You can configure the interval at which the tunnel is rebuilt.The valid range is from 1 to 4294967295.CSPF Method—You can configure the arbitrage policy of the current tunnel, which is usedfor path calculation.Route Fixing—If a route is fixed, the path information can not be changed.Tunnel Reoptimization—Dynamic CR-LSP optimization involves periodic calculation ofpaths that traffic trunks should traverse. If a better route is found for an existing CR-LSP,a new CR-LSP is established to replace the old one, and services are switched to the newCR-LSP. You can enable reoptimization for the MPLS TE tunnel.Auto Bandwidth Adjustment—As data traffic increases or decreases due to the size andtype of data being transmitted, you can enable the Auto Bandwidth Adjustmentfunctionality to optimize bandwidth usage and thereby improves bandwidth efficiency.Auto Bandwidth Adjustment Lower Threshold (Kbps)—The valid range is 1 to 32000000.Bandwidth Collection Lower Threshold (Kbps)—After the bandwidth of links regulated byMPLS TE changes, CSPF may need to recalculate paths. This tends to be resourceconsuming as recalculation involves IGP flooding. To reduce recalculations and floodonly significant changes, you may configure the bandwidth collection lower threshold.The valid range is 1 to 32000000.


j. Configure the parameters as needed, and then click OK. This tunnel appears in the MPLSTE Tunnel Query List section of the page.

Managing MPLS TE tunnelsYou can query, delete, refresh, modify, and view the network topology of an MPLS TE tunnel thatyou have created. You can also view detailed information about the ingress device and the MPLSTE tunnel.

Querying for an MPLS TE tunnelOver time, the MPLS TE Tunnel query list can grow large, making it more difficult for you to findan MPLS TE tunnel at a glance. The Query capability enables you to search for MPLS TE tunnelsby query type and its corresponding value.To query for an MPLS TE tunnel:1. Click Service > MPLS TE Manager > MPLS TE Tunnel Mng from the tabular navigation system

on the top of the IMC main page.2. In the MPLS TE Tunnel Query section of the page, select Tunnel Name, Protocol or Tunnel Status

from the Query Type list, specify the corresponding value in the Value field, and then clickQuery.MPLS TE tunnels that match these descriptions appear in the MPLS TE Tunnel Query List sectionof the page.

Deleting an MPLS TE tunnelTo delete an MPLS TE tunnel:1. Query for the MPLS TE tunnel that you want to delete.2. In the MPLS TE Tunnel Query List section of the page, mark the check box on the same line as

the MPLS TE tunnel that you want to delete, and then click the Delete button.3. Click OK.

Modifying an MPLS TE tunnelTo modify an MPLS TE tunnel:1. Query for the MPLS TE tunnel that you want to modify.

2. In the MPLS TE Tunnel Query List section of the page, click the Modify icon on the sameline as the tunnel that you want to modify.

Viewing the network topology of an MPLS TE tunnelTo view the network topology of an MPLS TE tunnel:1. Query for the MPLS TE tunnel of which you want to view the network topology.

2. In the MPLS TE Tunnel Query List section of the page, click the Topology icon on the sameline as the tunnel for which you want to view the network topology.

Viewing detailed information about the ingress device of an MPLS TE tunnelTo view detailed information about the ingress device of an MPLS TE tunnel:1. Query for the MPLS TE tunnel that uses the ingress device you are interested in.2. In the MPLS TE Tunnel Query List section of the page, click the name of the ingress device

under the Device Name column.

Viewing detailed information about the MPLS TE tunnelTo view detailed information about the MPLS TE tunnel:


1. Query for the MPLS TE tunnel that uses the ingress device you are interested in.2. In the MPLS TE Tunnel Query List section of the page, click the name of the MPLS TE tunnel

under the MPLS TE Tunnel Name column.

Configuring traffic accessAfter you have created a TE tunnel and have it operational, you should make sure that traffic isintroduced to the tunnel so that data can be forwarded along the tunnel. You can enable the TEtunnel to forward traffic in three ways: Static Routing, IGP Shortcut, and Forwarding Adjacency.

Configuring traffic access procedureTo configure traffic access:1. Click Service > MPLS TE Manager > Traffic Access Mng from the tabular navigation system on

the top of the IMC main page.2. In the Access Traffic List section of the page, click Add.

The Traffic Access Type Selection page appears, as shown in Figure 73.

Figure 73 Traffic Access Type Selection page

3. Click Select next to Device Name, enter part or the entire name of the ingress device and clickthe Query button. Devices matching this description appear in the Device Query List sectionof the page. Select the ingress device, and then click OK.

4. Click Select next to Tunnel Name, enter part or the entire name of the tunnel that you wanttraffic to be introduced to in the Tunnel Name field, and then click Query. Tunnels matchingthis description appear in the Tunnel Info List section of the page. Select the tunnel you want,and then click OK.

5. Select Static Routing, IGP Shortcut, or Forwarding Adjacency from the Traffic Access Type list,depending on how your network was set up.Static Routing—Static Routing is not really a routing protocol. Static Routing is the process ofmanually entering routes into a routing table of a device via a configuration file that is loadedwhen the routing device starts up. As an alternative, these routes can be entered by a networkadministrator who configures the routes manually. Since these manually configured routes donot change after they are configured, they are called static routes. Static Routing is the simplestform of routing, but it is a manual process.A static routed environment is best suited to a small, single-path, static network. A small networkis defined as 2 to 10 networks. Single-path means that there is only a single path for packetsto travel between any two endpoints on the network. Static means that the topology of thenetwork does not change over time. You only need to manually create a route that reachesthe destination through the tunnel interface.


Static Routing has disadvantages. If a router or link goes down, static routers do not sensethe fault or inform other routers of the fault. Therefore it is suitable for small networks whererouters or networks do not go down often enough to justify deploying a multipath topologyand a routing protocol. Besides, Static Routing does not handle failures or changes in networkswell. For example, if a new network is added or removed from the network, routes to the newnetwork must be manually added or removed. If a new router is added, it must be properlyconfigured for the routes of the network.IGP Shortcut—Interior Gateway Protocol (IGP) shortcut is an extra step in the intra-area (orintra-level) best route selection process in OSPF or IS-IS. Without the autoroute-enabled MPLSTE tunnels, the Shortest Path First (SPF) algorithm builds the shortest path tree to compute theminimum cost to all other routers in the area, and then selects the best routes based on theminimum cost. The IGP Shortcut feature modifies the shortest path tree on the tunnel head-endLSR before the best routes are selected by inserting the MPLS TE tunnel in the SPF tree. TheIGP Shortcut feature ensures that the tunnel is used to transport all the traffic from the head-endLSR to all destinations behind the tailed LSR. The path toward the tunnel tail-end LSR is replacedby a direct link (MPLS TE tunnel) in the SPF tree.The modification of the SPF tree is local to the head-end router and does not affect the topologydatabase or the SPF trees built by other routers. Therefore, the MPLS TE tunnel created by IGPShortcut is not seen by other routers, which means that other routes cannot use this tunnel tocompute the shortest path for routing traffic throughout the network.Forwarding Adjacency—The Forwarding Adjacency feature allows a network administratorto handle a TE, label-switched path (LSP) tunnel as a link in an IGP network based on the SPFalgorithm. A Forwarding Adjacency can be created between routers regardless of their locationin the network. The routers can be located multiple hops from each other.OSPF includes MPLS TE tunnels in the OSPF link-state database in the same way that otherlinks appear for purposes of routing and forwarding traffic. When an MPLS TE tunnel isconfigured between networking devices, that link is considered a Forwarding Adjacency. Youcan assign a cost to the tunnel to indicate the preference of the link.The benefit of the Forwarding Adjacency feature is that TE tunnel interfaces are advertized inthe IGP network just like any other links. Routers can then use these advertisements in theirIGPs to compute the SPF even if they are not the head-end of any TE tunnels. This means thatrouters outside of the TE domain can see the TE tunnel and use it to compute the shortest pathfor routing traffic throughout the network. However, using the MPLS TE Forwarding Adjacencyfeature increases the size of the IGP database by advertising a TE tunnel as a link. Moreover,MPLS TE Forwarding Adjacency tunnels must be configured bidirectionally.IGP shortcut and Forwarding Adjacency—IGP Shortcut and Forwarding Adjacency are different.In the Forwarding Adjacency approach, routes with TE tunnel interfaces as outgoing interfacesare advertised to neighboring routers but not in the IGP Shortcut approach. Therefore, TEtunnels are visible to other routers in the Forwarding Adjacency approach but not in the IGPShortcut approach.


Figure 74 IGP Shortcut and Forwarding Adjacency

As shown in Figure 74, a TE tunnel is present between Router D and Router C. With IGPShortcut enabled, the ingress node Router D can use this tunnel when calculating IGP routes.This tunnel, however, is invisible to Router A; therefore, Router A cannot use this tunnel toreach Router C. With Forwarding Adjacency enabled, Router A can know the presence ofthe TE tunnel and thus forward traffic to Router C to Router D through this tunnel.

6. If you select Static Routing for Traffic Access Type, you are directed to the Static Routing AccessConfiguration page, as shown in Figure 75.

Figure 75 Static Routing Access Configuration page

a. In the Next Hop IP (A.B.C.D) field, enter the IP address of the next hop.b. In the Route Tag (1-4294967295) field, enter the value of the route tag.

Route Tag—Both OSPF and IS-IS allow the association of a 32-bit value called a routetag with external prefixes. You can consider route tags as a protocol extensibility featurebecause they enable you to arbitrarily assign some administratively meaningful value toexternal prefixes to associate them with some group that you define. You can then createrouting policies that act on the external prefixes according to their assigned tags.The most common application of route tags is in complex route redistribution policies.Route tags are used when it is impractical to identify prefixes using prefix lists or routefilters, either because there are so many prefixes to be identified that the list would beunmanageably long, or because you are uncertain what prefixes need to be identified.


You can tag prefixes at their point of origin by incoming interface, advertising neighbor,or redistribution point, for example, and then apply polices to the prefixes elsewhere inyour network by identifying the tag, rather than individual prefixes.Another application for route tags is for leaking prefixes from one IS-IS level to another,in which you want to leak some prefixes but not others. Polices can be used to tag prefixesat their origin, identifying them with administratively defined groups. Other polices canthen be implemented at level boundaries that identify the prefix groups, by tags, that areto be leaked and the prefix groups that are to be suppressed.

c. In the Route Priority field, assign a value to the route priority. A lower numerical numberindicates a higher priority.

d. Select Tunnel Destination or Custom IP Address in the Destination IP Address list. You canuse the destination address of the tunnel or customize the address by yourself. The defaultvalue of destination IP address is 60.

7. Click Complete. The traffic access is added successfully and appears in the Access Traffic Listsection of the page.


8. If you select IGP Shortcut or Forwarding Adjacency for Traffic Access Type, you are directedto the IGP Shortcut Configuration page, as shown in Figure 76.

Figure 76 IGP Shortcut Configuration page

a. Select OSFP, ISIS or OSPF and ISIS from the IGP Type list.MPLS TE must be aware of dynamic TE attributes of each link on the network. This isachieved by extending link state-based IGPs such as OSPF and IS-IS.OSPF or IS-IS with extensions for TE is used to carry information pertaining to the linkstates. The extensions add to link states such TE attributes as link bandwidth, color,maximum reservable link bandwidth and non-reserved bandwidth with a particular priority.As a result, a link that does not have the requested resources (like bandwidth) is notchosen to be a part of the LSP tunnel or TE tunnel.

b. Assign a metric value, either absolute or relative, to TE tunnels for the purpose of pathcalculation. If it is absolute (or fixed), the metric is directly used for path calculation. If itis relative (or floating), the cost of the corresponding IGP path must be added to the metricbefore it can be used for path calculation.An absolute metric indicates that there is no relationship to the underlying IGP cost. Arelative metric is added to or subtracted from the underlying IGP shortest path cost. If youuse a relative metric, the actual assigned metric value of routes is based on the IGP metric.This relative metric can be positive or negative, and is bounded by minimum and maximumallowed metric values.For example, if you specify a relative metric of -2 for an MPLS TE tunnel, OSPF treats thistunnel as having a metric of 2 less than the shortest path metric it has calculated. Thetunnel is therefore preferred over other paths to prefixes beyond the tunnel endpoint. Ifyou specify an absolute metric of 25, and configure OSPF to enable the considerationof SPF best paths, OSPF considers this metric in its SPF calculations for traffic to the tunnelendpoint as well as beyond the endpoint. Traffic is routed via this tunnel only if the othercalculated paths have higher metrics.

c. Click Complete. The traffic access is added successfully and appears in the Access TrafficList section of the page.

Managing traffic accessYou can query, add and delete traffic access configuration. Through the traffic access configuration,you can distribute traffic to a specified tunnel.To query for traffic access:1. Click Service > MPLS TE Manager > Traffic Access Mng from the tabular navigation system on

the top of the IMC main page.2. In the Traffic Access Query section of the page, select the query type and enter the query

value.3. Click Query.To delete traffic access configuration:


1. Click Service > MPLS TE Manager > Traffic Access Mng from the tabular navigation system onthe top of the IMC main page.

2. In the Access Traffic List section of the page, select the traffic access record you want to delete,and then click Delete.

3. Click OK.

Protection managementYou can use the protection management function to avoid an invalid link or node, in order to avoiddata loss and service interruption. You can perform protection configuration to protect a link ornode, so that when the link or node fails, its traffic can travel through the backup link or nodeinstead. The supported protection types are CR-LSP backup protection and FRR.

CR-LSP backup protectionCR-LSP backup provides end-to-end path protection for the entire LSP without time limitation. Thisis different from Fast Reroute (FRR) which provides quick but temporary per-link or per-node protectionon an LSP.In the same TE tunnel, the LSP used to back up a primary LSP is called a secondary LSP. When theingress of a TE tunnel detects that the primary LSP is unavailable, it switches traffic to the secondaryLSP and after the primary LSP becomes available, switches traffic back. This is how LSP pathprotection is achieved.

Configuring CR-LSP backup protection

Configuration prerequisitesBefore you configure CR-LSP backup, complete the following tasks:• Configure MPLS basic capabilities.

• Configure MPLS TE basic capabilities.

• Configure MPLS TE tunnels.You need to make sure that MPLS and MPLS TE basic capabilities are enabled on your devicesbefore you can manage your TE networks using MPLS TE Management. The configurationinstructions for enabling MPLS and MPLS TE basic capabilities may differ from device to device.For detailed configuration instructions, see the configuration guide of your device.

NOTE: CR-LSP backup should be configured at the ingress node of a tunnel. The system routesthe primary LSP and backup LSP automatically. You do not need to configure them.

Querying for a tunnel for CR-LSP backupTo query for a tunnel for CR-LSP backup:1. Click Service > MPLS TE Manager > Protection Mng from the tabular navigation system on the

top of the IMC main page.2. In the Tunnel Query section of the page, select MPLS TE Tunnel name, Tunnel State, or Protocol

from the Query Type list, specify the corresponding value in the Value field, and then clickQuery. Tunnels matching this description appear in the Protected Tunnel List section of thepage, as shown in Figure 77.


Figure 77 Protected Tunnel List section

3. Find the tunnel that you want to configure CR-LSP backup for, click Hot Backup in the CR-LSPBackup Operation column to change the CR-LSP backup type if needed, and then click the

CR-LSP Backup Operation icon .Two approaches are available for CR-LSP backup:• Hot backup—Where a secondary CR-LSP is created immediately after a primary CR-LSP

is created. MPLS TE switches traffic to the second CR-LSP after the primary CR-LSP fails.• Second backup—Where a secondary CR-LSP is created to take over after the primary

CR-LSP fails.

FRRFast Reroute (FRR) provides a quick per-link or per-node protection on an LSP.In this approach, once a link or node fails on a path, FRR comes up to reroute the path to a newlink or node to bypass the failed link or node. This can happen as fast as 50 milliseconds thusminimizing data loss.

Basic conceptsThe following are FRR concepts:• Primary LSP—The protected LSP.

• Bypass LSP—An LSP used to protect the primary LSP.

• Point of local repair (PLR)—The ingress of the bypass LSP. It must be located on the primaryLSP but must not be the egress.

• Merge point (MP)—The egress of the bypass LSP. It must be located on the primary LSP butmust not be the ingress.

FRR link protection and node protectionFRR provides link protection and node protection for an LSP as follows:• Link protection, where the PLR and the MP are connected through a direct link and the primary

LSP traverses this link. When the link fails, traffic is switched to the bypass LSP. As shown inFigure 78, the primary LSP is Router A —> Router B —> Router C —> Router D, and thebypass LSP is Router B —> Router F —> Router C.


Figure 78 FRR link protection

• Node protection, where the PLR and the MP are connected through a router and the primaryLSP traverses this router. When the router fails, traffic is switched to the bypass LSP. As shownin Figure 79, the primary LSP is Router A —> Router B —> Router C —> Router D —> RouterE, and the bypass LSP is Router B —> Router F —> Router D. Router C is the protected router.

Figure 79 FRR node protection

Deploying FRRWhen configuring the bypass LSP, make sure that the protected link or node is not on the bypassLSP.Because bypass LSPs are pre-established, FRR requires extra bandwidth. When network bandwidthis insufficient, use FRR for crucial interfaces or links only.

Configuring FRRFast Reroute (FRR) provides quick but temporary per-link or per-node local protection on an LSP.FRR uses bypass tunnels to protect primary tunnels. As bypass tunnels are pre-established, theyrequire extra bandwidth and are usually used to protect crucial interfaces or links only.You can define which type of LSP can use bypass LSPs, and whether a bypass LSP providesbandwidth protection as well as the sum of protected bandwidth.The bandwidth of a bypass LSP is to protect its primary LSPs. To guarantee that a primary LSP canalways bind with the bypass LSP successfully, make sure that the bandwidth assigned to the bypassLSP is not less than the total bandwidth needed by all protected LSPs.


Normally, bypass tunnels only forward data traffic when protected primary tunnels fail. To allowa bypass tunnel to forward data traffic while protecting the primary tunnel, you need to make surethat bypass tunnels are available with adequate bandwidth.A bypass tunnel cannot be used for services like VPN at the same time.

Configuration prerequisitesBefore you configure FRR, complete the following tasks:• Configure IGP, ensuring that all LSRs are reachable.


• Configure MPLS TE basic capabilities.

• Establish an MPLS TE tunnel with RSVP-TE.

• Set up primary LSPs.You need to make sure that MPLS and MPLS TE basic capabilities are enabled on your devicesbefore you can manage your TE networks using MPLS TE Management. The configuration instructionsfor enabling MPLS and MPLS TE basic capabilities may differ from device to device. For detailedconfiguration instructions, see the configuration guide of your device.To configure link protection:1. Click Service > MPLS TE Manager > Protection Mng from the tabular navigation system on the

top of the IMC main page.2. In the Protected Tunnel List section of the page, select a tunnel that you want to use as the

bypass tunnel, and then click FRR Protection.3. Select Link Protection from the Protection Type list.4. Click Next.5. In the Link List section of the page, select the primary tunnel that you want to protect.6. Click Next.7. In the Protected Tunnel List section of the page, select the bypass tunnel, and then click Bound

> Complete. The bypass tunnel is bound with the primary tunnel and disappears from theProtected Tunnel List section.

8. To view detailed information about the protection, click the Operation icon .To configure node protection:1. Click Service > MPLS TE Manager > Protection Mng from the tabular navigation system on the

top of the IMC main page.2. In the Protected Tunnel List section of the page, select a tunnel that you want to use as the

bypass tunnel, and then click FRR Protection.3. Select Node Protection from the Protection Type list.4. Click Next.5. In the Node List section of the page, select the primary tunnel that you want to protect.6. Click Next.7. In the Protected Tunnel List section of the page, select the bypass tunnel, and then click Bound


8. To view detailed information about the protection, click the Operation icon .


Typical applications

Usage scenario 1A corporation has three subsidiaries, which are located in site A, site B, and site C, respectivelyand are connected with one another through networks. As services expand, network congestionsoccur frequently due to network load imbalance. Router A, Router B, and Router C represent thethree subsidiaries, respectively.Assume that the routers are reachable to each other after being configured with IS-IS or OSPF andare properly configured with basic MPLS and MPLS TE capabilities, as shown in Figure 80.

Figure 80 Usage scenario 1

In this scenario, the main factor that causes network congestions is the network load imbalance.To ensure that important services can be smoothly transmitted along Router A —> Router B —>Router C, you should import Router A, Router B and Router C into MPLS TE Management, configurean MPLS TE tunnel using static CR-LSP, and then introduce traffic to it. Router A works as the ingressdevice, Router B works as the transit device and Router C works as the egress device.

• Router A—Device name is H3C-1; Device IP is 172.10.0.70; LSR ID address is 3.3.3.70;address of Vlan-interface34 is 2.2.4.167.

• Router B—Device name is H3C; Device IP is 172.10.0.82; LSR ID address is 3.3.3.82; addressof GigabitEthernet4/0/4 is 2.2.4.4; address of GigabitEthernet4/0/2 is 11.11.13.165.

• Router C—Device name is H3C-3; Device IP is 172.10.0.88; LSR ID is 3.3.3.88; address ofGigabitEthernet4/0/2 is 11.11.13.166.

Operation procedureImport Router A, Router B and Router C into MPLS TE Management.To configure an MPLS TE tunnel using static CR-LSP:1. Click Service > MPLS TE Manager > MPLS TE Tunnel Mng from the tabular navigation system

on the top of the IMC main page.2. In the MPLS TE Tunnel Query List section, click Add.

The Configure Static CR-LSP page appears, as shown in Figure 81.

Typical applications 211

Figure 81 Usage scenario 1 — Add Tunnel page

3. Specify the configuration information for the static CR-LSP.a. Select Router A as the ingress device for the MPLS TE tunnel. Click Select next to Select

Device. On the Select Device page, specify part or the entire name of Router A, and thenclick Query. Devices that match the description appear in the Device Query List sectionof the page. Select Router A, and then click OK.

b. On the Configure Static CR-LSP page, click Select next to MPLS TE Tunnel Name. Assigna name to the tunnel, and then click OK.

c. Enter the description for the tunnel, if needed.d. Select Static CR-LSP from the Protocol list.e. Assign an IP Address/Mask for the tunnel.f. Enter the loopback address of Router C in the field of Destination IP Address (A.B.C.D),

and then click Next.4. In the Configure Static CR-LSP page, click Add. The Add Static CR-LSP Node screen with Ingress

selected as the role is displayed, as shown in Figure 82.

Figure 82 Usage scenario 1 — Add Static CR-LSP Node screen with Ingress selected as therole

5. Add Router A as an ingress device node.a. Click Select next to Select Device. In the Select Device page, specify part or the entire

name of Router A, and then click Query. Devices that match the description appear inthe Device Query List section of the page. Select Router A, and then click OK.


b. Select Ingress from the Select Role list.c. In the Destination Address (A.B.C.D) field, enter the loopback address of Router C.d. In the Next Hop (A.B.C.D) field, enter the in interface of Router B.e. Next to Out Label, enter the out label value and click Detect to see if this value is available.f. Click OK. The information of Router A appears in the Configure Static CR-LSP section of

the page.6. Add Router B as a transit device node.

a. In the Configure Static CR-LSP section of the page, click Add.The Add Static CR-LSP Node screen with Transit selected as the role appears, as shownin Figure 83.

Figure 83 Usage scenario 1 — Add Static CR-LSP Node screen with Transit selected asthe role

b. Click Select next to Select Device. In the Select Device page, specify part or the entirename of Router B, and then click Query. Devices that match the description appear inthe Device Query List section of the page. Select the transit device, and then click OK.

c. Select Transit from the Select Role list. The In Interface field is populated with interfacesof Router B. Select the interface that you want to connect to Router A.

d. In the In Label field, enter the in label value and click Detect to see if this value is available.e. In the Next Hop (A.B.C.D) field, enter the in interface of Router C.f. In the Out Label field, enter the out label value of Router B. Click Detect to see if this value

is available if needed.g. Click OK. The information of the transit device appears in the Configure Static CR-LSP

section of the page.


7. Add Router C as the egress device node.a. In the Configure Static CR-LSP section of the page, click Add.

The Add Static CR-LSP Node screen with Egress selected as the role appears, as shownin Figure 84.

Figure 84 Add Static CR-LSP Node screen with Egress selected as the role

b. Click Select next to Select Device. In the Select Device page, specify part or the entirename of Router C, and then click Query. Devices that match the description appear inthe Device Query List section of the page. Select Router C, and then click OK.

c. Select Egress from the Select Role list. The In Interface field is populated with the informationof interfaces of Router C. Select the interface that you want to connect with Router B.

d. In the In Label field, enter the in label value and select Detect to see if this value isavailable.

e. Click OK. The information of Router C appears in the Configure Static CR-LSP section ofthe page.

f. Click Finish.

To introduce traffic to the static CR-LSP tunnel:1. Click Service > MPLS TE Manager > Traffic Access Mng from the tabular navigation system on



Figure 85 Usage scenario 1 — Traffic Access Type selection page

3. Click Select next to Device Name, enter part or the entire name of the Router A and click theQuery button. Devices matching this description appear in the Device Query List section ofthe page. Select Router A, and then click OK.

4. Click Select next to Tunnel Name, enter part or the entire name of the tunnel that you havejust created in the Tunnel Name field, and then click Query. Tunnels matching this descriptionappear in the Tunnel Info List section of the page. Select your tunnel, and then click OK.


5. Select Static Routing from the Traffic Access Type list. In this usage scenario, the tunnel is astatic CR-LSP route, so you should select the Static Routing option.

6. You are directed to the Static Routing Access Configuration page, as shown in Figure 86.

Figure 86 Usage scenario 1 — Static Routing Access Configuration page

7. Click Complete. The traffic access is added successfully and appears in the Access Traffic Listsection of the page.

Usage scenario 2A bank has four branches, branch A through branch D, which are connected to one anotherthrough networks. Branch A needs to send important data to branch D. It is required that theremust be enough bandwidth to guarantee the data transmission even if network congestion occurs.Assume that the routers are reachable to each other after being configured with IS-IS or OSPF andare properly configured with basic MPLS and MPLS TE capabilities, as shown in Figure 87:


In this scenario, you need to configure a dynamic MPLS TE tunnel from Router A to Router D througha dynamic signaling protocol RSVP-TE and reserve resources on the devices along the tunnel, sothat data from Router A to Router D is always serviced.

• Router A—Device name is H3C-1; Device IP is 172.10.0.70; LSR ID address is 3.3.3.70;address of Vlan–interface34 is 2.2.4.167.

• Router B—Device name is H3C; Device IP is 172.10.0.82; LSR ID address is 3.3.3.82; addressof GigabitEthernet4/0/4 is 2.2.4.4; address of GigabitEthernet4/0/2 is 11.11.13.165.


• Router C—Device name is H3C-3; Device IP is 172.10.0.88; LSR ID address is 3.3.3.88;address of GigabitEthernet4/0/2 is 11.11.13.166; address of GigabitEthernet4/0/3 is11.11.12.166.

• Router D—Device name is H3C-2; Device IP is 172.10.0.91; LSR ID address is 3.3.3.91;address of Vlan–interface3 is 1.1.1.164.

Operation procedureImport Router A, Router B, Router C, and Router D into MPLS TE Management.To create a tunnel using the dynamic signaling protocol RSVP-TE:1. Click Service > MPLS TE Manager > MPLS TE Tunnel Mng from the tabular navigation system





3. Specify the configuration information for the dynamic MPLS TE tunnel.a. Click Select next to Select Device, enter part or the entire name of Router A, and then click

Query. All devices that match the description appear in the Device Query List section ofthe page. Select Router A, and then click OK.

b. Click Select next to MPLS TE Tunnel Name, assign a name to the tunnel, and then clickOK.

c. Select RSVP-TE from the Protocol list.d. Assign the IP address/mask to the tunnel, if needed.e. In the Destination IP Address (A.B.C.D) field, enter the loopback address of Router D, and

then click Next. You are directed to the Configure Basic Attributes page, as shown inFigure 89. You can use default settings on this page.

Figure 89 Usage scenario 2 — Configure Basic Attributes page

f. Click Next. You are directed to the Configure Path Policy page, as shown in Figure 90.You can use default settings on this page.

Figure 90 Usage scenario 2 — Configure Path Policy page

g. Click Next. You are directed to the Configure Advanced Attributes page.h. Click OK. This tunnel appears in the MPLS TE Tunnel Query List section of the page.

To introduce traffic to this tunnel:1. Click Service > MPLS TE Manager > Traffic Access Mng from the tabular navigation system on



2. In the Access Traffic List section of the page, click Add. The Traffic Access Type Selection pageis displayed, as shown in Figure 91.

Figure 91 Usage scenario 2 — Traffic Access Type Selection page

3. Click Select next to Device Name, enter part or the entire name of Router A and click the Querybutton. Devices matching this description appear in the Device Query List section of the page.Select Router A, and then click OK.


5. Click Next.6. Click Complete. The traffic access is added successfully and appears in the Access Traffic List


Usage scenario 3A company has four offices, office A through office D, which are connected with one anotherthrough networks. It is required to backup the forwarding of service data from office A to officeC.Assume that the routers are reachable to each other after being configured with IS-IS or OSPF andare properly configured with basic MPLS and MPLS TE capabilities, CR-LSP backup is configuredat Router A, as shown in Figure 92:



In this scenario, you can create two tunnels through a dynamic signaling protocol: tunnel A (RouterA —> Router B —> Router C) and tunnel B Router A —> Router D —> Router C. Thus you canconfigure tunnel B as the CR-LSP backup tunnel of tunnel A. Then you should then introduce trafficto tunnel A.

NOTE: You cannot configure CR-LSP backup for MPLS TE tunnels configured using the staticCR-LSP protocol.

• Router A—Device name is H3C-1; Device IP is 172.10.0.70; LSR ID address is 3.3.3.70;address of Vlan 34 (Vlan-interface34) is 2.2.4.167; address of Vlan 3 (Vlan-interface3) is2.2.4.299.

• Router B—Device name is H3C; Device IP is 172.10.0.82; LSR ID address is 3.3.3.82; addressof g4/0/4 (GigabitEthernet4/0/4) is 2.2.4.4; address of g4/0/2 (GigabitEthernet4/0/2)is 11.11.13.165.

• Router C—Device name is H3C-3; Device IP is 172.10.0.88; LSR ID address is 3.3.3.88;address of g4/0/2 (GigabitEthernet4/0/2) is 11.11.13.166.

• Router D—Device name is H3C-2; Device IP is 172.10.0.91; LSR ID address is 3.3.3.91;address of Vlan 3 (Vlan-interface3) is 1.1.1.164; address of Vlan 123 (Vlan-interface123) is11.11.12.164.

Operation procedureImport Router A, Router B, Router C and Router D into MPLS TE Management.To configure an explicit path for the primary tunnel:1. Click Service > MPLS TE Manager > Explicit Path Mng from the tabular navigation system on



Figure 93 Usage scenario 3 — Add Explicit Path page

3. Click Select next to Device Name, specify part or the entire name of Router A, and then clickQuery. Devices that match the description appear in the Device Query List section of the page.Select Router A and click OK.




Figure 94 Usage scenario 3 — Next Hop Info page

8. In the Next Hop Address field, enter the in interface address of your next hop (Router B).9. Select Include from the Next Hop Include Policy list.10. Select Strict from the Next Hop Strict Loose Policy list.11. Click OK. Information about your next hop displays in the Next Hop Info List section of the

page.12. In the Next Hop Info List section of the page, click Add.



13. In the Next Hop Address field, enter the in interface address of your next hop (Router C).14. Select Include from the Next Hop Include Policy list.15. Select Strict from the Next Hop Strict Loose Policy list.16. Click OK. Information about your next hop displays in the Next Hop Info List section of the

page.17. Click Finish. The explicit path is created and displayed in the Explicit Path List section of the

Explicit Path Management page.To create a tunnel from Router A to Router C using the dynamic signaling protocol RSVP-TE:1. Click Service > MPLS TE Manager > MPLS TE Tunnel Mng from the tabular navigation system






3. Specify the configuration information for the dynamic MPLS TE tunnel.a. Click Select next to Select Device, enter part or the entire name of Router A and click




then click Next. You are directed to the Configure Basic Attributes page, as shown inFigure 97.


f. Enter information in the Bandwidth (Kbps) field and the Backup Bandwidth (Kbps) field.You need to configure the same settings accordingly on your devices.

g. Click Next. You are directed to the Configure Path Policy page, as shown in Figure 98.


h. Refer to the explicit path that you have configured, and then click Next. You are directedto the Configure Advanced Attributes page.

i. Click OK. This tunnel appears in the MPLS TE Tunnel Query List section of the page.

Configure tunnel B in the similar way from Router A —> Router D —> Router C.


To introduce traffic to this tunnel:1. Click Service > MPLS TE Manager > Traffic Access Mng from the tabular navigation system on







section of the page.To configure CR-LSP backup:1. Click Service > MPLS TE Manager > Protection Mng from the tabular navigation system on the

top of the IMC main page.2. In the Tunnel Query section of the page, select MPLS TE Tunnel name, Tunnel State, or Protocol

from the Query Type list, specify the corresponding value in the Value field, and then clickQuery. Tunnels matching this description appear in the Protected Tunnel List section of thepage.

3. Find the tunnel that you want to configure CR-LSP backup for, and then click the CR-LSP Backup

Operation icon .

Usage scenario 4A company has four offices, office A through office D, which are connected with one anotherthrough networks. It is required to protect the link between office B and office C, so that datapackets can be switched to another path quickly when the link fails, and switched back to theoriginal link after the original link resumes.Assume that the routers are reachable to each other after being configured with IS-IS or OSPF andare properly configured with basic MPLS and MPLS TE capabilities, as shown in Figure 100:



In this scenario, you should create the primary tunnel through a dynamic signaling protocol. Thetunnel path is Router A —> Router B —> Router C. In this tunnel, the link between Router B andRouter C is to transmit important service data, therefore required to be protected. You should alsocreate the bypass tunnel through a dynamic signaling protocol. The bypass tunnel path is RouterB —> Router D —> Router C. Once the link between Router B and Router C fails, the primarytunnel’s path will change to Router A —> Router B —> Router D —> Router C.

• Router A—Device name is H3C-1; Device IP is 172.10.0.70; LSR ID address is 3.3.3.70;address of Vlan 34 (Vlan-interface 34) is 2.2.4.167.

• Router B—Device name is H3C; Device IP is 172.10.0.82; LSR ID address is 3.3.3.82; addressof g4/0/4 (GigabitEthernet4/0/4) is 2.2.4.4; address of g4/0/2 (GigabitEthernet4/0/2)is 11.11.13.165; address of g4/0/3 (GigabitEthernet4/0/3) is 1.1.1.165.

• Router C—Device name is H3C-3; Device IP is 172.10.0.88; LSR ID address is 3.3.3.88;address of g4/0/2 (GigabitEthernet4/0/2) is 11.11.13.166; address of g4/0/3(GigabitEthernet4/0/3) is 11.11.12.166.

• Router D—Device name is H3C-2; Device IP is 172.10.0.91; LSR ID address is 3.3.3.91;address of Vlan 3 (Vlan-interface 3) is 1.1.1.164; address of Vlan 123 (Vlan-interface 123)is 11.11.12.164.

Operation procedureImport Router A, Router B, Router C, Router D into MPLS TE Management.To configure an explicit path for the primary tunnel:1. Click Service > MPLS TE Manager > Explicit Path Mng from the tabular navigation system on









8. In the Next Hop Address field, enter the in interface address of your next hop (Router B).9. Select Include from the Next Hop Include Policy list.10. Select Strict from the Next Hop Strict Loose Policy list.11. Click OK. Information about your next hop displays in the Next Hop Info List section of the






page.17. Click Finish. The explicit path is created and displayed in the Explicit Path List section of the

Explicit Path Management page.To create the primary tunnel using dynamic signaling protocol:1. Click Service > MPLS TE Manager > MPLS TE Tunnel Mng from the tabular navigation system








c. Select RSVP-TE from the Protocol list.d. Assign the IP address/mask to the tunnel, if needed.e. In the Destination IP Address (A.B.C.D) field, enter the loopback address of Router C, and



f. Click Next. You are directed to the Configure Path Policy page, as shown in Figure 106.


g. Click Select next to Explicit Path, select the explicit path that you have just created, thenclick OK.

h. Click Next. You are directed to the Configure Advanced Attributes page.i. Click OK. This tunnel appears in the MPLS TE Tunnel Query List section of the page.

To configure an explicit path for the bypass tunnel:


1. Click Service > MPLS TE Manager > Explicit Path Mng from the tabular navigation system onthe top of the IMC main page.

2. In the Explicit Path List section of the page, click Add.The Add Explicit Path page appears, as shown in Figure 107.


3. Click Select next to Device Name, specify part or the entire name of Router B, and then clickQuery. Devices that match the description appear in the Device Query List section of the page.Select Router B and click OK.




8. In the Next Hop Address field, enter the in interface address of your next hop (Router D).9. Select Include from the Next Hop Include Policy list.10. Select Strict from the Next Hop Strict Loose Policy list.11. Click OK. Information about your next hop displays in the Next Hop Info List section of the






page.17. Click Finish. The explicit path is created and displays in the Explicit Path List section of the

Explicit Path Management page.To create the backup tunnel using dynamic signaling protocol:1. Click Service > MPLS TE Manager > MPLS TE Tunnel Mng from the tabular navigation system





3. Specify the configuration information for the dynamic MPLS TE tunnel.a. Click Select next to Select Device, enter part or the entire name of Router B and click

Query. All devices that match the description appear in the Device Query List section ofthe page. Select Router B, and then click OK.







g. Click Select next to Explicit Path, select the explicit path that you have just created for thebackup tunnel, then click OK.

h. Click Next. You are directed to the Configure Advanced Attributes page.i. Click OK. The backup tunnel appears in the MPLS TE Tunnel Query List section of the

page.

To configure FRR:


1. Click Service > MPLS TE Manager > Protection Mng from the tabular navigation system on thetop of the IMC main page.

2. In the Protected Tunnel List section of the page, select the bypass tunnel, and then click FRRProtection.

3. Select Link Protection from the Protection Type list.4. Click Next.5. In the Link List section of the page, select the link that you want to protect.6. Click Next.7. In the Protected Tunnel List section of the page, select the bypass tunnel, and then click Bound


8. You can click the Operation icon to view detailed information about the protection.To introduce traffic to the primary tunnel:1. Click Service > MPLS TE Manager > Traffic Access Mng from the tabular navigation system on





4. Click Select next to Tunnel Name, enter part or the entire name of the primary tunnel that youhave just created in the Tunnel Name field, and then click Query. Tunnels matching thisdescription appear in the Tunnel Info List section of the page. Select the primary tunnel, andthen click OK.



Usage scenario 5A company has five offices, office A through office E, which are connected with one anotherthrough networks. It is required to protect the link between office B and office D. Once the linkfails (for example, the device in office C fails), data packets can be forwarded quickly throughanother path, and, after the link resumes, data packets can be forwarded through the link again.Assume that the routers are reachable to each other after being configured with IS-IS or OSPF andare properly configured with basic MPLS and MPLS TE capabilities, as shown in Figure 114:



In this scenario, you should create the primary tunnel through a dynamic signaling protocol. Theprimary tunnel path is Router A —> Router B —> Router C —> Router D. In this tunnel, the linkbetween Router B and Router D needs to transmit important service data. Therefore it is requiredto protect the link's node Router C. You should also create the bypass tunnel using a dynamicsignaling protocol. The bypass tunnel path is Router B —> Router E —> Router D. Once the linkbetween Router B and Router D fails (for example, Router C cannot be pinged on the network),the path will change to Router A —> Router B —> Router E —> Router D.




• Router D—Device name is H3C-2; Device IP is 172.10.0.91; LSR ID address is 3.3.3.91;address of Vlan 3 (Vlan-interface 3) is 1.1.1.164; address of Vlan 123 (Vlan-interface 123)is 11.11.12.164.

• Router E—Device name is H3C-4; Device IP is 172.10.0.92; LSR ID address is 3.3.3.92;address of Vlan 123 (Vlan-interface 123) is 11.11.12.133; address of g4/0/2(GigabitEthernet4/0/2) is 11.11.13.177.

Operation procedureImport Router A, Router B, Router C, Router D and Router E into MPLS TE Management.To configure an explicit path for the primary tunnel:1. Click Service > MPLS TE Manager > Explicit Path Mng from the tabular navigation system on









8. In the Next Hop Address field, enter the in interface address of Router B.9. Select Include from the Next Hop Include Policy list.10. Select Strict from the Next Hop Strict Loose Policy list.11. Click OK. Information about your next hop displays in the Next Hop Info List section of the


The Next Hop Info appears, as shown in Figure 117.



13. In the Next Hop Address field, enter the in interface address of Router C.14. Select Include from the Next Hop Include Policy list.15. Select Strict from the Next Hop Strict Loose Policy list.16. Click OK. Information about your next hop displays in the Next Hop Info List section of the




18. In the Next Hop Address field, enter the in interface address of Router D.19. Select Include from the Next Hop Include Policy list.20. Select Strict from the Next Hop Strict Loose Policy list.21. Click OK. Information about your next hop displays in the Next Hop Info List section of the


Explicit Path Management page.To create the primary tunnel using dynamic signaling protocol:1. Click Service > MPLS TE Manager > MPLS TE Tunnel Mng from the tabular navigation system
















To configure an explicit path for the bypass tunnel:1. Click Service > MPLS TE Manager > Explicit Path Mng from the tabular navigation system on



2. In the Explicit Path List section of the page, click Add.The Add Explicit Path page appears, as shown in Figure 122.






8. In the Next Hop Address field, enter the in interface address of Router E.9. Select Include from the Next Hop Include Policy list.10. Select Strict from the Next Hop Strict Loose Policy list.11. Click OK. Information about your next hop displays in the Next Hop Info List section of the







Explicit Path Management page.To create the backup tunnel using dynamic signaling protocol:1. Click Service > MPLS TE Manager > MPLS TE Tunnel Mng from the tabular navigation system





3. Specify the configuration information for the dynamic MPLS TE tunnel.a. Click Select next to Select Device, enter part or the entire name of Router B and click

Query. All devices that match the description appear in the Device Query List section ofthe page. Select Router B, and then click OK.







g. Click Select next to Explicit Path, select the explicit path that you have just created for thebackup tunnel, then click OK.

h. Click Next. You are directed to the Configure Advanced Attributes page.i. Click OK. The backup tunnel appears in the MPLS TE Tunnel Query List section of the

page.

To configure FRR:1. Click Service > MPLS TE Manager > Protection Mng from the tabular navigation system on the

top of the IMC main page.


2. In the Protected Tunnel List section of the page, select the bypass tunnel, and then click FRRProtection.

3. Select Node Protection from the Protection Type list.4. Click Next.5. In the Node List section of the page, select the link that you want to protect.6. Click Next.7. In the Protected Tunnel List section of the page, select the bypass tunnel, and then click Bound


8. You can click the Operation icon to view detailed information about the protection.To introduce traffic to the primary tunnel:1. Click Service > MPLS TE Manager > Traffic Access Mng from the tabular navigation system on





4. Click Select next to Tunnel Name, enter part or the entire name of the primary tunnel that youhave just created in the Tunnel Name field, and then click Query. Tunnels matching thisdescription appear in the Tunnel Info List section of the page. Select the primary tunnel, andthen click OK.



Usage scenario 6A company has four offices, office A through office D, which are connected with one anotherthrough networks. It is required that data from office A to office C must pass through the device(Router D) in office D. Assume that the routers are reachable to each other after being configuredwith IS-IS or OSPF and are properly configured with basic MPLS and MPLS TE capabilities, asshown in Figure 129.



In this scenario, you want to force the tunnel to go through the specified node Router D. In orderfor the tunnel to pass through Router D, you need to configure an explicit path that goes throughRouter D. In this way, the tunnel path is Router A —> Router B —> Router D —> Router C.




• Router D—Device name is H3C-2; Device IP is 172.10.0.91; LSR ID address is 3.3.3.91;address of Vlan 3 (Vlan-interface 3) is 11.11.12.164; address of Vlan 123 (Vlan-interface123) is 1.1.1.164.

Operation procedureImport Router A, Router B, Router C, Router D into MPLS TE Management.To create an explicit path that forces the tunnel to pass through router D:1. Click Service > MPLS TE Manager > Explicit Path Mng from the tabular navigation system on









8. In the Next Hop Address field, enter the in interface address of Router B.9. Select Include from the Next Hop Include Policy list.10. Select Strict from the Next Hop Strict Loose Policy list.11. Click OK. Information about your next hop displays in the Next Hop Info List section of the









18. In the Next Hop Address field, enter the in interface address of Router C.19. Select Include from the Next Hop Include Policy list.20. Select Strict from the Next Hop Strict Loose Policy list.21. Click OK. Information about your next hop displays in the Next Hop Info List section of the


Explicit Path Management page.To create a tunnel using dynamic signaling protocol:1. Click Service > MPLS TE Manager > MPLS TE Tunnel Mng from the tabular navigation system















To Introduce traffic to the tunnel:1. Click Service > MPLS TE Manager > Traffic Access Mng from the tabular navigation system on



2. In the Access Traffic List section of the page, click Add.The Traffic Access Type Selection page appears, as shown in Figure 137.



4. Click Select next to Tunnel Name, enter part or the entire name of the tunnel that you havejust created in the Tunnel Name field, and then click Query. Tunnels matching this descriptionappear in the Tunnel Info List section of the page. Select the tunnel that you have just created,and then click OK.




7 Frequently Asked QuestionsMPLS VPN Management

Why does the batch process not deal with all selected objects?Due to server performance capability it times out during the batch process. Therefore it does notdeal with the rest after the timeout. If this case happens, contact HP to adjust system parameters.

Why does the system prompt Telnet failure when I import a device?• Check whether MPLS VPN Management can communicate with the device normally.

• Check whether Telnet parameters on the platform are consistent with those configured on thedevice. You can query or modify the parameters through detailed information of the deviceson the platform.

Why does the system prompt PE synchronization failure in global topologyor access topology?• Check whether MPLS VPN Management can communicate with the device normally.

• Check whether Telnet parameters on the platform are consistent with those configured on thedevice. You can query or modify the parameters through detailed information of the deviceson the platform.

• Check whether MPLS VPN Management supports the device version. For details, refer to theversion description.

In MCE networking scheme, why can't PE-MCE links be discovered duringauto discovery process?• Check whether MCE device is correctly configured, for example, whether an interface of PE

is associated with VRF.• Check whether the MCE is imported correctly.

• Check whether more than two interfaces of MCE are associated with a same VRF, and the IPaddress of one interface is in the same subnet with one of PE.

Why can't VPNs existing on the network be discovered during auto discoveryprocess?• The auto discovered PEs do not synchronize the latest VRF configurations of the device.

• Only one PE-CE link belonging to this VPN exists on a VPN network.

• The RT value of the VPN is the same as that of the existing VPN.

How should I add a VPN link in global or access topology?In global topology, right-click the PE device to select Auto Discovery.

How does import or removal of some HoPEs affect the other HoPEs in a VPNnetwork?If the imported PEs are not hierarchical, they exist in the VPN as common PEs. Otherwise, thesystem automatically recognizes PE roles. This rule applies to the removal of PEs, too.

246 Frequently Asked Questions

Three types of PEs exist in a VPN: superstratum PEs (SPE), underlayer PEs (UPEs), and middle-levelPEs (MPE).

• If you import an SPE and a UPE, they exist as common PEs.

• If you import an SPE and an MPE, or import an MPE and a UPE, they exist as an SPE and aUPE respectively.

• If you import an MPE when an SPE and a UPE exist, these three devices exist as SPE, MPE,and UPE, respectively.

• If an SPE, MPE, and UPE exist in the VPN, and you remove the MPE only, the SPE and UPEbecome common PEs.

• If an SPE, MPE, and UPE exist in the VPN, when you remove the SPE or UPE, the remainingdevices are SPE and UPE, respectively.

How should I discover a complete VPN network in MPLS VPN Management?When selecting a PE to discover a VPN network, it is recommended that you remove the VPNrelated to the CEs in the VPN list and select PEs to be synchronized before auto discovery.

Why does an invalid link exist in global access topology after auto discoveryis completed?After auto discovery is completed, if the original VPN link does not belong to any VPN, this linkis marked as invalid in global access topology.The causes for the invalid link may be:• Association between the interface and VRF on the PE is removed.

• Definition of the VRF associated with the interface on the PE was modified, and the RT valuein the new VRF does not belong to any VPN in MPLS VPN Management.

MPLS VPN Management does not manage an invalid link. Therefore, it is recommended that youremove it.

Why can't PC be imported to MPLS VPN Management as a CE?PEs and CEs managed by MPLS VPN Management must support SNMP. Check whether the PCsupports SNMP. If not, you can create a virtual CE to replace the PC and configure a real IP addressfor the virtual CE interface.

In a VPN with the audit result being Connected, why are PE-Core linksdisplayed as unknown in the topology?PE-Core links and inter-HoPE links are defined when the devices are being imported and MPLSVPN Management does not support dynamic interface update. You can modify interfaces onPE-Core links and inter-HoPE links.

Why is audit information not displayed when inter-spoke unconnectivity in aHub-Spoke VPN is audited?• There are less than two spokes.

• No hub sites exist on the VPN network.

What networking schemes does MPLS VPN Management support?Currently the following networking schemes are supported: Full-Mesh and Hub-Spoke based onVPN type, VPN with VMCEs, VPN with HoPEs, and VPN with dual-homed CEs based on deviceroles.


When I deploy a connected link, why is it displayed in red in the topology?When you associate VPN with a PE interface, the interface automatically becomes down, andgenerates a Down alarm. Therefore, the IMC considers this link failed.

• If you have configured a PE to send Traps to the IMC, the IMC displays the link as normalbecause it received an interface up alarm when the interface automatically becomes up.

• If you do not configure the PE to send Traps to the IMC but configured polling interval, theIMC displays the link as normal because it can obtain the real status of the link during thenext polling.

• If you do not configure the PE to send Traps to the IMC nor configure polling interval, you canset polling for the PE or manually synchronize the PE to make the link displayed as normal.

Why do only two links at most between AS and PEs appear in the topology?• If too many links are displayed in a topology, the topology looks disorderly, and it is difficult

for you to view the links.• The system considers the link on the PE enabled with MPLS as a connection to the core network.

However, when the PE is a P, there may be many links to other PEs. In this case, the systemdisplays only two of the links to avoid influence on monitoring of the network. If the two linksdisplayed in the topology are not what you need, you can select either of them, and modifythe PE interface connected to the link as the PE interface you want to view. In this way, youcan view the link you want to view.

In a PE to CE VPN link information page, both left and right interfaces of thelink are all up, but why is the status of this link unknown in topology?The link status cannot be obtained because one of devices cannot be reached by ping, so thestatus of this link is unknown.

Why am I unable to select sub-interfaces of a Cisco router during interfaceconfiguration for service deployment?Configure VLANs or enable MPLS for the sub-interfaces of the Cisco router and synchronize thedevice in the MVM.

When I add an SA to a VPN that is monitored, why isn't this SA monitoredin this VPN monitor automatically?The system does not add a new SA to any monitor automatically, and you need to do it yourself.When you delete an SA, the system removes it from all the monitors.

Why can't SA be monitored after rebooting a Cisco device?The interface index is changed after reboot. To prevent this situation execute thesnmp-serverifindex persist command in Cisco devices.

When I add a VPN or SA to monitor, why does it return "Interface trafficsampling test failed" or doesn't display a correct status?• Check the GET operation on ifTable (ifXTable) through SNMP protocol.

• Try to synchronize PEs in the VPN or SA first, make auto discovery, and then add it to monitoragain.


When I import devices to MPLS VPN Management, why can't I see Ciscodevices in the Select Device page?The MPLS VPN Management has no Cisco driver. Contact the technical support center.

Why is the progress information in the device import operation result pageincorrect sometimes?Only one client can perform the device import operation at a time. If two clients perform theoperation at almost the same time, they may be able to perform the operation but the progressinformation cannot show the device import progress correctly. However, the device import operationssucceed. In this case, you can view the operation results from the device list.

When several spokes are deployed, why can't these links be discovered?When the networking scheme is Hub-Spoke, it is necessary to configure both hub and spoke nodesin order to discover valid links.

What should be done if MPLS VPN Management daemon process terminatesabnormally, for instance, when power goes off, and MPLS VPN Managementmay not be working properly?Delete all VPNs and PEs in MPLS VPN Management. Import PE again and execute auto discovery.

Why is the audit result of CE-to-CE “unconnective” when CE-to-CE is actually“connective”?MPLS VPN Management executes connectivity audit when it receives related alarms. Because ofa time delay, such as device reboot or instantaneous power down and up, BGP is not steady. Inthis case audit result may not be correct. If this happens, audit VPN manually

Why can't MPLS VPN Management discover hierarchy relation in an existingVPN?MPLS VPN Management cannot discover UPEs in an existing VPN if there are new UPEs addedinto the VPN network. In this case delete all PEs and execute auto discovery again.

Why can't the auto discover process finish sometimes?During the auto discovery process network connection may disconnect occasionally. In this casethe auto discovery page cannot receive the auto discovery completion message. Hence it does notfinish. If this happens, click cancel auto discovery link in the page and redo auto discovery again.

Why is there a VPN shown in topology after it has been deleted in the Webpage?The message of VPN deletion is not received by topology due to a network problem. In this casereload the topology tree.

Why do some SA links not belong to any VPN but they are shown asundeployment failure in topology when some SA links are undeployed in aslot?When you undeploy some SA links in a slot, some fail but their associated VPNs are markedinvalid. This is because the system is busy. Undeployment is not completed. In this case removethese SA links manually.


What is the restriction of importing a P device to an AS in MPLS global networktopology?A P device can only exist in one AS.

On a PE device, two VPN instances are configured, associated with twointerfaces respectively, and set with the same IP address and mask for theinterfaces. When the SA link information of the PE device is viewed on theaccess topology, why do the IP address and mask of the interface on one ofthe links are displayed as "N/A"?The MPLS VPN Management module reads SA link information based on the standard MIB, whichrequires that the interfaces on the same device cannot have the same IP address. As a result, MPLSVPN Management cannot read duplicate IP address information and displays "N/A" instead. Toprevent such problems, do not configure two or more interfaces on a device with the same IPaddress

Why doesn't global topology show the links between P devices and PE devicesafter P devices are imported?Add links between P devices and PE devices in the topology in either of the following ways:• Use the Auto Link function in the global topology to add links between P devices and PE

devices.• If the IP address of an interface directly connecting the devices does not have a 30-bit mask,

you must manually add links in the topology.

When a VPN or SA is added as the monitor target of a PE interface (whichis a VLAN interface), a success message appears. Why is the actual operationresult a failure?The traffic monitor function allows you to map one physical interface to only one VLAN interface.Otherwise, the system can give an inconsistent prompt message with the actual monitor status.

In an MCE network, why is the MCE-CE link data different from the actualtraffic?When MPLS VPN Management monitors traffic for an MCE-CE link, it actually monitors the VPNtraffic on the sub-interfaces bound to PE-MCE. As a result, the data is different from the actualtraffic.

L2VPN Management

What should I do if the configuration comparison result for a PE is DifferentConfig?This result indicates that the L2VPN configuration maintained in IMC for a PE is different from theL2VPN configuration on the PE. If the configuration on the PE is trustworthy, you can use the autodiscovery function of the L2VPN Management to update IMC with the configuration on the PE. Ifthe L2VPN configuration on the PE has errors, log in to the PE to restore the configuration.


MPLS TE Management

If I just configure part of the configuration parameters to add a dynamicRSVP-TE tunnel, what happens?In the tunnel adding process, the system uses the default settings for the configuration parametersthat you do not configure.

How do affinity and affinity mask configurations of a dynamic RSVP-TE tunnelaffect the displaying of topology information?The topology function module displays only topology information that matches the specified affinityand affinity mask when you select to filter topology by affinity.

In the process of adding or modifying dynamic RSVP-TE tunnels, why are theconfiguration items on the advanced attributes configuration page not alwaysthe same?Some commands for configuring an MPLS TE tunnel are mutually exclusive. For such commands,the system provides the hiding function. If you select one command, the commands exclusive withthe command do not appear on the interface.

After I configured FRR protection, the system prompted that the configurationsucceeded, but why isn't there a related record in the IMC database?Because of a time delay, the FRR configuration has not taken effect on the device. Therefore, thereis no related record on the device and in the IMC database. It is recommended that you useautomatic discovery or perform device synchronization.

During the traffic forwarding configuration process, why did I fail to configureforwarding adjacency after I configured IGP shortcut?IGP shortcut and forwarding adjacency configurations are mutually exclusive.

In the process of configuring traffic forwarding, IGP shortcut or forwardingadjacency configuration is successful, but why isn't there a related record inthe IMC database?The MPLS TE management can obtain only the configuration currently used by the device. However,the device may not be using the traffic forwarding configuration that you made. Therefore, thereis no record of your configuration in the IMC database.

When configuring multiple protection for the same interface, why does theTE management only show information for one protection?Even though multiple protections are configured, only one protection can be active when tunnel isdown. Other protections do not take effect. The TE management only displays the ones that areactive.

MPLS Management

Why does the system prompt "Telnet failure" when I import a device?Analysis: The Telnet parameters on the IMC platform are inconsistent with those configured on thedevice.Solution: View and modify the Telnet parameters for the device on the device details page on theIMC platform.

MPLS TE Management 251

Why does the system prompt "synchronization failure" when I synchronize adevice on the Device Management page or in the MPLS topology?Analysis: Possible reasons for the synchronization failure include device unreachability, inconsistencyof Telnet parameters on the IMC platform and those on the device, and device model not beingsupported by the MPLS management.Solution: Check and modify the network configuration if needed to make sure the device and IMCcan reach each other. View and modify Telnet parameters on the device details page of the IMCplatform. See the Release Notes to check whether MPLS Management supports the device model.


8 Support and other resourcesContacting HP

For worldwide technical support information, see the HP support website:http://www.hp.com/supportBefore contacting HP, collect the following information:

• Technical support registration number (if applicable)

• Product serial numbers

• Product model names and number

• Product identification number

• Applicable error message

• Add-on boards or hardware

• Third-party hardware or software

• Operating system type and revision level

Subscription serviceHP recommends that you register your product at the Subscriber's Choice for Business website:http://www.hp.com/go/wwalertsAfter registering, you will receive email notification of product enhancements, new driver versions,firmware updates, and other product resources.

Related information

DocumentsTo find related documents, browse to the Manuals page of the HP Business Support Center website:http://www.hp.com/support/manuals

• For related documentation, navigate to the Networking section, and select a networkingcategory.

• For a complete list of acronyms and their definitions, see HP FlexNetwork Technology Acronyms.

Websites• HP.com: http://www.hp.com

• HP Networking: http://www.hp.com/go/networking

• HP download drivers and software: http://www.hp.com/support/downloads

Typographic conventionsThis section describes the conventions used in this documentation set.

Contacting HP 253

http://www.hp.com/support

http://www.hp.com/go/wwalerts

http://www.hp.com/support/manuals

http://www.hp.com

http://www.hp.com/go/networking

http://www.hp.com/support/downloads

Document conventionsTable 2 Document conventions

DescriptionConvention

Cross-reference links and email addressesBlue text:Table 2 (page 254)

Website addressesBlue, underlined text: http://www.hp.com

Bold text • Keys that are pressed

• Text typed into a GUI element, such as a box

• GUI elements that are clicked or selected, such as menu and list items, buttons,tabs, and check boxes

Text emphasisItalic text

Monospace text • File and directory names

• System output

• Code

• Commands, their arguments, and argument values

Monospace, italic text • Code variables

• Command variables

Emphasized monospace textMonospace, bold text

GUI conventionsTable 3 GUI conventions

DescriptionConvention

Window names, button names, field names, and menu items are in bold text.BoldfaceFor example, the New User window appears; click OK.

Multi-level menus are separated by angle brackets.>For example, File > Create > Folder.

Symbols

NOTE: An alert that contains additional or supplementary information.

TIP: An alert that provides helpful information.

254 Support and other resources

http://www.hp.com

http://www.hp.com

9 Documentation feedbackHP is committed to providing documentation that meets your needs. To help us improve thedocumentation, send any errors, suggestions, or comments to Documentation Feedback([email protected]). Include the document title and part number, version number, or the URLwhen submitting your feedback.

255

mailto:[email protected]

GlossaryThe following list defines terms and acronyms related to MVM.

A

AC Attachment circuit. Connects a CE to a PE. It can use physical interfaces or virtual interfaces.Usually, all user packets on an AC, including Layer 2 and Layer 3 protocol messages, must beforwarded to the peer site without being changed.

access topology Access topology involves global topology and VPN access topology. Global topology displaysthe network structure of all VPN resources, including all PEs, CEs, and the AS Core; while theVPN access topology displays network structure of all VPN resources in a VPN.

AS core An Autonomous System (AS). It can contain different regions and devices. In the global topologyof an MPLS VPN network, AS Core can also represent a network composed of a set of coredevices. MVM does not manage the devices in the network.

auto discovery Based on VPN resources, auto discovery enables you to discover VPNs and VPN links existingin a network by using the VPN instance RT value of a PE device.

B

BGP Border Gateway Protocol. It establishes signaling sessions through route reflectors (RRs) andsupports networking across multiple autonomous systems (ASs).

BGP/MPLS VPN Border Gateway Protocol/Multiprotocol Label Switching VPN. Uses BGP to advertise VPN routesand uses MPLS to forward VPN packets on service provider backbones.

BSB Blockade State Block.

C

CE Customer edge device. A device directly connected with the service provider network.CE dual-homing A CE router is connected to two Provider Edge (PE) routers, and the binding VRF information of

their interfaces connecting to the two CEs belongs to the same Virtual Routing and Forwarding(VRF) instance.

CLNP Connectionless network protocol. A datagram network protocol, it provides the same underlyingservice to a transport layer as IP.

configuration audit Compare the latest configuration that MVM synchronized from the device with the deviceconfiguration saved in the MVM. The results are displayed in the PE device list and the networktopology.

configurationchanged

Compare the latest configuration that MVM synchronized from the device with the deviceconfiguration saved in the MVM. If they are not consistent, the device is considered asconfiguration changed.

connectivity audit Connectivity between CEs in the same VPN is audited and the connectivity or unconnectivitybetween CEs is listed in detail. (Inter-Spoke connectivity is not audited by default, unless otherwisespecified.)

CPE-based Customer premises equipment-based.customized group With this function, you can divide VPNs into manageable groups as needed.

E

export RT Export RT defines which sites can receive VPN-IPv4 routes. A local PE sets this type of VPN targetattribute for VPN-IPv4 routes learned from directly connected sites before advertising them toother PEs. See RT.

256 Glossary

F

FEC Forwarding Equivalence Class. A technique used for controlling errors in data transmission overunreliable or noisy communication channels. See RT.

full-mesh In this networking scheme, each site contains a group of RT attributes with values of Import RTand Export RT being the same, and all sites are hub sites.

full-mesh network A full mesh network has a fully connected mesh topology. For a VPLS VPN network, it means thatevery PE on the network has a direct connection to every other PE on the network, logically.

H

H-VPLS network In an H-VPLS network, all NPE devices are fully meshed logically, and a UPE device establishesa virtual connection with only the nearest NPE device.

HoPE Hierarchy of PE. MVM includes three types of HoPEs: SPE, MPE, and UPE, with no limit on thenumber of levels. A one-level PE is called a general PE, a two-level HoPE includes SPE and UPE.If there is a three-level HoPE or a HoPE with more than three levels, the lowest level is UPE, thehighest is SPE, and the PEs in the middle are MPEs.

hub-spoke In this networking scheme, the site in the center is called the hub site, which knows routes to allthe other sites in the same VPN. The sites that are not in the center are called spoke sites, fromwhich traffic reaches the destination through the hub site. This type of networking scheme is calledHub-Spoke networking.

I

import RT Import RT defines from which sites a PE can receive routes. A PE checks the Export RT of VPN-IPv4routes advertised by other PEs. If the Export RT matches the Import RT of the VPN instance, thePE adds the routes to the VPN routing table. See RT.

IPX Internet packet exchange.IS-IS Intermediate System to Intermediate System. A routing protocol designed to move information

efficiently within a network.

L

L2VPN manager Layer 2 VPN manager.LDP Label Distribution Protocol. An MPLS signaling protocol, which is in charge of classifying FECs,

distributing labels, and establishing and maintaining LSPs.LDP session LDP sessions are established between LSRs based on TCP connections and are used to exchange

messages for label binding, label releasing, and error notification.LER Label Edge Router. A router that operates at the edge of a Multiprotocol Label Switching network.link invalid If association lost or RT value change on a VPN link results in the link not belonging to the original

VPN, MVM considers it invalid.LSP Label Switched Path. An LSP is the path along which packets of a FEC travel through an MPLS

network.LSR Label Switching Router. An LSR is a fundamental component on an MPLS network. LSRs support

label distribution and label swapping.

M

management VPN A management VPN is a VPN with Hub-Spoke networking scheme, and it can manage user-endCEs.

MCE Multi-VPN-Instance CE. A a router that has Multiple VPN-Instances, running in an Intranet.MPE Middle level PE. In an HoPE architecture, the device connecting a UPE and an SPE.MPLS Multiprotocol Label Switching. MPLS is critical to the implementation of MPLS traffic engineering,

and supports explicit LSP routing.

257

MPLS TE MPLS Traffic Engineering. MPLS TE combines the MPLS and traffic engineering technologies. Byestablishing LSP tunnels along specific paths, it supports reserving resources to best utilize networkresources and avoid non-even load distribution. When network resources are insufficient, MPLSTE allows bandwidth-hungry LSPs and critical user traffic to occupy the bandwidth for lowerpriority LSP tunnels. In case an LSP tunnel fails or congestion occurs on a network node, the pathbackup and Fast Reroute (FRR) features that MPLS TE provides can reroute traffic to a backuppath for forwarding.

MPLS VPN Multiprotocol Label Switching Virtual Private Network.MPLS VPNconfigurationsynchronization

The latest VRF configuration and VRF routing information on a PE are obtained, deciding whetherthe VRF configuration in MVM has changed.

MVM MPLS VPN Manager.

N

non-managed CE A CE device in a VPN. It maps to an actual existing but unmanageable CE device.NPE Network provider edge. A device that functions as the network core PE. An NPE resides at the

edge of a VPLS network core domain and provides transparent VPLS transport services betweencore networks.

O

OSPF Open Shortest Path First.

P

P Provider Router. A backbone router on a service provider network and not directly connectedwith any CE. It only needs to be equipped with MPLS capability.

PBB Provider Backbone Bridge. A set of architecture and protocols for routing over a provider'snetwork, allowing interconnection of multiple Provider Bridge Networks without losing individuallydefined VLANs.

PE Provider edge. A device connecting one or more CEs to the service provider network, mainly foraccess to VPN services. A PE maps and forwards packets between private networks and publicnetwork tunnels. A PE can be a UPE or NPE.

peer Two LSRs using an LDP session to exchange FEC-label bindings are peers.PW Pseudo wire. The bidirectional virtual connection between two VSIs. A PW consists of two

unidirectional virtual circuits (VCs).

R

RD Route Distinguisher. An address field prefixed to a specific IPv4 address, making VPN IPv4prefixes globally unique.

region Network devices that belong to the same area are assigned to the same region to facilitatemanagement. A region can contain up to ten levels of sub-regions.

RSVP Resource Reservation Protocol. RSVP is designed for Integrated Service (IntServ). It reservesresources on each node along a path. RSVP operates at the transport layer but does not participatein data transmission. It is an Internet control protocol similar to ICMP.

RSVP-TE RSVP Traffic Engineering extension protocol. RSVP-TE is an extension to the RSVP. It supportsMPLS label distribution and allows resource reservation information to be transmitted with labelbindings. It can be used as a signaling protocol for LSP tunnel setup in MPLS TE.

RT Route Target. BGP/MPLS uses the 32-bit BGP extended community attributes called VPN targetattributes, or route target attributes, to control the advertisement and receipt of VPN routinginformation.VPN RT attributes define which sites can receive VPN-IPv4 routes, and from whichsites a PE can receive routes.

258 Glossary

S

SA Service Access. Equals to a PE-CE link, indicating an access from a CE in the VPN.SC Service Community. The basic element in constructing a VPN, including Full-Mesh and Hub-Spoke

networking schemes. If multiple SCs exist in a common station, they can form a VPN together.service topology Logical structure of all VPN links in a VPN, including links between CEs and CEs, with CEs

including manageable CEs and non-managed CEs.site A group of IP systems with IP connectivity being implemented without relying on any service

provider network.SOA Service Oriented Architecture.SPE Superstratum PE (SPE) or Service Provider-end PE. The device connecting the core device in an

HoPE architecture.spoke In Hub-Spoke networking scheme, the sites that do not reside on the core are called spoke sites.

Packets from these sites reach the destination through the hub node.

T

TCP Transmission Control Protocol.TE Traffic Engineering. The process of steering traffic across the network backbone to enable efficient

use of available bandwidth between two routers.

U

UPE User Facing-Provider Edge. A device that functions edge device that functions as the user accessconvergence device. In a HoPE architecture, the device connecting the user network is called anunderlayer PE (UPE) or user-end PE.

V

VDPN Virtual Dialup Private Network. Extends remote access to a private network using a sharedinfrastructure.

VLL Virtual Leased Line. A point-to-point virtual leased line technology.VMCE A VLAN isolation of MCE (VMCE). A CE device connecting multiple PEs and CEs.VPLS Virtual private LAN service. Provides multipoint to multipoint communication over IP/MPLS networks.VPN Virtual Private Network. A set of sites. VPN is used to set up private dedicated networks over the

public network.VPN Link A link for a user-end network to connect to an MPLS VPN network, that is, a PE-CE link. For a

network that has MCEs, it is an MCE-CE link.VPN networkingschemes

VPN networking schemes include Hub-Spoke and Full-Mesh based on VPN network types andinclude VPN network with MCEs, with HoPEs and with dual-homed CEs based on device roles.

VRF VPN Routing and Forwarding instance. Allows multiple instances of a routing table to co-existwithin the same router at the same time.

VSI Virtual switch instance that maps actual VPLS access links to virtual links.

259

Index

Ccentralized deployment model, 17configuring traffic engineering in MPLS TE Management

, 179contacting HP, 253

Ddeploying a PBB VPN, 127deploying a VLL VPN, 126deploying a VPLS VPN, 123distributed deployment model, 18documentation, 253

typographic conventions, 254

Eexplicit path management, 15

FFAQ, 246Frequently asked questions see FAQ

Hhelp

obtaining, 253HP

technical support, 253

Iinstallation

centralized deployment model, 17distributed deployment model, 18installation types, 17installing MVM in a centralized deployment, 18installing MVM in a distributed deployment, 21

installation requirements, 17installation types, 17

centralized deployment model, 17distributed deployment model, 18

LL2VPN Management

deployment guidelines, 23terminology, 118using L2VPN Management with non-BGP protocols, 118

L2VPN management, 116application, 171applications, 140automatic discovery, 169basic VPN concepts, 116configuring a PBB network, 156configuring a VLL VPN, 150configuring an LDP H-VPLS VPN, 145configuring an LDP VPLS VPN, 140deploying VPNs , 123L2VPN topology, 171

managing an BGP VPLS VPN, 172managing VPN resources, 166using L2VPN management with BGP protocol, 160VPN devices, 161

Mmanaging ACs, 122managing deployment tasks, 129managing VPN resources, 119managing VPNs, 119MPLS, 13MPLS Management, 28

introduction to, 14, 15Quick Guide page, 16Quick Start page, 14tools available in, 16tools included in, 14

MPLS TE Management, 175introduction to, 14Quick Guide page, 15TE and MPLS, 175

MPLS TE Management overview, 175MPLS TE Manager

tools available in, 15MPLS TE tunnel management, 15MPLS VPN Management

as base MVM application, 13introduction to, 13Quick Guide page, 13tools included in, 13

Multiprotocol Label Switching, 13MVM

introduction to, 13MVM installation, introduction, 17

PPBB

Basic Concepts, 118Overview, 118

protection management, 15

Rregistering

product, 253subscription service, 253

resource management, 15RSVP TE advanced functions, 15

TTE topology, 15technical support, 253

HP, 253Traffic access management, 15traffic engineering tools, 15traffic monitoring, 14typographic conventions

260 Index

documentation, 253symbols, 254text GUI conventions, 254

Uuninstalling MVM, 26unploying VPNs, 129upgrading MVM, 25using L2VPN management

automatic discovery, 137L2VPN topology, 139VPN devices, 130

using MPLS management, 91getting started with MPLS management, 93MPLS management overview, 91typical application, 94using MPLS management components, 96

using MPLS VPN Managementalarm TopN, 72applications, 81auto discovery, 61basic VPN concepts, 28global topology, 64MPLS VPN Managementoverview, 28quick guide, 29traffic monitor, 73VPN devices, 56VPN resource management, 31

VVLL

Basic Concepts, 117Overview, 117

VPLSBasic Concepts, 116Operation, 117Overview, 116VPN Types, 117

VPN device lists, 14VPN fault detection, 14VPN resource management, 14VPN traffic monitoring, 14

Wwebsites, 253

261