Table of Contents
Advertisement
4.1 WHAT TO DO FIRST
To begin troubleshooting, find out first if the problem affects all the ports or
only some of the ports.
•
When the problem involves all the ports, do the following:
1.
If
message nunlber 913 appears on the supervisor port terminal,
go no further in this sequence of steps. Refer directly to Section
4.2.5, Message Nunlber 913 Appears.
2.
If
the terminal users can still enter MUXserver 100 commands
at their terminals, have them finish their active sessions. Then
have them log out their terminals.
If
they cannot use their termi-
nals, go on to Step 3.
3.
Initialize the MUXserver 100 by turning the power switch OFF,
wait for ten seconds, then turn it on again. (This is a "power-up"
of the server). The server executes its diagnostic self-test. After
about 20 seconds, the green light on the server stays off or
comes on, and status messages are output to the supervisor port
terminal.
4.
If
the green light on the back of the unit stays off, go on to
Section 4.2.1, Server Green Light Off.
•
If
the green light stays on take note of the error message displayed
on the Supervisor Port terminal.
If
an ERROR MESSAGE appears,
refer to Appendix A, Section A.2.5 (Supervisor Port Message Codes
900-999). The text in this appendix will refer you to a trouble shoot-
ing procedure on this chapter.
•
If
the message indicates that the 'Downline Load is Complete' but
'Composite Link A' or 'Composite Link B' is DOWN, refer to Section
4.3, PROBLEMS INVOLVING THE COMPOSITE LINKS.
•
If
the problem affects only terminals associated with a particular
DECmux II unit, refer to Section 4.3.
•
If
the problem affects individual terminals, refer to Section 4.4,
PROBLEMS INVOLVING INDIVIDUAL PORTS.
The diagnostic self-test is an important feature of the MUXserver 100. During
the self-test, internal software checks the state of a number of hardware com-
ponents. The green light on the server shows the result of the test.
6
CHAPTER 4 MUXserver 100 TROUBLESHOOTING
Advertisement
Table of Contents
