Skip to content

Fix: Remove extra parameter in EXOS OSPFv2 timer configuration#3254

Open
ipspace wants to merge 1 commit intodevfrom
exos-ospf-timer
Open

Fix: Remove extra parameter in EXOS OSPFv2 timer configuration#3254
ipspace wants to merge 1 commit intodevfrom
exos-ospf-timer

Conversation

@ipspace
Copy link
Copy Markdown
Owner

@ipspace ipspace commented Mar 29, 2026

The fifth parameter in the 'configure ospf vlan timer' command should be positive (the template value is zero) on SW release 33.1.1.31

The parameter seems to be optional, so it might be better to remove it?

Closes #3253

The fifth parameter in the 'configure ospf vlan timer' command should
be positive (the template value is zero) on SW release 33.1.1.31

The parameter seems to be optional, so it might be better to remove it?

Closes #3253
@ipspace ipspace requested a review from sdargoeuves March 29, 2026 15:19
Copy link
Copy Markdown
Collaborator

@sdargoeuves sdargoeuves left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, I'm not sure why 0 got there initially...

Removing this value seems the best approach indeed

wait timer interval—This interval is required by the OSPF standard to be equal to the router dead interval. Under some circumstances, setting the wait interval to smaller values can help OSPF routers on a broadcast network to synchronize more quickly at the expense of possibly electing an incorrect DR or BDR. This value should not be set to less than the hello interval. The default value is equal to the router dead interval.

(source)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Incorrect parameters in EXOS OSPFv2 timer command

2 participants