HCX - Save option is missing when adding Static Routes to Compute Profile

Products

• VMware HCX

Issue/Introduction

When configuring an HCX Compute Profile in the HCX Manager UI, administrators may encounter a situation where the Save button remains greyed out after entering static route details in the Static Routes section.

As a result, the Compute Profile cannot be saved, preventing the completion of the Compute Profile wizard and blocking the deployment or modification of HCX Service Mesh components that depend on these static routes for management or uplink connectivity.

During validation, one or more error messages similar to the following may be displayed:

• The network addresses for the static route should not be overlapping with the network address of the selected network profile

• The nextHop address must be an address from the network address range of the selected network profile excluding the first and last address.

Additional validation errors may also be displayed depending on the specific static route configuration and the associated network profile.

Environment

VMware HCX

Cause

HCX performs a series of validation checks before enabling the Save option. If any of these validations fail, the configuration is considered invalid and the Save button remains greyed out.

The validation checks include, but are not limited to, the following:

• The destination network configured for the static route must not overlap with the network address of the selected network profile.
• The next hop IP address must belong to the IP address range of the selected network profile.
• The next hop IP address cannot be the network address (first IP) or the broadcast address (last IP) of the selected subnet.
• The static route configuration must be valid and consistent with the selected network profile and HCX networking requirements.

If any of the above validation checks fail, HCX prevents the configuration from being saved to ensure that only valid and reachable static routes are configured for the Compute Profile.

Resolution

Review the static route configuration and the corresponding network profile associated with the Compute Profile, ensuring that they meet all HCX validation requirements before attempting to save the Compute Profile.

Verify the following:

• The destination network does not overlap with the network address of the selected network profile.
• The next hop IP address belongs to the subnet of the selected network profile.
• The next hop IP address is a valid host address and is not the network address (first IP) or broadcast address (last IP) of the subnet.
• The subnet mask, destination network, and next hop values are entered correctly.
• The selected network profile is appropriate for the desired routing configuration.

After correcting any validation failures, return to the Static Routes section. Once all validation checks pass, the Save button becomes enabled, allowing the Compute Profile configuration to be saved.

If the required next hop is outside the selected network profile's subnet, review the network design with your network team. Depending on your environment, you may need to:

• Make the required network routable so that a valid next hop exists within the selected network profile.
• Select a different network profile that contains a valid next hop for the desired route.
• Modify the HCX network design to align with your routing requirements.

These recommendations should be evaluated based on your organization's networking architecture and routing policies.