Hi Everyone, this is Alvin Morales, Senior Support Escalation Engineer for System Center and I wanted to take a minute to talk about a potential issue with virtual switches in System Center 2012 Virtual Machine Manager SP1.
Recently I’ve come across a few issues when performing a live migration from one cluster node to another where in the wizard you receive a warning stating that the virtual switch is not compliant.
This can be caused by creating logical switches on the nodes out of order, thus the settings in the logical switch may not be in sync. Another possibility is that changes were made to the virtual switch out of band (i.e. directly in Hyper-V), thus the settings may be different for each node. Fortunately for us, a new feature of System Center 2012 Virtual Machine Manager Service Pack1 (VMM) will warn us if settings among switches are different.
A value of “Fully compliant” indicates that the settings on the host are consistent with the configuration in VMM. For example, “Fully compliant” indicates that all IP subnets and VLANs that are included in the network site are assigned to the network adapter.
A value of “Partially compliant” indicates that there is only a partial match between the settings on the host and the configuration in VMM. In the details pane, the Logical network information section lists the assigned IP subnets and VLANs for the network adapter, so if an adapter is partially compliant you can view the reason in the Compliance errors section.
A value of “Not compliant” indicates that the settings on the host are missing from the configuration in VMM. For example, “Not compliant” indicates that none of the IP subnets and VLANs that are defined for the logical network are assigned to the physical adapter. If you find yourself in this situation we can resolve it by using the steps below:
1. Go to the fabric section and select logical switches, then from the ribbon select hosts. This will change the view and show the status of all NICs, VNICs and logical switches.
2. For the switch that shows as not complaint, highlight the switch and view the compliance warning. Right-click the switch and select remediate. This process will validate and resolve the issues on the switch.
You may find that fixing one network adapter for a cluster node may trigger a warning on another. If this is the case, you need to perform the remediation action to all the network adapters on all nodes.
Alvin Morales | Senior Support Escalation Engineer | Management and Security Division
Get the latest System Center news onFacebookandTwitter:
System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm
Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/