Bug ID 1250925: Alarm for AOM fault due to "LOP Runtime fault detected: lop:nc-si-rmii:failure"

Last Modified: Oct 21, 2024

Affected Product(s):
F5OS AFM(all modules)

Known Affected Versions:
F5OS-A 1.1.1, F5OS-A 1.2.0

Fixed In:
F5OS-A 1.8.0

Opened: Feb 22, 2023

Severity: 3-Major

Symptoms

The AOM may report a runtime fault after a failure to configure the NC-SI RMII interface. This results in a system alarm for "Fault detected in the AOM" and an event indicating that "LOP Runtime fault detected: lop:nc-si-rmii:failure".

Impact

The AOM uses the NC-SI RMII interface to allow external SSH access directly to the AOM through the management interface. When the interface configuration fails, then the AOM is not accessible via SSH.

Conditions

The conditions causing the LOP runtime fault for NC-SI RMII interface configuration are not known.

Workaround

A reset of the AOM can correct this issue. Login to the system as root. Issue the following command to reset the AOM. docker exec -ti platform-hal psf POST:lop/object/reset-device device=Aom Wait approximately 10 minutes and check the AOM runtime status to verify the the "LOP Runtime fault detected: lop:nc-si-rmii:failure" condition has cleared. docker exec -ti platform-hal psf GET:lop/object/health For example, a healthy LOP with no runtime status faults will return "runtimeStatus" equal to zero as shown below. [root@appliance-1 ~]# docker exec -ti platform-hal psf GET:lop/object/health field | value -----------------------------+-------- postBitDescriptionItems | [] postStatus | 0 runtimeBitDescriptionItems | [] runtimeStatus | 0

Fix Information

Fixed with AOM version 2.00.350.0.1 and later.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips