IJ03810: SNMP BOOT TIME IS SYSUPTIME AND NOT CONSISTANT WITH NON-SNMP BOOT TIME FIELD

APAR status

• Closed as program error.

Error description

• In TADDM 7.3.0.4 code has been modified to use  OID
  1.3.6.1.2.1.1.3 for sysUpTime to collect boot time for SNMP
  devices. This time is represented in milliseconds in the TADDM
  UI, whereas non-SNMP sensors show a UTC date/time stamp.
  In this APAR two changes will be made;
  1. Boottime field would be renamed as Estimated Boot time
  2. The boot time for snmp devices will be calculated based on
  TADDM discovery server time minus uptime and be stored in epoch
  time format and shown in the UI as UTC date/time the same as
  non-snmp computer system CIs. Also, rollover scenario shall be
  considered while computing the estimated boot time.
  Note that the date/time may not accurately reflect the boot time
  in the targets time zone, this is due to snmp not providing
  current target system time, hence we will use TADDM discovery
  server time for the calculation.
  3. For devices supporting alternate non-wrapping OID for boot
  time, calculate boot time using that OID and for other devices
  calculate boot time using sysuptime.
  4. In a future fix pack, the sysUpTime column will be added to
  the TADDM schema and we will populate the millisecond value of
  sysUpTime there.
  

Local fix

• Subtract the sysuptime millisecond value from the target server
  discovery time to get the time of last boot.
  

Problem summary

• In TADDM 7.3.0.4 code has been modified to use OID
  1.3.6.1.2.1.1.3 for sysUpTime to collect boot time for SNMP
  devices. This time is represented in milliseconds in the TADDM
  UI, whereas non-SNMP sensors show a UTC date/time stamp.
  In this APAR the following changes will be made:
  1. Boottime field would be renamed as Estimated Boot time
  2. The boot time for snmp devices will be calculated based on
  TADDM discovery server time minus uptime and be stored in epoch
  time format and shown in the UI as UTC date/time the same as
  non-snmp computer system CIs. Also, rollover scenario shall be
  considered while computing the estimated boot time.
  Note that the date/time may not accurately reflect the boot time
  in the targets time zone, this is due to snmp not providing
  current target system time, hence we will use TADDM discovery
  server time for the calculation.
  3. For devices supporting alternate non-wrapping OID for boot
  time, calculate boot time using that OID and for other devices
  calculate boot time using sysuptime.
  

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