Technical Support Fundamentals — Broadcom Wolken Case Management
Objectives
- Navigate Broadcom Support Portal and Wolken case management site
- Create a support case with correct severity level and required fields
- Understand when Raise Concern becomes available (P1 after 12 h, P2 after 24 h, P3 and P4 after 48 h; once every 24 h per case — Broadcom KB 142527)
- Search and use KB articles for troubleshooting (key articles: 144456, 200997, 252162, 275360)
- Generate and transfer diagnostic log bundles via Log Assist
- Use VCF Operations Log Analysis for real-time troubleshooting
Prerequisites
Active Holodeck VCF 9.0 lab or access to VCF documentation
Required skills:
- Basic VMware terminology
Tasks
Task 1 Wolken Case Management
Navigate and use Broadcom's Wolken case management system
Broadcom Support Portal: register with corporate email, access requires valid Support Site ID (processing up to 48 hours). Navigate: My Dashboard → My Cases or My Entitlements → select product → case icon. Case views: My Cases (user-opened), All Cases (includes cases from additional Site IDs).
Required fields: Issue Type (Technical/Non-Technical), Product (entitled products only), Company/Site ID (auto-populated), Product Release/version, Severity (P1-P4), Component, Subject (auto-searches KB), Description (detailed issue description + actions taken). For P1 (Critical): must confirm production down + describe business impact. Operating System and Service Pack are optional.
P1 Critical: production down, 24/7 engagement, Raise Mgmt Concern after 12 hours. P2 High: significant impact, Raise Mgmt Concern after 24 hours. P3 Medium: limited impact, Raise Mgmt Concern after 48 hours. P4 Low: minimal impact, Raise Mgmt Concern after 48 hours. Raise Mgmt Concern = child ticket to support manager (NOT a severity change). A concern can be raised once every 24 hours per case; Raise Concern is not the way to move a case to Severity 1 — use the change-severity process (KB 142527).
Quick actions: add comment, file attachment info (FTP/SFTP upload details), refresh, export (PDF/Word), Raise Management Concern (escalation), request close. Case tabs: Unified History (all activities), Comments (add info), Knowledge (linked KB articles), Related Content (technical references). Filter views: AND/OR conditions, sort by field, custom columns, save views.
Validation Gate
Check: What log bundles should you collect before filing a VCF support case?
Expected: ESXi: vm-support bundle. vCenter: vc-support bundle. NSX: support bundle from NSX Manager UI. SDDC Manager: sddc-support bundle from SDDC Manager CLI. Collect ALL relevant bundles — the issue may span components.
Common Errors
Task 2 Knowledge Base & Log Collection
Use KB articles for troubleshooting and collect diagnostic logs
KB article types: how-to, best practices, FAQs, advisories (critical updates/vulnerabilities). Article sections: Products, Issue/Introduction, Environment, Cause, Resolution. Access: Broadcom Support Portal → Knowledge widget → search by keywords + filter by article type/product/date. Subscribe to articles for update notifications. Key KB articles: 144456 (case management), 200997 (advanced search), 252162 (KB from case), 275360 (subscribe to KB).
Log Assist in VCF Operations console generates diagnostic log bundles. Prerequisites (VCF 9.0.1 docs p.3910-3912, Set up Log Assist): VCF Operations licensing registered in Connected Mode; Log Assist activated on a unified cloud proxy (Administration > Control Panel > Cloud Proxies > Activate Log Assist — Classic collectors are not supported); inventory objects assigned under Infrastructure Operations > Configurations > Log Assist Assignment. Supported objects: vCenter, ESX, NSX, SDDC Manager, VCF Operations, VCF Operations for logs, VCF Operations fleet management. Transfer to the Broadcom support case needs the support case ID (partners also give their partner ID). Workflow: select inventory objects → generate bundle (each object = separate task) → authenticate to the Broadcom Support Portal → provide the Support Case ID (partners also their partner ID) → transfer. Status tracked on Log Assist page. Also can upload directly via Wolken (KB 140731).
[HOLODECK NOTE] Log Assist bundle generation works in Holodeck — it collects logs from nested ESXi hosts and management appliances. However, the 'Transfer to Support Portal' step requires internet connectivity from the VCF Operations appliance. In air-gapped Holodeck environments, download the bundle locally and upload manually via the Broadcom support portal web interface. Bundle sizes from Holodeck are typically smaller than production (fewer hosts, less traffic) but the process is identical.
VCF Operations Log Analysis: log-based dashboards, saved queries, custom filters (criteria + grouping), visualization modes and chart types. Live monitoring for real-time analysis. Log-based alerts: configure proactive notifications for specific log patterns. Customizable charts for detailed visualization. Effective troubleshooting: identify issue → check relevant logs → cross-reference with KB articles → collect bundles → submit to support.
Validation Gate
Check: What are the four severity levels for Broadcom support cases?
Expected: P1: Production down, data loss risk (24×7 response). P2: Production degraded (business hours, urgent). P3: Partial impact, workaround exists (business hours). P4: General question, enhancement request (business hours).
Common Errors
Design Reflection (VCDX)
Support readiness is part of operational design. VCDX panelists may ask about your support engagement model: who files cases, what information is included, and how escalations are handled. This demonstrates operational maturity beyond initial deployment.
Requirements
- Understand Broadcom Wolken support portal and case management
- Know severity levels and appropriate classification
- Collect diagnostic bundles before support engagement
Constraints
- P1 cases require production impact justification
- Log bundles must be collected before service restarts
- Support portal access requires active support contract
Assumptions
- Active Broadcom support contract is in place
- Operations team has access to support portal and knows log collection procedures
Risks
- Delayed resolution from inadequate initial case information
- Evidence loss from restarting services before collecting logs
- Support contract lapse leaving production environment without vendor support
⚠ Known Pitfalls
References
- Broadcom Support PortalTier 1 — Official
- VMware to Broadcom Support Frequently Asked Questions (Broadcom KB 278681)Tier 1 — Official