campinam
asked on
Hyper-V virtual switch card config
This server host is 2012r2, as well as all its (not installed yet) VMs the same. It has multiple network cards.
I installed the host and configured all network adapters with static IPs.
Then I installed Hype-V role and checked a physical card for each of the VMs, leaving the rest for the host.
Now each checked card is linked to a virtual switch created automatically.
Then I go to Virtual Switch Manager and uncheck the "Share with host..." for each switch, so that its card is used exclusively by its VM.
But...
Now if I go to properties of such a "switch" card (on the host), I don't have access anymore to network properties (IP, mask, etc.). Only the Hyper-V is checked, and the rest cannot be accessed.
Anyone can explain why?
Shouldn't one be able to configure the card? I understand that connecting to the VM will use the address of the virtual NIC... but does this mean the physical card has no address at all?? I thought the physical card is like an uplink to the switch, am i wrong?
I installed the host and configured all network adapters with static IPs.
Then I installed Hype-V role and checked a physical card for each of the VMs, leaving the rest for the host.
Now each checked card is linked to a virtual switch created automatically.
Then I go to Virtual Switch Manager and uncheck the "Share with host..." for each switch, so that its card is used exclusively by its VM.
But...
Now if I go to properties of such a "switch" card (on the host), I don't have access anymore to network properties (IP, mask, etc.). Only the Hyper-V is checked, and the rest cannot be accessed.
Anyone can explain why?
Shouldn't one be able to configure the card? I understand that connecting to the VM will use the address of the virtual NIC... but does this mean the physical card has no address at all?? I thought the physical card is like an uplink to the switch, am i wrong?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Team two ports, preferably on different physical NICs, and bind a static IP to that team. That's your management access.
Then, create at least one more team for the virtual switch (vSwitch). We prefer to _not_ share this team with the host OS just as you have. The TCP/IP stack gets completely hidden to the host OS. This is as it should be.