Sign in
Microsoft.com
 
Windows Server TechCenter
 
 
 
Windows Server TechCenter > Windows Server Forums > Hyper-V > Internal virtual network used for two VMs on a Hyper-v cluster
Ask a questionAsk a question
Search Forums:
 

AnswerInternal virtual network used for two VMs on a Hyper-v cluster

  • Friday, October 09, 2009 2:06 PMmlmill Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I have a two-node Windows Server 2008 R2 Hyper-V cluster.  I am creating a SQL 2008 VM and a SharePoint 2007 VM.  Since the SQL traffic will be coming from the SharePoint VM, I am thinking of just setting up an Internal Virtual Network to be used by these two VMs to avoid using up yet another pNIC for this.  First, is this the right design for this? Second, since the VMs will be on the Cluster, what happens if one of the VMs are moved to the other node?  Will the Internal Virtual Network still work or does both VMs always have to be on the same node in the cluster to be able to communicate with each other?
     

Answers

  • Friday, October 09, 2009 3:06 PMBrianEhMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    They will not be allowed to fail individually.

    If they need to be Highly Available - managed by Failover Clustering - then you need to create the two of them as a single managed 'application' / workload in Failover Clustering manager.
    You also need to duplicate the Internal Virtual Network switches on all nodes in the cluster.

    Then they and their dependencies can fail as a unit.

    BTW - you can have multiple VM nics on a single virtual network, just as you can have multiple VMs on a singel virtual network.
    This is not a one vm to one external virtual network type of relationship - unless that is the design you are imposing.
    Brian Ehlert (hopefully you have found this useful)
     

All Replies

  • Friday, October 09, 2009 3:06 PMBrianEhMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    They will not be allowed to fail individually.

    If they need to be Highly Available - managed by Failover Clustering - then you need to create the two of them as a single managed 'application' / workload in Failover Clustering manager.
    You also need to duplicate the Internal Virtual Network switches on all nodes in the cluster.

    Then they and their dependencies can fail as a unit.

    BTW - you can have multiple VM nics on a single virtual network, just as you can have multiple VMs on a singel virtual network.
    This is not a one vm to one external virtual network type of relationship - unless that is the design you are imposing.
    Brian Ehlert (hopefully you have found this useful)
     
  • Friday, October 09, 2009 3:16 PMmlmill Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    So, if they both exist now in the cluster I need to re-create them?  How exactly do I create them as a single managed application / workload?  Thanks
     
  • Thursday, October 15, 2009 8:43 AMPravin Mestry Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Have a look at this post:

    Network configuration when clustering Hyper-V

    http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/023680f3-fc5e-4b45-ae17-fcb12f148f1a

     
  • Friday, October 16, 2009 7:07 AMVincent HuMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    ·         Hi,

     

    Have you tried the suggestion? I want to see if the information provided was helpful. Your feedback is very useful for the further research. Please feel free to let me know if you have addition questions.

     

     

    Best regards,

    Vincent Hu