mhdcommunications
asked on
Server 2012 NIC Teaming does not work without all adapters 'connected'
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?
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?
strivoli
How did you set the ports on the switch side? Are they "Trunked"?
ASKER
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.
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.
Please post make, model and firmware version of the switch. Thank you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Issue resolved by itself, and not reproducable