Aria Automation delayed in discovering manually reconfigured static IP addresses for Virtual Machines.

Products

• VCF Automation

Issue/Introduction

In Aria Automation 8.18.x environments, when a virtual machine's static IP address is manually reconfigured directly within vSphere/vCenter, the following issues occur:

• The IP address field in the Aria Automation Inventory remains empty or displays an APIPA (169.254.XX.XX). 

• Networking changes are not reflected during standard Incremental Enumeration cycles.

• The correct IP address only appears after a significant delay (could be more than 48 hours), coinciding with a Full Data Collection cycle.

Environment

Aria Automation 8.18.X

Cause

This behavior is by design based on the default inventory collection mechanism in Aria Automation.

Aria Automation does not immediately reconcile these changes in its database, resulting in a synchronization delay (Could be more than 48 Hrs.) full inventory collection cycle is performed.

Resolution

To force Aria Automation to discover the updated IP address without waiting for the 24-hour full collection cycle, you must trigger a vCenter event that Aria Automation recognizes.

Recommended Action: Perform a Power State Change A power cycle sends a machine metadata update from vCenter to Aria Automation, which triggers an immediate incremental enumeration for that specific object.

1. Log in to the vSphere Client.

2. Locate the affected Virtual Machine.

3. Power Off the Virtual Machine.

4. Power On the Virtual Machine.

Note: Once the Power On event is received by Aria Automation, it initiates a targeted data collection for that machine, populating the IP address field in the database.

If reboot of the VM is not possible then below operations could be performed: 

• Performing a "Reconfigure VM" task (e.g., adding a temporary disk or adjusting CPU/Memory).
• VM Snapshot.