3Com S7906E Configuration Manual page 1543

Perform this configuration on the PEs. The configuration method on the CEs is the same for
configuring ordinary static routes.
For information about static route, refer to Static Routing Configuration in the IP Routing Volume.
Configuring RIP between PE and CE
A RIP process belongs to only one VPN instance. If you run a RIP process without binding it to a VPN
instance, the process is considered a public network process.
Follow these steps to configure RIP between PE and CE:
To do...
Enter system view
Create a RIP instance between
PE and CE and enter RIP view
:
Perform this configuration on the PEs. Only conventional RIP is required on CEs.
After configuring a RIP instance, you must start RIP by using the same method for starting a
common RIP process.
For description and detailed configuration about RIP, refer to RIP Configuration in the IP Routing
Volume.
Configuring OSPF between PE and CE
An OSPF process that is bound to a VPN instance does not use the public network router ID configured
in system view. Therefore, you need to specify the router ID when starting a process or to configure the
IP address for at least one interface of the VPN instance.
An OSPF process belongs to only one VPN instance. If you run an OSPF process without binding it to a
VPN instance, the process is considered a public network process.
Follow these steps to configure OSPF between PE and CE:
To do...
Enter system view
Create an OSPF instance
between PE and CE and enter
the OSPF view
Configure the OSPF domain ID
Use the command...
system-view
rip [ process-id ] vpn-instance
vpn-instance-name
Use the command...
system-view
ospf [ process-id | router-id
router-id | vpn-instance
vpn-instance-name ]
domain-id domain-id
[ secondary ]
1-28
Remarks
—
Required
Remarks
—
Required
Optional
0 by default