3Com S7906E Configuration Manual page 1615

[PE2-ospf-100] quit
[PE2] bgp 100
[PE2-bgp] ipv4-family vpn-instance vpn1
[PE2-bgp-vpn1] import-route ospf 100
[PE2-bgp-vpn1] import-route direct
[PE2-bgp-vpn1] quit
[PE2-bgp] quit
After completing the above configurations, if you issue the display ip routing-table vpn-instance
command on the PEs, you should see that the path to the peer CE is along the OSPF route across the
customer networks, instead of the BGP route across the backbone. Take PE 1 as an example:
[PE1] display ip routing-table vpn-instance vpn1
Routing Tables: vpn1
Destinations : 5
Destination/Mask Proto
20.1.1.0/24 OSPF
30.1.1.0/24 OSPF
100.1.1.0/24 Direct 0
100.1.1.2/32 Direct 0
120.1.1.0/24 OSPF
4) Configure a sham link
# Configure PE 1.
[PE1] interface loopback 1
[PE1-LoopBack1] ip binding vpn-instance vpn1
[PE1-LoopBack1] ip address 3.3.3.3 32
[PE1-LoopBack1] quit
[PE1] ospf 100
[PE1-ospf-100] area 1
[PE1-ospf-100-area-0.0.0.1] sham-link 3.3.3.3 5.5.5.5 cost 10
[PE1-ospf-100-area-0.0.0.1] quit
[PE1-ospf-100] quit
# Configure PE 2.
[PE2] interface loopback 1
[PE2-LoopBack1] ip binding vpn-instance vpn1
[PE2-LoopBack1] ip address 5.5.5.5 32
[PE2-LoopBack1] quit
[PE2] ospf 100
[PE2-ospf-100] area 1
[PE2-ospf-100-area-0.0.0.1] sham-link 5.5.5.5 3.3.3.3 cost 10
[PE2-ospf-100-area-0.0.0.1] quit
[PE2-ospf-100] quit
After completing the above configurations, if you issue the display ip routing-table vpn-instance
command again on the PEs, you should see that the path to the peer CE is now along the BGP route
across the backbone, and that a route to the sham link destination address is present. Take PE 1 as an
example:
[PE1] display ip routing-table vpn-instance vpn1
Routing Tables: vpn1
Routes : 5
Pre Cost NextHop
10 1563 100.1.1.1
10 3125 100.1.1.1
0 100.1.1.2
0 127.0.0.1
10 3126 100.1.1.1
1-100
Interface
Vlan12
Vlan12
Vlan12
InLoop0
Vlan12