Configure NSX Backup Schedule task fails during a Workload Domain import (VCF 9.1)

Products

• VCF Operations

Issue/Introduction

This article addresses deployment failures during NSX Manager provisioning in VCF 9.1 environments, specifically when the "Configure NSX Backup Schedule" subtask fails due to missing or misconfigured network settings.

The following error was observed on the Configure NSX Backup Schedule subtask of a brownfield import:

Error: Failed to configure NSX Backup Schedule for NSX Managers
Cause: InvalidRequest (com.vmware.vapi.std.errors.invalid_request) (statusCode:400) => { messages =[], data ==> {error_message=Restore error: Error while fetching fingerprint of fileserver <fileserver> at port <port>, httpStatus=BAD_REQUEST, error_code=29259, module_name=backup-restore}, errorType = INVALID_REQUEST }

Environment

• VMware Cloud Foundation (VCF) 9.1
• NSX Manager 9.1
• VMware vCenter 9.1

Cause

The issue stems from an incorrect target vCenter or misconfigured vApp network options, resulting in an invalid or missing default gateway on the NSX Manager VM. This prevents the appliance from routing traffic to external backup servers, causing SSH fingerprint errors or connection timeouts.

Resolution

Steps to identify the missing default gateway:

1. Verify Configuration: Access the VM console (Alt+F1), login as the admin user (credentials are available from the deployment task), switch to root (st en)
2. Test connectivity: traceroute and ping to the backup server fail
3. View the routing table: The route command did not show a default gateway
4. Add the default gateway: (route add default gw <gateway_ip>)
   
5. Test connectivity: traceroute and ping to the backup server are successful
6. Reboot the VM: The VM was rebooted but was still having issues (SSH unresponsive, no DNS, etc) after adding the default gateway.
7. Further analysis: The NSX Manager VM's vApp Properties showed values that were obtained from the incorrect deployment.
   
8. Abandon the corrupted deployment: The Workload Domain import task was already canceled and the resolution was to abandon the corrupted deployment and initiate a fresh NSX cluster deployment, ensuring the correct target vCenter and network port group is utilized.

Additional Information

Contact Broadcom support for additional assistance