HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Aruba & ProVision-based
Showing results for 
Search instead for 
Did you mean: 

LACP Load Sharing based on IP Source

Occasional Visitor

LACP Load Sharing based on IP Source

I'm trying to make a LACP trunk to my server, but I can't find the option to divide the outgoing traffic from my switch, based on the source IP address of the packet. On a Cisco switch the command would be 

port-channel load-balance src-ip

My switch is a Procurve 3400cl

Any ideas ?

Frequent Advisor

Re: LACP Load Sharing based on IP Source


if I remember correctly, there are no more firmware upgrades for this switch. What version are you running?

On new versions you can issue " trunk-load-balance" in global configuration mode and set it to L3 or L4 load-balancing.

Source-IP should work with L3 load-balancing, though I think L3 takes both Source and destination IP into account.

Occasional Visitor

Re: LACP Load Sharing based on IP Source


Im running

Image stamp:    /sw/code/build/makf
                Aug 24 2015 17:12:42

There are no "trunk-load-balance" option in global config.

What is the default load sharing option, if its not possible to set one.

Honored Contributor

Re: LACP Load Sharing based on IP Source

The manual says,


The two trunk group options (LACP and Trunk) use source-destination
address pairs (SA/DA) for distributing outbound traffic over trunked links.
SA/DA (source address/destination address) causes the switch to distribute
outbound traffic to the links within the trunk group on the basis of source/
destination address pairs. That is, the switch sends traffic from the same
source address to the same destination address through the same trunked link,
and sends traffic from the same source address to a different destination
address through a different link, depending on the rotation of path assignments
among the links in the trunk. Likewise, the switch distributes traffic for
the same destination address but from different source addresses through
different links.
Broadcasts, multicasts, and floods from different source addresses are distributed
evenly across the links. As links are added or deleted, the switch
redistributes traffic across the trunk group.