Forum Discussion
How to setup F5 LTM HA network
- Jan 04, 2018
Agree with nitass, don't use failover port. A number of limitations and basically no worthwhile advantages
I'd use both 1G interfaces that are already populated with GbE SFPs for HA, configured as LACP Port Trunk. You will need more SFPs for data though.
Observing the ports available, you cannot evenly allocate remaining ports for segregated client-side and server-side LACP bundles. So I'd bundle 2x 10G interfaces as LACP port trunk for data, and use this 20G link for both, client-side and server-side VLANs.
Here's summary
- 2x 1G interfaces directly to other unit for HA functions. Config sync, Network failover, Traffic mirror
- 2x 10G to network switch stack. All client-side and serve-side traffic
- Mgmt to network switch (ideally dedicated management switch). SSH and HTTPS (GUI)
Agree with nitass, don't use failover port. A number of limitations and basically no worthwhile advantages
I'd use both 1G interfaces that are already populated with GbE SFPs for HA, configured as LACP Port Trunk. You will need more SFPs for data though.
Observing the ports available, you cannot evenly allocate remaining ports for segregated client-side and server-side LACP bundles. So I'd bundle 2x 10G interfaces as LACP port trunk for data, and use this 20G link for both, client-side and server-side VLANs.
Here's summary
- 2x 1G interfaces directly to other unit for HA functions. Config sync, Network failover, Traffic mirror
- 2x 10G to network switch stack. All client-side and serve-side traffic
- Mgmt to network switch (ideally dedicated management switch). SSH and HTTPS (GUI)
Excellent!! this what i need. you have explain in perfect manner which i need. Do i need to do anything on switch level for LACP Port Trunk?
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