Self-Describing Capability Might Be Overwritten By Unix Monitoring Server Application Support - IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual

Self-describing capability might be overwritten by UNIX
monitoring server application support
Under the following conditions, if self-describing product installation is expected,
one or more Tivoli Monitoring products might not be properly enabled for
monitoring:
v The self-describing product installation for a hub or remote monitoring server
might not run
v The product application support installation (seeding) step might not take place
on the hub or remote monitoring server
v The self-describing product installation on the Tivoli Enterprise Portal Server
might not take place
If your environment has a self-describing monitoring agent that is at a lower
version of IBM Tivoli Monitoring than the Tivoli Enterprise Monitoring Server on
Linux or UNIX that it connects to, it is possible that the installation of application
support to the monitoring server overwrites the monitoring agent's self-describing
capability.
Diagnosing that the self-describing capability is not available
Installation of a monitoring server on Linux or UNIX is different from that on
Windows in that application support for all base monitoring agents and other
supported agents are automatically installed on the monitoring server. The
automatic installation of application support files for the agents might affect the
self-describing agent capability. Check the monitoring server and portal server to
ensure that self-describing agent products are installed as expected.
To determine if the monitoring server self-describing agent product installation and
seeding took place, check the enterprise self-describing agent installation status
with the following command:
tacmd listappinstallrecs -t PC
where PC is the product code for the self-describing agent in question, such as nt
for the Windows OS agent. The following example of the output from tacmd
listappinstallrecs -t nt shows how the results of a successful installation might
look:
HUB/RTEMS
HUB_TEMS
HUB_TEMS
HUB_TEMS
REMOTE_TEMS_ZOS NT
The command output has entries for the HUB TEMS and any REMOTE_TEMS that the
agent can be connected to. The entries for PRODUCT NT with ID TMS have a value of
IC in the STATE column, Y in the SEEDSTATE column, and 0 in the STATUS column.
An unsuccessful installation and seeding might generate results like those in the
following example:
HUB/RTEMS
HUB_TEMS
The record for PRODUCT NT and ID TMS might not exist or, if it does exist, the STATE
and SEEDSTATE columns are empty. In this example, the results show that the
product NT was manually installed at the hub (STATE column is empty and there is
an entry only for ID TMS).
PRODUCT VERSION GRPID ID IDVER
NT 06230000 5655 TMS 06230000 Y
NT 06230000 5655 TPS 06230000
NT 06230000 5655 TPW 06230000
06230000 5655 TMS 06230000 Y
PRODUCT VERSION GRPID ID IDVER
NT 06230000 5655 TMS 06230000
Chapter 5. Installation and configuration troubleshooting
SEEDSTATE STATE STATUS
IC 0
IC 0
IC 0
IC 0
SEEDSTATE STATE STATUS
0
89