HPUX :After a Firmware update, the rx7620 would Not boot because the system defaulted to nPars mode and not vPars.

After a Firmware update, the rx7620 would Not boot because the system defaulted to nPars mode and not vPars.

Overview

After a Firmware update, the rx7620 would not boot because the system defaulted to nPars mode and not vPars

Procedures

Upon trying to boot the system using the defined boot menu option, the system fails to boot with: ©) Copyright 2004 Hewlett-Packard Development Company, L.P.All rights reserved HP-UX Boot Loader for IPF -- Revision 2.027 Press Any Key to interrupt Autoboot \efi\hpux\AUTO ==> boot /stand/vpmon -a Seconds left till autoboot - 0 AUTOBOOTING...> System Memory = 12151 MB loading section 0 ... (complete) loading section 1 ................................................................................ ......... (complete) loading symbol table loading System Directory (boot.sys) to MFS .....Launching /stand/vpmon SIZE: Text:1126K + Data:45108K + BSS:18958K = Total:65194K Console is on a Serial Device ERROR: Please use the vparenv(1M) command in HP-UX or the vparconfig(1M) command at the EFI prompt to switch to vPars mode . Unsupported boot environment for the vPar monitor. Resetting the system! ======== The /EFI/HPUX directory is missing the vparconfig command. The command needed to be reinstalled using efi_cp by copying the command from /usr/newconfig/sbin/vparconfig.efi to /EFI/HPUX/vparconfig.efi . We first booted the server in nPar mode in order to get the server to a point where we could issue the commands to get the EFI command copied to the disk's EFI partition. Then the disk where the EFI partion resides is c0t6d0s1 , and we used the commands: # lvlnboot -v Boot Definitions for Volume Group /dev/vg00: Physical Volumes belonging in Root Volume Group: /dev/dsk/c0t6d0s2 (0/0/0/2/0.6.0) -- Boot Disk Boot: lvol1 on: /dev/dsk/c0t6d0s2 Root: lvol3 on: /dev/dsk/c0t6d0s2 Swap: lvol2 on: /dev/dsk/c0t6d0s2 Dump: lvol2 on: /dev/dsk/c0t6d0s2, 0 # efi_ls -d /dev/rdsk/c0t6d0s1 /efi/hpux FileName Last Modified Size . 5/ 5/2006 0 .. 5/ 5/2006 0 HPUX.EFI 5/ 5/2006 541306 NBP.EFI 5/ 5/2006 24576 AUTO 5/ 8/2006 21 total space 523251712 bytes, free space 519626752 bytes # efi_cp -d /dev/rdsk/c0t6d0s1 vparconfig.efi /efi/hpux # efi_cp -d /dev/rdsk/c0t6d0s1 crashdump.efi /efi/hpux # efi_ls -d /dev/rdsk/c0t6d0s1 /efi/hpux FileName Last Modified Size . 5/ 5/2006 0 .. 5/ 5/2006 0 HPUX.EFI 5/ 5/2006 541306 NBP.EFI 5/ 5/2006 24576 AUTO 5/ 8/2006 21 crashdump.efi 4/16/2007 107990 vparconfig.efi 4/16/2007 101897 Total space 523251712 bytes, free space 519626752 bytes While the system is still running in nPars mode, use the vparenv command to change to vPars mode: # vparenv -m vpars The other option would be to reboot the system and enter the EFI shell to run the vparconfig command: Shell> fs0: fs0:\> cd efi\hpux fs0:\EFI\HPUX> vparconfig Current mode: nPars. vparconfig supports the following options: vparconfig vparconfig reboot vPars vparconfig reboot nPars fs0:\EFI\HPUX> vparconfig reboot vpars Rebooting ... Affected systems: rx7620 rx7640 rx8620 rx8640 Superdome SX1000 SD32A SD64A Superdome SX2000 SD32B SD64B .

Keywords.

efi_cp, vparenv,

HPUX :Switching between nPars and vPars Modes

Switching between nPars and vPars Modes(Integrity only).

Overview

Modes On an Integrity system, you will need to set the mode in order to boot into a specific mode. For vPars usage, there are only two modes: • vPars sets the next nPartition boot to boot into the vPars environment. This allows you to boot the vPars Monitor and therefore the virtual partitions in the next nPartition boot. You still need to boot the vPars Monitor and the virtual partitions, but this mode allows you to do this. • nPars sets the next nPartition boot to boot into the standalone environment. In this mode, you cannot boot the vPars Monitor and therefore the virtual partitions. However, you can boot any OE instance into standalone mode.

Procedures

Commands to Set the Mode • HP-UX Shell: vparenv [-m mode] where mode has the value of either vPars or nPars sets the mode for the next nPartition reboot. Note that this may take a few minutes to process. Example: To set the nPartition into vPars mode so that the next nPartition boot allows you to boot the vPars Monitor and therefore the vPars environment: 1. Set the mode # vparenv -m vPars 2. Then, you manually reboot the nPartition: # shutdown –r ... Shell> fs0: fs0:\> hpux /stand/vpmon ... MON> • Monitor: reboot [mode] where mode has the value of either vPars or nPars reboots the nPartition into the mode mode. If any virtual partitions are up, this will cause them to be shutdown ungracefully. • EFI: vparconfig [reboot mode] where mode has the value of either vPars or nPars sets the mode for the next nPartition reboot and then also reboots the nPartition. Note that vparconfig is not a built-in EFI shell command. You must go to the disk (for example, fs0:) to execute the vparconfig command. Examples: • To set the mode to vPars and then immediately reboot the nPartition into vPars mode: Shell> fs0: /* first goto the disk */ fs0:\> vparconfig reboot vPars /* then you can execute vparconfig */ • To set the mode to nPars and then immediately reboot the nPartition into nPars mode Shell> fs0: /* first goto the disk */ fs0:\> vparconfig reboot nPars • EFI: parconfig [mode[-n] ] where mode has the value of only nPars. parconfig does not allow you to set the mode to vPars -n means no interactive prompts NOTE: HP recommends using vparconfig instead of parconfig whenever possible; information on parconfig is provided here as additional information or when vparconfig is not present on the disk. vparconfig is installed only on the boot disks of the virtual partitions when vPars is installed. If the boot disks are removed or you switch boot disks, you may need to use parconfig. Example To set the nPartition into nPars mode and reboot the nPartition: 1. First, set the mode: Shell> parconfig nPars -n 2. Then, you can reboot the nPartition from either the EFI shell using the reset option: Shell> parconfig reset Usage Scenarios • If you are running HP-UX in nPars mode (standalone), use the following vPars command to switch to vPars mode: OS-Prompt> vparenv -m vPars /* sets the mode for the next nPartition reboot */ OS-Prompt> reboot /* to reboot the system into vPars mode */ • If you are at the Monitor prompt, use the following Monitor command to switch to nPars mode: MON> reboot nPars /* sets the mode and reboots the system */ • If you are at EFI shell prompt, use the following EFI utility to switch to either nPars or vPars mode: Shell:> fsN: fsN:> vparconfig reboot nPars|vPars Since vparconfig is not a built-in EFI shell command, you must goto the disk to execute vparconfig. For example, to switch to vPars mode: Shell:> fs0: /* goto the EFI partition of the disk */ fs0:> vparconfig reboot vPars /* sets the mode and reboots the system */ Note: vparconfig is an EFI utility which gets installed in the EFI partition during the installation of the vPars product. • If you are at EFI shell prompt in vPars mode and you do not have vPars installed on any of your disks, you can use the built-in EFI command parconfig to switch to nPars mode: Shell:> parconfig nPars Shell:> parconfig reset Note: Remember to issue a parconfig reset after setting the mode. parconfig nPars only sets the mode to nPars. You must issue the parconfig reset to reset the system so that it boots into nPars mode. Note: parconfig does not support switching to vPars mode. In other words, you can use parconfig to set the mode to nPars, but you cannot use parconfig to set the mode to vPars.

Keywords.

Vparenv Vparconfig,vparboot,reboot,parconfig.

HPUX :TOC : Virtual partition to Resolve hung issue and dump creation.

TOC : Virtual partition to Resolve hung issue and dump creation.

Overview

TOC : Virtual partition to Resolve hung issue and dump creation.

Procedures

[root@traclp01:/.root]# #-> vparstatus [Virtual Partition]                                                                           Boot Virtual Partition Name         State Attributes   Kernel Path             Opts ============================== ===== ============ ======================= ===== gthcomp2                       Down  Dyn,Auto,Nsr /stand/vmunix                traclq01                       Up    Dyn,Auto,Nsr /stand/vmunix                traclp01                       Up    Dyn,Auto,Nsr /stand/vmunix                [Virtual Partition Resource Summary]                                            CPU    Num        Memory (MB)                                   CPU     Bound/   IO   # Ranges/ Virtual Partition Name          Min/Max  Unbound  devs  Total MB    Total MB ==============================  ================  ====  ==================== gthcomp2                          2/ 16    2   2    17    0/  0         8192   traclq01                          2/ 16    2   0    11    0/  0         8192   traclp01                          2/ 16    2   0    12    0/  0         8064   [ [root@traclp01:/.root]# #-> vparreset -p traclq01 -t Reset virtual partition traclt01? [n]  y ******** TOC -- Processor 2: HPA 0xfffffffffc071000  Entity ID: 1 ********* General Registers 0 - 31 00-03  0000000000000000  0000000008ef20f0  0000000000000000  0000000009cb2000 04-07  0000000000000001  0000000000000000  0000000009cb2000  0000000000000000 08-11  0000000009cb29b0  0000000000000000  006454351f701252  006454351f701252 12-15  0000000008ee60f0  0000000009cb5268  0000000000000064  0000000000000000 16-19  0000000000000000  800000010043b428  0000000000080000  000000000922b848 20-23  0000000000000000  0000000000000000  0000000000000000  0000000000000000 24-27  0000000000000000  0000000413d66170  000000055128a000  0000000008eea0f0 28-31  0000000000000000  0000000413d66240  0000000413d66270  000000001bc68b64 Control Registers 0 - 31 00-03  000000006ef13a8a  0000000000000000  0000000000000000  0000000000000000 04-07  0000000000000000  0000000000000000  0000000000000000  0000000000000000 08-11  000087a500007ea3  000000000003e100  00000000000000c0  000000000000001e 12-15  0000000000000000  0000000000000000  000000000800a000  fffffff0ffffffff 16-19  006454351fe9c4da  0000000000000000  000000000815f604  00000000ebe0f000 20-23  0000000010340027  000000002c8b31d8  000000ff0824ff1f  0000000000000000 24-27  0000000009cb2000  0000000000429000  000000055128a000  8000000100311cd0 28-31  0000000000000000  006454351f6fbd91  0000000077f91af8  0000000413d66270 Space Registers 0 - 7 00-03  000000000bd26800  0000000001093400  0000000002e22400  0000000000000000 04-07  0000000000000000  00000000ffffffff  0000000008fa8000  0000000000000000 IIA Space                    = 0000000000000000 IIA Offset                   = 000000000815f608 CPU State                    = 0x9e000001 ******** TOC -- Processor 3: HPA 0xfffffffffc074000  Entity ID: 2 ********* General Registers 0 - 31 00-03  0000000000000000  ffffffffffffffff  000000000000001e  0000000009cb53c8 04-07  0000000000000001  0000000000000001  0000000009cb53c8  0000000009cc56b0 08-11  0000000009cb5d78  0000000000000001  0064543597dae4a1  0064543597dae4a1 12-15  0000000008ee60f0  0000000009cb8630  0000000000000064  000000000000008a 16-19  0000000000000000  00000000ffffffff  0000000000000000  0000000000000000 20-23  0000000000000006  000000000922b848  00000000093c2e90  0000000000000000 24-27  0000000000000006  000000000000000c  0000000009cb2000  0000000008eea0f0 28-31  0000000000000000  0000000000000000  0000000413d69270  00000000000026d6 Control Registers 0 - 31 00-03  000000007f9935c0  0000000000000000  0000000000000000  0000000000000000 04-07  0000000000000000  0000000000000000  0000000000000000  0000000000000000 08-11  000000000002bad3  0000000000030892  00000000000000c0  0000000000000035 12-15  0000000000000000  0000000000000000  000000000800a000  fffffff0ffffffff 16-19  00645436105b5b19  0000000000000000  000000000815ef18  0000000053d53cd1 20-23  0000000000000000  0000000000000000  000000ff082cfb1f  0000000100000000 24-27  0000000009cb53c8  0000000000487000  0000000009cb2000  0000000077f6d090 28-31  00000000093c2e90  0064543610078d7b  0000000008ee68f0  0000000413d69270 Space Registers 0 - 7 00-03  000000000a751800  0000000000000000  000000000feff800  0000000000000000 04-07  0000000000000000  00000000ffffffff  0000000008fa8000  0000000000000000 IIA Space                    = 0000000000000000 IIA Offset                   = 000000000815ef44 CPU State                    = 0x9e000001 #monitor the console for dump creation /reboot sequence.

Vparstatus, vparinfo, vparreset.