Avaya Comcode 700220627 manual Troubleshooting upgrade failures, Enter cd /adminsave/init.d

Page 65

Upgrading the system

Troubleshooting upgrade failures

If you receive an error message that one of the installation scripts failed when you run the cvue_activate command, you may be able to recover and continue with the upgrade. Some of the installation scripts can be skipped during this part of the upgrade. However, any script that is skipped during this part of the upgrade must be installed later using the standard software installation procedures found in the CMS software installation document.

The following table lists all of the possible software installation scripts, and explains what to do if one of them fails during the upgrade. When identifying the installation scripts, be aware that each script is numbered with a prefix (for example, S04) before the script name.

	Script name	Description		How to recover


	install_sql	ISQL software	All of these scripts install optional software or
			drivers needed by the customer. You can skip the
	x25_setup	Set up X.25
			script and reinstall the software later. To skip the

	install_nts	NTS drivers	script:
			1.	Enter: cd /adminsave/init.d
	install_hsip	HSI/P drivers
			2.	Enter: mv scriptname /adminsave/ where

	install_hsis	HSI/S drivers
			scriptname is the name of the script.
			3.	Enter: cd /cdrom/cdrom0
	install_saip	SAI/P drivers
			4.	Run the ./cvue_activate command again.

	install_saipu	SAI/P utilities
			5.	Install the software package that you skipped

	install_tokenring_s	Token Ring software	before you migrate the customer’s data.
			After each script is executed, a copy of the script is
	install_tokenring_p	Token Ring software
			moved to /adminsave/init.d.completed.

	install_odbcX_X	ODBC software

Issue 3.0 February 2002 65

Image 65

Contents TM leee 2002, Avaya Inc All Rights Reserved Preface Overview Disk upgrade procedures Preface Related documents Customer support for the United States Frequently asked questions FAQsTechnician support for the United States Customer and technician support outside the United StatesPage Upgrading an Enterprise 3000 to CMS R3V9 Hardware additions OverviewTrouble escalation Disk mirroring Customization issuesParts list Procedures that are done by the customer before the upgrade Doing a Cmsadm backup Cleaning the tape driveDetermining the current CMS load Enter pkginfo -x cmsCmsadm backup for R3V6 and earlier Upgrading an Enterprise 3000 to CMS R3V9 Procedures that are done by the customer before the upgrade Upgrading an Enterprise 3000 to CMS R3V9 Cmsadm backup for R3V8 Upgrading an Enterprise 3000 to CMS R3V9 Procedures that are done by the customer before the upgrade Backing up Visual Vectors vector layouts and comments Indicates the first noncompressing tape drive with Doing a full maintenance backup System displays the following for R3V8 Field Value to enter or option to select Doing an incremental maintenance backup System displays the following for R3V8 Checking for printer requests and large mail files Cmsadm Checking for nonsequential ACDsCollecting third-party and custom software Upgrading the system Extracting the customer’s administration and options Tail -f /var/tmp/new/var/log/cvuelog CvueextractUpgrading an Enterprise 3000 to CMS R3V9 Has Isql been purchased for this upgrade y or n? Isql will not be installed as part of upgrade Upgrading the system Usr/sbin/shutdown -y -i0 -g0 Pg /var/tmp/new/var/log/cvuelogRemoving and replacing Enterprise 3000 disk drives Disk upgrade proceduresOverview Removing and labeling the old disk drivesE3000removedisk.cdr Boot disk Drive Boot Disk Slot Installing the new disk drivesBooting up the system with the new disk drives Checking the status of the disk drives Verifying that the system recognizes the new disk drivesOpt/informix/bin/setenv Onstat -d egrep X pgLs -x /dev/rmt Checking the status of the tape drivesVerifying that the upgrade can continue Overview Eject cdrom Installing CMS patchesContinue with Copying customer data Cvuecopy Copying customer dataCd /cdrom/cdrom0 Activating customer optionsCvueactivate Tail -f /var/log/cvuelogUpgrading the system Ls -l /adminsave/init.d Continue with Shutting down and rebooting the system Shutting down and rebooting the systemRemoving temporary ACDs Verifying the status of the disksVerifying CMS permissions Pkgchk -n cmsSu cms Turning on CMSVerifying that CMS is operating Checking Free Space Allocation Nohup ./verifyfileproperties /nohup.out Comparing directory and file permissionsVerifyfileproperties Setting the Informix configuration parameters Updating the switch setupCvuecleanup Removing the upgrade filesMigrating the customer’s data Migrating system administration dataDevice name Tape drive device name Data Type Pg /cms/migrate/r3mig.log Migrating agent and call center administration dataAgent/Call Center Admin data Onstat -d egrep Pdrx pg Checking the status of the disksReplacing the customer’s tapes Enter cd /adminsave/init.d Troubleshooting upgrade failuresEnter mv scriptname /adminsave/ where Enter cd /cdrom/cdrom0Checks for devices Adddisks Adds nonboot disks Procedures that are done by the customer after the upgrade Migrating historical data 1159 PM Mt -f /dev/rmt/0 status mt -f /dev/rmt/1 status Restoring non-CMS filesR3V6 and earlier R3V8 Feature or service Responsible Installing and administering unpreserved softwareDoing a Cmsadm backup CMS administration data