250
Step Command
Remarks
5.
Set the maximum number of
routes allowed.
routing-table
limit
number
{
warn-threshold
|
simply-alert
}
Optional.
Setting the maximum number of
routes for a VPN instance is for
preventing too many routes from
being redistributed into the PE.
6.
Apply an import routing
policy.
import route-policy
route-policy
Optional.
By default, all routes matching the
import target attribute are
accepted.
7.
Apply an export routing
policy.
export route-policy
route-policy
Optional.
By default, routes to be advertised
are not filtered.
NOTE:
•
Route related attributes configured in VPN instance view are applicable to both IPv4 VPNs and IPv6
VPNs.
•
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.
Configuring a tunneling policy for a VPN instance
When multiple tunnels exist in an MPLS L3VPN network, you can configure a tunneling policy to specify
the type and number of tunnels to be used by using the
tunnel select-seq
command or the
preferred-path
command.
With the
tunnel select-seq
command, you can specify the tunnel selection preference order and the
number of tunnels for load balancing.
With the
preferred-path
command, you can configure preferred tunnels that each correspond to a tunnel
interface.
After a tunneling policy is applied on a PE, the PE selects tunnels in this order:
•
The PE matches the peer PE address against the destination addresses of preferred tunnels, starting
from the tunnel with the smallest number. If no match is found, the local PE selects tunnels as
configured by the
tunnel select-seq
command or the default tunneling policy if the
tunnel select-seq
command is not configured. The default tunneling policy selects only one tunnel (no load balancing)
in this order: LSP tunnel, CR-LSP tunnel.
•
If a matching tunnel is found and the tunnel is available, the local PE stops matching other tunnels
and forwards the traffic to the specified tunnel interface.
•
If the matching tunnel is unavailable (for example, the tunnel is down or the tunnel's ACL does not
permit the traffic) and is not specified with the
disable-fallback
keyword, the local PE continues to
match other tunnels. If the tunnel is specified with the
disable-fallback
keyword, the local PE stops
matching and tunnel selection fails.
IMPORTANT:
Create a tunneling policy before applying it to a VPN instance. Otherwise, the default tunneling policy is
used. The default tunneling policy selects only one tunnel (no load balancing) in this order: LSP tunnel,
CR-LSP tunnel.
