IBM Support

IT49012: STORAGE INSIGHTS REPORTS DATA COLLECTION FAILED FOR MULTIPLE IBM SAN VOLUME CONTROLLER DEVICES DUE TO PROBE PROCESSING FAILURES.

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

  • Customers may observe multiple SAN Volume Controller devices
    with Data Collection status set to Failed. While the devices may
    still show a Last Successful Monitor, the Last Successful Probe
    is not updated.
    
    Despite the failed probe status, certain datasets such as
    capacity information may appear fully up to date, which can
    create confusion regarding the actual health of data collection.
    
    
    During server-side processing of probe data, the system detects
    multiple cluster files, which leads to processing failure. This
    occurs because the agentless server name contains the string
    cluster, causing the processing logic to incorrectly associate
    additional cluster files that are not related to the target SVC
    device.
    
    As a result, the processing workflow fails and Storage Insights
    is unable to generate processed probe results for the affected
    SAN Volume Controller devices. This leaves the devices with a
    failed data collection status and an outdated Last Successful
    Probe, even though partial data may still be visible.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IBM Storage Insights users monitoring storage system         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Customers may observe multiple SAN Volume Controller devices *
    * with Data Collection status set to Failed. While the devices *
    * may                                                          *
    * still show a Last Successful Monitor, the Last Successful    *
    * Probe                                                        *
    * is not updated.                                              *
    *                                                              *
    * Despite the failed probe status, certain datasets such as    *
    * capacity information may appear fully up to date, which can  *
    * create confusion regarding the actual health of data         *
    * collection.                                                  *
    *                                                              *
    *                                                              *
    * During server-side processing of probe data, the system      *
    * detects                                                      *
    * multiple cluster files, which leads to processing failure.   *
    * This                                                         *
    * occurs because the agentless server name contains the string *
    * cluster, causing the processing logic to incorrectly       *
    * associate                                                    *
    * additional cluster files that are not related to the target  *
    * SVC                                                          *
    * device.                                                      *
    *                                                              *
    * As a result, the processing workflow fails and Storage       *
    * Insights                                                     *
    * is unable to generate processed probe results for the        *
    * affected                                                     *
    * SAN Volume Controller devices. This leaves the devices with  *
    * a                                                            *
    * failed data collection status and an outdated Last           *
    * Successful                                                   *
    * Probe, even though partial data may still be visible.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is targeted for the following release:
    
    IBM Storage Insights 1Q26   [ 54X-IBM-SI ]
    ( release target 1Q 2026 / March )
    
    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

    IT49012

  • 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

    2026-01-29

  • Closed date

    2026-02-23

  • Last modified date

    2026-02-23

  • 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":"BU048","label":"IBM Software"},"Product":{"code":"SSQRB8","label":"IBM Storage Insights"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"54X","Line of Business":{"code":"LOB69","label":"Storage TPS"}}]

Document Information

Modified date:
24 February 2026