Specifications

Verifying the Configuration
1. Ensure that the snmptrap utility is available as noted above.
2. Specify the network management node to which the SNMP traps will be sent. This can be
done either by command line or by editing the /etc/default/LifeKeeper file. You must
specify the IP address rather than domain name to avoid DNS issues.
l By command line, use the lk_configsnmp (see thelk_configsnmp(1M) man page for
details). This utility will only accept IP addresses.
l Or, edit the defaults file /etc/default/LifeKeeper to add the IP address. Search for the
entry LK_TRAP_MGR= and insert the IP address to the right of the = (no white space around
the =).
3. If you are using an older version of the snmp implementation that does not support the
defCommunity directive, skip this step. Traps will be sent using the "public" community
string. Otherwise, do the following:
Specify a default community in /usr/share/snmp/snmp.conf. If this file does not
exist, create it using sufficiently secure permissions. Add the directive
"defCommunity" with a value.This specifies the SNMP version 2c community string
to use when sending traps. For example, add a line like this:
defCommunity myCommunityString
Refer to the snmp.conf man page (delivered with the snmp package) for more
information about this configuration file.
4. Perform whatever configuration steps are needed on the remote management console to
detect and respond to the incoming trap OIDs from LifeKeeper events.If the management
node is a Linux server, the minimum that you would need to do to begin verification of this
feature would be to start the snmptrapd daemon with the -f -Lo option (print the messages to
stdout).
Verifying the Configuration
To verify that the configuration is working, initiate a LifeKeeper action (for example, start or stop
LifeKeeper, or bring a resource in-service manually using the LifeKeeper GUI).Verify that the trap
message was received at the management console. If a trap is not received, inspect the appropriate
log files on the management system, and follow the normal troubleshooting practices provided with
the management software. The LifeKeeper log can be inspected to determine if there was a problem
sending the trap message. SeeSNMP Troubleshootingfor more information.
Disabling SNMP Event Forwarding
To disable the generation of SNMP traps by LifeKeeper, simply remove the assignment of an IP
address from the LK_TRAP_MGR environment variable in the file /etc/default/LifeKeeper.
This can be accomplished using the lk_configsnmp utility from the command line with the
"disable"option (see the lk_configsnmp(1M) page for an example). Or, edit
/etc/default/LifeKeeper and change the entry for LK_TRAP_MGR to LK_TRAP_MGR= (or
remove the line entirely).This must be done on each node that should be disabled from sending trap
messages.
66Configuration