Use this troubleshooting process if one or several devices function incorrectly or not at all. This process focuses on your operating system, which is where the problem probably might be.
Process
Step 1. 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 devices should work.
If the device doesn't work, contact Digi Technical Support.
Make note of the results and continue to the next step.
Step 2. Check the LED indicators on the PortServer. Is OFC on?
If OFC is not on, continue to the next step.
Step 3. 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, call Digi Technical Support.
Step 4. Test the connection 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 5. Verify that the RealPort daemon is running on the Linux system by entering:
ps -ef | grep drpdDoes 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, call 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 6.
Step 6. Enable the forcecd setting on the port with this command:
ditty-rp -n /device forcecdwhere
/deviceis 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.
Contact Digi Technical Support.
