Skip to Main Content
IBM Power Ideas Portal

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:

Post your ideas

Start by posting ideas and requests to this portal to enhance a Power product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas and add comments to ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The Power teams will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.


Specific link you will want to bookmark for future use

IBM Unified Ideas Portal - https://ideas.ibm.com/ - Use this site to create or search for existing Ideas across all IBM products that are outside of Power, and track all of your personal interactions with all Ideas.

ADD A NEW IDEA

FILTER BY CATEGORY

PowerVM VIOS

Showing 73 of 3542

Remove the fixed, built-in password of user vpgadmin and reduce the blast radius of the vpgadmin user

The VIOS vpgadmin user has a known pre-defined password(1), that can't be changed(2). Although the user has login=false, and rlogin=false (3), it's a user that is part of the bin and system groups (4). One common request of many security policies ...
2 months ago in PowerVM VIOS 0 Submitted

Provide meaningful info with errpt id 32BB81EF and FBD8625E - UNKNOWN error against SEA

with VIO 3.1.3.21, errpt now shows entries with 32BB81EF and FBD8625E but the data is meaningless to the end user. Allegedly, this is an indication that the SEA has become "primary" again, according to IBM Support. But, errpt id E48A73A4 already t...
3 months ago in PowerVM VIOS 1 Planned for future release

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

updateios failure during window closure

You can reach out Deepak Menezes(deepakme@in.ibm.com) .This is with respect to issue we hit on case TS008403859Was installing Fix Pack 3.1.2.10 on top of his system 3.1.1.25 .During the installation the Putty session disconnected due to VPN discon...
6 months ago in PowerVM VIOS 0 Under review

Need boot support for VIOS to boot over iSCSI to SAN

Customer wants to have iSCSI boot from SAN using VIOS supported. During the Ericsson road map sessions, it was mentioned that IBM did some testing of this. Also, after the AIX, VIOS, and storage presentations, it was felt that it would not take de...
9 months ago in PowerVM VIOS 2 Future consideration

Support for NFS v4 mounts on virtual I/O server

The current mount command of the the ioscli interface does not support the option '-o vers=4'. NFSv4 is now the industrial standard for NFS. NFS is uses to store for example virtual I/O server system backups (mksysb) to a NIM server. Using the vir...
9 months ago in PowerVM VIOS 0 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.
10 months ago in PowerVM VIOS 0 Future consideration

viosecure -level high should set default firewall rules to denied for inbound traffic

IBM support case TS006803177:---------------------------------------After applying vioscure level 'high', the default firewall rule 0 permits all IP packages, if an IP package does not met any rules. This make the firewall settings useless if you ...
11 months ago in PowerVM VIOS 1 Future consideration

cfgmgr locks VIOS if called in separate processes at the same time

mkdev, mkiscsi, cfgmgr, rmdev, rmiscsi cause the odm to lock and subsequently the VIOS gets locked and needs to be rebooted to recover. We run these commands when an LPAR is started/stopped and they could happen at the same time. This causing the ...
about 1 year ago in PowerVM VIOS 1 Is a defect