Loading...
Loading...
If a user, deletes a fqdn pool on one BIG-IP in a cluster and then run a manual config sync with another BIG-IP, the change fails to sync with the other BIG-IPs in the cluster.
FQDN pool delete failed in another BIG-IP and manual config sync operation is failed.
- Create fqdn pool in one BIG-IP - Save sys config - Run config sync - Delete fqdn pool - Save sys config - Run config sync manually Result: After deleting fqdn pool in BIG-IP and config sync with another BIG-IP, Manual config sync failed. Still, we can see the deleted fqdn pool in another BIG-IP
The workaround for this issue is to use auto-sync.
None
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.