Avaya CMS Base Load Upgrade 19.2 March 2021

Avaya Call Management System
Base Load Upgrade
Release 19.2
Issue 1
March 2021
© 2020-2021 Avaya Inc. OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT
All Rights Reserved. EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM
ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA
Notice CHANNEL PARTNER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL
While reasonable efforts have been made to ensure that the information in this ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE
document is complete and accurate at the time of printing, Avaya assumes no SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR
liability for any errors. Avaya reserves the right to make changes and USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,YOU, ON
corrections to the information in this document without the obligation to notify BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE
any person or organization of such changes. INSTALLING, DOWNLOADING OR USING THE SOFTWARE
(HEREINAFTER REFERRED TO INTERCHANGEABLY AS “YOU” AND “END
Documentation disclaimer USER”), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A
“Documentation” means information published in varying mediums which may BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
include product information, operating instructions and performance APPLICABLE AVAYA AFFILIATE (“AVAYA”).
specifications that are generally made available to users of products. Avaya grants You a license within the scope of the license types described
Documentation does not include marketing materials. Avaya shall not be below, with the exception of Heritage Nortel Software, for which the scope of
responsible for any modifications, additions, or deletions to the original the license is detailed below. Where the order documentation does not
published version of Documentation unless such modifications, additions, or expressly identify a license type, the applicable license will be a Designated
deletions were performed by or on the express behalf of Avaya. End User System License as set forth below in the Designated System(s) License (DS)
agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and section as applicable. The applicable number of licenses and units of capacity
employees against all claims, lawsuits, demands and judgments arising out of, for which the license is granted will be one (1), unless a different number of
or in connection with, subsequent modifications, additions or deletions to this licenses or units of capacity is specified in the documentation or other materials
documentation, to the extent made by End User. available to You. “Software” means computer programs in object code,
provided by Avaya or an Avaya Channel Partner, whether as stand-alone
Link disclaimer products, pre-installed on hardware products, and any upgrades, updates,
Avaya is not responsible for the contents or reliability of any linked websites patches, bug fixes, or modified versions thereto. “Designated Processor”
referenced within this site or Documentation provided by Avaya. Avaya is not means a single stand-alone computing device. “Server” means a set of
responsible for the accuracy of any information, statement or content provided Designated Processors that hosts (physically or virtually) a software application
on these sites and does not necessarily endorse the products, services, or to be accessed by multiple users. “Instance” means a single copy of the
information described or offered within them. Avaya does not guarantee that Software executing at a particular time: (i) on one physical machine; or (ii) on
these links will work all the time and has no control over the availability of the one deployed software virtual machine (“VM”) or similar deployment.
linked pages.
License type(s)
Warranty Designated System(s) License (DS). End User may install and use each copy
Avaya provides a limited warranty on Avaya hardware and software. Refer to or an Instance of the Software only: 1) on a number of Designated Processors
your sales agreement to establish the terms of the limited warranty. In addition, up to the number indicated in the order; or 2) up to the number of Instances of
Avaya's standard warranty language, as well as information regarding support the Software as indicated in the order, Documentation, or as authorized by
for this product while under warranty is available to Avaya customers and other Avaya in writing. Avaya may require the Designated Processor(s) to be
parties through the Avaya Support website: identified in the order by type, serial number, feature key, Instance, location or
https://support.avaya.com/helpcenter/getGenericDetails?detailId=C200911201 other specific designation, or to be provided by End User to Avaya through
12456651010 under the link “Warranty & Product Lifecycle” or such successor electronic means established by Avaya specifically for this purpose.
site as designated by Avaya. Please note that if You acquired the product(s) Concurrent User License (CU). End User may install and use the Software on
from an authorized Avaya Channel Partner outside of the United States and multiple Designated Processors or one or more Servers, so long as only the
Canada, the warranty is provided to You by said Avaya Channel Partner and licensed number of Units are accessing and using the Software at any given
not by Avaya. time. A “Unit” means the unit on which Avaya, at its sole discretion, bases the
pricing of its licenses and can be, without limitation, an agent, port or user, an
“Hosted Service” means an Avaya hosted service subscription that You acquire e-mail or voice mail account in the name of a person or corporate function
from either Avaya or an authorized Avaya Channel Partner (as applicable) and (e.g., webmaster or helpdesk), or a directory entry in the administrative
which is described further in Hosted SAS or other service description database utilized by the Software that permits one user to interface with the
documentation regarding the applicable hosted service. If You purchase a Software. Units may be linked to a specific, identified Server or an Instance of
Hosted Service subscription, the foregoing limited warranty may not apply but the Software.
You may be entitled to support services in connection with the Hosted Service Shrinkwrap License (SR). You may install and use the Software in accordance
as described further in your service description documents for the applicable with the terms and conditions of the applicable license agreements, such as
Hosted Service. Contact Avaya or Avaya Channel Partner (as applicable) for “shrinkwrap” or “clickthrough” license accompanying or applicable to the
more information. Software (“Shrinkwrap License”).
Hosted Service Heritage Nortel Software

THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA HOSTED “Heritage Nortel Software” means the software that was acquired by Avaya as
SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA CHANNEL part of its purchase of the Nortel Enterprise Solutions Business in December
PARTNER (AS APPLICABLE), THE TERMS OF USE FOR HOSTED 2009. The Heritage Nortel Software is the software contained within the list of
SERVICES ARE AVAILABLE ON THE AVAYA WEBSITE, Heritage Nortel Products located at https://support.avaya.com/licenseinfo
HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO UNDER THE LINK “Avaya under the link “Heritage Nortel Products” or such successor site as designated
Terms of Use for Hosted Services” OR SUCH SUCCESSOR SITE AS by Avaya. For Heritage Nortel Software, Avaya grants Customer a license to
DESIGNATED BY AVAYA, AND ARE APPLICABLE TO ANYONE WHO use Heritage Nortel Software provided hereunder solely to the extent of the
ACCESSES OR USES THE HOSTED SERVICE. BY ACCESSING OR USING authorized activation or authorized usage level, solely for the purpose specified
THE HOSTED SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON in the Documentation, and solely as embedded in, for execution on, or for
BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE DOING communication with Avaya equipment. Charges for Heritage Nortel Software
SO (HEREINAFTER REFERRED TO INTERCHANGEABLY AS “YOU” AND may be based on extent of activation or use authorized as specified in an order
“END USER”), AGREE TO THE TERMS OF USE. IF YOU ARE ACCEPTING or invoice.
THE TERMS OF USE ON BEHALF A COMPANY OR OTHER LEGAL ENTITY,
YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO BIND SUCH Copyright
ENTITY TO THESE TERMS OF USE. IF YOU DO NOT HAVE SUCH Except where expressly stated otherwise, no use should be made of materials
AUTHORITY, OR IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF on this site, the Documentation, Software, Hosted Service, or hardware
USE, YOU MUST NOT ACCESS OR USE THE HOSTED SERVICE OR provided by Avaya. All content on this site, the documentation, Hosted Service,
AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED SERVICE. and the product provided by Avaya including the selection, arrangement and
design of the content is owned either by Avaya or its licensors and is protected
Licenses by copyright and other intellectual property laws including the sui generis rights
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, relating to the protection of databases. You may not modify, copy, reproduce,
HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO, UNDER THE LINK “AVAYA republish, upload, post, transmit or distribute in any way any content, in whole
SOFTWARE LICENSE TERMS (Avaya Products)” OR SUCH SUCCESSOR or in part, including any code and software unless expressly authorized by
SITE AS DESIGNATED BY AVAYA, ARE APPLICABLE TO ANYONE WHO Avaya. Unauthorized reproduction, transmission, dissemination, storage, and
DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, or use without the express written consent of Avaya can be a criminal, as well
PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA as a civil offense under the applicable law.
CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL
AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER. UNLESS
Virtualization Avaya Toll Fraud intervention
The following applies if the product is deployed on a virtual machine. Each If You suspect that You are being victimized by Toll Fraud and You need
product has its own ordering code and license types. Unless otherwise stated, technical assistance or support, call Technical Service Center Toll Fraud
each Instance of a product must be separately licensed and ordered. For Intervention Hotline at +1-800-643-2353 for the United States and Canada. For
example, if the end user customer or Avaya Channel Partner would like to additional support telephone numbers, see the Avaya Support website:
install two Instances of the same type of products, then two products of that https://support.avaya.com or such successor site as designated by Avaya.
type must be ordered.
Security Vulnerabilities
Third Party Components
Information about Avaya's security support policies can be found in the
“Third Party Components” mean certain software programs or portions thereof Security Policies and Support section of https://support.avaya.com/security.
included in the Software or Hosted Service may contain software (including
Suspected Avaya product security vulnerabilities are handled per the Avaya
open source software) distributed under third party agreements (“Third Party
Product Security Support Flow
Components”), which contain terms regarding the rights to use certain portions
(https://support.avaya.com/css/P8/documents/100161515).
of the Software (“Third Party Terms”). As required, information regarding
distributed Linux OS source code (for those products that have distributed Downloading Documentation
Linux OS source code) and identifying the copyright holders of the Third Party
For the most current versions of Documentation, see the Avaya Support
Components and the Third Party Terms that apply is available in the products,
Documentation or on Avaya's website at: https://support.avaya.com/Copyright website: https://support.avaya.com, or such successor site as designated by
or such successor site as designated by Avaya. The open source software Avaya.
license terms provided as Third Party Terms are consistent with the license
Contact Avaya Support
rights granted in these Software License Terms, and may contain additional
rights benefiting You, such as modification and distribution of the open source See the Avaya Support website: https://support.avaya.com for product or
software. The Third Party Terms shall take precedence over these Software Hosted Service notices and articles, or to report a problem with your Avaya
License Terms, solely with respect to the applicable Third Party Components to product or Hosted Service. For a list of support telephone numbers and contact
the extent that these Software License Terms impose greater restrictions on addresses, go to the Avaya Support website: https://support.avaya.com (or
You than the applicable Third Party Terms. such successor site as designated by Avaya), scroll to the bottom of the page,
and select Contact Avaya Support.
The following applies only if the H.264 (AVC) codec is distributed with the
product. THIS PRODUCT IS LICENSED UNDER THE AVC PATENT Trademarks
PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR
The trademarks, logos and service marks (“Marks”) displayed in this site, the
OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO (i)
Documentation, Hosted Service(s), and product(s) provided by Avaya are the
ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD (“AVC
registered or unregistered Marks of Avaya, its affiliates, its licensors, its
VIDEO”) AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED BY A
suppliers, or other third parties. Users are not permitted to use such Marks
CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS
without prior written consent from Avaya or such third party which may own the
OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC
Mark. Nothing contained in this site, the Documentation, Hosted Service(s) and
VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY
product(s) should be construed as granting, by implication, estoppel, or
OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED FROM
otherwise, any license or right in and to the Marks without the express written
MPEG LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM.
permission of Avaya or the applicable third party.
Service Provider Avaya is a registered trademark of Avaya Inc.
THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER'S HOSTING All non-Avaya trademarks are the property of their respective owners. Linux®
OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT OR HOSTED is the registered trademark of Linus Torvalds in the U.S. and other countries.
SERVICE MAY USE THIRD PARTY COMPONENTS SUBJECT TO THIRD
PARTY TERMS AND REQUIRE A SERVICE PROVIDER TO BE
INDEPENDENTLY LICENSED DIRECTLY FROM THE THIRD PARTY
SUPPLIER. AN AVAYA CHANNEL PARTNER'S HOSTING OF AVAYA
PRODUCTS MUST BE AUTHORIZED IN WRITING BY AVAYA AND IF
THOSE HOSTED PRODUCTS USE OR EMBED CERTAIN THIRD PARTY
SOFTWARE, INCLUDING BUT NOT LIMITED TO MICROSOFT SOFTWARE
OR CODECS, THE AVAYA CHANNEL PARTNER IS REQUIRED TO
INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE AGREEMENTS, AT
THE AVAYA CHANNEL PARTNER'S EXPENSE, DIRECTLY FROM THE
APPLICABLE THIRD PARTY SUPPLIER.
WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL PARTNER IS
HOSTING ANY PRODUCTS THAT USE OR EMBED THE H.264 CODEC OR
H.265 CODEC, THE AVAYA CHANNEL PARTNER ACKNOWLEDGES AND
AGREES THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY
AND ALL RELATED FEES AND/OR ROYALTIES. THE H.264 (AVC) CODEC
IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE
PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES
NOT RECEIVE REMUNERATION TO: (I) ENCODE VIDEO IN COMPLIANCE
WITH THE AVC STANDARD (“AVC VIDEO”) AND/OR (II) DECODE AVC
VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A
PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO
PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS
GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL
INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS MAY BE
OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM.
Compliance with Laws

You acknowledge and agree that it is Your responsibility for complying with any
applicable laws and regulations, including, but not limited to laws and
regulations related to call recording, data privacy, intellectual property, trade
secret, fraud, and music performance rights, in the country or territory where
the Avaya product is used.
Preventing Toll Fraud

“Toll Fraud” is the unauthorized use of your telecommunications system by an
unauthorized party (for example, a person who is not a corporate employee,
agent, subcontractor, or is not working on your company's behalf). Be aware
that there can be a risk of Toll Fraud associated with your system and that, if
Toll Fraud occurs, it can result in substantial additional charges for your
telecommunications services.
Contents
Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 2: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Supported upgrade scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Software upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Platform upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Base load upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
When and how to use this document . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Impacts to CMS service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Contacting Avaya technical support during upgrade . . . . . . . . . . . . . . . . . . . 11
Possible customization impacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Upgrade software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Chapter 3: Preparing for a base load upgrade. . . . . . . . . . . . . . . . . . . . . . . . . 13

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Verifying the current CMS version and load . . . . . . . . . . . . . . . . . . . . . . . . 14
Verifying that your previous backups completed successfully . . . . . . . . . . . . . 14
Verifying the backup of your CMS system data . . . . . . . . . . . . . . . . . . . . 15
Verifying that your last CMSADM backup completed successfully . . . . . . . 15
Verifying that your last LAN backup of the system data completed successfully 16
Verifying the backup of your CMS data . . . . . . . . . . . . . . . . . . . . . . . . 16
Verifying that your previous full or incremental backup completed successfully 17
Verifying that your last LAN backup of CMS data completed successfully . . . 17
Verifying that the nightly archiver is functioning . . . . . . . . . . . . . . . . . . . . . 18
Checking the status of the hardware platform disk drives . . . . . . . . . . . . . . . . 19
Checking for memory errors and system panics . . . . . . . . . . . . . . . . . . . . . 20
Verifying free space in the root file system . . . . . . . . . . . . . . . . . . . . . . . . 20
Rebooting your CMS server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Backing up the CMS data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Backing up your CMS system data . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Doing a CMSADM backup to tape . . . . . . . . . . . . . . . . . . . . . . . . . 22
Doing a full system backup with IBM Spectrum Protect . . . . . . . . . . . . . 23
Doing a full system backup with Veritas Netbackup . . . . . . . . . . . . . . . 24
Backing up your CMS data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Doing a full data backup with a tape device . . . . . . . . . . . . . . . . . . . . 25
Doing a full data backup with IBM Spectrum Connect . . . . . . . . . . . . . . 26
Doing a full data backup with Veritas Netbackup . . . . . . . . . . . . . . . . . 26
Backing up any new CMS data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Avaya CMS Base Load Upgrade March 2021 5

Contents
Chapter 4: Updating the Linux operating system . . . . . . . . . . . . . . . . . . . . . . . 29

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Common procedure for mounting a CMS ISO image . . . . . . . . . . . . . . . . . . . 29
Stopping the CMS Supervisor Web Client software. . . . . . . . . . . . . . . . . . . . 30
Stopping Avaya OA data forwarders . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Installing Linux RPMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Chapter 5: Upgrading the CMS base load . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Removing the current CMS load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Installing the new CMS base load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Installing the new CMS base load on a hardware platform . . . . . . . . . . . . . . 40
Installing the new CMS base load on a VMware-based server . . . . . . . . . . . . 42
Installing the CMS security script and changing the cmssvc password . . . . . . . . 45
Installing CMS patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Upgrading the CMS Supervisor Web Client software package . . . . . . . . . . . . . . 47
Turning on CMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Starting the CMS Supervisor Web Client software . . . . . . . . . . . . . . . . . . . . 50
Starting Avaya OA data forwarders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Chapter 6: Completing the base load upgrade process . . . . . . . . . . . . . . . . . . . 51

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Doing a backup of the system files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Doing a backup of the CMS data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Chapter 7: Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
CMS and CMS Supervisor Documents . . . . . . . . . . . . . . . . . . . . . . . . . 53
Avaya Solutions Platform Documents . . . . . . . . . . . . . . . . . . . . . . . . . 56
WebLM Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
VMware Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Finding documents on the Avaya Support website . . . . . . . . . . . . . . . . . . 57
Accessing the port matrix document. . . . . . . . . . . . . . . . . . . . . . . . . . 58
Avaya Documentation Portal navigation . . . . . . . . . . . . . . . . . . . . . . . . 58
Viewing Avaya Mentor videos. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Using the Avaya InSite Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . 60

Chapter 1: Introduction
Purpose
The purpose of this document is to describe the Avaya Call Management System (CMS) base
load upgrade process. A base load upgrade is designed to be installed by CMS customers who
either are experiencing problems with their current release or want to use new features of the
latest release.
A PCN for the new release provides a list of all fixes and features added in the new release. You
can download the CMS software from the Avaya support site. You should install this upgrade as
soon as possible so that Avaya support can properly troubleshoot products that have the latest
release installed.
! Important:
Important: Before installing a base load upgrade, verify that you have downloaded the
proper software ISO image for the new release. Verify that you are using the
proper base load upgrade document for the new release of CMS.
Note:
Note: For existing systems on Solaris, you cannot do a base load upgrade. You must do
a platform upgrade.
For a complete list of bug fixes and new features available in the latest CMS load, see the CMS
Release Notes at:
https://support.avaya.com

Chapter 1: Introduction

Chapter 2: Overview
Supported upgrade scenarios

CMS supports the following upgrade scenarios:
● Software Upgrades - Upgrading from an older CMS software release and retaining the
same hardware server or VMware server. You will back up the customer data, use
software discs and a CMS OVA file to install the new Linux OS and CMS software, then
migrate the customer data.
● Platform Upgrades - Upgrading from an older CMS software release and installing a new
customer-provided VMware server or an Avaya Solutions Platform server. You will back up
the customer data, use a CMS OVA file to install the new Linux OS and new CMS
software, then migrate the customer data onto the new software release.
● Base Load Upgrades - Upgrading from an older CMS software release within the same
minor release or an approved upgrade scenario. You will use a software disc or a CMS
ISO image file to install the new Linux OS and CMS software.
For more information about upgrades, see the following documents:
● Planning for Avaya Call Management System Upgrades
● Upgrading Avaya Call Management System
● Deploying Avaya Call Management System
● Avaya Call Management System Base Load Upgrade
Software upgrades
The software upgrade process reuses existing CMS hardware that can support the new CMS
software. The following models of hardware can support CMS Release 19.2 regardless of the
current CMS release installed on the hardware:
● Avaya Solutions Platform Profile 130 VMware servers
● Customer-provided VMware servers
● Dell R630
● Dell R730
● HPE DL20 G9
● HPE DL380 G9

Chapter 2: Overview
● Customer-provided Amazon Web Services (AWS) servers
Platform upgrades
CMS Release 19.2 supports platform upgrades from CMS Releases 16.x, 17.x, 18.x, 19.0, and
19.1.0.0 or 19.1.0.1 regardless of what hardware the CMS software currently resides.
Note:
Note: Contact your Avaya account team if you need to upgrade from CMS releases
older than 16.x.
Base load upgrades

A base load upgrade must be used when upgrading from a CMS Release 19.1.0.0 or 19.1.0.1
to CMS Release 19.2.
! Important:
Important: Base Load upgrades cannot be used to upgrade any CMS release prior to CMS
19.1.0.0. Because of the data privacy encryption software that is new with CMS
19.1.0.0, you must do a full software upgrade or a platform upgrade.
When and how to use this document

Use this document to upgrade CMS from Release 19.1.0.0 or 19.1.0.1 to Release 19.2. Unless
indicated otherwise, all procedures in this document are required.
Avaya recommends that:
● Before doing the upgrade, read through this entire document so that you are familiar with
what tasks you will need to do. If you decide you would like to have Avaya assist you doing
the upgrade, see Contacting Avaya technical support during upgrade on page 11.
● Have a pen or pencil during the upgrade so that you can record any required information.
● During the upgrade, mark each step as it is completed.
● You will be required to enter Linux commands during the upgrade process. You must enter
the command from the Linux prompt in a terminal window. Press the Enter key after you
have typed in the command. Use the same capitalization and spacing shown in this
document.
● If you encounter problems or have questions during the upgrade, contact Avaya technical
support.

Impacts to CMS service
Impacts to CMS service

! CAUTION:
CAUTION: A base load upgrade is service affecting. Schedule the upgrade during a regular
maintenance interval or when there is no traffic or during a low traffic period.
During the Operating System patch installation using rpm_updates for Linux, your system
displays an estimate of the amount of time needed to install the Operating System updates. The
Operating System update installation is the part of the base load upgrade that usually requires
the longest amount of time to complete.
Contacting Avaya technical support during upgrade

You can make arrangements to have Avaya provide remote assistance for this upgrade.This
remote assistance must be scheduled at least two weeks before your upgrade. Charges, which
will be quoted, vary for this service.
If you want Avaya Professional Services to do the Base Load upgrade, contact your account
team or business partner to obtain a quote for a billable Avaya Professional Services
engagement.
If you encounter problems or have questions during the upgrade and are unable to resolve them
by following the upgrade instructions, contact Avaya technical support. Be ready to provide the
number of the Quality Protection Plan you are using.
Possible customization impacts

The software upgrade that you are installing could potentially impact system customization that
was done before this upgrade. For example:
● Custom reports
● LAN printer customization
● Work-force management interfaces
● Operational Analyst

Chapter 2: Overview
You can schedule an evaluation of your system to determine whether any of your system
customizations might be impacted by this upgrade. Schedule this evaluation at least two weeks
before your upgrade. Charges, which will be quoted, vary for this service. Contact Avaya CRM
at 1-866-282-9266.
Upgrade software
If you are upgrading a supported hardware server (Dell R630, Dell R730, HPE DL20 G9, or
HPE DL380 G9) or upgrading a VMware-based system or an Amazon Web Services system,
you must download the ISO image file from the Avaya PLDS site:
https://plds.avaya.com

Chapter 3: Preparing for a base load
upgrade
This section describes the tasks you must do before you start a base load upgrade. These
procedures will help you verify that your CMS server has no existing hardware or software
problems before the upgrade. If you do not do these procedures, your base load upgrade could
fail, and your CMS server could be put in a non-functioning state for some time.
This section includes the following topics:
● Prerequisites on page 13
● Verifying the current CMS version and load on page 14
● Verifying that your previous backups completed successfully on page 14
● Verifying that the nightly archiver is functioning on page 18
● Checking the status of the hardware platform disk drives on page 19
● Checking for memory errors and system panics on page 20
● Verifying free space in the root file system on page 20
● Rebooting your CMS server on page 21
● Backing up the CMS data on page 21
Prerequisites
Before you do the procedures in this section, you must:
● Read the information in Introduction on page 7.
● The CMS software disc and the ISO image have a readme file called cms.readme. Avaya
recommends you review this file for any changes that might impact the procedures in this
document. For more information, see Avaya Call Management System Release Notes.
● Log on to the system as root.
! Important:
Important: You cannot directly log on as root from a remote connection. You must log on
using an administered CMS user ID, then use su - root to log on with root
privileges.

Chapter 3: Preparing for a base load upgrade
Verifying the current CMS version and load

Procedure
1. Log on to the system as root.
! Important:
privileges.
2. Enter:
rpm -q cms
The system displays the currently installed CMS package, including the load number, for
example:
cms-Rnn.n.n.n-<BuildNumber>
3. Record the displayed CMS version information for reference later during the upgrade
process.
CMS version: _______________________________
Verifying that your previous backups completed

successfully
Approximately two days before the CMS base load upgrade, verify that your backups have
been completing successfully.
● Verifying the backup of your CMS system data on page 15
● Verifying the backup of your CMS data on page 16

Verifying that your previous backups completed successfully
Verifying the backup of your CMS system data

To verify that your previous CMS data backup completed successfully, choose one of the
following procedures:
● If you back up your data directly to tape, a USB storage device, or a network mount point,
go to Verifying that your last CMSADM backup completed successfully on page 15.
You are responsible for backing up your CMS system data unless you engage Avaya to do
the backups in conjunction with this base load upgrade.
● If you use the CMS LAN backup feature, go to Verifying that your last LAN backup of the
system data completed successfully on page 16
You are responsible for backing up your CMS system data. Avaya is not responsible for
doing LAN backups. For more information about the CMS LAN backup feature, see Using
Avaya Call Management System LAN Backup. This document provides information about
using the CMS LAN backup feature, hardware requirements, software requirements, and
support guidelines.
Verifying that your last CMSADM backup completed successfully
Procedure
1. Enter:
tail /cms/install/logdir/backup.log
2. Verify that the previous CMSADM backup completed successfully.
An example of a successful CMSADM backup message is:
===== Begin backup <timestamp>
Converter started <timestamp>

Converter completed successfully <timestamp>
Testing tape on /dev/rmt/0...
Tape test on /dev/rmt/0 is okay...
2873600 blocks
===== Finished backup <timestamp>
3. Choose one of the following actions:

● If your previous backup was successful, go to Verifying the backup of your CMS
data on page 16.
● If your previous backup was not successful, contact your Avaya support
representative.

Verifying that your last LAN backup of the system data completed
successfully
Procedure
1. Enter:
cat /cms/install/logdir/backup.log | more
2. Press Enter to continue the display. It might be necessary to repeat this step several
times.
3. Verify that the previous system backup completed successfully.
An example of a successful system backup message is:
===== LAN SYSTEM BACKUP SUCCESSFULLY FINISHED Date and time

● If your previous backup was successful, go to Verifying the backup of your CMS
data on page 16.
representative.
Verifying the backup of your CMS data

To verify that your previous CMS data backup completed successfully, choose one of the
following procedures:
● If you backup your data directly to a tape device, go to Verifying that your previous full or
incremental backup completed successfully on page 17.
● If you use the CMS LAN backup feature, go to Verifying that your last LAN backup of CMS
data completed successfully on page 17.
For more information about the CMS LAN backup feature, see Using Avaya Call
Management System LAN Backup. This document provides information about using the
CMS LAN backup feature, hardware requirements, software requirements, and support
guidelines.

Verifying that your previous backups completed successfully
Verifying that your previous full or incremental backup completed

successfully
Procedure
1. Verify that you are logged in as root.
! Important:
privileges.
! Important:
Important: If at anytime during the upgrade process you need to verify that you are logged in
as the root user, you can enter the command: id
2. Enter:
tail /cms/maint/backup/back.log
3. Verify that the previous full or incremental backup completed successfully.
An example of a successful full or incremental backup message is:
1711 <timestamp> 2 1 INFO

BACKUP INFO: The backup has completed successfully.
Please label the volume CMS-030415-01-LSAC-00-F-01-r3milcms

● If your previous backup was successful go to Verifying that the nightly archiver is
functioning on page 18.
representative.
Verifying that your last LAN backup of CMS data completed successfully
Procedure
1. Enter:
cat /cms/install/logdir/backup.log | more
times.

3. Verify that the previous data backup completed successfully.

An example of a successful data backup message is:
+++++ ON-Bar BACKUP SUCCESSFULLY FINISHED Date and time

● If your previous backup was successful, go to Verifying that the nightly archiver is
functioning on page 18.
representative.
Verifying that the nightly archiver is functioning

Procedure
1. Verify that you are logged in to the system as root.
! Important:
privileges.
2. Enter:
su cms cms
The system displays the CMS main menu.
3. Press Enter to accept the default terminal type.
4. Select Maintenance > Error Log Report.
5. Enter 2600 in the Error codes field.
6. Leave all of the other fields blank.
7. Press Enter to select the Run option.
8. Press Enter.
The system displays an archive history report.

Checking the status of the hardware platform disk drives
9. Verify that the nightly archiver is functioning correctly for all ACDs administered on the
system.
An example of a successful nightly archiver message is:
2600 <timestamp> 2 1 INFO

ARCHIVER status: Daily Archive for (Mon)
<timestamp> Successful
10. Select Exit to return to the previous menu.

● If the nightly archiver is functioning correctly, go to Checking the status of the hardware
platform disk drives on page 19.
● If the nightly archiver is not functioning correctly, contact your Avaya support
representative.
Checking the status of the hardware platform disk drives

About this task
This procedure is for non-VMware hardware platform deployments only. You can skip this
procedure if your system is a VMware deployment.
Procedure
1. To verify the disk or disk volume, run the following command:
/olds/chkDisks
● If this command returns to the prompt without generating any output, there are no
errors and you can continue with the upgrade.
● If this command returns the following output:
SEVERE ERROR: Enclosure 32, RAID Drive Slot X is in state Failed (where X is
the slot number)
Possible Disk Errors! Please check /olds/log/err.log for details
then you must contact Avaya Services and resolve the issue before continuing with the
upgrade.

Checking for memory errors and system panics

Procedure
1. Check for memory errors and system panics. Enter:
egrep -i "panic | memory error" /var/log/messages* | more
Note:
Note: It might be necessary to press Enter to continue the display.
An example of a panic error message is:
messages-20121223:<timestamp> trex Kernel panic – not syncing: : Port x halting

system due to client process failure
2. Choose one of the following actions, depending on the message that is displayed:
● If the system displays no memory error or panic messages, go to Verifying free space
in the root file system on page 20.
● If the system displays any memory error or panic messages, your system requires
maintenance. Contact your Avaya support representative.
Verifying free space in the root file system

Procedure
1. Enter:
df -k /
The system displays a message similar to the following:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda2 9842412 2709148 6633288 29% /
2. Check the disk capacity.

● If the disk Use% is less than 85%, go to Rebooting your CMS server on page 21.
● If the disk Use% is 85% or greater, contact your Avaya support representative.

Rebooting your CMS server
Rebooting your CMS server

About this task
You must reboot your CMS server and verify that the system is functioning properly. Reboot the
CMS server before you back up your data.
! CAUTION:
CAUTION: A reboot is service affecting. Schedule the reboot during a regular maintenance
interval or when there is no traffic or during a low traffic period.
Procedure
1. Enter the following command from the pound (#) prompt:
shutdown -r now
The system reboots.
! Important:
privileges.
● If the system does not boot correctly or if any error messages are displayed, contact
your Avaya support representative.
● If the system boots correctly, go to Backing up the CMS data on page 21.
Backing up the CMS data

Before beginning a CMS base load upgrade, you must backup your CMS system data and CMS
data.
● Backing up your CMS system data on page 22
● Backing up your CMS data on page 24
● Backing up any new CMS data on page 27

Backing up your CMS system data

A backup of the system data must be done approximately one day before the CMS base load
upgrade.
To take a backup of your current system files, choose one of the following procedures:
● If you back up your data directly to a tape device, go to Doing a CMSADM backup to
tape on page 22.
● If you back up your data to a USB storage device, see Maintaining and Troubleshooting
Avaya Call Management System.
● If you back up your data to a network mount point, see Maintaining and Troubleshooting
● If you use the CMS LAN backup feature, go to Doing a full system backup with IBM
Spectrum Protect on page 23 or Doing a full system backup with Veritas Netbackup on
page 24.
guidelines.
Doing a CMSADM backup to tape
Procedure
1. Verify that you are using the correct tape for the tape drive for your system. Many of the
tape cartridges look alike, and using the wrong tape can damage the tape drive
mechanism and tape heads.
2. Log on as root.
! Important:
privileges.
3. Enter:
cmsadm
The Avaya Call Management System Administration Menu (CMSADM Menu) is
displayed.
4. Enter the number associated with the backup option.
Depending on the number of tape drives connected to your system, one of the following
messages will be displayed by your system.

● If only one tape drive is available, the system displays the following message:
Please insert the first cartridge tape into device name.

Press ENTER when ready or Del to quit:
● If more than one tape drive is available for use, the system displays a list of tape
devices. Enter a tape drive selection from the displayed list.
An example of a tape device list is:
Select the tape drive:

1) SCSI 2 tape drive: /dev/st0
2) SCSI 2 tape drive: /dev/st1
Enter choice (1-2):
Note:
Note: If the system fails to identify the tapes by manufacturer name, tape devices are
displayed according to their system device names, such as “/dev/st0”.
5. Press Enter.
The backup process is initiated.
When the backup is complete, the system displays the following message:
xxxxxxx blocks
Tape Verification
xxxxxxx blocks
WARNING: A CMS Full Maintenance Backup in addition to this cmsadm
backup must be done to have a complete backup of the system. . .
. .
Please label the backup tape(s) with the date and the current CMS
version (rxxxxx.x)
6. Write protect the tape and store the tape in a secure location until the next backup is done.
7. Go to Backing up your CMS data on page 24.
Doing a full system backup with IBM Spectrum Protect
Procedure
1. Log on as root.
! Important:
privileges.

2. Enter:
/cms/LANbkup/bin/backup.tivoli 0
3. Verify that the backup has completed successfully by entering:
cat /cms/install/logdir/backup.log
4. Go to Backing up your CMS data on page 24.
Doing a full system backup with Veritas Netbackup
Procedure
1. Log on as root.
! Important:
privileges.
2. Enter:
/cms/LANbkup/bin/backup.netbackup 0
3. Verify that the backup has completed successfully by entering:
4. Continue with Backing up your CMS data on page 24.
Backing up your CMS data

Your CMS data must be backed up approximately one day before the CMS base load upgrade
is done.
To backup your CMS data, choose one of the following procedures:
● If you back up your data directly to a tape device, go to Doing a full data backup with a tape
device on page 25.
● If you back up your data to a USB storage device, see Maintaining and Troubleshooting
● If you back up your data to a network mount point, see Maintaining and Troubleshooting

● If you use the CMS LAN backup feature, go to Doing a full data backup with IBM Spectrum
Connect on page 26 or Doing a full data backup with Veritas Netbackup on page 26.
guidelines.
Doing a full data backup with a tape device
Procedure
1. Verify that you are using the correct tape for the tape drive for your system. Many of the
tape cartridges look alike, and using the wrong tape can damage the tape drive
mechanism and tape heads.
2. Verify that you are logged in as cms.
3. Enter cms.
4. From the main menu, select Maintenance > Back Up Data.
The system displays the Back Up Data window, as shown below. Do not change any of
the default selections.

5. Press Enter to access the action list in the upper right corner of the window.
6. Select Run and press Enter.
7. Wait for the backup to complete. If the backup does not complete successfully, contact
your Avaya support representative.
8. Write-protect the tape and store the tape in a secure location until the next backup is done.
9. Go to Backing up any new CMS data on page 27.
Doing a full data backup with IBM Spectrum Connect
Procedure
1. Verify that you are logged on as root.
! Important:
privileges.
2. Enter:
/cms/LANbkup/bin/onbar_backup.tivoli 0
3. Verify that the backup has completed successfully by entering the following commands:
cat /cms/install/logdir/bar_act.log
4. Continue with Backing up any new CMS data on page 27.
Doing a full data backup with Veritas Netbackup
Procedure
1. Verify that you are logged on as root.
! Important:
privileges.
2. Enter:
/cms/LANbkup/bin/onbar_backup.netbackup 0
3. Verify that the backup has completed successfully by entering the following commands:
cat /cms/install/logdir/bar_act.log

4. Continue with Backing up any new CMS data on page 27.
Backing up any new CMS data

You must back up any CMS data that has been generated since your last CMS data backup.
Choose one of the following options:
● If no new CMS data has been generated since your last CMS data backup, continue with
Updating the Linux operating system on page 29.
● If new CMS data has been generated since your last CMS data backup, do one of the
following procedures immediately before the upgrade:
- Doing a full data backup with a tape device on page 25
- Doing a full data backup with IBM Spectrum Connect on page 26
- Doing a full data backup with Veritas Netbackup on page 26
Once the new CMS data has been backed up, continue with Updating the Linux operating
system on page 29.
For more information about the CMS LAN backup feature, see Using Avaya Call Management
System LAN Backup. This document provides information about using the CMS LAN backup
feature, hardware requirements, software requirements, and support guidelines.


Chapter 4: Updating the Linux operating
system
This section contains procedures for updating your operating system. You must complete the
procedures in this section before upgrading the CMS software.
Prerequisites
● Do all of the required procedures in Preparing for a base load upgrade on page 13.
● Verify that you are logged on to the system as root.
! Important:
privileges.
Common procedure for mounting a CMS ISO image

About this task
Use this procedure to take the CMS software ISO image and mount the image so that you can
use it for upgrading the Linux and CMS software.
! Important:
Important: This procedure is referenced from several other procedures within this document.
Do not use this procedure unless directed from other procedures.

Chapter 4: Updating the Linux operating system
Procedure
! Important:
Important: Skip Steps 1-10 if you have already uploaded the ISO image file while doing
another procedure from this document.
1. Copy the downloaded CMS software ISO image for the new CMS load to the PC where
the vSphere client is installed.
2. Using the vSphere client, upload the CMS software ISO image from the PC to a datastore
storage area on VMware server.
3. Access the Virtual CMS.
4. Access Edit Settings.
5. Expand Connect the CD/DVD Drive.
6. From the drop-down list, select Datastore ISO File.
7. Select the CMS software ISO image file.
8. Click OK.
9. Click Connected.
10. Click OK.
11. Use vSphere client to access the Virtual CMS and establish a CD/DVD connection to the
CMS software ISO image in the storage directory.
12. On the Virtual CMS, execute:
mount /dev/cdrom /mnt
Stopping the CMS Supervisor Web Client software

Procedure
cmsweb stop
Stopping Avaya OA data forwarders

If the CMS configuration includes data collection by Avaya OA, turn off all Avaya OA forwarders
on the CMS server using the pa stop all command. For more information about Avaya OA
forwarders, see Avaya OA Maintenance and Troubleshooting.

Installing Linux RPMs

About this task
It is important to update the Linux RPM packages because the updates might contain new Linux
operating system updates for security and system operation. Avaya provides the Linux RPM
updates on the CMS media used for upgrades. For hardware, it is a software disc. For VMware,
it is an ISO image.
Avaya might also release RPM updates outside of normal CMS releases. Any RPM updates are
announced using a PSN. For example, PSN005673u describes how to update CMS Release
19.1.0.1 with a new set of Linux RPMs. In this example, the RPMs are recommended, but not
required for Release 19.1.0.1. Note that the PSN contains complete steps to install new RPMs,
including some steps you have already done during the standard base load upgrade procedure,
such as stopping the CMS Supervisor Web Client software or stopping Avaya OA data
forwarders. You can skip the steps shown in the PSN if you have already done the steps.
Before you begin

Check the Avaya support site to see if there are any new Linux RPM updates for the release of
CMS to which you are upgrading.
! CAUTION:
CAUTION: If the CMS encryption passphrase auto-unlock feature is disabled (that is, your
system is administered to require a passphrase after a reboot), you must be
prepared to enter a passphrase at the system console if RPMs are installed and
the system reboots. You can work around this requirement by temporarily
enabling the encryption passphrase auto-unlock feature before you install RPMs.
You must then remember to disable the encryption passphrase auto-unlock
feature after you finish installing the RPMs. Note that this scenario does not apply
to an Amazon Web Services deployment.
Procedure
1. Do one of the following:
● If on a VMware or Amazon Web Services system, do the steps in Common procedure
for mounting a CMS ISO image on page 29. After completing that procedure, continue
with Step 5.
● If on a non-VMware system, continue with step 2.
2. Load the CMS software disc into the disc drive.
3. Change to the root directory, enter:
cd /

4. Mount the DVD drive. Enter:

mount /dev/dvd /mnt
The system displays the following message:
mount: block device /dev/sr0 is write-protected, mounting read-only
5. Enter:
cmssvc
The system displays the CMS Services menu.
6. Enter the number associated with the run_cms option.
7. Enter the number associated with the Turn off both CMS and IDS option.
The system returns to the command prompt.
8. Run the RPM update script. Enter:
/mnt/rpm_update
! Important:
Important: Do not halt the system while installing RPMs. You need to monitor the system
during the RPM installation process to ensure that the installation of the RPMs
does not halt. When the RPM installation process completes, the system either
automatically reboots into multiuser mode and displays the graphical login screen
or requests that you enter an encryption passphrase at the system console after
rebooting.
One of the following occurs depending on whether there are RPMs to install:
● If there are no RPMs to install, the system displays the following message and you
continue with Step 11:
RPM Updates (for Rnn.n.n.n) started: <TimeStamp>
No rpm updates are required.

package hmaccalc exists, add not required.
package dracut-fips exists, add not required.
package rpcbind does not exist, remove not required.
RPM updates finished: <TimeStamp>

● If there are Linux RPMs to install, the installation starts and the system displays
messages similar to the following example:
RPM Updates (for Rnn.n.n.n rNN<BuildNumber>) started: <TimeStamp>
Updating RPMs.
Loaded plugins: security
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package abrt.x86_64 0:2.0.8-43.el6 will be updated
---> Package abrt.x86_64 0:2.0.8-44.el6 will be an update
---> Package abrt-addon-ccpp.x86_64 0:2.0.8-43.el6 will be updated
---> Package abrt-addon-ccpp.x86_64 0:2.0.8-44.el6 will be an update
---> Package abrt-addon-kerneloops.x86_64 0:2.0.8-43.el6 will be updated
….
yum-utils.noarch 0:1.1.30-41.el6
Complete!
kernel update successfully verified.
**if warnings exist, IGNORE them**
All RPM updates successfully applied.
package hmaccalc exists, add not required.
package dracut-fips exists, add not required.
Removing rpcbind package

warning: erase unlink of /var/cache/rpcbind failed: No such file or directory
remove rpcbind package successfully executed.
**if warnings exist, IGNORE them**
Note:
Note: Various configuration conditions can exist that produce warning messages.
Ignore the warning messages; the RPMs are completely installed.
● If the encryption passphrase auto-unlock feature is disabled (that is, you are required
to enter a passphrase at the console after reboot), the system displays the following
message after the RPMs are installed:
WARNING: This utility will reboot the Linux system.

Access to the system console to enter the disk encryption passphrase
is required on reboot.
Do you want to reboot (y/n)?

! CAUTION:
CAUTION: Be prepared to enter a CMS encryption passphrase at the system console after
the RPMs are installed and the system reboots. You can work around this
requirement by temporarily enabling the encryption passphrase auto-unlock
feature before you install RPMs. You must then remember to disable the
encryption passphrase auto-unlock feature after you finish installing the RPMs.
Note that this scenario does not apply to an Amazon Web Services deployment.
9. Enter y to reboot.
! Important:
privileges.
11. Verify that all the Linux RPMs are installed. Enter:
tail -10 /var/cms/spatches/rpm_update.log
Verify that the system displays the following message:
Update the message box to include:

Rebooting the system now.
Note:
Note: If the installation procedure fails for any of the RPMs, the system might display
one or more of the following messages. Continue with this procedure and the
remaining CMS base load upgrade procedures. When the upgrade is complete, if
messages 1 or 2 were displayed, notify Avaya support. If messages 3 or 4 were
displayed, notify Avaya support if you plan to use FIPS security.
- Error running the RPM check-update command. Exiting.
- Errors detected executing yum update command, Exiting.
- WARNING: cannot add hmaccalc/dracut-fips package, not found in /mnt/rpm_updates. If

the FIPS feature will be utilized, consult Avaya Support. The hmaccalc/dracut-fips
package must be installed for FIPS operations. Continuing.
- WARNING: hmaccalc/dracut-fips add failed. If the FIPS feature will be utilized,

consult Avaya Support. The hmaccalc/dracut-fips package must be installed for FIPS
operations. Continuing.

12. (Optional) If a PSN indicates there are additional RPM updates for the CMS release to
which you are upgrading, do the steps described in the PSN.
13. Verify that IDS is running. Enter:
cmssvc
The system displays the CMSSVC menu. If the system displays the following text, IDS is
not running and you must continue with Step 14:
cmssvc: Warning IDS off-line. It will take approx 45 seconds to

start cmssvc. IDS can be turned on with the run_ids command on the
cmssvc menu
If IDS is running, continue with Step 16.

14. Select the run_ids option.
15. Select the Turn IDS on option.
The system starts IDS and returns to the command prompt.
16. Continue with Upgrading the CMS base load on page 37.


Chapter 5: Upgrading the CMS base load
You must complete the procedures in the previous sections before upgrading your CMS base
load. Use the procedures in this section to upgrade an older CMS base load to a newer CMS
base load.
● Removing the current CMS load on page 38
● Installing the new CMS base load on a hardware platform on page 40
● Installing the new CMS base load on a VMware-based server on page 42
● Installing CMS patches on page 47
● Upgrading the CMS Supervisor Web Client software package on page 47
● Turning on CMS on page 49
● Starting the CMS Supervisor Web Client software on page 50
● Starting Avaya OA data forwarders on page 50
Prerequisites
● Do all of the required procedures in Updating the Linux operating system on page 29.
● Verify that you are logged on to the system as root.
! Important:
privileges.

Removing the current CMS load

Procedure
1. Log on to CMS as root.
! Important:
privileges.
2. Enter:
cmssvc
Avaya(TM) Call Management System Services Menu
Select a command from the list below.

1) auth_display Display feature authorizations
2) weblm_set Set up the connection to the WebLM
3) run_ids Turn Informix Database on or off
4) run_cms Turn Avaya CMS on or off
5) setup Set up the initial configuration
6) swinfo Display switch information
7) swsetup Change switch information
8) uninstall Remove the CMS rpm from the machine
9) patch_rmv Backout an installed CMS patch
10) back_all Backout all installed CMS patches from machine
11) security Administer CMS security features
Enter choice (1-11) or q to quit: 1
3. Select the uninstall option.

The following package is currently installed
Avaya(TM) Call Management System Rnn.n.n.n

Do you want to remove this package? [y,n,?] ?

Removing the current CMS load
4. Enter y.
Proceeding with the removal of CMS...

Do you want to preserve CMS data? [y,n,?] ?
! CAUTION:
CAUTION: If you select n in response to this question, all your CMS data is deleted from the
system, so you should answer y to preserve the data.
5. Enter y.
CMS will be removed from this machine; the data will be preserved
Are you sure this is correct? [y,n,?] ?
6. Enter y.
All file systems should be backed up before continuing.

See the Maintenance chapter in the CMS
Installation and Maintenance Manual for instructions.
Have you backed up the file systems? [y,n,?] ?
7. Enter y.
Proceeding with removal of CMS...
warning: /var/elog/elog_if saved as /var/elog/elog_if.rpmsave

warning: /var/elog/elog saved as /var/elog/elog.rpmsave
warning: /usr/lib/cms/Sname saved as /usr/lib/cms/Sname.rpmsave
warning: /usr/lib/cms/Pname saved as /usr/lib/cms/Pname.rpmsave
warning: /usr/lib/cms/Aname saved as /usr/lib/cms/Aname.rpmsave
warning: /cms/pbx/master saved as /cms/pbx/master.rpmsave
warning: /cms/pbx/acd1/xln.log saved as /cms/pbx/acd1/xln.log.rpmsave
.
.
.
Removal of Avaya(TM) Call Management System (cms) is complete
8. Continue with Installing the new CMS base load on page 40.

Installing the new CMS base load

● If the system is a Dell or a HP platform, continue with Installing the new CMS base load on
a hardware platform on page 40.
● If the system is a customer-provided VMware system or an Avaya-provided Avaya
Solutions Platform (formerly Avaya Converged Platform) system, continue with Installing
the new CMS base load on a VMware-based server on page 42.
Installing the new CMS base load on a hardware platform

Procedure
1. Verify that the CMS software disc is in the disc drive.
2. Mount the CMS software disc by running the following command:
mount /dev/dvd /mnt
3. Enter the following command to update the CMS related Informix files:
/mnt/update_ids
The system displays the following message when IDS updates are applied:
/mnt/update_ids successfully finished
4. Install CMS. Enter:

/mnt/cms.bin
Unpacking files please wait...

Extracting the tar....
Installing Avaya(TM) Call Management System Rnn.n.n.n (cms) version rNN<BuildNumber>

This is an upgrade
In order to install CMS, the existing version must be removed.

The following package is currently installed:


● If CMS is turned on and you want to continue with the installation of the new CMS
base load, enter y.
● If CMS is turned on and you want to cancel the installation of the new CMS base load,
enter n.
● If CMS is not running, the installation process continues without prompting the user for
an input.
When CMS is installed, the system displays the following message:
Customer CMS data successfully upgraded.

CMS is installed.
Note:
Note: If the installation procedure fails for any reason, the system displays the following
message:
- Customers in the US should call the CMS Technical Services

Organization at 1-800-242-2121
- Customers outside the US should contact your Avaya representative or
distributor.
If the system displays the message shown in this example, notify Avaya support as
prompted by the system.
5. Enter:
cat /cms/install/logdir/admin.log | more
The system displays part of the CMS administration log.
6. Verify that there were no errors during the installation.
times.
8. Reboot the system. Enter:
shutdown -r now
The system reboots.
! Important:
privileges.


cmssvc
The system displays the CMSSVC menu. If the system displays the following text, then
IDS is not running and you must continue with Step 11:

cmssvc menu

13. Continue with Installing the CMS security script and changing the cmssvc password on
page 45.
Installing the new CMS base load on a VMware-based server

Procedure
1. Execute the steps in Common procedure for mounting a CMS ISO image on page 29.
After completing that procedure, continue with Step 2.
2. Enter the following command to update the CMS related Informix files:
/mnt/update_ids
<timestamp> Updating dbinit.sh and env files

3. Install CMS. Enter:

/mnt/cms.bin

Extracting the tar....
Installing Avaya(TM) Call Management System Rnn.n.n.n (cms) version rNN<BuildNumber>

This is an upgrade
In order to install CMS, the existing version must be removed.

The following package is currently installed:

● If CMS is turned on and you want to continue with the installation of the new CMS
base load, enter y.
● If CMS is turned on and you want to cancel the installation of the new CMS base load,
enter n.
● If CMS is not running, the installation process continues without prompting the user for
an input.
When CMS is installed, the system displays the following message:
Customer CMS data successfully upgraded.

CMS is installed.
Note:
Note: If the installation procedure fails for any reason, the system displays the following
message:
- Customers in the US should call the CMS Technical Services

Organization at 1-800-242-2121
- Customers outside the US should contact your Avaya representative or
distributor.
If the system displays the message shown in this example, notify Avaya support as
prompted by the system.
4. Enter:
cat /cms/install/logdir/admin.log | more
The system displays part of the CMS administration log.
5. Verify that there were no errors during the installation.

times.
7. Use vSphere client to access the Virtual CMS and reset the CD/DVD to Client and not
connected.
8. Enter
unmount/mnt
9. Reboot the system. Enter:
shutdown -r now
The system reboots.
! Important:
privileges.
cmssvc
The system displays the CMSSVC menu. If the system displays the following text, then
IDS is not running and you must continue with Step 12:

cmssvc menu

14. Continue with Installing the CMS security script and changing the cmssvc password on
page 45.

Installing the CMS security script and changing the cmssvc password
Installing the CMS security script and changing the

cmssvc password
About this task
As part of installing or upgrading CMS software, you must install the CMS security options using
the cms_sec script. As part of the security script, you are also prompted to change the default
cmssvc user ID password the first time you run this script. If you have previously changed the
default password for the cmssvc user ID, you are not prompted to enter a new password.
! Important:
Important: You can log in to the console as root only after you run the CMS security script. If
you are logging into the system remotely, log in as a user and then enter:
su - root
Procedure
1. Verify that you are logged on to the system as root.
2. Verify the current services running on the system and save the list for comparison with the
listing after the security script run.
Note:
Note: It is necessary to find out which services in the list of differences are used by the
customer.
3. To capture the current services and preserve the output to a file, enter:
chkconfig --list > /tmp/current_chkconfig.txt
● If on a VMware system, do the steps in Common procedure for mounting a CMS ISO
image on page 29. After completing that procedure, continue with Step 8.
● If on a non-VMware system, continue with Step 5.
Note:
Note: If the CMS software disc is already mounted, continue with Step 8.
5. Insert the CMS software disc into the disc drive.
6. Change to the root directory. Enter:
cd /
7. Mount the CMS software disc. Enter:
mount /dev/dvd /mnt

8. Enter:
/mnt/security/cms_sec
The system displays the following message if you have not already changed the default
password for cmssvc user ID:
Avaya CMS security configuration started: Thu Jan 28 19:53:46 EST 2021
The backup directory for this run is: /cms/install/logdir/security/bkup_10338
Password change is required for user cmssvc

New password:
9. Enter and reenter a new password for the cmssvc user ID. You must follow standard
password requirements as documented in Avaya Call Management System Security.
The system displays messages similar to the following example:
Force password reset for user: cmssvc successfully executed.

File: /etc/cron.d/cron.allow already exists
Changed: permissions on /etc/cron.d/cron.allow to 644
File: /etc/cron.d/at.allow already exists
Changed: permissions on /etc/cron.d/at.allow to 644
File: /etc/init.d/umask already exists
Changed: permissions on /etc/init.d/umask to 744
Changed: group on /etc/init.d/umask to sys
File: /etc/rc1.d/S00umask already exists
Note: Forwarding request to 'systemctl disable sendmail.service'.
Disabled: sendmail
File: /etc/mail/sendmail.cf already exists, will overwrite
Copied: sec_files/sendmail.cf to /etc/mail/sendmail.cf
Line: ->PermitRootLogin no<- already in file: /etc/ssh/sshd_config
Line: ->PermitRootLogin no<- already in file: /etc/ssh/sshd_config
Service: sshd restarted
Disabled: time-dgram
Disabled: time-stream
Disabled: echo-dgram
Disabled: echo-stream
Disabled: discard-dgram
Disabled: discard-stream
Disabled: daytime-dgram
Disabled: daytime-stream
Disabled: chargen-dgram
Disabled: chargen-stream
Updated user informix shell to /sbin/nologin
Only 1 kernel exists, remove old kernels not required
Avaya CMS security configuration completed: Thu Jan 28 19:54:04 EST 2021
Note:
Note: If the system displays a configuration failed message, contact your Avaya
services representative.

Installing CMS patches
10. To capture the new services and preserve the output to a different file, enter:
chkconfig --list > /tmp/new_chkconfig.txt
11. Run the diff command against the two listings files and search for services that need to
be re-enabled. For example:
diff /tmp/current_chkconfig.txt /tmp/new_chkconfig.txt
12. View the output from the diff command and re-enable the services that are displayed. To
re-enable any customer used services, enter:
chkconfig [--level levels] <Service name> <on|off|reset>
The service name is the first column of the output from the chkconfig --list
command. For example:
chkconfig --level 2345 rpcbind on
Note:
Note: The files in the /tmp directory are not saved during the reboot process. If you
need to keep a copy of the files, move them to a directory where contents are not
erased during a reboot.
13. Continue with Installing CMS patches on page 47.
Installing CMS patches

The initial release of CMS Release 19.2 does not have any CMS patches. This section will be
updated when CMS patches are required for installation.
For a complete list of bug fixes and new features available in the latest CMS load, see Avaya
Call Management System Release Notes at:
Continue with Upgrading the CMS Supervisor Web Client software package on page 47.
Upgrading the CMS Supervisor Web Client software

package
Procedure

● If on a VMware system, do the steps in Common procedure for mounting a CMS ISO
image on page 29. After completing that procedure, continue with Step 5.
● If on a non-VMware system, continue with step 2.
2. Load the CMS software disc into the disc drive.
3. Change to the root directory, enter:
cd /
4. Mount the DVD drive. Enter:
mount /dev/dvd /mnt
mount: block device /dev/sr0 is write-protected, mounting read-only
5. Determine whether the Web Client software package is installed on the system. Enter:
rpm -q cmsweb
The system displays the following output:
cmsweb-Rnn.n.n.n-<BuildNumber>
6. Determine the Web Client software version on the CMS software disc or CMS ISO image.
Enter:
strings /mnt/cmsweb.bin | grep MINOR=
The system displays the following output:
MINOR=web<BuildNumber>
7. Compare the version portion of the Web Client software on the disc to the version of the
Web Client currently installed on the CMS server and do one of the following steps:
● If the Web Client software version on the disc is newer than the Web Client software
version on the CMS server, then you need to upgrade the Web Client software.
Continue with Step 8.
● If the Web Client software version on the disc is same or older than the Web Client
software version on the CMS server, then you do not need to upgrade the Web Client
software. Continue with Turning on CMS on page 49.
8. Remove the current Web Client package. Enter:
rpm -e cmsweb
The system removes the Web Client package.

Turning on CMS
9. To install the Web Client package, enter:

/mnt/cmsweb.bin
The system displays the following messages:

Extracting the rpm....
Installing (cmsweb) version

Proceeding with install...
Preparing... ########################################### [100%]

1:cmsweb ########################################### [100%]
The system installs the new Web Client software package.

10. Continue with Turning on CMS on page 49.
Turning on CMS
Procedure
1. Enter:
cmsadm
The system displays the CMSADM menu.
2. Enter the number associated with the run_cms option.
Select one of the following

1) Turn on CMS
2) Turn off CMS but leave IDS Running
3) Turn off CMS
Enter choice (1-3):
3. Enter: 1
The system starts CMS and returns to the command prompt.
4. Restart CMS data collection if data collection was turned off at the beginning of the
upgrade.
5. Manually run the appropriate Archiver from System Setup if CMS was off during the time
your Archiver normally runs.
6. Continue with Starting the CMS Supervisor Web Client software on page 50.

Starting the CMS Supervisor Web Client software

Procedure
1. Enter:
cmsweb start
! Important:
Important: Do not start the Web Client software if the customer does not plan on using the
Web Client to access CMS administration or reports. Starting the Web Client
software opens ports that the customer may not want opened.
2. Continue with Starting Avaya OA data forwarders on page 50.
Starting Avaya OA data forwarders

If the CMS configuration includes data collection by Avaya OA, turn on all Avaya OA forwarders
on the CMS server using the pa start all command. For more information about Avaya OA
forwarders, see Avaya OA Maintenance and Troubleshooting.

Chapter 6: Completing the base load
upgrade process
You must do the procedures in this section to complete the CMS base load upgrade process.
This section includes the following procedures:
● Doing a backup of the system files on page 51
● Doing a backup of the CMS data on page 51
Prerequisites
● Do all of the required procedures in Updating the Linux operating system on page 29.
● Do all of the required procedures in Upgrading the CMS base load on page 37.
Doing a backup of the system files

After the base load upgrade has completed successfully, do a backup to create a reliable copy
of the computer system files. For instructions on how to backup the system files, see Backing
up your CMS system data on page 22.
Doing a backup of the CMS data

After the base load upgrade has completed successfully, do a backup to create a reliable copy
of the computer CMS data files. For instructions on how to backup the CMS data, see Backing
up your CMS data on page 24.

Chapter 6: Completing the base load upgrade process

Chapter 7: Resources
Documentation
CMS and CMS Supervisor Documents
Title Description Audience

Overview
Avaya Call Management Describes tested product characteristics and Sales engineers,
System Overview and product capabilities including feature Administrators
Specification descriptions, interoperability, performance
specifications, security, and licensing
requirements.
Product Privacy Statement for Describes how personal data is stored and Administrators
Avaya Call Management processed by CMS.
System
Design
Avaya Customer Experience Describes the Avaya Customer Experience Sales engineers
Virtualized Environment Virtualized Environment market solution
Solution Description from a holistic perspective that focuses on
the functional view of the solution
architecture.
Installation, upgrades, maintenance, and troubleshooting
Deploying Avaya Call Describes how to plan, deploy, and Avaya support
Management System configure CMS on new VMware-based personnel
installations.
Deploying Avaya Call Describes how to plan, deploy, and Avaya support
Management System on configure CMS on new Amazon Web personnel
Amazon Web Services Services installations.
Port Matrix for Avaya Call Lists the ports and connections used by Avaya support
Management System CMS. personnel


Avaya Call Management Describes how to install, maintain, and Avaya support
System Dell® PowerEdge™ troubleshoot Dell® servers used with CMS. personnel
R630 and R730 Hardware
Installation, Maintenance and
Troubleshooting
Avaya Call Management Describes how to install, maintain, and Avaya support
System HPE DL20 G9 and troubleshoot HPE servers used with CMS. personnel
DL380 G9 Hardware
Installation, Maintenance, and
Troubleshooting
Planning for Avaya Call Describes the procedures customers must Administrators
Management System Upgrades plan for before and after upgrading to a new
CMS release.
Upgrading Avaya Call Describes the procedures required to Avaya support
Management System upgrade to a new CMS release. personnel
Avaya Call Management Describes the procedures to upgrade from Avaya support
System Base Load Upgrade one base load (for example, 19.1.0.0) to personnel,
another base load (for example, 19.1.0.1). Administrators
Not all releases support base load upgrades.
Maintaining and Describes how to configure, maintain, and Avaya support
Troubleshooting Avaya Call troubleshoot CMS. personnel,
Management System Administrators
Avaya Call Management Describes how to connect and administer Avaya support
System and Communication the Communication Manager systems used personnel,
Manager Connections, by CMS.
Administration, and Administrators
Troubleshooting
Avaya Call Management Describes how to connect to HA servers and Avaya support
System High Availability upgrade to HA. personnel,
Connectivity, Upgrade and
Administration Administrators
User guides
Using Avaya Call Management Describes how to use and maintain a CMS Avaya support
System High Availability HA system. personnel,
Administrators
Using Avaya Call Management Describes how to back up your CMS data Administrators
System LAN Backup using a LAN connection to a remote server.
Using Avaya Call Management Describes how to install and maintain your Avaya support
System High Availability CMS High Availability (HA) system. personnel,
Administrators

Documentation

Using ODBC and JDBC with Describes how to use Open Database Administrators
Avaya Call Management Connectivity (ODBC) and Java Database
System Connectivity (JDBC) with CMS.
Administration
Administering Avaya Call Provides instructions on administering a Avaya support
Management System contact center using CMS Supervisor. personnel,
Administrators
Avaya Call Management Describes the format of the Call History data Administrators
System Call History Interface files and how to transfer these files to
another computer.
Avaya Call Management Describes each database item and Administrators,
System Database Items and calculation that CMS tracks and how CMS Report designers
Calculations calculates the values displayed on CMS
reports and CMS Supervisor reports.
Avaya Call Management Describes how to design and create custom Administrators,
System Custom Reports reports in CMS. Operations
personnel, Report
designers
Avaya Call Management Describes how to implement security Avaya support
System Security features in CMS. personnel,
Administrators.
CMS Supervisor
Avaya CMS Supervisor Clients Describes how to install and configure CMS Avaya support
Installation and Getting Started Supervisor. personnel,
Administrators
Avaya CMS Supervisor Reports Describes how to use CMS Supervisor Administrators,
reports. Operations
personnel
Avaya CMS Supervisor Report Describes how to create new reports and to Administrators,
Designer edit existing reports through Report Operations
Designer and Report Wizard. personnel, Report
designers

Avaya Solutions Platform Documents

Avaya Solutions Describes the key features of Avaya IT Management, sales and
Platform Overview and Solutions Platform server. deployment engineers, solution
Specification architects, support personnel
Installing the Avaya Describes how to install Avaya Solutions Sales and deployment engineers,
Solutions Platform 130 Platform 130 Series servers. solution architects, support
Appliance personnel
Maintaining and Describes procedures to maintain and Sales and deployment engineers,
Troubleshooting Avaya troubleshoot Avaya Solutions Platform solution architects, support
Solutions Platform 130 130 Series servers. personnel
Appliance
Avaya Solutions Describes procedures to use the Sales and deployment engineers,
Platform 130 Series iDRAC9 tools on the Avaya Solutions solution architects, support
iDRAC9 Best Platform 130 Series servers. personnel
Practices
WebLM Documents

Deploying standalone Avaya Deploy the application in virtual appliance Implementation
WebLM in Virtual Appliance environment by using Solution personnel
Deployment Manager.
Deploying standalone Avaya Deploy the application in virtualized Implementation
WebLM in Virtualized Environment environment. personnel
Deploying standalone Avaya Deploy the application on cloud services. Implementation
WebLM in Infrastructure as a personnel
Service Environment
Deploying standalone Avaya Deploy the application in software-only Implementation
WebLM in Software-Only environment. personnel
Environment
Upgrading standalone Avaya Upgrade the application. Implementation
WebLM personnel
Administering standalone Avaya Administer the system. System
WebLM administrators

Documentation
VMware Documents
VMware Document description Document URL

component or
operation
vSphere Virtual Provides information on managing virtual https://docs.vmware.com/en/
Machine machines in the VMware vSphere Web Client for VMware-vSphere/6.5/
Administration vSphere 6.0 or later. This document also provides com.vmware.vsphere.vm_a
information of the following: dmin.doc/
GUID-55238059-912E-411F
● Deploying OVF templates -A0E9-A7A536972A91.html
● Configuring virtual machine hardware and
options
● Managing Virtual Machines
vSphere Web Provides information on how through a browser https://docs.vmware.com/en/
Client vSphere Web Client connects to a vCenter server VMware-vSphere/6.5/
or directly to an ESXi host if a vCenter Server is com.vmware.vsphere.vcent
not used. erhost.doc/
GUID-A618EF76-638A-49D
A-991D-B93C5AC0E2B1.ht
ml
Note:
Note: If the document description (link) are no longer active, consult VMware for
documents associated with the component or operation.
Related links
Finding documents on the Avaya Support website on page 57
Accessing the port matrix document on page 58
Avaya Documentation Portal navigation on page 58
Finding documents on the Avaya Support website

Procedure
1. Go to https://support.avaya.com.
2. Log on to the Avaya website with a valid Avaya user ID and password.
3. Click Support by Product > Documents.

4. In Enter your Product Here, type the product name and then select the product from the
list.
5. In Choose Release, select an appropriate release number.
The Choose Release field is not available if there is only one release for the product.
6. In the Content Type filter, click a document type, or click Select All to see a list of all
available documents.
For example, for user guides, click User Guides in the Content Type filter. The list only
displays the documents for the selected category.
7. Click the document to open it in your browser or download the document.
Accessing the port matrix document

Procedure
3. Click Support by Product > Documents.
4. In Enter your Product Here, type the product name and then select the product from the
list.
5. In Choose Release, select an appropriate release number.
The Choose Release field is not available if there is only one release for the product.
6. In the Content Type filter, select one or more of the following categories:
● Application & Technical Notes
● Design, Development & System Mgt
The system displays the Port Matrix document.
7. Click the document to open it in your browser or download the document.
Avaya Documentation Portal navigation

Customer documentation for some programs is now available on the Avaya Documentation
Center website at https://documentation.avaya.com/.
! Important:
Important: For documents that are not available on the Avaya Documentation Center, click
More Sites > Support on the top menu to open https://support.avaya.com.

Viewing Avaya Mentor videos
Using the Avaya Documentation Center, you can:

● Search for content in one of the following ways:
- Type a keyword in Search, and click Filters to search for content by product or
release.
- From Products & Solutions, select a solution and product and then select the
appropriate document from the list.
● Sort documents on the search results page by last updated and relevance.
● Publish a PDF of the current section in a document, the section and its subsections, or the
entire document.
● Add content to your collection by using My Docs.
Navigate to the Manage Content > My Docs menu, and do any of the following:
- Create, rename, and delete a collection.
- Add content from various documents to a collection.
- Save a PDF of selected content in a collection and download it to your computer.
- Share content in a collection with others through email.
- Receive content that others have shared with you.
● Add yourself as a watcher by using the Watch icon.
Navigate to the Manage Content > Watchlist menu, and do the following:
- Enable Include in email notification to receive alerts in email.
- Unwatch selected content, all content in a document, or all content on the Watch list
page.
As a watcher, you are notified when content is updated or deleted from a document, or the
document is removed from the portal.
● Share a section on social media platforms, such as Facebook, LinkedIn, and Twitter.
● Send feedback on a section and rate the content.
Note:
Note: Some functionality is only available when you log in to the portal. The available
functionality depends on the role with which you are logged in.
Viewing Avaya Mentor videos

Avaya Mentor videos provide technical content on how to install, configure, and troubleshoot
Avaya products.

About this task

Videos are available on the Avaya Support website, listed under the video document type, and
on the Avaya-run channel on YouTube.
Procedure
● To find videos on the Avaya Support website, go to https://support.avaya.com and do one
of the following:
- In Search, type Avaya Mentor Videos, click Clear All, and select Video in the
Content Type.
- In Search, type the product name. On the Search Results page, click Clear All, and
select Video in the Content Type.
The Video content type is displayed only when videos are available for that product.
In the right pane, the page displays a list of available videos.
● To find the Avaya Mentor videos on YouTube, go to www.youtube.com/AvayaMentor and
do one of the following:
- Enter a key word or key words in the Search Channel to search for a specific product
or topic.
- Scroll down Playlists, and click the name of a topic to see the list of videos available for
the topic. For example, Contact Centers.
Note:
Note: Videos are not available for all products.
Support
Go to the Avaya Support website at https://support.avaya.com for the most up-to-date
documentation, product notices, and knowledge articles. You can also search for release notes,
downloads, and resolutions to issues. Use the online service request system to create a service
request. Chat with live agents to get answers to questions, or request an agent to connect you
to a support team if an issue requires additional expertise.
Related links
Using the Avaya InSite Knowledge Base on page 60
Using the Avaya InSite Knowledge Base

The Avaya InSite Knowledge Base is a web-based search engine that provides:

Support
● Up-to-date troubleshooting procedures and technical tips

● Information about service packs
● Access to customer and technical documentation
● Information about training and certification programs
● Links to other pertinent information
If you are an authorized Avaya Partner or a current Avaya customer with a support contract, you
can access the Knowledge Base without extra cost. You must have a login account and a valid
Sold-To number.
Use the Avaya InSite Knowledge Base for any potential solutions to problems.
The system displays the Avaya Support page.
3. Click Support by Product > Product Specific Support.
4. In Enter Product Name, enter the product, and press Enter.
5. Select the product from the list, and select a release.
6. Click the Technical Solutions tab to see articles.
7. Select relevant articles.


Avaya CMS Base Load Upgrade 19.2 March 2021

Uploaded by

Copyright:

Available Formats

Avaya CMS Base Load Upgrade 19.2 March 2021

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Avaya CMS Base Load Upgrade 19.2 March 2021

Uploaded by

Copyright:

Available Formats

Avaya Call Management System

Base Load Upgrade

Hosted Service Heritage Nortel Software

Compliance with Laws

Preventing Toll Fraud

Chapter 3: Preparing for a base load upgrade. . . . . . . . . . . . . . . . . . . . . . . . . 13

Avaya CMS Base Load Upgrade March 2021 5

Chapter 4: Updating the Linux operating system . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 5: Upgrading the CMS base load . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Chapter 6: Completing the base load upgrade process . . . . . . . . . . . . . . . . . . . 51

Avaya CMS Base Load Upgrade March 2021 6

Avaya CMS Base Load Upgrade March 2021 7

Avaya CMS Base Load Upgrade March 2021 8

Supported upgrade scenarios

Avaya CMS Base Load Upgrade March 2021 9

● Customer-provided Amazon Web Services (AWS) servers

Base load upgrades

When and how to use this document

Avaya CMS Base Load Upgrade March 2021 10

Impacts to CMS service

Contacting Avaya technical support during upgrade

Possible customization impacts

Avaya CMS Base Load Upgrade March 2021 11

Avaya CMS Base Load Upgrade March 2021 12

Avaya CMS Base Load Upgrade March 2021 13

Verifying the current CMS version and load

Verifying that your previous backups completed

Avaya CMS Base Load Upgrade March 2021 14

Verifying the backup of your CMS system data

Verifying that your last CMSADM backup completed successfully

===== Begin backup <timestamp>

Converter started <timestamp>

Testing tape on /dev/rmt/0...

Tape test on /dev/rmt/0 is okay...

===== Finished backup <timestamp>

3. Choose one of the following actions:

Avaya CMS Base Load Upgrade March 2021 15

===== LAN SYSTEM BACKUP SUCCESSFULLY FINISHED Date and time

4. Choose one of the following actions:

Verifying the backup of your CMS data

Avaya CMS Base Load Upgrade March 2021 16

Verifying that your previous full or incremental backup completed

1711 <timestamp> 2 1 INFO

4. Choose one of the following actions:

Avaya CMS Base Load Upgrade March 2021 17

3. Verify that the previous data backup completed successfully.

+++++ ON-Bar BACKUP SUCCESSFULLY FINISHED Date and time

4. Choose one of the following actions:

Verifying that the nightly archiver is functioning

Avaya CMS Base Load Upgrade March 2021 18

2600 <timestamp> 2 1 INFO

10. Select Exit to return to the previous menu.

Checking the status of the hardware platform disk drives

Avaya CMS Base Load Upgrade March 2021 19

Checking for memory errors and system panics

messages-20121223:<timestamp> trex Kernel panic – not syncing: : Port x halting

Verifying free space in the root file system

Filesystem 1K-blocks Used Available Use% Mounted on

/dev/sda2 9842412 2709148 6633288 29% /

2. Check the disk capacity.