IZ18931: srProcessorTable percentages become incorrect after 497 days of uptime on Linux.

IBM Tivoli 4.0.0-TIV-SSM-FP0010
IBM Tivoli 4.0.0-TIV-SSM-FP0011
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 12 README 4.0.0-TIV-SSM-FP0012
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 13 README 4.0.0-TIV-SSM-FP0013
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 14 README 4.0.0-TIV-SSM-FP0014
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 1 README 4.0.0.14-TIV-SSM-IF0001
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 2 README 4.0.0.14-TIV-SSM-IF0002
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 3 README 4.0.0.14-TIV-SSM-IF0003
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 4 README 4.0.0.14-TIV-SSM-IF0004
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 5 README 4.0.0.14-TIV-SSM-IF0005
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 6 README 4.0.0.14-TIV-SSM-IF0006
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 7 README 4.0.0.14-TIV-SSM-IF0007
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 8 README 4.0.0.14-TIV-SSM-IF0008
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 1 README 4.0.0.15-TIV-SSM-IF0001

APAR status

• Closed as program error.

Error description

• SSM notice that a server is busy after it worked fine for 492
  days.
  srResources of srProcessorTable was shown the idle percent as 1
  when srSystem CPUUsage is 0.
  
  The following data received from the Net SNMP command
  # snmpwalk -c public -v 2c -M /opt/netcool/ssm/mibs -m ALL
  172.18.66.29 srProcessorTable
  SYSRES-MIB::srProcessorIdlePercent.1 = INTEGER: 1
  SYSRES-MIB::srProcessorIdlePercent.2 = INTEGER: 1
  # snmpwalk -c public -v 2c -M /opt/netcool/ssm/mibs -m ALL
  172.18.66.29 srSystem
  SYSRES-MIB::srSystemCPUUsage.0 = INTEGER: 0
  
  If you see in the above results that Processor Idle percent is
  1, but System CPU usage is 0.
  
  There is a customer data for system uptime as well. Here it is:
  ----------------------------------------------------------------
  ----------------------------------------------
  SYSRES-MIB::srProcessorIdle.1 = Timeticks: (4294967295) 497
  days, 2:27:
  52.95
  SYSRES-MIB::srProcessorIdle.2 = Timeticks: (4294967295) 497
  days, 2:27:
  52.95
  ----------------------------------------------------------------
  ---------------------------------------------
  
  However the problem seem to be working fine after customer
  restarted the system. But he is concerned about what could have
  caused this issue. Is it due to the fact that , sysuptime
  reaches 492 days, this problem will occur
  

Local fix

• no work around
  

Problem summary

• An integer overflow occurred when monitoring CPU information.
  

Problem conclusion

• Maintain CPU data internally as 64 bit values.
  
  The fix for this APAR is contained in the following maintenance
  packages:
     | fix pack | 4.0.0-TIV-SSM-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

  NETCOOL SYS SVC

• Fixed component ID

  5724P4300

Applicable component levels

• R400 PSY

     UP