2. Before You Begin
- Event Monitor must be installed with RAIDWatch Manager. Executing the program requires running RAIDWatch Manager and its agents. RAIDWatch's RAID agents serve as communication bridges between the controller, RAID servers, and the software.
- Event Monitor can be run locally or remotely via Java-enabled browser.
- When running remotely via browser, a Java Applet will be started. Connection to an HTTP server providing access to "GREM.htm" is necessary.
- When the Java Applet is started, a prompt will request the IP address of a Primary Agent server. Connection to other Primary agents can then be established through the program's menu commands.
Files listed in the table below must be on an HTTP server if you want to run Event Monitor remotely over a network:
HTML | grem.htm |
Jar | grem.jar grm.jar |
OEM Definitions | em_oemname oemname oemlogo default.enc |
Help Files (if online help is preferred) | /help /em_help |
Basic Running Requirements
Event Monitor is a module of RAIDWatch Manager. It must be started manually (and re-run after a host computer reset).
1. Please be sure that your system meets the system requirements listed in Chapter 2 of the RAIDWatch User's Manual.2. The RAID disk arrays should be properly installed.
3. There is no need for configuration. The program (GREM.jar/GREM.htm) can be downloaded or copied directly to a management platform. Remote management is possible by connecting to an HTTP server providing access to "GREM.htm" and other necessary files (see table above) in its web page root directory.
4. Event Monitor requires at least one disk array to be operating normally and RAIDWatch Primary and Secondary agents installed and running on a main management server. Other requirements for running Event Monitor are identical to those required for RAIDWatch Manager.
Go to Section 3. Starting Event Monitor