Dedicated Management Port on Hyper-V 2012 with the same subnet in a cluster?



if setting nics hyper-v 2012 in cluster understand following best practices should be adhered to:-

1x hearbeat
1x csv
1x live migration
1x dedicated management port (set via check box in virtual switch manager?)
1x dedicated nic vm traffic

the internal production lan runs on 10.0.1.x , 10.0.2.x, gateway 10.0.1.254.

now if configure virtual switch for lan using address 10.0.1.10, new virtual switch created "allow management operating system share network adapter" setting set.

if configure dedicated nic management on either 10.0.1.11 or 10.0.2.12 gateway of 10.0.1.254 multi-home problem - don't want virtual switch dedicated management port  but if don't create virtual switch how can ensure dedicated nic management isn't used hyper-v , how can avoid multi-home issue there 2 network adapters on same sub-net or same gateway?

if want dedicated nic host management, not create virtual switch on nic.  without virtual switch, no vms have access nic.

you not subnet mask on networks, if using 10.0.1.254 gateway both 10.0.1.x , 10.0.2.x network, means on same subnet, giving multi-home environment if put 2 nics on of networks.

for describing, need single virtual switch dedicated vm traffic.  not check box management os access on switch, , host not 'see' nic on network.  sounds trying create switch on management network - not needed.


tim



Windows Server  >  Hyper-V



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file