Configuring DR Priority of an Interface
Context
The DR priority on a switch interface qualifies the interface for the DR election. If the DR priority is 0, the switch cannot be elected as a DR or BDR.
Do as follows on the switch that runs OSPFv3.
Procedure
- Run system-view
The system view is displayed.
- Run interface interface-type interface-number
The interface view is displayed.
- On an Ethernet interface, run undo portswitch
The interface is switched to Layer 3 mode.
By default, an Ethernet interface works in Layer 2 mode.
The mode switching function takes effect when the interface only has attribute configurations (for example, shutdown and description configurations). Alternatively, if configuration information supported by both Layer 2 and Layer 3 interfaces exists (for example, mode lacp and lacp system-id configurations), no configuration that is not supported after the working mode of the interface is switched can exist. If unsupported configurations exist on the interface, delete the configurations first and then run the undo portswitch command.
If many Ethernet interfaces need to be switched to Layer 3 mode, run the undo portswitch batch interface-type { interface-number1 [ to interface-number2 ] } &<1-10> command in the system view to switch these interfaces to Layer 3 mode in batches.
- Run ospfv3 dr-priority priority [ instance instance-id ]
The DR priority of the interface is set.
- Run commit
The configuration is committed.
Follow-up Procedure
After the DR priority is changed, you can re-elect a DR or BDR through the following methods, which, however, will result in the interruption of the OSPFv3 neighbor relationship between switches and therefore are used only when necessary.
Restarting all switches.
Running the shutdown and undo shutdown commands on the interface on which the OSPFv3 neighbor relationship is set up.