H3C Technologies H3C S6800 Series Switches - Manual (Page 448)

435
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:
Step Command Remarks
1. Enter system view. system-view N/A
2. Configure a static route
for a VPN instance.
ip route-static vpn-instance s-vpn-instance-name
dest-address { mask-length | mask } { interface-type
interface-number [ next-hop-address ] |
next-hop-address [ public ] [ track track-entry-number ]
| vpn-instance d-vpn-instance-name next-hop-address
[ track track-entry-number ] } [ permanent ]
[ preference preference-value ] [ tag tag-value ]
[ description description-text ]
By default, no static
route is configured.
Perform this
configuration on the
MCE. On the VPN
site, configure a
common static route.
3. (Optional.) Configure
the default preference
for static routes.
ip route-static default-preference
default-preference-value The default preference
is 60.
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