vlan 1

[Vince-Whirlwind]

Thank you, that is very well explained.

Here is why I don't use dynamic protocols:

When I design a network I don't design a network where PCs are connected to link-aggregated ports on a switch. It just doesn't happen.
In fact, I really can't remember using link aggregation on copper ports, and although I deal with PCs that use fibre connectivity at the access layer, those networks are so tightly controlled that I'm pretty sure if anybody connected a PC to link agg port, they'd be fed to the sharks, and rightly so.

As with many of us I guess, my formal network training was originally in Cisco. Cisco had (from memory)
"passive" - which was rubbish and a complete waste of time
 "active" - which really only worked in a pure Cisco environment
"on" - which worked.

From there, as we tried to get our customers to stop wasting their money on Cisco, and as we added good stuff like HP Procurve to their networks, we used Cisco "ON" and HP "Trunk" and it all worked fine.

I have implemented recent 3COM networks. It is powerful kit, and on the whole, it's the way to go for a good many applications, which pains me to say because I am so not a fan of the whole operation at 3COM, from design to business, to the security aspect of where it comes from. I can't recall my configs, but whatever it was, it was going to play nice with Cisco "On" and HP Procurve "Trunk", so nothing dynamic, regardless of how 3COM labels it.

[VoIP-Buddy]

Hi Vince!

I agree with you.  We most often see this on upward or downward links to switches.  HOWEVER, there is a very good reason to use them to servers that support dynamic Link-aggregation.  You get increased aggregated bandwidth for each port connection.  The only caveat is that if they all aren't the same speed, the link will run at the speed of the slowest port.

One reason to consider copper ports is that there are models of the 5130 EI family that support 10g on copper ports.  Typically we would see fiber to a server but we now have a copper solution too.

Regards,

David

[Vince-Whirlwind]

I find when creating a link aggregation for a server, I am at the mercy of the server guy and what he understands about configuring link aggregation on his server (which usually approximates to about nil).
Generally, he will do something undocumented and on the fly and then I have to use trial and error to come up with the link agg config on my switch that works with whatever he has done.

I used DAC to connect two Core switches once, so I guess I lied about never using copper for link aggs.