Skip to main content
NetApp Knowledge Base

LUN not reported from SM-as destination cluster

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

Applies to

  • ONTAP 9.16.1P1
  • SnapMirror active sync (SM-as)
  • iSCSI
  • Oracle Linux 8.10

Issue

  • Out of many LUNs, the host does not have paths to SM-as destination cluster nodes
  • SnapMirror relationship is in sync

cluster2::> snapmirror show -fields source-path,type,destination-path,state,status,healthy,lag-time,policy

source-path    destination-path type policy                  state        status healthy lag-time

-------------- ---------------- ---- ----------------------- ------------ ------ ------- --------

ora-1:/cg/cg1  ora-2:/cg/cg1    XDP  AutomatedFailOverDuplex Snapmirrored InSync true    -

  • Reporting nodes are configured correctly:

cluster2::> lun mapping show -vserver ora-2 -path /vol/ora_olvm_oradatastore/lun_ora_olvm_oradatastore_1 -igroup OracleVM

[...]

       Reporting Nodes: cluster2-01, cluster2-02

  • Host reboot and rescan do not work to establish paths

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.