2-4
To do…
Use the command…
Remarks
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.
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.
Follow these steps to configure RIP between a MCE and a site:
To do…
Use the command…
Remarks
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.
Redistribute routes
from the remote site
advertised by the PE
import-route protocol
[
process-id
] [
allow-ibgp
]
[
cost cost
|
route-policy
route-policy-name
|
tag tag
] *
Required
By default, RIP does not redistribute
routes from other protocols.
After enabling RIP for a VPN instance, you need also to configure to use RIP for routing information
exchange.
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.
Follow these steps to configure OSPF between a MCE and a site:
