Question

Windows Server Configuration

I don't even understand this can someone please help?

Respond to the following in a minimum of 175 words:

• You need to ensure that VM1 and VM2 can communicate with each other only. The solution must prevent VM1 and VM2 from communicating with Server1. Which cmdlet should you use and why?

Answer 1

Set-VMSwitch cmdlet is used.

It allows an administrator to configure a virtual switch.

Hyper-V virtual network adapters enable communications between VM1 and VM2 through a virtual switch. However, newly created VMs do not have any virtual switches assigned to them. Each new VM has a network adapter, which can be configured by assigning a single virtual switch, or you can leave it disconnected. Thus, to enable network connectivity, you need to create a virtual switch and configure a virtual network adapter.

There are three virtual switches that provide different levels of network connectivity:

    An external virtual switch can connect to the physical network adapter, which allows VMs to access a physical network. An external virtual switch enables communications between VMs on the same physical computer, VMs and the physical computer, as well as enables VMs to access physical network.
    An internal virtual switch enables communications between the VMs running on the same Hyper-V server, as well as between those VMs and the management OS. However, this type of switch does not provide access to a physical network.
    A private virtual switch only ensures connectivity between the VMs that run on the same Hyper-V host. This type of network provides an isolated mode of network connectivity.

The Hyper-V Private switch allows VMs to communicate to each other ONLY when they are on the same host. The Private virtual switch cannot communicate to any network outside of the host either. It is important to note the Private virtual switch can communicate to other VMs on one host only. They can't connect to any outside network unless the VM(s) in question are connected to additional virtual switches (such as one Private and one external). A host can have multiple Private switches and the same Private switch name can exist on multiple hosts.

The Hyper-V Internal switch is a bit different in that the VMs on the switch can communicate to each other, but additionally can communicate to the Hyper-V host itself. This can commonly be used as a file exchange mechanism. The internal switch for the most part functions the same as the Private switch, with the added ability to communicate directly to the Hyper-V host.

It is important to note that both the Internal and Private switch types are not bound to a physical network interface. As such, there is "authoritative" network addressing scheme that is set by the host. In the case of the Private virtual switch, the host has no real concern what happens on the virtual switch. This means that the networking (IP addressing) needs to be set by the VMs on the Private network.