VM IP Addresses Not Displayed in Prism After Cluster Network/Gateway Change

Hello,

I am experiencing an issue where VM IP addresses are no longer displayed in Prism after changing the network environment of a Nutanix cluster.

I would appreciate any advice or information about similar cases.

Environment

• Nutanix AHV-based cluster

• Multiple VMs running on the cluster

• Both Windows and Linux guest operating systems are present

• Nutanix Guest Tools (NGT) are not being used

What happened

1. The network environment of the Nutanix cluster was changed.

2. The Gateway configuration of the existing cluster/service network was also changed.

3. The cluster was then connected to a different network environment.

4. The cluster was powered on again.

5. The cluster and VMs are operating normally after the change.

Current symptoms

• All VMs have valid IP addresses configured inside their guest operating systems.

• Network connectivity from the VMs to the Gateway and external networks is working normally.

• The VM network adapters and VLAN configuration appear to be functioning correctly.

• However, the VM IP address information is not displayed in Prism.

• The same behavior is occurring on multiple VMs.

• NGT is not installed or enabled on these VMs.

Because the VMs themselves have valid IP configurations and normal network connectivity, I suspect that the issue may be related to the IP discovery/information collection process between the VM, AHV/OVS, and Prism after the network environment was changed.

I am currently considering the following possibilities:

• ARP or IP discovery information was not properly refreshed after the network/Gateway change

• AHV/OVS is not properly learning the VM MAC/IP information

• Prism/AOS is having an issue collecting or displaying VM IP information

• Some network-related information, such as the Cluster Virtual IP or related configuration, was not properly updated after the network change

The VMs themselves have no apparent network connectivity issues. The main symptom is that their IP addresses are not displayed in Prism.

Has anyone experienced a similar issue after changing the cluster/service network subnet or Gateway and moving the cluster to a different network environment?

I would also appreciate any guidance regarding the following:

1. Are there any known issues or KBs related to this behavior?

2. What is the recommended way to verify VM IP discovery on AHV/OVS?

3. Which Prism/AOS services or logs are responsible for collecting VM IP information?

4. Is there a recommended procedure to refresh ARP/IP discovery information?

5. Are there any specific NCC health checks or post-network-change validations that should be performed?

For security reasons, I have intentionally omitted all IP addresses and internal network information from this post.

Thank you.