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
VMRM - make hardcoded timeout interval tunable parameter.
Based on communication with support team dealing with case TS011408072 we would like to rise this idea. In a VMRM 'HA' Cluster, after a failover, there's a hard coded 5 minute timeout for AIX VMs to IPL and start again heartbeating with the VIOSes...
Ford has switched to Pure Storage and would like to automate DR such that during a disaster, VMRM would be able to automatically change the replication and mounts such that Ford can failover to DR automatically.
When Critical, Warning and Maintenance counts are displayed, the event details can be displayed by hovering the mouse over them. With an event for each count, the dashboard will be more useful. All counts should have a corresponding hover detail.
Possibility to 'quiesce' (or 'unmanage') entire VMRM cluster during SW upgrades
Under 'Description' write the details of your new idea: On a 'HA' cluster with 2 Hosts we had to upgrade the HMCs from v9 to v10, during the upgrade the KSYS logged the event HMC_UNREACHABLE even though it's expected that the HMC may not be Fully ...
ksysmgr - do not suggest running discover on empty workgroup
When the last VM is removed from a workgroup, ksysmgr should not suggest running a "discovery to apply changes" (should say "discover" as there is no "discovery" process) against the empty workgroup because it is not needed and the resulting retur...
Do not place IBM confidential, company confidential, or personal information into any field.