IT09003: QUERY SAN/SANDISCOVERY FAIL WITH ANR1786W HBAAPI NOT ABLE TO GET ADAPTER NAME

7.1.3.000-TIV-TSMSRV-WIN
7.1.3.000-TIV-TSMSRV-SolarisSPARC
7.1.3.000-TIV-TSMSRV-Linuxx86_64
7.1.3.000-TIV-TSMSRV-Linuxs390x
7.1.3.000-TIV-TSMSRV-Linuxppc64
7.1.3.000-TIV-TSMSRV-HP-UX
7.1.3.000-TIV-TSMSRV-AIX

APAR status

• Closed as program error.

Error description

• The server receives ANR1786W HBAAPI not able to get adapter name
  when SanDiscovery is evoked or Query San is issued.  This has
  been seen using two or more Dual-Port Brocade BR-825 and
  QLogic-825 HBA fibre channel adapters on a Linux system. The
  problem is that HBA_GetDiscoveredPortAttributes HBA API function
  does not return the expected data from the second adapter.  The
  HBA vendor implements the "HBA_GetDiscoveredPortAttributes"
  function. If this function is not implemented as expected the
  HBA's API do not handled this call properly and not all of the
  devices are discovered.   This function will work for the first
  port of the second HBA but  may not work on the second port.  If
  the tape devices are connected to the second port, then
  SANdiscovery can get a failure status from this function.
  Therefore, SanDiscovery skips the second port and goes to the
  next adapter. SANdiscovery will always work when tape devices
  are connected to the first port only on a dual-port HBA.
  
  Customer/L2 Diagnostics (if applicable)
  09:22:08.452 [45173][psdiscvr.c][601][psOpenFCAdpt]:Opening
  adapter = one through external module file handle = 13
  .................
  09:22:08.477 [45173][nadiscvr.c][2511][DiscoverDevices]:Found 1
  FC devices from port 1  <---- looking at second port - 0 is
  first port
  09:22:08.478
  [45173][nadiscvr.c][2527][DiscoverDevices]:deviceName =
  /dev/bsg/fc_host2 assumed number = 1 j = 1
  09:22:08.478 [45173][nadiscvr.c][2538][DiscoverDevices]:PortWWN
  10008c7cff30c023
  09:22:08.478 [45173][nadiscvr.c][2963][GetAllAdrOnSanV2]:handle
  13 port 1 number 10 index = 1
  09:22:08.478 [45173][nadiscvr.c][2973][GetAllAdrOnSanV2]:PortWWN
  10008c7cff30c023
  09:22:08.478
  [45173][psdiscvr.c][1124][psGetDiscoveredPortAttr]:Getting
  discovered port attributes for handle = 13, card index = 1 port
  index = 1.
  09:22:08.478
  [45173][psdiscvr.c][1170][psGetDiscoveredPortAttr]:Returning
  status = 6, deviceName = <NONE> for port attr.
  09:22:08.478
  [45173][nadiscvr.c][2981][GetAllAdrOnSanV2]:discover port
  failed, status = 6
  09:22:08.479
  [45173][nadiscvr.c][2559][DiscoverDevices]:GetAllAdrOnSan for
  adapter one port 1 completed with rc = -1 diskPort = 0 diskFlag
  = 0.
  09:22:08.479 [45173][nadiscvr.c][2569][DiscoverDevices]:done
  with the port 1 index 2
  09:22:08.479 [45173][psdiscvr.c][665][psCloseFCAdpt]:Closing
  handle = 13.
  09:22:08.479 [45173][psdiscvr.c][697][psCloseFCAdpt]:Handle = 13
  is closed, status = 1.
  09:22:08.479 [45173][psdiscvr.c][516][psGetFCAdptName]:Getting
  number of adapters on handle = 13 adptNumb = 1.
  09:22:08.479 [45173][psdiscvr.c][568][psGetFCAdptName]:Returning
  adapter name = <Error> for number = 1 status = 1.
  09:22:08.479
  [45173][nadiscvr.c][2439][DiscoverDevices]:GetFCAdptName failed
  with status = 1
  09:22:08.480 [45173][output.c][7474][PutConsoleMsg]:ANR1786W
  HBAAPI not able to get adapter name.~
  09:22:08.480
  [45173][nadiscvr.c][2576][DiscoverDevices]:emptyPort = 0
  diskPort = 0 totalPort = 2
  09:22:08.480
  [45173][nadiscvr.c][897][naDiscoverDevices]:DiscoverDevices
  returned with rc = 0
  09:22:08.480 [45173][psdiscvr.c][727][psFreeFCLib]:Freeing
  library with handle = 13
  
  *NOTE*
  none
  
  Platforms affected:
  Linux x86_64
  
  Initial Impact: Medium
  
  Additional Keywords: dual-port FC sandiscovery HBA API call
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Tivoli Storage Manager users of SANdiscovery.            *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in                                     *
  * level 7.1.3. 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

• R71L PSY

     UP