Forum Discussion
Port Fail-over
I have two 10G connections going from my LTM to two different cisco switches. Each port on the cisco switch is configured for vlan tagging 802.1Q. How can I configure the LTM to provide port fail over in the event one of the 10G interfaces goes down? I currently have one of the 10G interfaces configured and added to a vlan as a tagged interface.In the very near future we will be adding additional vlans and want all vlans to use the 10G interface.
8 Replies
- shaggy
Nimbostratus
HA groups. If the interfaces are configured in a port-channel (f5 trunk), it should be easy. https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip_redundant_systems_config_11_0_0/8.html
- Brad_Parker_139
Nacreous
I would suggest Cross-Stack Etherchannel(or distributed LACP) and create one big LACP trunk on the BigIP device. All your VLANs can be added to that trunk and you can utilize all links and have redundancy.
- John_131301
Nimbostratus
If I create a trunk on the BigIP that creates an ether channel, won't this cause spanning tree to disable one of the ports on the cisco switch? - Brad_Parker_139
Nacreous
Not if your switches support Cross-Stack Etherchannel also known as distributed trunking(HP calls it LACP-dt). With distributed trunking, Spanning Tree is not needed.
- Brad_Parker
Cirrus
I would suggest Cross-Stack Etherchannel(or distributed LACP) and create one big LACP trunk on the BigIP device. All your VLANs can be added to that trunk and you can utilize all links and have redundancy.
- John_131301
Nimbostratus
If I create a trunk on the BigIP that creates an ether channel, won't this cause spanning tree to disable one of the ports on the cisco switch? - Brad_Parker
Cirrus
Not if your switches support Cross-Stack Etherchannel also known as distributed trunking(HP calls it LACP-dt). With distributed trunking, Spanning Tree is not needed.
- THi
Nimbostratus
Isn't Cross-Stack Etherchannel link aggregation within a Cisco switch stack instead of two separate Cisco switches? I guess you were referring to "dual homing" BIG-IP to two separate switches.
I have a customer whom we helped to use two separate Nexus switches, with Virtual PortChannel (vPC), to dual home a BIG-IP pair with crossed LACP links and that works fine in this scenario. I assume Cisco VSS can do about the same. As Brad mentions spanning tree is not needed - and not recommended either..
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com