H3C S6800 Series Configuration Manual page 15

Step
1. Enter system view.
2. Create an OSPF process for a
VPN instance and enter OSPF
view.
3. (Optional.) Configure the
OSPF domain ID.
4. (Optional.) Configure the type
codes of OSPF extended
community attributes.
5. (Optional.) Configure the
external route tag for
imported VPN routes.
6. Redistribute remote site routes
advertised by the PE into
OSPF.
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 }
route-tag tag-value
import-route protocol [ process-id
| all-processes | allow-ibgp ]
[ allow-direct | cost cost |
route-policy route-policy-name |
tag tag | type type ] *
8
Remarks
N/A
Perform this configuration on the
MCE. On a VPN site, create a
common OSPF process.
An OSPF process bound to a VPN
instance does not use the public
network router ID configured in
system view. Therefore, configure
a router ID for the OSPF process.
An OSPF process can belong to
only one VPN instance, but one
VPN instance can use multiple
OSPF processes to advertise VPN
routes.
The default domain ID is 0.
Perform this configuration on the
MCE.
All OSPF processes of the same
VPN instance must be configured
with the same OSPF domain ID to
ensure correct route advertisement.
The defaults are as follows:
•
0x0005 for Domain ID.
•
0x0107 for Router ID.
•
0x0306 for Route Type.
By default, no route tag is
configured.
In some networks, a VPN might be
connected to multiple MCEs.
When one MCE advertises the
routes learned from BGP to the
VPN, the other MCEs might learn
the routes, resulting in routing
loops. To avoid such routing loops,
you can configure route tags for
VPN instances on an MCE. HP
recommends that you configure the
same route tag for the same VPN
on the MCEs.
By default, no routes are
redistributed into OSPF.