<!---
Copyright (c) Alianza, Inc. All rights reserved.
Highly Confidential Material
-->

|**Metadata**|**Description**  |
|--|--|
|Doc Title|  MVM v3 LEA: Release {{ DOWNLEVEL_MVM_VERSION | default('<DOWNLEVEL_MVM_VERSION>') }} to Release {{ UPLEVEL_MVM_VERSION | default('<UPLEVEL_MVM_VERSION>') }} Upgrade Overview|
|Navigation|[WIKI Home Page](https://dev.azure.com/mvmprodeus2/MVM/_wiki/wikis/documentation/1/documents-home#)|
|Tracking| Document Number: VPE-5512-500|
|Author| Graeme Thomson (gt163y) |
| Agreement Number | 24252.S.005 |


**Notices**

Copyright &copy; 2025 Metaswitch Networks.  All rights reserved.

This manual is Confidential Information of Metaswitch Networks subject to the confidentiality terms
of the Agreement 01019223 as amended between AT&amp;T and Metaswitch Networks.

It is issued on the understanding that no part of the product code or documentation (including this manual)
will be copied or distributed without prior agreement in writing from Metaswitch Networks and Alianza.

Metaswitch Networks and Alianza reserve the right to, without notice, modify or revise all or part of
this document and/or change product features or specifications and shall not be responsible for any
loss, cost, or damage, including consequential damage, caused by reliance on these materials.

Metaswitch and the Metaswitch logo are trademarks of Metaswitch Networks. Other brands and
products referenced herein are the trademarks or registered trademarks of their respective holders.

Product(s) and features documented in this manual handle various forms of data relating to your
users. You must comply with all laws and regulations applicable to your deployment, management,
and use of said product(s), and you should take all appropriate technical and organizational
measures to ensure you are handling this data appropriately according to any local legal and
regulatory obligations.

You are responsible for determining whether said product(s) or feature(s) is/are appropriate for
storage and processing of information subject to any specific law or regulation and for using said
product(s) or feature(s) in a manner consistent with your own legal and regulatory obligations. You
are also responsible for responding to any request from a third party regarding your use of said
product(s), such as a request to take down content under the U.S. Digital Millennium Copyright Act
or other applicable laws.


Metaswitch Networks
399 Main Street
Los Altos
CA 94022
<http://www.metaswitch.com>


***
***Table of Contents***
[[_TOC_]]


# Document History

| **Issue** | **Issue Date** | **Author(s)** | **Identification** **of** **Changes** |
|-|-|-|-|
| 1 | 12/05/2025 | gt163y | Initial version |


# 1. Introduction

This document serves as an overall guide to the set of MOPs required to upgrade an
existing LEA deployment of MVM on Azure (also known as MVM v3) from Release **{{ DOWNLEVEL_MVM_VERSION | default('<DOWNLEVEL_MVM_VERSION>') }}** to Release **{{ UPLEVEL_MVM_VERSION | default('<UPLEVEL_MVM_VERSION>') }}**.

It includes a list of MOPs to run, in order. Use this as a reference to know when to run each of the individual MOPs included.

# 2. List of MOPs

The following MOPs must be followed to upgrade the deployment from Release **`{{ DOWNLEVEL_MVM_VERSION | default('<DOWNLEVEL_MVM_VERSION>') }}`** to Release **`{{ UPLEVEL_MVM_VERSION | default('<UPLEVEL_MVM_VERSION>') }}`**.

>Note that the MOPs ***must*** be run in the order listed.

## 2.1 Upgrade resources on all regions in the deployment

***
These MOPs ***must*** be run on all regions before proceeding with the subsequent steps
***


**Upgrade the Azure pipelines**



- **Upgrade the pipeline software** [*R1154LEAupgradeADOPipelineResources*](r1154leaupgradeadopipelineresources.md)

  - No new variables have been added to the pipeline configuration file.



  - No existing variables have been removed from the pipeline configuration file.



  - No additional secrets need to be added to the deployment wide variable group.



  - No additional secrets need to be added to the regional variable group.



- **Upgrade the Self-hosted Agents** [*R1154LEAupgradeSelfHostedAgentVM*](r1154leaupgradeselfhostedagentvm.md)

  - A new pipeline configuration file is NOT required.



**Upload new release artifacts** [*R1154LEAUploadArtifacts*](r1154leauploadartifacts.md)


## 2.2 Upgrade the deployment wide resources

**Upgrade mvm-config-manager** [*R1154LEAupgradeConfigManager*](r1154leaupgradeconfigmanager.md)

>This step can be skipped if the same configuration manager is to be used for both
the main and LEA deployments



**Upgrade the deployment wide prerequisites** [*R1154LEAUpgradeDeploymentPrereqs*](r1154leaupgradedeploymentprereqs.md)

***
**This MOP must be run in a Maintenance Window in a production environment**
***

  - No new variables have been added to the deployment prerequisites tfvars file.



  - No existing variables have been removed from the deployment prerequisites tfvars file.


  - No additional secrets need to be added to the deployment wide variable group.



## 2.3  Upgrade the region specific resources

***
***The first region to be upgraded must be the deployment region***
***

**Upgrade region prerequisites** [*R1154LEAUpgradeRegionalPrereqs*](r1154leaupgraderegionalprereqs.md)

***
**This MOP must be run in a Maintenance Window in a production environment**
***

- No new variables have been added to the regional prerequisites tfvars file.


- No existing variables have been removed from the regional prerequisites tfvars file.


- No additional secrets need to be added to the regional variable group.



**Prepare the up-level config repository** [*R1154LEAupgradeConfiguration*](r1154leaupgradeconfiguration.md)

- The value to use for **DOWNLEVEL_MVM_VERSION** is `{{ DOWNLEVEL_MVM_VERSION | default('<DOWNLEVEL_MVM_VERSION>') }}`.

- The value to use for **UPLEVEL_MVM_VERSION** is `{{ UPLEVEL_MVM_VERSION | default('<UPLEVEL_MVM_VERSION>') }}`.

- No new variables have been introduced in this release.


- No existing variables have been retired in this release.



- No existing variables need to be updated.



- No configuration needs to be specified in the file perimeta-config. Ensure that it is set to:
  ```
  # Copyright (c) Alianza, Inc. All rights reserved.
  # Highly Confidential Material
  #
  # WARNING: Modifications to this file may cause your deployment to break.
  #
  # Changes should not be made without consulting your Support representative, and must
  # be done by following the process for updating a Service Instance by replacement.
  ```


- There are no new secrets introduced in this release.


**Upgrade the SIMPL cluster** [*R1154LEAUpgradeSimplCluster*](r1154leaupgradesimplcluster.md)

- The version of SIMPL for this release is `{{ UPLEVEL_SIMPL_VERSION | default('<UPLEVEL_SIMPL_VERSION>') }}`.

  - A new pipeline configuration file is NOT required.



**Upgrade the SIMon SIs** [*R1154LEAUpgradeSIMon*](r1154leaupgradesimon.md)
***
**In a production environment, the first SIMon SI upgrade in this deployment must be carried out during a maintenance window.**
***


**Upgrade SAS SIs** [*R1154LEAUpgradeSAS*](r1154leaupgradesas.md)


**Upgrade ESC SIs** [*R1154LEAUpgradeESC*](r1154leaupgradeesc.md)

- When running this MOP the following sections should be ignored. These cover enabling
  OBER Monitoring which is currently disabled.

  - *Implementation: Enable automatic prioritization for the uplevel ESC*

  - *ESC Verification: Verify that the ESC is processing synthetic traffic*

- Note that in the traffic-moving and verification steps, fewer traffic weightings need be used for SIs
  after the first SI has been verified. For example, you might choose weightings of "10", "50", "500", and finally "1000".

  Make sure to decrease the weight of the down-level SIs as you increase the weight of the up-level SIs, to keep the weighting
  across the two at 1000 at all times.


**Upgrade the Tooling VMs and CLI tools** [*R1154LEAUpgradeToolingVM*](r1154leaupgradetoolingvm.md)

  - A new pipeline configuration file is NOT required.




**Delete down level resources**

To avoid data/function loss certain downlevel resources cannot be deleted when the
corresponding uplevel resource is created. Deletion of these resources is instead
consolidated at the end of upgrade process.

- **Delete the down-level SASs** [*R1154LEADeleteSAS*](r1154leadeletesas.md)

  To avoid loss of SAS records, the downlevel SAS SI can only be tidied up when
  the alert SasSiUnused is raised for the SAS. This can occur at different times
  for different downlevel SAS SIs.


## 2.4 On-premise Perimetas

The configuration for upstream on-premise Perimetas must be checked against the
settings documented in section 4.2.15 of the Deployment Guide.