Skip to main content
NetApp Knowledge Base

Node panic after ATTO bridge b/88/5/12 errors are reported

  1. Last updated
  2. Save as PDF
Views:
83
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • MetroCluster FC
  • ATTO FibreBridge 7500

Issue

  • Node panic with error:

WAFL hung for aggregate_name. in SK process wafl_exempt02 

  • ATTO FibreBridge reporting 0B880512 in dumpeventlog all
  • ONTAP event log shows lots of scsi.cmd errors:

[NodeA:scsi.cmd.checkCondition.bridge.SAS.reset:debug]: Disk device 3a.125L5: Sense Data SCSI:aborted command - (0xb - 0x88 0x5 0x12)

  • shm.threshold.ioLatency reported for disks through the other ATTO bridge, connected to the same shelf stack

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.