201
Step Command Remarks
SNMP context for the VPN
instance.
context-name
configured.
464BAssociating a VPN instance with an interface
After creating and configuring a VPN instance, associate the VPN instance with the interface
connected to the CE.
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, an interface is not
associated with a VPN instance
and belongs to the public network.
The
ip binding vpn-instance
command deletes the IP address
of the current interface. You must
reconfigure an IP address for the
interface after configuring the
command.
465BConfiguring route related attributes for a VPN instance
Step Command Remarks
1. Enter system view.
system-view
N/A
2. Enter VPN instance
view or IPv4 VPN view
• Enter VPN instance view:
ip vpn-instance
vpn-instance-name
• Enter IPv4 VPN view:
a. ip vpn-instance
vpn-instance-name
b. address-family ipv4
Configurations made in VPN
instance view apply to both IPv4
VPN and IPv6 VPN.
IPv4 VPN prefers the
configurations in IPv4 VPN view
over the configurations in VPN
instance view.
3. Configure route targets.
vpn-target
vpn-target&<1-8> [
both
|
export-extcommunity
|
import-extcommunity
]
By default, no route targets are
configured.
4. Set the maximum
number of active routes.
routing-table
limit
number
{ warn-threshold |
simply-alert
}
By default, the number of active
routes in a VPN instance is not
limited.
Setting the maximum number of
active routes for a VPN instance
can prevent the PE from learning
too many routes.
5. Apply an import routing
policy.
import route-policy
route-policy
By default, all routes matching the
import target attribute are
accepted.
The specified routing policy must
have been created.
For information about routing
policies, see Layer 3—IP Routing
Configuration Guide.
To Next Page
Loading...
Need help?
General