Mark Berry June 8, 2011
I have a DRAC 5 in a Dell PowerEdge 2900. It was working fine on firmware version 1.51, but I was doing some other server updates so decided to update the DRAC firmware as well.
I downloaded the Windows install package for DRAC firmware version 1.60. The first install failed (because I had an open connection to the DRAC web interface from a browser?), so I ran the update again. This time it succeeded, and although it didn’t ask me to, I rebooted the server.
Unfortunately, I was no longer able to connect to the DRAC from a browser using the custom HTTPS port that I had configured. I tried the default port (443) and got to the login screen, but after entering credentials, it would redirect to the custom port and be unable to connect. It’s like the port configuration was only half effective.
Finally I decided to return the DRAC to the factory default configuration to see if that at least worked. From a command prompt on the server, type:
Wait a minute and check the config:
This sets the DRAC back to the default IP of 192.168.0.120. You can use racadm to change that, or just log in to OpenManage on the server and go to System > Main System Chassis > Remote Access > Configuration tab > LAN > IPv4 Address.
You can also do a factory reset and adjust the IP address from the server console if you press Ctrl-E when prompted during bootup.
Sure enough, I was now able to access the DRAC web interface on the default port 443, using the default password of “calvin”.
To change the HTTPS port, from the DRAC web interface (not OpenManage), go to System > Remote Access > Configuration tab > Services > Web Server and change the HTTPS Port Number.
Don’t forget to set a custom password under System > Remote Access > Configuration tab > Users > “root” user.
It’s unclear whether the failed update caused this issue, or whether the firmware update itself does not fully retain the custom HTTPS address. At least the workaround is fairly straightforward. One lesson learned is to note down or print out the configuration before doing a firmware update, in case you have to do a factory reset to get back in business.