H3C SR8800 10G Mpls Configuration Manual page 261

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 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:
Step
1. Enter system view.
2. Create an OSPF process for a
VPN instance and enter the
OSPF view.
3. Configure the OSPF domain
ID.
Configure the type codes of
4.
OSPF extended community
attributes.
5. Create an OSPF area and
enter area view.
Enable OSPF on the interface
6.
attached to the specified
network in the area.
NOTE:
Deleting a VPN instance also deletes all the associated OSPF processes.
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.
The domain ID of an OSPF process is included in the routes generated by the process. When an OSPF
route is redistributed into BGP, the OSPF domain ID is included in the BGP VPN route and delivered as
a BGP extended community attribute.
Command
system-view
ospf [ process-id | router-id
router-id | vpn-instance
vpn-instance-name ] *
domain-id domain-id [ secondary ]
ext-community-type { domain-id
type-code1 | router-id type-code2
| route-type type-code3 }
area area-id
network ip-address wildcard-mask
250
Remarks
N/A
Perform the configurations on PEs.
On CEs, create a normal OSPF
process.
Optional.
0 by default.
Optional.
The defaults are as follows:
0x0005 for Domain ID,
0x0107 for Router ID, and
0x0306 for Route Type.
Perform this configuration on PEs.
By default, no OSPF area is
created.
By default, an interface neither
belongs to any area nor runs
OSPF.