Servers3.1 - Implementing Hyper V & Virtual Networks

POLL QUESTION: Which feature allows all traffic on the virtual switch to be sent to the virtual network interface for monitoring purposes? A) Router Guard B) Device Naming C) Port Mirroring D) NIC Teaming

C) Port Mirroring; We're mirroring the port, which is how we can mirror traffic that's going in and out of the actual interface.

What is the purpose of a virtual switch?

A virtual switch is what allows virtual machines to connect to, by adding a virtual network interface to the virtual switch.

What do VM's that are on the same virtual switch, use to communicate with one another?

IP - Internet Protocol JUST LIKE COMPUTERS ON A PHYSICAL SWITCH

POLL QUESTION: Which type of Hyper-V virtual switch represents a virtual network to which only virtual machines can connect? A) External B) Internal C) Production D) Private

D) Private Biggest difference, is that a Private Virtual Switch it not reliant on the Hyper-V role. Whereas, an Internal Switch is completely dependent on the Hyper-V role. Therefore, the question alludes to only VM's being able to connect, not necessarily 'the Server' connecting to this as well.... IT HAS TO BE PRIVATE FOR THIS REASON!

Fill in the blank: If we're creating an external virtual switch, we have to have it connected to an _______ _______ ______.

External physical switch. AKA: WE NEED IT TO CONNECT TO THE PHYSICAL LAYER.

True or False: Windows PowerShell does NOT allow network admins to manage virtual switches.

FALSE 'ExternalVS', is a command we can run in PowerShell, specifying the name of the virtual switch that uses the physical network adapter (Ethernet).

True or False: We can not install Hyper-V using PowerShell or Windows Admin Console

FALSE We CAN install Hyper-V with either PowerShell or the Windows Admin Console.

What does Hyper-V Extensible Virtual Switch protocol being enabled do?

Hyper-V Extensible Virtual Switch protocol allows the Hyper-V ability to share th8e physical network interface with multiple VMs simultaneously. Setting is automatically enabled on a physical network when creating an external virtual switch.

True or false: In order to run Hyper-V, the processor must support Intel VT or AMD-V virtualization extensions with SLAT support.

TRUE - Additionally, there is a Hyper-V role that must be added within Server Manager, to initiate the installation of Windows Server 2019.

What does SR-IOV stand for in virtual environments, and what does it enable?

Single-root I/O Virtualization Allows network interface to work closely with Hyper-V to separate network requests from different virtual machines in order to optimize performance. If physical network interface supports SR-IOV, this option should be enabled for the external virtual switch.

What type of hypervisor is Hyper-V (MS Product)?

Type 1 "Bare Metal" Installation Where we would install the Hypervisor directly on top of the Bare Metal server, to then run virtual Machines on top of.

What is a VLAN?

Virtual Local Area Network A physical switch can be partitioned into separate VLANs, each acting as an independent physical switch. Ensures that network traffic between host OS and physical switch use the correct VLAN identification, which is necessary for network management software.

When enabling live migration during the installation of Windows Server 2019, there are two ways in which the two servers can authenticate with one another during the process. Of the options listed below, select the two below that are two of the applicable authentication methods for servers to leverage during live migration: 1) Credential Security Support Provider (CredSSP) 2) ATP 3) UDP 4) Kerberos

1) CredSSP --> This type of authentication requires that we start the live migration process while logged into the source server as a user with administrative privileges in the domain. 4) Kerberos --> Allows to start a live migration from any computer running Hyper-V Manager within an Active Directory domain, but requires that both computer accounts within Active Directory are configured for constrained delegation.

Why would we want to use private/internal virtual switches?

1) Dev Environments that aren't yet ready for prod, but they're a safe environment for testing. Private network is good for this too.

What are the three types of virtual switches, as defined by Hyper-V?

1) External Virtual Switch --> Represents underlying physical switch, and connects underlying physical network to server running Hyper-V. 2) Internal Virtual Switch --> Represents a virtual network, in which VM's and the hosts OS can connect. 3) Private Virtual Switch --> Represents a virtual network to which on virtual machines can connect

Generally speaking, what is the purpose of a Switch? A) To connect layer 4 devices to layer 3 devices B) To connect layer 1 devices to layer 2 devices C) To connect layer 2 devices to other layer 2 devices (LAN) D) To connect layer 3 devices to layer 2 devices (Internet)

C) To connect devices to network interfaces within each computer on a network, via a network Ethernet cable. In a physical network, this connects devices in a LAN to other devices in the LAN. In a wireless network, this could also come in form of a Wireless Access Point (WAP)

When installing Hyper-V, after adding the Hyper-V role in Server Manager, we can then select one or more network interfaces. What is the purpose of selecting network interfaces?

During this phase, we are telling Windows Server which network interfaces will be providing access to our physical network. Ex: Ethernet, etc.

What is meant by an N-tier architecture?

In a Virtual Network, when we have a physical machine connecting to a VM via an external virtual switch, to then access an additional VM within a Private/Internal switch, the # of systems that implement security measures before gaining access is the value of 'N'. AKA: A front-end user can access a database on VM 2, but they would first have to access VM 3, which within its private virtual network, could access VM Machine 2, which holds a database.

After configuring the network faces the Windows Server Will be leveraging, we then indicate the Live Migration configuration. What does enabling live migration do?

Live Migration allows us to copy a running Hyper-V virtual machine from one server (source server) across a network to another server in the same Active Directory domain (target server).

True or False: If we do not configure live migration during the installation of Hyper-V, we can configure it aftewards.

TRUE It does NOT have to be configured at time of installation, in order to be configured at all.