IT36735: PING SERVER HANGS ON FIRST ATTEMPT WHEN SERVER IS PINGING ITSELF

IBM Spectrum Protect Server V8.1 Fix Pack 13 (V8.1.13) Downloads

APAR status

• Closed as program error.

Error description

• After defining a server using ('define server') on
  itself,
  'ping server MYSELF' will hang the first time. After
  the
  sessions started by the command either time out or are
  manually
  cancelled, all subsequent attempts at 'ping server
  MYSELF' will
  succeed. Command routing is unaffected by this
  issue.
  
  When ping server ends the first time (after sessions
  timeout or
  are canceled), the following messages are seen in
  dsmffdc.log
  
  gsk_secure_soc_write error: sessId 12, rc 406
  GSK_ERROR_IO
  gsk_secure_soc_read error. SessId 12, rc 406
  GSK_ERROR_IO
  
  
  Here is an example scenario:
  
  There is a server
  called SERVER1 where the output of ipconfig
  showed the ipV4
  address as 123.45.67.890
  
  Then server to server communication
  is set up as follows:
  
  Protect: SERVER1>set serverpassword
  password
  	(this is the password of the server)
  
  Protect:
  SERVER1>define server SERVER1 hla=123.45.67.890
  		 lla=1500
  serverpassword=password
  	(defining the server on itself, with
  the same password)
  
  Protect: SERVER1>ping server
  SERVER1
  	(pinging the server from itself)
  
  The first time you
  try to ping SERVER1 from SERVER1 after
  'define server SERVER1',
  it will hang.
  
  Issuing 'ping server SERVER1' starts two
  sessions. One is a
  Server session and the other is a Node
  session.
  
  When one of the two sessions (Server or Node) times
  out or is
  manually cancelled, ping server ends with the
  following
  messages:
  
  ANR0454E Session rejected by server
  SERVER1, reason: 201 -
   Communication Failure.
  ANR4546W A ping
  request to server 'SERVER1' was not able to
   establish a
  connection by using server credentials.
  ANR1706I A ping request
  to server 'SERVER1' was able to
   establish a connection by
  using administrator
   credentials.
  ANS8001I Return code
  11.
  
  Once it has ended in this way, the second time and
  all
  subsequent times you try to ping server SERVER1 from
  SERVER1 it
  succeeds quickly with:
  
  ANR4617I A ping request to
  server 'SERVER1' was able to
   establish a connection by using
  server credentials.
  ANR1706I A ping request to server 'SERVER1'
  was able to
   establish a connection by using administrator
  
  credentials.
  
  Versions Affected:
   IBM Spectrum Protect Server
  8.1.2 and above on all platforms
   IBM Spectrum Protect Server
  7.1.8 and above on all platforms
  
  Initial Impact: Low
  

Local fix

• After starting 'ping server SERVER1' issue 'query session'
  from
  an admin command line to find the Server session
  number:
  
  Protect: SP101>query session
  
   Sess Comm. Sess Sess
  Client Name
  Number Method State ... Type ...
  ------ ------
  ------ ------- ---------
   1 SSL Run ... Admin ... TSMADMIN
   13
  SSL IdleW ... Server ... SERVER1
   14 SSL Start ... Node ...
  SERVER1
   15 SSL Run ... Admin ... TSMADMIN
  
  
  Then issue 'cancel
  session 13' to cancel the Server session.
  
  Retry 'ping server
  SERVER1'.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All IBM Spectrum Protect server users                        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level. This problem was fixed in level 8.1.12.  *
  ****************************************************************
  

Problem conclusion

• Affected platforms for reported release:  AIX, Linux, Windows.
  Platforms fixed:  AIX, Linux, Windows.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels

• R81A PSY

     UP

• R81L PSY

     UP

• R81W PSY

     UP