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 Submitted
Created by Guest
Created on Aug 25, 2023

BMC inband local ID. User needs locked down

For 7063-CR2 HMCs, there requires a HMC-to-BMC Inband Communications Credentials to allow for periodic monitoring of hardware problem events and other management console functions .This is local user. By default, root account is used for this purpose, and when setting up a CR2, the user is required to change the root BMC password, so this communication doesn’t work out of the box. But as suggested by IBM , we use different id instead of root for the inband communication requirement. The reason not to use root is the HMC will try every 20 minutes to log into OpenBMC and would cause the account to be locked out if the password is changed on the BMC and not updated on the HMC software.

This ‘local’ user ID for inband communication can also access OpenBMC GUI hence a risk. Ask here is to look at locking out console inband ‘local’ user from accessing the OpenBMC GUI.

Idea priority High