Last Modified: Sep 13, 2023
Known Affected Versions:
14.1.0, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 14.1.2, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 15.0.0, 15.0.1, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 15.1.0, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 15.1.1
16.0.0, 15.1.2, 184.108.40.206, 220.127.116.11
Opened: Jul 30, 2019 Severity: 3-Major
The Management interface flaps after rebooting the device, which may cause a momentary active-active condition in a high availability (HA) configuration.
Devices go active-active for a few seconds and then resume normal operation.
This can occur after rebooting the active or standby device in an HA configuration if the final management port configuration completes late in the startup sequence. This can be due to network conditions for the network the management port is connected to. This problem has been observed only on hardware platforms.
You may be able to work around this by changing the management port speed to 100/Fixed Duplex. For more information on changing the interface, see K14107: Configuring the media speed and duplex settings for network interfaces (11.x - 13.x), available at https://support.f5.com/csp/article/K14107. or Connecting serial failover cable between HA peers would prevent active/active issue from happening.
The startup sequence has been changed to confirm that management port configuration is complete before proceeding with HA processing.