Fresh Agent Installation Asset Name IP Fix
On fresh agent installations, the first scan previously used the Discovery Application's IP in the asset name instead of the agent's own IP, due to a race condition in IP detection. IP detection now runs before scanning starts and selects the correct physical adapter IP using an interface-scoring algorithm. VPN, Docker, and VMware virtual interfaces are explicitly filtered out.
Where the fix appears
The corrected asset name is visible in the following locations:
| Location | What changed |
|---|---|
| CMDB > Host CI created after fresh agent install | The asset name correctly shows the agent's own IP instead of the Discovery Application IP. |
| Discovery Agents list | Newly registered agents display the correct IP address. |
Procedure
Complete the following steps to apply the fix to new and existing agents.
-
Update the Discovery Agent.
Deploy the updated agent. All new installations use the corrected IP detection automatically.
-
Fix existing affected CIs.
Trigger a re-scan on affected agents to correct the asset name on previously created CIs.