Proactive Upgrade Case for TCP Environments
search cancel

Proactive Upgrade Case for TCP Environments

book

Article ID: 405897

calendar_today

Updated On:

Products

VMware Telco Cloud Platform

Issue/Introduction

Note: The proactive support process for Telco Cloud Platform (TCP) upgrade activities is limited to Advanced Support customers with a Support Account Manager (SAM) and/or Designated Support Engineer (DSE).

VMware by Broadcom Support will:

  • Assist in resolving any pre-check issues.
  • Review the MOP and offer feedback on any potential issues or concerns.
  • Validate the target upgrade version and advise on newer, or more applicable versions.
  • Once the review is completed, the TCP Proactive Upgrade Case will be closed.
  • Two days prior to upgrade window the SAM or DSE will open a Proactive Planned Activity Case to track the upgrade.

Environment

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

Resolution

Prerequisites for opening a Proactive TCP Upgrade Case:

  • Cases must be opened 10 business days prior to the planned upgrade window.
    • Less than 10 business days' notice may prevent timely review or pre-check resolution before your maintenance window.
  • Cases should be opened as a Low - P4.
  • Open one Proactive Case per TCP component involved in the activity.
  • Add all relevant stakeholders to the Additional CC list on the case.
  • Have a Method of Procedure (MOP) prepared and available for review.
  • Review the version-specific TCP Upgrade Guide available on the TCP TechDocs Page
  • For production environments, upgrade a staging environment first to confirm customization functionality with the target version.
  • Run pre-upgrade checks in advance and identify any unresolved issues.
  • Confirm that the planned upgrade path is officially supported.

Complete the following template when opening the Case:

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

Powered by Wolken Software