HP-UX Virtual Partitions Administrator's Guide (includes A.04.06 and A.05.04)
Table Of Contents
- HP-UX Virtual Partitions Administrator’s Guide
- Table of Contents
- About This Document
- 1 Introduction
- 2 How vPars and Its Components Work
- Partitioning Using vPars
- vPars Monitor and Database
- Boot Sequence
- Virtual Consoles
- Security
- EFI and Integrity Notes
- Integrity Differences Relative to PA-RISC
- Comparing vPars on PA-RISC and Integrity
- Comparing vPars Versions
- Resource Migration and Required States
- Transitioning from vPars A.03.xx to vPars A.04.xx/A.05.xx (CPU Syntax and Rules)
- 3 Planning Your System for Virtual Partitions
- Full ioscan Output of Non-Cellular System Named winona
- Full ioscan Output of Cellular (nPartitionable) System Named keira
- Planning, Installing, and Using vPars with an nPartitionable Server
- Planning Your Virtual Partitions
- Mixed HP-UX 11i v1/v2 vPars Environments in vPars A.04.05
- Mixed HP-UX 11i v2/v3 vPars Environments in vPars A.05.xx
- Mixed HP-UX 11i v1/v2/v3 vPars Environments in vPars A.05.03
- 4 Installing, Updating, or Removing vPars and Upgrading Servers with vPars
- Notes, Cautions, and Other Considerations Before You Update or Install vPars
- Bundle Names
- Setting Up the Ignite-UX Server
- Ignite-UX, the LAN, the LAN card, and vparboot -I
- Updating from vPars A.04.xx to A.05.xx
- Updating from vPars A.03.xx to Mixed HP-UX 11i v1/v2 vPars (A.03.05 and A.04.05) Environment
- Migrating from vPars A.03.xx to Mixed HP-UX 11i v1/v2/v3 vPars (A.03.05, A.04.02 or later, A.05.03)
- Updating from vPars A.04.xx to Mixed HP-UX 11i v2/v3 vPars (A.04.xx and A.05.xx) Environment
- Updating from vPars A.03.xx to A.05.xx
- Updating from vPars A.03.xx to A.04.xx
- Updating vPars A.03.xx to vPars A.03.05
- Updating from vPars (A.02.xx or A.03.xx) to A.03.xx
- Applying a vPars Sub-System Patch
- Upgrading Integrity Servers from the sx1000 to sx2000 Chipset
- Upgrading HP 9000 Servers from the sx1000 to sx2000 Chipset
- Upgrading Backplanes from PCI to PCI-X
- Updates Involving VPARSBASE
- Installing vPars with Ignite-UX on PA-RISC
- Installing vPars with Ignite-UX on Integrity
- Installing vPars with Software Distributor
- Removing the vPars Product
- 5 vPars Monitor and Shell Commands
- Notes on Examples in this Chapter
- Modes: Switching between nPars and vPars Modes (Integrity Only)
- EFI Boot Disk Paths, including Disk Mirrors, and vparefiutil (Integrity Only)
- vPars Monitor: Booting the vPars Monitor
- vPars Monitor: Accessing the vPars Monitor Prompt
- vPars Monitor: Using vPars Monitor Commands
- vPars Monitor: Using the vPars Monitor Commands from ISL or EFI
- Commands: vPars Manpages
- Commands: vPars Commands Logging
- Commands: Displaying vPars Monitor and Resource Information (vparstatus)
- Virtual Partition States
- vparstatus Output Examples
- vparstatus: Summary Information
- vparstatus: Verbose Information
- vparstatus: Available Resources
- vparstatus: CPU Information on vPars A.04/A.05
- vparstatus: Dual-Core CPUs
- vparstatus: Pending Migrating CPUs Operations
- vparstatus: Pending Migrating Memory Operations
- vparstatus: Base and Float Memory Amounts
- vparstatus: Pending nPartition Reboot for Reconfiguration
- vparstatus: vPars Monitor and Database Information
- Managing: Creating a Virtual Partition
- Managing: Removing a Virtual Partition
- Managing: Modifying Attributes of a Virtual Partition
- Booting a Virtual Partition
- Shutting Down or Rebooting a Virtual Partition
- Shutting Down or Rebooting the nPartition (Or Rebooting the vPars Monitor)
- Setboot and System-wide Stable Storage
- Using Primary and Alternate Boot Paths
- Autoboot
- Single-User Mode
- Other Boot Modes
- Resetting a Virtual Partition
- Using an Alternate Partition Database File
- Managing Resources With Only One Virtual Partition
- 6 CPU, Memory, and I/O Resources (A.05.xx)
- I/O: Topics
- I/O: Concepts and Functionality
- I/O: Adding or Deleting LBAs
- I/O: Allocation Notes
- Memory: Topics
- Memory: Concepts and Functionality
- Memory: Assigning (Adding) or Deleting by Size (ILM)
- Memory: Assigning (Adding) Or Deleting by Size (CLM)
- Memory: Assigning (Adding) Or Deleting by Address Range
- Memory: Available and Assigned Amounts
- Memory: Converting Base Memory to Float Memory
- Memory: Granularity Concepts
- Memory: Granularity Issues (Integrity and PA-RISC)
- Memory: Setting the Granularity Values (Integrity)
- Memory: Setting the Granularity Values (PA-RISC)
- Memory: Notes on vPars Syntax, Rules, and Output
- CPU: Topics
- CPU: Concepts and Functionality
- CPU: Specifying Min and Max Limits
- CPU: Adding and Deleting by Total
- CPU: Adding or Deleting by CLP (Cell Local Processor)
- CPU: Adding or Deleting by Hardware Path
- CPU: Notes on vPars Syntax, Rules, and Output
- CPU: Dual-Core Processors
- CPU: Hyperthreading ON/OFF (HT ON/OFF)
- CPUs: Managing I/O Interrupts
- CPU: CPU Monitor (Formerly Known As LPMC Monitor)
- Memory, CPU: Canceling Pending Operations
- 7 CPU, Memory, and I/O Resources (A.04.xx)
- I/O: Concepts
- I/O: Adding or Deleting LBAs
- I/O: Allocation Notes
- Memory: Concepts and Functionality
- Memory: Assigning by Size (ILM)
- Memory: Assigning by Size (CLM)
- Memory: Specifying Address Range
- Memory: Granularity Concepts
- Granularity Issues (Integrity and PA-RISC)
- Memory: Choosing a Granularity Value and Boot Time (Integrity)
- Memory: Setting the Granularity Values (Integrity)
- Memory: Setting the Granularity Values (PA-RISC)
- Memory: Allocation Notes
- CPU
- CPU: Boot Processor and Dynamic CPU Definitions
- CPU: Specifying Min and Max Limits
- CPU: Adding and Deleting by Total
- CPU: Adding or Deleting by CLP (Cell Local Processor)
- CPU: Adding or Deleting by Hardware Path
- CPU: Syntax, Rules, and Notes
- Managing I/O Interrupts
- CPU: Using iCAP (Instant Capacity on Demand) with vPars (vPars A.04.xx and iCAP B.07)
- CPU: Dual-Core Processors
- CPU: CPU Monitor (Formerly Known As LPMC Monitor)
- 8 CPU, Memory, and I/O Resources (A.03.xx)
- I/O: Concepts
- I/O: Adding or Deleting LBAs
- I/O: Allocation Notes
- Memory: Concepts and Functionality
- Memory: Assigning by Size (ILM)
- Memory: Specifying Address Range
- Memory: Allocation Concepts and Notes
- CPU
- CPU: Specifying Min and Max Limits
- CPU: Bound and Unbound
- CPU: Determining Whether to Use Bound or Unbound
- CPU: Determining When to Specify a Hardware Path for a Bound CPU
- CPU: Adding and Removing Bound CPUs
- CPU: Adding a CPU as a Bound CPU
- CPU: Removing a Bound CPU
- CPU: Adding, Removing, and Migrating Unbound CPUs
- CPU: Managing I/O Interrupts
- CPU: Dual-Core Processors
- CPU: CPU Monitor (Formerly Known As LPMC Monitor)
- 9 nPartition Operations
- Basic Conceptual Points on using vPars within nPartitions
- nPartition Information
- Setting Hyperthreading (HT ON/OFF) and cpuconfig Primer
- Rebooting and Reconfiguring Conceptual Points
- Reconfiguring the nPartition
- Putting an nPartition into an Inactive State and Other GSP Operations
- Configuring CLM for an nPartition
- 10 Crash Processing and Recovery
- Crash Processing
- Network and Tape Recovery
- Using make_net_recovery within a vPars Environment
- Using make_tape_recovery Outside of a vPars Environment
- Using make_tape_recovery and Dual-media Boot
- Using make_tape_recovery within a vPars Environment
- Expert Recovery
- 11 vPars Flexible Administrative Capability
- Synopsis
- Terms and Definitions
- Flexible Administrative Capability Commands
- monadmin
- vparadmin
- Persistence across vPars Monitor Reboots
- vPars Commands
- Example vPars Monitor Scenario (monadmin)
- Example HP-UX Shell Scenario (vparadmin)
- A Command Successfully Executed
- A Command Not Executed Due to the Flexible Administrative Capability Feature
- Adding a Virtual Partition to the Designated-admin Virtual Partition List
- Deleting a Virtual Partition to the Designated-admin Virtual Partition List
- Listing the Virtual Partitions in the Designated-admin Virtual Partition List
- Changing the Flexible Administrative Capability Password
- Determining whether Flexible Administrative Capability is ON or OFF
- 12 Virtual Partition Manager (A.03.xx)
- A LBA Hardware Path to Physical I/O Slot Correspondence (PA-RISC only)
- B Problem with Adding Unbound CPUs to a Virtual Partition (A.03.xx)
- C Calculating the Size of Kernels in Memory (PA-RISC only)
- D Memory Usage with vPars in nPartitions
- E Moving from a Standalone to vPars
- F Supported Configurations for Memory Migration
- Glossary
- Index
Memory: Allocation Concepts and Notes
• The unit for the specified size of memory for the vPars commands is megabytes; parmodify
uses gigabytes.
• The default memory assigned to a virtual partition is 0 MB, so you need to specify enough
memory for your applications and the operating system. While there is no specific minimum
base memory requirement per vpar, the HPUX kernel does require a certain amount of base
memory to boot successfully. For this reason, we currently recommend that 1 GB of base
memory is assigned per vpar. The more base memory a virtual partition has, the better the
performance will be. This is especially true of applications that require large amounts of
locked memory. See the Installation and Update Guide for your OS and the nPartition
Administrator’s Guide for your server.
• Memory is allocated in multiples of 64 MB. Any specified size that is not a multiple of 64
MB is rounded up to the nearest 64 MB boundary. For example, if you specify 1 MB, 64 MB
will be allocated.
CPU
NOTE:
Processor Terminology Processing resources under vPars, both as input arguments and command
outputs, are described as “CPUs.” For multi-core processors such as the PA-8800, the term “CPU”
is synonymous with “core.” The term “processor” refers to the hardware component that plugs
into a processor socket. Therefore a single processor can have more than one core, and vPars
commands will refer to the separate cores as distinct “CPUs,” each with its own hardware path.
Two vPars terms pre-date multi-core processors, so they are exceptions to this terminology:
• “boot processor,” which refers to the CPU (that is, core) on which the OS kernel of the virtual
partition was booted, and
• “cell local processor (CLP),” which refers to a CPU on a specified cell.
For more information on dual-core processors, see “CPU: Dual-Core Processors” (page 261).
CPU migration refers to adding CPUs to and deleting CPUs from a virtual partition. Dynamic
CPU migration refers to migrating CPUs while the target virtual partition is running. vPars allows
the assignment of most CPUs while the virtual partitions are running.
For vPars A.03 and earlier, the two types of CPUs are bound and unbound (floater) CPUs. This
discussion begins at “CPU: Bound and Unbound” (page 255).
NOTE:
Using vPars A.03.xx and Earlier Syntax on a vPars A.04.xx System Although not recommended
under most circumstances, you can still use the vPars A.03.xx CPU syntax on vPars A.04.xx
systems. However, the concepts and rules of boot processors and dynamic CPUs in A.04.xx will
apply because the concepts and rules of bound and unbound CPUs in A.03.xx no longer apply.
Memory: Allocation Concepts and Notes 253