Setting Alert Actions for Systems Running Supported
Red Hat Enterprise Linux and SUSE Linux Enterprise Server
Operating Systems
When you set Alert Actions for an event, you can specify the action to Display an alert on the server. To perform this action, Server Administrator writes a message to /dev/console. If the Server Administrator system is running an X Window System, you will not see that message by default. To see the alert message on a Red Hat® Enterprise Linux® system when the X Window System is running, you must start xconsole or xterm -C before the event occurs. To see the alert message on a SUSE® Linux Enterprise Server system when the X Window System is running, you must start xterm -C before the event occurs.
When you set Alert Actions for an event, you can specify the action to Broadcast a message. To perform this action, Server Administrator executes the wall command, which sends the message to everybody logged in with their message permission set to Yes. If the Server Administrator system is running an X Window System, you will not see that message by default. To see the broadcast message when the X Window System is running, you must start a terminal such as xterm or gnome-terminal before the event occurs.
NOTE: On SUSE Linux Enterprise Server (Version 9), messages sent by wall are displayed by the xterm terminal program but not by the Konsole terminal program.
When you set Alert Actions for an event, you can specify the action to Execute application. There are limitations on the applications that Server Administrator can execute. Follow these guidelines to ensure proper execution:
Do not specify X Window System based applications because Server Administrator cannot execute such applications properly.
Do not specify applications that require input from the user because Server Administrator cannot execute such applications properly.
Redirect stdout and stderr to a file when specifying the application so that you can see any output or error messages.
If you want to execute multiple applications (or commands) for an alert, create a script to do that and put the full path to the script in the Absolute path to the application box.
Example 1:
ps -ef >/tmp/psout.txt 2>&1
The command in Example 1 executes the application ps, redirects stdout to the file /tmp/psout.txt, and redirects stderr to the same file as stdout.
Example 2:
mail -s "Server Alert" admin </tmp/alertmsg.txt >/tmp/mailout.txt 2>&1
The command in Example 2 executes the mail application to send the message contained in the file /tmp/alertmsg.txt to Red Hat Enterprise Linux user or SUSE Linux Enterprise Server user, and Administrator, with the subject Server Alert. The file /tmp/alertmsg.txt must be created by the user before the event occurs. In addition, stdout and stderr are redirected to the file /tmp/mailout.txt in case an error occurs.
BMC Platform Events Filter Alert Messages
All possible Platform Event Filter (PEF) messages along with a description of each event is listed in Table 11-1.
Table 11-1. BMC PEF Alert Events
Event
Description
Fan Probe Failure
The fan is running too slow or not at all.
Voltage Probe Failure
The voltage is too low for proper operation.
Discrete Voltage Probe Failure
The voltage is too low for proper operation.
Temperature Probe Warning
The temperature is approaching excessively high or low limits.
Temperature Probe Failure
The temperature is either too high or too low for proper operation.
Chassis Intrusion Detected
The system chassis has been opened.
Redundancy (PS or Fan) Degraded
Redundancy for the fans and/or power supplies has been reduced.
Redundancy (PS or Fan) Lost
No redundancy remains for the system's fans and/or power supplies.
Processor Warning
A processor is running at less than peak performance or speed.
Processor Failure
A processor has failed.
PPS/VRM/DCtoDC Warning
The power supply, voltage regulator module, or DC to DC converter is pending a failure condition.
Power Supply/VRM/D2D Failure
The power supply, voltage regulator module, or DC to DC converter has failed.
Hardware log is full or emptied
Either an empty or a full hardware log requires administrator attention.
Automatic System Recovery
The system is hung or is not responding and is taking an action configured by Automatic System Recovery.
Understanding Service Names
The service executable and display names of the following services have changed:
Table 11-2. Service Names
Purpose
Service Name
Previous Release
Current Release
Web Server
Display Name
Secure Port Server
DSM SA Connection Service
Executable Name
Omaws[32|64]
dsm_om_connsvc[32|64]
dsm_om_connsvc
Scheduling or Notification
Display Name
OM Common Services
DSM SA Shared Services
Executable Name
Omsad[32|64]
dsm_om_shrsvc[32|64]
dsm_om_shrsvc
Fixing a Faulty Server Administrator Installation on Supported
Windows Operating Systems
You can fix a faulty installation by forcing a reinstall and then performing an uninstall of Server Administrator.
To force a reinstall:
Find out the version of Server Administrator that was previously installed.
Download the installation package for that version from the Dell™ Support website at
support.dell.com.
Locate SysMgmt.msi from the srvadmin\windows\SystemsManagement directory.
Type the following command at the command prompt to force a reinstall
Select Custom Setup and choose all the features that were originally installed. If you are not sure
which features were installed, select all features and perform the installation.
NOTE: If you installed Server Administrator in a non-default directory, make sure to change it in the Custom Setup as well.
After the application is installed, you can uninstall Server Administrator using Add/Remove Programs.
