HP 6125XLG R2306-HP 6125XLG Blade Switch MCE Configuration Guide - Page 30

Configuring route attributes for a VPN instance

Get HP 6125XLG PDF manuals and user guides View all HP 6125XLG manuals
Add to My Manuals
Save this manual to your list of manuals

Page 30 highlights

Step 1. Enter system view. Command system-view 2. Enter interface view. interface interface-type interface-number 3. Associate the current interface ip binding vpn-instance with a VPN instance. vpn-instance-name Remarks N/A N/A 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: 1. 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. 2. The VPN instance determines which routes it can accept and redistribute according to the import-extcommunity in the route target. 3. 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 attributes for a VPN instance: Step 1. Enter system view. Command system-view Remarks N/A 2. Enter VPN instance view. 3. (Optional.) Enter IPv6 VPN view. ip vpn-instance vpn-instance-name N/A ipv6-family N/A 4. Configure route targets for the vpn-target vpn-target& VPN instance. [ 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 routing-table limit number the VPN instance. { 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. 27

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
27
Step
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:
1.
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.
2.
The VPN instance determines which routes it can accept and redistribute according to the
import-extcommunity
in the route target.
3.
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 attributes for a VPN instance:
Step
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.