R3303-HP HSR6800 Routers MPLS Configuration Guide

287
Ste
p
Command Remarks
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
meet the criteria are assigned with labels. All the other routes are still common IPv4 routes.
To configure a routing policy for inter-AS option C on an ASBR PE:
Ste
p
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.
For more information about routing policy configuration, see Layer 3—IP Routing Configuration Guide.
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.
Before you configure nested VPN, configure basic MPLS L3VPN settings. For configuration information,
see "Configuring basic MPLS L3VPN."
W
hen you configure nested VPN, follow these guidelines:
• The address ranges for sub-VPNs of a VPN cannot overlap.
• Do not give nested VPN peers addresses that public network peers use.
• Before specifying a nested VPN peer or peer group, configure the corresponding CE peer or peer
group in BGP VPN instance view.
• Nested VPN does not support multi-hop EBGP. A service provider PE and its peer must use the
addresses of the directly connected interfaces to establish neighbor relationship.