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
The nPartition number is 0. Record this information.
b. Find the boot path of the boot disk of a future vPars A.05.01 virtual partition. This boot
path will become the nPartition’s new PRI boot path.
Since keira3 is being updated to A.05.01, let’s chose to change the nPartition’s PRI path
to the boot disk of keira3.
Since we have chosen keira3 as the future A.05.01 virtual partition, we need to find the
boot path of keira3:
keira1# vparstatus -v -p keira3
...
[IO Details]
0.0.6
0.0.6.0.0.5.0 BOOT
The BOOT attribute identifies the boot path for the virtual partition keira3 as
0.0.6.0.0.5.0. Record this information.
c. Set the mode for the next nPartition reboot.
• on Integrity, set the mode to nPars for the next reboot: # vparenv -m nPars
• on PA, no mode setting is required.
The remainder of the steps to change the PRI boot path will be done later, while in
nPars/standalone mode.
5. For each virtual partition, except the first virtual partition, use Update-UX to install the latest
OE and vPars bundle. These updates can occur in parallel, although this is not required.
Example where target OS will be 11.31, which implies vPars A.05.xx:
keira3 # update-ux -s depot1:/release/1131/HPUX11i-OE-Ent.DVD HPUX11i-OE-Ent T1335CC
Example where target OS will be 11.23, which implies vPars A.04.xx:
keira2 # update-ux -s depot1:/release/1123/HPUX11i-OE-Ent.DVD HPUX11i-OE-Ent T1335BC
Be sure that both the OE and vPars bundles are specified on the update-ux command line.
CAUTION:
Using Update-UX Update-UX allows for both the OE and vPars bundles to be updated in
the same session. To simultaneously update both the OE and vPars bundles in the same
session, they both must be in the same source depot.
If you update from a depot which does not contain the vPars bundle, your disk will no
longer boot in vPars mode. See the Ignite-UX Administration Guide and Using Golden Images
with Virtual Partitions for information on how to setup your Ignite-UX server.
NOTE: Although you can update all the virtual partitions, including the first virtual
partition, in parallel, by leaving the first virtual partition up until all the updates for the
other virtual partitions are complete, it allows you to use the first virtual partition to verify
the processing and status of the other virtual partitions.
Further, if you need to change the primary path in stable storage, you will use the first virtual
partition to enter into standalone/nPars mode and change the PRI boot path.
6. After the all updates for the above virtual partitions have completed, use Update-UX to
install the latest OE and vPars bundle to the first virtual partition.
Example:
keira1 # update-ux -s depot1:/release/1131/HPUX11i-OE-Ent.DVD HPUX11i-OE-Ent T1335CC
Although you can do all the updates in parallel, you need to make sure that all of the other
virtual partition updates have successfully performed the updating to the point of halting.
100 Installing, Updating, or Removing vPars and Upgrading Servers with vPars