Answered Hyper-V with HP EVA CLX - VMM resource dependency issue.

  • Monday, November 24, 2008 1:13 PM
     
     

    Hi,

     

    Firstly just some background on the implementation I'm working on:

     

    I have two sites, each with an HP EVA 4100 Storage Array with LUNS that are replicated in a Synchronous manner. Each LUN holds one VM and is independent in its replication setting, so some can be replicating in one direction and others in the other independently of each other.

     

    I have two Cluster Nodes on each site, a File Share at a third site and have the Quorum set for Node and File Share Majority.

     

    The HP Cluster Extension software is installed and I've added a "Cluster Extension EVA" resource to each Virtual Machine and made it's Disk resource dependent on the Cluster Extension resources (The cluster extension resource is responsible for changing the replication direction depending on which cluster host the VM is active on).

     

    Now this works absolutely beautifully, it fails over between hosts between each site changing the replication direction as expected with complete transparency and no user intervention required.

     

    Only snag is that because of the CLX resource dependency, VMM 2K8 sets the status to “Unsupported Cluster Configuration”, and won’t allow me to manage it unless I remove the dependency and resource, which of course is required for CLX to work.

     

    Is anyone aware of a way to customise the Cluster Check to allow for this via PowerShell or anything?

     

    I’m not expecting a Yes, but would be interested if anyone else is doing anything similar and having the same problem.

     

    I’m aware that HP presently hasn’t certified CLX for use with Hyper-V but as I understand it, they are in the process of doing so now. Given the amount of work they seem to have put into the PRO Tips for VMM I expect that they push MS for a Hotfix to enable CLX to be used with VMM as part of their certification program.

     

    I’m going to open a support case with MS tomorrow to see if there is a work around, but until then any comments and feedback would be appreciated.

     

     

    Jas Smile

Answers

  • Tuesday, December 02, 2008 10:33 PM
     
     Answered

    Jason,

     

    Yes you should open a support case for this issue. VMM expects only "VM res->VM config res->Disk res" in a resource group and if it finds any other resource in the resource group, it marks the HAVM as UnsupportedCluster which means it is not manageable using VMM. The dependency check needs to be loosened a bit :-)

     

    Hope this helps.

     

    Regards,

    Shon

  • Wednesday, December 03, 2008 5:53 AM
     
     Answered

    Hi Shon,

     

    Thanks for the reply, I've been flat out so I haven't had a chance to open a ticket but I'll try get onto it today. You've confirmed what I though was the case in any event.

     

    I've since been informed that HP are planning for certify CLX (Cluster Extension) for use with Hyper-V at the latest by April 2009 so I expect they will be requesting this change as well to ensure that the solution as a whole works transparently.

     

    If I do end up with a solution I'll be sure to post back here with the details.

     

     

    Jas Smile

     

     

     

     

     

All Replies

  • Tuesday, December 02, 2008 10:33 PM
     
     Answered

    Jason,

     

    Yes you should open a support case for this issue. VMM expects only "VM res->VM config res->Disk res" in a resource group and if it finds any other resource in the resource group, it marks the HAVM as UnsupportedCluster which means it is not manageable using VMM. The dependency check needs to be loosened a bit :-)

     

    Hope this helps.

     

    Regards,

    Shon

  • Wednesday, December 03, 2008 5:53 AM
     
     Answered

    Hi Shon,

     

    Thanks for the reply, I've been flat out so I haven't had a chance to open a ticket but I'll try get onto it today. You've confirmed what I though was the case in any event.

     

    I've since been informed that HP are planning for certify CLX (Cluster Extension) for use with Hyper-V at the latest by April 2009 so I expect they will be requesting this change as well to ensure that the solution as a whole works transparently.

     

    If I do end up with a solution I'll be sure to post back here with the details.

     

     

    Jas Smile

     

     

     

     

     

  • Wednesday, December 10, 2008 8:59 PM
     
     
     Jason Bailey wrote:

    Hi,

     

    Firstly just some background on the implementation I'm working on:

     

    I have two sites, each with an HP EVA 4100 Storage Array with LUNS that are replicated in a Synchronous manner. Each LUN holds one VM and is independent in its replication setting, so some can be replicating in one direction and others in the other independently of each other.

     

    I have two Cluster Nodes on each site, a File Share at a third site and have the Quorum set for Node and File Share Majority.

     

    The HP Cluster Extension software is installed and I've added a "Cluster Extension EVA" resource to each Virtual Machine and made it's Disk resource dependent on the Cluster Extension resources (The cluster extension resource is responsible for changing the replication direction depending on which cluster host the VM is active on).

     

    Now this works absolutely beautifully, it fails over between hosts between each site changing the replication direction as expected with complete transparency and no user intervention required.

     

    Only snag is that because of the CLX resource dependency, VMM 2K8 sets the status to “Unsupported Cluster Configuration”, and won’t allow me to manage it unless I remove the dependency and resource, which of course is required for CLX to work.

     

    Is anyone aware of a way to customise the Cluster Check to allow for this via PowerShell or anything?

     

    I’m not expecting a Yes, but would be interested if anyone else is doing anything similar and having the same problem.

     

    I’m aware that HP presently hasn’t certified CLX for use with Hyper-V but as I understand it, they are in the process of doing so now. Given the amount of work they seem to have put into the PRO Tips for VMM I expect that they push MS for a Hotfix to enable CLX to be used with VMM as part of their certification program.

     

    I’m going to open a support case with MS tomorrow to see if there is a work around, but until then any comments and feedback would be appreciated.

     

     

    Jas

     

    Hi Jason,

     

    I am trying to do exactly what you are doing with Hyper-V and CLX.  Can you help me and give me some hints about the way you add the storage and the CLX ressource to the cluster ?  i an unable to bring the storage online.

     

    Thanks !

     

    Stephan

  • Monday, January 26, 2009 11:08 AM
     
     

    Hello Jason, Stephane,

      We have ran into exactly the same problem as you have outlined in your message with Hyper-V and CLX.  We are unable to manage our HP Geo-Cluster  solution with VMM because it is being marked as an "unsupported cluster configuration" error 2923. 

    Has anyone found a solution or update for this to work? Has HP or MS found a hotfix or solution.

    Thanks in advance,

    Juan Carlos

     

     

     

     

     

     


    MCT
  • Tuesday, June 09, 2009 3:20 PM
     
     
    This issue has been fixed in following update:

    http://support.microsoft.com/kb/961983


    Issue 5

    Hyper-V virtual machines in a Windows Server 2008 failover cluster have a status of Unsupported Cluster Configuration in System Center Virtual Machine Manager 2008 if the virtual machine resource group contains resources in addition to the Virtual Machine, Virtual Machine Configuration, and Physical Disk resources. These additional resources typically are third-party resources that provide functionality such as replicating storage in a multi-site cluster.

    Hope this helps.

    Regards,
    Shon