IZ45673: SSM 4.0 service starts too early on Solaris 10, causing Veritas Volume Manager to hang

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 fixed if next.

Error description

• SSM 4.0 service starts too early on Solaris 10, causing Veritas
  Volume Manager to hang
  
  When server boots it takes very long time and finally hangs
  because the SSM agent is running.
  
  Agent: SSM 4 FP6
  

Local fix

• Workaround:
  1. Disable the ssmagent service (application/ssmagent); or
  2. (May also work) Set HostresProbeDisks=off in config/init.cfg
  
  
  Manual fix:
  <dependency
  name='fs-local'
  grouping='require_all'
  restart_on='none'
  type='service'>
  <service_fmri value='svc:/system/filesystem/local' />
  </dependency
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of the SSM on solaris 10 and later. Where the SSM is not
  installed on the same local partition that the system boots
  from.
  ****************************************************************
  PROBLEM DESCRIPTION:
  It is possible for the SSM service on Solaris 10 systems to not
  be able to start as the installation location has not been
  mounted when the service manager tries to start the SSM. This
  can cause problems with the system boot up sequence.
  ****************************************************************
  RECOMMENDATION:
  We recommend that a dependency on the local file system be added
  to the SSM service configuration like so:
  
  1) Open config/ssmagent.xml in a text editor.
  2) Navigate to the line containing <single_instance />
  3) After that line insert the following:
     <dependency
      name='fs'
      type='service'
      grouping='require_all'
      restart_on='none'>
      <service_fmri value='svc:/system/filesystem/local' />
     </dependency>
  4) Save the file.
  5) Reset the service by running the following command:
     svccfg import ssmagent.xml
  6) Confirm the dependency exists by running the following
  command:
     svcs -l ssmagent
     There should be a local file system dependency.
  ****************************************************************
  

Problem conclusion

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

Applicable component levels

• R400 PSN

     UP