CA Vantage

Expand all | Collapse all

CA Vantage: refresh SMI-S object collecting manually?

  • 1.  CA Vantage: refresh SMI-S object collecting manually?

    Posted 11-16-2018 03:06 AM

    Hello, 

    is there a possibility to start the SMI-S Object Collection scans manually with a corresponding operator command? 

    Or can this only be achieved by reducing the scan intervals? 

     

    Thanks!

    Best regards,

    Andi



  • 2.  Re: CA Vantage: refresh SMI-S object collecting manually?

    Posted 11-19-2018 06:03 AM

    Hi Andi,

     

    please try "F SAMS,REFRESH,CIMSUPP". This should rebuild all objects that are managed by the CIMMNGR task and should start a new collection confirmed by message

     

    VAN0884I SMI-S Object Collection Starting

     

    Best regards

    Achim



  • 3.  Re: CA Vantage: refresh SMI-S object collecting manually?

    Posted 11-21-2018 09:37 AM

    Hello Achim,

     

    thank you very much, it work's!

    Unfortunately in the CA Vantage Windows Client under "RAID Devices - CIM Provider List", i get an ERROR in Column Status and can't find any indication what's leading to the error.

     

    Best regards,

    Andi



  • 4.  Re: CA Vantage: refresh SMI-S object collecting manually?

    Posted 11-21-2018 09:58 AM

    Hi Andi,

    glad it works. As for the ERROR status the help for the Object says:

     

    >
    CIM Provider List

    Status
    This identifies the "last known status" of each CIM
    Provider. A status of UNKNOWN indicates that
    CA Vantage has not tried to access the Provider since
    the last time the CIMLIST structure was built. A status
    of ERROR indicates that the last attempt to access the
    CIM Provider failed, while a status of NORMAL indicates
    that the last access to the Provider was successful.
    A value of ACTIVE indicates that CA Vantage
    is currently accessing the Provider.

    <

     

    In order to find out the cause of the ERROR status, I suggest you open a Support Case in Support Online.
    May be there is any related message in JESMSGLG or in the MSGE log that gives a clue.

     

    Best regards
    Achim