418
The specified routing policy must
have been created.
For information about routing
policies, see Layer 3—IP Routing
Configuration Guide.
6. Apply an export routing
policy.
export route-policy
route-policy
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.
7. Apply a tunnel policy to
the VPN instance.
tnl-policy
tunnel-policy-name
By default, only one tunnel is
selected (no load balancing) in
this order: LSP tunnel, and
CRLSP tunnel.
The specified tunnel policy must
have been created.
For information about tunnel
policies, see "Configuring tunnel
policies."
Configuring routing on an MCE
MCE implements service isolation through route isolation. MCE routing configuration includes the
following:
• MCE-VPN site routing configuration.
• MCE-PE routing configuration.
On the PE, do the following:
• Disable routing loop detection to avoid route loss during route calculation.
• Disable route redistribution between routing protocols to save system resources.
Before you configure routing on an MCE, configure VPN instances, and bind the VPN instances to
the interfaces connected to the VPN sites and the PE.
Configuring routing between an MCE and a VPN site
You can configure static routing, RIP, OSPF, IS-IS, EBGP, or IBGP between an MCE and a VPN site.
Configuring static routing between an MCE and a VPN site
An MCE can reach a VPN site through a static route. Static routing on a traditional CE is globally
effective and does not support address overlapping among VPNs. An MCE supports binding a static
route to a VPN instance, so that the static routes of different VPN instances can be isolated from
each other.
To configure a static route to a VPN site:
1. Enter system view.
N/A
To Next Page
Loading...
Need help?
General