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
, 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
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
Tunnel
2
CE
