Overview
Polystack Networking distributes work across multiple agents running on compute and network nodes. Monitoring agent health is a core administrative responsibility — a downed agent can silently prevent new port bindings, DHCP assignments, or routing updates. This guide covers how to inspect, manage, and recover agents across your cluster.Prerequisites
- Admin credentials sourced from
openrc.sh openstackCLI installed and configured
Inspect Agent Health
- Dashboard
- CLI
Navigate to Network Agents
Navigate to Network > Network Agents (admin view).
Review agent status
Each row represents one agent instance. Review the following columns:
Enable and Disable Agents
Disable an agent before performing maintenance on its host to prevent the scheduler from assigning new work to it. Re-enable after maintenance completes.- CLI
Disable agent for maintenance
Re-enable agent after maintenance
Agent Type Reference
Restart an Agent
When an agent showsAlive: False, restart the service on the affected host. Agents
running inside Docker containers are managed by the deployment console:
Restart networking agents via the deployment console
Confirm agent is alive
Agent shows
Alive: True and a recent heartbeat timestamp.Next Steps
DHCP Configuration
Schedule networks to DHCP agents and configure HA for high availability
L3 Router Configuration
Configure HA and distributed routing across L3 agents
Service Architecture
Understand the distributed agent model and message bus communication
Admin Troubleshooting
Diagnose and resolve agent failures and VXLAN connectivity issues
