HPlogo DTC Device File Access Utilities and Telnet Port Identification: HP 9000 Computers > Chapter 6 Simple DDFA Troubleshooting

Troubleshooting Outgoing Connections

» 

Technical documentation

Complete book in PDF

 » Table of Contents

 » Index

Outgoing connections use ocds to send output to serial devices such as printers and plotters. Use this list of tasks to isolate problems due to syntax errors, incorrect port addresses, telnet operation, ocd processes, pty device files, or the system data path.

Check for Syntax Errors

Because dpp parses the dp file and tries to execute an ocd process for each valid entry, problems associated with dpp usually involve incorrect command line syntax, or references to illegal or non-existent files on the dpp command line. This class of problem will usually affect all ports configured in the dp file. The dpp error messages are listed in Appendix A of this manual.

Check for Incorrect Addresses

DDFA supports several different port addressing formats (See Chapter 3). If a ping to the IP address of the DTC or other terminal server fails, then you may have an IP configuration problem.

Verify the correct IP address of the DTC or other terminal server by cross-checking the dp file, and the server configuration.

Verify the TCP port associated with a DTC port to which you are trying to connect using the formula.

TCP_port = ( 32 * board + port + 1 ) * 256 +23

Check Telnet Operation

Verify that you can use telnet to access the port:

telnet <DTC or Server IP Addr> <TCP port>

If this command fails, then the port is probably in use, is not set up correctly, or may be broken. If the telnet connection succeeds, then ocd should also succeed.

Verify ocd

Check to see if the ocd process is running.

ps -ef | grep ocd

Look at the ocd command line to make sure you have the correct syntax and values for IP address of the DTC or non-DTC server. (Note: Board and port apply to DTCs only.)

Check the pty

Make sure the pty has a character special device file with access rights of rw-rw-rw and a major number of 17. The minor numbers will always be different.

ll   /dev/telnet/<devfilename>

The resulting display should look something like this:

crw-rw-rw-  1  root  sys  17  0x000030 Jan  20  10:15  /dev/telnet/dtc1b0p0

Check System Level Data Path

Verify that system level processes are working properly.

cat /etc/services  >  /dev/telnet/<devfilename>

At the system level, ocd, cat and all other applications use the same outbound data path. If this data is sent to the device correctly, it proves that it is possible to detect the opened device file, open a connection to the DTC or non-DTC server, and send the data to the desired port. If this fails, then it indicates the need to troubleshoot ocd. Refer to the ocdebug man page for details.

© 1995 Hewlett-Packard Development Company, L.P.