Hello!
After setting up a test Windows Server 2012 R2 two-node cluster with the following network configuration:
Node1 (computer name = Host1):
Network adapters: 1) Host1-Heartbeat - for access to the host and for the cluster communication
2)iSCSI - for iSCSI target connection
Node2 (computer name = Host2):
Network adapters: 1) Host2-Heartbeat - for access to the host and for the cluster communication2)iSCSI - for iSCSI target connection
...I decided to add the third network adapter to each node for VM usage (I named those adapters "VM"), but inspite of the fact that I was adding VM adapter to Host2 in the exact same manner as to Host1 the results were as follows:
Although we can see "VM" adapter in the Host1's Network Connections window there's no corresponding vEthernet(VM1) netadapter that actually holds all ip settings ("VM" is "empty" on both nodes for it's just a ~virtual switch adapter).
So why adding a network adapter and choosing it for the Hyper-V usage may NOT lead to creating a corresponding vEthernet adapter?
Thank you in advance,
Michael