Configuring Hovpn; Configuring An Ospf Sham Link - HP 10500 SERIES Configuration Manual

Configuring HoVPN

For hierarchical VPNs, you can adopt HoVPN to reduce the performance requirements for PEs.
Before you configure HoVPN, complete basic MPLS L3VPN settings on UPE and SPE.
Do not connect an SPE to a CE directly. If an SPE must be directly connected to a CE, the VPN instance
on the SPE and that on the UPE must be configured with different RDs.
To configure HoVPN:
Step
1. Enter system view.
2. Enter BGP view.
3. Enter BGP-VPNv4 subaddress
family view.
4. Enable the exchange of
BGP-VPNv4 routing
information with a peer or
peer group.
5. Specify the BGP peer or peer
group as a UPE.
6. Advertise routes to the UPE.

Configuring an OSPF sham link

The sham link is considered an OSPF intra-area route. It is used to make sure the VPN traffic is transmitted
over the backbone instead of the backdoor link between two CEs.
The source and destination addresses of the sham link must be loopback interface addresses with 32-bit
masks. Besides, the loopback interfaces must be bound to the VPN instances and be advertised through
BGP.
Before you configure an OSPF sham link, complete the following tasks:
Configure basic MPLS L3VPN (OSPF is used between PEs and CEs).
•
Command
system-view
bgp as-number
ipv4-family vpnv4
peer { group-name | ip-address }
enable
peer { group-name | ip-address }
upe
•
(Approach 1) Advertise a
default VPN route:
peer { group-name |
ip-address }
default-route-advertise
vpn-instance
vpn-instance-name
•
(Approach 2) Advertise routes
permitted by a routing policy:
peer { group-name |
ip-address } upe route-policy
route-policy-name export
267
Remarks
N/A
N/A
N/A
N/A
The default route of a VPN instance
can be advertised to only a BGP
peer or peer group that is UPE.
Use either approach. Do not
configure both the peer
default-route-advertise
vpn-instance command and the
peer upe route-policy command.
By default, BGP does not advertise
routes to a VPNv4 peer.
With the peer
default-route-advertise
vpn-instance command
configured, the SPE always
advertises a default route using the
local address as the next hop
address to the UPE, regardless of
whether the default route is present
in the local routing table or not.