Tivoli Header

Quick Start


Managing TSM Client/Server Communications

Setting Client/Server Communications Options

This section helps you to set up Tivoli Storage Manager client/server communications.

Use the Server Options utility available from the TSM Console to view and specify server communications options. This utility is available from the Service Information view in the server tree. By default, the server uses the TCP/IP, Named Pipes, and HTTP communication methods. If you start the server console and see warning messages that a protocol could not be used by the server, either the protocol is not installed or the settings do not match the Windows protocol settings.

For a client to use a protocol that is enabled on the server, the client options file must contain corresponding values for communication options. From the Server Options utility, you can view the values for each protocol.


Attention

This section describes setting server options before you start the server. When you start the server, the new options go into effect. If you modify any server options after starting the server, you must stop and restart the server to activate the updated options.

For more information about server options, see the Administrator's Reference or the TSM Console online help.

TCP/IP Options

Here is an example of TCP/IP setting:

+--------------------------------------------------------------------------------+
|commmethod                   tcpip                                              |
|   tcpport                   1500                                               |
|   tcpwindowsize             8                                                  |
|   tcpnodelay                no                                                 |
+--------------------------------------------------------------------------------+

Named Pipes Options

The Named Pipes communication method is ideal when running the server and client on the same Windows machine because Named Pipes support is internal to the Windows base system. Named Pipes require no special configuration. Here is an example of a Named Pipes setting:

+--------------------------------------------------------------------------------+
|commmethod                     namedpipe                                        |
|     namedpipename             \\.\pipe\adsmpipe                                |
+--------------------------------------------------------------------------------+

HTTP Options

Use the HTTP communication method for the administrative Web interface. HTTP and communications require a TCP/IP connection. Here are sample HTTP settings:

+--------------------------------------------------------------------------------+
|commmethod                     http                                             |
|     httpport                   1580                                            |
+--------------------------------------------------------------------------------+

To use the administrative Web interface, your browser must have Java 1.1.6 support. See System Requirements for a list of supported browsers.

SNMP DPI(R) Subagent Options

TSM implements a simple network management protocol (SNMP) subagent. You can configure the SNMP subagent to send traps to an SNMP manager, such as NetView(R), and to provide support for a management information base (MIB). For details about configuring SNMP for use with TSM, see the Administrator's Guide.

The subagent communicates with the snmpd daemon, which in turn communicates with a management application. The snmpd daemon must support the DPI protocol. Agents are available on AIX(R), Windows 95, Windows NT, and OS/2(R). The subagent process is separate from the TSM server process, but the subagent gets its information from a server options file. When the SNMP management application is enabled, it can get information and messages from servers.

Here is an example of a SNMP setting. You must specify the COMMMETHOD option. For details about the other options, see the Administrator's Reference.

+--------------------------------------------------------------------------------+
|commmethod                     snmp                                             |
|   snmpheartbeatinterval       5                                                |
|   snmpmessagecategory         severity                                         |
+--------------------------------------------------------------------------------+

Configuring TSM Client/Server Communication Across a Firewall

The Tivoli Storage Manager server and clients can work across a firewall in most cases. You must configure the firewall to open up the ports that the server and clients need. Because firewalls differ in how you open the ports, you must follow the instructions that accompanied the firewall software or hardware that you are using. If you need help with opening ports, contact the supplier of your firewall.

The following operations require that you open ports on the firewall:

Currently the following operations are known to have problems when a firewall is in place:


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]