Description
Use
the tacmd startAgent command to start the given agent or agents
for the given managed systems, locally or remotely, if they are not
running. You can start all agents of one or more specified types on
a specified node remotely by running the startagent command
with the -t|--type and -n|--node options.
If you have the
authority to start agents and you specify only the agent type, you
do not need to log in to start an agent on a local computer. When
you run the startagent command on a local system, use the -t|--type
option and do not use the -n|--node or -m|--system options.
When
you specify only an agent type, all agents of that type are started
on the local computer.
To start an OS agent, you must issue
the command on the local computer where the agent is installed.
By
using the bulk deployment option, the agents specified in the bundle
group are started on the managed systems specified in the deployment
group.
The no execute option is intended to allow the user
to determine which managed systems will be started.
Note: - If you have made changes to the agent configuration file on a UNIX computer, use the itmcmd
agent command with the -c option to start the agent instead
of this command. By using the -c option with itmcmd agent preserves
any changes that you have made to the configuration. The tacmd
startAgent command does not preserve the changes.
- You cannot use this command to start a non-default Universal Agent
instance that you created manually. Use the itmcmd agent command
with the -p option instead to start a non-default Universal
Agent instance.
- If you attempt to start the portal server using this
command, you will receive a failure message. To start the portal server,
you must use either the Manage Tivoli Enterprise Services or the associated
command line, for example, itmcmd server.
- Remote Deployment is not supported in environments with a z/OS
Tivoli Enterprise Monitoring Server. This restriction includes this
command.
CLI syntax
Starting IBM® Tivoli® Monitoring
agent, remote execution path:
tacmd startAgent
{-m|--system} SYSTEM ...
[{-f|--force}]
Starting IBM Tivoli Monitoring
agent, remote execution path:
tacmd startAgent
{-n|--node} MANAGED-OS
{-t|--type} TYPE ...
[{-f|--force}]
Starting IBM Tivoli Monitoring
agent, local execution path:
tacmd startAgent
{-t|--type} TYPE ...
[{-f|--force}]
Starting
System Service Monitors agent, remote execution path:
tacmd startAgent
{-h|--host} [ {smb|ssh|rexec|rsh}:// ] HOST [ :PORT ]
{-u|--username} USERNAME
{-w|--password} PASSWORD
[{-p|--property|--properties} SECTION.NAME=VALUE ...]
[{-d|--dir|--directory} INSTALLDIR]
[{-f|--force}]
Starting IBM Tivoli Monitoring
agent, bulk remote execution path:
tacmd startAgent
{-g|--deploygroup DEPLOY_GROUP_NAME}
{-b|--bundlegroup BUNDLE_GROUP_NAME}
[ [{-f|--force} | {-x|--noexecute} ]
Starting
System Service Monitors agent, bulk remote execution path:
tacmd startAgent
{-g|--deploygroup DEPLOY_GROUP_NAME}
{-b|--bundlegroup BUNDLE_GROUP_NAME}
[ {-u|--username} USERNAME ]
[ {-w|--password} PASSWORD ]
[ {-s|--serverlist} SERVER_LIST ]
[ [{-f|--force} | {-x|--noexecute} ]
where:
- -m|--system
- Specifies a managed system on which to start the agents.
- -f|--force
- Starts the specified agents without confirmation.
- -t|--type
- Specifies one or more agents or agent instances to start. The
value of type is scoped to the node level.
- -n|--node
- Specifies the node on the computer where you want to start an
agent. The node is the installation directory for all agents. The
name of a node includes the computer where the OS agent is installed
and the product code for the OS agent. For example, stone.ibm.com:LZ
is the name of the node on computer stone.ibm.com, which has a Linux OS agent installed.
- -h|--host
- Specifies the host on which to start the System Service Monitors
agent. Optionally, a specific connection protocol and a port can be
specified.
- -u|--username
- A valid user log in ID on the specified host.
- -w|--password
- The password for the specified username.
- -p|--property|--properties
- Specifies one or more SECTION.NAME=VALUE pairs that identify configuration
properties, where SECTION specifies the configuration section containing
the configuration property, NAME specifies the name of the configuration
property, and VALUE specifies the property value. Specify the instance
name of the system to be configured through the INSTANCE property
for systems that can have multiple instances.
- -s|--serverlist
- Specifies one or more server names separated by spaces.
- -d|--dir|--directory
- Specifies the location on the specified host where the agent is
installed, if the agent is not installed in the default location.
This location must be specified as a directory, in absolute path format.
- -g|--deploygroup
- Specifies the name of the deployment group to which the agents
in the bundle group will be started.
- -b|--bundlegroup
- Specifies the name of the bundle group containing the agent(s)
which will be started on the managed system(s) in the deployment group.
- -x|--noexecute
- Causes the command to display which managed systems will be started.
CLI example
This command starts the
Universal
Agent agent with the name
stone:UA.
tacmd startAgent –m stone:UA
This
command starts all
UM agents on the node
Primary:STONE:NT.
tacmd startAgent –n Primary:STONE:NT –t UM
The
following command starts all
NT agents on the local system:
tacmd startAgent –t NT
The
following command starts a System Service Monitors agent:
tacmd startagent -h stone.tivlab.raleigh.ibm.com -u adminstrator
-w ****** -d D:\ibm\itm
The following
is an example for bulk execution. The command starts IBM Tivoli Monitoring
agents:
tacmd startagent -g WindowsGroup -b NTBundle