Proactive Upgrade Case for Aria Operations for Networks
search cancel

Proactive Upgrade Case for Aria Operations for Networks

book

Article ID: 375617

calendar_today

Updated On:

Products

VCF Operations for Networks

Issue/Introduction

Note: The Proactive Upgrade process for Aria Operations for Networks is limited to Advanced Support customers with a Support Account Manager (SAM) and/or Dedicated Technical Support Engineer (DTSE). 

Prerequisites to be followed before opening proactive Aria Operations for Networks (AON) upgrade Cases:

  1. Cases must be opened 10 business days in advance of the upgrade window.
  2. Cases should be opened as Severity 4.
  3. Read the target version of the release notes and be aware of known issues.
  4. Confirm the target Aria Operations for Networks version is compatible with other products in the environment. Also, confirm the Aria Operations for Networks upgrade path is supported. Refer to the Upgrade Path page of the Interoperability Matrix.
  5. Validate Aria Operations for Network backups are being taken. Follow this article for Best practices to shutdown Aria Operations for Networks Clustered deployments
  6. If a bespoke upgrade runbook is being followed, ensure it is aligned with the official Upgrade documentation. 
  7. Broadcom advises to upgrade to the latest available or n-1 version(s). 
  8. For issues fixed and known issues, see the Release Notes for more information for those versions.

VMware by Broadcom Support will: 

  1. Validate the target version and advise if a newer one is available. 
  2. Validate upgrade path.

Please complete the following template when opening the Case: 

  1. Upgrade Date & Time:
  2. Aria Operations for Networks current running version:
  3. Aria Operations for Networks upgrade to version:
  4. VCF version (if applicable):
  5. Aria Suite Lifecycle Manager (vRSLCM) environment (if applicable):
  6. On Aria Operations for Networks GUI, navigate to Settings > Infrastructure and support > Infrastructure and updates page. From this page, take 1-2 screenshots covering the entire page. If you see any problems, click on them and capture additional screenshots showing all the problems.

    Note: After support engineer has reviewed the template, further information might be requested from the deployment (screenshots, command outputs, support bundles, etc.)
Upgrade Recommendations:
  1. Backup and snapshot of the environment following this article: Backup/Snapshot clustered deployments. 
  2. Prepare a contingency plan to allow the upgrade maintenance window to be extended should a failure occur.
  3. Schedule a maintenance window for the entire upgrade so that VMs can be powered off to make cold snapshots/backups. Make sure there are good backups just prior to the upgrade.  
  4. If an upgrade failure occurs, please request an uplift in case severity of the maintenance case that was created by your SAM.
  5. As part of the recent updates, the Online Upgrade option is no longer available following the Broadcom Migration. Moving forward, the only available upgrade method is the Single Click Offline Upgrade. This can be toggled off via the GUI.
  6. Back to back upgrades for Aria Operations for Networks on the same day is not recommended. There should be a minimum gap of 8-10 hours between upgrade operations.

Environment

Aria Operations for Networks 6.12.0
Aria Operations for Networks 6.12.1
Aria Operations for Networks 6.13.0
Aria Operations for Networks 6.14.0
Aria Operations for Networks 6.14.1

Resolution

This is not an exhaustive health check of the environment, if this is required please engage VMware by Broadcom Professional Services. Broadcom Support

Please Note:
Broadcom Support will not be able to provide dedicated support to be on standby during the maintenance window.  If you experience issues during your scheduled change, please reach out on the maintenance case created by your SAM, request an uplift in severity and the next available technical support engineer will contact you.

Additional Information