AT&T 3B2 Series User manual
NOTICE
The
information
in
this
document
is subject to
change
without
notice. AT&T
assumes
no
responsibility for
any
errors
that
may
appear
in this
document.
Copyright©
1989 AT&T
All Rights Reserved
Printed
in
U.s.A.
TRADEMARKS
The
following is a listing
of
the
trademarks
that
are
used
in
this
manual:
• INTEL -Registered
trademark
of
Intel Corporation
• UNIX -Registered
trademark
of
AT&T
•
WE
-Registered
trademark
of
AT&T
ORDERING
INFORMATION
Additional
copies
of
this
document
can
be
ordered
by
calling
Toll free: 1-800-432-6600 In
the
U.S.A.
1-800-255-1242 In
Canada
Toll: 1-317-352-8557 Worldwide
OR
by
writing to:
AT&T
Customer
Information
Center
Attn:
Customer
Service Representative
P.O. Box 19901
Indianapolis,
IN
46219
TRAINING
INFORMATION
The
AT&T Education
and
Training
Catalogue
of
Courses
and
course
schedules
are free
and
can
be
ordered
by
contacting
your
account
executive
or
by
calling toll free:
1-800-554-6400 (extension 7150)
Training
information
can
also
be
accessed electronically
through
our
computerized
catalogue:
DIAL: 1-800-662-0662
or
1-614-764-5566
LOGIN: comcats
PASSWORD: 88cat
Table
of
Contents
1 Introduction 1-1
General
1-1
Manual
Organization 1-3
2 Using Diagnostics 2-1
Introduction 2-1
Procedures for Using Diagnostics 2-2
3 System Board Diagnostics 3-1
Introduction 3-1
Version 2
Hardware
System
Board Diagnostics 3-2
Version 3
Hardware
System
Board Diagnostics
3-66
4 Multiprocessor Diagnostics 4-1
Introduction 4-1
Phase
Descriptions 4-2
5 Cartridge
Tape
Controller Diagnostics 5-1
Introduction 5-1
Phase
Descriptions 5-2
6 Intelligent Serial Controller Diagnostics 6-1
Introduction
6-1
Phase
Descriptions 6-2
7
Network
Interface Diagnostics 7-1
Introduction 7-1
Phase
Descriptions 7-2
TABLE
OF
CONTENTS
Table
of
Contents
8 PORTS Diagnostics 8-1
Introduction
8-1
Phase
Descriptions 8-2
9 EPORTS Diagnostics 9-1
Introduction
9-1
Phase
Descriptions 9-2
10
Remote
Management
Diagnostics 10-1
Introduction
10-1
Phase
Descriptions 10-2
11
Expansion Disk Controller Diagnostics 11-1
Introduction
11-1
Phase
Descriptions 11-2
12
Math
Accelerator Unit Diagnostics 12-1
Introduction
12-1
Phase
Descriptions 12-2
13
Virtual
Cache
Diagnostics 13-1
Introduction
13-1
Phase
Descriptions 13-2
14
Small
Computer
System Interface Diagnostics 14-1
Introduction
14-1
Phase
Descriptions 14-2
15
STARLAN Interface Diagnostics 15-1
Introduction
15-1
Phase
Descriptions 15-2
ii
OFF-LINE
DIAGNOSTIC
MANUAL
-------------------------Table
of
Contents
16 General
Purpose
Synchronous
Controller
Introduction
Phase
Descriptions
Glossary
Index
16-1
16-1
16-2
G-l
1-1
TABLE
OF
CONTENTS
iii
TableofContents--------------------------------------------------------------
iv
OFF-LINE
DIAGNOSTIC
MANUAL
List
of
Figures
Figure 6-1:
Figure 6-2:
Figure 6-3:
Figure 8-1:
ISC to ASCII Terminal
Connection
for
Debug
Operation
ISC Loopback
Connection
for
Phases
15
and
16
ISC Loopback
Connection
for
Phases
17
and
18
Loop
Around
Plug
Wiring
6-24
6-26
6-30
8-45
LIST
OF
FIGURES
v
Chapter
1:
Introduction
General
1-1
Standard
Format 1-1
Conventions
Explanation
of
VOID/NULL
in
the
Equipped
Device Table
Manual
Organization
TABLE
OF
CONTENTS
1-1
1-2
1-3
General
This
manual
contains
the
diagnostic
phases
and
tests
that
run
on
the
AT&T 3B2
computer
system.
Diagnostics
are
available for all versions
of
the
System
Board (SBD),
the
Math
Accelerator
Unit
(MAU),
the
Small
Computer
System
Interface (SCSI),
and
the
feature cards
that
can
be
plugged
into
the
3B2
computer.
Standard
Format
To
ensure
consistency,
each
phase
and
test description are
presented
in
a
standard
format. Each
phase
description defines
the
phase
name,
type,
and
function. A list
of
the
associated tests,
as
well
as
the
approximate
times
required
to
run
them,
is also
provided.
Any
important
warnings
and
notes
about
a
phase
are
also given.
The
standard
phase
format is as follows:
Phase
Name:
Type:
Function:
Test(s):
Time:
Warnings:
Notes:
Each
individual
test description
provides
the
test
number,
its function,
and
the
procedure
it uses.
The
hardware
tested
and
any
data
returned
are
also
noted
in
the
test description.
Any
notes
about
a
test
are
also given.
The
following
shows
the
standard
test format:
Test Number(s):
Function:
Procedure:
Hardware
Tested:
Data
Returned:
Notes:
Conventions
This
document
contains
sample
displays
which
will
help
you
understand
described procedures.
The
sample
displays
in
this
document
and
the
displays
on
your
terminal screen
may
differ slightly
due
to
improvements
in
the
product
after this
document
was
published.
Therefore,
use
the
displays
in
this
document
as
samples
of
the
types
of
data
available.
However,
the
data
displayed
on
your
terminal
screen
accurately reflects
the
software
on
your
computer.
The
following
conventions
are
used
in
this
manual
to
show
your
terminal
input
and
the
system
output.
INTRODUCTION
1-1
General--------------------------------------------------------------------------------
This
style
of
type
is
used
to
show
system
generated
responses
that
are
displayed
on
your
screen.
Bold
type
is
used
to
show
inputs
entered
from
your
keyboard
that
are
displayed
on
your
screen.
The
symbols
<
and
>
identify
inputs
from
the
keyboard
that
are
not
displayed
on
your
screen,
such
as:
<CR>
carriage
return,
<CTRL
d>
control
d,
<ESC
g>
escape
g,
passwords,
and
tabs.
This style of italic type
is
used
for
notes that
provide
you
with additional information.
Explanation
of
VOID/NULL
in
the
Equipped
Device
Table
Upon
powerup
initialization
or
reset
of
the
3B2
computer,
the
Equipped
Device Table (EDT) is
created.
The
EDT is
used
to indicate
what
device is
in
a particular 3B2
computer
Input/Output
(I/O)
slot.
Each
time
the
system
is reset,
the
Identification (ID)
code
for
each
device is
written
into
the
EDT.
The
filledt
program
uses
the
ID codes to
determine
the
type
of
device
in
each
slot.
The
device
names
are
written
into
the
EDT
by
filledt.
The
information
in
the
EDT is
used
when
running
diagnostics.
The
ID is
read
from
the
ID
/Vector
register.
If
a device is detected in
an
I/O
slot
and
its ID is
not
recognized
by
filledt,
the
EDT will
show
that
device as VOID.
If
a
subdevice
has
an
ID
of
OxO,
it will
be
shown
in
the
EDT as NULL.
To
determine
if
the
VOID
or
NULL conditions exist,
boot
the
Diagnostic
Monitor
(DGMON).
Once
DGMON
is
booted,
perform
the
following
command:
DGMON>
show
<CR>
If
the
3B2
computer
is
equipped
with
a given device,
and
the
software associated
with
that
device
has
been
loaded,
the
EDT
should
list
that
device.
If
a given device is
not
listed
in
the
EDT,
but
VOID
or
NULL is,
that
device
may
be
considered
a
suspect
when
trying to locate a
problem.
1-2
OFF-LINE
DIAGNOSTIC
MANUAL
Manual
Organization
The
remainder
of
this
manual
is
organized
as
follows:
•
Chapter
2,
"Using
Diagnostics,"
contains
guidelines explaining
what
diagnostics
are
and
how
to
use
them.
•
Chapter
3,
"System
Board Diagnostics,"
provides
descriptions of
the
diagnostic
phases
and
tests
that
run
on
two
versions
of
the
System
Board (SBD). This
chapter
also
contains
diagnostics
of
the
Math
Accelerator
Unit
when
those
diagnostics
are
part
of
the
system
board
diagnostics.
•
Chapter
4,
"Multiprocessor
Diagnostics," contains a description of
the
diagnostic
phases
and
tests
that
run
on
the
Multiprocessor
Enhancement
card.
•
Chapter
5,
"Cartridge
Tape
Controller
Diagnostics,"
provides
descriptions
of
the
diagnostic
phases
and
tests
that
run
on
the
Cartridge Tape Controller (CTC) card.
•
Chapter
6,
"Intelligent
Serial
Controller
Diagnostics,"
contains
descriptions
of
the
diagnostic
phases
and
tests
that
run
on
the
Intelligent Serial Controller (ISC) card.
•
Chapter
7,
"Network
Interface Diagnostics," gives descriptions
of
the
diagnostic
phases
and
tests
that
run
on
the
Network
Interface (NI) card.
•
Chapter
8,
"PORTS
Diagnostics," gives descriptions
of
the
diagnostic
phases
and
tests
that
run
on
the
PORTS card.
•
Chapter
9,
"EPORTS
Diagnostics," gives descriptions
of
the
diagnostic
phases
and
tests
that
run
on
the
EPORTS card.
•
Chapter
10,
"Remote
Management
Diagnostics," contains a description
of
the
diagnostic
phases
and
tests
that
run
on
the
Remote
Management
card.
•
Chapter
11,
"Expansion
Disk Controller Diagnostics," gives descriptions
of
the
diagnostic
phases
and
tests
that
run
on
the
Expansion Disk Controller (XDC) card.
•
Chapter
12,
"Math
Accelerator
Unit
Diagnostics,"
provides
a description
of
diagnostic
phases
and
tests
that
run
on
the
Math
Accelerator Unit.
•
Chapter
13,
"Virtual
Cache
Diagnostics," contains a description
of
the
diagnostic
phases
and
tests
that
run
on
the
Virtual
Cache
(VCACHE) card.
•
Chapter
14,
"Small
Computer
System
Interface Diagnostics," contains a description
of
the
diagnostic
phases
and
tests
that
run
on
the
Small
Computer
System
Interface.
•
Chapter
15, "STARLAN Interface Diagnostics," contains a description
of
the
diagnostic
phases
and
tests
that
run
on
the
STARLAN Local Area
Network
Interface.
•
Chapter
16,
"General
Purpose
Synchronous
Controller Diagnostics,"
contains
a description
of
the
diagnostic
phases
and
tests
that
run
on
the
General
Purpose
Synchronous
Controller
(GPSC-3B) card.
INTRODUCTION
1-3
Chapt.,
2:
Using
Diagnostics
Introduction
Types
of
Diagnostic
Phases
Procedures
for Using Diagnostics
Diagnostics
Run
During
Powerup
How
to
Go
From
the
UNIX
Operating
System
to
the
Firmware
Mode
How
to
Enter
the
Interactive
Firmware
Mode
How
to
Enter
the
Interactive Diagnostic
Monitor
Diagnostic
Monitor
Commands
How
to
Run
Diagnostics
Examples
of
Diagnostic Requests
Diagnostic
Report
Messages
How
to
Leave
the
Interactive Diagnostic
Monitor
How
to
Boot
From
the
Firmware
to
the
UNIX
Operating
System
How
to
Power
Down
From
the
Firmware
Mode
Recommended
Procedure
for
Running
Diagnostics
2-1
2-1
2-2
2-2
2-3
2-6
2-6
2-8
2-12
2-13
2-15
2-18
2-18
2-19
2-20
TABLE
OF
CONTENTS
Introduction
Diagnostics
are
used
to identify
and
locate
hardware
problems
in
the
3B2
computer
system. Five
versions
of
the
System
Board (SBD) as well
as
the
feature cards
and
all
add-on
hardware
items
have
off-line diagnostics.
By
running
these
diagnostics,
you
should
be
able to
pinpoint
the
source
of
a
problem
to a particular
component
of
the
hardware
device. All diagnostics
are
functionally
organized
into
groups
called
phases.
Each
phase
consists
of
one
or
more
diagnostic tests. For example,
three
diagnostic
phases
(I,
2,
and
3)
run
on
the
3B2
computer
Math
Accelerator
Unit
(MAU). Diagnostic tests
are
normally
stored
on
the
system
hard
disk.
The
control
program
for diagnostics
runs
in
the
firmware
mode.
Therefore,
to
run
diagnostics,
the
3B2
computer
must
be
in
the
firmware
mode.
No
other
users
can
be
logged
on
while
the
system
is
in
the
firmware
mode.
The
diagnostic
phases
run
sequentially. This
means
that
only
after all
of
the
tests
of
one
diagnostic
phase
are
completed,
is
the
next
phase
started.
Once
an
individual
phase
is started, its tests
continue
until
all
the
tests
pass
or
until
one
test fails. Failure
of
a test
prevents
subsequent
phases
from
running
(command
options
are
available
which
cause
testing
to
continue
even
if a
phase
fails).
Each diagnostic
phase
generates
a
report
of
its activity.
These
reports
are
displayed
as
diagnostic
messages
on
the
system
console. Each
message
reports
the
phase
and
test
number(s)
and
whether
the
phase
passed
or
failed.
The
phase
and
test
number(s)
can
be
used
to refer to
the
phase
and
test
descriptions
provided
in
this
manual.
Types
of
Diagnostic
Phases
The
3B2
computer
has
three
types
of
diagnostic phases:
Normal
Demand
Interactive
Normal
diagnostic
phases
are
the
standard
diagnostics
that
run
each
time
the
system
is
powered
up
or
taken
to
the
firmware
mode
and
rebooted.
The
SBD
and
each
feature
card
in
the
3B2
computer
have
a set
of
normal
diagnostics. You
can
also
manually
request
normal
diagnostics to
run
using
the
Diagnostic
Monitor
(DGMON)
firmware
program.
Demand
diagnostic
phases
consist
of
more
extensive tests.
Some
of
the
demand
diagnostics check
optional
3B2
computer
hardware;
others
require
more
system
resources to
run.
For
these
reasons,
demand
diagnostics
are
not
run
during
powerup.
You
can
only
run
demand
diagnostics
with
manual
requests to
the
DGMON
firmware
program.
Interactive diagnostics
must
also
be
requested
manually
with
the
DGMON
firmware
program.
The
interactive diagnostics consist
of
tests
that
require
your
input
and/or
special test conditions. For example,
two
interactive
phases
on
the
Peripheral
Ports
C;ontroller (PORTS) card require
that
a special test cable
be
attached.
Be
sure
that
you
understand
the
function
of
an
interactive diagnostic
before
requesting
it
because
a few
of
the
interactive
phases
can
adversely
affect
the
system
software. For example,
one
interactive diagnostic
may
destroy
the
contents
of
the
Nonvolatile
Random
Access
Memory
(NVRAM) if
there
is
an
early
abort
or
reset.
Another
interactive diagnostic overwrites
the
contents
of
the
Time-of-Day clock.
The
system
informs
you
about
the
requirements
and
impact
of
an
interactive diagnostic,
and
the
system
asks
you
to confirm
that
you
want
the
diagnostic to run.
USING
DIAGNOSTICS
2-1
Procedure$
for
Using
Diagnostics
The
following
procedures
explain
what
you
need
to
know
to
be
able to
run
diagnostics
on
the
3B2
computer.
The
procedures
are
given
in
sequential
order
from
power
up
to
power
down.
Diagnostics
Run
During
Powerup
When
the
3B2
computer
is
powered
up,
the
Power
and
Diagnostic indicators
on
the
front
of
the
unit
come
on
simultaneously. After a few seconds,
the
message
SELF-CHECK is
displayed
on
the
system
console. This
message
indicates
that
the
basic
system
sanity
tests
have
started.
If
a basic
sanity
test fails
the
Diagnostic indicator will begin flashing
in
a
pattern.
The
flashes
on
the
Diagnostic indicator
are
the
only
way
for
you
to
know
that
a
sanity
test failed.
The
number
of
flashes
on
the
Diagnostic indicator
represent
the
following failures:
• 1
flash-The
system
completed
the
basic
sanity
tests
and
is
ready
for
the
firmware
password,
but
no
system
console device is connected.
Check
the
console
and/or
cable
connection
to
the
system.
• 2
flashes-The
processor is
not
working
correctly.
• 3
flashes-There
are
problems
in
Programmable
Read
Only
Memory
(PROM).
• 4
flashes-The
Random
Access
Memory
(RAM) (first 16 kilobytes) failed
pattern
tests.
• 5
flashes-The
Dual
Universal
Asynchronous
Receiver/Transmitter
(DUART) failed
transmission
tests.
For
these
problems,
call
your
AT&T Service Representative
or
authorized
dealer.
By
knowing
the
number
of
flashes
on
the
Diagnostic indicator,
your
AT&T Service Representative
or
authorized
dealer
will
have
a
better
idea
of
the
equipment
to bring.
If
the
basic
sanity
tests pass,
the
message
DIAGNOSTICS is
displayed
on
the
system
console.
The
system
then
runs
all
normal
diagnostic
phases
on
itself.
Demand
and
interactive diagnostic
phases
are
not
run
during
powerup.
It
takes
approximately
2
minutes
for
the
system
to
run
all
of
the
normal
diagnostics.
The
exact
amount
of
time required to
run
diagnostics
depends
on
the
system's
hardware
configuration.
The
Diagnostic indicator stays
on
until all
of
the
diagnostics
complete
successfully
or
one
of
the
diagnostics tests fail.
If
all
of
the
diagnostics pass,
the
message
PASSED is
displayed
on
the
system
console after
the
DIAGNOSTICS message,
and
the
Diagnostic indicator goes off.
If
a diagnostic test
failed,
the
message
FAILED is
displayed
after
the
DIAGNOSTICS message. A SYSTEM FAILURE
message
is also
displayed
when
a diagnostic test fails.
The
Diagnostic indicator
remains
on
after a
diagnostic failure.
The
system
can
be
placed
in
the
firmware
mode
by
entering
the
firmware
password
(see
the
procedure
"How
to
Enter
Interactive
Firmware
Mode").
By
putting
the
system
into
the
firmware
mode,
you
can
rerun
the
diagnostics to
determine
which
diagnostic test failed.
2-2
OFF-LINE
DIAGNOSTIC
MANUAL
Other manuals for 3B2 Series
5
Table of contents
Other AT&T Desktop manuals
