2. Wait 120 seconds.
The iDRAC is unable to process any other jobs during this time.
3. Reset the iDRAC
racadm -r <dracIP> -u root -p <password> racreset
The iDRAC becomes accessible on the network 3 to 5 minutes after the reset.
iDRAC virtual console issues
Within the iDRAC virtual console window, if the keyboard or some of the keys are not
responding, perform the following checks:
l
Ensure on your keyboard that the Scroll Lock button is off.
l
In the iDRAC virtual console, ensure that the Keyboard/Mouse Attach State is
set to Auto-attached.
For persistent iDRAC virtual console issues, see Troubleshoot general iDRAC failures
on page 343.
iDRAC virtual media issues
The following are solutions to problems that may occur when using iDRAC virtual
media:
1. If the iDRAC is stuck, one of these actions may assist with recovery:
l
In the server's Attached Media screen, disconnect the iDRAC Remote File
Share from the iDRAC browser.
l
Disconnect the iDRAC remote image:
racadm -r <dracIP> -u root -p <password> remoteimage –d
Where:
n
<dracIP>
is the iDRAC IP address
n
<password>
is the password for the server
Note:
The default password is calvin for 13G nodes and Scaleio123 for 14G nodes.
2. Issues when booting to iDRAC virtual media may cause CPU machine check errors
at POST. When this occurs, clear the iDRAC job queue and reset the iDRAC, as
described in Troubleshoot general iDRAC failures on page 343.
DTK A08: BIOS set commands fail
When running DTK A08 on R630/R730xd servers with iDRAC FW version 2.50.50.50
or higher, the BIOS set commands may fail.
The DTK is unable to configure the BIOS settings, and the following error message
may appear:
ERROR: BOOT016: Input source argument value for the boot device is
incorrect or not found among the boot devices on the system.
DTK - Hardware Update Bootable ISO
344 Dell EMC VxFlex Ready Node AMS User Guide
To Next Page
Loading...
