Unsolved
This post is more than 5 years old
1 Message
0
1535
August 31st, 2012 14:00
Windows Hyper-V Cluster & VNXe SP Failover
I've got a two node Hyper-V cluster running on Windows 2008R2 SP1 and a VNXe 3100 with dual storage processors. I'm using MPIO and PowerPath, and have made the configuration changes, registry edits, etc. as specified in the EMC documentation for VNXe, Hyper-V and Windows Servers.
My problem is that when I have a storage processor failover (software update, reboot, service mode, etc), the cluster is disconnected from the iSCSI server on the failed storage processor, and does not failover to the redundant SP. The hosts queue I/O until the drive is disconnected. This forces the VM's offline, resulting in unwanted downtime. The SP does actually failover, but not before my VM's die.
I found reference to emc289415 on https://community.emc.com/thread/132151, but I don't know where this document resides. It describes my problem, but has no solution.
Has anyone out there run into this and/or found a solution?
LouisLu
161 Posts
0
September 4th, 2012 03:00
The emc289415 is primus ID. You can search it by primus iview. It demostrates there is a permanent fix included in MRS3SP1 release. It should resolve known problem on VNXe connecting to windows cluster servers. Is the document you refer?
Ben186
10 Posts
0
May 6th, 2013 20:00
I'm trying to get a little more info on this as I seem to be having the same issue. So how do you search Primus? Is that something I need to request access to? Not really getting anywhere with searches.