Troubleshooting
Problem
During troubleshooting of a failed schedule prompt or server-to-server communication, it is may be useful to confirm what ports the various Tivoli Storage Manager client daemons or processes are using.
Resolving The Problem
The Tivoli Storage Manager client daemons (dsmcad/dsmsched), storage agent process (dsmsta) or TSM server process (dsmserv) all use their own respective port. The below example will show how to find out which one uses port 1500.
- Issue the netstat operating system command.
netstat -Aan|grep 1500
For example, this will show the following output :
f100020003c9f390 tcp4 0 0 *.1500 *.* LISTEN
Note: If there is no output, it means no process is listening on port 1500.
- Issue the rmsock operating system command.
rmsock f100020003c9f390 tcpcb
For example, this will show the following output :
The socket 0x3c9f000 is being held by process 10716 (dsmsta).
Note: f100020003c9f390 is from step 1 output.
- Issue the ps operating system comnmand.
ps -ef|grep 10716
For example, this will show the following output :
root 10716 20760 0 Jun 01 - 0:30 dsmsta
Note: 10716 is the process ID from step 2.
In this example, dsmsta is the daemon listening on port 1500.
[{"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Server","Platform":[{"code":"PF002","label":"AIX"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21239951