Configuring Route Exchange For Mce - H3C S5800 Series Configuration Manual

Only when BGP runs between the MCE and PE, can the VPN target attribute be advertised to the
PE along with the routing information. In other cases, configuring this attribute makes no sense.
VPN targets configured for a VPN instance on an MCE must be consistent with those configured
for the VPN instance on the PE.
A single vpn-target command can configure up to eight VPN targets. You can configure up to 20
VPN targets for a VPN instance.
You can define the maximum number of routes for a VPN instance to support, preventing too
many routes from being redistributed into the PE.
Before associating a routing policy with a VPN instance, you must create the routing policy at first.
Otherwise, the default routing policy is used.

Configuring Route Exchange for MCE

Multi-VPN-instance CE can be regarded as a networking solution for implementing service isolation by
route isolation. There is no special configuration required for a multi-VPN-instance CE, except that you
need to enable the multi-VPN-instance CE function.
After you enable multi-VPN-instance CE, routing loop detection on the PE is disabled for route
calculating to avoid route loss, and the interoperability between routing protocols is disabled to save
system resources.
This section describes the configuration of an MCE in an MPLS L3VPN application. The configuration
for route exchange between an MCE and the peer MCE or CEs in a tunneling application is the same
at that for route exchange between an MCE and PE in an MPLS L3VPN application.
Configuring route exchange when using static routes
An MCE can be connected with a site or a PE through a static route. A static route configured for a
traditional CE is effective globally, which cannot solve the problem of address space overlapping
among VPNs. An MCE supports binding a static route with a VPN instance, so that the static routes of
different VPN instances can be isolated from each other.
Follow these steps to configure route exchange when using static routes:
To do...
Enter system view
Use the command...
system-view
14-12
Remarks
—