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,
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.
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.

When using EqualLogic, install the EqualLogic Host Integration Tools (HIT) from the EqualLogic support site. The HIT Kit allows you to properly configure MPIO and snapshots. All configuration is done against the group IP. You don't ever specifically hit the IP of a NIC unless you have multiple EqualLogic arrays and you need to administer a specific member.

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
mraineynolaAuthor Commented:
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.
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
Microsoft Virtual Server

From novice to tech pro — start learning today.