locked
Virtual Network Name on Multiple Hosts RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello All,

    Will naming the virtual network name the same on two different hyper-v hosts cause any issues if failover is not configured?

    Is it best practice to name the virtual networks different or the same?

    I see where if failover the virtual network name needs to be the same.

    Thanks in advance.


    Thursday, February 9, 2012 9:37 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    There is a desire to maintain your own sanity by having a standard naming convention for virutal networks - and at scale names like "NIC1" and "NIC2" don't take you very far.

    If the VMs are going to be HA, then yes, the name of the virtual networks needs to be the same.

    In SCVMM 2008 it helps keeps things straight - in SCVMM 2012 there is the "logical network" that manages the External virtual connections in situations where naming is not equal.

    I usually name my virutal networks according to the physical network or subnet or vlan that the External virtual network is connected to.  This makes the name related to the topology and not the particular hypervisor.

    Oh, will it cause issues?  Not at all.  Only the Hyper-V server knows the name - or SCVMM if it is involved.  These virtual network names are not seen on the network or anything like that.

    Brian Ehlert (hopefully you have found this useful) http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Backup, test your backup, try new things. Attempting change is of your own free will.


    • Edited by BrianEhMVP Thursday, February 9, 2012 10:02 PM
    • Marked as answer by Daniel_S'____ Thursday, February 9, 2012 10:08 PM
    Thursday, February 9, 2012 10:01 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    There is a desire to maintain your own sanity by having a standard naming convention for virutal networks - and at scale names like "NIC1" and "NIC2" don't take you very far.

    If the VMs are going to be HA, then yes, the name of the virtual networks needs to be the same.

    In SCVMM 2008 it helps keeps things straight - in SCVMM 2012 there is the "logical network" that manages the External virtual connections in situations where naming is not equal.

    I usually name my virutal networks according to the physical network or subnet or vlan that the External virtual network is connected to.  This makes the name related to the topology and not the particular hypervisor.

    Oh, will it cause issues?  Not at all.  Only the Hyper-V server knows the name - or SCVMM if it is involved.  These virtual network names are not seen on the network or anything like that.

    Brian Ehlert (hopefully you have found this useful) http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Backup, test your backup, try new things. Attempting change is of your own free will.


    • Edited by BrianEhMVP Thursday, February 9, 2012 10:02 PM
    • Marked as answer by Daniel_S'____ Thursday, February 9, 2012 10:08 PM
    Thursday, February 9, 2012 10:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks BrianEh 

    Please if you help me in my case too that is I have SCVMM2008 R2 SP1 and 5 host machine are added on it but I am not able to assign any card it always give me error that 

    Error (505)
    Virtual Machine Manager was unable to create a new virtual network 
     (Unknown error (0x80338000)) 


    Recommended Action
    Check the virtual network name, and then try the operation again.

    Even i try every possibilities but I am not able to bind the card, I also try the same operation with Hyper V but it fail ...any suggestion ? 



    Danish Khan DK

    Wednesday, February 29, 2012 9:24 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    hi friends, almost after one year I know and facing the same issue.

    I am trying to create a new switch with new name in different hp blade where I have installed Hyper-V 2012 and attached to SCVMM 2012 R2. 

    I am getting the same issue bu unknown error number is different, any suggestion to fix...?

    Error (505)
    Virtual Machine Manager was unable to create a new virtual network 
     (Unknown error (0x80338126)) 

    Recommended Action
    Check the virtual network name, and then try the operation again.

    Tuesday, March 12, 2013 11:33 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    @Karan.T sorry to hijack this question, did you solve this issue?

    we have the same issue?

    Error (505)
    Virtual Machine Manager was unable to create a new virtual switch New Virtual Switch0.
    Unknown error (0x80041001)

    Recommended Action
    Check the virtual switch name, and then try the operation again.


    Andrew Hancock

    Friday, May 10, 2013 10:59 AM