sav_Alex

updated

8 years ago

S

sav_Alex

3 Posts

0

4327

December 18th, 2018 02:00

PowerEdge r430 Problem with BMC module

There are constant reloads of the module BMС. In the logs, the problem looks like this

"Message = The iDRAC firmware was rebooted with the following reason: ID Button."

Tried to turn off the server for a while, by  completely shutting down and replacing the module with another (good). These actions did not solve the problem - the same error messages appear on the same server (despite of another BMC module). Maybe someone faced a similar problem and can help in solving it?

  • Dell-DylanJ

    6 Operator

    •

    2924 Posts

    3643

    0

    Posted December 18th, 2018 09:00

    Thanks for the manual reference, being able to see what you saw is very helpful.

    The module in question is a pass-through module for network traffic. It doesn't have any logic on it. I would try two other things. First, perform a power drain on the server. Make sure to unplug the power from the server, then hold the power button down for 30 seconds. The idea is to perform a hard restart of the iDRAC. That message leads me to believe that something is doing a soft reset of it, and we can try to clear the iDRAC by restarting it, and disabling the front panel to isolate that.

    The second thing you may try is flashing the iDRAC firmware. iDRAC 2.61.60: https://downloads.dell.com/FOLDER05296867M/1/iDRAC-with-Lifecycle-Controller_Firmware_1HY5M_WN64_2.61.60.60_A00.EXE

  • Dell-DylanJ

    6 Operator

    •

    2924 Posts

    3653

    0

    Posted December 18th, 2018 07:00

    Hello,

    The BMC/iDRAC on this family of server is integrated with the board and not removable. The module that you mentioned, could that be the control panel? It would connect to the motherboard by cable and include the power button and front USB ports. What you could do to test is to log into iDRAC settings, then front panel security, and set front panel access to "Lock Out" for testing. That would disable the front panel entirely. The system also has a rear ID button on itas well, its beneath the iDRAC port. Checking to make sure that isn't stuck may also be a good idea.

  • sav_Alex

    3 Posts

    3648

    0

    Posted December 18th, 2018 09:00

    Hello.
    Thanks for the advice, I'll try. Meant the module connected behind on a motherboard. It is on page 116 of the manual. I checked that the rear button was not stuck.

  • nkut

    1 Rookie

    •

    23 Posts

    3583

    0

    Posted December 19th, 2018 23:00


    @Dell-DylanJ wrote:
    log into iDRAC settings, then front panel security, and set front panel access to "Lock Out" for testing.

    Could you, please, provide a little bit more details on how to lock out a front panel? I was not able to find such option in "Front Panel" menu of iDRAC web-interface (see screenshot below).

    Front panel settings in iDRACFront panel settings in iDRAC

    If disabling front panel can be done via racadm command I would appreciate any info on it.

  • nkut

    1 Rookie

    •

    23 Posts

    3578

    0

    Posted December 19th, 2018 23:00

    Sorry for the noise! I could found "Front Panel Security" option in "System Setup" menu.

    image.png

    So I set front panel to locked out. We have to wait a bit to see if that will help since duration of iDRAC reboot loops varies:

    2018-12-20T05:36:16+0300RAC0182
    The iDRAC firmware was rebooted with the following reason: ID Button.
    2018-12-20T04:48:23+0300RAC0182
    The iDRAC firmware was rebooted with the following reason: ID Button.
    2018-12-20T03:37:27+0300RAC0182
    The iDRAC firmware was rebooted with the following reason: ID Button.
    2018-12-20T03:15:29+0300RAC0182
    The iDRAC firmware was rebooted with the following reason: ID Button.
    2018-12-20T03:06:58+0300RAC0182
    The iDRAC firmware was rebooted with the following reason: ID Button.
    2018-12-20T02:43:02+0300RAC0182
    The iDRAC firmware was rebooted with the following reason: ID Button.
    2018-12-20T02:03:42+0300RAC0182
    The iDRAC firmware was rebooted with the following reason: ID Button.
    2018-12-20T01:40:03+0300RAC0182
    The iDRAC firmware was rebooted with the following reason: ID Button.
    2018-12-20T00:56:39+0300RAC0182
    The iDRAC firmware was rebooted with the following reason: ID Button.
    2018-12-20T00:19:44+0300RAC0182
    The iDRAC firmware was rebooted with the following reason: ID Button.
    2018-12-20T00:14:14+0300RAC0182
    The iDRAC firmware was rebooted with the following reason: ID Button.
    2018-12-20T00:01:18+0300RAC0182
    The iDRAC firmware was rebooted with the following reason: ID Button.
  • nkut

    1 Rookie

    •

    23 Posts

    3550

    0

    Posted December 20th, 2018 06:00

    Up to now there are no new error messages in iDRAC log about BMC reboot.

  • nkut

    1 Rookie

    •

    23 Posts

    3467

    0

    Posted December 24th, 2018 07:00

    Returning "Front Panel Access" into "Full capabilities" triggers RAC0182 "The iDRAC firmware was rebooted with the following reason: ID Button" message. So it seems the problem is in Front Panel. The only thing left is to understand what can be done to fix it. I guess another way is to keep Front panel locked out and manage that server via iDRAC. I would appreciate any advice on our further steps.
  • Dell-DylanJ

    6 Operator

    •

    2924 Posts

    3423

    0

    Posted December 26th, 2018 07:00

    I would look at replacing the control panel the button is on. Considering this is a 13G system, you can probably get the part without too much trouble. There are a few different versions of the control panel, so I would recommend going to https://www.dell.com/support, giving it the service tag, then checking the build to see the part number for the control panel.

  • sav_Alex

    3 Posts

    3403

    0

    Posted December 27th, 2018 04:00

    I'll keep in mind. Thank you for your help!

  • nkut

    1 Rookie

    •

    23 Posts

    718

    0

    Posted December 27th, 2018 06:00

    Dear Dylan,

    thanks a lot for your replies and valuable help what let us to locate a source of problem!