![[Return to Library]](BOOKSHLF.GIF)
![[TOC]](TOC.GIF)
![[PREV]](REW.GIF)
![[NEXT]](FF.GIF)
![[INDEX]](INDEX.GIF)
![[Help]](HELP.GIF)
This chapter provides processor-specific boot commands to boot from the Digital UNIX CD-ROM or over a network connection to a RIS server.
Unlike full installations, you do not boot from the distribution media to perform a Digital UNIX update installation. Update installations are performed from single-user mode at the command line. Refer to Chapter 2 for information about performing update installations. Note
In addition, this release provides an automatic reboot feature for systems that have unattended installation capability. See Table 4-3 for a list of the systems that support this feature.
The goal of this chapter is to provide the information necessary for you to perform the user actions shown in Table 4-1.
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 single-board computer must be registered as
a client on a Remote Installation Services (RIS) server.
If you are adding peripheral devices to your system at this time, go
to Step 2.
If you are not connecting additional peripheral devices to your system,
go to Step 3.
If you connect additional peripherals or controllers after the installation,
refer to the System Administration guide for instructions about how to reconfigure
your system.
4.1 Shutting Down and Booting the Processor
To prepare the hardware for the installation booting
process, do the following:
# shutdown -h +30 Please log out
In the previous example, the system is shut down and
halted in 30 minutes and sends the message Please log out
to all logged in users. Consult the System Administration guide or the shutdown(8)
reference page if you need more information about shutting down a system. Note
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.
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. Note
Some systems are rebooted automatically during the installation process. This automatic reboot feature is new in this release and is supported on systems with unattended installation capability. Table 4-3 lists the systems that support unattended installation.
| Systems with Unattended Installation Capability |
|---|
| AlphaServer 1000A Series |
| AlphaServer 2100 Series |
| AlphaServer 4000/4100 Series |
Follow this procedure to boot the system:
bootdevice
For example, to boot the system from CD-ROM drive number
1, enter the following command:
The device parameter is the network device from which you want to boot.
The AlphaServer 300 and AlphaServer 400 processors support two network adapters: ewa0 and ena0.
setdevice_protocols
bootp setdevice_inet_init
bootp
For example, if the device you are booting from with the bootp protocol is ewa0, enter the following commands:
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.
For more information about the show device and boot commands, see the hardware documentation that comes with your
system.
To boot from a Digital UNIX Server, see Section 4.4.4.1.
setdevice_inet_init
bootp setdevice_protocols
bootp
For example, if the device you are booting from with the bootp protocol is ewa0, enter the following commands:
Follow this procedure to boot the system:
bootdevice
For example, to boot the system from CD-ROM drive number
1, enter the following command:
The device parameter is the network device from which
you want to boot. AlphaServer 2000 Series processors support two network adapters: ewa0 and ewb0.
setdevice
_protocols bootp setdevice
_inet_init bootp
For example, if the device you are booting from with the bootp protocol is ewa0, enter the following commands:
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.
You have completed booting your system. Continue the installation procedure
with Chapter 5.
Follow this procedure to boot the system:
bootdevice
For example, to boot the system from CD-ROM drive number
1, enter the following command:
The device parameter is the network device from which
you want to boot. The AlphaServer 2100 Series, AlphaServer 2100A Series, AlphaServer 4000/4100 Series,
and Digital Alpha VME 2100 Series processors support two network adapters: ewa0
and ewb0.
setdevice_protocols
bootp setdevice_inet_init
bootp
For example, if the device you are booting from with the bootp protocol is ewa0, enter the following commands:
For the AlphaServer 4000/4100 Series processor only, enter the following
command to supercede the boot_ osflags setting:
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.
You have completed booting your system. Continue the installation procedure
with Chapter 5.
Use the following procedure to boot the system:
bootdevice-number
For example, to boot the system from CD-ROM drive number
4, enter:
The device parameter is the network device from which
you want to boot. The AlphaServer 8200 and AlphaServer 8400 Series processors
support two network adapters: ewa0 and ewb0.
setdevice_protocols
bootp setdevice_inet_init
bootp
For example, if the device you are booting from with the bootp protocol is ewa0, enter the following commands:
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.
Follow this procedure to boot the system:
bootdevice
For example, to boot the system from CD-ROM drive number
1, enter the following command:
The device parameter is the network device from which you want to boot.
The AlphaStation 200 Series, AlphaStation 250 Series, AlphaStation 255 Series, and AlphaStation 400 Series
processors support two network adapters: ewa0 and ena0.
setdevice_protocols
bootp setdevice_inet_init
bootp
For example, if the device you are booting from with the bootp protocol is ewa0, enter the following commands:
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.
For more information about the show device and boot commands, see the hardware documentation that comes with your
system.
To boot from a Digital UNIX Server, see Section 4.9.3.1.
setdevice_inet_init
bootp setdevice_protocols
bootp
For example, if the device you are booting from with the bootp protocol is ewa0, enter the following commands:
For more information about the show device and boot commands, see the hardware documentation that comes with your
system.
setdevice_inet_init
bootp setdevice_protocols
bootp
For example, if the device you are booting from with the bootp
protocol is ewa0, enter the following commands:
For more information about the show device and boot commands, see the hardware documentation that comes with your
system.
setdevice_inet_init
bootp setdevice_protocols
bootp
For example, if the device you are booting from with the bootp
protocol is ewa0, enter the following commands:
Similarly, when using DE205 (ISA LeMAC) Ethernet card, enter the following
sequence of commands:
For more information about the show device and boot commands, see the hardware documentation that comes with your
system.
setdevice_inet_init
bootp setdevice_protocols
bootp
For example, if the device you are booting from with the bootp
protocol is ewa0, enter the following commands:
Use this procedure to boot the system:
bootdevice
For example, to boot the system from CD-ROM drive number
4, enter the following command:
Use the following procedure to boot the system:
bootdevice
For example, to boot the system from CD-ROM drive number
4, enter the following command:
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.
ttcslot_number
cnfg
For example, to determine the device number of a disk on a
PMAZB option card, enter the following command:
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:
To boot from an FDDI network interface device, find the device names
as described in Section 4.14.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 Digital UNIX server using the bootp protocol:
Use the following procedure to boot the system:
bootdevice
For example, to boot the system from CD-ROM drive number
1, enter the following command:
The device parameter is the network device from which
you want to boot. The DEC 4000 processor supports two network adapters: eza0 and ezb0.
Set your device protocols to boot from a Digital UNIX server.
setdevice_protocols
bootp
For example, if the device you are booting from with the bootp protocol is eza0, enter the following commands:
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.
You have completed booting your system. Continue the installation procedure
with Chapter 5.
Use the following procedure to boot the system:
bootdevice-number
For example, to boot the system from CD-ROM drive number
4, enter:
4.3 AlphaServer 300 and AlphaServer 400 Processors
The following sections describe
how to boot an AlphaServer 300 or AlphaServer 400 processor from a CD-ROM
optical disc and from the network.
4.3.1 Setting the Console Flags
Before starting the boot procedure on an AlphaServer 300 or AlphaServer 400
processor, complete the following steps:
>>> set boot_osflags ""
NOTE
>>> 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 auto_action halt
4.3.2 Booting from the CD-ROM Optical Disc Kit
If your CD-ROM optical disc is not already in a caddy, follow
the instructions in Appendix B.
You have completed booting your system. Continue the installation
procedure with Chapter 5.
>>> 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:
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.
>>> init
>>> 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 - Wed Jul 5 17:18:57 EDT 1995
4.3.3 Booting from the Network
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.
4.3.3.1 Booting from a Digital UNIX Server
Use the following command syntax to boot your system over the
network:
>>> 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.
4.4 AlphaServer 1000 and AlphaServer 1000A Series Processors
This section provides instructions for booting AlphaServer 1000 and AlphaServer 1000A
series processors.
4.4.1 The bus_probe_algorithm Environment Variable
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
4.4.2 Setting the Console Flags
Before starting the boot procedure on an AlphaServer 1000 or AlphaServer 1000A
processor, complete the following steps:
>>> set boot_osflags ""
NOTE
>>> 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 auto_action halt
>>> set boot_file
4.4.3 Booting from the CD-ROM Optical Disc Kit
Follow these steps to boot AlphaServer 1000 or AlphaServer 1000A series
processors from a CD-ROM optical disc:
>>> 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:
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.
>>> boot dka400
4.4.4 Booting from the Network
To boot an AlphaServer 1000 or AlphaServer 1000A series processor 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.
4.4.4.1 Booting from a Digital UNIX Server
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 ewa0_inet_init bootp
>>> set ewa0_protocols bootp
>>> boot -fi "" ewa0
You have completed booting your system. Continue the installation procedure
with Chapter 5.
4.5 AlphaServer 2000 Series Processors
The following sections describe
how to boot AlphaServer 2000 Series processors from a CD-ROM optical disc and
from the network.
4.5.1 The bus_probe_algorithm Environment Variable
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
4.5.2 Setting the Console Flags
Before starting the boot procedure, complete the following steps:
>>> set boot_osflags ""
NOTE
>>> 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 auto_action halt
4.5.3 Booting from the CD-ROM Optical Disc Kit
If your CD-ROM optical disc
is not already in a caddy, follow the instructions in Appendix B.
You have completed booting your system. Continue the installation
procedure with Chapter 5.
>>> 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:
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.
>>> init
>>> 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 - Mon Aug 5 15:49:49 EDT 1993
4.5.4 Booting from the Network
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.
4.5.4.1 Booting from a Digital UNIX Server
Use the following command syntax to boot your system over the network:
>>> set ewa0_protocols bootp
>>> set ewa0_inet_init bootp
>>> boot ewa0
4.5.5 Prestoserve Option
These instructions apply to AlphaServer 2000 Series processors equipped
with the Prestoserve option.
4.5.5.1 The prcache Command
AlphaServer 2000 Series 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.
4.6 AlphaServer 2100 Series, AlphaServer 2100A Series, AlphaServer 4000/4100 Series, and Digital Alpha VME 2100 Series
Processors
The following sections describe how to boot AlphaServer 2100 Series, AlphaServer 2100A Series,
AlphaServer 4000/4100 Series, and Digital Alpha VME 2100 Series processors from a CD-ROM
optical disc and from the network.
4.6.1 The bus_probe_algorithm Environment Variable
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
4.6.2 Setting the Console Flags
Before starting the boot procedure, complete the following steps:
>>> set boot_osflags ""
NOTE
>>> 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 auto_action halt
4.6.3 Booting from the CD-ROM Optical Disc Kit
If your CD-ROM optical disc is not already
in a caddy, follow the instructions in Appendix B.
You have completed booting your system. Continue the installation
procedure with Chapter 5.
>>> 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:
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.
>>> init
>>> 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 13 15:49:49 EDT 1996
4.6.4 Booting from the Network
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.
4.6.4.1 Booting from a Digital UNIX Server
Use the following command syntax to boot your system over the network:
>>> set ewa0_protocols bootp
>>> set ewa0_inet_init bootp
>>> boot ewa0
>>> boot -fl an ewa0
To stop the autoreboot feature on the AlphaServer 4000/4100
Series processor, enter the following command:
>>> boot -fl anh ewa0
4.6.5 Prestoserve Option
These instructions apply to AlphaServer 2100 Series, AlphaServer 2100A Series, AlphaServer
4000/4100 and Digital Alpha VME 2100 Series processors equipped with the Prestoserve option.
4.6.5.1 The prcache Command
The AlphaServer 2100 Series, AlphaServer 2100A Series, AlphaServer 4000/4100, and Digital Alpha VME 2100 Series system
consoles provide the prcache command to support the Prestoserve
option (NVRAM). Refer to hardware documentation for a description of this
command.
4.7 AlphaServer 8200 and AlphaServer 8400 Series Processors
The following sections
describe how to boot AlphaServer 8200 and AlphaServer 8400 processors
from a CD-ROM optical disc.
4.7.1 Setting the Console Flags
Before starting the boot procedure, complete the following steps:
>>> set boot_osflags ""
NOTE
>>> 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 auto_action halt
>>> set boot_reset on
4.7.2 Booting from the CD-ROM Optical Disc Kit
If your CD-ROM optical disc is not already in a caddy, follow
the instructions in Appendix B.
You have completed booting your system. Continue the installation
procedure with Chapter 5.
>>> 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:
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.
>>> 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
.
.
.
4.7.3 Booting from the Network
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.
4.7.3.1 Booting from a Digital UNIX Server
Use the following command syntax to boot your system over the network:
>>> show net
>>> set ewa0_protocols bootp
>>> set ewa0_inet_init bootp
>>> boot -fl an ewa0
4.8 AlphaStation 200 Series, AlphaStation 250 Series, AlphaStation 255 Series, and AlphaStation 400 Series Processors
The
following sections describe how to boot AlphaStation 200 Series, AlphaStation 250 Series,
AlphaStation 255 Series, and AlphaStation 400 Series processors from a CD-ROM optical
disc and from the network.
4.8.1 Setting the Console Flags
Before starting the boot procedure on an AlphaStation 200 Series processor, an AlphaStation 250 Series
processor, an AlphaStation 255 Series processor, or an AlphaStation 400 Series processor, complete
the following steps:
>>> set boot_osflags ""
NOTE
>>> 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 auto_action halt
4.8.2 Booting from the CD-ROM Optical Disc Kit
If your CD-ROM optical disc is not already in
a caddy, follow the instructions in Appendix B.
You have completed booting your system. Continue the installation
procedure with Chapter 5.
>>> 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:
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.
>>> init
>>> 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 - Wed Jul 5 17:18:57 EDT 1995
4.8.3 Booting from the Network
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.
4.8.3.1 Booting from a Digital UNIX Server
Use the following command syntax to boot your system
over the network:
>>> set ewa0_protocols bootp
>>> set ewa0_inet_init bootp
>>> boot ewa0
4.9 AlphaStation 500 and AlphaStation 600 Series Processors
This section provides instructions for booting AlphaStation 500 and AlphaStation 600
processors.
4.9.1 Setting the Console Flags
Before starting the boot procedure on AlphaStation 500 and AlphaStation 600 processors,
complete the following steps:
>>> set boot_osflags ""
NOTE
>>> 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 auto_action halt
>>> set boot_file
4.9.2 Booting from the CD-ROM Optical Disc Kit
Follow these steps to boot AlphaStation 500 and AlphaStation 600 processors
from a CD-ROM optical disc:
>>> 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:
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.
>>> boot dka400
4.9.3 Booting from the Network
To boot an AlphaStation 500 and AlphaStation 600 processors 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.
4.9.3.1 Booting from a Digital UNIX Server
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 ewa0_inet_init bootp
>>> set ewa0_protocols bootp
>>> boot -fi "" ewa0
You have completed booting your system. Continue the installation procedure
with Chapter 5.
4.10 AXPvme 64, AXPvme 100, AXPvme 160, AXPvme 166, AXPvme 230, Alpha VME 4/224, Alpha VME 4/288, and Alpha VME 5/nnn Single-Board Computers
(SBCs)
This section provides instructions for booting AXPvme 64, AXPvme 100, AXPvme 160, AXPvme 166, AXPvme 230, Alpha VME 4/224, Alpha VME 4/288,
and AlphaVME 5/nnn single-board computers. You must update your system's firmware
before installing Digital UNIX Version 4.0B. Refer to Section 1.4.6
for more information about updating firmware.
4.10.1 Setting the Console Flags
Before starting the boot procedure, complete the following steps:
>>> set boot_osflags ""
NOTE
>>> 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 auto_action halt
>>> set boot_file
4.10.2 Booting from the CD-ROM Optical Disc Kit
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 single-board computers from a CD-ROM optical disc:
>>> 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:
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.
>>> boot dka400
4.10.3 Booting from the Network
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.
4.10.3.1 Booting from a Digital UNIX 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 ewa0_inet_init bootp
>>> set ewa0_protocols bootp
>>> boot ewa0
You have completed booting your system. Continue the installation procedure
with Chapter 5.
4.11 AXPpci 33 Single Board Computer (SBC) and Digital PICMG Alpha CPUs
This section provides instructions for booting an AXPpci 33 single-board
computer or Digital PICMG Alpha CPUs (also known as Digital DMCC EBM4x and
EBM2n Series SBCs).
4.11.1 Setting the Console Flags
Before starting the boot procedure on an AXPpci 33 single-board computer
or Digital PICMG Alpha CPU, complete the following steps:
>>> set boot_osflags ""
NOTE
>>> 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 auto_action halt
>>> set boot_file
4.11.2 Booting from the CD-ROM Optical Disc Kit
Follow these steps to
boot the AXPpci 33 single-board computer or Digital PICMG Alpha CPU from
a CD-ROM optical disc:
>>> 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:
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.
>>> boot dka400
4.11.3 Booting from the Network
To boot your AXPpci 33
SBC or Digital PICMG Alpha CPU 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 Digital UNIX server.
4.11.3.1 Booting from a Digital UNIX 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 ewa0_inet_init bootp
>>> set ewa0_protocols bootp
>>> boot ewa0
You have completed booting your system. Continue the installation procedure
with Chapter 5.
4.11.4 Booting Considerations
Debugging information printed during the system boot phase may cause
the internal ring message buffer to be overwritten. This results in not all
messages being saved in the /usr/var/adm/syslog.dated directory.
4.11.5 Booting from a PCI Tulip or ISA LeMAC Ethernet Card
To boot over the DE435 (PCI TULIP) Ethernet card using bootp protocol, enter the following sequence of commands after you have
configured your boot server:
>>> set ewa0_inet_init bootp
>>> set ewa0_protocols bootp
>>> boot ewa0
>>> set ena0_inet_init bootp
>>> set ena0_protocols bootp
>>> boot ena0
4.12 AlphaPC64, AlphaPC164, EB64+, EB66+, and EB164 Single-Board Computers
This section provides instructions for booting AlphaPC64, AlphaPC164, EB64+, EB66+, and EB164 single-board
computers (SBCs).
4.12.1 Setting the Console Flags
Before starting the boot procedure on AlphaPC64, AlphaPC164, EB64+, EB66+, and EB164 SBCs, complete the following
steps:
>>> set boot_osflags ""
NOTE
>>> 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 auto_action halt
>>> set boot_file
4.12.2 Booting from the CD-ROM Optical Disc Kit
Follow these steps to boot AlphaPC64, AlphaPC164, EB64+, EB66+, and EB164 single-board computers from a CD-ROM
optical disc:
>>> 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:
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.
>>> boot dka400
4.12.3 Booting from the Network
To boot your AlphaPC64, AlphaPC164, EB64+, EB66+, and 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 Digital UNIX server.
4.12.3.1 Booting from a Digital UNIX 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 ewa0_inet_init bootp
>>> set ewa0_protocols bootp
>>> boot ewa0
You have completed booting your system. Continue the installation procedure
with Chapter 5.
4.13 DEC 2000 Series Processors
The following sections
describe how to boot the DEC 2000 processor from a CD-ROM optical disc
and from the network.
4.13.1 Setting the Console Flags
Before starting the boot procedure, enter the following commands. Each
command is echoed by the system when you press Return:
>>> set boot_osflags ""
NOTE
>>> 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 auto_action halt
>>> set keyboard <type>
Use the help set
command to list the available keyboard types.
4.13.2 Booting from the CD-ROM Optical Disc Kit
Place the CD-ROM optical
disc into a caddy as described in Appendix B.
You have completed booting your system. Continue the installation
procedure with Chapter 5.
>>> 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:
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.
>>> b dka400
4.13.3 Booting from the Network
Booting from the network is not supported for the DEC 2000 processors.
4.14 DEC 3000 Series Processors
The following sections
describe how to boot the DEC 3000 series processor from a CD-ROM optical
disc and from the network.
4.14.1 Setting the Console Flags
Before starting the boot procedure, enter the following commands. Each
command is echoed by the system when you press Return:
>>> set boot_osflags ""
NOTE
>>> 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 auto_action halt
>>> set boot_reset on
>>> set scsi_reset 4
4.14.2 Booting from the CD-ROM Optical Disc Kit
Place the CD-ROM optical
disc into a caddy as described in Appendix B.
You have completed booting your system. Continue the installation
procedure with Chapter 5.
>>> 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:
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.
>>> b dka400
4.14.3 Booting from the Network
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.
4.14.3.1 Booting from a Digital UNIX Server
When booting from a Digital UNIX server, the system uses the bootp protocol. Enter the following command to boot your system
over the network:
>>> boot ez0
4.14.4 Booting from the SCSI TURBOchannel Option Card
To
boot from the dual SCSI TURBOchannel option card (PMAZB or PMAZC), complete
the following steps:
To boot from the PMAZB (or PMAZC) option card, enter the boot command with the following syntax:
>>> show conf
Your system displays output similar to the following (the output differs depending
on your system configuration):
DEC 3000 - M500
Digital Equipment Corporation
VPP 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.
>> 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
>>> b "1/dka400"
You have
completed booting your system. Continue the installation procedure with Chapter 5.
4.14.5 Booting from an FDDI Network Interface
Booting
over an FDDI network interface is supported for DEFTA and CRE-DEFTA devices.
>>> b "1/ez0"
You have completed booting your system. Continue the installation procedure
with Chapter 5.
4.15 DEC 4000 Series Processors
The following sections describe how to boot the DEC
4000 processor from a CD-ROM optical disc and from the network.
4.15.1 Setting the Console Flags
Before starting the boot procedure, complete the following steps:
>>> set boot_osflags ""
NOTE
>>> 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 auto_action halt
4.15.2 Booting from the CD-ROM Optical Disc Kit
If your CD-ROM optical disc
is not already in a caddy, follow the instructions in Appendix B.
You have completed booting your system. Continue the installation
procedure with Chapter 5.
>>> 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:
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.
>>> init
>>> 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 - Wed Jul 5 15:49:49 EDT 1995
4.15.3 Booting from the Network
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.
4.15.3.1 Booting from a Digital UNIX Server
Use the following command syntax to boot your system over the network:
>>> set eza0_protocols bootp
>>> boot eza0
4.15.4 Prestoserve Option
The following instructions apply to DEC 4000 systems equipped
with the Prestoserve option.
4.15.4.1 The prcache Command
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.
4.16 DEC 7000 and DEC 10000 Series Processors
The following
sections describe how to boot the DEC 7000 processor and DEC 10000 processor
from a CD-ROM optical disc.
4.16.1 Setting the Console Flags
Before starting the boot procedure, complete the following steps:
>>> set boot_osflags ""
NOTE
>>> 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 auto_action halt
>>> set boot_reset on
4.16.2 Booting from the CD-ROM Optical Disc Kit
If
your CD-ROM optical disc is not already in a caddy, follow the instructions
in Appendix B.
You have completed booting your system. Continue the installation
procedure with Chapter 5.
>>> show dev
Output similar to the following is displayed:
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:
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 RRD43.
The device boot string for your system appears in that same line. The device
boot string begins with the letters DKB.
>>> 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
.
.
.