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.

Status Future consideration
Created by Guest
Created on Mar 16, 2021

Better support for RMC and Novalink

Currently, firmware updates rely on an RMC connection between the HMC and the individual AIX/Linux partitions. Also, Cloud Management Console relies on an RMC connection to the individual partitions to obtain some of its data.

We would like Novalink to be integrated to the environment in a better way, allowing to update POWER systems' firmware when there is only an RMC connection between the partitions and the managing Novalink partition; when updates are performed, the last step of updating partition firmware (PFW) could be initiated by the HMC, at which point Novalink could send a message through RMC to the partitions to perform the necessary actions.

We think requiring an RMC connection between the HMC(s) and all partitions is overkill, in particular since for day to day activities (including remote restart, dynamic LPAR operations and Live Partition Mobility) a connection between partition and Novalink is sufficient. This also allows for better security in multi-tenant environments and better scalability.

The current requirement makes concurrent firmware updates impossible (since we use Novalink and only Novalink has the RMC connection) which is bad for shared operations, requiring us to vacate a machine in order to update it, while we used to be able to do this concurrently.

Idea priority High