Adding an ISCSI Data Services IP Address (Cluster Details)

  • 24 November 2021
  • 0 replies

Userlevel 2
Badge +4
  • Nutanix Employee
  • 69 replies


You can add a cluster name or virtual facing IP address at any time. To create or modify either value, do the following:



In the main menu, either click the cluster name at the far left or click the gear icon in the main menu and then select cluster details in the Settings page.


The cluster Details window appears. It displays the cluster UUID (Universally unique Identifier), ID and incarnation ID values, along with the cluster name, virtual IP address and iSCSI data services IP address (if configured). The cluster ID remains the same for the life of the cluster, but the incarnation ID is reset (typically to the wall time) each time the cluster is re-initialized.



  1. Enter (or update) a name for the cluster in the Cluster Name field.
    The default name is simply Unnamed. Providing a custom name is optional but recommended.

  2. Enter (or update) an IP address for the cluster in the Cluster Virtual IP Address field.
    A Controller VM runs on each node and has its own IP address, but this field sets a logical IP address that always connects to one of the active Controller VMs in the cluster (assuming at least one is active), which removes the need to enter the address of a specific Controller VM. The virtual IP address is normally set during the initial cluster configuration (see the Field Installation Guide), but you can update the address at any time through this field. Providing a virtual IP address is optional but recommended.

  3. Enter (or update) an IP address for use with Nutanix Volumes in theISCSI Data Services IP Address field.
    When the field entries are correct, click the Save button to save the values and close the window.

Any Nutanix feature that uses the virtual IP address might be adversely affected if you change the cluster virtual IP address.

  • You can no longer manage a Nutanix cluster (Hyper-V) through the System Center Virtual Machine Manager (SCVMM).

  • Nutanix data protection service might lose connection if you configured the remote site using the virtual IP address of that cluster.

  • All the VMs running the NGT (Nutanix guest tools) instance will be affected.

  • External machines mounting shares from Nutanix might fail if the virtual IP address is used for HA functionality (as recommended).

  • Some products such as Nutanix Objects use the virtual IP address for access. Check your product-specific documentation before changing the virtual IP address.

About iSCSI data services IP

To provide access to cluster storage, Nutanix Volumes utilizes an iSCSI data services IP address to clients for target discovery which simplifies external iSCSI configuration on clients. This iSCSI data services IP address acts as an iSCSI target discovery portal and initial connection point.

Nutanix does not recommend configuring iSCSI client sessions to connect directly to Controller VM IP addresses. The data services address is owned by one Controller VM at a time. If the owner Controller VM becomes unavailable, the address moves to another Controller VM, ensuring that it is always available.

This IP address is also used as a cluster-wide address by clients configured as part of Nutanix Files and other products. This IP address:

  • Should be in the same subnet as the cluster Controller VM IP eth0 network interface addresses

  • Helps load balance storage requests

  • Enables path optimization in the cluster, preventing bottlenecks

  • Eliminates the need for configuring a multi pathing service such as Microsoft multipath I/O (MPIO)

Nutanix recommends setting the iSCSI data services IP address once for each cluster, but you can change it if needed through the Cluster Details window in the Prism web console. If you change the iSCSI data services IP address, you will need to reconfigure any clients to use the new IP address.

  • Log out of or disconnect from existing iSCSI or Nutanix Files sessions.

  • Delete the old IP address if necessary.

  • Re-discover the new target or reestablish Nutanix Files sessions.



0 replies

Be the first to reply!