This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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.
At this time, we are choosing not to invest in the suggestion you are making. The specific incident you mention is a real problem, but hopefully that defect has been addressed with the vendor and not something that should happen again. We are currently (and constantly) evaluating improvements to our error detection and recovery and will continue to monitor if this becomes more of a trend verses one time issue.
The CAAC has reviewed this requirement and recommends that IBM view this as a high priority requirement that is important to be addressed. As more folks move to external storage, they need to be able to trust the OS to identify and handle errors appropriately.
Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.
For more information about CAAC, see www.common.org/caac
For more details about CAAC's role with RFEs, see http://www.ibmsystemsmag.com/Blogs/i-Can/May-2017/COMMON-Americas-Advisory-Council-%28CAAC%29-and-RFEs/
Nancy Uthke-Schmucki - CAAC Program Manager
Under Consideration
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Storage
Operating system - IBM i
Source - None
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Core OS
Operating system - IBM i
Source - None
IBM has modified some of the information in this request. Please contact us if you have any questions.
IBM has modified some of the information in this request. Please contact us if you have any questions.
IBM has modified some of the information in this request. Please contact us if you have any questions.
In particular, RFEs are required to be in English so that a majority in the Community can read and vote on them. The Headline, Description, and Use Case have been translated to English. Do add a Comment if there is an improvement for the machine translation to English:
Original Headline:
Mejora de resilencia del sistema operativo IBM i
Original Description:
Solicitamos mejora en el diseño de la resilencia del IBMi que actualmente utilizamos en el banco banbif; esto debido a los constantes incidentes de degradación que hemos tenido en el tiempo;
el cual fué originado por gbics defectuosos con baja potencia (error fábrica de los gbics en los switch brocade).
Original Use Case:
Actualmente se tiene 4 vías de acceso a los discos (2 de redundancia) y lo que hace el diseño al encontrar gbics con baja potencia es seguir intentando el acceso debido a que no lo ve como
error; por tanto sigue intentando y genera degradación en el sistema; por lo cual sugerimos mejorar este diseño y ver la forma de que reconozca dicho error de baja potencia y el sistema
utilice las demás vías de acceso (cerrando esta defectuosa hasta que se realice cambio gbic). La idea es tener un sistema resilente para este tipo de escenarios.