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 Delivered
Workspace IBM i
Categories Core OS
Created by Guest
Created on Jun 1, 2017

Retry Cluster Node Activation

Enhancement to auto retry cluster node activation based on user defined (or static) intervals.


Use Case:

We have a 3 node cluster, Source node, target node and Flash node. When performing maintenance (includes IPL) or role swapping the timing for node activation can cause a node to think all other nodes in the cluster are not active. When it is our Flash node, the flashcopy backup fails. to prevent this a retry-monitor-retry-monitor-retry over a period of time or indefinitely would help us avoid failed backups which occur about every three weeks or so.


Idea priority High
  • Guest
    Reply
    |
    Feb 17, 2021

    During cluster node activation, if the TCP/IP stack is active or starting, cluster code will wait up to 20 seconds for the loopback or cluster node interface to become active.
    If the TCP/IP stack is inactive, the legacy behavior will be taken and the cluster node activation will fail.
    If there is more than one node starting at the same time, cluster code will retry to attempt getting all nodes active together and avoid a singleton cluster (where a node is active but thinks all other nodes are inactive).

    This function was delivered in V7R4M0 GA codebase and PTF'd to V7R2 and V7R3.

    V7R2 PTFs: SI75016, MF68169
    V7R3 PTFs: SI75017, MF67188

  • Guest
    Reply
    |
    May 5, 2020

    We are considering this RFE for a future enhancement.

  • Guest
    Reply
    |
    May 17, 2018

    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 i
    Component - Core OS
    Operating system - IBM i
    Source - COMMON

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - PowerHA
    Operating system - IBM i
    Source - COMMON

  • Guest
    Reply
    |
    Oct 23, 2017

    IBM has received the requirement and is evaluating it. IBM will provide a response after evaluation is complete.

  • Guest
    Reply
    |
    Jun 14, 2017

    The CAAC has reviewed this requirement and recommends that IBM view this as a “nice to have” low priority feature.

    Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.

    For more information about CAAC, see www.common.org/caac

    For more details about CAAC's role with RFEs, see http://www.ibmsystemsmag.com/Blogs/i-Can/May-2017/COMMON-Americas-Advisory-Council-%28CAAC%29-and-RFEs/

    Dawn May - CAAC Program Manager

  • Guest
    Reply
    |
    Jun 2, 2017

    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 i
    Component - High Availability, PowerHA
    Operating system - IBM i
    Source - COMMON

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - PowerHA
    Component - PowerHA for i
    Operating system - IBM i
    Source - COMMON