Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX Virtual Partitions Administrator’s Guide > Chapter 4 Installing, Updating, or Removing vPars and Upgrading Servers with vPars

Notes, Cautions, and Other Considerations Before You Update or Install vPars

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

Notes

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”.

Cautions

Hardware Paths on the vPars Command Line  

  • Hardware Path Differences Between Cellular (nPartitionable) and Non-cellular Systems

    The hardware paths for some example system are formatted for non-cellular systems. For cellular systems, their hardware paths contain the prefix of the cell number. Therefore, on non-cellular systems, the path 0/0 refers to a SBA/LBA format. However, on cellular systems, the path 0/0 refers to a cell/SBA format. Read the section “Planning, Installing, and Using vPars with an nPartitionable Server” if you are using a cellular system.

  • Path Formats on the vPars Command Line

    For vPars A.03.01 or earlier, you must explicitly specify the LBA for I/O allocation. Thus, for cellular systems on A.03.01 or earlier, you must use the cell/SBA/LBA format on the command line. If you use only the cell/SBA format the vPars commands will not assume that all LBAs under the specified SBA are to be included in the allocation. Doing so may cause the system to panic.

    For vPars A.03.02 or later, you can use either the cell/SBA or cell/SBA/LBA format on the command line. The vPars commands will assume the command applies to all LBAs under the specified SBA.

Other Considerations

This section covers:

Installing Server Firmware on non-nPartitionable Servers

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.

  • Non-nPartitionable Systems  On the rp5470/L3000 and rp7400/N4000 servers, for firmware patches to take effect in a vPars environment, follow this procedure:

    1. Shut down all the virtual partitions.

    2. Reboot the server into standalone mode using the primary path. This consists of the following:

      1. At the MON> prompt, type reboot

      2. If needed, interrupt the boot sequence at the BCH>, and using the primary path, boot/stand/vmunix instead of/stand/vpmon. For example:

        BCH> bo pri interact with IPL? y . . . ISL> hpux /stand/vmunix
      NOTE: The server must be in standalone mode for the patches to take effect, so do not skip this step.
    3. Install the firmware patch as you would in a non-vPars environment. The firmware patch will reboot your server.

    4. After the firmware installation has completed, you can boot the vPars Monitor and virtual partitions as you normally would.

      For example, if you have not modified your AUTO file in the LIF area to boot the vPars Monitor and virtual partitions, boot the vPars Monitor (for example, ISL> hpux /stand/vpmon) and then the virtual partitions (for example, MON> vparload -auto).

  • Mid-range Servers  Once in standalone or nPars mode, install the server firmware as you normally do.

  • Superdomes (PA-RISC and Integrity)  Upgrading firmware on a Superdome must be performed by Hewlett-Packard qualified service personnel only. Contact your local HP Support Representative to schedule a convenient time for the firmware upgrade service.

Setting the GSP Terminal Type

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:

  • If you are using a hardwired HP terminal or a LAN-based terminal emulator of type “hpterm”, set the GSP terminal-type setting to hpterm.

  • If you are using a LAN-based terminal emulator of type “dtterm” or “xterm”, set the GSP terminal-type setting to vt100.

How to Set the GSP Terminal Type
  1. Access the GSP through the lan console, the remote-modem port, or a physically connected terminal.

  2. Use the CA command at the GSP prompt to modify the console attributes:

    GSP> ca

  3. Answer “y” (yes) to indicate that you want to change the console port settings:

    Do you want to modify the Local Console Serial Port settings? (Y/[N]) y

  4. Answer “n” (no) to the questions about modifying the “Serial Port bit rate” and the “Current Flow Control

    Current Local Console Serial Port bit rate: 9600 bits/s Do you want to modify it? (Y/[N]) n Current Flow Control: Software Do you want to modify it? (Y/[N]) n
  5. Indicate which terminal type you want to use, then answer “y” (yes) to confirm your change:

    Enter Terminal Type ([Vt100] / Hpterm): New Terminal Type: hpterm Confirm? (Y/[N]): y -> Terminal Type will be updated.
  6. Answer n (no) to the question about updating the “Remote Console Serial Port Modem settings”:

    Do you want to modify the Remote Console Serial Port Modem settings? (Y/[N]) n

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.

TIP: If you get a garbled display, you can press Ctrl-L to refresh the display.

Increase in Size of /stand File System

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.

VxFS (Veritas File System) (vPars A.03.xx)

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.

SecurePath

Before installing the SecurePath product, install the vPars product and create and install all the virtual partitions.

NOTE: The SecurePath product is not supported on HP-UX 11i v3 (11.31). Use the native multipathing available with the HP-UX 11i v3 mass storage stack, as described in the white paper The Next Generation Mass Storage Stack. This paper can be found in the Network and Systems Management section of http://docs.hp.com, under Storage Area Management.
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2008 Hewlett-Packard Development Company, L.P.