Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Validation port remains open in virtual switch after the associated virtual machine fails over to another node in Windows Server 2012

Validation port remains open in virtual switch after the associated virtual machine fails over to another node in Windows Server 2012

View products that this article applies to.

Symptoms

Consider the following scenarios. 

Scenario 1

  • You have the Hyper-V server role installed on a Windows Server 2012-based multiple-node failover cluster.
  • You create a clustered virtual machine that uses Server Message Block (SMB)-based storage on a node (node A).
  • Node A crashes or restarts. Then, the virtual machine on node A fails over to another node (node B).
In this scenario, the validation port that is associated with the virtual machine remains open in the virtual switch on node A.

Note This issue continues to occur even after you delete the virtual machine from node B.

Scenario 2

  • You have the Hyper-V server role installed on a Windows Server 2012-based multiple-node failover cluster.
  • You create a clustered virtual machine that uses SMB-based storage on a node (node A).
  • The cluster service stops on node A. Then, the virtual machine on node A fails over to another node (node B).

In this scenario, the validation port that is associated with the virtual machine remains open in the virtual switch on node A.

Note When an invalid validation port remains open in the virtual switch, this may not cause any observable problems for administrators or for users. However, if many virtual machines are deleted over time, lots of invalid validation ports remain open in the virtual switch. In this situation, the virtual switch may run out of available ports and therefore reach its capacity limit. This behavior may prevent an administrator from creating new virtual machines to be hosted by the cluster nodes.

For more information about validation ports, go to the following Microsoft website:
General information about validation ports

↑ Back to the top

Cause

This issue occurs because the Hyper-V Virtual Machine Management service (VMMS) cannot delete the validation port after the virtual machine is deleted.

↑ Back to the top

Resolution

This hotfix is also available at Microsoft Update Catalog.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Server 2012.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.





Windows Server 2012 file information notes
Important Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    VersionProductMilestoneService branch
    6.2.920 0.16 xxxWindows Server 2012RTMGDR
    6.2.920 0.20 xxxWindows Server 2012RTMLDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Rdvgpuinfo.dll6.2.9200.1638460,41626-Jul-201201:28x64
Vmms.exe6.2.9200.1668511,204,09609-Aug-201301:52x64
Rdvgpuinfo.dll6.2.9200.1638460,41626-Jul-201201:28x64
Vmms.exe6.2.9200.2079311,204,60809-Aug-201304:39x64

↑ Back to the top

Workaround

To work around the issue, delete and re-create the virtual switch on the affected node to remove the validation port.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012
File propertyValue
File nameAmd64_00868cde328481a0ec972c7097e198b5_31bf3856ad364e35_6.2.9200.20793_none_cab31e533d0b241c.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_153c587cb7673895eb79730c8f9fca8f_31bf3856ad364e35_6.2.9200.20793_none_279c17f6ced30bea.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_1b9998302481cd92cfbef94b9b25b04a_31bf3856ad364e35_6.2.9200.20793_none_659afc4bca73cb1f.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_2bdfb329e0fc59f839763566326d4e5a_31bf3856ad364e35_6.2.9200.20793_none_eba7a8f6c7eec1a4.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_393be198852b664f038f6514ed6ec4a0_31bf3856ad364e35_6.2.9200.20793_none_f76abd96d6fb6d99.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_3d927eb90410243dcc00a867d9e571a8_31bf3856ad364e35_6.2.9200.20793_none_108278a56ac8ca0a.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_3e1aed74fe7159c3aea94d78db4df346_31bf3856ad364e35_6.2.9200.20793_none_f8c8b9bc86163c36.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_4085cb40242c7e833c3a43d5196ddce3_31bf3856ad364e35_6.2.9200.20793_none_c3b82ab36514dcec.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_44ce25133d3d579b4c26e536e6146a61_31bf3856ad364e35_6.2.9200.20793_none_c819bfad96d6dc99.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_5376f4bf977e54b3ebbcef8bac243311_31bf3856ad364e35_6.2.9200.20793_none_1a96dd70d8d5b0cd.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_58b48ccbd5ff29201cc896ac68c6c59e_31bf3856ad364e35_6.2.9200.20793_none_47e7f80620df5c8d.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_6aae7dfaaae2b01be6e1ecd695a870f0_31bf3856ad364e35_6.2.9200.20793_none_ef4679f0292e0791.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_7d2925f7b79c664ef7bb6012117889ba_31bf3856ad364e35_6.2.9200.20793_none_55695c11684b731e.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_7f1c8a20a4038ec41e54f2acc4b8f532_31bf3856ad364e35_6.2.9200.20793_none_a4fb3e230a1f0b93.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_8245698f38e55e7077474f2d8d3640e5_31bf3856ad364e35_6.2.9200.20793_none_2b045c7c97a541fb.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_84e5fc5c836273054125a259fe683158_31bf3856ad364e35_6.2.9200.20793_none_f9669c34272f2b81.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_8ddcf1d51b652e16fedc7d28af7435c5_31bf3856ad364e35_6.2.9200.16685_none_e6a6bbb2e0a14ac6.manifest
File versionNot applicable
File size703
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_90573a3dbcb1968a55efc0485a7219c0_31bf3856ad364e35_6.2.9200.20793_none_91b9c5704afb5ab5.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_934a059487f82e0ad3a0f4a9d5b911aa_31bf3856ad364e35_6.2.9200.20793_none_11ba206b81e4c2f7.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_b13299b107a5b84c1b2da5b9c43383f0_31bf3856ad364e35_6.2.9200.20793_none_c7d47985d5fbe70a.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_b5eafb5ac4e0dbdc742b61dfc177a25f_31bf3856ad364e35_6.2.9200.20793_none_a190a3886c7585b1.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_b91f3140a74eef8b17ae9e3f372fb710_31bf3856ad364e35_6.2.9200.20793_none_93c7d877e39fd65e.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_e1e26f43078f0c6d6c40368195502a81_31bf3856ad364e35_6.2.9200.20793_none_6a76925a4cbff609.manifest
File versionNot applicable
File size703
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_ebc9d507af2c584eb3ea1b51551cc16e_31bf3856ad364e35_6.2.9200.20793_none_249105c3c6bbd1d9.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_fad8a613a94fd4afaec2841381a0fca4_31bf3856ad364e35_6.2.9200.20793_none_5b0a1eeeab9f47d9.manifest
File versionNot applicable
File size711
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_microsoft-hyper-v-vstack-vmms_31bf3856ad364e35_6.2.9200.16685_none_8f60b500e8affc7f.manifest
File versionNot applicable
File size1,134,338
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_microsoft-hyper-v-vstack-vmms_31bf3856ad364e35_6.2.9200.20793_none_8fdd814c01d7858c.manifest
File versionNot applicable
File size1,135,762
Date (UTC)09-Aug-2013
Time (UTC)15:46
PlatformNot applicable

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2861168
Revision : 1
Created on : 1/7/2017
Published on : 4/27/2014
Exists online : False
Views : 173