Owners Manual

Table Of Contents
Table 27. Event descriptions and recommended actions (continued)
Number Severity Description/Recommended actions
Recommended actions:
No action is required.
127 Warning The controller has detected an invalid disk dual-port connection. This event indicates that a
controller host port is connected to an expansion port, instead of to a port on a host or a switch.
Recommended actions:
Disconnect the host port and expansion port from each other and connect them to the
proper devices.
136 Warning Errors detected on the indicated disk channel have caused the controller to mark the channel as
degraded.
Recommended actions:
Determine the source of the errors on the indicated disk channel and replace the faulty
hardware.
When the problem is resolved, event 189 is logged.
139 Info. The Management Controller (MC) has powered up or restarted.
Recommended actions:
No action is required.
140 Info. The Management Controller is about to restart.
Recommended actions:
No action is required.
141 Info. This event is logged when the IP address used for management of the system has been changed
by a user or by a DHCP server (if DHCP is enabled). This event is also logged during power up or
failover recovery, even when the address has not changed.
Recommended actions:
No action is required.
152 Warning The Management Controller (MC) has not communicated with the Storage Controller (SC) for
15 minutes and may have failed.
This event is initially logged as Informational severity. If the problem persists, this event is logged
a second time as Warning severity and the MC is automatically restarted in an attempt to
recover from the problem. Event 156 is then logged.
Recommended actions:
If this event is logged only one time as Warning severity, no action is required.
If this event is logged more than one time as Warning severity, do the following:
Check the version of the controller firmware and update to the latest firmware if needed.
If the latest firmware is already installed, the controller module that logged this event
probably has a hardware fault. Replace the module.
If you are not able to access the management interfaces of the controller that logged this
event, do the following:
Shut down that controller and reseat the module.
If you are then able to access the management interfaces, check the version of the
controller firmware and update to the latest firmware if needed.
If the problem recurs, replace the module.
Info. The Management Controller (MC) has not communicated with the Storage Controller (SC) for
160 seconds.
If communication is restored in less than 15 minutes, event 153 is logged. If the problem persists,
this event is logged a second time as Warning severity.
86 Events and event messages