You can generate Simple Network Management Protocol (SNMP)
Version 1 traps for health events and dynamic cluster start and stop
application server events.
Before you begin
Any standard SNMP management endpoint that is capable of
receiving Version 1 traps can receive traps that are sent by Intelligent Management. See the documentation
associated with your SNMP management endpoint for instructions on
how to import the Management Information Base (MIB) file that is provided
with Intelligent Management.
About this task
You can generate SNMP Version 1 traps for the following
two types of events:
- Health events: In this case, sending an SNMP trap is one of the
actions that can be performed when a health policy is triggered. The
SNMP trap contains the name of the health policy that was triggered,
when the health policy was triggered, and where the health policy
was triggered.
- Dynamic cluster start and stop application server events: When
the application placement controller starts or stops an application
server, the controller can send an SNMP trap notifying an SNMP management
endpoint.
The precise events are defined by a MIB file in the
WAS_HOME/etc/wvemib.txt file.
You can use this MIB file to import the events into your SNMP management
endpoint.
Complete the following procedure to generate SNMP
traps.
Procedure
- Configure the host name and an optional port of the SNMP
management endpoint. Set the following custom property:
- In the administrative console, select .
- Specify the name of the custom property as snmp.manager.
Note: You can also create multiple
SNMP managers by using the snmp.manager custom
property. The property accepts comma separated values of <snmp
manager host name>:<port>.
- Specify the value of the custom property as hostname[:port]. This is the host name and UDP port to which the SNMP traps are
sent. The default port value is 162.
For example, setting the value of the custom property to mySnmpManagerHost:162 indicates
that SNMP Version 1 traps should be sent to UDP port 162 of the host
named mySnmpManagerHost.
- Configure the product to send an SNMP trap for health policy
violations. Create a new health policy and select the Generate
an SNMP trap predefined health policy action as one of
the actions to perform when the health policy is triggered. In the
administrative console, select .
- Set the following custom property to disable SNMP traps
from being sent when the application controller starts or stops a
member of a dynamic cluster.
- In the administrative console, select .
- Specify the name of the custom property as snmp.disabledTraps.
- Specify the value of the custom property as dynamicClusterStartStopServer.
- Configure the SNMP community string. By default,
the product sends an SNMP trap with a community string value equal
to public. Set the following custom property
to override the default value.
- In the administrative console, select .
- Specify the name of the custom property as snmp.community.
- Specify a value for the custom property. The
value of the custom property is then used as the community string
value.