Products Applications Support Partners News About Digi Where to Buy
   
 
 
Technical Support

drivers
firmware upgrades
FAQs
product documentation
cabling
support tools
legacy products
about digi support
knowledge base
online support request
support feedback
support feedback
FTP site
inside out networks
 
 
Testing and Troubleshooting a PortServer Port
www.digi.com
  Advanced Search
Product Selector
     
  Technical Support
Drivers

Firmware Upgrades

FAQs

Product Documentation

Cabling

Support Tools

Legacy Products

About Digi Support

Knowledge Base

Online Support Request

FTP Site



Related Links
Inside Out Networks


 
Solutions Partners Support and Training Corporate Info Where to Buy Order Where to Buy Site Map Contact Us
Home > Support >kbase >
Testing and Troubleshooting a PortServer Port
Testing and Troubleshooting a PortServer Port Testing and Troubleshooting a PortServer Port

1) Troubleshooting a Port

Make sure that you have a cable built according to the specifications in the Digi Standard Cabling Guides: Portserver, Portserver II (TS), and Digi One Realport

  • Telnet or log in to the Portserver and type
      port ra=## dev=term
      line ra=## baud=9600 csize=8 parity=N stopb=1
    (where ## is the port number you wish to test).

  • Disconnect the Portserver from the network and power cycle it.
  • Set your terminal for 9600 8-N-1 and attempt to log in on the port. (If you can log in as root, then the port is working).

    2) Troubleshooting a Port remotely with RealPort

    Make sure that you have a cable built according to the specifications in the Digi Standard Cabling Guides: Portserver, Portserver II (TS), and Digi One Realport

  • Loop send and receive (a phillips head screwdriver between pins 2+3 of a DB25 or strip and twist the center two wires together on an RJ45 or RJ12 plug).
  • disable ttya01 ttyA01 [disable the ports for login in your OS ]
  • cat < /dev/ttya01 & [this example is for SCO Unix, the method]
  • date > /dev/ttya01 [or your version of Unix may differ]
  • cat /etc/termcap > /dev/ttya01
  • kill 0

    If the date appears on the screen, the port is working.
    The /etc/termcap file will test software flow control.

    3)Troubleshooting a Port remotely without RealPort

    Make sure that you have a cable built according to the specifications in the Digi Standard Cabling Guides: Portserver, Portserver II (TS), and Digi One Realport

  • disable ttya01 ttyA01 [if realport is installed]
  • telnet portserver
      port dev=prn ra=## [## is the port number you wish to test]
      flow ra=## [make sure that all hardware signals are off*]
      set line ra=## baud=9600 csize=8 parity=N stopb=1

    *altpin should be on if you are using 8 wire cable

  • telnet portserver 20##

    Note: 20## is 2000 + the two digit number of the port you want to test,
    for example: 2001 = port 1

    You will now be typing to the terminal or printer, or be able to give AT commands to your modem.

    A useful additional check is to press the right button on your PortServer or Portserver II until the number of the port in question is shown on the LEDs. While doing the tests outlined above, watch the signal lights to determine what is happening on the port. The same can be done with the Portserver TS or Digi One Realport line by using the DPA Remote Utility found here. 

    Related Information:

  • http://supportold.digi.com/support/techsupport/common/cables/async/pscableindex.html

  • http://ftp.digi.com/support/utilities/dpar/

  • solutions | partner programs | corporate info | support and training | where to buy
    site map | contact us | press releases |
    events | promotions | advertising

    Copyright © 1996-2001 Digi International. All rights reserved.

    products | applications | support | partners | news | about Digi | where to buy | contact us | site map

    Copyright © 1996-2002 Digi International. All rights reserved.



    Contact Us Site Map Product Selector Digi Homepage