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 Delivered
Created by Guest
Created on Apr 2, 2024

CSM Primary to automatically reconnect to the standby server after the standby CSM task is recycled or vice/versa Standby reconnects automatically to Primary

Every time one of our CSM started tasks is recycled or if an lpar is IPL'd when the CSM started task comes back up it does NOT reconnect to either the standby or the primray (depending on which CSM task that was shutdow/restarted.

The ability of the surviving CSM to have redundancy is impacted by this.

It is never an acceptable feature/function for the reconnection to have to be manually initiated.

Please supply this functionality.




Idea priority Urgent
  • Guest
    Jun 28, 2024
    Delivered in the CSM 6.3.11 release
  • Guest
    Apr 2, 2024
    The reason we do not automatically reconnect today is because we cannot tell whether the disaster is due to an issue that may have "corrupted" the active server. If we reconnect automatically...we would then corrupt the standby server as well and leave you without a valid configuration. I'll make this an uncommitted candidate...but the solution is not as simple as reconnecting automatically. This is similar to how Replication works for DR environments. We don't auto restart replication because it could corrupt the target site.