Table of Contents
Advertisement
Terminal server checks
If following the steps in Table 18 did not correct the problem, continue with the
steps shown in "Terminal server connection failure" on page 69.
68
Installation and Service
Table 18. Troubleshooting the terminal server network for the Remote Console
Symptom
1. Unable to execute rconsole commands
and get an active terminal session.
Action
1. Check conncection of cables and
connectors at the nodes and the InReach
terminal server.
2. Verify the InReach terminal server is
powered up and functional by pinging
the unit at 172.30.20.1.
3. Follow steps 1 through 9 of
"Configuration and setup after device
replacement" on page 90, then at the
*IN-Reach_Priv>* prompt type show port
<portnumber> to verify the settings of all
suspect ports against ports that are
working correctly.
4. Verify the InReach terminal server is
powered up and functional by pinging
the unit at 172.30.20.1
5. Ensure the serial port (COM 1) is
configured to redirect output to the
terminal server. Take the following steps:
v Restart the node and watch the
monitor screen.
v When the message Press F1 for
Configuration/Setup appears, press
F1.
v From the main menu, select Devices
and I/O Ports then press Enter.
v Verify that Serial Port A is set to Port
3F8, IRQ 4.
v Select Serial Port A.
v Select Remote Console Redirection.
v Verify the following settings:
Remote Console Active [Enabled]
Remote Console Com Port [COM1]
Remote Console Baud Rate [9600]
Remote Console Data Bits [8]
Remote Console Parity [None]
Remote Console Stop Bits [1]
Remote Console Emulation [VT100]
Remote Console Active After Boot
[Enabled]
v Save settings and exit.
6. Swap out cables and dongle with known
good units.
7. Run diagnostics against the serial port to
certify function.
Advertisement
Table of Contents
Troubleshooting
