IV53276: AGENT INSTANCE IS NOT RESPONDING TO THE REQUEST AND BECOMES UNRESPONSIVE.

7.2.0-TIV-ITM_VMWVI-FP0003
7.2.0.2-TIV-ITM_VMWVI-IF0003
IBM Tivoli Monitoring for Virtual Servers:VMware VI 7.2.0.2-TIV-ITM_VMWVI-IF0002
IBM(R) Tivoli(R) Monitoring for Virtual Environments: VMware VI 7.2.0.2-TIV-ITM_VMWVI-IF0003
IBM(R) Tivoli(R) Monitoring for Virtual Environments: VMware VI 7.2.0-TIV-ITM_VMWVI-FP0003

APAR status

• Closed as program error.

Error description

• ENVIRONMENT:
  IBM Tivoli Monitoring for Virtual Environment: VMware VI Agent
  7.2 FixPack 2
  
  PROBLEM DESCRIPTION:
  
  If multiple data sources are configured for a single agent
  instance and if some of the data sources (could be vCenter or
  ESX Server) are in a non responding mode ("hostd" and "vpxa"
  services for ESX Server and "Vmware VirtualCenter Server"
  service for vCenter has been stopped) then agent hangs on the
  non-responsive data source. It is unable to discover the rest
  of the configured data sources and no response is received for
  the data sources.
  
  To monitor the above behavior. Assign a query as follows:
  1) Query editor >  VMware VI Agent > KVM VCENTERS > vCenters_V7
  This query will not list all configured data sources. Further on
  "Monitored Server" workspace, you will see the ESX Server
  listed as "DOWN" for the data source in question. This will
  confirm delay/hang caused by one or more ESX servers.
  
  2) Once this is confirmed you can request a DEBUG binary from
  L3 to investigate this further. After applying the debug
  binary, traces similar to the following entry will be seen in
  the data provider log after the HANG occurs
  ****
  ?Connection.open: Open()::Step 29 : Trying to login for
  :<dataSourceName>?.
  And after this there will be no entries for the successful
  connection attempt for the particular data source as
  ?Connection.open: Open()::Step 30 : Successful login for
  :<dataSourceName>?.
  ****
  

Local fix

Problem summary

• If multiple data sources are configured for a single agent
  instance and if some of the data sources (could be vCenter or
  ESX Server) are in a non responding mode ("hostd" and "vpxa"
  services for ESX Server and "Vmware VirtualCenter Server"
  service for vCenter has been stopped) then agent hangs on the
  non-responsive data source. It is unable to discover the rest of
  the configured data sources and no response is received for
  the data sources.
  To monitor the above behavior. Assign a query as follows:
  1) Query editor > VMware VI Agent > KVM VCENTERS > vCenters_V7
  This query will not list all configured data sources. Further on
  "Monitored Server" workspace, you will see the ESX Server listed
  as "DOWN" for the data source in question. This will confirm
  delay/hang caused by one or more ESX servers.
  2) Once this is confirmed you can request a DEBUG binary from L3
  to investigate this further. After applying the debug binary,
  traces similar to the following entry will be seen in the data
  provider log after the HANG occurs
  ****
  ?Connection.open: Open()::Step 29 : Trying to login for
  :?.
  And after this there will be no entries for the successful
  connection attempt for the particular data source as
  ?Connection.open: Open()::Step 30 : Successful login for
  :?.
  ****
  

Problem conclusion

• If some of the configured data sources are delaying the response
  for the connection attempt then provider was waiting to get the
  response from the server, as a result provider blocks all of its
  processing till it get the response.
  To resolve this added a connection timeout for each connection
  attempt in a connection class so that data provider will not
  wait infinitely to receive the response from the problematic
  data source .
  The fix for this APAR is contained in the following maintenance
  packages:
  Interim Fix: 0002, 7.2.0.2-TIV-ITM_VMWVI-IF0002
  

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

  ITMF VE VM WARE

• Fixed component ID

  5724L92VI

Applicable component levels

• R720 PSY

     UP