IZ85255: UA SNMPV2 STANDARD TRAPS TO SNMPV1 HAS 'UNAVAILABLE' VALUES

IBM Tivoli Monitoring 6.2.2 Fix Pack 8 (6.2.2-TIV-ITM-FP0008)
IBM Tivoli Monitoring 6.2.2 Fix Pack 9 (6.2.2-TIV-ITM-FP0009)
IBM Tivoli Monitoring 6.2.2 Fix Pack 6 (6.2.2-TIV-ITM-FP0006)

APAR status

• Closed as program error.

Error description

• Product: Universal Agent
  Release: 6.22
  Severity: 2
  Approver:BEH
  Compid:  5724K1000 Tivoli Universal Agent
  
  Environment:
  Components MibUtility.jar,  rfc233.mib, UA's handling of the
  Generic Trap Number and Specific Trap Number associated to
  the various SNMP traps that belong to SNMP trap enterprise
  OID 1.3.6.1.6.3.1.1.5
  
  Platforms: AIX;6.1
  
  Problem Description:
  While attempting to compile a set of MIBs for one of our Cisco
  switches using the MibUtility some of the MIBs generate an mdl
  file but no trapcnfg file.
  
  The UA code that is trying to deprecate SNMPv2 received traps
  to SNMPv1, since UA only fully supports SNMPv1.
  
  Detailed Recreation Procedure:
  Here are the issues with regard to UA processing the SNMP traps
  named
  linkDown and linkUp, with the OIDs 1.3.6.1.6.3.1.1.5.3 and
  1.3.6.1.6.3.1.1.5.4, respectively.
  
  The correct SNMP trap enterprise entry and the correct SNMP trap
  entries
  to the TRAPCNFG are as follows:
  
  # enterprises:
  #
  snmpMIB {1.3.6.1.6.3.1.1.5}
  
  
  # User added trap formats:
  #
  linkDown {1.3.6.1.6.3.1.1.5} 6 3 A 1 0 "Status Events"
  linkUp {1.3.6.1.6.3.1.1.5} 6 4 A 1 0 "Status Events"
  authenticationFailure {1.3.6.1.6.3.1.1.5} 6 5 A 1 0 "Status
  Events"
  coldStart {1.3.6.1.6.3.1.1.5} 6 1 A 1 0 "Status Events"
  warmStart {1.3.6.1.6.3.1.1.5} 6 2 A 1 0 "Status Events"
  
  NOTE:  Inserting multiple entries for a given SNMP trap
  enterprise OID
  serves no purpose, as UA will use the first one it finds per
  sequential
  processing of TRAPCNFG file. So for example:
  
  interfaces {1.3.6.1.6.3.1.1.5}
  Cisco_SAN {1.3.6.1.6.3.1.1.5}
  snmpMIBObjects {1.3.6.1.6.3.1.1.5}
  
  UA will use the 'interfaces' as the user-friendly name as the
  value
  displayed in column labeled 'Enterprise Name' in TEP display.
  One can declare whatever user-friendly name desired and it is
  what will
  appear as the value in TEP display; however altering the OID
  inside the
  curly braces will define a completely different SNMP trap
  enterprise OID
  and likely lead to a number of the trap Column displaying
  'Unavailable'.
  
  I managed to get MibUtility to generate the correct trapcnfg_*
  output,
  first by fooling MibUtility and in a separate, second case I
  corrected
  and updated the rfc233.mib ( the IF-MIB module ) that is stored
  in the
  MibUtility.jar file.
  
  In order for the SNMP objects that reside in SNMP Traps VarBind
  list to
  display user-friendly names in the TEP display of Value_List
  column, the
  interface objects ifIndex, ifAdminStatus and ifOperStatus must
  be
  defined in a SNMP metafile that is loaded by UA.   It appears
  that
  customer is already doing this per a SNMP metafile which they
  named
  nxinterfaces.mdl.
  
  Finally, even with the above content in the TRAPCNFG file there
  remains
  the need to open an APAR for UA's handling of the Generic Trap
  Number
  and Specific Trap Number associated to the various SNMP traps
  that
  belong to SNMP trap enterprise OID 1.3.6.1.6.3.1.1.5 .
  

Local fix

• No workaround available
  

Problem summary

• Universal Agent fails to correctly convert SNMPv2 standard traps
  to SNMPv1 standard traps, resulting in trap attribute 'Specific
  Trap' always displaying a value of '0' and numerous other trap
  attributes displaying value of 'Unavailable'.  SNMP standard
  traps include Specific Trap values 1, 2, 3, 4, 5 and 6 for
  standard traps coldStart, warmStart, linkDown,
  linkUp,authFailure and egpNeighborLoss, respectively.
  

Problem conclusion

• Conversion logic was corrected to assign accurate Specific Trap
  and Generic Trap values for SNMPv2 standard traps so that the
  standard traps are successfully found in Universal Agent's
  TRAPCNFG file.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
    | fix pack | 6.2.2-TIV-ITM-FP0004
  

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

• R622 PSY

     UP