IT06497: TPC FAILS TO ADD DS8K WHEN USING BOTH PRIMARY AND SECONDARY HMCS

Refresh Pack 5.2.6 (June 2015) for Tivoli Storage Productivity Center
Refresh Pack 5.2.7 (August 2015) for Tivoli Storage Productivity Center
IBM Spectrum Control V5.2.8 (December 2015)
IBM Spectrum Control V5.2.9 (February 2016)
IBM Spectrum Control V5.2.10 (May 2016)
IBM Spectrum Control V5.2.10.1 (July 2016)
IBM Spectrum Control V5.2.11 (August 2016)
IBM Spectrum Control V5.2.12 (November 2016)
IBM Spectrum Control V5.2.13 (March 2017)
IBM Spectrum Control V5.2.14 (May 2017)
IBM Spectrum Control V5.2.15 (August 2017)
IBM Spectrum Control V5.2.15.2 (November 2017)
IBM Spectrum Control V5.2.16 (March 2018)
IBM Spectrum Control V5.2.17 (May 2018)
Fix Pack 5.2.7.1 (February 2016) for Tivoli Storage Productivity Center

APAR status

• Closed as program error.

Error description

• The problem exists when using ESSNI client with R7.2 code or
  above (which TPC 5.2.x uses) and microcode lower than R7.2 on
  the DS8k side.
  Starting from R7.2, the ESSNI client uses new port 1751 to
  connect to the HMC. If the connection fails, it will use old
  1750 port.
  However, the NI client by itself does not specify a timeout
  value when opening socket on port 1751, so it depends on the OS
  to supply the default timeout value or on the application (TPC).
  The problem happens because the ESSNI client will take 20*2=40
  seconds to connect with each HMC because two sockets are
  established for each HMC. This means a total of 80+ seconds
  needed to finish dual HMC connection.
  Since TPC is presently set to a 60 second timeout to establish
  the connection, the dual connection will fail to establish
  because it is under the total time for a dual HMC environment.
  This APAR will increase the default timeout value for the ESSNI
  client in TPC to 2 minutes.
  

Local fix

• Increase the TPC ESSNI client timeout value to 2 minutes.
  To increase the timeout from the CLI you can use the command
  "setdscfg". The the variable to set is called
  "NAPI.Timeout.TestConnection". The default is 60000 miliseconds.
  Please note that the value specified is considered milliseconds
  by TPC.
  Note: You must have root/Administrator authority to use this
  command.
  - Open a Windows CMD prompt or AIX/Linux shell and type:
  - cd <TPC_installation_directory>\cli
  - tpctool setdscfg -user <userid> -pwd <password> -url
  localhost:9550 -property NAPI.Timeout.TestConnection 120000
  - No need to restart the Device server.
  - Then re-add the DS8k in question using both HMCs.
  Please see these links:
  - Location of tpctool:
  http://www-01.ibm.com/support/knowledgecenter/SSNE44_5.2.1/com.i
  bm.tpc_V521.doc/fqz0_r_pdguide_tpctool.html?lang=en
  - About the tpctool:
  http://www-01.ibm.com/support/knowledgecenter/SSNE44_5.2.1/com.i
  bm.tpc_V521.doc/fqz0_r_tpctool_command.html?lang=en
  - About the setdscfg command:
  http://www-01.ibm.com/support/knowledgecenter/SSNE44_5.2.1/com.i
  bm.tpc_V521.doc/fqz0_r_cli_setdscfg.html?lang=en
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users adding DS8000 subsystems using 2 HMC adresses          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * TPC stops the connection for timeout before completing and   *
  * the DS8K cannot be added using both HMC addresses            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fix maintenance when available.                        *
  ****************************************************************
  

Problem conclusion

• This fix increases the timeout and the connection can be done.
  The fix for this APAR is targeted for the following maintenance
  package:
  
  | refresh pack | 5.2-TIV-TPC-RP0006 - target June 2015
  
  http://www-01.ibm.com/support/docview.wss?&uid=swg21320822
  
  The target dates for future refresh packs do not represent a
  formal commitment by IBM. The dates are subject to change
  without notice.
  

Temporary fix

• Add the subsystem using only one HMC address.
  

Comments

APAR Information

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

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

Modules/Macros

• DISK
  

Fix information

• Fixed component name

  TPC

• Fixed component ID

  5608TPC00

Applicable component levels

• R520 PSY

     UP

• R525 PSY

     UP