User Guide

124 Server Operating System Administration Guide
Server Operating System Administration Guide
103-000148-001
August 30, 2001
Novell Confidential
Manual 99a38 July 17, 2001
 Check the cabling for interference from fluorescent lights, microwaves,
radar, X-rays, and copy machines. Either move the cable or shield it from
the source of interference.
 Take a sniffer or LAN trace of the problem and analyize it.
 As a last resort, perform a core dump (see “Creating a Core Dump” on
page 112) and contact a Novell Support technician.
Server Console Hangs
If the server console locks up so that you cannot enter commands, but there is
no abend message on the System Console or Logger screen, follow these steps
to troubleshoot the problem. If there is an abend message on the screen, see
“Resolving Abends” on page 116.
1 Verify whether you can toggle among console screens.
If yes, the problem might be caused by high server utilization. See “High
Utilization Statistics” on page 125. If no, continue with the following
steps.
2 Verify whether the server console hangs when you unload a specific
NLM.
If yes, the NLM is probably the source of the problem. Contact the NLM
vendor.
3 Make sure you are using the latest disk and LAN drivers, BIOS, and
firmware.
If not, update disk and LAN drivers. For information on NetWare drivers,
see “Keeping Your Servers Patched” on page 106.
4 Verify whether the server console hangs after you mounted the last
volume.
If yes, the network board might not be seated correctly or might not be
configured correctly. Check the board and its configuration and correct
any problems.
5 Verify whether you can you break into the debugger by pressing
Shift+Shift+Alt+Esc on the system console keyboard.
6 If the console is locked, you can’t toggle among screens and you can’t
enter the debugger, contact Novell Technical Support or your computer
vendor to learn how to generate a nonmaskable interrupt to shut down the
server.