IJ06795: VIRTUAL CENTER SENSOR DOES NOT ITERATE OVER ALL MANAGEMENT INTERFACES WHEN COLLECTING SERIAL NUMBER VIA CIM API IN 7304

APAR status

• Closed as program error.

Error description

• The problem is the ESX has multiple virtual NICs and when
  TADDM connects with the CIM api we only attempt to connect
  to the first IP which is not reachable from this Discovery
  Server and this error is returned;
  
  2018-05-12 14:48:49,505 DiscoverManager [DiscoverWorker-30]
  2018051214073543#VirtualCenterSensor-vCSAsupport-1.2.3.4
  DEBUG vmware.ESXDiscoveryDelegate - ex
  
  org.sblim.wbem.cim.CIMTransportException:
  EXT_ERR_UNABLE_TO_CONNECT; nested exception is: ^M
  
  java.net.ConnectException: Connection refused: connect^M
  
  at
  org.sblim.wbem.client.CIMClientXML.transmitRequest(CIMClientXML.
  java:1714)^M
  
  at
  org.sblim.wbem.client.CIMClientXML.enumerateInstances(CIMClientX
  ML.java:533)^M
  
  at
  org.sblim.wbem.client.CIMClient.enumerateInstances(CIMClient.jav
  a:617)^M
  
  at
  org.sblim.wbem.client.CIMClient.enumerateInstances(CIMClient.jav
  a:648)^M
  
  at
  com.ibm.cdb.discover.sys.vmware.version.Vim25DataProvider.getEsx
  CimSerialNumber(Vim25DataProvider.java:981)^M
  
  
  Yet prior to this message you can see in the log there are other
  IPs TADDM could try to connect on.
  
  
  A Taddm code change is needed so that it should always attempt
  to connect with next IP(ESX) to get serial number if current IP
  is unreachable.
  

Local fix

• NA
  

Problem summary

• The problem is the ESX has multiple virtual NICs and when
  TADDM connects with the CIM api we only attempt to connect
  to the first IP which is not reachable from this Discovery
  Server and this error is returned;
  2018-05-12 14:48:49,505 DiscoverManager [DiscoverWorker-30]
  2018051214073543#VirtualCenterSensor-vCSAsupport-1.2.3.4
  DEBUG vmware.ESXDiscoveryDelegate - ex
  org.sblim.wbem.cim.CIMTransportException:
  EXT_ERR_UNABLE_TO_CONNECT; nested exception is: ^M
  java.net.ConnectException: Connection refused: connect^M
  at
  org.sblim.wbem.client.CIMClientXML.transmitRequest(CIMClientXML.
  java:1714)^M
  at
  org.sblim.wbem.client.CIMClientXML.enumerateInstances(CIMClientX
  ML.java:533)^M
  at
  org.sblim.wbem.client.CIMClient.enumerateInstances(CIMClient.jav
  a:617)^M
  at
  org.sblim.wbem.client.CIMClient.enumerateInstances(CIMClient.jav
  a:648)^M
  at
  com.ibm.cdb.discover.sys.vmware.version.Vim25DataProvider.getEsx
  CimSerialNumber(Vim25DataProvider.java:981)^M
  Yet prior to this message you can see in the log there are other
  IPs TADDM could try to connect on.
  The APAR shall fix this issue such that it should always attempt
  to connect with next IP(ESX) to get serial number if current IP
  is unreachable.
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  packages:
  | Fix Pack | 7.3.0-TIV-ITADDM-FP0005
  

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

• 999
  

Fix information

• Fixed component name

  APP DEPENDENCY

• Fixed component ID

  5724N5500

Applicable component levels