An administrator is configuring an iSCSI LUN for use on a CVO HA instance in AWS. Before the LUN goes into production, the administrator needs to do…

In a Cloud Volumes ONTAP (CVO) High-Availability (HA) configuration in AWS, client data access for protocols like iSCSI relies on floating IP addresses. A floating IP is a virtual IP address assigned to a data Logical Interface (LIF) that is not permanently bound to a single node's network interface. During a failover event, Cloud Manager automatically updates the AWS VPC route tables to direct traffic destined for the floating IP to the network interface of the surviving node. This mechanism ensures that the host maintains a persistent connection to the iSCSI LUN using the same IP address, enabling seamless failover without requiring host-side reconfiguration.

A. IntraCluster: These IP addresses are used exclusively for internal communication and synchronization between the nodes within the HA pair, not for client data access.

C. Private: This term is too generic. While the floating IP is a private IP from the VPC's CIDR block, its essential characteristic for failover is its ability to "float," not just its private nature.

D. InterCluster: These IP addresses are configured on Intercluster LIFs and are used for replication traffic, such as SnapMirror, between different ONTAP clusters, not for host-to-LUN access.

1. NetApp Documentation, "Set up Cloud Volumes ONTAP for AWS," Networking requirements for HA pairs in AWS section.

"For an HA pair, you need to specify floating IP addresses for the SVM data LIFs. These IP addresses can fail over from one node to the other. Cloud Volumes ONTAP uses these floating IP addresses to communicate with clients and hosts. If a node fails, the floating IP addresses move to the other node to provide continued access to data."

2. NetApp Technical Report, "TR-4597: Cloud Volumes ONTAP for AWS Architecture and Deployment Guide," Section 3.2 Networking.

"For data access, CVO HA pairs use floating IP addresses that are not tied to a specific ENI. In the event of a failure, the floating IP addresses are reassigned to the ENIs on the healthy node by making an API call to AWS to change the routing tables in the VPC."

3. NetApp Documentation, "Cloud Volumes ONTAP release notes," Networking for HA pairs in AWS section.

"An HA pair in AWS uses floating IP addresses for data LIFs to provide seamless failover. When a node fails, the floating IP addresses move to the healthy node, which takes over and continues to serve data."