 |
» |
|
|
|
The first step in investigating nodal problems is to examine
any error message returned. Error messages returned by NS 3000/iX
and associated links are listed in the NS 3000/iX Error
Messages Reference Manual, along with their meaning
and recommended recovery action. If you have received a specific error message, find it in
the manual and take the action recommended. Only if there is no
clear error or the recommended action does not correct the problem
is it necessary to investigate further. Follow the strategy shown
in Figure 4-1 “Characterizing the Problem”. Recent Changes | |
If you begin experiencing problems immediately following either
a new installation or changes to the software or hardware, often
you can easily identify what is causing the problem. Table 5-1 “Nodal Troubleshooting Strategy ” shows the symptoms and
possible causes for a new installation, changed software and changed
hardware, respectively. This table also suggests a course of action
for situations where no recent changes have been made. Once you have identified the possible cause, you may need
to isolate the actual cause. Proceed to Investigate the Software
or Investigate the Link, depending on the nature of the possible
cause. For more information on some of the possible causes, including
what to do when you have isolated the actual cause, proceed to Determine
the Action. If the recommended action is to contact an HP representative,
use the guidelines in Appendix A of the NS 3000/iX Error
Messages Reference Manual. Table 5-1 Nodal Troubleshooting Strategy Changes | Symptom | Possible Causes |
|---|
New installation | Console locked or hung;serious failures. | Software installation invalid. | | System abort | Configuration incorrect, serious internal
error. | Software changes | System abort | Configuration incorrect, serious internal
error. | | DSCOPY
command aborts. | NFTCAT.NET.SYS
is bad; incompatible version, or MAKECAT
was not done. | Hardware changes | Unable to use NS. | For LAN, LAN card not properly connected
to MAU or network cable, (LOOP, twisted pair) or cable not properly
installed (missing or bad terminator, twisted pair not connected
to hub). For Fiber Distributed Data Interface/iX, either the Media
Interface Connector (MIC) receptacle is not properly connected to
the FDDI device adapter or the FDDI concentrator. For NS 3000/iX
Point-to-Point, either the PSI card is not properly connected to
the cable, or the cable is improperly installed (missing or bad
terminator). Also check all modem or other connections. For DTC/X.25
iX Network Links, the DTC/X.25 Network Access card may not be properly
installed in the DTC. | No changes | Unable to use services or a warning that
old services are being used. | NSCONTROL
has been stopped or network has been shut down, or NSCONTROL
has been issued to limit the number of active servers. | | Cannot connect to remote system. | See "Line Opening Errors." |
|
