<div>
have you performed a vmkping command to the traget IP? Are you able to get into the management side of the Netapp?
</div>


<div>
Yes connectivity is good as I pinged both ways (regular ping from esxi host to the storage targets)<br />
<br />
When we do a nework interface show we get all the interfaces up/up and we can connect to the Oncommand cluster IP. It's odd that we don't see any interfaces in the network interfaces screen? but we see them when running the command at the command line and are pingable.
</div>


<div>
Perhaps the failover didn't failover the interface properly or the switch configuration is not the same. &nbsp;I would rescan the adapters and datastores. &nbsp;I imagine you're running iSCSI, if so check your initiator groups just in case, I haven't see too many issues with cluster mode but 7 mode was wonky every once in a while. &nbsp;If the LUNs are showing online on the Netapp I'd reboot one of the hosts and try again, this may be session issue, check Netapp for stale sessions.<br><br>Display iSCSI sessions<br>&nbsp; &nbsp; <strong>Availability:&nbsp;</strong>This command is available to <em>cluster</em> and <em>Vserver</em> administrators at the <em>admin</em> privilege level.<br>&nbsp; &nbsp;&nbsp;<h2>Description</h2>This command displays iSCSI session information. If you do not specify the target session ID (TSIH), &nbsp; &nbsp;the command displays all session information for the specified Vserver. If a Vserver is not specified, the command &nbsp; &nbsp;displays all session information in the cluster. Use the <a href="http://docs.netapp.com/ontap-9/topic/com.netapp.doc.dot-cm-cmpr-970/vserver__iscsi__connection__show.html" rel="ugc">vserver iscsi connection show</a> command &nbsp; &nbsp;to display connection information. Use the <a href="http://docs.netapp.com/ontap-9/topic/com.netapp.doc.dot-cm-cmpr-970/vserver__iscsi__session__parameter__show.html" rel="ugc">vserver iscsi session parameter show</a> command to show &nbsp; &nbsp;the parameters used when creating the session. &nbsp; &nbsp;You can use session information for troubleshooting performance problems.<br>&nbsp; &nbsp;&nbsp;An iSCSI session can have one or multiple connections. Typically a session has at least one connection.<br>&nbsp; &nbsp;&nbsp;Most of the parameters are read-only. However, some parameters can be modified with the <a href="http://docs.netapp.com/ontap-9/topic/com.netapp.doc.dot-cm-cmpr-970/vserver__iscsi__modify.html" rel="ugc">vserver iscsi modify</a> command.<br>&nbsp; &nbsp;<br><a href="http://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.dot-cm-cmpr-970%2Fvserver__iscsi__session__show.html" rel="ugc">http://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.dot-cm-cmpr-970%2Fvserver__iscsi__session__show.html</a><br><br>
</div>


<div>
Thanks Paul but basic steps have been tried. This has been a 30 hour outage so far. Trust me reboots have taken place. iqn's haven't changed. The Filer is corrupt. cluster show shows healthy but performing any commands says it's unhealthy and can't perform any tasks. A PCI card had to be reseated during a power outage so this may be why our Network Interfaces in the GUI is not visible yet everythign is pingable. I created another post on creating a new SVM and migrating data to it but if you happen to know how to do that let me know.
</div>


<div>
Sorry to hear that, been through plenty of those calls. &nbsp;I imagine you have Netapp support on the line. &nbsp;Is there any way to get a new &nbsp;controller since the OS is separated from the LUN. &nbsp;If there is corruption of NVRAM or controller itself the data should still be ok since it should be able to scrub WAFL and recreate the metadata if needed. &nbsp;Just a thought..
</div>


snyderkv

<div>
We found the issue.<br />
<br />
Ontap 9.0 has a bug that stops it from functioning correctly when one node is in a giveback state for a long period of time during a power outage. We had to rebuild the bad node in order to fix it. They sent me the article that determined we had the bug.
</div>


<div>
That is strange, typically takeover/giveback is a fairly straightforward process.
</div>


<div>
That's why it's a bug. It. One node must have been down for a long period without us noticing then the power outage strikes then the bug in that order I think. So the surviving node never fully recovers.
</div>


<div>
<div class="content wysiwyg-content">
A remote site had a TCF wide power outage today that bricked NetApp B. But we are still able to ping NetApp A from the ESX hosts. However, after removing the bad Nodes IP from the dynamic discovery tab and re-scanning HBA or even rebooting, we still can't connect or see any datastores.<br />
<br />
Nothing has changed with NetApp besides the hard cycle bricking it's failover partner. The good node sucessfully took ownership of the volumes and luns. Their online and still mapped to the iGroup yada yada. Additionally, when I put the good nodes target IP back into the dynamic discovery, it doesn't automatically populate the static fields. No we're not using CHAP.<br />
<br />
Thanks in advance
</div>
</div>


A remote site had a TCF wide power outage today that bricked NetApp B. But we are still able to ping NetApp A from the ESX hosts. However, after removing the bad Nodes IP from the dynamic discovery tab and re-scanning HBA or even rebooting, we still can't connect or see any datastores.

Nothing has changed with NetApp besides the hard cycle bricking it's failover partner. The good node sucessfully took ownership of the volumes and luns. Their online and still mapped to the iGroup yada yada. Additionally, when I put the good nodes target IP back into the dynamic discovery, it doesn't automatically populate the static fields. No we're not using CHAP.

Thanks in advance

vSphere can't connect to NetApp storage?

Computer data storage, often called storage or memory, is a technology consisting of computer components and recording media used to retain digital data. In addition to local storage devices like CD and DVD readers, hard drives and flash drives, solid state drives can hold enormous amounts of data in a very small device. Cloud services and other new forms of remote storage also add to the capacity of devices and their ability to access more data without building additional data storage into a device.

Storage

vSphere

VMware, a software company founded in 1998,  was one of the first commercially successful companies to offer x86 virtualization. The storage company EMC purchased VMware in 1994. Dell Technologies acquired EMC in 2016. VMware’s parent company is now Dell Technologies.

VMware has many software products that run on desktops, Microsoft Windows, Linux, and macOS, which allows the virtualizing of the x86 architecture.  Its enterprise software hypervisor for servers, VMware vSphere Hypervisor (ESXi), is a bare-metal hypervisor that runs directly on the server hardware and does not require an additional underlying operating system.