 |
» |
|
|
|
If you are updating software on an existing HP-UX 10.20 system
you should begin the update procedure at this point. Otherwise, you should have installed the new SW-DIST
product first, as given in the previous sections in this chapter.
Then do the following to start swinstall: On Series 700, you will see a Graphical User Interface (GUI),
by default. On Series 800, you will see a character display Terminal
User Interface (TUI) on a console. You will have a GUI if you are
working from an Xterminal. Updating a Single System or Series 800 Server-Cluster | |
For a Series 800 serving Series 700 clients, or for a non-clustered
system, enter the Software Management area of SAM and select Install
Software to Cluster/Local Host. Or enter the following: You will see the swinstall
Specify Source screen in Figure 3-1 “Title not available (Updating a Cluster )”.
Skip to the section "Specify Source Screen".
Updating a Cluster | |
If you are updating Series 700 cluster clients or a Series
700 serving Series 700 clients, enter the Software Management area
of SAM and select Install Software to Cluster. Or you can use swcluster,
as follows: Enter the swcluster
command for interactive mode: (swcluster
will shut down the cluster clients if you are updating kernel software): You will see the swinstall
interface. The screens are similar to those used for the non-clustered
procedure below. Select the default shared root (/export/shared_roots/OS_700)
in the interactive window. Select the software source host and depot. Select software as desired, or Match what Target
Has from the Actions menu. Select Install/Analysis from the Actions menu. After the analysis phase finishes, select OK to
continue with the cluster install process.
For screen details see the non-clustered installation in the
next section. Installing or updating an operating system or kernel software
to a shared root shuts down any clients booted from that server
and reboots the server. If you are installing non-kernel applications
to a shared root, the clients will not be shut down and the server
will not be re-booted. When the server has rebooted and finished the startup process,
turn on the diskless clients. They will boot and configure the software. Note that, on a Series 800 server-cluster, this
process will only update the (Series 700) clients. Time Note If you are updating a large cluster, this process could take
several hours. Specify Source Screen Clicking on the field beside Source Depot Type displays a
choice of Local CDROM, Local Directory, Local Tape, or Network Directory/CDROM.
The latter category will get a remote source for the update. If the source depot/host name filled in is not the
one you want, enter the correct one. You may also use the IP address
for a host. If you click on Source Depot Path, you will get
a listing of available depots on the source you have just specified.
If the source is a tape device, you may need to type the device
file name. The mount point for a CD-ROM should already exist as
/SD_CDROM, if
the system was cold-installed. For more detail, see the man page
swreg(1m). If you wish to limit the listing, click on Software
Filter to see the list of filters protocols available. At the same
time, you can select one or none. Click on OK. You will next see the Software Selection screen.
For More Information For information on the options for swinstall,
and to change the degree of detail for its logging functions, see
the manual Managing HP-UX Software with SD-UX. Software Selection Screen On the Software Selection screen,
highlight an item and click on the Actions menu item Open Item to
see a listing of the contents of that bundle or product. You can
also successively double-click on the selected item to show the
contents at the next level of detail. To see a general description
of the selected software, click on Show Description of Software
from the Actions menu. Click on the OK button when you have finished
with the description screen. If you want to match the general filesets and functionality
you already have on your old system, choose Match What Target Has
... from the action menu, AND/OR To choose specific bundles/products to add to the
Match What Target Has ... selection, highlight the additional item,
and then choose Mark for Install from the Actions menu. (You can
also use the right mouse button to mark for install). To start the install process, choose Install (analysis)
... from the Actions menu. You will see the following screen (superimposed):
Install Analysis Screen By clicking on the Logfile button,
you can open the logfile to monitor the progress of the analysis.
You will also see a listing of files already on the target system
which will be reinstalled in new versions. The Disk space ... button
will become accessible after the analysis process is complete and
you can view the results (see Figure 3-4 “Title not available (Updating a Cluster )”).
Time Note The analysis phase requires 5 to 10 minutes. Disk Space Analysis Screen The Disk Space Analysis gives you an estimate of available
disk space vs. requirements for the new system. If disk space is a concern, you may want to look at graphics
and related products especially for possible deletion. For example,
in case you are running a Series 800 with a character terminal console,
you may not want to update graphics products. | | | |  | NOTE: If you are updating from an HP-VUE bundle to a CDE bundle,
the /usr file
system will undergo significant expansion. This expansion may exceed
the default file system size set by Cold Install for /usr.
See Chapter 5 “Troubleshooting Your Installation” for information
on resetting file system size. | | | | |
Ensure that the /var
"Available After" space is at least 20 MB. (The screen shown indicates
only about 6 MB, which is insufficient and would require deletion
of old log and
tmp files in
/var/adm and
/var/tmp.) Close the Disk Space confirmation window to see
the analysis window. When the disk analysis is satisfactory, choose OK
on the Install Analysis screen to proceed with the update. A confirmation screen will appear, to which you
can respond Yes or No as to whether you want to continue with the
installation. | | | | | NOTE: Note that, up to this time, you can "back out" of any
action by clicking on Cancel in order to return to previous screens,
for example, in order to adjust the selection of filesets being
updated. | | | | |
You will see a second confirmation screen warning
you that a new kernel will be loaded (in case you are updating HP-UX
or a kernel-related patch bundle), and this will necessitate a reboot.
Respond Yes, if you wish to go ahead. You will see an install status screen which monitors
the current progress of the installation, including the time remaining. If you want to keep track of the progress of messages
and scripts being run during the load, you can keep a logfile window
open during the process. Do this by clicking on the Logfile button,
on the status screen.
Time Note A typical HP-UX update, if done from
a network server, will require one to two hours. Systems with 16
MB of memory will require considerably longer. At the end of an HP-UX update, you will see a confirmation
message and reboot warning (with about 30 seconds delay until shut
down). As the system reboots for the first time, configure
scripts run for the new filesets so you can expect a first boot
time of several minutes. Subsequent reboot processes will not take
as long.
After Logging In The login screen appears after the system has rebooted. Log
in at this time. Check the following logfiles for any messages, including
warnings, relating to the update: /var/adm/sw/swinstall.log
/var/adm/sw/swagent.log |
| | | | | NOTE: For an OS update, you will also need to repeat the update
steps with the appropriate bundle on the HP-UX Extension Software
which came with your HP-UX media. This provides core-related patches
for the current version of HP-UX. (See “Using HP-UX Extension Software ”, in this chapter, and the patch descriptions
on the disc or tape.) The system will automatically reboot after
updating with this bundle. | | | | |
Updating a Patched SystemIf you are updating the OS of a previously-patched HP-UX 10.x
system, you will need to remove the old patches after installing.
Use the cleanup tool is available
to accomplish this selectively. If the cleanup tool is not available
on your new system via Extension Software, you can get it via the
patch PHCO_12140, available from your HP support service. If You are Updating from HP-VUE to CDE The HP-UX 10.20 CDE filesets do not contain updated versions
of SharedPrint or HP VUE files. Therefore, when updating from HP
VUE to CDE, the old versions of SharedPrint or VUE remain on the
system. As a result, you will see SharedPrint and VUE errors appearing
in the swagent.log,
and the swverify.log
(if swverify
has been run). These messages can be ignored, as no functional
problems are implied. The following filesets will produce these failed verify error
message: SharedPrint.SHP-ENG-A-MAN
SharedPrint.SHPRNT-CLI
SharedPrint.SHPRNT-PCL
SharedPrint.SHPRNT-SRV
VUE.VUE-RUN
VUE.VUE-HELP-INFO
VUE.VUE-MAN
VUE.VUE-RUN-AUX |
(Non-English systems will display the localized fileset names.) In addition, note that your 10.01 and 10.10 files will work
on HP-UX 10.20, as binary compatibility between versions has been
maintained. Using HP-UX Extension Software | |
For core-specific patches to HP-UX 10.20, you will have an
Extension Software CD-ROM containing Series 700 and Series 800 10.20
Patch Bundles. (If your system came with Instant Ignition (pre-loaded)
HP-UX, your Extension Software is on the disk and will load automatically.)
In the event that you need to apply core-specific patches to your
system, you will use the same SD update process with the Extension
Software as for other types of 10.x software. The Extension Software CD or tape depot directory looks similar
to the following. It will contain critical patches relating to the
10.20 core software only: |READMEFIRST
|
|READMES__________|PB_07_700_1020.lj
/SD_CDROM_________| |PB_07_800_1020.lj
|
|10.X_____________|s700_10.20
| |s800_10.20 |
The 10.20 bundles are contained in SD depots (the update format
used for HP-UX 10.x). In addition, these
will be identified for Series 800 (s800_10.20)
or Series 700 (s700_10.20). You should first identify the bundle
which is appropriate to your system(s). Specific documentation for each bundle (in LaserJet/PCL
format) is kept in the /SD_CDROM/READMES
directory. Before installing from a Patch Bundle, you can print
the appropriate Readme file for that bundle, using the lp -oraw
command. Use the install procedure given in this chapter
“Updating HP-UX Software ” to install the patch
bundle, Use swinstall
or swcluster,
as appropriate. Set Source Depot Path to /SD_CDROM/10.X/s700_10.20
or /SD_CDROM/10.X/s800_10.20. From the Actions menu, select Match What Target
Has. Perform installation analysis (Actions →
Install (analysis), if needed. If there are no errors, proceed with the installation
at the prompt message.
To get general information about patching your system,
see the following files in /usr/share/doc: Patch_pgm.txt
sw_patches.txt |
Adding Additional Functionality | |
In case you need to add more bundles for the new functionality
of HP-UX 10.20, such as JFS or NFSD filesets, use the "Match What
Target Has" option described in this chapter, and then select additional
bundles which you have purchased. If you need further details, see the manual Managing
HP-UX Software with SD-UX. Networking Products on Additional Media | |
If you are using certain networking products or
other Independent Software Units (ISUs) which are not present on
the core HP-UX CD or tape, then you may need to follow
modified update procedures. Some of the networking products affected
include FDDI, Token-Ring and 100VG AnyLan, which are provided on
the HP Applications
CD-ROM or tape. Since optional networking products are shipped on separate
media from the CORE
HP-UX, their drivers are removed from the kernel during the update
process. This means that if you update using the CORE
medium or a depot made from it, the optional networking
will not be available after reboot. If the networking which was removed provides access to the
remote SD depot or CD-ROM drive, then, after reboot, any swinstall
of applications, including networking will need to be performed
from a local CD-ROM drive or tape drive. An alternative is to use swcopy
to create a combined CORE
and Applications
depot and use that depot as your swinstall
source. Since a combined depot or tape contains the new revisions
of the networking products, their drivers will be reinstalled before
reboot and so the networking they provide will be available after
reboot. If you have a custom update tape provided as part of your
HP software support contract, then it is normally already combined
and you do not need to create a combined depot, as long as the update
tape, or any depot made from it, contains the HP-UX CORE
software and the optional networking software which you need. Installing the Optional OnlineJFS
Product | |
HP OnlineJFS is the advanced optional bundle for the VxFS
File System. You can use the capabilities of OnlineJFS to perform
certain key administrative tasks on mounted VxFS file systems. Because
you can perform these tasks on mounted file systems, users on the
system can continue to perform their work uninterrupted. These tasks include: Defragmenting a file system to regain
performance. Creating a snapshot file system for backup purposes.
You can install it with swinstall
in the following order: Install the JournalFS product, if it is not already installed. Install two HP OnlineJFS bundle filesets. (AdvJournalFS.VXFS-ADV-KRN
and AdvJournalFS.VXFS-ADV-RUN).
During the install, swinstall
will edit the /stand/system
file, rebuild the kernel, and reboot the system to bring the new
kernel libraries into memory. For more information about installing and using VxFS and HP
OnlineJFS, see the manual HP-UX System Administration
Tasks, Chapter 4. |
Printable version
