215
To do…
Use the command…
Remarks
Configure a description for the
VPN instance
description
text
Optional
The description should contain the
VPN instance’s related
information, such as its relationship
with a certain VPN.
Associating a VPN instance with an interface
After creating and configuring a VPN instance, you need to associate the VPN instance with the interface
for connecting the CE. Any LDP-capable interface can be associated with a VPN instance. For
information about LDP-capable interfaces, see the chapter “Configuring basic MPLS.”
To associate a VPN instance with an interface:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Enter interface view
interface
interface-type
interface-number
—
Associate a VPN instance with the
interface
ip binding vpn-instance
vpn-instance-name
Required
No VPN instance is associated
with an interface by default.
NOTE:
The
ip binding vpn-instance
command clears the IP address of the interface on which it is configured. Be
sure to re-configure an IP address for the interface after configuring the command.
Configuring route related attributes for a VPN instance
The control process of VPN route advertisement is as follows:
•
When a VPN route learned from a CE gets redistributed into BGP, BGP associates it with a VPN
target extended community attribute list, which is usually the export target attribute of the VPN
instance associated with the CE.
•
The VPN instance determines which routes it can accept and redistribute according to the
import-extcommunity
in the VPN target.
•
The VPN instance determines how to change the VPN targets attributes for routes to be advertised
according to the
export-extcommunity
in the VPN target.
To configure route related attributes for a VPN instance:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Enter VPN instance view
ip vpn-instance
vpn-instance-name
—
Enter IPv4 VPN view
ipv4-family
Optional
Configure VPN targets
vpn-target
vpn-target
&<1-8>
[
both
|
export-extcommunity
|
import-extcommunity
]
Required
Set the maximum number of routes
allowed
routing-table
limit
number
{
warn-threshold
|
simply-alert
}
Optional