3Com S7906E - Switch, Configuration Manual

Page: 1428 / 2621

2-17
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.30.0/24 Direct 0 0 10.214.30.1 Vlan30
10.214.30.2/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.30.1 Vlan30
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.40.0/24 Direct 0 0 10.214.40.1 Vlan40
10.214.40.2/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.40.1 Vlan40
After the above configurations, the routing information of VPN1 and VPN2 can be advertised to PE
properly.
MCE Configuration Example (B)
Network requirements
z
An S7900E 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.