Bug ID 513916: String iStat rollup not consistent with multiple blades

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP All(all modules)

Known Affected Versions:
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 HF1, 11.5.3 HF1, 11.2.1, 11.4.1, 11.6.0, 11.6.1, 11.6.2, 11.6.3,,,,, 11.6.4, 11.6.5,,,, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF6, 11.5.3 HF2, 11.4.1 HF10, 11.2.1 HF15

Opened: Mar 23, 2015

Severity: 3-Major

Related Article: K80955340


An iStat of type string does not merge consistently in a multi-bladed chassis, so the value read on different blades at the same time may differ.


The value of the iStat after the merge differs on different blades.


The iStat must be of type string, and the chassis must have multiple blades.


Use clsh to write the string iStat value to all blades together.

Fix Information

The rollup of strings is based on a timestamp of the last update, but this value was not preserved through the first level of merge so the second level done on each blade was arbitrary. Now, the value is preserved, so the iStat value for multiple blades is correct.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips