"IP is already provisioned" may be encountered on a Platform VM during cluster creation

Products

• VCF Operations for Networks

Issue/Introduction

During the cluster creation process from a standalone deployment of VMware Aria Operations for Networks (formerly vRNI), the setup fails with the explicit error message IP is already provisioned.

This failure occurs when attempting to form a multi-node cluster (supported configurations include 3, 5, 7, 10, or 15 nodes), which strictly requires the additional platform VMs to be pre-deployed, powered on, and properly assigned unique network configurations prior to running the initialization script.

Environment

VCF Operations for Networks

Resolution

To avoid this IP conflict error, you can use the standard method of creating a cluster using the steps mentioned in How to create a Cluster, from a standalone deployment of VCF Operations for Networks

• Verify that the intended target IP address is completely unallocated on the network by running standard lookup utilities from an independent terminal:

  ping <TARGET_IP>
  nslookup <TARGET_IP>
  

• Deploy a fresh, additional platform VM from the official OVF template within vCenter Server.

• Assign a completely unique, unallocated IP address to the new node during the OVF deployment customization phase.

• Ensure the new platform VM is fully powered on and its internal services have stabilized.

• Re-run the cluster formation process from the primary standalone interface to successfully bind the nodes into the cluster.