Forum Discussion
2 Replies
- natheCirrocumulus
Sounds like you're using aggregated links / trunks from your description. If so then I'd recommend HA Group to monitor the health of the interfaces within this trunk. i.e. if an interface goes down then possibly failover.
I believe this is recommended over vlan fail-safe as it's quicker to failover (it's called Fast Failover). But for extra redundancy then vlan fail-safe is an option. Basically it checks that traffic is traversing this vlan (on a per vlan basis) and if not then it will initiate traffic before deeming that there is an issue (interface down) and failing over.
Hope this helps,
N
- Gambler_168259Nimbostratus
Yes Nathan,
We have two upstream Cisco Nexus 5000 L3 Switches and both our F5 LTM Load Balancers have connected to them in full mesh i.e. LTM-01 is connected to Nexus-01 & Nexus-02, similarly LTM-02 is connected to Nexus-01 and Nexus-02 as well + Both LTM are connected to each other on HA VLAN trunk and with heartbeat cable as well.
Two VLANs are configured on it External VLAN & Internal VLAN. Both VLANs have their floating IPs.
What we had do is that we had disable layer-3 connectivity of nexus-01 with client upstream core router and the primary path definitely went unavailable for traffic and in the meanwhile it switches to the secondary nexus-02 which is having a layer-3 link with client upstream secondary router. We then observes a drop with request time-out in the continuous ping + a service disruption as well and the active LTM-01 appears as Backup and the backup LTM-02 appears as primary without even a manual intervention or without even using any manual forceful standby option in LTM.
Looking for response.