Description
Use
the tacmd stopAgent command to stop the given agent or agents
for the given managed systems. The OS agent must be running
on the local computer before issuing this command for a non-OS agent.
If
you have the authority to start agents and you specify only the agent
type, you do not need to log in to stop an agent on a local computer.
When you run the stopagent 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 stopped
on the local computer.
To stop an OS agent, you can 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 stopped on the managed systems specified in the deployment
group.
The no execute option is intended to allow the user
to determine which managed systems are stopped.
Note: You cannot
use this command to stop a non-default Universal Agent instance that
you created manually. Use the itmcmd agent command with the -p option
instead to stop a non-default Universal Agent instance.
Note: If you attempt to stop the portal server using this command,
you will receive a failure message. To stop the portal server, you
must use either the Manage Tivoli Enterprise Services or the associated
command line, for example, itmcmd server.
Note: Remote
Deployment is not supported in environments with a z/OS Tivoli Enterprise
Monitoring Server. This restriction includes this command.
CLI syntax
Stopping IBM® Tivoli® Monitoring
agent, remote execution path:
tacmd stopAgent
{-m|--system} SYSTEM ...
[{-f|--force}]
Stopping IBM Tivoli Monitoring
agent, remote execution path:
tacmd stopAgent
{-n|--node} MANAGED-OS
{-t|--type} TYPE ...
[{-f|--force}]
Stopping IBM Tivoli Monitoring
agent, local execution path:
tacmd stopAgent
{-t|--type} TYPE ...
[{-f|--force}]
Stopping System
Service Monitors agent, remote execution path:
tacmd stopAgent
{-h|--host} [ {smb|ssh|rexec|rsh}:// ] HOST [ :PORT ]
{-u|--username} USERNAME
{-w|--password} PASSWORD
[{-p|--property|--properties} SECTION.NAME=VALUE ...]
[{-f|--force}]
Stopping IBM Tivoli Monitoring
agent, bulk remote execution path:
tacmd stopAgent
{-g|--deploygroup DEPLOY_GROUP_NAME}
{-b|--bundlegroup BUNDLE_GROUP_NAME}
[{-f|--force} | {-x|--noexecute} ]
Stopping
System Service Monitors agent, bulk remote execution path:
tacmd stopAgent
{-g|--deploygroup DEPLOY_GROUP_NAME}
{-b|--bundlegroup BUNDLE_GROUP_NAME}
[{-u|--username} USERNAME ]
[ {-w|--password} PASSWORD]
[{-s|--serverlist} SERVER_LIST ]
[{-d|--dir|--directory} INSTALLDIR]
[{-f|--force} | {-x|--noexecute} ]
where:
- -m|--system
- Specifies a managed system on which to stop the agents.
- -f|--force
- Stops the specified agents without confirmation.
- -t|--type
- Specifies one or more agents or agent instances to stop. The value
of type is scoped to the node level.
- -n|--node
- Specifies the node on the computer where you want the agent to
be stopped. A node is identified by the managed operating system that
it contains; it 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 stop 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 stopped.
- -b|--bundlegroup
- Specifies the name of the bundle group containing the agent(s)
which will be stopped on the managed system(s) in the deployment group.
- -x|--noexecute
- Causes the command to display which managed systems will be stopped.
CLI example
The following command stops
the
Universal Agent agent with the name
stone:UA:
tacmd stopAgent –m stone:UA
The
following command stops all
UM agents on the node
Primary:STONE:NT:
tacmd stopAgent –n Primary:STONE:NT –t UM
The
following command stops all
NT agents on the local system:
tacmd stopAgent –t NT
The
following command stops a System Service Monitors agent:
tacmd stopagent -h stone.tivlab.raleigh.ibm.com -u adminstrator
-w ****** -d D:\ibm\itm
The following is an example
for bulk execution. The command stops IBM Tivoli Monitoring agents:
tacmd stopagent -g WindowsGroup -b NTBundle