Skip to main content
NetApp Knowledge Base

CFBMC-2191: AFF A900, FAS9500: Communication failures with multiple sensors results in environmental shutdown

  1. Last updated
  2. Save as PDF
Views:
19
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
HW
Last Updated:

Issue

On AFF A900 and FAS9500 systems, communication failures with multiple sensors can result in environmental shutdown. The communication failures occur when the Controller Area Network (CAN bus) manager on the Baseboard Management Controller (BMC) can no longer access the CAN bus due to a transient failure of a previous "unlock" operation of the CAN bus.

The BMC might have previously rebooted to recover from this condition, as indicated by this example event in the BMC system event log:
Record 538: Tue Aug 02 05:53:45.994305 2022 [BMC.critical]: Rebooting BMC due to CAN skt error

Also, events similar to the following are seen in the BMC's messages log:
Aug 16 08:09:53 (none) canbusmngr2can2can3[1099]: [1099 : 1104 CRITICAL][semaph.c:433]semtimedop error
Aug 16 08:09:53 (none) canbusmngr2can2can3[1099]: [1099 : 1104 CRITICAL][ipc.c:319]Waiting for semaphore failed
Aug 16 08:09:53 (none) canbusmngr2can2can3[1099]: [1099 : 1104 WARNING] mutex.c:335]gm_lock_mutex(key=37, timeout=15000) : mutex_lock_recursive() FAILED!

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.