Skip to main content
NetApp Knowledge Base

SM-as destination LUN not mapped despite replicated host configuration

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

Applies to

  • ONTAP 9
  • SnapMirror active sync (SM-as)
  • All-flash SAN Array r2 (ASA r2)
  • SAN

Issue

  • Destination LUN of SM-as relationship is unmapped
  • Host configuration replication is enabled on the igroup
  • Mapping the LUN to the destination igroup manually is not possible as it is already mapped on source SVM and host configuration replication is enabled:

dest_cluster::> lun mapping create -vserver dest_svm1 -lun lun1_dst -igroup igroup1

Error: command failed: Creation of a replicated LUN map failed in peer Vserver "src_svm1". Reason: LUN already mapped to this group

  • When initial LUN mapping was created, SnapMirror was out-of-sync for multiple days because of intercluster communication issue
  • bcomd logs show LUN mapping timed out:

INFO: SAN::KACOMM::KADISPATCH: src/ka_communication/kaDispatch.cc:dispatch:1048 did: 2be281 - command dispatch to node dest_cluster-03 result: (19/9168) Cannot modify the LUN or NVMe namespace: The LUN or NVME namespace is busy. Retry the command later.

CRIT: bcomd::AsyncQueue: src/async_queue/AsyncQueue.cc:run:110 Expired without success

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.