Hyper-V Server Virtual Switch

The Windows Server 2012/r2 Hyper-V Virtual Switch (vSwitch) introduces a number of user-requested features to enable tenant isolation, communication shaping, preventing malicious virtual machines, and more easily troubleshooting problems. This guide focuses on improvements in open scalability and manageability of non-Microsoft extensions. You can write non-Microsoft extensions to emulate the full functionality of hardware-based switches and to support more complex virtual environments and solutions.

Hyper-V VSwitch is a 2nd-tier virtual network switch that programmatically provides management and extension capabilities to connect virtual machines to a physical network. VSwitch provides policy enforcement for security, isolation, and service levels. By supporting the Network Device Interface Specification (NDIS) filter driver and the Windows Filtering Platform (WFP) callout driver, Hyper-V VSwitch allows non-Microsoft extensible plug-ins that provide enhanced networking and security features.

Hyper-V VSwitch allows you to implement and manage virtualized datacenters by providing the following:

1. Open platform. VSwitch is built on an open platform that allows independent software vendors to add or extend functionality that is natively available in VSwitch. The functionality of VSwitch is run with the extended functionality added.

2. Standard API. The programming model for the extensible switch uses the same application programming interface (API) as the API for network filters and drivers in earlier versions of Windows, namely, NDIS and WFP. Added new APIs and parameters for the virtual Switch port.

3. Windows reliability and quality. The Windows platform and the Windows Hardware Quality logo (WHQL) program set a higher standard for extended quality.

4. Policy and configuration integration. Extended administration provides standard management methods by integrating Windows Management Instrumentation (WMI) calls and Windows PowerShell cmdlets into Windows management. During a live migration, the scaling policy is automatically migrated along with the virtual machine configuration.

5. Easy to troubleshoot problems. VSwitch comes with event logs and unified tracking, which is easier to diagnose and troubleshoot when a problem occurs.

Shows Hyper-V VSwitch Architecture and extensibility

650) this.width=650; "height=" 545 "title=" clip_image001 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image001 "src=" http://s3.51cto.com/wyfs02/ M00/58/a5/wkiom1s2c3-aozjaaafcr4smkjw204.jpg "border=" 0 "/>

Hyper-V comes with three virtual switch modes, internal and private, from the earliest 1.0 eras, which are created using Hyper-V Switch manager or created through PowerShell or SCVMM.

1. External: After the Virtual Switch deployment is complete, the virtual machine and the host are connected to the same virtual switch. The virtual machine obtains the IP address of the same segment as the host, communicates with other computers on the same network as the host, and each virtual machine is equivalent to a host on the same network as the host.

650) this.width=650; "height=" 401 "title=" clip_image003 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image003 "src=" http://s3.51cto.com/wyfs02/ M01/58/a5/wkiom1s2c3_jit6saaeacats4zm796.jpg "border=" 0 "/>

When an external virtual network switch is created, the data flow on the Hyper-V host changes. By default, the Windows Server operating system uses a physical network adapter to send network packets. This is because the network service needs to use a physical network adapter that binds the network protocols and services. All network packets are generated by the Network Service/application received by the switch. Once the external virtual network switch receives the network packets, the packets are forwarded to the mapped physical network adapter.

This is because when an administrator creates an external virtual network switch, the Virtual Switch manager modifies some of the necessary properties for the physical network adapter and the external virtual network switch. Before the virtual Switch manager implements the changes, the administrator sees a warning message as shown in the following screen:

650) this.width=650; "height=" 213 "title=" clip_image004 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image004 "src=" http://s3.51cto.com/wyfs02/ M02/58/a5/wkiom1s2c4dylg9vaaeru8tjaa8504.jpg "border=" 0 "/>

The warning in the figure indicates that the Hyper-V host connection failed. You will not see such a warning when you create a private or internal virtual network switch. The above prompts are only available when you create an external virtual network switch. This is because changes are handled during the creation process, including binding and binding of protocols, services, and customer services.

For example, an administrator creates an external virtual network switch named "LAB" and maps it to a physical network adapter named "Intel (R) 82576 Gigabit Dual Port Network". When you click the OK button, the properties of the physical network adapter change as follows:

1) Unbind the following services, protocols, and customers: Microsoft network client, Microsoft Network file and printer share, TCP/IP protocol IPV4, TCP/IP protocol IPV6, and all other services, clients, or protocols listed in the physical network adapter properties.

2) Bind "Microsoft Virtual Network Switch Protocol".

Additionally, the following changes occur in the external virtual network switch:

1) Bind the following services, protocols, and clients: Microsoft network client, Microsoft Network file and printer share, TCP/IP protocol IPV4, TCP/IP protocol IPv6.

2) Unbind "Microsoft Virtual Network Switch Protocol".

The Microsoft Virtual Network Switch protocol is bound to a physical network adapter and is responsible for listening for network traffic from an external virtual network switch. If the Microsoft Virtual Network Switch protocol is not bound to a physical network adapter, the physical network adapter will reduce the network packets that are generated by the external virtual network switch.

2. Internal: The internal network is equivalent to a virtual network card for the host, used for virtual machine communication, and provides DHCP service and NAT proxy service. A virtual machine can surf the web but cannot communicate with the host on which it resides.

650) this.width=650; "height=" 329 "title=" clip_image006 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image006 "src=" http://s3.51cto.com/wyfs02/ M00/58/a5/wkiom1s2c4dyvlqnaaddycij_y0252.jpg "border=" 0 "/>

3. Dedicated: The private network is quite a virtual switch that is connected to a virtual machine, all virtual machines are connected to the same virtual switch, all the virtual machines can communicate with each other, but they cannot access the host and the host's network.

650) this.width=650; "height=" 349 "title=" clip_image008 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image008 "src=" http://s3.51cto.com/wyfs02/ M01/58/a5/wkiom1s2c4dql6e-aadbviginnw620.jpg "border=" 0 "/>

When an administrator creates a virtual switch based on actual requirements, only need to open Hyper-V Manager and click Virtual Switch Manager to create a virtual machine switch. When an administrator creates an external virtual network switch on a Hyper-V host, it is recommended that you plan for downtime.

650) this.width=650; "height=" 260 "title=" clip_image010 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image010 "src=" http://s3.51cto.com/wyfs02/M02/58/A5/ Wkiom1s2c4db7mjtaadt5b795pe027.jpg "border=" 0 "/>

This article is from "Xu Ting Blog-Microsoft technology Sharing" blog, please be sure to keep this source http://ericxuting.blog.51cto.com/8995534/1604084

Hyper-V Server Virtual Switch