Collecting diagnostic information for Telco Cloud Platform cases

Products

• VMware Telco Cloud Automation
• VMware Telco Cloud Platform

Issue/Introduction

• Which logs to attach to a TCA / TCP case

Environment

TCA: 2.3, 3.1, 3.1.1, 3.2, 3.3, 3.3.0.1, 3.4, 3.4.0.1

TCP: 3.0, 4.0, 4.0.1, 5.0, 5.0.1, 5.0.2, 5.1, 5.1.1

Cause

To ensure faster root cause analysis and reduce back-and-forth communication, it is essential to attach the appropriate logs when opening a case.

Resolution

Recommended logs to collect, based on the nature of the issue:

Issues During Install / Configure / Upgrade via TCA

• TCA Support Bundle – collected via TCA UI
• TCA-CP Log Bundle – collected via TCA-CP UI

If Kubernetes and/or Network Function (NF) LCM operations are involved:

• Include applicable workload cluster and parent management cluster logs via the K8s Log Bundle option.

If errors are observed in the vCenter Console (vc-console):

• Include the associated vCenter Support Bundle
  Note: These logs can be very large. Confirm with GS prior to generating/uploading.

If failure impacts an ESXi host:

• Include ESXi logs
  Note: These are typically required only in rare scenarios. Confirm with GS prior to generating/uploading.

Scale or Performance Issues (NF or Kubernetes)

• TCA Support Bundle – via TCA UI
• TCA-CP Log Bundle – via TCA-CP UI
• Kubernetes Cluster Logs
  • Include both Management and Workload Clusters
• Node-Level Logs
  • Collect from the node pool where the application is deployed and facing performance issues
• vCenter Support Bundle
  • Ensure Host Logs are included
• NSX Log Bundle
  • Include logs from Management, Control-Plane, and Data-Plane

NSX Performance Issues

• High CPU Utilization on ENS lcores 

Additional Information

Collecting logs from additional TCP components:

• vCenter
  • Collecting diagnostic information for VMware vCenter Server 7.x and 8.x (330178)
  • Collecting diagnostic information for ESXi/ESX hosts and vCenter Server using the vSphere Web Client (326299)
• ESXi
  • Collecting diagnostic information for VMware ESXi/ESX using the vSphere Client (319493)
  • Collecting diagnostic information for VMware ESXi/ESX using the vm-support command (313542)
  • Collecting diagnostic information for ESXi/ESX hosts and vCenter Server using the vSphere Web Client (326299)
• vCloud Director
• VMware Integrated OpenStack
• Gathering Logs for vSphere with Tanzu
• Manually collect logs from a TKG cluster
• Aria Automation Orchestrator
• Aria Operations
• Aria Operation for Logs
• Aria Operations for Networks
• NSX Advanced Load Balancer
• Avi Kubernetes Operator
• Site Recovery Manager
• vSphere Replication

General Best Practice

• Logs stored locally on subsystems such as TCA or vCenter are limited by disk space and the volume of logs generated.
• In cases where a system is encountering frequent errors or large exception traces, logs may rotate quickly—sometimes retaining only a few days or a week's worth of data.
• Since root cause analysis often depends on historical logs, this can hinder timely resolution.

It is strongly recommend to utilize Aria for Logs where:

• Larger volumes of historical logs are retained.
• Filters can be applied based on context, timestamps, or component type to speed up analysis.

See the following KBs

• Configure TCA to forward logs to Aria for Logs
• Download, install, and use TCA Content pack