 |
» |
|
|
|
|
|
Updating to HP-UX 11i v3 is a simple upgrade if your environment is completely current – but let’s get real! Your HP-UX environment is critical to your operation, and for many companies, has been running for over a decade. So let’s look at this very carefully.
Here find HP’s recommended structure approach, instructions, and look-up tools, for the smoothest, quickest path from HP-UX 11i v1 or v2 running on existing HP 9000 or Integrity servers, to HP-UX 11i v3. You may also hear our HP-UX 11i v3 engineer's Webcast that describes how to update to HP-UX 11i v3. Alternately, you may read transcripts in eight languages.
At the highest level, here are the steps for updating your HP-UX environment to HP-UX 11i v3. The details below support these steps.
Update the first system
- Confirm your existing system, its devices and firmware, are supported by v3, and disk and memory supply is sufficient. Update as necessary.
- Idenfity inhouse and 3rd party software on the existing system that needs to run on v3. Work with the 3rd party software supplier for their v3 version, and satisfy your QA requirements for inhouse software.
- Update to or cold-install HP-UX 11i v3
- Install applications in a test environment
- Move environment to production.
Update additional systems
- Use a ‘golden’ image from your first system, or repeat the process used for the first system.
Print the checklist to track your systems’ information and update progress!
|
|
|
HP-UX 11i v3 runs on all currently supported systems that have shipped since 2003, and some currently supported systems that first shipped as far back as 2001. All currently supported HP Superdome systems run HP-UX 11i v3.
What matters to you is your own system, so:
- Determine exactly what system, processor and chipset you have using the HP-UX command machinfo
- Look for your system and processor in the HP-UX Server Support Matrix, and confirm there’s a ‘Yes’ for HP-UX 11i v3 support.
If your system is not listed in the HP Server Support Matrix, your system is no longer supported, and HP-UX 11i v3 is not supported on your system.
If your system is listed with HP-UX 11i v3 support, proceed! If it’s not, please discuss new system options with your HP or channel partner sales rep. HP offers trade-in credit worldwide for old equipment and software, as well as eco-friendly system disposal.
If you are deploying new hardware, follow the steps outlined in the HP-UX 11i v3 hardware & application sofware change and HP-UX 11i v3 hardware change sheets | |
|
|
HP invests in supporting our customers’ existing storage, as well as supporting new devices as quickly as possible, with HP-UX 11i v3.
If your system is running HP-UX 11i v2, retrieve the msv2v3check script from the HP Software Depot.
- Run the msv2v3check script to validate whether the firmware, drivers, mass storage I/O cards, and mass storage devices installed on your HP-UX 11i v2 system are supported on 11i v3. This script will report if any unsupported drivers, mass storage I/O cards, and mass storage devices are found on your system.
- This script also checks the minimum firmware versions required for cards or devices on your system to run properly on HP-UX 11i v3.
For more details on the msv2v3check script, refer to HP-UX 11i v2 to 11i v3 Mass Storage Stack Update Guide.
If your system is running HP-UX 11i v1, determine exactly what host bus adapters and storage devices you have using the HP-UX command ioscan. Compare your system I/O device list to the supported devices in the matrices below. » HP-UX 11i v3 mass storage support – HP products
» Ethernet System Driver Matrix
» Fibre-Channel (td) Support Matrix
» HP-UX Fibre Channel (fcd and fclp) Host Bus Adapter Support Matrix
» Smart Array RAID Controllers Support Matrix
Determine what firmware revision your system is running using the HP-UX command machinfo and compare it to the minimum level required for the servers listed in the minimum firmware table.
If a firmware upgrade is indicated, visit the BizCenter to download the firmware. Update the firmware on an HP 9000 and Integrity system using the HP Firmware Manager (HP FM). HP FM is packaged with the firmware and distributed via the Web. Download the firmware with HP FM as required.
HP FM provides two methods of updating firmware. The method to use depends on whether or not the operating system is running on the system:
- Use HP OS-Initiated Firmware Manager (HP OSIFM) if the HP-UX operating system is running. HP OSIFM provides a firmware package in a patch or product file for HP-UX. You download the patch or product, then use the operating system to update the firmware.
- Use HP Offline Firmware Manager (HP OFM) if the operating system is not running or to update the firmware for a device in the boot path. HP OFM provides a firmware package as an .ISO image that you download to a system to create a CD. You then use the CD to boot the system and update the firmware. HP OFM is available only for HP Integrity systems.
If you plan to use HP-UX 11i v3 Dynamic nPartitions (nPars), please review the minimum firmware levels required to support that feature.
When your firmware level is sufficient and your devices are supported, proceed! | |
|
| HP-UX 11i v3 requires 1.5 GB of memory for the HP-UX 11i v3 Base Operating Environment and minimal applications. Additional memory is required for optimal performance and additional software and applications including higher level OEs: check application specifications for additional memory requirements.
This is true for the base system as well as for each vPar or Virtual Machine guest where HP-UX 11i v3 is installed.
Determine how much memory you have using the HP-UX command top or glance-m if you have GlancePlus installed..
Memory sufficient? … proceed! | |
|
Applications that run on HP-UX 11i v1 will run on HP-UX 11i v3 without modification, due to HP-UX 11i forward compatibility1. In short, an application built to run on HP-UX 11i v1 or v2 will run on v3. That said, it is critical that your application suppliers know that you are running their applications on v3.
Identify the software products on your system with the HP-UX 11i command swlist. Here is an example command that writes the resulting list into a file called software_list.
/usr/sbin/swlist -l bundle-l product> /tmp/software_list
Confirm that your applications are available for HP-UX 11i v3 by searching the ISV (Independent Software Vendor) Availability Lookup Database2 for preliminary information. Contact your software supplier directly to ensure you have the latest version of the applications as appropriate – ISVs who build applications on HP-UX 11i v3 may increase application performance significantly, depending on how recent the compiler versions were for their previous application build. | |
|
Determine whether to cold-install or update your system to HP-UX 11i v3.
“Update” here means using the tool update-ux to selectively overwrite the operating system and application software from a media or network source depot. An advantage of performing an update is that it leaves user data, configuration, and applications in place.
You can update to HP-UX 11i v3 from HP-UX 11i v2 (B.11.23), as long as you are updating to the same or higher level Operating Environment. The diagram below reviews the process for updating your operating system. For more information, refer to chapter 6 of the HP-UX 11i v3 Installation and Update Guide.
|
|
|
|
|
1 Compatibility is ensured when applications use published Application Programming Interfaces (APIs). That said, many software suppliers run quality assurance tests on their applications, so their statement of support includes an assurance of quality and support beyond the simple fact that the application runs.
2 The ISV Availability Lookup Database is under constant update as software suppliers update their information.
|
 |
|
|
From any HP-UX release older than HP-UX 11i v2, you must perform a cold-install.
Even when you are running HP-UX 11i v2, you may choose to cold-install under certain conditions– please compare the characteristics of your environment to the distinctions identified in the most recent version of the HP-UX 11i v3 Installation and Update Guide, “Deciding Which Method to Use”.
Follow the preparation tasks and instructions for installing HP-UX 11i v3 in chapters 4 through 6 of the HP-UX 11i v3 Installation and Update Guide.
The diagram below shows the overall process of cold-installing HP-UX 11i v3 from media. For more, please review chapter 5 of the HP-UX 11i v3 Installation and Update Guide. You can also cold-install HP-UX 11i v3 from network depots and from golden images. For more information on these alternative methods of cold-installing refer to the Ignite-UX Administration Guide. |
|
 | |
|
|
Use the HP-UX command swlist to list the bundles and products installed on your system and compare with your software inventory taken before the cold install or update
- Use swverify to verify that all software was successfully installed on your system:
/usr/sbin/swverify \*
For full verification instructions, visit the verification chapter in the Installation and Update Guide | |
|
See Appendix B of the HP-UX 11i v3 Installation and Update Guide for information about controlling memory utilization of VxFs 4.1
There is a known problem with updating from HP-UX 11i v2 with VxFS 4.1:
If any VxFS file system with disk layout version 2 or version 3 has been created, these file systems cannot be mounted under VxFS 4.1 on HP-UX 11i v3. Please use the vxfsconvert command to upgrade the disk layout to version 4 before upgrading to VxFS 4.1 on HP-UX 11i v3.
There is a known problem with updating from HP-UX 11i v2 with FxFS 5.0:
If VxFS 5.0 has been used to create file systems with disk layout version 7, those disks will not be readable by the VxFS 4.1 for HP-UX 11i v3. Please make sure you copy data from your DLV 7 file systems onto file systems created at layout version 5 or 6 before updating to HP-UX 11i v3. |
|
| |
|
|
A high level summary of vPars migration follows these steps:
- Boot in npar mode
- Run Update-UX to update the OS to HP-UX 11i v3
- Boot vpmon
- Boot rest of vPars
For a more detailed description of vPars migration see: |
|
| |
|
|
Versija spausdinimui
