Description
Use the tacmd checkprereq command to check
for prerequisites required for deploying an agent to a managed system.
The tacmd checkprereq command deploys a prerequisite
checking tool to determine if the target system meets the requirements
for the agent. A global transaction ID is immediately returned. You
can then use the Deployment Status workspace in the Tivoli Enterprise
Portal, or run the tacmd getDeployStatus command,
to view the status of the queued operation. The pass or fail status
information is saved in candlehomelogs/
checkprereq_results.
Note: Remote Deployment is not supported in environments
with a z/OS Tivoli Enterprise Monitoring Server. This restriction
includes this command.
CLI syntax
For a single monitoring agent with endpoint credentials:
tacmd checkprereq {-h|--host} [ {smb|ssh|rexec|rsh}:// ] HOST [ :PORT ]
{-t|--type} TYPE
{-u|--username} USERNAME
{-w|--password} PASSWORD
[ {-d|--dir|--directory} DIRECTORYPATH ]
[ {-v|--version} VERSION ]
[ {-p|--property|--properties} NAME=VALUE ... ]
[ {-o|--option|--options} NAME=VALUE ... ]
[ {-c|--collectall} ]
For a single monitoring agent with an OS agent at the endpoint:
tacmd checkprereq {-n|--node MANAGED-OS}
{-t|--type} TYPE
[ {-v|--version} VERSION ]
[ {-p|--property|--properties} NAME=VALUE ... ]
[ {-o|--option|--options} NAME=VALUE ... ]
[ {-c|--collectall} ]
For bulk execution of agents:
tacmd checkprereq {-g|--deploygroup DEPLOY_GROUP_NAME}
{-t|--type} TYPE
[{-u|--username} USERNAME ]
[{-w|--password} PASSWORD ]
[ {-d|--dir|--directory} DIRECTORYPATH ]
[ {-v|--version} VERSION ]
[ {-o|--option|--options} NAME=VALUE ... ]
[ {-c|--collectall} ]
where:
- -h|--host
- Identifies the host where the prerequisite check
runs. Optionally, a specific connection protocol and a port can be
specified. If you specify an OS agent product code, the correct product
code for the target is automatically chosen.
- -n|--node
- Identifies the node or monitoring system where you want to execute
the prerequisite check.
- -g|--deploygroup
- Identifies the name of the deployment group to which the prerequisite
checker will be deployed.
- -t|--type
- Specifies the type of agent to add to the monitoring system.
- -u|--username
- A valid user login ID on the specified host. The software prompts
you for the user name if you do not specify one.
- -w|--password
- The password for the specified user name. The software prompts
you for the password if you do not specify one.
- -d|--dir|--directory
- Specifies the location on the specified host where the agent
is to be installed. This location must be specified as a directory,
in absolute path format.
- -v|--version
- Specifies the version of the agent.
- -o|--option|--options
- One or more configuration parameters that can be used to customize
the operation of this program. The valid options are the following:
TIMEOUT, CONNECT_TIMEOUT, TEMP, VERSION, AUTOCLEAN, KEYFILE, PASSPHRASE,
AGENT, JLOG_APPENDING, JLOG_SET_FILE_DIR, JLOG_SET_FILE_NAME, JLOG_SET_MAX_FILES,
JLOG_SET_MAX_FILE_SIZE, ENV_env_variable_name. The values are to be
specified in KEY=VALUE format.
- -p|--property|--properties
- Specifies one or more configuration properties that identify
configuration properties of the new system and their values. Values
can differ per system. The following properties are valid for an IBM
Tivoli Monitoring OS agent: ENCRYPT, KEY, IP_PIPE, IP_SPIPE, PROTOCOL,
PROTOCOL1, PROTOCOL2, PROTOCOL3, PORT, SERVER, SNA_NETNAME, SNA_LOGMODE,
SNA_LUNAME, SNA_TPNAME, BACKUP, BSERVER, BPROTOCOL, BPROTOCOL1, BPROTOCOL2,
BPROTOCOL3, BSNA_NETNAME, BSNA_LOGMODE, BSNA_LUNAME, BSNA_TPNAME,
FOLDER, BPORT, BIND_TO_NIC. The values are to be specified in KEY=VALUE
format. See the tacmd describeSystemType command
for a list of valid IBM Tivoli Monitoring application agent properties.
- -c|--collectall
- Specifies the collection of all results for all members in the
deployment group, meaning that both success and failure results are
retrieved. The default without specifying this option is to retrieve
only failed results.
If you want to collect results for a selected
group member only, you can specify KDYRXA.COLLECTALL=TRUE in the properties
list for the deployment group member.
CLI example
The following example runs the command on the amsntx00 host, where
a Windows OS Agent is being added. Both the success and failure results
are retrieved:
tacmd checkprereq --host amsntx00 --type NT --collectall -u administrator
The following example, for bulk execution of agents, runs the command
on the UX_deploy_group, for UNIX agents. Both the success and failure
results are retrieved:.
tacmd checkprereq -g UX_deploy_group -t UX -c
Related commands
Return to Table 1.