How-To

Dell iDRAC 9 Quick Reference: RACADM Cheat Sheet, Ports, Alerts, and Glossary

6 min read

This final part of the Dell iDRAC 9 runbook series is designed to live open in a browser tab during both setup and incident response. Parts 1–5 walked through the full configuration and troubleshooting lifecycle; this appendix distills the most frequently needed reference material into a single, scannable page — no narrative, just the commands, tables, and links you reach for under pressure.

If you arrived here directly from a search, the RACADM cheat sheet below covers the most common operations. For the full configuration walkthrough, start with Part 1 of this series.

Configuration Reference

Common Settings Summary

SettingRACADM pathRecommended value
NIC selectioniDRAC.NIC.SelectionDedicated
DHCP disableiDRAC.IPv4.DHCPEnable0
VLAN enableiDRAC.NIC.VLanEnable1
IPMI over LANiDRAC.IPMILan.Enable0 (disabled)
TLS minimumiDRAC.WebServer.TLSProtocolTLS_1_2_and_higher
SNMP communityiDRAC.SNMP.AgentCommunityChange from public
Thermal profileSystem.ThermalSettings.ThermalProfileDefaultFanSpeedOffset or MaximumPerformance

Tips and Troubleshooting

Virtual console blank screen after launch

iDRAC 9 web UI showing Virtual Console session management and license overview screen

Confirm license tier: iDRAC Settings > Overview > License must show Enterprise or Datacenter. If licensed, check concurrent session count — iDRAC limits virtual console to 6 simultaneous sessions by default. Terminate stale sessions under iDRAC Settings > Services > Virtual Console. If still blank after a valid license is confirmed, perform a soft reset: racadm racreset, then retry after 2 minutes.

Firmware update job stuck in queue

# View current job queue
racadm jobqueue view

# Delete all pending jobs (do this during a maintenance window)
racadm jobqueue delete --all

# Resubmit the update

Confirm the firmware image matches your exact PowerEdge model by downloading via your server’s Service Tag at dell.com/support.

RACADM remote authentication fails

# Test basic Redfish connectivity first
curl -sk -u root:YOUR_PASSWORD https://<iDRAC-IP>/redfish/v1

# Add SSL skip flag to RACADM for troubleshooting
racadm -r <iDRAC-IP> -u root -p YOUR_PASSWORD -S ssl getsysinfo

If the web UI accepts the credentials but RACADM fails, check that port 443 is open and not filtered by an intermediate proxy.

Alerts silently stopped working

iDRAC 9 web UI SSL certificate expiry details under Web Server settings

Check the SSL certificate expiry date first — monitoring tools that validate certificates will silently fail when the iDRAC cert expires. Navigate to iDRAC Settings > Services > Web Server > SSL to check the expiry date. If expired, regenerate the CSR and upload a new signed certificate (Step 5).

Then send a test alert: racadm testalert -l 1 and verify delivery.

SNMP traps not arriving at receiver

Capture traffic on the receiver to confirm packets are arriving: run a packet capture on the trap receiver host filtering for UDP port 162 from the iDRAC IP. If packets arrive but aren’t processed, the issue is in the receiver configuration. If no packets arrive, the problem is network routing or a firewall rule between iDRAC and the trap destination.

Appendix: Quick Reference

RACADM Cheat Sheet

Terminal window showing multiple RACADM commands with output on Linux
# System info
racadm getsysinfo

# NIC config
racadm getniccfg -n idrac

# Get any iDRAC setting
racadm get iDRAC.<Group>.<Attribute>

# Set any iDRAC setting
racadm set iDRAC.<Group>.<Attribute> <value>

# Server power actions
racadm serveraction powerdown
racadm serveraction powerup
racadm serveraction powercycle
racadm serveraction graceshutdown

# Soft-reset iDRAC only (OS unaffected)
racadm racreset

# View job queue
racadm jobqueue view

# Delete all jobs
racadm jobqueue delete --all

# Storage: list controllers
racadm storage get controllers

# Storage: list virtual disks
racadm storage get vdisks -o -p Name,RAIDStatus,RemainingRedundancy

# Storage: list physical disks
racadm storage get pdisks -o -p DeviceDescription,State,Size

# Blink disk locator LED
racadm storage blink:<disk-FQDD>

# Export LC log
racadm lclog export -f lclog.xml

# Export SCP (full config)
racadm get -f config.xml -t xml -l ALL

# Import SCP
racadm set -f config.xml -t xml -l ALL -s TIME_NOW

# Firmware versions
racadm getversion

# Sensor readings
racadm getsensorinfo

# Hardware inventory
racadm hwinventory

# Test alert delivery
racadm testalert -l 1

Port Reference Table

PortProtocolDirectionService
443TCPInbound to iDRACWeb UI, Redfish API, HTML5 console
22TCPInbound to iDRACSSH / firmware RACADM
5900TCPInbound to iDRACVNC console path
162UDPOutbound from iDRACSNMP traps
514UDP/TCPOutbound from iDRACSyslog
25/465/587TCPOutbound from iDRACSMTP email alerts
623UDPInbound to iDRACIPMI over LAN — disable
3269TCPOutbound from iDRACAD/LDAP (Global Catalog SSL)

Alert Category Reference

CategoryKey eventsRecommended action threshold
System HealthCPU fault, memory fault, voltageCritical + Warning
StorageVirtual disk degraded/failed, predictive disk failureCritical + Warning
ThermalTemperature threshold exceeded, fan failureCritical
PowerPSU failure, power budget exceededCritical
ConfigurationiDRAC config changes, firmware updatesInformational (audit)
AuditLogin/logout events, user changesInformational (SIEM)
UpdatesFirmware update success/failureInformational

Licensing Feature Comparison

FeatureBasicExpressEnterpriseDatacenter
Hardware health dashboard
LC Log / SEL
RACADM (limited)
Virtual console (KVM)Limited
Virtual media
AD/LDAP auth
SNMP v3
Syslog forwarding
Redfish API (full)
SCP export/import
Group Manager
Telemetry streaming
iDRAC Direct (full)

Common LC Event IDs

Event IDMeaningSeverity
MEM0001Correctable ECC errorWarning
MEM0002Uncorrectable ECC errorCritical
STOR001Virtual disk state changeWarning/Critical
STOR004Physical disk state changeWarning/Critical
STOR006Predictive failure (SMART)Warning
THER0001Temperature threshold exceededCritical
PWR1004PSU failureCritical
FAN0001Fan failureCritical
RAC0182iDRAC configuration changeInformational
USR0001User login/logoutInformational
SWC0001Firmware update completedInformational

Dell Support Resources

Glossary

TermDefinition
iDRACIntegrated Dell Remote Access Controller — the out-of-band management controller embedded in PowerEdge servers
RACADMRemote Access Controller Admin — the CLI for iDRAC management
LCLifecycle Controller — the persistent firmware environment for updates, inventory, and configuration
SELSystem Event Log — IPMI-level hardware sensor event log
PERCPowerEdge RAID Controller — Dell’s embedded RAID controller family
SCPSystem Configuration Profile — full server configuration export/import format
LOMLAN on Motherboard — shared NIC used for both host traffic and iDRAC when dedicated NIC is not used
FQDDFully Qualified Device Descriptor — iDRAC’s unique identifier for hardware components (e.g., Disk.Bay.0:Enclosure.Internal.0-1:RAID.Integrated.1-1)
VDVirtual Disk — a RAID volume presented to the OS by the PERC controller
PDPhysical Disk — an individual drive in the system
DRMDell Repository Manager — tool for creating and hosting local firmware catalogs
SIDService Tag ID — Dell’s unique server identifier, used for support and firmware lookups
KVMKeyboard/Video/Mouse — the virtual console that gives remote access to the server’s display

Wrapping Up

With this runbook in hand, you can stand up a new PowerEdge from zero to production-ready — with static IP, named user accounts, signed certificates, verified alerting, and a current firmware baseline — in a single maintenance window. When something breaks, the troubleshooting sections give you a structured path from symptom to resolution without guessing.

The single most valuable habit to build: export the LC log before touching hardware during an incident. That timestamp trail is what separates a clean root-cause analysis from a support case that drags on for days.

This appendix wraps up the complete Dell iDRAC 9 runbook series. Across six parts, we covered everything from first login and network hardening through RAID management, firmware updates, virtual console access, automation with RACADM and Redfish, and structured troubleshooting runbooks for the most common PowerEdge hardware incidents. Bookmark this quick-reference page and the troubleshooting runbook in Part 5 — those are the two you’ll return to most often in production.