Server and client configuration
This domain tests server and client configuration: how the server listens, how a node is registered, and how the client finds the server. You need to distinguish server options, client option files, node definitions, and communication settings.
Server-side settings
Server behavior is controlled in dsmserv.opt. Typical entries include COMMMETHOD TCPIP and TCPPORT 1500. After changing server options, restart the server or use the supported refresh mechanism. Administrative access uses an admin ID, not a client node password. Storage destinations and policy domains must exist before clients can back up successfully.
Client-side settings
On Windows the client option file is dsm.opt; on UNIX it is dsm.sys, with dsm.opt selecting a server stanza. A stanza normally contains SERVERNAME, TCPSERVERADDRESS, TCPPORT, NODENAME, PASSWORDACCESS GENERATE, and DOMAIN. Register the node on the server with REGISTER NODE, assigning the correct policy domain. PASSWORDACCESS GENERATE stores an encrypted password locally after the first successful authentication.
Worked example
Register node web01 in policy domain WEB with REGISTER NODE web01 secret DOMAIN=WEB. On the client, create a dsm.sys stanza named tsmprod with TCPSERVERADDRESS tsm.example.com, TCPPORT 1500, NODENAME web01, PASSWORDACCESS GENERATE, and DOMAIN /home /opt. Run dsmc query session to test. The reasoning is: server node definition first, client stanza second, then authentication and filespace discovery.
Traps
Do not use an admin password as a node password. Do not put client stanza settings in dsmserv.opt. A wrong DOMAIN means expected filespaces are not backed up, and a missing NODENAME can make the client use the host name unexpectedly.