H3C S9500 Series Operation Manual page 908

Operation Manual – MPLS L3VPN
H3C S9500 Series Routing Switches
different from common hosts; it is implemented by specifying an interface of another
VPN as the egress interface through a static route in a VPN; and thus allowing one
logical interface to access multiple VPNs.
1.2 MPLS L3VPN Configuration
1.2.1 Configuring Various Kinds of Routers
Implementing MPLS L3VPN functions requires the following procedures in general:
Configure basic information on PE, CE and P; establish the logical or physical link with
IP capabilities from PE to PE; advertise and update VPN network information.
I. CE router
The configuration on CE is relative simple. Only static route, RIP, OSPF or EBGP
configuration is needed for VPN routing information exchange with the PE connected,
MPLS configuration is not needed.
II. PE router
The configuration on PE is relative complex. After the configuration, the PE implements
MPLS L3VPN core functions.
The following sections describe the configuration tasks on a PE device:
Configuring basic MPLS capability
Defining MPLS L3VPN site
Configuring PE-CE route exchanging
Configuring PE-PE route exchanging
III. P router
The configuration on P device is relative simple. The main task is to configure MPLS
basic capacity on the P device to support LDP and MPLS forwarding.
The following are detailed configurations.
1.2.2 Configuring CE Router
As a customer-side device, only basic configuration is required on a CE router, for
routing information exchange with PE router. Currently route switching modes available
include static route, RIP, OSPF, EBGP, and so on.
I. Creating static route
If you select static route mode for CE-PE route switching, you should then configure a
private static route pointing to PE on CE.
Perform the following configuration in the system view to create/delete a static route in
VPN instance routing table:
Chapter 1 MPLS L3VPN Configuration
1-11