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
 Installing and Managing HP-UX Virtual Partitions (vPars) > Chapter 4 Planning Your Virtual Partitions and Installing vPars

Installation
» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

spacerspacerspacer
spacer
spacer
  		 
 

You can install vPars on an existing HP-UX installation directly from a depot or CD or by using an Ignite-UX server.

Related Information

For information on the installation of HP-UX, see the manual "HP-UX 11i Installation and Update Guide".

For information on swinstall and software depots, see the manual "Software Distributor Administration Guide for HP-UX".

For information on using the vPars commands, see the following sections in the chapter Chapter 5 “Monitor and Shell Commands”:

NOTE: Before installing vPars, please read “Planning Your Virtual Partitions”.

Setting the GSP Terminal Type

Note: this section applies only to the rp5470/L3000 and rp7400/N4000 servers. You can skip this section for nPartion-able 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.

Setting Up the Ignite-UX Server

NOTE: To use an Ignite-UX server to install the vPars software, you must be running Ignite-UX version B.3.4.115 (September 2001) or higher.

If you will be using Ignite-UX, see “Ignite-UX and other Curses Applications”.

For quick steps in setting up your Ignite-UX Server to include the vPars bundles, you can use the "cookbook" information provided by the ITRC. You can access this information by:

  1. Go to the ITRC web site:

    http://itrc.hp.com

  2. Under maintenance and support, select search technical knowledgebase

  3. Enter the keyword vPars

  4. You will see Ignite-UX & vPars Cookbook

For complete information on Ignite-UX, see the manual Ignite-UX Administration Guide.

Updating the Ignite-UX Server

CAUTION: If you are using Ignite-UX versions B.3.4.XX (September 2001), B.3.5.XX (December 2001), or B.3.6.XX (March 2002), in addition to adding the vPars bundles to your Ignite server, you need to replace the existing file /opt/ignite/boot/WINSTALL with a vPars-compatible WINSTALL file using the script named WINSTALL_script.

WINSTALL is a bootable kernel used by Ignite-UX during the installation and recovery of a virtual partition. WINSTALL_script copies a vPars-compatible WINSTALL to the correct location on the Ignite-UX server.

Determining the Version of Ignite-UX

To determine which version of Ignite-UX you are running, execute the command:

# swlist -l fileset -a revision Ignite-UX.FILE-SRV-11-11

For example, if your swlist output shows

	# Initializing...
# Contacting target "rust"...
#
# Target:  rust:/
#
Ignite-UX.FILE-SRV-11-11                  B.3.5.89

then your Ignite-UX version is B.3.5.89.

Installing a vPars-compatible WINSTALL file using WINSTALL_script

To replace the WINSTALL file on your Ignite-UX server, perform the following from your Ignite-UX server:

  1. Obtain the vPars WINSTALL and WINSTALL_script files:

    • From the vPars CD:

      If you have purchased the vPars CD, the files are located in the vParsWINSTALL directory off the root directory of CD.

    • From the vPars web site:

      Go to http://www.software.hp.com

      Select Enhancement Releases
      Select HP-UX Virtual Partitions

      Follow the instructions on the web page for obtaining the files WINSTALL and WINSTALL_script.

  2. Run the script WINSTALL_script to copy the WINSTALL file to the correct location on your Ignite-UX server.

NOTE: The WINSTALL_script saves a copy of the original WINSTALL file. To restore the original WINSTALL file, execute the WINSTALL_script again.

Increase in Size of /stand File System

Due to the vPars files that will exist in /stand, you should increase by 50 MB the size of the /stand file system that you normally create.

Bundle Names

vPars Bundles

The vPars bundle names are as follows:

Bundle Name

Description

VPARSBASE

free vPars product

T1335AC

purchased vPars product

For more information on the free and purchased versions of vPars, see “Features of Free Versus Purchased Product”.

vPars-related Bundles

Products related to this release of vPars (all of which are on the vPars CD) are:

Bundle Name

Description

VPARMGR

vPars GUI (vparmgr)

B6826AA

Partition Manager for nPartitions (parmgr)

B6191AAE

Online Diagnostics

B9073AA

iCOD

NOTE: For information on product versions required to run with vPars, please see the document Read Before Installing HP-UX Virtual Partitions available as the vPars CD booklet and at the documentation web page http://docs.hp.com/hpux/11i/index.html#Virtual%20Partitions.

Installing and Removing vPars-related Bundles

VPARMGR

The vPars GUI (vparmgr) is not automatically installed when vPars is installed. If you wish to use vparmgr, you need to manually select this bundle during your Software Distributor (SD) or Ignite-UX session or add this bundle to your swinstall command line.

VPARMGR is available on the vPars CD and from the vPars web page at http://software.hp.com.

To install the VPARMGR bundle using the vPars CD:

# swinstall -s /cdrom VPARMGR

To remove the VPARMGR product:

# /usr/sbin/swremove vParManager

B6826AA (parmgr)

The Partition Manager (parmgr) is required for installation of the vPars product. This is true on both nPartition-able servers as well as non-nPartitionable servers (rp7400/N4000 and rp54700/L3000). It is normal to have this product installed on non-nPartitionable servers.

The Partition Manager is available on the vPars CD and at http://www.software.hp.com/products/PARMGR.

To install the Partition Manager bundle using the vPars CD:

# swinstall -s /cdrom B6826AA

To remove the Partition Manager product:

# /usr/sbin/swremove PartitionManager

Note that the PartitionManager product can be removed only after the vPars product is removed from a virtual partition.

B6191AAE (Online Diagnostics)

Online Diagnostics is not automatically installed when vPars is installed. If you wish to use Online Diagnostics, you need to manually select this bundle during your Software Distributor (SD) or Ignite-UX session or add this bundle to your swinstall command line.

The Online Diagnostics bundle is available on the vPars CD and from the vPars web page at http://www.software.hp.com.

To install the Online Diagnostics bundle using the vPars CD:

# swinstall -s /cdrom -x autoreboot=true B6191AAE

To remove the Online Diagnostics product:

# /usr/sbin/swremove OnlineDiag

Note: Removing OnlineDiag also removes the Predictive Support package.

B9073AA (iCOD)

iCOD is not automatically installed when vPars is installed. If you wish to use iCOD, you need to manually select this bundle during your Software Distributor (SD) or Ignite-UX session or add this bundle to your swinstall command line.

iCOD is available on the vPars CD and from http://www.software.hp.com.

Please also see the iCOD web page at http://software.hp.com for the latest patch information for iCOD.

To install the iCOD bundle using the vPars CD:

# swinstall -s /cdrom -x autoreboot=true B9073AA

To remove the iCOD bundle:

# /usr/sbin/swremove B9073AA

NOTE: The iCOD product B9073AA should not be selected for installation unless you are already participating in the iCOD program.

For complete information and notes on installing, removing, and configuring iCOD, see the section "Installing and Un-installing iCOD Software" in the manual Instant Capacity on Demand (iCOD) User's Guide for version B.05.00 available at http://docs.hp.com.

Example
Installing vPars and the vPars-related Bundles from CD

Below is an example of using the swinstall command line to install vPars from the CD:

# swinstall -s /cdrom -x autoreboot=true T1335AC

To install vPars and the vPars-related bundles:

# swinstall -s /cdrom -x autoreboot=true T1335AC VPARMGR \ B68266AA B6191AAE B9073AA

NOTE: The products VPARMGR, B6191AAE (Online Diagnostics), and B9073AA (iCOD) are optional. Also, see NOTE above for iCOD.

Quality Pack

After installing HP-UX, you should also install the latest HP-UX 11i Quality Pack. You can obtain the latest Quality Pack bundle from the latest Support Plus CD or from the web:

  • http://software.hp.com

    Select Enhancement Releases
    Select HP-UX Quality Packs

JFS (Journal File System)

To avoid hangs on vxfs file systems, please install kernel patch PHKL_27121 on the operating systems of each virtual partition. This patch is available from the IT Resource Center web site at http://itrc.hp.com.

Installing Firmware Patches on the rp5470/L3000 and rp7400/N4000

NOTE: Upgrading firmware on a Superdome must be performed by Hewlett-Packard qualified service personnel only. Please contact your local HP Support Representative to schedule a convenient time for this firmware upgrade service.

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 please 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 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).



Planning Your Virtual Partitions
  		 


Installing vPars Using Ignite-UX  
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2002 Hewlett-Packard Development Company, L.P.