Академический Документы
Профессиональный Документы
Культура Документы
0Ava
tion Srv Avaya Application Server 5300 R3.0Ava
Avaya Application Server 5300 R3.0Ava
102.2.3 AS 5300 3.0 - 2.0 to 3.0 SIP CORE Upgrade
Method of Procedure
Product Release:
AS 5300 R3.0
Document Version:
2.6
Document Status:
Released
Security Classification:
Avaya Confidential
Revision History
Version Date
Description
0.0
November 3, 2010
Initial Draft
0.1
0.2
March 1, 2011
0.3
0.4
April 1, 2011
0.5
0.6
0.7
May 4, 2011
0.8
May 5, 2011
0.9
1.0
1.1
August 8,2011
1.2
August 10,2011
1.3
1.4
1.5
1.6
1.7
1.8
1.9
October 1, 2011
2.0
2.1
2.2
Nov 7, 2011
2.3
2.6
Method of Procedure
Version Date
Description
Added instructions to access EM console in FIPS compliant
mode after upgrade.
Updated Data Changes section.
2.4
2.5
Feb 8, 2012
2.6
ii
Table of Contents
1 Upgrade AS 5300 2.0 Release to 3.0 .......................................................................... 1
1.1
1.2
1.3
3.2
3.3
3.3.2
3.4
3.4.1
3.4.2
Provisioning Data changes that may be required after the Database Upgrade..........................58
3.5
4.1
5.2
7.2
7.3
User Forced Out msg or Unable to launch MCP Mgmt Console .................................71
9.1.1
Installing 8.1 Hardened Client ASU files on the AS 5300 3.0 Server ...........................75
2012 Avaya Inc.
Avaya proprietary use pursuant to company instructions
iii
2.6
Method of Procedure
9.1.2
Installing 7.2 Hardened Client ASU files on the MCP Server ......................................76
12.2.2
iv
List of Figures
Figure 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 Console Servers Panel ..........................................................................49
Figure 9: Management Console IP Addresses Panel .................................................................50
Figure 10: Management Console Physical View ICON ...............................................................50
Figure 11: Management Console Physical View panel ...............................................................51
Figure 12: Management Console Physical View with Servers/NE instances...............................52
Figure 13: Management Console Config Tree ............................................................................53
Figure 14: Management Console NE Maintenance Panel ..........................................................54
Figure 15: Management Console Undeploy 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 for 13.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 load from the NE instance window .................................68
Figure 24: Apply the 15.1 load from the pop up window .............................................................68
Figure 25: Deploy a NE Instance Maintenance panel .................................................................69
Figure 26: Start a NE Instance Maintenance panel.....................................................................70
2012 Avaya Inc.
Avaya proprietary use pursuant to company instructions
2.6
Method of Procedure
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
vi
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
vii
To upgrade from the 2.0 release, the latest Released status MR must be installed
on the given system.
Information regarding the Latest General Available MR and/or Patch load can be
checked from the Application Server 5300 web page via the following link. Be
sure 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 firmware
phones, 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 all
Provisioning/Configuration Data. Note that the Data Freeze for Provisioning
Data 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 been
upgraded (as noted within the MOP itself below).
The primary role of a user can be determined by executing the roles command
as shown below:
[ntappadm@zngdy18a install]$ roles
roles for ntappadm are: AA
2012 Avaya Inc.
Avaya proprietary use pursuant to company instructions
Method of Procedure
If required, the primary role of a user can be changed by executing the chrole
<newrole> 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.
Note, that even for the pre-configured system, there are no guarantees that the
default username will exist (a customer can delete these usernames and add
back their own usernames for each role).
The user might or might not be prompted for a password when they login as the
SSA role (ntsysadm) and execute the "sudo" command (or any command that is
aliased to an underlying sudo command). If the system does prompt for the
password, 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/<MCP release>/<dbName> directory is
/var/mcp/run/<MCP release>/<dbName>/work or
/var/mcp/run/<MCP release>/<dbName>/installLogs
When following the steps in this MOP you will notice that instead of
cut&pasting information within the MOP, the MOP references the given Step or
Section (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 two
different windows. One window will be used for working on each step in the
given Upgrade Table, and the other window will be used to look up references to
other steps/sections. If you are using a Hardcopy of the MOP, then when a
reference to another step/section comes up, then create two stacks from the
MOP such that the current page/step stays at the top of one stack, and thus is
not lost when looking up the referenced step/section.
2012 Avaya Inc.
Avaya proprietary use pursuant to company instructions
This document will generally use the terms AS 5300 2.0 and AS
5300 3.0 when referring to the two releases involved in this
upgrade process.
Step #
Description
3a
3b
Method of Procedure
3d
4a
4b
Method of Procedure
2 Preparatory Steps
The table below contains a list of steps that must be performed/verified prior to the day
when the actual Upgrade to AS 5300 3.0 procedure is performed. Given the low
impact to service of the Prep Steps, they can be performed during normal operational
hours if needed. However with any operation at a customer site, a Maintenance Window
during off-hours prior to the day of actual upgrade is the preferred timeframe.
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
Ensure the person performing the upgrade knows how to launch the
System Management Console, and how to use it.
For details regarding how to launch a System Management Console,
please refer to section 7.1 of Appendix D: MCP SM/EM CONSOLE Notes.
4a
Ensure the 2.0 onlineHelp file and ASU (Automatic Software Update)
files exist on the Primary Element Management Server
mcpExtractContent o -aat
Note:
The AS 5300 2.0 load zip file will be copied to the
/var/mcp/loads directory.
Note: Remove the extracted ASU 7.2 files by following the steps below.
4b
cd /var/mcp/media
rm rf HardenedClient_7.2.XXX
Save the 2.0 ASU files to the Primary Element Management Server to be
used during upgrade/rollback.
Note:
- Even though the system may have more than one PROV, only one copy of
the Online Help file is required.
2012 Avaya Inc.
Avaya proprietary use pursuant to company instructions
Method of Procedure
cd /var/mcp/media
mkdir HardenedClient_ASU_preupg
o exit
Login as the AA role (ntappadm) to the Primary Element
Management Server
cd /var/mcp/media
2012 Avaya Inc.
Avaya proprietary use pursuant to company instructions
4c
4d
Backup Preparation
AS 5300 2.0 backups taken for the upgrade to the 2.0 release will be
stored 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
Method of Procedure
Notes:
The server restore logic will only look for server backup
filenames formatted like mcpPlatform*.tar.
Core Servers
If 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 Secondary
Element 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
[ntsysadm@ ]$ configPlatformBkup
o
10
o
o
o
to be stored (/var/mcp/backup/remote/13.0)
SSA role (ntsysadm) username to use for remote SSH commands
Previously generated SSH keys
Select exit when finished.
4g
Server information required when rolling back the server to the 2.0
release
Note that this information is required to rollback to 2.0 if the
upgrade to 3.0 runs into some unforeseen issue.
11
Method of Procedure
o The user will be the SSA role (ntsysadm) for the server
backups
mcpShowNwkConfig
or
o
su -
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 Database
o 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 AudioCodes EMS
The new (AS 5300 3.0) License Key is required to deploy the AS 5300
3.0 load. And a new AVAYA MS 7.5 license key is also required for the
applicable 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 Key
have been obtained.
For information about generating/retrieving a license key, please
refer to Appendix L: Retrieving the MCP License Key.
12
13
Method of Procedure
14
10.
11.
12.
15
Method of Procedure
then select Monitor. From the <DBname> 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
Server
Name
Server IP
address
Associated
NEs
In addition, a list of the Non-Core Servers should be generated. NonCore Servers are servers in which one of the following components are
deployed/running:
MAS
AudioCodes
If the MASs are configured in a redundant configuration, then
reference 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 CDs
exist.
These are needed if a system rollback from 3.0 to 2.0 is required for
some unforeseen reason.
11
16
Extract the latest 3.0 Linux OS Platform Patch to all servers in the
system.
Execute the following steps on the Primary Element Management Server
If 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-<patch>.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 <aa_role_user>@<target_server>
- cd /var/mcp/media
- put mcp_core_linux_ple2_<patch>.iso
Execute the following steps on each remaining server on the Primary
and 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-<patch>.iso .
- chown root:root mcp_core_linux_ple2-<patch>.iso
- chmod 400 mcp_core_linux_ple2-<patch>.iso
17
Method of Procedure
- mcpExtractContent o aat
Note:
12
Please determine if there are patches available for the 3.0 MR that is
being upgraded.
13
14
18
19
Method of Procedure
The following diagrams show the MCP systems are divided into two groups
Primary Servers and Secondary Servers.
Figure 1: Small (2 server) SIP Core configuration
20
Note: A data freeze for all provisioning and configuration data must take place after Step
2c. Therefore, it is recommended to execute Step 2a to Step 2c of Table 3: Pre-upgrade
steps for a MCP Redundant configuration system no more than two hours prior to the
maintenance window scheduled for the upgrade.
Table 3: Pre-upgrade steps for a MCP Redundant configuration system
Step # Est. Time
Description
N/A
25 mins
21
5 mins
Method of Procedure
Ensure there are very few deferred DB transactions for the
Database
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 there
is 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-><DBname>
folders, and 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 below).
22
23
Time
will
vary
based on
the size
of the
DB
Method of Procedure
Take a backup (e.g. export) of the data in the database for
safe keeping.
login as the DBA role (ntdbadm) to the server hosting the
primary Database
cd /var/mcp/run/MCP_13.0/<dbName>/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
The following table contains the detailed steps for performing the upgrade.
Table 4: Upgrade a MCP (Redundant configuration) system
Step #
Est. Time
Description
5 mins
1a
24
1b
5 mins
2a
15 mins
(per
server)
2b
Install the latest OS patch (if any)
2012 Avaya Inc.
Avaya proprietary use pursuant to company instructions
25
Method of Procedure
20 -40
mins
3a
0 mins
26
10 - 30
mins
cd /var/mcp/install
./mcpUpgradeNextRel.pl
o
Note:
The upgrade script will stop/undeploy SM_1 instance and
deploy/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).
o
o
cd /var/mcp/install
./mcpDbSwPatch.pl primary
27
Method of Procedure
o
o
o
o
o
o
o
o
o
o
su root
cd /var/mcp
chmod 660 <15.1.x.y_patch_name>
chown ntappsw:ntappgrp <15.1.x.y_patch_name>
mv <15.1.x.y_patch_name> /var/mcp/dropbox
Login as the AA role (ntappadm) to the Primary
Element Management Server
cd /var/mcp/loads
ls (wait for the patch load to be generated, note
that you might need to wait up to 10 minutes)
cd /var/mcp/install
./mcpPatch.pl
4a
5 mins
Note 1:
To access AS 5300 Element Manager Console in FIPS compliant
mode,a new fips-mgmtconsole.zip file must be downloaded and
unzipped EVERY time the MCP system is upgraded.
The following are quick reference steps:
1.
2.
3.
29
Method of Procedure
4b
30
4c
Console:
15 mins
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 is
Unavailable. Stop or kill the NE before deploying it.
Reference section 7.2 Deploy/start a Network Element (NE)
if additional details are needed for this process.
5b
31
Method of Procedure
32
10 mins
6a
10 mins
20 mins
7a
Varies
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) stopped
and still on the 2.0 release.
Please perform some sanity tests using 7.2 Hardened clients
to verify the 3.0 non-redundant system is functioning
properly.
2012 Avaya Inc.
Avaya proprietary use pursuant to company instructions
33
Method of Procedure
9a
With the 3.0 simplex system up and running, the customer can
begin making user data provisioning changes via the 3.0
NEs/components running on the Primary Servers (e.g. the data
freeze for provisioning user data is now off). However,
note that in the unlikely event that the 3.0 system is
rolled back to the old/previous 2.0 system, any/all
provisioning changes made to the 3.0 system will be lost.
10
10 mins/
server
10a
Secondary
Secondary
Secondary
Secondary
10 mins
34
cd /var/mcp/install
./oracleUninstall.pl -secondary
./mcpDbSwInstall.pl -secondary
12
12b
13
25 mins
13a
35
Method of Procedure
14
15
25 mins
15a
25 mins
16
16a
5 mins
36
will be displayed
If the Monitor is not running, select the Start
Monitor menu button at the bottom of the Monitor
panel
Close these panels
Note:
You might need to re-start DB monitor for DB instance 0, if
Replication tab is not displayed after DB resync
completes.
A screenshot of the Database Monitor
16b
37
Method of Procedure
17
18
varies
38
18a
Please refer to sections 3.4 and 3.5 for instructions
regarding changes that may be required to the existing data.
Please verify those changes (if any was required) are
completed.
18b
18c
Varies
18d
18e
19
19a
If for some unforeseen reason the 3.0 system becomes nonoperational, please reference Section 11.2 Rollback an
entire system, for instructions regarding the rollback of
an entire redundant system to the 2.0 release.
25 mins
5 mins
Now that all NEs have been upgraded to use the MCP_15.1
load, remove the <13.0.x_loadname>.zip file from both
Primary and Secondary Element Management Servers
o login as the AA role (ntappadm) to the Primary and
Secondary Element Management Server
o cd /var/mcp/loads
o rm <13.0.x_loadname>.zip
or
o rm R f v MCP_13* (optional: if you want to remove all
MCP_13 directory stored under /var/mcp/loads)
Note:
User should perform the commands in parallel [e.g. have two
2012 Avaya Inc.
Avaya proprietary use pursuant to company instructions
39
Method of Procedure
windows up, one for each EM server, and execute the commands
one after another on the two servers]
19b
Time
will
vary
based on
the size
of the
DB.
20 mins
40
Description
10 mins
If
41
Method of Procedure
Varies
2a
Varies
42
Varies
5 mins
43
Method of Procedure
cd /var/mcp/backup/remote
rm rf 13.0
Install the ASU files for the 8.1 Hardened Client on the
Primary and Secondary PROV/PA server(s).
5 mins
45
Method of Procedure
46
To update the License Key from the Management Console, the user selects the
Network Data and Mtc=>Licensekey menu option from the System tree as shown
in 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 shown
in the above figure.
Once the Edit button is selected, a dialog box is displayed to the Administrator to
Update the License Key. The Update window is shown in Figure 6: Management
Console Update License Key Window.
47
Method of Procedure
Once the new license key is selected, click on open and license key information is
displayed as shown in the following figure. To enter the new license key, click on
apply.
Figure 7: Management Console License Key Information Dialog
48
49
Method of Procedure
Then display the Addresses panel to display the mapping of IP address to Logical
Interface 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 Console IP Addresses Panel
To
find/determine the NEs that are deployed to a server or set of servers, bring up
the Physical view from the Management Console (which is the 5th ICON from the
left, below the Main Menu Bar).
Figure 10: Management Console Physical View ICON
50
The physical view panel is displayed once the ICON has been selected. From the
Physical View panel, open up the Physical Sites folder, the Site1 folder, and then
the Servers Folder, as shown in Figure 11: Management Console Physical View
panel.
Figure 11: Management Console Physical View panel
Then under the Servers folder, open the folder for each physical server that you
are searching to find the deployed NEs for. In the screenshot below the
EMServer1, and the SESMServer1 have been opened, and then the Instances
folder opened to display the NE instances that are deployed onto each of these
servers.
51
Method of Procedure
Once the NE Instances are found/determined for the given physical servers, then
for each NE Instance perform the steps in section 3.3.1 Steps to Stop a given
NE to stop the NE Instance.
52
Then open the appropriate component type folder for the NE instance (e.g.
Session Managers), and then open the folder with the given NEname, and select
the NE Maintenance service under that NEs folder. The screenshot below
shows the NE Maintenance panel for the SESM1 NE.
53
Method of Procedure
To stop the NE instance from the NE Maintenance panel, select the given Instance
from the panel, and then select the Stop ICON (Red Stop Light 4th ICON from
the left) at the bottom of the Maintenance panel.
54
55
Method of Procedure
56
Section
Filename
Currently, there are no Config Data changes defined/required for this upgrade.
57
Method of Procedure
58
ASU
CD-ROM
DVD
DB
Database
EM
Gig
Gigabyte
GUI
IP
Internet Protocol
IPCM
IP Client Manager
MAS
MCP
MOP
Method of Procedure
OS
Operating System
PC
Personal Computer
SIP
SM
SSA
SSH
Secure Shell
URL
59
Method of Procedure
60
61
Method of Procedure
Default is 0.
62
63
Method of Procedure
64
The SM/EM console will automatically load/install using files resident on the
SM/EM.
For redundant System/Element Manager installations select the correct one from the drop
down menu and press connect.
Figure 18:
Figure 19:
65
Method of Procedure
Select Ok.
Note: If the Pre and Post Login Security Banners are enabled in the system, the
Pre-Login banner is displayed and need to be acknowledged before attempting to
login and the Post-Login banner is displayed and need to be acknowledged after
logging in to proceed with the main Management Console screen.
66
If you are not able to launch the Management Console, please refer to section 7.3
User Forced Out msg or Unable to launch MCP Mgmt Console.
Open the Network Elements folder, and then open the folder for the type of
component and the folder for the currently configured NE that you are going to
deploy/start. Under the given NE folder, select Instance (to display the NE
Instance window), and then select NE Maintenance (to display the NE
Maintenance window).
The given NE instance must be in an Offline or Configured State (shown
in the NE Maintenance window), before the load can be updated (in the NE
Maintenance window). Thus, if the NE instance being updated is not in the
OffLine or Configured State, then select the instance from the NE Maintenance
window and select the Stop ICON (4th from the left). If for some reason the NE
does not go to the OffLine or Configured state, then select the Kill ICON (ICON
farthest to the right) to kill the instance.
2012 Avaya Inc.
Avaya proprietary use pursuant to company instructions
67
Method of Procedure
To deploy and start an NE using the new load, the instance must be modified to
use (e.g. configure) the 3.0 load.
To modify the load, select the instance from the NE Instance window and select
the Edit ICON (2nd from the left). In the new pop up window, click on the drop
down menu next to Load or Patch, select the latest load and click Apply.
Figure 23: Configure a NE to the 15.1 load from the NE instance window
Figure 24: Apply the 15.1 load from the pop up window
68
Once the load has been updated to the new 3.0 load, then from the NE
Maintenance panel, select the instance, and then select the first ICON (from the
left) to deploy the instance. FYI - if you place your cursor over the first ICON, it
will show that the ICON is the Deploy Icon, as shown below.
Figure 25: Deploy a NE Instance Maintenance panel
69
Method of Procedure
Once the NE has been deployed, from the same NE Maintenance panel select the
third ICON (from the left) to start the instance. FYI - if you place your cursor
over the third ICON, it will show that the ICON is the Start Icon, as shown
below.
Figure 26: Start a NE Instance Maintenance panel
Once the NE has started successfully, it will go to the Active or Hot Standby
state.
70
OR
If any of the following error messages is received (most likely
after a 3.0 Mgmt console has been used, and then you are
attempting to use the old 2.0 Mgmt Console):
71
Method of Procedure
Once the MCP Mgmt Console Application(s) have been removed, then
exit from the above window (click on the Close button), and then
try opening the Management Console from an Internet Explorer
window again.
72
73
Method of Procedure
Once the zip file has been installed onto the server hosting the Provisioning
Manager/Personal Agent, then execute the utility script to extract all of the help
files from the MCP-OnlineHelp zip file.
6. cd /var/mcp/run/MCP_15.1/PROV1_0/bin
7. ./installHelp.pl z MCP-OnlineHelp_15.1.X_<date-time>.zip
With the Help files successfully extracted from the MCPOnlineHelp_13.0.X.X_<date-time>.zip file, the updated Online Help Files will now
be accessible from the Provisioning Manager/Personal Agent client and the 7.2
PCClient.
74
75
Method of Procedure
Once the files have been installed onto the server hosting the Provisioning
Manager/Personal Agent, then execute the utility script to extract the ASU files.
8. cd /var/mcp/run/MCP_15.1/PROV1_0/bin
9. ./installASU.pl -j HardenedClient_8.1.<release info>_Release.jnlp -s
HardenedClient_8.1.<release info>_Release.zip u
HardenedClient_8.1.<release info>_UnsignedRelease.zip
- where <release info> is the release number and date of the client
9.1.2 Installing 7.2 Hardened Client ASU files on the MCP Server
Note, in the example below the Provisioning Manager has been named PROV1.
Thus, replace PROV1 with the name that has been given the Provisioning Manager or
Personal Agent Manager within your system.
The HardenedClient.jnlp and HardenedClient.zip files should already be on the server
(this was performed in the Step 4b of Table 2: Preparatory Steps).
To download the jnlp and zip files to a server hosting Provisioning
Manager/Personal Agent:
1. login as the AA role (ntappadm) to the server hosting Provisioning
Manager/Personal Agent
2. cd /var/mcp/media/prov_pa_installs/
If the Provisioning Manager/Personal Agent is not on the Primary Element
Management Server, execute step 3 to sftp the jnlp and zip files from the Primary
Element Management Server and proceed to step 8, otherwise proceed to step 4.
3. sftp the HardenedClient.jnlp, HardenedClient_Release.zip and
HardenedClient_unsigned.zip files from the Primary Element Management
Server.
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 AA role (ntappadm) password
o cd /var/mcp/media
o cd HardenedClient_ASU_preupg
o get HardenedClient.jnlp
o get HardenedClient*.zip
o exit
If the Provisioning Manager/Personal Agent is on the Primary Element
Management Server, execute step 4-6 to copy the jnlp and zip files from the
/var/mcp/media directory.
4. ls /var/mcp/media
5. cp /var/mcp/media/HardenedClient_ASU_preupg/HardenedClient.jnlp .
6. cp /var/mcp/media/HardenedClient_ASU_preupg/HardenedClient*.zip .
7. ls /var/mcp/media/prov_pa_installs
2012 Avaya Inc.
Avaya proprietary use pursuant to company instructions
76
Once the jnlp and zip files have been installed onto the server hosting the
Provisioning Manager/Personal Agent, execute the following steps to install the ASU
files.
8. cd /var/mcp/run/MCP_15.1/PROV1_0/bin
9. ./installASU.pl -j HardenedClient.jnlp -s HardenedClient_Release.zip u
HardenedClient_unsigned.zip
-
77
Method of Procedure
78
A redundant system is being upgraded, and after half of the system has been
upgraded, it was determined that the new system (AS 5300 3.0) was not
functioning correctly. Thus, a decision was made to take that half of the
system back to the previous release (AS 5300 2.0) that had been running
(from Step 11 of section 0 ). For this scenario, follow the steps defined in
section 11.1 Rollback one half of an upgraded system.
An entire redundant system has been upgraded to AS 5300 3.0 and it was
determined that the AS 5300 3.0 system was not functioning correctly. Thus,
a decision was made to go back to the AS 5300 2.0 release that had been
running prior to the upgrade. For this scenario, follow the steps defined in
section 11.2 Rollback an entire system.
Note:
If during the steps to rollback a AS 5300 system, you receive the message User
Forced Out when attempting to login to a 2.0 System Management Console, then
please reference section 7.3 User Forced Out msg or Unable to launch MCP
Mgmt Console, for details of a workaround for this known Java Web Start issue
(that can occur when switching back and forth between login to Management
Consoles on different MCP releases).
Note: When the Primary servers are rolled back, the data on these servers will
be removed completely, but the data on the Secondary servers will be
retained.
Table 9: Downgrade one half of a Redundant system
Step # Est. Time Description
1
5mins
79
Method of Procedure
be stored in /var/mcp/backup/remote/13.0 on
the Secondary Element Management Server from
previous Preparatory Steps.
Note: For safe keeping, also save off a copy
of the 2.0 backup files to local PC, or USB
drive, or remote disk.
In addition, if any changes were made to the
data stored in the 3.0 Database, those
changes will be lost when the DB is restored
with the 2.0 backup.
2
15 mins
2a
5 mins
Element Manager
3a
From the
Management Console:
80
4
4a
81
Method of Procedure
[ntsysadm@ ]$ configBkup
You are required to set:
o IP address of remote backup server
(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/13.0)
o SSA role (ntsysadm) username to use for
remote SSH commands
o Previously generated SSH keys
o Select exit when finished.
o Execute the restoreSvr script to restore the
Application data on the Primary Element
Management Server
[ntsysadm@ ]$ restoreSvr remote
4b
1 hour
82
5b
60 mins
6a
15 mins
6b
From the
Management Console:
83
Method of Procedure
For each NE on the Primary Servers, deploy and start
the NE instance from the NE Maintenance window on the
System Management Console.
Recommended order of deploying and starting NEs
according to their types is as follows:
o Provisioning Managers
o Personal Agent Managers
o Accounting Managers (deploy only)
o Session Managers
5 mins
Restart
running
traffic
Primary
84
7a
5 mins
7b
7c
varies
8a
5 mins
8b
varies
85
Method of Procedure
7.2 ASU for the Provisioning Managers and Personal
Agent Managers running on the Primary Servers.
9.1.2 Installing 7.2 Hardened Client ASU files
on the MCP Server
10 mins
9a
10
5 mins
86
- get *.tar
Note 2:
For safe keeping, also save off a copy of
the 2.0 backup files to local PC, or USB
drive, or remote disk.
Note 3:
In addition, if any changes were made to the
data stored in the 3.0 Database, those
changes will be lost when the DB is restored
with the 2.0 backup.
0a
N/A
87
Method of Procedure
DB and the NE instances in a single (one-by-one)
fashion, and the NEs will connect to the correct DB
based on the current load/version installed.
0b
1 hour/
NE
5 mins
1a
10 mins
2a
10 mins
10 mins
88
3b
4
4a
120
mins
Note 1:
If re-install platform using the data stored on
Primary Element management Server and IPSec is
enabled, then IPSec need to be disabled before
executing step 5 of above mentioned section 10.1 and
IPSec need to be re-enabled after step 15 of section
10.1 is completed for all the primary servers.
Method of Procedure
cd /var/mcp/loads/<MCP_13.0load>/install_scripts/bin
cp * /var/mcp/install
cp .* /var/mcp/install
cd /var/mcp/install
On the primary EMS (currently running 15.1),
change the ne.load within the installprops.txt
file to point to the MCP_13.0 load you are
rolling back to (if ne.load is not set
correctly)
o To do this run the command :
./populateInstallprops.pl
./oracleInstall.pl -secondary
./oraclePatch.pl -secondary
o cd /var/mcp/backup/local
o Transfer backup file mcpApp.<Primary EM
Server's hostname>.<date.time>.tar from remote
backup server:
2012 Avaya Inc.
Avaya proprietary use pursuant to company instructions
90
o mv mcpApp.<Primary EM Server's
hostname>.<date.time>.tar mcpApp.<Secondary EM
Server's hostname>.<date.time>.tar
o Execute the restoreSvr script to restore the
Application data on the Secondary Element
Management Server
[ntsysadm@ ]$ restoreSvr local
91
Method of Procedure
5a
Varies
(30
mins)
92
cd /var/mcp/run/MCP_13.0/<DBname>_1/bin/util
./dbRestore.pl repdbupgrade.tar.gz
o repdbupgrade.tar.gz is the name of the
13.0 backup taken prior to the upgrade
starting
Verify the import worked successfully - from the
messages displayed to the screen.
Note that once the Secondary DB has been rolled back,
several alarms should be displayed on the Management
console stating the given component cannot connect to
the Secondary DB nor have database Communication
Error. Disregard these alarms and continue with this
process.
5b
Management Console:
93
Method of Procedure
displayed
Select the previously deployed 13.0 loadname
from the pulldown list (the previous 13.0 load
may already be selected - from the data that was
restored in the Database.)
Click the apply button
Deploy and start the NE instance from the NE
Maintenance window for all the NEs on Secondary
Server except Secondary System Manager. (DO NOT
deploy and start Secondary SM from NE Maintenance
window on SM CONSOLE)
cd /var/mcp/install
./smDeploy.pl
./smStart.pl
10 mins
94
6b
6c
Management Console:
8
8a
0 mins
120
mins
95
Method of Procedure
cd /var/mcp/backup/remote/
mkdir 13.0
chown root:ntsysgrp 13.0
chmod 770 13.0
- get *.tar
8b
96
[ntsysadm@ ]$ configSvrBkup
97
8c
Method of Procedure
cd /var/mcp/install
./oracleInstall.pl -primary
./oraclePatch.pl -primary
9a
60 mins
98
9c
60 mins
10
10a
15 mins
99
Method of Procedure
10 mins
100
12
10 mins
kill the NE
redeploy the NE
start the NE
Restart
running
traffic
Primary
12a
13
varies
13a
5 mins
101
Method of Procedure
the 13.0 OnlineHelp for the Provisioning Managers and
Personal Agent Managers running on the Primary and
Secondary Servers.
8.1 Install the AS 5300 2.0 OnlineHelp files
13b
varies
14
14a
10 mins
install the
Personal
Secondary
ASU files
102
103
Method of Procedure
This script will produce output detailing the progress of the patch process. At the
completion of the database schema and System Manager patch, the output should
indicate that the database and both System Manager instances have been patched
and the patched System Manager instances have been started. The system is ready
for the next step in the patch process.
Note: If the mcpPatch.pl script fails (i.e. the network goes down and
communications fail when upgrading the DB or the SM), once the problem is
corrected, the mcpPatch.pl script should be re-executed. This should be done at
least once prior to contacting the support teams as this will be successful in most
cases.
o Re-login to the MCP System Management Console.
Result:
The EM has been started and is in Active state running on the desired load. A
new MCP System Management Console has been started.
104
105
Method of Procedure
2. The Load Manager application shows what NEs need to be patched based upon
the patch selected. Select the patch load that the system is being patched to in the
in the Load or Patch dropdown box.
Figure 28: Selecting the patch load in the Load Manager
106
3. Once the patch load is selected, expand the Network Element branch in the Load
Manager tree and select the Network Element to be patched. In the Figure below,
applying a patch to Session Manager is shown as an example.
Figure 29: Patch Session Managers
107
Method of Procedure
4. Once the Network Element is selected, the patch button on the bottom of the Load
Manager application can be used to patch the Network Element instances. Once
the patch process has begun, the NE Maintenance Panel will be launched to
monitor the patch of the Network Element. As an example, the application of
patch to the Session Manager is shown in the Figure below.
Figure 30: Session Manager Patch
5. If the Network Element is fault tolerant, both instances of the Network Element
will be patched. The details of the patch can be monitored by clicking the
Details button on the NE Maintenance panel.
Note: These steps must be repeated for each Network Element if multiple Network
Elements are present in the tree in the Load Manager application in the MCP System
Management Console.
Result:
The Instance window for the Network Element shows one or more instances. If
there is one instance, it is in the ACTIVE state. Additional instances, if present,
are in the HOT STANDBY state in case of Network Element that is supported
2012 Avaya Inc.
Avaya proprietary use pursuant to company instructions
108
in hot standby mode such as Session Manager. The load name listed for each
instance is the patched load.
109
Method of Procedure
Login to the EM console, the title bar of the console shows the AS 5300
2.0.x.y load deployed in the system.
Where:
The letter y represents the current patch level
110
111
Method of Procedure
112