United States-English |
|
|
HP-UX Virtual Partitions Administrator’s Guide > Chapter 4 Installing, Updating, or Removing vPars and Upgrading Servers
with vParsNotes, Cautions, and Other Considerations Before You Update or Install vPars |
|
Be sure you understand vPars before attempting the updates and installations. See Chapter 2: “How vPars and Its Components Work ” and Chapter 3: “Planning Your System for Virtual Partitions”. Booting from HP-UX Install Media (Integrity only) Under vPars A.05.02 and later, the vPars Monitor supports booting an install kernel from CD or DVD media with the vparload -p partition_name -D disk_index command. For details, see “vPars Monitor: Using vPars Monitor Commands”. Related Information For information on the installation of HP-UX and what is supported for your HP-UX version, see the applicable HP-UX 11i Installation and Update Guide and the HP-UX 11i Release Notes for your OS version. For information on swinstall and software depots, see the manual "Software Distributor Administration Guide for HP-UX". For more information on booting and boot devices on PA-RISC systems, see also the paper titled Booting, Installing, Recovery, and Sharing in a vPars Environment from DVD / CDROM / TAPE / Network available at: http://docs.hp.com/en/vse.html#Virtual%20Partitions For information on using the vPars commands, see the following sections in the chapter vPars Monitor and Shell Commands: Server Chipset Upgrade The process documented in many of the updates assumes you are not performing a hardware upgrade that causes a change in hardware paths (for example, upgrading from the sx1000 chipset to the sx2000 chipset). For information on upgrading vPars when the upgrade includes a hardware path change, see “Upgrading Integrity Servers from the sx1000 to sx2000 Chipset”. Hardware Paths on the vPars Command Line
Installing Firmware for the systems running vPars must be done in a standalone (PA-RISC) or nPars (Integrity) mode. Once in standalone or nPars mode, the procedure for installing firmware on a system with vPars installed is the same as a system without vPars installed. Additional information is shown below. For information on specific firmware versions for your servers, see the HP-UX Virtual Partitions Ordering and Configuration Guide.
Note: this section applies only to the rp5470/L3000 and rp7400/N4000 servers. You can skip this section for nPartitionable servers. The Guardian Service Processor (GSP) provides multiple access methods for the console: the hardware console port, the remote-modem port, and the LAN console port. To avoid mismatches in terminal emulation which can cause strange results on your display, it is important to match the display type as set in the GSP to the display type of the terminal or terminal emulator that you are using. For example:
You will see a message indicating the command execution will take a few seconds and then a message indicating that your settings have been updated. The virtual partitions that you create will use this terminal-type setting for their virtual console displays.
Due to the vPars files that will exist in /stand, you should increase your planned size of the /stand file system by 100 MB. For example, if you originally had planned to create /stand with 1 GB for your HP-UX instance, you should plan for 1.1 GB when that HP-UX instance resides in a virtual partition. To avoid hangs on VxFS file systems, install kernel patch PHKL_27121 or its successor on the operating systems of each virtual partition. This patch is available from the IT Resource Center website at http://itrc.hp.com. Before installing the SecurePath product, install the vPars product and create and install all the virtual partitions.
|
Printable version | ||
|