219
NOTE:
For information about static routing, see
Layer 3—IP Routing Configuration Guide.
Configuring RIP between PE and CE
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.
To configure RIP between PE and CE:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Create a RIP process for a VPN
instance and enter RIP view
rip
[
process-id
]
vpn-instance
vpn-instance-name
Required
Perform this configuration on PEs.
On CEs, create a normal RIP
process.
Enable RIP on the interface
attached to the specified network
network
network-address
Required
By default, RIP is disabled on an
interface.
NOTE:
For more information about RIP, see
Layer 3—IP Routing Configuration Guide.
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 must 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 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 PE and CE:
To do…
Use the command…
Remarks
Enter system view
system-view
—
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
] *
Required
Perform the configurations on PEs.
On CEs, create a normal OSPF
process.
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.
Perform this configuration on PEs.
