Link to home
Start Free TrialLog in
Avatar of mraineynola
mraineynola

asked on

iSCSI Multipath with Hyper-V Core 2012 using Powershell

I am a real Powershell newbie and not real familiar with iSCSI either. I have just rolled out my first 2012 server using Hyper-V Core install on a Dell Poweredge server, putting the VM's on a Equallogic SAN. I followed the Step by Step guide here, http://blogs.technet.com/b/keithmayer/archive/2013/03/12/speaking-iscsi-with-windows-server-2012-and-hyper-v.aspx
but I don't think I have it right as far as MPIO is concerned.

On the server I have 4 nics, 2 on the lan subnet and 2 on the iSCSI SAN subnet, lets say the SAN Nics are x.x.40.1 and x.x.40.2. On the Equallogic there are 3 Nics, 1 on the lan for a management interface and 2 on the iSCSI subnet, say x.x.40.10 and x.x.40.20. The Equallogic also has a group member ip address on the iSCSI subnet, x.x.40.15

The 4 server nics and the 3 EQL nics are connected to a GB Switch.

So when I make my New-IscsiTargetPortal -TargetPortalAddress x.x.40.? I can make a connection on any of the 3 40.x addresses on the Equallogic. If I want MPIO to work should I use the group member ip? or do I need to make both of the physical Nics Portals?

If I make the Member IP the iSCSI target, then Enable-MSDSMAutomaticClaim –BusType iSCSI how does it know to use the 2 physical nicsto get there?

And there does not seem to be any command to show what nics are being claimed by MPIO DSM. Do I just have to monitor traffic on the 2 .40 nicks to see that both are being used?

Sorry for the naive newbie questions but the PS learning curve is steep and I have been pouring over the docs for days and this multipath business still remains obscure.
ASKER CERTIFIED SOLUTION
Avatar of kevinhsieh
kevinhsieh
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of mraineynola
mraineynola

ASKER

Thanks, that provided some clarity. I decided to blow away the Hyper-V core install, just too much PowerShell H*ll and installed the Gui with Hyper-V role. Got a lot more clarity about how to MPIO the interfaces in the Gui. Monitoring the nics in the EQL manager and can see that the round robin algorithm is working perfectly.
My experience with Hyper-V is that you don't need to use any PowerShell. Just use config to join the host to the domain and configure basic networking. Hyper-V Manager from a remote system for everything else.