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.

Add a new idea Subscribe
Status Future consideration
Workspace AIX
Created by Guest
Created on Dec 20, 2019

RELATED IDEAS

RMC connection through NAT firewall

In an MSP environment there are multiple customers on one system with multiple VLANs. The VLANs are all behind a NAT firewall. From a management point of view, an LPAR should talk to the HMC over RMC through that NAT firewall.

The issue in that environment is where the RMC send's back the contact IP to the HMC. It sends the real IP address and not the NAT IP address, the HMC and the network it resides in have no knowledge of how to communicate with this IP address.

The solution would be, that it should be possible for RMC on the LPAR to request for the HMC to establish a new connection by the LPAR hostname (short name not the FQDN).

Idea priority High
  • Guest
    Reply
    |     Jun 10, 2020

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM AIX
    Component - Product functionality
    Operating system - IBM AIX
    Source - Client

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - Power Hardware Management Console
    Component - Product functionality
    Operating system - Other
    Source - Client

  • Guest
    Reply
    |     Jan 22, 2020

    This RFE is the same as another RFE 177181 (Enhance RSCT code base to allow for daemon communication via SNAT/NAT)

  • Guest
    Reply
    |     Jan 9, 2020

    If it is easier to implement, it would be sufficient, if the HMC additionally tries the client's source IP address from the IP protocol header for communication.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.