417
instance.
configured for a VPN instance.
5. (Optional.) Configure a VPN
ID for the VPN instance.
vpn-id
vpn-id
configured for a 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:
1. Enter system view.
N/A
2. Enter interface view.
interface
interface-type
interface-number
N/A
3. Associate
with the interface.
ip binding vpn-instance
vpn-instance-name
By default,
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
command.
Configuring route related attributes for a VPN instance
1. Enter system view.
system-view
N/A
2. Enter
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
Co
instance view apply to both IPv4
VPN and IPv6 VPN.
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
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.
To Next Page
Loading...
Need help?
General