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 9 nPartition Operations

Reconfiguring the nPartition

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

You must perform a Reboot for Reconfiguration on an nPartition in the following circumstances:

  • whenever you add cells to the nPartition

  • whenever you need to allow an inactive cell to join the nPartition (such as after changing a cell use-on-next-boot value from “n” to “y”).

  • whenever you remove active cells from the nPartition

When the nPartition reboots from a Reboot for Reconfiguration, variables are written by the HP-UX kernel in nPar mode. Some of these variables contain the most recent information about the cells.

The vPars Monitor reads these variables when it boots. If a Reboot for Reconfiguration of the nPartition has not been performed, the vPars Monitor does not receive the most recent information about the cells, and an error will occur.

For information on performing a Reboot for Reconfiguration, see “Rebooting and Reconfiguring Conceptual Points” as well as “Reconfiguring an nPartition (Integrity)” for Integrity systems, and “Reconfiguring an nPartition (PA-RISC)” for PA-RISC systems.

Reconfiguring an nPartition (Integrity)

NOTE: On an Integrity server, the OS kernel in nPars mode needs to write the new CPU mapping data to certain EFI variables; in order for this to occur properly, a complete reboot in nPars mode is required after the parmodify operation has taken affect.

From nPars mode:

  1. Perform the changes as you would in a non-vPars environment. For example, if we want to add cell 6 to partition 0:

    keira# parmodify -p0 -a 6:base:y:ri In order to activate any cell that has been newly added,reboot the partition with the -R option. Command succeeded.
  2. Perform a Reboot for Reconfiguration from a virtual partition. For example,

    keira# shutdown -R

    Do not put the nPartition into vPars mode; you will need to perform an additional reboot into nPars mode.

  3. Allow the system to reboot into nPars mode. Once this is successful, the OS kernel automatically will write the correct CPU mapping data to EFI. Now you can reboot the nPartition back into vPars mode and reboot the vPars Monitor.

    keira# vparenv -m vPars keira# shutdown -r ... fs0:\EFI\HPUX> boot vpmon ...

From vPars mode:

  1. Perform the changes as you would in a non-vPars environment. For example, if we want to add cell 6 to partition 0 for the next boot of the vPars Monitor:

    keira1# parmodify -p0 -a 6:base:y:ri In order to activate any cell that has been newly added,reboot the partition with the -R option. Command succeeded.
  2. Perform a Reboot for Reconfiguration from a virtual partition. For example,

    keira1# vparstatus keira1# shutdown -R -H

    At this point, the nPartition is in the Boot-Is-Blocked (BIB) state. Note that once the nPartition is in the BIB state, vparstatus shows the following message in the remaining virtual partitions:

    Note: A profile change is pending. The hard partition must be rebooted to complete it.

  3. Shutdown all the other virtual partitions. For example, on keira2:

    keira2# shutdown -h ... Transition to run-level0 is complete. Executing "/sbin/reboot-R ". Note: If this is a partitionable system, the requested reconfiguration will not take place until all the virtual partitions on this hard partition are shut down and the virtual partition Monitor is rebooted. Shutdown at 16:19 (in 0 minutes)

    This should bring you to the vPars Monitor prompt (MON>)

  4. From the vPars Monitor prompt, boot the nPartition into nPars mode:

    MON> reboot nPars

    Allow the nPartition to boot into nPars mode. If autoboot is not setup, perform the boot into nPars mode manually when the system comes up:

    Shell> fsN: fsN:\> efi\hpux\hpux /stand/vmunix
  5. Once the system boots into nPars mode, the OS kernel automatically will write the correct CPU mapping data to EFI. Now you can reboot the nPartition back into vPars mode and reboot the vPars Monitor.

    keira# vparenv -m vPars keira# shutdown -r ... fs0:\EFI\HPUX> boot vpmon ...

Reconfiguring an nPartition (PA-RISC)

For the following example, the virtual partitions keira1 and keira2 exist within the nPartition 0. Only relevant output is shown.

  1. Perform the changes as you would in a non-vPars environment. For example, if we want to add cell 6 to partition 0:

    keira1# parmodify -p0 -a 6:base:y:ri In order to activate any cell that has been newly added,reboot the partition with the -R option. Command succeeded.
  2. Perform a Reboot for Reconfiguration from a virtual partition. For example,

    keira1# vparstatus keira1# shutdown -R . . . Transition to run-level0 is complete. Executing "/sbin/reboot-R". Note: If this is a partitionable system, the requested reconfiguration will not take place until all the virtual partitions on this hard partition are shut down and the virtual partition Monitor is rebooted. Shutdown at 16:09 (in 0 minutes)

    At this point, the nPartition is in the Boot-Is-Blocked (BIB) state. The virtual partition keira1 remains down until all the virtual partitions have been shutdown and the vPars Monitor rebooted.

    Note also that once the nPartition is in the BIB state, vparstatus shows the following message:

    Note: A profile change is pending. The hard partition must be rebooted to complete it.

  3. Shutdown the other virtual partitions. For example:

    keira2# vparstatus keira2# shutdown -R . . .Transition to run-level0 is complete. Executing "/sbin/reboot-R ". Note: If this is a partitionable system, the requested reconfiguration will not take place until all the virtual partitions on this hard partition are shut down and the virtual partition Monitor is rebooted. Shutdown at 16:19 (in 0 minutes)

    At this point, all virtual partitions have been shut down. The vPars Monitor will reboot automatically. On the console, we would see the following message:

    All partitions have halted. System will now reboot for reconfiguration.

    and the beginning of the boot process for the nPartition:

    Firmware Version 21.3 Duplex Console IO Dependent Code (IODC) revision 2 -------------------------------------------------------------------------- (c) Copyright 1995-2002, Hewlett-Packard Company, All rights reserved -------------------------------------------------------------------------- Cab/ Cell ------- Processor -------- Cache Size Cell Slot State # Speed State Inst Data ---- ---- ------------ --- -------- ----------- ------ ------ 0 0/0 Idle 0A 1000 MHz Idle 32 MB 32 MB 0B 1000 MHz Idle 32 MB 32 MB 1A 1000 MHz Idle 32 MB 32 MB 1B 1000 MHz Idle 32 MB 32 MB 2A 1000 MHz Idle 32 MB 32 MB 2B 1000 MHz Idle 32 MB 32 MB 1 0/1 Active 0A 1000 MHz Active 32 MB 32 MB 0B 1000 MHz Idle 32 MB 32 MB 1A 1000 MHz Idle 32 MB 32 MB 1B 1000 MHz Idle 32 MB 32 MB 2A 1000 MHz Idle 32 MB 32 MB 2B 1000 MHz Idle 32 MB 32 MB Primary Boot Path: 1/0/0/3/0.6 Boot Actions: Go to BCH. HA Alternate Boot Path: 1/0/0/3/0.6 Boot Actions: Go to BCH. Alternate Boot Path: 1/0/12/1/0.8 Boot Actions: Go to BCH. Console Path: 1/0/0/0/1.0
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2008 Hewlett-Packard Development Company, L.P.