
362
[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 connected to PE 1 and PE 2, respectively.
CE 1 and CE 2 are in the same OSPF area.
VPN traffic between CE 1 and CE 2 is required to be forwarded through the MPLS backbone, instead
of any route in the OSPF area.
Figure 97 Network diagram
Device Interface IP
address
Device Interface IP
address
CE 1
GE2/1/1
100.1.1.1/24
CE 2
GE2/1/1
120.1.1.1/24
S2/1/2 20.1.1.1/24
S2/1/2 30.1.1.2/24
PE 1
Loop0
1.1.1.9/32
PE 2
Loop0
2.2.2.9/32
Loop1
3.3.3.3/32
Loop1
5.5.5.5/32
GE2/1/1
100.1.1.2/24
GE2/1/1
120.1.1.2/24
S2/1/2 10.1.1.1/24
S2/1/1 10.1.1.2/24
Router
A
S2/1/1
30.1.1.1/24
S2/1/2
20.1.1.2/24
Configuration procedure
1.
Configure OSPF on the customer networks:
Configure conventional OSPF on CE 1, Router A, and CE 2 to advertise segment addresses of
the interfaces as shown in
After completing the configurations, CE 1 and CE 2 can learn the OSPF route to the Ethernet
interface of each other. Take CE 1 as an example:
<CE1> display ip routing-table
Routing Tables: Public
Destinations : 9 Routes : 9
Destination/Mask Proto Pre Cost NextHop Interface
20.1.1.0/24 Direct 0 0 20.1.1.1 S2/1/2
20.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0