Last Modified: Oct 04, 2024
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1
Opened: Jul 25, 2023 Severity: 4-Minor
After failover, newly active BIG-IP does not refresh the server nexthop value when a routing change occurs. This is an intermittent issue.
Connection failure until the flow entry is deleted.
BIG-IP in high availability (HA) scenario with connection mirroring. A network failure triggers a failover and also stops the newly active from reaching the server nexthop. A routing change (eg: bgp peering timeout) occurs which should trigger a recalculation of the server nexthop mac-address.
Clear the connflow entry from the table. Remove connection mirroring. Reconfigure network so that active and standby have equal access to the network in the event of failure. Use VRRP/HSRP or similar on the downstream network.
None