IT19198: "QUERY SAN" WILL DISPLAY SAME DEVICE FILE TWICE EVEN THOUGH AN ALTERNATE PATH TO THE DEVICE EXISTS

8.1.2.000-IBM-SPSRV-AIX
8.1.2.000-IBM-SPSRV-Linuxppc64le
8.1.2.000-IBM-SPCMS-Linuxx86_64
8.1.2.000-IBM-SPCMS-WindowsI32
8.1.2.000-IBM-SPSRV-Linuxs390x
8.1.2.000-IBM-SPCMS-WindowsX64
8.1.2.000-IBM-SPSRV-Linuxx86_64
8.1.2.000-IBM-SPSRV-WindowsX64
8.1.2.000-IBM-SPOC-AIX
8.1.2.000-IBM-SPOC-LinuxPPC64le
8.1.2.000-IBM-SPOC-Linuxs390x
8.1.2.000-IBM-SPOC-Linuxx86_64
8.1.2.000-IBM-SPOC-WindowsX64
IBM Spectrum Protect Server V8.1 Fix Pack 2 (V8.1.2) Downloads
IBM Spectrum Protect Server V7.1 Fix Pack 8 (7.1.8.000) Downloads

APAR status

• Closed as program error.

Error description

• Currently, the SANdiscovery function, expects that one physical
  tape device has one device file on the operating system.
  If a device is connected to two different ports on the same FC
  adapter or to two different FC adapters and appears as two
  devices to the operating system,
  the server displays the first device file twice instead of
  displaying each device file.
  For example:
  On a Linux server there are two FC adapters and a tape device is
  connected to both.
  A non-IBM tape drive is discovered as /dev/tsmscsi/mt0 and has
  an alternate path of /dev/tsmscsi/mt1
  tsmdlst shows:
  tsmdlst
  Index Minor Host CHN ID  LUN Type Vendor_ID Device_Serial_Number
  Product_ID       Rev.
  000   034   009  000 001 000 001  STK       serial_numberX
    T10000D           4.10
  001   035   005  000 003 000 001  STK       serial_numberX
  T10000D          4.10
  
  so the same tape device is attached to two different HBAs.
  
  "query san" reports the same device name twice:
  DRIVE        STK          T10000D              serial_numberX
  /dev/tsmscsi/mt0
  DRIVE        STK          T10000D              serial_numberX
  /dev/tsmscsi/mt0
  
  instead of /dev/tsmscsi/mt0 and the alternate path
  /dev/tsmscsi/mt1
  
  
  This affects IBM devices configured with IBM device driver as
  well as non-IBM devices.
  Physical  and virtual tape and library devices are affected.
  
  So if a path uses /dev/tsmscsi/mt0 and sandiscovery needs to
  update the path for some reason, it will use /dev/tsmscsi/mt0
  again rather than the alternate path of /dev/tsmscsi/mt1 .
  
  
  IBM Spectrum Protect versions affected:
  Server 6.3.x, 7.1.x and 8.1.x on Linux
  platforms.
  
  
  
  Initial Impact: Low
  
  Additional Keywords:  TSM IBM Spectrum Protect sandiscovery san
  hba path
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All IBM Spectrum Protect server users of SANdiscovrey        *
  * function.                                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available.                           *
  * This problem is projected to be fixed in levels 7.1.8 and    *
  * 8.1.2.100.                                                   *
  * Note that this is subject to change at the discretion of     *
  * IBM.                                                         *
  ****************************************************************
  

Problem conclusion

• This problem was fixed.
  Affected platforms: Linux.
  

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

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels