“IP Subnet for Management Network Not Provided” error Displayed in Cloud Status Despite Correct Configuration

Products

• VMware Avi Load Balancer

Issue/Introduction

• An “IP subnet for Management Network not provided” error may appear in the UI when navigating to Cloud Status → Management Network, even though the management network and static IP pool are properly configured.

      Path to reproduce the issue in UI:

      Infrastructure → Cloud → Select the Cloud → Click the three dots → Cloud Status → Management Network

• Upon clicking Management Network, the UI reports the error “IP subnet for Management Network not provided”, despite the management network and static IP pool being correctly configured under the Networks section.

 

Environment

• Avi Load Balancer
• Affected Version: 31.2.1

Cause

 

• This behavior is due to a known issue in the Network Diagnostics RPC, where it still checks the mgmt_ip_subnet field in the vCenter configuration even though this field is no longer populated.
• This situation typically occurs when a vCenter cloud is configured with dhcp_enabled or ip6_autocfg_enabled set to False, which causes the Management Network to inherit these flags during discovery.

Resolution

Workaround:

• The diagnostic error can be safely ignored, as it does not have any impact on operations or traffic.

• From the UI perspective, you should still be able to save the Cloud configuration successfully.

• Once the Cloud status shows Placement Ready, you should be able to proceed with creating Service Engines and Virtual Services.

Verifying the cloud status via CLI

You can also check the cloud status using the controller shell:

1. Log in to the Controller shell using admin credentials.

2. Run the following command:

 

show cloud <cloud-name> status

 

Fix: 

This issue is a known UI bug and is planned to be fixed in a future release.