Tivoli Storage Manager for Sun Solaris Quick Start


Enabling Communications with the Server

You can choose one or more communication methods to use with Tivoli Storage Manager. The server supports the following communication methods:

You can also specify that no communication method be used by adding the following server option to the server options file:

+--------------------------------------------------------------------------------+
|commmethod none                                                                 |
+--------------------------------------------------------------------------------+

With this option, users cannot connect to the server. It is useful for experimenting with policy commands.

Setting Shared Memory Options

Tivoli Storage Manager supports shared memory communication between clients and servers on the same machine. To use shared memory, TCP/IP must be installed on the machine. This is the default communication method. Here is a sample shared memory setting:

+--------------------------------------------------------------------------------+
|commmethod     sharedmem                                                        |
|   shmport     1510                                                             |
+--------------------------------------------------------------------------------+

In this example, SHMPORT specifies the TCP/IP port address of a server when using shared memory. Use the SHMPORT option to specify a different TCP/IP listen port. The default port address is 1510.


Attention
  
To avoid shared memory communication errors, one of the following statements must be true:
  • The dsm.sys stanza for the local client must include PASSWORDACCESS GENERATE. This causes the dsmtca (Trusted Communications Agent) to run as root.
  • The client user ID must be root.
  • The client and server user ID must be the same.

Setting TCP/IP Options

Here is a sample TCP/IP setting:

+--------------------------------------------------------------------------------+
|commmethod        tcpip                                                         |
|  tcpport         1500                                                          |
|  tcpwindowsize   0                                                             |
|  tcpnodelay      yes                                                           |
+--------------------------------------------------------------------------------+

TCPPORT
The server TCP/IP port address. The default value is 1500.

TCPWINDOWSIZE
The size of the TCP/IP buffer used when sending or receiving data. The window size used in a session is the smaller of the server and client window sizes. Larger window sizes use additional memory but may improve performance.

You can specify an integer from 0 to 64. To use the default window size for the operating system, specify 0.

TCPNODELAY
Whether or not the server sends small messages or lets TCP/IP buffer the messages. Sending small messages may improve throughput but increases the number of packets sent over the network. Specify YES to send small messages or NO to let TCP/IP buffer them. The default is YES.

Setting HTTP Options

Use the HTTP communication method for the administrative web interface. TCP/IP must be active for you to use the administrative client web interface. Here is a sample HTTP communication setting:

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

HTTPPORT specifies the TCP/IP port address of a server when using HTTP. The default value is 1580.

Note:If you use the administrative web interface, your browser must have Java 1.1 support.

Setting SNMP 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, and to provide support for a management information base (MIB).

Note:For details about configuring SNMP for use with Tivoli Storage Manager, 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, Windows 95, Windows NT, and OS/2.

The subagent process is separate from the TSM server process, but the subagent gets its information from a TSM server options file. When the SNMP management application is enabled, it can get information from TSM servers.

Here is an example of a SNMP communication method setting:

+--------------------------------------------------------------------------------+
|commmethod                  snmp                                                |
|  snmpsubagent             hostname jimbo communityname public timeout 2600     |
|  snmpheartbeatinterval    5                                                    |
|  snmpmessagecategory      severity                                             |
+--------------------------------------------------------------------------------+

You must specify the COMMMETHOD and SNMPSUBAGENT options. The SNMPSUBAGENT option must specify a host that is an AIX, Windows 95, Windows NT, or OS/2 system with an SNMP agent. This option is for the dsmsnmp program. For details about the other options, see Administrator's Reference.


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