HP 10500 Series Configuration Manual page 112

Configuring route related attributes for a VPN instance
VPN routes are controlled and advertised on a PE using the following process:
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 target attributes for routes to be advertised
according to the export-extcommunity in the route target.
To configure 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 routes
allowed.
5. Apply an import routing
policy.
6. Apply an export routing
policy.
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. ipv4-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
export route-policy route-policy
106
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.
Support for this command depends
on the device model.
By default, no route limit is
configured for the VPN instance.
This setting prevents a VPN
instance from learning too many
routes.
By default, all routes matching the
import target attribute are
accepted.
The specified routing policy must
have been created.
For information about routing
policies, see Layer 3—IP Routing
Configuration Guide.
By default, routes to be advertised
are not filtered.
The specified routing policy must
have been created.
For information about routing
policies, see Layer 3—IP Routing
Configuration Guide.