KDY2077E: The specified agent bundle depot \\hubtems\depot is not a directory.
Either the agent bundle depot directory does not exist or it is not a directory.
The agent bundle depot directory does not exist because no bundles have been added.
Create the repository at the C:\IBM\ITM\CMS level of the directory structure, not at
the C:\IBM\ITM\CMS\depot level. Then set DEPOTHOME to DEPOTHOME=\\hubtems\
centralrepository\depot.
The agent installation log shows error AMXUT7502E
The error AMXUT7512E might occur when running the Distributed Monitoring
Upgrade Toolkit.
The agent was not installed for one of the following reasons:
v There is another installation in progress that cannot complete until the computer
is restarted.
–OR–
v You are attempting to install a component that is already installed.
Refer to the lcfd.log on the endpoint and the agent installation log as listed in
Table 8 to determine the exact cause of the problem.
Table 8. lcfd log file
Windows UNIX-based systems
install_dir/Install/Abort IBM Tivoli Monitoring
timeStamp.log
install_dir/logs/candle_installation.log
Contact IBM Software Support if you cannot install the agent. See Chapter 2, “Logs
and data collection for troubleshooting,” on page 5 for information on what types
of data to collect before contacting Support. See the IBM Support Portal
(http://www.ibm.com/support/entry/portal/software).
Failure occurs when sharing directories for the agent deploy
depot
Although it is more efficient to use a network shared directory for the agent
deploy depot directory, there are weaknesses that might negatively impact
deployment in large enterprises:
v If an NFS is used to contain the depot and there is a problem with the NFS, then
the deployment activity is suspended for all deployments in progress.
v For UNIX environments, the directories that are mentioned on the shared
directory must have the names of each of the Tivoli Enterprise Monitoring
Server servers.
v Administrator privileges need to be assigned based on a domain user ID. This is
impractical and is contrary to the desired effect of sharing.
You receive a KFWITM290E error when using deploy
commands with a z/OS monitoring server
Remote Deployment is not supported in environments with a z/OS Tivoli
Enterprise Monitoring Server.
Running deployment in a hot-standby environment
The IBM Tivoli Monitoring hot-standby capability allows your monitoring
environment to continue operating in the event of environmental or operational
issues with the primary hub monitoring server (for detailed information about
80 IBM Tivoli Monitoring: Troubleshooting Guide
To Next Page
Loading...
Need help?
General
