Operation Manual – MCE
H3C S3610&S5510 Series Ethernet Switches
Chapter 2 MCE Configuration
2-20
10.214.10.0/24 Direct 0 0 10.214.10.4 Vlan10
10.214.10.4/32 Direct 0 0 127.0.0.1 InLoop0
100.100.10.1/32 Direct 0 0 127.0.0.1 InLoop0
192.168.0.0/16 O_ASE 150 1 10.214.10.2 Vlan10
As shown in the displayed information above, the static routes of VPN1 have been
imported to the OSPF routing table between MCE and PE.
Create OSPF process 20 and import the routing information of VPN2, which is similar
to the above procedure. The only difference lies in that RIP routes rather than static
routes are imported to the OSPF routing table of MCE. The detailed configuration
procedures are omitted here. The information displayed below verifies the
configuration.
<PE> display ip routing-table vpn-instance vpn2
display ip routing-table vpn-instance vpn2
Routing Tables: vpn2
Destinations : 6 Routes : 6
Destination/Mask Proto Pre Cost NextHop Interface
127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0
127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0
10.214.20.0/24 Direct 0 0 10.214.20.4 Vlan20
10.214.20.4/32 Direct 0 0 127.0.0.1 InLoop0
200.200.20.1/32 Direct 0 0 127.0.0.1 InLoop0
192.168.10.0/24 O_ASE 150 1 10.214.20.2 Vlan20
After the above configurations, the routing information of VPN1 and VPN2 can be
advertised to PE properly.
2.5.2 MCE Configuration Example (B)
I. Network requirements
z
An S3610 switch functions as MCE. It is required that VPN routes of site 1 and site
2 be advertised to the PE for the purpose that VPNs at both ends of the MPLS
backbone network can communicate with each other properly.
z
OSPF runs within both site 1 and site 2, and EBGP runs between MCE and PE.
