Quick Start
You can choose one or more communication methods to use with Tivoli Storage
Manager. The server supports the following communication methods:
- Shared memory
- TCP/IP
- HTTP (for the administrative client web interface)
- SNMP DPI
- NETBIOS
- IPX/SPX
- SNA LU6.2 (APPC)
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.
Tivoli Storage Manager supports multiple network adapters that let an
administrator specify one or more communication methods. This support
lets an administrator increase server throughput by providing multiple
connections to the same network or serve several physically distinct networks
with the same server.
With the exception of Shared Memory, the server communication methods
support multiple network adapters. IPX/SPX supports a single adapter
through the IPX socket number. Protocols differ in the way the use of
multiple adapters is specified. Multiple protocols may be used on each
of the adapters in the system.
- TCP/IP
- No additional server configuration is required for TCP/IP support of
multiple adapters. Each of the adapters must be set up with a separate
TCP/IP address. Clients are then provided with one of the addresses for
their client options file. The server will accept sessions from each of
the adapters. The session limit is placed on the accumulated count from
all of the adapters.
- SNA LU6.2 (APPC)
- Separate LUnames must be configured for sessions from each of the adapters
to be used. The LUname statement in the dsmserv.opt file must be
specified so that the server knows the LUnames on which to accept
sessions. Up to four LUnames can be specified on the LUname statement
to provide an LUname for each of the adapters. Only one TP profile need
be configured for the multiple adapters. Clients are given a single
network address (networkname.LUname) with which to communicate with the
server, meaning they can establish a session with the specific adapter that
corresponds to the LUname in their options file.
- NETBIOS
- A LANADAPTER statement is specified for each NETBIOS session.
LANADAPTER statements range from LANADAPTER 0 to LANADAPTER 3, letting you
specify up to four network adapters on which to accept sessions. The
NETBIOSNAME statement then specifies up to four server names, one per adapter
on which the server accepts sessions. Clients use the NETBIOSSERVERNAME
statement to name the corresponding name on the server. This process
also directs the session request to a specific adapter.
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. 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.

| To avoid shared memory communication errors, at least one of
the following statements must be true:
|
Depending on the AIX software installed, you may be able to establish up to
fifty concurrent shared memory communications sessions when running Tivoli
Storage Manager.
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 2048. 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.
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.
|
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 an 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 |
| snmpheartbeatinterval 5 |
| snmpmessagecategory severity |
+--------------------------------------------------------------------------------+
You must specify the COMMMETHOD option. For details about the
other options, see Administrator's Reference.
To use NetBIOS on AIX 4.1, IBM AIX NetBIOS or IBM AIX Connections
must be installed on the AIX server. Here is a sample NETBIOS
setting:
+--------------------------------------------------------------------------------+
|commmethod netbios |
| lanadapter 0 |
| netbiosname tsmserv1 |
| netbiosbuffersize 16 |
+--------------------------------------------------------------------------------+
Note: | In configuring IBM AIX NetBIOS or IBM AIX Connections, ensure that you use
the AT&T naming convention choice on the TPI configuration of the mcsadm
utility.
|
- LANADAPTER
-
A network adapter number on which the server communicates when the NETBIOS
communication method is specified. Up to four adapters may be specified
with up to four LANADAPTER statements. The default is 0. You can
specify a value from 0 to 3.
- NETBIOSNAME
-
The name to be used for communications on the network. This name must
be unique across the network that includes the LAN requestors and other
NETBIOS applications. This name can up to 16 characters and is
case-sensitive. The first character cannot be an asterisk (*), and the
first three characters cannot be the letters IBM. The defaults are
ADSMSERV1, ADSMSERV2, ADSMSERV3, and ADSMSERV4 (depending on the number of
LANAdapter statements you have). For example, if you have LANADAPTER 0
and LANADAPTER 1, the defaults are ADSMSERV1 and ADSMSERV2.
- NETBIOSBUFFERSIZE
-
The size, in kilobytes, of the NETBIOS communications buffer. This
parameter is optional, and the default is 16. Valid values are from 1
to 32. A larger buffer can improve communication performance but
requires more memory.
To use IPX/SPX, IBM AIX and NetBIOS Support/6000 or IBM AIX
Connections must be installed on the AIX server. Here is a sample
IPX/SPX setting:
+--------------------------------------------------------------------------------+
|commmethod ipxspx |
| ipxsocket 8522 |
| ipxbuffersize 4 |
+--------------------------------------------------------------------------------+
Where:
- IPXSOCKET
- The socket number (hex value) on which the server SPX communication driver
is to wait. The default, 8522, is registered with Novell.
- IPXBUFFERSIZE
- The size, in kilobytes, of the IPX/SPX communications buffer. This
parameter is optional, and the default is 4. Valid values are from 1 to
32. A larger buffer can improve communication performance but requires
more memory.
Application programs communicate with each other using a layer of Systems
Network Architecture (SNA) called advanced program-to-program communication
(APPC), also known as LU6.2. Sample Communication Profiles shows sample configuration profiles for AIX 4.1 SNA
Server/6000 3.1. Here is a sample SNA LU6.2
setting:
+--------------------------------------------------------------------------------+
|commmethod snalu6.2 |
| luname dsmserv1 |
| tpnprofilename dsmservlocal |
+--------------------------------------------------------------------------------+
Where:
- LUNAME
-
The name that TSM uses for APPC communications on the network. The
default is DSMSERV1. You can specify up to four LU names. The
maximum length is eight characters.
- TPNPROFILENAME
-
The transaction program profile name for APPC AIX. This is a required
option. The TP profile name should also be in the SNA database.
This must be a unique name of up to 14 ASCII characters.
To establish an SNA LU6.2 configuration by using SMIT, complete the
following procedure:
- Define your machine to SNA Services by the use of Initial Node
Setup. Refer to the control_pt stanza in Figure 5.
- Modify the SNA DLC token ring profile (tok0.0001) by performing the
following steps:
- On an X Windows command line, enter:
+--------------------------------------------------------------------------------+
| smit sna |
+--------------------------------------------------------------------------------+
- Click Configure SNA Profiles.
- Click Advanced Configuration.
- Click Links.
- Click Token Ring.
- Click Token Ring SNA DLC.
- Click Change/Show a Profile.
- In the Profile name field, supply a profile name, and click
Do .
- Set the value in the Max. number of active link stations
(1-255) field to a value between 1 and 255. Set this value
to 255 to allow 255 active link stations on a particular port at one
time. See the max_active_link_stations line in the
sna_dlc_token_ring stanza of Figure 5.
- Set the value in the Dynamic link stations supported? field to
No to prevent the base listening station (tok0.0001) from creating a
dynamic link station to intercept incoming calls. See the
dynamic_link_station_supported line in the
sna_dlc_token_ring stanza of Figure 5.
- Click Do.
- Define a link station token ring profile for clients:
- On an X Windows command line, enter:
+--------------------------------------------------------------------------------+
| smit sna |
+--------------------------------------------------------------------------------+
- Click Configure SNA Profiles.
- Click Advanced Configuration.
- Click Links.
- Click Token Ring.
- Click Token Ring Link Station.
- Click Add a Profile.
Note: | If you need to make changes to this profile, select Change/Show a
Profile.
|
- In the Profile name field, supply a unique name. In the
example provided in Figure 5, this profile is called SERVER. See the
prof_name line in the
link_station_token_ring stanza of Figure 5.
- In the SNA DLC Profile name field,
Select List.
Choose the SNA DLC token ring profile name defined previously
(tok0.0001). See the sna_dlc_profile_name
line in the link_station_token_ring stanza of Figure 5.
- Set the value in the Stop link station on inactivity? field to
Yes to allow the link stations to be reused when no more active
sessions remain on the link station. This enables a different TSM
client to establish a link with this particular server. See the
stop_on_inactivity line in the
link_station_token_ring stanza of Figure 5.
- Specify a value in the If yes, Inactivity time-out (0-10
minutes) field to a number between 1 and 10. In this example,
this value is set to 1 minute. If the IDLETimeout option (of the server
options file) is larger than this link station inactivity time-out value, it
may take longer for a TSM client to establish connection with the server
because a new link station may have to be created. See the
time_out_value line in the
link_station_token_ringstanza of Figure 5.
Note: | For information on deactivating the system-generated SNASVCMG mode sessions,
refer to Administrator's Guide
|
- Ensure the Access routing field is link_address. See
the access_routing_type line in the
link_station_token_ring stanza of Figure 5.
Leave the value for Remote link address field blank, so the
server machine is a non-selective listening station.
- Set the value in the Initiate call when link station is
activated? field to No to specify this station as a listening
station. See the call_out_on_activation line in the
link_station_token_ring stanza of Figure 5.
- Change the value in the Activate link station at SNA start up?
field to Yes to allow the link station to be established
automatically. See the
activate_link_during_system_init line in the
link_station_token_ring stanza of Figure 5.
- Change the value in the CP-CP sessions supported? field to
Yes. See the cp_cp_sessions_supported
line in the link_station_token_ring stanza of Figure 5.
- Set the value in the Restart on activation? field to
Yes to allow a new listening station to be generated. See
the restart_on_activation line in the
link_station_token_ring stanza of Figure 5.
- Click Do.
- Define a Transaction Program Name:
- On an X Windows command line, enter:
+--------------------------------------------------------------------------------+
| smit sna |
+--------------------------------------------------------------------------------+
- Click Configure SNA Profiles.
- Click Advanced Configuration.
- Click Sessions.
- Click LU 6.2.
- Click LU 6.2 Transaction Program Name (TPN).
- Click Add a Profile.
Note: | If you need to make changes to this profile, click Change/Show a
Profile.
|
- In the Profile name field, supply a unique name, and ensure
that it matches the name used in the TPNPROFILENAME option in your server
options file. In the example here, it is DSMSERVLOCAL. See the
prof_name line in the local_tp stanza of Figure 5.
- In the Transaction Program name (TPN) field, supply one program
name, for example, DSMSERV. This name must be uppercase, for example,
DSMSERV. See the tp_name line in the
local_tp stanza of Figure 5.
- In the Full path to TP executable field, supply a full path
name, for example,
+--------------------------------------------------------------------------------+
| /usr/tivoli/tsm/server/bin/dsmserv |
+--------------------------------------------------------------------------------+
See the full_path_tp_exe line in the
local_tp stanza
of Figure 5.
- In the Standard input file/device field, change
/dev/console to /dev/null
- In the Standard output file/device field, change
/dev/console to /dev/null
- In the Standard error file/device field, change
/dev/console to /dev/null
- Click Do.
- Verify and update your profiles:
- On the command line, enter:
+--------------------------------------------------------------------------------+
| smit sna |
+--------------------------------------------------------------------------------+
- Click Configure SNA Profiles.
- Click Advanced Configuration.
- Click Verify Configuration Profiles.
- In the Update action if verification successful field, click
List.
- Click dynamic_update to verify and update SNA Services as
active. Otherwise, click on normal_update.
- Click Do.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]