> Have couple of questions regarding Hyper-V, I'll be using initially 3
> exactly
> same HP DL360 G5 (each server: 8GB RAM, dual quad core proc, SAS 2.5 HD
> config as RAID 1 + spare standby, 4 NICs) All with Win 2008 Ent Edition.
> For
> VMs storage I'm using iSCSI HP SAN (4TB RAID6). 2 NICs from each server
> are
> connected 2 isolated networks for iSCSI network failover HP SAN had 2
> controllers for auto failover, 3rd NIC for LAN and 4th NIC for VMs
> communication, here is my first question why do I need to have dedicated
> NIC
> for VMs communication? this is one I'm asked to select while installing
> Hyper-V. Also since VMs have to communicate with LAN can I share same NIC
> which connects Host server OS with LAN and for Hyper-V?
>
> second question, since iSCSI initiator is build into Windows 2008 server
> vs.
> used to be download/install piece of software in W2k and W2k3 how can I
> tell
> what version of iSCSI initiator is used in Windows 2008 x64 ? Latest
> released
> iSCSI initiator by MS is 2.07 and I think latest tested and supported by
> HP
> SAN I'm using is 2.03
>
> TIA

> What I didn't see in your scenario is the use of Failover Clustering to gain
> High Availability for your VMs...have you considered that?
>
> Also, more RAM and more NICs = Happier VMs. :-)
>
> --
> Ryan Sokolowski
> MVP - Clustering
> MCT, MCITP x3, MCTS x7, MCSE x2, CCNA, CCDA, BCFP
>
>
> "RW" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Have couple of questions regarding Hyper-V, I'll be using initially 3
> > exactly
> > same HP DL360 G5 (each server: 8GB RAM, dual quad core proc, SAS 2.5 HD
> > config as RAID 1 + spare standby, 4 NICs) All with Win 2008 Ent Edition.
> > For
> > VMs storage I'm using iSCSI HP SAN (4TB RAID6). 2 NICs from each server
> > are
> > connected 2 isolated networks for iSCSI network failover HP SAN had 2
> > controllers for auto failover, 3rd NIC for LAN and 4th NIC for VMs
> > communication, here is my first question why do I need to have dedicated
> > NIC
> > for VMs communication? this is one I'm asked to select while installing
> > Hyper-V. Also since VMs have to communicate with LAN can I share same NIC
> > which connects Host server OS with LAN and for Hyper-V?
> >
> > second question, since iSCSI initiator is build into Windows 2008 server
> > vs.
> > used to be download/install piece of software in W2k and W2k3 how can I
> > tell
> > what version of iSCSI initiator is used in Windows 2008 x64 ? Latest
> > released
> > iSCSI initiator by MS is 2.07 and I think latest tested and supported by
> > HP
> > SAN I'm using is 2.03
> >
> > TIA
>

> Thanks Ryan for your comments, yes I was thinking about HA via clustering
> either on the physical layer (host servers) or virtual (guest servers) or
> combination of both. Question about phisical hosts clustering, lets say it
> is
> 2 node cluster PH1 and PH2, there is 10 VMs on shared iSCSI sorage both
> PH1
> and PH2 servers accessing same LUN where VMs are stored, while both are up
> can 5 VMs utilize CPUs, RAM resources of PH1 and other 5 VMs CPUs, RAM of
> PH2
> ? and in case of one node failure VMs are failing to second node and
> temporairly single Host is managing all 10 VMs? or clustering of Hyper-V
> is
> strictly Active - Standby sytuation where one node is managing all VMs and
> other host does nothing?
>
> regarding your second comment more RAM is self expalnatory, but how would
> I
> utilize more NICs and what I'm gaining? I guess this is ore of the
> design/concept question should this NICs for VM be in the same network as
> host (LAN) should these be in another network isolated from LAN, what
> acctually are these use for?
>
> RW
> MCSE, MCDBA, MCITP, OCA, CCA, LCP, VCP
>
> "Ryan Sokolowski [MVP]" wrote:
>
>> What I didn't see in your scenario is the use of Failover Clustering to
>> gain
>> High Availability for your VMs...have you considered that?
>>
>> Also, more RAM and more NICs = Happier VMs. :-)
>>
>> --
>> Ryan Sokolowski
>> MVP - Clustering
>> MCT, MCITP x3, MCTS x7, MCSE x2, CCNA, CCDA, BCFP
>>
>>
>> "RW" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > Have couple of questions regarding Hyper-V, I'll be using initially 3
>> > exactly
>> > same HP DL360 G5 (each server: 8GB RAM, dual quad core proc, SAS 2.5 HD
>> > config as RAID 1 + spare standby, 4 NICs) All with Win 2008 Ent
>> > Edition.
>> > For
>> > VMs storage I'm using iSCSI HP SAN (4TB RAID6). 2 NICs from each server
>> > are
>> > connected 2 isolated networks for iSCSI network failover HP SAN had 2
>> > controllers for auto failover, 3rd NIC for LAN and 4th NIC for VMs
>> > communication, here is my first question why do I need to have
>> > dedicated
>> > NIC
>> > for VMs communication? this is one I'm asked to select while installing
>> > Hyper-V. Also since VMs have to communicate with LAN can I share same
>> > NIC
>> > which connects Host server OS with LAN and for Hyper-V?
>> >
>> > second question, since iSCSI initiator is build into Windows 2008
>> > server
>> > vs.
>> > used to be download/install piece of software in W2k and W2k3 how can I
>> > tell
>> > what version of iSCSI initiator is used in Windows 2008 x64 ? Latest
>> > released
>> > iSCSI initiator by MS is 2.07 and I think latest tested and supported
>> > by
>> > HP
>> > SAN I'm using is 2.03
>> >
>> > TIA
>>