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.
IBM i Development Team
Maybe the issue is related to the use of NFS V3 with TCP instead of UDP, so let me refrase my request:
Can you allow the 632B device to use NFS V3 over TCP so we can connect to Azure NFS service or Azure DataBox?
Understand this changes, but sometimes we need to perform some tasks like upgrades or restore 21 that require the 632B device usage. Are 632B devices aware of these changes to use TCP instead of UDP?
The IBM i NFSv3 client does have support for TCP, but it is not the default. Additional steps need to be taken to enable TCP client support on releases prior to IBM i 7.5. See https://www.ibm.com/support/pages/start-nfs-client-using-tcp-instead-udp-r610 for information on how to enable TCP support.
The virtual optical NFS devices only support NFSv3 over UDP. Those are not compatible with NFS servers that only support NFS over TCP.
Does any of that information resolve the problem, or is more investigation required to address and define the request?
-- IBM i NFS development team lead
We have make some tests with Azure NFS V3 service to mount from IBM i using ADDMFS and fail with a message telling there's no response from the NFS server.
We have also tried with a 632B device (works different) with errors too.
The request, as currently stated, appears to be invalid because the NFS client does not ping the server during or prior to processing a mount request. Is there a specific connection scenario or support case related to this request that could help the development team better understand the problem?
-- IBM i NFS development team lead