8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
1/120
2012 Avaya Inc. iAvaya proprietaryuse pursuant to company instructions
102.2.3 AS 5300 3.0 - 2.0 to 3.0 SIP CORE UpgradeMethod of Procedure
Product Release: AS 5300 R3.0
Document Version: 2.6
Document Status: Released
Document Release Date: March 14, 2012Security Classification: Avaya Confidential
Copyright 2012 AvayaAll rights reserved.
Avaya CONFIDENTIAL: The information contained in this document is the property of Avaya. Except asspecifically authorized in writing by Avaya, the holder of this document shall keep the information containedherein confidential and shall protect same in whole or in part from disclosure and dissemination to third partiesand use same for evaluation, operation, and maintenance purposes only.
AvaAvaya Application rver 5300 R3.0Ava
tion SrvAvaya Application Server 5300 R3.0Ava
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
2/120
2012 Avaya Inc. iAvaya proprietaryuse pursuant to company instructions
Revision History
Version Date Description
0.0 November 3, 2010 Initial Draft
0.1 December 13, 2010 Removed Online Help installation
0.2 March 1, 2011 Removed Oracle Database installation
0.3 March 15, 2011 Added IPCM Decommissioning steps
0.4 April 1, 2011 Added new required steps for SM console launch
0.5 April 12, 2011 Modified step 12b inTable 4
0.6 April 28, 2011 Modified Step 7 in Table 1
0.7 May 4, 2011 Updated Software load Protal link
0.8 May 5, 2011 Added new required steps for Half Rollback
0.9 June 30, 2011 Added new required steps for Full Rollback
1.0 July 29, 2011` Added SM Renaming steps
1.1 August 8,2011 Updated SM Renaming steps
1.2 August 10,2011 Updated screen captures, table of contents etc..
1.3 August 12, 2011 Updated Rollback section
1.4 August 17, 2011 Updated R3.0 naming. Replace MCP Management Consolewith AS 5300 Element Manager Console. Replaced AMSwith Avaya MS, replaced SESM with AS 5300 SESM
1.5 August 25, 2011 Updated Table 10 for System Rollback
1.6 Sept ember 10, 2011 Updated Rollback Section
1.7 September 15, 2011 Updated after MOP review
1.8 September 20, 2011 Updated Audiocodes Firmware Upgrade
1.9 October 1, 2011 Updated SM Renaming steps
2.0 Oct 14, 2011 Updated document number, rollback section, and AudioCodesection
2.1 Oct 28, 2011 Changed MCP 15.0 to MCP 15.1, and more updates as perreview comments
2.2 Nov 7, 2011 Added IPv6 manual upgrade instructions
2.3 Nov 18, 2011 Updated as per review comments from AvayaGov Training.
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
3/120
2.6Method of Procedure
2012 Avaya Inc. iiAvaya proprietaryuse pursuant to company instructions
Version Date Description
Added instructions to access EM console in FIPS compliantmode after upgrade.
Updated Data Changes section.
2.4 January 25, 2012 Changed title bar to Avaya Application Server 5300
Changed instances of AS5300 to AS 5300
Changed product reference of MCP 13.0 to AS 5300 2.0
Changed product reference of MCP 15.1 to AS 5300 3.0
Inserted step 17 in table 4
Changed diagrams to relect the Element Manager Console
2.5 Feb 8, 2012 Updated patching related information
2.6 March 14, 2012 Updated Prep Steps
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
4/120
2012 Avaya Inc. iiiAvaya proprietaryuse pursuant to company instructions
Table of Contents
1 Upgrade AS 5300 2.0 Release to 3.0.......................................................................... 1
1.1
Notes for upgrading from the AS 5300 2.0 Release ........................................................ 1
1.2 Conceptual view of the Upgrade Process............................................................................... 3
1.3 Options to upgrade over multiple Maintenance Windows ................................................ 4
2 Preparatory Steps..................................................................................................... 6
3 Process to Upgrade AS 5300 2.0 to 3.0 ............................................................ 19
3.1
Upgrading a Redundant System......................................................................................... 19
3.2 Steps to Update the License Key........................................................................................ 46
3.3 Steps to find/stop/undeploy Primary/Stand-by NEs........................................................... 49
3.3.1
Steps to Stop a given NE Instance ....................................................................... 52
3.3.2 Steps to Undeploy a given NE Instance ............................................................... 54
3.4 Config Data changes that may be required.......................................................................... 56
3.4.1 Directory Change for Records on OSS Server............................................................ 56
3.4.2 Config Data Changes............................................................................................... 56
3.5
Provisioning Data changes that may be required after the Database Upgrade.......................... 58
4 Definitions & Abbreviations................................................................................... 59
4.1 External Documents Referenced......................................................................................... 60
5
Appendix A: MAS Upgrade Notes.......................................................................... 61
5.1 MAS Platform Upgrade (13.0 to 15.1)................................................................................ 61
5.2 MAS Platform Rollback (15.1 to 13.0)................................................................................ 61
6 Appendix C: Example installprops file................................................................... 62
7 Appendix D: MCP SM/EM CONSOLE Notes....................................................... 64
7.1 Install/launch the MCP SM/EMCONSOLE......................................................................... 64
7.2
Deploy/start a Network Element (NE) ............................................................................ 67
7.3
UserForced Out msg or Unable to launch MCP Mgmt Console................................. 71
8
Appendix E: Installing OnlineHelp files................................................................. 73
8.1
Install the AS 5300 2.0 OnlineHelp files ......................................................................... 73
9 Appendix F: Installing ASU files............................................................................. 75
9.1 Installing Client ASU files ............................................................................................... 75
9.1.1 Installing 8.1 Hardened Client ASU files on the AS 5300 3.0 Server........................... 75
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
5/120
2.6Method of Procedure
2012 Avaya Inc. ivAvaya proprietaryuse pursuant to company instructions
9.1.2 Installing 7.2 Hardened Client ASU files on the MCP Server...................................... 76
10 Appendix G: Upgrade AudioCodes to its latest MR............................................... 78
11 Appendix H: Rollback Steps................................................................................... 79
11.1 Rollback one half of an upgraded system ...................................................................... 79
11.2 Rollback an entire system .............................................................................................. 86
12 Appendix I: Applying a MCP Patch..................................................................... 103
12.1 Patch the Database Schemas and System Manager............................................................. 103
12.2
Patch Network Elements.................................................................................................. 104
12.2.1 Service Issues .................................................................................................... 104
12.2.2 Perform the Patch.................................................................................................. 105
13 Appendix J: 13.0 Patch current determination..................................................... 110
14
Appendix L: Retrieving the MCP License Key..................................................... 111
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
6/120
2012 Avaya Inc. vAvaya proprietaryuse pursuant to company instructions
List of FiguresFigure 1: Small (2 server) SIP Core configuration .......................................................................... 20
Figure 2: Medium (4 server) SIP Core configuration ..................................................................... 20
Figure 3: Large (8 server) SIP Core configuration ......................................................................... 21
Figure 4: Management Console License Key Invalid Alarm .......................................................... 46
Figure 5: Management Console Update License Key Right-Click Option ...................................... 47
Figure 6: Management Console Update License Key Window ...................................................... 48
Figure 7: Management Console License Key Information Dialog .................................................. 48
Figure 8: Management ConsoleServers Panel .......................................................................... 49
Figure 9: Management ConsoleIP Addresses Panel ................................................................. 50
Figure 10: Management ConsolePhysical View ICON ............................................................... 50
Figure 11: Management ConsolePhysical View panel ............................................................... 51
Figure 12: Management ConsolePhysical View with Servers/NE instances............................... 52
Figure 13: Management ConsoleConfig Tree ............................................................................ 53
Figure 14: Management ConsoleNE Maintenance Panel .......................................................... 54
Figure 15: Management ConsoleUndeploy a given NE ............................................................. 55
Figure 16: Launch 13.0 System Management Console Window .................................................. 64
Figure 17: Launch 15.1 AS 5300 Element Manager Console Window .......................................... 65
Figure 18: MCP System Management Console Connection Frame for13.0 .......................................... 65
Figure 19: AS 5300 Element Manager Console Connection Frame for 15.1 ................................. 65
Figure 20:: Login to the System Management Console for 13.0 ................................................... 66
Figure 21: Login to AS 5300 Element Manager Console for 15.1 ................................................. 66
Figure 22 Initial Management Console display window ................................................................. 67
Figure 23: Configure a NE to the 15.1 loadfrom the NE instance window ................................. 68
Figure 24: Apply the 15.1 loadfrom the pop up window ............................................................. 68
Figure 25: Deploy a NE InstanceMaintenance panel ................................................................. 69
Figure 26: Start a NE InstanceMaintenance panel..................................................................... 70
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
7/120
2.6Method of Procedure
2012 Avaya Inc. viAvaya proprietaryuse pursuant to company instructions
Figure 27: Access to the Load Manager application .................................................................... 105
Figure 28: Selecting the patch load in the Load Manager......................................................... 106
Figure 29: Patch Session Managers ............................................................................................ 107
Figure 30: Session Manager Patch .............................................................................................. 108
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
8/120
2012 Avaya Inc. viiAvaya proprietaryuse pursuant to company instructions
List of Tables
Table 1: High-Level steps to perform an Upgrade ........................................................................... 3
Table 2: Preparatory Steps ............................................................................................................... 6
Table 3: Pre-upgrade steps for a MCP Redundant configuration system ...................................... 21
Table 4: Upgrade a MCP (Redundant configuration) system ........................................................ 24
Table 5: Post-upgrade steps .......................................................................................................... 41
Table 6: Section to Filename mapping for Config Data Changes .................................................. 57
Table 7: Definitions & Abbreviations............................................................................................... 59
Table 8: Documents referenced by this MOP ................................................................................ 60
Table 9: Downgrade one half of a Redundant system ................................................................... 79
Table 10: Downgrade an Entire Redundant system ....................................................................... 86
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
9/120
2012 Avaya Inc. 1Avaya proprietaryuse pursuant to company instructions
1 Upgrade AS 5300 2.0 Release to 3.0This document contains the process (steps) to upgrade the components in an AS5300 system executing a 2.0 release to a 3.0 release.
For the 3rdparty components which can be utilized by the MCP system, pleasereference the vendors documentation regarding the appropriate upgrade processfor each of these components.
o Audiocodes EMSo Audiocodes Gatewayso Audiocodes IADs
1.1Notes for upgrading from the AS 5300 Release
To upgrade from the 2.0 release, the latest Released status MR must be installedon the given system.
Information regarding the Latest General Available MR and/or Patch load can bechecked from the Application Server 5300 web page via the following link. Besure to select 2.0 in the pulldown window (in the upper/middle of the page)
http://support.avaya.com/css/appmanager/public/support/Downloads/P0626
All load line up information (MCP Core Load, Operating System Patch level,Client versions, MAS Firmware versionsetc) are available from the Release
Notes located in Portal page in the above link.
All the 1120/1140 (Unistim) phones must be migrated to SIP 4.2 firmwarephones, and all the IPCMs must be decommissioned from the system prior to
the upgrade window.
During this upgrade process, there must be a Data Freeze for allProvisioning/Configuration Data. Note that the Data Freeze for ProvisioningData does not stay intact for the entire upgrade process of a Redundant system.
Provisioning data can be modified once one half of a Redundant system has beenupgraded (as noted within the MOP itself below).
The primary role of a user can be determined by executing the roles commandas shown below:
[ntappadm@zngdy18a install]$ rolesroles for ntappadm are: AA
http://support.avaya.com/css/appmanager/public/support/Downloads/P0626http://support.avaya.com/css/appmanager/public/support/Downloads/P0626http://support.avaya.com/css/appmanager/public/support/Downloads/P06268/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
10/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 2Avaya proprietaryuse pursuant to company instructions
primary Role is: AA
If required, the primary role of a user can be changed by executing the chrole command
When the user is directed to perform some function (e.g. logging in, running a
script) as a selected role, that role must be the users primary role. As an attempt to assist with the usernames for a pre-configured (e.g. not
individual) system, the default username created for the role will be shown inparenthesis in each step that requests the user to login, as shown below.
o Login as the DBA role(ntdbadm) to the Primary database server
Note, that even for the pre-configured system, there are no guarantees that thedefault username will exist (a customer can delete these usernames and addback their own usernames for each role).
The user might or might not be prompted for a password when they login as theSSA role (ntsysadm) and execute the "sudo" command (or any command that isaliased to an underlying sudo command). If the system does prompt for thepassword, then please enter the SSA roles (ntsysadm's) password.
When the user gets the below prompt, while SFTPing to a server for the first time,always accept the connection by answering yes.
The authenticity of host '47.104.19.19 (47.104.19.19)' can't be established.RSA key fingerprint is ec:27:47:7f:ff:47:c2:c5:7f:63:0d:6d:08:e6:21:e5.Are you sure you want to continue connecting (yes/no)? yes
In the 15.1 release, the log file location for all the
- install/upgrade scripts in the /var/mcp/install directory is/var/mcp/run/install/logs
- DB scripts in the /var/mcp/run// directory is/var/mcp/run///work or/var/mcp/run///installLogs
When following the steps in this MOP you will notice that instead ofcut&pasting information within the MOP, the MOP references the given Step orSection (this keeps the data in the document from growing stale/inconsistent.)Thus, as a suggestion to keep the references from confusing the flow of the
document, if you are using a softcopy of the MOP, bring up the MOP in twodifferent windows. One window will be used for working on each step in thegiven Upgrade Table, and the other window will be used to look up references toother steps/sections. If you are using a Hardcopy of the MOP, then when areference to another step/section comes up, then create two stacks from theMOPsuch that the current page/step stays at the top of one stack, and thus isnot lost when looking up the referenced step/section.
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
11/120
2012 Avaya Inc. 3Avaya proprietaryuse pursuant to company instructions
Terminology used within this documento Releases MCP 13.0 and AS 5300 2.0 are synonymouso Releases MCP 15.1 and AS 5300 3.0 are synonymouso System Manager in R2.0/MCP 13.0 has been renamed to Element
Manager in R3.0/MCP 15.1o System Management Console (SM Console)in R2.0/MCP 13.0 has beenrenamed to AS 5300 Element Manager Console (EM Console) inR3.0/MCP 15.1
o MAS(Media Application Server) in R2.0/MCP 13.0 has been renamed toAvaya MS (Avaya Media Server) in R3.0/ MCP 15.1
This document will generally use the terms AS 5300 2.0 and AS5300 3.0 when referring to the two releases involved in this
upgrade process.
1.2Conceptual view of the Upgrade ProcessTo assist the user in understanding the upgrade process, the following Table shows thehigh level steps that will be performed during an upgrade.
Table 1: High-Level steps to perform an Upgrade
Step # Description1 Perform Prep Steps described in the Table 2
2 Perform Pre-Upgrade Steps described in the Table 3
3 Perform Upgrade of the Primary Core componentsdescribed in the Table 4
3a To perform an upgrade with minimal service downtime acrossthe Core elements, the Servers and Network Elements (NE) are
divided into two logical groups and upgrade one-half of
the MCP system/network at a time letting the other half
continue to provide services. With this, the servers (and
the NEs resident on those servers) are divided into two
groups, Primary and Secondary.
3b Upgrade the Primary Core Servers and NEs
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
12/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 4Avaya proprietaryuse pursuant to company instructions
Stop the NEs running on the Primary Servers
Upgrade the OS/Platform on the Primary servers
Upgrade the DB and EM to the AS 5300 3.0 load
Bring up the AS 5300 3.0 Element Manager Console andinsert the new license key
Deploy and Start the NEs on the Primary Servers withthe new AS 5300 3.0 load
Stop the 2.0 core NEs running on the Secondaryservers.
o This will force traffic to the 3.0 systemInstall client ASU files on the PA/PROV residing onthe Primary Servers
3c Primary Core Components Upgrade is complete.
3d A AS 5300 3.0Primary system is now running.Perform Sanity testing to ensure the system is
operating normally.
4 Perform Upgrade of the Secondary Core componentsdescribed in the Table 4
4a Upgrade the Secondary Core Servers and NEs
Upgrade the OS/Platform on the Secondary servers
Deploy and Start the NEs on the Secondary Serverswith the new AS 5300 3.0load
Resync the Databases.
Install the ASU files on the PA/PROV residing on the
Secondary Servers
4b Secondary Core Components Upgrade is complete.
5 Perform Post-Upgrade Steps described in the Table 5
1.3 Options to upgrade over multiple MaintenanceWindows
The Media Application Server (MAS) and AudioCodes components are upgradedafter all of the Core MCP components. Given the upgrade of the MAS andAudioCodes are independent of the Core components, the upgrade to AS 5300 3.0can be split over multiple Maintenance windows (if required). The corecomponents can be upgraded in one Maintenance window, and then the MAS
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
13/120
2012 Avaya Inc. 5Avaya proprietaryuse pursuant to company instructions
and/or AudioCodes components can be upgraded within another Maintenancewindow.
For additional details regarding the upgrade of a MAS, please refer to AppendixA: MAS Upgrade Notes.
For additional details regarding the upgrade of an AudioCodes component to itslatest MR (if the given AS 5300 2.0 system being upgraded has an AudioCodescomponent configured), please refer to Appendix G: Upgrade AudioCodes to itslatest MR.
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
14/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 6Avaya proprietaryuse pursuant to company instructions
2 Preparatory StepsThe table below contains a list of steps that must be performed/verified prior to the daywhen the actual Upgrade toAS 5300 3.0 procedure is performed. Given the low
impact to service of the Prep Steps, they can be performed during normal operationalhours if needed. However with any operation at a customer site, a Maintenance Windowduring off-hours prior to the day of actual upgrade is the preferred timeframe.
Table 2: Preparatory Steps
Step # Description
1 The following documents are referenced by this upgrade. Please ensurethey are available before the upgrade process begins:
Link to 3.0 documents:
103.1.2_AS 5300_Software_Update
103.2.3 AS 5300 Backup And Restore
102.2.7 AS 5300 2.0 to 3.0 AVAYA MS Upgrade
102.1.9 AS 5300 IPv6 Configuration (if using IPv6 on the 2.0
system)
Link to 2.0 documents:
102.1.1_AS5300_Server_Installation
102.1.2_AS5300_Initial_System_Installation
103.1.2_AS5300_Software_Update
103.2.3_AS5300_Backup_And_Restore
101.2.6_AS5300 IPv6 Configuration (if using IPv6 on the 13.0
system)
103.1.3_AS5300 11x0 SIP Client Configuration
2 Ensure the person performing the upgrade knows how to launch theSystem Management Console, and how to use it.
For details regarding how to launch a System Management Console,
please refer to section 7.1of Appendix D: MCP SM/EM CONSOLENotes.
3 Ensure the AS 5300 system is on the latest 2.0 MR and Patch.
Refer to the instructions in Appendix J: 13.0 Patch current
determinationto determine if the MCP system is Patch current
and apply the latest Patch if needed.
Refer to the 103.1.2_AS5300_Software_Update MOP for AS 5300 2.0
for the steps to apply the patch.
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
15/120
2012 Avaya Inc. 7Avaya proprietaryuse pursuant to company instructions
4 Perform 2.0 Backups for the Core Servers.
4a Ensure the 2.0 onlineHelp file and ASU (Automatic Software Update)files exist on the Primary Element Management Server
Login as the AA role (ntappadm) to the Primary Element Management
Server cd /var/mcp/media
ls l
You should see the following:
MCP-OnlineHelp_13.0.X.0_XXX.zip
HardenedClient_7.2.XXX
If the onlineHelp file and the ASU files do not exist, please execute
the following steps:
1) Obtain the latest AS 5300 2.0 Core Apps CD for the MCP load
currently installed.
2) Extract the 2.0 online Help file
insert DVD in the DVD tray of the Primary Element Management
Server
login as the AA Role (ntappadm) to the server
mcpExtractContent o -aat
Note:
The AS 5300 2.0 load zip file will be copied to the
/var/mcp/loads directory.
The OnlineHelp zip file will be copied to the /var/mcp/media
directory.
The ASU related files will be copied to the
/var/mcp/media/HardenedClient_7.2.XXX.
The Database installer will be copied to the /var/mcp/media
directory.
Note: Remove the extracted ASU 7.2 files by following the steps below.
cd /var/mcp/media
rm rf HardenedClient_7.2.XXX
4b Save the 2.0 ASU files to the Primary Element Management Server to beused during upgrade/rollback.
Note:
- Even though the system may have more than one PROV, only one copy of
the Online Help file is required.
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
16/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 8Avaya proprietaryuse pursuant to company instructions
- This step may not be applicable for non-hardened system.
- Login as the AA role (eg:ntappadm) to the Primary Element
Management Server
cd /var/mcp/media
mkdir HardenedClient_ASU_preupg chmod 770 HardenedClient_ASU_preupg
If the Provisioning Manager is on the Primary Element ManagementServer, execute the following steps:
o cd /var/mcp/media/prov_pa_installs/ASU
o cp smcclient.jnlp
/var/mcp/media/HardenedClient_ASU_preupg/HardenedClient.jnlp
o zip r pcclientcode/signedJar/HardenedClient_Release.zip *
o mv pcclientcode/signedJar/HardenedClient_Release.zip
/var/mcp/media/HardenedClient_ASU_preupg
o zip -r pcclientcode/HardenedClient_unsigned.zip * -x
signedJar/*
o mv pcclientcode/HardenedClient_unsigned.zip
/var/mcp/media/HardenedClient_ASU_preupg
If the Provisioning Manager is NOT on the Primary Element
Management Server, execute the following steps:
o Login as the AA role (eg:ntappadm) to a server hosting a PROV
cd /var/mcp/media/prov_pa_installs/ASU
o cp smcclient.jnlp HardenedClient.jnlp
o zip r pcclientcode/signedJar/HardenedClient_Release.zip *o zip -r pcclientcode/HardenedClient_unsigned.zip * -x
signedJar/*
o sftp 47.10.10.20
(where 47.10.10.20 is the IP address of the Primary Element
Management Server. Please replace it with the IP address used
in your system.)
o Enter the ntappadm password
o cd /var/mcp/media/HardenedClient_ASU_preupg
o put HardenedClient.jnlp
o put pcclientcode/signedJar/HardenedClient_Release.zip
o put pcclientcode/HardenedClient_unsigned.zip
o exit
Login as the AA role (ntappadm) to the Primary Element
Management Server
cd /var/mcp/media
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
17/120
2012 Avaya Inc. 9Avaya proprietaryuse pursuant to company instructions
chmod 660 HardenedClient_ASU_preupg/*
4c Remove unneeded old loads on the Element Management Servers if needed
Normally the number of loads in the /var/mcp/loads directory should
be 3 or less.
For example, when an MR with multiple Patch loads exist, keep the
latest base/MR load (MCP_13.0.0.0_2010-05-05-2108) and the latest
associated patch load (MCP_13.0.0.3_2010-07-13-1208).
In two different windows, login as the AA role (ntappadm) to the
Primary and Secondary Element Management Servers
cd /var/mcp/loads (on both servers)
Get the rm command ready on both servers (e.g. rm rf )
Hit the Enter key on both servers at roughly the same time. (Note:
The reason for doing this is that Primary EM and Secondary EM
monitor the loads and if the load is on one server but not the
other, it will repopulate the loads in the /var/mcp/loads on theother Element Management Server.)
4d Backup Preparation
AS 5300 2.0 backups taken for the upgrade to the 2.0 release will bestored on the Secondary Element Management Server in the/var/mcp/backup/remote/13.0 directory.Create a 2.0 backup directory on the Secondary Element Management
Server
- login as the SSA role (ntsysadm) to the Secondary Element Management
Server
- su root
- cd /var/mcp/backup/remote/
- mkdir 13.0
- chown root:ntsysgrp 13.0
- chmod 770 13.0
- ls lrt
Note: Ensure the /var/mcp/backup/remote/13.0 directory exits and is
owned byroot:ntsysgrp.
In addition, as an additional safe guard, it is recommended that the
backups stored in the /var/mcp/backup/remote/13.0 directory are copiedto one of the following machines if available:
Site dropbox (eg: /var/mcp/dropbox)
PC
Non-core server
4e Take a backup for each of the Core Servers:
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
18/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 10Avaya proprietaryuse pursuant to company instructions
Notes:
The server restore logic will only look for server backup
filenames formatted like mcpPlatform*.tar.
Core server backups are required to rollback to 13.0 if the
upgrade to 15.1 runs into some unforeseen issue.
Core ServersIf you are familiar with the execution of the MCP backup script,
execute the following steps to back up the server configuration and
Application data. However if additional details are required
regarding how to create a backup, please refer to the sections
listed below,
3.12.2 Example invocation (Change passphrase and/or SSH Keys)
3.12.5 Config script help
4.3.2 Backup to remote server
in the 103.2.3_AS5300_Backup_And_Restore MOP
Follow the steps below for all Core Servers except the SecondaryElement Management Server.
Login as the SSA role (e.g., ntsysadm)
Ensure job-specific backup parameters for the "server" and
"platform" backup jobs are disabled.
[ntsysadm@ ]$ configSvrBkup
o If the menu option "[6] Set remote configuration parametersto default values" is available, then select menu option 6,
answering "y" to confirm.
o Otherwise, select menu option 4 to exit the tool.
[ntsysadm@ ]$ configPlatformBkup
o If the menu option "[6] Set remote configuration parameters
to default values" is available, then select menu option 6,
answering "y" to confirm.
o Otherwise, select menu option 4 to exit the tool.
Enable remote backup configuration parameters for all backup jobs
(Select Option 2).
[ntsysadm@ ]$ configBkup
You are required to set:
o IP address of remote backup server (Primary or Secondary
Element Management Server or any other server that you want)
o Directory on remote backup server where backup tar files are
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
19/120
2012 Avaya Inc. 11Avaya proprietaryuse pursuant to company instructions
to be stored (/var/mcp/backup/remote/13.0)
o SSA role (ntsysadm) username to use for remote SSH commands
o Previously generated SSH keys
o Select exit when finished.
On the Primary Element Management Server, backup the Configuration andApplication data to the Secondary Element Management Server.
[ntsysadm@ ]$ bkupSvr remote
The duration of this backup can vary based on the number and
size of files to be backed up. Larger backups typically will be
completed in less than 30 minutes.
On the Secondary Element Management Server, backup the Configurationand Application data to the Secondary Element Management Server.
[ntsysadm@ ]$ bkupSvr local
[ntsysadm@ ]$ cd /var/mcp/backup/local
[ntsysadm@ ]$ mv mcp* ../remote/13.0/
For all other core servers, backup the Configuration data to theSecondary Element Management Server.
[ntsysadm@ ]$ bkupPlatform remote
If IPv6 is configured for any 2.0 AS 5300 SESM, reference section "8.2
Manual Backup and Restore" of 101.2.6 AS 5300 IPv6 Configuration for
details on manually saving any IPv6 AS 5300 SESM configuration.Perform this step for each of the 2.0 SIP Core servers which have an
AS 5300 SESM deployed to them.
4g Server information required when rolling back the server to the 2.0release
Note that this information is required to rollback to 2.0 if the
upgrade to 3.0 runs into some unforeseen issue.
The information required to restore a server (using a backup of the
given server stored on a remote server) is listed below. As part
of the preparation for the actual server upgrade, please compile a
table with this information for each Core server.
The VLAN ID, the IP address, the gateway and the netmask of the
server that you are restoring.
The IP address of the remote server (that the server backup is
stored on), the directory where the backup was placed, and the
userid/password for accessing the data on the remote server.
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
20/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 12Avaya proprietaryuse pursuant to company instructions
o The user will be the SSA role (ntsysadm) for the server
backups
To obtain this information for a given server, login to the server
as the SSA role (ntsysadm) user.
Execute the command below:
o mcpShowNwkConfig
or
o su -
o cat /admin/nwk/mcpNwkCfg.xml
Identify the three required items from the output of the command.
There will be other items listed in mcpNwkCfg.xml An example of
the information to be captured from the above output, is shown
here:
gateway=47.10.X.X
machineIP=47.10.X.X
vlanID=1729 (optional)
5 Passwords required
Before the upgrade is started, ensure that the following passwords are
known:
On all Core servers
o AA role (ntappadm) user password
o root password
o SSA role (ntsysadm) user password
Only on the Core server(s) hosting the Databaseo DBA role (ntdbadm) user password
Only on the MAS Server(s)
o Note down the username/password of the MAS Server(s) and EM.
Only on the AudioCodes EMS
o Note down the username/password for AudioCodesEMS
6 The new (AS 5300 3.0) License Key is required to deploy the AS 53003.0 load. And a new AVAYA MS 7.5 license key is also required for theapplicable services on the AVAYA MS 7.5 platform (i.e., Adhoc,Announcements, Chat, Music on Hold, and Meet Me Conferencing). Thus,
ensure the AS 5300 3.0 License Key and the AVAYA MS 7.5License Keyhave been obtained.
For information about generating/retrieving a license key, pleaserefer toAppendix L: Retrieving the MCP License Key.
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
21/120
2012 Avaya Inc. 13Avaya proprietaryuse pursuant to company instructions
7 IPCM Decommissioning (following the steps below to make sure IPCMinstances are deleted from the system) IMPORTANT!!
(Note: This is an important step. Upgrade will fail if this step isnot completed.)
After all the hard phones are migrated successfully to the SIPsoftware from UNIStim firmware, the IPCM NE (which was managing the
UNIStim phones) can be decommissioned.
Note: Please refer to Migration from UNIStim to SIP section of
103.1.3 AS 5300 11x0 SIP Client Configuration MOP for AS 5300 2.0
The following steps describe the procedure to decommission the IPCM
using the AS 5300 2.0 System Manager console.
1. Ensure that all the UNIStim phones are migrated to SIP phones
2. Launch the AS 5300 2.0 System Manager console
3. Click on IP Client Manager NE under Network Elements
4. Click on IPCM NE Maintenance
5. Select the instance in the IPCM Maintenance Panel and stop the
instance by clicking on the Stop button, as shown below.
6. Click on the Yes button in the Confirmation panel
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
22/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 14Avaya proprietaryuse pursuant to company instructions
7. Click on the Undeploy button to undeploy all the IPCM NEs as
shown below.
8. Select the Instanceand Click on the - (Delete) button to
remove the all the IPCM instances, as shown below.
9. Click on the Yes button in the Confirmation panel.
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
23/120
2012 Avaya Inc. 15Avaya proprietaryuse pursuant to company instructions
10. Select IP Client Managers, and click on the - (Delete)
button to remove the IPCMx as shown below.
11. Click on the Yes button in the Confirmation panel.
12. Select IP Client Managers, all the IPCM instances should be
deleted as shown below.
8 (For a Redundant MCP system only)Ensure there are a limited number of deferred DB transactions for theDatabase
Use the System Management Console to check for deferred transactions
PRIOR to beginning the AS 5300 2.0 to 3.0 upgrade process. Deferred
transactions are changes that have been made to the Database and are
awaiting transfer to the other Database. A few deferredtransactions are fine (as updates are being made to the system), but
the number of deferred transactions should be very low (less than 50)
unless some type of Bulk Provisioning is taking place. In addition,
it is essential to clear (resolve) any/all alarms regarding Database
replication before starting the upgrade process.
From the Management Console, open the Database-> folders, and
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
24/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 16Avaya proprietaryuse pursuant to company instructions
then select Monitor. From the Monitor panel, select instance
0 of the Database, and then select the Monitor button at the bottom of
the Panel. Once the Database Instance Monitor panel initializes,
select the Replication Tab to see the number of Deferred Transactions
(as is shown in the screenshot
9 Suggestion Prior to starting the upgrade process of a Redundantsystem, a list should be generatedshowing the Servers, IP Addresses,the NEs that are deployed on each server, and whether the server is
designated a Primary or Secondary Server.
Primary/
Secondary
Server
Name
Server IP
address
Associated
NEs
In addition, a list of the Non-Core Servers should be generated. Non-
Core Servers are servers in which one of the following components are
deployed/running:
MAS
AudioCodes
If the MASs are configured in a redundant configuration, thenreference Appendix A: MAS Upgrade Notes for details in generating an
upgrade order/strategy for these components which limits any service
impact.
The information in these lists can then be referenced (checked-off)
during the upgrade steps out-lined below.
10 Make sure 2.0 Server installation CDs, Server Patch CDs, Core App CDs,Oracle 10.2.0.4 Installation CDs, Oracle 10.2.0.4 Patch CDs, MAS CDsexist.
These are needed if a system rollback from 3.0 to 2.0 is required for
some unforeseen reason.
11 Ensure all applicable 3.0 software is on Site prior to starting theupgrade.
The 3.0 software (CoreApp bundle) in the DVD are extracted to theservers in Preparatory Steps for two reasons:
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
25/120
2012 Avaya Inc. 17Avaya proprietaryuse pursuant to company instructions
- to reduce the amount of time required during the actual upgrade- to eliminate the chance of finding a bad CD or DVD during theupgrade
11a Extract the latest 3.0 Linux OS Platform Patch to all servers in thesystem.
Execute the following steps on the Primary ElementManagement ServerIf a latest Platform Patch CD is available:
- place the Linux OS Platform Patch CD in the DVD tray
- log into the server as an SSA role user
- mcpExtractContent o aat (take note of the extracted
"mcp_core_linux_ple2-.iso" file)
- type "su " to become the root user
- cd /var/mcp/os/install/images
- Transfer the platform patch (ISO) file to all other core and
MAS servers in the system using SFTP as the AA role user (e.g.,ntappadm). In the steps that follow, "target server" refers to
the IP address of either a core or MAS server.
- sftp @
- cd /var/mcp/media
- put mcp_core_linux_ple2_.iso
Execute the following steps on each remaining server on the Primaryand Secondary half of the system after transferring to these servers:
- Log into the server as an SSA role user
- Type "su " to become the root user- cd /var/mcp/os/install/images
- mv /var/mcp/media/mcp_core_linux_ple2-.iso .
- chown root:root mcp_core_linux_ple2-.iso
- chmod 400 mcp_core_linux_ple2-.iso
If the latest platform patch is available at Avaya Portal page
https://support.avaya.com/css/appmanager/public/support/Downloads/P0626,then please manually transfer the platform patch ISO Image file to the
directory /var/mcp/os/install/images (owned by root) for all the
servers.
11b Extract the AS 5300 3.0 Core Applications to the Primary ElementManagement Server by executing the following steps.
- place the MCP Core Applications DVD in the CD-ROM drive
- login as the SSA role (ntsysadm) to the server
https://support.avaya.com/css/appmanager/public/support/Downloads/P0626https://support.avaya.com/css/appmanager/public/support/Downloads/P06268/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
26/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 18Avaya proprietaryuse pursuant to company instructions
- mcpExtractContent o aat
Note:
The AS 5300 3.0 load zip file will be copied to the
/var/mcp/loads directory.
The ASU related files will be copied to the
/var/mcp/media/HardenedClient_8.1.XXXX.
After extracting the MCP apps to the Primary EM Server, alarms
will be raised in the System Management Console that a new load
is available
12 Please determine if there are patches available for the 3.0 MR that isbeing upgraded.
If patches are available, then please manually transfer the patches tothe /var/mcp directory on the Primary Element Management Server (owned
by the AA (ntappadm) user).
Note: after the Element Manager has been upgraded to the 15.1 release,
the application patch will be moved to the normal directory
(/var/mcp/dropbox) and database software patch will be moved to the
normal directory (/var/mcp/media).
For detailed information regarding how to download a patch, please
refer to Download Update Fileswithin the 103.1.2_AS
5300_3.0_Software_Update document.
13 Make sure there is no NE with short name "EM".
During upgrade procedure System Manager called "SM" will be renamed to
"EM". Use System Management Console to check short names of all NE and
rename them if required.14 Manually backup the IPv6 Configuration Data
During the upgrade procedure, all IPv6 data will be removed from the
system and will need to be manually added after the upgrade to 3.0 is
complete. To save the current IPv6 configuration, run the command
- configIPv6and manually write down (or copy and paste) the current IPv6
onfiguration data for each server and the Avaya SESMs. This command
will need to be run on all servers that have IPv6 enabled. This data
will have to be manually re-entered once the 3.0 upgrade is complete.
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
27/120
2012 Avaya Inc. 19Avaya proprietaryuse pursuant to company instructions
3 Process to Upgrade AS 5300 2.0 to3.0
3.1Upgrading a Redundant SystemThe diagrams on the following page show redundant 4 server and 2 serverconfigurations. The Servers and Network Elements (NE) are divided into twological networks sothat the user can upgrade them with minimal servicedowntime. The strategy is to upgrade half of the MCP system/network at a time;while letting the other half providing service. Thus, the servers are divided into twogroups, Primary and Secondary.
Prov does not have an active/standby configuration; however they are namedPrimary and Secondary to match the server they reside on. Please use the followingdiagrams to help envision how the Primary Servers/components are upgraded first,and then the Secondary Servers/components are upgraded next.
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
28/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 20Avaya proprietaryuse pursuant to company instructions
The following diagrams show the MCP systems are divided into two groupsPrimary Servers and Secondary Servers.
Figur e 1: Small (2 server) SIP Core con figur at ion
Figure 2: Medium (4 server) SIP Core conf igurat ion
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
29/120
2012 Avaya Inc. 21Avaya proprietaryuse pursuant to company instructions
Figur e 3: Large (8 server) SIP Core co nfigu rat ion
Note: A data freeze for all provisioning and configuration data must take place after Step2c. Therefore, it is recommended to execute Step 2a to Step 2c ofTable 3: Pre-upgradesteps for a MCP Redundant configuration system no more than two hours prior to themaintenance window scheduled for the upgrade.
Table 3: Pre-upgrade steps for a MCP Redundant configuration system
Step # Est. Time Description
1 N/A Ensure the Preparatory Steps (in Table ) havealready been performed.
2 25 mins Prepare for the upgrade (drop Database Replicationand backup the database)
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
30/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 22Avaya proprietaryuse pursuant to company instructions
2a 5 mins Ensure there are very few deferred DB transactions for theDatabase
Login to the System Management Console to check for
deferred transactions. Deferred transactions are changes
that have been made to the Primary Database and are
awaiting transfer to the Secondary Database. Given thereis a data freeze on for the upgrade process, there should
be very few deferred transactions ( less than 50 since
only registrations and NE admin state changes (by the EM)
are being written to the DB). Note, if less than 50
deferred transactions are present, the upgrade can proceed.
However, there is a potential that some of those
transactions will not be propagated to the Secondary
Database (before Database replication is dropped in the
next step).
From the Management Console, open the Database->
folders, and then select Monitor. From the Monitor panel,
select instance 0 of the Database, and then select theMonitor button at the bottom of the Panel. Once the
Database Instance Monitor panel initializes, select the
Replication Tab to see the number of Deferred Transactions
(as is shown in the screenshot below).
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
31/120
2012 Avaya Inc. 23Avaya proprietaryuse pursuant to company instructions
A snapshot of the Database Monitor with 0 Deferred Transactions:
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
32/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 24Avaya proprietaryuse pursuant to company instructions
2b Time
will
vary
based on
the size
of the
DB
Take a backup(e.g. export) of the data in the database forsafe keeping.
login as the DBA role (ntdbadm) to the server hosting theprimary Database
cd /var/mcp/run/MCP_13.0//bin/util/
./dbBackup.pl repdbupgrade
Note: The generated DB backup file is stored in the
/var/mcp/db/backup directory. for safe keeping.
Also, save off a copy of the dbBackup to the local PC.
2c 15 mins
Idle: 10
mins
Drop Database Replication
login as the DBA role (ntdbadm) to the server hosting thePrimary Database
cd /var/mcp/run/MCP_13.0//bin/util
./cleanupReplication.pl
The following table contains the detailed steps for performing the upgrade.
Table 4: Upgrade a MCP (Redundant configuration) system
Step # Est. Time Description
1 5 mins Stop the NEs running on the Primary Servers
CallP Impact:
1 min/active SessMgr to failover
1a Using the MCP System Management console, stop and undeploythe components running on the Primary Servers.
If additional details are needed regarding how to stop and
undeploy a running component from the SM Console, then
please reference the steps defined in Sections 3.3.1and
3.3.2.
Stop and undeploy the NEs listed below, except the System
Manager itself, from the System Management Console. Order
which to stop/undeploy the NEs running on the Primary
Servers:
- Session Managers- Personal Agent Managers (if any)
- Provisioning Managers
- Accounting Managers
Note that as the components on the Servers are stopped,
Peer presumed failed alarms will be displayed on the
Management console. These alarms are expected.
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
33/120
2012 Avaya Inc. 25Avaya proprietaryuse pursuant to company instructions
1b 5 mins Stop the System Manager (SM) running on the Primary ElemenManagement Server.
Login to the MCP System Management Console (using the SM
Service Address) and
Stop the SM running on the Primary Element Management serv
(instance 0), by traversing to the SystemManager Folder:
From the NE Maintenance panel, select instance 0, and then
select the Stop ICON (Red Stop Sign) at the bottom of the
panel.
If instance 0 was in a
Hot Standby state, it will go to Offline.
Active state, Then a Warning message will be display
stating Connection with the server lost answer OIf User Force Out message is received, answer OK.
2 15 mins(per
server)
Upgrade platform for each of the Primary serversincluding the server hosting the Primary Databas
2a The Server Patch file(s) should already reside on the
Servers (this was performed in step 11a ofTable 2:
Preparatory Steps). Upgrade platform for each of primary
servers.
To reduce the overall time to patch the platform, the
Primary Servers can be patched in parallel by opening awindow to each server, and then executing the
patchPlatform.pl command (described in the step below)
within each window.
2b
Install the latest OS patch (if any)
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
34/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 26Avaya proprietaryuse pursuant to company instructions
login as the SSA role (ntsysadm) to the server
su
patchPlatform.pl
A list of available patch ISO files is presented,
followed by the prompt:
Please make selection =>
Enter the number of the menu choice corresponding to th
patch ISO file to be used.
If the locally resident "patchPlatform.pl" command is o
of date, it is automatically updated at this point and
the tool exits after displaying the following message:
The system-resident patching tool (patchPlatform.pl)
has been updated from version x.x.x to version y.y.y
Please re-execute the (updated) "patchPlatform.pl"
command.
If this happens, then re-execute the patchPlatform
command as described above and continue with the next
step below.
If there are patches that need to be applied, the list to
applied (the patch chain) is presented, and the following
prompt is given:
Apply patch chain?
Enter "y" to apply the patches. The server will
automatically reboot after all patches have been applie
3 20 -40mins
On the Primary servers hosting the DB and EM,upgrade the DB (and the data) and the EM to the 5300 3.0 load
Note that once the Primary DB has been Upgraded, several
alarms should be displayed on the Management console stati
the given component cannot connect to the Primary DB.
Disregard these alarms and continue with this process.
3a 0 mins The MCP_15.1 load (zip file) should already be on the
Primary Element Management Server (this was performed instep 11b of Table 2: Preparatory Steps)
FYI - before the components can be upgraded to the AS
5300 3.0 load, the AS 5300 3.0 load must be installed
onto the Primary Element Management Server (and the
old/existing 2.0 load must be there as well).
o NOTE: the 2.0 load will not be installed/deployed, bu
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
35/120
2012 Avaya Inc. 27Avaya proprietaryuse pursuant to company instructions
it must be resident on the Primary Element Management
Server (in the /var/mcp/loads directory) during the
upgrade to 3.0 to determine Eng/Config Parms that hav
been deleted/added/modified between the new and old
loads.
3b 10 - 30mins
Upgrade the DB and EM to the 3.0 load in the Primary ElemeManagement Server
Login as the AA role (ntappadm) to the Primary Element
Management Server
cd /var/mcp/install
./mcpUpgradeNextRel.pl
o select the MCP_15.1 load
Note:
The upgrade script will stop/undeploy SM_1 instance anddeploy/start EM_0 instance
At this point, Primary Element Management Server has been
upgraded from 2.0 to 3.0. System Manager(SM) is renamed to
Element Manager(EM).
Apply patches if applicable.
If there is a MCP 15.1 database software patch to
apply (downloaded in Table 2: Preparatory Steps):
o Login as the SSA role (ntsysadm) to the PrimarElement Management Server
o su root
o cd /var/mcp
o chmod 660
(e.g.installer-mcp-postgresql-9.0.5-8.LINUX64.zi
o chown ntappsw:ntappgrp
o mv /var/mcp/medi
o Login as the AA role (ntappadm) to the Primary
Element Management Server
o cd /var/mcp/install
o ./mcpDbSwPatch.pl
primary
If there is a MCP 15.1 core application load patch t
apply (downloaded in Table 2: Preparatory Steps)
o Login as the SSA role (ntsysadm) to the Primar
Element Management Server
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
36/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 28Avaya proprietaryuse pursuant to company instructions
o su root
o cd /var/mcp
o chmod 660
o chown ntappsw:ntappgrp o mv /var/mcp/dropbox
o Login as the AA role (ntappadm) to the Primary
Element Management Servero cd /var/mcp/loadso ls (wait for the patch load to be generated, n
that you might need to wait up to 10 minutes)
o cd /var/mcp/install
o ./mcpPatch.pl
Pick the load
Note that as the Primary servers, Primary EM and DB are
upgraded, the following alarms may be displayed on the
Management Console
Load audit failed NEComm
Rogue NE instance
SNMP Agent Communication Failure
Database Communication Error
These alarms are expected and will be cleared once the oth
Primary NEs, Secondary Servers and Secondary DB are upgrad
to the 15.1 release.
Also the following is expected:
The db.shared property failed validation, setting it to N
INSTALL, for Database Software on 172.27.153.150 ...Installing Database Software...please be patient
4 5 mins Bring up the AS 5300 3.0 Element Manager Consoleinsert 3.0 license key and stop DB monitor for tSecondary DB.
4a Launch the 3.0 Element Manager Console
At this point, the 3.0 Element Manager Console will be use
to communicate with the 3.0 EM.
Given the upgrade process will cause the SM/EM to failover
between the Primary and Secondary EMs, ensure you are usin
the Service Address of the SM/EM (not the IP address of th
server where an SM/EM instance runs) to log into the SM/EM
console during this process.
For details of how to launch the 3.0 Element Manager
Console, please reference Section 7.1 Install/launch the
MCP SM/EM.
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
37/120
2012 Avaya Inc. 29Avaya proprietaryuse pursuant to company instructions
Note 1:
To access AS 5300 Element Manager Console in FIPS complian
mode,a new fips-mgmtconsole.zipfile must be downloaded anunzipped EVERYtime the MCP system is upgraded.
The following are quick reference steps:
1. Download the FIPS Management Console ZIP file by issuingthe following command in the web browser:
https://:12121/fips-mgmtconsole.zip
2. Save the fips-mgmtconsole.zip file to the workstation
3. Unzip the file to the C:\hard drive.
For detailed MCP Hardening steps, please refer to MCP FIPconfiguration section of 105.1.3 AS 5300 3.0 Security
Hardening MOP.
Note 2:
If Custom Certificats are used, please perform the followi
steps to apply certificates:
1. Launch the 3.0 Element Manager Console
2. Click on Advance button from Element Manager Console
3. Click Trust Store Certificates tab and click +
button to add Trust Store Certificates
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
38/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 30Avaya proprietaryuse pursuant to company instructions
4. Click Key Store Certificates tab and Click + button
to add Key Store Certificates.
5. Click on Connect button to launchElement Manager
Console
4b With the database and Element Manager updated to the 3.0
release, the associated 3.0 license key must be entered in
the system. To update the License Key select the
NetworkData and Mtc => Licensekey menu option from theSystem tree of the Element Manager Console.
For additional details, please reference section 3.2title
Steps to Update the License Key
Note: Without a new 3.0 License Key, you will not be able
deploy any components in the 3.0 system.
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
39/120
2012 Avaya Inc. 31Avaya proprietaryuse pursuant to company instructions
4c Stop the DB monitor for Secondary DB
From the EM Console:
Open the Database Folder, then the folder:
Select Monitor (under the database name) and the Monit
panel will display.o Select the instance 1
o Select the Monitor menu button and the Monitor pane
will be displayed
o Select the Stop Monitor menu button at the bottom
the Monitor panel
o A Confirmation message will be displayed stating
Stopping this monitor will also stop corresponding
data collection for this Database Instance!
Do you wish to continue? Answer Yes.
o Close these panels
5 15 mins Deploy/Start the NEs on the Primary Servers with
the new MCP 15.1loadReference section 7.2Deploy/start a Network Element(NE)
if additional details are needed for this process.
5a Note:
If an NE is in a deactivated, disconnected, or rogue
state, then stop or kill the NE to get it to the offlined
state. Once in the offlined state, the load can be
changed and it will go to the configured state.
Due to the DB migration, an NE that was stopped before is
likely in an Online state although its Operation State i
Unavailable. Stop or kill the NE before deploying it.
Reference section 7.2Deploy/start a Network Element(NE)
if additional details are needed for this process.
5b Deploy and Start the remaining NEs on the Primary Servers
1. Select the MCP 15 load that you use for upgrade in
Instance Windows first prior to deploy.
o Open the Instance window for the NE
o Select the instance to be deployedo Click the -/+ button
o Use the Load or Patchdropdown box to select
the MCP 15 load
o Click the Apply button
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
40/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 32Avaya proprietaryuse pursuant to company instructions
2. Deploy and Start the NEs listed below, from the
Element Manager Console
Order in which to deploy and start the 3.0 NEs:
Fault Performance Managers (if any)
Accounting Managers
Provisioning Managers
Personal Agent Managers (if any)
Session Managers
NEs can be upgraded/deployed in parallel.
Note:
While the PROV is being deployed, the "Media Application
Server Unreachable" alarm will be displayed on the Element
Manager Console. This alarm is expected and will clear oncthe PROV is deployed and started successfully.
If IPv6 was configured on the 2.0 AS 5300 SESM, the IPv6
configuration that was manually saved during the backup
procedure must be manually re-applied to the 15.1 AS 5300
SESM once it is deployed. Refer to section "4.8 Configurin
AS 5300 SESM IPv6 Service Address" of 101.2.6 AS 5300 IPv6
Configuration for details on configuring an AS 5300 SESM
IPv6 address. Once the 3.0 AS 5300 SESM IPv6 address has
been manually configured, the AS 5300 SESM must be restart
to pick up the IPv6 address.
5c With the upgraded 3.0 (non-redundant) system, please
reference sections 3.4& 3.5for instructions regarding
changes that may be required to the existing data.
The provisioning changes (if any are required), can be
performed in parallel with the remaining steps - which
upgrade the Secondary servers/components of the system to
15.1.
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
41/120
2012 Avaya Inc. 33Avaya proprietaryuse pursuant to company instructions
6 10 mins Stop the remaining 2.0 core NEs running on theSecondary servers. This will force the PrimaryNEs (on the 3.0 system) to take over activity.
6a 10 mins Using the Element Manager Console stop and undeploy theRunning SecondaryNEs(this forces traffic to the upgrad15.1 Primary components).
Order in which to stop the remaining 2.0components:
Session Managers
Personal Agent Managers (if any)
Provisioning Managers
Accounting Managers
Fault-Performance Managers (if any)
If additional details are needed regarding how to stop and
undeploy a running component from the Management console
then please reference the steps defined in Sections 3.3.1and 3.3.2.
7 20 mins Install the ASU files on the PA/PROV residing onthe Primary Servers.
7a Install the 2.0 ASU files on the Primary Servers.
Please reference the following section to install the 7.2
Hardened Clients for the Provisioning Managers and Persona
Agent Managers running on the Primary Servers. Note that t
8.1 ASU will be installed later once the 3.0 system (non-
redundant) is verified to be functioning properly.
9.1.2 Installing 7.2 Hardened Client ASU files on the
MCP Server for instructions regarding the ASU.
8 Varies You now have one half of the Core upgraded to thAS 5300 3.0 release and the active NEs areexecuting on the 3.0 system (non-redundant)
8a
At this point in time, the Active side of the Core is
Running on the 3.0 release (non-redundant) with the
Redundant Core components (on the Secondary Servers) stopp
and still on the 2.0 release.
Please perform some sanity tests using 7.2 Hardened client
to verify the 3.0 non-redundant system is functioning
properly.
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
42/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 34Avaya proprietaryuse pursuant to company instructions
Thus, this is the point in the process to ensurethe 3.0 system (running on the Primary Servers) operating correctly prior to Upgrading theremaining 2.0servers/components.
If for some unforeseen reason the 3.0 system is not
operating correctly, you can rollback to a 2.0 system by
following the steps defined in section 11.1Rollback one
half of an upgraded system.
9 Data Freeze for Provisioning User Data ends here
9a With the 3.0 simplex system up and running, the customer cbegin making user data provisioning changes via the 3.0NEs/components running on the Primary Servers (e.g. the dafreeze for provisioning user data is now off). However,note that in the unlikely event that the 3.0 system isrolled back to the old/previous 2.0 system, any/allprovisioning changes made to the 3.0 system will be lost.
10 10 mins/server
Upgrade the platform for the remaining Secondaservers
10a Upgrade the remaining secondary servers, which consist of:
2.0 components that were just stopped.
Secondary System Manager (SM)
Secondary Session Manager
Secondary Database
Secondary PROV
The Server Patch file(s) should already reside on the
Servers (this was performed in step 11a of Table 2:
Preparatory Steps).
For each of the Secondary Servers:Upgrade the Linux servers using step 2b (the Upgradeprocess can be done in parallel across the servers):
11 Uninstall Oracle and Install Postgres on the SecondaryDatabase
11a 10 mins Execute the script that performs all of the necessaryfunctions to change the database.
Note: Make sure execute the following scripts from PRIMARYElement Management server hosting the DB and SM
login as the AA role (ntappadm) to the Primary SystemManagement server
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
43/120
2012 Avaya Inc. 35Avaya proprietaryuse pursuant to company instructions
cd /var/mcp/install
./oracleUninstall.pl -secondary
./mcpDbSwInstall.pl -secondary
./mcpDbSwPatch.pl -secondary (if there is database
software patch available)
12 Deploy and Start the Secondary EM server
Reference section 7.2Deploy/start a Network Element(NE)
if additional details are needed for this process.
12a From the Element Manager Console, deploy Secondary EM with15.1 load
12b From the Element Manager Console, start Secondary EM with
Reference section 7.2Deploy/start a Network Element(NE)
if additional details are needed for this process.
13 25 mins Deploy and Start the remaining Core NEs on theSecondary Servers
Reference section 7.2Deploy/start a Network Element(NE)
if additional details are needed for this process.
13a From the Element Manager Console, deploy and start the
remaining NEs.
If an NE is in a deactivated, rogue, or disconnected
state, then stop or kill the NE to get it to the offlined
state. Once in the offlined state, the load can be
changed and it will go to the configured state.
Given the DB was backed up when the NEs were up and runnin
an NE may show an Online Admin state, with an Operation
State of Unavailable. For this case, Stop or kill the NE
to get it to the offlined Admin state.
The ordered list of NEs to deploy and start on the SecondaServers is:
- Fault Performance Managers (if any)
- Accounting Managers
- Provisioning Managers
- Personal Agent Managers (if any exist)
- Session Managers
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
44/120
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
45/120
2012 Avaya Inc. 37Avaya proprietaryuse pursuant to company instructions
will be displayed
o If the Monitor is not running, select the Start
Monitor menu button at the bottom of the Monitor
panel
o Close these panels
Note:You might need to re-start DB monitor for DB instance 0, i
Replicationtab is not displayed after DB resync
completes.
A screenshot of the Database Monitor
16b Start the Server Monitors so that the system will generate
alarms when the server has high CPU, Memory, Disk, or I/O
usage.
Open the Servers Folder, and then for each Server configurexecute the following steps:
Open the given server folder
Select Monitor (under server) and the Monitor panel wi
be displayed
If the Monitor is not running, select the Start Monit
menu button at the bottom of the Monitor panel
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
46/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 38Avaya proprietaryuse pursuant to company instructions
A screenshot of a Server Monitor
17 For upgrades of hardened 2.0 systems to 3.0, perform the
following to configure the HTTPS cipher suites: Access the AS 5300 Element Manager Console
o (if MCP FIPS is enabled: run fips-mgmtconsole.bat,
o if MCP FIPS is not enabled: https://:12121)
Login as the "admin" user
Click "+" next to Network Data and Mtc
Click "+" next to Cipher Suites
Click HTTPS Cipher Suites
Modify the HTTPS Cipher Suites to ensure that only the followin
are enabled, disable all others:
SSL_RSA_WITH_3DES_EDE_CBC_SHA
TLS_RSA_WITH_AES_128_CBC_SHA
Click Apply
Restart all Provs and EM (both inactive and active)
18 varies Steps to complete the core components upgrade
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
47/120
2012 Avaya Inc. 39Avaya proprietaryuse pursuant to company instructions
18a
Please refer to sections 3.4and 3.5 for instructions
regarding changes that may be required to the existing dat
Please verify those changes (if any was required) are
completed.
18b Install the 2.1 ASU on the Secondary Servers.
Please reference the following section to install the 2.1A
for the Provisioning Managers and Personal Agent Managers
running on the Secondary Servers. Note that the 8.1 ASU wi
be installed later once the 3.0 system is verified to be
functioning properly
9.1.2 Installing 7.2 Hardened Client ASU files on the
MCP Serverfor instructions regarding the ASU files.
18c Varies The 3.0 Core Components upgrade is now complete. Please
perform some sanity tests using the 7.2 Clients to verify
the 3.0 system is functioning properly.
18d Once it is verified that the 15.1 load is functioning
properly, then simultaneously delete the oldest MCP load
from the Primary and Secondary Element Management Servers.
Normally, the current and previous MCP loads should be
retained on the Element Management Servers. All other ol
loads should be removed.
18e If for some unforeseen reason the 3.0 system becomes non-
operational,please reference Section 11.2Rollback an
entire system, for instructions regarding the rollback ofan entire redundant system to the 2.0 release.
19 25 mins Step to perform once it is verified that the 3.0system is functioning properly
19a 5 mins
Now that all NEs have been upgraded to use the MCP_15.1
load, remove the .zip file from both
Primary and Secondary Element Management Servers
o login as the AA role (ntappadm) to the Primary andSecondary ElementManagement Server
o cd /var/mcp/loads
o rm .zip
oro rm R f v MCP_13* (optional: if you want to remove alMCP_13 directory stored under /var/mcp/loads)
Note:
User should perform the commands in parallel [e.g. have tw
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
48/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 40Avaya proprietaryuse pursuant to company instructions
windows up, one for each EM server, and execute the comman
one after another on the two servers]
19b Time
will
vary
based onthe size
of the
DB.
20 mins
Once the upgrade has completed, a 15.1 Database backupshould be taken (as a precautionary step).
login as the DBA role (ntdbadm) to the server hosting tPrimary Database.
cd /var/mcp/run/MCP_15.1//bin/util
./dbBackup.pl post_15.1_upgrade
Note: The generated DB backup file is stored in the
/var/mcp/db/backup directory.
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
49/120
2012 Avaya Inc. 41Avaya proprietaryuse pursuant to company instructions
Table 5: Post-upgrade steps
Step # Est. Time Description
1 10 mins This step contains the detailed process for taking serverbackups of the upgraded Core system.
Backup configuration data (/admin) for every Core Server.
Backup the Primary and Secondary Element Management Servers
loads, media and install directories.
If you are familiar with the execution of the MCP backup
script, the commands to perform backups are shown below. If
additional details are required, then please refer to
Section 4.3 Backup of an MCS server in 103.2.3 AS 5300
Backup And Restore MOP.
/usr/local/bin/configBkup.pl
For the configuration data and application data(if
available) backup of Core Server, execute the followingcommand,
/usr/local/bin/bkupSvr.pl
For the configurationdatabackup of a Core Server, executethe following command,
/usr/local/bin/bkupPlatform.pl
Recommendation of where to backup is as follows:
1. Set the backup of all servers (except Secondary
Element Management Server) to Secondary Element
Management Server directory /var/mcp/backup/remote/15.
2. The backup of Secondary Element Management Server willbe taken using the local optionin the Secondary
Element Management Server directory
/var/mcp/backup/local/
Note, prior totaking remote backups, please ensure that
/var/mcp/backup/remote/15.1 directory exists on the
Secondary Element Management Servers by executing the
following steps.
o Login as the SSA role (ntsysadm) to the
Secondary Element Management Servers
o su - root
o cd /var/mcp/backup/remoteo ls -l
o Check if 15.1 directory exists. If not, create 15.1
directory as follows:
o mkdir 15.1
o chown root:ntsysgrp 15.1
o chmod 770 15.1
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
50/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 42Avaya proprietaryuse pursuant to company instructions
Once it is ensured that the/var/mcp/backup/remote/15.1
directory exists, follow the steps below to take backups of
the server.
o Login as the SSA role (ntsysadm) to the servers which
you want to take a backup
o For all servers except the Secondary Element Management
Server, execute configBkup to enable remote backupconfiguration parameters for all backup jobs (Select
Option 2).
[ntsysadm@ ]$ configBkup
You are required to set:
o IP address of remote backup server (Primary or
Secondary Element Management Server or any other
server that you want)
o Directory on remote backup server where backup tar
files are located (/var/mcp/backup/remote/15.1)o SSA role (ntsysadm) username to use for remote SSH
commands
o Previously generated SSH keys
o Select exit when finished.
o On the Primary Element Management Server, backup the
Configuration and Application data to the Secondary
Element Management Server
[ntsysadm@ ]$ bkupSvr remote
o On the Secondary Element Management Server, backup the
Configuration and Application data to the SecondaryElement Management Server
[ntsysadm@ ]$ bkupSvr local
[ntsysadm@ ]$ cd /var/mcp/backup/local
[ntsysadm@ ]$ mv mcp* /var/mcp/backup/remote/15.1/
o For all other core servers, backup the Configuration
data to the Secondary Element Management Server
[ntsysadm@ ]$ bkupPlatform remote
2 Varies Steps that can be performed now, or in a laterMaintenance Window
2a Varies Upgrade the MAS components to 3.0
Please reference section 5Appendix A: MAS UpgradeNotesfor
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
51/120
2012 Avaya Inc. 43Avaya proprietaryuse pursuant to company instructions
o Instructions regarding upgrading Multiple MASs.
o Instructions to upgrade the base software on the server.
Note: After upgrade, 2.0 MAS becomes 3.0 AVAYA MS.
2b Varies Upgrade the AudioCodes components to its latest MR (if theyexist in this system)
The upgrade steps are as follows:
1) Upgrade the EMS using 101.2.1 AS 5300 Install & Config
Method for Audiocodes EMS
2) Upgrade the M3K using 101.2.2 AS 5300 Install & Config
Method for Audiocodes M3K GW
3) Upgrade the MP-112/124 IADs, if they exist, using
101.2.3 AS 5300 Install & Config Method for
AudiocodesMP112/124
4) Upgrade the M500s, if they exist, using 101.2.4 AS
5300 Install & Config Method for Audiocodes M800 IAD
Please reference Upgrade/Downgrade the GW/MP Firmware Using EMSsection of the each MOP mentioned in Appendix G: Upgrade
AudioCodes to its latest MR for Instructions to upgrade
the base software on the server.
2c If for some unforeseen reason, the Audiocodes or 15.1 AVAYA
MS need to rollback, follow the procedures below:
AudioCodes Gateways or MPs: (if it has been upgraded to15.1)For procedure to rollback/downgrade Audiocodes, please refer
to Upgrade/Downgrade the GW/MP Firmware Using EMS section in each
of the MOPs mentioned in Appendix G: Upgradethe AudioCodesFirmware for Instructions to downgrade/rollback the base
software on the server.
AVAYA MS: (if it has been upgraded to 15.1)The steps to restore the 13.0 MAS are defined in Section 0
3 5 mins Clean up the /var/mcp/backup/remote directory
Once the MCP 15.1 System has been operating satisfactory for
a period of time (a few days), the 13.0 directory can be
removed. Please note that once the/var/mcp/backup/remote/13.0 directory is removed, the server
rollback to the previous releasewill not be possible.
Login as the SSA role (ntsysadm) to the Primary Element
Management Server
su - root
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
52/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 44Avaya proprietaryuse pursuant to company instructions
cd /var/mcp/backup/remote
rm rf 13.0
4 Note: This step is applicable only for Federal Civilian andEnterprise. For DoD, the ASU patch will be delivered viaDVD.
Execute this step to download the ASU patch only if a 15.1.xpatch was downloaded in step 12 of Table 2: PreparatorySteps.
Download the Hardened Client related software for this 15.1
MR patch.
For example:
Title:
o HardenedClient8.1.
o ASU HardenedClient 8.1.
Transfer the Hardened Client to the proper location.
o Login as the AA role (ntappadm)to the serverhosting the Primary EM.
o cd /var/mcp/media
o ls HardenedClient_8.1.
where is the Hardened Client
version number for the patch found above
o If this directory exists, skip the rest of the
Patching ASU procedure since there is no need to
download the Hardened Client.
o mkdir HardenedClient_8.1.
o chmod 770 HardenedClient_8.1.
o cd HardenedClient_8.1.
Download the
ASU_HardenedClient_8.1..zip
o unzip ASU_HardenedClient_8.1..zip
o rm ASU_HardenedClient_8.1..zip
o chmod 660 *
o cd ..
o ls
o Remove the older Hardened Client ASU files that wer
extracted from the 15.1.x Core App Bundle.
rm -rf HardenedClient_8.1.
5 Install the ASU files for the 8.1 Hardened Client on thePrimary and Secondary PROV/PA server(s).
Please reference the below section to install the 8.1 ASU
for the Provisioning Managers and Personal Agent
Managers.
9.1.1Installing 8.1 Hardened Client ASU files on the AS
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
53/120
2012 Avaya Inc. 45Avaya proprietaryuse pursuant to company instructions
5300 3.0 Server
6 5 mins To capture the timestamps for the upgrade scripts that wereexecuted on the server hosting the Primary EM.
Login as the AA role (ntappadm) to the Primary Element
Management Server cd /var/mcp/run/install/logs
find . -mtime -3 | xargs fgrep " at => " | tee
timestamps_file
Note: The command above is capturing timestamps from the
log files which are less than 3 days old. Output from the
command is displayed to screen, and written to the
timestamps_file. In addition, you can change the number
of days (-3) if needed.
7 Perform Network separation (optional), once it is verifiedthat Media Server and Audiocodes are working fine with SIP
Core.
In AS 5300 3.0 the system can be configured to use separate
networks for Internal OAM, External OAM, Signaling and Media
traffic. To configure the system in this way, please
reference the 105.1.1 AS 5300 Network Separationdocument
for configuring the VLAN.
8 Manually Configure IPv6 (optional)
If the servers had IPv6 enabled prior to the upgrade, then
using the IPv6 data written down in the pre-upgrade steps,refer to the IPv6 Configuration MOP and perform all the
steps in that doc to manually re-configure IPv6 on each IPv6
capable server.
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
54/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 46Avaya proprietaryuse pursuant to company instructions
3.2Steps to Update the License KeyAn alarm will be raised by the Element Manager when the EM and DB areupgraded to the 15.1 release, and the 13.0 License Key is still being used.
Figure 4: Management Console License Key Invalid Alarm
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
55/120
2012 Avaya Inc. 47Avaya proprietaryuse pursuant to company instructions
To update the License Key from the Management Console, the user selects theNetwork Data and Mtc=>Licensekey menu option from the System tree as shownin the following figure.
Figure 5: Management Console Update License Key Right-Click Option
The Edit option is available from the bottom of the License Key panel as shownin the above figure.
Once the Edit button is selected, a dialog box is displayed to the Administrator toUpdate the License Key. The Update window is shown inFigure 6: ManagementConsole Update License Key Window.
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
56/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 48Avaya proprietaryuse pursuant to company instructions
Figure 6: Management Console Update License Key Window
Once the new license key is selected, click on open and license key information isdisplayed as shown in the following figure. To enter the new license key, click onapply.
Figure 7: Management Console License Key Information Dialog
In addition, the alarm shown inFigure 4: Management Console License KeyInvalid Alarm,will be cleared once a valid license key is entered.
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
57/120
2012 Avaya Inc. 49Avaya proprietaryuse pursuant to company instructions
3.3Steps to find/stop/undeploy Primary/Stand-byNEs
To find/stop/undeploy NEs executing on the Primary/Secondary Servers, you first
must know the Server Names for the Primary/Stand-by Servers that the NEs aredeployed to.
If you do not know the Server names, but do know the IP addresses of the serversin question, then first display the Servers Panel to find the Interface 1 value forthe given servers.
Figure 8: Management ConsoleServers Panel
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
58/120
Document Version 2.6 Method of Procedure
2012 Avaya Inc. 50Avaya proprietaryuse pursuant to company instructions
Then display the Addresses panel to display the mapping of IP address to LogicalInterface name. Matching the Logical Name to the above Interface 1 value will
give you the Server Name to IP address mapping required.
Figure 9: Management ConsoleIP Addresses Panel
Tofind/determine the NEs that are deployed to a serveror set of servers, bring upthe Physical view from the Management Console (which is the 5thICON from theleft, below the Main Menu Bar).
Figure 10: Management ConsolePhysical View ICON
8/10/2019 102.2.3_AS5300_3.0-2.0_to_3.0_SIP_CORE_Upgrade
59/120
2012 Avaya Inc. 51Avaya proprietaryuse pursuant to company instructions
The physical view panel is displayed once the ICON has been selected. From thePhysical View panel, open up the Physical Sites folder, the Site1 folder, and thenthe Servers Folder, as shown inFigure 11: Management ConsolePhysical Viewpanel.