E
Error messages, A–5
DEC MicroServer, C–5
Errors
BIND request, 1–47
CRC, 1–11, 1–52
Frame too long, 1–12
Receive overrun, 1–11
transmission, 1–52
Ethernet address, finding, 1–18
Event messages, A–2 to A–3
Event types, A–4
Event types/end, A–4
Executor loopback tests, 2–7 to 2–8
G
Gateway Management traces, 3–1 to 3–2
physical unit level, 3–1
SDLC circuit level, 3–1
session level, 3–1
Gateway-ST problems
cannot be loaded, 1–16
circuit not active, 1–29
dial-up line failures, 1–9
network object unknown at remote node,
1–36
no access name recognition, 1–42
no DECnet node name recognition, 1–34
no LU name recognition, 1–44
no PU name recognition, 1–43
restricted ON state, 1–40
when system unreachable, 1–39
Generalized PIU trace, 3–3 to 3–4
H
Halt codes, C–5
Hardware address, 1–18
Hardware problems, 1–1 to 1–14
DEC MicroServer power up failure, 1–3
faulty synchronous port, 1–8
Gateway-ST boots, dial-up fails, 1–9
Hardware problems (cont’d)
Gateway-ST loads, but some lines do not
come up, 1–13
line counter Receive failures, 1–11
remote modem connection failure, 1–7
Help
at remote console, D–11
I
IBM parameters, 1–27, 1–29
IBM sense codes, 1–46, A–6
IBM traces, 3–2 to 3–5
generalized PIU, 3–3
SDAID Trace program, 3–4
VTAM buffer contents, 3–3
VTAM internal, 3–5
VTAM line, 3–4
Initialization problems, 1–15 to 1–36
circuits not active, 1–29
DEC MicroServer unexpected software
loaded, 1–21
DECnet node name not recognized, 1–34
Errors in Gateway-ST initialization
process, 1–32
Gateway-ST cannot be loaded, 1–16
Gateway-ST loads, but some lines do not
come up, 1–27
Gateway-ST network object unknown at
remote node, 1–36
load command not working, 1–23
no event messages, 1–25
PU does not become active, 1–31
receive aborted service request events,
1–22
snaevl not running, 1–25
with inconsistent access names, 1–35
with inconsistent components, 1–35
L
Line problems
dial-up failure, 1–9
Index–2
