2.5 Other Boot- Related Tasks There are other commands that we can issue from HP-UX, the GSP, and the BCH/EFI interface that are related to booting a partition. We can categorize these tasks as follows : -
-
Reboot-for-reconfig a partition -
-
-
-
Some of these are trivial, but we will cover them, if only for completeness. 2.5.1 Reboot/Halt a partition We still have the traditional ways of rebooting and halting a partition; the shutdown and reboot commands work in exactly the same way.
root @uksd3 # reboot -h Shutdown at 04:54 (in 0 minutes) *** FINAL System shutdown message from root@uksd3 *** System going down IMMEDIATELY
The main difference here is that if you halt a partition, there isn't a partition-reset-button anywhere . We do not use the power switch on the front of the cabinet except to power-off the entire cabinet. When a partition is halted, we can view an appropriate message on the system console.
Closing open logical volumes... Done Boot device reset done. System has halted OK to turn off power or reset system UNLESS "WAIT for UPS to turn off power" message was printed above
At this stage, in order to restart the partition, we would use the GSP BO command. 2.5.2 Reboot-for-reconfig a partition We have looked at this scenario a number of times in respect of the shutdown command. The options “R and “H also apply to the reboot command. Obviously, we all know that the reboot command does not run the shutdown scripts and should be used only when the system is in a quiescent state, i.e., single- user mode. If we are in a situation where we have forgotten to use the “R option to shutdown / reboot , any pending changes to the SCCD will not be pushed out by the GSP and the partition will reboot with the same Complex Profile as before the reboot. We don't necessarily want the partition to fully boot up in order to run another shutdown / reboot “R command. In this instance, we can interrupt the boot-up of the partition, stopping the partition at the BCH/EFI interface. From the BCH/EFI prompt, we can issue the RECONFIGRESET command:
---- Main Menu -------------------------------------------------------------- Command Description ------- ----------- BOot [PRIHAAALT<path>] Boot from specified path PAth [PRIHAAALT] [<path>] Display or modify a path SEArch [ALL<cell><path>] Search for boot devices ScRoll [ONOFF] Display or change scrolling capability COnfiguration menu Displays or sets boot values INformation menu Displays hardware information SERvice menu Displays service commands DeBug menu Displays debug commands MFG menu Displays manufacturing commands DIsplay Redisplay the current menu HElp [<menu><command>] Display help for menu or command REBOOT Restart Partition RECONFIGRESET Reset to allow Reconfig Complex Profile ---- Main Menu: Enter command or menu > reconfigreset Reset the partition for reconfiguration of Complex Profile ...
Alternately, we could issue the GSP RR command, which results in the same thing.
GSP MAIN MENU: CO: Consoles VFP: Virtual Front Panel CM: Command Menu CL: Console Logs SL: Show chassis Logs HE: Help X: Exit Connection GSP> cm Enter HE to get a list of available commands GSP:CM> rr This command resets for reconfiguration the selected partition. WARNING: Execution of this command irrecoverably halts all system processing and I/O activity and restarts the selected partition in a way that it can be reconfigured. # Name --- ---- 0) uksd1 1) uksd2 2) Finance Department Select a partition number: Do you want to reset for reconfiguration partition number 0? (Y/[N]) y -> The selected partition will be reset for reconfiguration. GSP:CM>
It should be noted that using the RR and RECONFIGRESET command should be performed on a partition not running an operating system because the commands will immediately reset the partition terminating all processes/applications immediately without performing a graceful shutdown. 2.5.3 Reset a partition The task I am thinking about here is probably when a partition has hung and you want to reset the operating system without performing a crashdump . We probably all know the RS command we can run from the console/GSP. The same command is available for Node Partitionable servers. The only difference is that for an Administrator and Operator user, you will be asked which partition you want to reset.
GSP MAIN MENU: CO: Consoles VFP: Virtual Front Panel CM: Command Menu CL: Console Logs SL: Show chassis Logs HE: Help X: Exit Connection GSP> cm Enter HE to get a list of available commands GSP:CM> rs This command resets the selected partition. WARNING: Execution of this command irrecoverably halts all system processing and I/O activity and restarts the selected partition. # Name --- ---- 0) uksd1 1) uksd2 2) Finance Department Select a partition number: Do you want to reset partition number 0? (Y/[N]) y -> The selected partition will be reset. GSP:CM>
Another way to reset a partition would be to run the REBOOT command from the BCH or the RESET command from the ISL interface. 2.5.4 Instigate a crashdump in a hung partition This is similar to the concept of resetting a partition using the RS command, except that we will perform a crashdump of the operating system. Again, an Administrator and Operator user will be asked to specify the partition they want to reset. We use the GSP TC command to initiate a Transfer Of Control.
GSP MAIN MENU: CO: Consoles VFP: Virtual Front Panel CM: Command Menu CL: Console Logs SL: Show chassis Logs HE: Help X: Exit Connection GSP> cm Enter HE to get a list of available commands GSP:CM> tc This command TOCs the selected partition. WARNING: Execution of this command irrecoverably halts all system processing and I/O activity and restarts the selected partition. # Name --- ---- 0) uksd1 1) uksd2 2) Finance Department Select a partition number: 1 Do you want to TOC partition number 1? (Y/[N]) y -> The selected partition will be TOCed. GSP:CM>
Once the partition has been reset, you can navigate to the Console screen for that partition to interact with the crashdump, should you need to perform a full, partial, or no crashdump.
@(#) $Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for  CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $Transfer of control: (display==0xd904, flags==0x0) Processor 2 TOC: pcsq.pcoq = 0'0.0'4156760 isr.ior = 0'10340001.0'3bcee5a0 Processor 3 TOC: pcsq.pcoq = 0'0.0'41569c4 isr.ior = 0'0.0'0 Processor 4 TOC: pcsq.pcoq = 0'0.0'41569e8 isr.ior = 0'0.0'0 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Boot device reset done. *** The dump will be a SELECTIVE dump: 323 of 4088 megabytes. *** To change this dump type, press any key within 10 seconds. *** Select one of the following dump types, by pressing the corresponding key: N) There will be NO DUMP performed. S) The dump will be a SELECTIVE dump: 323 of 4088 megabytes. F) The dump will be a FULL dump of 4088 megabytes. *** Enter your selection now.
2.5.5 Boot actions We discussed Boot Actions in Section 2.2.2.1. I want to reiterate that section because we need to ensure that the configuration of settings such as PATHFLAGS is appropriate for all of our partitions. Boot Actions are settings we can change at the BCH/EFI interface that can affect how a partition will boot. The main part of this section deals with a setting known as PATHFLAGS . The PATHFLAGS affect how the boot interface interprets the three boot paths available to it. Remember, the three boot paths in order are Primary (PRI), High-Availability Alternate (HAA), and Alternate (ALT). By default, the boot interface will go to the next boot bath if the current path fails to boot the operating system. The PATHFLAGS can change this behavior. A PATHFLAG is a numeric value associated with each boot path. The available PATHFLAGs are: : Go to BCH; if this path is accepted, stop at the Boot Console Handler. 1 : Boot from this path; if unsuccessful , go to BCH. 2 : Boot from this path; if unsuccessful, go to the next path (default). 3 : Skip this path, and go to the next path. The only place to directly set/modify the PATHFLAGS is from the BCH Configuration screen:
Main Menu: Enter command or menu > co ---- Configuration Menu ----------------------------------------------------- Command Description ------- ----------- BootID [<cell>[<proc>[<bootid>]]] Display or set Boot Identifier BootTimer [0-200] Seconds allowed for boot attempt CEllConfig [<cell>] [ONOFF] Config/Deconfig cell COreCell [<choice> <cell>] Display or set core cell CPUconfig [<cell>[<cpu>[ONOFF]]] Config/Deconfig processor DataPrefetch [ENABLEDISABLE] Display or set data prefetch behavior DEfault Set the Partition to predefined values FastBoot [test][RUNSKIP] Display or set boot tests execution KGMemory [<value>] Display or set KGMemory requirement PathFlags [PRIHAAALT] [<value>] Display or set Boot Path Flags PD [<name>] Display or set Partition name values ResTart [ONOFF] Set Partition Restart Policy TIme [cn:yr:mo:dy:hr:mn:[ss]] Read or set the real time clock BOot [PRIHAAALT<path>] Boot from specified path DIsplay Redisplay the current menu HElp [<command>] Display help for specified command REBOOT Restart Partition RECONFIGRESET Reset to allow Reconfig Complex Profile MAin Return to Main Menu ---- Configuration Menu: Enter command > Configuration Menu: Enter command > pf Primary Boot Path Action Boot Actions: Boot from this path. If unsuccessful, go to next path. HA Alternate Boot Path Action Boot Actions: Go to BCH. Alternate Boot Path Action Boot Actions: Go to BCH. Configuration Menu: Enter command >
On a preconfigured Superdome, the PATHFLAGS for all three Boot Paths should be 2 (Boot from this path; if unsuccessful, go to the next path). To change a path, we use the PF command for each Boot Path:
Configuration Menu: Enter command > pf pri 2 Primary Boot Path Action Boot Actions: Boot from this path. If unsuccessful, go to next path. Configuration Menu: Enter command > pf haa 2 HA Alternate Boot Path Action Boot Actions: Boot from this path. If unsuccessful, go to next path. Configuration Menu: Enter command > pf alt 2 Alternate Boot Path Action Boot Actions: Boot from this path. If unsuccessful, go to next path. Configuration Menu: Enter command > pf Primary Boot Path Action Boot Actions: Boot from this path. If unsuccessful, go to next path. HA Alternate Boot Path Action Boot Actions: Boot from this path. If unsuccessful, go to next path. Alternate Boot Path Action Boot Actions: Boot from this path. If unsuccessful, go to next path. Configuration Menu: Enter command >
In some instances, it may be appropriate to change the PATHFLAGS for a particular Boot Path, e.g., due to a hardware failure or testing, where you don't want to change the actual Boot Paths themselves . There are other commands at the boot interface that can affect the boot-up of a partition, e.g., RESTART , CORECELL , CELLCONFIG , BOOTTIMER . I will let you investigate these yourself. 2.5.6 Powering off components There is little need for us, as administrators, to power-off individual components in the complex in a day-to-day configuration. If a qualified HP Customer Engineer needs to add more CPUs or RAM to a cell, we may have to power-off the cell board in question depending on whether our complex and operating system version support OLA/R for cell components. To power-off components, we use the GSP PE (Power Enable) command. At first sight, this may seem like a strange command to disable power, but it will first display the power-state of the component in question and then prompt you as to what to do next.
GSP:CM> ps This command displays detailed power and hardware configuration status. The following GSP bus devices were found: +----+-----+-----------+----------------+-----------------------------------+ Core IOs IO Bay IO Bay IO Bay IO Bay UGUY Cells 0 1 2 3 Cab. IO Chas.IO Chas.IO Chas.IO Chas. # GSP CLU PM 0 1 2 3 4 5 6 7 0 1 2 3 0 1 2 3 0 1 2 3 0 1 2 3 +----+-----+-----+-----+----------------+--------+--------+--------+--------+ 0 * * * * * * * * * * * You may display detailed power and hardware status for the following items: B - Cabinet (UGUY) C - Cell G - GSP I - Core IO Select Device: c Enter cabinet number: Enter slot number: 6 HW status for Cell 6 in cabinet 0: NO FAILURE DETECTED Power status: on, no fault Boot is blocked; PDH memory is shared Cell Attention LED is off RIO cable status: connected RIO cable connection physical location: cabinet 0, IO bay 0, IO chassis 3 Core cell is INVALID PDH status LEDs: __*_ CPUs 0 1 2 3 Populated * * * * Over temperature DIMMs populated: +----- A -----+ +----- B -----+ +----- C -----+ +----- D -----+ 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 * * * * * * * * PDC firmware rev 35.4 PDH controller firmware rev 7.8, time stamp: WED MAY 01 17:19:28 2002 GSP:CM> GSP:CM> pe This command controls power enable to a hardware device. B - Cabinet C - Cell I - IO Chassis Select Device: c Enter cabinet number: Enter slot number: 6 The power state is ON for the Cell in Cabinet 0, Slot 6. In what state do you want the power? (ON/OFF) off GSP:CM> GSP:CM> ps This command displays detailed power and hardware configuration status. s The following GSP bus devices were found: +----+-----+-----------+----------------+-----------------------------------+ Core IOs IO Bay IO Bay IO Bay IO Bay UGUY Cells 0 1 2 3 Cab. IO Chas.IO Chas.IO Chas.IO Chas. # GSP CLU PM 0 1 2 3 4 5 6 7 0 1 2 3 0 1 2 3 0 1 2 3 0 1 2 3 +----+-----+-----+-----+----------------+--------+--------+--------+--------+ 0 * * * * * * * * * * * You may display detailed power and hardware status for the following items: B - Cabinet (UGUY) C - Cell G - GSP I - Core IO Select Device: c Enter cabinet number: Enter slot number: 6 HW status for Cell 6 in cabinet 0: NO FAILURE DETECTED Power status: OFF, no fault Boot is blocked; PDH memory is not shared Cell Attention LED is off RIO cable status: connected RIO cable connection physical location: cabinet 0, IO bay 0, IO chassis 3 Core cell is INVALID PDH status LEDs: _*** CPUs 0 1 2 3 Populated * * * * Over temperature DIMMs populated: +----- A -----+ +----- B -----+ +----- C -----+ +----- D -----+ 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 * * * * * * * * PDC firmware rev 35.4 PDH controller firmware rev 7.8, time stamp: WED MAY 01 17:19:28 2002 GSP:CM>
This is a disruptive command, so ensure that the components in question are inactive . To reinstate power, we simply run the PE command again to flip the power-state from OFF to ON. If we use the PE command on the entire cabinet (effectively the same as using the power-switch on the front of the cabinet), there is still power to the Utility System and the GSP. If we want to completely power-off the cabinet (in order to move the cabinet), we need to use the power-breakers situated on the PDCA (Power Distribution Control Assembly) units located on the rear of the cabinet. | 