IBM RS/6000 SP, Problem Determination Manual

Page: 205 / 316

This soft copy for use by IBM employees only.
6.3.5 Notification on Boot Device
The following example shows how to mail the error report to
root@controlworkstation when an error on the boot device of hdisk0 occurs.
Adding the
dsh -a
command to the ODM commands will perform the action on
all nodes of the RS/6000 SP.
1. Set up the directories for the error notification objects and methods:
mkdir /<define_path>/errnotify/objects
mkdir /<define_path>/errnotify/methods
2. Create the error notification method script.
Create the script that will be run when the error occurs. For example:
#!/bin/ksh
#########################################################################
# Run errpt to get the full error report for the error that
#
# was written and redirect it to a unique errnot.$$ file. #
# $$ will expand to the PID of this script. #
#########################################################################
errpt -a -l $1 > /tmp/errnot.$$
#########################################################################
# Mail the full expanded error report to root@controlworkstation.
#
# This is the user and the hostname that the administrator wants #
# to be notified at. They could be anywhere in the system. #
#########################################################################
mail root@controlworkstation < /tmp/errnot.$$
3. Create the error notification objects.
Create the file that contains the error notification object to catch the boot
disk error. In this example we assume that hdisk0 is the boot device:
errnotify:
en_name =
″
errnot.boot.obj
″
en_persistenceflg = 1
en_label =
″
hdisk0
″
en_method =
″/<
define_path>/methods/errnot.$1
″
4. Add the error notification object to the errnotify class:
odmadd /<define_path>/object/errnot.boot.obj
To delete this object, enter:
odmdelete -o errnotify -q
″
en_name = errnot.boot.obj
″
To view these objects in the ODM database, enter:
odmget -q
″
en_name = errnot.boot.obj
″
errnotify
5. Mail will be sent to the administrator at the Control Workstation when an
error on hdisk0 occurs.
Chapter 6. E r r o r Logging
185