Web UI unreachable or unable to ping appliance after deployment in VCF Operations
search cancel

Web UI unreachable or unable to ping appliance after deployment in VCF Operations

book

Article ID: 449880

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

After deploying the VCF Operations appliance using an OVA, the node is not reachable on the network and the Web console fails to load.

  • Unable to ping the appliance IP address.
  • Pinging the gateway from the console and it was unsuccessfu
  • Unable to launch or access the VCF Operations Web UI console.
  • Network connectivity tests from the appliance console fail.

Environment

 VCF Operations 9.1

Cause

An incorrect subnet mask was provided during the OVA deployment wizard. While the assigned IP may belong to a /24 network, a different mask configured in the vApp properties prevents correct routing and connectivity.

Resolution

To resolve this issue, update the subnet mask in the vCenter vApp properties:

  1. Log in to the vCenter Server UI.
  2. Locate the VCF Operations appliance VM in the inventory.
  3. Shut down the node using Shut down Guest OS.
  4. Navigate to Configure > App Options > Properties.
  5. Select the ipv4_netmask.VMware_Aria_Operations property and click Set Value.
  6. Enter the correct subnet mask (e.g., 255.255.255.0 for a /24 network) and click OK.
  7. Power on the appliance.
  8. Verify functionality by pinging the IP and accessing the Web UI.

If the issue persists, verify that the Gateway and DNS settings in the same vApp Options menu are also correct.

Additional Information

For standard deployment steps, refer Deploy VCF Operations Nodes