Overview
The DHCP agent provides IP address assignment, DNS resolver delivery, and host route injection for tenant subnets. Multiple DHCP agents can serve the same network for high availability — when the active agent fails, a standby takes over without disrupting existing DHCP leases.Prerequisites
- Admin credentials sourced from
admin-openrc.sh - At least one running DHCP agent (verify with
openstack network agent list --agent-type dhcp)
View Networks Served by an Agent
- Dashboard
- CLI
Log in to the Xloud Dashboard (
https://connect.<your-domain>) as an administrator
and navigate to Admin → Network → Agents. Click the agent ID of a DHCP agent.
The Networks tab lists all networks this agent is currently serving.Schedule a Network to a DHCP Agent
- Dashboard
- CLI
Navigate to Admin → Network → Agents, click a DHCP agent, then click
Add Network in the Networks tab. Select the network from the list.
Remove a Network from an Agent
Remove network from a specific DHCP agent
DHCP Agent HA Architecture
Troubleshoot DHCP Issues
Instances not receiving IP addresses
Instances not receiving IP addresses
Cause: DHCP agent is down, subnet DHCP is disabled, or allocation pool is exhausted.Resolution:
- Confirm DHCP is enabled on the subnet:
Check subnet DHCP status
- Verify the DHCP agent is alive:
Check DHCP agent health
- Check the allocation pool size vs. current port count:
Count ports on network
Stale DNS or gateway options on instances
Stale DNS or gateway options on instances
Cause: Subnet DNS or gateway was updated but running instances have stale DHCP leases.Resolution:
Force DHCP renewal on the affected instance:Alternatively, restart the network interface or reboot the instance.
Renew DHCP lease on Linux guest
Next Steps
Network Agent Management
Monitor and manage the full set of SDN agents across your cluster
Subnets
Configure DHCP allocation pools, DNS, and host routes at the subnet level
DNS Configuration
Control DNS resolver delivery to instances through DHCP
Admin Troubleshooting
Resolve agent and connectivity issues with diagnostic commands