Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

Why did I lose CIFS share connectivity during CVO failover?

Views:
47
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
cloud
Last Updated:

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.
Scan to view the article on your device