ansible-idrac-9-10

Name: ansible-idrac-9-10
Availability: InStock
Author: air-gapped

Branch Ansible playbooks for iDRAC 9/10 authentication and Redfish attribute differences.

5|1|Updated Apr 19, 2026

Search Tags:#automation #session #ansible #generations #idrac #openmanage #redfish

Ready to run

npx skills add https://github.com/air-gapped/skills --skill ansible-idrac-9-10

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ansible-idrac-9-10
Source: https://github.com/air-gapped/skills/tree/main/.claude/skills/ansible-idrac-9-10
Command: npx skills add https://github.com/air-gapped/skills --skill ansible-idrac-9-10

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Operator teams need a unified, generation-aware approach to manage Dell iDRAC 9 and iDRAC 10 across OpenManage modules, with guidance on session/token handling, attribute mappings, and deprecations.

Core Features & Use Cases

Cross-generation support for iDRAC 9 and iDRAC 10, including canonical session lifecycle and per-generation module mapping.
Auth and attribute migration guidance to smoothly transition from legacy modules to Redfish-based attributes and token-based sessions.
Mixed-inventory workflows that detect generation and branch playbooks to avoid outages in diverse fleets.

Quick Start

Apply a canonical idrac_session playbook that mints a token, then perform a minimal idrac_attributes update against a target.

Frequently Asked Questions about ansible-idrac-9-10

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage mixed iDRAC 9 and 10 fleets with Ansible without playbook failures?▼

To manage mixed iDRAC 9 and 10 fleets, Ansible playbooks must detect the generation and branch accordingly, using per-generation module mappings like idrac_network versus idrac_network_attributes to prevent outages.

How does idrac_session token handling work for Dell PowerEdge automation?▼

idrac_session token handling for Dell PowerEdge automation requires minting a token via a canonical playbook before performing updates, ensuring Redfish-based attribute changes use proper session lifecycle management.

What is the correct Ansible module to use for iDRAC Redfish attribute migration?▼

The correct Ansible approach for iDRAC Redfish attribute migration involves transitioning from legacy modules to Redfish-based attributes, utilizing specific per-generation mappings to ensure compatibility across iDRAC 9 and 10.

Do I need the dell/dellemc-openmanage-ansible-modules library to automate iDRAC 10?▼

Yes, automating iDRAC 10 requires the dell/dellemc-openmanage-ansible-modules library (OME) v10.x, which provides the necessary generation-aware modules and token-based session support for unified control.

Why do my deprecated Ansible modules fail when updating iDRAC 9 network settings?▼

Deprecated Ansible modules fail when updating iDRAC 9 network settings because newer OpenManage implementations require Redfish-based attributes and specific module mappings like idrac_network_attributes for iDRAC 10 compatibility.