Skip to main content
NetApp Stage KB

How does Trident handle a dataLIF setting for ontap-san driver with multipathing

Views:
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
SNAPX
Last Updated:

Applies to

  • Trident for Openshift and Kubernetes
  • Drivers: ontap-san, ontap-san-economy

Answer

With either no dataLIF setting, or just a specific IP address, Trident will still create sessions to the HA Pair partner's iSCSI LIF as well.
 
If multipathd is not running, and mapper devcies for multipath are therefore not created, Trident will mount one of the new disk devices on node attach.
With this situation, there is no HA pair failover redundancy, when the connection IP disappears (these IPs do not travel to other interfaces or nodes).

Additional Information

Multipathing needs to be enabled, or there will be issues with handling of the PVC, since errors about the remaining disk devices can crop up.
Additionally, it is expected to use find_multipaths = no, since Trident will provide the necessary functionality.
 
Note: the dataLIF only takes one IP address, in the Trident backend configuration. The option was mainly meant for NFS, since, when using multiple LIFs in the SVM, you may want to specify the IP that normally runs on the node with the aggregate of the PVC volume.
NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.
Case Citation
68b52f97-580e-4d1f-a6e4-a8b69e6fd983