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,
Post an idea
Upvote ideas and add comments to ideas that matter most to you
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.
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 ...
Support for multiple VIOS pairs in 1KSYS of VM Recovery Manager HA
Currently VM Recovery Manager HA supports only one VIOS pair per KSYS.In an environment where multiple VIOS pairs are exist on a single node, it is necessary to configure a separate KSYS for each VIOS pair.Therefore, please improve the function so...
Enable fc_mappings feature support in VMRM to be able to manage Migration between physical servers in Hostgroup which have multiple paths to disk
Everybody deploying VMRM can benefit from it.
In fact this is a product limitation for VMRM as the LPM SRR feature directly launched from HMC works properly while VMRM fails to manage this case.
This prevents VMRM form managing properly the autom...
Move the VLAN management from the host_group to the workgroup for more granular management. Away to have a backup of th
We have multiple VLANs in our PROD site, but a single VLAN in DR if the VLAN management was moved to the workgroup level it would be easier to manage the VLANs by creating a workgroup for each VLAN in PROD and mapping the VLAN for the workgroup to...
Let's take this scenario: we have two datacenters, each one has the same number of POWER servers managed by VMRM. We have two KSYS consoles - one in each datacenter. Basic idea is, when 1 DC acts as primary, while 2nd as standby. I'd like to have ...
Replace Bull Frewware RPMs with IBM Open Source repository RPMs for VM Recovery Manager
It would be much better for this product to use RPMs from IBM's own RPM repository, as managed by yum rather than using a third party RPM repo. Companies that standardize on using the RPMs from IBM's repo must uninstall them to utilize the RPMs fr...
A customer is hitting an issue that we have seen a few times with customers. Discover / verify operation fails with the following error when issuing an inquiry command:migmgr -f get_adapter -t vscsi -s U9080.M9S.21D5C47-V2-C418 -w 1385770584273256...
Case TS004589009:Before we move our LPARS into backup location using VMRM DR, we run 'ksysmgr verify' to make sure there will not be any issues during move. Although "verify" process reports success, real move fails on insufficient resources.
Do not place IBM confidential, company confidential, or personal information into any field.