Loading...
Loading...
If a secondary blade in a 'ready' state becomes primary and then quickly is disabled, it does not send a cluster packet for ten seconds. A new primary, therefore, is not elected for ten seconds (the heartbeat timeout), instead of the expected time (immediately). The other blades, including the new primary, never receive the message that the blade was set to disabled, so the blade is be re-enabled without the user requesting it.
A blade that the user expects to be disabled is spuriously re-enabled. User interfaces to access configuration, such as tmsh and the GUI might hang for the ten-second interval. The system posts an error message similar to the following: load_config_files: '/usr/bin/tmsh -n -g load sys config partitions all base' - failed. -- Unexpected Error: Saving and loading configuration is only allowed on the primary slot.
This occurs only if the blade disable operations occur very shortly after the primary blade is moved.
Wait ten seconds after disabling a blade before disabling another blade.
A previously disabled blade is no longer spuriously re-enabled if the primary blade is moved around quickly.
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.