Configuring Route Attributes For A Vpn Instance - HP 10500 Series Configuration Manual

Step
1. Enter system view.
2. Enter interface view.
3. Associate the current interface
with a VPN instance.
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:
Step
1. Enter system view.
2. Enter VPN instance view.
3. (Optional.) Enter IPv6 VPN
view.
4. Configure route targets for the
VPN instance.
5. (Optional.) Configure the
maximum number of routes for
the VPN instance.
6. (Optional.) Apply an import
routing policy.
Command
system-view
interface interface-type
interface-number
ip binding vpn-instance
vpn-instance-name
Command
system-view
ip vpn-instance vpn-instance-name
ipv6-family
vpn-target vpn-target&<1-8>
[ both | export-extcommunity |
import-extcommunity ]
routing-table limit number
{ warn-threshold | simply-alert }
import route-policy route-policy
29
Remarks
N/A
N/A
By default, no VPN instance is
associated with an interface.
Remarks
N/A
N/A
N/A
By default, no route target is
configured for the VPN instance.
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.
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.