HP HSR6800 Configuration Manual page 373

[PE2-GigabitEthernet2/1/1] ip binding vpn-instance vpn1
[PE2-GigabitEthernet2/1/1] ip address 120.1.1.2 24
[PE2-GigabitEthernet2/1/1] quit
[PE2] ospf 100 vpn-instance vpn1
[PE2-ospf-100] domain-id 10
[PE2-ospf-100] area 1
[PE2-ospf-100-area-0.0.0.1] network 120.1.1.0 0.0.0.255
[PE2-ospf-100-area-0.0.0.1] quit
[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 configurations, execute 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
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
Routes : 5
Proto Pre Cost
OSPF 10 1563
OSPF 10 3125
Direct 0 0
Direct 0 0
OSPF 10 3126
365
NextHop Interface
100.1.1.1 GE2/1/1
100.1.1.1 GE2/1/1
100.1.1.2 GE2/1/1
127.0.0.1 InLoop0
100.1.1.1 GE2/1/1