Project

General

Profile

Actions

Correction #10954

closed

Feedback on Troubleshooting — Troubleshooting High Availability DHCP Failover

Added by Bill McGonigle about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Troubleshooting
Target version:
-
Start date:
10/04/2020
Due date:
% Done:

0%

Estimated time:

Description

Page: https://docs.netgate.com/pfsense/en/latest/troubleshooting/ha-dhcp-failover.html

Feedback:

Could use something like:

Both nodes must have the same interface definitions such that the same DHCP scope is on the same OPT interface. For example, if you create a new interface pair 'DMZ' on both nodes sharing a VIP, but one is OPT3 and the other is OPT6, IP will work, VIP will work, but DHCP peering will fail and rules propagation will fail via pfsync. Ensure that both nodes have the same interface number for the same DHCP scope. Create dummy/placeholder interfaces (e.g. assign unused VLANs) on the other node if needed to get the new interface to the same OPT number.

Both nodes must be running the same version of pfSense® software. Update both nodes to the newest available stable release if they do not match. Older versions may have problems with various aspects of DHCP failover that have already been corrected.

Actions #1

Updated by Bill McGonigle about 1 year ago

(sorry, ignore the accidental copy & paste second paragraph) - can't edit.

Actions #2

Updated by Jim Pingle about 1 year ago

  • Category set to Troubleshooting
Actions #3

Updated by Jim Pingle about 1 year ago

  • Status changed from New to Resolved

I added a more concise version of that on the page, plus on the main HA troubleshooting page and on the XML-RPC sync page.

https://docs.netgate.com/pfsense/en/latest/troubleshooting/high-availability.html
https://docs.netgate.com/pfsense/en/latest/highavailability/xmlrpc-sync.html

Changes will show up shortly once the build finishes.

Actions

Also available in: Atom PDF