Symptoms

The system may report a transient error for a fault in the AOM/LOP due to not receiving health reports from all installed VFC (fantray) or VPC (PSU controller) cards, and then the error condition is resolved only a couple of seconds later. For example, the error condition occurring: 65543 controller-1 aom-fault ASSERT ERROR "Fault detected in the AOM" "2020-12-30 01:16:32.522027731 UTC" 65543 controller-1 aom-fault EVENT Network Access "Asserted: LOP is not receiving health reports from all installed VPC cards" "2020-12-30 01:16:32.522051183 UTC" The resolution of the error two seconds later: 65543 controller-1 aom-fault CLEAR ERROR "Fault detected in the AOM" "2020-12-30 01:16:34.184866455 UTC" 65543 controller-1 aom-fault EVENT Network Access "Deasserted: LOP is not receiving health reports from all installed VPC cards" "2020-12-30 01:16:34.184891732 UTC" These transient error reports do not indicate an AOM/LOP fault and can be ignored.

Impact

The transient error report for an AOM/LOP fault caused by not receiving health reports from all installed fantrays and PSU controllers can be ignored.

Conditions

No special conditions cause the transient error report for an AOM/LOP fault caused by not receiving health reports from all installed fantrays and PSU controllers. It may occur at any time.

Workaround

The transient error report for an AOM/LOP fault caused by not receiving health reports from all installed VFC(fantray) and VPC(PSU controller)cards can be ignored.

Fix Information

Fixed in CC-LOP firmware v1.00.1085.00.1 and later available with F5OS-C 1.2.0.

Behavior Change