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).
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Code enhancement to handle VIOS Path loss issues during Brocade haReboot - There have been multiple outages experienced in IBM VIO Server(VIOS) managed environment, during storage related events. The haReboot performed on Brocade SAN switches are supposed to be non-disruptive, but in reality they do take a finite amount of time. In VIO managed environments, this has sometimes resulted in impact and affected availability. During a haReboot the fabric services are not available and hence when the VIOS queries the Name server on the switch, it may not get the desired response due to the haReboot in progress. This results in the VIOS logging out and attempting to log back in again, resulting in path failures at the VIOS. To prevent the same from happening, the VIOS code can be updated to include an appropriate time interval that kicks in as and when the haReboot is in progress. The VIOS will then wait for this interval and pause any activity, before querying the name server again. The assumption is that the haReboot RSCN notification is sent correctly by the Brocade switches and received by the VIO servers. If not, then this can be worked out jointly by Brocade and IBM, to prevent outages in the future. The referenced Support Case has additional information.
among all the different vendor servers, the IBM VIOS managed AIX server environments seem to be susceptible and have experienced outages as and when haReboot is performed.
NFS based files as BackingDevices for vSCSI mapping
Allow files located on NFS shares mounted on the VIOs to be used as BackingDevice for vSCSI mapping (similar to VMware data store). Until now file based BackingDevices are only possible using StoragePools or ISOs.
almost 4 years ago
in PowerVM VIOS
Not under consideration
When using SSP deployment, Tiers can be created as Thin provisioned thus consuming LUN space that is used in the assigned LPARs.By time data in the LUs is written and subsequently erased, causing the LUs (and their containing tiers) to inflate.The...
VIOS storage mirror testing over distant datacenters
To increase the rubustness of the VIOS, it is highly appreciated to also do testing for storage mirroring over distant datacenters.The requesting client has an environment of about 5.000 vscsi disks from two datacenters with a distance of 5 miles....
Change padmin group to non-zero We have manually set many of our VIOS instances to 1 staff without any issues. However this is non-standard and not supported by IBM. Need a supported option from IBM. RFQ system doesn't allow Salesforce cases. TS00...
Retry FDISC to re-establish a NPIV connection at a user settable time frame
In a virtualized environment with NPIV certain fabric changes (such as firmware updates) may require the need to re-establish a NPIV connection using a FDISC. This FDISC is being retried. If this is not successful the NPIV client is giving up, and...
Hi IBM, Would you be able to add a flag/option to the updateios command to suppress the 'Continue bos.rte.install installation [y|n]?' and other similar prompts?
almost 6 years ago
in PowerVM VIOS
Not under consideration
Do not place IBM confidential, company confidential, or personal information into any field.