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 Future consideration
Created by Guest
Created on Dec 9, 2022

Session recovery via query

CSM is currently designed to stop monitoring underlying replication in an event where certain types of communication failures occur with a subsystem (say after panic/warmstart). It's designed this way to not inadvertently monitor relationships that weren't intentional. Thus, this leaves a Session in a state of failure when these communication errors occur. The recovery routine is quite simple, issue a START or STARTGC command to resume monitoring of the replication; however, this poses certain operational risks in the environment as we perform region switch's with some regularity which changes the expected state of a relationship (i.e. it could be PPRC synchronous or PPRC-XD depending on which region we are operating in). It would be helpful to have a new function that would give us the ability to 'recover status' as our first step in a recovery routine, rather than relying on environmental knowledge. 

Idea priority Low
  • Guest
    Dec 21, 2022

    I believe the issue is that CSM loses communication with the Storage side and CSM marks the GM session as severe (copysets go Defiened in CSM only), however the GM session on the Storage side is still working and in Normal state. When communication is restored between CSM and the Storage hardware, the GM session still remains severe, even thou it is running correctly on the Storage.

    Since CSM marked the session severe, to would be a good idea to have an option in CSM to "resync" the GM session to match the correct state reported on the Storage hardware, prior to the loss of communication.

  • Guest
    Dec 13, 2022
    The issue I think you're talking about is when the hardware query from CSM results in CSM marking the pair as Defined. In this state the only thing that will mark the pair as active again is a start command. The hw however should never return Defined for the pair if the pair is actually active. So that issue really needs to be addressed by the hardware side.

    With that said, we do have a discover command now for FC relationships. We could consider doing the same for remote copy relationships now as well.