281
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create a RIPng process for a
VPN instance and enter RIPng
view.
ripng
[
process-id
]
vpn-instance
vpn-instance-name
Perform this configuration on the
PE. On the CE, create a common
RIPng process.
3.
Return to system view.
quit
N/A
4.
Enter interface view.
interface
interface-type
interface-number
N/A
5.
Enable RIPng on the interface.
ripng
process-id
enable
By default, RIPng is disabled on an
interface.
Configuring OSPFv3 between a PE and a CE
An OSPFv3 process belongs to the public network or a single VPN instance. If you create an OSPF
process without binding it to a VPN instance, the process belongs to the public network.
For more information about OSPFv3, see
Layer 3—IP Routing Configuration Guide
.
To configure OSPFv3 between a PE and a CE:
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
PE. On the CE, create a common
OSPF process.
Deleting a VPN instance also
deletes all related OSPFv3
processes.
3.
Set the router ID.
router-id
router-id
N/A
4.
(Optional.) Configure an
OSPFv3 domain ID.
domain-id
{
domain-id
[
secondary
] |
null
}
The default domain ID is 0.
Perform this configuration on the
PE.
When you redistribute OSPFv3
routes into BGP, BGP adds the
primary domain ID to the
redistributed BGP VPNv6 routes as
a BGP extended community
attribute.
You can configure the same
domain ID for different OSPFv3
processes.
All OSPF processes of the same
VPN must be configured with the
same OSPF domain ID to ensure
correct route advertisement.