BaseLoad.book

8/12/2019 BaseLoad.book

1/42

Avaya Call Management SystemRelease 16

Base Load Upgrade

November 2009


2/42

2009 Avaya Inc. All Rights Reserved.

Notice

While reasonable efforts were made to ensure that the information in thisdocument was complete and accurate at the time of printing, Avaya Inc. canassume no liability for any errors. Changes and corrections to the informationin this document might be incorporated in future releases.

Documentation disclaimer

Avaya Inc. is not responsible for any modifications, additions, or deletions tothe original published version of this documentation unless such modifications,additions, or deletions were performed by Avaya. Customer and/or End Useragree to indemnify and hold harmless Avaya, Avaya's agents, servants andemployees against all claims, lawsuits, demands and judgments arising out of,

or in connection with, subsequent modifications, additions or deletions to thisdocumentation 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 Websites referenced elsewhere within this documentation, and Avaya does notnecessarily endorse the products, services, or information described or offeredwithin them. We cannot guarantee that these links will work all the time and wehave no control over the availability of the linked pages.

Warranty

Avaya Inc. provides a limited warranty on this product. Refer to your salesagreement to establish the terms of the limited warranty. In addition, Avayasstandard warranty language, as well as information regarding support for thisproduct, while under warranty, is available through the Avaya Support Website:

http://www.avaya.com/support

License

USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER'SACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERALLICENSE TERMS AVAILABLE ON THE AVAYA WEB SITEhttp://www.avaya.com/support/LicenseInfo("GENERAL LICENSE TERMS").IF YOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUSTRETURN 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 typesdescribed below. The applicable number of licenses and units of capacity forwhich the license is granted will be one (1), unless a different number oflicenses or units of capacity is specified in the Documentation or othermaterials available to End User. "Designated Processor" means a singlestand-alone computing device. "Server" means a Designated Processor thathosts a software application to be accessed by multiple users. "Software"means the computer programs in object code, originally licensed by Avaya andultimately utilized by End User, whether as stand-alone Products orpre-installed on Hardware. "Hardware" means the standard hardwareProducts, originally sold by Avaya and ultimately utilized by End User.

License type(s)Designated System(s) License (DS).End User may install and use eachcopy of the Software on only one Designated Processor, unless a differentnumber of Designated Processors is indicated in the Documentation or othermaterials available to End User. Avaya may require the DesignatedProcessor(s) to be identified by type, serial number, feature key, location orother specific designation, or to be provided by End User to Avaya throughelectronic means established by Avaya specifically for this purpose.

Concurrent User License (CU).End User may install and use the Software onmultiple Designated Processors or one or more Servers, so long as only thelicensed number of Units are accessing and using the Software at any giventime. A "Unit" means the unit on which Avaya, at its sole discretion, bases thepricing of its licenses and can be, without limitation, an agent, port or user, ane-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 administrativedatabase utilized by the Product that permits one user to interface with theSoftware. Units may be linked to a specific, identified Server.

Copyright

Except where expressly stated otherwise, the Product is protected by copyrightand other laws respecting proprietary rights. Unauthorized reproduction,transfer, and or use can be a criminal, as well as a civil, offense under theapplicable law.

Third-party components

Certain software programs or portions thereof included in the Product maycontain software distributed under third party agreements ("Third PartyComponents"), which may contain terms that expand or limit rights to usecertain portions of the Product ("Third Party Terms"). Information identifyingThird Party Components and the Third Party Terms that apply to them isavailable on the Avaya Support Web site:

http://www.avaya.com/support/ThirdPartyLicense

Preventing tol l fraud

"Toll fraud" is the unauthorized use of your telecommunications system by anunauthorized party (for example, a person who is not a corporate employee,agent, subcontractor, or is not working on your company's behalf). Be awarethat there can be a risk of toll fraud associated with your system and that, if tollfraud occurs, it can result in substantial additional charges for yourtelecommunications services.

Avaya f raud int erven tion

If you suspect that you are being victimized by toll fraud and you need technicalassistance or support, call Technical Service Center Toll Fraud InterventionHotline at +1-800-643-2353 for the United States and Canada. For additionalsupport telephone numbers, see the Avaya Support Web site:


Trademarks

Avaya and the Avaya logo are either registered trademarks or trademarks ofAvaya 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 Website:


Avaya supp ort

Avaya provides a telephone number for you to use to report problems or to askquestions about your product. The support telephone numberis 1-800-242-2121 in the United States. For additional support telephonenumbers, see the Avaya Support Web site:

http://www.avaya.com/supporthttp://www.avaya.com/support/LicenseInfohttp://www.avaya.com/support/ThirdPartyLicensehttp://www.avaya.com/supporthttp://www.avaya.com/support/http://www.avaya.com/support/http://www.avaya.com/support/http://www.avaya.com/support/ThirdPartyLicensehttp://www.avaya.com/support/LicenseInfohttp://www.avaya.com/support/http://www.avaya.com/supporthttp://www.avaya.com/support


3/42

Avaya CMS R16 Base Load Upgrade November 2009 3

Introduct ion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Purpose of thi s document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

When and how to use this document . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Impacts to CMS service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Contacting Avaya for assistance with your upgrade . . . . . . . . . . . . . . . . . . . 7

Possible cus tomization impacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Upgrade ki t contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Contacting Avaya technical support during the upgrade . . . . . . . . . . . . . . . . . 7

Visual Vectors upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Preparing for a base load upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Prerequisi tes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Verifying the current CMS vers ion and load . . . . . . . . . . . . . . . . . . . . . . . . 10

Verifying that your previous backups completed successful ly . . . . . . . . . . . . . 10

Verify ing the backup of your CMS system data . . . . . . . . . . . . . . . . . . . . 10Verifying that your last CMSADM backup completed successfu lly . . . . . . . 11

Verifying that your last LAN backup of the system data completed successful ly 11

Verify ing the backup of your CMS data . . . . . . . . . . . . . . . . . . . . . . . . 12

Verifying that your previous full or incremental backup completed successful ly 12

Verifying that your last LAN backup of CMS data completed successfully . . . 13

Verifying that the nightly archiver is func tion ing . . . . . . . . . . . . . . . . . . . . . 13

Checking the status of the disk drives . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Checking for memory errors and system panics . . . . . . . . . . . . . . . . . . . . . 15

Verifying free space in the root fi le system . . . . . . . . . . . . . . . . . . . . . . . . 16

Reboot ing your CMS sys tem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Backing up the CMS system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Backing up your system data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Performing a CMSADM backup . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Performing a full system backup with LAN backup . . . . . . . . . . . . . . . . 18

Backing up your CMS data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Performing a full data backup with a tape device . . . . . . . . . . . . . . . . . 19

Performing a full data backup with LAN backup . . . . . . . . . . . . . . . . . 20

Backing up any new CMS data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Updating the Solaris operat ing system . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Prerequisi tes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Stopping the Avaya Visual Vectors server software. . . . . . . . . . . . . . . . . . . . 24

Stopping AOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Contents


4/42

Contents

4 Avaya CMS R16 Base Load Upgrade November 2009

Stopping Avaya OA data forwarders . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Install ing Solaris patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Install ing the Avaya CMS security scr ipt . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Upgrading the CMS base load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Prerequisi tes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Upgrading CMS Supplemental Services . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Removing CMS patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Removing the cur rent CMS load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Starting AOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Install ing the new CMS base load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Install ing CMS patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Turning on CMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Starting Avaya OA data forwarders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Preparing the Avaya Visual Vectors Server software . . . . . . . . . . . . . . . . . . . 38Removing the Avaya Visual Vectors Server software. . . . . . . . . . . . . . . . . 38

Installing the Avaya Visual Vectors Server sof tware . . . . . . . . . . . . . . . . . 39

Turning on Avaya Visual Vectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Completing the base load upgrade process . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Prerequisi tes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Returning to the Common Desktop Environment . . . . . . . . . . . . . . . . . . . . . 41

Performing a backup of the system fi les . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Performing a backup of the CMS data . . . . . . . . . . . . . . . . . . . . . . . . . . . 42


5/42


Introduction

This Avaya Call Management System (CMS) base load upgrade is designed to be installed byAvaya 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 AvayaCMS R16 issues.

Avaya recommends that you load this upgrade as soon as possible. If you ask our TechnicalSupport Organization to troubleshoot your Avaya product, they will require you to use the latestsoftware 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) baseload upgrade process for R16xx.x. This Avaya CMS base load upgrade is designed to beinstalled by Avaya CMS customers who either have had problems with an earlier version of theproduct or would like access to any new features added in the maintenance release. Thisupgrade provides all known software fixes from previous versions. The software is acquired byordering the latest PCN. The PCN provides a list of all fixes and features added in themaintenance 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. Verifythat you are using the proper base load upgrade document for your release ofCMS.


6/42

Introduction


When and how to use this document

Use this document to upgrade Avaya Call Management System (CMS) from an older CMSRelease 16 (R16) base load to a newer CMS R16 load. Unless indicated otherwise, all

procedures in theAvaya CMS Release 16 Base Load Upgradedocument are required.

Avaya recommends that:

Before performing the upgrade, you read through this entire document so that you arefamiliar 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 yourupgrade 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 enterthe command from the UNIX prompt in a terminal window. Press the Enterkey after youhave typed in the command. Use the same capitalization and spacing shown in thisdocument.

If you encounter problems or have questions during the upgrade, contact Avaya technicalsupport.

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 CMSsoftware. 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 thelongest amount of time to complete.


7/42

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. Thisremote 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 at1-800-242-2121.

Possible customization impacts

The software upgrade that you are installing could potentially impact system customization thatwas 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 systemcustomizations might be impacted by this upgrade. Schedule this evaluation at least two weeksbefore your upgrade. Charges, which will be quoted, vary for this service. Contact Avaya CRMat 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 toprovide the number of the Quality Protection Plan you are using.


8/42

Introduction


Visual Vectors upgrades

If you are upgrading the Visual Vectors software to Visual Vectors 16, which is compatible withCMS 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.


9/42


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 orsoftware problems before the upgrade. If you do not perform these procedures, your base loadupgrade could fail, and your CMS system could be put in a non-functioning state for some time.


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. Avayarecommends you review this file for any changes that might impact the procedures in thisdocument.

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


10/42



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, forexample:

3. Record the displayed CMS version information for reference later, during the upgradeprocess.

CMS version: _______________________________

Verifying that your previous backups completed

successfully

Approximately two days before the CMS base load upgrade, verify that your backups havebeen completing successfully.


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 followingprocedures:

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 performthe backups in conjunction with this base load upgrade.

cms Avaya Cal l Management Syst em( spar c) xxxxx.x


11/42

Verifying that your previous backups completed successfully


If you use the CMS LAN backup feature, go to Verifying that your last LAN backup of thesystem data completed successfully on page 11

You are responsible for backing up your CMS system. Avaya is not responsible forperforming LAN backups. For more information about the CMS LAN backup feature, seeAvaya Call Management System Release 16 LAN Backup User Guide. This documentprovides: information about using the CMS LAN backup feature, hardware requirements,software requirements, and support guidelines.

Verifying that your last CMSADM backup completed successful ly

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:

3. Choose one of the following actions:

If your previous backup was successful, go to Verifying the backup of your CMSdata on page 12.

If your previous backup was notsuccessful, contact your Avaya CMS supportrepresentative.

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 Enterto continue the display. It might be necessary to repeat this step severaltimes.

===== Begi n backup Wed Apr 9 05: 37: 05 EDT 2009

Convert er st ar t ed Wed Apr 9 05: 37: 07 EDT 2009Conver t er compl et ed successf ul l y Wed Apr 9 05: 37: 10 EDT 2009

Test i ng t ape on / dev/ r mt / 0. . .

Tape t est on / dev/ r mt / 0 i s okay. . .

2873600 bl ocks

===== Fi ni shed backup Wed Apr 9 06: 30: 35 EDT 2009


12/42



3. Verify that the previous system backup completed successfully.

An example of a successful system backup message is:


If your previous backup was successful, go to Verifying the backup of your CMSdata on page 12.


Verifying the backup of your CMS data

To verify that your previous system backup completed successfully, choose one of the followingprocedures:

If you backup your data directly to a tape device, go to Verifying that your previous full orincremental backup completed successfully on page 12.

If you use the CMS LAN backup feature, go to Verifying that your last LAN backup of CMSdata completed successfully on page 13

For more information about the CMS LAN backup feature, seeAvaya Call ManagementSystem Release 16 LAN Backup User Guide. This document provides: information aboutusing the CMS LAN backup feature, hardware requirements, software requirements, andsupport guidelines.

Verifying that your previous ful l 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

===== LAN SYSTEM BACKUP SUCCESSFULLY FI NI SHED Date and time


13/42

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:


If your previous backup was successful go to Verifying that the nightly archiver isfunctioning on page 13.


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


3. Verify that the previous data backup completed successfully.

An example of a successful data backup message is:


If your previous backup was successful, go to Verifying that the nightly archiver isfunctioning on page 13.


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.

1711 4/ 15/ 09 2: 14 AM 2 1 I NFOBACKUP I NFO: The backup has compl et ed success f ul l y.Pl ease l abel t he vol ume CMS- 030415- 01- LSAC- 00- F- 01- r 3mi l cms

+++++ ON- Bar BACKUP SUCCESSFULLY FI NI SHED Date and time


14/42



2. Enter:

su cms cms

The system displays the CMS main menu.

3. Press Enterto accept the default terminal type.

4. Select Mai nt enance> Err or Log Report .5. Enter 2600in the Er r or codes field.

6. Leave all of the other fields blank.

7. Press Enterto select the Runoption.

8. Press Enter.

The system displays an archive history report.

9. Verify that the nightly archiver is functioning correctly for all ACDs administered on thesystem.

An example of a successful nightly archiver message is:

10. Select Exi t to return to the previous menu.


If the nightly archiver is functioning correctly, go to Checking the status of the diskdrives on page 14.

If the nightly archiver is notfunctioning 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" | pg3. The output will look similar to the following:

2600 4/ 15/ 09 2: 15 AM 2 1 I NFOARCHI VER st atus: Dai l y Ar chi ve f or ( Mon)Apr. 14, 2009 Successf ul

Logi cal devi ces/ Fai l ed/ Degr aded : 1/ 0/ 0


15/42

Checking for memory errors and system panics


If the output shows zero for Failed or Degraded, continue with Checking for memory errorsand system panics on page 15

If the output shows anything other than zero for Failed and Degraded, your systemrequires 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:Note: It might be necessary to press Enterto continue the display.

An example of some memory error messages are:

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 spacein the root file system on page 16.

If the system displays any memory error or panic messages, your system requiresmaintenance. Contact your Avaya CMS support representative.

/ var / adm/ messages: Apr 15 21: 27: 51 r 3upct n SUNW, Ul t r aSPARC- I I : [ I D 860344 kern. not i ce][ AFT0] er r I D 0x00011903. 9c12748f Corr ect ed Memory Err or on Boar d 3 J 3600 i s Per si st ent/ var / adm/ messages: Apr 16 09: 27: 52 r 3upct n SUNW, Ul t r aSPARC- I I : [ I D 417990 kern. not i ce][ AFT0] Cor r ect ed Memory Er r or on CPU7, er r I D 0x00014050. 8646ccd6/ var / adm/ messages: Apr 16 09: 27: 52 r 3upct n AFSR 0x00000000. 00100000 AFAR0x00000000. 09498550/ var / adm/ messages: Apr 16 09: 27: 52 r 3upct n AFSR. PSYND 0x0000( Score 05) AFSR. ETS 0x00Faul t _PC 0x10023bd0/ var / adm/ messages: Apr 16 09: 27: 52 r 3upct n SUNW, Ul t r aSPARC- I I : [ I D 136280 kern. not i ce][ AFT0] er r I D 0x00014050. 8646ccd6 Corr ect ed Memory Err or on Boar d 3 J 3600 i s Per si st ent/ var / adm/ messages: Apr 16 21: 27: 51 r 3upct n SUNW, Ul t r aSPARC- I I : [ I D 488351 kern. not i ce]

[ AFT0] Cor r ect ed Memory Err or on CPU6, er r I D 0x0001679c. f 8a4aa5f/ var / adm/ messages: Apr 16 21: 27: 51 r 3upct n AFSR 0x00000000. 00100000 AFAR0x00000000. 09498550/ var / adm/ messages: Apr 16 21: 27: 51 r 3upct n AFSR. PSYND 0x0000( Score 05) AFSR. ETS 0x00Faul t _PC 0x10023bd0/ var / adm/ messages: Apr 16 21: 27: 51 r 3upct n SUNW, Ul t r aSPARC- I I : [ I D 599456 kern. not i ce][ AFT0] er r I D 0x0001679c. f 8a4aa5f Corr ect ed Memory Er r or on Boar d 3 J 3600 i s Persi st ent/ var / adm/ messages: Apr 17 09: 27: 51 r 3upct n SUNW, Ul t r aSPARC- I I : [ I D 473191 kern. not i ce][ AFT0] Cor r ect ed Memory Er r or on CPU6, er r I D 0x00018ee9. a6074f b3


16/42



Verifying free space in the root f ile system

To verify that sufficient free space is available in your root file system to accomplish the baseload upgrade:

1. Enter:

df -k /

The system displays a message similar to the following:

2. Check the disk capacity.


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 theCMS 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.



If the system does not boot correctly or if any error messages are displayed, contactyour Avaya CMS support representative.

If the system boots correctly, go to Backing up the CMS system on page 17.

Fi l esyst em kbytes used avai l capaci t y Mount ed on

/ dev/ dsk/ c1t 0d0s0 6201485 1738401 4401070 29% /


17/42

Backing up the CMS system



Before beginning a CMS base load upgrade, you must backup your CMS system data and CMSdata.


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 onpage 17.

If you use the CMS LAN backup feature, go to Performing a full system backup with LANbackup on page 18


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 thetape cartridges look alike, and using the wrong tape can damage the tape drivemechanism and tape heads.

2. Log in as root.

3. Enter:

cmsadmThe Avaya Cal l Management Syst emAdmi ni st r at i on Menu (CMSADM Menu) isdisplayed.


18/42



4. Enter the number associated with the backup option.

Depending on the number of tape drives connected to your system, one of the followingmessages will be displayed by your system.

If only one tape drive is available, the system displays the following message:

If more than one tape drive is available for use, the system displays a list of tapedevices. Enter a tape drive selection from the displayed list.

An example of a tape device list is:

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/ r mt / 0.

5. Press Enter.

The backup process is initiated.

When the backup is complete, the system displays the following message:

6. Write protect the tape and store the tape in a secure location until the next backup isperformed.

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.

Pl ease i nser t t he f i r st car t r i dge t ape i nt o device name.Press ENTER when r eady or Del t o qui t :

Sel ect t he t ape dr i ve: 1) HP DAT- 72 t ape dr i ve: / dev/ r mt / 0 2) HP DAT- 72 t ape dr i ve: / dev/ r mt / 1Ent er choi ce ( 1- 2) :

xxxxxxx bl ocksTape Ver i f i cat i onxxxxxxx bl ocksWARNI NG: A CMS Ful l Mai ntenance Backup i n addi t i on t o t hi s cmsadm

backup must be done t o have a compl et e backup of t he syst em. . .. .

Pl ease l abel t he backup t ape(s) wi t h the date and t he cur r ent CMSver si on (xxxxx.x)


19/42



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 upgradeis 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 atape device on page 19.

If you use the CMS LAN backup feature, go to Performing a full data backup with LANbackup on page 20.


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 thetape cartridges look alike, and using the wrong tape can damage the tape drivemechanism and tape heads.



20/42



3. From the main menu, select Mai nt enance> Back Up Dat a.

The system displays the Back Up Dat a window, as shown below. Do not change any ofthe default selections.

4. Press Enterto access the action list in the upper right corner of the window.

5. Select Run and pressEnter.

6. Wait for the backup to complete. If the backup does not complete successfully, contactyour 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:


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.


21/42



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 Updatingthe Solaris operating system on page 23.

If new CMS data has been generated since your last CMS data backup, perform one of thefollowing 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 SystemRelease 16 LAN Backup User Guide. This document provides information about using the CMSLAN backup feature, hardware requirements, software requirements, and support guidelines.


22/42




23/42


Updating the Solaris operating system

This section contains procedures for updating your Solaris operating system. You mustcomplete the procedures in this section before upgrading your CMS base load.



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



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 r oot .


24/42



Stopping the Avaya Visual Vectors server software

To stop the Avaya Visual Vectors server software:

1. Enter:

setupaas

The system displays the Avaya Vi sual Vect or s Ser ver Syst em Ser vi cesMenu, as shown in the following figure.

2. Enter the number associated with the r un_vvs option.

The system displays the following message:

3. Enter the number associated with theTurn VVS Of foption.

Stopping AOM

To stop AOM, enter:

aom stop

Avaya Vi sual Vectors Server Syst emServi ces Menu

Sel ect a command f r omt he l i st bel ow.

1) i ni t _vvs Set up t he i ni t i al conf i gurati on2) r un_vvs Tur n VVS on or of f3) aut h_di spl ay Di spl ay si mul t aneous VVS l ogi ns4) aut h_set Change si mul t aneous VVS l ogi ns5) backup Backup vect or st eps and l ayout f i l es6) r est or e Rest or e vect or st eps and l ayout f i l es

Ent er choi ce ( 1- 6) or q t o qui t :

1) Turn VVS On2) Turn VVS Of f

Ent er choi ce ( 1- 2) or q t o qui t :


25/42

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 forwarderson the CMS server using thepa stop allcommand. For more information about Avaya OA

forwarders, seeAvaya 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 Cal l Management Syst em Ser vi ces Menu(CMSSVC Menu).

CAUTION:!

CAUTION: CMS must be off in order to install the Solaris patches.

3. Enter the number associated with the r un_cms option.

4. Enter the number associated with theTurn of f CMS but l eave I DS r unni ngoption.

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:


26/42



If there are Solaris patches to install, the system displays the following message:

! Important:Important: The message will contain an estimate of the amount of time needed to install the

Solaris patches.

If there are noSolaris patches to install, the system displays the following message:

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. TheSolaris patch installation takes at least the amount of time that was estimated earlier in theprocedure. After the Solaris patches are installed, the system reboots into multiuser modeand displays a login prompt.

CAUTION:!

CAUTION: If you cancel the installation of Solaris patches, must install them beforeupgrading CMS. To cancel installation of the Solaris patches, enter: n


12. Verify that all of the Solaris patches have been installed by entering:

tail -10 /var/cms/spatches/spatches.log


Warni ng: you must cl ose al l appl i cat i ons bef or e r unni ng t hi s scr i pt. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .Sol ari s patches have been spool ed t o your machi ne. The patches wi l l

be i nst al l ed af t er r eboot i ng. Dur i ng t he i nst al l at i on of pat chesyourser ver wi l l not be avai l abl e.

The est i mat ed t i me t o i nst al l al l patches i s: 15 minutes

Ready to i nst al l Pat ches. Pl ease l eave t he CD i n t he dr i ve.You wi l l need t o r eboot t he ser ver f or patches t o i nst al l .

Do you want t o r eboot now? [ y, n, ?]

There ar e no Sol ar i s patches t o i nst al l

Al l pat ches i nst al l ed successf ul l y.


27/42

Installing the Avaya CMS security scrip t


Note:Note: If the installation procedure fails for any of the patches, the following message is

displayed:

If the message shown above is displayed, continue with this procedure and theremaining 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_idsoption.

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 rootafter you run the Avaya CMS

security script. If you are logging into the system remotely, you will need to log inas 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 thelisting after the security script run.

I nst al l at i on f ai l ed f or one or mor e Sol ar i s pat ches.

- Cust omers i n the US shoul d cal l t he CMS Techni cal Servi cesOr gani zat i on at 1- 800- 242- 2121

- Cust omers outsi de t he US shoul d contact your Avayarepresent at i ve or di st ri but or .Pat ch i nstal l at i on compl eted: Fr i J an 18 13: 28: 19 MST 2009


28/42



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. Thesystem displays the following message when the process is complete:

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 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:Note: The files in /tmpdirectory 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 notvolatile during a reboot.

10. Reboot the system by entering:

/usr/sbin/shutdown -i6 -g0 -y

Log into the system as root.

Avaya CMS secur i t y conf i gur at i on compl et ed: date


29/42


Upgrading the CMS base load

You must complete the procedures in the previous sections before upgrading your CMS baseload. Use the procedures in this section to upgrade an older CMS base load to a newer CMSbase load.



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

PrerequisitesBefore you perform the procedures in this section, you must:



Perform all of the required procedures in Updating the Solaris operating system onpage 23

Verify that you are logged in to the system as r oot .


30/42



Upgrading CMS Supplemental Services

Do not perform this procedure if a Supplemental Services software disc was notshipped withyour 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 CMSupgrade 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


5. Enter: y

The system removes the LUimpackage.

6. Enter:

/usr/sbin/pkgadd -d /cdrom/cdrom0 LUim

The system loads the new LUimpackage.

7. Enter:

/opt/LUim/bin/install 2>&1|tee -a /opt/LUim.log

8. Perform one of the following actions:

If the system does notdisplay a license agreement or questions for the SUNWexplopackage, or if the system displays a message "CTEact al r eady i nst al l ed", go toStep 9.

If the system does display a series of questions for the SUNWexplo package, installthe package, and accept the default answers when provided. Prompts can be leftblank if information is not available.

9. Enter:

/opt/cc/install/ahl.cssrXXXX.X/bin/setup

where XXXX.Xis the version number on the CMS Supplemental Servicessoftware disc.


Do you want t o r emove t hi s package?[ y, n, ?]


31/42

Upgrading CMS Supplemental Services


If no previous version is in place, the system displays a message similar to thefollowing:

If a previous version is in place, the system displays a message similar to thefollowing:

10. Enter:

/opt/cc/install/aot.cssrXXXX.X/bin/setup

where XXXX.Xis the version number on the CMS Supplemental Servicessoftware disc.


If no previous version is in place, the system displays a message similar to thefollowing:

If a previous version is in place, the system displays a message similar to thefollowing:

No previous version is in place.

enable crontab entry...

set up output log configuration...

AHL set up compl eted successf ul l y.

Mi gr ati ng pr evi ous ver si on ahl.cssrXXXX.X. . . . . . . . . . . . .. . . . . . . . . . . . .. . . . . . . . . . . . .AHL set up compl eted successf ul l y.

No pr evi ous ver si on i s i n pl ace.copy pr evi ous l og f i l es. . .no l og f i l es exi st f or t ag "LAN_Admi n_Log"l i nki ng new ver si on. . .r egi st eri ng server wi t h Or bi x daemon

. . . . . . . . . . . . .. . . . . . . . . . . . .

. . . . . . . . . . . . .[ 786: New Connect i on ( cms3, I T_daemon, *, r oot , pi d=645, opt i mi sed) ]

AOM set up compl eted successf ul l y.

Migrating previous version aot.cssrXXXX.X. . . . . . . . . . . . .. . . . . . . . . . . . .

. . . . . . . . . . . . .l i nki ng new ver si on. . .


32/42



Removing CMS patches

1. Enter:

cmssvc

The system displays the CMSSVC Menu.

2. Enter the number associated with the back_al l option.

The system displays one of the following messages, depending on whether CMS patchesare present:

If no patches are present, the system displays a No CMS pat ches message.

If patches are present, the system displays the following message:

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 thesteps you must perform. The patch installation or removal will fail until youperform the required steps. For example, a patch might require both CMS andIDS 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 displaysmessages similar to the following:

When all patches have been removed, the system returns to the prompt.

The f ol l owi ng patches are i nst al l ed on t hi s machi ne:.

..Ar e you sure you wi sh to remove al l t hese patches? ( y| n)

Removi ng patch package f or cmspx- s:

Pat ch x has been backed out .


33/42

Removing the cur rent 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:

3. Enter:y

4. Enter:y


Note:Note: The package message might not appear if Visual Vectors is not

installed on the system.

The f ol l owi ng package i s cur r ent l y i nst al l ed: cms AvayaCal l Management Syst em( spar c) r xxxxx. xDo you want t o r emove thi s package?

Removi ng i nst al l ed package i nst ance . . .WARNI NG: Thi s package cont ai ns scr i pts whi ch wi l l be executed wi t hsuper- user permi ssi on duri ng t he pr ocess of r emovi ng t he package.

Do you want t o cont i nue wi t h the r emoval of t hi s package [y, n, ?, q]

Removi ng i nst al l ed package i nst ance . . .

WARNI NG:The package depends on t he package cur r ent l y bei ngr emoved.

Dependency checki ng f ai l ed.

Do you want t o cont i nue wi t h the r emoval of t hi s package [y, n, ?, q]


34/42



5. Enter: y


6. Enter: y


7. Enter: y


8. Enter: y

If CMS has not been turned off, the system displays the following message:

9. Enter: y

The system removes the current CMS load and displays the following message:

Starting AOM

To start AOM, enter:

aom start

Note:Note: If AOM was started automatically by the system, the system will display a

message stating AOM is already on.

Ver i f yi ng package dependenci es.Processi ng package i nf ormat i on.Execut i ng pr eremove scr i pt

Do you want t o pr eser ve CMS dat a [ y, n, ?]

CMS wi l l be removed f r omt hi s machi ne; t he data wi l l be pr eser ved.Ar e you sure t hi s i s cor r ect [ y, n, ?]

Have you backed up t he f i l e syst ems [ y, n, ?]

CMS must be t urned of f i n order t o r emove sof t ware.

Do you want t o t urn of f CMS now?

Turni ng of f CMS, pl ease wai t .. . . . . . . . . . . . . . . . .Removal of was successf ul .


35/42

Installing the new CMS base load


Installing the new CMS base load

To install the new CMS base load:


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 yseveral times to continue the CMS software

installation.

The system installs the CMS software and displays a message similar to the following:

4. PressEnter.

The system proceeds to install several CMS performance tool packages. When theinstallation is complete, the program once again displays the following message:

I nst al l i ng Avaya Cal l Management Syst em as . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . .Backgr ound i nst al l at i on of perf ormance packages compl ete.

I f CMS was i nst al l ed by choosi ng CMS f r ompkgadd menu, t ype q andpr ess ret ur n t o exi t .

If CMS was installed using pkgadd -d /cdrom/cdrom0 cms, press

return.

I f CMS was i nst al l ed by choosi ng CMS f r ompkgadd menu, t ype q andpr ess ret ur n t o exi t .If CMS was installed using pkgadd -d /cdrom/cdrom0 cms, press

return.


36/42



Note:Note: If the installation procedure fails for any of the performance tools, the system

displays the following message:

If the message shown above is displayed, continue with this procedure and theremaining CMS base load upgrade procedures. When the upgrade is complete,notify your Avaya CMS support organization as prompted by the system.

5. Press theEnter key.

The system returns to the command prompt.

6. The system prompts you to reboot the system. Enter:

/usr/sbin/shutdown -i6 -g0 -yThe system reboots.

7. Enter:

pkgchk -n cms

If the software installation was successful, the system prompt returns to the screen after afew seconds. If you receive any error messages, call the Avaya Technical ServicesOrganization, 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.


Installing CMS patches

To install the CMS patches:1. Enter:

cmssvc

The system displays the CMSSVC Menu.

- Cust omers i n the US shoul d cal l t he CMS Techni cal Servi cesOr gani zat i on at 1- 800- 242- 2121

- Cust omers outsi de t he US shoul d contact your Avayarepresent at i ve or di st ri but or .


37/42

Turning on CMS


2. Enter the number associated with the l oad_al l 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 effectand returns to the system prompt.

If there are no patches to be installed, the system displays the following message:

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 thesteps you must perform. The patch installation or removal will fail until youperform the required steps. For example, a patch might require both CMS andIDS to be off.


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 keepsyou informed of its progress, as shown in the following message:

Turning on CMS

To turn on CMS:

1. Enter:

cmsadm

The system displays the CMSADM Menu.

2. Enter the number associated with the r un_cms option.


Ar e you sur e you want t o i nst al l al l t hese pat ches? ( y| n)

Gener at i ng l i st of f i l es t o be pat ched. . .. . .

Pat ch i nst al l at i on compl et ed.

Sel ect one of t he f ol l owi ng 1) Tur n on CMS 2) Turn of f CMS but l eave I DS Runni ng 3) Tur n of f CMSEnt er choi ce ( 1- 3) :


38/42



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 theupgrade.

5. Manually run the appropriate Archiver from System Setup if CMS was off during the timeyour Archiver normally runs.

Starting Avaya OA data forwarders

If the CMS configuration includes data collection by Avaya OA, turn on all Avaya OA forwarderson the CMS server using thepa start allcommand. For more information about Avaya OAforwarders, seeAvaya 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 onpage 41.

Choose one of the following options:

If you are upgrading Visual Vectors from an earlier version, go to Removing the AvayaVisual Vectors Server software on page 38.

If you are not upgrading Visual Vectors and if Visual Vectors is installed on the system, goto Turning on Avaya Visual Vectors on page 40.

Removing the Avaya Visual Vectors Server software

To remove the Avaya Visual Vectors Server software:


2. Enter:

pkgrm LUfaasFor each package, the system will display at least two messages asking for confirmation tocontinue the removal.


39/42

Preparing the Avaya Visual Vectors Server software


3. Enter yeach 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


3. Enter:

pkgadd -d /cdrom/cdrom0 LUfaas


Note:Note: You might receive messages about installing conflicting files. Enter yto install the

files and continue with the installation.

4. Enter:y


5. Enter:

aom start

6. Go to Turning on Avaya Visual Vectors on page 40.

Processi ng package i nstance f r om

Vi sual Vect ors Server Sof t war e( spar c) vvsXX.X

. . . . . . . . .

. . . . . . . . .

. . . . . . . . .

Do you want t o cont i nue wi t h the i nst al l ati on of [ y, n, ?]

I nst al l i ng Vi sual Vect or s Ser ver Sof t ware as

. . . . . . . . . .

. . . . . . . . . .

. . . . . . . . . .

I nst al l ati on of was successf ul .


40/42



Turning on Avaya Visual Vectors

To turn on the Avaya Visual Vectors software:

1. Enter:

setupaas

The system displays the Avaya Vi sual Vect ors Ser ver Syst emSer vi ces Menu.

2. Enter the number associated with the r un_vvs option.

3. Enter the number associated with the Tur n 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.


41/42


Completing the base load upgrade process

You must perform the procedures in this section to complete the CMS base load upgradeprocess.

This section includes the following procedures:


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




Perform all of the required procedures in Updating the Solaris operating system onpage 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


consol e l ogi n:


42/42

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 openXTERM windows.

Performing a backup of the system files

After the base load upgrade has completed successfully, perform a backup to create a reliablecopy of the computer system files. For instructions on how to backup the system files, seeBacking 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 reliablecopy of the computer CMS data files. For instructions on how to backup the CMS data, seeBacking up your CMS data on page 19.

Documents

BaseLoad.book