Skip to Main Content
IBM System Storage Ideas Portal

This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Is a defect
Created by Guest
Created on Nov 4, 2022

Refresh States function should function when devices are in severe status

During a recent issue where CSM lost access to the underlying DASD (due to a warmstart), it marked some of the replicated devices in a Severe state. That state never changed, even after issuing a 'Refresh States' command. You can submit a START or STARTGC to correct this issue, but I would like to see the refresh states function work instead.

Idea priority Medium
  • Guest
    Nov 4, 2022
    This sounds like a defect vs. an RFE. The only time CSM won't "refresh" the state based off the hardware state, should be if the pairs are in a Defined state. I know there's a known issue where the DS8000 queries may return to CSM that the pairs no longer exist, which causes the pairs to go Defined which has been seen during warm starts. If this is what you hit that needs to be pursued as a defect against the DS8000 ESSNI component.

    CSM does not change pairs from Defined to active. This is because we do not want to accidentally assimilate reltionships without explicit action by a customer. As the refresh states runs the same code as a normal state check, this could lead to issues in scenarios where customers have a CSM session setup but do not want it managing the hw yet or at all. This is why we require and explicit start command. The start command shouldn't cause a full copy of the data, but it officially tells CSM that you wish to manage those pairs and thus allows the assimilation.