349
To associate a Layer 3 aggregate interface with a VPN instance, you must associate all the member ports
of the aggregate interface with the VPN instance.
Executing the
ip binding vpn-instance
command on an interface deletes the IPv6 address of that
interface. You must reconfigure the IPv6 address of the interface after executing the command.
To associate a VPN instance with an interface:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter interface view.
interface
interface-type
interface-number
N/A
3.
Associate a VPN instance
with the interface.
ip binding vpn-instance
vpn-instance-name
By default, no VPN instance is
associated with the interface.
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 route
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 route target.
•
The VPN instance determines how to change the route targets attributes for routes to be advertised
according to the
export-extcommunity
in the route target.
To configure route related attributes for a VPN instance:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter VPN instance view.
ip vpn-instance
vpn-instance-name
N/A
3.
Enter IPv6 VPN view.
ipv6-family
Optional.
4.
Configure route targets.
vpn-target
vpn-target
&<1-8>
[
both
|
export-extcommunity
|
import-extcommunity
]
A single
vpn-target
command can
configure up to eight route targets.
You can configure up to 64 route
targets for a VPN instance.
5.
Set the maximum number of
routes supported.
routing-table
limit
number
{
warn-threshold
|
simply-alert
}
Optional.
Setting the maximum number of
routes for a VPN instance to
support is for preventing too many
routes from being redistributed into
the PE.
