Solved

Server 2012 NIC Teaming does not work without all adapters 'connected'

Posted on 2014-01-29
5
569 Views
Last Modified: 2014-03-02
I have used Broadcoms BACS suite or the HP Teaming Software to team adapters prior to Server 2012. I am now, unfortunately, required to use the Server 2012 native NIC Teaming function since HP no longer provides, or supports, using their utility with 2012. Not a HUGE issue, but it's not working as the 3rd Party software method has in the past.
I have 2 x QP HPNC365T adapters, for a total of 8 ports. No matter the Teaming method used (Static, LACP, Switch Independant) the Team does not function unless ALL the adapters have link. Is this by design? I would imagine if you are using it for speed/fault tolerance, they would have taken that into consideration. Also, there is no way to create multiple virtual VLAN adapters, as you can with the BACS suite (im not sure if the HP Teaming Software can do this). Am i missing something?
0
Comment
Question by:mhdcommunications
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 19

Expert Comment

by:strivoli
ID: 39820411
How did you set the ports on the switch side? Are they "Trunked"?
0
 
LVL 1

Author Comment

by:mhdcommunications
ID: 39822191
Yes, the ports are trunked. When using LACP, i made sure the ports had LACP enabled on the switch.

Still wondering how the native NIC Teaming in Server 2012 provides 'fault tolerance' or 'link aggregation' if a single port being unplugged/going bad brings the whole team down.
0
 
LVL 19

Expert Comment

by:strivoli
ID: 39823284
Please post make, model and firmware version of the switch. Thank you.
0
 
LVL 1

Accepted Solution

by:
mhdcommunications earned 0 total points
ID: 39885921
I thought i had previously closed this, my apologies.

This issue is resolved. I'm not sure if the problem was with the OS, but i was able to get it to work.

After installing updates (inadvertently) i deleted and re-created the Team, only this time, i did not attempt to manually set the teaming method. I accepted defaults, and viola - Team up and running. I was not able to reproduce the issue again, even after manually re-creating and setting teaming method. Im not sure if it was a windows update that fixed it, or what. NO settings were changed on my switches, fyi.
0
 
LVL 1

Author Closing Comment

by:mhdcommunications
ID: 39898339
Issue resolved by itself, and not reproducable
0

Featured Post

Revamp Your Training Process

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
For many of us, the  holiday season kindles the natural urge to give back to our friends, family members and communities. While it's easy for friends to notice the impact of such deeds, understanding the contributions of businesses and enterprises i…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…

733 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question