Avaya Comcode 700220627 manual Booting up the system with the new disk drives

Page 42

Upgrading an Enterprise 3000 to CMS R3V9

Booting up the system with the new disk drives

Note:

When the upgrade is being supported by remote personnel, such as CMS Provisioning, the system commands in this section are for use by remote personnel to monitor the progress of the upgrade. Run the commands from the local console only when instructed to do so, or when there is no remote support.

To boot up the system with the new disk drives:

1.Turn on all external SCSI devices, starting with the device farthest from the system and working toward the system.

2.Turn on the system monitor.

3.Turn on the system. Return the key switch to the position that was used by the customer before the upgrade was started.

4.Close the front door of the system.

The system begins to boot up. If the boot fails, turn off the power to the computer and check all device cabling. Cycle power on all external devices.

The power LEDs on the SCSI drives will light. Note that during boot-up, you might see error messages concerning hardware for which software is not yet installed. This will be corrected later in the upgrade procedure when the customer’s options are installed.

5.After the system reboots, log in as root.

6.If prompted for a password, press Enter. (At this point in the upgrade, there is no password.)

7.If using the CMS console on site, open an XTERM window if one is not displayed. Move the cursor into the window and click the left mouse button to activate that window.

8.Continue with Verifying that the system recognizes the new disk drives on page 43.

42 CentreVu CMS R3V9 Sun Enterprise 3000 Computer CVUE Instructions

Image 42

Contents TM leee 2002, Avaya Inc All Rights Reserved Preface Overview Disk upgrade procedures Preface Related documents Technician support for the United States Frequently asked questions FAQsCustomer support for the United States Customer and technician support outside the United StatesPage Upgrading an Enterprise 3000 to CMS R3V9 Overview Trouble escalationHardware additions Customization issues Disk mirroringParts list Procedures that are done by the customer before the upgrade Determining the current CMS load Cleaning the tape driveDoing a Cmsadm backup 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 Checking for nonsequential ACDs Collecting third-party and custom softwareCmsadm Upgrading the system Extracting the customer’s administration and options Cvueextract Tail -f /var/tmp/new/var/log/cvuelogUpgrading 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 Pg /var/tmp/new/var/log/cvuelog Usr/sbin/shutdown -y -i0 -g0Overview Disk upgrade proceduresRemoving and replacing Enterprise 3000 disk drives Removing and labeling the old disk drivesE3000removedisk.cdr Installing the new disk drives Boot disk Drive Boot Disk SlotBooting up the system with the new disk drives Opt/informix/bin/setenv Verifying that the system recognizes the new disk drivesChecking the status of the disk drives Onstat -d egrep X pgChecking the status of the tape drives Ls -x /dev/rmtVerifying that the upgrade can continue Overview Installing CMS patches Eject cdromContinue with Copying customer data Copying customer data CvuecopyCvueactivate Activating customer optionsCd /cdrom/cdrom0 Tail -f /var/log/cvuelogUpgrading the system Ls -l /adminsave/init.d Shutting down and rebooting the system Continue with Shutting down and rebooting the systemVerifying CMS permissions Verifying the status of the disksRemoving temporary ACDs Pkgchk -n cmsTurning on CMS Verifying that CMS is operatingSu cms Checking Free Space Allocation Comparing directory and file permissions VerifyfilepropertiesNohup ./verifyfileproperties /nohup.out Updating the switch setup Setting the Informix configuration parametersRemoving the upgrade files CvuecleanupMigrating system administration data Migrating the customer’s dataDevice name Tape drive device name Data Type Migrating agent and call center administration data Pg /cms/migrate/r3mig.logAgent/Call Center Admin data Checking the status of the disks Replacing the customer’s tapesOnstat -d egrep Pdrx pg Enter mv scriptname /adminsave/ where Troubleshooting upgrade failuresEnter cd /adminsave/init.d 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 Restoring non-CMS files R3V6 and earlierMt -f /dev/rmt/0 status mt -f /dev/rmt/1 status R3V8 Installing and administering unpreserved software Feature or service ResponsibleDoing a Cmsadm backup CMS administration data