264
Step Command
Remarks
5.
Configure the ASBR PE to
change the next hop to itself
when advertising routes to PEs
in the same AS.
peer
{
group-name
|
ip-address
}
next-hop-local
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.
6.
Configure the remote ASBR PE
as the EBGP peer.
peer
{
group-name
|
ip-address
}
as-number
as-number
N/A
7.
Enable the ASBR PE to
exchange labeled IPv4 routes
with the peer ASBR PE.
peer
{
group-name
|
ip-address
}
label-route-capability
By default, the device does not
advertise labeled routes to the IPv4
peer.
8.
Apply a routing policy to the
routes advertised by peer
ASBR PE.
peer
{
group-name
|
ip-address
}
route-policy
route-policy-name
export
By default, no routing policy is
applied to a peer or peer group.
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 the 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 Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter routing policy view.
route-policy
policy-name
permit
node
seq-number
N/A
3.
Configure the device to match
IPv4 routes with labels.
if-match mpls-label
N/A
4.
Configure the device to assign
labels to IPv4 routes.
apply mpls-label
By default, an IPv4 route does not
carry any label.
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
implement layered management of internal VPNs easily with a low cost and simple management
operation.
Configure the basic MPLS L3VPN capability. For configuration information, see "
."
Configuration guidelines
•
The address ranges for sub-VPNs of a VPN cannot overlap.
