IBM E027SLL-H - Tivoli Monitoring - PC, Руководство по устранению неисправностей

Страница: 101 / 310

A reported failure means that the agent is installed without using the
self-describing mode. You can relaunch the agent installation to attempt support
installation again. Before relaunching the installation, ensure that the failure will
not reappear by checking the previous installation log for the reasons for the
failure. Correct the obtained failure reasons (for example, fix the contents of the
manifest, unlock required files or folders). The alternative is to leave the agent
installed in non-self-describing mode. When relaunching, select only the agents
that must be installed with installation self-describing mode support.
If the reinstallation fails, an appropriate message is displayed, and the failure
reasons are logged in the main installation log file. If no errors are encountered, the
installation ends successfully.
Receive fatal errors during self-describing agent installation
Certain fatal error conditions when a self-describing monitoring agent installation
is running on a Tivoli Enterprise Monitoring Serverrequire you to manually use
commands to reset and remove the metadata error record in the TAPPLPROPS
table.
When the installation errors have been manually corrected on the monitoring
server, you can retry a new self-describing monitoring agent installation on the
affected hub or remote monitoring server installations.
To clear up these errors, you must be able to identify the source of the error
condition. These error condition messages are provided by the monitoring server
workload manager (WLM) in RAS1 or MSG2 error messages, or audit facility
messages. You must examine these messages to identify the specific problems in
the monitoring server installation process and in the TAPPLPROPS table.
You can view and delete the monitoring server metadata or seed installation
records stored into the TAPPLPROPS table by using the
tacmd listappinstallrecs
command and the
tacmd deleteappinstallrecs
command. You must first log in to
the monitoring server by using the
tacmd login
command. For more information
about these commands, see the IBM Tivoli Monitoring Command Reference.
To use these two commands, complete the following steps:
1.
Use the
tacmd listappinstallrecs
command to see the status of a
self-describing monitoring agent installation.
2. Analyze RAS1 or MSG2 error messages and perform the proper actions to clean
up the failed installation.
3.
Use the
tacmd deleteappinstallrecs
command to delete the records in error.
4. Retry the installation.
Missing agent managed system group in a hot standby
environment
In certain IBM Tivoli Monitoring environments, it is possible to get no predefined
managed system group for a self-describing agent in a hot standby environment.
Tivoli Monitoring environment:
v
Hub Tivoli Enterprise Monitoring Server and the mirror hub monitoring server
are at V6.2.3 Fix Pack 1 (or higher)
v
Remote monitoring server (or servers) is at V6.2.3
v
A monitoring agent with an affinity that is not known to the monitoring server,
such as a new agent
Chapter 5. Installation and configuration troubleshooting
83