 |
» |
|
|
|
See the section, “Updating to HP-UX 11.0”
in this chapter, for specific information about transitioning to
HP-UX 11.0. You should have installed the new SW-DIST
product first, as given in the previous sections in this chapter. On HP 9000 Workstations, you will see a Graphical User Interface
(GUI), by default, for interactive invocation of swinstall.
On HP 9000 Servers, 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 HP-UX on a Stand-Alone System | |
To invoke swinstall, do one
of the following: | | | |  | CAUTION: Updating an HP 9000 Server to HP-UX 11.0 will stop
the Server from interacting with clients and may jeopardize data.
Before attempting such an update you should uncluster (backup and
unmount) clients. | | | | |
Options for 11.0 TransitionUse a command-line invocation, if you are transitioning to
HP-UX 11.0. You must use -x options
specifying the target system word-width and OS version, for either
an interactive or non-interactive SD-UX session. To specify an OS for the update, the following options are
used: using the following syntax: swinstall -x os_name=<OS>:<width> -x os_release=<release> |
The value <OS> specifies the
name of the OS, such as HP-UX. The value <width>
specifies the word-width in bits for the OS to be installed, such
as 32 or 64.
The <OS> and <width>values
must be separated by a colon (:). The value <release>
can include the following: In addition to the size/version options, updatingbetween 11.0 word-widths requires the following options
to swinstall: Interactive Command-Line ExampleFor example, for an interactive update from 10.x
to B.11.00 (32-bit), you would enter the following: swinstall -x os_name=HP-UX:32 -x os_release=B.11.00 |
Non-interactive Command Line (match_target)Non-interactive updates to 11.0 require
additional options, including specification of match_target and
autoreboot. (For cold-installing
non-interactively, see the instructions for using the Go!
action in “Executing the Installation: Go! ”, in Chapter 5 “Installing from the Ignite-UX Server”) The details are
given in “Updating Non-Interactively from Media
or Network ”. Updating to HP-UX 11.0 | |
Before Updating or Installing to HP-UX 11.0 64-bit
VersionIf
you are planning to update a system to HP-UX 11.0 64-bit, you need
to determine if your system can support the 64-bit version of the
operating system. To do this you need determine the following: Does your system hardware support
64-bit operation? Is the firmware installed in your system recent
enough for 64-bit 11.0?
Firmware Revisions Needed for HP-UX 11.0 64-bit OperationBefore installing or updating your HP 9000 Server to HP-UX
11.0 64-bit, you must determine that your system's Processor
Dependent Code (PDC or firmware) version supports 64-bit
operation. This section describes how to determine the version of firmware
operating on your server, and the minimum version of firmware required. Note the following precautionsIf you are patching a 10.x system having previous patches,
in order to remove all prior patch information from the IPD prior
to updating to HP-UX 11.0, see the procedure toward the end of this
manual: “Section 8: Loading HP-UX Patches Using
Ignite-UX”, in Appendix C “Ignite-UX System Administration” Note that you are not required to update
firmware on any HP 9000 Server on which you will only install or
update to HP-UX 11.0 32-bit version. However, it is always advisable
to have the most current firmware revisions installed. The revisions
of firmware that support 64-bit operation will also support 32-bit
operation. You may wish to confirm with your HP Support Representative
that you have current firmware revisions installed. Verifying Hardware Support and Firmware RevisionThe
following table lists all the HP 9000 servers that support 64-bit
operation, along with the minimum required firmware revision levels. Table 2-1 Supported
Hardware and Firmware for 11.0 64-bit Operation | Server model | HP-UX Version Supported | Minimum PDC Revision | Minimum Firmware Revision |
|---|
| 9000/802/K250 | 32 and 64-bit | 36 | 37.40 | | 9000/879/K260 | 32 and 64-bit | 36 | 37.40 | | 9000/879/K260-EG | 32 and 64-bit | 36 | 37.40 | | 9000/898/K370 | 32 and 64-bit | 8 | 37.23 | | 9000/800/K380 | 32 and 64-bit | 8 | 37.23 | | 9000/804/K450 | 32 and 64-bit | 36 | 37.40 | | 9000/889/K460 | 32 and 64-bit | 36 | 37.40 | | 9000/889/K460-EG | 32 and 64-bit | 36 | 37.40 | | 9000/889/K460-XP | 32 and 64-bit | 36 | 37.40 | | 9000/899/K570 | 32 and 64-bit | 8 | 37.23 | | 9000/800/K580 | 32 and 64-bit | 8 | 37.23 | | 9000/893/T600 | 32 and 64-bit | J537 | | 9000/800/V2200 | 64 bit only | All are 64-bit capable. | | 9000/800/V2250 | 64-bit only | All are 64-bit capable. |
There are different methods of determining your system's
firmware revision, depending upon its system class. Using the command
getconf HW_CPU_SUPP_BITS will indicate
your system's bit compatibility. The sections that follow
detail the procedures for K-class, T-class, and V-class servers. Determining the Firmware Revision of
K-Class
ServersTo determine the firmware revision on HP 9000 K-class servers,
perform the following steps. Determine which model of K-class you have
by entering: You will see a string similar to the following: Compare the model string to the listing in the table of supported
64-bit systems. | | | | | CAUTION: If the model number does not appear in the table
of supported 64-bit systems, do not attempt
to install or update to HP-UX 11.0 64-bit, because you risk rendering
your system unusable. Instead, install or update to HP-UX 11.0 32-bit
operation. | | | | |
If the model number does appear in the
table of supported 64-bit systems, go to the next step to determine
if your system's firmware revision supports 64-bit operation. There are two methods for determining your system firmware
revision level on K-class servers. These are described in Step
2 and Step 3. The easiest way to determine the system's firmware
(PDC) revision level is to run the Support Tools Manager (STM).
STM is provided on the HP-UX Support Disc, which is packaged with
HP-UX. Support Tools Manager can be run as a character-based (cstm),
menu-driven (mstm), or X-Windows
(xstm) application. If you do not have Support Tools Manager loaded on your system, Insert the Support
Disc in the CD-ROM and mount the CD-ROM read-only. For example, mount -r /dev/dsk/c0t2d0 /SD_CDROM |
If you do not know the device special file name of the CD-ROM,
you can find out by using ioscan
(with options -kfnC disk) or SAM
(Peripheral Devices -> Device List;
select the device, then use the Actions
pulldown and choose Show Device Files). List the contents of the DIAGNOSTICS
directory on the Support Disc, using swlist.
For example, swlist -d -l bundle @ /SD_CDROM/DIAGNOSTICS Find the OnlineDiag bundle
appropriate to your system. Use swinstall to
load the OnlineDiag bundle. For details on SD-UX procedures, refer to Managing
HP-UX Software with SD-UX.
Execute the Support Tools Manager, to determine the firmware
(PDC) revision loaded in your CPU. | | | |  | NOTE: On a multiprocessor system, you need to determine the
firmware revision for only one CPU. The firmware installed applies
to all processors. | | | | |
The following procedure demonstrates use of the Support Tools
Manager, using mstm to determine
the firmware revision level: At an HP-UX prompt, type mstm
to start the application. Once you press F2 (OK)
after reading the licensing statement, mstm
returns an ioscan-like map of the
system hardware. Scroll to a CPU entry and locate the cursor on
that line. For example, the line might read: 32 CPU Information Successful Press space bar to select the line. Press F5 for tools. Press F2 for info. Press F2 for run.
(While the program is executing, the word run is replaced by asterisks.)
When the program completes, the CPU line will read Information Successful. Press F3, labeled info log,
to create the Information Tool Log of the selected CPU. Examine the Information Tool Log and look for the PDC (firmware)
revision level. For example, the line might read: PDC Firmware Revision: 37.31 Compare the firmware revision level against the
information shown in Table 2-1 “Supported
Hardware and Firmware for 11.0 64-bit Operation” If the firmware installed on your
server matches or exceeds the firmware revision listed, you may
proceed to install HP-UX 11.0 for 64-bit operation. If your HP 9000 Server does not
have installed the necessary revision of firmware, you must contact
your HP Support Representative to get your firmware updatedbefore attempting to install or update to HP-UX 11.0
64-bit version.
| | | | | CAUTION: If you try to update a system lacking the correct
level of firmware, you risk putting the system into an unusable
state. | | | | |
If you have not installed the Support
Tools Manager (STM) on your system, then you will need to shutdown
and reboot your system to check the PDC subsystem and determine
the firmware revision. (If you have completed Step 2, you do not
need to perform this step). Read through the following procedure
before starting. Execute the shutdown
command to shutdown and reboot the system. Processing messages will be displayed, ending with
a message like the following: FINAL System shutdown message from root@gsysem14 |
System going down IMMEDIATELY |
System shutdown time has arrived |
sync'ing disks (37 buffers to flush): 37 10 |
Closing open logical volumes... |
Watch the console. You will see either a boot prompt or a
message indicating that the system will autoboot
in 10 seconds unless you press a key. If you see the 10 second
message, press a key to get the boot prompt. (If you do not press a key in time, do not worry. Just wait
until the system finishes booting and then repeat the shutdown/reboot
procedure.) Next you will see the Main menu. At the Enter Command or Menu
prompt, enter: Main menu: Enter command or menu > in fv |
You will see a message similar to the following: To display the chip revision, enter: Main menu: Enter command or menu > in cr |
You will see a message listing modules and revisions for the
system. Look for the module named PDC. For example,
Determining the Firmware Revision on
T-Class
ServersTo determine the firmware revision on HP 9000 T-class servers,
perform the following steps. At the system console, type CONTROL-B
to engage the PDC console interface. | | | | | NOTE: If the console does not respond to the CONTROL-B,
make sure the system console interface is enabled by checking the
setting of the console
key on the main system front panel.
It must be set to the unlocked position (padlock with open bar)
to access the PDC interface. | | | | |
To connect to the Service Processor, enter: You see a message similar to the following: Connecting to Service Processor. (APMSG 10) |
To display the firmware revision at the SP>
prompt, enter You'll see a display showing that the T-class has
two PDC banks. For example, Active Firmware Versions: |
SP Bank 0: SP 2.02, PSCM 1.60, Compiled 06/24/97 19:08 UT |
Alternate Firmware Versions: |
SP Bank 1: SP 2.00, PSCM 1.60, Compiled 03/21/97 21:45 UT |
The critical piece of information is the PDC Bank
of the active Firmware Version. (In this
example, the information is J537.)
For detailed information on what firmware or hardware is needed
to update your system to HP-UX 11.0 64-bit version, see the document
Readme Before Installing or Updating to HP-UX 11.0,
the Release Notes for HP-UX 11.0 , or check
with your HP field engineer. Updating to HP-UX 11.0 32-bit VersionIf you are updating your system to HP-UX 11.0 32-bit version,
no hardware or firmware updates are required, but note the caution
below. When you update a system to 11.0 32-bit version, you have
the following choices: If you are updating a system running
HP-UX 10.01, 10.10, or 10.20, you can update directly to HP-UX 11.0
32-bit version. If you are upgrading a system running HP-UX 9.04,
first upgrade to HP-UX 10.01, and then update to HP-UX 11.0 32-bit
version.
Updating to HP-UX 11.0 64-bit VersionWhen you update a system to 11.0 64-bit version, you have
the following choices: If you are updating a system running
HP-UX 10.20, and it is 64-bit capable (PA8000 and 64-bit compatible
firmware), you can update directly to the HP-UX 11.0 64-bit version. If you are updating a system running HP-UX 10.01
or 10.10, you must first update to HP-UX 10.20, make the appropriate
hardware and firmware upgrades, and then update to the HP-UX 11.0
64-bit version. If you are upgrading a system running HP-UX 9.04,
first upgrade to HP-UX 10.01, then update to 10.20, make the appropriate
hardware and firmware upgrades, and then update to the HP-UX 11.0
64-bit version.
Transitions within HP-UX 11.0, between 32-bit and
64-bit, are also possible. Example of Update Path to 11.0 64-bit (K220 System):For example, suppose you are running HP-UX 10.01 on a K220
system (PA7200), which does not support 64-bit, and you want to
update to a K260 system (PA8000), which does support 64-bit, in
order to update to HP-UX 11.0 64-bit. You would perform the following
steps: Update HP-UX 10.01 to 10.20. (The 10.20
update is needed to support the hardware upgrade in step 2.) Upgrade K220 to K260 hardware. Upgrade the firmware on the K260 (if not done in
step 2). Update HP-UX 10.20 to HP-UX 11.0 64- bit.
Example of Update Path 11.0 64-bit (K460 System)For example, suppose you are running HP-UX 10.20 on a K460
system (PA8000, which does support 64-bits), and you want to update
to HP-UX 11.0 64-bit. You would perform the following steps: Upgrade firmware on K460 (if
not already compatible). Update HP-UX 10.20 directly to HP-UX 11.0 64-bit
version.
Transitioning Between VersionsOnce HP-UX 11.0 is running on your system, you can transition
between the 32-bit and 64-bit versions of the operating system.
If you are updating from HP-UX 11.0 32-bit to HP-UX 11.0 64-bit,
the transition should be straightforward. However, before switching
from HP-UX 11.0 64-bit to HP-UX 11.0 32-bit, you will need to ensure
that all applications can accommodate the change. If any 64-bit
applications have written binary data files (for example, 64-bit
ELF executables), there may compatibility issues when you switch
back to the 32-bit version of the operating system. See the HP-UX 11.0 Release Notes and
the Application Interoperability White Paper
for more information. Updating Interactively from the GUI | |
After invoking swinstall
from the command line for an interactive update (for example: swinstall -x os_name=HP-UX:32 -x os_release=B.11.0),
you will see the following screen: Specify Source ScreenClicking 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. Alternatively, you may 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.
Select the correct depot. 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 filter protocols available. Click on OK. You will see the Software Selection screen next.
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
and the man page for swinstall(1M). 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. Alternatively,
you can successively double-click on the selected item to show the
contents at the next level of detail. The subproduct/fileset level of the Software Selection screen
now also has an architecture column and filters for hardware compatibility
(as has always been done at the bundle and product levels). 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. A log file is available from the Analysis
screen. 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.
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. This screen may
be saved or printed under the menu options File
--> Print 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 an HP 9000 server 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 7 “Troubleshooting ” 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 3.7 MB "Available After", 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: 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. At the end of an HP-UX update, press Done
and 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, the new
filesets are being configured. You can, therefore, 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 log files 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 install 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). The system
will automatically reboot after updating with this bundle. | | | | |
Migrating to CDE:The
first time you log in after completing an update from an HP VUE
environment to a CDE environment, a VUEtoCDE
migration dialog will pop up. You may want to migrate VUE customizations
to CDE using this utility. | | | | | NOTE: If you choose to migrate customizations, complete
the VUEtoCDE migration before
uninstalling VUE. In any case, you will need to run the Uninstall HP VUE
action from the System_Admin folder in the application manager.
Failure to run Uninstall HP VUE could result
in swverify warnings for VUE, CDE,
ImagingSubsystem, ScreenCapture, AudioSubsystem, SharedPrint, and
DigitalVideo products. | | | | |
If you are updating from HP-UX 10.20, there will be swverify
warnings regarding the group and ownership of /etc/dt,
/etc/dt/config, and /etc/dt/config/Xsession.d.
You can disregard these warning messages. Updating Non-Interactively from Media
or Network | |
For a generic, single-media update where no "customizing"
is required, you will be using the swinstall
tool non-interactively. You can use a general instruction to "match
what the target has" in order to load the updated versions of the
same filesets as you have on your current system. If you are using an external CD-ROM, ensure that the drive
is turned onand mounted. Insert the medium
in the drive. At a shell prompt, enter the following: swinstall -x match_target=true \ |
-x os_name=HP-UX:32 \ Needed for OS upsdate to 11.0 |
-x os_release=B.11.00 \ Needed for OS upsdate to 11.0 |
If you do not use match_target=true
you can specify the bundle names after the -s device_file
option, as, for example, HPUXEng32RT. Specify the device_file for your
CD-ROM drive, or network source. For example /SD_CDROM/c1t2d0
or simila r, for a CD-ROM |
hostname:/depot_path
for network sources |
You will see warning messages in case filesets are found on
the target system that are not on the source.
In the example, you would change HP-UX:32
to HP-UX:64, if you are installing
64-bit. For 32 --> 64 bit and 64 --> 32 bit transitions,
do the following: Use swinstall as
in the example, except that you would also use the following options:
|
Printable version
