IT34335: CANNOT PROBE HITACHI VSP F700 ARRAYS. PROBES END WITH ERROR HWN025032E.

APAR status

• Closed as program error.

Error description

• Scenario exist as no pools are defined causing probes to
  fail.
  
  Because user had not created any pools, they were
  directly assigning LDEVs they had created from parity groups
  instead of the typical method of assigning those LDEVs to a
  dynamic pool and then creating LDEVs from the pool.
  
  Errors in
  Trace Logs:
  
  2020-09-16 14:20:41.572 - ERROR - HWN025032E Job
  failed during post processing of collected data from the data
  source.
  2020-09-16 14:20:41.572 - ERROR - Error processing data
  files. Exiting...
  2020-09-16 14:20:41.572 - DEBUG - Traceback
  (most recent call last):
   File "hitachi_vsp.py", line 271, in
  main
   File "Reporter.py", line 92, in start
   File
  "Reporter.py", line 1516, in probe
  KeyError:
  'host_connection_set'
  
  2020-09-16 14:20:41.572 - DEBUG -
  Writing status file...
  2020-09-16 14:20:41.572 - DEBUG - Exit
  code:
  99
  ____________________________________________________
  DB2
  Version used for Server: N/A
  The defect is against component:
  Storage
  Server/Manager build/release (TPC): 5.4.0
  Agent
  build/release (TPC): N/A
  Server/Manager (OS): N/A
  Agent(OS):  N/
  A
  ____________________________________________________
  Problem
  as described by customer:
  Cannot Probe Hitachi devices
  Initial
  customer impact (low/med/high): low
  

Local fix

• TBD
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Control & Storage Insights users monitoring     *
  * HITACHI VSP F700 where no pools are defined                  *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Spectrum Control & Storage Insights users monitoring         *
  * HITACHI VSP F700 where no pools are defined are              *
  * experiencing failed probes.                                  *
  *                                                              *
  * Because the device did not have any pools, they were         *
  * configured by directly assigning LDEVs they had created      *
  * from parity groups instead of the typical method of          *
  * assigning those LDEVs to a dynamic pool and then             *
  * creating LDEVs from the pool.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is targeted for the following release:
  
  IBM Spectrum Control 5.4.2   [ 5.4.2-IBM-SC ]
  
  ( release target 1Q 2021 / February )
  
  http://www.ibm.com/support/docview.wss?&uid=swg21320822
  
  The target dates for future releases do not represent a formal
  commitment by IBM. The dates are subject to change without
  notice.
  

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