IV24439: SSM 4.0 ON A SOLARIS LOCAL ZONE HAS THE UPTIME FROM THE GLOBAL ZONE IN HRSYSTEMUPTIME

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 on a Solaris Local zone has the uptime from the
  global zone in hrSystemUptime
  
  DETAILS: :   SSM hrSystemUptime in local zones on Solaris does
  not use the uptime from the local system but rather gets the
  uptime from the global zone.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users monitoring non-global zones on Solaris.                *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The SSM was getting the boot time for the server from kstat. *
  * This only showed the boot time for the global zone and not   *
  * the zone that was currently being monitored.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to SSM 4.0.1 or SSM 4.0 FP14                         *
  ****************************************************************
  

Problem conclusion

• Changed where we get our boot time form, previously we obtained
  the value from kstat. If we get it from utmpx then we get the
  zone specific value.
  
  The fix for this APAR is contained in the SSM 4.0.1 release.
  The fix for this APAR is contained in the following maintenance
  packages:
      | fix pack | 4.0.0-TIV-SSM-FP0014
  

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