333[SPE2-ospf-1-area-0.0.0.0] network 180.1.1.0 0.0.0.255[SPE2-ospf-1-area-0.0.0.0] quit[SPE2-ospf-1] quit# Configure VPN instances vpn1 and vpn2.[SPE2] ip vpn-instance vpn1[SPE2-vpn-instance-vpn1] route-distinguisher 600:1[SPE2-vpn-instance-vpn1 ] vpn-target 100:1 both[SPE2-vpn-instance-vpn1] quit[SPE2] ip vpn-instance vpn2[SPE2-vpn-instance-vpn2] route-distinguisher 800:1[SPE2-vpn-instance-vpn2] vpn-target 100:2 both[SPE2-vpn-instance-vpn2] quit# Configure SPE 2 to establish MP-IBGP peer relationship with UPE 2 and to inject VPN routes, andspecify UPE 2.[SPE2] bgp 100[SPE2-bgp] peer 4.4.4.9 as-number 100[SPE2-bgp] peer 4.4.4.9 connect-interface loopback 0[SPE2-bgp] peer 4.4.4.9 next-hop-local[SPE2-bgp] peer 2.2.2.9 as-number 100[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 routesof CE 1.[SPE2] ip ip-prefix hope index 10 permit 10.2.1.1 24[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 exportConfiguring OSPF sham linksNetwork requirementsAs shown in Figure 85:• CE 1 and CE 2 belong to VPN 1 and are connected to PE 1 and PE 2, respectively.• CE 1 and CE 2 are in the same OSPF area.
