Skip to main content

VCF 9 - Automating the VCF Support logs using Log Assist Feature

In IT infrastructure, support engineers handle a wide range of daily activities—maintaining, sustaining, and troubleshooting systems. At times, they also face complex bugs or advanced issues that require assistance from product support teams.

In this scenario, we’re using VCF as the example product a tightly integrated solution composed of multiple components working together to deliver its capabilities.

Let’s walk through a short story to understand the root cause of an issue and how it was resolved:

A support engineer named Vivek was working on importing a vCenter instance into a VCF 9 environment. During this process, he encountered a challenging error within VCF Operations that he was unable to resolve on his own.

Realizing he needed help, Vivek opened a support request with Broadcom. The support team asked him to provide the necessary log bundles for analysis. Vivek downloaded the requested logs locally and uploaded them to the Broadcom portal a task that took considerable time. Unfortunately, Broadcom later informed him that the uploaded logs were corrupted and asked him to repeat the process. This repeated effort consumed several productive hours, leaving Vivek frustrated.

Determined to find a better way, Vivek began researching and discovered a feature called Log Assist—the successor to one of his previous favorite tools, VMware Skyline.

Log Assist is a built-in capability in VCF 9 that automates the collection and upload of logs directly to Broadcom, eliminating the need for manual downloads or uploads. This significantly reduces operational overhead and allows support engineers to focus on actual troubleshooting rather than time-consuming log handling.

Now that we have a basic understanding of Log Assist, let’s look at what is required to enable and use it in a VCF 9 environment. Note that this feature is available only from VCF 9.0 onward.

Prerequisites for Enabling Log Assist in VCF 9

  • VCF Operations Deployment
    The VCF Operations appliances must be deployed in the environment.

  • Unified Cloud Proxy
    A Unified Cloud Proxy must be installed and configured. It acts as the secure communication bridge between the on-premises VCF environment and Broadcom Cloud Services.

  • VCF Operations for Logs
    VCF Operations for logs must be integrated with the vCenter instance, licensed with VCF or VMware vSphere Foundation (VVF) version 9 or later.

  • Network Connectivity
    The Unified Cloud Proxy must have outbound HTTPS connectivity (port 443) to Broadcom Cloud Services (eapi.broadcom.com), as well as access to VCF endpoints such as vCenter and ESXi hosts.

Now, As we had discussed about the requirement of technical requirement to enable "Log Assist" Feature.

Lets begin with Deployment and configuration steps:

Step 1: Download "Unified Cloud Proxy OVA" from Broadcom support Site.


Step 2: Login to VCF Operation > Administrator > Cloud Proxies










Step 3
:
Click on ADD under "Cloud proxies" section




Step 4: Copy the Unique registration key which is at #5 for future reference " This will be required during deployment of Unified Cloud proxy OVA installation"










Step 5: Installation of Unified Cloud proxy:

Deploy the Unified Cloud proxy OVA on Managment vCenter

Note: Make Sure you select "Unified Cloud Proxy" During deployment and select size as per your environment.








Step 6: Once the Unified Cloud proxy installation completed please validate it should say connected to VCF operation. It may take 5-10 min to get the connectivity. So please be bit patience.



Step 7: Once the Cloud proxy is well connected to VCF Operation follow below steps:
Administration > Cloud Proxies:     Here you will see your newly Cloud proxy vm showing with            status" Online" with Type " Unified" 

Note: As I have already activated my CloudUnified Proxy, thats the reason its showing as "Activated" . However, initially you need to Activate it using below option

Select the Cloud Proxy > Click on 3 dots > Activate Log Assist

Step 8: Now, its time integrate your Unfied Cloud proxy with associated components like VCF, vCenter and others. 

For that Go to Administration > Integrations > Accounts > ADD > VCF or NSX or vCenter 
Here we adding VCF as an account type:
>Populate the VCF details
>Collector /Group : Select the Unified Cloud Proxy 
Like this you could add other Account type like vCenter, NSX and others.

Step 9: Now its time to access the LogAssist Feature:
Login to VCF operations > Infrastructure Operatons > Diagnostic Findings > Log Assist

Click on "Prepare A Transfer" to upload logs using "Log Assist"

Select the inventory for which you would like to generate and ship the logs to Broadcom support.
Here i have selected the VCF operations logs to be shipped.

Here, log assist will validate and confirm the connectivity




Add active Broadcom Support case ID and click > TRANSFER










Logs starting initiating > Downloading and processing.. 




Logs download and shipping got completed in just 4 minutes. But again it depends on logs size.




Using "Log Assist" greatly simplifies the support engineer's workflow and eliminates unnecessary los of productive hours.

Hope you found this article useful.

Comments

Popular posts from this blog

VCF 9 Networking : Centralized vs Distributed Connectivity

  VCF 9 Networking : Centralized vs Distributed Connectivity With the release of VMware Cloud Foundation 9 (VCF 9.0) , VMware has redefined the private cloud networking model by introducing both centralized and distributed connectivity. This dual approach provides flexibility for organizations to choose between traditional edge-based routing and modern, host-level distributed networking. Why New Networking in VCF 9? Prior to VCF 9, NSX networking was largely edge-centric—requiring dedicated Edge clusters to handle north-south traffic. This created scaling and operational overheads. VCF 9 introduces a cloud-like networking abstraction with: Native VPCs (Virtual Private Clouds) for tenant isolation. Transit Gateways (TGW) to interconnect VPCs and external networks. Simplified bootstrapping – NSX VIBs are embedded in ESXi for easier enablement. Improved lifecycle and visibility via integrated VCF Operations. These enhancements align with VMware’s goal of offer...

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out. Now the option left is from the command line of VCSA appliance. Below steps will make it possible to change the FQDN of the VCSA from the command line. Access the VCSA from console or from Putty session. Login with root permission Use above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_net Opt for option 3 (Hostname) Change the hostname to new name Reboot the VCSA appliance.   After reboot you will be successfully manage to change the FQDN of the VCSA . Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client. If you are using self-signed certificate, you can regenerate the certificate with...

High-Speed Networking for VMs: VMXNET3 Now Supports Up to 65 Gbps

The VMXNET3 adapter is VMware's high-performance virtual network adapter, designed for optimized performance in vSphere environments. It is the default and recommended adapter for most modern workloads on ESXi , delivering high throughput, low latency, and support for advanced networking features. With the release of vSphere ESXi 8.0 Update 2 , VMXNET3 introduces new capabilities that significantly enhance virtual network performance. What’s New in ESXi 8.0 Update 2 for VMXNET3? Traditionally, VMXNET3 reports a default link speed of 10 Gbps to the guest operating system. However, the actual achievable throughput often exceeds this value—thanks to technologies such as multi-queue support , Receive Side Scaling (RSS) , and Large Packet Offload . Starting with ESXi 8.0 Update 2 , this limitation can now be overridden , and VMXNET3 can be configured to support custom link speeds of up to 65 Gbps . This enhancement enables improved flexibility and throughput for high-performance w...