Home > Storage > Unity XT > Virtualization, Cloud & Applications > Dell Unity XT: Oracle Database Best Practices > Configuring LACP – NAS client
In environments requiring high availability, bonded NIC interfaces for NFS control traffic are recommended.
If an unbonded interface is used for the NFS mount on the NFS client, or NFS filer (see Figure 33), NFS control traffic can be blocked if the interface is down. This blocked NFS traffic causes the database to appear unavailable in certain operations.
To mitigate this single point of failure:
Also, consider configuring LACP on Unity interfaces used for NFS data traffic, and port channels on the switch connected to the Unity interfaces. Using bonded interfaces on the database server for dNFS data traffic is not recommended by Oracle. Also see the note in the section Dell Unity file system and Oracle ASM disks regarding network redundancy considerations.
The bonded interface can be shared with other network traffic like public network traffic or even traffic from an Oracle RAC interconnect. LACP needs to be configured on multiple interfaces to create a channel-bonded interface. Be mindful that NFS control or metadata traffic is minimal compared to NFS data traffic, so using 1 GbE interfaces for the bonded interface of NFS control traffic may suffice.
When LACP is configured on the NFS client interfaces for NFS control traffic, a port channel must be configured on the Ethernet switch interfaces connected to the LACP client interfaces.
When configuring dNFS with multiple network paths, if possible, use a unique network for each path. When multiple unique networks are not available, a different IP address from the same subnet can be used for each of the network paths. For more information, see the section Shared subnets.