IBM Support

IT00103: SYSTEM MONITORING SHARED SERVICE STUCK AT "STARTING VIRTUAL MACHINES"

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In some cases, deploying the System monitoring shared service
    never completes, and the virtual machines are not pingable from
    the worlkoad console.  If you log in to the virtual machine,
    en0 is not assigned an IPv6 address.
    

Local fix

Problem summary

  • This occurs if the management IPv6 address is not assigned
    during deployment. As a result the PureApplication System
    cannot contact it to verify it has completed its
    initialization. This can happen if an FSM inventory process
    does not run as expected.
    

Problem conclusion

  • Code added to force FSM inventory if needed.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT00103

  • Reported component name

    PUREAPP SYS W17

  • Reported component ID

    5725F4600

  • Reported release

    110

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-11-15

  • Closed date

    2013-11-19

  • Last modified date

    2013-11-19

  • 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

    PUREAPP SYS W17

  • Fixed component ID

    5725F4600

Applicable component levels

  • R110 PSY

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSM8NY","label":"PureApplication System"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"110"}]

Document Information

Modified date:
24 September 2021