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
When an NFSv4 client mounts a share from an NFS server and has nfso client_delegation set to 1, it causes the rtcmd daemon on NFS server to establish a callback connection to the n4bg daemon on the NFS client on a random high port.
These connections are not necessary for NFS functionality, and in the environments where not specifically allowed they cause numerous drops on the firewalls. This becomes a source of complaints coming from the network team.
As seen in the support case TS003909582, it does not seem to be possible to disable this callback on the NFS server. The only way to do so today is to disable it on the clients. This is cumbersome in certain environments where NFS clients and server are managed by different entities, and e.g. a "misconfigured" client can cause problem for NFS server administrator since it's the NFS server that is establishing the connection. It's much more efficient to just disable this type of connection on the server side.
Idea priority | High |
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.
Server_delegation=0 or export using option deleg=no doesn't work. When combining AIX NFS server and Linux client using 4.1 or 4.2 you have no way how to get rid of deleg and that's shame for AIX admin.
Client delegation is available, but doesn't solve the problem "Option to disable client delegation on the SERVER SIDE". Server_delegation=0 or export option deleg=no doesn't work and NFS client using default client_delegation=1 nfs option overrides this!
https://www.ibm.com/docs/zh/aix/7.1?topic=n-nfso-command