Enabling OSPFv3
Context
OSPFv3 supports multiple processes. Multiple OSPFv3 processes running on one switch are differentiated by process IDs. OSPFv3 process ID is set when OSPFv3 is enabled and is only locally valid. It does not affect the packet exchange with other switches.
In the format of an IPv4 address, a router ID is a 32-bit unsigned integer that uniquely identifies a switch within an AS. The router ID of OSPFv3 must be manually set. If no router ID is set, OSPFv3 fails to run normally.
When manually setting the router ID, ensure that the router IDs of any two switches in an AS are different. When multiple processes are enabled on a switch, it is necessary to specify a unique route ID for each process.
To ensure the stable running of OSPFv3, you need to allocate router IDs and set them in network planning.
Do as follows on the switch that runs OSPFv3.
Procedure
- Run system-view
The system view is displayed.
- Run ospfv3 [ process-id ] [ vpn-instance vpn-instance-name ]
OSPFv3 is enabled and the OSPFv3 view is displayed.
If a VPN instance is specified, the OSPFv3 process belongs to the specified VPN instance. Otherwise, the OSPFv3 process belongs to the public network instances.
- Run router-id router-id
A router ID is set.
If a router ID conflict occurs, perform either of the following operations:
- Reconfigure a router ID.
- Run the undo ospfv3 router-id auto-recover disable command to enable the router ID automatic recovery function. After the function is enabled, the system automatically allocates a new router ID.
- If the automatic recovery function is enabled and a router ID conflict occurs between indirectly connected switches in one OSPF area, the system replaces the conflicted router ID with a newly calculated one. The automatic recovery function takes effect on both configured and automatically generated router IDs.
- The system can replace a router ID in a maximum of three attempts in case the router ID conflict persists.
- Run commit
The configuration is committed.