Error 'NO NETWORK DETECTED' on newly deployed VMware Aria Operations
search cancel

Error 'NO NETWORK DETECTED' on newly deployed VMware Aria Operations

book

Article ID: 392838

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • Aria Operations OVA file was manually deployed directly on the ESXi host using the host client
  • First boot fails while waiting for network to be configured. In VM console, following errors are observed:



  • In /opt/vmware/var/log/vrops_network_manager.log, you see entries similar to:

    2025-03-31T09:08:47 Main-INFO:vROps network Manager start
    2025-03-31T09:08:48 Main-INFO: Faild to dump ovfEnv xMl, this is expected behavior only on SAAS deployment
    2025-04-01T07:37:15 Main-INFO:vROps network Manager start
  • The issue is also seen when DHCP is chosen while configuring Network settings during the vAPP deployment of Cloud Proxy as well.

Environment

VMware Aria Operations 
vCenter Server 

 

Cause

This issue occurred as the Aria Operations or Cloud Proxy OVA deployment was performed directly from ESXi host client instead of vCenter web client. This is because the vApp properties, including network settings and other values, are populated by the vCenter server via the vApp properties

Resolution

Deploy Aria Operations from the vCenter web client, as this ensures that vApp properties are automatically populated with network settings and other essential configurations.
For more information, please refer Create a Aria Operations Node by Deploying an OVF 

Additional Information

"For stability, network settings and vApp properties should use static IPv4 instead of DHCP to prevent errors."