Bug ID 495024: Policy flow's nexthop not always updated when route pool member status changes

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Opened: Dec 06, 2014
Severity: 3-Major

Symptoms

Policy flow's nexthop is not always updated when route pool member status changes.

Impact

IPsec traffic continues to use the down pool member.

Conditions

This issue shows when an IPsec flow is routed via a gateway pool. When a monitored gateway pool member is detected to be down, a different member is selected as the gateway. The policy flow's nexthop is not always updated to reflect the member switch.

Workaround

None.

Fix Information

None

Behavior Change