Diagnosis Guide

Preparing to examine and monitor this information

This section describes how to define the conditions that are discussed previously, to the SP Event Perspective and how to define event definitions that are associated with these conditions.

SP Event Perspective - conditions that you can monitor using the default event definition

The following conditions have a default event definition which you can install using the SP Event Perspective.

Table 2. Conditions and default event definitions

Each of these conditions is to be monitored in all locations, with the exception of sdrd Daemon Activity, which is to be monitored only on the control workstation. Each default event definition contains a definition for the condition, so you need only load and register the event definition. Use the following procedure for each of the event definitions listed previously:

1. Bring up the SP Event Perspective.
2. Click in the Event Definitions pane.
3. Select Actions > Load Defaults from the menu bar.

   This opens the Load Default Event Definitions dialog box.

4. Select the default event definition of interest from the list.
5. If you wish to register the selected event definition, click Register the selected event definitions.
6. Click OK to load the selected default event definition and close the dialog box.

SP Event Perspective - conditions that you can monitor that you must define to the SP Event Perspective

This section contains instructions for using the SP Event Perspective to create the conditions that do not have default definitions.

To start:

1. Bring up the SP Event Perspective
2. If the Conditions pane is hidden, select View > Add Pane from the menu bar, to add the Conditions pane.
3. Click in the Conditions pane.
4. Select Actions > Create from the menu bar.
5. This displays the Create Conditions Notebook.

Now use the SP Event Perspective to create a condition for each of the following conditions:

• Frame Controller ID Mismatch - create a condition by following these steps:
  1. In the Name field, enter a name that describes the condition. For example, frameControllerIDMismatch.
  2. Type a description of the condition.
  3. Scroll down in the Resource variable classes list and select IBM.PSSP.SP_HW.
  4. Scroll down in the Resource variable names list and select IBM.PSSP.SP_HW.Frame.controllerIDMismatch.
  5. In the Event expression field, enter X==1
  6. Leave the Rearm expression field blank.
  7. Press the Create button.
• Frame Temperature - create a condition by following these steps:
  1. In the Name field, enter a name that describes the condition. For example, frameTempOutOfRange.
  2. Type a description of the condition.
  3. Scroll down in the Resource variable classes list and select IBM.PSSP.SP_HW.
  4. Scroll down in the Resource variable names list and select tempRange.
  5. In the Event expression field, enter X==1
  6. Leave the Rearm expression field blank.
  7. Press the Create button.
• Frame Node Slot Failure - create a condition by following these steps:
  1. In the Name field, enter a name that describes the condition. For example, frameSlotFailure.
  2. Type a description of the condition.
  3. Scroll down in the Resource variable classes list and select IBM.PSSP.SP_HW.
  4. Scroll down in the Resource variable names list and select IBM.PSSP.SP_HW.Frame.nodefail.
  5. In the Event expression field, enter X==1
  6. Leave the Rearm expression field blank.
  7. Press the Create button.
  8. Repeat the previous steps for each IBM.PSSP.SP_HW.Frame.nodefail* resource variable.
• Switch Power Shutdown - create a condition by following these steps:
  1. In the Name field, enter a name that describes the condition. For example, switchShutdownTemp.
  2. Type a description of the condition.
  3. Scroll down in the Resource variable classes list and select IBM.PSSP.SP_HW.
  4. Scroll down in the Resource variable names list and select IBM.PSSP.SP_HW.switch.shutdownTemp.
  5. In the Event expression field, enter X==1
  6. Leave the Rearm expression field blank.
  7. Press the Create button.
• Switch Hardware Environment Indicator - create a condition by following these steps:
  1. In the Name field, enter a name that describes the condition. For example, switchEnvLED.
  2. Type a description of the condition.
  3. Scroll down in the Resource variable classes list and select IBM.PSSP.SP_HW.
  4. Scroll down in the Resource variable names list and select IBM.PSSP.SP_HW.Switch.envLED.
  5. In the Event expression field, enter X>0
  6. Leave the Rearm expression field blank.
  7. Press the Create button.
• Switch Temperature - create a condition by following these steps:
  1. In the Name field, enter a name that describes the condition. For example, switchTemp.
  2. Type a description of the condition.
  3. Scroll down in the Resource variable classes list and select IBM.PSSP.SP_HW.
  4. Scroll down in the Resource variable names list and select IBM.PSSP.SP_HW.Switch.tempRange.
  5. In the Event expression field, enter X==1
  6. Leave the Rearm expression field blank.
  7. Press the Create button.
• Node Temperature - create a condition by following these steps:
  1. In the Name field, enter a name that describes the condition. For example, nodeTemp.
  2. Type a description of the condition.
  3. Scroll down in the Resource variable classes list and select IBM.PSSP.SP_HW.
  4. Scroll down in the Resource variable names list and select IBM.PSSP.SP_HW.Node.tempRange.
  5. In the Event expression field, enter X>0
  6. Leave the Rearm expression field blank.
  7. Press the Create button.
• / File system Filling - create a condition by following these steps:
  1. In the Name field, enter a name that describes the condition. For example, rootFull.
  2. Type a description of the condition.
  3. Scroll down in the Resource variable classes list and select IBM.PSSP.aixos.
  4. Scroll down in the Resource variable names list and select IBM.PSSP.aixos.FS.%totused.
  5. In the Event expression field, enter X>90
  6. In the Rearm expression field, enter X<80
  7. In the Resource ID Elements to be Fixed for the Condition field, enter LV=hd4;VG=rootvg.
  8. Press the Create button.
• Kernel Memory Buffer Failures - create a condition by following these steps:
  1. In the Name field, enter a name that describes the condition. For example, mbufFailures.
  2. Type a description of the condition.
  3. Scroll down in the Resource variable classes list and select IBM.PSSP.aixos.
  4. Scroll down in the Resource variable names list and select IBM.PSSP.aixos.Mem.Kmem.failures.
  5. In the Event expression field, enter X>X@P
  6. Leave the Rearm expression field blank.
  7. In the Resource ID Elements to be Fixed for the Condition field, enter Type=mbuf.
  8. Press the Create button.
• srcmstr Daemon Activity - create a condition by following these steps:
  1. In the Name field, enter a name that describes the condition. For example, srcmstrFailure.
  2. Type a description of the condition.
  3. Scroll down in the Resource variable classes list and select IBM.PSSP.Prog.
  4. Scroll down in the Resource variable names list and select IBM.PSSP.aixos.FS.xpcount.
  5. In the Event expression field, enter X@0<X@1
  6. Leave the Rearm expression field blank.
  7. In the Resource ID Elements to be Fixed for the Condition field, enter ProgName=srcmstr;UserName=root
  8. Press the Create button.
• biod Daemon Activity - create a condition by following these steps:
  1. In the Name field, enter a name that describes the condition. For example, biodFailure.
  2. Type a description of the condition.
  3. Scroll down in the Resource variable classes list and select IBM.PSSP.Prog.
  4. Scroll down in the Resource variable names list and select IBM.PSSP.aixos.FS.pcount.
  5. In the Event expression field, enter X@0<X@1
  6. Leave the Rearm expression field blank.
  7. In the Resource ID Elements to be Fixed for the Condition field, enter ProgName=biod;UserName=root
  8. Press the Create button.
• portmap Daemon Activity - create a condition by following these steps:
  1. In the Name field, enter a name that describes the condition. For example, portmapFailure.
  2. Type a description of the condition.
  3. Scroll down in the Resource variable classes list and select IBM.PSSP.Prog.
  4. Scroll down in the Resource variable names list and select IBM.PSSP.aixos.FS.pcount.
  5. In the Event expression field, enter X@0<X@1
  6. Leave the Rearm expression field blank.
  7. In the Resource ID Elements to be Fixed for the Condition field, enter ProgName=portmap;UserName=root
  8. Press the Create button.
• xntpd Daemon Activity - create a condition by following these steps:
  1. In the Name field, enter a name that describes the condition. For example, xntpFailure.
  2. Type a description of the condition.
  3. Scroll down in the Resource variable classes list and select IBM.PSSP.Prog.
  4. Scroll down in the Resource variable names list and select IBM.PSSP.aixos.FS.pcount.
  5. In the Event expression field, enter X@0<X@1
  6. Leave the Rearm expression field blank.
  7. In the Resource ID Elements to be Fixed for the Condition field, enter ProgName=xntpd;UserName=root
  8. Press the Create button.
• kerberos Daemon Activity - create a condition by following these steps:
  1. In the Name field, enter a name that describes the condition. For example, kerberosFailure.
  2. Type a description of the condition.
  3. Scroll down in the Resource variable classes list and select IBM.PSSP.Prog.
  4. Scroll down in the Resource variable names list and select IBM.PSSP.aixos.FS.pcount.
  5. In the Event expression field, enter X@0<X@1
  6. Leave the Rearm expression field blank.
  7. In the Resource ID Elements to be Fixed for the Condition field, enter ProgName=kerberos;UserName=root
  8. Press the Create button.
• dced Daemon Activity - create a condition by following these steps:
  1. In the Name field, enter a name that describes the condition. For example, dcedFailure.
  2. Type a description of the condition.
  3. Scroll down in the Resource variable classes list and select IBM.PSSP.Prog.
  4. Scroll down in the Resource variable names list and select IBM.PSSP.aixos.FS.pcount.
  5. In the Event expression field, enter X@0<X@1
  6. Leave the Rearm expression field blank.
  7. In the Resource ID Elements to be Fixed for the Condition field, enter ProgName=dced;UserName=root
  8. Press the Create button.
• cdsadv Daemon Activity - create a condition by following these steps:
  1. In the Name field, enter a name that describes the condition. For example, cdsadvFailure.
  2. Type a description of the condition.
  3. Scroll down in the Resource variable classes list and select IBM.PSSP.Prog.
  4. Scroll down in the Resource variable names list and select IBM.PSSP.aixos.FS.pcount.
  5. In the Event expression field, enter X@0<X@1
  6. Leave the Rearm expression field blank.
  7. In the Resource ID Elements to be Fixed for the Condition field, enter ProgName=cdsadv;UserName=root
  8. Press the Create button.
• cdsd Daemon Activity - create a condition by following these steps:
  1. In the Name field, enter a name that describes the condition. For example, cdsdFailure.
  2. Type a description of the condition.
  3. Scroll down in the Resource variable classes list and select IBM.PSSP.Prog.
  4. Scroll down in the Resource variable names list and select IBM.PSSP.aixos.FS.pcount.
  5. In the Event expression field, enter X@0<X@1
  6. Leave the Rearm expression field blank.
  7. In the Resource ID Elements to be Fixed for the Condition field, enter ProgName=cdsd;UserName=root
  8. Press the Create button.
• secd Daemon Activity - create a condition by following these steps:
  1. In the Name field, enter a name that describes the condition. For example, secdFailure.
  2. Type a description of the condition.
  3. Scroll down in the Resource variable classes list and select IBM.PSSP.Prog.
  4. Scroll down in the Resource variable names list and select IBM.PSSP.aixos.FS.pcount.
  5. In the Event expression field, enter X@0<X@1
  6. Leave the Rearm expression field blank.
  7. In the Resource ID Elements to be Fixed for the Condition field, enter ProgName=secd;UserName=root
  8. Press the Create button.

SP Event Perspective - creating the event definitions

Create one event definition for each of the conditions that are listed previously. Most of these specify that the conditions be checked in all locations, while some are on specific nodes. Those that are checked in all locations are:

• Frame Controller ID Mismatch
• Frame Temperature
• Switch H/W Environment Indicator
• Switch Temperature
• Node Temperature
• / file system becoming full
• Kernel Memory Buffer Failures
• srcmstr Daemon Activity
• portmap Daemon Activity

Conditions to monitor only in specific locations

Conditions to monitor only in specific locations are:

• Frame Node Slot Failures - The slots to be monitored are those slots where nodes are directly connected in the frame.

  Those slots that cannot be used because wide or high nodes occupy previous slots are not to be monitored. You will need to identify which slots in which frames are to be monitored, and you can create one event per slot.

  When creating the event definition, select the proper "nodefail" resource name for the slot, and select the range of frame numbers where this slot is in use.

• biod Daemon Activity - This daemon is monitored only for nodes that use the NFS file system.

  When creating the event definition, select those nodes where NFS is used.

• xntpd Daemon Activity - This daemon is monitored only for nodes that use NTP time service.

  When creating the event definition, select only those nodes where NTP is used.

• kerberos Daemon Activity - This daemon is monitored on the control workstation if the Kerberos database resides on the control workstation.
• DCE - When creating the event definition, specify only the nodes where DCE is configured. Specify the control workstation if DCE is configured anywhere on the SP system.
  • cdsd Daemon Activity - This daemon is monitored on the control workstation if the DCE servers reside on the control workstation.
  • secd Daemon Activity - This daemon is monitored on the control workstation if the DCE servers reside on the control workstation.

Creating an event definition using the Create Event Definition notebook

On the Definition Page:

1. Give the event definition a descriptive name. For example, you can use rootFullEvent for the rootFull condition.
2. Click the down-arrow button for Name in the Condition box, and find the condition you want to use.
3. For those conditions that are to be observed in all locations, click the Wild Card Element selector under Specify remaining resource ID elements box.
4. For those that are to be observed in specific locations, select those locations under Element Values.

On the Notifications page, make sure the Notification (Get notified of events during the SP Event Perspective session) button is selected.

On the Actions page:

1. Click the Take these actions when the event occurs button.
2. In the Run command field, enter the following:

   'echo $PMAN_HANDLE Alert: Instance Vector $PMAN_IVECTOR |
   mail -s "$PMAN_HANDLE Alert" username@address'
   

Then click the Create button at the bottom of the page.

SP Hardware Perspective

The SP Hardware Perspective can be used to investigate further when the SP Event Perspective detects a hardware problem. This Perspective can show you the node's LED or LCD values (the SP Event Perspective cannot), and can be used to control the hardware or reset nodes when necessary.

Problem Management

Problem Management can be used as an alternative to the SP Event Perspective, to define event definitions that monitor conditions on your SP system.

Ensuring that the conditions you intend to monitor are known to Problem Management

The SP Event Perspective uses Problem Management whenever the event definition indicates that a command should be issued when the event occurs. If you used the SP Event Perspective to set up the event definitions and conditions, these definitions may already be known to Problem Management. Use the pmanquery command to check if the definition already exists. For example:

pmanquery -n varFullEvent

will check for the varFullEvent definition.

If the event definitions are not known, use the pmandef command to define them. Any event definitions made using the pmandef command are also usable by the SP Event Perspective later on. To create new event definitions, use the pmandef command. It is best to write a shell script with all the pmandef commands in it, and then invoke the shell script.

When the pmandef commands complete, the event definitions will be registered, which means that Problem Management will begin to check for these conditions immediately. If this is a problem, issue the pmandef -d command to disable the event until you are ready to monitor the condition. Then, use the pmandef -a command to activate it.

For more information about problem management, see the chapter on using the Problem Management subsystem in PSSP: Administration Guide. For more information about the pmandef command, see the man page for the command in PSSP: Command and Technical Reference.

The pmandef commands for specific conditions

Use these pmandef commands to set up event definitions for the following conditions. The field username is the user ID to receive the notification, and the address is a hostname.

• Frame power

  pmandef -s framePowerEvent \
  -e 'IBM.PSSP.SP_HW.Frame.frPowerOff:FrameNum=*:X==1' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' 
   
  

• Frame controller responding:

  pmandef -s frameCtrlRespondingEvent \
  -e 'IBM.PSSP.SP_HW.Frame.controllerResponds:FrameNum=*:X==1' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' 
   
  

• Frame controller ID mismatch:

  pmandef -s frameCtrlIDMismatchEvent \
  -e 'IBM.PSSP.SP_HW.Frame.controllerIDMismatch:FrameNum=*:X==1' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' 
   
  

• Frame temperature:

  pmandef -s frameTempEvent \
  -e 'IBM.PSSP.SP_HW.Frame.tempRange:FrameNum=*:X==1' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' 
   
  

• Frame node slot failure:

  pmandef -s frameSlot1FailureEvent \
  -e 'IBM.PSSP.SP_HW.Frame.nodefail1:FrameNum=*:X==1' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' 
   
  

• Frame Switch slot failure:

  pmandef -s frameSwitchSlotFailEvent \
  -e 'IBM.PSSP.SP_HW.Frame.nodefail17:FrameNum=*:X==1' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' 
   
  

• Switch power:

  pmandef -s switchPowerEvent \
  -e 'IBM.PSSP.SP_HW.Switch.powerLED:FrameNum=*:X!=1' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' 
   
  

• Switch hardware environment indicator:

  pmandef -s switchLEDEvent \
  -e 'IBM.PSSP.SP_HW.Switch.envLED:FrameNum=*:X>0' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' 
   
  

• Switch shutdown due to extreme temperature:

  pmandef -s switchTempShutdownEvent \
  -e 'IBM.PSSP.SP_HW.Switch.shutdownTemp:FrameNum=*:X==1' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' 
   
  

• Switch temperature:

  pmandef -s switchTempEvent \
  -e 'IBM.PSSP.SP_HW.Switch.tempRange:FrameNum=*:X==1' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' 
   
  

• Node power:

  pmandef -s nodePowerEvent \
  -e 'IBM.PSSP.SP_HW.Node.powerLED:NodeNum=*:X!=1' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• Node controller responding:

  pmandef -s hostRespondsEvent \
  -e 'IBM.PSSP.SP_HW.Node.hostResponds:NodeNum=*:X==0' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• Node hardware environment indicator:

  pmandef -s nodeLEDEvent \
  -e 'IBM.PSSP.SP_HW.Node.envLED:NodeNum=*:X>0' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• Node temperature:

  pmandef -s nodeTempEvent \
  -e 'IBM.PSSP.SP_HW.Node.tempRange:NodeNum=*:X>0' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• Node key mode switch position:

  pmandef -s nodeKeySwitchNotNormalEvent \
  -e 'IBM.PSSP.SP_HW.Node.keyModeSwitch:NodeNum=*:X>0' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• Node LCD or LED readout:

  pmandef -s nodeLCDMessageEvent \
  -e 'IBM.PSSP.SP_HW.Node.LCDhasMessage:NodeNum=*:X>0' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• Node processorsOffline:

  pmandef -s processorsOfflineEvent \
  -e 'IBM.PSSP.SP_HW.Node.processorsOffline:NodeNum=*:X>0' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• Node reachable by RSCT Group Services:

  pmandef -s nodeNotReachableEvent \
  -e 'IBM.PSSP.Membership.Node.state:NodeNum=*:X>0' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• /tmp File system filling:

  pmandef -s tmpFullEvent \
  -e 'IBM.PSSP.aixos.FS.%totused:Nodenum=*;\
  VG=rootvg;LV=hd3:X>90'\
  -r "X<80" \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• /var File system filling:

  pmandef -s varFullEvent \
  -e 'IBM.PSSP.aixos.FS.%totused:Nodenum=*;\
  VG=rootvg;LV=hd9var:X>90" -r "X<80" \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• / File system filling:

  pmandef -s rootFullEvent \
  -e 'IBM.PSSP.aixos.FS.%totused:Nodenum=*;VG=rootvg;LV=hd4:X>90'\
  -r "X<80" \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• Paging space low:

  pmandef -s pageSpaceLowEvent \
  -e 'IBM.PSSP.aixos.PagSp.%totalused:NodeNum=*:X>90' \
  -r "X<80" \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• Kernel memory buffer failures:

  pmandef -s mbufFailureEvent \
  -e 'IBM.PSSP.aixos.Mem.Kmem.failures:NodeNum=*;Type-mbuf:X>X@P'\
  -r "X<80" \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• Switch input errors:

  pmandef -s switchInputErrEvent \
  -e 'IBM.PSSP.CSS.ierrors:NodeNum=*:X>X@P' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• Switch output errors:

  pmandef -s switchOutputErrEvent \
  -e 'IBM.PSSP.CSS.oerrors:NodeNum=*:X>X@P' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• Switch Transmit Queue overflows:

  pmandef -s switchInputErrEvent \
  -e 'IBM.PSSP.CSS.xmitque_ovf:NodeNum=*:X>X@P' \
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• inetd daemon activity:

  pmandef -s inetdFailureEvent \
  -e 'IBM.PSSP.Prog.xpcount:NodeNum=*;\
  ProgName=inetd;UserName=root:X@0<X@1'\
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• srcmstr daemon activity:

  pmandef -s srcmstrFailureEvent \
  -e 'IBM.PSSP.Prog.xpcount:NodeNum=*;\
  ProgName=srcmstr;UserName=root:X@0<X@1'\
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• biod daemon activity:

  pmandef -s biodFailureEvent \
  -e 'IBM.PSSP.Prog.pcount:NodeNum=*;\
  ProgName=biod;UserName=root:X@0<X@1'\
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• portmap daemon activity:

  pmandef -s portmapFailureEvent \
  -e 'IBM.PSSP.Prog.pcount:NodeNum=*;\
  ProgName=portmap;UserName=root:X@0<X@1'\
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• xntpd daemon activity:

  pmandef -s xntpdFailureEvent \
  -e 'IBM.PSSP.Prog.pcount:\
  NodeNum=range of nodes where xntpd daemon runs;\
  ProgName=xntpd;UserName=root:X@0<X@1'\
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• kerberos daemon activity:

  pmandef -s kerberosdFailureEvent \
  -e 'IBM.PSSP.Prog.pcount:\
  NodeNum=node where kerberos daemon runs;\
  ProgName=kerberos;UserName=root:X@0<X@1'\
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• dced daemon activity:

  pmandef -s dcedFailureEvent \
  -e 'IBM.PSSP.Prog.pcount:\
  NodeNum=node where dced daemon runs;\
  ProgName=dced;UserName=root:X@0<X@1'\
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• cdsadv daemon activity:

  pmandef -s cdsadvFailureEvent \
  -e 'IBM.PSSP.Prog.pcount:\
  NodeNum=node where cdsadv daemon runs;\
  ProgName=cdsadv;UserName=root:X@0<X@1'\
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• cdsd daemon activity:

  pmandef -s cdsdFailureEvent \
  -e 'IBM.PSSP.Prog.pcount:\
  NodeNum=node where cdsd daemon runs;\
  ProgName=cdsd;UserName=root:X@0<X@1'\
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local
  

• secd daemon activity:

  pmandef -s secdFailureEvent \
  -e 'IBM.PSSP.Prog.pcount:\
  NodeNum=node where secd daemon runs;\
  ProgName=secd;UserName=root:X@0<X@1'\
  -c 'echo $PMAN_HANDLE Alert: Location Information $PMAN_IVECTOR\
  | mail -s "$PMAN_HANDLE Alert" username@address' \
  -h local