Dot Hill Systems SANnet II 200, Installation, Operation And Service Manual

Page: 80 / 186

6-6 SANnet II 200 SCSI Array Installation, Operation, and Service Manual • June 2005
Note –
Pushing the Reset button has no effect on controller event alarms and muting
the beeper has no effect on failed component alarms.
6.5 Viewing Event Logs on the Screen
A controller event log records an event or alarm that occurs after the system is
powered on. The controller event log records up to 200 events that occur after the
system is powered on. The event log records configuration and operation events and
error messages. The event log also shows alarm events reported by the event
monitoring units in each RAID unit and expansion unit. The status of battery backup
units, fans, temperatures, and voltages are sometimes recorded as well.
For each event, a <P> or <S> on the right side of the screen indicates whether the
primary or secondary controller in a dual-controller configuration issued the event
message.
Caution –
Powering off or resetting the controller automatically deletes all recorded
event logs.
Table 6-2 Silencing Alarms
Cause of Alarm To Silence Alarm
Failed Component
Alarms Use a paper clip to push the Reset button on the right ear of the array.
Controller Event
Alarms In the Firmware Application: From the Main Menu, choose system
Functions
→
Mute beeper . Refer to the SANnet II Family RAID Firmware
User’s Guide fore more information.
In SANscape: Refer to “Updating the Configuration” in the SANscape
User’s Guide for information about the Mute beeper command.
In the SANscape CLI: Run
mute [controller].
Refer to the SANscape CLI User’s Guide for more information.