IMPORTANT ANNOUNCEMENT FOR OUR READERS!
AskPFEPlat is in the process of a transformation to the new Core Infrastructure and Security TechCommunity, and will be moving by the end of March 2019 to our new home at https://aka.ms/CISTechComm (hosted at https://techcommunity.microsoft.com). Please bear with us while we are still under construction!
We will continue bringing you the same great content, from the same great contributors, on our new platform. Until then, you can access our new content on either https://aka.ms/askpfeplat as you do today, or at our new site https://aka.ms/CISTechComm. Please feel free to update your bookmarks accordingly!
Why are we doing this? Simple really; we are looking to expand our team internally in order to provide you even more great content, as well as take on a more proactive role in the future with our readers (more to come on that later)! Since our team encompasses many more roles than Premier Field Engineers these days, we felt it was also time we reflected that initial expansion.
If you have never visited the TechCommunity site, it can be found at https://techcommunity.microsoft.com. On the TechCommunity site, you will find numerous technical communities across many topics, which include discussion areas, along with blog content.
NOTE: In addition to the AskPFEPlat-to-Core Infrastructure and Security transformation, Premier Field Engineers from all technology areas will be working together to expand the TechCommunity site even further, joining together in the technology agnostic Premier Field Engineering TechCommunity (along with Core Infrastructure and Security), which can be found at https://aka.ms/PFETechComm!
As always, thank you for continuing to read the Core Infrastructure and Security (AskPFEPlat) blog, and we look forward to providing you more great content well into the future!
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 host. 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