R21xx-HP FlexFabric 11900 MPLS Configuration Guide
29
Ste
p
Command
Remarks
1. Enter system view.
system-view N/A
2. Enter interface view.
interface interface-type
interface-number
N/A
3. Associate the current interface
with a VPN instance.
ip binding vpn-instance
vpn-instance-name
By default, no VPN instance is
associated with an interface.
NOTE:
The ip binding vpn-instance command deletes the IPv6 address of the current interface. You must
reconfigure an IPv6 address for the interface after configuring the command.
Configuring route attributes for a VPN instance
The MCE controls 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 list 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 target attributes for advertised routes
according to the export-extcommunity in the route target.
To configure route 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. (Optional.) Enter IPv6 VPN
view.
ipv6-family N/A
4. Configure route targets for the
VPN instance.
vpn-target vpn-target&<1-8>
[ both | export-extcommunity |
import-extcommunity ]
By default, no route target is
configured for the VPN instance.
5. (Optional.) Configure the
maximum number of routes for
the VPN instance.
routing-table limit number
{ warn-threshold | simply-alert }
By default, the maximum route
number is not configured.
Setting the maximum number of
routes for a VPN instance is for
preventing too many routes from
being redistributed into the PE.
6. (Optional.) Apply an import
routing policy.
import route-policy route-policy
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.










