跳转到主内容

在BMC 15.10上、A250 BMC检测信号丢失且节点无响应

Views:
9
Visibility:
Public
Votes:
0
Category:
aff-series
Specialty:
HW
Last Updated:

适用场景

  • AFF A250
  • AFF C250
  • ASA A250
  • ASA C250
  • FAS500f
  • BMC 15.10

问题描述

  • 节点意外重新启动 、并出现EMS错误: 

[?]  Fri Nov 17 13:10:28 +0100 [NodeName: spmgrd: sp.heartbeat.stopped:error]: Have not received a IPMI heartbeat from the Service Processor (SP) in last 600 seconds.
[?]  Fri Nov 17 13:21:27 +0100 [NodeName: spmgrd: sp.heartbeat.stopped:error]: Have not received a IPMI heartbeat from the Service Processor (SP) in last 600 seconds.
[?]  Fri Nov 17 13:21:27 +0100 [NodeName: spmgrd: callhome.sp.hbt.missed:notice]: Call home for SP HBT MISSED
[?]  Fri Nov 17 13:31:46 +0100 [NodeName: spmgrd: callhome.sp.hbt.stopped:alert]: Call home for SP HBT STOPPED

[?]  Fri Nov 17 13:34:07 +0100 [NodeName: env_mgr: sp.ipmi.lost.shutdown:EMERGENCY]: SP heartbeat stopped and cannot be recovered. To prevent hardware damage and data loss, the system will shut down in 10 minutes.
[?]  Fri Nov 17 13:44:07 +0100 [NodeName: env_mgr: monitor.shutdown.emergency:EMERGENCY]: Emergency shutdown: Environmental Reason Shutdown (System reboot to recover the BMC)
[?]  Fri Nov 17 13:44:08 +0100 [NodeName: mgwd: mgwd.notify.halt.result:info]: MGWD able to notify CLAM on its HA partner node that this node is undergoing a planned shutdown (reason: E). Error: -

  • 从BMC事件日志中、有一个先导FPGA交流周期、之后会出现大量可更正的总线错误: 

1c5 | OEM record f2 | FPGA pull BMC whole reset
1c6 | OEM record f2 | Pilot FPGA AC cycle
1c7 | 11/17/2023 | 12:50:16 | Power Supply #0x20 | Presence detected | Asserted
1c8 | 11/17/2023 | 12:50:16 | Power Supply #0x25 | Presence detected | Asserted
1c9 | 11/17/2023 | 12:50:17 | Power Supply #0x72 | Presence detected | Asserted
1ca | 11/17/2023 | 12:50:17 | Power Supply #0x73 | Presence detected | Asserted
1cb | 11/17/2023 | 12:50:19 | Battery #0x4a | State Deasserted
1cc | 11/17/2023 | 12:50:19 | Battery #0x4b | State Asserted
1cd | 11/17/2023 | 12:50:19 | Battery #0x4c | State Asserted
1ce | 11/17/2023 | 12:50:19 | Battery #0x4d | State Deasserted
1cf | 11/17/2023 | 12:50:19 | Battery #0x4f | State Deasserted
1d0 | 11/17/2023 | 12:50:19 | Other FRU #0x50 |
1d1 | 11/17/2023 | 12:50:19 | Other FRU #0x50 |
1d2 | 11/17/2023 | 12:50:19 | Other FRU #0x50 |
1d3 | 11/17/2023 | 12:50:19 | Other FRU #0x50 |
1d4 | 11/17/2023 | 12:50:36 | Critical Interrupt #0x31 | Bus Correctable error | Asserted
1d5 | 11/17/2023 | 12:50:36 | Critical Interrupt #0x31 | Bus Correctable error | Asserted
1d6 | 11/17/2023 | 12:50:36 | Critical Interrupt #0x31 | Bus Correctable error | Asserted
1d7 | 11/17/2023 | 12:50:36 | Critical Interrupt #0x31 | Bus Correctable error | Asserted

 

 

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.