Skip to main content
NetApp Knowledge Base

IOM not recognized after partner IOM reboot

Views:
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
HW
Last Updated:

Applies to

  • DS212C
  • DS224C
  • DS460C
  • IOM12B

Issue

  • IOM-A reboot due to software crash

Sat Oct 04 20:27:08 +0800 [node1: storlog_admin: sla.shelf.message:debug]: params: {'type': 'SEVERITY', 'log': 'Thu Jan  1 00:00:00 1970 (    0+00:00:00.192); 02000093; U?; HAL; hal; 04; Module Reboot: Startup type 3-Internal software reset'}
Sat Oct 04 20:27:08 +0800 [node1: storlog_admin: sla.shelf.mod.reboot:notice]: Reboot event reported by module A in shelf: 0b.01.99.1, log: Thu Jan  1 00:00:00 1970 (    0+00:00:00.192); 02000093; U?; HAL; hal; 04; Module Reboot: Startup type 3-Internal software reset

  • AutoSupport report SHELF COOLING UNIT FAILED alert when IOM reboot

Sat Oct 04 20:27:32 +0800 [node1: dsa_worker0: callhome.shlf.fan.warn:error]: Call home for SHELF COOLING UNIT FAILED

  • After IOM-A is rebooted, IOM-B is not recognized in sysconfig -a, but System Storage Configuration still in Multi-Path HA

System Storage Configuration: Multi-Path HA
Shelf 1: DS460-12  Firmware rev. IOM12B A: 0141   B: ----

  • Replace IOM-B or Replace Chassis or Power Cycle shelf will not solve this issue.

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.