Number
Severity
Description/Recommended actions
•
Wait at least 5 minutes for the automatic recovery process to complete. Then sign in and confirm that
both controller modules are operational. (You can determine if the controllers are operational with the CLI
show redundancy-mode
command.) In most cases, the system will come back up and no action is
required.
•
If both controller modules do not become operational in 5 minutes, see the recommended actions for
event 485, which will be logged at approximately the same time.
487
Info.
Historical performance statistics were reset.
Recommended actions:
•
No action is required.
488
Info.
Creation of a volume group started.
Recommended actions:
•
No action is required.
489
Info.
Creation of a volume group completed.
Recommended actions:
•
No action is required.
490
Info.
Creation of a volume group failed.
Recommended actions:
•
No action is required.
491
Info.
Creation of a volume group started.
Recommended actions:
•
No action is required.
492
Info.
The volumes in a volume group were ungrouped.
Recommended actions:
•
No action is required.
493
Info.
A volume group was modified.
Recommended actions:
•
No action is required.
495
Warning
The algorithm for best-path routing selected the alternate path to the indicated disk because the I/O error
count on the primary path reached its threshold.
The controller that logs this event indicates which channel (path) has the problem. For example, if the B
controller logs the problem, the problem is in the chain of cables and expansion modules connected to the B
controller module.
Recommended actions:
•
If this event is consistently logged for only one disk in an enclosure, perform the following actions:
– Replace the disk.
– If that does not resolve the problem, the fault is probably in the enclosure midplane. Replace the
chassis FRU for the indicated enclosure.
•
If this event is logged for more than one disk in an enclosure or disks in multiple enclosures, perform the
following actions:
Events and event messages
119
