2.4.2 Installing RAIDWatch
Follow these steps to install RAIDWatch on your server(s) and RAID systems (the installation procedure for RAIDWatch Manager and Event Monitor is explained in section 2.4.3):
1. Insert the Infortrend RAIDWatch installation CD into your CD-ROM drive.
2. If installing on a Unix system, mount the RAIDWatch CD to /mnt.
3. If you are currently running other applications, close them before proceeding with the setup process. This will minimize the possibility of encountering system errors during setup.
If you are installing remotely, skip step 4.
4. For local installs, run the install script file related to the OS you are using to start the installation process. (Each OS has its own subdirectory.) This method will open a command line window and ask first if you want to install Java Runtime Environment (JRE). Enter "N" for no unless you are also installing RAIDWatch Manager (see 2.4.3 Installing RAIDWatch Manager). The installation script will then ask if you want to install RAIDWatch. Type "Y" for a first install, reinstall, or reconfigure of the program.
If you have just completed step 4, skip step 5.
5. For remote installation, open …\common\install.htm through a web browser. (For example, use your web browser to open "/mnt/common/install.htm" from a Unix system or the directory "d:\common\install.htm" under Windows NT.) The installation procedure will auto-select the software modules that match your OS.
(The browser installation start explained in step 5 can also be used locally if you prefer.)
6. For both local and browser starts, accessing the install file should open the first stage of the installation process. There are three options here for installing or configuring your package. Please select Install Packages then Configure, and click the OK button to continue.
![]()
7. Click the Next button on the Welcome screen to continue.
![]()
8. Read the contents of the License and click the I Agree button to continue.
![]()
9. If you are installing to a primary host, please select Primary Agent, NPC (Notification Processing Center), Event Monitor, and, if the primary host server is also connected to a RAID, please select Secondary Agent. Then click on the Next button to continue. (Please note that although Event Monitor can run without starting RAIDWatch Manager, it cannot be successfully installed independent of RAIDWatch Manager.)
![]()
10. Click on the Install button under the SELECT PATHS Window to start installing the selected components to your system. The installer program will automatically create a new directory for these components. The default is "/usr/hybrid/bin." For Windows NT, the directory will be "c:\Program Files\hybrid\bin." RAIDWatch Manager and Event Monitor must be installed to the same directory.
![]()
11. Primary Agent Settings Assign the "TCP Port Number" that RAIDWatch Manager stations will use to communicate with the Primary Agent. The "Max Client Number" and "Max Controller Number" are also configurable. Users are recommended to keep the defaults for these two parameters.
Redundant Modules:
It is recommended to install Primary and NPC Agents redundantly on different servers to avoid the blind time when the Primary Agent or NPC module is down. Once the Primary Agent or NPC is down, the Primary Agent installed on another server will take over instantly allowing NPC to work.
Primary Agent and NPC should be installed manually on different servers. The configuration utility does not automatically add these modules to the selected RAID server.
- Redundant enable: select to enable primary agent/NPC on another server for the precaution that a Primary Agent/NPC might fail and, as the consequence, fatal system events might then occur unnoticed.
- Mode: assign the preferred mode for the Primary Agent installed on current server as active or standby. There exists an active-standby relationship between Primary Agents and the relationship can be automatically resolved between agents.
- Peer Host: enter the IP address.
- Peer's TCP Port Number: enter the same TCP port number.
- Negotiation Interval is the duration of time (in seconds) for Primary Agents to negotiate for the active-standby status. A Primary Agent might wait for seconds for its peer agent to start up.
IMPORTANT:At least one Primary Agent and one Secondary Agent must be installed in a network managed by RAIDWatch. RAID controllers are managed by Secondary Agents which are in-turn managed by the Primary Agent. Without Secondary Agents associated with each RAID, it will be impossible to manage RAID systems.
The Event Monitor requires Primary and Secondary Agents to be running on RAID servers to record system events and report system status.
Even if the system only has one RAID and all RAIDWatch components are installed on a single server, both a Primary Agent and a Secondary Agent must be installed.12. Managed Secondary Agent Settings (subsection of Primary Agent Settings): under this part of the Primary Agent configuration, list each Secondary Agent RAID server that will be managed through the Primary Agent where you are installing RAIDWatch.
- Host Names are IP addresses for each RAID server.
- TCP Port settings should be the same for all Secondary Agents but should be a different Port setting from the Primary Agent setting and otherwise unique to the Secondary Agents.
![]()
IMPORTANT:The Primary Agent default TCP port setting should be changed to a network-unique assignment. The default TCP port setting is 58632. Any TCP port number between 49152 and 65535 can be used.
Also, Managed Secondary Agents should all use a different, common-to-all Secondary Agents, TCP port setting from that of the Primary Agent.
IMPORTANT:Local Secondary Agents must be installed at all RAID hosts managed by RAIDWatch.
13. Secondary Agent Settings: each Secondary Agent RAID server needs to be configured under this window.
- Host Name/IP Address is the IP address for the current RAID server.
- TCP Port Number is the TCP port to be used by all secondary agents.
- Event Polling Period is the time interval (in seconds) for event queries from the Secondary Agent to the RAID controller.
![]()
14. NPC Settings: Notifier has four possible means of informing RAID managers that an event has occurred. They are: Fax, Pager, Broadcast, Email. In order to use fax or pager notification, Modem parameters must also be set. For NT servers, Widows Messaging must be installed and running for NPC to work. If NPC will not be used, skip these steps.
Modem Settings include Serial Port, which is a COM port setting and Baud Rate which is the maximum transfer speed of the modem. A modem must be installed and setup in order to use NPC fax or pager notification.
Fax Settings
- Profile Name is a collection name required for logon to a Windows Messaging profile (FAX, E-mail, Exchange Mail, or Personal address book). It is usually the same with the account name. A profile name validates the available messaging services and service providers during a particular MAPI session.
- Telephone is the phone number for an event message receiving fax machine. (Note that any access dialing requirements, such as accessing an outside line, must be included in the phone number. For example: 9,,,2241603 wherein "9" is access for an outside line and ",,," indicates a pause.)
- Message is the text that will be sent as a fax. You may add, for example, contact information for technical personnel.
- Available Modems provides a list of installed and configured modems that may be used for sending event notices via fax.
Pager Settings
- Initializing String – standard AT command set. The default is "V1B1E0F0L1M1Q0TV1X1Y0&C1&D2&G0S7=20" and should be left as is for most fax modems.
- Telephone is the phone number for an event message receiving pager. (Note that any access dialing requirements, such as accessing an outside line or entering commands upon connecting with a pager service, must be included in the phone number. For example: 9,,,2241603,,,1 wherein "9" is access for an outside line, ",,," indicates a pause, and "1" is to leave a message to be forwarded to the pager.)
- Message is the text that will be sent to the pager. (Note: any pager specific limitations regarding length or content must be considered.)
- Available Modems provides a list of installed and configured modems that may be used for sending event notices via this pager number.
Broadcast Settings include a Host Name (IP address) and the Message to be broadcast. The host name should be the server for the LAN where the notification messages will be broadcast.
- Initializing String – standard AT command set. The default is "V1B1E0F0L0M0Q0TV1X1Y0" and should be left as is for most pagers.
Email Settings
- Profile Name is a collection name required for logon to a Windows Messaging profile (FAX, E-mail, Exchange Mail, or Personal address book). It is usually the same with the account name. A profile name validates the available messaging services and service providers during a particular MAPI session.
- SMTP Server is the mail server used to send event notifications via e-mail.
- Sender's Email is the "From" part of e-mail notification messages. It must be a valid internet e-mail address.
- Receiver's Email allows users to enter multiple event notification e-mail receipients with messages for each. Each entry must be a valid internet e-mail address.
- Subject allows users to add a subject to event notification emails.
SNMP Settings
- Message is the message sent to the particular e-mail address being added. You may add, for example, contact information for technical personnel.
- Severity is the parameter used to determine what levels of events will be sent via SNMP (1, all levels; 2, Warning and Alert; 3, Alert).
- Host IP is the port number of the agents listening for traps. Click Add to avail agents to the Trap Receiver List.
- Trap Receiver List is a list of listening SNMP agents.
IMPORTANT:Agent and NPC configuration parameters can be reconfigured later using the installation program. Run the installation program and select Configure Only from the Start menu to reconfigure Agent and NPC settings.
If the Primary Agent, Secondary Agent, and NPC (if needed) have all been installed and configured, including Secondary Agents for each RAID host, then installation is complete.
After all elements have been installed in a particular machine, click the ExitSetup button to exit.You may now install RAIDWatch Manager or Event Monitor at stations from which your RAIDs will be monitored and managed.