IBM System Storage Ideas Portal
Hide about this 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.

Add a new idea Subscribe
Status Not under consideration
Workspace IBM Spectrum Virtualize / FlashSystem
Created by Guest
Created on Oct 22, 2018

RELATED IDEAS

Need to shorten disruptive time when reconfiguring nodes

See this idea on ideas.ibm.com

System : IBM Storwize series
Actor : User needs to improve I/O wait time during Storwize microcode (SVC code) upgrading.

When concurrent SVC code upgrading on Storwize storage series, we need to "reconfigure" a node to the cluster after code update. Now it take closed 20 secs to 30 secs in this customer's environment and servers have to stop all I/O operation during that time. Yes, that may met the limitation of OS timeout, like as 30 secs in Windows, AIX and so on, but VMware ESX shows time-out errors when ESX detects no response from storage device over 14 secs. The customer as infrastructure service unit cannot accept the long waiting time over 14 secs. So disruptive time of Storwize SVC code upgrading should be shorter than 14 secs or less.

Idea priority High

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.

Contact IBM Privacy Terms of use Accessibility