Deployment Guide Series: IBM Tivoli Monitoring V6.2

Chapter 3. Installation and configuration 119

Populating the agent depot with the tacmd addBundles

command

To populate the agent depot using the tacmd addBundles command, run the

following command:

tacmd addBundles [-i IMAGE_PATH] [-t PRODUCT_CODE] [-p

OPERATING_SYSTEM] [-v VERSION] [-n] [-f]

For the full syntax, including parameter descriptions, refer to IBM Tivoli

Monitoring Version 6.2.0 Command Reference, SC23-6045.

3.3.2 Deploying OS agents

You can install the OS agent locally or remotely using the tacmd createNode

command. The tacmd createNode command creates a directory on the target

computer called the

node. This is the directory into which not only the OS agent

is installed, but where any non-OS agents are deployed. The tacmd createNode

command uses one of the following protocols to connect to the computers on

which you want to install the OS agent:

򐂰 Server Message Block (SMB), used primarily for Windows servers

򐂰 Secure Shell (SSH), used primarily by UNIX servers, but also available on

Windows

򐂰 Remote Execution (REXEC), used primarily by UNIX servers, but not very

secure

򐂰 Remote Shell (RSH), used primarily by UNIX servers, but not very secure

You can specify a protocol to use; if you do not, the tacmd createNode command

selects the appropriate protocol dynamically.

Note: Remote deployment of agents is covered in detail in Chapter 7,

“Deploying IBM Tivoli Monitoring agents in a large scale environment”, in IBM

Tivoli Monitoring: Implementation and Performance Optimization for Large

Scale Environments, SG24-7443. You can refer to this document for more

information.

Note: Only SSH version 2 is supported.

120 Deployment Guide Series: IBM Tivoli Monitoring V6.2

Requirements for the tacmd createNode command

Before you can use the tacmd createNode command to deploy OS agents,

ensure that the following is true:

򐂰 The user ID that you are going to use during the deployment has

administrative privileges on the target computer.

򐂰 Any computer to which you want to deploy the OS agent must have a

supported protocol installed.

򐂰 Security in your environment should be configured to permit createNode to

pass through the firewall, using the protocol that you specify in the command

parameters.

򐂰 On Windows computers:

– SMB requires that the default, hidden, and administrative shares are

available on the drive being accessed and on the drive that hosts the

System temporary directory.

– SMB signing is not supported when connecting using SMB. The computer

to which you are deploying an OS agent cannot require SMB signing. For

Windows XP, disable Simple File Sharing. Simple File Sharing requires

that all users authenticate with guest privileges. This is not supported for

createNode.

– For Windows XP computers with Service Pack 2, disable the Internet

Connection Firewall.

– For Windows XP computers, set Network Access Sharing and Security to

Classic - local users authenticate as themselves.

– For all Windows computers, enable remote registry administration. (This is

enabled by default.)

򐂰 On UNIX systems, if you are using the RSH protocol, run the tacmd

createNode command as root on the monitoring server.

򐂰 If you are deploying the OS agent to a UNIX or Linux computer, that computer

must have either the ksh or bash shell.

򐂰 If you are using SSH V2 (for either Windows or UNIX), configure SSH on the

target computers to permit the use of password authentication.

Note: If you are using private key authentication in your environment, you

do not need to set SSH to permit password authentication.