Sign in
 
Home2012Previous VersionsLibraryForumsGallery
System Center TechCenter >
> 
> 
Is SCVMM 2012 worth it for me?

Вопрос Is SCVMM 2012 worth it for me?

  • Wednesday, February 06, 2013 9:05 PM
     
     
    Sign In to Vote
    0

    In the past I've used VMM 2008 R2 and loved it.  Just for the ease of managing our Hyper-V environment and moving servers around.

    We now have some 2012 Hyper-V hosts, so I installed SCVMM 2012 to start working with those, but all I find in VMM 2012 is errors and confusion.

    I can migrate VMs between some hosts, but not others.  The ones that I can't migrate to, say "No available connection to selected VM Network can be found."

    So in order to fix that, I tried to set up a logical network, an IP address pool, etc.  But it hasn't fixed the issue.  And really just has made things more complex.

    I really don't care about all these bells and whistles, why do they make you use them?  We have 1 subnet and 1 trusted network.  All of our Hyper-V hosts live on that same network.  Why do I need all this other stuff?

    Is this product not designed for smaller environments?

     

All Replies

  • Saturday, February 09, 2013 4:56 PM
    Moderator
     
     
    Sign In to Vote
    0

    Yes - but you need to design the logical network model in VMM first (as part of preparing your fabric for your workloads in the cloud).

    see this blog post for how to configure networking in VMM and assign them to hosts:

    http://kristiannese.blogspot.no/2011/05/create-networks-with-vmm-2012.html

    Further information about networking with SP1: http://kristiannese.blogspot.no/2013/01/the-network-virtualization-guide-with.html

    -kn

    Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

     
  • Tuesday, February 12, 2013 6:38 PM
     
     
    Sign In to Vote
    0

    Thanks for the info.

    Regarding the first link, when you get down to the part about virtual networks, I don't see "Virtual Networks" in my view.  I see "Virtual Switches".  I'm assuming that is a change they made.

    Anyway, I created the logical network and I noticed that on our newer Hyper-V hosts, that new logical network i just created is already selected as the logical network for all virtual switches.  However, on the older hosts, that isn't the case.  They usually just parrot the name of the virtual switch.  So for instance, if our three virtual network connections on an old host are named VM Network 1, VM Network 2, and VM Network 3, then VM Network 1 has a logical network selected of "VM Network 1".  VM Network 2 has a logical network selected as "VM Network 2".  Etc.  I never created those logical networks, they are just automatically listed there.   Is that normal?

    I assume I should change all of those to be part of the logical network I created.   Will that cause any connectivity loss during the process?

     
  • Wednesday, February 13, 2013 6:40 AM
    Moderator
     
     
    Sign In to Vote
    0

    Yes - virtual networks are now called virtual switches (finally) with Win 2012 Hyper-V.

    If all the host are physically connected to the same logical network, you could simplify the administration by putting them on the same logical network.

    If you check in settings in VMM, you'll see some default network settings for how VMM can auto-create logical and virtual networks for you.

    Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )