Skip to Main Content
IBM Power Ideas Portal


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 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

FILTER BY CATEGORY

PowerVM VIOS

Showing 76 of 3631

powerVM SSP check ability to resolve all nodes before expell them

When a new node is added to a PowerVM_SSP cluster, all other nodes receive this information. But if this new node is not able to be resolved, existing nodes are expelled from the cluster.
over 1 year ago in PowerVM VIOS 0 Future consideration

Warning when reach the 16 nodes limit in SSP cluster

There is a limit of 16 nodes in a SSP cluster, but you can add a 17th without any warning message. I think it would be better to be informed.
over 1 year ago in PowerVM VIOS 0 Future consideration

VIOS Maintenance Mode

The new VIOS Maintenance Mode should address the following requirements:1. Possibility to set the VIOS in maintenance mode with one click (for example through the HMC UI)2. Automatic failover of all SEA to backup VIOS (chdev -dev entX -attr ha_mod...
about 7 years ago in PowerVM VIOS 1 Planned for future release

Updating the viosbr utility

would it be possible to add the force option of the mkvdev command in the viosbr? mkvdev -f in viosbr
over 1 year ago in PowerVM VIOS 1 Future consideration

Support for Trusted Execution in VIOS

Many IT organizations require antivirus or similar protections, such as File Integrity Monitoring, on critical infrastructure as a matter of routine Security and Compliance policy. In the AIX space, IBM's recommended solution (as stated many times...
7 months ago in PowerVM VIOS 0 Future consideration

VIOS no-prompt updateios

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 5 years ago in PowerVM VIOS 1 Future consideration

VIOS syslog configuration for splunk

We will move into Service Now as a replacement from existing solution. Splunk is used by the Service Now solution. To create incidents for VIOs I need syslog data sent to splunk.
about 1 year ago in PowerVM VIOS 0 Future consideration

IBM i handle disk timeout error during VIOS outage and dump

IBM i to the disk I/O time out error recovery processing when a VIOS partition is unresponsive allowing faster fail over to another available path.'
about 2 years ago in PowerVM VIOS 4 Future consideration

VIO device naming convention after LPM (vfchostX)

See case TS002260514:LPM/HMC does mess up the AIX device names on target VIOS.Especially if using the "vios-virtual-slot-number" on the target VIOSs i would assume the device naming is the same on both. But it is not as we know.
over 3 years ago in PowerVM VIOS 0 Future consideration

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.
7 months ago in PowerVM VIOS 1 Not under consideration