IT18458: ADDING NETAPP DEVICE RESULTS IN ERROR BPCUI0172E IN GUI

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)

APAR status

• Closed as program error.

Error description

• When customers attempt to add a NetApp device, they will see
  error BPCUI0172E almost immediately (a few seconds after
  attempting to add the device).
  Then, in the GUI logs (tpctrace<N>.log), there will be a timeout
  10 minutes later. For instance:
  ''''''''''
  2016-06-20 09:17:33.414-04:00 -5287411129919322244
  NapiToBackendConvertor getNapiBean2Napi Entry, parm 1 =
  NapiDataSourceBean[
  com.ibm.tpc.internal.api.services.beans.NapiDataSourceBean@92701
  7fd,
  ,
  napiIP = <IP address>
  secondaryIP = null,
  deviceType = NETAPP_FILER,,
  internalId = ,
  capabilityId = -1,
      [...]
  2016-06-20 09:17:33.414-04:00 -5287411129919322244
  com.ibm.tpc.internal.api.services.impl.NapiManagerServiceImpl
  checkAndUploadKeyToServer
      [...]
  2016-06-20 09:27:33.426-04:00 -5287411129919322244
  com.ibm.tpc.gui.rest.datasource.ExceptionCallable timedOut
  java.util.concurrent.TimeoutException
      [...]
  2016-06-20 09:27:33.428-04:00 -5287411129919322244
  com.ibm.tpc.gui.rest.datasource.AddDataSourceTask
  createAddDataSourceStep
  com.ibm.tpc.internal.api.TPCInternalAPIException: BPCUI0172E
      at
  com.ibm.tpc.gui.rest.datasource.ExceptionCallable.timedOut(Excep
  tionCallable.java:64)
  ''''''''
  In other words, the timeout will occur 10 minutes after getting
  error BPCUI0172E in the GUI while trying to add it.
  In traceTPCDeviceServer.log, entries such as these will appear:
  ''''''''
  2016-08-10 13:38:53.988-0400 stderr: SEVERE: HWNEP0111E
  com.ibm.saas.agent.tasks.ExecuteExternalProcess executeCommand
  Thread-104583
  2016-08-10 13:38:53.988-0400 stderr:
  com.ibm.tpc.common.api.napi.NAPIConnectionException: rc = 4, msg
  = Failed running command on netapp device at <IP address>
      [...]
  2016-08-10 13:38:53.992-0400 stderr: SEVERE: HWNEP0111E The
  connection to the storage device failed. The error code is 4.
  ''''''''
  Further, the same traceTPCDeviceServer.log shows
  "NetAppException: connection refused" entries such as:
  '''''''
  2016-08-10 13:26:03.270-0400 stderr:
  com.ibm.tpc.ep.netapp.ontap.NetAppException: Connection refused
  com.ibm.saas.agent.tasks.ExecuteExternalProcess executeCommand
  Thread-103642
  2016-08-10 13:38:53.985-0400 stderr:
  com.ibm.tpc.ep.netapp.ontap.NetAppException: Connection refused
  com.ibm.saas.agent.tasks.ExecuteExternalProcess executeCommand
  Thread-104583
  '''''''
  The device server is actually attempting to connect to http port
  80; not SSH (port 22).
  This APAR will improve the handling code and the messaging to
  better inform of the port being utilized to connect to the
  storage device.
  

Local fix

• enable port 80 on the storage device to resolve the issue.
  On NetApp devices, the "httpd.admin.enable" flag might need to
  be set to ON in Data Ontap 7-mode.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Control 5.2.x users attempting to add a NetApp  *
  * device                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * IBM Spectrum Control 5.2.x users attempting to add a NetApp  *
  * device may encounter nearly immediately (a few seconds after *
  * attempting to add the device) error BPCUI0172E.  Then, in    *
  * the GUI logs there will be a timeout 10 minutes later.       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fix maintenance when available                         *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is targeted for the following maintenance
  package:
  
  | refresh pack | 5.2-TIV-TPC-RP0012 - released November 2016
  
  Fixed in IBM Spectrum Control 5.2.12
  
  http://www.ibm.com/support/docview.wss?&uid=swg21320822
  

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

  TPC ADVANCED

• Fixed component ID

  5608TPCA0

Applicable component levels