Linux Os Agent Fails To Start; Os Agent Start Command Fails; Specific Events Are Not Monitored By The Windows Os Agent; Take Action Commands And Reflex Automation - IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual

Linux OS agent fails to start

On some Linux systems (SUSE 10, Linux Itanium) there is a problem with OS
agent operation after deployment. The current workaround is to use the -o
KDYRXA.AUTOCLEAN=NO option when executing the tacmd createnode command to
deploy the OS agent to a remote node. This option places the transferred
installation image in the system temporary directory on the remote node.

OS agent start command fails

If you receive an error message indicating that your OS agent start command has
failed, you might have exceeded the maximum number of supported processes
while using the IP.PIPE network protocol. The host using the IP.PIPE network
protocol is limited to 16 Tivoli Monitoring processes. You can identify the issue by
noting the agent server process exiting unexpectedly with the following key
messages:
(4E85BA02.005E-1:kdcsuse.c,119,"KDCS_UseFamily") status=1c010005,
"cant bind socket", ncs/KDC1_STC_CANT_BIND_SOCK
(4E85BA02.005F-1:krabrreg.cpp,1289,"CTRA_reg_base__Load") Use family failed,
family=34, st=1c010005
(4E85BA02.0060-9:kde12li.c,189,"KDE1_ServerListen") Status 1DE0002C=
KDE1_STC_SERVERNOTBOUND
(4E85BA02.0061-9:kdcs1li.c,126,"Listen") KDE1_ServerListen(0x1DE0002C)
(4E85BA02.0062-1:kraaumsg.cpp,143,"CTRA_msg_server_exit_status")
CTRA Server: exit status, 0
These messages indicate that the server cannot bind a socket and that the server is
exiting. This behavior is a known limitation.

Specific events are not monitored by the Windows OS agent

You might encounter a problem monitoring specific events with the Windows OS
Agent. When running IBM Tivoli Monitoring V6.2.3 Fix Pack 1 (or later), you have
the capability to display events and event data from any event log you are
monitoring. However, the Log Name and Log Name (Unicode) attributes represent
input fields, not output fields. Filtering on the event log name is not supported.
You must specify the exact name of the event log you want to monitor.
The Windows Registry Editor lists the event log name as a key in either of two
paths:
The name of the event log is the key listed under the Eventlog or Channels key.
For example, the Internet Explorer event log has the key HKEY_LOCAL_MACHINE\
SYSTEM\CurrentControlSet\Services\Eventlog\Internet Explorer and the
Channels\Microsoft-Windows-TaskScheduler/Operational event log channel has
the key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\
WINEVT\Channels\Microsoft-Windows-TaskScheduler/Operational

Take action commands and reflex automation

Attributes differ between the situation action commands and
what is displayed in the portal client
The raw data delivered by an monitoring agent is a string or number. The Tivoli
Enterprise Portal has format information to control the display. When an attribute
172
IBM Tivoli Monitoring: Troubleshooting Guide
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\
Channels