Advertising Routes Destined for the End Address of the Sham Link

The route destined for the end address of the sham link cannot be advertised to the remote PE through the OSPF process of the VPN. The end address of the sham link is advertised to the remote PE by BGP as a VPNv4 address.

Context

Perform the following steps on the PEs of the two ends of the sham link.

Procedure

Access the system view.
```
system-view
```
Access the BGP view.
```
bgp { as-number-plain | as-number-dot }
```
Access the BGP-VPN instance IPv4 address family view.
```
ipv4-family vpn-instance vpn-instance-name
```
Import the direct route.
```
import-route direct
```
The route of the end address is imported into BGP.

BGP advertises the end address of the sham link as the VPN-IPv4 address.

The route of one end address of the sham link cannot be advertised to the remote PE through the OSPF process of the private network.

If the routes, however, are advertised to the remote PE through the OSPF process of the private network, the remote PE has two routes destined for the end address of the sham link. One route is learnt through the OSPF process of the private network, and the other route is learnt through MP-BGP. In this case, the remote PE incorrectly selects the OSPF route, because the OSPF route has a higher priority than the BGP route. As a result, the sham link cannot be successfully established.