426
To do…
Use the command…
Remarks
Create an OSPFv3 process for a
VPN instance and enter OSPFv3
view
ospfv3
[
process-id
]
vpn-instance
vpn-instance-name
Required
Perform this configuration on the
IPv6 MCE. On a VPN site,
configure normal OSPFv3.
Set the router ID
router-id
router-id
Required
Redistribute remote site routes
advertised by the PE.
import-route
protocol
[
process-id
|
allow-ibgp
] [
cost
value
|
route-policy
route-policy-name
|
type
type
] *
Required
By default, no route of any other
routing protocol is redistributed
into OSPFv3.
Return to system view
quit
—
Enter interface view
interface
interface-type
interface-number
—
Enable OSPFv3 on the interface
ospfv3
process-id
area
area-id
[
instance
instance-id
]
Required
By default, OSPFv3 is disabled on
an interface.
NOTE:
•
Deleting a VPN instance will delete all related OSPFv3 processes at the same time.
•
For more information about OSPFv3, see
Layer 3—IP Routing Configuration Guide.
Configuring IPv6 IS-IS between IPv6 MCE and VPN site
An IPv6 IS-IS process belongs to the public network or a single IPv6 VPN instance. If you create an IPv6
IS-IS process without binding it to an IPv6 VPN instance, the process belongs to the public network.
By configuring IPv6 IS-IS process-to-IPv6 VPN instance bindings on an IPv6 MCE, you allow routes of
different IPv6 VPNs to be exchanged between the IPv6 MCE and the sites through different IPv6 IS-IS
processes, ensuring the separation and security of IPv6 VPN routes.
Follow these steps to configure IPv6 IS-IS between IPv6 MCE and VPN site:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Create an IPv6 IS-IS process for a
VPN instance and enter IS-IS view
isis
[
process-id
]
vpn-instance
vpn-instance-name
Required
Perform this configuration on the
IPv6 MCE. On a VPN site,
configure normal IPv6 IS-IS.
Configure a network entity title for
the IS-IS process
network-entity
net
Required
Not configured by default
Enable the IPv6 capacity for the
IPv6 IS-IS process
ipv6 enable
Required
Disabled by default