Bug ID 472310: BIG-IP may report getLopSensorData warnings at boot time or when changing a PSU

Last Modified: Jan 16, 2024

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

Known Affected Versions:
5.4.0 HF1, 5.4.0 HF2, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
5.0.0, 12.0.0, 11.5.4 HF2

Opened: Jul 18, 2014

Severity: 4-Minor

Symptoms

When booting a BIG-IP device, or performing a hot swap operation of one of its power supplies, the following kind of log messages may be displayed for a brief time: localhost warning chmand[7059]: 012a0004:4: getLopSensorData: LopDev: sendLopCmd: Lopd status: 1 packet: action=1 obj_id=115 sub_obj=0 slot_id=ff result=24 len=0 crc=6576 payload= (error code:0x24) localhost warning chmand[7059]: 012a0004:4: getLopSensorData: LopDev: sendLopCmd: Lopd status: 1 packet: action=1 obj_id=16f sub_obj=1 slot_id=ff result=1 len=0 crc=acaf payload= (error code:0x1) These messages should not persist, and when a real error occurs it should be accompanied by additional warnings and alerts from the system.

Impact

A few additional log messages that indicate a warning when there is no legitimate failure.

Conditions

The condition occurs when the sensor monitoring process tries to obtain information from power supply model types that are supported but not actually installed. It does this until it discovers the actual model type installed, or that no power supply is installed. The specific conditions under which this is likely to happen are when the BIG-IP software is re-started or a power supply is changed while the system is running.

Workaround

None. This is cosmetic.

Fix Information

getLopSensorData warnings are not logged with error code 0x24 for newly-inserted power supplies (PSUs).

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips