Loading...
Loading...
BIG-IP tenant that is running on appliance that goes down for reboot becomes active, causing current active peer tenant to go briefly standby.
Traffic impact is observed until the newly active tenant stops and the peer tenant returns to the desired active state. Typically up to two minutes.
-- BIG-IP tenants running on F5OS -- Appliance that is running a standby tenant is rebooted (e.g., during an upgrade)
Prior to rebooting or upgrading the appliance: -- Stop the standby tenant (for example, set tenant's running-state to Configured or Provisioned from F5OS) -- Or force offline the standby tenant
None
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.