
396
Step Command
Remarks
7.
Enable RIPng on the
interface.
ripng
process-id
enable
Disabled by default.
For more information about RIPng, see
Layer 3—IP Routing Configuration Guide
.
Configuring OSPFv3 between an MCE and a VPN site
An OSPFv3 process belongs to the public network or a single IPv6 VPN instance. If you create an
OSPFv3 process without binding it to an IPv6 VPN instance, the process belongs to the public
network.
By configuring OSPFv3 process-to-IPv6 VPN instance bindings on a MCE, you allow routes of
different IPv6 VPNs to be exchanged between the MCE and the sites through different OSPFv3
processes, ensuring the separation and security of IPv6 VPN routes.
To configure OSPFv3 between an MCE and a VPN site:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create an OSPFv3 process
for a VPN instance and enter
OSPFv3 view.
ospfv3
[
process-id
]
vpn-instance
vpn-instance-name
Perform this configuration on the
MCE. On a VPN site, configure
normal OSPFv3.
3.
Set the router ID.
router-id
router-id
N/A
4.
Redistribute remote site
routes advertised by the PE.
import-route
protocol
[
process-id
|
allow-ibgp
] [
cost
value
|
route-policy
route-policy-name
|
type
type
] *
By default, no route of any other
routing protocol is redistributed
into OSPFv3.
5.
Return to system view.
quit
N/A
6.
Enter interface view.
interface
interface-type
interface-number
N/A
7.
Enable OSPFv3 on the
interface.
ospfv3
process-id
area
area-id
[
instance
instance-id
]
By default, OSPFv3 is disabled on
an interface.
NOTE:
Deleting a VPN instance also deletes 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 an MCE and a 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 a MCE, you allow routes of
different IPv6 VPNs to be exchanged between the MCE and the sites through different IPv6 IS-IS
processes, ensuring the separation and security of IPv6 VPN routes.
To configure IPv6 IS-IS between an MCE and a VPN site:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create an IPv6 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 a VPN site, configure
normal IPv6 IS-IS.