Home
%3CLINGO-SUB%20id%3D%22lingo-sub-570971%22%20slang%3D%22en-US%22%3ELogical%5CStandard%20Switch%20Deployment%20Failures%20in%20System%20Center%20Virtual%20Machine%20Manager%202016%20(UR%206)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-570971%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EFirst%20published%20on%20TECHNET%20on%20Feb%2019%2C%202019%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CSTRONG%3E%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CBR%20%2F%3EHi%20everyone%2C%20Chuck%20Timon%20here%20to%20talk%20to%20you%20about%20an%20issue%20my%26nbsp%3Bcustomer%20contacted%20me%20on%20recently%2C%20reporting%20an%20issue%20with%20Logical%20Switch%20deployments%20on%20two%20nodes%20of%20a%20four%20node%20Windows%20Server%202016%20Failover%20Cluster%20managed%20by%20System%20Center%20Virtual%20Machine%20Manager%202016%20(UR6).%20The%20error%20message%20is%20shown%20here%20-%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20822px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F113497i69169F733E856622%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20%2F%3E%3C%2FSPAN%3E%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20decode%20for%20the%20error%20%E2%80%93%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20624px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F113498iB0F77679C1CB8FDF%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20%2F%3E%3C%2FSPAN%3E%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EI%20asked%20the%20customer%20to%20collect%20a%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F2913445%2Fhow-to-enable-debug-logging-in-virtual-machine-manager%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20Carmine%20trace%20%3C%2FA%3E%20to%20capture%20additional%20details%20of%20the%20failure.%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20initial%20exception%20-%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20624px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F113499iDD25527304E993A9%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20%2F%3E%3C%2FSPAN%3E%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20final%20failure%20%E2%80%93%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20624px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F113500iF6DB30A42715C498%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20%2F%3E%3C%2FSPAN%3E%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EAs%20a%20test%2C%20I%20asked%20the%20customer%20to%20deploy%20a%20Standard%20Switch%20which%20failed%20as%20well.%20I%20asked%20the%20customer%20to%20verify%20he%20could%20create%20a%20simple%20external%20Hyper-V%20switch%20on%20the%20hosts%20and%20that%20completed%20successfully.%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EI%20was%20aware%20of%20a%20problem%20in%20SCVMM%20with%20Logical%20Switches%20'disappearing'%20as%20documented%20here%20-%20System%20Center%20Virtual%20Machine%20Manager%20fails%20to%20enumerate%20and%20manage%20Logical%20switch%20deployed%20on%20the%20host%20.%20The%20customer%20reviewed%20the%20blog%20and%20reported%20that%20none%20of%20the%20symptoms%20applied%20to%20his%20environment.%20We%20decided%20to%20go%20ahead%20and%20re-compile%20the%20.mof%20files%20mentioned%20in%20the%20blog%20anyway.%20After%20that%20action%20completed%20successfully%2C%20the%20Hosts%20were%20refreshed%20in%20the%20SCVMM%20console.%20Another%20attempt%20was%20made%20to%20deploy%20a%20Logical%20Switch%2C%20and%20the%20failure%20was%20the%20same.%20The%20cluster%20node%20was%20rebooted%2C%20and%20after%20that%2C%20the%20Logical%20Switch%20deployment%20completed%20successfully.%20The%20process%20was%20duplicated%20on%20the%20other%20node%20and%20in%20the%20end%20all%20Logical%20Switch%20deployments%20were%20completed%2C%20and%20the%20cluster%20was%20up%20and%20running%20properly.%20The%20conclusion%20I%20reached%20was%20perhaps%20the%20WMI%20service%20needed%20to%20be%20restarted%20which%2C%20obviously%2C%20occurred%20as%20a%20result%20of%20the%20reboot.%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20for%20your%20attention%20and%20I%20hope%20this%20information%20was%20useful%20to%20you.%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3ECharles%20Timon%2C%20Jr.%20%3CBR%20%2F%3ESenior%2C%20Premiere%20Field%20Engineer%20%3CBR%20%2F%3EMicrosoft%20Corporation%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-570971%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20%23ffffff%3B%20color%3A%20%23333333%3B%20cursor%3A%20text%3B%20font-family%3A%20inherit%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.7142%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3EHi%20everyone%2C%20Chuck%20Timon%20here%20to%20talk%20to%20you%20about%20an%20issue%20my%26nbsp%3Bcustomer%20contacted%20me%20on%20recently%2C%20reporting%20an%20issue%20with%20Logical%20Switch%20deployments%20on%20two%20nodes%20of%20a%20four%20node%20Windows%20Server%202016%20Failover%20Cluster%20managed%20by%20System%20Center%20Virtual%20Machine%20Manager%202016%20(UR6).%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-570971%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Echuck%20timon%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eproudmicrosoftemployee%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Escvmm%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESystem%20Center%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EVirtual%20Machine%20Manager%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ewindows%2010%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%207%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ewindows%208%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ewindows%208%201%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ewindows%20server%202008%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ewindows%20server%202008%20r2%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ewindows%20server%202012%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ewindows%20server%202012%20r2%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20server%202016%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft

First published on TECHNET on Feb 19, 2019


Hi everyone, Chuck Timon here to talk to you about an issue my customer contacted me on recently, reporting an issue with Logical Switch deployments on two nodes of a four node Windows Server 2016 Failover Cluster managed by System Center Virtual Machine Manager 2016 (UR6). The error message is shown here -





The decode for the error –





I asked the customer to collect a Carmine trace to capture additional details of the failure.


The initial exception -





The final failure –





As a test, I asked the customer to deploy a Standard Switch which failed as well. I asked the customer to verify he could create a simple external Hyper-V switch on the hosts and that completed successfully.


I was aware of a problem in SCVMM with Logical Switches 'disappearing' as documented here - System Center Virtual Machine Manager fails to enumerate and manage Logical switch deployed on the ... . The customer reviewed the blog and reported that none of the symptoms applied to his environment. We decided to go ahead and re-compile the .mof files mentioned in the blog anyway. After that action completed successfully, the Hosts were refreshed in the SCVMM console. Another attempt was made to deploy a Logical Switch, and the failure was the same. The cluster node was rebooted, and after that, the Logical Switch deployment completed successfully. The process was duplicated on the other node and in the end all Logical Switch deployments were completed, and the cluster was up and running properly. The conclusion I reached was perhaps the WMI service needed to be restarted which, obviously, occurred as a result of the reboot.


Thanks for your attention and I hope this information was useful to you.


Charles Timon, Jr.
Senior, Premiere Field Engineer
Microsoft Corporation