R3102-R3103-HP 6600/HSR6600 Routers MPLS Configuration Guide

268
Ste
p
Command Remarks
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
No VPN instance is associated
with an interface by default.
NOTE:
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.
Configuring route related attributes for a VPN instance
The device processes VPN route advertisement as follows:
• When a VPN route learned from a site 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 site.
• 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:
Ste
p
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 IPv4 VPN view.
ipv4-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 allowed by the VPN
instance.
routing-table limit number
{ warn-threshold | simply-alert }
Optional.
By default, a VPN instance
supports 100000 routes at most.
Setting the maximum number of
routes for a VPN instance is for
preventing too many routes from
being redistributed into the PE.
6. Apply an import routing
policy.
import route-policy route-policy
Optional.
By default, all routes matching the
import target attribute are
accepted.
Make sure the routing policy
already exists. Otherwise, the
device does not filter received
routes.