Actual configuration node for dhcp-server failvor in 1.4 and 1.5 looks like this:
vyos@dhcp-sag-main# set service dhcp-server failover Possible completions: name Peer name used to identify connection remote IPv4 remote address used for connectio source-address IPv4 source address used to initiate connection status Failover hierarchy [edit] vyos@dhcp-sag-main# set service dhcp-server failover
And behavior is quite different in both of the:
- VyOS 1.4: is an active-active setup, where both server will attend request
- VyOS 1.5: is an active-passive setup, when primary server will attend all the request.
Also, the word failover tends to define an active-passive setup.
So, this task is focus on re-naming failover node, so later inside such node we can define appropriate mode.
Intended new structure:
vyos@dhcp-sag-main# set service dhcp-server high-availability Possible completions: name Peer name used to identify connection remote IPv4 remote address used for connectio source-address IPv4 source address used to initiate connection status Failover hierarchy [edit] vyos@dhcp-sag-main# set service dhcp-server high-availability
Once this is implemented, we could add mode leafnode, to define active-active or active-passive configuration.
Related task: https://vyos.dev/T6068