Technical data

5–96 Event Reporting: Templates and Codes
09 Determine power failure cause.
0A Determine which SBB has a failed connector and replace it.
0B The other controller in a dual-redundant configuration has been reset with the “Kill” line by
the controller that reported the event.
To restart the “Killed” controller enter the CLI command RESTART OTHER on the “Surviving”
controller and then depress the (//) RESET button on the “Killed” controller.
If the other controller is repeatedly being “Killed” for the same or a similar reason, follow
repair action 20.
0C Both controllers in a dual-redundant configuration are attempting to use the same SCSI ID
(either 6 or 7 as indicated in the event report).
The other controller of the dual-redundant pair has been reset with the “Kill” line by the
controller that reported the event. Two possible problem sources are indicated:
■ A controller hardware failure.
■ A controller backplane failure.
First, follow repair action 20 for the “Killed” controller. If the problem persists follow repair
action 20 for the “Surviving” controller. If the problem still persists replace the controller
backplane.
0D The Environmental Monitor Unit has detected an elevated temperature condition. Check the
shelf and its components for the cause of the fault.
0E The Environmental Monitor Unit has detected an external air-sense fault. Check components
outside of the shelf for the cause of the fault.
0F An environmental fault previously detected by the Environmental Monitor Unit is now fixed.
This event report is notification that the repair was successful.
10 Restore on-disk configuration information to original state.
20 Replace the controller module.
Table 5–4 Recommended Repair Action Codes (Continued)
Code Description