About BMC log active:#0 inactive:#0

[xuanchel]

Hi team

I have a question about BMC log.

Model is FAS8300 and when i check the SP-LATEST-STATISTICS log i found a watchdog timeout error.

SP-LATEST-STATISTICS

    IPMI_Main.c main start 9.58 7.74
    IPMI_Main.c main after sync time 12.51 9.88 Mon Apr 18 05:28:34 GMT 2022
    BMC init unknown:Mon Apr 18 05:28:44 GMT 2022
    GPIO boot       : Primary
    Physical slot   : #1
    Primary env     : active:#1 inactive:#1
    Last boot error : None
    
    IPMI_Main.c main start 11.48 7.53
    IPMI_Main.c main after sync time 14.91 10.57 Wed Sep 28 08:35:16 UTC 2022
    BMC init unknown:Wed Sep 28 08:35:37 UTC 2022
    GPIO boot       : Primary
    Physical slot   : #0
    Primary env     : active:#0 inactive:#0
    Last boot error : HW watchdog timeout happened last time! Try to update your inactive flash again!
    

First IPMI main start history showed no error and   Primary env showed active:#1 inactive:#1

But when it comes to the second history there was watchdog timeout error and primary env showed active:#0 inactive:#0

What does this active:#0 inactive:#0 in Primary env mean?

Best Regards,

Xuanchen Li

[Ontapforrum · Accepted solution]

I would suggest - Please raise a ticket with NetApp Technical Support and have them review logs to determine what caused it. As a best practice, ensure the firmware for BMC/SP is up to date. Following kb has more information around how to collect the logs.

https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Systems/FAS_Systems/What_is_a_Baseboard_Management_Controller_(BMC)_and_how_do_I_use_it%...

Related kb:
https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Systems/FAS_Systems/FAS8300_reboot_due_to_Watchdog_2_Timer_expired_(OEM)