IT09640: ADDING CISCO SWITCHES USING SNMP ONLY RESULTS IN ERRONEOUS FABRIC REFERENCES AND OTHER MISREPRESENTATIONS

Tivoli Storage Productivity Center 5.2.7 (select fixes from group)
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)

APAR status

• Closed as program error.

Error description

• After adding switches in the same fabric - 3 different physical
  fabrics appear for them one for each switch, and then the
  Logical Fabric changes the parent fabric with the fabric that is
  last probed. (physical switch contained by the physical fabric
  last probed.)
  
  EXPECTED RESULT: There should be only one Physical fabric since
  the switches are physically connected, and then the Logical
  fabric that contains 3 logical switches should have as parent
  the Physical fabric containing all the 3 physical switches.
  
  Additional side effects of this problem include strange things
  seen in the Web UI:
  1. For the Switches panel, the 'Links' information for a
  physical switch may be wrong.
  2. For a physical Switch's detailed view, the Internal Resources
  menu may incorrectly have no Inter-Switch Connections available,
  or may list only a subset of the Inter-Switch Connections.
  3. For a physical Switch's detailed view, the Internal Resources
  menu's Ports table may incorrectly list the Connected Resource
  and Connected Port as 'Unavailable' when the connected port is
  on a switch that is managed by TPC.
  4. The Inter-Switch Link name for a link between two switches
  may incorrectly only include one of the two managed switches'
  names.
  
  This does not occur if the fabrics were first added using the
  DCNM SMI Agent.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * TPC 5.1.x and 5.2.x users adding Cisco switches using SNMP   *
  * only                                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION.                                       *
  ****************************************************************
  * 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-RP0007 - target August 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 is sysrouted FROM one or more of the following:

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

Modules/Macros

• FABRIC
  

Fix information

• Fixed component name

  TPC ADVANCED

• Fixed component ID

  5608TPCA0

Applicable component levels