Member_2_231077
asked on
MD3000 virtual disk not on preferred path
Had a controller lockup on an MD3000 (might have been MD3000i). Controller has been fixed and both are working, however now getting warning that virtual disks are not on preferred paths. Should I tackle it through VMware or through MD3000 DS manager? It's VMware 5.x with 5 clustered hosts. Also there's 8 paths seen by the hosts, isn't that more than would be wanted?
ASKER
No, but that question is using the MS iSCSI initiator, this one just has VMware as the initiator.
That's normal after a controller failover. You handle that through the MDSM software (not vmware). As for number of paths, that depends on how you have your hosts and controllers connected. But no -- that doesn't seem abnormal (we have 10).
ASKER
VMware's not going to time out when we force the ownership back to the preferred controller? Just that the HP MSA2000 takes up to 1 minute for a path failover although admittedly it's not LSI Engenio based.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Failover didn't affect VMware (apart from slow I/O due to write cache being disabled with a faulty controller) so I'll accept that forced failback won't hurt it either.
https://www.experts-exchange.com/questions/28154405/Virtual-Disk-not-on-preferred-path-due-to-AVT-RDAC-failover-on-MD3000i-Storage-Array.html