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 Submitted
Workspace AIX
Created by Guest
Created on Nov 5, 2024

RELATED IDEAS

Correct the way AIX NFS4 client constructs its clientID, so that it is persistent across LPMs, as it is required to be.

Current behavior/design

Currently, the clientID generated by AIX NFS4 client can possibly change after an LPM. This is because of the current design.

In the current design, NFS4 client uses the nodeID as a part of the clientID, and the nodeID can change after an LPM. The new clientID can possibly conflict with one generated by an old LPAR in the frame.

Expected Enhancement

Use a different algorithm for generating the clientID, so that it remains persistent across LPMs (and across reboots as well).

Benefit

The current behavior violates the RFC requirement that clientID should remain unchanged on reboots & reincarnations of the client. So modifying the current design would help keep us in line with RFC.

Also, the current design could elicit an unexpected "NFS4ERR_CLID_INUSE" error from the server if the server still has that clientID saved. Or it could lead to other types of server misbehavior, due to the collision. This is what had happened at a customer site, and it resulted in data availability issues . There could be more chaos depending on the server (if it discards all the state associated with the other client). We would avoid these data availability, and possible data inconsistency issues.

Idea priority Urgent
  • Guest
    Reply
    |     Nov 14, 2024

    Please fix this bug asap.
    We have already created many tickets in the last few years but have not received a solution except to reboot the affected lpars.
     

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.