Configuring HoVPN

In a HoVPN networking scenario, perform basic MPLS L3VPN settings on UPE and SPE. In addition, configure the following settings on the SPE:

As a best practice, do not configure the peer default-route-advertise vpn-instance and peer upe route-policy commands at the same time.

To configure SPE for HoVPN:

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Enter BGP instance view.

bgp as-number [ instance instance-name ] [ multi-session-thread ]

N/A

3. Specify a BGP peer or peer group.

peer { group-name | ipv4-address [ mask-length ] } as-number as-number

By default, no BGP peers exist.

4. Enter BGP-VPN VPNv4 address family view.

address-family vpnv4

N/A

5. Enable BGP VPNv4 route exchange with the peer or peer group.

peer { group-name | ipv4-address [ mask-length ] } enable

By default, BGP does not exchange VPNv4 routes with any peer.

6. Specify the BGP peer or peer group as a UPE.

peer { group-name | ipv4-address [ mask-length ] } upe

By default, no peer is a UPE.

7. Advertise routes to the UPE.

  • Advertise a default VPN route to the UPE:peer { group-name | ipv4-address [ mask-length ] } default-route-advertise vpn-instance vpn-instance-name

  • Advertise routes permitted by a routing policy to the UPE:peer { group-name | ipv4-address [ mask-length ] } upe route-policy route-policy-name export

By default, no route is advertised to the UPE.

Do not configure both commands.

The peer default-route-advertise vpn-instance command advertises a default route using the local address as the next hop to the UPE, regardless of whether the default route exists in the local routing table. However, if the specified peer is not a UPE, the command does not advertise a default route.

8. Return to BGP instance view.

quit

N/A

9. Create a BGP-VPN instance, and enter BGP-VPN instance view.

ip vpn-instance vpn-instance-name

By default, no BGP-VPN instances exist.