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?
LVL 57
andyalderSaggar maker's bottom knockerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
0
andyalderSaggar maker's bottom knockerAuthor Commented:
No, but that question is using the MS iSCSI initiator, this one just has VMware as the initiator.
0
shanepresleyCommented:
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).
0
Powerful Yet Easy-to-Use Network Monitoring

Identify excessive bandwidth utilization or unexpected application traffic with SolarWinds Bandwidth Analyzer Pack.

andyalderSaggar maker's bottom knockerAuthor Commented:
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.
0
shanepresleyCommented:
The key is that your vmware hosts need to have paths to both controllers.  But I assume they do, since you're seeing 8 paths.  If everything is wired/configured correctly, then forcing ownership back won't have any impact.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
andyalderSaggar maker's bottom knockerAuthor Commented:
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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Server Hardware

From novice to tech pro — start learning today.