This section lists several key considerations when using OneFS NFSv3 over RDMA feature.
- NFSv4.x includes built-in support for stronger security mechanisms compared to NFSv3. While these security features are not directly tied to RDMA, NFSv4.x over RDMA benefits from the enhanced security capabilities of NFSv4.x compared to NFSv3.
- Match the Maximum Transfer Unit (MTU) on both the OneFS cluster and NFS client. Mismatch MTU size may result in NFS operations becoming unresponsive and breaking your workload.
- Dynamic IP pools failover considerations when using NFS over RDMA.
- Dynamic IP pools is the current network configuration recommendation for OneFS NFS. The purpose of dynamic IP pools is to allow client workflow to continue processing when a node goes down. Dynamic IP pools provide an IP-failover ability to move an IP from one network interface card (NIC) to another NIC on any node.
- IP failover from a ROCEv2 capable interface to a ROCEv2 incapable interface is not supported. Therefore, enabling NFS RDMA RRoCE only option in the RDMA IP pool is recommended if you are using NFS over RDMA.
- When OneFS cluster and NFS clients are connected through L2 Switch directly, the IP failover may fail for NFS over RDMA workflow. This is caused by the client RDMA stack cannot handle Gratuitous ARP properly. Therefore, we recommend placing a router or L3 Switch between the OneFS cluster nodes and the NFS over RDMA clients.
- Enable flow control on switch ports to achieve good performance when losing network packet.
- NFS over RDMA does not support aggregated interfaces and VLAN tagged interfaces in PowerScale nodes.
- IPv6 is not supported when using NFS over RDMA.
- Making sure your NFS client is running on RoCEv2 mode.