Skip to main content
NetApp Stage KB

Why did I lose CIFS share connectivity during CVO failover?

Applies to

  • Cloud Volumes ONTAP (CVO)
  • CIFS

Answer

  • Clients are connecting to CIFS shares on a port tied to the local data LIF instead of connecting to the floating IP data LIF.
  • Example showing connection to port 445 on the local data LIF10.251.164.124, instead of the floating data IP of 10.253.0.2 (not shown):
Node01:
Local Address                                 Foreign Address                              (state)
10.251.164.124. 445                           10.251.103.190.59794                         ESTABLISHED 3
10.251.164.124. 445                           10.254.0.220.58846
  • When a node fails over in CVO, the floating IPs are responsible for maintaining data connectivity as they migrate between the down node to the remaining up node.
  • Floating IPs fall outside the CIDR range of the VPC network region.
  • In the example above, any client that is still connected to the local data LIF on the problematic node instead of via the floating IP will experience a CIFS outage until the down node is up again and connectivity is restored for the local LIF.

Additional Information

See Multiple Availability Zones for more information on how network traffic is delegated through floating IPs.
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.
324dff9f-c667-4c2b-815a-c5d89728f3b4