Direct links to fixes
Tivoli Storage Productivity Center Refresh Pack 5
Refresh Pack 5.2.5 (March 2015) for Tivoli Storage Productivity Center
Fix Pack 5.2.5.1 (April 2015) for Tivoli Storage Productivity Center
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
We have a Windows 2012 Hyper-V server hosting 20 VMs, each of which is running Windows 2012. They are assigned virtual HBA ports based on a common WWNN generated on the Hyper-V server. So, the end result is twenty unique WWPNs that can be zoned, mapped, etc. When I try to add an agentless server, I type in the name of one of the hosts. TPC says it has discovered other WWPNs related to that host , and it displays all 20 WWPNs of the VMs. And, it won't let me remove any of them (all or nothing). In other words, this part of the code seems to assume that these WWPNs all belong to the same host. If I try to manually "add port" and just type a single WWPN, the same thing happens: TPC insists all 20 belong to the same host. The problem here is that all VMs' ports are grouped together with one node WWN on the Hyper-V side.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * TPC 5.2.x users with multiple virtual HBA ports associated * * with a common node WWN. * **************************************************************** * PROBLEM DESCRIPTION: * * See ERROR DESCRIPTION. * **************************************************************** * RECOMMENDATION: * * Apply fix maintenance when available. * ****************************************************************
Problem conclusion
A fix has been provided such that agentless servers can be added in this case. The fix for this APAR is targeted for the following maintenance package: | refresh pack | 5.2-TIV-TPC-RP0005 - March 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
Comments
APAR Information
APAR number
IT06506
Reported component name
TPC ADVANCED
Reported component ID
5608TPCA0
Reported release
524
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-01-14
Closed date
2015-02-09
Last modified date
2015-02-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
DEVICE
Fix information
Fixed component name
TPC ADVANCED
Fixed component ID
5608TPCA0
Applicable component levels
Document Information
Modified date:
05 October 2023