Hyper-V Win 2012 Clusetring with NIC teaming?

hello all,

hope of fine , doing well.

i have 2 x physical server win 2012. 1 server has 4 nics , second has 2 nics.

i created nic teaming on 2 servers following:

1st server: 3 physical nics in 1 team

2nd server: 1 physical nic in 1 team

the remaining physical nic reserved iscsi storage.

after created new virtual nics nic teaming (using powershell) on every server following:

three virtual nics on every server (one management, 1 cluster , 1 migration), configured these 3 new virtual nics  static ip address , every 1 on different subnet (the management on subnet, cluster on different subnet , migration on different subnet)

after created 2 new vlan using powershell , every 1 has unique id, 2 vlans for: 1 cluster subnet , 1 migration subnet.

i able add storage hyper-v nodes, 2 nodes joined domain.

now problem can't ping between cluster interfaces!! can tell me should check?

regards,

i think going have give clearer description of environment.  on first server have total of 4 physical nics , 3 physical nics in 1 team.  remaining nic used iscsi.  configured 3 virtual nics.  way create 3 virtual nics on 2 physical nics if created @ least 1 of them internal or private virtual switch.  and, since 1 nic reserved iscsi, mean created 3 virtual nics 1 physical nic (the three-member team) available.  again, way possible have @ least 2 internal or private.  internal virtual switches allow communication between virtual machines , host on virtual machines running.  cannot reach across network other systems.  private virtual switches allow communication among virtual machines running on same host, not allowing communication host on virtual machines running.

with 4 nics , iscsi shared storage, have limited options.  should have 2 physical nics iscsi.  can one, creates single point of failure in storage access.  should have single nic dedicated accessing physical host.  should have single nic cluster shared volumes.  should have single nic live migration.  and, should have single nic accessing virtual machines.  and, argue single nic cluster communications.  adds 7 nics best practices.

so can do?  let's go single nic dedicated iscsi.  should not configured virtual switch unless want clustering of virtual machines.  leaves 3 nics.  team 2 of them , create external virtual switch , use cluster functions - cluster communication, csv, live migration, , vm access.  , save last physical nic use host.

btw, post seems eerily post answered couple days ago.

---

tim

Windows Server  >  Hyper-V