Alphaserver1000a Serviceguide
Alphaserver1000a Serviceguide
Alphaserver1000a Serviceguide
Service Guide
Order Number: EKALPSVSV. A01
S3016
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xi
1 Troubleshooting Strategy
1.1
1.1.1
1.2
1.3
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
11
12
17
19
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
22
24
29
211
212
215
218
219
220
220
221
221
222
224
224
225
225
225
226
iii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
31
32
33
34
37
38
310
312
314
315
316
317
318
318
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
41
42
44
45
45
46
52
52
54
iv
54
55
57
59
59
514
515
515
523
524
5.2.2
5.3
5.4
5.5
5.5.1
5.6
5.6.1
5.6.2
5.6.3
5.6.4
5.7
5.7.1
5.8
5.8.1
5.8.2
5.8.3
5.9
5.10
5.10.1
5.10.2
5.10.3
5.10.4
5.10.5
Memory Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Motherboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EISA Bus Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ISA Bus Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Identifying ISA and EISA options . . . . . . . . . . . . . . . .
EISA Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . .
Before You Run the ECU . . . . . . . . . . . . . . . . . . . . . . .
How to Start the ECU . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring EISA Options . . . . . . . . . . . . . . . . . . . . . .
Configuring ISA Options . . . . . . . . . . . . . . . . . . . . . . .
PCI Bus Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PCI-to-PCI Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCSI Buses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Internal StorageWorks Shelf . . . . . . . . . . . . . . . . . . . .
External SCSI Expansion . . . . . . . . . . . . . . . . . . . . . .
SCSI Bus Configurations . . . . . . . . . . . . . . . . . . . . . . .
Power Supply Configurations . . . . . . . . . . . . . . . . . . . . . . .
Console Port Configurations . . . . . . . . . . . . . . . . . . . . . . . .
set console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
set tt_allow_login . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
set tga_sync_green . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Up a Serial Terminal to Run ECU . . . . . . . . . .
Using a VGA Controller Other than the Standard
On-Board VGA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
524
525
526
527
527
528
528
529
531
532
533
534
534
534
535
536
540
543
543
544
545
545
546
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
61
67
69
612
621
622
623
624
626
630
631
.
.
.
.
.
.
.
.
.
.
.
.
636
636
639
640
6.2.14
Removable Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
641
Motherboard Jumpers . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CPU Daughter Board (J3 and J4) Supported Settings . . . .
CPU Daughter Board (J1 Jumper) . . . . . . . . . . . . . . . . . . .
A2
A4
A6
56
28
29
216
216
217
223
52
514
523
525
527
533
537
Glossary
Index
Examples
51
Figures
21
22
23
24
25
26
51
52
53
54
55
56
57
58
59
510
511
61
vi
538
539
541
542
65
62
63
64
65
66
67
68
69
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
.
.
.
.
.
.
.
.
.
.
.
.
66
67
68
69
610
610
611
612
613
614
615
616
617
618
619
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
620
621
622
623
624
625
626
627
628
630
631
632
633
635
636
637
638
639
vii
635
636
637
638
A1
A2
A3
A4
Removing Speaker . . . . . . . . . . . . . . . . . . . . . . .
Removing a CDROM Drive . . . . . . . . . . . . . . .
Removing a Tape Drive . . . . . . . . . . . . . . . . . . .
Removing a Floppy Drive . . . . . . . . . . . . . . . . . .
Motherboard Jumpers (Default Settings) . . . . . .
AlphaServer 1000A 4/266 CPU Daughter Board
(Jumpers J3 and J4) . . . . . . . . . . . . . . . . . . . . .
AlphaServer 1000A 4/233 CPU Daughter Board
(Jumpers J3 and J4) . . . . . . . . . . . . . . . . . . . . .
CPU Daughter Board (J1 Jumper) . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
640
641
642
643
A2
.....
A4
.....
.....
A5
A6
13
Tables
11
12
13
14
15
21
22
23
24
25
26
27
31
41
51
52
53
54
55
viii
14
15
16
17
22
25
210
212
214
218
220
32
42
55
56
58
516
525
56
57
58
61
62
531
532
536
62
611
ix
Preface
This guide describes the procedures and tests used to service AlphaServer 1000A
systems. AlphaServer 1000A systems use a deskside wide-tower enclosure.
Intended Audience
This guide is intended for use by Digital Equipment Corporation service personnel
and qualified self-maintenance customers.
xi
Conventions
The following conventions are used in this guide:
Convention
Meaning
Return
A key name enclosed in a box indicates that you press that key.
Ctrl/x
Ctrl/x indicates that you hold down the Ctrl key while you
press another key, indicated here by x. In examples, this key
combination is enclosed in a box, for example, Ctrl/C .
Warning
Caution
Note
boot
[]
show config
italic type
<>
{}
Related Documentation
DECevent Translation and Reporting Utility for OpenVMS Alpha, User and
Reference Guide, AA-Q73KC-TE
DECevent Translation and Reporting Utility for Digital UNIX, User and
Reference Guide AA-QAA3A-TE
xii
DECevent Analysis and Notification Utility for OpenVMS Alpha, User and
Reference Guide, AA-Q73LC-TE
DECevent Analysis and Notification Utility for Digital UNIX, User and
Reference Guide AA-QAA4A-TE
xiii
1
Troubleshooting Strategy
This chapter describes the troubleshooting strategy for AlphaServer 1000A
systems.
Has the system been used before and did it work correctly?
Troubleshooting Strategy 11
12 Troubleshooting Strategy
Action
Troubleshooting Strategy 13
Action
14 Troubleshooting Strategy
Action
Note
The external SCSI terminator must be
installed on the SCSI port at the rear of
the enclosure. Without the termination,
some SCSI drives will not be available
these drives will be missing from the show
config display.
If the power-up screen or console event log indicates
problems with EISA devices, or if EISA devices are
missing from the show config display, use the
troubleshooting table (Section 2.6) to determine the
problem.
If the power-up screen or console event log indicates
problems with PCI devices, or if PCI devices are
missing from the show config display, use the
troubleshooting table (Section 2.7) to determine the
problem.
Run the ROM-based diagnostic (RBD) tests
(Section 3.1) to verify the problem.
Troubleshooting Strategy 15
Action
(Section 5.1).
16 Troubleshooting Strategy
Action
Examine the crash dump file.
Refer to OpenVMS Alpha System Dump Analyzer
Utility Manual (AA-PV6UB-TE) for information on
how to interpret OpenVMS crash dump files.
Refer to the Guide to Kernel Debugging (AAPS2TD
TE) for information on using the Digital UNIX Krash
Utility.
Troubleshooting Strategy 17
18 Troubleshooting Strategy
Crash Dumps
For fatal errors, such as fatal bugchecks, Digital UNIX and OpenVMS
operating systems will save the contents of memory to a crash dump file.
RECOMMENDED USE: Crash dump files can be used to determine why the
system crashed. To save a crash dump file for analysis, you need to know
the proper system settings. Refer to the OpenVMS Alpha System Dump
Analyzer Utility Manual (AA-PV6UB-TE) or the Guide to Kernel Debugging
(AAPS2TDTE) for Digital UNIX.
ftp://ftp.digital.com/pub/Digital/Alpha/firmware/
http://www.service.digital.com/alpha/server/firmware/
Troubleshooting Strategy 19
ECU Revisions
The EISA Configuration Utility (ECU) is used for configuring EISA options on
AlphaServer systems. Systems are shipped with an ECU kit, which includes
the ECU license. Customers who already have the ECU and license, but need
the latest revision of the ECU, can order a separate kit. Call 1-800-DIGITAL
to order.
If the customer plans to migrate from Digital UNIX or OpenVMS to Windows
NT, you must re-run the appropriate ECU. Failure to run the operatingspecific ECU will result in system failure.
OpenVMS Patches
Software patches for the OpenVMS operating system are available from the
World Wide Web as follows:
http://www.service.digital.com/html/patch_service.html
Choose the Contract Access option if you have a valid software contract
with Digital or you wish to become a software contract customer. Choose the
Public Access options if you do not have a sofware service contract.
Late-Breaking Technical Information
You can download up-to-date files and late-breaking technical information
from the Internet for managing AlphaServer 1000A systems.
FTP address:
ftp.digital.com
cd /pub/DEC/Alpha/systems/as1000/docs
http://www.service.digital.com/alpha/server/1000.html
The information includes firmware updates, the latest configuration utilities,
software patches, lists of supported options, Wide SCSI information and more.
Supported Options
Refer to the AlphaServer 1000A Supported Options List for a list of options
supported under Digital UNIX, OpenVMS, and Windows NT. The options list
is available from the Internet as follows:
FTP address:
ftp://ftp.digital.com/pub/Digital/Alpha/systems/
http://www.service.digital.com/alpha/server/
ftp://ftp.digital.com/pub/Digital/info/SOC/
Training
The following Computer Based Training (CBT) and lecture lab courses are
available from the Digital training center:
Alpha Concepts
2
Power-Up Diagnostics and Display
This chapter provides information on how to interpret error beep codes and
the power-up display on the console screen. In addition, a description of the
power-up and firmware power-up diagnostics is provided as a resource to aid in
troubleshooting.
Section 2.2 describes SROM memory tests that can be run at power-up to
isolate failing SIMM memory.
Problem
ROM data path error detected while
loading ARC/SRM console code.
Corrective Action
1-1-4
1-2-1
Problem
1-3-3
Corrective Action
3-1-2
Problem
Corrective Action
3-3-2
3-3-3
Test Description
Test Results
....done.
If the test takes longer than a few seconds to complete,
there is a problem with the backup cachereplace the
CPU daughter board (Chapter 6).
Memory Test:
Tests memory with
backup and data
cache disabled.
12345.done.
If an error is detected, the bank number and failing
SIMM position are displayed. The following OCP message
indicates a failing SIMM at bank 0, SIMM position 2.
Test Description
Test Results
Memory Test,
Cache Enabled:
Tests memory with
backup and data
cache enabled.
12345.done.
If an error is detected, the bank number and failing
SIMM position are displayed. The following OCP message
indicates a failing SIMM at bank 0, SIMM position 2.
Test Description
Test Results
d
D
D
d
12345.done.
12345.done.
12345.done.
12345.done.
MA00926
Bank
Jumper Setting
SROM memTest: memory test with backup and data cache disabled
SROM memTestCacheOn: memory test with backup and data cache enabled
Bank 3
Bank 2
Bank 1
Bank 0
ECC Banks
SIMM 1
SIMM 3
SIMM 0
SIMM 2
SIMM 1
SIMM 3
SIMM 0
SIMM 2
SIMM 1
SIMM 3
SIMM 0
SIMM 2
SIMM 1
SIMM 3
SIMM 0
SIMM 2
MA00327
Description
Likely FRU
ff
Non-specific/Status message
fe
Non-specific/Status message
fd
Initializing semaphores
Non-specific/Status message
fc,fb,fa
Initializing heap
Non-specific/Status message
f9
Non-specific/Status message
f8
Non-specific/Status message
f7
f6
Non-specific/Status message
f5
Lowering IPL
Non-specific/Status message
f4
ef
df
ee
ed
Non-specific/Status message
ec
eb
SIMM memory
ea
Non-specific/Status message
e9
Non-specific/Status message
e8
Non-specific/Status message
e7
e6
e5
Restore timers
Windows NT Systems
The Windows NT operating system is supported by the ARC firmware (see
Section 5.1.1). Systems using Windows NT power up to the ARC boot menu as
follows:
Alpha Firmware Version n.nn
Copyright (c) 1993-1995 Microsoft Corporation
Copyright (c) 1993-1995 Digital Equipment Corporation
Boot menu:
Boot Windows NT
Boot an alternate operating system...
Run a program...
Supplementary menu...
Use the arrow keys to select, then press Enter.
Ctrl/S .
To resume scrolling,
You can also use the command, more el, to display the console event log
one screen at a time.
The following example shows a console event log that contains a standard error
message indicating that the mouse is not plugged in or is not working.
>>> cat el
ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.
ef.df.ee.f4.ed.ec.initializing keyboard
** mouse error **
eb.ea.e9.e8.e7.e6.e5.e4.e3.e2.e1.e0.
X4.4-5365, built on Oct 27 1995 at 09:26:04
>>>
Table 25 provides troubleshooting tips for AlphaServer systems that use the
RAID Array 200 Subsystem.
Symptom
Corrective Action
Drive failure
Replace drive.
SCSI ID set to 7
(reserved for host ID)
Symptom
Corrective Action
Missing or loose
cables. Drives not
properly seated on
StorageWorks shelf
Terminator missing or
wrong terminator used
Extra terminator
Symptom
Corrective Action
Action
Action
Figure 23 shows the LEDs for disk drives contained in a StorageWorks shelf.
A failure is indicated by the Fault light on each drive.
Figure 24 shows the Activity LED for the floppy drive. This LED is on when
the drive is in use.
Figure 25 shows the Activity LED for the CDROM drive. This LED is on
when the drive is in use.
MA00927
Activity LED
MA00330
MA00333
Action
Confirm that the EISA module and any cabling are properly seated.
Confirm that the system has been configured with the most recently installed
controller.
See what the hardware jumper and switch setting should be for each ISA
controller.
See what the software setting should be for each ISA and EISA controller.
See if any controllers are locked (!), which limits the ECUs ability to change
resource assignments.
Confirm that the hardware jumpers and switches on ISA controllers reflect the
settings indicated by the ECU. Start with the last ISA module installed.
Storage adapterRun test to exercise the storage devices off the EISA
controller option (Section 3.3.1).
Check for a bad slot by moving the last installed controller to a different slot.
Be sure you run the correct version of the ECU for the operating system.
For windows NT, use ECU diskette DECpc AXP (AK-PYCJ*-CA); for Digital
UNIX and OpenVMS, use ECU diskette DECpc AXP (AK-Q2CR*-CA).
The CFG files supplied with the option you want to install may not work on
AlphaServer 1000A systems. Some CFG files call overlay files that are not
required on this system or may reference inappropriate system resources, for
example, BIOS addresses. Contact the option vendor to obtain the proper
CFG file.
Not all EISA products work together. EISA is an open standard, and not
every EISA product or combination of products can be tested. Violations of
specifications may matter in some configurations, but not in others.
Manufacturers of EISA options often test the most common combinations and
may have a list of ISA and EISA options that do not function in combination
with particular systems. Be sure to check the documentation or contact the
option vendor for the most up-to-date information.
EISA systems will not function unless they are first configured using the
ECU.
The ECU will not notify you if the configuration program diskette is writeprotected when it attempts to write the system configuration file (system.sci)
to the diskette.
Action
Confirm that the PCI module and any cabling are properly seated.
Storage adapterRun test to exercise the storage devices off the PCI
controller option (Section 3.3.1).
Check for a bad slot by moving the last installed controller to a different slot.
ftp://ftp.digital.com/pub/DEC/Alpha/systems/
http://www.service.digital.com/alpha/server/
The fail-safe loader (FSL) allows you to attempt to recover when one of the
following is the cause of a problem getting to the console program under normal
power-up:
Meaning
Floppy
Loader
Starting
CPU
FSL firmware found a valid boot block, loaded the program into memory,
and is attempting to transfer control to the loaded program.
MA00926
Bank
Jumper Setting
SROM memTest: memory test with backup and data cache disabled
SROM memTestCacheOn: memory test with backup and data cache enabled
AC power-up
DC power-up
The AlphaServer 1000A enclosure will not power up if the top cover is not
securely attached. Removing the top cover will cause the system to shut
down.
3. Test the system bus to PCI bus bridge and system bus to EISA bus bridge. If
the PCI bridge fails or EISA bridge fails, an audible error beep code (3-3-1)
sounds (Table 21). The power-up tests continue despite these errors.
4. Test the PCI-to-PCI bus bridge. If the bridge fails, an error beep code (3-3-2)
sounds.
5. Test the native SCSI controller. If the controller fails, an error beep code
(3-1-2) sounds.
6. Configure the memory in the system and test only the first 4 MB of memory.
If there is more than one memory module of the same size, the lowest
numbered memory module (one closest to the CPU) is tested first.
If the memory test fails, the failing bank is mapped out and memory is
reconfigured and re-tested. Testing continues until good memory is found. If
good memory is not found, an error beep code (1-3-3) is generated and the
power-up tests are terminated.
7. Check the data path to the FEPROM on the motherboard.
8. The console program is loaded into memory from the FEPROM on the
motherboard. A checksum test is executed for the console image. If the
checksum test fails, an error beep code (1-1-4) is generated, and the power-up
tests are terminated.
If the checksum test passes, control is passed to the console code, and the
console firmware-based diagnostics are run.
5. Enter console mode or boot the operating system. This action is determined
by the auto_action environment variable.
If the os_type environment variable is set to NT, the ARC console is loaded
into memory, and control is passed to the ARC console.
3
Running System Diagnostics
This chapter provides information on how to run system diagnostics.
Function
Reference
Acceptance Testing
test
Section 3.3.1
cat el
Section 3.3.2
more el
Section 3.3.2
Error Reporting
Extended Testing/Troubleshooting
memory
Section 3.3.3
net -ic
Section 3.3.7
net -s
Section 3.3.6
netew
Section 3.3.4
network
Section 3.3.5
Function
Reference
test lb
Section 3.3.1
netew
Section 3.3.4
network
Section 3.3.5
Loopback Testing
Diagnostic-Related Commands
kill
Section 3.3.8
kill_diags
Section 3.3.8
show_status
Section 3.3.9
3.3.1 test
The test command runs firmware diagnostics for the entire core system. The
tests are run concurrently in the background. Fatal errors are reported to the
console terminal.
The cat el command should be used in conjunction with the test command to
examine test/error information reported to the console event log.
Because the tests are run concurrently and indefinitely (until you stop them with
the kill_diags command), they are useful in flushing out intermittent hardware
problems.
Note
By default, no write tests are performed on disk and tape drives. Media
must be installed to test the floppy drive and tape drives. A loopback
connector is required for the COM2 (9-pin loopback connector, 12-2735101) port.
The test command does not test the DNSES, TGA card, reflective memory
option, nor third party options.
When using the test command after shutting down an operating system,
you must initialize the system to a quiescent state. Enter the following
commands at the SRM console:
P00>>> set auto_action halt
P00>>> init
...
P00>>> test
After testing is completed, set the auto_action environment variable to
its previous value (usually, boot) and use the Reset button to reset the
system.
The loopback option includes console loopback tests for the COM2 serial
port and the parallel port during the test sequence.
Examples:
In the following example, the system is tested and the tests complete successfully.
Note
Examine the console event log after running tests.
>>> test
Requires diskette and loopback connectors on COM2 and parallel port
type kill_diags to halt testing
type show_status to display testing progress
type cat el to redisplay recent errors
Testing COM2 port
Setting up network test, this will take about 20 seconds
Testing the network
48 Meg of System Memory
Bank 0 = 16 Mbytes(4 MB Per Simm) Starting at 0x00000000
Bank 1 = 16 Mbytes(4 MB Per Simm) Starting at 0x01000000
Bank 2 = 16 Mbytes(4 MB Per Simm) Starting at 0x02000000
Bank 3 = No Memory Detected
Device
Pass Hard/Soft Bytes Written Bytes Read
------------ ------ --------- ------------- ------------system
0
0
0
0
0
tta1
0
0
0
1
0
era0.0.0.2.1
43
0
0
1376
1376
memory
7
0
0
424673280
424673280
dka100.1.0.6
0
0
0
0
2688512
dka200.2.0.6
0
0
0
0
922624
In the following example, the system is tested and the system reports a fatal
error message. No network server responded to a loopback message. Ethernet
connectivity on this system should be checked.
>>> test
Requires diskette and loopback connectors on COM2 and parallel port
type kill_diags to halt testing
type show_status to display testing progress
type cat el to redisplay recent errors
Testing COM2 port
Setting up network test, this will take about 20 seconds
Testing the network
*** Error (era0), Mop loop message timed out from: 08-00-2b-3b-42-fd
*** List index: 7 received count: 0 expected count 2
>>>
3.3.3 memory
The memory command tests memory by running a memory exerciser each time the
command is entered. The exercisers are run in the background and nothing is
displayed unless an error occurs.
The number of exercisers, as well as the length of time for testing, depends on the
context of the testing. Generally, running three to five exercisers for 15 minutes
to 1 hour is sufficient for troubleshooting most memory problems.
To terminate the memory tests, use the kill command to terminate an individual
diagnostic or the kill_diags command to terminate all diagnostics. Use the
show_status display to determine the process ID when terminating an individual
diagnostic test.
Synopsis:
memory
Examples:
The following is an example with no errors.
>>> memory
>>> memory
>>> memory
Testing the memory
>>> show_status
ID
Program
-------- -----------00000001
idle
0000006b
memtest
00000071
memtest
00000077
memtest
>>> kill_diags
>>>
Device
Pass Hard/Soft Bytes Written Bytes Read
------------ ------ --------- ------------- ------------system
0
0
0
0
0
memory
1
0
0
53477376
53477376
memory
1
0
0
31457280
31457280
memory
1
0
0
24117248
24117248
The following is an example with a memory compare error indicating bad SIMMs.
>>> memory
>>> memory
>>> memory
*** Hard Error - Error #44 - Memory compare error
Diagnostic Name
memtest
Expected value:
Received value:
Failing addr:
ID
000000c8
00000004
80000001
800001c
1-JAN-2066
12:00:01
3.3.4 netew
The netew command is used to run MOP loopback tests for any EISA- or PCIbased ew* (DECchip 21040, TULIP) Ethernet ports. The command can also be
used to test a port on a live network.
The loopback tests are set to run continuously (-p pass_count set to 0). Use the
kill command (or Ctrl/C ) to terminate an individual diagnostic or the kill_diags
command to terminate all diagnostics. Use the show_status display to determine
the process ID when terminating an individual diagnostic test.
Note
While some results of network tests are reported directly to the console,
you should examine the console event log (using the cat el or more el
commands) for complete test results.
Synopsis:
netew
When the netew command is entered, the following script is executed:
net -sa ew*0>ndbr/lp_nodes_ew*0
set ew*0_loop_count 2 2>nl
set ew*0_loop_inc 1 2>nl
set ew*0_loop_patt ffffffff 2>nl
set ew*0_loop_size 10 2>nl
set ew*0_lp_msg_node 1 2>nl
net -cm ex ew*0
echo "Testing the network"
nettest ew*0 -sv 3 -mode nc -p 0 -w 1 &
The script builds a list of nodes for which to send MOP loopback packets, sets
certain test environment variables, and tests the Ethernet port by using the
following variation of the nettest exerciser:
netew ew*0 -sv 3 -mode nc -p 0 -w 1 &
Device
Pass Hard/Soft Bytes Written Bytes Read
------------ ------ --------- ------------- ------------system
0
0
0
0
0
ewa0.0.0.0.0
13
0
0
308672
308672
3.3.5 network
The network command is used to run MOP loopback tests for any EISA- or PCIbased er* (DEC 4220, LANCE) Ethernet ports. The command can also be used to
test a port on a live network.
The loopback tests are set to run continuously (-p pass_count set to 0). Use the
Ctrl/C ) to terminate an individual diagnostic or the kill_diags
command to terminate all diagnostics. Use the show_status display to determine
the process ID when terminating an individual diagnostic test.
Note
While some results of network tests are reported directly to the console,
you should examine the console event log (using the cat el or more el
commands) for complete test results.
Synopsis:
network
When the network command is entered, the following script is executed:
echo "setting up the network test, this will take about 20 seconds"
net -stop er*0
net -sa er*0>ndbr/lp_nodes_er*0
net ic er*0
set er*0_loop_count 2 2>nl
set er*0_loop_inc 1 2>nl
set er*0_loop_patt ffffffff 2>nl
set er*0_loop_size 10 2>nl
set er*0_lp_msg_node 1 2>nl
set er*0_mode 44 2>nl
net -start er*0
echo "Testing the network"
nettest er*0 -sv 3 -mode nc -p 0 -w 1 &
The script builds a list of nodes for which to send MOP loopback packets, sets
certain test environment variables, and tests the Ethernet port by using the
following variation of the nettest exerciser:
network er*0 -sv 3 -mode nc -p 0 -w 1 &
Device
Pass Hard/Soft Bytes Written Bytes Read
------------ ------ --------- ------------- ------------system
0
0
0
0
0
era0.0.0.0.0
13
0
0
308672
308672
3.3.6 net -s
The net -s command displays the MOP counters for the specified Ethernet port.
Synopsis:
net -s ewa0
Example:
>>> net -s ewa0
Status
ti: 72
rps: 0
tto: 1
counts:
tps: 0 tu: 47 tjt: 0 unf: 0 ri: 70 ru: 0
rwt: 0 at: 0 fd: 0 lnf: 0 se: 0 tbf: 0
lkf: 1 ato: 1 nc: 71 oc: 0
MOP BLOCK:
Network list size: 0
MOP COUNTERS:
Time since zeroed (Secs): 42
TX:
Bytes: 0 Frames: 0
Deferred: 1 One collision: 0 Multi collisions: 0
TX Failures:
Excessive collisions: 0 Carrier check: 0 Short circuit: 71
Open circuit: 0 Long frame: 0 Remote defer: 0
Collision detect: 71
RX:
Bytes: 49972 Frames: 70
Multicast bytes: 0 Multicast frames: 0
RX Failures:
Block check: 0 Framing error: 0 Long frame: 0
Unknown destination: 0 Data overrun: 0 No system buffer: 0
No user buffers: 0
>>>
Synopsis:
kill_diags
kill [PID . . . ]
Argument:
[PID . . . ]
show_status
3.3.9 show_status
The show_status command reports one line of information per executing
diagnostic. The information includes ID, diagnostic program, device under
test, error counts, passes completed, bytes written, and bytes read.
Many of the diagnostics run in the background and provide information only
if an error occurs. Use the show_status command to display the progress of
diagnostics.
The following command string is useful for periodically displaying diagnostic
status information for diagnostics running in the background:
>>> while true;show_status;sleep n;done
Where n is the number of seconds between show_status displays.
Synopsis:
show_status
Example:
>>> show_status
>>>show_status
ID
Program
-------- -----------00000001
idle
0000002d
exer_kid
0000003d
nettest
00000045
memtest
00000052
exer_kid
>>>
Device
Pass Hard/Soft Bytes Written Bytes Read
------------ ------ --------- ------------- ------------system
0
0
0
0
0
tta1
0
0
0
1
0
era0.0.0.2.1
43
0
0
1376
1376
memory
7
0
0
424673280
424673280
dka100.1.0.6
0
0
0
0
2688512
Process ID
Program module name
Device under test
Error count (hard and soft): Soft errors are not usually fatal; hard errors halt
the system or prevent completion of the diagnostics.
4
Error Log Analysis
This chapter provides information on how to interpret error logs reported by the
operating system.
Section 4.1 describes machine check/interrupts and how these errors are
detected and reported.
Section 4.2 describes the entry format used by the error formatters.
Section 4.3 describes how to generate a formatted error log using the
DECevent Translation and Reporting Utility available with OpenVMS and
Digital UNIX.
If possible, it corrects the problem and passes control to the operating system
for reporting before returning the system to normal operation.
EDC check bits on the data store, and parity on the tag
address store and tag control store.
Memory Subsystem
Memory SIMMs
System Motherboard
SCSI Controller
Single power supply failure when operating with redundant power supplies.
Maintaining and customizing the user environment with the interactive shell
commands
Note
Microsoft Windows NT does not currently provide bit-to-text translation
of system errors.
Section 4.3.1 summarizes the command used to translate the error log
information for the OpenVMS operating system using DECevent.
Section 4.3.2 summarizes the command used to translate the error log
information for the Digital UNIX operating system using DECevent.
5
System Configuration and Setup
This chapter provides configuration and setup information for AlphaServer 1000A
systems and system options.
Section 5.1 describes how to examine the system configuration using the
console firmware.
Section 5.1.1 describes the function of the two firmware interfaces used
with AlphaServer 1000A systems.
Sections 5.1.3 and 5.1.4 describe the commands used to examine system
configuration for each firmware interface.
Section 5.5 describes how ISA options are compatible on the EISA bus.
PCI-PCI
Bridge
CPU Card
SROM
21064
OLOGIC
ISP1020A
Fast-Wide
SCSI Bus
PCI Slots
PCI Slots
Bcache
2MB
TOY
OCP
PCI Slots
Flash
ROM
(1MB)
PCI Slots
EISA
Config
RAM
Epic
Comanche
PCI Slots
Decade
8242
Keybd &
Mouse
PCI Slots
Buffers
PCI Slots
Memory
(16MB-1GB)
EISA Slots
X-Bus
EISA Slots
SVGA
Cirrus
5422
PCI-EISA
Bridge
NS
87332
Primary
PCI Bus
Keyboard
Mouse
EISA Bus
Serial Ports
Floppy Port
Parallel Port
MA00946
Digital UNIX and OpenVMS Alpha are supported under the SRM command
line interface, which can be serial or graphical. The SRM firmware is in
compliance with the Alpha System Reference Manual (SRM).
The console firmware provides the data structures and callbacks available to
booted programs defined in both the SRM and ARC standards.
All console test and reporting commands are run from the SRM console.
Certain environment variables are changed using the SRM set command.
For example:
er*0_protocols
ew*0_mode
ew*0_protocols
ocp_text
pk*0_fast
pk*0_host_id
To run the ECU, you must enter the ecu command. This command will boot the
ARC firmware and the ECU software.
ARC Menu Interface
Systems running Windows NT access the ARC console firmware through menus
that are used to configure and boot the system, run the EISA Configuration
Utility (ECU), run the RAID Configuration Utility (RCU), adapter configuration
utility, or set environment variables.
You must run the EISA Configuration Utility (ECU) whenever you add,
remove, or move an EISA or ISA option in your AlphaServer system. The
ECU is run from diskette. Two diskettes are supplied with your system
shipment, one for Digital UNIX and OpenVMS and one for Windows NT. For
more information about running the ECU, refer to Section 5.6.
If you purchased a StorageWorks RAID Array 200 Subsystem for your server,
you must run the RAID Configuration Utility (RCU) to set up the disk
drives and logical units. Refer to StorageWorks RAID Array 200 Subsystems
Controller Installation and Standalone Configuration Utility Users Guide,
included in your RAID kit.
The EISA Configuration Utility (ECU) and the RAID Configuration Utility
(RCU) are run from the ARC interface.
The arc command loads the ARC firmware and switches to the ARC menu
interface.
The ecu command loads the ARC firmware and then boots the ECU diskette.
For systems that boot the Windows NT operating system, return to the ARC
console by setting the os_type environment variable to NT, then enter the init
command:
>>> set os_type NT
>>> init
The first screen displays system information, such as the memory, CPU type,
speed, NVRAM usage, the ARC version time stamp, and the type of video
option detected.
The second screen displays devices detected by the firmware, including the
monitor, keyboard, serial ports and devices on the SCSI bus. Tape devices are
displayed, but cannot be accessed from the firmware.
The third screen contains the PCI slot information: bus number, device
number, function number, vendor ID, revision ID, interrupt vector and device
type. All PCI network cards are displayed.
The fourth screen contains the EISA slot information: slot, device, and
identifier. All EISA network cards are displayed.
Action
Result
Table 52 explains the device names listed on the first screen of the hardware
configuration display.
Note
The available boot devices display marks tape devices as not used by the
firmware. All PCI and EISA network cards are listed under the PCI and
EISA screen displays.
Description
multi(0)key(0)keyboard(0)
multi(0)serial(0)
multi(0)serial(1)
eisa(0)video(0)monitor(0)
eisa(0)disk(0)fdisk(0)
scsi(0)disk(0)rdisk(0)
scsi(0)cdrom(5)fdisk(0)
21064
3
0x1
266.02 MHz
64 MB
2 MB
Wednesday
(continued on next page)
RZ29B
RRD43
(C)DEC007
(C) DEC 1084
Device
Type
------EISA bridge
PCI bridge
Ethernet
SCSI
Device
Other
Disk
Identifier
DEC5000
FLOPPY
Table 53 lists and explains the default ARC firmware environment variables.
Table 53 ARC Firmware Environment Variables
Variable
Description
A:
AUTOLOAD
CONSOLEIN
CONSOLEOUT
COUNTDOWN
ENABLEPCIPARITYCHECKING
FLOPPY
FLOPPY2
FWSEARCHPATH
KEYBOARDTYPE
TIMEZONE
VERSION
Note
The operating system or other programs, for example, the ECU, may
create either temporary or permanent environment variables for their
own use. Do not edit or delete these environment variables.
show config (Section 5.1.4.1)Displays the buses on the system and the
devices found on those buses.
show device (Section 5.1.4.2)Displays the devices and controllers in the
system.
set and show (Section 5.1.4.4)Set and display environment variable settings.
Firmware:
The version numbers for the firmware code, PALcode, SROM chip, and
CPU are displayed.
Memory:
The memory size and configuration for each bank of memory is displayed.
PCI Bus:
Bus 0, Slot 7 = PCI to EISA bridge chip
Bus 0, Slot 8 = PCI to PCI bridge chip
1
2
3
4
=
=
=
=
PCI1
PCI2
PCI3
PCI4
In the case of storage controllers, the devices off the controller are
also displayed.
Bus 0, Slots 1113 correspond to physical PCI card cage slots on the
primary PCI bus:
Slot 11 = PCI11
Slot 12 = PCI12
Slot 13 = PCI13
In the case of storage controllers, the devices off the controller are also
displayed.
EISA Bus:
Slot numbers correspond to EISA card cage slots (1 and 2). For storage
controllers, the devices off the controller are also displayed.
For more information on device names, refer to Figure 52. Refer to Figure 53
for the location of physical slots.
Synopsis:
show config
Example:
>>> show config
Firmware
SRM Console:
ARC Console:
PALcode:
Serial Rom:
X4.4-5365
4.43p
VMS PALcode X5.48-115, OSF PALcode X1.35-84
X2.1
Processor
DECchip (tm) 21064A-6
MEMORY
32 Meg of System Memory
Bank 0 = 32 Mbytes() Starting at 0x00000000
PCI Bus
Bus 00 Slot 07: Intel
SCSI Bus ID 7
RZ29B
RRD45
08-00-2B-E1-03-19
Note
The onboard SCSI controller (Qlogic 1020A) is always device pka.
The following show config example illustrates how PCI options that contain a
PCI-to-PCI bridge are represented in the display. For each option that contains a
PCI-to-PCI bridge, the bus number increments by 1, and the logical slot numbers
start anew at 0.
The sample system configuration contains the following options:
Primary Bus
Physical PCI slot 11: KZPSM option with PCI-to-PCI bridge
Physical PCI slot 12: KZPSM option with PCI-to-PCI bridge
Physical PCI slot 13:
Secondary Bus
Physical
Physical
Physical
Physical
PCI
PCI
PCI
PCI
slot
slot
slot
slot
1:
2:
3:
4:
Example:
>>> show config
Firmware
SRM Console:
ARC Console:
PALcode:
Serial Rom:
X4.4-5365
4.43p
VMS PALcode X5.48-115, OSF PALcode X1.35-84
X2.1
Processor
DECchip (tm) 21064A-6
MEMORY
32 Meg of System Memory
Bank 0 = 32 Mbytes() Starting at 0x00000000
PCI Bus
Bus 00 Slot 07: Intel
SCSI Bus ID 7
RZ29B
RRD45
08-12-2E-C3-04-92
08-24-3D-C6-08-04
Synopsis:
show device [device_name]
Argument:
[device_name]
MA00921
Example:
>>> show device
dka400.4.0.6.0
dva0.0.0.0.1
era0.0.0.2.1
pka0.7.0.6.0
>>>
DKA400
DVA0
ERA0
PKA0
RRD43 2893
08-00-2B-BC-93-7A
SCSI Bus ID 7
show memory
Example:
>>> show memory
48 Meg of System Memory
Bank 0 = 16 Mbytes(4 MB Per Simm) Starting at 0x00000000
Bank 1 = 16 Mbytes(4 MB Per Simm) Starting at 0x01000000
Bank 2 = 16 Mbytes(4 MB Per Simm) Starting at 0x02000000
Bank 3 = No Memory Detected
>>>
show envar
Arguments:
envar
value
Options:
-default
-integer
-string
Examples:
>>> set bootdef_dev eza0
>>> show bootdef_dev
eza0
>>> show auto_action
boot
>>> set boot_osflags 0,1
>>>
Table 54 Environment Variables Set During System Configuration
Variable
Attributes
Function
auto_action
NV,W
Attributes
Function
bootdef_dev
NV
boot_file
NV,W
boot_osflags
NV,W
Attributes
Function
bus_probe_
algorithm
NV
console
NV
ew*0_mode
NV
Attributes
Function
er*0_protocols,
ew*0_protocols
NV
os_type
NV
Attributes
Function
pci_parity
NV
Note
If you disable PCI parity, no parity checking is implemented for any PCI device,
even those devices in full compliance with
the PCI specification.
pk*0_fast
NV
Attributes
Function
pk*0_host_id
NV
pk*0_soft_term
NV
Enables or disables SCSI terminators. This environment variable applies to systems using the QLogic
ISP1020 SCSI controller.
The QLogic ISP1020 SCSI controller implements the
16-bit wide SCSI bus. The QLogic module has two
terminators, one for the 8 low bits and one for the high
8 bits. There are five possible values:
offTurns off both low 8 bits and high 8 bits.
lowTurns on low 8 bits and turns off high 8 bits.
highTurns on high 8 bits and turns of low 8 bits.
onTurns on both low 8 bits and high 8 bits.
diffPlaces the bus in differential mode.
Attributes
Function
tga_sync_green
NV
tt_allow_login
NV
Note
Whenever you use the set command to reset an environment variable,
you must initialize the system to put the new setting into effect. Initialize
the system by entering the init command or pressing the Reset button.
Diskette Drive
Connector
Upper Fan
Connector
Bank 3
Bank 2
Memory Module
Connectors (20)
Lower Fan
Connector
Bank 1
Bank 0
ECC Banks
CPU Module
Connector
NVRAM Chip
(E14 On Board)
EISA 1
EISA 2
PCI
Primary
Slots
PCI
Secondary
Slots
TOY/NVRAM Chip
(E78 On Board)
11
12
13
1
2
3
4
RCM Interconnect
Connector
RCM DC Enable
Connector
Removable Media
Internal SCSI
Connector
(50 Pin Narrow)
Speaker
Connector
StorageWorks
Internal SCSI
Connector
(68 pin Wide)
MA00923
APECS chipset, which provides logic for external access to the cache for main
memory control, and the PCI bus interface
SROM code (SROM tests are controlled by jumper J6 on the CPU daughter
board)
The motherboard has 20 SIMM connectors. The SIMM connectors are grouped in
four memory banks (0, 1, 2, and 3) and one bank for ECC (Error Correction Code)
memory (Figure 54).
Memory Configuration Rules
Observe the following rules when configuring memory on AlphaServer 1000A
systems:
A memory option consists of five SIMMs (0, 1, 2, 3 and 1 ECC SIMM for the
bank).
Memory Requirements
32 MB minimum; 64 MB recommended
Windows NT
16 MB minimum; 32 MB recommended
Windows NT Server
32 MB minimum; 64 MB recommended
Bank 3
Bank 2
Bank 1
Bank 0
ECC Banks
SIMM 1
SIMM 3
SIMM 0
SIMM 2
SIMM 1
SIMM 3
SIMM 0
SIMM 2
SIMM 1
SIMM 3
SIMM 0
SIMM 2
SIMM 1
SIMM 3
SIMM 0
SIMM 2
MA00327
5.3 Motherboard
The motherboard provides a standard set of I/O functions:
A Fast Wide SCSI controller chip (Qlogic 1020A) that supports up to 7 Fast
Wide SCSI drives
Two serial ports with full modem control and the parallel port
Connectors:
PCI bus connectors (Slots 11, 12, and 13before the bridge)
ISA boards have one row of contacts and no more than one gap.
EISA boards have two interlocking rows of contacts with several gaps.
ISA
EISA
MA00111
If you are configuring an EISA bus that contains only EISA options, refer
to Table 56.
If you are configuring an EISA bus that contains both ISA and EISA
options, refer to Table 57.
4. Locate the correct ECU diskette for your operating system. The ECU diskette
is shipped in the accessories box with the system. Make a copy of the
appropriate diskette, and keep the original in a safe place. Use the backup
copy for configuring options. The diskettes are labeled as follows:
From the Setup menu, select Run EISA configuration utility from
floppy. This boots the ECU program.
The system displays loading ARC firmware. When the firmware has
finished loading, the ECU program is booted.
3. Complete the ECU procedure according to the guidelines provided in the
following sections.
If you are configuring an EISA bus that contains only EISA options, refer
to Table 56.
Note
If you are configuring an EISA bus that contains both ISA and EISA
options, refer to Table 57.
4. After you have saved configuration information and exited from the ECU:
d. Select your operating system console, then press enter on the Setup
menu.
e.
Explanation
Note
It is not necessary to run Step 2 of the ECU,
Add or remove boards. (EISA boards are
recognized and configured automatically.)
View or Edit Details
(optional).
Explanation
Table 57 (Cont.) Summary of Procedure for Configuring EISA Bus with ISA
Options
Step
Explanation
MA00080
Install PCI boards according to the instructions supplied with the option. PCI
boards require no additional configuration procedures; the system automatically
recognizes the boards and assigns the appropriate system resources.
Warning: For protection against fire, only modules with currentlimited outputs should be used.
Physical PCI slots 11, 12, and 13 (primary PCI) are located before the bridge.
Physical PCI slots 1, 2, 3 and 4 (secondary PCI) are located behind the bridge.
Some PCI options are restricted to the primary PCI bus, slots 11, 12, and 13.
Refer to the following documents for restrictions on specific PCI options:
Dual bus Up to seven drives (bus A node IDs 03, bus B node IDs 02).
Narrow SCSI (8-bit) devices can be used in the wide StorageWorks shelf, as
long as the devices are at a supported revision level. The narrow devices will
run in narrow mode.
Narrow and wide devices can be mixed in the wide StorageWorks shelf. In a
mixed configuration, wide devices run in wide mode and narrow devices run
in narrow mode.
For best performance, wide devices should be operated in wide SCSI-2 mode.
Supported devices and configuration rules for wide SCSI-2 are described in the
Wide SCSI Technical Bulletin. This bulletin is frequently updated and can be
downloaded from the Internet:
Via FTP on ftp.digital.com Once connected, go to /pub/Digital/ Alpha/systems
Via the World Wide Web at http://www.service.digital.com/alpha/server
Consult your controller documentation for other requirements.
The device must be supported by the operating system. Consult the software
product description for the device or contact the hardware vendor.
Each device on the bus must have a unique SCSI ID. You may need to change
a devices default SCSI ID in order to make it unique. All removable-media
device bus node IDs are set via switches on the device. For information about
setting a devices ID, refer to the guide for that device.
The entire SCSI bus length, from end-to-end, must not exceed 3 meters for
Fast SCSI-2 at 10 MB/sec (6 meters at 5 MB/sec).
Ensure that the SCSI bus is properly terminated and that no devices in the
middle of the bus are terminated.
Configuration
Single
Dual
Triple
Bus ID 4
Bus ID 5
Bus A
12-45490-01
J10
0
J1
J12
2
J2
3
J11
J16
J14
17-04233-01
J13
5
12-41667-05
17-04021-01
J15
6
External
Terminator
W3
W2
W1
17-04022-01
J3
J17
StorageWorks
Backplane
(Rear)
StorageWorks
Shelf
(Front)
MA00900
Bus ID 4
Bus ID 5
Bus A
Bus B
J10
0
J1
Controller
Option
Card
J12
2
J2
3
J11
J16
J14
17-04233-01
12-41667-05
J13
1
12-45490-01
17-04022-01
J15
17-04019-01
12-41667-04
External
Terminators
2
W3
W2
W1
17-04022-02
J17
J3
StorageWorks
Backplane
(Rear)
StorageWorks
Shelf
(Front)
MA00950
Bus ID 4
Bus ID 5
Bus A
Bus B
Bus C
J10
0
J1
Controller
Option
Cards
J12
2
J2
3
J11
J16
J14
17-04233-01
12-41667-05
J13
1
17-04022-01
J15
17-04019-01
2
W3
W2
W1
12-41667-04
17-04022-01
J17
J3
StorageWorks
Backplane
(Rear)
StorageWorks
Shelf
(Front)
17-04019-01
12-41667-04
External
Terminators
MA00902
The combination of 3.3 V power and 5.0 V power cannot exceed 335 watts.
Single
UPS
UPS
MA00335
The H7290-AA power supply kit is used to order a second power supply and
current sharing cable.
Signal/Misc. Harness
(22-Pin/15-Pin)
+ 3.3V Harness
(20-Pin)
+ 5V Harness
(24-Pin)
17-03969-01
Current Sharing
Harness (3-Pin)
J12
Storage Harness
(12-Pin)
+ 5V Harness
(24-Pin)
J13
+ 3.3V Harness
(20-Pin)
Signal/Misc.
Harness (15-Pin)
MA00928
Description
console
tt_allow_login
serial
Example:
P00>>> set console serial
P00>>> init
.
.
. !Now switch to the serial terminal.
P00>>> show console
console
serial
Whenever you change the value of this environment variable, you must initialize
the firmware with the init command.
Example:
From the General menu, set the terminal mode to VTxxx, 8-bit controls.
From the Comm menu, set the character format to 8 bit, no parity, and
set receive XOFF to 128 or greater.
From the Keyboard menu, set the keyboard so that the tilde (~) key sends
the escape (ESC) signal.
2. Enter the following commands a the SRM console prompt to set the console
terminal to receive input in serial mode.
>>> set console serial
>>> init
.
.
. !Now switch to the serial terminal
>>> show console
console
serial
The on-board CIRRUS VGA options must be set to disabled through the ECU.
The VGA jumper (J27) on the upper-left corner of the motherboard must then
be set to disable (off).
If there are multiple VGA controllers, the system will direct console output to
the first controller it finds.
6
AlphaServer 1000A FRU Removal and
Replacement
This chapter describes the field-replaceable unit (FRU) removal and replacement
procedures for AlphaServer 1000A systems, which use a deskside wide-tower
enclosure.
Section 6.2 provides the removal and replacement procedures for the FRUs.
Description
Section
17-03970-02
Figure 65
17-03971-01
Figure 66
17-00083-09
Power cord
Figure 67
17-04195-01
Figure 68
70-31346-01
Section 6.2.2
17-03969-01
Figure 611
70-32283-01
Figure 612
17-04021-01
Figure 613
17-04022-01
Figure 614
17-04022-02
Figure 614,
Figure 615
17-04019-01
Figure 616
17-04233-01
Figure 617
54-23297-04
Section 6.2.3
54-23297-03
Section 6.2.3
Cables
CPU Modules
Description
Section
70-31350-01
92 mm fan
Section 6.2.4
70-31351-01
120 mm fan
Section 6.2.4
Fans
Internal StorageWorks
RZnn -VW
Section 6.2.5
54-23365-01
Section 6.2.6
12-45490-01
Figure 613
17-04021-01
Figure 613
Memory Modules
54-21225-BA
1 x 4MB SIMM
Section 6.2.7
54-21246-BA
1 x 8MB SIMM
Section 6.2.7
54-23170-BA
1 x 16MB SIMM
Section 6.2.7
54-21277-BA
1 x 32MB SIMM
Section 6.2.7
54-24123-AA
1 x 64 MB SIMM
Section 6.2.7
(continued on next page)
Description
Section
Interlock switch
Section 6.2.8
54-23499-01
System motherboard
Section 6.2.9
21-29631-02
Section 6.2.10
21-32423-01
Section 6.2.10
54-23302-02
OCP module
Section 6.2.11
30-43120-02
Section 6.2.12
70-31349-01
Speaker
Section 6.2.13
12-41667-05
12-41667-04
17-41667-02
12-27351-01
12-22196-01
12-35619-01
H8223
H8225
74-50062-01
Removable Media
RRDnn -CA
CDROM drives
Section 6.2.14
TLZnn -LG
Tape drives
Section 6.2.14
TZKnn -LG
Tape drives
Section 6.2.14
RXnn -AA
Floppy drive
Section 6.2.14
Tape Drive
Interlock
Switch
Interlock/Server
Management Cable
DC Cable
Assembly
CDROM Drive
Floppy Drive
Floppy Drive
Cable
OCP Module
OCP Cable
Hard Disk
Drives
Current Sharing
Cable
Power Supply
Power Supply
Storage Harness
StorageWorks Backplane
StorageWorks Jumper
Cable
MA00929
Upper Fan
SCSI Cables
Speaker
Lower Fan
Power Cord
SCSI Removable
Media Cable
Motherboard
MA00930
Unless otherwise specified, you can install an FRU by reversing the steps shown
in the removal procedure.
Figure 63 Opening Front Door
MA00909
Top Cover
Release Latch
MA00914
6.2.1 Cables
This section shows the routing for each cable in the system.
Figure 65 Floppy Drive Cable (34-Pin)
17-03970-02
MA01420
17-03971-01
MA01421
MA00338
Digital Number
BN09A-1K
17-00083-09
BN019H-2E
17-00198-14
BN19C-2E
17-00199-21
U.K., Ireland
BN19A-2E
17-00209-15
Switzerland
BN19E-2E
17-00210-13
Denmark
BN19K-2E
17-00310-08
Italy
BN19M-2E
17-00364-18
BN19S-2E
17-00456-16
Israel
BN18L-2E
17-00457-16
MA00931
Cable
Channel
Guide
MA01433
+ 3.3V Harness
(20-Pin)
+ 5V Harness
(24-Pin)
+ 5V Harness
(24-Pin)
+ 3.3V Harness
(20-Pin)
Signal/Misc.
Harness (15-Pin)
MA01434
70-31346-01
J12
Storage Harness
(12-Pin)
J13
MA01422
J254
MA00932
12-45490-01
J10
J1
J12
J2
J11
J16
J14
17-04233-01
12-41667-05
J13
17-04021-01
External
Terminator
W3
W2
W1
17-04022-02
J15
J3
J17
StorageWorks
Backplane
(Rear)
MA01427
J10
J1
Controller
Option
Card
J12
J2
J11
J16
J14
17-04233-01
12-41667-05
J13
12-45490-01
17-04022-01
J15
17-04019-01
W3
W2
W1
12-41667-04
External
Terminators
17-04022-02
J17
J3
StorageWorks
Backplane
(Rear)
MA01428
Note
Figure 614 shows the 17-04022-01 SCSI cable used from the native wide
SCSI controller to the J17 connector of the StorageWorks backplane,
and the 17-04022-02 SCSI cable used from the option controller to the
12-45490-01
J10
J1
J12
J2
J11
J16
J14
17-04233-01
12-41667-05
J13
17-04019-01
External
Terminator
W3
W2
W1
17-04022-02
J15
J3
J17
StorageWorks
Backplane
(Rear)
MA01429
J10
J1
Controller
Option
Card
J12
J2
J11
J16
J14
17-04233-01
12-41667-05
J13
12-45490-01
17-04022-02
J15
17-04019-01
W3
W2
W1
12-41667-04
External
Terminators
17-04022-02
J17
J3
StorageWorks
Backplane
(Rear)
MA01430
J10
J1
Controller
Option
Card
J12
J2
J11
J16
J14
17-04233-01
12-41667-05
J13
12-45490-01
17-04022-02
J15
17-04019-01
W3
W2
W1
12-41667-04
External
Terminators
17-04022-02
J17
J3
StorageWorks
Backplane
(Rear)
MA01431
Crossbar
Retaining
Screw
CPU Card
Handle
Clips
MA00312
Warning: CPU and memory modules have parts that operate at high
temperatures. Wait 2 minutes after power is removed before handling
these modules.
6.2.4 Fans
STEP 1: REMOVE THE CPU DAUGHTER BOARD AND ANY OTHER OPTIONS
BLOCKING ACCESS TO THE FAN SCREWS.
See Figure 618 for removing the CPU daughter board.
STEP 2: DISCONNECT THE FAN CABLE FROM THE MOTHERBOARD AND
REMOVE FAN.
Figure 619 Removing Fans
Upper Fan
Lower Fan
MA00311
MA00322
Rear Screws
6/32 Inch (4)
Internal Screws
3.5 mm (2)
Current Sharing
Harness (3-Pin)
Storage Harness
(12-Pin)
+ 5V Harness
(24-Pin)
+ 3.3V Harness
(20-Pin)
Signal/Misc.
Harness (15-Pin)
MA00933
MA00934
Bank 3
Bank 2
Bank 1
Bank 0
ECC Banks
SIMM 1
SIMM 3
SIMM 0
SIMM 2
SIMM 1
SIMM 3
SIMM 0
SIMM 2
SIMM 1
SIMM 3
SIMM 0
SIMM 2
SIMM 1
SIMM 3
SIMM 0
SIMM 2
MA00327
Warning: Memory and CPU modules have parts that operate at high
temperatures. Wait 2 minutes after power is removed before handling
these modules.
Caution
Do not use any metallic tools or implements including pencils to release
SIMM latches. Static discharge can damage the SIMMs.
Bank 3
Bank 2
Bank 1
Bank 0
ECC Banks
SIMM 1
SIMM 3
SIMM 0
SIMM 2
SIMM 1
SIMM 3
SIMM 0
SIMM 2
SIMM 1
SIMM 3
SIMM 0
SIMM 2
SIMM 1
SIMM 3
SIMM 0
SIMM 2
MA00315
Note
SIMMs can only be removed and installed in successive order. For
example; to remove a SIMM at bank 0, SIMM 1, SIMMs 0 and 1 for
banks 3, 2, and 1 must first be removed.
Bank 3
Bank 2
Bank 1
Bank 0
ECC Banks
SIMM 1
SIMM 3
SIMM 0
SIMM 2
SIMM 1
SIMM 3
SIMM 0
SIMM 2
SIMM 1
SIMM 3
SIMM 0
SIMM 2
SIMM 1
SIMM 3
SIMM 0
SIMM 2
MA00316
Note
When installing SIMMs, make sure that the SIMMs are fully seated. The
two latches on each SIMM connector should lock around the edges of the
SIMMs.
MA00935
6.2.9 Motherboard
STEP 1: RECORD THE POSITION OF EISA AND PCI OPTIONS.
STEP 2: REMOVE EISA AND PCI OPTIONS.
STEP 3: REMOVE CPU DAUGHTER BOARD.
Figure 627 Removing EISA and PCI Options
MA00936
Crossbar
Retaining
Screw
CPU Card
Handle
Clips
MA00312
Warning: CPU and memory modules have parts that operate at high
temperatures. Wait 2 minutes after power is removed before handling
these modules.
STEP 4: DETACH MOTHERBOARD CABLES, REMOVE SCREWS AND
MOTHERBOARD.
Caution
When replacing the system bus motherboard install the screws in the
order indicated.
2
1
MA01432
STEP 5: MOVE THE NVRAM CHIP (E14) AND NVRAM TOY CHIP (E78) TO THE
NEW MOTHERBOARD.
Move the socketed NVRAM chip (position E14) and NVRAM TOY chip (E78) to
the replacement motherboard and set the jumpers to match previous settings.
Note
The NVRAM TOY chip contains the os_type environment variable. This
environment variable may need to be reset (Section 5.1.4.4).
Diskette Drive
Connector
Upper Fan
Connector
Lower Fan
Connector
Bank 3
Bank 2
Memory Module
Connectors (20)
Bank 1
Bank 0
ECC Banks
TOY/NVRAM Chip
(E78 On Board)
CPU Module
Connector
NVRAM Chip
(E14 On Board)
EISA 1
EISA 2
PCI
Primary
Slots
PCI
Secondary
Slots
RCM DC Enable
Connector
11
12
13
1
2
3
4
Removable Media
Internal SCSI
Connector
(50 Pin Narrow)
Speaker
Connector
RCM Interconnect
Connector
StorageWorks
Internal SCSI
Connector
(68 pin Wide)
MA00923
6.2.10 NVRAM Chip (E14) and NVRAM TOY Clock Chip (E78)
See Figure 630 for the motherboard layout.
Note
The NVRAM TOY clock chip contains the os_type environment variable.
The default setting is for the SRM console for OpenVMS or Digital UNIX
operating systems.
MA01426
Remove
Hidden
Screws
Remove
Screws
MA00307
J254
Black/Red
(To Interlock
Switch)
Green/Yellow
(To Motherboard)
MA01423
Rear Screws
6/32 Inch (4)
Internal Screws
3.5 mm (2)
Current Sharing
Harness (3-Pin)
Storage Harness
(12-Pin)
+ 5V Harness
(24-Pin)
+ 3.3V Harness
(20-Pin)
Signal/Misc.
Harness (15-Pin)
MA00933
6.2.13 Speaker
Figure 635 Removing Speaker
MA01424
MA00324
MA00325
MA00326
A
Default Jumper Settings
This appendix provides the location and default setting for all jumpers in
AlphaServer 1000A systems:
Section A.1 provides location and default settings for jumpers located on the
motherboard.
Section A.2 provides the location and supported settings for jumpers J3 and
J4 on the CPU daughter board.
Section A.3 provides the location and default setting for the J1 jumper on the
CPU daughter board.
Flash ROM
VPP Enable (J50)
Force
Shutdown (J53)
Temperature
Shutdown (J52)
Fan Fault (J56)
SCSI
Termination (J51)
RCM DC
Enable (J25)
MA00924
Jumper Name
Description
Default Setting
J16
Large Fan
J25
Remote Console
Module (RCM)
DC Enable
J27
VGA Enable
J50
Jumper installed.
J51
J52
Temperature
Shutdown
J53
Force Shutdown
J55
Small Fan
J56
Fan Fault
J4
J3
MA00951
Supported settings:
J4 Jumper:
Off
Off
On
Off
On
J3 Jumper:
Off
J3
MA00791
Supported settings:
J4 Jumper:
Off
On
Off
Off
On
J3 Jumper:
Off
MA00926
Bank
Jumper Setting
SROM memTest: memory test with backup and data cache disabled
SROM memTestCacheOn: memory test with backup and data cache enabled
Glossary
10Base-T Ethernet network
IEEE standard 802.3-compliant Ethernet products used for local distribution of
data. These networking products characteristically use twisted-pair cable.
ARC
User interface to the console firmware for operating systems that require
firmware compliance with the Windows NT Portable Boot Loader Specification.
ARC stands for Advanced RISC Computing.
AUI Ethernet network
Attachment unit interface. An IEEE standard 802.3-compliant Ethernet network
connected with standard Ethernet cable.
autoboot
A system boot initiated automatically by software when the system is powered up
or reset.
availability
The amount of scheduled time that a computing system provides application
service during the year. Availability is typically measured as either a percentage
of uptime per year or as system unavailability, the number of hours or minutes of
downtime per year.
BA350 storage shelf
A StorageWorks modular storage shelf used for disk storage in some AlphaServer
systems.
backplane
The main board or panel that connects all of the modules in a computer system.
Glossary1
backup cache
A second, very fast cache memory that is closely coupled with the processor.
bandwidth
The rate of data transfer in a bus or I/O channel. The rate is expressed as the
amount of data that can be transferred in a given time, for example megabytes
per second.
battery backup unit
A battery unit that provides power to the entire system enclosure (or to
an expander enclosure) in the event of a power failure. Another term for
uninterruptible power supply (UPS).
boot
Short for bootstrap. To load an operating system into memory.
boot device
The device from which the system bootstrap software is acquired.
boot flags
A flag is a system parameter set by the user. Boot flags contain information that
is read and used by the bootstrap software during a system bootstrap procedure.
boot server
A computer system that provides boot services to remote devices such as network
routers.
bootstrap
The process of loading an operating system into memory.
bugcheck
A software condition, usually the response to softwares detection of an internal
inconsistency, which results in the execution of the system bugcheck code.
bus
A collection of many transmission lines or wires. The bus interconnects computer
system components, providing a communications path for addresses, data, and
control information or external terminals and systems in a communications
network.
Glossary2
bystander
A system bus node (CPU or memory) that is not addressed by a current system
bus commander.
byte
A group of eight contiguous bits starting on an addressable byte boundary. The
bits are numbered right to left, 0 through 7.
cache memory
A small, high-speed memory placed between slower main memory and the
processor. A cache increases effective memory transfer rates and processor speed.
Cache contains copies of data recently used by the processor and fetches several
bytes of data from memory in anticipation that the processor will access the next
sequential series of bytes.
card cage
A mechanical assembly in the shape of a frame that holds modules against the
system and storage backplanes.
carrier
The individual container for all StorageWorks devices, power supplies, and so
forth. In some cases because of small form factors, more than one device can
be mounted in a carrier. Carriers can be inserted in modular shelves. Modular
shelves can be mounted in modular enclosures.
CDROM
A read-only compact disc. The optical removable media used in a compact disc
reader.
central processing unit (CPU)
The unit of the computer that is responsible for interpreting and executing
instructions.
client-server computing
An approach to computing whereby a computerthe serverprovides a set of
services across a network to a group of computers requesting those servicesthe
clients.
Glossary3
cluster
A group of networked computers that communicate over a common interface.
The systems in the cluster share resources, and software programs work in close
cooperation.
cold bootstrap
A bootstrap operation following a power-up or system initialization (restart). On
Alpha based systems, the console loads PALcode, sizes memory, and initializes
environment variables.
commander
In a particular bus transaction, a CPU or standard I/O that initiates the
transaction.
command line interface
One of two modes of operation in the AlphaServer operator interface. The
command line interface supports the OpenVMS and Digital UNIX operating
systems. The interface allows you to configure and test the system, examine and
alter the system state, and boot the operating system.
console mode
The state in which the system and the console terminal operate under the control
of the console program.
console program
The code that executes during console mode.
console subsystem
The subsystem that provides the user interface for a computer system when the
operating system is not running.
console terminal
The terminal connected to the console subsystem. The terminal is used to start
the system and direct activities between the computer operator and the console
subsystem.
data bus
A bus used to carry data between two or more components of the system.
Glossary4
data cache
A high-speed cache memory reserved for the storage of data. Abbreviated as
D-cache.
DEC VET
Digital DEC Verifier and Exerciser Tool. A multipurpose system diagnostic tool
that performs exerciser-oriented maintenance testing.
diagnostic program
A program that is used to find and correct problems with a computer system.
Digital UNIX
A general-purpose operating system based on the Open Software Foundation
technology. Digital UNIX runs on the range of AlphaGeneration systems, from
workstations to servers.
direct-mapping cache
A cache organization in which only one address comparison is needed to locate
any data in the cache, because any block of main memory data can be placed in
only one possible position in the cache.
direct memory access (DMA)
Access to memory by an I/O device that does not require processor intervention.
DRAM
Dynamic random-access memory. Read/write memory that must be refreshed
(read from or written to) periodically to maintain the storage of information.
DSSI
Digitals proprietary data bus that uses the System Communication Architecture
(SCA) protocols for direct host-to-storage communications.
DSSI cluster
A cluster system that uses the DSSI bus as the interconnect between DSSI disks
and systems.
DUP server
Diagnostic Utility Program server. A firmware program on board DSSI devices
that allows a user to set host to a specified device in order to run internal tests or
modify device parameters.
Glossary5
ECC
Error correction code. Code and algorithms used by logic to facilitate error
detection and correction.
EEPROM
Electrically erasable programmable read-only memory. A memory device that can
be byte-erased, written to, and read from.
EISA bus
Extended Industry Standard Architecture bus. A 32-bit industry-standard I/O
bus used primarily in high-end PCs and servers.
EISA Configuration Utility (ECU)
A feature of the EISA bus that helps you select a conflict-free system
configuration and perform other system services. The ECU must be run
whenever you add or move an EISA or ISA controller.
environment variables
Global data structures that can be accessed only from console mode. The setting
of these data structures determines how a system powers up, boots the operating
system, and operates.
Ethernet
IEEE 802.3 standard local area network.
Factory Installed Software (FIS)
Operating system software that is loaded into a system disk during manufacture.
On site, the FIS is bootstrapped in the system.
fail-safe loader (FSL)
A program that allows you to power up without initiating drivers or running
power-up diagnostics. From the fail-safe loader you can reload console frimware
from a floppy diskette.
Fast SCSI
An optional mode of SCSI-2 that allows transmission rates of up to 10 megabytes
per second.
FDDI
Fiber Distributed Data Interface. A high-speed networking technology that uses
fiber optics as the transmissions medium.
Glossary6
FIB
Flexible interconnect bridge. A converter that allows the expansion of the system
enclosure to other DSSI devices and systems.
field-replaceable unit
Any system component that a qualified service person is able to replace on site.
firmware
Software code stored in hardware.
fixed-media compartments
Compartments that house nonremovable storage media.
Flash ROM
Flash-erasable programmable read-only memory. Flash ROMs can be bank- or
bulk-erased.
FRU
Field-replaceable unit. Any system component that a qualified service person is
able to replace on site.
full-height device
Standard form factor for 5 1/4-inch storage devices.
half-height device
Standard form factor for storage devices that are not the height of full-height
devices.
halt
The action of transferring control of the computer system to the console program.
hose
The interface between the card cage and the I/O subsystems.
hot swap
The process of removing a device from the system without shutting down the
operating system or powering down the hardware.
initialization
The sequence of steps that prepare the computer system to start. Occurs after a
system has been powered up.
Glossary7
instruction cache
A high-speed cache memory reserved for the storage of instructions. Abbreviated
as I-cache.
interrupt request lines (IRQs)
Bus signals that connect an EISA or ISA module (for example, a disk controller)
to the system so that the module can get the systems attention through an
interrupt.
ISA
Industry Standard Architecture. An 8-bit or 16-bit industry-standard I/O bus,
widely used in personal computer products. The EISA bus is a superset of the
ISA bus.
LAN
Local area network. A high-speed network that supports computers that are
connected over limited distances.
latency
The amount of time it takes the system to respond to an event.
LED
Light-emitting diode. A semiconductor device that glows when supplied with
voltage. A LED is used as an indicator light.
loopback test
Internal and external tests that are used to isolate a failure by testing segments
of a particular control or data path. A subset of ROM-based diagnostics.
machine check/interrupts
An operating system action triggered by certain system hardware-detected errors
that can be fatal to system operation. Once triggered, machine-check handler
software analyzes the error.
mass storage device
An input/output device on which data is stored. Typical mass storage devices
include disks, magnetic tapes, and CDROMs.
Glossary8
MAU
Medium attachment unit. On an Ethernet LAN, a device that converts the
encoded data signals from various cabling media (for example, fiber optic, coaxial,
or ThinWire) to permit connection to a networking station.
memory interleaving
The process of assigning consecutive physical memory addresses across multiple
memory controllers. Improves total memory bandwidth by overlapping system
bus command execution across multiple memory modules.
menu interface
One of two modes of operation in the AlphaServer operator interface. Menu mode
lets you boot and configure the Windows NT operating system by selecting choices
from a simple menu. The EISA Configuration Utility is also run from the menu
interface.
modular shelves
In the StorageWorks modular subsystem, a shelf contains one or more modular
carriers, generally up to a limit of seven. Modular shelves can be mounted in
system enclosures, in I/O expansion enclosures, and in various StorageWorks
modular enclosures.
MOP
Maintenance Operations Protocol. A transport protocol for network bootstraps
and other network operations.
motherboard
The main circuit board of a computer. The motherboard contains the base
electronics for the system (for example, base I/O, CPU, ROM, and console serial
line unit) and has connectors where options (such as I/Os and memories) can be
plugged in.
multiprocessing system
A system that executes multiple tasks simultaneously.
node
A device that has an address on, is connected to, and is able to communicate with
other devices on a bus. Also, an individual computer system connected to the
network that can communicate with other systems on the network.
Glossary9
NVRAM
Nonvolatile random-access memory. Memory that retains its information in the
absence of power.
OCP
Operator control panel.
open system
A system that implements sufficient open specifications for interfaces, services,
and supporting formats to enable applications software to:
Glossary10
portability
The degree to which a software application can be easily moved from one
computing environment to another.
porting
Adapting a given body of code so that it will provide equivalent functions
in a computing environment that differs from the original implementation
environment.
power-down
The sequence of steps that stops the flow of electricity to a system or its
components.
power-up
The sequence of events that starts the flow of electrical current to a system or its
components.
primary cache
The cache memory that is the fastest and closest to the processor.
processor module
Module that contains the CPU chip.
program mode
The state in which the system console terminal is under the control of a program
other than the console program.
RAID
Redundant array of inexpensive disks. A technique that organizes disk data to
improve performance and reliability. RAID has three attributes:
The users data is distributed across the physical set of drives in a defined
manner.
Redundant disk capacity is added so that the users data can be recovered
even if a drive fails.
redundant
Describes duplicate or extra computing components that protect a computing
system from failure.
Glossary11
reliability
The probability a device or system will not fail to perform its intended functions
during a specified time.
responder
In any particular bus transaction, memory, CPU, or I/O that accepts or supplies
data in response to a command/address from the system bus commander.
RISC
Reduced instruction set computer. A processor with an instruction set that is
reduced in complexity.
ROM-based diagnostics
Diagnostic programs resident in read-only memory.
script
A data structure that defines a group of commands to be executed. Similar to a
VMS command file.
SCSI
Small Computer System Interface. An ANSI-standard interface for connecting
disks and other peripheral devices to computer systems. Some devices are
supported under the SCSI-1 specification; others are supported under the SCSI-2
specification.
self-test
A test that is invoked automatically when the system powers up.
serial control bus
A two-conductor serial interconnect that is independent of the system bus. This
bus links the processor modules, the I/O, the memory, the power subsystem, and
the operator control panel.
serial ROM
In the context of the CPU module, ROM read by the DECchip microprocessor
after reset that contains low-level diagnostic and initialization routines.
SIMM
Single in-line memory module.
Glossary12
SRM
User interface to console firmware for operating systems that expect firmware
compliance with the Alpha System Reference Manual (SRM).
storage array
A group of mass storage devices, frequently configured as one logical disk.
StorageWorks
Digitals modular storage subsystem (MSS), which is the core technology of the
Alpha SCSI-2 mass storage solution. Consists of a family of low-cost mass storage
products that can be configured to meet current and future storage needs.
superscalar
Describes a processor that issues multiple independent instructions per clock
cycle.
symmetric multiprocessing (SMP)
A processing configuration in which multiple processors in a system operate as
equals, dividing and sharing the workload.
symptom-directed diagnostics (SDDs)
An approach to diagnosing computer system problems whereby error data logged
by the operating system is analyzed to capture information about the problem.
system bus
The hardware structure that interconnects the CPU and memory modules. Data
processed by the CPU is transferred throughout the system through the system
bus.
system disk
The device on which the operating system resides.
TCP/IP
Transmission Control Protocol/Internet Protocol. A set of software
communications protocols widely used in UNIX operating environments.
TCP delivers data over a connection between applications on different computers
on a network; IP controls how packets (units of data) are transferred between
computers on a network.
Glossary13
Glossary14
write back
A cache management technique in which data from a write operation to cache is
written into main memory only when the data in cache must be overwritten.
write-enabled
Indicates a device onto which data can be written.
write-protected
Indicates a device onto which data cannot be written.
write through
A cache management technique in which data from a write operation is copied to
both cache and main memory.
Glossary15
Index
A
A: environment variable, 57
AC power-up sequence, 224
Acceptance testing, 318
arc command, 54
ARC interface, 53
switching to SRM from, 54
AUTOLOAD environment variable, 58
B
Beep codes, 22, 221, 225, 226
Boot diagnostic flow, 16
Boot menu (ARC), 211
C
Card cage location, 523
cat el command, 211, 37
CDROM LEDs, 217
CFG files, 219
COM2 and parallel port
loopback tests, 34
Commands
diagnostic, summarized, 32
diagnostic-related, 33
firmware console, functions of, 18
to examine system configuration, 54
to perform extended testing and
exercising, 33
Configuration
See also ECU
console port, 543
Configuration (contd)
EISA boards, 531
ISA boards, 532
of environment variables, 515
power supply, 540, 541
verifying, OpenVMS and Digital UNIX,
59
verifying, Windows NT, 54
Console
diagnostic flow, 14
firmware commands, 18
Console commands, 18
cat el, 37
diagnostic and related, summarized,
32
kill, 316
kill_diags, 316
memory, 38
more el, 37
net -ic, 315
net -s, 314
netew, 310
network, 312
set bootdef_dev, 516
set boot_osflags, 516
set envar, 515
show auto_action, 516
show config, 59
show device, 514
show envar, 515
show memory, 515
show_status, 317
test, 34
Index1
D
DC power-up sequence, 225
DEC VET, 18, 318
DECevent, 17
Device naming convention
SRM, 514
Devices
Windows NT firmware device display,
56
Windows NT firmware device names,
55
dia command, 46
DIAGNOSE command, 45
Diagnostic flows
boot problems, 16
console, 14
errors reported by operating system,
17
power, 13
problems reported by console, 15
RAID, 214
Diagnostics
command summary, 32
command to terminate, 33, 316
console firmware-based, 226
firmware power-up, 225
Index2
Diagnostics (contd)
power-up, 21
power-up display, 21
related commands, 33
related commands, summarized, 32
ROM-based, 17, 31
serial ROM, 225
showing status of, 317
Digital Assisted Services (DAS), 111
Digital UNIX
event record translation, 46
E
ECU
ecu command, 54, 529
invoking console firmware, 528
procedure for running, 528
procedures, 531
starting up, 528
ECU revisions, 110
EISA boards
configuring, 531
EISA bus
features of, 526
problems at power-up, 218
troubleshooting, 218
troubleshooting tips, 219
EISA devices
Windows NT firmware device names,
55
Environment variables
A:, 57
AUTOLOAD, 58
configuring, 515
CONSOLEIN, 57
CONSOLEOUT, 57
COUNTDOWN, 58
default Windows NT firmware, 57
ENABLEPCIPARITYCHECKING, 57
FLOPPY, 57
FLOPPY2, 58
FWSEARCHPATH, 57
other, 58
setting and examining, 515
TIMEZONE, 57
F
Fail-safe loader, 221
activating, 221
power-up using, 221
Fan failure, 13
Fast Track Service Help File, 19
Fault detection/correction, 41
KN22A processor module, 41
Motherboard, 41
SIMM memory, 41
Firmware
console commands, 18
device names, ARC, 56
diagnostics, 31
environment variables, ARC, 58
power-up diagnostics, 225
Fixed media
storage problems, 212
Floppy drive
LEDs, 217
FLOPPY environment variable, 57
H
Hot swap, 623
I
I/O bus, EISA features, 526
Information resources, 19
Initialization, 318
Interfaces
switching between, 54
Internet files
Firmware updates, 19
OpenVMS patches, 110
supported options list, 110
technical information, 110
ISA boards
configuring, 532
J
Jumpers
on daughter board, A4, A6
on motherboard, A2
K
kill command, 316
kill_diags command, 316
L
LEDs
CDROM drive, 217
floppy drive, 217
storage device, 215
StorageWorks, 215
Index3
Logs
event, 17
Loopback tests, 18
COM2 and parallel ports, 34
command summary, 33
M
Machine check/interrupts, 42
processor, 42
processor corrected, 42
system, 42
Maintenance strategy, 11
service tools and utilities, 17
Mass storage
described, 534
Mass storage problems
at power-up, 212
fixed media, 212
removable media, 212
memory command, 38
Memory module
configuration, 524
displaying information for, 515
minimum and maximum, 524
Memory tests, 25
Memory, main
exercising, 38
Modules
CPU, 524
memory, 524
motherboard, 525
more el command, 37
Motherboard, 525
N
net -ic command, 315
net -s command, 314
netew command, 310
network command, 312
Index4
O
OpenVMS
event record translation, 45
Operating system
boot failures, reporting, 17
crash dumps, 19
exercisers, 18
Operator interfaces, switching between,
54
Options
system bus, 523
P
PBXGA, 545
PCI bus
problems at power-up, 220
troubleshooting, 220
troubleshooting tips, 220
PCI-to-PCI bridge, 534
Power problems
diagnostic flow, 13
Power supply
cables, 542
configuration, 540, 541
redundant, configuring, 540
Power-on tests, 224
Power-up
diagnostics, 225
displays, interpreting, 21
screen, 29
sequence, 224
AC, 224
DC, 225
Power-up test description and FRUs, 29
Processor machine check, 43
Processor-corrected machine check, 44
R
RAID
diagnostic flow, 214
RAID problems, 214
Removable media
storage problems, 212
ROM-based diagnostics (RBDs), 17
diagnostic-related commands, 33
performing extended testing and
exercising, 33
running, 31
utilities, 32
S
SCSI bus
on-board, 534
SCSI devices
Windows NT firmware device names,
55, 56
Serial ports, 544
Serial ROM diagnostics, 225
Service
tools and utilities, 17
set command (SRM), 515
show command (SRM), 515
show configuration command (SRM), 59
show device command (SRM), 514
show memory command (SRM), 515
show_status command, 317
SIMMs, 524
troubleshooting, 25
SRM interface, 53
switching to ARC from, 54
SROM memory tests, 25
Storage device LEDs, 215
Storage shelf
See StorageWorks
StorageWorks
internal, 534
internal, configuring, 538, 539
LEDs, 215
System
architecture, 52
options, 523
power-up display, interpreting, 21
troubleshooting categories, 12
System bus
location, 523
System machine check, 43
System module devices
Windows NT firmware device names,
55
T
test command, 34
Testing
See also Commands; Loopback tests
acceptance, 318
command summary, 32
commands to perform extended
exercising, 33
memory, 38
with DEC VET, 318
TGA card, 545
tga_sync_green, 545
TIMEZONE environment variable, 57
Tools, 17
console commands, 17, 18
crash dumps, 19
DEC VET, 18
DECevent, 17
error handling, 17
log files, 17
loopback tests, 18
RBDs, 17
Training, 111
Troubleshooting
See also Diagnostics; RAID diagnostic
flow
See also RAID diagnostic flow
actions before beginning, 11
boot problems, 16
categories of system problems, 12
crash dumps, 19
diagnostic flows, 14, 15, 16, 17
Index5
Troubleshooting (contd)
EISA problems, 218
error report formatter, 17
errors reported by operating system,
17
interpreting error beep codes, 22
mass storage problems, 212
PCI problems, 220
power problems, 13
problem categories, 12
problems getting to console, 14
problems reported by the console, 15
RAID, 214
RAID problems, 214
Index6
SIMMs, 25
with DEC VET, 18
with loopback tests, 18
with operating system exercisers, 18
with ROM-based diagnostics, 17
W
Windows NT firmware
Available hardware devices display,
56
default environment variables, 57
device names, 55
Technical Support
If you need help deciding which documentation best meets your needs, call 800-DIGITAL
(800-344-4825) and press 2 for technical assistance.
Electronic Orders
If you wish to place an order through your account at the Electronic Store, dial
800-234-1998, using a modem set to 2400- or 9600-baud. You must be using a VT
terminal or terminal emulator set at 8 bits, no parity. If you need assistance using
the Electronic Store, call 800-DIGITAL (800-344-4825) and ask for an Electronic Store
specialist.
Call
Write
U.S.A.
DECdirect
Phone: 800-DIGITAL
(800-344-4825)
Fax: (603) 884-5597
Puerto Rico
Canada
Phone: 800-267-6215
Fax: (613) 592-1946
International
Internal Orders1
(for software
documentation)
DTN: 264-3030
(603) 884-3030
Fax: (603) 884-3960
Internal Orders
(for hardware
documentation)
DTN: 264-3030
(603) 884-3030
Fax: (603) 884-3960
1 Call
Readers Comments
AlphaServer 1000A
Service Guide
EKALPSVSV. A01
Your comments and suggestions help us improve the quality of our publications.
Thank you for your assistance.
Excellent
Good
Fair
For software manuals, please indicate which version of the software you are using:
Name/Title
Dept.
Company
Date
Mailing Address
Phone
Poor
No Postage
Necessary
If Mailed
in the
United States