H3C Technologies H3C S6800 Series Switches - Manual (Page 450)

437
Step Command Remarks
3. (Optional.) Configure the
OSPF domain ID.
domain-id domain-id [ secondary ]
The default domain ID is 0.
Perform this configuration on the
MCE.
All OSPF processes of the same
VPN must be configured with the
same OSPF domain ID to ensure
correct route advertisement.
4. (Optional.) Configure the type
codes of OSPF extended
community attributes.
ext-community-type { domain-id
type-code1 | router-id type-code2
| route-type type-code3 }
The defaults are as follows:
• 0x0005 for Domain ID.
• 0x0107 for Router ID.
• 0x0306 for Route Type.
5. (Optional.) Configure the
external route tag for
imported VPN routes.
route-tag tag-value
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.
6. Redistribute remote site routes
advertised by the PE into
OSPF.
import-route protocol [ process-id
| all-processes | allow-ibgp ] [ cost
cost | nssa-only | route-policy
route-policy-name | tag tag | type
type ] *
By default, no routes are
redistributed into OSPF.
7. (Optional.) Configure OSPF
to redistribute the default
route.
default-route-advertise summary
cost cost
By default, OSPF does not
redistribute the default route.
This command redistributes the
default route in a Type-3 LSA. The
MCE advertises the default route to
the site.
8. Create an OSPF area and
enter OSPF area view.
area area-id
By default, no OSPF area is
created.
9. Enable OSPF on the interface
attached to the specified
network in the area.
network ip-address wildcard-mask
By default, an interface neither
belongs to any area nor runs
OSPF.
Configuring IS-IS between an MCE and a VPN site
An IS-IS process belongs to the public network or a single VPN instance. If you create an IS-IS process
without binding it to a VPN instance, the process belongs to the public network.
Binding IS-IS processes to VPN instances can isolate routes of different VPNs. For more information about
IS-IS, see Layer 3—IP Routing Configuration Guide.