H3C Technologies H3C S12500-X Series Switches - Manual (Page 133)

122
Step 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
PE. On the CE, create a common
RIP process.
3. Enable RIP on the interface
attached to the specified
network.
network network-address
By default, RIP is disabled on an
interface.
Configuring OSPF between a PE and a 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 must specify a router ID when starting a process or configure an IP address
for at least one interface of the VPN instance.
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.
To configure OSPF between a PE and a CE:
Step Command Remarks
1. Enter system view. system-view N/A
2. Create an OSPF process for a
VPN instance and enter the
OSPF view.
ospf [ process-id | router-id
router-id | vpn-instance
vpn-instance-name ] *
Perform this configuration on the
PE. On the CE, create a common
OSPF process.
3. (Optional.) Configure an
OSPF domain ID.
domain-id domain-id [ secondary ]
The default domain ID is 0.
Perform this configuration on the
PE. On the CE, configure common
OSPF.
The domain ID is carried in the
routes of the OSPF process. When
redistributing routes from the OSPF
process, BGP adds the domain ID
as an extended community
attribute into BGP VPN routes.
An OSPF process can be
configured with only one domain
ID. Domain IDs of different OSPF
processes are independent of each
other.
All OSPF processes of a VPN must
be configured with the same
domain ID, while OSPF processes
on PEs in different VPNs can be
configured with domain IDs as
desired.