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

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

Tivoli Monitoring's hot-standby feature, see the IBM Tivoli Monitoring
High-Availability Guide for Distributed Systems). You should refrain from
deploying or updating agents when IBM Tivoli Monitoring is converting to a
mirror monitoring server. No agent deployments or remote deployment operations
should be executed from a hot-standby mirror hub, as this might cause your
deployment transactions to get stuck in a queued state, and you might not be able
to clear them.
Difficulty with default port numbers
You can use Telnet to test if the port is open in the firewall. Use the following
command for this test:
telnet hostname 15001
where 15001 is the port number in question.
Selecting Security Validation User displays a blank popup
While configuring the Tivoli Enterprise Monitoring Server you have an option to
select the Security Validation User. When selecting this option a blank popup is
displayed. The Security Validation is working despite a blank popup with this
label that has a yellow triangle and exclamation point:
TEMS User Authentication actions are needed!
When installing a monitoring agent on top of the Systems
Monitor Agent, you receive an error
If you try to install a monitoring agent (that is not one of the agents built with IBM
Tivoli Monitoring v6.2.2 Agent Builder) on top of the Systems Monitor Agent, you
receive an error:
install.sh failure: KCI1163E cannot read file "/opt/IBM/ITM/registry/imdprof.tbl".
Monitoring agents that have been configured to connect to a monitoring server
cannot be installed on the same system as those that have been configured for
autonomous operation.
Also, monitoring agents that have been configured for autonomous operation
cannot be installed on the same system as those that are connected to a monitoring
server.
Some rows do not display in an upgraded table
About this task
You might not see all tables after upgrading the Warehouse Proxy to IBM Tivoli
Monitoring V6.1 because some tables might be corrupted. Do the following to find
the errors that occurred during the upgrade:
1. Edit the KHDRAS1_Mig_Detail.log file.
2. Search for the word EXCEPTION.
The
KHD_MAX_ROWS_SKIPPED_PER_TABLE
environment variable allows you to skip bad
data.
KHD_MAX_ROWS_SKIPPED_PER_TABLE
indicates the number of rows per table to
skip to migrate if the data that needs to be inserted is incorrect. When this number
is reached, migration of the table is aborted.
Chapter 5. Installation and configuration troubleshooting
81