Problem Description
While deploying the Nutanix AHV backup proxy via Prism Central, proxy registration fails during the token activation phase with the following error:
Data services IP not configured.
In certain complex topologies, the IP address displayed within the error output may redirect to an unexpected or alternative Prism Central instance, creating operational confusion.
Additionally, a secondary deployment block may be encountered if alternative registration paths are attempted:
Activation failed: cluster was activated in the past; activating parent of activated Prism Element is not allowed
Cause
Cause 1: Unsupported Hypervisors Detected during Discovery
When the Druva proxy initiates activation through Prism Central, it scans the managed inventory. If the environment contains a mix of supported (AHV) and unsupported (ESXi) clusters under the same Prism Central parent instance, the automated registration workflow aborts upon encountering the unsupported hypervisor nodes.
Cause 2: Data Services IP Not Configured at the Cluster Level
The backup proxy routes high-performance backup streams to the Nutanix storage fabric via iSCSI loopbacks. This requires an active iSCSI Data Services IP configured directly on the underlying Prism Element cluster. If this IP is missing or unassigned, registration will fail even if initiated from a properly configured Prism Central.
Cause 3: Pre-Existing Activated Child Cluster (Prism Element)
Druva logic prevents a parent Prism Central and its child Prism Elements from being simultaneously registered as distinct top-level entities. If a Prism Element cluster under that Prism Central was already activated as a standalone asset in the Druva console, any subsequent attempt to register the parent Prism Central will be blocked.
Validation Steps
Step 1: Verify Data Services IP Configuration
Log in to Prism Element.
Click on the Cluster Name in the top ribbon bar to open Cluster Details.
Verify if a valid IP address is assigned to the iSCSI Data Services IP field and ensure it is reachable.
Step 2: Check Active Registrations in Druva
Log in to the Druva Console and navigate to Hybrid Workloads → Nutanix AHV.
Review the list of configured clusters to see if any standalone Prism Element instances belonging to your Prism Central are already registered.
Step 3: Identify Hypervisor Inventory Mix
Open Prism Central and review the connected cluster types.
Confirm if both ESXi and AHV clusters are actively being managed under the same umbrella.
Resolution
Step 1: Update Proxy Configuration to Bypass Mixed Hypervisors
Access the deployed AHV proxy via SSH/CLI.
Open and edit the configuration file using a text editor (such as
viornano):vi /etc/Phoenix/AHV/Phoenix.cfg
Locate the parameter
SKIP_UNSUPPORTED_HYPERVISORS=falseand change it to:SKIP_UNSUPPORTED_HYPERVISORS=true
Save and exit the file (
:wq!).
Step 2: Restart AHV Services
Apply the new configuration options by restarting the internal backup proxy service:
systemctl restart PhoenixAHV
Step 3: Target and Activate the Prism Element Cluster Directly
To bypass parent-child blocks, target your registration configuration directly to the intended workload level:
Obtain an activation token from the Druva Console.
Instead of pointing your registration profile to the Prism Central IP, map it directly to the specific Prism Element cluster IP requiring backup coverage.
Complete the activation workflow.
Future Guidance & Recommendations
Prism Central Consolidation: If registration at the Prism Central level becomes an absolute requirement later, you must first delete/deregister the individual Prism Element clusters from the Druva Console before initiating the Prism Central link.
Port & Routing Isolation: Ensure that firewall rules permit seamless port communications between the newly deployed AHV proxy VM, Prism Central, and the Prism Element Data Services IP.