Table of Contents
Advertisement
Problem
The server's DECnet load host is not on the same Ethernet.
Correction: Have the network manager assign one of the nodes on
the server's Ethernet to be a load host for the MUXserver 100.
Have the load host's system manager add the server to his database
by running the MSV ACONF'IG program.
Correction: Reconfigure the network to ensure that the load host is
on the same physical Ethernet as the server.
Problem
Transmissions between the MUXserver 100 and the load host fail
because of Ethernet circuit problems.
Correction: Have the systerIl manager of a DECnet Phase IV node
execute the NCP LOOP CIRCUIT command with the MUXserver
100 as the target node. The LAT Network Manager's Guide de-
scribes the LOOP CIRCUIT command. The NCP facility shows the
results of the loopback test at the DECnet node.
4.2.5 Message Number 913 Appears
If
message number 913 appears on
th€~
supervisor port terminal, it means that
the MUXserver 100 detected an internal fatal error (fatal bugcheck).
A software problem, or bug, is likely to cause only intermittent fatal bugchecks
of the MUXserver 100. Your unit may operate again for a period of time and
then fail again. If there is more than one server on the Ethernet, the bug is
likely to affect all the units.
If the fatal error was a hardware error, the problem probably affects only one
of several MUXserver 100 units. The hardware problenl may be intermittent
and only occasionally affect the unit.
After a fatal bugcheck, the server automatically executes its self-test and re-
quests a down-line load of the server software. If the green light is off or an
error message is displayed after the self-test, go to Section 4.2.1, Server Green
Light Off, or 4.2.2, Error Message On the Supervisor Port. Otherwise, take the
following steps.
CHAPTER 4 IVIUXserver 100 TROUBLESHOOTING
17
Advertisement
Table of Contents
