To do...
Associate the current VPN instance
with one or more VPN targets
Configure the maximum number of
routes for the VPN instance
Apply an import routing policy to
the current VPN instance
Apply an export routing policy to
the current VPN instance
NOTE:
Only when BGP runs between the MCE and PE can the VPN target attribute be advertised to the PE
•
along with the routing information. In other cases, configuring this attribute makes no sense.
•
You can configure route related attributes for IPv4 VPNs in both VPN instance view and IPv4 VPN view.
Those configured in IPv4 VPN view take precedence.
A single vpn-target command can configure up to eight VPN targets. You can configure up to 64 VPN
•
targets for a VPN instance.
You can define the maximum number of routes for a VPN instance to support, preventing too many
•
routes from being redistributed into the PE.
Before associating a routing policy with a VPN instance, you must first create the routing policy.
•
Otherwise, the default routing policy is used.
Configuring routing on an MCE
MCE implements service isolation through route isolation. MCE routing configuration includes:
•
MCE-VPN site routing configuration
MCE-PE routing configuration
•
On the PE in an MCE network environment, disable routing loop detection to avoid route loss during
route calculation and disable route redistribution between routing protocols to save system resources.
Configuration prerequisites
Before you configure routing on an MCE, complete the following tasks:
On the MCE, configure VPN instances, and bind the VPN instances with the interfaces connected
•
to the VPN sites and those connected to the PE.
Configure the link layer and network layer protocols on related interfaces to ensure IP connectivity.
•
Use the command...
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
400
Remarks
Required
Optional
Not configured by default
Optional
By default, all routes permitted by
the import target attribute can be
redistributed into the VPN instance.
Optional
By default, all VPN instance routes
permitted by the export target
attribute can be redistributed.