Solaris Patch Installation HP−UX Patch Installation

Since the analysis is completed, select OK. Start the installation, select YES. Follow the procedure, select Logfile. Since the installation was completed, select OK and then DONE. Exit swinstall and dismount CD umount SD_CDROM 5.

26.3.2 Patches

26.3.2.1 Solaris Patch Installation

Download needed patches and put in the patches directory mkdir patches ftp HOST where HOST is machine with patches, or obtain from sunsolve.sun.com, or sunsolve1.sun.com 1. Ftp−ed files are of the form: PatchID.tar.Z, where PatchID corresponds to the listed files. Once patches are downloaded uncompress them: cd patches uncompress 2. Untar each patch: tar −xvf PatchID.tar The corresponding subdirectories with needed files are created. 3. Continue with individual patch installation. A few examples of individual patch installations follow: OS Patches cd patches2.6_Recommended . install_cluster Are you ready to continue with install? [yn]: y Volume Manager cd patches105463–04 patchadd. Flashprom Patches updates: cd patches103346–11 . flash−update−11 Do you wish to flash update your firmware? y[n] : y Are you sure you wish to continue? y[n] : y halt ok setenv auto−boot? false Power−cycle machine ok power−off 4. 677 ok setenv auto−boot? true Optionally remove downloaded patches: rm −R patches 5.

26.3.2.2 HP−UX Patch Installation

Three different installation procedures are presented, for a single patch, multiple patches, and a set of patches provided on CD. HP−UX Individual Patches Download individual patches from the HP Web site: http:us−support.external.hp.com. You can register at any time as a new user you must be registered to use the site. Alternatively, patches could be ftp−ed from the HP ftp site: i3107ffs.external.hp.comhp−ux_patchess80010.X ♦ To ftp, follow the procedure: mkdir tmpPATCHES cd tmpPATCHES ftp HP_ftp_site_name cd hp−ux_patchess80010.X ls get whatever_patch_name Select and download a patch. 1. Become root at the target HP−UX host. 2. Copy a patch for example: PHKL_xxxxx to the temporary directory for example: tmpPATCHES if not already there. 3. Change the directory and unshar the patch: cd tmpPATCHES sh PHKL_xxxxx Two files will be created: PHKL_xxxxx.depot and PHKL_xxxxx.text You can read the text file to learn more about the patch including how to install it. 4. Run swinstall to install the patch: swinstall −x autoreboot = true −x match_target = true \ −s tmpPATCHESPHKL_xxxxx.depot The selected patch will be installed. If the installation requests rebooting it will be automatically done option autoreboot = true. 5. To check if the patch is installed: If the patch was installed individually: swlist | grep PHKL_xxxxx a. If the patch was installed within a fileset: swlist −l fileset | grep PHKL_xxxxx b. 6. 678 what standvmunix | grep PHKL_xxxxx ◊ c. HP−UX Multiple Patches — For multiple individual patches, creating a single jumbo patch to be installed at once is recommended. A sequential installation of multiple patches sometimes does not work because of existing dependencies among the patches. This example describes how to create a single jumbo patch that includes multiple patches, to be installed at one time. Make a list of required patches. For example a new model of 19 GB disk, unknown at the time of the OS installation, has to be added to the system. The list of required patches is information could be obtained from HP−UX Technical Support Center, Web site, or other: Status Catalog Text Nine Patches PHCO_16591 fsck_vxfs1M cumulative patch PHKL_16751 SIG_IGNSIGCLD,LVM,JFS,PCISCSI cumulative patch PHKL_16957 Physical dump devices configuration patch PHKL_17858 Fix for mountaccess of disc sections PHKL_18522 LOFS cumulative patch PHCO_18563 LVM commands cumulative patch PHKL_19159 Correct process hangs on ufs inodes PHKL_19540 VxFS JFS mount,fsck cumulative changes PHNE_19936 cumulative ARPA Transport patch 1. Be sure to have all of the required patches unsharred and in one directory; for example source is the path to patches, and target is the new depot do not mkdir. swcopy −x enforce_dependencies=false −s source \ target Here is an example, assuming the.depot files are in the tmp dir: swcopy −x enforce_dependencies=false −s tmpPHKL_16751.depot \ tmphp_patch You must run this command for each patch. 2. When you are done, start the swinstall menu: swinstall −s tmphp_patch Select options and make sure that the top five options are checked marked: select all the patches mark for install install analysis 3. HP−UX Set of Patches on CD Insert CD HP−UX Recommended Patches Extension Software last available version. Log in as root and mount the CD: mount devdskc2t2d0 SD_CDROM 1. Enter swinstall, to start swinstall menu−driven utility: 2. 679 none Select OK. Select ActionMatch What Target Has and follow messages. 3. Select ActionInstall analysisand follow instructions to complete: Selectenterread Logfile. Since the analysis was completed, select OK to start installation; it takes about one hour. Selectenterread Logfile. Since the installation was completed, select DONE. At the end, the system would be rebooted. 4. Log in as root and mount CD: mount devdskc2t2d0 SD_CDROM 5. Enter swinstall to start swinstall menu−driven utility. The screen: Specify Source Source depot type: Local CDROM Source host name: scarlet Source depot path: SD_CDROM10.x80010.20 XSW800GR1020 Software filter: none Select OK. 6. Select ActionMatch What Target Has and follow messages. 7. Select ActionInstall analysisand follow instructions to complete: Selectenterread Logfile. Since the analysis was completed, select OK to install; it takes about one hour. Selectenterread Logfile. Since the installation was completed, select DONE. At the end, the system would be rebooted. 8. 680

Chapter 27: Upgrade Disk Space

27.1 Adding a Disk

Adding a disk is a routine task, and to accomplish this task, the procedure specific to the particular UNIX flavor must be fully respected and followed. To add a new disk does not mean simply to connect a disk — there are several more steps that must be accomplished: To partition a disk, and prepare one or more independent disk partitions • To create a filesystem, and make disk partitions available for data storage • To mount created filesystem, and make accessible for data storage • If logical volume manager LVM is used, a few more steps are required before a filesystem creation, to create a logical volume for further processing.

27.1.1 New Disk on the Solaris Platform

Solaris 2.x as well as the earlier Sun Microsystems UNIX version, SunOS 4.1.x provides the disk utility format to partition a disk. Once it is invoked from the command line by typing format, an interactive, menu−driven, user−friendly program offers a number of useful disk−related commands. At the very start, all attached and detected disks are displayed. Solaris requires the system to be rebooted with the −r option for new disk disks to be detected. Solaris does not check the system for new hardware every time it is booted; hardware checking takes additional time, so normally it is assumed there are no changes in the system hardware configuration. In the rare situations when the system is being upgraded, Solaris needs an explicit action by the administrator: reboot −− −r or halt OK boot −r The OK prompt specifies the system monitor mode the low−level system ROM resident program that enables a number of monitoring functions, primarily checking the hardware and booting the system. It is actually recommended to first check that the disk is connected properly: OK probe−scsi ..... ..... And then boot the system: OK boot −r Assuming everything is done properly, the system should recognize and display the new disk as well as the preexisting disks. Since a new disk was selected, the FORMAT MENU is displayed: FORMAT MENU: disk − select a disk type − select define a disk type partition − select define a partition table current − describe the current disk 681