Configuring Ospf Sham Links - HP 12500 Series Configuration Manual

[SPE2-bgp] peer 2.2.2.9 connect-interface loopback 0
[SPE2-bgp] ipv4-family vpnv4
[SPE2-bgp-af-vpnv4] peer 2.2.2.9 enable
[SPE2-bgp-af-vpnv4] peer 4.4.4.9 enable
[SPE2-bgp-af-vpnv4] peer 4.4.4.9 upe
[SPE2-bgp-af-vpnv4] quit
[SPE2-bgp]ipv4-family vpn-instance vpn1
[SPE2-bgp-vpn1] quit
[SPE2-bgp]ipv4-family vpn-instance vpn2
[SPE2-bgp-vpn2] quit
[SPE2-bgp] quit
# Configure SPE 2 to advertise to UPE 2 the routes permitted by a routing policy, that is, the routes
of CE 1.
[SPE2] ip ip-prefix hope index 10 permit
[SPE2] route-policy hope permit node 0
[SPE2-route-policy] if-match ip-prefix hope
[SPE2-route-policy] quit
[SPE2] bgp 100
[SPE2-bgp] ipv4-family vpnv4
[SPE2-bgp-af-vpnv4] peer 4.4.4.9 upe route-policy hope export

Configuring OSPF sham links

Network requirements
CE 1 and CE 2 belong to VPN 1 and are in the same OSPF area.
Forword VPN traffic between CE 1 and CE 2 through the MPLS backbone instead of any route in the
OSPF area.
Figure 76 Network diagram
Device
CE 1
PE 1
Interface IP address
Vlan-int1 100.1.1.1/24
Vlan-int2 20.1.1.1/24
Loop0 1.1.1.9/32
Loop1 3.3.3.3/32
10.2.1.1 24
Device Interface
CE 2 Vlan-int1
Vlan-int2
PE 2 Loop0
Loop1
321
IP address
120.1.1.1/24
30.1.1.2/24
2.2.2.9/32
5.5.5.5/32