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.

Status Future consideration
Created by Guest
Created on Nov 12, 2021

VMRM Discover/Verify - VM_CONFIG_COLLECTION_FAILURE for one LPar must not impact others

We've VMRM 'HA' cluster among 2 Hosts. I had 5 VMs as 'managed', then i ran a Hostgroup discover + verify. Due to a HW failure the 'discover' failed for 2 VMs with event VM_CONFIG_COLLECTION_FAILURE, but was successful for the other 3 VMs. At the end of the discover + verify however all 5 VMs were in READY state.
My desire would be to have the VMs not affected by the HW failure in READY_TO_MOVE state instead, so that i can avoid having to 'unmanage' the 2 VMs affected by the HW issue and then re-run discover + verify to have the 3 VMs in READY_TO_MOVE.
All details in Case TS007342720

Idea priority Medium
  • Guest
    Jul 4, 2022
    Once after discovery is success, then it moves to verification. Verification moves LPARs state into READY_TO_MOVE.
    But since the discovery itself failed, it is not moving to verification process.
    It is critical to pass discovery process, since HA cluster at VIOS level creation and trunk, client adapter creations happen automatically.