Collecting Support Bundles for Failed VCF Automation and vIDB Installs in Fleet 9.0

When a VCF Automation (vRA) or VCF Identity Broker (vIDB) deployment fails in Fleet 9.0, troubleshooting often requires generating and downloading a support bundle.

While Broadcom KB 394146 covers part of this process, it doesn’t address all scenarios in detail. This blog consolidates the steps and provides exact commands for different situations.

🔹 Prerequisites

• Fleet Management Appliance FQDN (used in API calls).

• Fleet LCM admin user credentials (example: lcmadminuser:adminpassword).

• Environment ID:

  • Found in /var/log/vrlcm/vmware_vrlcm.log on the Fleet appliance.

  • Example command:

    grep environmentId /var/log/vrlcm/vmware_vrlcm.log


• Product ID:

  • vra → VCF Automation

  • vidb → VCF Identity Broker

🔹 Step 1: Generate Support Bundle

Run the following command to trigger log bundle creation:

• Replace <fleet-mgmt-appliance-fqdn> with your Fleet FQDN.

• Replace <environmentId> with the ID from logs.

• Replace <productId> with vra or vidb.

• duration=2 → captures the last 2 days of logs (adjust as needed).

🔹 Step 2: Check Status of the Request

You can check progress either:

• In Fleet Manager UI → Tasks, or

• By running this command:

Sample output:

The downloadUrl is the direct path to the generated support bundle.

🔹 Step 3: Download the Support Bundle

Use the downloadUrl value from Step 2:

🔹 Step 4: Alternative Download Method (Windows SCP)

If you don’t have rights to install WinSCP or another GUI tool, you can use the built-in scp command on Windows:

Replace:

• <fleetappliance_ip> → IP of the Fleet appliance.

• <REPLACEUSERNAME> → Your Windows username.

This will copy the bundle directly to your local system.

🔹 Common Scenarios

1. Failed VCF Automation (vRA) Install

   curl -k -u 'lcmadminuser:adminpassword' \
-X POST "https://fleet-mgmt.corp.local/lcm/lcops/api/environments/abcd-1234/products/vra/logs/bundle/failed?duration=2" \
-H "accept: application/json" -d ""


2. Failed vIDB Install

   curl -k -u 'lcmadminuser:adminpassword' \
-X POST "https://fleet-mgmt.corp.local/lcm/lcops/api/environments/abcd-1234/products/vidb/logs/bundle/failed?duration=2" \
-H "accept: application/json" -d ""


3. Checking Status

   curl -k -u 'lcmadminuser:adminpassword' \
-X GET "https://fleet-mgmt.corp.local/lcm/lcops/api/requests/<Request_UUID>"


4. Downloading Bundle

   curl -k -u 'lcmadminuser:adminpassword' \
-X GET "https://fleet-mgmt.corp.local/lcm/lcops/api/environments/abcd-1234/products/vra/logs/bundle/download?downloadUrl=https://10.10.10.50/supportbundles/vra-bundle-20250128T091346Z-20250130T091347Z-15820.tar.gz" \
-H "accept: */*" \
-o vra-bundle.tar.gz


🔹 Summary

• Always get Environment ID from Fleet logs.

• Use Product ID → vra (Automation) or vidb (Identity Broker).

• Trigger bundle collection with bundle/failed.

• Validate request in UI or via API.

• Download using either curl or scp.

With these steps, you can reliably collect logs for failed VCF Automation and vIDB installs in Fleet 9.0.

🔖 Reference: Broadcom KB 394146
#VCF9 #Fleet9 #SupportBundle #VCFAutomation #vIDB #BroadcomKB394146