Do you have an iDRAC 8 that is acting sluggish, no virtual console, or take forever to validate credentials?


The behavior  you described where it sits verifying credentials I have seen in our lab.

My go to fix is this:
Go to iDRAC Settings > Server Profile and export the server profile, then import it back after the below steps are complete. If the settings are very important to you, I would write them down or do screenshots also. 
1. SSH into the iDRAC

2. Use the command:

racadm systemerase idrac,lcdata

Note: This will wipe your iDRAC and Lifecycle Controller information/settings. This will cause the system to perform at least one reboot. 

3. After the system erase completes, use the clr_nvram jumper process I mentioned previously in this thread. 

I would power off the system, move the nvram_clr jumper so that it clears the nvram contents. Then power on the system and power it off when the system complains that the jumper has been enabled. Then move the jumper back to its original position, and you “should” be ok. I work for Dell and we have a lab of about 80 R730’s, and we have yet to see this issue you’re describing.


4. Power off system with the power button. Remove power cords from system along with the iDRAC network cable, after 30 seconds, re-attach power cords, but don’t attach iDRAC network cable for at least two minutes after power is reapplied. 

5. Attach a monitor to the system and apply iDRAC network settings. You WILL have to clear your browser cache to open a browser page to the iDRAC after doing all these steps or perform a SHIFT + F5 in most browsers. 

This has always resolved the issue for me. My theory is that the Lifecycle Log gets so big that it causes problems for the iDRAC, and once the lcdata gets cleared (which clears the Lifecycle Log), the iDRAC runs normally.