Planned Activity Precheck Review Case for TCP Environments
search cancel

Planned Activity Precheck Review Case for TCP Environments

book

Article ID: 405897

calendar_today

Updated On:

Products

VMware Telco Cloud Platform

Issue/Introduction

Note: The Planned Activity Precheck Review outlined in this KB is available only to Advanced Support customers with a Support Account Manager (SAM) and/or Dedicated/Designated Support Engineer (DTSE/DSE). 

The Planned Activity Precheck Review is provided on a best effort basis and is intended to assist with identified issues and precheck failures. While Broadcom Support strives to highlight potential risks, this review is not exhaustive and may not identify all issues or environment-specific considerations. It is not a commitment to participate during the planned activity nor is it a certification or validation of a runbook. The customer remains responsible for validating their activity plan and ensuring their environment if fully prepared for the change. 

VMware by Broadcom Support will: 

  • Confirm the target version and advise if a newer one is available.
  • Review identified precheck issues and advise on necessary resolutions.
  • Once the Planned Activity Precheck Review is complete, the case will be closed.
  • Two days prior to the activity, SAM/DTSE/DSE will open a Proactive Planned Activity Case for TCP Environments to track the activity.
    • Please note that Broadcom cannot provide dedicated standby support during the activity.
    • However, in the event of a production-down outage, the next available support engineer will be engaged promptly. 

Environment

2.x, 3.x, 4.x, 5.x

Cause

N/A

Resolution

Prerequisites before opening a Planned Activity Precheck Review for TCP:

  • Run pre-upgrade checks in advance and identify any unresolved issues.
  • Confirm that the planned upgrade path is officially supported.
  • Review the version-specific TCP Upgrade Guide available on the TCP TechDocs Page
  • For production upgrades, upgrade a staging environment to ensure customizations function correctly on the target version.
  • Execute per TCP component pre-upgrade checks in advance to identify any outstanding issues.
  • Open a separate Low-P4 Planned Activity Precheck Review case for each TCP component involved in the activity.
  • Submit cases at least 10 business days prior to the scheduled activity window.
    • Fewer than 10 business days' notice may impede timely review or resolution before the activity window.

Please complete the following template when opening the Case:

0. Output of pre-upgrade checks

    • Attached Artifact(s): Specify the file name(s) attached to the case
      • e.g., NSX_Precheck_Report.csv, TCA_Test_Summary.png, vLCM_Compliance_Scan.pdf
    • Pre-Check Status: Pass / Warn / Fail
    • List any warnings that are expected and acknowledged
      • e.g., Storage usage at 82%, threshold is 80% - safe to proceed. 

1. Change Overview / Scope:

    • Change Type: Patch / Upgrade / Update
    • Versions: (Current to Target)
      • TCP Version: Example: TCP 4.0 to 5.0.1
      • Component (Product) Version: Example: NSX 4.1.1.1 to 4.2.1.6
    • Scheduled Date and Time:

2. Site Location / OpCo:

    • Architecture Type: Example: Single-site, Redundant-site, Management Domain, Workload Domain
    • Impacted Network Functions and/or Subscriber Base.
    • Timeline / Sequence:
    • Upgrade Path Confirmed as Supported by TCP TechDocs Page: Yes / No
    • Component-Specific Sequence and Timing Provided: Yes / No

3. Inventory

    • Components, Hostnames, IP Addresses, FQDNs, Current Builds, Target Builds
    • Client Plugins and Extensions:
    • Content Packs / Management Packs:
    • Third-Party Integrations or Custom Scripts (if any):
    • Firmware and Driver Compatibility Confirmed: Yes / No

4. Interoperability

5. Backup

    • Backup of Environment Components Completed: Yes / No / Planned
    • Backup Type: Snapshot / Image / Configuration Export
    • Backup Tool Used:
    • Backup Completion Date:
    • Backup Integrity Verified: Yes / No

6. Documentation

    • Method of Procedure (MOP) Available: Yes / No
    • Runbook Finalized: Yes / No
    • Rollback Plan Defined: Yes / No

7. Stakeholder

    • Primary Stakeholders Identified and Notified: Yes / No
    • Escalation Contact Matrix Aligned with Change Window: Yes / No

Additional Information

If an exhaustive health check of the environment is required, please engage VMware by Broadcom Professional Services.

For further Planned Activity Precheck Review guidance, please see the Planned Activity Precheck Review - Broadcom Advanced Support KB