Sign in
 
Home2012Previous VersionsLibraryForumsGallery
System Center TechCenter >
> 
> 
Windows 2012 with 2 nics - reference architecture with SCVMM 2012 SP1

Unanswered Windows 2012 with 2 nics - reference architecture with SCVMM 2012 SP1

  • Friday, January 25, 2013 3:31 PM
     
      Has Code
    Sign In to Vote
    0

    I'm trying to find right solution for my virtualization environment.

    4 host, HP BL460 with 2 port  embedded nics and 2 ports FC HBA. connected to 2 HP 6120XG. I'm want to use HA (Failover Cluster) and SCVMM for management task.

    VMs must be in several VLANS.

    From 6120XG side ports are trunks.


    If i create team adapter on host, and try to add hyper-V standard switch following error is occured

    Error (26900)
A logical switch instance cannot be created on physical network adapter (Microsoft Network Adapter Multiplexor Driver) because the adapter is a teamed adapter
Recommended Action
Please delete the team from the host and create logical switch instance on the physical network adapters

    if i try add logical switch to team adapter , following error is occured 

    Error (2912)
An internal error has occurred trying to contact the hyper460slot5.domain.com server: : .
 WinRM: URL: [http://hyper460slot5.domain.com:5985], Verb: [GET], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/ErrorInfo?ID=1002]
 Unknown error (0x80041008)
Recommended Action
Check that WS-Management service is installed and running on server hyper460slot5.domain.com. For more information use the command "winrm helpmsg hresult".

    After week of trying, i found solution, but not sure that is right solution for my configuration.

    Break Team on Host, Create Physical Uplink port Profile, create logical networks and sites, create logical switch

    Assign logical switch to one of adapters (second used as temporary management). After that create new virtual adapter in SCVMM. Move management ip address to this virtual adapter, add second physical adapter to new team interface created when i assign Logical switch to physical interface. Because Logical Switch is created with "Team" option in "Uplink mode" setting.

    What is reference (supported) architecture  for 2 nics servers in failover cluster and SCVMM 2012 SP1? 


     

All Replies

  • Wednesday, January 30, 2013 3:13 AM
     
     
    Sign In to Vote
    0
    I test this configuration for HA. When i shutdown port on HP 6120XG, no intterrupt in tcp session is occured.
     
  • Friday, February 22, 2013 9:46 PM
     
     
    Sign In to Vote
    0
    I have the same errors. I do believe that I read in the VMM documentation for 2012 sp1 that it is supposed to work both ways.
     
  • Monday, February 25, 2013 6:13 PM
    Moderator
     
     
    Sign In to Vote
    0

    Can you see this blog post for guidance, and see how it goes?

    This is a supported configuration and recommended way to to it. http://kristiannese.blogspot.no/2013/02/configure-nic-teaming-and-qos-with-vmm.html

    -kn

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

     
  • Thursday, May 16, 2013 2:31 PM
     
     
    Sign In to Vote
    0

    I've gone through this guide and have the same errors.  

    If the host has only 2 pnics how can it be communicating with the SCVMM server if both pnics are setup for teaming (LACP) on the switch side yet neither pnic on the host is in a team yet?

    I was hoping I could have a Windows 2012 team with both pnics, add the host to SCVMM, create the Logical Switch (including all the other bits from the guide), apply the logical switch to the host and have it overwrite the current team with the new SCVMM team and vnics.  

    Is this not what is expected?

    Thanks

     
  • Friday, May 17, 2013 4:33 AM
     
     
    Sign In to Vote
    0

    Go here...

    http://www.thomasmaurer.ch/2012/07/windows-server-2012-hyper-v-converged-fabric/

    some of the steps can only be done in Powershell.  All of it can be done with powershell.  The order as I see it on that link is..

    • Install the Hyper-V Role
    • Create NIC Teams
    • Create a Hyper-V Virtual Switch
    • Add new Virtual Network Adapters to the Management OS
    • Set VLANs of the Virtual Network Adapters
    • Set QoS Policies of the Virtual Network Adapters
    • Configure IP Addresses of the Virtual Network Adapters

    Another great link....

    http://www.hyper-v.nu/archives/marcve/2013/01/lbfo-hyper-v-switch-qos-and-actual-performance-part-1/

    Thanks, -Lindy

     
  • Friday, May 17, 2013 3:51 PM
     
     
    Sign In to Vote
    0

    The steps described in the previous reply work with PS commands to manually configure the environment. IF I want to sue SC 2012 SP1 VMM to do it , from bare metal deployment to switch configuration, is it possible? Do you have detailed steps on how to perform same operations in VMM?

    Thanks!

    /Dung

     
  • Friday, May 17, 2013 8:10 PM
     
     
    Sign In to Vote
    0

    This is the best guide I can find anywhere.

    http://www.thomasmaurer.ch/2013/04/hyper-v-converged-fabric-with-system-center-2012-sp1-virtual-machine-manager/

    It does not talk about bare metal.  It says this about a host....

    "Configure Hyper-V host

    After all the needed network definitions like Logical Networks, Port Profiles and the Logical Switch have been created, the Hyper-V host configuration will follow next. Make sure you to already have the management IP address assigned to one of the 10 GbE network interfaces and the host is also domain joined. Virtual Machine Manager will use the same network settings from this physical NIC to configure the Virtual Network Adapter."

    The assumption there would be that you have installed Windows 2012 OS on a physical host and enabled Hyper V and put an IP on 1 NIC (So SCVMM can reach out to it and configure it).

    Thanks, -Lindy

     
  • Tuesday, May 21, 2013 7:25 PM
    Moderator
     
     
    Sign In to Vote
    0

    Did you read that blog post, because it should explain all the required steps to get this up and running.

    1. Configure all the logical network parts within VMM prior to adding any hosts. Also, create VM network for each logical network that is associated with the logical networks.

    2. Create host group or use the existing one. However, make sure these logical networks are available to the host group.

    3. add the hosts to VMM (discovery and installation of vmm agent)

    4. Associate the physical adapters on the hosts that should participate in the team with the logical networks.

    5. Create logical switch with preferred teaming mode and load algorithm, containing virtual port profiles and uplink port profiles

    6. Assign the logical switch to the host and add physical NICs to the team and create required virtual adapters. 

    so to answer your question, yes you can add the host to VMM, let VMM take care of the teaming (using LACP fo) apply the logical switch to the host.

    But for this to work you can't have a team present on your host prior to this. VMM must be the master of disaster in this scenario, handeling everything.

    The reason for this may be hard to understand at first, but you'll get there once you explore all the opportunities this gives.

    -kn

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

     
  • Tuesday, May 21, 2013 7:29 PM
    Moderator
     
     
    Sign In to Vote
    0

    and yes - vmm can handle this from the early beginning, including bare-metal.

    -kn

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