Bug ID 489499: chmand needs to check for LopUnsSensClientExists status after registering for unsolicited alerts with lopd

Last Modified: Oct 17, 2023

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

Known Affected Versions:
11.2.1, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.1, 11.6.2, 11.6.3,,,,, 11.6.4, 11.6.5,,,, 12.1.0, 12.1.1, 12.1.2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.0.0

Fixed In:
13.0.0 HF1

Opened: Nov 07, 2014

Severity: 3-Major


chmand fails to register for unsolicited LOP events, meaning that asynchronous alerts from lopd will not seen or reported by chmand. A message is seen in /var/log/ltm that contains the phrase, "failed to register for LOP at <address>"


Asynchronous events from lopd will not be reported or handled, such as fan tray removal/insertion and PSU removal/insertion. Alerts that are driven by system_check through polling sensor values and comparing them to specified limits, however, will still be operational.


Occurs when chmand has been re-started after it has already synchronized once with lopd.


Re-start lopd: # bigstart restart lopd

Fix Information

Modified chmand to recognize the case where unsolicited alert registration with lopd has already occurred so that it no longer treats it as an error.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips