Skip to main content
NetApp Knowledge Base

CONTAP-739683: SVMDR fails with Apply failed for Object: nvmf_subsystem_map Method: remove_crs. Reason: There is no subsystem named

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

Issue

SVMDR vserver update fails: "Apply failed for Object: nvmf_subsystem_map Method: remove_crs [or add]. Reason: There is no subsystem named <subsystem> in Vserver <uuid>"
AND snapmirror show output on destination shows Snapmirrored/Idle with is-healthy=FALSE while all constituent PVC volumes remain healthy=true
AND source EMS shows wafl.vvol.destroyed for NVMe-namespace-containing PVC volumes (LUN.nvfail.option.on) between last-good and next SVMDR update
AND no EMS event fires on either node for the failure itself;
visible only via last-transfer-error in snapmirror show output

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.