Issue 1: CFE failed to update all forwarding-rules pointing to BigIP instance type on failover.
We created more than 200 forwarding-rules targeting the active instance group. On triggering failure, F5 successfully failover to the other device but CFE fails to update all the forwarding-rules in GCP. It updated few rules but not all.
I did run reset failover state and tried agin to failover and saw the same issue.
Issue 2: CFE seems to update forwarding-rules sequentially.
CFE seems like not using GCP batch updates to modify forwarding-rules on failover. Time to failover complete is depending on the number of forwarding rules. With 200+ forwarding rules, complete failover takes close to 5 minutes.
Description
Issue 1: CFE failed to update all forwarding-rules pointing to BigIP instance type on failover. We created more than 200 forwarding-rules targeting the active instance group. On triggering failure, F5 successfully failover to the other device but CFE fails to update all the forwarding-rules in GCP. It updated few rules but not all. I did run reset failover state and tried agin to failover and saw the same issue.
Issue 2: CFE seems to update forwarding-rules sequentially. CFE seems like not using GCP batch updates to modify forwarding-rules on failover. Time to failover complete is depending on the number of forwarding rules. With 200+ forwarding rules, complete failover takes close to 5 minutes.
Template
https://github.com/F5Networks/f5-google-gdm-templates/tree/master/supported/standalone/3nic/existing-stack/byol
Severity Level
Severity: 2