A firewall change has interrupted the DHCP Failover communication between two DHCP Failover peers. Both peers are still online and can communicate to clients, but the state is now COMMUNICATIONSINTERRUPTED. What should the administrator do?
Comprehensive and Detailed In-Depth Explanation:DHCP Failover peers sync leases via TCP 647. A firewall blocking this shifts the state to COMMUNICATIONS-INTERRUPTED:
State Impact:
Both peers serve existing clients and limited new leases (via MCLT).
No sync occurs, risking lease conflicts if prolonged.
Best Action:Manually set one peer toPARTNER-DOWN(Grid > DHCP > Failover > Edit), giving the other full pool control to avoid conflicts.
Why Secondary:Conventionally, the secondary is set to PARTNER-DOWN, letting the primary take over as the authoritative peer (per Infoblox best practices).
Options:
A:Doing nothing risks conflicts if new leases exceed MCLT capacity. Incorrect long-term.
B:Primary to PARTNER-DOWN cedes control to secondary, less standard. Incorrect.
C:Secondary to PARTNER-DOWN empowers primary, aligning with failover design. Correct.
D:Changing split value doesn’t address sync loss. Incorrect.
Practical Example:In an INE lab, you’d simulate this, set secondary to PARTNER-DOWN, and troubleshoot lease consistency post-firewall fix.References:Infoblox NIOS Administrator Guide – DHCP Failover States; INE Course Content: NIOS DDI DHCP Troubleshooting.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit