IZ22022: UA DOES NOT PARSE THE SNMP MIB VARIABLE PROPERLY

APAR status

• Closed as program error.

Error description

• At this point, I suspect that the "***Error: received
  unsupported Counter/Gauge attribute size: 1" messages mentioned
  by the customer are just a downstream side effect of the
  malformed OIDs that UA is trying to retrieve.  The first order
  of business is to fix the variable instance problem that's
  causing BESSYSHEALTHTABLE data retrieval to fail.
  

Local fix

• comment out OID causing problem.
  

Problem summary

• For some SNMP OID trees, the OIDs pertaining tablular instances
  of a SNMP table can cause incorrect parsing by UA SNMP data
  provider.  Typical user experience will be successful processing
  and display of first N instances of an SNMP table, followed by
  recurring errors in UA trace log; these errors are due to SNMP
  data provider attempting to process N +1, N +2, ...  instances
  of the SNMP table, but these N+ instances are not valid OIDs.
  UA "NoSuchName" trace message of following form will appear in
  UA trace logs.
  
  *****SNMP response error status received - <some_SNMP_OID>
  <NoSuchName> MIB attribute <some_SNMP_variable_name>
  

Problem conclusion

• The fix for this APAR is included in the following maintenance
  vehicle:
  
     | interim fix | 6.1.0.7-TIV-ITM-IF0001
  
  Note: Search the IBM technical support web site for maintenance
  package availability.
  

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

  UNIVERSAL AGENT

• Fixed component ID

  5724K1000

Applicable component levels

• R610 PSY

     UP