Last Modified: May 29, 2024
Affected Product(s):
F5OS (all modules)
Known Affected Versions:
F5OS-C 1.5.0, F5OS-C 1.5.1
Fixed In:
F5OS-C 1.6.0
Opened: Jan 27, 2023 Severity: 3-Major
LOP RX timeout error messages seen in velos.log for non-existing blade.
Error messages will be logged in velos.log once in every hour.
As part of background-monitoring, we are running a task to monitor the power on hours of each blade. This task is creating the errors in velos.log.
NA
LopBladePresentNotification is sending slotID as 1 based index, which causes the monitoring of the subsequent blade, as diag-agent expects it to be 0 based index. Updated LopBladePresentNotification to 0 based index.