Manualshelf

Specifications

ManualsBrandsMicroNet ManualsMusical equipmentFibre to SAS/SATA II RAID Subsystem
81828384858687888990
Configuring LifeKeeper Event Forwarding
LifeKeeper Communications Path Up
A communications path to a node has become operational
140 .1.3.6.1.4.1.7359.1.0.140
LifeKeeper Communications Path Down
A communications path to a node has gone down
141 .1.3.6.1.4.1.7359.1.0.141
The following variables are used to "carry" additional
information in the trap PDU:
Trap message all .1.3.6.1.4.1.7359.1.1
Resource Tag 130 .1.3.6.1.4.1.7359.1.2
Resource Tag 131 .1.3.6.1.4.1.7359.1.2
Resource Tag 132 .1.3.6.1.4.1.7359.1.2
List of recovered resources 111 .1.3.6.1.4.1.7359.1.3
List of recovered resources 121 .1.3.6.1.4.1.7359.1.3
List of failed resources 112 .1.3.6.1.4.1.7359.1.4
List of failed resources 122 .1.3.6.1.4.1.7359.1.4
* This trap may appear multiple times if recovery fails on multiple backup servers.
Configuring LifeKeeper Event Forwarding
Prerequisites
The SNMP event forwarding feature is included as part of the LifeKeeper core functionality, and does
not require additional LifeKeeper packages to be installed. It does require that SNMP software be
installed on each LifeKeeper node that will generate trap notification of LifeKeeper events.LifeKeeper
uses the snmp trap utility to generate the traps. This utility is provided by the snmp-utils package on
most Linux distributions (called snmp on SuSE).
In older versions of the snmp implementation (prior to 4.1) where the defCommunity directive is not
supported, the traps will be sent using the "public" community string.
It is not necessary to have an SNMP agent snmpd running on the LifeKeeper node.
The configuration of a trap handler on the network management console and its response to trap
messages is beyond the scope of this LifeKeeper feature. See the documentation associated with
your system management tool for related instructions.
Configuration Tasks
The following tasks must be performed to set up LifeKeeper SNMP Event Forwarding. All but the last
task must be repeated on each node in the LifeKeeper cluster that will be generating SNMP trap
messages.
SteelEye Protection Suite for Linux65