Home > Storage > PowerStore > Databases and Data Analytics > Dell PowerStore: Oracle Best Practices > Single network path for dNFS
For the simplest dNFS network configuration, a single network path can be configured. The single network path in Figure 50 is used for the database server public network and traffic between the NAS server and NFS client. A benefit of this configuration is its simplicity, however it creates a single point of failure for NFS and potentially not enough bandwidth to support general network and NFS traffic. For these reasons, Dell Technologies does not recommend using this network configuration.
Note: Figure 50 represents a network route between a PowerStore bonded interface and an interface on the database server that is intended to be used by NFS control and data traffic. For more information about creating network routes and using specific networks, see the following sections: Shared subnets, Static routing, dNFS without oranfstab, and dNFS with oranfstab.
The interfaces shown in Figure 50 were cabled to switches, as shown by the diagram in step 7 of Adding link aggregate network interfaces to a PowerStore NAS server and in Figure 50.
The following figures show the corresponding NAS server, file system, NFS export, and NFS client interface configuration using this path:
dNFS uses two kinds of NFS mounts: the native operating system mount of NFS (known as a kernel kNFS mount) and the Oracle database NFS mount (dNFS mount). When a single network path for dNFS is used, file oranfstab is not necessary because Oracle dNFS gleans the required information for the mounted NFS share in file /etc/mtab.
If dNFS is unable to find the necessary information in /etc/mtab, control is handed back to the database, and file access is attempted through kNFS.