Skip to content

Hardware collector ​

Generated by scripts/docs/New-CollectorReferencePages.ps1 from the collector definitions. Do not edit by hand.

PropertyValue
Idhardware
FunctionInvoke-RangerHardwareCollector
Classoptional
Covershardware, oem-integration
Required targetbmc
Required credentialbmc
Manifest domainsdomains.hardware, domains.oemIntegration

Access and permissions ​

Redfish over HTTPS to each BMC (iDRAC, iLO, XClarity or compatible) with a BMC credential; WinRM for the matching node when reachable. Read-only.

Output ​

Top-level keys of each domain, as seen in the fixture manifest (tests/maproom/Fixtures/synthetic-manifest.json). Collectors can add keys between releases; the manifest schema keeps domain payloads open.

domains.hardware ​

firmware, nodes, security, summary

domains.oemIntegration ​

endpoints, managementPosture

When it is skipped, degraded or failed ​

Auto-deselected when no BMC endpoints are configured; skipped when the BMC network is unreachable. A BMC that answers with 401 or 403 is reported per endpoint and the rest continue.

The collector status in the manifest is one of success, partial, failed, skipped or not-applicable. Since v2.7.0 the entry also carries degraded, degradationCount and degradations (source and message of every non-fatal read that failed), and a degraded collector adds an informational finding. Debug-level detail is in ranger.log.

Released under the MIT License.