Home > Workload Solutions > SAP > Guides > SAP HANA TDI Guides > Dell Validated Design for SAP HANA TDI Deployments with Dell PowerFlex File Storage > Host connection and setup using NAS/NFS
Each SAP HANA host requires a network connection with a minimum 25 Gb/s link speed to the dedicated storage network switches. For redundancy, the connection must have at least two NICs.
With two 25 Gb/s NICs on the SAP HANA hosts, you can optionally configure active/active interface groups on the SAP HANA hosts to use network bonding (bonds), in which multiple network interfaces are aggregated into a single logical bonded interface.
On the SAP HANA hosts, create the mount points by running the following commands, where x = 1, 2, 3, and so on, up to the number of hosts in the scale-out system:
mkdir -p /hana/data/SID/mnt0000x
mkdir -p /hana/data/SID/mnt0000x
mkdir -p /hana/shared
chmod -R 775 /hana/data/SID/
chmod -R 775 /hana/log/SID/
chmod -R 775 /hana/shared
Note: For SAP HANA scale-out systems, all the mount points must be created on each host and the /hana/shared must be shared between all hosts.
Add the entries to /etc/fstab:
<NAS Server>:/<filesystem> /hana/shared nfs4 rw,bg,hard,timeo=600,intr,noatime,vers=4.0,rsize=262144,wsize=262144,lock,_netdev 0 0
where <NAS Server> is the IP address or hostname of your NAS server on the PowerFlex system. If you are using NFSv3, adjust the NFS version. Add the _netdev mount option when mounting NAS devices. This mount option prevents the system from attempting to mount these file systems until the network has been enabled on the system.
Note: Dell SAP engineering performed the SAP HANA scalability test on both the NFSv3 and NFSv4 file systems. The test results showed that NFSv3 performs slightly better than NFSv4, with NFSv4 having a performance overhead of between 5 and 10 percent. NFSv3 achieved the scalability for SAP HANA that is shown in Table 3 . Consider this 5 to 10 percent impact when sizing for SAP HANA if NFSv4 is your preferred option.
For optimal performance, ensure that the SAP HANA mounts are evenly distributed across all available PowerFlex File front-end IP networks of the NAS servers in the /etc/fstab file. In a 2+1 SAP HANA scale-out system with SID = PFX, the mount points are in the /etc/fstab file on each of the SAP HANA clients, including any standby hosts. The following code extract shows an example using NFSv3:
# SYSTEM PFX 2+1 NFS3
172.93.39.101:/fs1 /hana/shared nfs re,vers=3,hard,timeo=600,rsize=262144,wsize=262144,intr,noatime,nolock,_netdev 0 0
172.92.37.101:/fs2 /hana/data/PFX/mnt00001 nfs rw,vers=3,hard,timeo=600,rsize=262144,wsize=262144,intr,noatime,nolock,_netdev 0 0
172.92.37.101:/fs3 /hana/log/PFX/mnt00001 nfs rw,vers=3,hard,timeo=600,rsize=262144,wsize=262144,intr,noatime,nolock,_netdev 0 0
172.92.39.101:/fs4 /hana/data/PFX/mnt00002 nfs rw,vers=3,hard,timeo=600,rsize=262144,wsize=262144,intr,noatime,nolock,_netdev 0 0
172.92.39.101:/fs5 /hana/log/PFX/mnt00002 nfs rw,vers=3,hard,timeo=600,rsize=262144,wsize=262144,intr,noatime,nolock,_netdev 0 0
If preferred, use the following example for /etc/fstab with NFSv4 parameters.
# SYSTEM PFX 2+1 NFS4
172.93.39.101:/fs1 /hana/shared nfs4 rw,bg,vers=4.0,hard,timeo=600,rsize=262144,wsize=262144,intr,noatime,nolock,_netdev 0 0
172.92.37.101:/fs2 /hana/data/PFX/mnt00001 nfs4 rw,bg,vers=4.0,hard,timeo=600,rsize=262144,wsize=262144,intr,noatime,nolock,_netdev 0 0
172.92.37.101:/fs3 /hana/log/PFX/mnt00001 nfs4 rw,bg,vers=4.0,hard,timeo=600,rsize=262144,wsize=262144,intr,noatime,nolock,_netdev 0 0
172.92.39.101:/fs4 /hana/data/PFX/mnt00002 nfs4 rw,bg,vers=4.0,hard,timeo=600,rsize=262144,wsize=262144,intr,noatime,nolock,_netdev 0 0
172.92.39.101:/fs5 /hana/log/PFX/mnt00002 nfs4 rw,bg,vers=4.0,hard,timeo=600,rsize=262144,wsize=262144,intr,noatime,nolock,_netdev 0 0
The operating system command mount –a mounts all the directories from the PowerFlex File system. Run this command on each SAP HANA client.