Chapter Subsystem Monitoring | Meridian Data 16i specification

Chapter 3 Subsystem Monitoring

Formatted: Bullets and Numbering

3.1 Subsystem Monitoring Overview

The SecurStor 16i subsystem is equipped with a variety of self-monitoring features that help to keep subsystem managers informed of the subsystem operational statuses. These monitoring features provide vital feedback to help you maintain the operational integrity of the subsystem. Prompt response to warnings and subsystem component failure notifications will ensure data integrity and help ensure the longevity of the subsystem.

Self-monitoring features include:

Firmware (FW): The RAID controller in the subsystem is managed by Formatted: Bullets and Numbering preinstalled FW, which can be accessed using a PC hyper-terminal connected

through the COM1 serial port. Device status information can be obtained from the FW-embedded configuration utility. The FW is fully described in the Manual that came with your system. Please refer to this manual for further information.

RAIDWatch: RAIDWatch is a fully integrated, Graphical User Interface (GUI) installed with the firmware, which can be used to monitor and maintain the subsystem locally or remotely over TCP/IP network. Connection to RAIDWatch is made using the 10/100BaseT management port.

The RAIDWatch Panel View can be customized to display a graphical representation of the subsystem components in the content panel of the RAIDWatch screen. Panel View allows you to quickly determine the operational status of critical components. Please refer to the RAIDWatch User’s Manual for further details.

NOTE:

Detailed installation instructions for RAIDWatch Manager are given in the RAIDWatch User’s Manual.

LEDs: Device-status-indicating LEDs are located on all important modules. These LEDs inform you of the integrity of a given component or a host/management link. You should become familiar with the various LEDs and be aware of their functions. (See Section 0)

Audible alarm: An audible alarm is present on the subsystem controller board and will be triggered if any of a number of threatening events occurred. These events usually jeopardize the functional and operational integrity of the controller board and must be heeded at all times. Events such as a breaching of the temperature threshold will trigger the alarm. If a subsystem manager is present, the manager should use the RS-232 terminal console to determine the cause of the alarm and take appropriate corrective measures. (See Section 0)

Formatted: Bullets and Numbering

3-1