IT35627: VADP UNABLE TO SUCCESSFULLY CONNECT TO A MULTIPLE NICS VSNAP IF THE FIRST VSNAP NIC IS IN A DIFFERENT SUBNET

APAR status

• Closed as program error.

Error description

• Error Dscription:
  Starting with 10.1.6, support for multiple  network interfaces
   (NICs) was added.
  The expected behaviour when an IBM Spectrum Protect Plus vSNAP
   has multiple network interfaces (NICs) in different subnets,
  is that a vADP host using a NIC in a subnet different from the
   first NIC of the vSnap should attempt to connect to the other
  NICs until connection can complete.
  The current observed behaviour is that when the vADP fails to
  connect to the first vSnap NIC for any reason,
  the vADP does not retry, using the remaining network
  interfaces.
  
  The vADP  should try the next vSnap NICs one by one until
  finding the one located in the same subnet.
  
  A backup Joblog might display the following messages :
  SUMMARY,<timestamp>,CTGGA2399,Starting job for policy BACKUP
  with job name <SLA_Name> (ID:<SLA_ID>). id -> <JobID>.
  IBM Spectrum Protect Plus version 10.1.6-2045.
  ...
   DETAIL,<timestamp>,CTGGA0671,Backing up VM (<VMName>)
   from remote proxy (IP: <vADP_IP> Host name: <vADP_HostName>)
  ...
    ERROR,<timestamp>,CTGGA2403,Backup of vm <VMName> failed
    target storage volume name <vSnapVolumeName>.
    Error: Command finished with error: exit status 32  desc
    (mount.nfs: Connection timed out) (Mounting failed)
  
  in the vADP VMware vddk log, the same error is seen when
  attempting to access the network share presented by the vSnap :
  <timestamp> [I] Creating mount point
  /sppvadp/sppvadp__vsnap_vpool<x>_fs<abc>_<vSnapFirstNIC>_<jobID>
  <timestamp> [I] Calling 'mount -o rw,hard,wsize=1048576,
  rsize=1048576,tcp,vers=3,timeo=600 <vSnapFirstNIC>:
  /vsnap/vpool<x>/fs<abc>
  /sppvadp/sppvadp__vsnap_vpool<x>_fs<abc>_<vSnapFirstNIC><JobID>'
  
  <timestamp> [I] Command finished with error: exit status 32,
  desc (mount.nfs: Connection timed out)
  
  <timestamp> [I] Removing directory
  /sppvadp/sppvadp__vsnap_vpool<x>_fs<abc>_<vSnapFirstNIC><JobID>.
  ..
  
  <timestamp> [I] publishing status, ProcessedBytes: 0
  
  <timestamp> [I] publishing status, ProcessedBytes: 0 ... done
  
  <timestamp> [E] The backup job failed. Error:Command finished
  with error: exit status 32, desc (mount.nfs: Connection timed
  out) (Mounting failed)
  
  IBM Spectrum Protect Plus Versions Affected:
  IBM Spectrum Protect Plus 10.1.6
  
  
  Initial Impact: Medium
  
  Additional Keywords: SPP, SPPlus, NIC, VADP, VSNAP
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus level 10.1.6 and 10.1.7            *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in IBM Spectrum Protect Plus level     *
  * 10.1.7 ifix2 and 10.1.8. Note that this is subject to change *
  * at the discretion of IBM                                     *
  ****************************************************************
  

Problem conclusion

• This fix correctly handles the situation where the VADP proxy is
  connecting to a vSnap server that has multiple NICs on different
  subnets
  

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

  SP PLUS

• Fixed component ID

  5737SPLUS

Applicable component levels