Contents

1   Introduction

This document contains information needed when upgrading the virtualized MTAS from 1.4.2 and 1.5.1 to 1.6.

This document is to be used when planning upgrades on customer sites.

1.1   Prerequisites

This section describes the prerequisites which must be fulfilled before the MTAS can be upgraded from 1.4.2 and 1.5.1 to 1.6.

1.1.1   Licenses

Ensure that the needed licenses are installed before the installation of the MTAS upgrade packages.

1.1.2   Update of Charging System

Update the charging system, if applicable, with the new charging XML files to prepare for the new charging AVPs and enumeration values.

Note:  

Use the described charging system instead of Multi-Mediation (MM) as the MTAS can interact with other types of charging systems.

To perform the charging system update, refer to MTAS Charging Management GuideMTAS Charging Management Guide, Reference [6].

For more details of the XML specifications, refer to the following files:

• MTAS, Communication Details, 3GPP R7 XMLMTAS, Communication Details, 3GPP R7 XML, Reference [5]
• MTAS, Offline Charging, 3GPP R7 MM XMLMTAS, Offline Charging, 3GPP R7 MM XML, Reference [11]
• MTAS, Offline Charging, 3GPP R9 MM XMLMTAS, Offline Charging, 3GPP R9 MM XML, Reference [12]
• MTAS, Offline Charging, 3GPP R12 MM XMLMTAS, Offline Charging, 3GPP R12 MM XML, Reference [13]
• MTAS, Online Charging, 3GPP R7 MM XMLMTAS, Online Charging, 3GPP R7 MM XML, Reference [14]
• MTAS, Online Charging, 3GPP R9 MM XMLMTAS, Online Charging, 3GPP R9 MM XML, Reference [15]
• MTAS, Online Charging, 3GPP R12 MM XMLMTAS, Online Charging, 3GPP R12 MM XML, Reference [16]

1.1.3   Hardware and Software Required

This section describes the required hardware and software.

Note:  

Later EP deliveries can be used as from state and are found in the Product Revision Information (PRI).

Network Element Version

This instruction applies to the following Network Elements (NEs):

• MTAS 1.4.2: CXP9025660/9 R5G03
• MTAS 1.5.1: CXP9025660/9 R6F02

Hardware Configurations

The supported Hardware (HW) configurations are as follows:

• Virtualized MTAS can run on any hardware supported by the hypervisor.

From Software Configuration States

• vMTAS 1.4.2: CXP9025660/9 R5G03

  Component Level

  • LDEwS, CXP 902 0125/4, R2B04
  • LDE BRF SCRIPT, CXP 902 1148/2, R3A03
  • Core MW, CXP 902 0355/2, R2B06
  • Core MW BRF-C, CXP 901 8859/2, R2B06
  • Core MW BRF-EIA, CXP902 4651/2, R2B06
  • Trace CC, CXP 902 0582/3, R2B01
  • Trace EA, CXP 902 1069/3, R2B01
  • COM, CXP 901 8493/2, R1C01
  • eVIP, CXP 902 0395/3, R2B02
  • SS7 CAF, CXP 902 9429/5, R1B07
  • SEC_Cert, CXP 902 7891, R2C
  • SEC_Crypto, CXP 902 7895, R2C
  • SEC_ACS, CXP 902 6450, R2C
  • SEC_LA, CXP 902 6994, R2C
  • SEC_SecM, CXP 902 8976, R1C
  • SEC_LDAP, CXP 902 8981, R1C
  • LM, CXP9020396/5, R2A
  • LM SENTINEL, CXP9027034/5, R2A
  • LM SA, CXP 902 1377/2, R2A
  • JavaOaM, CXP 902 0490/2, R2B
  • MMAS, CXP 904 0026/5, R2A
  • MMAS EAP, CXP 904 0550/5, R2A
  • MMAS JDK, CXP 904 0510/5, R2A
  • MMAS Tomcat, CXP 904 0580/5, R2A
  • vDicosEE, CXP9025265/4, R2A195
  • DBS, CXP 902 5264/5, R2B09
  • LEM, CXP9025257/4, R2A206
  • IMS CMCO AAA FW, CXP9023222/1, R7A01
  • IMS CMCO CTL, CXA1105679/1, R7A01
  • IMS CMCO IMS FW, CXP9023164/1, R7C01
  • IMS CMCO REGEX, CXA1105678/1, R6A01
  • IMS CMCO CMCO utilities, CXP9020686/1, R7A01
  • IMS CMCO LI, CXP9031413/1, R6D01
• vMTAS 1.5.1: CXP9025660/9 R6F02

  Component Level

  • LDEwS, CXP 902 0125/4, R2C03
  • LDE BRF SCRIPT, CXP 902 1148/2, R3A03
  • Core MW, CXP 902 0355/2, R2F01
  • Core MW BRF-C, CXP 901 8859/2, R2F01
  • Core MW BRF-EIA, CXP902 4651/2, R2F01
  • Trace CC, CXP 902 0582/3, R2B01
  • Trace EA, CXP 902 1069/3, R2C01
  • COM, CXP 901 8493/2, R1C01
  • eVIP, CXP 902 0395/3, R2B02
  • SS7 CAF, CXP 902 9429/5, R1B07
  • SEC_Cert, CXP 902 7891, R2C
  • SEC_Crypto, CXP 902 7895, R2C
  • SEC_ACS, CXP 902 6450, R2C
  • SEC_LA, CXP 902 6994, R2C
  • SEC_SecM, CXP 902 8976, R1C
  • SEC_LDAP, CXP 902 8981, R1C
  • LM, CXP9020396/5, R2B
  • LM SENTINEL, CXP9027034/5, R2B
  • LM SA, CXP 902 1377/2, R2B
  • JavaOaM, CXP 902 0490/2, R2B
  • MMAS, CXP 904 0026/5, R2B
  • MMAS EAP, CXP 904 0550/5, R2B
  • MMAS JDK, CXP 904 0510/5, R2B
  • MMAS Tomcat, CXP 904 0580/5, R2B
  • vDicosEE, CXP9025265/4, R2D03
  • DBS, CXP 902 5264/5, R2B09
  • LEM, CXP9025257/4, R2C15
  • IMS CMCO AAA FW, CXP9023222/1, R8A01
  • IMS CMCO CTL, CXA1105679/1, R7B01
  • IMS CMCO IMS FW, CXP9023164/1, R8A01
  • IMS CMCO REGEX, CXA1105678/1, R7A01
  • IMS CMCO CMCO utilities, CXP9020686/1, R7C01
  • IMS CMCO LI, CXP9031413/1, R7C01

To Software Configuration States

• MTAS 1.6: CXP9025660/9 R7E02

  Component Level

  • LDEwS, CXP 902 0125/4, R3B05
  • LDE BRF SCRIPT, CXP 902 1148/2, R4B01
  • Core MW, CXP 902 0355/2, R3D38
  • Core MW BRF-C, CXP 901 8859/2, R3D38
  • Core MW BRF-EIA, CXP902 4651/2, R3D38
  • Trace CC, CXP 902 0582/3, R3A44
  • Trace EA, CXP 902 1069/3, R3A20
  • COM, CXP 901 8493/2, R2A51
  • eVIP, CXP 902 0395/3, R3A219
  • SS7 CAF, CXP 902 9429/5, R2C08
  • SEC_Cert, CXP 902 7891, R3C
  • SEC_Crypto, CXP 902 7895, R3D
  • SEC_ACS, CXP 902 6450, R3D
  • SEC_LA, CXP 902 6994, R3D
  • SEC_SecM, CXP 902 8976, R2D
  • SEC_LDAP, CXP 902 8981, R2D
  • LM, CXP9020396/5, R2B
  • LM SENTINEL, CXP9027034/5, R2B
  • LM SA, CXP 902 1377/2, R2A
  • JavaOaM, CXP 902 0490/2, R3A
  • MMAS, CXP 904 0026/5, R3A
  • MMAS EAP, CXP 904 0550/5, R3A
  • MMAS JDK, CXP 904 0510/5, R3A
  • MMAS Tomcat, CXP 904 0580/5, R3A
  • vDicosEE, CXP9025265/4, R3C03
  • DBS, CXP 902 5264/5, R4A353
  • LEM, CXP9025257/4, R3A203
  • IMS CMCO AAA FW, CXP9023222/1, R8A01
  • IMS CMCO CTL, CXA1105679/1, R7B01
  • IMS CMCO IMS FW, CXP9023164/1, R8A01
  • IMS CMCO REGEX, CXA1105678/1, R7A01
  • IMS CMCO CMCO utilities, CXP9020686/1, R7C01
  • IMS CMCO LI, CXP9031413/1, R7F01

1.1.4   Documents

Before starting this procedure, ensure that the following information or documents are available:

• Information (facts) as, node name, software version, platform, operating system, and hardware.
• Information about IP addresses, usernames and passwords, how to collect data and log files, refer to Data Collection Guideline for MTASData Collection Guideline for MTAS, Reference [2].
• Information about the Ericsson Command-Line Interface (ECLI), refer to Ericsson Command-Line Interface User GuideEricsson Command-Line Interface User Guide, Reference [3].
• Information about the Managed Object Model (MOM), refer to Managed Object Model (MOM)Managed Object Model (MOM), Reference [4].

• Some of the recovery steps require physical access to the nodes for pressing buttons, replacing hardware, and so on. For information on physical access and handling, refer to MTAS Health CheckMTAS Health Check, Reference [8].

1.1.5   Tools

The following tool must be available before performing any procedure in this document:

• A workstation (laptop) with SSH and SCP or FTP client, and a NETCONF browser.

1.1.6   Conditions

The following conditions must apply:

• Verify that the Node Hardening is done and <maintenance_user> user/password and root password are available.
• The upgrade is supported with a 30% average CPU load traffic limit on the Pay Load Blades.
• An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.

1.1.7   Prerequisites for Upgrading MTAS with Network Redundancy

1. The IMS network must be configured for AS failover. That is the AS FQDN has to have at least two DNS entries, one per used MTAS. For information on how to configure MTAS for Dynamic Allocation, refer to sections Configuration for Dynamic Allocation and DNS Based Redundancy and Load Sharing of External Server Nodes in MTAS External Network ConfigurationMTAS External Network Configuration, Reference [7].
2. Verify that the intended secondary MTAS nodes are operational by following the MTAS Health Check procedure, refer to MTAS Health CheckMTAS Health Check, Reference [8].
3. Verify that the intended secondary MTAS nodes are configured properly, meaning that the suggested number of Sh, Rf, and Ro Diameter applications connections towards each Diameter application peer node is equal to the minimum number of Traffic Processors – between MTAS and the Peer Node.

1.2   Limitations

The following limitations apply:

• Provisioning is not allowed during the upgrade as configuration changes during upgrade can cause problems.
• It is not supported to use AppTrace during software upgrade.
• Subscriber Data query or purge operations are not supported during upgrade.

2   Upgrade Overview

This section describes the upgrade, and a possible rollback, from an impact point of view.

Lead Time

For information about lead times (minutes) for the MTAS upgrade, see Table 1 and Table 2.

Table 1    Overall Lead Time for MTAS Upgrade without Network Redundancy

	2+2	2+4	2+10
Pre-Upgrade	60 minutes	60 minutes	60 minutes
Upgrade	60 minutes	150 minutes	210 minutes
Post-Upgrade	30 minutes	30 minutes	30 minutes

Table 2    Overall Lead Time for MTAS Upgrade with Network Redundancy

	2+4	2+10
Pre-Upgrade	60 minutes	60 minutes
Upgrade(1)	40 minutes	40 minutes
Post-Upgrade	30 minutes	30 minutes

(1)  In case of network redundancy, the time may increase with 15-30 minutes since the graceful shutdown of the MTAS depends on ongoing calls.

Down Time

No down time is expected during the upgrade.

Traffic Loss

During the upgrade the following traffic loss is expected:

• Rejected traffic: None

  Three Party (3PTY) sessions and conferences are lost.

• Disconnected traffic: None

Service Disturbances

Stable calls stay connected during the upgrade.

2.1   Impact of Upgrade

This section describes the impact of the upgrade.

Operation and Maintenance

The upgrade has the following impact on the operation and maintenance of the system:

• Alarms

  There are no alarms.

• Counters

  The error counters are expected to increase during the upgrade.

Provisioning

Provisioning is not supported during the upgrade.

Charging

No impact.

Security

Security is not treated in this document.

End Terminals

No impact.

Database Handling

No impact.

Dependencies to Other Nodes

This subsection describes the impact on the dependencies to other nodes during the upgrade.

The external interfaces are impacted as follows by the upgrade:

For more information about new, modified, obsolete, or temporary parameters during the upgrade, refer to vMTAS Network Impact Report from 1.4 to 1.6vMTAS Network Impact Report from 1.4 to 1.6, Reference [9] and vMTAS Network Impact Report from 1.5 to 1.6vMTAS Network Impact Report from 1.5 to 1.6, Reference [10].

Other Impacts

No other impacts.

2.2   Impact of Rollback

This section describes the impact of a possible rollback, in case the upgrade is not concluded in a satisfactory manner.

When restoring the backup, a cluster reboot is automatically triggered.

Traffic Loss

Traffic loss is expected during the cluster reboot, unless upgrade is performed with Network Redundancy.

Service Disturbances

Service disturbance is expected during the cluster reboot, unless upgrade is performed with Network Redudancy.

Provisioning

Provisioning is not supported during the upgrade.

Charging

Charging information is not generated during the cluster reboot.

Security

Security is not treated in this document.

End Terminals

No impact.

Database Handling

No Impact.

Rollback Dependencies on Interaction with Other Nodes

The rollback has no impact on the external interfaces.

The rollback has no impact on the backward compatibility.

Note:  

Roll back any attribute modification performed on other nodes in preparation for the upgrade, to prevent possible conflicts.

Other Impacts

No impact.

3   Parameter Changes

For information about new, modified, obsolete, or temporary parameters during the upgrade, refer to vMTAS Network Impact Report from 1.4 to 1.6vMTAS Network Impact Report from 1.4 to 1.6, Reference [9] and vMTAS Network Impact Report from 1.5 to 1.6vMTAS Network Impact Report from 1.5 to 1.6, Reference [10].

Reference List

Ericsson Documents
[1] Glossary of Terms and Acronyms, TERMINOLOGY, 1/0033-AVA 901 29/9
[2] Data Collection Guideline for MTAS, OPERATING INSTRUCTIONS, 70/1543-AVA 901 29/9
[3] Ericsson Command-Line Interface User Guide, USER GUIDE, 1/1553-APA 901 44/1
[4] Managed Object Model (MOM) MANAGED OBJECT MODEL, 155 54-LZN 765 0163/9-V1
[5] MTAS, Communication Details, 3GPP R7 XML, PROCESSING SPEC. 4/190 04-AVA 901 18
[6] MTAS Charging Management Guide, OPERATING INSTRUCTIONS, 3/1553-AVA 901 29/9
[7] MTAS External Network Configuration, USER GUIDE, 43/1553-AVA 901 29/9
[8] MTAS Health Check, OPERATING INSTRUCTIONS, 53/1543-AVA 901 29/9
[9] vMTAS Network Impact Report from 1.4 to 1.6, NETWORK IMPACT REPORT, 19/10948-AVA90129/9-5
[10] vMTAS Network Impact Report from 1.5 to 1.6, NETWORK IMPACT REPORT, 20/10948-AVA90129/9-5
[11] MTAS, Offline Charging, 3GPP R7 MM XML, TECHNICAL DOCUMENT, 2/190 04-AVA 901 18
[12] MTAS, Offline Charging, 3GPP R9 MM XML, TECHNICAL DOCUMENT, 5/190 04-AVA 901 18
[13] MTAS, Offline Charging, 3GPP R12 MM XML, TECHNICAL DOCUMENT, 15/190 04-AVA 901 18
[14] MTAS, Online Charging, 3GPP R7 MM XML, TECHNICAL DOCUMENT, 3/190 04-AVA 901 18
[15] MTAS, Online Charging, 3GPP R9 MM XML, TECHNICAL DOCUMENT, 6/190 04-AVA 901 18
[16] MTAS, Online Charging, 3GPP R12 MM XML, TECHNICAL DOCUMENT, 16/190 04-AVA 901 18
[17] Trademark Information, LIST, 2/006 51-AVA 901 29/9
[18] Typographic Conventions, DESCRIPTION, 1/1551-FCK 101 05

Other References
[19] SW Gateway. https://swgateway.ericsson.net/