Table 28. Event descriptions and recommended actions (continued)
Number
Severity
Description/Recommended actions
●
If event 359 has been logged for the indicated channel, indicating the condition no longer
exists, no further action is required.
●
If the condition persists, this indicates a hardware problem in one of the controller modules
or in the controller enclosure midplane. For help identifying which FRU to replace, see
Troubleshooting and problem solving
.
Warning
Some, but not all, PHYs are down for the indicated disk channel.
Recommended actions:
●
Monitor the log to see whether the condition persists.
●
If event 359 has been logged for the indicated channel, indicating the condition no longer
exists, no further action is required.
●
If the condition persists, this indicates a hardware problem in one of the controller modules
or in the controller enclosure midplane. For help identifying which FRU to replace, see
Troubleshooting and problem solving
.
359
Info.
All PHYs that were down for the indicated disk channel have recovered and are now up.
Recommended actions:
●
No action is required.
360
Info.
The speed of the indicated disk PHY was renegotiated.
Recommended actions:
●
No action is required.
361
Critical, Error,
or Warning
The scheduler experienced a problem with the indicated schedule.
Recommended actions:
●
Take appropriate action based on the indicated problem.
Info.
A scheduled task was initiated.
Recommended actions:
●
No action is required.
362
Critical, Error,
or Warning
The scheduler experienced a problem with the indicated task.
Recommended actions:
●
Take appropriate action based on the indicated problem.
Info.
The scheduler experienced a problem with the indicated task.
Recommended actions:
●
No action is required.
363
Error
When the Management Controller (MC) is restarted, firmware versions that are currently
installed are compared against those in the bundle that was most recently installed. When
firmware is updated, it is important that all components are successfully updated or the system
may not work correctly. Components checked include the CPLD, Expander Controller (EC),
Storage Controller (SC), and MC.
Recommended actions:
●
Reinstall the firmware bundle.
Info.
When the Management Controller (MC) is restarted, firmware versions that are currently
installed are compared against those in the bundle that was most recently installed. If the
versions match, this event is logged as Informational severity. Components checked include the
CPLD, Expander Controller (EC), Storage Controller (SC), and MC.
Recommended actions:
●
No action is required.
364
Info.
The broadcast bus is running as generation 1.
102
Events and event messages
