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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
According to the recent flash " IBM Storage Scale: An expired cluster key prevents nodes from connecting to the Storage Scale cluster resulting in admin commands failing to update the cluster configuration.https://www.ibm.com/support/pages/node/7145023 (Note: Internal reference D.326872)" when the cluster key expires, it can cause outages to local and remote cluster.
In order to prevent it to happen, new keys needs to be created. However, the administrators will forget to check it or don't know the issue until it happens.
The suggestion is to create a monitoring and events to prevent the cluster to reach the expiration of cluster key, and help client to take actions in advance.
So Scale should monitor the cluster key certificate time to time and issue events on mmhealth and GUI.
The procedure would be :
Once a week, check the committed cluster key certificate valid date:
/usr/lpp/mmfs/bin/mmgskkm print --cert id_rsa_committed.cert | grep Valid
If current date is 91 days greater than expiration day, do nothing
If current date is from 60 - 90 days to expiration day, issue a TIP event
If current date is from 30 - 59 days to expiration day, issue a DEGRADED/WARNING event
If current date is from 0 - 29 days to expiration day, issue a ERROR event
Create a Direct Maintenance Procedure pointing to the https://www.ibm.com/support/pages/node/7145023 to guide administrators on how to renew the cluster key certificate
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.