Avaya Call Management System: Release 16 Base Load Upgrade

Avaya Call Management System
Release 16 Base Load Upgrade
November 2009
2009 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document might be incorporated in future releases. Documentation disclaimer Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all the time and we have no control over the availability of the linked pages. Warranty Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avayas standard warranty language, as well as information regarding support for this product, while under warranty, is available through the Avaya Support Web site: http://www.avaya.com/support License USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER'S ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA WEB SITE http://www.avaya.com/support/LicenseInfo ("GENERAL LICENSE TERMS"). IF YOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUST RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN (10) DAYS OF DELIVERY FOR A REFUND OR CREDIT. Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. "Designated Processor" means a single stand-alone computing device. "Server" means a Designated Processor that hosts a software application to be accessed by multiple users. "Software" means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone Products or pre-installed on Hardware. "Hardware" means the standard hardware Products, originally sold by Avaya and ultimately utilized by End User. License type(s) Designated System(s) License (DS). End User may install and use each copy of the Software on only one Designated Processor, unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User. Avaya may require the Designated Processor(s) to be identified by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given 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 e-mail or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Product that permits one user to interface with the Software. Units may be linked to a specific, identified Server. Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law. Third-party components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ("Third Party Components"), which may contain terms that expand or limit rights to use certain portions of the Product ("Third Party Terms"). Information identifying Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: http://www.avaya.com/support/ThirdPartyLicense
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. Avaya fraud intervention If you suspect that you are being victimized by toll fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support Web site: http://www.avaya.com/support Trademarks Avaya and the Avaya logo are either registered trademarks or trademarks of Avaya Inc. in the United States of America and/or other jurisdictions. All other trademarks are the property of their respective owners. Downloading documents For the most current versions of documentation, see the Avaya Support Web site: http://www.avaya.com/support Avaya support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Support Web site: http://www.avaya.com/support
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of this document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . When and how to use this document . . . . . . . . . . . . . . . . . . . . . . . . . . . Impacts to CMS service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contacting Avaya for assistance with your upgrade . . . . . . . . . . . . . . . . . . . Possible customization impacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade kit contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contacting Avaya technical support during the upgrade . . . . . . . . . . . . . . . . . Visual Vectors upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for a base load upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying the current CMS version and load . . . . . . . . . . . . . . . . . . . . . . . . Verifying that your previous backups completed successfully . . . . . . . . . . . . . Verifying the backup of your CMS system data . . . . . . . . . . . . . . . . . . . . Verifying that your last CMSADM backup completed successfully . . . . . . . Verifying that your last LAN backup of the system data completed successfully Verifying the backup of your CMS data . . . . . . . . . . . . . . . . . . . . . . . . Verifying that your previous full or incremental backup completed successfully Verifying that your last LAN backup of CMS data completed successfully . . . Verifying that the nightly archiver is functioning . . . . . . . . . . . . . . . . . . . . . Checking the status of the disk drives . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking for memory errors and system panics . . . . . . . . . . . . . . . . . . . . . Verifying free space in the root file system . . . . . . . . . . . . . . . . . . . . . . . . Rebooting your CMS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing up the CMS system . . . . . . . . . . . . . . . . . Backing up your system data . . . . . . . . . . . . . . . Performing a CMSADM backup . . . . . . . . . . . . Performing a full system backup with LAN backup . Backing up your CMS data . . . . . . . . . . . . . . . . Performing a full data backup with a tape device . . Performing a full data backup with LAN backup . . Backing up any new CMS data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5 6 6 7 7 7 7 8 9 9 10 10 10 11 11 12 12 13 13 14 15 16 16 17 17 17 18 19 19 20 21 23 23 24 24
Updating the Solaris operating system . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping the Avaya Visual Vectors server software. . . . . . . . . . . . . . . . . . . . Stopping AOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Avaya CMS R16 Base Load Upgrade
November 2009
Contents
Stopping Avaya OA data forwarders . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Solaris patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Avaya CMS security script. . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading the CMS base load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading CMS Supplemental Services . . . . . . . . . . . . . . . . . . . . . . . . . . Removing CMS patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing the current CMS load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting AOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the new CMS base load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing CMS patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Turning on CMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting Avaya OA data forwarders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing the Avaya Visual Vectors Server software . . . Removing the Avaya Visual Vectors Server software . Installing the Avaya Visual Vectors Server software . Turning on Avaya Visual Vectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25 25 27 29 29 30 32 33 34 35 36 37 38 38 38 39 40 41 41 41 42 42
Completing the base load upgrade process . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Returning to the Common Desktop Environment . . . . . . . . . . . . . . . . . . . . . Performing a backup of the system files. . . . . . . . . . . . . . . . . . . . . . . . . . Performing a backup of the CMS data . . . . . . . . . . . . . . . . . . . . . . . . . . .
November 2009
Introduction
This Avaya Call Management System (CMS) base load upgrade is designed to be installed by Avaya customers who have had problems with earlier versions of the Avaya CMS Release 16 (R16) software application. This upgrade provides all known software fixes from previous Avaya CMS R16 issues. Avaya recommends that you load this upgrade as soon as possible. If you ask our Technical Support Organization to troubleshoot your Avaya product, they will require you to use the latest software release. This section includes the following topics:

Purpose of this document on page 5 When and how to use this document on page 6 Impacts to CMS service on page 6 Contacting Avaya for assistance with your upgrade on page 7 Possible customization impacts on page 7 Upgrade kit contents on page 7 Contacting Avaya technical support during the upgrade on page 7 Visual Vectors upgrades on page 8
Purpose of this document

The purpose of this document is to describe the Avaya Call Management System (CMS) base load upgrade process for R16xx.x. This Avaya CMS base load upgrade is designed to be installed by Avaya CMS customers who either have had problems with an earlier version of the product or would like access to any new features added in the maintenance release. This upgrade provides all known software fixes from previous versions. The software is acquired by ordering the latest PCN. The PCN provides a list of all fixes and features added in the maintenance release.
!
Important:
Important: Before installing a base load upgrade, verify that the software discs you received when ordering the PCN actually upgrade your current version of software. Verify that you are using the proper base load upgrade document for your release of CMS.
November 2009
Introduction
When and how to use this document

Use this document to upgrade Avaya Call Management System (CMS) from an older CMS Release 16 (R16) base load to a newer CMS R16 load. Unless indicated otherwise, all procedures in the Avaya CMS Release 16 Base Load Upgrade document are required. Avaya recommends that:
Before performing the upgrade, you read through this entire document so that you are familiar with what tasks you will need to perform. If you decide you would like to have Avaya assist you performing the upgrade, see Contacting Avaya for assistance with your upgrade on page 7. 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 UNIX commands during the upgrade process. You must enter the command from the UNIX 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

!
CAUTION:
CAUTION: This software upgrade is service affecting.
During the upgrade process you will have to reboot your CMS system and turn off the CMS software. This upgrade can take several hours to complete. During the Solaris patch installation, your system will display an estimate of the amount of time needed to install the Solaris patches. The Solaris patch installation is the part of the base load upgrade that usually requires the longest amount of time to complete.
November 2009
Contacting Avaya for assistance with your upgrade
Contacting Avaya for assistance with your 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. Contact the Technical Support Organization at 1-800-242-2121.
Possible customization impacts

The software upgrade that you are installing could potentially impact system customization that was performed before this upgrade. For example:

Custom reports LAN printer customization Work-force management interfaces Operational Analyst
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 kit contents

All the software you need for the upgrade should be included with your upgrade kit.
Contacting Avaya technical support during the upgrade

If you encounter problems or have questions during the upgrade and are unable to resolve them by following the upgrade instructions, call technical support at 1-800-242-2121. Be ready to provide the number of the Quality Protection Plan you are using.
November 2009
Introduction
Visual Vectors upgrades

If you are upgrading the Visual Vectors software to Visual Vectors 16, which is compatible with CMS R16, you must upgrade to the appropriate versions of the following software:

A CMS load of r16aa.x or later. Visual Vectors server vvsr16xx.x or later. Visual Vectors client software release VV16.
November 2009
Preparing for a base load upgrade

This section describes the tasks you must perform before you upgrade your CMS base load. These procedures will help you verify that your CMS system has no existing hardware or software problems before the upgrade. If you do not perform these procedures, your base load upgrade could fail, and your CMS system could be put in a non-functioning state for some time. This section includes the following topics:

Prerequisites on page 9 Verifying the current CMS version and load on page 10 Verifying that your previous backups completed successfully on page 10 Verifying that the nightly archiver is functioning on page 13 Checking the status of the disk drives on page 14 Checking for memory errors and system panics on page 15 Verifying free space in the root file system on page 16 Rebooting your CMS system on page 16 Backing up the CMS system on page 17
Prerequisites
Before you perform the procedures in this section, you must:

Read the information in Introduction on page 5 The Avaya CMS software disc will include a readme file called cms.readme. Avaya recommends you review this file for any changes that might impact the procedures in this document. Log in to the system as root.
!
Important:
Important: You will not be able to log into the system remotely as root. If you are logging into the system remotely, log in as a user and then enter: su - root
November 2009
Verifying the current CMS version and load

To verify the version and load of CMS currently on the machine: 1. Log in to the system as root. 2. Enter: pkginfo -x cms
The system displays the currently installed CMS package, including the load number, for example:
cms Avaya Call Management System (sparc)
xxxxx.x
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. This section includes the following topics:

Verifying the backup of your CMS system data on page 10 Verifying the backup of your CMS data on page 12
Verifying the backup of your CMS system data

To verify that your previous system backup completed successfully, choose one of the following procedures:
If you backup your data directly to a tape device, go to Verifying that your last CMSADM backup completed successfully on page 11. You are responsible for backing up your CMS system unless you engage Avaya to perform the backups in conjunction with this base load upgrade.
10
November 2009
Verifying that your previous backups completed successfully
If you use the CMS LAN backup feature, go to Verifying that your last LAN backup of the system data completed successfully on page 11 You are responsible for backing up your CMS system. Avaya is not responsible for performing LAN backups. For more information about the CMS LAN backup feature, see Avaya Call Management System Release 16 LAN Backup User Guide. 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

To verify that your last CMSADM backup completed successfully: 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 Wed Apr 9 05:37:05 EDT 2009
Converter started Wed Apr 9 05:37:07 EDT 2009 Converter completed successfully Wed Apr 9 05:37:10 EDT 2009 Testing tape on /dev/rmt/0... Tape test on /dev/rmt/0 is okay... 2873600 blocks ===== Finished backup Wed Apr 9 06:30:35 EDT 2009
3. Choose one of the following actions:
If your previous backup was successful, go to Verifying the backup of your CMS data on page 12. If your previous backup was not successful, contact your Avaya CMS support representative.
Verifying that your last LAN backup of the system data completed successfully
If you use the CMS LAN backup feature, perform the following procedure: 1. Enter: cat /cms/install/logdir/backup.log | pg 2. Press Enter to continue the display. It might be necessary to repeat this step several times.
November 2009
11
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 12. If your previous backup was not successful, contact your Avaya CMS support representative.
Verifying the backup of your CMS data

To verify that your previous system 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 12. If you use the CMS LAN backup feature, go to Verifying that your last LAN backup of CMS data completed successfully on page 13 For more information about the CMS LAN backup feature, see Avaya Call Management System Release 16 LAN Backup User Guide. This document provides: information about using the CMS LAN backup feature, hardware requirements, software requirements, and support guidelines.
Verifying that your previous full or incremental backup completed successfully

To verify that your previous full or incremental backup completed successfully: 1. Verify that you are logged in as root.
!
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: whoami
2. Enter: tail /cms/maint/backup/back.log
12
November 2009
Verifying that the nightly archiver is functioning
3. Verify that the previous full or incremental backup completed successfully. An example of a successful full or incremental backup message is:
1711 4/15/09 2:14 AM 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 13. If your previous backup was not successful, contact your Avaya CMS support representative.
Verifying that your last LAN backup of CMS data completed successfully
To verify that your last LAN backup of CMS data completed successfully: 1. Enter: cat /cms/install/logdir/backup.log | pg 2. Press Enter to continue the display. It might be necessary to repeat this step several 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 13. If your previous backup was not successful, contact your Avaya CMS support representative.
Verifying that the nightly archiver is functioning

To verify that nightly archiver is functioning correctly: 1. Verify that you are logged in to the system as root.
November 2009
13
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. 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 4/15/09 2:15 AM 2 1 INFO ARCHIVER status: Daily Archive for (Mon) Apr. 14, 2009 Successful
10. Select Exit to return to the previous menu. 11. Choose one of the following actions:
If the nightly archiver is functioning correctly, go to Checking the status of the disk drives on page 14. If the nightly archiver is not functioning correctly, contact your Avaya CMS support representative.
Checking the status of the disk drives

To check the status of the disk drives: 1. Verify that you are logged in to the system as root. 2. Enter: /opt/StorMan/arcconf getconfig 1 | egrep "Logical devices" | pg 3. The output will look similar to the following:
Logical devices/Failed/Degraded : 1/0/0
14
November 2009
Checking for memory errors and system panics
If the output shows zero for Failed or Degraded, continue with Checking for memory errors and system panics on page 15 If the output shows anything other than zero for Failed and Degraded, your system requires maintenance. Contact your Avaya CMS support representative.
Checking for memory errors and system panics

To check for memory errors and system panics: 1. Enter: egrep -i "panic | memory error | afsr" /var/adm/messages* | pg Note: It might be necessary to press Enter to continue the display. An example of some memory error messages are:
/var/adm/messages:Apr 15 21:27:51 r3upctn SUNW,UltraSPARC-II: [ID 860344 kern.notice] [AFT0] errID 0x00011903.9c12748f Corrected Memory Error on Board 3 J3600 is Persistent /var/adm/messages:Apr 16 09:27:52 r3upctn SUNW,UltraSPARC-II: [ID 417990 kern.notice] [AFT0] Corrected Memory Error on CPU7, errID 0x00014050.8646ccd6 /var/adm/messages:Apr 16 09:27:52 r3upctn AFSR 0x00000000.00100000<CE> AFAR 0x00000000.09498550 /var/adm/messages:Apr 16 09:27:52 r3upctn AFSR.PSYND 0x0000(Score 05) AFSR.ETS 0x00 Fault_PC 0x10023bd0 /var/adm/messages:Apr 16 09:27:52 r3upctn SUNW,UltraSPARC-II: [ID 136280 kern.notice] [AFT0] errID 0x00014050.8646ccd6 Corrected Memory Error on Board 3 J3600 is Persistent /var/adm/messages:Apr 16 21:27:51 r3upctn SUNW,UltraSPARC-II: [ID 488351 kern.notice] [AFT0] Corrected Memory Error on CPU6, errID 0x0001679c.f8a4aa5f /var/adm/messages:Apr 16 21:27:51 r3upctn AFSR 0x00000000.00100000<CE> AFAR 0x00000000.09498550 /var/adm/messages:Apr 16 21:27:51 r3upctn AFSR.PSYND 0x0000(Score 05) AFSR.ETS 0x00 Fault_PC 0x10023bd0 /var/adm/messages:Apr 16 21:27:51 r3upctn SUNW,UltraSPARC-II: [ID 599456 kern.notice] [AFT0] errID 0x0001679c.f8a4aa5f Corrected Memory Error on Board 3 J3600 is Persistent /var/adm/messages:Apr 17 09:27:51 r3upctn SUNW,UltraSPARC-II: [ID 473191 kern.notice] [AFT0] Corrected Memory Error on CPU6, errID 0x00018ee9.a6074fb3
Note:
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 16. If the system displays any memory error or panic messages, your system requires maintenance. Contact your Avaya CMS support representative.
November 2009
15
Verifying free space in the root file system

To verify that sufficient free space is available in your root file system to accomplish the base load upgrade: 1. Enter: df -k / The system displays a message similar to the following:
Filesystem /dev/dsk/c1t0d0s0 kbytes 6201485 used 1738401 avail 4401070 capacity 29% Mounted on /
2. Check the disk capacity. 3. Choose one of the following actions:

If the disk capacity is less than 85%, go to Rebooting your CMS system on page 16. If the disk capacity is 85% or greater, contact your Avaya CMS support representative.
Rebooting your CMS system

You must reboot your CMS system and verify that the system is functioning properly. Reboot the CMS system before you backup your data. To reboot your CMS system: 1. Enter the following command from the pound (#) prompt: /usr/sbin/shutdown -i6 -g0 -y The system reboots. 2. Log in to the system as root. 3. Choose one of the following actions:
If the system does not boot correctly or if any error messages are displayed, contact your Avaya CMS support representative. If the system boots correctly, go to Backing up the CMS system on page 17.
16
November 2009
Backing up the CMS system

Before beginning a CMS base load upgrade, you must backup your CMS system data and CMS data. This section includes the following topics:

Backing up your system data on page 17 Backing up your CMS data on page 19 Backing up any new CMS data on page 21
Backing up your system data

A backup of the system data must be performed approximately one day before the CMS base load upgrade. To back up of your current system files, choose one of the following procedures:
If you backup your data directly to a tape device, go to Performing a CMSADM backup on page 17. If you use the CMS LAN backup feature, go to Performing a full system backup with LAN backup on page 18 For more information about the CMS LAN backup feature, see Avaya Call Management System Release 16 LAN Backup User Guide. This document provides: information about using the CMS LAN backup feature, hardware requirements, software requirements, and support guidelines.
Performing a CMSADM backup

To back up of your current system files, perform the following 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 in as root. 3. Enter: cmsadm The Avaya Call Management System Administration Menu (CMSADM Menu) is displayed.
November 2009
17
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: device name.
Please insert the first cartridge tape into 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) HP DAT-72 tape drive: /dev/rmt/0 2) HP DAT-72 tape drive: /dev/rmt/1 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/rmt/0. 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 (xxxxx.x)
6. Write protect the tape and store the tape in a secure location until the next backup is performed. 7. Go to Backing up your CMS data on page 19.
Performing a full system backup with LAN backup

If you use the CMS LAN backup feature, perform the following procedure: 1. Log in as root.
18
November 2009
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 19.
Backing up your CMS data

Your CMS data must be backed up approximately one day before the CMS base load upgrade is performed. To backup your CMS data, choose one of the following procedures:
If you backup your data directly to a tape device, go to Performing a full data backup with a tape device on page 19. If you use the CMS LAN backup feature, go to Performing a full data backup with LAN backup on page 20. For more information about the CMS LAN backup feature, see Avaya Call Management System Release 16 LAN Backup User Guide. This document provides: information about using the CMS LAN backup feature, hardware requirements, software requirements, and support guidelines.
Performing a full data backup with a tape device

To perform a full backup of CMS data: 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 root.
November 2009
19
3. 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.
4. Press Enter to access the action list in the upper right corner of the window. 5. Select Run and press Enter. 6. Wait for the backup to complete. If the backup does not complete successfully, contact your Avaya CMS support representative. 7. Write protect the tape and store the tape in a secure location until the next backup is performed. 8. Go to Backing up any new CMS data on page 21.
Performing a full data backup with LAN backup

If you use the CMS LAN backup feature, perform the following procedure: 1. Verify that you are logged in as root. 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/backup.log cat /cms/install/logdir/bar_act.log 4. Go to Backing up any new CMS data on page 21.
20
November 2009
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, go to Updating the Solaris operating system on page 23. If new CMS data has been generated since your last CMS data backup, perform one of the following procedures immediately before the upgrade: - Performing a full data backup with a tape device on page 19 - Performing a full data backup with LAN backup on page 20
For more information about the CMS LAN backup feature, see Avaya Call Management System Release 16 LAN Backup User Guide. This document provides information about using the CMS LAN backup feature, hardware requirements, software requirements, and support guidelines.
November 2009
21
22
November 2009
Updating the Solaris operating system

This section contains procedures for updating your Solaris operating system. You must complete the procedures in this section before upgrading your CMS base load. This section includes the following topics:

Prerequisites on page 23 Stopping the Avaya Visual Vectors server software on page 24 Stopping AOM on page 24 Stopping Avaya OA data forwarders on page 25 Installing Solaris patches on page 25 Installing the Avaya CMS security script on page 27
Prerequisites

Read the information in Introduction on page 5 Perform all of the required procedures in Preparing for a base load upgrade on page 9 Verify that you are logged in to the system as root.
November 2009
23
Stopping the Avaya Visual Vectors server software

To stop the Avaya Visual Vectors server software: 1. Enter: setupaas The system displays the Avaya Visual Vectors Server System Services Menu, as shown in the following figure.
Avaya Visual Vectors Server System Services Menu Select a command from the list below. 1) 2) 3) 4) 5) 6) init_vvs run_vvs auth_display auth_set backup restore Setup the initial configuration Turn VVS on or off Display simultaneous VVS logins Change simultaneous VVS logins Backup vector steps and layout files Restore vector steps and layout files
Enter choice (1-6) or q to quit:
2. Enter the number associated with the run_vvs option. The system displays the following message:
1) Turn VVS On 2) Turn VVS Off Enter choice (1-2) or q to quit:
3. Enter the number associated with the Turn VVS Off option.
Stopping AOM
To stop AOM, enter: aom stop
24
November 2009
Stopping Avaya OA data forwarders
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 Solaris patches

To install the Solaris patches: 1. Load the Avaya Call Management System software disc into the disc drive. 2. Enter: cmssvc The system displays the Avaya Call Management System Services Menu (CMSSVC Menu).
!
CAUTION:
CAUTION: CMS must be off in order to install the Solaris patches.
3. Enter the number associated with the run_cms option. 4. Enter the number associated with the Turn off CMS but leave IDS running option. The system returns to the command prompt. 5. Set the IDS environment by entering: . /opt/informix/bin/setenv 6. Enter: onmode -yuk 7. Ignore any error messages. 8. Enter: /cdrom/cdrom0/spatches_conf The system displays one of the following messages:
November 2009
25
If there are Solaris patches to install, the system displays the following message:
Warning: you must close all applications before running this script ................... ................... ................... Solaris patches have been spooled to your machine. The patches will be installed after rebooting. During the installation of patches your server will not be available. The estimated time to install all patches is:
15 minutes
Ready to install Patches. Please leave the CD in the drive. You will need to reboot the server for patches to install. Do you want to reboot now? [y,n,?]
!
Important:
Important: The message will contain an estimate of the amount of time needed to install the Solaris patches. If there are no Solaris patches to install, the system displays the following message:
There are no Solaris patches to install
9. Choose one of the following steps:

If there are Solaris patches to install, go to Step 10. If there are no Solaris patches to install, go to Step 13.
10. Install the Solaris patches by entering: y The system boots into single user mode and begins to install the Solaris patches. The Solaris patch installation takes at least the amount of time that was estimated earlier in the procedure. After the Solaris patches are installed, the system reboots into multiuser mode and displays a login prompt.
!
CAUTION:
CAUTION: If you cancel the installation of Solaris patches, must install them before upgrading CMS. To cancel installation of the Solaris patches, enter: n
11. Log in to the system as root. 12. Verify that all of the Solaris patches have been installed by entering: tail -10 /var/cms/spatches/spatches.log The system displays the following message:
All patches installed successfully.
26
November 2009
Installing the Avaya CMS security script
Note:
Note: If the installation procedure fails for any of the patches, the following message is displayed:
Installation failed for one or more Solaris patches. - 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. Patch installation completed: Fri Jan 18 13:28:19 MST 2009
If the message shown above is displayed, continue with this procedure and the remaining CMS base load upgrade procedures. When the upgrade is complete, notify your Avaya CMS support organization as prompted by the system. 13. If IDS is not running, turn on IDS with the following command: a. Enter cmssvc The system displays the CMSSVC menu. b. Enter the number associated with the run_ids option. The system starts IDS and returns to the command prompt. 14. If needed, restart the volfs service with the following command: svcadm disable svc:/system/filesystem/volfs svcadm enable svc:/system/filesystem/volfs 15. Go to Installing the Avaya CMS security script on page 27.
Installing the Avaya CMS security script

To install the Avaya security script:
!
Important:
Important: You will be able to log into the console only as root after you run the Avaya CMS security script. If you are logging into the system remotely, you will need to log in as another user and then su to root.
1. Verify that you are logged into the system as root. 2. Verify the current services running on the system, save the list for comparison against the listing after the security script run.
November 2009
27
Note:
Note: It is necessary to find out which services in the list of differences are used by the customer. 3. To verify services, enter: svcs -a > /tmp/current_svcs.txt 4. Verify the Avaya Call Management System software disc is in the disc drive. 5. Enter: cd / 6. Enter: /cdrom/cdrom0/security/cms_sec The system configures your security settings. This process will take some time. The system displays the following message when the process is complete:
Avaya CMS security configuration completed:
date
Note:
Note: If the system displays a configuration failed message, contact your Avaya services representative. 7. Run the verify command again with a new output name: svcs -a > /tmp/new_svcs.txt 8. Run a diff against the two listings files and search for services that need to be re-enabled. diff /tmp/current_svcs.txt /tmp/new_svcs.txt
9. View the output from the diff command and re-enable the services that are displayed. To re-enable any customer used services enter: svcadm enable <service name>
Service name is the third column in your listing files. You do not typically need the ":default" at the end of the service name. Example: svcadm enable svc:/network/rpc/bind Note: The files in /tmp directory will not be saved during the reboot process. If you feel you need to keep a copy of the files, move them to another location that is not volatile during a reboot. 10. Reboot the system by entering: /usr/sbin/shutdown -i6 -g0 -y Log into the system as root.
Note:
28
November 2009
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. This section includes the following topics:

Prerequisites on page 29 Upgrading CMS Supplemental Services on page 30 Removing CMS patches on page 32 Removing the current CMS load on page 33 Starting AOM on page 34 Installing the new CMS base load on page 35 Installing CMS patches on page 36 Turning on CMS on page 37 Starting Avaya OA data forwarders on page 38 Preparing the Avaya Visual Vectors Server software on page 38
Prerequisites

Read the information in Introduction on page 5 Perform all of the required procedures in Preparing for a base load upgrade on page 9 Perform all of the required procedures in Updating the Solaris operating system on page 23 Verify that you are logged in to the system as root.
November 2009
29
Upgrading CMS Supplemental Services

Do not perform this procedure if a Supplemental Services software disc was not shipped with your CMS upgrade. If a Supplemental Services software disc was not shipped with your CMS upgrade, continue with Removing CMS patches on page 32. To upgrade the CMS Supplemental Services software: 1. Obtain the CMS Supplemental Services software disc that was shipped with your CMS upgrade software. 2. Record the version number printed on the software disc, for use later in this procedure. 3. Load the software disc, CMS Supplemental Services into the disc drive. 4. Enter: pkgrm LUim The system displays the following message:
Do you want to remove this package?[y,n,?]
5. Enter: y The system removes the LUim package. 6. Enter: /usr/sbin/pkgadd -d /cdrom/cdrom0 LUim The system loads the new LUim package. 7. Enter: /opt/LUim/bin/install 2>&1|tee -a /opt/LUim.log 8. Perform one of the following actions:
If the system does not display a license agreement or questions for the SUNWexplo package, or if the system displays a message "CTEact already installed", go to Step 9. If the system does display a series of questions for the SUNWexplo package, install the package, and accept the default answers when provided. Prompts can be left blank if information is not available.
9. Enter: /opt/cc/install/ahl.cssrXXXX.X/bin/setup where XXXX.X is the version number on the CMS Supplemental Services software disc. The system displays one of the following messages:
30
November 2009
Upgrading CMS Supplemental Services
If no previous version is in place, the system displays a message similar to the following:
No previous version is in place. enable crontab entry... set up output log configuration... AHL setup completed successfully.
If a previous version is in place, the system displays a message similar to the following:
Migrating previous version ahl.cssrXXXX.X ............. ............. ............. AHL setup completed successfully.
10. Enter: /opt/cc/install/aot.cssrXXXX.X/bin/setup where XXXX.X is the version number on the CMS Supplemental Services software disc. The system displays one of the following messages:
If no previous version is in place, the system displays a message similar to the following:
No previous version is in place. copy previous log files... no log files exist for tag "LAN_Admin_Log" linking new version... registering server with Orbix daemon ............. ............. ............. [786: New Connection (cms3,IT_daemon,*,root,pid=645,optimised) ] AOM setup completed successfully.
If a previous version is in place, the system displays a message similar to the following: aot.cssrXXXX.X
Migrating previous version ............. ............. ............. linking new version...
November 2009
31
Removing CMS patches

1. Enter: cmssvc The system displays the CMSSVC Menu. 2. Enter the number associated with the back_all option. The system displays one of the following messages, depending on whether CMS patches are present:

If no patches are present, the system displays a No CMS patches message. If patches are present, the system displays the following message:
The following patches are installed on this machine: . . . Are you sure you wish to remove all these patches? (y|n)
Note:
Note: Some CMS patches might require additional steps for installation or removal. If additional steps are required, the system will display a message describing the steps you must perform. The patch installation or removal will fail until you perform the required steps. For example, a patch might require both CMS and IDS to be off. 3. Perform one of the following actions:

If no patches are present, go to Removing the current CMS load on page 33. If patches are present, enter: y
The system removes the patches. For each patch removed, the system displays messages similar to the following:
Removing patch package for cmspx-s: Patch x has been backed out.
When all patches have been removed, the system returns to the prompt.
32
November 2009
Removing the current CMS load
Removing the current CMS load

To remove the current CMS base package: 1. Load the Avaya Call Management System software disc into the disc drive. 2. Enter: pkgrm cms
The system checks the package and displays the following message:
The following package is currently installed: cms Avaya Call Management System (sparc) rxxxxx.x Do you want to remove this package?
3. Enter: y
Removing installed package instance <cms> . . . WARNING: This package contains scripts which will be executed with super-user permission during the process of removing the package. Do you want to continue with the removal of this package [y,n,?,q]
4. Enter: y The system displays the following message:

Removing installed package instance <cms> . . . WARNING: The <LUfaas> package depends on the package currently being removed. Dependency checking failed. Do you want to continue with the removal of this package [y,n,?,q]
Note:
Note: The <LUfaas> package message might not appear if Visual Vectors is not installed on the system.
November 2009
33
5. Enter:
The system displays the following message:

Verifying package dependencies. Processing package information. Executing preremove script Do you want to preserve CMS data [y,n,?]
6. Enter:

CMS will be removed from this machine; the data will be preserved. Are you sure this is correct [y,n,?]
7. Enter:

Have you backed up the file systems [y,n,?]
8. Enter:
If CMS has not been turned off, the system displays the following message:
CMS must be turned off in order to remove software. Do you want to turn off CMS now?
9. Enter:
The system removes the current CMS load and displays the following message:
Turning off CMS, please wait. ................. Removal of <cms> was successful.
Starting AOM
To start AOM, enter: aom start Note: If AOM was started automatically by the system, the system will display a message stating AOM is already on.
Note:
34
November 2009
Installing the new CMS base load
Installing the new CMS base load

To install the new CMS base load: 1. Verify the Avaya Call Management System software disc is in the disc drive. 2. Enter the following command to update the CMS related Informix files. /cdrom/cdrom0/update_ids 3. Enter: pkgadd -d /cdrom/cdrom0 cms
Note:
Note: It may be necessary to enter y several times to continue the CMS software installation. The system installs the CMS software and displays a message similar to the following:
Installing Avaya Call Management System as <cms> ...................... ...................... Background installation of performance packages complete. If CMS was installed by choosing CMS from pkgadd menu, type q and press return to exit. If CMS was installed using pkgadd -d /cdrom/cdrom0 cms, press return.
4. Press Enter. The system proceeds to install several CMS performance tool packages. When the installation is complete, the program once again displays the following message:
If CMS was installed by choosing CMS from pkgadd menu, type q and press return to exit. If CMS was installed using pkgadd -d /cdrom/cdrom0 cms, press return.
November 2009
35
Note:
Note: If the installation procedure fails for any of the performance tools, 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 message shown above is displayed, continue with this procedure and the remaining CMS base load upgrade procedures. When the upgrade is complete, notify your Avaya CMS support organization as prompted by the system. 5. Press the Enter key. The system returns to the command prompt. 6. The system prompts you to reboot the system. Enter: /usr/sbin/shutdown -i6 -g0 -y The system reboots. 7. Enter: pkgchk -n cms
If the software installation was successful, the system prompt returns to the screen after a few seconds. If you receive any error messages, call the Avaya Technical Services Organization, 1-800-242-2121, or your product distributor. 8. Enter: cat /cms/install/logdir/admin.log |pg The system displays part of the CMS administration log. 9. Verify that there were no errors during the installation. 10. Press Enter to continue the display. It might be necessary to repeat this step several times.
Installing CMS patches

To install the CMS patches: 1. Enter: cmssvc The system displays the CMSSVC Menu.
36
November 2009
Turning on CMS
2. Enter the number associated with the load_all option. Depending on the availability of CMS patches one of the following events occurs:
If there are no patches to be installed, the system displays a message to that effect and returns to the system prompt. If there are no patches to be installed, the system displays the following message:
Are you sure you want to install all these patches? (y|n)
Note:
Note: Some CMS patches might require additional steps for installation or removal. If additional steps are required, the system will display a message describing the steps you must perform. The patch installation or removal will fail until you perform the required steps. For example, a patch might require both CMS and IDS to be off. 3. Choose one of the following actions:

If there are no patches to be installed, continue with Turning on CMS on page 37. If there are patches to be installed, enter: y The system installs the CMS patches. As the installation proceeds, the system keeps you informed of its progress, as shown in the following message:
Generating list of files to be patched... . . . Patch installation completed.
Turning on CMS
To turn on CMS: 1. Enter: cmsadm The system displays the CMSADM Menu. 2. Enter the number associated with the run_cms option. The system displays the following message:
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):
November 2009
37
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.
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.
Preparing the Avaya Visual Vectors Server software

If you are not using Visual Vectors, go to Completing the base load upgrade process on page 41. Choose one of the following options:
If you are upgrading Visual Vectors from an earlier version, go to Removing the Avaya Visual Vectors Server software on page 38. If you are not upgrading Visual Vectors and if Visual Vectors is installed on the system, go to Turning on Avaya Visual Vectors on page 40.
Removing the Avaya Visual Vectors Server software

To remove the Avaya Visual Vectors Server software: 1. Verify the Avaya Call Management System software disc is in the disc drive. 2. Enter: pkgrm LUfaas For each package, the system will display at least two messages asking for confirmation to continue the removal.
38
November 2009
Preparing the Avaya Visual Vectors Server software
3. Enter y each time you receive messages asking for confirmation to continue the removal. When the last package is removed, the system returns to the command prompt. 4. Go to Installing the Avaya Visual Vectors Server software on page 39.
Installing the Avaya Visual Vectors Server software

To install or upgrade the Avaya Visual Vectors Server software: 1. Enter: aom stop 2. Verify the Avaya Call Management System software disc is in the disc drive. 3. Enter: pkgadd -d /cdrom/cdrom0 LUfaas The system displays the following message:
Processing package instance <LUfaas> from </cdrom/untitled> Visual Vectors Server Software (sparc) vvsXX.X ......... ......... ......... Do you want to continue with the installation of <LUfaas> [y,n,?]
Note:
Note: You might receive messages about installing conflicting files. Enter y to install the files and continue with the installation. 4. Enter: y The system displays the following message:
Installing Visual Vectors Server Software as <LUfaas> .......... .......... .......... Installation of <LUfaas> was successful.
5. Enter: aom start 6. Go to Turning on Avaya Visual Vectors on page 40.
November 2009
39
Turning on Avaya Visual Vectors

To turn on the Avaya Visual Vectors software: 1. Enter: setupaas The system displays the Avaya Visual Vectors Server System Services Menu. 2. Enter the number associated with the run_vvs option. 3. Enter the number associated with the Turn VVS On option. 4. Enter: eject cdrom 5. Verify that AOM is on. For more information, see Starting AOM on page 34 6. Go to Completing the base load upgrade process on page 41.
40
November 2009
Completing the base load upgrade process

You must perform the procedures in this section to complete the CMS base load upgrade process. This section includes the following procedures:

Prerequisites on page 41 Returning to the Common Desktop Environment on page 41 Performing a backup of the system files on page 42 Performing a backup of the CMS data on page 42
Prerequisites

Read the information in Introduction on page 5 Perform all of the required procedures in Preparing for a base load upgrade on page 9 Perform all of the required procedures in Updating the Solaris operating system on page 23 Perform all of the required procedures in Upgrading the CMS base load on page 29
Returning to the Common Desktop Environment

To return to the Common Desktop Environment (CDE) interface: 1. At the command prompt, enter: exit The system displays the following message:
console login:
November 2009
41
Completing the base load upgrade process
!
Important:
Important: Do not enter anything at the login prompt. After about 10 to 30 seconds, the system will return you to the CDE Login console.
2. Log in as root. The system displays the Common Desktop Environment, along with one or more open XTERM windows.
Performing a backup of the system files

After the base load upgrade has completed successfully, perform 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 system data on page 17.
Performing a backup of the CMS data

After the base load upgrade has completed successfully, perform 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 19.
42
November 2009

Avaya Call Management System: Release 16 Base Load Upgrade

Uploaded by

Copyright:

Available Formats

Avaya Call Management System: Release 16 Base Load Upgrade

Uploaded by

Document Information

Original Title

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 Call Management System: Release 16 Base Load Upgrade

Uploaded by

Copyright:

Available Formats

Avaya Call Management System

Release 16 Base Load Upgrade

Avaya CMS R16 Base Load Upgrade

Avaya CMS R16 Base Load Upgrade

Purpose of this document

Avaya CMS R16 Base Load Upgrade

When and how to use this document

Impacts to CMS service

CAUTION: This software upgrade is service affecting.

Avaya CMS R16 Base Load Upgrade

Contacting Avaya for assistance with your upgrade

Contacting Avaya for assistance with your upgrade

Possible customization impacts

Upgrade kit contents

Contacting Avaya technical support during the upgrade

Avaya CMS R16 Base Load Upgrade

Visual Vectors upgrades

Avaya CMS R16 Base Load Upgrade

Preparing for a base load upgrade

Avaya CMS R16 Base Load Upgrade

Preparing for a base load upgrade

Verifying the current CMS version and load

Verifying that your previous backups completed successfully

Verifying the backup of your CMS system data

Avaya CMS R16 Base Load Upgrade

Verifying that your previous backups completed successfully

Verifying that your last CMSADM backup completed successfully

3. Choose one of the following actions:

Avaya CMS R16 Base Load Upgrade

Preparing for a base load upgrade

===== LAN SYSTEM BACKUP SUCCESSFULLY FINISHED

Date and time

4. Choose one of the following actions:

Verifying the backup of your CMS data

Verifying that your previous full or incremental backup completed successfully

2. Enter: tail /cms/maint/backup/back.log

Avaya CMS R16 Base Load Upgrade

Verifying that the nightly archiver is functioning

4. Choose one of the following actions:

Date and time

4. Choose one of the following actions:

Verifying that the nightly archiver is functioning

Avaya CMS R16 Base Load Upgrade

Preparing for a base load upgrade

Checking the status of the disk drives

Avaya CMS R16 Base Load Upgrade

Checking for memory errors and system panics

Checking for memory errors and system panics

Avaya CMS R16 Base Load Upgrade

Preparing for a base load upgrade

Verifying free space in the root file system

2. Check the disk capacity. 3. Choose one of the following actions:

Rebooting your CMS system

Avaya CMS R16 Base Load Upgrade

Backing up the CMS system

Backing up the CMS system

Backing up your system data

Performing a CMSADM backup

Avaya CMS R16 Base Load Upgrade