Operation Manual – MCE
H3C S3610&S5510 Series Ethernet Switches
Chapter 2 MCE Configuration
2-5
2.2.2 Configuring to Use Static Routes between a MCE and a Site
Table 2-7
Configure to use static routes between a MCE and a site
Operation
Command
Description
Enter system view
system-view
—
Define a static
route for a VPN
instance
ip route-static
vpn-instance
s-vpn-instance-name
&<1-5>
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
]
Required
This operation is
performed on the
MCE device. The
corresponding
configuration on the
site is the same as
configuring a normal
static route.
2.2.3 Configuring to Use RIP between a MCE and a Site
A RIP process can be bound to only one VPN instance. RIP processes not bound to
any VPN instances belong to the public network.
Table 2-8
Configure to use RIP between a MCE and a site
Operation
Command
Description
Enter system view
system-view
—
Enable RIP for a
VPN instance
(This operation
also leads you to
RIP view)
rip
[
process-id
]
vpn-instance
vpn-instance-name
Required
This operation is performed on the
MCE device. As for the corresponding
configuration on the site, you can just
enable RIP as usual.
Note:
After enabling RIP for a VPN instance, you need also to configure to use RIP for routing
information exchange, which is described in the
IPv4 Routing
module of this manual.
2.2.4 Configuring to Use OSPF between a MCE and a Site
An OSPF process can be bound to only one VPN instance. OSPF processes not bound
to any VPN instances belong to the public network.
