Skip to main content
NetApp Knowledge Base

Hyper-V hosts cannot access clustered iSCSI LUNs

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

Applies to

  • ONTAP SAN, iSCSI
  • Windows Server Hyper-V with Failover Clustering
  • Microsoft iSCSI initiator configured with target host names
  • Customer DNS

Issue

  • After a change on Windows Hyper-V hosts, VMs go offline
  • Failover Cluster cannot open the clustered disks (Hyper-V data LUNs and the quorum LUN)
  • lun show shows those LUNs online and mapped
  • iSCSI data LIFs are up/up
  • vserver iscsi session show still lists established sessions from hosts that already had connections
  • nslookup of the NetApp iSCSI target host names fails on the affected hosts
  • VMs that already have sessions stay up

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.