Bug ID 1710765: The node number fetched by the SNMP disk stats handler from the disk operational handler has the wrong blade value.

Last Modified: Jun 19, 2025

Affected Product(s):
F5OS F5OS-C, Install/Upgrade, Velos(all modules)

Known Affected Versions:
F5OS-C 1.8.0

Fixed In:
F5OS-C 1.8.1

Opened: Oct 29, 2024

Severity: 3-Major

Symptoms

Rarely, SNMP command output may not show up the disk stats for a particular blade. This could happen because of incorrect blade value of the blade fetched from the backend. The partition "velos.log" file may show below logs: 1. <Timestamp> default platform-stats-bridge[8]: nodename=controller-2(p1) priority="Err" version=1.0 msgid=0x4305000000000007 msg="" msg="Invalid slot value." value=761491247. 2. <Timestamp> default platform-stats-bridge[8]: nodename=controller-2(p1) priority="Err" version=1.0 msgid=0x4305000000000007 msg="" msg="Failed to assign blade instance" value=761491247.

Impact

SNMPWalk will miss the disk utilisation stats of problematic blade.

Conditions

1. Upgrade the partition 2. Configure SNMP community of any version 3. Execute SNMPWalk command on the disk stats table MIB.

Workaround

As a workaround, either restart the platform-stats-bridge container of the partition or disable/enable the partition from Confd.

Fix Information

As a workaround, either restart the platform-stats-bridge container of the partition or disable/enable the partition from Confd.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips