Filter
Top Products
SANDISCOVERY
Specifies whether the Tivoli Storage Manager SAN discovery function is
enabled. When set to ON, the storage agent will perform SAN discovery in
the following instances:
v During storage agent initialization
v When the device path has been changed and there is a conflict between
the device serial number and the device path provided by the server
Using
SAN discovery, the storage agent can automatically correct the
device’s special file name if it has been changed. If the HBA used by the
storage agent does not support SAN device mapping, you should set the
SANDISCOVERY option to OFF.
For information about Tivoli Storage Manager supported HBAs for SAN
device mapping, see www.ibm.com/software/sysmgmt/products/
support/IBMTivoliStorageManager.html
The storage agent does not require persistent binding with the SAN
discovery function enabled.
STAMaxpooledsessions number
Specifies the number of individual sessions that are allowed to start and
stop between the storage agent and the Tivoli Storage Manager server. The
range of values is 0 - 150, with a default of 25. Each session is governed by
the IDLETIMEOUT option and is stopped when the timeout value is
exceeded. If the storage agent needs more sessions than specified,
additional sessions are allowed. Although the default value is typically
sufficient, setting this option with a low number can adversely affect
performance. Be aware that if the storage agent has multiple client
sessions, increasing the value of this option will help support these
sessions.
TCPADMINPORT number
Specifies the port number on which the server TCP/IP communication
driver is to wait for requests for sessions other than client sessions. This
includes administrative sessions, server-to-server sessions, SNMP subagent
sessions, storage agent sessions, library client sessions, managed server
sessions, and event server sessions. The default is the value of TCPPORT.
Using different port numbers for the options TCPPORT and
TCPADMINPORT enables you to create one set of firewall rules for client
sessions and another set for the other session types listed above. By using
the SESSIONINITIATION parameter of REGISTER and UPDATE NODE,
you can close the port specified by TCPPORT at the firewall, and specify
nodes whose scheduled sessions will be started from the server. If the two
port numbers are different, separate threads will be used to service client
sessions and the session types. If you allow the two options to use the
same port number (by default or by explicitly setting them to the same
port number), a single server thread will be used to service all session
requests. Client sessions which attempt to use the port specified by
TCPADMINPORT will be terminated (if TCPPORT and TCPADMINPORT
specify different ports). Administrative sessions are allowed on either port,
(unless the ADMINONCLIENTPORT option is set to NO) but by default
will use the port specified by TCPADMINPORT.
THROUGHPUTDatathreshold kilobytes_per_second
Specifies the throughput that client sessions must achieve to prevent
cancellation after THROUGHPUTTimethreshold minutes have elapsed. The
48 IBM Tivoli Storage Manager for SAN for AIX: Storage Agent User’s Guide
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|