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 Future consideration
Created by Guest
Created on May 10, 2023

Unique identifier for virtualized Spectrum Virtualize products to allow better integration with VMWare

VMWare users who are virtualizing multiple different models of Spectrum Virtualize controllers behind SVC have no way of differentiating these at the VMWare as they are all presented of type "2145" or "SVC". This means that different round-robin policies that are recommended by IBM for different storage systems cannot be easily applied.


The redbooks advise this to be done using a claim rule but that would end up applying to all models and may not be what is required.


The request is that the claim rule can be written based on the full MTM of the system or the GUID of the storage device.


The policy can be updated manually for each volume individually but that relies on a manual step and for systems with 100s of hosts and 100s of volumes this leads to additional workload and possibility of error.

Idea priority Medium
  • Guest
    Reply
    |
    May 10, 2023

    This is especially valid for new Arrays which should be set to SSD within Vmware, this task cannot be performed on any volume which is already attache to ESXi and therefore should be set as part of a claims rule.

    Using the 2145 in your claims rule will tell vmware that all SVC based systems are in fact flash based and this will lead to performance degradation on the older non flash arrays.