windows2012 Server Hyper-V host turns on multi-VLAN capabilities

The local physical machine IP segment is vlan5 with an address of 192.168.5.1. The virtual machine network segment is VLAN4, with the address 192.168.4.1.

Server Configuration steps:

First step: Open Hyper-V Manager and open the Virtual Switch manager on the right

650) this.width=650; "title=" QQ picture 20161206184509.png "alt=" wkiom1hgltgqayiyaaddf6ad9yq174.png-wh_50 "src="/http S1.51cto.com/wyfs02/m00/8b/32/wkiom1hgltgqayiyaaddf6ad9yq174.png-wh_500x0-wm_3-wmp_4-s_340587546.png "/>

Second step: Open the Virtual Machine Manager, check the virtual network switch used, tick the Enable Virtual LAN identity option for the management operating system. (Fill in the information for the Switch VLAN below)

650) this.width=650; "title=" QQ picture 20161206184816.png "alt=" wkiol1hgl-eztlbvaadtfulrjlk055.png-wh_50 "src="/http S5.51cto.com/wyfs02/m01/8b/2e/wkiol1hgl-eztlbvaadtfulrjlk055.png-wh_500x0-wm_3-wmp_4-s_2254718659.png "/>

The third step: Select the running virtual machine, right click on the settings, pop up the settings window of the virtual machine. Turn on the virtual LAN identity feature and set the VLAN number. ( if not, restart the next NIC Test )

650) this.width=650; "title=" QQ picture 20161206185505.png "alt=" wkiom1hgmsyj1a-xaaeyuttnnvs771.png-wh_50 "src="/http S2.51cto.com/wyfs02/m01/8b/32/wkiom1hgmsyj1a-xaaeyuttnnvs771.png-wh_500x0-wm_3-wmp_4-s_1340133768.png "/>

Switch configuration:

Locate the switch interface that is connected to the server NIC and configure the interface as trunk mode. and allow related VLANs to pass.

650) this.width=650; "title=" QQ picture 20161206185708.png "alt=" wkiol1hgmdrq3c1caaafvsvuqcu853.png-wh_50 "src="/http S2.51cto.com/wyfs02/m02/8b/2e/wkiol1hgmdrq3c1caaafvsvuqcu853.png-wh_500x0-wm_3-wmp_4-s_443103832.png "/>

Problem Description:

In this experiment, because the use of the server is not new, all encountered some problems, again explained:

Following the above steps to configure the completion, found that can be connected, but far thread attached to the physical server, the special card, occasionally will flash off. Finally, the original is the physical machine enabled in the windows2012 with the network card binding function (Nic Teaming), the two local network cards are bound together. (The specific binding method, the Internet is OK to find, here do not do)

650) this.width=650; "title=" QQ picture 20161206191044.png "alt=" wkiol1hgnmtxlr-vaac6uzaembw769.png-wh_50 "src="/http S2.51cto.com/wyfs02/m02/8b/2e/wkiol1hgnmtxlr-vaac6uzaembw769.png-wh_500x0-wm_3-wmp_4-s_3908791190.png "/>

650) this.width=650; "title=" QQ picture 20161206191205.png "alt=" wkiol1hgnrxrxqxdaab6vqr0pko711.png-wh_50 "src="/http S1.51cto.com/wyfs02/m00/8b/2e/wkiol1hgnrxrxqxdaab6vqr0pko711.png-wh_500x0-wm_3-wmp_4-s_1965190963.png "/>

Because when I was doing configuration on the switch, I only configured one interface to trunk, so this problem occurs, when the other switch interface is also configured as trunk, the device remote access is back to normal. This problem may also be tied to the network adapter load Balancer mode has a relationship, the specific is not in check.

Windows Server 2012 NIC Bindings Tutorial Link:http://www.360doc.com/content/12/0910/14/74060_235349278.shtml

This article from "Write something?" "Blog, be sure to keep this provenance http://lipenglong.blog.51cto.com/5309038/1880121

windows2012 Server Hyper-V host turns on multi-VLAN capabilities