224
Step Command
Remarks
7.
Enable MPLS on the
interface.
mpls enable
By default, MPLS is disabled on
the interface.
8.
Enable MPLS LDP on the
interface.
mpls ldp enable
By default, MPLS LDP is disabled
on the interface.
9.
Return to system view.
quit
N/A
10.
Enter interface view of the
interface connected to the
remote ASBR.
interface
interface-type
interface-number
N/A
11.
Enable MPLS on the
interface.
mpls enable
By default, MPLS is disabled on
the interface.
12.
Return to system view.
quit
N/A
13.
Enter BGP view.
bgp
as-number
N/A
14.
Configure the PE in the same
AS as an IBGP peer.
peer
{
group-name
|
ip-address
[
mask-length
] }
as-number
as-number
By default, no BGP peer is
created.
15.
Configure the ASBR in
another AS as an EBGP
peer.
peer
{
group-name
|
ip-address
[
mask-length
] }
as-number
as-number
By default, no BGP peer is
created.
16.
Create the BGP IPv4 unicast
address family and enter its
view.
address-family ipv4
[
unicast
]
By default, the BGP IPv4 unicast
address family is not created.
17.
Enable exchange of IPv4
unicast routes with the PE in
the same AS and the ASBR
in another AS.
peer
{
group-name
|
ip-address
[
mask-length
] }
enable
By default, BGP does not
exchange IPv4 unicast routes with
any peer.
18.
Enable exchange of labeled
IPv4 routes with the PE in the
same AS and the ASBR in
another AS.
peer
{
group-name
|
ip-address
[
mask-length
] }
label-route-capability
By default, BGP cannot advertise
labeled routes to any IPv4 peer or
peer group.
19.
Configure the ASBR to set
itself as the next hop of
routes advertised to the PE
in the local AS.
peer
{
group-name
|
ip-address
[
mask-length
] }
next-hop-local
By default, BGP does not use its
address as the next hop of routes
advertised to an IBGP peer or
peer group.
20.
(Optional.) Apply a routing
policy to routes incoming
from or outgoing to a peer or
peer group.
peer
{
group-name
|
ip-address
[
mask-length
] }
route-policy
route-policy-name
{
export
|
import
}
By default, no routing policy is
applied.
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.
Summary of Contents for HPE FlexNetwork MSR Router Series
Page 10: ...viii Index 540 ...