3Com S7902E, Configuration Manual

Page: 1416 / 2621

2-5
To do… Use the command… Remarks
Enter system view system-view —
Enable OSPF for a
VPN instance (this
operation also leads
you to OSPF view) ospf [ process-id |
router-id router-id |
vpn-instance
vpn-instance-name
] *
Required
This operation is performed on the MCE
device. As for the corresponding
configuration on the site, you can just
enable OSPF as usual.
Enable
multi-VPN-instance CE
for the OSPF process
vpn-instance-capability
simple
Required
Disabled by default
Redistribute routes
from the remote site
advertised by the PE
import-route protocol
[ process-id | allow-ibgp ]
[ cost cost | type type | tag
tag | route-policy
route-policy-name ] *
Required
Not redistributed by default
Configure the OSPF
domain ID domain-id domain-id
[ secondary ]
Optional
By default, the OSPF domain ID is 0.
This operation is performed on the MCE
device. As for the corresponding
configuration on the site, you can just
enable OSPF as usual.
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.
z
Router IDs of the public network configured in system view do not applies to OSPF processes
bound to VPN instances. So you need to configure the Router ID after enabling OSPF for a VPN
instance.
z
To make sure routes can be advertised properly, you need to configure the same domain ID for all
the OSPF processes bound to a VPN.
z
After enabling OSPF for a VPN instance, you need also to configure to use OSPF for routing
information exchange, which is described in the IP Routing Volume .
Configuring to Use IS-IS between a MCE and a Site
An IS-IS process can be bound to only one VPN instance. IS-IS processes not bound to any VPN
instances belong to the public network.
Follow these steps to configure IS-IS between a MCE and a site: