### Master Troubleshooting Process: Linux (All Devices Fail)

Use this Master Troubleshooting Process if none of the devices are functioning.

In many of the steps, you will be sent to another shorter procedure that you need to complete. Once you have completed the procedure, you most often will be sent back to the Master Troubleshooting Process to continue with where you left off. Otherwise, you might be directed to contact Digi Technical Support.

Process

Step 1. Check the status of the PortServer. Is AC displayed on the PortServer?

> Continue with the next step. | Do the following steps: Reboot the PortServer. If AC now is displayed, go to Step 2 to verify your network connection. Go to Running PortServer Diagnostics or Running PortServer II Diagnostics. If the PortServer is TFTP-booting firmware, go to Troubleshooting TFTP. If the PortServer is booting from internal firmware, continue with the next step. Note: TFTP booting may be bypassed by simultaneously pressing and releasing the two arrows on the front of the PortServer during a TFTP boot. Go to Resetting PortServer.

Step 2. To verify the network connection, telnet to the PortServer.

> From the UNIX RealPort host root prompt, enter:

> > `telnet ipaddress`

> > where `ipaddress` is the IP address of the PortServer.

> Did you receive a PortServer login prompt?

> Go to Telnet: Receiving a Login Prompt. | You might have a network, cable or hub problem. You need to check this. Go to Telnet: Receiving No Login Prompt.

Step 3. Test the port connection from the operating system. Go to Testing the Port Connection.

> Do the DTR and RTS indicator lights on the PortServer flash briefly and do you get data results and port status information on your terminal screen?

> Your connection was successful. Your device should work. If the device doesn't work, call Digi Technical Support. | Make note of the results and continue to the next step.

Step 4. Check the LED indicators on the PortServer. Is OFC on?

> Go to Checking the LED Indicators: OFC On? | If OFC is not on, continue to the next step.

Step 5. Telnet directly to the port. Go to Performing a Telnet to the Port.

> When you entered the command on the keyboard, did the word, "Connected," appear on the screen?

> Also, anything you entered should appear on the attached terminal and anything entered on the dumb terminal should appear on your telnet screen. This verifies that the port is functional, along with the attached cable and terminal while bypassing RealPort. Disconnect from the telnet session. Go to Disconnecting Telnet. | If the host cannot telnet to the port, then RealPort won't connect to it. Check the previous set commands on the PortServer and try the command again. If you still do not get any results, contact Digi Technical Support.

Step 6. Test the connections from each terminal. Go to Testing the Terminal Connection.

> Does the date appear on the terminal?

> The device is properly connected. Continue with the next step. | If nothing appears on the terminal, the device is not receiving data. Go to Testing the Terminal Connection: No Data. If scrambled characters appear on the screen, the device is receiving data but there is still something wrong. Go to Testing the Terminal Connection: Scrambled Data.

Step 7. Verify that the RealPort daemon is running on the Linux system by entering:

> > `ps -ef | grep drpd`

> Does the IP address assigned to the daemon match the IP address assigned to PortServer?

> Your devices should now be working properly. If they still do not work correctly, contact Digi Technical support. | Do the following: Change either: The IP address of the PortServer to match the IP address assigned to the daemon The IP address of the daemon to match the IP address of the PortServer. See Managing PortServers with Digi RealPort Manager and Managing PortServers with dgrp_cfg_node. Reboot the UNIX server. Your devices should now be in an available state and working properly. If they are not, go to Step 8.

Step 8. Enable the forcedcd setting on the port with this command:

> > `ditty-rp -n /device forcedcd`

> > where `/device` is the device path and name of your port.

> Do your devices work correctly now?

> Place the ditty-rp command in a startup file to make the setting permanent: You have completed the Master Troubleshooting Process. | Call Digi Technical Support.