Get your server issues fixed by our experts for a price starting at just 25 USD/Hour. Click here to register and open a ticket with us now!

Author Topic: How to fix Unsupported Cluster Configuration issue in SCVMM  (Read 7665 times)

0 Members and 1 Guest are viewing this topic.

Arun

  • Newbie
  • *
  • Posts: 7
  • Karma: +0/-0
Sometimes SCVMM will show status of all running VMs in a cluster as Unsupported Cluster Configuration.
When we right click the VM, select Properties, and view status of the Network Adapter, it will show Not connected eventhough a Network is selected in the options. This is a known issue in which certain network adapters or firmware loses connectivity.


For an individual VM, this can be fixed by performing the following steps
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1) Identify the VM's Node. This will be shown below Host field in SCVMM.

2) Run virtmgmt.msc. This will open the Hyper-V Manager.

3) Goto Action -> Connect to Server... -> Another computer:
Type the name of corresponding Node and click OK. All the VMs in that Node will be listed. Restart the required VM.
This will also change the status of that VM in SCVMM to Running.



If we want to fix this this for all VMs, perform the following steps
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1) From SCVMM, open Powershell. This will load Powershell with all the required modules.

2) Execute the following command. It will list the details of all available Clusters. Note the value of variable ClusterName. In our case the value was myHVC1.
Code: [Select]
PS > Get-SCVMHostCluster
3) Following command will give us a list of connected Virtual Networks. In our case myhvc1n13 was missing.
Code: [Select]
PS > Get-SCVirtualNetwork | Sort logicalnetworks | ft name, logicalnetworks, vmhost
4) Restart the Windows Management Instrumentation service in myhvc1n13.
=>  Run -> services.msc. This will open up Services.

=> Goto -> Connect to another computer... -> Another computer:
Type myhvc1n13 and click OK. This will list all services in that node. Restart the service Windows Management Instrumentation.

=> Next time services.msc starts, it will still connect to myhvc1n13. So make sure to revert the changes.
Goto -> Connect to another computer... -> Local computer: and click OK.

5) Restarting WMI service will also restart depending services on the node. So we must refresh all the VMs.
As the VMs are showing Unsupported Cluster Configuration, they must be forcefully refreshed.
Code: [Select]
PS > Get-SCVirtualMachine | where {$_.StatusString -eq 'Unsupported Cluster Configuration'}| Read-SCVirtualMachine -Force
6) All VMs will be refreshed individually. So we will see the status of them changing one by one. This will take some time.

7) Done  8)
« Last Edit: July 28, 2017, 03:14:49 pm by Arun »
Get your server issues fixed by our experts for a price starting at just 25 USD/Hour. Click here to register and open a ticket with us now!