H3C S5500-HI Switch Series User manual

H3C S5500-HI Switch Series
MPLS Configuration Guide
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: Release 5501
Document version: 6W100-20140103

Copyright © 2014, Hangzhou H3C Technologies Co., Ltd. and its licensors
All rights reserved
No part of this manual may be reproduced or transmitted in any form or by any means without prior
written consent of Hangzhou H3C Technologies Co., Ltd.
Trademarks
H3C, , H3CS, H3CIE, H3CNE, Aolynk, , H3Care, , IRF, NetPilot, Netflow,
SecEngine, SecPath, SecCenter, SecBlade, Comware, ITCMM and HUASAN are trademarks of
Hangzhou H3C Technologies Co., Ltd.
All other trademarks that may be mentioned in this manual are the property of their respective owners
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.

Preface
The H3C S5500-HI documentation set includes 12 configuration guides, which describe the software
features for the H3C S5500-HI Switch Series and guide you through the software configuration
procedures. These configuration guides also provide configuration examples to help you apply software
features to different network scenarios.
The MPLS Configuration Guide describes fundamentals and configuration of MPLS and its extended
functions, including MCE, IPv6MCE, MPLS basics, MPLS TE, VPLS, MPLS L2VPN, IPv6 MPLS L3VPN,.and
MPLS L3VPN.
This preface includes:
•Audience
•Added and modified features
•Conventions
•About the H3C S5500-HI documentation set
•Obtaining documentation
•Technical support
•Documentation feedback
Audience
This documentation is intended for:
•Network planners
•Field technical support and servicing engineers
•Network administrators working with the S5500-HI series
Added and modified features
Compared to Release 5206, Release 5501 does not contain any changes to MPLS.
Conventions
This section describes the conventions used in this documentation set.
Command conventions
Convention Descri
p
tion
Boldface Bold text represents commands and keywords that you enter literally as shown.
Italic Italic text represents arguments that you replace with actual values.
[ ] Square brackets enclose syntax choices (keywords or arguments) that are optional.
{ x | y | ... }
Braces enclose a set of required syntax choices separated by vertical bars, from which
you select one.

Convention Descri
p
tion
[ x | y | ... ]
Square brackets enclose a set of optional syntax choices separated by vertical bars, from
which you select one or none.
{ x | y | ... } *
Asterisk marked braces enclose a set of required syntax choices separated by vertical
bars, from which you select at least one.
[ x | y | ... ] *
Asterisk marked square brackets enclose optional syntax choices separated by vertical
bars, from which you select one choice, multiple choices, or none.
&<1-n> The argument or keyword and argument combination before the ampersand (&) sign can
be entered 1 to n times.
# A line that starts with a pound (#) sign is comments.
GUI conventions
Convention Descri
p
tion
Boldface Window names, button names, field names, and menu items are in Boldface. For
example, the New User window appears; click OK.
> Multi-level menus are separated by angle brackets. For example, File > Create > Folder.
Convention Descri
p
tion
< > Button names are inside angle brackets. For example, click <OK>.
[ ] Window names, menu items, data table and field names are inside square brackets. For
example, pop up the [New User] window.
/ Multi-level menus are separated by forward slashes. For example, [File/Create/Folder].
Symbols
Convention Descri
p
tion
WARNING An alert that calls attention to important information that if not understood or followed can
result in personal injury.
CAUTION An alert that calls attention to important information that if not understood or followed can
result in data loss, data corruption, or damage to hardware or software.
IMPORTANT An alert that calls attention to essential information.
NOTE An alert that contains additional or supplementary information.
TIP An alert that provides helpful information.
Network topology icons
Represents a generic network device, such as a router, switch, or firewall.
Represents a routing-capable device, such as a router or Layer 3 switch.
Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports
Layer 2 forwarding and other Layer 2 features.

Port numbering in examples
The port numbers in this document are for illustration only and might be unavailable on your device.
About the H3C S5500-HI documentation set
The H3C S5500-HI documentation set includes:
Cate
g
or
y
Documents Pur
p
oses
Product
description and
specifications
Marketing brochure Describe product specifications and benefits.
Technology white papers Provide an in-depth description of software features and
technologies.
Hardware
specifications and
installation
Compliance and safety
manual
CE DOCs
Provide regulatory information and the safety instructions
that must be followed during installation.
Installation quick start Guides you through initial installation and setup
procedures to help you quickly set up your device.
Installation guide Provides a complete guide to switch installation and
specifications.
LSPM1FAN and
LSPM1FANB Installation
Manual
Describes the appearances, specifications, installation,
and removal of the pluggable fan modules available for
the products.
User manuals for power
modules
Describe the specifications, installation, and replacement
of hot swappable power modules.
RPS Ordering Information
for H3C Low-End Ethernet
Switches
Helps you order RPSs for switches that can work with an
RPS.
User manuals for RPSs Describe the specifications, installation, and replacement
of RPSs.
User manuals for interface
cards
Describe the specifications, installation, and replacement
of expansion interface cards.
H3C Low End Series
Ethernet Switches Pluggable
Modules Manual
Describes the specifications of pluggable transceiver
modules.
Pluggable SFP[SFP+][XFP]
Transceiver Modules
Installation Guide
Describe the installation, and replacement of
SFP/SFP+/XFP transceiver modules.
Software
configuration
Configuration guides Describe software features and configuration procedures.
Command references Provide a quick reference to all available commands.
Operations and
maintenance Release notes
Provide information about the product release, including
the version history, hardware and software compatibility
matrix, version upgrade information, technical support
information, and software upgrading.

Obtaining documentation
You can access the most up-to-date H3C product documentation on the World Wide Web
at http://www.h3c.com.
Click the links on the top navigation bar to obtain different categories of product documentation:
[Technical Support & Documents > Technical Documents] – Provides hardware installation, software
upgrading, and software feature configuration and maintenance documentation.
[Products & Solutions] – Provides information about products and technologies, as well as solutions.
[Technical Support & Documents > Software Download] – Provides the documentation released with the
software version.
Technical support
servi[email protected]
http://www.h3c.com
Documentation feedback
You can e-mail your comments about product documentation to [e-mail].
We appreciate your comments.

i
Contents
Configuring MCE ························································································································································· 1
MCE overview ···································································································································································1
MPLS L3VPN overview·············································································································································1
MPLS L3VPN concepts ·············································································································································2
Multi-VPN-instance CE ·············································································································································4
How MCE works ······················································································································································5
Using MCE in tunneling applications·····················································································································5
Configuring routing on an MCE······································································································································6
Route exchange between an MCE and a VPN site······························································································6
Route exchange between an MCE and a PE ········································································································8
Configuring an MCE ························································································································································8
Configuring VPN instances ·····································································································································8
Configuring routing on an MCE··································································································································· 10
Configuration prerequisites ·································································································································· 10
Configuring routing between MCE and VPN site······························································································ 11
Configuring routing between MCE and PE ········································································································ 16
Resetting BGP connections ············································································································································ 20
Displaying and maintaining MCE································································································································ 21
MCE configuration examples ······································································································································· 22
Using OSPF to advertise VPN routes to the PE··································································································· 22
Using BGP to advertise VPN routes to the PE····································································································· 27
Using tunnels to advertise VPN routes ················································································································ 30
Configuring IPv6 MCE···············································································································································37
Overview········································································································································································· 37
Configuring an IPv6 MCE ············································································································································· 37
Configuring VPN instances ·································································································································· 37
Configuring routing on an IPv6 MCE ·························································································································· 39
Configuration prerequisites ·································································································································· 39
Configuring routing between IPv6 MCE and VPN site ····················································································· 39
Configuring routing between IPv6 MCE and PE································································································ 43
Resetting BGP connections ············································································································································ 46
Displaying information about IPv6 MCE ····················································································································· 46
IPv6 MCE configuration examples ······························································································································· 47
Using IPv6 ISIS to advertise VPN routes to the PE ····························································································· 47
Configuring basic MPLS ············································································································································53
MPLS overview ······························································································································································· 53
Basic concepts ······················································································································································· 53
MPLS network structure ········································································································································· 55
LSP establishment and label distribution ············································································································· 55
MPLS forwarding ··················································································································································· 58
LDP ·········································································································································································· 59
Protocols ································································································································································· 61
MPLS configuration task list··········································································································································· 61
Enabling the MPLS function··········································································································································· 62
Configuring a static LSP ················································································································································ 63
Establishing dynamic LSPs through LDP······················································································································· 64
Configuring MPLS LDP capability ························································································································ 64
Configuring local LDP session parameters ········································································································· 65

ii
Configuring remote LDP session parameters ······································································································ 65
Configuring PHP ···················································································································································· 66
Configuring the policy for triggering LSP establishment ··················································································· 67
Configuring the label distribution control mode ································································································ 67
Configuring LDP loop detection ··························································································································· 68
Configuring LDP MD5 authentication·················································································································· 69
Configuring LDP label filtering ····························································································································· 69
Configuring DSCP for outgoing LDP packets ····································································································· 71
Maintaining LDP sessions ·············································································································································· 71
Configuring BFD for MPLS LDP ···························································································································· 71
Resetting LDP sessions··········································································································································· 72
Managing and optimizing MPLS forwarding ············································································································· 72
Configuring TTL processing mode at ingress······································································································ 72
Sending back ICMP TTL exceeded messages for MPLS TTL expired packets ················································· 73
Configuring LDP GR ·············································································································································· 74
Setting MPLS statistics reading interval························································································································ 76
Inspecting LSPs ······························································································································································· 76
Configuring MPLS LSP ping·································································································································· 77
Configuring MPLS LSP tracert······························································································································· 77
Configuring BFD for LSPs······································································································································ 78
Configuring periodic LSP tracert·························································································································· 79
Enabling MPLS trap························································································································································ 80
Displaying and maintaining MPLS ······························································································································· 80
Displaying MPLS operation ·································································································································· 80
Displaying MPLS LDP operation··························································································································· 81
Clearing MPLS statistics ········································································································································ 82
MPLS configuration examples······································································································································· 82
Configuring static LSPs·········································································································································· 82
Configuring LDP to establish LSPs dynamically·································································································· 85
Configuring BFD for LSPs······································································································································ 89
Configuring MPLS TE ·················································································································································91
Overview········································································································································································· 91
Basic concepts of MPLS TE ··································································································································· 92
MPLS TE implementation······································································································································· 92
CR-LSP····································································································································································· 93
RSVP-TE··································································································································································· 94
Traffic forwarding·················································································································································· 98
CR-LSP backup ······················································································································································· 99
FRR ·········································································································································································· 99
PS for an MPLS TE tunnel····································································································································101
Protocols and standards ·····································································································································101
MPLS TE configuration task list ···································································································································102
Configuring basic MPLS TE·········································································································································102
Creating an MPLS TE Tunnel over a static CR-LSP ····································································································103
Configuration prerequisites ································································································································103
Configuration procedure ····································································································································103
Creating an MPLS TE tunnel with a dynamic signaling protocol ············································································104
Configuration prerequisites ································································································································104
Configuration procedure ····································································································································105
Configuring RSVP-TE advanced features ···················································································································108
Configuring RSVP reservation style ···················································································································108
Configuring RSVP state timers····························································································································109
Configuring the RSVP refresh mechanism·········································································································109
Configuring the RSVP hello extension ···············································································································110

iii
Configuring RSVP-TE resource reservation confirmation ·················································································110
Configuring RSVP authentication·······················································································································111
Configuring DSCP for outgoing RSVP packets·································································································111
Configuring RSVP-TE GR·····································································································································111
Tuning CR-LSP setup·····················································································································································112
Configuring route pinning ··································································································································112
Configuring administrative group and affinity attribute··················································································112
Configuring CR-LSP reoptimization····················································································································113
Tuning MPLS TE tunnel setup·······································································································································114
Configuring loop detection ································································································································114
Configuring route and label recording·············································································································114
Configuring tunnel setup retry····························································································································114
Assigning priorities to a tunnel ··························································································································115
Configuring traffic forwarding····································································································································115
Forwarding traffic along MPLS TE tunnels using static routes·········································································115
Forwarding traffic along MPLS TE tunnels through automatic route advertisement······································116
Configuring traffic forwarding tuning parameters····································································································117
Configuring the failed link timer ························································································································117
Specifying the link metric type for tunnel path calculation ·············································································118
Configuring the traffic flow type of a tunnel·····································································································118
Configuring CR-LSP backup ········································································································································119
Configuring FRR ···························································································································································119
Configuration prerequisites ································································································································119
Enabling FRR on the headend of a primary LSP ······························································································120
Configuring a bypass tunnel on its PLR·············································································································120
Configuring node protection ······························································································································121
Configuring the FRR polling timer······················································································································121
Inspecting an MPLS TE tunnel ·····································································································································122
MPLS LSP ping ·····················································································································································122
MPLS LSP tracert ··················································································································································122
Configuring BFD for an MPLS TE Tunnel···········································································································122
Configuring periodic LSP tracert for an MPLS TE tunnel ·················································································124
Configuring protection switching ·······························································································································125
Displaying and maintaining MPLS TE ························································································································125
MPLS TE configuration examples································································································································128
MPLS TE using static CR-LSP configuration example························································································128
MPLS TE using RSVP-TE configuration example ·······························································································132
RSVP-TE GR configuration example···················································································································138
MPLS RSVP-TE and BFD cooperation configuration example ·········································································140
CR-LSP backup configuration example ·············································································································142
FRR configuration example·································································································································146
MPLS TE in MPLS L3VPN configuration example·····························································································154
Troubleshooting MPLS TE ············································································································································162
Configuring VPLS ···················································································································································· 163
VPLS overview ······························································································································································163
Basic VPLS concepts············································································································································163
PW establishment················································································································································164
MAC address learning and flooding ················································································································165
VPLS loop avoidance ··········································································································································166
VPLS packet encapsulation·································································································································166
H-VPLS implementation ·······································································································································167
VPLS configuration task list··········································································································································169
Enabling L2VPN and MPLS L2VPN····························································································································169
Configuring LDP VPLS ··················································································································································169

iv
Configuring an LDP VPLS instance·····················································································································170
Configuring BGP VPLS·················································································································································171
Configuring the BGP extension··························································································································171
Configuring a BGP VPLS instance ·····················································································································171
Resetting VPLS BGP connections························································································································172
Binding a service instance with a VPLS instance ······································································································172
Configuring MAC address learning···························································································································173
Configuring MAC address move ·······························································································································173
Configuring VPLS instance attributes··························································································································173
Inspecting PWs·····························································································································································174
Displaying and maintaining VPLS ······························································································································174
VPLS configuration examples······································································································································175
Binding service instances with VPLS instances ·································································································175
Configuring PW redundancy for H-VPLS access······························································································180
Configuring BFD for the primary link in an H-VPLS network···········································································184
Troubleshooting VPLS···················································································································································189
Configuring MPLS L2VPN······································································································································· 190
MPLS L2VPN overview ················································································································································190
Basic concepts of MPLS L2VPN ·························································································································190
MPLS L2VPN network models ····························································································································191
Remote connection operation ····························································································································191
Implementation of MPLS L2VPN·························································································································193
VC types ·······························································································································································198
MPLS L2VPN configuration task list····························································································································198
Configuring basic MPLS L2VPN ·································································································································199
Configuring a PE-CE interface of a PE·······················································································································199
Configuring Ethernet encapsulation ··················································································································199
Configuring VLAN encapsulation······················································································································200
Configuring a remote CCC connection·····················································································································200
Configuring SVC MPLS L2VPN···································································································································200
Configuring Martini MPLS L2VPN ······························································································································201
Configuring the remote peer······························································································································202
Creating a Martini VC on a Layer 3 interface·································································································202
Creating a Martini VC for a service instance ··································································································202
Inspecting VCs ·····················································································································································204
Configuring Kompella MPLS L2VPN ··························································································································204
Configuring BGP L2VPN capability ··················································································································204
Creating and configuring an MPLS L2VPN ······································································································205
Creating a CE connection ··································································································································205
Displaying and maintaining MPLS L2VPN ················································································································207
MPLS L2VPN configuration examples························································································································208
Example for configuring a remote CCC connection ·······················································································208
Example for configuring SVC MPLS L2VPN ·····································································································212
Example for configuring Martini MPLS L2VPN ································································································215
Example for configuring Kompella MPLS L2VPN·····························································································219
Example for configuring a VC for a service instance······················································································222
Troubleshooting MPLS L2VPN·····································································································································226
Configuring MPLS L3VPN······································································································································· 227
Overview·······································································································································································227
MPLS L3VPN concepts ········································································································································228
MPLS L3VPN packet forwarding························································································································231
MPLS L3VPN networking schemes·····················································································································231
MPLS L3VPN routing information advertisement······························································································234

v
Inter-AS VPN ························································································································································235
Carrier's carrier ···················································································································································238
Nested VPN ·························································································································································240
HoVPN··································································································································································242
OSPF VPN extension···········································································································································244
BGP AS number substitution and SoO··············································································································246
MPLS L3VPN configuration task list····························································································································247
Configuring basic MPLS L3VPN ·································································································································247
Configuration prerequisites ································································································································248
Configuring VPN instances ································································································································248
Configuring routing between PE and CE··········································································································252
Configuring routing between PEs ······················································································································258
Configuring routing features for BGP VPNv4 subaddress family ··································································258
Configuring inter-AS VPN ···········································································································································261
Configuring inter-AS option A····························································································································261
Configuring inter-AS option B ····························································································································262
Configuring inter-AS option C····························································································································262
Configuring nested VPN··············································································································································264
Configuring HoVPN·····················································································································································265
Configuring an OSPF sham link ·································································································································266
Configuring a loopback interface ·····················································································································266
Redistributing the loopback interface route and OSPF routes into BGP························································267
Creating a sham link···········································································································································267
Configuring BGP AS number substitution and SoO·································································································268
Resetting BGP connections ··········································································································································268
Displaying and maintaining MPLS L3VPN ················································································································269
MPLS L3VPN configuration examples························································································································271
Configuring MPLS L3VPNs using EBGP between PE and CE ·········································································271
Configuring MPLS L3VPNs using IBGP between PE and CE ··········································································278
Configuring a hub-spoke network ·····················································································································286
Configuring inter-AS option A····························································································································294
Configuring inter-AS option B ····························································································································299
Configuring inter-AS option C····························································································································304
Configuring carrier's carrier ······························································································································310
Configuring nested VPN·····································································································································317
Configuring HoVPN ············································································································································327
Configuring OSPF sham links ····························································································································333
Configuring BGP AS number substitution ·········································································································338
Configuring BGP AS number substitution and SoO ························································································342
IPv6 MPLS L3VPN configuration ···························································································································· 345
IPv6 MPLS L3VPN overview ········································································································································345
IPv6 MPLS L3VPN packet forwarding ···············································································································346
IPv6 MPLS L3VPN routing information advertisement ·····················································································346
IPv6 MPLS L3VPN network schemes and functions··························································································347
IPv6 MPLS L3VPN configuration task list ···················································································································347
Configuring basic IPv6 MPLS L3VPN·························································································································347
Basic IPv6 MPLS L3VPN configuration task list ································································································347
Configuration prerequisites ································································································································348
Configuring VPN instances ································································································································348
Configuring route related attributes for a VPN instance·················································································349
Configuring routing between PE and CE··········································································································351
Configuring routing between PEs ······················································································································354
Configuring routing features for the BGP-VPNv6 subaddress family·····························································355
Configuring inter-AS IPv6 VPN···································································································································356

vi
Configuration prerequisites ································································································································357
Configuring inter-AS IPv6 VPN option A ··········································································································357
Configuring inter-AS IPv6 VPN option C ··········································································································357
Resetting BGP connections ··········································································································································358
Displaying information about IPv6 MPLS L3VPN······································································································359
IPv6 MPLS L3VPN configuration examples ···············································································································360
Configuring IPv6 MPLS L3VPNs·························································································································360
Configuring inter-AS IPv6 VPN option A ··········································································································367
Configuring inter-AS IPv6 VPN option C ··········································································································372
Configuring carrier's carrier ······························································································································379
Index ········································································································································································ 387

1
Configuring MCE
The term "router" in this document refers to both routers and Layer 3 switches.
The term "interface" in this document refers to Layer 3 interfaces that include VLAN interfaces, Layer 3
Ethernet interfaces, and Layer 3 aggregate interfaces. You can set an Ethernet port as a Layer 3 Ethernet
interface by using the port link-mode route command (see Layer 2—LAN Switching Configuration
Guide).
This chapter covers MCE related configuration. For information about routing protocols, see Layer 3—IP
Services Configuration Guide.
MCE overview
MPLS L3VPN overview
MPLS L3VPN is a type of PE-based L3VPN technology for service provider VPN solutions. It uses BGP to
advertise VPN routes and uses MPLS to forward VPN packets on service provider backbones.
MPLS L3VPN provides flexible networking modes, excellent scalability, and convenient support for MPLS
QoS and MPLS TE.
The MPLS L3VPN model consists of the following types of devices:
•Customer edge (CE) device—A CE resides on a customer network and has one or more interfaces
directly connected with service provider networks. It can be a router, a switch, or a host. It can
neither "sense" the existence of any VPN nor does it need to support MPLS.
•Provider edge (PE) device—A PE resides on a service provider network and connects one or more
CEs to the network. On an MPLS network, all VPN processing occurs on the PEs.
•Provider (P) device—A P device is a core device on a service provider network. It is not directly
connected with any CE. It only needs to be equipped with basic MPLS forwarding capability.

2
Figure 1 Network diagram for MPLS L3VPN model
CEs and PEs mark the boundary between the service providers and the customers.
After a CE establishes adjacency with a directly connected PE, it advertises its VPN routes to the PE and
learns remote VPN routes from the PE. A CE and a PE use BGP/IGP to exchange routing information. You
can also configure static routes between them.
After a PE learns the VPN routing information of a CE, it uses BGP to exchange VPN routing information
with other PEs. A PE maintains routing information about only VPNs that are directly connected, rather
than all VPN routing information on the provider network.
A P router maintains only routes to PEs and does not deal with VPN routing information.
When VPN traffic travels over the MPLS backbone, the ingress PE functions as the ingress Label Switching
Router (LSR), the egress PE functions as the egress LSR, and P routers function as the transit LSRs.
MPLS L3VPN concepts
Site
Sites are often mentioned in the VPN. A site has the following features:
•A site is a group of IP systems with IP connectivity that does not rely on any service provider network
to implement.
•The classification of a site depends on the topology relationship of the devices, rather than the
geographical positions, though the devices at a site are, in most cases, adjacent to each other
geographically.
•The devices at a site can belong to multiple VPNs.
•A site is connected to a provider network through one or more CEs. A site can contain many CEs,
but a CE can belong to only one site.
Sites connected to the same provider network can be classified into different sets by policies. Only the
sites in the same set can access each other through the provider network. Such a set is called a VPN.

3
Address space overlapping
Each VPN independently manages the addresses it uses. The assembly of such addresses for a VPN is
called an address space.
The address spaces of VPNs may overlap. For example, if both VPN 1 and VPN 2 use the addresses on
network segment 10.110.10.0/24, address space overlapping occurs.
VPN instance
In MPLS VPN, routes of different VPNs are identified by VPN instance.
A PE creates and maintains a separate VPN instance for each VPN at a directly connected site. Each
VPN instance contains the VPN membership and routing rules of the corresponding site. If a user at a site
belongs to multiple VPNs at the same time, the VPN instance of the site contains information about all of
the VPNs.
For independence and security of VPN data, each VPN instance on a PE maintains a relatively
independent routing table and a separate label forwarding information base (LFIB). VPN instance
information contains the following items: the LFIB, IP routing table, interfaces bound to the VPN instance,
and administration information of the VPN instance. The administration information of the VPN instance
includes the route distinguisher (RD), route filtering policy, and member interface list.
VPN-IPv4 address
Traditional BGP cannot process overlapping VPN routes. If, for example, both VPN 1 and VPN 2 use
addresses on the segment 10.110.10.0/24 and each advertise a route to the segment, BGP selects only
one of them, which results in the loss of the other route.
PEs use MP-BGP to advertise VPN routes and use VPN-IPv4 address family to solve the problem with
traditional BGP.
A VPN-IPv4 address consists of 12 bytes. The first eight bytes represent the RD, followed by a four-byte
IPv4 address prefix.
Figure 2 VPN-IPv4 address structure
When a PE receives an ordinary IPv4 route from a CE, it must advertise the VPN route to the peer PE. The
uniqueness of a VPN route is implemented by adding an RD to the route.
A service provider can independently assign RDs if the assigned RDs are unique. A PE can advertise
different routes to VPNs even if the VPNs are from different service providers and are using the same IPv4
address space.
Configure a distinct RD for each VPN instance on a PE, so that routes to the same CE use the same RD.
The VPN-IPv4 address with an RD of 0 is a globally unique IPv4 address.
By prefixing a distinct RD to a specific IPv4 address prefix, you get a globally unique VPN IPv4 address
prefix.
An RD can be related to an autonomous system (AS) number, in which case it is the combination of the
AS number and a discretionary number; or it can be related to an IP address, in which case it is the
combination of the IP address and a discretionary number.

4
An RD can be in one of the following formats distinguished by the Type field:
•When the value of the Type field is 0, the Administrator subfield occupies two bytes, the Assigned
number subfield occupies four bytes, and the RD format is 16 - b i t A S n u m b e r :32-bit user-defined
number. For example, 100:1.
•When the value of the Type field is 1, the Administrator subfield occupies four bytes, the Assigned
number subfield occupies two bytes, and the RD format is 32-bit IPv4 address:16-bit user-defined
number. Fo r e xa m p l e, 172.1.1.1:1.
•When the value of the Type field is 2, the Administrator subfield occupies four bytes, the Assigned
number subfield occupies two bytes, and the RD format is 32-bit AS number:16-bit user-defined
number, where the minimum value of the AS number is 65536. For example, 65536:1.
To guarantee global uniqueness for an RD, do not set the Administrator subfield to any private AS
number or private IP address.
Route target attributes
MPLS L3VPN uses the BGP extended community attributes called "route target" attributes to control the
advertisement of VPN routing information.
A VPN instance on a PE supports the following types of route target attributes:
•Export target attribute: A local PE sets this type of route target attribute for VPN-IPv4 routes learned
from directly connected sites before advertising them to other PEs.
•Import target attribute: A PE checks the export target attribute of VPN-IPv4 routes advertised by
other PEs. If the export target attribute matches the import target attribute of the VPN instance, the
PE adds the routes to the VPN routing table.
In other words, route target attributes define which sites can receive VPN-IPv4 routes, and from which
sites that a PE can receive routes.
Similar to RDs, route target attributes can be of the following formats:
•16 - b i t A S n u m b e r :32-bit user-defined number. For example, 100:1.
•32-bit IPv4 address:16-bit user-defined number. Fo r e xa m p l e, 172.1.1.1:1.
•32-bit AS number:16-bit user-defined number, where the minimum value of the AS number is 65536.
For example, 65536:1.
Multi-VPN-instance CE
Using tunnels, MPLS L3VPN implements private network data transmission over the public network.
However, the traditional MPLS L3VPN architecture requires each VPN instance exclusively use a CE to
connect with a PE, as shown in Figure 1.
For better services and higher security, a private network is usually divided into multiple VPNs to isolate
services. To meet these requirements, you can configure a CE for each VPN, which increases users’
device expenses and maintenance costs. Or, you can configure multiple VPNs to use the same CE and
the same routing table, which sacrifices data security.
Using the Multi-VPN-Instance CE (MCE) function of the switch, you can remove the contradiction of low
cost and high security in multi-VPN networks. With MCE configured, a CE can bind each VPN in a
network with a VLAN interface on the CE, and create and maintain a separate routing table (multi-VRF)
for each VPN. This separates the forwarding paths of packets of different VPNs and, in conjunction with
the PE, can correctly advertise the routes of each VPN to the peer PE, ensuring the normal transmission
of VPN packets over the public network.

5
How MCE works
Figure 3 shows how an MCE maintains the routing entries of multiple VPNs and how an MCE exchanges
VPN routes with PEs.
Figure 3 Network diagram for the MCE function
On the left-side network, there are two VPN sites, both of which are connected to the MPLS backbone
through the MCE device. VPN 1 and VPN 2 on the left-side network must establish a tunnel with VPN 1
and VPN 2 on the right-side network, respectively.
With MCE enabled, routing tables can be created for VPN 1 and VPN 2 individually, VLAN-interface 2
can be bound to VPN 1, and VLAN-interface 3 can be bound to VPN 2. When receiving a piece of
routing information, MCE determines the source of the routing information according to the number of
the interface receiving the information. It then maintains the corresponding routing table accordingly.
You must also bind the interfaces to the VPNs on PE 1 in the same way as those on the MCE device. The
MCE device is connected to PE 1 through a trunk, which permits packets of VLAN 2 and VLAN 3 with
VLAN tags carried. In this way, PE 1 can determine the VPN a received packet belongs to according to
the VLAN tag of the packet and passes the packet to the corresponding tunnel.
Using MCE in tunneling applications
In addition to MPLS L3VPN, tunneling technologies can also be used to implement other types of VPNs.
The MCE function provided by the switch can be applied in VPN applications based on tunneling.
Figure 4 Network diagram for using MCE in a tunneling application (1)
PE1
PE
PE2
P
P
VPN2
Site2
VPN1
Site1
MCE
VLAN-int2
VLAN-int3
CE
Site1
VPN2
CE
VPN1
Site2
VLAN-int7
VLAN-int8

6
By establishing multiple tunnels between two MCE devices and binding the tunnel interfaces with VPN
instances, you can make the routing information and data of the VPN instances delivered to the peer
devices through the bound tunnel interfaces. According to the tunnel interfaces receiving the routes, an
MCE device determines the VPN instances that the routes belong to and advertises the routes to the
corresponding sites. As shown in Figure 4, you can bind Tunnel 1 with VPN 1 to make the MCE devices
deliver the routing information and data of VPN 1 through the tunnel.
An MCE can also be used in a tunneling application as shown in Figure 5 to connect with multiple
remote CEs through tunnels. In this scenario, the CE devices only need to receive and advertise routes as
usual, while the MCE advertises and receives VPN routing information based on the bindings between
tunnel interfaces and VPNs.
Figure 5 Network diagram for using MCE in a tunneling application (2)
MCE devices in a tunneling application can exchange VPN routing information with their peer MCE
devices or CE devices directly, just as MCE devices in an MPLS L3VPN application do with the
corresponding PEs. For more information, see "Route exchange between an MCE and a PE."
GRE tunnels, IPv4 over IPv4 tunnels, and IPv4 over IPv6 tunnels support MCE. For introduction and
configuration of tunnel types, see Layer 3—IP Services Configuration Guide.
Configuring routing on an MCE
Interface-to-VPN-instance binding enables MCEs and PEs to determine the sources of received packets
and then forward the packets according to the routing information concerning the corresponding VPNs.
MCE routing configuration includes:
•MCE-VPN site routing configuration
•MCE-PE routing configuration
Route exchange between an MCE and a VPN site
An MCE can adopt the following routing protocols to exchange VPN routes with a site:
•Static route
•RIP
•OSPF
•IS-IS
•IBGP
IP network
VPN 1
Site1
VPN 1
Site2
VPN 2
Site1 VPN 2
Site2
MCE
CE
Tunnel2
CE

7
•EBGP
This section briefly introduces the cooperation of routing protocols and MCE. For information about the
routing protocols, see Layer 3—IP Routing Configuration Guide.
Static routes
An MCE can communicate with a site through static routes. As static routes configured for traditional CEs
take effect globally, address overlapping between multiple VPNs remains a problem until the emergence
of MCE. MCE allows static-route-to-VPN-instance binding, which isolates the static routes of different
VPNs.
RIP
The switch can bind RIP processes to VPN instances. With these bindings on the MCE, private network
routes of different VPNs can be exchanged between MCE and sites through different RIP processes,
isolating and securing VPN routes.
OSPF
The switch can bind OSPF processes to VPN instances and isolate the routes of different VPNs.
For an OSPF process bound to a VPN instance, the router ID of the public network configured in system
view is invalid. You must specify the router ID when creating an OSPF process.
An OSPF process can be bound to only one VPN instance. However, a VPN instance can use multiple
OSPF processes for private network route transmission. To make sure routes can be advertised properly,
configure the same domain ID for all OSPF processes bound to the same VPN instance.
Routes redistributed from OSPF to BGP on the MCE have their OSPF attributes removed. To enable BGP
to distinguish routes redistributed from different OSPF domains, you must enable the redistributed routes
to carry the OSPF domain ID by configuring the domain-id command in OSPF view. The domain ID is
added to BGP VPN routes as an extended community attribute.
In cases where a VPN has multiple MCE devices attached to it and when an MCE device advertises the
routes learned from BGP within the VPN, the routes may be learned by other MCE devices, generating
route loops. To prevent route loops, configure route tags for different VPN instances on each MCE. H3C
recommends that you assign the same route tag to the same VPN on all MCEs.
IS-IS
Similar to those in OSPF, IS-IS processes can be bound to VPN instances for private network routes to be
exchanged between MCE and sites. An IS-IS process can be bound to only one VPN instance.
IBGP
To use IBGP to exchange private routes between an MCE and a site, configure IBGP peers for VPN
instances on the MCE and redistribute IGP routing information from corresponding VPNs. If the MCE is
connected with multiple sites in the same VPN, you can configure the MCE as a route reflector (RR) and
configure the egress routers of the sites as clients, making the MCE reflect routing information between
the sites. This eliminates the necessity for BGP connections between sites, reducing the number of BGP
connections and simplifying network configuration.
EBGP
To use EBGP for exchanging routing information between an MCE and VPN sites, you must configure a
BGP peer for each VPN instance on the MCE, and redistribute the IGP routes of each VPN instance on
the VPN sites. You also can configure filtering policies to filter the received routes and the routes to be
advertised.

8
Route exchange between an MCE and a PE
Routing information entries are bound to specific VPN instances on an MCE device, and packets of each
VPN instance are forwarded between MCE and PE according to interface. As a result, VPN routing
information can be transmitted by performing relatively simple configurations between MCE and PE,
such as importing the VPN routing entries on MCE devices to the routing table of the routing protocol
running between MCE and PEs.
The following routing protocols can be used between MCE and PE devices for routing formation
exchange:
•Static route
•RIP
•OSPF
•IS-IS
•IBGP
•EBGP
For information about routing protocol configuration and route import, see Layer 3—IP Routing
Configuration Guide.
Configuring an MCE
Configuring VPN instances
Configuring VPN instances is required in all MCE networking schemes.
By configuring VPN instances on a PE, you isolate not only VPN routes from public network routes, but
also routes of a VPN from those of another VPN. This feature allows VPN instances to be used in
networking scenarios besides MCE.
Creating a VPN Instance
A VPN instance is associated with a site. It is a collection of the VPN membership and routing rules of its
associated site. A VPN instance does not necessarily correspond to one VPN.
A VPN instance takes effect only after you configure an RD for it. Before configuring an RD for a VPN
instance, you can configure no other parameters for the instance but a description.
You can configure a description for a VPN instance to record its related information, such as its
relationship with a certain VPN.
To create and configure a VPN instance:
Ste
p
Command Remarks
1. Enter system view. system-view N/A
2. Create a VPN instance and
enter VPN instance view. ip vpn-instance vpn-instance-name
N/A
3. Configure an RD for the VPN
instance.
route-distinguisher
route-distinguisher
For easy management, set the
same RD for the same VPN
instance on the MCE and PE.