Unsolved

This post is more than 5 years old

10617

July 11th, 2019 13:00

Poweredge C6420 iDRAC issue

I recently experienced the error "RAC0182 The iDRAC firmware was rebooted with the following reason: AC" that forced three out of four nodes on my PE servers to reboot at the same time. During the time this error occurred, no one was anywhere near the PE server. I found a similar article on dell support https://www.dell.com/support/article/id/en/idbsd1/sln309655/dell-poweredge-idrac9-rac0182-the-idrac-firmware-was-rebooted?lang=en

However, the problem mentioned in this article was for watchdogs while my problem was AC. In addition my iDRAC firmware version is well above the version mentioned in the article when this particular incident occurred. I am struggling to find out what caused this event to happening.

 

7 Practitioner

 • 

9.7K Posts

 • 

48K Points

July 12th, 2019 06:00

FrustratedC6420User,

The RAC0182 error can be caused by a couple things, some reasons may include: AC Power Cycle, the Watchdog timer as you stated, or a resets initiated via user interface or ID Button. With the 3 of 4 nodes having restarted, do you know if there were any power discrepancies that may have occurred, such as a brown out or something along those lines? Also, you stated that the iDrac fw was above the level listed in the article, but is the C6420 iDrac (3.34.34.34) AND BIOS (2.2.11) both up to date and on the latest versions?

Let me know.

 

1 Message

September 20th, 2019 01:00

Hi, This same issue happened to our servers as well. 3 out of 4 servers rebooted at the same time after midnight (The iDRAC firmware was rebooted with the following reason: ac.) iDrac version: 3.34.34.34 BIOS: 2.2.11 BR, Juha

October 1st, 2019 14:00

We saw this error once on a Dell R630 which is running as an appliance
TimeLine
2019-08-22 19:56 PM Server and Linux stop logging
2019-08-22 19:56:57 GMT database system was not properly shut down [database log after reboot]
2019-08-22 19:57:04 GMT SYS1001 System is turning off [iDrac log]
2019-08-22 19:57:04-0500 SYS1003 System CPU Resetting.
2019-08-22 19:58:14 Power Supply 1: Status = 0x00, IOUT = 0x0, VOUT= 0x0, TEMP= 0x0, FAN = 0x0, INPUT= 0x0.
2019-08-22 19:59:58 GMT RAC0182 The iDRAC firmware was rebooted with the following reason: ac.
2019-08-22 20:00:16 GMT IPA0100 The iDRAC IP Address changed from 0.0.0.0 to n.n.n.n.

I think it looks like an iDrac problem, possibly related to LifeCycle v. 2.61 problem:

Lifecycle Controller Logs frequently logging PSU0800 events that are not associated with User initiated reboot of server or iDRAC.
https://www.dell.com/support/article/us/en/04/sln316859/idrac7-idrac8-idrac-unresponsive-or-sluggish-performance?lang=en

Fix is to update to Lifecycle v.2.63. Does this sound like the fix is in v.2.63?

3 Posts

November 29th, 2019 08:00

Dear Chris Hawk,

I am a new T340 user (bought about a fortnight ago) with Essentials 2019 preinstalled - and with IDRAC9 upgraded to Enterprise TRIAL version 3.36.36 - and today after about 10 working days of usage - today exactly the same issue occurred in our server too as described in an earlier post by another user - https://www.dell.com/community/Systems-Management-General/Previous-reboot-was-due-to-a-firmware-watchdog-timeout/td-p/6246502

- with the fans seeming to be spinning full speed noisily and then normalising - and this happened today for the 1st time and so when I logged into IDRAC and saw the log, it showed the reason  as "RAC0182....idrac reboot due to  watchdog" - and this has occurred thrice today after gaps of about 1-2 hours each. (I can also send a photo of the log - if so desired by you).

I searched the net and came across this post - https://www.dell.com/support/article/in/en/inbsd1/sln309655/dell-poweredge-idrac9-rac0182-the-idrac-firmware-was-rebooted?lang=en

and hence writing to you because this solution post mentioned that this issue is fixed in 3.21.21 - whereas we are already using 3.36.36 - so please advise.

Thanks in advance,

 

3 Posts

November 29th, 2019 22:00

Just to add to my query - I now came across possibly a more recent knowledgebase update:

https://www.dell.com/support/article/in/en/inbsd1/sln319041/idrac9-rac0182-idrac-firmware-rebooting-with-watchdog-due-to-network-traffic?lang=en

which seems to suggest to wait for version 3.40.40 in Dec. 2019 - so is this the solution we need to wait for?

Thanks in anticipation of your clarification / confirmation.

1 Message

August 25th, 2020 10:00

We recently experienced the same error as your posted.  I believe you have resolved this issue.  I really appreciate if you could share with us how you resolved it and what the real problem was.  Thank you very much !

November 18th, 2021 09:00

Hello, I got same issue on a lot of this servers with last updates installed. We are very very angry.

Please , if someone has found a solution  send me an email:

 

130 Posts

November 18th, 2021 11:00

Can you elaborate on what happened, what model of systems are involved and what version of bios and idrac fw you have? What do the SEL and LC log say happened at the time the systems rebooted? 
Have you confirmed this wasnt a power fluctuation in the building?  

5 Posts

April 17th, 2022 08:00

Hello,

We had same problem last week 2 times in different C6420 chasis:

Last March 18 we updated our C6420:

  • BIOS Version: 2.10.2 → 2.13.3
  • iDRAC Firmware Version: 4.40.10.00 → 5.10.10.00

Some days ago one of our C6420 restarted 4 nodes with message:

RAC0182 The iDRAC firmware was rebooted with the following reason: ac.

 

Today, we have same issue in different C6420 chasis. In this case, only 2 of 4 servers was restarted with same log.

Actual firmwares version are:

C6420 with 4 servers restarted:

  • BIOS Version: 2.13.3

  • Lifecycle Controller Firmware: 5.10.00.00

  • iDRAC Firmware Version: 5.10.00.00

  • PS1 firmware: 0.3d.67

  • PS2 firmware: 0.3d.65

C6420 with 2 servers restarted:

  • BIOS Version: 2.13.3

  • Lifecycle Controller Firmware: 5.10.00.00

  • iDRAC Firmware Version: 5.10.00.00

  • PS1 firmware: 0.3d.67

  • PS2 firmware: 0.3d.67

We discarded that somebody pressed reset button or power failure. We have different C6420 in every rack and they are connected to different power lines for redundancy.

Please let me know if you need some additional information, this issue is very important for us.

Thanks.

5 Posts

April 17th, 2022 10:00

How can i check which version we have already installed?

5 Posts

April 17th, 2022 10:00

I found the command to validate Chassis Management FW version:

# ipmitool -I lanplus -H XX.XX.XX.XX -U XXXXXX -P XXXXX raw 0x30 0x12
01 dd 1b 01 35 01 00 00 00 01 02 00 01 2d 37 ff
ff 08 c2 00 00 00 08 01 08 10 64 23 fa 01

 01 -> 1 

35 -> 53

We are using fw version 1.53 instead 3.35 (latest). We use Update menu from iDrac, HTTPS option with downloads.dell.com:

  1. Why this process doesn't suggest upgrade Chassis Management firmware?
  2. There are others firmwares that Update menu from iDrac are not suggested?
  3. I see that CM fw 3.35 increased power limits. What is the limit in version <3.35?

Thanks.

6 Operator

 • 

3K Posts

April 17th, 2022 10:00

Can you check whether you have latest Chassis Manager FW installed on the chassis. You can refer below link to get latest Chassis FW 

https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=mn93p&oscode=naa&productcode=poweredge-c6400 

6 Operator

 • 

3K Posts

April 17th, 2022 19:00

Chassis Manager firmware is for C6400 chassis not for C6420 SLED. That is why downloads.dell.com is not showing chassis manager FW. iDRAC is a method to update chassis manager firmware.

Moderator

 • 

5.4K Posts

 • 

37 Points

April 17th, 2022 19:00

To add to what Shine said, C6420 do not have Chassis management cards, unlike M1000e or MX7000 (those with chassis). It’s just the way how it was designed from birth. Hence no chassis management such as MM.

5 Posts

April 17th, 2022 22:00

Hello,

I guest that Power Supply firmwares are not managed by downloads.dell.com. How can i check all the firmwares not managed by the update manager? For example, CM, PS...

Thanks.

No Events found!

Top