BWaring wrote:I realize only NG has access to the actualy support ticket with all the info.... there are 2 physical servers running ESXi 4.0 with redundant NICs through redundant switches with multipath configured attaching to 3 LUNs on the 3100 - so that's 6 total paths. Basically, from the ESX side, it's as though the pair of paths to the LUN on the 3100 are simultaneously removed - there is no other info other than loss of connectivity and the 'inactive' path status. With 4.2.11, all 6 paths - 2 to each LUN - went inactive. Last Sat with 4.2.12, only 1 LUN (2 paths) went inactive. When that happens, CIFS access to to the 3100 is still available - I can see the shares, but Frontview is down and iSCSI to the affected LUN(s) is down. Double press of power does not shut down the 3100; a hard reset is required.
Hardware or software iSCSI on the ESX end? Do you have a classic ESX host in the environment? (There should be a /var/log/vmkiscsid.log file which may give us more information)
I can't talk on behalf of NetGear here, but -generally- if it's hung, it's a hardware error (at least this would be the case if we were talking about ESX, there is enough error checking in the code that it will PSOD), can you run hardware diagnostic on the array itself?
When the ports simultaneously go down, do you see an APD (All Paths Down) state in the ESX host?
Have you engaged VMware on this issue at all, although from what your telling me it seems like an issue on the target side, VMware may still be able to provide assistance/guidance in troubleshooting this for you.
I'm not sure about error correction/handling inside the ReadyNAS, but is there a log file / core dump that can be analyzed to see why the device is 'hung'? I only have the ReadyNAS duo, but it becomes unresponsive at times (During initial replication, also had it lock up due to bad network card drivers on the client side), but it's a home unit, so I kind of expect it.
You mentioned that you have multiple paths from the ESX host to the array, try breaking the vmkernel interfaces onto two separate vSwitches if you haven't already (I've seen clients have multiple vmkernel port groups in the same vSwitch)
Sorry, I can't be of more help here, if the array isn't responding to things like FrontView, other than telling you the last thing the ESX host did, you'll need Netgear support to assist you with the RCA, but if you need help with the VMware logs, I might be of assistance.