Problem(Abstract)
A TSM HSM client receives the ANS9592E error in the dsmerror.log
Cause
The ANS9592E error may be received when the HSM processes fails to connect to dsmscoutd at http://hostname:23152
Environment
TSM HSM client V5.5 and V61 on UNIX and Linux
Diagnosing the problem
1: Verify if the dsmscoutd daemon is running and active listening on port 23152.
For example :
# ps -ef | grep dsmscoutd
# netstat -an | grep 23152
tcp4 0 0 *.23152 *.* LISTEN
2: Verify if the hostname in DSMNodeset is correct.
3: Verify if there is a tcpip issue with the hostname. For example :
node1 is the hostname in “DSMNodeset” and is also the hostname reported by the “hostname” command, however, the following command fails:
# ping node1
PING node1: (172.21.33.101): 56 data bytes
0821-069 ping: sendto: Cannot reach the destination network.
ping: wrote node1 64 chars, ret=-1
0821-069 ping: sendto: Cannot reach the destination network.
ping: wrote node1 64 chars, ret=-1
Resolving the problem
Different steps need be taken depending on the failure as listed above.
1: Restart dsmscoutd if it is not running or if it is not listening on port 23152.
2: Use technote “1459480” for directions on correcting the DSMNodeset.
3: Fix the TCP/IP configuration issue for node1
Note:
There are some issues with the TSM HSM V5.5.client causing the dsmscoutd to crash or terminate abnormally. These issues with dsmscoutd may also cause the automigration (dsmautomig) to stop. Those issues are described by APARs IC57526, IC58163 , IC58088 and IC60134.
