Configuring Nested Vpn - HP 10500 SERIES Configuration Manual

Step
1. Enter system view.
2. Enter BGP view.
3. Configure each PE in the
same AS as the IBGP peer.
4. Enable the ASBR PE to
exchange labeled IPv4 routes
with the PEs in the same AS.
5. Configure the ASBR PE to
change the next hop to itself
when advertising routes to PEs
in the same AS.
6. Configure the remote ASBR PE
as the EBGP peer.
7. Enable the ASBR PE to
exchange labeled IPv4 routes
with the peer ASBR PE.
8. Apply a routing policy to the
routes advertised by peer
ASBR PE.
Configuring the routing policy
After you configure and apply a routing policy on an ASBR PE, it does the following:
Assigns MPLS labels to the routes received from the PEs in the same AS before advertising them to
•
the peer ASBR PE.
• Assigns new MPLS labels to the labeled IPv4 routes to be advertised to the PEs in the same AS.
Which IPv4 routes are to be assigned with MPLS labels depends on the routing policy. Only routes that
satisfy the criteria are assigned with labels. All other routes are still common IPv4 routes.
For information about routing policy configuration, see Layer 3—IP Routing Configuration Guide.
To configure a routing policy for inter-AS option C on an ASBR PE:
Step
1. Enter system view.
2. Enter routing policy view.
3. Configure the device to match
IPv4 routes with labels.
4. Configure the device to assign
labels to IPv4 routes.

Configuring nested VPN

For a network with many VPNs, if you want to implement layered management of VPNs and to conceal
the deployment of internal VPNs, nested VPN is a good solution. By using nested VPN, you can
Command
system-view
bgp as-number
peer { group-name | ip-address }
as-number as-number
peer { group-name | ip-address }
label-route-capability
peer { group-name | ip-address }
next-hop-local
peer { group-name | ip-address }
as-number as-number
peer { group-name | ip-address }
label-route-capability
peer { group-name | ip-address }
route-policy route-policy-name
export
Command
system-view
route-policy policy-name permit
node seq-number
if-match mpls-label
apply mpls-label
265
Remarks
N/A
N/A
N/A
By default, the device does not
advertise labeled routes to the IPv4
peer or peer group.
By default, a BGP speaker does not
use its address as the next hop
when advertising a route to its
IBGP peer or peer group.
N/A
By default, the device does not
advertise labeled routes to the IPv4
peer.
By default, no routing policy is
applied to a peer or peer group.
Remarks
N/A
N/A
N/A
By default, an IPv4 route does not
carry any label.