It also provides logical link indication. For example, if two switches are connected via a LAG with LACP enabled and one of the switches crashed but physical link did not drop, then at the end of the LACP timeout the switch that is still up would declare the link disconnected. If the two switches were connected via a static LAG and one crashed without bringing down physical link, there would be no indication to the running switch that the LAG was now connected to an non-functional switch.
Thank you so much! I appreciate it. That explains my whole confusion. In the help section on the OpenManage interface of the switch, it mentioned a little bit of that, but I appreciate a clear answer. Thank you.
bh1633
909 Posts
1
November 9th, 2009 11:00
LACP provides protection against mis-cabling.
It also provides logical link indication. For example, if two switches are connected via a LAG with LACP enabled and one of the switches crashed but physical link did not drop, then at the end of the LACP timeout the switch that is still up would declare the link disconnected. If the two switches were connected via a static LAG and one crashed without bringing down physical link, there would be no indication to the running switch that the LAG was now connected to an non-functional switch.
ryanmoat
4 Posts
0
November 9th, 2009 11:00
Thank you so much! I appreciate it. That explains my whole confusion. In the help section on the OpenManage interface of the switch, it mentioned a little bit of that, but I appreciate a clear answer. Thank you.
PartTimeGeek
3 Posts
0
December 29th, 2010 11:00
Why does the Manual for the 28xx series show LACP support? Doesn't that include Dynamic Link Aggregation?
I am trying to determine the best mode for link bonding for a PowerEdge 2950 running PROXMOX to a PowerConnect 2824.
Proxmox is Debian-Based and here are the modes:
http://www.debianhelp.co.uk/bonding.htm
Thanks.