Specifications
Chapter 3 Subsystem Monitoring
Chapter 3
Subsystem Monitoring
3.1. Subsystem Monitoring Overview
The Falcon subsystem is equipped with a variety of self-monitoring features that
keep you informed of the subsystem’s operational status. These monitoring features
provide vital feedback to help you maintain the operational integrity of the
subsystem. Prompt response to warnings and component failure notifications will ensure
data integrity and help ensure the longevity of the RAID subsystem.
Self-monitoring features include:
Management firmware (FW): The firmware manages the array and provides
device status information and is preinstalled in the subsystem controller. Device
status information can be obtained from the FW. You can access the FW using
either the LCD keypad panel or a PC running a terminal emulation program
connected to a PC running terminal software through the system’s COM 1 RS-
232C (audio jack) serial port. The firmware is fully described in the Generic
Operation Manual that came with the subsystem. Please refer to this manual for
further details.
RAIDWatch: RAIDWatch is a Java-based Graphical User Interface (GUI) that
came with the subsystem and can be used to monitor the subsystem locally or
remotely over TCP/IP. You can use the powerful Configuration Client or
Notification Process Center (NPC) sub-modules to keep you informed over a
variety of communications methods such as fax, pager, e-mail, etc. The installation
and operation of RAIDWatch is fully described in the RAIDWatch Users Manual.
Please refer to this manual for further details.
LEDs: Device status indicating LEDs are placed on all of the active components.
These LEDs inform users of the integrity of a given component. You should
become familiar with the different LEDs and be aware of their functions.
Audible alarm: An audible alarm is present on the subsystem controller board and
will be triggered if any of a number of threatening events occurs. These events
usually jeopardize the functional and operational integrity of the controller board
and must be heeded at all times. Events such as a breach of the temperature
threshold will trigger the alarm and if an onsite subsystem manager is present, the
3-1