Skip to main content
NetApp Knowledge Base

VMware host can't detect LUNs or ISCSI paths from new nodes

  1. Last updated
    Oct 4, 2024
  2. Save as PDF
Views:
131
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
san
Last Updated:
10/4/2024, 11:40:44 AM

Applies to

  • ONTAP 9
  • ISCSI
  • VMware7.0.x

Issue

  • ISCSI Luns of newly provisioned nodes are not visible at VMware end.
  • 'Dynamic discovery' from VMware reported alert below
    "iSCSI discovery to <IP address> on vmhbaxx failed. The Discovery target returned a login error of: 0200."
  • The LUN is online and mapped appropriately.
  • Ensure that new node is part of reporting nodes and all ISCSI LIF on storage are pingable to Host VMkernal.
  • ONTAP reports below EMS events,

[?]  Wed Jun 26 10:48:18 +1200 [Cluster-01: iswt_admin_thread: iscsi.warning:notice]: ISCSI: Initiator iqn.1998-01.com.xxxxx does not have access to portal with ip 172.xx.xx.xx
[?]  Wed Jun 26 10:48:42 +1200 [Cluster-01: iswt_admin_thread: iscsi.warning:notice]: ISCSI: Initiator iqn.1998-01.com.xxxxx does not have access to portal with ip 172.xx.xx.xx

Note: ISCSI access lists are configured for the initiator iqn.1998-01.com.xxxxx in ONTAP, however the LIFs from respective reporting nodes are not part of access list.

 

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.