3Com S7906E Configuration Manual page 1431

10.100.10.1/32 Direct 0
172.16.10.0/24 OSPF
As shown in the displayed information above, MCE has obtained the routing information of VPN1
through OSPF process 10.
# Create OSPF process 20 for MCE whose router ID is 10.10.20.1, bind the process to VPN2.
Redistribute BGP routes from VPN2, enable OSPF multi-instance, and advertise the network segment
10.100.20.0. The procedure of configuring OSPF process 20 is similar to that of configuring OSPF
process 10. Followed is the result of the above configuration.
[MCE] display ip routing-table vpn-instance vpn2
Routing Tables: vpn2
Destinations : 5
Destination/Mask Proto
127.0.0.0/8 Direct 0
127.0.0.1/32 Direct 0
10.100.20.0/24 Direct 0
10.100.20.1/32 Direct 0
172.16.20.0/24 OSPF
Configure the routing protocol running between MCE and PE
# The procedure of connecting MCE to PE through trunk ports is similar to that in
Example (A) and is omitted here.
# Create BGP process 10 for MCE.
[MCE] bgp 100
[MCE-bgp]
# Enter IPv4 address family view in VPN1.
[MCE-bgp] ipv4-family vpn-instance vpn1
[MCE-bgp-vpn1]
# Configure PE as an EBGP peer and import the routing information of OSPF process 10 (assuming
that the address of the interface bound to VPN1 is 10.100.30.3 and the ID of the BGP process is 200).
[MCE-bgp-vpn1] peer 10.100.30.3 as-number 200
[MCE-BGP-vpn1] import-route ospf 10
# Create BGP process 200 on the PE, and configure MCE as an EBGP peer.
<PE> system-view
[PE] bgp 200
[PE-bgp] ipv4-family vpn-instance vpn1
[PE-bgp-vpn1] peer 10.100.30.1 as-number 100
# Display the information about the routes of VPN1 on PE.
<PE-bgp-vpn1> display ip routing-table vpn-instance vpn1
Routing Tables: vpn1
Destinations : 5
Destination/Mask Proto
0 127.0.0.1
10 1 10.100.10.2
Routes : 5
Pre Cost NextHop
0 127.0.0.1
0 127.0.0.1
0 10.100.20.1
0 127.0.0.1
10 1 10.100.20.2
Routes : 5
Pre Cost NextHop
2-20
InLoop0
Vlan2
Interface
InLoop0
InLoop0
Vlan3
InLoop0
Vlan3
MCE Configuration
Interface