H3C Technologies H3C SR8800 - Manual (Page 367)

356
NOTE:
For information about IPv6 static routing, see Layer 3—IP Routing Configuration Guide.
Configuring RIPng between PE and CE
A RIPng process belongs to the public network or a single VPN instance. If you create a RIPng process
without binding it to a VPN instance, the process belongs to the public network.
To configure RIPng between PE and CE:
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 PEs.
On CEs, create a normal 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.
NOTE:
For more information about RIPng, see Layer 3—IP Routing Configuration Guide.
Configuring OSPFv3 between PE and 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.
To configure OSPFv3 between PE and CE:
Step Command Remarks
1. Enter system view. system-view N/A
2. Create an OSPFv3 process for
a VPN instance and enter the
OSPFv3 view.
ospfv3 [ process-id ] vpn-instance
vpn-instance-name
Perform this configuration on PEs.
On CEs, create a normal OSPF
process.
3. Set the router ID. router-id router-id Required
4. Return to system view. quit N/A
5. Enter interface view.
interface interface-type
interface-number
N/A
6. Enable OSPFv3 on the
interface. ospfv3 process-id area area-id
[ instance instance-id ]
By default, OSPFv3 is disabled on
an interface.
Perform this configuration on PEs.
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.