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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
In PowerVC environments that utilize IBM Cloud Management Console (CMC) for Power Enterprise Pools (PEP), it's common for managed systems to be co-managed by HMC and PowerVM NovaLink. PowerVM NovaLink is in controller mode to facilitate operations on the managed system via PowerVC and HMC is in co-management mode to allow the CMC to report usage information for Power Enterprise Pools.
Power Enterprise Pools and HMC - https://www.ibm.com/docs/en/power10?topic=pool-using-power-enterprise-pools
PowerVM NovaLink and HMC co-management - https://www.ibm.com/docs/en/power10/9105-42A?topic=environment-powervm-novalink#p10eig_kickoff__title__4
Virtual Machines and NovaLink on a Managed System
Virtual Machines deployed by PowerVC on the managed system establish an RMC connection to PowerVM NovaLink via the dedicated internal virtual network between the Virtual Machine and NovaLink. Most importantly, the Virtual Machine deployed by PowerVC typically does not have access to the HMC, especially in multi-tenant PowerVC environments where the HMC is solely used for hardware management and CMC reporting.
PowerVM NovaLink RMC - https://www.ibm.com/docs/en/power10/9105-42A?topic=novalink-resource-monitoring-control-rmc-powervm
Managed System with NovaLink and HMC Co-Management
In this type of environment, the HMC and PowerVM Novalink must coordinate for co-management mode of the managed system which results in a shared RSTC domain between HMC and NovaLink. This shared domain causes the HMC to be propagated to PowerVM NovaLink managed Virtual Machines even though these Virtual Machines cannot reach the HMC.
Prevent HMC Information from being propagated to Virtual Machine
This idea proposes an RSCT configuration flag that allows a PowerVM NovaLink operator to filter any domain peers from being propagated to the PowerVM NovaLink managed Virtual Machine via RMC. PowerVC managed Virtual Machines should only ever establish an RMC connection with PowerVM NovaLink.
Idea priority | Medium |
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.
Notes to this idea are in Case TS014790269 -