Skip to main content
NetApp Knowledge Base

Disk redundancy failed due to failed NSM

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

Applies to

  • ONTAP 9
  • NS224 shelf

Issue

  • Disk redundancy failed due to failed NSM
[Node-01: start_asup_collector_thread: callhome.dsk.redun.fault:error]: Call home for DISK REDUNDANCY FAILED
[Node-01: start_asup_collector_thread: shelf.config.tospha:info]: System has transitioned to single path HA attached storage
  • NoPathToNSMA_Alert
[Node-01: nchmd: hm.alert.raised:alert]: Alert Id = NoPathToNSMA_Alert , Alerting Resource = 530670491063066624 raised by monitor node-connect
  • Ports connected to the failed NSM reports down in both Nodes
Node-01
slot 0: Dual 40G/100G Ethernet Controller CX5
  e0c MAC Address:    d0:39:ea:97:28:11 (auto-unknown-fd-down)
      QSFP Vendor:         Amphenol
      QSFP Part Number:    112-00573
      QSFP Serial Number:  APF22199567575
Node-02
e0d MAC Address:    d0:39:ea:97:2a:dc (auto-unknown-fd-down)
      QSFP Vendor:         Amphenol
      QSFP Part Number:    112-00573
      QSFP Serial Number:  APF22199567486
  Device Type:        CX5 PSID(NAP0000000005)
  Firmware Version:   16.26.4012
 
  • NSM still shows as failed even after performing reseat
 

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.