H3C Technologies H3C S7500E Series Switches - Manual (Page 300)

9-5
Enabling OSPFv3
Prerequisites
z Make neighboring nodes accessible with each other at the network layer.
z Enable IPv6 packet forwarding
Enabling OSPFv3
To enable an OSPFv3 process on a router, you need to enable the OSPFv3 process globally, assign
the OSPFv3 process a router ID, and enable the OSPFv3 process on related interfaces.
A router ID uniquely identifies a router within an AS. Therefore, you need to specify a unique router ID
for each OSPFv3 router within the AS to ensure normal operation. Note that if a router runs multiple
OSPFv3 processes, you need to specify a unique router ID for each process.
An OSPFv3 process ID has only local significance. Therefore, process 1 on a router can exchange
packets with process 2 on another router.
Follow these steps to enable OSPFv3:
To do… Use the command… Remarks
Enter system view system-view —
Enable an OSPFv3 process and
enter its view
ospfv3 [ process-id ]
Required
By default, no OSPFv3 process is
enabled.
Specify a router ID router-id router-id Required
Enter interface view
interface interface-type
interface-number
—
Enable an OSPFv3 process on the
interface
ospfv3 process-id area area-id
[ instance instance-id ]
Required
Not enabled by default
Configuring OSPFv3 Area Parameters
The stub area and virtual link features of OSPFv3 are the same as OSPFv2.
Splitting an OSPFv3 AS into multiple areas reduces the number of LSAs and extends OSPFv3
applications. For those non-backbone areas residing on the AS boundary, you can configure them as
stub areas to further reduce the size of routing tables and the number of LSAs.
Non-backbone areas exchange routing information via the backbone area. Therefore, the backbone
and non-backbone areas, including the backbone itself must be contiguous. In practice, necessary
physical links may not be available for such connectivity. You can configure virtual links to address the
problem.