• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

HP Proliant Server adapter teaming

rsutoratosu

Platinum Member
So we have an argument in the office.. maybe someone with more knowledge would know this.

As far as I know, when you team the adapter for load balancing, it does not require any additional hardware... the software creates a virtual IP and assigns 2 ip to the 2 individual nic cards.

The cisco guys in the office is arguing that you need special team aware switches in order for the adapter teaming to work properly..

Any truth in that ? we feel that they're trying to get us to buy more cisco stuff.. but I can't be 100% sure

hp-team1.jpg
 
The cisco guys in the office is arguing that you need special team aware switches in order for the adapter teaming to work properly..

This is partially true. You need to have a switch that supports LACP in order to do bi-directional link aggregation.

If you're using teaming strictly for failover, then you don't need anything special on the switch.
 
Cisco guys are right. Your switch needs to be aware of what's going on if you're using it for load balance. Granted it doesn't HAVE to be Cisco gear to do it, but none the less they are right.
 
For strictly failover (active/passive) the switch(es) don't need to be aware.

For load balancing (active/active) on a single switch, the switch must support link aggregation.

For load balancing + failover (each server port connected to a different switch or blade), the switches need to be in a stacked (Cisco) / virtual chassis (Juniper) configuration.
 
Very similar to how vsphere does active/active - but there is no true load balancing, you need something smart like openflow to handle vpn port routing on a per connection basis.

Easier to just move up to faster networking.
 
In this case, you don't need switches as the NICs aren't doing LACP. In this case, the HP network drivers use round-robin MAC addresses when responding to ARP requests for that IP address. In that manner, they can aggregate without causing MAC flapping on the switch.

It's not as good a solution as LACP, but it is functional.

I typically avoid using it.
 
Back
Top