Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP All
Known Affected Versions:
11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4
Fixed In:
12.1.0, 11.6.1 HF1, 11.5.4 HF2
Opened: Jan 20, 2016 Severity: 2-Critical Related Article:
K22989000
In some specific cases the standby unit's secondary blade ZebOS daemons might not get started when it becomes active.
The new primary blade does not start some ZebOS daemons resulting in ospf not working as expected on the standby unit.
If the failover occurs as a result of the primary blade's mcpd restarting
Run the following tmsh command on the new active unit: bigstart restart tmrouted.
The BIG_IP system now correctly starts ZebOS daemons on the standby unit on a new blade that is starting up as a primary.