Talk:Link aggregation
From Wikipedia, the free encyclopedia
Contents |
[edit] Redirects to this page
The following redirects have been created that link to this article:
- 802.3ad
- ethernet trunk
- ethernet trunking
- link aggregate group
- NIC teaming
- port trunking
- port teaming
[edit] OSI layer
What OSI layer does link aggregation occur at? —The preceding unsigned comment was added by 192.91.171.36 (talk • contribs).
- I guess it would conceptually fit between layers one and two. The data link layer (OSI layer 2) would be deciding which trunk to pass the data to. Then you'd have the aggregation layer splitting it between the ports and then the physical layer (OSI layer 1) for each port. Plugwash 21:02, 7 May 2006 (UTC)
[edit] Deleted this
- Some low-cost switches will typically have 24 or 48 10/100-mbit ports, and two additional gigabit ports for the backbone. The expected usage is that there is a 1-gigabit backbone, and the second gigabit port passes the backbone data along to the next switch in the network closet.
- While the two 1-gigabit ports may support operating as a single 2-gigabit trunk, there is no way for the switch to pass this 2-gigabit trunk along to additional switches. For a network with an expected maximum backbone speed of 2-gigabits, this is acceptable in a remote closet that can be fully served by the single switch with only 24 or 48 10/100-mbit ports. It is also acceptable if there a lot of switches in a closet and a single expensive switch can be used to manage all their uplinks.
We probably all know which switch he is describing and it should be patently obvious that if you are using this switch and decide to use BOTH of the gig ports for a downlink, then you won't have any ports left over to uplink. This has nothing to do with Link Aggregation and clearly not a limitation of it.
[edit] LACP
LACP is part of the 802.3ad specification, yet is not mentioned in this article. Anyone care to add it in the appropriate place? fonetikli 23:00, 20 July 2006 (UTC)
[edit] Another redirect
Redirecting 'ethernet bonding' here would be good. 83.27.231.169 20:15, 31 August 2006 (UTC) Kosma
[edit] Network Availability
I'm not a networking guru, but shouldn't there be some more reference to aggregation being used for network availability & redundancy rather than just bandwidth? I've seen it used a few times, and always for this purpose.
Also, how does 'static' and 'dynamic' link agregation fit in? zorruno 23:56, 7 September 2006 (UTC)
- There is a mention of it, but it only protects against link failures not equipment failures. Plugwash 22:28, 14 October 2006 (UTC)
