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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Apr 22, 2021

Provide meaningfull names for volumes created by HyperSwap volume pair allocation by CLI and GUI

When allocating an HyperSwap volume pair, the client input naming the HyperSwap volume (let's assume it is new_HS_volume) is only used to name the Master copy of the quadruplet created by the allocation dialogue. The 3 other volumes (Auxiliary, Master_Change and Auxiliary_Change instances) are named by the system as vdiskxx where xx is a sequence number.
The RFE proposed to use meaningful names for the 4 volumes created by the dialogue instead. This could be new_HS_volume_Master, new_HS_volume_Aux, new_HS_volume_Master_Change and, new_HS_volume_Aux_Change.
This enhancement would 1) avoid in many cases clients to use CLI to attribute meaningful names for the 3 volumes and 2) improve user experience when restarting in a quorum override sequence where correspondences between servers and volumes is not really possible when solely using vdiskxx names
The enhancement should be implemented at CLI level and it would benefit to the GUI dialogue using it.

Idea priority Medium