Sign in
 
Home2012Previous VersionsLibraryForumsGallery
System Center TechCenter > System Center - Virtual Machine Manager Forums > Virtual Machine Manager – Clustering > Unsupported Cluster Configuration

Answered Unsupported Cluster Configuration

    •  
      Friday, November 07, 2008 6:06 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi,  All of our clustrered guest os's on our Hyper-V cluster show the same error in SCVMM as show below.  Each blade has four network cards two on the iSCSI SAN and two on the produciton network.  All of the guest's move across the nodes of the cluster just fine using the Failover Cluster MMC.  Any help as to where to get some idea about the correct configuraiton of the NIC's would be greatly appreciated.

      Thanks

      JOe

       

       

      Warning (13921)

      Highly available virtual machine LouTS is not supported by VMM because one or more of its network adapters is not configured correctly.

      Recommended Action

      Ensure that all of the virtual network adapters are either disconnected or connected to highly available virtual networks.

       

       

       

       

    Answers

    • Monday, November 10, 2008 8:45 PM
       
       Answered
      Sign In to Vote
      1
      Sign In to Vote

      Hi Joe,

       

      For a VN to be marked as HA, The location and tag of the VN in all nodes must be the same. For each VN in the cluster:

      • The NICs to which the VN is attached in each node have the same location
      • The Tag in the VN in each node is the same
      • The VN Name is the same
      • After you commit changes, refresh the cluster so ensure that the VN is detected as HA.

      To check that the VNs are properly detected as HA:

      • In the admin console, select the cluster, right click and select properties
      • Go to the Virtual Networks and check that the VNs are displayed.
      • If a VN is not displayed, it means that location, tag or name is not consistent across the cluster nodes

      Lastly, if the VM has a DVD image attached, ensure that the .iso file resides in the shared storage and not in a local volume of the Host.

      • Go to the VM properties and in the hardware tab select the DVD driver.
      • Check the path to the .iso file points to a share resource

      I hope this helps

       

       

       

    All Replies

    • Friday, November 07, 2008 6:23 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Joe,

       

      Can you please ensure that the virtual networks that the VMs are conencted to have the same name on every host in the cluster?

       

      One or more virtual network adapters on the virtual machine are not connected to a highly available virtual network.

      If virtual networks on all hosts in the host cluster do not have the same name and the same case (virtual network names are case-sensitive), a highly available virtual machine might lose connectivity when it is migrated or fails over to another cluster node.  To find out the common virtual networks for the cluster, use VMM Administrator Console to view the Networks tab in the host cluster properties. To configure virtual networks on the hosts, use the Networking tab in host properties of VMM Administrator Console.

       

      Hope this helps.

       

      Regards,

      Shon

       
    • Friday, November 07, 2008 3:04 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Shon,

       

      Currently they all have the same names on all the nodes.  All of the VM's successfully fail over to all of the nodes.  Is there any debugging that will let me see into why VMM is reporting this error even though all the public networks are named the same?

      Joe

       

       
    • Monday, November 10, 2008 8:45 PM
       
       Answered
      Sign In to Vote
      1
      Sign In to Vote

      Hi Joe,

       

      For a VN to be marked as HA, The location and tag of the VN in all nodes must be the same. For each VN in the cluster:

      • The NICs to which the VN is attached in each node have the same location
      • The Tag in the VN in each node is the same
      • The VN Name is the same
      • After you commit changes, refresh the cluster so ensure that the VN is detected as HA.

      To check that the VNs are properly detected as HA:

      • In the admin console, select the cluster, right click and select properties
      • Go to the Virtual Networks and check that the VNs are displayed.
      • If a VN is not displayed, it means that location, tag or name is not consistent across the cluster nodes

      Lastly, if the VM has a DVD image attached, ensure that the .iso file resides in the shared storage and not in a local volume of the Host.

      • Go to the VM properties and in the hardware tab select the DVD driver.
      • Check the path to the .iso file points to a share resource

      I hope this helps

       

       

       
    • Monday, November 10, 2008 10:29 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Alejandro, Thanks for the information about setting the Tag for each node.  That was the problem.  Just curious   is that documented anywhere?  It’s not in the help files and I’ve looked at the upcoming Microsoft Class on SCVMM and it wasn’t there either.  Any documents that you could point me to would be greatly appreciated.

      Thanks

      Joe

       
    • Tuesday, November 11, 2008 8:12 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Joe,

       

      http://technet.microsoft.com/en-us/library/cc967323.aspx lists the steps to troubleshoot "Unsupported Cluster Configuration" issues. You are right that the bullet point that covers networking does NOT have a mention of tag. I have sent email to documentation folks to get it updated.

       

      Appreciate your feedback!

       

      Regards,

      Shon

       
    • Friday, November 14, 2008 2:05 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Shon,

       

      While they're updating the documentation have them add in the override for the discovered network location on the hardware tab, it missing from the help file as well.  I somewhat like the product but the documentation for SCVMM leaves a lot to be desired.

       

      Thanks

      Joe

       
    • Tuesday, December 02, 2008 9:00 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I am running into the smae issue with my 2 node Hyper-V cluster that is managed by SCVMM 2008.  SCVMM is reporting Unsupported Cluster Configuration.

       

      As with the OP, all the NICs are named the same on both Nodes and I can falover with no issues.  In SCVMM 2008, under the Host properties under the Networking tab, my Virtual Network is listed there.  It also shows (No tag).  Is it required to add a Tag?  What exactly is a tag and how do I add one to each node if it is necessary?

       
    • Tuesday, December 02, 2008 10:25 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      There's no need to have a tag or a location.

       

      The only need is that the locations are tag are the same in all nodes of the cluster, either empty or with a string.

       

      Check the locations of the physical NICs and that the case of the name is the same: myvn and MyVN are not considered a HA VN

       

       
    • Wednesday, December 03, 2008 2:26 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      The are named exactly the same.

       

      Screenshots:

       

      Node1:  http://img142.imageshack.us/img142/3364/node1mg2.jpg

       

      Node2:  http://img386.imageshack.us/img386/1897/node2ys2.jpg

       

      The only thing I see different is on Node2 (the currently active node) under Connectivity, it says Access to Local and Internet whereas on Node 1, it says Acess to Local Only...why is that?

       

      I do not have a dedicated NIC for remote access (RDP) to each Host and am using the Physical NIC that the Virtual switch uses.

       
    • Wednesday, December 03, 2008 6:49 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Can you run the commands get-virtualnetwork -Name "<VNName>" in the SCVMM powershell interface and send them to my mail?

       
    • Wednesday, December 03, 2008 8:02 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I just noticed something on both Nodes.

       

      On both Nodes 1 and 2, the NICs are named "Local Area Connection 2 as shown in the screenshots under the "Name" tab.

       

      However, under the "Device Name" tab, which I blurred out in the pics, Node 1 shows "Serverabc_Virtual_Network" and Node 2 shows "ServerABC_Virtual_Network".  Would that be the issue? If so, what is the easiest way to corrected it with minimal VM downtime? 

       

       
    • Wednesday, December 03, 2008 8:35 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Check the settings in SCVMM instead of the Windows network adapters page

       
    • Friday, December 05, 2008 9:04 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I think that is the issue!

       

      Note "(virtual network names are case-sensitive)" from below excerpt from http://technet.microsoft.com/en-us/library/cc967323.aspx

       

      The following situations can cause Unsupported Cluster Configuration status:

       

      One or more virtual network adapters on the virtual machine are not connected to a highly available virtual network.
      If the virtual networks on all hosts in the host cluster do not have the same name and the same case (virtual network names are case-sensitive), a highly available virtual machine might lose connectivity when it is migrated or fails over to another cluster node. To find out the common virtual networks for the cluster, in the VMM Administrator Console, view the Networks tab in the host cluster properties. To configure virtual networks on the hosts, use the Networking tab in host properties. For more information about configuring virtual networks, see How to Add or Modify Virtual Networks on a Host in VMM 2008 Help.

       

      Regards,

      Shon