NS3000/iX Operations and Maintenance Reference Manual (36922-90039)

68 Chapter5
Common Network Problems
Investigate the Link
Investigate the Link
The following is a strategy to use to identify and solve link problems.
You should use this strategy if you are not sure what is causing the
problem because many times errors in the upper level software are due
to hardware problems. You can also use this strategy if you have
identified a hardware-related possible cause and need to isolate the
actual cause.
LAN, Token Ring, FDDI, 100VG-AnyLAN,
100Base-T Link Problems
For problems that involve LAN, Token Ring, FDDI, 100VG-AnyLAN, or
100Base-T link, use the following strategy where applicable:
• Issue the LINKCONTROL linkname; STATUS=DIAGSTATS command.
Inspect the output and attempt to identify the problem. Refer to the
Online Diagnostic Subsystem Manual, Volume I, for a detailed
analysis of the fields displayed. Retain a copy of the output from this
command for your Hewlett-Packard representative.
• Run PING to confirm whether or not the remote node is reachable.
See Chapter 6, “Using NETTOOL,” for instructions on running
PING.
•IfPING fails, use the LAN node diagnostic that is appropriate for the
type of card on your system:
Card Online Diagnostic
LAN LANDAD
LAN3PBB
CONSOLAN
Token Ring LAN5PBB
FDDI FDDIPBA
100VG-AnyLAN VGPBA
100Base-T VGPBA
Refer to your hardware documentation for information on these
diagnostics. These diagnostics are online tools that verify the
hardware components by running the self-test, then a series of tests
of the cables and connectors.
• If a failure has taken place, give the files NMLGxx.PUB.SYS and
NETDMPnn.PUB.SYS to your Hewlett-Packard representative for
additional analysis.