After you populate the agent depot, you can deploy the
monitoring agent to remote systems.
Before you begin
Before you begin, ensure that your system meets all of
the remote deployment preinstallation requirements, and that the operating
system agent on the remote system is started and has root access.
Procedure
To install the monitoring agent, and initiate the deployment,
complete the following steps:
- Go to where the tacmd command
is located. For example, the default directory is:
/opt/IBM/ITM/bin
- Log on to the remote system by using the sysadmin user
ID and password:
./tacmd login -s host_name -u sysadmin -p password
- Locate the nodes that you want to deploy
the monitoring agent to, by issuing the following command:
./tacmd listSystems -t UX
- Deploy the monitoring agent by issuing
the following command:
./tacmd addSystem -t sk -n Primary:yourhost:UX -p INSTANCE=yourhost
TSM_AUTHENTICATION_INFORMATION.KSK_SERVER_ADDR=yourhost.yourcompany.com
TSM_AUTHENTICATION_INFORMATION.KSK_PORT_NUMBER=1500
TSM_AUTHENTICATION_INFORMATION.KSK_USER=tsmusername
TSM_AUTHENTICATION_INFORMATION.KSK_PASSWORD=tsmpassword
where:
- TSM_AUTHENTICATION_INFORMATION.KSK_SERVER_ADDR indicates
the server IP address of the Tivoli® Storage
Manager server
- TSM_AUTHENTICATION_INFORMATION.KSK_PORT_NUMBER indicates
the port that is required to access the Tivoli Storage
Manager server
- TSM_AUTHENTICATION_INFORMATION.KSK_USER indicates
the user ID that is used to access the Tivoli Storage
Manager server
- TSM_AUTHENTICATION_INFORMATION.KSK_PASSWORD indicates
the password for the user ID that is used to access the Tivoli Storage
Manager server
- TSM_AUTHENTICATION_INFORMATION.KSK_KEYSTORE indicates
the file system location if your agent will be communicating with
the Tivoli Storage
Manager server
through an SSL connection. Leave this blank to use the default non-SSL
authentication method.
If your agent will be communicating with the server through
an SSL connection, specify a value by using the TSM_AUTHENTICATION_INFORMATION.KSK_KEYSTORE option.
Tip: When
specifying a monitoring agent instance name, as a best practice, you
can specify the name of the Tivoli(r) Storage
Manager server, or the host name of the server as your instance
name.
For example:./tacmd addSystem -t sk -n Primary:yourhost:UX -p INSTANCE=yourhost
TSM_AUTHENTICATION_INFORMATION.KSK_SERVER_ADDR=yourhost.yourcompany.com
TSM_AUTHENTICATION_INFORMATION.KSK_PORT_NUMBER=1500
TSM_AUTHENTICATION_INFORMATION.KSK_USER=tsmusername
TSM_AUTHENTICATION_INFORMATION.KSK_PASSWORD=tsmpassword
KUICAR010I: The agent type SK is being deployed.
KUICAR028I: The operation has been successfully queued for deployment,
the transaction id is 1329702031328000000000041,
use the getDeployStatus CLI to view the status.
- Review the deployment status by
issuing the following command:
./tacmd getDeployStatus -t sk
For
example:Transaction ID : 1334178758871657000027663
Command : INSTALL
Status : SUCCESS
Retries : 0
TEMS Name : TEMS
Target Hostname: yourhost:UX
Platform : aix526
Product : SK
Version : 063300000
Error Message : KDY0028I: Request completed successfully. Deployment request was
processed successfully and is now completed.
What to do next
After
you deployed the agent, verify that the Tivoli Storage
Manager data is
being collected and displayed in Tivoli Enterprise
Portal. Log in
to Tivoli Enterprise
Portal,
select the system that the monitoring agent was deployed to, and verify
that data is displayed correctly in the workspaces.