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 Sep 30, 2022

Retain CSM level after HMC Kernel update

When CSM is upgraded outside of a Remote Code Load (RCL) using the stand alone DSCLI and an RCL occurs afterwards where the HMC kernel is updated, CSM is back-leveled to the version that is included in the microcode bundle.

This forces the User/Administration to re-install CSM to the level it was BEFORE the microcode upgrade.

Idea priority High
  • Admin
    Randy Blea
    Reply
    |
    Oct 5, 2022

    Please re-read the comment on the reason why CSM moved this to a not under consideration state. This IDEA needs to be open on the DS8000 side. CSM has zero control over how the HMC is rebuilt, nor how data is stored on the HMC in order to allow the rebuild. We backup our contents so that they can be used on the rebuild, but we cannot backup the installer level. So, while I agree with the IDEA, we cannot implement anything on the CSM side to resolve the issue.

    I have personally argued this point multiple times to the DS8000 team. So I can assure you this is not a case of CSM not caring abot users who run CSM on the HMC. Perhaps by opening the IDEA against DS8000 with all the votes, it will drive a solution and a priority.

    As for not running on the HMC. While this situation does cause extra steps, it is not a reason to run only on standalone. There are a lot of benefits to various customers for running CSM on the HMC. A lot of these benefits may outweigh the reason for this request.

  • Guest
    Reply
    |
    Oct 5, 2022

    "Not under consideration" Is complete BS. I will be making it a priority to encourage, at every opportunity, that CSM should be run standalone, as CSM development does not care about users who run CSM on HMC. This behavior, and CSM development's response, are 100% unaccceptable.

  • Guest
    Reply
    |
    Oct 3, 2022
    CSM requested this functionality when installing on the DS8000, however, we were told the DS8000 has limited space in which it can store information that is needed to rebuild the system on an HMC rebuild, etc. They can store off a backup of the CSM data, but cannot store the full installer that was uploaded to perform the manual upgrade. Thus the rebuild process only has access to the installer that is part of the bundle itself.

    I have to reject this IDEA from a CSM standpoint, as there is nothing that we can do from the CSM side to support this request. I encourage you though to open this from the DS8000 side and see if they can find a way to store the upgrade installer so that it can be restored to the correct version.
  • Guest
    Reply
    |
    Oct 2, 2022

    This issue really makes IBM look like fools.