This was on the e1000e NIC driver, but we had already swapped down to the e1000. However, this is affect an iSCSI initiated connection to a Nimble volume. I took the risk and swapped back to the e1000e NICs and reset the MPIO, and so far its been running smoothly. also HOST and VMs have since been updated to ESXi 5.5. We did previously have this issue, although not nearly as frequent using the e1000e. It's very odd, considering we have other VMs with the same configurations, and they are nor have ever experienced this issue.
Good Afternoon Sean,
This thread has been open for several months & I'm just checking to see if you have received an answer. I'm not sure if you've seen the alert bulletin on InfoSight pertaining to the e1000 NICs in VMware, but this has been an issue we've tried to communicate to our customers as much & often as possible. Here is a link to that notification: https://infosight.nimblestorage.com/cgi-bin/viewPDFFile?alert=NimbleStorageFieldAlertExt0003.pdf
as well as a link to the corresponding VMware KB Article:
Please let us know if this assists in resolving your issues & please don't hesitate to reach out to our Nimble Storage Support for any additional questions as well.
If you could let us know if your question has been answered by one of the responses, it would be greatly appreciated.
Thank you for your time,
On our File Server, things have been running smoothly, then slowly we noticed our connection to the iSCSI initiated (MPIO script used to setup pathing) Volume dropping. Initially it was only 1/2 then randomly the volume was unavailable until NICs reset or Guest restarted. Now its becoming more frequent, running only about 2 hours before volume is unavailable. Server was originally Windows 2012, but recently changed to 2012 R2 to see is MPIO changes helped. Unfortunately they did not. We have other VMs configured this way that do not have the same issues. One being a SQL Server also running Server 2012 R2 with 3 Volumes connected this way. Against recommendations I am thinking of trying the e1000e to see if its a possible driver related issue. Any thoughts?
Host: ESXi 5.5 - Same problem on 5.1
Server: VMware Guest - Windows Server 2012 R2
2 iSCSI NICs: using e1000 not e1000e 192.168.110.53 and 192.168.210.53
Discovery IP on CS220: 192.168.110.20