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:

Follow these restrictions and guidelines when you configure HoVPN:

To configure SPE for HoVPN:

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Enter BGP view.

bgp as-number

N/A

3. Specify a BGP peer or peer group.

peer { group-name | peer-address } as-number as-number

By default, no BGP peer is specified.

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 | ip-address } 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 | ip-address } 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 | ip-address } default-route-advertise vpn-instance vpn-instance-name

  • Advertise routes permitted by a routing policy to the UPE:peer { group-name | ip-address } upe route-policy route-policy-name export

Use either command.

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 is present 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 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 instance is created.