HP 10500 SERIES Configuration Manual page 346

[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 configurations, issue the display ip routing-table vpn-instance command on
the PEs, you can 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
20.1.1.0/24
30.1.1.0/24
100.1.1.0/24
100.1.1.2/32
120.1.1.0/24
Configure a sham link:
4.
# 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 configurations, issue the display ip routing-table vpn-instance command
again on the PEs, you can 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
Destinations : 6
Destination/Mask
3.3.3.3/32
5.5.5.5/32
Routes : 5
Proto Pre Cost
OSPF 10 1563
OSPF 10 3125
Direct 0 0
Direct 0 0
OSPF 10 3126
Routes : 6
Proto Pre Cost
Direct 0 0
BGP 255 0
338
NextHop Interface
100.1.1.1 Vlan11
100.1.1.1 Vlan11
100.1.1.2 Vlan11
127.0.0.1 InLoop0
100.1.1.1 Vlan11
NextHop Interface
127.0.0.1 InLoop0
2.2.2.9 NULL0