Well, it looks as though the problems in the first run through were indeed driver related as well as process (which step goes before which) related:
We enabled the MPIO feature on the Hyper-V nodes after installing the updated drivers for both the Adaptec (which comes up unsigned despite Adaptec’s indicating they are) and the Intel SAS module.
- Driver install command line:
- pnputil –i –a Adaptec.inf
- pnputil –i –a IntelSAS.inf
- MPIO feature enable (TechNet):
- Dism /online /enable-feature:MultipathIo
- Note that this command is case sensitive.
- MPIO capture disks after reboot (TechNet):
- mpclaim –n –i –a
- Grab all of those disks
- mpclaim –l –m 4
- Set load balancing mode to “Lease Queue Length”
- mpclaim –s –d
- Shows the current load balancing mode:
New to Windows Server 2008 R2 SP1 Core and thus Hyper-V Server 2008 R2 SP1 is the MPIO Control Panel:
Once we go through and configure the MPIO based storage there are a few more steps to take to configure and test the networking and then we will stand the cluster up.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book