Went to the remote server location last night and found that resetting the DRAC with the racadm utility restores the remote console connection capability.
As a workaround I've created a Scheduled Task that runs daily and executes:
racadm racreset
I can now use the DRAC as intended, although I would still appreciate a solution to this problem.
Not sure if this is related.... but... I get notifications (2 or 3 a day) saying that the Drac cards of some servers are unavailable (ping timed out). i always though this was strange and there are no issues with the servers... just the Drac... and if I remote access the Drac the second I receive the alert, then they work fine....
Anyways.... I guess you have tried all the standard stuff?? reset the factory defaults and re-configure, checked for Firmware updates etc.... also check to see if the Drac's switch port has any errors? maybe a duplex issue? was the switch restarted recently?
Strange that they can no longer be reached by a ping, but do respond to remote access. Do you mean you actually start up the Console from within the web interface, or just the web interface?
In my case the Console stops working; but the webinterface works just fine. Ping also responds.
Maybe both issues are indeed related, perhaps some network related functions just crash after a period of time?
In response to your questions; I upgraded the firmware to version 1.21, which is the most recent. I have tried going back to default for the webinterface and other non-security related network settings, but that didn't work.
To rule out problems with the local network I've connected the server directly to my laptop with a cross cable; the Console still wouldn't work. Only after a racadm racreset the console returned back to life.
It's strange, luckily the workaround of having a scheduled task resetting it daily seems to work fine.
Thanks for posting. If there are recurring problems with a DRAC, sometimes there is a hardware problem, but more often a firmware flash will fix it. Even if you are at the latest firmware version, flash it to restore everything to the proper state. Keeping the DRAC on a management network instead of the general network is good for security and will sometimes help as well.
I had this same issue on a PE 2950 with Drac 5 and found that the Drac would allow login after a two minute power drain, but I would also agree with keeping firmware up to date.
-I just wanted to share my findings in case somebody else finds it useful.
Zephyr42
1 Rookie
•
7 Posts
0
September 8th, 2007 07:00
Zephyr42
1 Rookie
•
7 Posts
0
September 8th, 2007 07:00
Zephyr42
1 Rookie
•
7 Posts
0
September 8th, 2007 07:00
Stooartbaby
2 Intern
•
132 Posts
0
September 9th, 2007 22:00
Zephyr42
1 Rookie
•
7 Posts
0
September 11th, 2007 17:00
DELL-Jeff M
2 Intern
•
793 Posts
0
September 24th, 2007 22:00
Steve Robey
1 Message
0
March 18th, 2015 02:00
I had this same issue on a PE 2950 with Drac 5 and found that the Drac would allow login after a two minute power drain, but I would also agree with keeping firmware up to date.
-I just wanted to share my findings in case somebody else finds it useful.