If you think that when HP purchased 3com they would have either made everything a single code release (can we say, Juniper) or at least provide interoperability documentation that is easier to find and easier to read? You’re dead wrong and you may end up like me and make an assumption that keeps you here longer than you would like to be trying to fix it. To spare you the agony of it all I will just jump right into it…
On the 3com switch setup your bridge-aggregation FIRST and in this order:
interface Bridge-aggregation #
link-aggregation mode dynamic
quit
interface gigabit #/#/#
port link-aggregation group #
quit
interface gigabit #/#/#
link-aggregation group #
quit
interface Bridge-aggregation #
port link-type trunk
port trunk permit vlan # # # #
port trunk pvid vlan #
Be VERY VERY careful with this. If you bring in a new interface into the Bridge-Aggregation group it doesn’t seem to want to apply the correct configuration to the port. What I have done is basically put the new interface into the existing Bridge-Aggregation group and then reissue all my port link-type, port trunk permit vlan and port trunk pvid vlan commands to force it to apply to the newly grouped interface. I know, this sucks.
Now, for the HP side of life:
trunk #,#, trk# lacp
That is all the configuration needed to get this setup and working. Hopefully you have found this helpful.
