IBM Enterprise Console - Manual (Page 98)

Cold Start
The endpoint adapter is automatically started as a step in the adapter installation
process when the adapter configuration profile (ACP) is distributed using the
Adapter Configuration Facility (ACF).
Manually start the adapter on the endpoint with the following command:
init.tecad_snmp start
Warm Start
You can restart a running adapter. Doing so is useful when you have changed one
of the adapter files and want to have it read in without bringing the adapter or
host down completely.
Use one of the following kill commands to force the adapter to restart:
# kill -HUP process_number
—OR—
# kill -1 process_number
Stopping the Adapter
The endpoint adapter can be automatically stopped by distributing an ACP that
has the adapter start command removed from the after-file-distribution actions. See
the IBM Tivoli Enterprise Console User’s Guide for additional information.
Manually stop the adapter on the endpoint with the following command:
init.tecad_snmp stop
Events Listing
The following table shows the class names and severities of all events defined for
the SNMP adapter. You can use it to get a sense of how SNMP traps are mapped
to IBM Tivoli Enterprise Console events and to determine if you want to make any
changes. The events are defined in the BAROC file.
See the IBM Tivoli Enterprise Console Rule Builder’s Guide for more information
about customizing the BAROC file.
Event Class Structure
Event classes are defined hierarchically, with child classes inheriting attribute value
defaults from the parent. The SNMP event classes follow a simple hierarchy.
The adapter fills in the following attribute defaults. The attributes are used in
event group filters.
source
SNMP
sub_source
NET
origin
hostIPaddress where the event originated
hostname
hostname where the event originated
86 IBM Tivoli Enterprise Console: Adapters Guide