SNMP trap Sendto fails
An agent running on an IPv4 or dual stack IPv4/IPv6 system tries to emit an
SNMP trap to an IPv6 destination address defined in the trapcnfg XML file, but
the trap is not received on the destination system. In the agent log file, there is an
error message stating that the SNMP trap Sendto failed with rc=-1.
Ensure that the system sending SNMP traps to IPv6 destinations can resolve its
own IPv6 address. The system where the trap emitting-agent is running must have
a valid IPv6 address associated with its own local host name. If the DNS
configuration has not been updated for IPv6, then it is necessary to modify the
\etc\hosts file or /etc/resolv.conf file on the agent system in order to associate
the local host name with a valid local IPv6 address, for example, not a loopback or
link-local address.
Situation overrides cannot be used to disable situations on specific
systems at specific times
Dynamic thresholding has a restriction on the override of situations with calendar
entries. Situation overrides can be used to change the conditions under which
situations run on specific systems at specific times. However, they cannot be used
to disable a situation on specific systems at specific times. To override the time a
specific situation runs, the situation must include a time attribute, for example,
Local_Time.Day_Of_Week, and then you can use an override to change the value
of the time attribute that causes the situation to run.
Situation or calendar name in thresholds.xml file appears incorrect
If situation and calendar overrides are created with names that do not conform to
the naming convention, the names will be a randomly generated name and be
displayed in the xml file as such. The naming convention includes the following
conditions:
v Must start with an alphabetical character (a-z, A-Z)
v Can contain 1-30 additional alphanumeric characters (a-z, A-Z, 0-9)
v Can also contain the following special character (_)
v Must end with an alphanumeric character
BAROC file is missing for IBM Tivoli Monitoring 5.x Endpoint
situations
A BAROC file does not exist for the IBM Tivoli Monitoring 5.x Integration Agent
that defines the class definitions for the following situations:
v KTM_Health_Indication
v KTM_Missing_Metadata
v KTM_Resource_Model_Statu
As a result, when any of these situations are triggered, the forwarded situation
events are not successfully processed by the EIF receiver.
The BAROC file for the Integration Agent is no longer supplied with IBM Tivoli
Monitoring. Generate the BAROC files as needed by using the BAROC file
generator tool found here:
http://catalog.lotus.com/topal?NavCode=1TW10TM43
Chapter 10. Monitoring agent troubleshooting 183
To Next Page
Loading...
Need help?
General
