Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a clustered Hyper-V environment with four nodes and three PowerVault MD3xxx storage arrays for shared storage.

The servers are using standard Ethernet connections for the iSCSI fabric (not HBAs). MPIO is configured via the Dell storage wizard.

The problem that I seem to be having is that upon rebooting a node, the Ethernet connections seem to be taken down before the iSCSI initiator is ready for it - so the connectivity to any of the LUNs that it happens to own is lost unexpectedly.

Is there a way of preventing this so that a shutdown will be more graceful? In future I will be making sure that a node that is going to be rebooted has any storage it owns shifted to another node first, but I was wondering if this should really happen automatically.

share|improve this question
add comment

1 Answer

To answer the question - yes this should happen automatically. I have an estate with a number of Hyper-V servers, MD3xxxi arrays, etc. and have not seen an issue with rebooting nodes.

However, what is the error or issue you are seeing on a shutdown that makes you say "lost unexpectedly" ?

Also, how are you presenting the shared storage? Is it a CSV or are the LUNs shared between VMs that are in a windows cluster? (I note you have tagged mscs).

share|improve this answer
    
Thanks for your reply! It's a Hyper-V cluster with three LUNs configured as CSVs (and a witness disk as a regular LUN). I'll update my question with some more information that might explain things better - might take me a little while as I'll need to go back through the event logs so I might not get chance for a day or two. Thanks again! –  Chris McKeown Aug 3 '12 at 18:45
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.