IBM Tivoli Storage Manager, Version 7.1

Commmethod

The commmethod option specifies the communication method you use to provide connectivity for client-server communication.

Supported Clients

This option is valid for all clients.

Options File

AIX operating systems HP-UX operating systems Linux operating systems Oracle Solaris operating systems Mac OS X operating systems Place this option in the dsm.sys file within a server stanza. You can set this option on the Communication tab of the Preferences editor.

Windows operating systems Place this option in the client options file (dsm.opt). You can set this option on the Communication tab of the Preferences editor.

Syntax


              .-TCPip-----.   
>>-COMMMethod-+-----------+------------------------------------><
              +-SHAREdmem-+   
              '-V6TCPIP---'

Syntax


              .-TCPip------.   
>>-COMMMethod-+------------+-----------------------------------><
              +-SHAREdmem--+   
              +-V6TCPIP----+   
              '-NAMedpipes-'

Parameters

TCPip

The Transmission Control Protocol/Internet Protocol (TCP/IP) communication method. This is the default.

V6Tcpip

Indicates that either TCP/IP V4 or V6 should be used, depending on the system configuration and the results of a domain name service lookup. A valid DNS environment must be available.

NAMedpipes

The interprocess communication method that permits message data streams to pass between a client and a server. Use this communication method with a Tivoli® Storage Manager server running on the same workstation as the client.

SHAREdmem

Use the shared memory communication method when the client and server are running on the same system. This provides better performance than the TCP/IP protocol. This communication method is valid only for AIX®, HP-UX, Linux, and Solaris clients.

When specifying this communication method on AIX, the client can be logged in as root or non-root, as long as the server is running as root. If the server is not running as root, the user ID running the client must match the user ID running the server.

Important: When using commmethod sharedmem on Linux, you might receive error message: ANR8294W Shared Memory Session unable to initialize on the server or storage agent console. By default, Linux is not set up with sufficient system resources to create the message queues. You must increase the kernel parameter, MSGMNI, to 128 (the default is 16). You can modify this parameter by performing the following command:

echo 128 > /proc/sys/kernel/msgmni

To enable this parameter to remain persistent after rebooting the system, you can instead add the following line to the file /etc/sysctl.conf, then reboot the system:

kernel.msgmni=128

To view the current ipc settings, run this command:

ipcs -l

Now look at the max queues system wide value. The default is 16.

SHAREdmem

Use the shared memory communication method when the client and server are running on the same system. This provides better performance than the TCP/IP protocol.

Note: Use of this communication method requires that both client and server run under the same Windows account.

Examples

Options file:

commmethod tcpip

Use only TCP/IP V4

AIX operating systems HP-UX operating systems Linux operating systems Oracle Solaris operating systems Mac OS X operating systems Windows operating systems commmethod V6Tcpip

AIX operating systems HP-UX operating systems Linux operating systems Oracle Solaris operating systems Mac OS X operating systems Windows operating systems Use both TCP/IP V4 and V6, depending on how the system is configured, and the results of a domain name service lookup.

Note: The dsmc schedule command cannot be used when both SCHEDMODe prompt and commmethod V6Tcpip are specified.

Command line:

-commm=tcpip

AIX operating systems HP-UX operating systems Linux operating systems Oracle Solaris operating systems Mac OS X operating systems Windows operating systems -commm=V6Tcpip

This option is valid only on the initial command line. It is not valid in interactive mode.

Feedback