Number
Severity
Description/Recommended actions
If the firmware update fails, the user will be notified about the problem immediately and should take care of
the problem at that time, so even when there is a failure, this event is logged as Informational severity.
Recommended actions:
•
No action is required.
175
Info.
The network-port Ethernet link has changed status (up or down) for the indicated controller.
Recommended actions:
•
If this event is logged indicating the network port is up shortly after the Management Controller (MC) has
booted up (event 139), no action is required.
•
Otherwise, monitor occurrences of this event for an error trend. If this event occurs more than 8 times per
hour, it should be investigated.
– This event is probably caused by equipment outside of the storage system, such as faulty cabling or a
faulty Ethernet switch.
– If this event is being logged by only one controller in a dual-controller system, swap the Ethernet
cables between the two controllers. This will show whether the problem is outside or inside the
storage system.
– If the problem is not outside of the storage system, replace the controller module that logged this
event.
176
Info.
The error statistics for the indicated disk have been reset.
Recommended actions:
•
No action is required.
177
Info.
Cache data was purged for the indicated missing volume.
Recommended actions:
•
No action is required.
181
Info.
One or more configuration parameters associated with the Management Controller (MC) have been changed,
such as configuration for SNMP, SMI-S, email notification, and system strings (system name, system location,
etc.).
Recommended actions:
•
No action is required.
182
Info.
All disk channels have been paused. I/O will not be performed on the disks until all channels are unpaused.
Recommended actions:
•
If this event occurs in relation to disk firmware update, no action is required. When the condition is cleared,
event 183 is logged.
•
If this event occurs and you are not performing disk firmware update, see
.
183
Info.
All disk channels have been unpaused, meaning that I/O can resume. An unpause initiates a rescan, which
when complete is logged as event 19.
This event indicates that the pause reported by event 182 has ended.
Recommended actions:
•
No action is required.
185
Info.
An enclosure management processor (EMP) write command has completed.
Recommended actions:
Events and event messages
97