To invoke a full default, custom, or cloned installation of the operating system software, you boot your processor or single-board computer (SBC) from either of these sources:
Operating system software distribution media on CD-ROM
A Remote Installation Services (RIS) server that is set up to serve this version of the operating system
This chapter provides the information necessary for you to perform the user actions shown in Table 4-1.
| After reading this chapter, you will ... | As shown in ... |
| Shut down and halt your processor. | Section 4.2 |
| Locate your processor in the table and use the appropriate boot commands to boot your system off the CD-ROM or network to invoke the full installation procedure. | Table 4-2 |
If you are using a CD-ROM to boot your system, Section B.1 and Section B.2 describe how to load the CD-ROM into a caddy and disk drive.
An automatic reboot feature is available for systems that have unattended installation capability. Refer to Table 4-3 for a list of the systems that support this feature.
Note
Unlike full installations, you do not boot from the distribution media to perform an update installation. Update installations are performed from the command line in single-user mode. Refer to Chapter 2 for information about performing update installations.
If you are booting your system over the network, you are initiating an installation from a remote server. To boot over the network, your processor or SBC must be registered as a client on a Remote Installation Services (RIS) server. Refer to Sharing Software on a Local Area Network for information about setting up a RIS server, loading software into a RIS area, and registering a RIS client.
Caution
Observe the following general guildelines:
You must use additional parameters with the
bootcommand if you are installing a hardware product kit during a full installation. Refer to Section 6.4 for the correctbootcommand parameters to use when installing a hardware product kit.On some systems, console commands return an error if their arguments include other than alphanumeric characters. For example:
>>>set bootdef_dev 1/dka300?2C UNK SYM
If this occurs, enclose the argument in double quotes. For example:
>>>set bootdef_dev "1/dka300"
Do not use double quotes indiscriminately; some systems do not process double quotes in console command arguments.
On systems that support more than one type of operating system, make sure that your
OS_TYPEconsole variable is set tounixbefore you execute thebootcommand.
Follow the instructions in this guide and those provided in your hardware and firmware documentation when you add or upgrade your system hardware. However, if the new hardware option is only supported by the new version of the operating system, you must perform the upgrade in the following sequence:
Update your operating system software to the version that supports the new hardware option.
Upgrade your firmware to the appropriate level for your system and the new version of the operating system.
Follow the instructions in Chapter 6 to install the hardware product kit that supports your new hardware option.
To prepare the hardware for the installation booting process, do the following:
If your system is already running a version of the operating system, you must shut down and halt the processor using a command similar to the following:
#shutdown -h +NN Please log out
In the previous example, the
system is shut down and halted in
NN
minutes and sends
the message
Please log out
to all logged in users.
Refer to the
System Administration
guide or the
shutdown(8)
reference page if you need more information about shutting down a
system.
If you are adding peripheral devices to your system at this time, proceed to the next step.
If you are not connecting additional peripheral devices to your system, go to Step 3.
If you are adding additional peripheral devices, turn off your system.
Connect the peripheral devices while your system is turned off.
Turn on power to the console terminal and all additional peripheral devices; otherwise, the peripheral devices are not automatically configured by your system.
If you connect additional peripherals or controllers after the installation, refer to the System Administration guide for instructions about how to reconfigure your system.
Turn on power to the processor.
The console subsystem prints various
startup and diagnostic messages and ends with the console mode prompt ( >>>
).
Before starting the full installation, make sure your system's firmware has been updated. Firmware update instructions are in Section 1.4.6.
Boot your system from the console mode prompt ( >>>
).
The boot command you enter depends on the processor and whether
you are booting from CD-ROM or over the network.
The DEC 2000 and DEC 7000 servers
can be booted only from CD-ROM.
Note
Be sure to review your console firmware update documentation and perform the firmware update at the appropriate time. If you added peripherals, you may also need to run configuration utilities such as the EISA Configuration Utility (ECU) or the RAID Configuration Utility (RCU).
Locate your processor in Table 4-2 and follow the booting instructions in the corresponding section. After you have booted your processor, proceed to Chapter 5 to continue the default, custom, or cloned installation process.
| Alpha System | Booting Instructions |
| DEC 2000 Server | Section 4.5 |
| DEC 3000 Server | Section 4.6 |
| DEC 4000 Server | Section 4.7 |
| DEC 7000 Server | Section 4.8 |
| AlphaServer 300, 400 | Section 4.9 |
| AlphaServer 800, 1000, 1000A | Section 4.10 |
| AlphaServer 1200, DS20 | Section 4.11 |
| AlphaServer 2000, 2100, 2100A | Section 4.12 |
| AlphaServer 4000, 4100, ES40 | Section 4.13 |
| AlphaServer 8200, 8400, GS60, GS140 | Section 4.14 |
| AlphaStation 200, 250, 255, 400 | Section 4.15 |
| AlphaStation 500, 600, 600A | Section 4.16 |
| Personal Workstation 433au, 500au, 600au; Ultimate Workstation 533au2 | Section 4.17 |
| Professional Workstation XP1000 | Section 4.18 |
| AXPvme, AlphaVME, AXPpci SBCs; PICMG Alpha CPUs | Section 4.19 |
| EB66+, EB164, AlphaPC SBCs | Section 4.20 |
| SBCs and processors supported in hardware releases higher than the current version of the operating system | hardware documentation and release notes |
Note
If you have problems booting your system, refer to the hardware documentation for your particular processor. If the problem is not hardware related, refer to the System Administration guide. This guide provides information about boot options such as booting a generic kernel (
genvmunix) or booting an alternate custom kernel.
Some systems are rebooted automatically during the installation process. This automatic reboot feature is available on systems with unattended installation capability. Table 4-3 lists the systems that support unattended installation.
| Systems with Unattended Installation Capability | |||||
| AlphaServer 800 | AlphaServer 1000 | AlphaServer 1000A | AlphaServer 4000 | AlphaServer 4100 | AlphaServer ES40 |
Table 4-4 shows the required boot devices for booting over the network if your system uses FDDI. Follow the instructions in your hardware owner's guide to update the FDDI firmware before booting over the network.
| Bus Type | Boot Device |
| EISA (Extended Integrated System Architecture) | fra0
[Footnote 8]
|
| PCI (Peripheral Component Interconnect) | fwa0
[Footnote 8] |
| Turbochannel | "#/ez0"
[Footnote 9]
|
| XMI (Extended Memory Interface) | fxa0
[Footnote 8] |
You need the console device name of your CD-ROM drive or your network interface
when you boot your system for a full installation.
Shut down your system to the system
console prompt ( >>>
), and follow the instructions in this
section.
Enter the following command from the system console to display system device information:
>>>show dev
Your output will be similar to one of the following:
In this format, the output is displayed with column headings:
BOOTDEV ADDR DEVTYPE RM/FX DEVNAM REV NUMBYTES ------- ---- ------- ----- ------ --- -------- EZ0A 08-00-2B-38-A1-92 FD0 PC Floppy DISK RM SCSI Devices.. DKA200 A/2/0 DISK FX RZ25 0700 426.25MB DKA400 A/4/0 RODISK RM RRD43 4.5d ....... DKA500 A/5/0 DISK FX RZ25L 0006 535.65MB DKA600 A/6/0 DISK FX RZ28 435E 2.10GB HOST A/7/0 PROC AHA1742A G.2
Look for the line
with the CD-ROM device string
RRD.
In this example, the CD-ROM
device is
RRD43
and its corresponding console device name is
DKA400.
In this format, the output is displayed without column headings:
dka200.2.0.2.0 DKA200 RZ26 T392 dka400.4.0.2.0 DKA400 RRD42 4.5d ewa0.0.0.1.0 EWA0 08-00-2B-39-88-3A pka0.7.0.2.0 PKA0 SCSI Bus ID 7
Look for the line with the
CD-ROM device string
RRD.
In this example, the CD-ROM
device is
RRD42
and its corresponding console device name is
DKA400.
Enter the following command from the system console to display system device information:
>>>show dev
Your output will be similar to one of the following:
In this format, the output is displayed with column headings:
BOOTDEV ADDR DEVTYPE RM/FX DEVNAM REV NUMBYTES ------- ---- ------- ----- ------ --- -------- EZ0A 08-00-2B-38-A1-92 FD0 PC Floppy DISK RM SCSI Devices.. DKA200 A/2/0 DISK FX RZ25 0700 426.25MB DKA400 A/4/0 RODISK RM RRD43 4.5d ....... DKA500 A/5/0 DISK FX RZ25L 0006 535.65MB DKA600 A/6/0 DISK FX RZ28 435E 2.10GB HOST A/7/0 PROC AHA1742A G.2
Look for the line
with your system's network address.
In this example, the Ethernet address is
08-00-2B-38-A1-92
and its corresponding console device name in the
BOOTDEV
column is
EZ0A.
In this format, the output is displayed without column headings:
dka400.4.0.6.0 DKA400 RRD43 2893 dva0.0.0.0.1 DVA0 ewa0.0.0.13.0 EWA0 08-00-2B-3E-B6-C8 pka0.7.0.6.0 PKA0 SCSI Bus ID 7
Look for the line with your system's
network address.
In this example, the Ethernet address is
08-00-2B-38-A1-92
and its corresponding console device name is
EWA0.
The following section describes how to boot the DEC 2000 server from a CD-ROM optical disk. Booting from the network is not supported for the DEC 2000 server.
Before starting the boot procedure, enter the following commands. Each command is echoed by the system when you press Return:
Enter the following command to clear the
boot_osflags
variable to ensure that the kernel takes correct action upon boot:
>>>set boot_osflags ""
Set the
auto_action
variable to
halt.
This halts the system at the console prompt each time the system is turned on, when
the system crashes, or when you press the Halt button.
>>>set auto_action halt
Set the keyboard variable to match the keyboard type on the system.
Use the
help set
command to list the available keyboard types.
>>>set keyboard type
Place the CD-ROM optical disk into a caddy as described in Appendix B.
Use this procedure to boot the system:
Insert the Operating System Volume 1 CD-ROM.
Enter the following command to determine the unit number of the drive for your device:
>>>show dev
The following information is displayed about the devices on your system:
BOOTDEV ADDR DEVTYPE RM/FX DEVNAM REV NUMBYTES ------- ---- ------- ----- ------ --- -------- EZ0A 08-00-2B-38-A1-92 FD0 PC Floppy DISK RM SCSI Devices.. DKA200 A/2/0 DISK FX RZ25 0700 426.25MB DKA400 A/4/0 RODISK RM RRD43 4.5d ....... DKA500 A/5/0 DISK FX RZ25L 0006 535.65MB DKA600 A/6/0 DISK FX RZ28 435E 2.10GB HOST A/7/0 PROC AHA1742A G.2
The numbers under
BOOTDEV
represent the unit number assigned
to each drive on your system:
The letters DK refer to a SCSI disk device.
The third letter (A or B) refers to the SCSI bus designation. Refer to your hardware owner's guide for more details.
The number refers to the drive number.
In the
DEVNAM
column, look for the line with the
CD-ROM device string
RRD.
In the previous display from the
show dev
command, the CD-ROM device is
RRD43.
The device boot string for your system appears in that same line under the BOOTDEV
column as
DKA400.
Enter the
boot
command with the following syntax
to boot from a CD-ROM.
boot
device
For example, to boot the system from CD-ROM drive number 4, enter the following command:
>>>boot dka400
You have completed booting your system. Continue the installation procedure with Chapter 5.
The following sections describe how to boot the DEC 3000 server from a CD-ROM optical disk, from the network, from the SCSI TURBOchannel option card, and from an FDDI network interface.
Before starting the boot procedure, enter the following commands. Each command is echoed by the system when you press Return:
Enter the following command to clear the
boot_osflags
variable to ensure that the kernel takes correct action upon boot:
>>>set boot_osflags ""
Set the
auto_action
variable to
halt.
This halts the system at the console prompt each time the system is turned on, when
the system crashes, or when you press the Halt button.
>>>set auto_action halt
Set the
boot_reset
variable to
on.
This ensures that all devices are initialized prior to booting.
>>>set boot_reset on
Set the
scsi_reset
variable to
4.
This ensures that all devices have adequate time to initialize during the boot sequence.
>>>set scsi_reset 4
Place the CD-ROM optical disk into a caddy as described in Appendix B.
Use the following procedure to boot the system:
Insert the Operating System Volume 1 CD-ROM.
Enter the following command to determine the unit number of the drive for your device:
>>>show dev
The output of the
show dev
command
displays information about the devices on your system:
BOOTDEV ADDR DEVTYPE NUMBYTES RM/FX WP DEVNAM REV ------- ---- ------- -------- ----- -- ------ --- DKA0 A/0/0 DISK 426.25MB FX RZ25 0700 DKA200 A/2/0 DISK 426.25MB FX RZ25 0700 DKA400 A/4/0 DISK ..... RM WP RRD42 4.3d MKA500 A/5/0 TAPE RM TZK10 01B4 ..HostID.. A/6 INIT ..HostID.. B/6 INITR MKB500 B/5/0 TAPE RM TLZ04
The numbers under BOOTDEV represent the unit number assigned to each drive on your system:
The letters DK refer to a SCSI disk device.
The letters MK refer to a SCSI magnetic tape device.
The third letter (A or B) refers to the SCSI bus designation. Refer to your hardware owner's guide for more details.
The number refers to the drive number.
HostID
represents the SCSI id of the host adapter.
In the previous example,
A/6 INIT
represents
INITiator
on bus A, id 6.
In the DEVNAM column, look for the line with the CD-ROM device
string
RRD.
In the previous display from the
show dev
command, the CD-ROM device is
RRD42.
The device
boot string for your system appears in that same line under the BOOTDEV column as
DKA400.
Enter the
boot
command with the following syntax
to boot from a CD-ROM.
boot
device
For example, to boot the system from the CD-ROM drive with console
device name
dka400, enter the following command:
>>>boot dka400
You have completed booting your system. Continue the installation procedure with Chapter 5.
To boot your system from the network, make sure it is registered as a client on a RIS server. Refer to Sharing Software on a Local Area Network for information on registering a client.
When booting from a RIS server, the system uses the
bootp
protocol.
Enter the following command to boot your system over the network:
>>>boot ez0
Some system information is displayed by the installation software followed by the memory and hardware configurations.
If your initial network boot fails, enter
init
at the console
prompt.
If you encounter other problems during the RIS install, refer to
Sharing Software on a Local Area Network.
You have completed booting your system. Continue the installation procedure with Chapter 5.
To boot from the dual SCSI TURBOchannel option card (PMAZB or PMAZC), complete the following steps:
Determine which controllers and devices are configured on your system by entering the following command at the console prompt:
>>>show conf
Your system displays output similar to the following (the output differs depending on your system configuration):
DEC 3000 - M500
Compaq Computer CorporationVPP PAL X5.37-82000101/OSF PAL X1.28-82000201 -
Built on 13-DEC-1996 13:39:58.02
TCINFO DEVNAM DEVSTAT
------ -------- --------
CPU OK KN15-AA -V2.0-S1F4-I039-sV1.0-DECchip 21064
P3.0
ASIC OK
MEM OK
8
CXT OK
7
NVR OK
SCC OK
NI OK
ISDN OK
6
SCSI OK
3-PMAF-AA TC3
2-PMAZ-AA TC2
1-PMAZB-AA TC1
0-PMTNV-AA TC0
The numbers under the TCINFO column (and the entries in the DEVNAM column) represent the unit number assigned to the PMAZB or PMAZC option card.
Determine the number of your boot device by entering a command with the following syntax:
t
tcslot_number cnfg
For example, to determine the device number of a disk on a PMAZB option card, enter the following command:
>>t tc1 cnfg
A table similar to the following is displayed:
DEC PMAZB-AA V1.0 (Dual SCSI [53C96]) BOOTDEV ADDR DEVTYPE NUMBYTES RM/FX WP DEVNAM REV ------- ---- ------- -------- ----- -- ------ --- DKA200 A/2/0 DISK 426MB FX RZ25 0700 (rz200A) DKA400 A/4/0 RODISK 409MB RM WP RRD42 4.3d (rz400A) ..HostID.. A/7 INITR ..HostID.. B/7 INITR
To boot from the PMAZB (or PMAZC) option card, enter the
boot
command with the following syntax:
boot
"slot_number/device_number"
For example, to boot from disk number 4 on the PMAZB option card located in slot 1, enter the following command:
>>>b "1/dka400"
You have completed booting your system. Continue the installation procedure with Chapter 5.
Booting over an FDDI network interface is supported for DEFTA and CRE-DEFTA devices.
To boot from an FDDI network interface device, find the device names as described
in
Section 4.6.4.
For example, a DEFTA device appears
as
PMAF-FA
when you use the
show conf
command.
Identify the slot number and enter the following commands to boot from a RIS server
using the
bootp
protocol:
>>>b "1/ez0"
You have completed booting your system. Continue the installation procedure with Chapter 5.
The following sections describe how to boot the DEC 4000 server from a CD-ROM optical disk and from the network.
Before starting the boot procedure, complete the following steps:
Enter the following command to clear the
boot_osflags
variable to ensure that the kernel takes correct action upon boot:
>>>set boot_osflags ""
Set the
auto_action
variable to
halt.
This halts the system at the console prompt each time the system is turned on, when
the system crashes, or when you press the Halt button.
>>>set auto_action halt
Enter the
init
command with the following syntax:
>>>init
If your CD-ROM optical disk is not already in a caddy, follow the instructions in Appendix B.
Use the following procedure to boot the system:
Insert the Operating System Volume 1 CD-ROM.
Enter the following command to determine the unit number of the drive for your device:
>>>show dev
A device information table similar to the following is displayed:
dka0.0.0.0.0 DKA0 RZ73 dkb0.0.0.1.0 DKB0 RZ73 dkc0.0.0.2.0 DKC0 RZ26 dkc100.1.0.2.0 DKC100 RZ26 dkc200.2.0.2.0 DKC200 RZ26 dkc300.3.0.2.0 DKC300 RZ26 dke100.1.0.4.0 DKE100 RRD42 mka500.0.0.0.0 MKA500 TLZ04 mke0.0.0.4.0 MKE0 TZ85 eza0.0.0.6.0 EZA0 08-00-2B-2C-CE-DE ezb0.0.0.7.0 EZB0 08-00-2B-2C-CE-DF p_d0.7.0.3.0 Bus ID 7 pka0.7.0.0.0 PKA0 SCSI Bus ID 7 pkb0.7.0.1.0 PKB0 SCSI Bus ID 7 pkc0.7.0.2.0 PKC0 SCSI Bus ID 7 pke0.7.0.4.0 PKE0 SCSI Bus ID 7
The second column shows the numbers assigned to each drive:
The letters DK refer to a SCSI disk or CD-ROM device.
The letters MK refer to a SCSI magnetic tape device.
The third letter (A, B, C, D, or E) refers to the SCSI or DSA bus designation. Refer to your hardware owner's guide for more details.
The number refers to the drive number.
In the third column, look for the line with the CD-ROM device
string
RRD.
In the previous display from the
show dev
command, the CD-ROM device is
RRD42.
The device
boot string for your system appears in that same line.
The device boot string begins
with the letters
DKE.
Enter the
boot
command with the following syntax
to boot from a CD-ROM:
boot
device
For example, to boot the system from the CD-ROM drive with console
device name
dke400, enter the following command:
>>>boot dke100
Output similar to the following is displayed:
(boot dke100.1.0.4.0) block 0 of dke100.1.0.4.0 is a valid boot block reading 16 blocks from dke100.1.0.4.0 bootstrap code read in base = 1ee000, image_start = 0, image_bytes = 2000 initializing HWRPB at 2000 initializing page table at 1e0000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code OSF boot - Fri Dec 17 15:49:49 EST 1999
You have completed booting your system. Continue the installation procedure with Chapter 5.
To boot your system over the network, make sure it is registered as a client on a RIS server. Refer to Sharing Software on a Local Area Network for information on registering a client.
The
device
parameter is the network device from which you
want to boot.
The DEC 4000 server supports two network adapters:
eza0
and
ezb0.
Set your device protocols to boot from a RIS server.
Use the following command syntax to boot your system over the network:
set
device_protocolsbootp
For example, if the device you are booting from with the
bootp
protocol is
eza0, enter the following commands:
>>>set eza0_protocols bootp>>>boot eza0
Some system information is displayed by the installation software followed by the memory and hardware configurations.
If your initial network boot fails, enter
init
at the console
prompt.
If you encounter other problems during the RIS installation, refer to
Sharing Software on a Local Area Network.
You have completed booting your system. Continue the installation procedure with Chapter 5.
The following instructions apply to DEC 4000 systems equipped with the Prestoserve option.
The DEC 4000 system console provides the
prcache
command
to support the Prestoserve option (NVRAM).
Refer to the hardware documentation for
a description of this command.
You have completed booting your system. Continue the installation procedure with Chapter 5.
The following sections describe how to boot the DEC 2000 and DEC 7000 server from a CD-ROM optical disk and from the network.
Before starting the boot procedure, enter the following commands. Each command is echoed by the system when you press Return:
Enter the following command to clear the
boot_osflags
variable to ensure that the kernel takes correct action upon boot:
>>>set boot_osflags ""
Set the
auto_action
variable to
halt.
This halts the system at the console prompt each time the system is turned on, when
the system crashes, or when you press the Halt button.
>>>set auto_action halt
Set the keyboard variable to match the keyboard type on the system.
Use the
help set
command to list the available keyboard types.
>>>set keyboard type
Place the CD-ROM optical disk into a caddy as described in Appendix B.
Use this procedure to boot the system:
Insert the Operating System Volume 1 CD-ROM.
Enter the following command to determine the unit number of the drive for your device:
>>>show dev
The following information is displayed about the devices on your system:
BOOTDEV ADDR DEVTYPE RM/FX DEVNAM REV NUMBYTES ------- ---- ------- ----- ------ --- -------- EZ0A 08-00-2B-38-A1-92 FD0 PC Floppy DISK RM SCSI Devices.. DKA200 A/2/0 DISK FX RZ25 0700 426.25MB DKA400 A/4/0 RODISK RM RRD43 4.5d ....... DKA500 A/5/0 DISK FX RZ25L 0006 535.65MB DKA600 A/6/0 DISK FX RZ28 435E 2.10GB HOST A/7/0 PROC AHA1742A G.2
The numbers under BOOTDEV represent the unit number assigned to each drive on your system:
The letters DK refer to a SCSI disk device.
The third letter (A or B) refers to the SCSI bus designation. Refer to your hardware owner's guide for more details.
The number refers to the drive number.
In the DEVNAM column, look for the line with the CD-ROM device
string
RRD.
In the previous display from the
show dev
command, the CD-ROM device is
RRD43.
The device
boot string for your system appears in that same line under the BOOTDEV column as
DKA400.
Enter the
boot
command with the following syntax
to boot from a CD-ROM.
boot
device
For example, to boot the system from the CD-ROM drive with console
device name
dka400, enter the following command:
>>>boot dka400
You have completed booting your system. Continue the installation procedure with Chapter 5.
Booting from the network is not supported for the DEC 7000 servers.
The following sections describe how to boot an AlphaServer 300 or AlphaServer 400 server from a CD-ROM and from the network.
Before starting the boot procedure on an AlphaServer 300 or AlphaServer 400 server, complete the following steps:
Enter the following command to clear the
boot_osflags
variable to ensure that the kernel takes correct action upon boot:
>>>set boot_osflags ""
Set the
auto_action
variable to
halt.
This halts the system at the console prompt each time the system is turned on, when
the system crashes, or when you press the
Halt
button.
>>>set auto_action halt
If your CD-ROM is not already in a caddy, follow the instructions in Appendix B.
Follow this procedure to boot the system:
Insert the Operating System Volume 1 CD-ROM.
Enter the init command with the following syntax:
>>>init
Enter the boot command with the following syntax to boot from a CD-ROM:
boot
device
For example, to boot the system from the CD-ROM drive with console
device name
dka400, enter the following command:
>>>boot dka400
Output similar to the following is displayed:
(boot dka400.4.0.6.0) block 0 of dka400.4.0.6.0 is a valid boot block reading 16 blocks from dka400.4.0.6.0 bootstrap code read in base = 11e000, imagestart = 0, imagebytes = 2000 initializing HWRPB at 2000 initializing page table at 110000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code OSF boot - Fri Dec 17 17:18:57 EST 1999
You have completed booting your system. Continue the installation procedure with Chapter 5.
To boot your system over the network, make sure it is registered as a client on a RIS server. Refer to Sharing Software on a Local Area Network for information about registering a client.
The device parameter is the network device from which you want to boot.
The
AlphaServer 300 and AlphaServer 400 servers support two network adapters:
ewa0
and
ena0.
Use the following command syntax to boot your system over the network:
set
device_protocolsbootp
set
device_inet_initbootp
For example, if the device you are booting from with the
bootp
protocol is
ewa0, enter the following commands:
>>>set ewa0_protocols bootp>>>set ewa0_inet_init bootp>>>boot ewa0
Some system information is displayed by the installation software followed by the memory and hardware configurations.
If your initial network boot fails, enter
init
at the console
prompt.
If you encounter other problems during the RIS installation, refer to
Sharing Software on a Local Area Network
for more information.
You have completed booting your system. Continue the installation procedure with Chapter 5.
This section provides instructions for booting AlphaServer 800, 1000, and 1000A servers.
The
bus_probe_algorithm
console environment variable must
be set to
new.
To verify that the
bus_probe_algorithm
environment variable is set to
new, enter the following
console firmware command:
>>>show bus_probe_algorithm
If the environment variable is set to
old, set the variable to
new
and initialize the console
as shown in the following example:
>>>set bus_probe_algorithm new>>>init
Before starting the boot procedure on an AlphaServer 800, 1000, or 1000A server, complete the following steps:
Enter the following command to clear the
boot_osflags
variable to ensure that the kernel takes correct action upon boot:
>>>set boot_osflags ""
Note
If your system has unattended installation capability, the system will reboot automatically from the newly installed disks after the software subsets are loaded during the installation process. However, if you want to halt the system immediately after the software subsets are loaded (that is, you do not want to perform an automatic reboot), enter the following command:
>>>set boot_osflags h
Remember to use this command only if your system has unattended installation capability. See Table 4-3 for a list of the systems that support this capability.
Set the
auto_action
variable to
halt.
This halts the system at the console prompt each time it is turned on, when it crashes,
or when you press the Halt button.
>>>set auto_action halt
Set the
boot_file
variable.
This ensures that
an alternate boot file is not set.
>>>set boot_file
Follow these steps to boot AlphaServer 800, 1000, or 1000A servers from a CD-ROM:
Insert the Operating System Volume 1 CD-ROM.
Enter the following command to determine the unit number of the drive for your device:
>>>show device
Output similar to the following is displayed by the
show device
command:
dka400.4.0.6.0 DKA400 RRD43 2893 dva0.0.0.0.1 DVA0 ewa0.0.0.13.0 EWA0 08-00-2B-3E-B6-C8 pka0.7.0.6.0 PKA0 SCSI Bus ID 7
The second column shows the numbers assigned to each drive:
The letters DK refer to a SCSI disk or CD-ROM device.
The third letter (A, B, C, D, or E) refers to the SCSI bus designation. Refer to your hardware owner's guide for more details.
The number refers to the drive number.
In the third column, look for the line with the CD-ROM device
string
RRD.
In the previous example, the CD-ROM device is
RRD43.
The device boot string for your system appears in that same line.
The device boot string begins with the letters
DKA.
Enter the
boot
command and the appropriate boot
device string for your system.
For example:
>>>boot dka400
To boot an AlphaServer 800, 1000, or 1000A server over the network, make sure it is registered as a client of a RIS server. Refer to Sharing Software on a Local Area Network for information on registering a client.
Use the
show device
command to determine which network adapter
(such as
ewa
or
era) is in use:
>>>show device
Output similar to
the following is displayed by the
show device
command:
dka400.4.0.6.0 DKA400 RRD43 2893 dva0.0.0.0.1 DVA0 ewa0.0.0.13.0 EWA0 08-00-2B-3E-B6-C8 pka0.7.0.6.0 PKA0 SCSI Bus ID 7
Use the following command syntax to boot your system over the network:
set
device_inet_initbootp
set
device_protocolsbootp
For example, if the device you are booting from with the
bootp
protocol is
ewa0, enter the following commands:
>>>set ewa0_inet_init bootp>>>set ewa0_protocols bootp>>>boot -fi "" ewa0
You have completed booting your system. Continue the installation procedure with Chapter 5.
This section provides instructions for booting AlphaServer 1200 and DS20 servers.
The
bus_probe_algorithm
console environment variable must
be set to
new.
To verify that the
bus_probe_algorithm
environment variable is set to
new, enter the following
console firmware command:
>>>show bus_probe_algorithm
If the environment variable is set to
old, set the variable to
new
and initialize the console
as shown in the following example:
>>>set bus_probe_algorithm new>>>init
Before starting the boot procedure on an AlphaServer 1200 or DS20 server, complete the following steps:
Enter the following command to clear the
boot_osflags
variable to ensure that the kernel takes correct action upon boot:
>>>set boot_osflags ""
Note
If your system has unattended installation capability, the system will reboot automatically from the newly installed disks after the software subsets are loaded during the installation process. However, if you want to halt the system immediately after the software subsets are loaded (that is, you do not want to perform an automatic reboot), enter the following command:
>>>set boot_osflags h
Remember to use this command only if your system has unattended installation capability. See Table 4-3 for a list of the systems that support this capability.
Set the
auto_action
variable to
halt.
This halts the system at the console prompt each time it is turned on, when it crashes,
or when you press the Halt button.
>>>set auto_action halt
Set the
boot_file
variable.
This ensures that
an alternate boot file is not set.
>>>set boot_file
Follow these steps to boot AlphaServer 1200 or DS20 servers from a CD-ROM:
Insert the Operating System Volume 1 CD-ROM.
Enter the following command to determine the unit number of the drive for your device:
>>>show device
Output similar to the following is displayed by the
show device
command:
dka400.4.0.6.0 DKA400 RRD43 2893 dva0.0.0.0.1 DVA0 ewa0.0.0.13.0 EWA0 08-00-2B-3E-B6-C8 pka0.7.0.6.0 PKA0 SCSI Bus ID 7
The second column shows the numbers assigned to each drive:
The letters DK refer to a SCSI disk or CD-ROM device.
The third letter (A, B, C, D, or E) refers to the SCSI bus designation. Refer to your hardware owner's guide for more details.
The number refers to the drive number.
In the third column, look for the line with the CD-ROM device
string
RRD.
In the previous example, the CD-ROM device is
RRD43.
The device boot string for your system appears in that same line.
The device boot string begins with the letters
DKA.
Enter the
boot
command and the appropriate boot
device string for your system.
For example:
>>>boot dka400
To boot an AlphaServer 1200 or DS20 server over the network, make sure it is registered as a client of a RIS server. Refer to Sharing Software on a Local Area Network for information on registering a client.
Use the
show device
command to determine which network adapter
(such as
ewa
or
era) is in use:
>>>show device
Output similar to
the following is displayed by the
show device
command:
dka400.4.0.6.0 DKA400 RRD43 2893 dva0.0.0.0.1 DVA0 ewa0.0.0.13.0 EWA0 08-00-2B-3E-B6-C8 pka0.7.0.6.0 PKA0 SCSI Bus ID 7
Use the following command syntax to boot your system over the network:
set
device_inet_initbootp
set
device_protocolsbootp
For example, if the device you are booting from with the
bootp
protocol is
ewa0, enter the following commands:
>>>set ewa0_inet_init bootp>>>set ewa0_protocols bootp>>>boot -fi an ewa0
You have completed booting your system. Continue the installation procedure with Chapter 5.
The following sections describe how to boot AlphaServer 2000, 2100, and 2100A servers from a CD-ROM and from the network.
The
bus_probe_algorithm
console environment variable must
be set to
new.
To verify that the
bus_probe_algorithm
environment variable is set to
new, enter the following
console firmware command:
>>>show bus_probe_algorithm
If the environment variable is set to
old, set the variable to
new
and initialize the console
as shown in the following example:
>>>set bus_probe_algorithm new>>>init
Before starting the boot procedure, complete the following steps:
Enter the following command to clear the
boot_osflags
variable to ensure that the kernel takes correct action upon boot:
>>>set boot_osflags ""
Note
If your system has unattended installation capability, the system will reboot automatically from the newly installed disks after the software subsets are loaded during the installation process. However, if you want to halt the system immediately after the software subsets are loaded (that is, you do not want to perform an automatic reboot), enter the following command:
>>>set boot_osflags h
Remember to use this command only if your system has unattended installation capability. See Table 4-3 for a list of the systems that support this capability.
Set the
auto_action
variable to
halt.
This halts the system at the console prompt each time the system is turned on, when
the system crashes, or when you press the Halt button.
>>>set auto_action halt
Enter the
init
command with the following syntax:
>>>init
If your CD-ROM is not already in a caddy, follow the instructions in Appendix B.
Follow this procedure to boot the system:
Insert the Operating System Volume 1 CD-ROM.
Enter the following command to determine the unit number of the drive for your device:
>>>show dev
A device information table similar to the following is displayed:
dka0.0.0.0.0 DKA0 RZ28 dkb0.0.0.1.0 DKB0 RZ28 dkc0.0.0.2.0 DKC0 RZ26 dkc100.1.0.2.0 DKC100 RZ26 dkc200.2.0.2.0 DKC200 RZ26 dkc300.3.0.2.0 DKC300 RZ26 dke100.1.0.4.0 DKE100 RRD43 mka500.0.0.0.0 MKA500 TLZ04 mke0.0.0.4.0 MKE0 TZ85 ewa0.0.0.6.0 EWA0 08-00-2B-2C-CE-DE ewb0.0.0.7.0 EWB0 08-00-2B-2C-CE-DF p_d0.7.0.3.0 Bus ID 7 pka0.7.0.0.0 PKA0 SCSI Bus ID 7 pkb0.7.0.1.0 PKB0 SCSI Bus ID 7 pkc0.7.0.2.0 PKC0 SCSI Bus ID 7 pke0.7.0.4.0 PKE0 SCSI Bus ID 7
The second column shows the numbers assigned to each drive:
The letters DK refer to a SCSI disk or CD-ROM device.
The letters MK refer to a SCSI magnetic tape device.
The third letter (A, B, C, D, or E) refers to the SCSI or DSA bus designation. Refer to your hardware owner's guide for more details.
The number refers to the drive number.
In the third column, look for the line with the CD-ROM device
string
RRD.
In the previous example, the CD-ROM device is
RRD43.
The device boot string for your system appears in that same line.
The device boot string begins with the letters
DKE.
Enter the
boot
command with the following syntax
to boot from a CD-ROM:
boot
device
For example, to boot the system from the CD-ROM drive with console
device name
dke400, enter the following command:
>>>boot dke100
Output similar to the following is displayed:
(boot dke100.1.0.4.0) block 0 of dke100.1.0.4.0 is a valid boot block reading 16 blocks from dke100.1.0.4.0 bootstrap code read in base = 1ee000, image_start = 0, image_bytes = 2000 initializing HWRPB at 2000 initializing page table at 1e0000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code OSF boot - Fri Dec 17 15:49:49 EST 1999
You have completed booting your system. Continue the installation procedure with Chapter 5.
To boot your system over the network, make sure it is registered as a client on a RIS server. Refer to Sharing Software on a Local Area Network for information on registering a client.
The
device
parameter is the network device from which you
want to boot.
AlphaServer 2000, 2100, and 2100A servers support two network adapters:
ewa0
and
ewb0.
Use the following command syntax to boot your system over the network:
set
device _protocolsbootp
set
device _inet_initbootp
For example, if the device you are booting from with the
bootp
protocol is
ewa0, enter the following commands:
>>>set ewa0_protocols bootp>>>set ewa0_inet_init bootp>>>boot ewa0
Some system information is displayed by the installation software followed by the memory and hardware configurations.
If your initial network boot fails, enter
init
at the console
prompt.
If you encounter other problems during the RIS install, refer to
Sharing Software on a Local Area Network.
You have completed booting your system. Continue the installation procedure with Chapter 5.
These instructions apply to AlphaServer 2000, 2100, and 2100A servers equipped with the Prestoserve option.
AlphaServer 2000, 2100, and 2100A system consoles provide the
prcache
command to support the Prestoserve option (NVRAM).
Refer to your hardware
owner's guide for a description of this command.
You have completed booting your system. Continue the installation procedure with Chapter 5.
The following sections describe how to boot AlphaServer 4000, 4100, and ES40 servers from a CD-ROM and from the network.
The
bus_probe_algorithm
console environment variable must
be set to
new.
To verify that the
bus_probe_algorithm
environment variable is set to
new, enter the following
console firmware command:
>>>show bus_probe_algorithm
If the environment variable is set to
old, set the variable to
new
and initialize the console
as shown in the following example:
>>>set bus_probe_algorithm new>>>init
Before starting the boot procedure, complete the following steps:
Enter the following command to clear the
boot_osflags
variable to ensure that the kernel takes correct action upon boot:
>>>set boot_osflags ""
Note
If your system has unattended installation capability, the system will reboot automatically from the newly installed disks after the software subsets are loaded during the installation process. However, if you want to halt the system immediately after the software subsets are loaded (that is, you do not want to perform an automatic reboot), enter the following command:
>>>set boot_osflags h
Remember to use this command only if your system has unattended installation capability. See Table 4-3 for a list of the systems that support this capability.
Set the
auto_action
variable to
halt.
This halts the system at the console prompt each time the system is turned on, when
the system crashes, or when you press the Halt button.
>>>set auto_action halt
Enter the
init
command with the following syntax:
>>>init
If your CD-ROM optical disk is not already in a caddy, follow the instructions in Appendix B.
Follow this procedure to boot the system:
Insert the Operating System Volume 1 CD-ROM.
Enter the following command to determine the unit number of the drive for your device:
>>>show dev
A device information table similar to the following is displayed:
dka0.0.0.0.0 DKA0 RZ28 dkb0.0.0.1.0 DKB0 RZ28 dkc0.0.0.2.0 DKC0 RZ26 dkc100.1.0.2.0 DKC100 RZ26 dkc200.2.0.2.0 DKC200 RZ26 dkc300.3.0.2.0 DKC300 RZ26 dke100.1.0.4.0 DKE100 RRD43 mka500.0.0.0.0 MKA500 TLZ04 mke0.0.0.4.0 MKE0 TZ85 ewa0.0.0.6.0 EWA0 08-00-2B-2C-CE-DE ewb0.0.0.7.0 EWB0 08-00-2B-2C-CE-DF p_d0.7.0.3.0 Bus ID 7 pka0.7.0.0.0 PKA0 SCSI Bus ID 7 pkb0.7.0.1.0 PKB0 SCSI Bus ID 7 pkc0.7.0.2.0 PKC0 SCSI Bus ID 7 pke0.7.0.4.0 PKE0 SCSI Bus ID 7
The second column shows the numbers assigned to each drive:
The letters DK refer to a SCSI disk or CD-ROM device.
The letters MK refer to a SCSI magnetic tape device.
The third letter (A, B, C, D, or E) refers to the SCSI or DSA bus designation. Refer to your hardware owner's guide for more details.
The number refers to the drive number.
In the third column, look for the line with the CD-ROM device
string
RRD.
In the previous example, the CD-ROM device is
RRD43.
The device boot string for your system appears in that same line.
The device boot string begins with the letters
DKE.
Enter the
boot
command with the following syntax
to boot from a CD-ROM:
boot
device
For example, to boot the system from the CD-ROM drive with console
device name
dke400, enter the following command:
>>>boot dke100
Output similar to the following is displayed:
(boot dke100.1.0.4.0) block 0 of dke100.1.0.4.0 is a valid boot block reading 16 blocks from dke100.1.0.4.0 bootstrap code read in base = 1ee000, image_start = 0, image_bytes = 2000 initializing HWRPB at 2000 initializing page table at 1e0000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code OSF boot - Fri Dec 17 15:49:49 EST 1999
You have completed booting your system. Continue the installation procedure with Chapter 5.
To boot your system over the network, make sure it is registered as a client on a RIS server. Refer to Sharing Software on a Local Area Network for information on registering a client.
The
device
parameter is the network device from which you
want to boot.
The AlphaServer 4000, 4100, and ES40 servers support two network adapters:
ewa0
and
ewb0.
Use the following command syntax to boot your system over the network:
set
device_protocolsbootp
set
device_inet_initbootp
For example, if the device you are booting from with the
bootp
protocol is
ewa0, enter the following commands:
>>>set ewa0_protocols bootp>>>set ewa0_inet_init bootp>>>boot -fl a ewa0
To stop the autoreboot feature on the AlphaServer 4000, 4100, or ES40 server, enter the following command:
>>>boot -fl ah ewa0
Some system information is displayed by the installation software followed by the memory and hardware configurations.
If your initial network boot fails, enter
init
at the console
prompt.
If you encounter other problems during the RIS installation, refer to
Sharing Software on a Local Area Network.
You have completed booting your system. Continue the installation procedure with Chapter 5.
These instructions apply to AlphaServer 4000, 4100, and ES40 servers equipped with the Prestoserve option.
The AlphaServer 4000, 4100, and ES40 system consoles provide the
prcache
command to support the Prestoserve option (NVRAM).
Refer to hardware documentation
for a description of this command.
You have completed booting your system. Continue the installation procedure with Chapter 5.
The following sections describe how to boot AlphaServer 8200, 8400, GS60, and GS140 servers from a CD-ROM optical disk and from RIS.
Note
The AlphaServer GS60 and AlphaServer GS140 are upgrades of the AlphaServer 8200 and AlphaServer 8400, respectively, with the Alpha 21264 (EV6) processor chip.
The displays in this section reflect AlphaServer 8200 and AlphaServer 8400 systems, but the same examples and descriptions apply to AlphaServer GS60 and AlphaServer GS140 systems. Only the identification line at the bottom of the display is different.
Before starting the boot procedure, complete the following steps:
Enter the following command to clear the
boot_osflags
variable to ensure that the kernel takes correct action upon boot:
>>>set boot_osflags ""
Note
If your system has unattended installation capability, the system will reboot automatically from the newly installed disks after the software subsets are loaded during the installation process. However, if you want to halt the system immediately after the software subsets are loaded (that is, you do not want to perform an automatic reboot), enter the following command:
>>>set boot_osflags h
Remember to use this command only if your system has unattended installation capability. See Table 4-3 for a list of the systems that support this capability.
Set the
auto_action
variable to
halt.
This halts the system at the console prompt each time the system is turned on, when
the system crashes, or when you press the Halt button.
>>>set auto_action halt
Set the
boot_reset
variable to
on.
This must be done if you need to reboot the generic kernel (genvmunix)
at any time to reconfigure your system for additional peripherals.
>>>set boot_reset on
Set the
os_type
variable to
unix:
>>>set os_type unix
Set the
console
variable to
serial:
>>>set console serial
If your CD-ROM optical disk is not already in a caddy, follow the instructions in Appendix B.
Use the following procedure to boot the system:
Insert the Operating System Volume 1 CD-ROM.
Enter the following command to determine the unit number of the drive for your device:
>>>show dev
A display appears showing information about the devices on your system. For example:
dka0.0.0.5.0 DKA0 RZ73 dkb4.4.1.14.0 DKB400 RRD43
The numbers in the second column are the unit numbers assigned to each drive on your system:
The letters DK refer to a SCSI CD-ROM or disk device.
The third letter (A, B, C, D, or E) refers to the SCSI bus designation. Refer to your hardware owner's guide for more details.
The numbers refer to the drive number.
In the third column, look for the line with the CD-ROM device
string
RRD.
In the previous example, the CD-ROM device is
RRD43.
The device boot string for your system appears in that same line.
The device boot string begins with the letters
DKB.
Enter the
boot
command with the following syntax
to boot from a CD-ROM:
boot
device-number
For example, to boot the system from the CD-ROM drive with console
device name
dkb400, enter the following command:
>>>boot dkb400
Output similar to the following is displayed:
Initializing...
F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE #
A M M . . . . . P TYP
o + + . . . . . + ST1
. . . . . . . . B BPD
o + + . . . . . + ST2
. . . . . . . . B BPD
+ + + . . . . . + ST3
. . . . . . . . B BPD
+ . + . + . + . . + . . . . C0 XMI +
.
.
.
. A0 B0 . . . . . LV
. 256 64 . . . . . 320Mb
Firmware Rev = V2.3 SROM Rev = V2.0 SYS SN = GA12345678
Booting...
Connecting to boot device dkb400
.
.
.
You have completed booting your system. Continue the installation procedure with Chapter 5.
To boot your system over the network, make sure it is registered as a client on a RIS server. Refer to Sharing Software on a Local Area Network for information on registering a client.
The
device
parameter is the network device from which you
want to boot.
The AlphaServer 8200, 8400, GS60, and GS140 servers support two network
adapters:
ewa0
and
ewb0.
Note
RIS installations of this version of the operating system are not supported on AlphaServer 8200, 8400, GS60, and GS140 servers with XMI Ethernet devices.
Use the following command syntax to boot your system over the network:
set
device_protocolsbootp
set
device_inet_initbootp
For example, if the device you are booting from with the
bootp
protocol is
ewa0, enter the following commands:
>>>show net>>>set ewa0_protocols bootp>>>set ewa0_inet_init bootp>>>boot -fl a ewa0
Some system information is displayed by the installation software followed by the memory and hardware configurations.
If your initial network boot fails, enter
init
at the console
prompt.
If you encounter other problems during the RIS installation, refer to
Sharing Software on a Local Area Network.
You have completed booting your system. Continue the installation procedure with Chapter 5.
The following sections describe how to boot AlphaStation 200, 250, 255, and 400 workstations from a CD-ROM optical disk and from a RIS server.
Before starting the boot procedure on an AlphaStation 200, 250, 255, or 400 workstation, complete the following steps:
Enter the following command to clear the
boot_osflags
variable to ensure that the kernel takes correct action upon boot:
>>>set boot_osflags ""
Set the
auto_action
variable to
halt.
This halts the system at the console prompt each time the system is turned on, when
the system crashes, or when you press the
Halt
button.
>>>set auto_action halt
Enter the init command with the following syntax:
>>>init
If your CD-ROM optical disk is not already in a caddy, follow the instructions in Appendix B.
Follow this procedure to boot the system:
Insert the Operating System Volume 1 CD-ROM.
Enter the following command to determine the unit number of the drive for your device:
>>>show dev
A device information table similar to the following is displayed:
dka0.0.0.6.0 DKA0 RZ25L 0003 dka100.1.0.6.0 DKA100 RZ26 T386 dka400.4.0.6.0 DKA400 RRD43 2893 dva0.0.0.0.1 DVA0 ewa0.0.0.11.0 EWA0 08-00-2B-E2-74-32 pka0.7.0.6.0 PKA0 SCSI Bus ID 7
The second column shows the numbers assigned to each drive:
The letters DK refer to a SCSI disk or CD-ROM device.
The third letter (A, B, C, D, or E) refers to the SCSI bus designation. Refer to your hardware owner's guide for more details.
The number refers to the drive number.
In the third column, look for the line with the CD-ROM device
string
RRD.
In the previous example, the CD-ROM device is
RRD43.
The device boot string for your system appears in that same line.
The device boot string begins with the letters
DKA.
Enter the boot command with the following syntax to boot from a CD-ROM:
boot
device
For example, to boot the system from the CD-ROM drive with console
device name
dka400, enter the following command:
>>>boot dka400
Output similar to the following is displayed:
(boot dka400.4.0.6.0) block 0 of dka400.4.0.6.0 is a valid boot block reading 16 blocks from dka400.4.0.6.0 bootstrap code read in base = 11e000, imagestart = 0, imagebytes = 2000 initializing HWRPB at 2000 initializing page table at 110000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code OSF boot - Fri Dec 17 15:49:49 EST 1999
You have completed booting your system. Continue the installation procedure with Chapter 5.
To boot your system over the network, make sure it is registered as a client on a RIS server. Refer to Sharing Software on a Local Area Network for information about registering a client.
The device parameter is the network device from which you want to boot.
The
AlphaStation 200, 250, 255, and 400 workstations support two network adapters:
ewa0
and
ena0.
Use the following command syntax to boot your system over the network:
set
device_protocolsbootp
set
device_inet_initbootp
For example, if the device you are booting from with the
bootp
protocol is
ewa0, enter the following commands:
>>>set ewa0_protocols bootp>>>set ewa0_inet_init bootp>>>boot ewa0
Some system information is displayed by the installation software followed by the memory and hardware configurations.
If your initial network boot fails, enter
init
at the console
prompt.
If you encounter other problems during the RIS installation, refer to
Sharing Software on a Local Area Network
for more information.
You have completed booting your system. Continue the installation procedure with Chapter 5.
This section provides instructions for booting AlphaStation 500, 600, and 600A processors.
Before starting the boot procedure on AlphaStation 500, 600, and 600A processors, complete the following steps:
Enter the following command to clear the
boot_osflags
variable to ensure that the kernel takes correct action upon boot:
>>>set boot_osflags ""
Set the
auto_action
variable to
halt.
This halts the system at the console prompt each time it is turned on, when it crashes,
or when you press the Halt button.
>>>set auto_action halt
Set the
boot_file
variable.
This ensures that
an alternate boot file is not set.
>>>set boot_file
Follow these steps to boot AlphaStation 500, 600, and 600A processors from a CD-ROM optical disk:
Insert the Operating System Volume 1 CD-ROM.
Enter the following command to determine the unit number of the drive for your device:
>>>show device
Output similar to the following is displayed by the
show device
command:
dka400.4.0.6.0 DKA400 RRD43 2893 dva0.0.0.0.1 DVA0 ewa0.0.0.13.0 EWA0 08-00-2B-3E-B6-C8 pka0.7.0.6.0 PKA0 SCSI Bus ID 7
The second column shows the numbers assigned to each drive:
The letters DK refer to a SCSI disk or CD-ROM device.
The third letter (A, B, C, D, or E) refers to the SCSI bus designation. Refer to your hardware owner's guide for more details.
The number refers to the drive number.
In the third column, look for the line with the CD-ROM device
string
RRD.
In the previous example, the CD-ROM device is
RRD43.
The device boot string for your system appears in that same line.
The device boot string begins with the letters
DKA.
Enter the
boot
command and the appropriate boot
device string for your system.
For example, to boot the system from the CD-ROM
drive with console device name
dka400, enter the following command:
>>>boot dka400
To boot an AlphaStation 500, 600, or 600A workstation over the network, make sure it is registered as a client on a RIS server. Refer to the Sharing Software on a Local Area Network guide for information on registering a client.
Use the
show device
command to determine which network adapter
(such as
ewa
or
era) is in use:
>>>show device
Output similar to
the following is displayed by the
show device
command:
dka400.4.0.6.0 DKA400 RRD43 2893 dva0.0.0.0.1 DVA0 ewa0.0.0.13.0 EWA0 08-00-2B-3E-B6-C8 pka0.7.0.6.0 PKA0 SCSI Bus ID 7
Use the following command syntax to boot your system over the network:
set
device_inet_initbootp
set
device_protocolsbootp
For example, if the device you are booting from with the
bootp
protocol is
ewa0, enter the following commands:
>>>set ewa0_inet_init bootp>>>set ewa0_protocols bootp>>>boot -fi "" ewa0
You have completed booting your system. Continue the installation procedure with Chapter 5.
This section provides instructions for booting Personal Workstation 433au, 500au, 600au and Ultimate Workstation 533-au2 workstations.
Before starting the boot procedure, complete the following steps:
Enter the following command to clear the
boot_osflags
variable to ensure that the kernel takes correct action upon boot:
>>>set boot_osflags ""
Set the
auto_action
variable to
halt.
This halts the system at the console prompt each time the system is turned on, when
the system crashes, or when you press the Halt button.
>>>set auto_action halt
Set the
os_type
variable to
unix:
>>>set os_type unix
Enter the
init
command:
>>>init
If your CD-ROM optical disk is not already in a caddy, follow the instructions in Appendix B.
Use the following procedure to boot the system:
Insert the Operating System Volume 1 CD-ROM.
Enter the following command to determine the unit number of the drive for your device:
>>>show device
Output similar to the following is displayed by the
show device
command:
dka400.4.0.6.0 DKA400 RRD43 2893 dva0.0.0.0.1 DVA0 ewa0.0.0.13.0 EWA0 08-00-2B-3E-B6-C8 pka0.7.0.6.0 PKA0 SCSI Bus ID 7
The second column shows the numbers assigned to each drive:
The letters DK refer to a SCSI disk or CD-ROM device.
The third letter (A, B, C, D, or E) refers to the SCSI bus designation. Refer to your hardware owner's guide for more details.
The number refers to the drive number.
In the third column, look for the line with the CD-ROM device
string
RRD.
In the previous example, the CD-ROM device is
RRD43.
The device boot string for your system appears in that same line.
The device boot string begins with the letters
DKA.
Enter the
boot
command with the following syntax
to boot from a CD-ROM:
boot
device-number
For example, to boot the system from the CD-ROM drive with console
device name
dkb400, enter the following command:
>>>boot dkb400
You have completed booting your system. Continue the installation procedure with Chapter 5.
Use the following command syntax to boot your system over the network:
set
device_inet_initbootp
set
device_protocolsbootp
For example, if the device you are booting from with the
bootp
protocol is
ewa0, enter the following commands:
>>>set ewa0_inet_init bootp>>>set ewa0_protocols bootp>>>boot -fi "" ewa0
You have completed booting your system. Continue the installation procedure with Chapter 5.
This section provides instructions for booting Professional Workstation XP1000 workstations.
The
bus_probe_algorithm
console environment variable must
be set to
new.
To verify that the
bus_probe_algorithm
environment variable is set to
new, enter the following
console firmware command:
>>>show bus_probe_algorithm
If the environment variable is set to
old, set the variable to
new
and initialize the console
as shown in the following example:
>>>set bus_probe_algorithm new>>>init
Before starting the boot procedure on a Professional Workstation XP1000, complete the following steps:
Enter the following command to clear the
boot_osflags
variable to ensure that the kernel takes correct action upon boot:
>>>set boot_osflags ""
Set the
auto_action
variable to
halt.
This halts the system at the console prompt each time it is turned on, when it crashes,
or when you press the Halt button.
>>>set auto_action halt
Set the
boot_file
variable.
This ensures that
an alternate boot file is not set.
>>>set boot_file
Follow these steps to boot Professional Workstation XP1000 workstations from a CD-ROM:
Insert the Operating System Volume 1 CD-ROM.
Enter the following command to determine the unit number of the drive for your device:
>>>show device
Output similar to the following is displayed by the
show device
command:
dka400.4.0.6.0 DKA400 RRD43 2893 dva0.0.0.0.1 DVA0 ewa0.0.0.13.0 EWA0 08-00-2B-3E-B6-C8 pka0.7.0.6.0 PKA0 SCSI Bus ID 7
The second column shows the numbers assigned to each drive:
The letters DK refer to a SCSI disk or CD-ROM device.
The third letter (A, B, C, D, or E) refers to the SCSI bus designation. Refer to your hardware owner's guide for more details.
The number refers to the drive number.
In the third column, look for the line with the CD-ROM device
string
RRD.
In the previous example, the CD-ROM device is
RRD43.
The device boot string for your system appears in that same line.
The device boot string begins with the letters
DKA.
Enter the
boot
command and the appropriate boot
device string for your system.
For example, to boot the system from the CD-ROM
drive with console device name
dka400, enter the following command:
>>>boot dka400
To boot a Professional Workstation XP1000 workstation over the network, make sure it is registered as a client of a RIS server. Refer to the Sharing Software on a Local Area Network guide for information on registering a client.
Use the
show device
command to determine which network adapter
(such as
ewa
or
era) is in use:
>>>show device
Output similar to
the following is displayed by the
show device
command:
dka400.4.0.6.0 DKA400 RRD43 2893 dva0.0.0.0.1 DVA0 ewa0.0.0.13.0 EWA0 08-00-2B-3E-B6-C8 pka0.7.0.6.0 PKA0 SCSI Bus ID 7
Use the following command syntax to boot your system over the network:
set
device_inet_initbootp
set
device_protocolsbootp
For example, if the device you are booting from with the
bootp
protocol is
ewa0, enter the following commands:
>>>set ewa0_inet_init bootp>>>set ewa0_protocols bootp>>>boot -fi "" ewa0
You have completed booting your system. Continue the installation procedure with Chapter 5.
This section provides instructions for booting AXPvme, AlphaVME, and AXPpci single-board computers (SBCs) and PICMG Alpha CPUs (EBM2n-AZ). You must update your system's firmware before installing this version of the operating system. Refer to Section 1.4.6 for more information about updating firmware.
Before starting the boot procedure, complete the following steps:
Enter the following command to clear the
boot_osflags
variable to ensure that the kernel takes correct action upon boot:
>>>set boot_osflags ""
Set the
auto_action
variable to
halt.
This halts the SBC at the console prompt each time the SBC is turned on, when the
SBC crashes, or when you press the Halt button.
>>>set auto_action halt
Set the
boot_file
variable.
This ensures that
an alternate boot file is not set.
>>>set boot_file
Follow these steps to boot the AXPvme 64, AXPvme 100, AXPvme 160, AXPvme 166, AXPvme 230, Alpha VME 4/224, Alpha VME 4/288, and Alpha VME 5/nnn SBCs from a CD-ROM optical disk:
Insert the Operating System Volume 1 CD-ROM.
Enter the following command to determine the unit number of the drive for your device:
>>>show device
Output similar to the following is displayed by the
show device
command:
dka200.2.0.2.0 DKA200 RZ26 T392 dka400.4.0.2.0 DKA400 RRD42 4.5d ewa0.0.0.1.0 EWA0 08-00-2B-39-88-3A pka0.7.0.2.0 PKA0 SCSI Bus ID 7
The second column shows the numbers assigned to each drive:
The letters DK refer to a SCSI disk or CD-ROM device.
The third letter (A, B, C, D, or E) refers to the SCSI bus designation. Refer to your hardware owner's guide for more details.
The number refers to the drive number.
In the third column, look for the line with the CD-ROM device
string
RRD.
In the previous example, the CD-ROM device is
RRD42.
The device boot string for your system appears in that same line.
The device boot string begins with the letters
DKA.
Enter the
boot
command and the appropriate boot
device string for your system.
For example, to boot the system from the CD-ROM
drive with console device name
dka400, enter the following command:
>>>boot dka400
To boot your SBC over the network, make sure it is registered as a client on a RIS server. Refer to Sharing Software on a Local Area Network for information on registering a client.
Use the
show device
command to determine which network adapter
is in use.
The network adapter will have a value such as
ewa0
or
era0.
>>>show device
Output similar to the following is displayed by the
show device
command:
dka200.2.0.2.0 DKA200 RZ26 T392 dka400.4.0.2.0 DKA400 RRD42 4.5d ewa0.0.0.1.0 EWA0 08-00-2B-39-88-3A pka0.7.0.2.0 PKA0 SCSI Bus ID 7
Use the following command syntax to boot your system over the network:
set
device_inet_initbootp
set
device_protocolsbootp
For example, if the device you are booting from with the bootp protocol
is
ewa0, enter the following commands:
>>>set ewa0_inet_init bootp>>>set ewa0_protocols bootp>>>boot ewa0
You have completed booting your system. Continue the installation procedure with Chapter 5.
This section provides instructions for booting AlphaPC64, AlphaPC164, EB64+, EB66+, and EB164 single-board computers (SBCs).
Before starting the boot procedure on AlphaPC64, AlphaPC164, EB64+, EB66+, and EB164 SBCs, complete the following steps:
Enter the following command to clear the
boot_osflags
variable to ensure that the kernel takes correct action upon boot:
>>>set boot_osflags ""
Set the
auto_action
variable to
halt.
This halts the SBC at the console prompt each time it is turned on, when it crashes,
or when you press the Halt button.
>>>set auto_action halt
Set the
boot_file
variable.
This ensures that
an alternate boot file is not set.
>>>set boot_file
Follow these steps to boot AlphaPC64, AlphaPC164, EB64+, EB66+, and EB164 single-board computers from a CD-ROM optical disk:
Insert the Operating System Volume 1 CD-ROM.
Enter the following command to determine the unit number of the drive for your device:
>>>show device
Output similar to the following is displayed by the
show device
command:
dka400.4.0.6.0 DKA400 RRD43 2893 dva0.0.0.0.1 DVA0 ewa0.0.0.13.0 EWA0 08-00-2B-3E-B6-C8 pka0.7.0.6.0 PKA0 SCSI Bus ID 7
The second column shows the numbers assigned to each drive:
The letters DK refer to a SCSI disk or CD-ROM device.
The third letter (A, B, C, D, or E) refers to the SCSI bus designation. Refer to your hardware owner's guide for more details.
The number refers to the drive number.
In the third column, look for the line with the CD-ROM device
string
RRD.
In the previous example, the CD-ROM device is
RRD43.
The device boot string for your system appears in that same line.
The device boot string begins with the letters
DKA.
Enter the
boot
command and the appropriate boot
device string for your system.
For example, to boot the system from the CD-ROM
drive with console device name
dka400, enter the following command:
>>>boot dka400
To boot your AlphaPC64, AlphaPC164, EB64+, EB66+, or EB164 SBC over the network, make sure it is registered as a client on a RIS server. Refer to Sharing Software on a Local Area Network for information on registering a client. Set your device protocols to boot from a RIS server.
Use the
show device
command to determine which network adapter
is in use.
The network adapter will have a value such as
ewa0
or
era0.
>>>show device
Output similar to the following is displayed by the
show device
command:
dka200.2.0.2.0 DKA200 RZ26 T392 dka400.4.0.2.0 DKA400 RRD42 4.5d ewa0.0.0.1.0 EWA0 08-00-2B-39-88-3A pka0.7.0.2.0 PKA0 SCSI Bus ID 7
Use the following command syntax to boot your system over the network:
set
device_inet_initbootp
set
device_protocolsbootp
For example, if the device you are booting from with the bootp protocol
is
ewa0, enter the following commands:
>>>set ewa0_inet_init bootp>>>set ewa0_protocols bootp>>>boot ewa0
You have completed booting your system. Continue the installation procedure with Chapter 5.