Last Modified: Sep 07, 2026
Affected Product(s):
F5OS F5OS, F5OS-A, F5OS-C, Velos
Known Affected Versions:
F5OS-A 1.5.2, F5OS-A 1.7.0, F5OS-A 1.8.0, F5OS-A 1.8.1, F5OS-A 1.8.2, F5OS-A 1.8.3, F5OS-A 1.8.4, F5OS-A 1.8.4-HR1, F5OS-A 1.8.4-HR2, F5OS-C 1.6.0, F5OS-C 1.6.1, F5OS-C 1.6.2, F5OS-C 1.6.4
Fixed In:
F5OS-C 1.8.0, F5OS-A 1.5.3, F5OS v2.0.0, F5OS v2.0.0
Opened: Aug 07, 2024 Severity: 3-Major
When running an snmpwalk that includes the coreTotal5minAvg OID, you may encounter one of the following errors. - Timeout error (most common) Timeout: No Response from 10.170.9.16 - General error (less common) Error in packet Reason: (genError) A general failure occured
Error in the packet Reason: (genError) A general failure occurred Failed object: iso.3.6.1.4.1.12276.1.2.1.1.3.1.6.8.112.108.97.116.102.111.114.109.0
- snmpwalk on an MIB that includes coreTotal5minAvg - The polling is done for CPUs that are not present
Approximately two minutes after the system starts, the platform-stats-bridge logs the following message: msg="DB ready check done" NAME="SnmpCpuStatsHandler". After this log message appears, you can check the coreTotal5minAvg.
Modified the code to not execute the snmpwalk for offline cpus.