Sessioninitiation

Use the sessioninitiation option to control whether the server or client initiates sessions through a firewall. The default is that the client initiates sessions. You can use this option with the schedule command.

AIX operating systems HP-UX operating systems Linux operating systems Oracle Solaris operating systems Mac OS X operating systems For the client scheduler, you do not need to open any ports on the firewall. If you set the sessioninitiation option to serveronly, the client will not attempt to contact the server. All sessions must be initiated by server prompted scheduling on the port defined on the client with the tcpclientport option. The sessioninitiation option only affects the behavior of the client scheduler running in the prompted mode. If you set the sessioninitiation option to serveronly, with the exception of client acceptor daemon-managed schedulers, the command-line client, the backup-archive client GUI, and web client GUI still attempts to initiate sessions.

Windows operating systems For the client scheduler, you do not need to open any ports on the firewall. If you set the sessioninitiation option to serveronly, the client will not attempt to contact the server. All sessions must be initiated by server prompted scheduling on the port defined on the client with the tcpclientport option. The sessioninitiation option only affects the behavior of the client scheduler running in the prompted mode. If you set the sessioninitiation option to serveronly, with the exception of client acceptor daemon-managed schedulers, the command-line client, the backup-archive client GUI, and web client GUI still attempt to initiate sessions.

Attention: You cannot use the dsmcad for scheduling when you set the sessioninitiation option to serveronly

Note: If you set the sessioninitiation option to serveronly, the client setup wizard and scheduler service are unable to authenticate to the Tivoli® Storage Manager server. In this case, you can execute the scheduler from the command line (dsmc schedule) and enter the password for your node when prompted.

Note: If you set the sessioninitiation option to serveronly, the client setup wizard and scheduler service are unable to authenticate to the Tivoli Storage Manager server. In this case, you can execute scheduler from the command line (dsmc schedule) and enter the password for your node when prompted or use the following dsmcutil command to write the password into the Windows Registry:

dsmcutil updatepw /node:nnn /password:ppp /validate:no

Windows operating systems To avoid this problem, when configuring the client scheduler using the setup wizard, ensure that the Contact the TSM Server to validate password checkbox on the TSM Authentication page is unchecked.

A similar problem can occur if an encryption key is required for backup operations. In this case, you can execute the scheduler from the command line (dsmc schedule) and enter the encryption key when prompted. After the password and encryption key are updated, you must restart the scheduler.

If you set the sessioninitiation option to client, the client initiates sessions with the server by communicating on the TCP/IP port defined with the server option tcpport. This is the default. Server prompted scheduling can be used to prompt the client to connect to the server.

Note:

The Tivoli Storage Manager server can specify SESSIONINITiation=clientorserver or SESSIONINITiation=serveronly on the register node and update node commands. If the server specifies SESSIONINITiation=clientorserver, the client can decide which method to use. If the server specifies SESSIONINITiation=serveronly, all sessions are initiated by the server.
If sessioninitiation is set to serveronly, the value for the tcpclientaddress client option must be the same as the value for the HLAddress option of the update node or register node server command. The value for the tcpclientport client option must be the same as the value for the LLAddress option of the update node or register node server command.
The Tivoli Storage Manager client API does not support this option.

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 Scheduler tab, Session Initiation field of the Preferences editor.

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

Syntax


                      .-Client-----.   
>>-SESSIONINITiation--+------------+---------------------------><
                      '-SERVEROnly-'

Parameters

Client: Specifies that the client initiates sessions with the server by communicating on the TCP/IP port defined with the server option TCPPORT. This is the default. Server prompted scheduling can be used to prompt the client to connect to the server.
SERVEROnly: Specifies that the server will not accept client requests for sessions. All sessions must be initiated by server prompted scheduling on the port defined on the client with the tcpclientport option. Except for client acceptor daemon-managed schedulers, the command-line client, the backup-archive client GUI, and web client GUI still attempt to initiate sessions.; If the server AUTHENTICATION option is set to LDAP, do not set the client sessioninitiation option to serveronly; if you do, schedules cannot run.
SERVEROnly: Specifies that the server will not accept client requests for sessions. All sessions must be initiated by server prompted scheduling on the port defined on the client with the tcpclientport option. Except for client acceptor daemon-managed schedulers, the command-line client, the backup-archive client GUI, and web client GUI still attempt to initiate sessions.; If the server AUTHENTICATION option is set to LDAP, do not set the client sessioninitiation option to serveronly; if you do, schedules cannot run.

Examples

Options file:: sessioninitiation serveronly
Command line:: schedule -sessioninitiation=serveronly

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