# Configuring the ServeRAID Manager agent

You can configure the ServeRAID Manager agent port number and alarm. You can also configure the ServeRAID Manager agent to log events to the operating system event log. To configure the agent, edit the file RaidAgnt.pps. This file is located in the same directory where you installed the ServeRAID Manager. If you change these settings while the ServeRAID Manager agent is running, you must stop and restart the ServeRAID Manager agent for the changes to take effect. If the RaidAgnt.pps file does not exist when you start the ServeRAID Manager agent, a new file is created with the default settings.

Notes:
  1. The RaidAgnt.pps file is preserved during a ServeRAID Manager upgrade.
  2. The ServeRAID Manager agent alarm is not supported by the ServeRAID Manager in startable-CD mode.
  3. If you are using the ServeRAID Manager as an IBM Director Extension, the RaidAgnt.pps file is located in the directory where IBM Director is installed. You must stop and restart the IBM Director agent for any changes to take effect.

## Configuring the port number

The default port number for the ServeRAID Manager agent and console (client) is 34571. To change the port number, edit the following line in the file RaidAgnt.pps:

agent.startupPortNum=34571

For accessing remote systems, the ServeRAID Manager uses four consecutive ports starting from the startup port: 34571, 34572, 34573, and 34574. If your system has a conflict with these ports, change the startup port to a different port number.

## Configuring the alarm

When the ServeRAID Manager agent is started, it reads the alarm settings. When a critical or fatal event occurs in the RAID subsystem, the ServeRAID Manager agent triggers its alarm, if enabled. The alarm continues at the specified interval until you either:

- Correct all the critical and fatal problems (if agent.auto.off.alarm is set to true).
- Delete the file alarm.on. This file is located in the same directory where you installed the ServeRAID Manager. When you delete this file, the alarm stops until the next critical or fatal event occurs. The alarm.on file is automatically created each time the alarm starts.

You can configure the following alarm settings:

- agent.enable.alarm
  Specifies whether the agent alarm is enabled or disabled. Set this value to true to enable the alarm or false to disable the alarm. The default value is false.
- agent.interval.alarm
  Specifies the interval (in seconds) between audible alarms. The default is 300 seconds (5 minutes).
- agent.auto.off.alarm
  Specifies whether the alarm should turn off automatically when no more problems are detected. Set this value to true to cause the alarm to turn off automatically, or false to manually turn the alarm off. If you set this value to false, you must delete the file alarm.on to turn off the alarm. The default is true.

## Configuring event logging

The ServeRAID Manager agent logs warning and fatal events to the operating system event log. For Windows systems, you can view the log with the Windows Event Viewer. For Unix systems, events are logged according to the /etc/syslog.conf settings. (For more information, see the syslogd(8) man page.)

You can enable and disable event logging by editing the following line in the file RaidAgnt.pps. Set the value to true to enable event logging (the default) or false to disable event logging.

agent.enable.logEventsWithOS = true

## More information

- Using the ServeRAID Manager agent
- Verifying that the ServeRAID Manager agent is running
- Starting the ServeRAID Manager agent
- Specifying remote access settings

Glossary | Contents

x-1095-SRM-00-05-EN