R3102-R3103-HP 6600/HSR6600 Routers MPLS Configuration Guide

289
Ste
p
Command Remarks
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:
Ste
p
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.
3. Enable RIP on the interface
attached to the specified
network.
network network-address
By default, RIP is disabled on an
interface.
4. Redistribute remote site routes
advertised by the PE.
import-route protocol [ process-id ]
[ allow-ibgp ] [ cost cost |
route-policy route-policy-name |
tag tag ] *
By default, no route is redistributed
into RIP.
5. Configure the default cost
value for the redistributed
routes.
default cost value
Optional.
0 by default.
For more information about RIP, see Layer 3—IP Routing Configuration Guide.
Configuring OSPF between an MCE and a VPN site
An OSPF process belongs to the public network or a single VPN instance. If you create an OSPF process
without binding it to a VPN instance, the process belongs to the public network.
Binding OSPF processes to VPN instances can isolate routes of different VPNs. An OSPF process can
belong to only one VPN instance, but one VPN instance can use multiple OSPF processes to advertise the
VPN routes.