Configuring Nested Vpn - HP HPE FlexNetwork MSR Router Series Configuration Manual

Step
7. Enable MPLS on the
interface.
8. Enable MPLS LDP on the
interface.
9. Return to system view.
10. Enter interface view of the
interface connected to the
remote ASBR.
11. Enable MPLS on the
interface.
12. Return to system view.
13. Enter BGP view.
14. Configure the PE in the same
AS as an IBGP peer.
15. Configure the ASBR in
another AS as an EBGP
peer.
16. Create the BGP IPv4 unicast
address family and enter its
view.
17. Enable exchange of IPv4
unicast routes with the PE in
the same AS and the ASBR
in another AS.
18. Enable exchange of labeled
IPv4 routes with the PE in the
same AS and the ASBR in
another AS.
19. Configure the ASBR to set
itself as the next hop of
routes advertised to the PE
in the local AS.
20. (Optional.) Apply a routing
policy to routes incoming
from or outgoing to a peer or
peer group.

Configuring nested VPN

For a network with many VPNs, nested VPN is a good solution to implement layered management of
VPNs and to conceal the deployment of internal VPNs.
To build a nested VPN network, perform the following configurations:
•
Configurations between customer PE and customer CE—Configure VPN instances on the
customer PE and configure route exchange between customer PE and customer CE.
•
Configurations between customer PE and provider CE—Configure BGP VPNv4 route
exchange between them. To make sure the provider CE can receive all VPNv4 routes,
configure the undo policy vpn-target command on the provider CE to not filter VPNv4 routes
by RTs.
Command
mpls enable
mpls ldp enable
quit
interface interface-type
interface-number
mpls enable
quit
bgp as-number
peer { group-name | ip-address
[ mask-length ] } as-number
as-number
peer { group-name | ip-address
[ mask-length ] } as-number
as-number
address-family ipv4 [ unicast ]
peer { group-name | ip-address
[ mask-length ] } enable
peer { group-name | ip-address
[ mask-length ] }
label-route-capability
peer { group-name | ip-address
[ mask-length ] } next-hop-local
peer { group-name | ip-address
[ mask-length ] } route-policy
route-policy-name { export |
import }
224
Remarks
By default, MPLS is disabled on
the interface.
By default, MPLS LDP is disabled
on the interface.
N/A
N/A
By default, MPLS is disabled on
the interface.
N/A
N/A
By default, no BGP peer is
created.
By default, no BGP peer is
created.
By default, the BGP IPv4 unicast
address family is not created.
By default, BGP does not
exchange IPv4 unicast routes with
any peer.
By default, BGP cannot advertise
labeled routes to any IPv4 peer or
peer group.
By default, BGP does not use its
address as the next hop of routes
advertised to an IBGP peer or
peer group.
By default, no routing policy is
applied.