Dell Servers · Rate Limits

Dell Servers Rate Limits

The Dell server-management APIs are firmware-resident on iDRAC, OME, and related appliances inside the customer's own network. There are no vendor-imposed cloud rate limits. Throughput is bounded by the iDRAC's embedded controller (modest CPU and memory), the OME appliance sizing, and the network path from clients to the BMC. Excessive concurrent sessions against a single iDRAC or aggressive Redfish polling can degrade BMC responsiveness — Dell guidance is to space telemetry / inventory polls and prefer streaming (SSE) over polling for high-frequency data.

Dell Servers Rate Limits is the machine-readable rate-limit profile for Dell Servers on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring concurrent_sessions and requests_per_second.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled, serverError, and serviceUnavailable.

Tagged areas include Hardware, Infrastructure, Server Management, Redfish, and Rate Limiting.

3 Limits Throttle: 429
HardwareInfrastructureServer ManagementRedfishRate Limiting

Limits

iDRAC concurrent sessions device
concurrent_sessions
see iDRAC user guide for the active firmware version
iDRAC enforces a small concurrent-session ceiling (typically single-digit). Excess sessions are rejected with 503 / 429 depending on firmware.
Redfish polling cadence device
requests_per_second
operator-tunable; Dell recommends spacing inventory polls
Frequent polling against a single iDRAC can starve the BMC. Dell recommends Server-Sent Events (telemetry streaming) over polling.
OpenManage Enterprise appliance throughput appliance
requests_per_second
operator-defined — bounded by OME appliance sizing
OME is a customer-deployed virtual appliance; throughput is a function of the assigned vCPU / memory / storage and the count of managed nodes.

Policies

Streaming Over Polling
For high-frequency telemetry, use the iDRAC Telemetry Streaming (Server-Sent Events) endpoint rather than periodic Redfish GETs.
Session Lifecycle
Reuse iDRAC sessions where possible and explicitly delete sessions after use to avoid hitting the device's session ceiling.
Stagger Fleet Polling
When inventorying a fleet, randomize start times and parallelism so peaks do not saturate any single iDRAC or the OME appliance.
Firmware-Version Awareness
Specific limits and supported endpoints vary by iDRAC generation (8 vs 9 vs 10) and firmware revision. Always validate against the active iDRAC user guide.

Sources