Forum Discussion
AltostratusWhat's the difference between a "Trunk" and a LACP trunk?
I've noticed in the F5 interface that you can set up trunks on the F5 system in order to aggregate interfaces together. I know you can set up an LACP trunk, but the interface appears to let you set up a trunk without checking the "LACP" checkbox. If it's not doing LACP, what kind of protocol is the trunk using? What is the difference between that and a LACP trunk?
Without LACP selected, you will statically force link aggregation without a negotiating protocol. If on the other end you have a Cisco switch, this would be compatible with Etherchannel 'channel-group 1 mode on' configuration.
The only situation where static link aggregation makes technical sense is if on the other end you have a device which does not support LACP. Static aggregation is more susceptible to spanning-tree interference and switching loops
4 Replies
Hannes_Rapp_162Nacreous
Without LACP selected, you will statically force link aggregation without a negotiating protocol. If on the other end you have a Cisco switch, this would be compatible with Etherchannel 'channel-group 1 mode on' configuration.
The only situation where static link aggregation makes technical sense is if on the other end you have a device which does not support LACP. Static aggregation is more susceptible to spanning-tree interference and switching loops
AlgebraicMirrorThank you!
Hannes_RappNimbostratus
Without LACP selected, you will statically force link aggregation without a negotiating protocol. If on the other end you have a Cisco switch, this would be compatible with Etherchannel 'channel-group 1 mode on' configuration.
The only situation where static link aggregation makes technical sense is if on the other end you have a device which does not support LACP. Static aggregation is more susceptible to spanning-tree interference and switching loops
- AlgebraicMirror
Thank you!
