Table of Contents
Advertisement
Step
4.
(Optional.) Configure a
description for the VPN
instance.
5.
(Optional.) Configure a VPN
ID for the VPN instance.
Associating a VPN instance with an interface
After creating and configuring a VPN instance, associate the VPN instance with the MCE's interface
connected to the site and the interface connected to the PE.
To associate a VPN instance with an interface:
Step
1.
Enter system view.
2.
Enter interface view.
3.
Associate a VPN instance
with the interface.
Configuring route related attributes for a VPN instance
Step
1.
Enter system view.
2.
Enter VPN instance
view or IPv4 VPN view.
3.
Configure route targets.
4.
Set the maximum
number of active routes
allowed.
Command
description text
vpn-id vpn-id
Command
system-view
interface interface-type
interface-number
ip binding vpn-instance
vpn-instance-name
Command
system-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
vpn-target vpn-target&<1-8> [ both |
export-extcommunity |
import-extcommunity ]
routing-table limit number
{ warn-threshold | simply-alert }
5
Remarks
By default, no description is
configured for a VPN instance.
By default, no VPN ID is
configured for a VPN instance.
Remarks
N/A
N/A
By default, an interface is not
associated with a VPN instance.
The ip binding vpn-instance
command deletes the IP address
of the current interface. You must
re-configure an IP address for the
interface after configuring the
command.
Remarks
N/A
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.
By default, no route targets are
configured.
By default, the maximum number
of active routes in the 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.
Hide quick links:
Advertisement
Table of Contents
