HP 3000 Manuals HP 3000 Manuals
The Booting Process The process of booting the processor-dependent code (PDC) and the input/output-dependent code (IODC) takes place immediately after the system self-test. The initialization process is hardware-driven and begins automatically. After the system is reset, the PDC and IODC boot sequence messages indicate or prompt for the I/O paths required for successful completion. For more information on proper I/O paths for startup, refer to the previous section. Autobooting the system Autobooting allows you to boot the system from the primary boot path without the need to make any keyboard entries. Boot messages vary slightly depending on whether autoboot is enabled. The following examples show some typical boot sequences and illustrate use of the material covered up to this point (resetting the system, system self- test, and using I/O paths). Autobooting a system is usually accomplished by enabling autoboot with the ISL AUTOBOOT command, resetting the system, and following the system's prompts. For information on the AUTOBOOT command, refer to Chapter 3 . Even when autoboot is disabled (or you have interrupted an enabled autoboot sequence as described in the next section), the system still allows you the option of autobooting by issuing an Interact with IPL (Y or N)?> message. (Bypassing a disabled autoboot flag setting to autoboot a system is discussed later in this chapter.) Example 2-5 demonstrates autobooting a Series 925 system. The example is a partial listing of an uninterrupted autoboot (autoboot enabled) sequence.[REV BEG] The screen may contain a different boot path display and additional information, depending on the system you are using.[REV END]
NOTE If you are using a Series 949 system, your primary boot path is 8.1.0.
________________________________________________________ | | | | | CM> TC | | | | | | Processor Dependent Code (PDC) revision 3.2 | | | | Console path = 4.2.0.0.0.0.0 | | Primary boot path = 4.1.0.0.0.0.0 | | Alternate boot path = 4.5.0.0.0.0.0 | | | | Autoboot from primary boot path enabled. | | To override, press any key within 10 seconds. | | | | 10 seconds expired -- proceeding with autoboot. | | | | Booting from primary boot path = 4.1.0.0.0.0.0 | | | | Console IO Dependent Code (IODC) revision 4 | | Boot IO Dependent Code (IODC) revision 4 | | | | Soft Booted. | | MMSAVE Version 2.2 | | DUMPAREA found, save main memory to disc | | ISL loaded | | | | ISL Revision A.00.28 July 15, 1993 | | | | ISL booting START AUTO | | : | | | ________________________________________________________ Example 2-5. Autobooting a Series 925 System In example 2-5, autoboot must be turned on, and an autoboot file (also known as an autoexecute file) must reside in the logical interchange format (LIF) directory for ISL to autoboot. If not, you get the message Cannot find an autoexecute file. AUTOBOOT ABORTED. For information on turning on autoboot, refer to Chapter 3 . For information on replacing autoboot files using SYSGEN, refer to Chapter 8 . Interrupting an autobooting system Even with the autoboot sequence in effect, you can override it to select an alternate boot medium (for example, a tape drive or another disk drive), to activate a different ISL utility, or to enter a different set of options. This is accomplished by pressing any key within 10 seconds after receiving the message that autoboot has been enabled. Example 2-6 provides a partial listing of an interrupted autoboot sequences for a Series 925. Other systems may display different messages and boot paths. ______________________________________________________ | | | | | CM> TC | | | | Processor Dependent Code (PDC) revision 3.2 | | | | Console path = 4.2.0.0.0.0.0 | | Primary boot path = 4.1.0.0.0.0.0 | | Alternate boot path = 4.5.0.0.0.0.0 | | | | Autoboot from primary boot path enabled. | | To override, press any key within 10 seconds. | | | | ** A key is pressed ** | | | | Boot from primary boot path (Y or N)?> n | | | | Boot from alternate boot path (Y or N)?> n | | | | Enter boot path, command, or ?> 4.1.0 | | | | | | Booting. | | | | Console IO Dependent Code (IODC) revision 4 | | Boot IO Dependent Code (IODC) revision 4 | | | | Interact with IPL (Y or N)?> y | | | | | | Soft Booted. | | MMSAVE Version 2.2 | | DUMPAREA found, save main memory to disc | | ISL loaded | | | | ISL Revision A.00.28 July 15, 1993 | | | | ISL> | | | ______________________________________________________ Example 2-6. Interrupting Autobooting Series 925 System. When the sequence is interrupted, you are asked to select whether the system should boot from the primary system disk or from a system load tape on the alternate boot path. A third prompt allows you to enter a different boot path interactively. As another option, if you enter a "?" at the Enter boot path, command, or ? prompt, you see a menu of boot command options. The menu and boot command options can differ depending on your system. Example 2-7 shows the menu for a Series 925 System. ________________________________________________________ | | | | | Use BC/1.2.3 format for boot path. | | | | The following commands are available: | | RESTART Restart the boot device selection | | BOOT Boot the system again (hard boot) | | INFO Display boot information/warnings | | LANG Select Language for boot messages | | MEM_DUMP Read/Write address locations | | FASTBOOT Enable/Disable memory testing | | TESTBOOT Enable/Disable test boot sequence | | HELP Print this help list | | | | Enter boot path, command, or ?> | | | ________________________________________________________ Example 2-7. Boot Command Options for a Series 925 System If you enter an improper boot path, forget to place the boot device online, or if the disk or tape medium is defective, the system displays a boot device status along with one or more four-character boot error codes on the system console. Example 2-8 demonstrates a system's possible response to an improper boot path. _____________________________________________________________ | | | | | CM> TC | | | | | | Processor Dependent Code (PDC) revision 3 | | | | Console path = 2/4.1.0.0.0.0.0 | | Primary boot path = 2/4.1.0.0.0.0.0 | | Alternate boot path = 6/4.3.0.0.0.0.0 | | | | Autoboot from primary boot path enabled. | | To override, press any key within 10 seconds. | | | | ** A key is pressed ** | | | | Boot from primary boot path (Y or N)?> n | | | | Boot from alternate boot path (Y or N)?> n | | | | Enter boot path, command, or ?> 8.2.4 | | | | Interact with IPL (Y or N)?> y | | | | Booting. | | | | Boot error on path 8.2.4.0.0.0.0 | | | | No device at indicated physical module -- check path | | | | Boot from primary boot path (Y or N)?> | | | _____________________________________________________________ Example 2-8. A System's Response to an Improper Boot Path A Series 950 system was used in example 2-8. Other 900 Series HP 3000 systems perform similarly, although their boot paths may be different from the example shown. For an explanation of boot error codes, refer to MPE/iX Error Message Manual Volumes I, II, and III (32650-90066, 32650-90152, and 32650-90368). The message Interact with IPL (Y or N)? gives you an additional chance to autoboot even if you previously indicated an autoboot override (or have autoboot disabled). Answering NO to the Interact message returns the system to attempt an autoboot. Interactively booting the system with autoboot disabled Interactively booting the system with autoboot disabled allows you to select a particular boot path or to activate ISL from the keyboard. The initial interactive sequence is similar to the initial autoboot sequence, except in the interactive sequence, the system does not prompt the user with the option to override the process. Example 2-9 demonstrates the interactive[REV BEG] boot sequence for a Series 922 system. The screen display may contain a different boot path and additional information, depending on the system you are using.[REV END] [REV BEG]
NOTE If you have a 99X system, you must transfer to the service processor before you reset the system. _______________________________________ | | | | | CM> SP | | | _______________________________________
[REV END] ____________________________________________________ | | | | | CM> TC | | | | | | Processor Dependent Code (PDC) revision 3.2 | | | | Console path = 4.3.0.0.0.0.0 | | Primary boot path = 4.1.0.0.0.0.0 | | Alternate boot path = 4.5.0.0.0.0.0 | | | | Boot from primary boot path (Y or N)?> y | | | | Booting | | | | Console IO Dependent Code (IODC) revision 4 | | Boot IO Dependent Code (IODC) revision 4 | | | | Interact with IPL (Y N)?> y | | | | Soft Booted. | | | | NMSAVE Version 2.2 | | DUMPAREA found, save main memory to disc | | ISL loaded | | | | ISL Revision A.00.28 July 15, 1993 | | | | ISL> | | | ____________________________________________________ Example 2-9. Interactively Booting a Series 922 System In this example, the system halts at ISL and then waits for the operator to issue an ISL command. For more information on ISL and ISL utilities, refer to Chapter 3 . Bypassing the disabled autoboot setting Answering NO to the prompt Interact with IPL (Y or N)? causes the system to ignore a disabled autoboot flag setting and attempt to autoboot. Example 2-10 demonstrates bypassing a current disabled autoboot flag setting in order to autoboot. _________________________________________________________________ | | | | | CM> TC | | | | Processor Dependent Code (PDC) revision 3.2 | | | | Console path = 2/4.1.0.0.0.0.0 | | Primary boot path = 2/4.0.0.0.0.0.0 | | Alternate boot path = 6/4.3.0.0.0.0.0 | | | | 48 MB of memory configured and tested. | | | | Soft-Booted--memory state is valid | | | | Boot from primary boot path (Y or N)?> n | | Boot from alternate boot path (Y or N)?> n | | Enter boot path, commands, or ?> 2/4.0.0 | | | | Interact with IPL (Y or N)?> n | | | | Booting | | | | Console IO Dependent Code (IODC) revision 4 | | Boot IO Dependent Code (IODC) revision 4 | | | | Booted. | | | | NMSAVE Version 2.2 | | DUMPAREA found, save main memory to disc | | ISL loaded | | | | ISL Revision A.00.00 July 15, 1993 | | | | Cannot find an auto-execute file. AUTOBOOT ABORTED. | | | | ISL> | | | _________________________________________________________________ Example 2-10. Bypassing the Disabled Autoboot Setting When Booting a System