Boot Process. Superdome

Transcription

1 Boot Process Superdome

2 This even page intentionally left blank Boot Process 6-2

3 Chapter Table of Contents Introduction to the Boot process... 5 Objectives... 5 How to Access the BCH/PDC Menus... 6 Main Menu... 7 Configuration Menu... 8 Information Menu... 9 Service Menu Setting SCSI Parameters in the Service Menu How to Boot to the Operating System Superdome ISL Menus The Boot Process Overview Cell Boot Overview In-depth Bootstrap Description Early CPU initialization and cell monarch selection Cell Initialization Partition rendezvous and core cell selection The Boot Flow Troubleshooting the Bootstrap Process Several Types of (Re)Boots Lab Boot Process 6-3

4 This even page intentionally left blank. Boot Process 6-4

5 Introduction to the Boot process The Superdome series boot menus are basically the same as those used on the recent cell-based system marketed by HP. Instead of proceeding directly to the main PDC menu, one must first work with the Management Processor (MP) and open a console window. Objectives Upon completion of this chapter you will be able to: Define PDC. Define PDH. Describe how a cell boots Describe how a partition boots Describe the PDC/BCH menus. Access and use the boot level menus. Describe the startup process. Boot Process 6-5

6 How to Access the BCH/PDC Menus 1) Power on the system. 2) Access the MP. 3) Use the virtual front panel (VFP) to monitor the boot process. 4) Type CO (Consoles). 5) Choose a partition. 6) Type MA to access the Main menu. The BCH/PDC menus are similar to the menus seen on older HP9000 systems. For example, the Main menu contains the Boot, Path, SEArch, and HElp commands, plus the COnfiguration, INformation, and SERvice menus. Boot Process 6-6

7 Main Menu Main Menu: Enter command or menu > di ---- Main Menu Command Description BOot [PRI HAA ALT <path>] Boot from specified path PAth [PRI HAA ALT] [<path>] Display or modify a path SEArch [ALL <cell> <path>] Search for boot devices ScRoll [ON OFF] Display or change scrolling capability COnfiguration menu INformation menu SERvice menu DIsplay HElp [<menu> <command>] REBOOT RECONFIGRESET ---- Main Menu: Enter command or menu > Displays or sets boot values Displays hardware information Displays service commands Redisplay the current menu Display help for menu or command Restart Partition Reset to allow Reconfig Complex Profile search search cell search 2 search all search path search 3/0/11 Search for potential boot devices on core cell. Search for bootable devices on the specified cell. Search for potential boot devices on all cells within the partition. Search for bootable devices attached to PCI card in slot 8 (LBA 11) of the I/O chassis connected to cell 3 Boot Process 6-7

8 Configuration Menu 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>] [ON OFF] Config/Deconfig cell COreCell [<choice> <cell>] Display or set core cell CPUconfig [<cell>[<cpu>[on OFF]]] Config/Deconfig processor DataPrefetch [ENABLE DISABLE] Display or set data prefetch behavior DEfault Set the Partition to predefined values FastBoot [test][run SKIP] Display or set boot tests execution KGMemory [<value>] Display or set KGMemory requirement PathFlags [PRI HAA ALT] [<value>] Display or set Boot Path Flags PD [<name>] Display or set Partition name values ResTart [ON OFF] Set Partition Restart Policy TIme [cn:yr:mo:dy:hr:mn:[ss]] Read or set the real time clock BOot [PRI HAA ALT <path>] DIsplay HElp [<command>] REBOOT RECONFIGRESET MAin ---- Configuration Menu: Enter command > Boot from specified path Redisplay the current menu Display help for specified command Restart Partition Reset to allow Reconfig Complex Profile Return to Main Menu Auto Start Setting On Off Description The partition will attempt to boot, even if a CPU or DIMM failure is detected during POST. The boot process will stop at the BCH if a CPU or DIMM failure is detected during POST. The PathFlags command replaces the autoboot flag. PathFlags Setting Description 0 Do not boot OS; stop at BCH. 1 Boot from this path; if boot fails, go to BCH. 2 Boot from this path; if boot fails, try next path. 3 Skip this path and try the next path. Boot Process 6-8

9 Information Menu Main Menu: Enter command or menu > in ---- Information Menu Command Description ALL [<cell>] Display all of the information BootINfo Display boot-related information CAche [<cell>] Display cache information ChipRevisions [<cell>] Display revisions of major VLSI ComplexID Display Complex information FabricInfo Display Fabric information FRU [<cell>] [CPU MEM] Display FRU information FwrVersion [<cell>] Display version for PDC, ICM, and Complex IO [<cell>] Display I/O interface information MEmory [<cell>] Display memory information PRocessor [<cell>] Display processor information BOot [PRI HAA ALT <path>] DIsplay HElp [<command>] REBOOT RECONFIGRESET MAin ---- Information Menu: Enter command > Boot from specified path Redisplay the current menu Display help for specified command Restart Partition Reset to allow Reconfig Complex Profile Return to Main Menu Boot Process 6-9

10 Service Menu Main Menu: Enter command or menu > ser ---- Service Menu Command Description BAttery [<cell>] Display Cell Battery Status CLEARPIM [<cell>] Clear the Partition's NVM PIM data DimmDealloc [<cell>] [<dimm>] [ON OFF] Display or Deallocate the dimm <dimm> in cell <cell>. ErrorLog [<cell>][memory IO FABRIC CELL] Display Error log information LanAddress Display Core LAN station address MemRead <address> [<len>] Read memory locations scope of Partition PDT [<cell>] [CLEAR] Display or clear the PDT PIM [<cell> [<proc>]] [HPMC LPMC TOC] Display PIM information SCSI [<path> [INIT RATE TERM WIDTH DEFAULT [<id>]]] Display or set SCSI device parameters BOot [PRI HAA ALT <path>] DIsplay HElp [<command>] REBOOT RECONFIGRESET MAin ---- Service Menu: Enter command > Boot from specified path Redisplay the current menu Display help for specified command Restart Partition Reset to allow Reconfig Complex Profile Return to Main Menu Use the cellconfig (cec) command to display the cell configuration status or to schedule a cell for (de)configuration on the next hard boot. Use the DimmDealloc command to turn off suspect DIMMs. Use the CPUconfig (CPU) command to display cell processor configuration status or to schedule a processor for (de)configuration on the next hard boot. Use the ErrorLog command to display error logs. Use the PIM command to look at offline chassis-logs (tombstone files). Boot Process 6-10

11 SETTING SCSI PARAMETERS IN THE SERVICE MENU Boot Console Handler (BCH) SCSI commands displays or sets SCSI controller parameters. These parameters are used by the operating system SCSI driver. SCSI [<path> [INIT RATE TERM WIDTH DEFAULT [<id>]]] <path> is in I/O notation, such as 1/2/3/4.5.6 <rate> is FAST, ULTRA, or NOLIMIT If either the ID or PATH parameter is set to Unknown or a path is not in the parameters table, a default set of SCSI controller parameters, from firmware, is used by the OS SCSI driver. Defaults values: Initiator ID = 7 Rate = FAST Note The SCSI Default command may need to be run after configuring a new partition. If you see errors regarding SCSI device paths when you try to run a search (SEA), then issue this command. Boot Process 6-11

12 How to Boot to the Operating System 1) Power on the system. 2) Access the MP. 3) Type CO (Consoles). 4) Choose a partition (Usually partition 0). 5) The Boot Console Handler (BCH) menu appears. 6) Type MA to access the Main menu. 7) Type BO to boot to the primary boot device. 8) Answer Y to boot to the OS, or answer N at prompt about stopping at ISL prior to booting to OS. Superdome ISL Menus The ISL menu is the same as that found on many other HP9000 models. Boot Process 6-12

13 The Boot Process Overview System resources are configured into one or more boot npartitions. Each npartition includes the cells (with processors and memory) assigned to it and the I/O that is connected to those cells. An npartition can be booted or rebooted independently of any other npartition. Each npartition runs its own firmware and has its own boot environment. Boot Process 6-13

14 Cell Boot Overview 1) System administrator applies power to the cell. 2) The cell is held in a reset state until power stabilizes. 3) The cell is released from reset. 4) The boot-is-blocked bit (BIB ) is set. 5) The cell s monarch processor s PDC performs self-tests, identifies the cell s hardware. checks for I/O, and identifies everything that is connected to the cell via its crossbar link (XBC). 6) The cell reports its hardware configuration to the GSP. 7) The GSP ensures that the cell s copy of the complex profile has current information. 8) The GSP clears the BIB, allowing the cell to boot. 9) The cell s monarch processor s PDC checks that the cell is compatible with the other cells in the partition. 10) If the cell is compatible, its monarch processor s PDC reads the complex profile and the cell boots as part of its partition. 11) If the cell is the core cell, its monarch CPU performs the system boots and executes IPL. Boot Process 6-14

15 In-depth Bootstrap Description The bootstrap code (a portion of the PDC) is responsible for properly testing system hardware, and ensuring that the hardware is functional, configured, and initialized, so the next level of software will be able to take control of the system. The bootstrap process starts when the PDC is vectored to the PDCE_RESET entry point, and continues until control is handed off to the OS loader or another Initial Program Loader (IPL) software module. The bootstrap code goes through the following phases: 1) Early CPU initialization and cell monarch selection 2) Cell initialization 3) Partition rendezvous and core cell selection 4) Partition initialization 5) IPL launch 1 - EARLY CPU INITIALIZATION AND CELL MONARCH SELECTION Each CPU on every cell performs early CPU initialization. During this phase the CPU is initialized, basic testing is performed, and any CPUs that were deconfigured during the previous boot are re-configured. In addition, one CPU will be chosen as the Cell monarch. Once the monarch has been selected the Interconnect Medium (ICM) is initialized. Once the ICM has initialized, the cell monarch can send chassis codes. Once the self-tests are complete, the slave CPUs rendezvous and the monarch proceeds with cell initialization. How the monarch is chosen The CPU with the highest boot ID that has passed the early CPU initialization is chosen as monarch. If there is a tie, the lower-numbered CPU is chosen. Boot Process 6-15

16 2 CELL INITIALIZATION The monarch CPU is responsible for initializing and testing the cell resources. Every cell goes through this phase, which includes further self-tests on CPUs, memory, discovery, I/O discovery, and fabric discovery. The following are some of the actions that occur during cell initialization: The cell controller is initialized Memory discovery Early and late CPU self-tests PDC is moved from ROM into memory I/O discovery Fabric discovery The link between the cell controller (CC) and crossbar chip (XBC) is initialized. This allows the system to determine the topology of the fabric, as well as the health of fabric links. PDC can route around one failed XBC link. The cell information structure is updated. If the boot-is-blocked (BIB) bit is set, the cell enters a wait loop until the bit is cleared via the MP/GSP. 3 - PARTITION RENDEZVOUS AND CORE CELL SELECTION During this phase, all the cells communicate, and a core cell, that is, a base cell with a core I/O card attached, is selected. The core cell then proceeds to initialize the partition. The core cell checks the other cells to verify they are compatible with the core cell: Cells must be in the same type of cabinet, be running the same version of PDC, and have the same type and speed of CPU s. Cells that fail the check are not allowed to become part of the partition. Once the set of cells in the partition is determined, the cell controller (CC) registers for the partition are set up, page zero memory is initialized, and the console device is initialized. Control is then turned over to the boot console handler (BCH) for selection of a boot device. While in rendezvous mode, the slave CPUs periodically check that the monarch CPU is operating correctly. If the monarch CPU has failed, it is deconfigured and the cell is reset. Resetting the cell restarts the bootstrap process so a new monarch can be chosen. Boot Process 6-16

17 The Boot Flow Boot Process 6-17

18 Boot Process 6-18

19 Boot Process 6-19

20 Boot Process 6-20

21 Boot Process 6-21

22 Boot Process 6-22

23 Boot Process 6-23

24 Troubleshooting the Bootstrap Process In general, bootstrap errors are handled in one of three ways: a) A failed component is deconfigured and boot continues. b) Manual intervention is required before boot can continue. c) The cell must be restarted (powered off then powered on). Examples Slave CPU fails early CPU self-test If a slave CPU fails early CPU self-test, it is deconfigured and the boot process continues. The failed CPU is stopped and inactive. Monarch CPU fails early CPU self-test If a monarch CPU fails early CPU self-test, it is deconfigured and a new monarch is chosen. After the cell is deconfigured the cell resets to restart the boot process and a new monarch is chosen from the remaining cell CPUs. a) The partition takes a long time (over ten minutes) to boot b) Not all cells boot to join (rendezvous) a partition The cells may be powered off. Some cells may have failed self-tests or have their use-on-next-boot value set to N, or may have booted too late to rendezvous. In these cases, be sure to check/change the cell power status, set the cell s useon-next-boot value to Y, and then perform a reboot-for-reconfig (shutdown R ). A cell CPU has a different PDC revision The CPU is not allowed to join the cell and is reset for reconfiguration. A reset for reconfiguration resets the cell, and the BIB (boot-is-blocked) bit is set. The cell executes the bootstrap process, but will wait at the BIB until the bit is cleared by an Administrator using the GSP boot command. An error has been detected in PDC code The cell is halted. The only way it can be restarted is by powering it off then on. Additional examples can be found in Chapter 5, pages of the HP Systems Partition Guide, rev Boot Process 6-24

25 Several Types of (Re)Boots Know how to use and when to use the appropriate boot command. MP/GSP Cmd BCH/PDC Cmd HP-UX Cmd reboot shutdown -r Halt shutdown -h What It Does Shuts down HP-UX and reboots the partition; can also be used at BCH. Shuts down HP-UX, halts all processing on the partition, and does not reboot. RS reset reboot Resets the partition; only active cells are reset. bo (boot) shutdown -R Boot a partition; proceeds past the BIB state; cells will rendezvous, dependent on partition settings will either stop at BCH or proceed to OS. Shutdown HP-UX and reboot the partition for partition reconfiguration. All cells reboot and are reconfigured. Do this following any partition modifications. RR RECONFIGRESET shutdown -R -H Shuts down a partition, performs any reconfigurations, and sets the BIB, thus making the partition and all its cells inactive. In this state the partition can be removed from a remote partition. Boot Process 6-25

26 Lab This lab requires that one of your partitions be at the PDC/BCH menus. 1) At the end of the previous lab you powered on the system. 2) Log onto the MP as Admin. 3) Type CO for Consoles. 4) Choose an available partition. 5) If the partition is at the OS, reboot the partition and interrupt the boot sequence. 6) If the system is already at the BCH, go to the next step. 7) Type MA to ensure you are at the Main menu. 8) Type DI to display the Main Menu. 9) Check the Scroll flag. If it is off, turn it On. 10) Type CO to go to the Configuration menu. Use the commands on the Configuration menu to answer the following questions: a. What cabinet, cell, and slot are you working with? b. Which cells are configured? c. Has a core cell been designated yet? d. How many processors are available on this cell board? e. How many of these CPUs are configured? f. What is the known good memory for your system? g. On older HP9000 systems one could type boot pri or boot alt. What is the third choice that is available on newer HP systems? h. What is the maximum length for a partition name? 11) Read the help screen for RECONFIGRESET command. 12) Type RECONFIGRESET 13) Press <cntrl> B to access the MP. 14) Type VFP. 15) Choose the partition in which you have been working in this lab. 16) Note how the boot is blocked. 17) Press <cntrl> B to exit the VFP. 18) Type CM. 19) Type BO. Boot Process 6-26

27 20) Select the same partition. 21) Answer Y to the prompt Do you want to boot. 22) Type MA to go to the main menu. 23) Type CO. 24) Choose the same partition. 25) You are returned to the BCH Main Menu. 26) Type IN to go to the Information menu. Use the commands on the Configuration menu to answer the following questions: a. What is the primary boot path for the system? b. What is the alternate boot path? c. What is the high-availability alternate path? d. What is the chip revision for the PDC? e. Which model PA-RISC processor is installed? f. How much memory is installed? g. How many DIMMs are installed? h. What is the part number for the DIMMs? i. What is the speed of the processors? 27) Type MA to go back to the Main menu. 28) Type SER to go to the Service menu. Use the commands on the Service menu to answer the following questions: a. Is the battery state OK? b. How much memory is installed in this system? c. How many types of error logs can be viewed from this menu? d. What is the MAC/LAN/Ethernet address for this core I/O card? 29) Type MA to return to the Main menu. 30) Type BO to boot to the primary boot path. 31) Type Y to interact with ISL. 32) Type ls to view the utilities installed on this system. 33) Type hpux ls to view the contents of the /stand directory on this disk. 34) Boot the system to single user mode. 35) Type shutdown yh 0 Boot Process 6-27

28 This even page intentionally left blank. Boot Process 6-28