[f-nsp] linux 802.3ad bonding with foundry switch

[Nick Hilliard]

On 23/09/2011 06:21, panicloop wrote:
> This switch model is "Foundry FirstIron Edge 12GCF".
> 
> And according to the customer, they are trying to change "passive" to "active"
> or adding another parameter such as "key XXX" or "type server",
> but it seems that nothing help this problem.

panicloop,

If you're deploying a trunk to a standard linux box (i.e. not running
VMware ESX), then you will want to run something like this on your brocade
ports:

--
no trunk ethernet 9 to 10
trunk deploy
interface ethernet 9
 link-aggregate configure key 1234
 link-aggregate active
interface ethernet 10
 link-aggregate configure key 1234
 link-aggregate active
--

You do not need static trunk configuration which means that you should
remove the existing trunk configuration.

> and this said
> ESX doesn’t support link-aggregation protocols like LACP so a static trunk
> is a must.

Right.  If your linux server is actually running ESX then it won't support
LACP.  Either you will need ESX to use "Route based on ip hash" for NIC
Teaming and then configure static trunks on the switch:

--- begin ---
trunk ethernet 9 to 10
write memory
trunk deploy
--- end ---

Or else you should just configure the two ports as being in the same VLAN
and use some other hashing method on the ESX instance (e.g. "Route based on
the originating virtual port id" or something).

Nick