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 Delivered
Workspace AIX
Created by Guest
Created on Jul 19, 2017

RELATED IDEAS

Provide capability to bypass the node fencing when remove a node from the domain

Background information:

As part of the protocol (with gpfs_agent as the IBM.FenceAgent) when a node leaves a domain while maintaining quorum, the node will be fenced via mmexpelnode. This causes the file system on the fenced node to be unavailable.

This works great if the Db2 customer intends to put the entire cluster (peer domain and GPFS cluster in pureScale) into maintenance. However, there are customers who only want to put the peer domain in the maintenance only, but not GPFS. It is a valid use case because they need the GPFS to be online. The mmexpelnode causes their GPFS to go offline, leading the PMR 90845,122,000

In the investigation of PMR with RSCT development team, a short term fix and a long term fix was proposed. The short term fix involves using a temporary file on the RecRM leader to avoid the mmexpelnode when a node leaves the domain while maintaining quorum. This should provide temporary relief for the customer while working on the long term fix.

The long term fix is what this RFE is for. It involves adding a new option to stoprpnode to bypass the mmexpelnode.

Idea priority Urgent
  • Guest
    Reply
    |     Apr 2, 2020

    It is delivered in RSCT 3.2.4 for DB2

  • Guest
    Reply
    |     Oct 11, 2017

    Any update on this RFE ? it is important to get this feature to replace the current workaround. thanks.

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.