You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After using the clear ip ospf process command, the ospf interface state will be stuck in the Waiting state.
Version
10.2
How to reproduce
use the conf below to init ospf
interface r0-eth2
ip address 154.189.56.72/10
ip ospf area 0.0.0.2
router ospf
After a few seconds, we enter the following two commands. At this time the state of r0-eth2 is Waiting.(We can see it using show ip ospf interface json)
ip ospf dead-interval 54315
clear ip ospf process
We set the waitTimer bound to a very large value.
We then enter the following commands.
ip ospf dead-interval 1
In the absence of the clear ip ospf process command, the waitTimer will expire and the state will change to DR. But in the case of clear ip ospf process, the interface state will be stuck in Waiting state.
Expected behavior
State changes to DR.
Actual behavior
State is stuck in the Waiting state.
Additional context
No response
Checklist
I have searched the open issues for this bug.
I have not included sensitive information in this report.
The text was updated successfully, but these errors were encountered:
Description
After using the
clear ip ospf process
command, the ospf interface state will be stuck in the Waiting state.Version
How to reproduce
show ip ospf interface json
)We set the waitTimer bound to a very large value.
In the absence of the
clear ip ospf process
command, the waitTimer will expire and the state will change to DR. But in the case of clear ip ospf process, the interface state will be stuck in Waiting state.Expected behavior
State changes to DR.
Actual behavior
State is stuck in the Waiting state.
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: