beautypg.com

Configuring ospf between pe and ce – H3C Technologies H3C SecPath F1000-E User Manual

Page 75

background image

12

Follow these steps to configure RIP between PE and CE:

To do…

Use the command…

Remarks

Enter system view

system-view

Create a RIP instance between PE

and CE and enter RIP view

rip [ process-id ] vpn-instance

vpn-instance-name

Required

NOTE:

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, see

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…

Use the command…

Remarks

Enter system view

system-view

Create an OSPF instance between
PE and CE and enter the OSPF

view

ospf [ process-id | router-id
router-id | vpn-instance

vpn-instance-name ]

Required

Configure the OSPF domain ID

domain-id domain-id
[ secondary ]

Optional
0 by default

Configure the type codes of OSPF
extended community attributes

ext-community-type
{ domain-id type-code1 |
router-id
type-code2 |
route-type
type-code3 }

Optional
The defaults are as follows:
0x0005 for Domain ID,
0x0107 for Router ID, and
0x0306 for Route Type.
Configure this command on a PE.

NOTE:

Perform the configurations on PEs. Only conventional OSPF is required on CEs.

After a VPN instance is deleted, all related OSPF processes are deleted at the same time.

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 for routes to be correctly

advertised, while OSPF processes on PEs in different VPNs can be configured with domain IDs as

desired.