HP MSR2000 Configuration Manual page 217

Step
2. Create a RIP process for a VPN
instance and enter RIP view.
3. Enable RIP on the interface
attached
network.
4. Redistribute remote site routes
advertised by the PE into RIP.
5. (Optional.)
default cost value for the
redistributed routes.
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. For more information
about OSPF, see Layer 3—IP Routing Configuration Guide.
To configure OSPF between an MCE and a VPN site:
Step
1. Enter system view.
2. Create an OSPF process for a
VPN instance and enter OSPF
view.
3. (Optional.)
OSPF domain ID.
Command
rip [ process-id ] vpn-instance
vpn-instance-name
to the specified
network network-address
import-route protocol [ process-id ]
[ allow-ibgp ] [ allow-direct | cost
cost | route-policy
route-policy-name | tag tag ] *
Configure the
default cost value
Command
system-view
ospf [ process-id | router-id
router-id | vpn-instance
vpn-instance-name ] *
Configure the
domain-id domain-id [ secondary ]
208
Remarks
Perform this configuration on the
MCE. On a VPN site, create a
common RIP process.
By default, RIP is disabled on an
interface.
By default, no route is redistributed
into RIP.
The default cost is 0.
Remarks
N/A
Perform this configuration on the
MCE. On a VPN site, create a
common OSPF process.
An OSPF process bound to a VPN
instance does not use the public
network router ID configured in
system view. Therefore, configure
a router ID for the OSPF process.
An OSPF process can belong to
only one VPN instance, but one
VPN instance can use multiple
OSPF processes to advertise VPN
routes.
The default domain ID is 0.
Perform this configuration on the
MCE.
All OSPF processes of the same
VPN must be configured with the
same OSPF domain ID to ensure
correct route advertisement.