IBM Support

IT41389: SET LAST SUCCESSFUL PROBE TIME EVEN WHEN PROBE HAS A WARNING STATUS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When viewing the Resources views within Storage Insights, the
    ?Last Successful Probe? column is being populated only when
    probe has a SUCCESS status.
    When the probe column has a WARNING status, most of the capacity
    data is being persisted. The problems are with the relationship
    data which is not persisted.
    The outdated timestamp gives the user the impression that probes
    have been completely failing, when for the most part they?ve
    been successful.
    ____________________________________________________
    The defect is against component: 5608TPCSI
    Server/Manager build/release: 5.4.x
    Problem as described by customer: Storage Insights shows
    degraded DS8K probes and some failures.
    Initial customer impact (low/med/high): med
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IBM Storage Insights users viewing the Last Successful Probe *
    * information                                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When viewing the Resources views within Storage Insights,    *
    * the "Last Successful Probe" column is being populated only   *
    * when probe has a SUCCESS status.                             *
    *                                                              *
    * When the probe column has a WARNING status, most of the      *
    * capacity data is being persisted. The problems are with the  *
    * relationship data which is not persisted.                    *
    *                                                              *
    * The outdated timestamp gives the user the impression that    *
    * probes have been completely failing, when for the most part  *
    * they have been successful.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is targeted for the following release:
    
    IBM Storage Insights 3Q22   [ 54X-IBM-SI ]
    ( release target 3Q 2022 / July )
    
    The target dates for future releases do not represent a formal
    commitment by IBM. The dates are subject to change without
    notice.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT41389

  • Reported component name

    STORAGE INSIGHT

  • Reported component ID

    5608TPCSI

  • Reported release

    54X

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-06-29

  • Closed date

    2022-07-06

  • Last modified date

    2022-09-08

  • 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

    STORAGE INSIGHT

  • Fixed component ID

    5608TPCSI

Applicable component levels

[{"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSYS7R","label":"IBM Spectrum Control Storage Insights"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"54X"}]

Document Information

Modified date:
08 September 2022