Configuring the Dead Time of Neighbor Relationship
Context
If a switch does not receive any Hello packet from its neighbor during a specified period, the neighbor switch is considered invalid. The specified period is called the dead time of the neighbor relationship. The dead time must be at least four times the Hello interval on an interface.
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 timer dead interval [ instance instance-id ]
The dead time of the neighbor relationship is specified.
If the dead interval of an OSPFv3 neighbor is shorter than 10s, the session may be closed. Therefore, if dead interval is shorter than 10s, the actual dead interval of an OSPFv3 neighbor is not shorter than 10s. If the conservative mode is configured using the ospfv3 timer hello command, the configured dead timer takes effect even when its value is less than 10s.
- Run commit
The configuration is committed.
