![]() |
![]() HP OpenVMS Systems Documentation |
![]() |
OpenVMS Alpha Version 7.3
|
Previous | Contents | Index |
You can use an alternate TURBOchannel adapter to boot a DEC 3000 series Alpha computer (with the TURBOchannel option) over the network in an InfoServer or OpenVMS Cluster environment. Examples of alternate TURBOchannel adapters are the PMAD (which connects to the Ethernet) and the DEFTA (which connects to the FDDI).
To boot from a TURBOchannel device connected to one of these alternate adapters, enter the boot command as follows:
>>> BOOT "n/ESA0" |
The value for n is the TURBOchannel slot number for the device, which you can obtain by entering the SHOW CONFIGURATION command at the console prompt (>>>) and examining the display. In the following example, the TURBOchannel slot number (listed under the "TCINFO" column) is 0:
>>> SHOW CONFIG DEC 3000 - M300 Digital Equipment Corporation VPP PAL X5.56-80800101/OSF PAL X1.34-80800201 - Built on 12-JUN-2001 11:376 TCINFO DEVNAM DEVSTAT ------ -------- -------- CPU OK KN16-AA -V3.2-S6CD-I151-sV2.0-DECchip 21064 P3.0-150 ASIC OK MEM OK MEM OK 6 CXT OK 5 NVR OK SCC OK NI OK ISDN OK 4 SCSI OK 0-PMAD-AA TC0 |
If a system problem prevents your system from booting, you might need to perform an emergency boot operation. Table A-2 summarizes these emergency boot operations, and the sections that follow describe each boot operation in more detail.
Operation | When to Use |
---|---|
Booting with default system parameters | When parameter values in the parameter file have been modified so that the system is unbootable |
Booting without startup and login procedures | If an error in the startup or login procedures prevents you from logging in |
Booting without the user authorization file | If you have forgotten the password and cannot log in to a privileged account |
If the current values stored in the parameter file have been incorrectly modified, these incorrect values might cause the system to become unbootable. With a conversational boot operation, you can reset the active values for all system parameters to the default value. (In most cases, Compaq recommends that you use AUTOGEN to modify system parameters. In certain cases, however, you can use a conversational boot to modify a parameter value temporarily. To change a parameter value permanently, you must edit MODPARAMS.DAT and run AUTOGEN. For instructions, see the OpenVMS System Manager's Manual.) The default values allow you to boot the system temporarily so you can correct the problem.
How to Perform This Task
>>> BOOT -FLAGS 0,1 [device-name] |
SYSBOOT> USE DEFAULT |
SYSBOOT> CONTINUE |
Example
SYSBOOT> USE DEFAULT SYSBOOT> CONTINUE Username: SYSTEM Password: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET NPAGEDYN 2999808 SYSMAN> PARAMETERS WRITE CURRENT SYSMAN> EXIT $ EDIT SYS$SYSTEM:MODPARAMS.DAT . . . [Insert the following line in MODPARAMS.DAT:] MIN_NPAGEDYN = 2999808 . . . $ @SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT |
If the system does not complete the startup procedures or does not allow you to log in, bypass the startup and login procedures. The startup and login procedures provided by Compaq should always work. However, if you introduce an error when modifying the startup or login procedures, it is possible to accidentally lock yourself out of the system.
How to Perform This Task
>>> BOOT -FLAGS 0,1 [device-name] |
SYSBOOT> SET/STARTUP OPA0: |
SYSBOOT> CONTINUE |
$ SET NOON |
$ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET/STARTUP SYS$SYSTEM:STARTUP.COM SYSMAN> PARAMETERS WRITE CURRENT SYSMAN> EXIT $ |
$ @SYS$SYSTEM:STARTUP |
Example
SYSBOOT> SET/STARTUP OPA0: SYSBOOT> CONTINUE $ SET NOON $ SET DEFAULT SYS$SYSROOT:[SYSEXE] $ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET/STARTUP SYS$SYSTEM:STARTUP.COM SYSMAN> PARAMETERS WRITE CURRENT SYSMAN> EXIT $ @SYS$SYSTEM:STARTUP |
Ordinarily, the startup and login procedures provided by Compaq always work; however, certain user interventions can cause them to fail. A very simple way to lock yourself out of the system is to set passwords to login accounts and forget them. In such an emergency, you can use the alternate user authorization file rather than the standard user authorization file.
You can use this method only to log in to the system from the console terminal; you cannot use other terminal lines. |
Setting the system parameter UAFALTERNATE defines the logical name SYSUAF to refer to the file SYS$SYSTEM:SYSUAFALT.DAT. If this file is found during a normal login, the system uses it to validate the account and prompts you for the user name and password.
If it cannot find this file, the system assumes that the UAF is corrupt and accepts any user name and any two passwords to log you in to the system from the system console. Logins are prohibited from all other terminal lines.
When you perform this procedure, the system assigns the following values to your user account:
Field | Value |
---|---|
Name | User name |
UIC | [001,004] |
Command interpreter | DCL |
Login flags | None |
Priority | Value of the system parameter, DEFPRI |
Resources | Values of the PQL system parameters |
Privileges | All |
How to Perform This Task
>>> BOOT -FLAGS 0,1 [device-name] |
SYSBOOT> SET UAFALTERNATE 1 |
SYSBOOT> SET WINDOW_SYSTEM 0 |
SYSBOOT> CONTINUE |
$ DEFINE/SYSTEM/EXECUTIVE_MODE SYSUAF SYS$SYSTEM:SYSUAF.DAT |
$ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET UAFALTERNATE 0 |
SYSMAN> PARAMETERS SET WINDOW_SYSTEM 1 |
SYSMAN> PARAMETERS WRITE CURRENT |
Example
SYSBOOT> SET UAFALTERNATE 1 SYSBOOT> SET WINDOW_SYSTEM 0 SYSBOOT> CONTINUE Username: [Return] Password: [Return] Password: [Return] $ DEFINE/SYSTEM/EXECUTIVE_MODE SYSUAF SYS$SYSTEM:SYSUAF.DAT $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE AUTHORIZE> MODIFY SYSTEM/PASSWORD=FGLFTUTU AUTHORIZE> EXIT $ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET WINDOW_SYSTEM 1 SYSMAN> PARAMETERS SET UAFALTERNATE 0 SYSMAN> PARAMETERS WRITE CURRENT SYSMAN> EXIT $ @SYS$SYSTEM:SHUTDOWN |
The following sections describe how to perform SET, SHOW, and Writeboot
operations.
A.2.1 Setting the System for Automatic Booting
Alpha computers can boot automatically from a designated boot device. When you installed the Compaq OpenVMS Alpha operating system, you designated the system disk as the default boot device. Section A.2.2 describes how to change the default boot device.
Alpha computers can boot automatically from the default boot device under the following conditions:
Set the system to boot automatically by performing one of the following steps:
IF ... | THEN ... |
---|---|
the OpenVMS Alpha operating system is running, | go to step 1. |
the OpenVMS Alpha operating system is not running, | go to step 4. |
$ @SYS$SYSTEM:SHUTDOWN |
SYSTEM SHUTDOWN COMPLETE |
>>> INITIALIZE |
>>> SHOW AUTO_ACTION |
>>> SET AUTO_ACTION RESTART |
Use the SET BOOTDEF_DEV command to tell the system which drive you want to boot from (that drive becomes the default boot device). Use the SHOW BOOTDEF_DEV command to display the current default boot device.
Note that when you set this variable, Compaq recommends that you set the operating system boot parameters as well, using the SET BOOT_OSFLAGS command.
At the console prompt (>>>), enter the SET BOOTDEF_DEV command in the following format:
SET BOOTDEF_DEV device-name |
Substitute the device name of the system disk for device-name. For example, to boot from a drive with a device name of DKA400 on a DEC 3000 Alpha series computer, enter the following command and press the Return key:
>>> SET BOOTDEF_DEV DKA400 |
The next time you boot the system, you can enter the BOOT command without specifying a device name (because DKA400 is now the default boot device). For example:
>>> BOOT |
If you have not used the SET BOOTDEF_DEV command to set the drive to boot from and you enter the BOOT command without specifying a device name, the system displays an error message. |
Use the SHOW BOOTDEF_DEV command to find out what drive was specified in the last SET BOOT command. For example:
>>> SHOW BOOTDEF_DEV |
To cancel the drive specified in a previous SET BOOTDEF_DEV command, enter the following command and press the Return key:
>>> SET BOOTDEF_DEV |
This command is not valid on DEC 3000 Alpha series systems. |
By default, when you boot the operating system, the flags parameter is set to 0. If you want to define parameters to enable specific functions during the booting process, use the SET BOOT_OSFLAGS console command.
The following is a list of values you can specify with the SET BOOT_OSFLAGS command:
Hexadecimal Value | System Response |
---|---|
1 | Allows a conversational boot (the system displays the SYSBOOT> prompt). |
2 | Maps XDELTA to a running system. |
4 | Stops the boot procedure at the initial system breakpoint. |
8 | Performs a diagnostic bootstrap. |
10 | Stops the boot procedure at the bootstrap breakpoints. |
20 | Omits header from secondary bootstrap image. |
80 | Prompts for the name of the secondary bootstrap file. |
100 | Halts the system before the secondary bootstrap. |
2000 | Marks corrected read data error pages as bad. |
10000 | Displays extensive, detailed debug messages during the boot process. |
20000 | Displays selected user-oriented messages during the boot process. |
The following examples show how to use the SET BOOT_OSFLAGS command:
>>> SET BOOT_OSFLAGS 0,1 |
>>> SET BOOT_OSFLAGS 1,0 |
>>> SET BOOT_OSFLAGS 0,20007 |
To display the parameters you have just set, use the SHOW BOOT_OSFLAGS command. For example:
>>> SHOW BOOT_OSFLAGS BOOT_OSFLAGS = 0,20007 |
Previous | Next | Contents | Index |