2008 R2 Hyper-V Cluster / Dell MD3200i / iSCSI Configuration

[adamf]

I'm trying to add 2 additional nodes to our Hyper-V cluster (it currently has 2 nodes) and I am running into problems with the iSCSI configuration. The storage is a Dell PowerVault MD3200i and everytime I create multiple connections to storage I end up with the Access LUN appearing in Disk Management within Windows (Disk 4 in the screenshot). As far as I am aware the Access LUN is something to do with in-band management of the SAN.

 

 

On the 2 nodes currently in production this LUN doesn't appear and I can't work out what I have done differently. I've installed the MPIO feature, configured it and subsequently un-installed/re-installed so many times as I was sure that was the cause of the problem, but I'm still not getting anywhere.

 

Having that LUN appear in Disk Management is causing a problem with Cluster Validation because it is expected to be on the other nodes which it isn't.

 

Anybody know why it's appearing and where I am going wrong?

[Psymon]

When you did an autodiscover on the iSCSI configuration it must have picked up this drive as available - you should be able to remove it from the iSCSI Initiator. It should appear under "Discovered Targets" which you can disconnect it, it's also likely to be present in "Volumes and Devices".

 

Simon

[Rozzer]

Have you mapped the luns to the hosts on your MD3200i?

 

Ross