3Com S7902E, Configuration Manual

Page: 1554 / 2621

1-39
Follow these steps to configure a routing policy for inter-provider VPN option C on an ASBR PE:
To do… Use the command… Remarks
Enter system view system-view —
Enter routing policy view
route-policy policy-name
permit node seq-number
Required
Configure the device to match
IPv4 routes with labels
if-match mpls-label Required
Configure the device to assign
labels to IPv4 routes
apply mpls-label
Required
By default, an IPv4 route does
not carry any label.
For information about routing policy configuration, refer to Routing Policy Configuration in the IP
Routing Volume .
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.
Configuration Prerequisites
Before configuring nested VPN, configure the basic MPLS L3VPN capability. Refer to Configuring Basic
MPLS L3VPN .
Configuring Nested VPN
Follow these steps to configure nested VPN:
To do… Use the command… Remarks
Enter system view system-view —
Enter BGP view bgp as-number —
Enter BGP VPN instance view
ipv4-family vpn-instance
vpn-instance-name
—
Configure a CE peer or peer
group
peer { group-name |
peer-address } as-number
number
Required
Return to BGP view quit —
Enter BGP-VPNv4 subaddress
family view
ipv4-family vpnv4 —