로그인
 
홈라이브러리학습다운로드지원커뮤니티포럼
Resources for IT Professionals >
> 
> 
NIC Teaming

답변됨 NIC Teaming

  • 2012년 3월 6일 화요일 오전 8:40
     
     
    로그인하여 투표
    0

    Hi everybody!

    I couldn't find a Microsoft Connect program to provide feedback on Server 8 beta, so I decided to post here.

    I was quite eager to try out the new NIC teaming feature included in "8". I installed "8" as host OS on a lab computer, enabled the Hyper-V role amnd created an external virtual network that is shared with the management operating system (not the recommended setup, I know, but as a test computer it will have to do.)

    I created a VM installed with "8", gave it two synthetic NIC's connected to the same external network. Then it was time to have some fun.

    The guest OS detected "Wired Ethernet Connection" (NIC1) and "Wired Ethernet Connection 2" (NIC2), so I created a team called "Team 1" and added both NIC's into it. Then I had a teamed adapter with a link speed of 20Gbit to the virtual switch.

    Now, If I disconnect NIC2 (set it as "Not Connected" in VM settings) it will be in a "faulted" state in the teaming pane and speed will be reduced to 10Gbit. As expected.

    If I reconnect it and disconnect NIC1 instead, both adapters appears in a faulted state, the team adapter is disconnected and the network connection is lost. If I reconnect NIC1, networking is resumed, but NIC2 stays faulted until I disconnect and reconnect it again.

    It doesn't matter wether both are active or one is set as standby, if NIC1 is set as standby, NIC2 faults immediatly and NIC1 becomes active.

    Now, I know that my configuration is far from an ideal setup and I am unable to perform further tests at the moment (with additional NIC's or external networks), but is this kind of non-redundant behaviour expected due to my test machine being configured the way it is, or is it a beta bug?

    Note that I simply tested the feature itself this way, I don't have a spare NIC to setup another ext. virtual network, so maybe it works as it should if I did?



    • 편집됨 Mike_Andrews 2012년 3월 6일 화요일 오전 8:59
    • 편집됨 Mike_Andrews 2012년 3월 6일 화요일 오전 9:07
    •  
     

모든 응답

  • 2012년 3월 12일 월요일 오후 7:36
     
     답변됨
    로그인하여 투표
    0

    Hi Mike,

    Teaming is natively disabled in Virtual Machines. You will need enable Teaming for the Virtual Machine. 

    • Get-VmNetworkAdapter <VMName> | Set-VmNetworkAdapter -AllowTeaming On

    On the same note, a Team of only 2 NICs is supported on a VM.

    Thanks!



    JohnFernande [MSFT] | Support Engineer | Windows Distributed Systems | Bangalore, India. If an answer is Helpful, Please mark as answer. Others might find it helpful.

    • 답변으로 표시됨 Tiger LiModerator 2012년 3월 13일 화요일 오전 12:43
    •  
     
  • 2012년 4월 2일 월요일 오전 9:31
     
     
    로그인하여 투표
    0

    Hi!

    Sorry for not responding in a timely fashion, but I decided to try this properly before reporting back to you.

    That powershell command absolutely made the whole difference. Thank you! This post is going into my bookmarks.

    Since this would mean running the PS comman for every existing VM to enable NIC teaming inside guests, would now be a good time to suggest turning that into a check-box in the Hyper-V manager/Virtual Switch Manager GUI?

    Also, if you could please refer me to any documentation on this so we know what to expect if using guest teaming on higly available VM's in a fail-over cluster. Thank You!

    • 편집됨 Mike_Andrews 2012년 4월 2일 월요일 오전 9:36
    •  
     
  • 2012년 4월 12일 목요일 오전 4:18
     
     
    로그인하여 투표
    0

    Hi Mike,

    I am the Technical Writer for NIC Teaming. The latest Windows Server 8 "Beta" NIC Teaming documentation is here: http://download.microsoft.com/download/E/1/3/E13C9AD6-B4D6-4041-97E0-6BDC48273BC7/Windows Server 8 Beta NIC Teaming (LBFO) Deployment and Management.docx. We are only in beta, so look for more information here in the future: http://technet.microsoft.com/en-us/library/hh831648.aspx.

    Corey