Link Aggregation to HP ProCurve 4000m

Followup -

I have re-read the HP ProCurve 4000 manual. The manual suggests that Trunking works with HP UNIX and Windows NT servers (in 1998, that makes sense). The manual does state the switch supports 802.3ad (link aggregation), but outside trunking and meshing, the terms link aggregation is not mentioned in the documentation.

Meshing requires the VLAN option be active; however you do not have to have a VLAN setup and in use. HP uses the term "load balancing" for trunking and meshing. Meshing seems to be applied to switches only from the reading I have done.

HP offers three trunk configurations -

1) Trunk (Sounce address/Destination address) which works with other switches, a Sun trunking server, and Windows NT and HP-UX workstations.

2) Trunk (Source address only) which is for forwarding devices such as low-end switches.

3) FEC (Fast EtherChannel) which is for devices such as some Cisco switches, routers and workstations.

Does any of these option look correct for use with Mac OS X Server link aggregation?

Thanks

Cisco EtherChannel is a proprietary link-aggregation
protocol; I actually think Cisco invented it before
802.3ad was ratified.

What you want to use on your HP is 802.3ad, as it's
the international standard. I posted a thread myself
about link aggregation with Cisco switches, and a
replying poster told me to disable EtherChannel and
just use 802.3ad.

Are you sure you've got the latest firmware &
documentation for your switch? It's more than
possible that 802.3ad support was changed since the
switch was manufactured...

Chris --

While the old ProCurve 4000 says it supports 802.3ad, I think it is only for switch to switch interconnections. I just downloaded and updated the ProCurve 4000's firmware via TFTP. So it is current as of the April 2006. I thought perhaps with the firmware update, I would have a clear choice to turn on link aggregation, but my choices are still trunking and meshing.

Thanks.

PS --> Any advise on solid switches that do support Mac OS X Server link aggregation?

Leif -

Thanks for your insights. The HP 4000 series ProCurve does not have a CLI, just a web and console (menu) interface. I can try turning on STP and setup the OS X Server link aggregation. I will test that this evening when people are off the network and record the results. I shall post them here later today if I get time.

PS --> good to see another Scandanavian here. My son's name is Erik Perison Lund. <grin>

Thanks.

As I understand it LACP in newer HP switches is
"always on" ("standby" - all ports are pontential
LACP ports).

If you try "bonding" your 2 interfaces in the mac you
can see what happens when you connect them to the
switch.

When connecting 2 newer HP switches you setup LACP
trunking in one switch and then the other
automatically "get's it" : TRK1<->DYN1

You also need STP : Spanning Tree (maybe RSTP: Rapid
Spanning Tree is sufficient) on.

As I understand it LACP in newer HP switches is
"always on" ("standby" - all ports are pontential
LACP ports).

Turns out the older (1998) ProCurve 4000m does not have the "always on" feature. Even with the latest firmware updates, the switch does not seem to have LACP port abilities.

If you try "bonding" your 2 interfaces in the mac you
can see what happens when you connect them to the
switch.

You also need STP : Spanning Tree (maybe RSTP: Rapid
Spanning Tree is sufficient) on.

I turned on STP for testing purposes in creating a link aggregate with the ProCurve 4000; this had no positive effect on the intended outcome. As with a few other posts on ProCurve units, I also activated VLAN capability. However, I did not create any VLANs.

Looks like link aggregation fro ProCurve 4000m series is a dead issue.