9
Step Command
Remarks
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 advertise 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. H3C
recommends configuring the same
route tag for the same VPN on the
MCEs.
6.
Redistribute remote site routes
advertised by the PE.
import-route
protocol
[
process-id
|
allow-ibgp
] [
cost
cost
|
type
type
|
tag
tag
|
route-policy
route-policy-name
] *
By default, OSPF does not
redistribute routes from any other
routing protocol.
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 does not
run 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.
To configure IS-IS between an MCE and a VPN site:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create an IS-IS process for a
VPN instance and enter IS-IS
view.
isis
[
process-id
]
vpn-instance
vpn-instance-name
Perform this configuration on the
MCE. On the VPN site, configure a
normal IS-IS process.
3.
Configure a network entity
title.
network-entity
net
By default, no NET is configured.