Troubleshooting Pathway [ Troubleshooting Terminal, Printer, and Serial Device Connections ] MPE/iX 5.0 Documentation
Troubleshooting Terminal, Printer, and Serial Device Connections
Troubleshooting Pathway
A practiced method for problem resolution is to first identify the
problem and then identify alternative causes of that problem. Break the
big problem into smaller, more manageable components. By breaking the
problem into manageable and testable components, the cause can be easily
isolated. A recommended troubleshooting pathway is shown in figure 2-1.
Figure 2-1. Troubleshooting Pathway
Each of the numbered circles is a task used to troubleshoot problems in
networking environments. By completing these tasks, isolation of the
cause of the problem is likely to occur; this is the most difficult part
of troubleshooting. After the cause of the problem has been identified,
take an appropriate action to resolve the problem. Each task is
described below.
1. Troubleshooting at the Device. First, do some simple
verifications at the device. This can rule out causes such as
improper device settings and loose connections. Simple
observations can also indicate if the problem is system-wide. The
verifications require no particular expertise; they are
appropriate for general users. After this, it will be clear if
more detailed device, DTC, or LAN testing is needed.
2. Testing DTC-Device Connections. If necessary, use TermDSM for
more detailed diagnostics. This must be done at another device or
the console. Test DTC-device connections first. This can detect
faults within the device, the device cable, and parts of the DTC
circuitry. If DTC-device connections are not causing the problem,
further DTC diagnostics are suggested.
3. Testing the DTC. Using TermDSM, perform a DTC selftest. The
selftest can detect faults within specific field replaceable units
(FRU) of the DTC. If the DTC passes the selftest, the fault might
be in the LAN. Proceed with LAN diagnostics.
4. Testing the LAN. LAN troubleshooting is beyond the scope of this
manual. It generally requires special tools and the expertise of
an HP support representative.
Procedures to follow for the first three tasks in the troubleshooting
pathway are summarized in the pages that follow.
MPE/iX 5.0 Documentation