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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace PowerVC
Created by Guest
Created on Sep 25, 2019

Pvcauth via the Novalink partition

Proxy pvcauth via the Novalink partition to PowerVC. In the same nature RMC communication currently works with Novalink.

Idea priority Low
  • Guest
    Dec 9, 2020

    Thank you for your suggestion - we will consider this for a future release.

  • Guest
    Oct 3, 2019

    I think I may not have been clear with my request. I am not implying performing pvcauth via the RMC port, that would definitely not work. I was suggesting performing all the pvcauth and rest functions via the usual ports but using the TCP6 locallink interface between the client VM and the Novalink partition instead. Then Novalink will proxy this communication back to PowerVC via the management network. This is currently how RMC communication works when using NovaLink (hence the comparison).

    Currently if you install Novalink sshd listens on all interfaces by default and you can actually ssh to the Novalink partition via the TCP6 locallink interface (really bad default security by the way). So perhaps create a daemon to listen on the pvcauth and rest ports and listen on the Novalink TCP6 locallink interface and subsequently forward it to PowerVC via the TCP4 management network.