282
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.
Before you configure routing on an MCE, complete the following tasks:
•
Configure VPN instances, and bind the VPN instances with the interfaces connected to the
VPN sites and the PE.
•
Configure the link layer and network layer protocols on related interfaces to ensure IP
connectivity.
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 thus does not support address overlapping among VPNs. An MCE supports binding a
static route with 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:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Configure a static
route for a VPN
instance.
•
ip
route-static
dest-address
{
mask
|
mask-length
} {
gateway-address
|
interface-type interface-number
[
gateway-address
] |
vpn-instance
d-vpn-instance-name
gateway-address
}
[
preference
preference-value
] [
tag
tag-value
] [
description
description-text
]
•
ip route-static
vpn-instance
s-vpn-instance-name&
<1-6
>
dest-address
{
mask
|
mask-length
} {
gateway-address
[
public
] |
interface-type interface-number
[
gateway-address
] |
vpn-instance
d-vpn-instance-name gateway-address
}
[
preference
preference-value
] [
tag
tag-value
] [
description
description-text
]
Use either command
as needed.
Perform this
configuration on the
MCE. On a VPN site,
configure a normal
static route.
3.
Configure the default
precedence for static
routes.
ip route-static default-preference
default-preference-value
Optional.
60 by default.
Configuring RIP between an MCE and a VPN site
A RIP process belongs to the public network or a single VPN instance. If you create a RIP process
without binding it to a VPN instance, the process belongs to the public network. Binding RIP
processes to VPN instances can isolate routes of different VPNs.
To configure RIP between an MCE and a VPN site:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create a RIP process for a
VPN instance and enter RIP
view.
rip
[
process-id
]
vpn-instance
vpn-instance-name
Perform this configuration on the
MCE. On a VPN site, create a
normal RIP process.