Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

FRR: OSPF ipv6 influence interface cost via carp #2923

Closed
3 tasks done
AdSchellevis opened this issue Apr 1, 2022 · 1 comment
Closed
3 tasks done

FRR: OSPF ipv6 influence interface cost via carp #2923

AdSchellevis opened this issue Apr 1, 2022 · 1 comment
Assignees
@AdSchellevis
Labels
feature Adding new functionality

Comments

@AdSchellevis
Copy link
Member

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

Is your feature request related to a problem? Please describe.
This ticket is mostly an extension of #2091, which describes the general outline of carp challenges when using OSPF.

The concept around carp ospf cost calculation seems to be rather practical but only support IPv4 OSPF, it would be practical to support the same mechanism for IPv6 OSPF too, which is what this ticket is about.

Describe the solution you'd like

Add the same toggles to Routing -> OSPFv3 interfaces as we added for OSPF (cost_demoted, carp_depend_on) and expand the event handler to signal ospf6 as well.

Changing the costs for ospf6 should work similar, via vtysh go into configure mode, select an interface (interface XXX) and set the new cost (ipv6 ospf6 cost XXX)

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context

sponsored by : Modirum (https://www.modirum.com/)
@AdSchellevis AdSchellevis added the feature Adding new functionality label Apr 1, 2022
@AdSchellevis AdSchellevis self-assigned this Apr 1, 2022
AdSchellevis added a commit that referenced this issue Apr 5, 2022
@AdSchellevis
FRR: OSPF ipv6 influence interface cost via carp [#2923]
910044f 
add event handler for ospf6 carp demotion including required interface fields (carp_depend_on and cost_demoted).
while here polish some small usability issues, knowing:

o Interface networktype and interfacename should be single dropdown boxes
o diagnostics / bgp - fix search in grid, should only use a formatter for presentation purposes.
AdSchellevis added a commit that referenced this issue Apr 5, 2022
@AdSchellevis
FRR: OSPF ipv6 influence interface cost via carp [#2923]
e43a211 
add event handler for ospf6 carp demotion including required interface fields (carp_depend_on and cost_demoted).
while here polish some small usability issues, knowing:

o Interface networktype and interfacename should be single dropdown boxes
o diagnostics / bgp - fix search in grid, should only use a formatter for presentation purposes.
AdSchellevis added a commit that referenced this issue Apr 6, 2022
@AdSchellevis
FRR: OSPF ipv6 add "CARP demote" option in OSPFv3 for #2923
f3478e2 
Bring HA features on par with OSPF, adds:

o carp_frr_ospf6 rc.carp_service_status.d event handler
o add "CARP demote" to model, form and template
@AdSchellevis AdSchellevis mentioned this issue Apr 6, 2022
Merged
AdSchellevis added a commit that referenced this issue Apr 6, 2022
@AdSchellevis
FRR: OSPF ipv6 add "CARP demote" option in OSPFv3 for #2923
4bf64a5 
o bugfix previous, missing IFS= (internal field seperator)
AdSchellevis added a commit that referenced this issue Apr 8, 2022
@AdSchellevis
FRR: OSPF ipv6 influence interface cost via carp [#2923]
16af155 
o missing ospf6d in log event handler
@AdSchellevis
Copy link
Member Author

closed #2929

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

@AdSchellevis AdSchellevis

Labels
feature Adding new functionality
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AdSchellevis