HP P2000 G3 MSA Reference Manual page 30

194
Info The Storage Controller in the partner controller module is not up.
This indicates that a trigger condition has occurred that has caused the auto-write-through feature to
disable write-back cache and put the system in write-through mode. When the fault is resolved, event 195
is logged to indicate that write-back mode has been restored.
Recommended Actions:
• If event 195 has not been logged since this event was logged, the other Storage Controller is probably
still down and the cause should be investigated. Other events were probably logged at approximately
the same time as this event; see the recommended actions for those events.
195
Info The auto-write-through trigger event that caused event 194 to be logged has been resolved.
Recommended Actions:
• No action is required.
198
Info A power supply has failed.
This indicates that a trigger condition has occurred that has caused the auto-write-through feature to
disable write-back cache and put the system in write-through mode. When the fault is resolved, event 199
is logged to indicate that write-back mode has been restored.
Recommended Actions:
• If event 199 has not been logged since this event was logged, the power supply probably does not
have a health of OK and the cause should be investigated. Another power-supply event was probably
logged at approximately the same time as this event (such as event 168); see the recommended actions
for that event.
199
Info The auto-write-through trigger event that caused event 198 to be logged has been resolved.
Recommended Actions:
• No action is required.
200
Info A fan has failed.
This indicates that a trigger condition has occurred that has caused the auto-write-through feature to
disable write-back cache and put the system in write-through mode. When the fault is resolved, event 201
is logged to indicate that write-back mode has been restored.
Recommended Actions:
• If event 201 has not been logged since this event was logged, the fan probably does not have a health
of OK and the cause should be investigated. Another fan event was probably logged at approximately
the same time as this event (such as event 168); see the recommended actions for that event.
201
Info The auto-write-through trigger event that caused event 200 to be logged has been resolved.
Recommended Actions:
• No action is required.
30 Event descriptions