DHCP Failover Configuration on Enterprise SONiC Switch
1 Commands
1.1 Configuration Commands
|
2 Example Deployment
2.1 Networking Requirements

In this network design, two DHCP servers are configured to handle half of the client requests each, providing both high availability and load balancing. Downstream DHCP clients can obtain IP addresses normally, and the failure of a single server or a single downstream link does not affect the overall network functionality.
Configuration Recommendation:
During the lease renewal process, clients typically send a renewal request at 37.5% of the lease time. To ensure uninterrupted service, it is recommended that the minimum DHCP server lease time be configured to more than three times the MCLT. This ensures that the client’s renewal request is sent before the DHCP server’s stay in the communications_interrupted state expires, allowing the client to renew successfully and preventing temporary network outages caused by failed renewals and forced reallocation of IP addresses.
2.2 Configuration Steps
2.2.1 Configure the DHCP Server
- Configure interface information
|
- Configure DHCP Failover
|
- Configure DHCP Pool
|
- Configure routing
|
2.2.2 Configure DHCP Relay
- Configure interface information
|
- Configure DHCP Relay
|
- Configure routing
|
3 Display and Maintenance
|