https://community.hpe.com/t5/operating-system-linux/how-to-enable-lacp-mode-4-bonding-to-two-switches-with-4-nics/m-p/4510212#M82345 never mind. seems to work with a single bond spread across two switches as well, even in LACP mode. Thu, 08 Oct 2009 08:19:35 GMT lightxx 2009-10-08T08:19:35Z https://community.hpe.com/t5/operating-system-linux/how-to-enable-lacp-mode-4-bonding-to-two-switches-with-4-nics/m-p/4510211#M82344 ok. so i've got a bunch of C7000 blade enclosures here, loaded with BL460c blades. each blade has 4 eth ports. 2 ports are connected to switch A, two ports to switch B.<BR /><BR />on a windows host, i can use the HP network configuration utility to create a team which consists of TWO LACP trunks (one to switch A, one to switch B, each consisting of two eth ports), which results in a team that has fail-over/redundancy and load balancing, and can send with 4Gbs and receive with 2Gbs, and appears as ONE logical interface.<BR /><BR />with linux (Debian Lenny in this case), things are a bit different. <BR />i can create two bonds with two IPs (for 2 NICs for each uplink switch), but this is not what i want. i want the windows counterpart, where i have just ONE IP for the entire team consisting of four nics, that is, one logical interface.<BR /><BR />any ideas how to do that? Thu, 08 Oct 2009 07:50:52 GMT https://community.hpe.com/t5/operating-system-linux/how-to-enable-lacp-mode-4-bonding-to-two-switches-with-4-nics/m-p/4510211#M82344 lightxx 2009-10-08T07:50:52Z https://community.hpe.com/t5/operating-system-linux/how-to-enable-lacp-mode-4-bonding-to-two-switches-with-4-nics/m-p/4510212#M82345 never mind. seems to work with a single bond spread across two switches as well, even in LACP mode. Thu, 08 Oct 2009 08:19:35 GMT https://community.hpe.com/t5/operating-system-linux/how-to-enable-lacp-mode-4-bonding-to-two-switches-with-4-nics/m-p/4510212#M82345 lightxx 2009-10-08T08:19:35Z