Problem Description:
During Nutanix backup proxy deployment and token registration, the following error may appear in the console or logs:
Data services IP not configured.
Symptoms may also include:
The IP address shown in the error unexpectedly redirects traffic to a different Prism Central environment.
The token registration process fails completely, preventing the backup proxy from connecting to the Druva Cloud.
Cause:
This issue occurs due to one or more of the following environmental or structural mismatches:
The iSCSI Data Services IP is missing or unconfigured within the targeted Nutanix cluster settings.
An incorrect, cached, or stale environment configuration exists within the deployed backup proxy.
A mixed hypervisor environment (e.g., Nutanix clusters running unsupported hypervisors like ESXi alongside AHV) is interfering with the proxy's discovery workflow.
A configuration mismatch or load balancer rule is routing the proxy's registration request to an alternate Prism Central instance.
Resolution:
Step 1: Verify Data Services IP in Nutanix
Log in to Prism Central or the specific Prism Element cluster.
Navigate to Settings ➔ Network Configuration ➔ Data Services IP (or click the cluster name in Prism Element to check the Cluster Details dialog box).
Confirm that an iSCSI Data Services IP is configured, is assigned as a static IP (outside the DHCP scope), and is reachable.
Step 2: Validate Network and DNS Routing
Ensure that:
The backup proxy has clear network routing to reach Prism Central.
DNS resolution is functioning correctly on the proxy for all Prism FQDNs.
Firewalls are not dropping communication over storage/management traffic ports (e.g., 443, 9440, 3261).
Step 3: Skip Unsupported Hypervisors (For Mixed Environments)
If your Nutanix environment contains ESXi nodes that are confusing the discovery mechanism:
Log in to the backup proxy command line via SSH.
Open and edit the configuration file:
vi /etc/Phoenix/AHV/Phoenix.cfg
Add or update the following parameter:
SKIP_UNSUPPORTED_HYPERVISORS=true
Save the file and restart the Phoenix service to apply the changes:
systemctl restart Phoenix
Retry the token registration process.
Step 4: Validate IP Redirection
If the validation traffic redirects to an unexpected Prism Central instance:
Verify your environment's cluster-to-Prism Central mapping rules.
Confirm that public/internal DNS FQDNs or load balancers are not routing traffic to the wrong management endpoint.
Outcome:
Once the configuration anomalies are corrected and unsupported hypervisors are bypassed, the token registration succeeds, and the Nutanix backup proxy deployment completes normally.
Best Practices:
Always ensure an iSCSI Data Services IP is assigned to the Nutanix cluster prior to attempting a Druva proxy deployment.
Ensure clear isolation or explicit flags (
SKIP_UNSUPPORTED_HYPERVISORS) are set when operating within mixed-hypervisor setups.