Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP All
Known Affected Versions:
11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1
Fixed In:
12.0.0, 11.6.1 HF1, 11.5.4 HF2
Opened: Oct 08, 2014 Severity: 4-Minor Related Article:
K70333230
Some gauges in the MIB are incorrectly typed as 32-bit integers. This might cause large values to display as negative numbers.
Display of values is incorrect.
Values that are incorrectly typed may display incorrectly.
None.
MIB variables have been correctly typed as Gauge32, which is unsigned, and will not display as a negative number when it grows large.
before fix [root@localhost:Active:Standalone] images # tmsh modify ltm pool bob queue-depth-limit 4000000000 [root@localhost:Active:Standalone] images # snmpwalk -v 2c -c public localhost F5-BIGIP-LOCAL-MIB::ltmPoolQueueDepthLimit F5-BIGIP-LOCAL-MIB::ltmPoolQueueDepthLimit."/Common/bob" = INTEGER: -294967296 [root@localhost:Active:Standalone] images # after fix [root@localhost:Active:Standalone] config # tmsh create ltm pool test [root@localhost:Active:Standalone] config # tmsh modify ltm pool test queue-depth-limit 4000000000 [root@localhost:Active:Standalone] config # snmpwalk -v 2c -c public localhost F5-BIGIP-LOCAL-MIB::ltmPoolQueueDepthLimit F5-BIGIP-LOCAL-MIB::ltmPoolQueueDepthLimit."/Common/test" = Gauge32: 4000000000 [root@localhost:Active:Standalone] config #