PortServer I Configuration Guide and Reference Manual 90028700C
PortServer Default Settings Serial Parameters: (all ports) 9600 baud, No parity, 8 bits, 1 stop bit, VT100 terminal emulation Root Login: root Root Password: dbps Digi, Digi International, PortServer, RealPort, and the Digi logo are trademarks or registered trademarks of Digi International Inc. All other brand and product names are the trademarks of their respective holders. © Digi International 2000 All Rights Reserved Copyright © 2000 Digi International Inc. All Rights Reserved. http://www.digi.
Table of Contents PREFACE................................................................................................................................VI CONVENTIONS USED IN THIS MANUAL .......................................................................................... VI Keyboard Entry ......................................................................................................................vi Typefaces ....................................................................................
SNMP ......................................................................................................................................... 59 WHO .......................................................................................................................................... 60 REMOTE ACCESS COMMANDS ..................................................................................................... 61 CLOSE .....................................................................................
MODEMS.................................................................................................................................... 98 Notes on Configuring Modems .............................................................................................. 98 Configuring CU and UUCP to dial out without RealPort........................................................ 99 RTTY Program ...................................................................................................................
Preface Conventions Used in this Manual Certain conventions are used in this manual with respect to keyboard entry and typefaces: Keyboard Entry • Single keystrokes are enclosed in angle brackets (e.g. , , etc.) • Control keys (i.e. keys which are struck while holding down the key) are shown as single keystrokes. For example, “” means hold down the key while striking the key. Similarly, “” means hold down the key while striking the key.
Electronic Emission Notices Federal Communications Commission (FCC) Statements This equipment has been tested and found to comply with the limits for Class A digital devices pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.
Notes: Page viii PortServer Terminal Server
Introduction The Digi PortServer intelligent terminal server gives you the ability to connect up to 16 RS-232 asynchronous serial devices (such as terminals and printers) to an Ethernet network. Both Twisted Pair (10BaseT) and Thinnet (10base2) cabling standards are supported via the appropriate connectors on the side of the PortServer box. Description The PortServer hardware features a 20 MHz 80186 microprocessor and a 83902 16-bit network interface controller.
Besides terminals, PortServer serial ports can be configured as modem ports (incoming, outgoing or bi-directional) or printer ports. These options require knowledge of your host’s operating system to get it to “see” the devices connected to the ports. For supported operating systems, Digi’s RealPort port control protocol gives powerful control in accessing the remote PortServer ports. Help The PortServer software features extensive help functions.
PortServer Quick Start This “Quick Start” Getting Started section will help you quickly get your PortServer terminal server up and running. Wherever possible, the factory default settings are used. Later, once you have verified that the PortServer can communicate with your network, you can fine-tune the network and terminal parameters for optimum performance. Plug in the PortServer power supply, and connect the PortServer to the Ethernet Step 1. Turn off the power switch on the PortServer unit.
Connect a control terminal to the PortServer The PortServer is controlled from a terminal (or PC with terminal emulation software) connected to Port 1 on the PortServer’s back panel. (Any port can be used, but we will use the convention of Port 1 here.) In some installations, the PortServer can be controlled directly over the Ethernet; see Configuring the PortServer over the Ethernet on page 5. Step 1. Turn the PortServer’s power switch OFF.
Simple 3-Wire Cable RJ-11 - 4 Pin Signal Pin GND TxD RxD SG ( DB-25 Male Pin Signal 1 2 3 4 1 2 3 7 GND TxD RxD SG = Cable Shield) This same configuration can be constructed using 6 pin RJ-11 plugs, or either 8 or 10 pin RJ-45 plugs. See “RJ Connectors” on page 103 for the relationship of the various sizes of RJ connectors to the 10 pin RJ-45 jack.
Connect other terminals and peripherals to the PortServer At this point you may wish to connect other devices (terminals, modems or printers) to the PortServer. If you’d prefer to “play with it” a bit and add other peripherals later, skip this part and go to the next section, Log in and Configure the PortServer on page 9.
A more inclusive cable (necessary if you are going to set your port device as a host) is a full 10wire null-modem cable: Full 10-Wire Null Modem Cable Pin 10 Pin 1 RJ-45 - 10 Pin Signal Pin TxD RxD RTS CTS DSR SG DCD DTR RI GND ( 5 6 3 8 2 7 10 9 1 4 DB-25 Male Pin Signal 2 3 4 5 6 7 8 20 1 22 TxD RxD RTS CTS DSR SG DCD DTR RI GND = Cable Shield) PortServer Terminal Server Page 7
Modems The easiest way to connect modems is to use Digi’s RJ-45 to DB-25 straight-through cables, which offer full 10-pin connections for full modem control. (You may find ten-pin RJ-45 connectors difficult to find in the retail market). Here are the choices and part numbers: DB-25 Male DB-25 Female DB-9 Male 24 Inch Cables 61020024 61030024 61070024 48 Inch Cables 61020048 61030048 N/A If you wish to build your own modem cables, follow the diagram below.
Printers Serial printers can have different wiring requirements because of their manufacturer’s interpretations of the RS-232 “standard.” For those printers that can work with software handshaking (also called “XON/XOFF”), the three-wire hookup for terminals shown on page 5 will work well. Printers that require hardware handshaking (sometimes referred to as “DTR/DSR”) should work with the terminal hardware handshaking wiring scheme shown on page 6.
Step 4. When AC is showing on the PortServer display, press the Return or Enter key on your keyboard; you should get the login: prompt. Enter root. When asked for the root password, enter dbps: login: root passwd: #> (Note in this screen dump that the password is not echoed to the screen.) When you see the #> prompt, you are logged in. Step 5.
Domain Server’s Name If you have one, enter the IP address of the IP Name Service machine that will translate names to addresses. This example uses “192.83.159.2”: #>set config nameserv=192.83.159.2 #> Note that if you do not have an IP Name Service machine, you can use the PortServer’s Set Host commands to build a table of names and their IP addresses. (See page 47.) Network Subnet Mask Set your network subnet mask. (The PortServer’s default setting is 255.255.255.
Testing the network connection You should now be able to establish communications with another network machine. (You will need to know the IP Address of the other machine.) Enter the following ping command to test the connection: #>ping 192.83.159.227 #> (Again, the IP address “192.83.159.227" shown above is for example only. Use an IP address that is valid for your network.) The PortServer software should respond: 192.83.159.
Set up ports for your uses Your next step would be to configure individual PortServer ports for your own specific uses. This section sets up these example ports: • A wyse60 terminal on port 2, running at 38400 baud with software flow control • A printer with hardware flow control on port 3 • A bi-directional modem with hardware flow control on port 4 Security Levels Root Login is required for setting up ports, as it allows complete access to all PortServer options.
Terminal Setup Example (Wyse60 terminal on port 2, running at 38400 bps with software flow control) Step 1. Turn off the power to the terminal and the PortServer, and connect the Wyse terminal to Port 2. Power up again. Step 2. At the Port 1 control terminal, log in as root.
Flow Control While the default port flow control setting is for software flow control, let’s set it again just to make sure, by typing: #>set flow ixon=on range=2 #>set flow ixoff=off range=2 (In the above, set flow ixon=on sets port #2 to use software flow control (typically XON/XOFF) for output data. set flow ixoff=off sets port #2 to turn off software flow control for input data (keyboards shouldn’t need flow control).
Define Port as Printer Set Port #3 to be a Printer port by typing: #>set port dev=prn range=3 Note that you did not have to set the port to be a terminal in the previous example, because they all default to terminal as shipped. To change Port #3 back to a terminal someday, you would type “set port dev=term range=3.
Modem Setup Example (Bi-directional modem with hardware flow control on port 4) Step 1. Turn off the power to the modem and the PortServer, and connect the modem, wired as discussed on page 8, then power up again. Step 2. At the control terminal, log in as root. Step 3. The default baud rate setting of 9600 baud should be raised or lowered to the highest setting that the modem can handle.
Flow Control Change the flow control for Port #4 to RTS/CTS (“hardware”) by typing: #>set flow rts=on range=4 #>set flow cts=on range=4 (In the above, set flow rts=on sets port #4 to use hardware flow control for input data. set flow cts=on sets port #4 to use hardware flow control for output data.) Also note that the modem must be set (through AT commands or DIP switches) for hardware flow control.
Set up a new user A typical next step would be to set up a new user and password. For this example, we will: • Set up a new user for that Wyse 60 terminal on Port #2; the user’s login will be betty. • Give Betty the password MeBoss, and require that she give it whenever she logs in. (That is the default, but we will make sure it is in place.) Passwords are case-sensitive, and limited to eight characters in length. • Change the login prompt from the default login> to MegaCorp>.
Create New User “Betty” Create “regular” (as opposed to root) user “Betty” by typing: #>set users name=betty The user names are stored in a table of users, viewable by typing “set users” without any other parameters. As you will later find, this way of getting the current PortServer setup information works for all commands.
Change Betty’s Password to “MeBoss” Passwords are case-sensitive, and limited to eight characters or less. Changing the password can be done either by Betty herself, or by the root user. As root, set the password itself to “MeBoss.” Type: newpass name=betty The PortServer responds with current passwd: Type in “MeBoss”—note that it will not be echoed on the screen. (You will be asked again for the new password, to make sure it was typed correctly.
Have User “Rex” bypass PortServer Command Shell, connect directly to Host “Corporate” First, we create table entries for the host named “Corporate,” including its IP address (152.83.151.1 is a “phony” name used here for an example). Note that the “ip=” part is not necessary if you have IP name service. #>set host name=corporate ip=152.83.151.1 (You can inspect the Host table at any time by typing set host with no other parameters.
Telnet and Multisession Here is an example of Betty logging in on her newly-configured terminal, logging into her company’s Corporate and Engineering hosts via telnet, switching between the two sessions, then logging out. The PortServer supports up to nine separate login sessions per port.
Log in as “Betty” The PortServer is already up and running. Betty turns on her terminal, presses (if the login prompt is not already showing) and sees: MegaCorp> She types in Betty and presses ENTER. Next she sees: passwd: Betty enters “MEBoss”. The PortServer responds “login invalid...” because Betty got the case wrong. She logins in again, and properly enters her new password “MeBoss”.
Switch between sessions Betty’s session with Corporate is session #1, and her session with Engineering is session #2. From her Engineering session, she can switch to Corporate by typing 1 (the telnet escape character followed by the number 1). From her session on Corporate, she can switch to the Engineering session by typing 2, or switch back and forth between the two sessions by pressing ].
Telnet and modems In a previous part of this getting-started example, we installed a modem on Port #4, with DTR (“hardware”) handshaking and configured for bi-directional (incoming and outgoing calls) use. Here, Betty will telnet to that modem (from her Port #2 terminal to the modem on Port #4), use “AT” type modem commands to set a fixed DTE interface and 2400 baud, then call an information service.
Set Modem for Hardware Handshake on Serial Connection In the modem setup example (page 17), the connection from the PortServer to the modem was set to use RTS/CTS hardware handshaking. Here, Betty tells the modem to use the same, by typing: AT&K3 (Betty is connected directly to the modem, so there are no command prompts.) Set Modem Baud Rate In the modem setup example, the connection from the PortServer to the modem was set at 2400 baud. Now Betty sets the modem to 2400 baud.
Page 28 Quick Start
Command Reference This Command Reference is divided into these parts: Abbreviations ...........................................................................................................(page 29) PortServer Help Screens..........................................................................................(page 30) PortServer Editing Keystrokes................................................................................(page 31) PortServer Commands.................................................
PortServer Help Screens On-line help for the PortServer's command language is available to you through context-sensitive help screens. Help is available by entering a “?” either by itself or after part of a command line. The screen will tell you which parameters are available to complete the command line.
PortServer Editing Keystrokes The following keystrokes can be used in editing commands sent to the PortServer from a terminal: PortServer Terminal Server Page 31
PortServer Commands These commands are specific to the PortServer. admin Syntax: admin The admin command allows you root privileges with the PortServer if you have previously logged in as other than root. You will be asked for the root password. boot Syntax: boot action=reset|eewrite The boot command is used to reboot the PortServer, and requires root privileges.
cpconf Syntax: cpconf tohost|fromhost hostname filename cpconf term The cpconf (copy configuration) command was added to allow saving and restoring the configuration of the PortServer to a disk file. The format of the save file is a list of the set commands needed to set up the PortServer in the current configuration. These commands will be read and acted on by the server (just as if the user had typed them on the command line) when the configuration is restored.
If an attempt is made to change the IP address when restoring over the network, the restoration will fail because the PortServer will ignore any conversation on the old IP address. The save file prints a “#” at the beginning of the set config ip=x.x.x.x command, commenting it out to avoid the problem. For security, it is probably wise to remove world write permissions on the save file once the cpconf command has completed, to prevent unauthorized users from changing the file.
info tablename displays the following information (values shown are arbitrary examples). These are actual screen dumps of a root-level session—note the root prompt (#>): #> info network Network statistics collected over last 129 minute(s).
#> info tcp Network statistics collected over last 129 minute(s).
newpass Syntax: newpass [user=username] Use the newpass command to create or change your current password. If you are at the root level, be very careful not to forget your root password. If you supply the optional name=username, another user’s password can be changed. Root-level privileges are required to change another user’s password. ping Syntax: ping hostipaddress|hostname [options . . . ] The ping command is used to request ICMP echo responses from the specified host or network gateway.
quit Syntax: quit The quit command terminates your current login session. If you quit a session without first closing it, PortServer will automatically do a close for you. (See the telnet commands). Note that exit works the same as quit. Quit can also be used to give up root privileges temporarily acquired with the admin command.
set Syntax: set tablename [options . . . ] The set command is used to set or display various PortServer system and port parameters. The different tables that can be substituted for tablename are: altip host users arp route config terms The variables in these tables are referenced by their table indexes. flow logins keys ports line The variables in these tables are referenced by port numbers. Each of the tables will have their own options, as outlined in the following descriptions.
Multiple command options can be included in the same line with a single range option. For example: set line range=1-4 baud=2400 parity=E csize=7 stopb=1 will set the serial characteristics of ports 1 through 4 for 2400 baud, even parity, character size of 7 and 1 stop bit.
altip Syntax: set set set set altip [range=range] altip ip=ipaddr group=port# | group# altip rmip=ipaddress altip rmrange range=range The altip command allows you to telnet to a port or huntgroup using an IP address (or host name). You must assign an additional IP address to the port or hunt group.
arp Syntax: set arp [range=range] set arp ip=ipaddr ether=etaddr [tim2liv=time] set arp range=range rmarp=on This sets or displays the arp (Address Resolution Protocol) table entries. The arp table maps IP addresses to Ethernet addresses. In most cases, this is done automatically by the ARP protocol and manual modification of this table will not be required. Making changes with ARP requires root priveledges.
config Syntax: set config option=value This sets or displays the network parameters configuration table entries. Options are: domain netcx gateway submask myname ether ip boothost nameserv bootfile More than one configuration option can be included in a command. The set config command writes to EEPROM, and informs you of the number of locations found bad and corrected in EEPROM memory.
submask=subnet mask Used to set the network subnet mask. Default=255.255.255.0 boothost=ip_address_of_host_with_bootfile Used to set the IP address of the remote host with any upgraded PortServer software for booting via TFTP (Trivial File Transfer Protocol). This requires that the host supports TFTP— see the operating system documentation.
TFTP Error Messages The host with the bootfile may pass back a TFTP error message, which the PortServer will display in the alphanumeric display.
aixon=on|off Use auxiliary flow control characters (defined by set keys xona= and set keys xofa=) for output flow control. Default=off altpin=on|off Setting Altpin ON switches the function of the DSR and the DCD inputs on the interface connector, so that DCD is available when using an 8-pin RJ-45 connector instead of a 10-pin RJ-45 connector. (See RJ Connectors on page 103.) Default=off cts=on|off Use (or do not use) CTS (Clear To Send) for output flow control.
host Syntax: set set set set host [range=range] host name=hostname ip=ipaddress host rmhost=hostname host rmhost=on range=range This sets or displays the host name table, which maps host names to IP addresses. If name service is configured, this table is filled in automatically, and manual modification of this table will probably not be required. Making changes with this command requires root privileges.
keys Syntax: set keys option=value Use keys to define the local key combinations for various functions. The different keys that can be set are: eof tesc erase xon intr xoff kill xona range xoffa save Each of the preceding will have their own options, as outlined in the following descriptions. Use set keys range= to specify a single port or group of ports. More than one option can be included in a command.
xona=value Use to set the auxiliary XON Character you prefer. Default=^Q () xoffa=value Use to set the auxiliary XOFF Character you prefer. Default=^S () line Syntax: set line option=value Use line to view or modify serial line parameters. Use set line range= to specify a single port or group of ports. Options are: baud onlcr break otab csize parity error range inpck save istrip stopb Each of the preceding will have their own options, as outlined in the following descriptions.
onlcr=on|off Use to map (ON) or not to map (OFF) NEWLINE characters to CR-NEWLINE on output. Default=off otab=on|off Converts output tabs to eight spaces. Default= off parity=O|E|N Use to select Odd, Even or No parity. Default=N (no parity). range=startport#-endport# Specify a range of ports to be modified. save=on|off Save the changes to EEPROM. stopb=1|2 Use to set the Stop Bits to 1 or 2.
cmdprompt=character_string Use to define the PortServer command prompt. Default is digi>. (The root prompt of ># cannot be changed.) logprompt=character_string Use to define the login prompt (up to 11 characters). Default is login:. Root privileges required. login=on|off Use to set whether the user is required to log in before using terminal. Default=on. Root privileges required. Important! login must be ON for Auto users. write=on|off Use to set whether the user (other than root) can save to the EEPROM.
ports Syntax: set ports option=value Use set ports to set or display device configuration parameters. set ports range is used to specify multiple ports, or one specific port. Options are: auto group bin sess dest range dev save dport termtype edelay uid Each of the preceding will have their own options, as outlined in the following descriptions. (More than one option can be included in a command.
dport=remote_port# Use to specify the port number an auto connect port should connect to. (See set ports auto on page 52). • If set to 23, specifies telnet protocol services. • If set to 513, specifies Rlogin services. • If set to 0 (the default value), then checks the value of uid (below); if uid is set to 0, then specifies telnet services. If uid has a valid user index #, then specifies rlogin services. Check your operating system documentation for service numbers.
route Syntax: set route [range=range] set route net=network_address mask=ipmask gateway=ipaddress metric=numhops set route rmroute=on range=range set route displays, adds entries to, or removes entries from the routing table. Making changes with this command requires root privileges.
terms Syntax: set terms [range=range] set terms termtype=terminal_type [npages=# of screens] [clrseq=clear_escseq] [swtseq=screen# pageswitch_escseq] ... [save=on|off] set terms rmterm terminal_type set terms rmterm=on range=range This command sets or displays the terminal types, and their associated escape sequences used when switching between sessions. (See Multiple Sessions page 110, as well as your terminal's manual.) Making changes with this command requires root privileges.
Example: This example sets up the user's default terminal (since no range is specified) to a Wyse60, supporting three screens with a clear sequence of + (control-left bracket, plus key) and defines keys to switch between the three screens.
users Syntax: set users [range=range] set users name=username [passwd=on|off] [auto=on|off] [dest=IPaddress] [dport=tcp_port#] set users rmuser=username set users rmuser=on range=range set users newname=newusername name=oldusername This command sets or displays the user name table. Making changes with this command requires root privileges. More than one option can be included in a command.
• (Also see set port auto on page 52, which is similar except that a port is set up so that any user on that port will bypass the PortServer's command shell and automatically connect to the defined destination.) • Important! login must be set to on for Auto users—see set logins login= on page 51. set users newname=newusername name=oldusername This is used to change the user name oldusername already in the table to the new name newusername.
snmp Syntax: snmp [run=off | on] [auth_trap=off | on] [trap_dest=ipaddress] [location=PortServer’s location] The snmp command is used to configure and enable/disable snmp. The snmp community is “public.” Snmp sets are not supported. snmp run=on|off This starts or stops the SNMP daemon. Default is Off. snmp auth_trap=on|off This configures SNMP to send or ignore authentication traps when an authentication error occurs. Default is Off.
who Syntax: who The who command displays a list of the current users of the PortServer. Information includes each user's name and tty, the number of sessions each user is using, and where each user is connected from and connected to.
Remote Access Commands The commands in this section are remote access related. close Syntax: close Closes the current tcp session (the session last escaped from) to reenter the PortServer operating system’s command mode. mode Syntax: mode [option=offlow] The mode command is used to display telnet operating parameters.
rlogin The rlogin command logs a user into a remote system. syntax: rlogin hostipaddr|hostname [options] options: [user=username] [esc=escape_char] To avoid entering your password when logging into a remote system, you may put the PortServer's node name in the .rhosts file. You may also ask the remote system administrator to make passwords globally unnecessary by entering the PortServer's node name in the remote hosts /etc/hosts.equiv file.
send Syntax: send telnet_special_character This command transmits one of the following telnet special characters to the last active telnet session: abort output are you there? break erase character erase line ao ayt brk ec el escape ga ip nop synch esc character go ahead interrupt process no operation synchronize process For example, to send a break signal, type: send brk status Syntax: status The status command displays information on the current telnet session (if any), including the peer you ar
telnet Syntax: telnet hostname|hostip [port#] The telnet command is used to log you into a remote system using telnet protocol. Once you are connected via telnet, you can escape back to PortServer command mode by typing your telnet escape character, followed by a carriage return. You may also type your telnet escape character followed by a digit to switch to an alternate telnet session. (Also see Multiple Sessions on page 110.
Appendix Appendix Table of Contents RealPort Protocol ...................................................................................................................... 67 Troubleshooting ........................................................................................................................ 69 Master Troubleshooting Process ......................................................................................... 69 Troubleshooting Procedures ...........................................
Page 66 Appendix
RealPort Protocol RealPort is a protocol developed by Digi International that, when used in conjunction with device driver software on a host operating system, allows ports on the PortServer to be used as if they were connected directly to the host system.
Master Troubleshooting Process Introduction Use this Master Troubleshooting Process if one or more of your PortServer devices are not functioning. Note: This procedure assumes that you are not using the Digi RealPort driver to control your PortServer ports. RealPort is software that can be installed on one or more host servers to provide local serial port functionality. In many of the steps, you will be sent to another procedure that you need to complete.
2. Verify the network connection by using telnet to connect to the PortServer. From a computer on your network, enter this command at a prompt: telnet ipaddress where ipaddress is the IP address of the PortServer. Did you receive a PortServer login prompt? YES V Login to the PortServer as root and continue to the next step. 3. NO V You might have a network, cable or hub problem. You need to check this. Go to Procedure 3: Telnet: Receiving No Login Prompt on page 74. Check the PortServer port settings.
5. Telnet directly to the non-functional port. Go to Procedure 4: Performing a Telnet to the Port on page 75. When you entered the command on the keyboard, did the word, "Connected," appear on the screen? YES V Continue to the next step. NO V Recheck the set commands on the PortServer as described in Procedure 5: Checking the PortServer Port Settings and try the command again. If you still do not get any results, contact Digi Technical Support. 6. Test the port communication.
Troubleshooting Procedures Use these requested procedures as needed by the PortServer Master Troubleshooting Process. Procedure 1: Troubleshooting TFTP Use this procedure to verify that TFTP is working correctly on your UNIX host. This procedure is only valid on a UNIX system. 1. Access a root prompt on the UNIX host. 2. Make sure that you are not in the /tftpboot directory. 3. Enter this command: tftp ipaddress where ipaddress is the IP address of the UNIX host. A TFTP prompt should appear. 4.
7. Verify that the /tftpboot directory exists and has read, write and execute (777) permissions with this command: ls -l /tftpboot If necessary, use this command to create the directory: mkdir /tftpboot If necessary, use this command to change permissions of the directory to read, write and execute: chmod 777 /tftpboot 8.
11. Test TFTP by repeating steps 1-7. 12. If successful, reboot the PortServer. 13. Return to and continue with the Master Troubleshooting Process. Procedure 2: Resetting the PortServer Use this troubleshooting procedure when AC does not display on your PortServer and you need to reset the PortServer to the factory defaults. Important: You will lose all PortServer settings when you reset your PortServer to factory defaults. If you have a complex configuration, call Digi Technical Support for assistance. 1.
If the ping fails (you do not receive a response), continue with this procedure. If it succeeds (you received a response), this indicates there is another system using the same IP address. In this case, you need to assign another IP address to the PortServer. 3. From a terminal directly attached to the PortServer, check the configuration by entering the command: set config Verify the IP address, the mask settings, the gateway and that the RealPort setting is 771.
Procedure 5: Checking the PortServer Port Settings Use this procedure during the Master Troubleshooting Process when you performed a telnet to the PortServer and did receive a PortServer login prompt. 1. Log in as root. The default password is dbps. 2. Check to see that the required information appears in your port settings by using the following commands: Command set port range=range where range is two numbers separated by a hyphen.
set line range=range where range is two numbers separated by a hyphen. The first number is the beginning range and must be less than the second number. Often the number is 1. The second number is the end range and is between 8 and 64. 3. Verify that all parameters are configured correctly. Set line allows you to configure the baud rate, data bits, stop bits and parity. Go to Example: set line Command for an example of the result of choosing a set line range that equals 1-16.
Procedure 8: Checking LED Indicators: OFC On? Use this procedure when an OFC indicator light is on when monitoring a PortServer port. 1. From a terminal attached to the port, enter: control-Q 2. From the PortServer, enter: kill tty=portnumber where portnumber is the port number of the port to which the terminal is connected. 3.
Simple Network Management Protocol (SNMP) Also see SNMP on page 59. General Information The PortServer provides a Simple Network Management Protocol (SNMP) agent. This agent implements the current standard Management Information Base II (MIB-II) as defined in RFC1213. Configuring the SNMP Agent The SNMP agent is configured via the snmp command. Entering snmp with no options, as in: snmp prints out a list of the current SNMP configuration.
SNMP Protocol The SNMP agent in the PortServer supports the Get, GetNext, Set, and Trap messages that are defined in RFC1157. The following is a description of these messages. Get : Retrieves the value of a specific object from one of the supported MIBs. GetNext : Retrieves the value of the object following a specific object in the MIB list. This allows a management station to traverse or “walk” the MIB variables. Set : Modifies the value of a MIB object.
ICMP MIB icmpInMsgs icmpInErrors icmpInDestUnreachs icmpInTimeExcds icmpInParmProbs icmpInSrcQuenchs icmpInRedirects icmpInEchos icmpInEchoReps icmpInTimestamps icmpInTimestampReps icmpInAddrMasks icmpInAddrMaskReps icmpOutMsgs icmpOutErrors icmpOutDestUnreachs icmpOutTimeExcds icmpOutParmProbs icmpOutSrcQuenchs icmpOutRedirects icmpOutEchos icmpOutEchoReps icmpOutTimestamps icmpOutTimestampReps icmpOutAddrMasks icmpOutAddrMaskReps TCP MIB tcpRtoAlgorithm tcpRtoMin tcpRtoMax tcpMaxConn tcpActiveOpens tcpPas
PortServer Front Panel CCITT ™ 103 104 105 106 107 109 108 125 SEND TD RD RTS CTS DSR DCD DTR ETHERNET TD RD SERIAL LG POL CS TWISTED PAIR RI OFC IFC RX ERR EVF TX COL RECEIVE TRANSMIT The front panel of the PortServer terminal server has ten LEDs, two seven-segment alphanumeric displays, and two pushbuttons ( 8 and 9 ). The pushbuttons are used to: 10 11 Select diagnostic tests (see User Diagnostics on page 85).
ETHERNET (Ethernet Activity) When EA is shown by the alphanumeric display, the row of ten LEDs gives Ethernet information as follows: “Serial” TD: RD: “Twisted Pair”LG: POL: “Receive” CS: RX: ERR: OVF: “Transmit” Page 82 Appendix TX: COL: Data has been transmitted on any of the 8 or 16 serial lines. Data has been received on any of the 8 or 16 serial lines. Line Good. (Indicates a good connection to the twisted pair hub box.
PortServer BIOS The PortServer’ BIOS can be broken down into three parts: Power On Self Test (POST), Command Mode and user diagnostics. The POST sequence performs a series of basic tests to ensure that the microprocessor, memory, network interface controller, etc. are functioning properly. Command Mode is used to activate the Ethernet operating system and to switch to the user diagnostics. The user diagnostics are used for more extensive testing of the PortServer hardware.
Set temporary stack at 00400h. Data segment now available (00800h). Test 256K DRAM from 40000h to 7FFFFh. Test 256K DRAM from 80000h to BFFFFh. Test 256K DRAM from C0000h to FFFFFh. Set BIOS stack at 3FC00h. Transfer interrupt vectors from EPROM to DRAM. Disable all hardware interrupts. Enable interrupts. Check for 16 asynchronous (RS-232) ports. Check for NIC (Network Interface Controller). Board configuration is set. Real time clock is started (Timer 0). NIC and async ports are initialized.
User Diagnostics Video Display Diagnostics The two modes of the user diagnostics are video display mode and front panel mode. Either mode can be selected at any time before the POST diagnostic tests finish. • Front Panel Mode: Press either “arrow” pushbutton ( front panel display diagnostics begins on page 86. • Video Display Mode: Enter either a “V” or “v” from a terminal connected to Port 1. 18 or 19 ).
Front Panel Display Diagnostics Enter Front Panel Mode by pressing either the left or right pushbutton on the front panel during the POST startup tests. At this time, all of the lights (LEDs) go OFF, the left 7-segment display is blank, and the right 7segment display reads “1.” The right decimal point blinks at a 1 second rate. At this point, Test 1 - Panel Light Test is selected.
Test 2 - Memory Test Each pass of this test performs a pattern test and an address tag test to DRAM memory. The byte pattern is incremented for each pass and is displayed on the front panel LEDs 0-7 (TD-RI). The pattern is written to 32K bytes beginning at address 08000h. The pattern is written again to 32K bytes beginning at address 30000h. The two 32K blocks are compared to determine pass or fail status. The address tag test writes 32K bytes beginning at address 08000H.
Test 5 - Built-In UART External Loopback Test Same as Test 4, but uses external loopback. From the front panel, press the right pushbutton ( ) to select the port to test. The display will cycle from “01” to “16” or highest UART plus “All”. With the port selected, press the left pushbutton ( ) to start the test. In Test 5 (Async External Test), each port loops back on itself instead of looping back between ports.
PortServer Security The PortServer has four basic security access levels: Root login This allows complete access to everything. The root user can write and save any of the configurable parameters for any port. This login is always present, and must always have a password. It is not possible to remove the root user entry, or delete the root user password. Regular user login Except for parameter changes to his or her own PortServer port, a regular user cannot configure any of the PortServer parameters.
Auto-Connect User login The PortServer supports two types of automatic logins. Auto Connect User (described here) connects a specified user to a specified host no matter what port or terminal that user logs in from. Auto Connect Port (described on page 91) connects a specified port to a specified host no matter what user logs in through it. Auto Connect User effectively makes a user name a synonym for a particular connection request.
telnet example: set users name=martha passwd=on dport=23 dest=192.1.2.3 auto=on Auto connect user w/o password This is the same as “Auto Connect User with Password,” but set up with “passwd=off” added to the command line. Auto-Connect Port Auto Connect Port connects a specified port to a specified host no matter what user logs in through it. This dedicates a port to be a connection with a specific system only.
Resetting the PortServer to Factory Defaults Resetting the PortServer memory to the factory defaults will cause you to lose all user settings. Turn off the PortServer’s power switch. Press and hold both “arrow” pushbuttons ( 21 and ) at the same time, and turn on the power switch. Hold the pushbuttons in until the display reads “EP” (stands for EEPROM Program). This will reset the PortServer to boot from the factory ROM. The default Root login will revert to dbps.
Devices and Wiring Considerations Configuring PortServer Ports as Specific Devices The Serial Device Type Characteristics Table on page 96 summarizes the device type characteristics described in the following text. You may also wish to refer to set ports dev= on page 52 of the Command Reference section. (Computer or other devices) dev=host This is used for connecting another computer via a serial connection; a typical use might be connecting a BBS to the Ethernet through the PortServer.
(Terminals) dev=term This is designed for a terminal device. When the device is set to a terminal device, the incoming port ignores DCD. All outgoing connect attempts are refused. Wiring required: Only TD, RD, and GND connections are needed, making it easy to wire up to a terminal. (Printers) dev=prn The PortServer treats printers as outgoing devices that ignore DCD. Any incoming characters are also ignored, until an outgoing connection is made.
(Modem Out) dev=mout This is designed for a modem for outgoing communications with full DTR/DCD modem support. Until an outgoing connection is made, DTR remains low, keeping a modem from answering the telephone. When an outgoing connection succeeds, DTR is raised. The state of DCD is ignored, except that a high-to-low transition of DCD closes the connection, and drops DTR. DTR then remains low for 2 seconds to assure a clean modem disconnect, and then input is flushed to discard DISCONNECT messages, etc.
Serial Device Type Characteristics Table This table summarizes the device type characteristics.
Printers Configuring a Printer First, you need to define the port that the printer is connected to as a printer device, with the command set ports dev=prn range=printer port. (See page 52.) Also see Devices and Wiring Considerations on page 93. Connecting a Printer See the discussion on connecting peripheral devices on page 6 for a suggested printer wiring diagram, and the discussion under “dev=prn” on page 94.
Modems Notes on Configuring Modems Usually it is desirable to configure modems to be bidirectional (dev=mio) although if desired they may also be configured to be input only (dev=min) or output only (dev=mout). • Be sure to wire TD, RD, DCD, DTR and GND in the modem cable. • Make sure the modem is configured so DCD goes high when an incoming connection is received. (For Hayes-compatible modems, this command is AT &C1.
Configuring CU and UUCP to dial out without RealPort Use FTP to download the “rtty” program. The source code will always be available there, and binaries will be provided for the most popular operating systems. RTTY works by associating a particular pseudo tty port with a particular port or port “group” on the PortServer. The pseudo tty then acts enough like a regular port so that it fools most programs including kermit, uucp and cu. Not all pseudo ttys can be used for this.
Add a few lines like the following to your uucp “Devices” file. All baud rates are equivalent, since the pseudo tty device driver ignores them, but they must match up with the value given in your “Systems” file. On some systems, the “hayes” keyword is omitted; on other systems you will want to replace it with the name of the dialer script your modem uses.
RTTY Program The following is an extract from the RTTY source code mentioned on page 99, explaining the command usage. RTTY is provided on a limited-support basis for our customers, when used with the PortServer and other Digi network products. /********************************************************** * NAME * rtty - Connect a tty to a remote TCP port. * * SYNOPSIS * rtty [-dhw] tty host port * * DESCRIPTION * rtty attaches the master side of a named pseudo tty * to a TCP session.
static char *copyright[] = { "@(#)Copyright 1992, Digi International, All Rights Reserved.", "@(#)An unlimited use and distribution license is granted for use with,", "@(#)and only with, Digi terminal servers and other network products.
RJ Connectors There are four types of modular plugs that can be used with the PortServer's RJ-45 10-pin jack. These are the 4 or 6-pin RJ-11 plugs, and the 8 or 10-pin RJ-45 plugs. The 8 and 10-pin RJ-45 plugs are the same physical size, but the 10-pin version has one additional wire at each end of the row of contacts. Thus pins 1-8 of an 8-pin RJ-45 directly correspond to pins 2-9 of a 10-pin RJ-45 connector.
10 Pin RJ 45 Plugs The 10-pin RJ-45 plug carries all eight of the RS-232 signals supported by the PortServer hardware, plus the two ground lines, Signal Ground (SG) and Chassis Ground (GND). The 10-pin configuration includes the modem control lines Ring Indicator (RI) and Data Carrier Detect (DCD). RJ-45 WIRING: 10 PIN PLUG TO 10 PIN JACK RJ-45 - 10 Pin Plug 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. Page 104 Appendix RI DSR RTS GND TxD RxD SG CTS DTR DCD RJ-45 - 10 Pin Jack Pin 1 Pin 1 Pin 10 Pin 10 1. 2.
8 Pin RJ 45 Plugs The 8-pin RJ-45 plug supports all of the RS-232 signals except the modem control lines RI and DCD. It is ideal for use with terminals and printers that require full hardware handshaking (as when both DSR and CTS must be satisfied for data transmission to occur). The PortServer software permits software rewiring the RJ-45 connectors so that DCD is available in 8-pin configurations. See Modems on page 98.
6 Pin RJ 11 Plugs 6-pin RJ-11 plugs can be used in hardware handshaking situations that require only RTS and CTS to be available. RJ-11 WIRING: 6 PIN PLUG TO 10 PIN JACK RJ-11 - 6 Pin Plug RJ-45 - 10 Pin Jack Pin 1 Pin 1 Pin 6 1. 2. 3. 4. 5. 6. RTS GND TxD RxD SG CTS Pin 10 N/C N/C N/C N/C Page 106 Appendix 1. 2. 3. 4. 5. 6. 7. 8. 9. 10.
4 Pin RJ 11 Plugs The 4-pin RJ-11 plug can be used in situations requiring no handshaking, or software handshaking (XON/XOFF). No hardware handshake lines are available with this configuration. This is useful for the popular three-wire connection (TxD, RxD and Signal Ground) used for terminals and printers that support XON/XOFF handshaking. RJ-11 WIRING: 4 PIN PLUG TO 10 PIN JACK RJ-11 - 4 Pin Plug RJ-45 - 10 Pin Jack Pin 1 Pin 1 Pin 4 Pin 10 1. 2. 3. 4. GND TxD RxD SG N/C N/C N/C N/C N/C N/C 1. 2.
Digi RJ-45 to DB-25 Cable Legs Since most RS-232 devices are equipped with DB-25 connectors, it is necessary to buy or build an adapter to transfer the signals to a DB-25 plug. The most simple and direct approach is to purchase ready-made Cable Legs from a Digi International dealer or distributor. These are made with a full 10-pin RJ-45 plug (which can be difficult to obtain in the retail market), connected via a two or four foot cable to a DTE-configured DB-25 plug.
Connecting Modems Modems are generally equipped with DB-25 connectors, so it is usually necessary to buy or build an adapter such as the ones mentioned previously. Since the modem control lines, RI (Ring Indicator) and DCD (Data Carrier Detect) are on pins 1 and 10, respectively, of Digi’s RJ-45 jack, the adapter cable provided by Digi is ideal, since it has a 10-pin RJ-45 plug, and is terminated in a modem-ready, DTE-configured DB-25 plug.
Multiple Sessions Any user can use the multiple session feature if that user's port is configured to allow it. Users logged into a host with one of the auto options (auto port or auto user) cannot run multiple sessions, as this would defeat the security purpose of the Auto connections. Multiple sessions are initiated one at a time from the command line.
Switching to another session At the PortServer command line, type the session number as the first character of a line to switch to the associated session. This is a special case, and does not require that you hit return after typing the number. Closing a session To close either a telnet or rlogin session, either log out of the remote system (which closes the session from the other end) or escape to the command line and type the close command.
Configuring Multiscreens The PortServer supports up to 16 different terminal types. Each terminal type must have a different name, although a particular manufacturer's terminal may be known by several different names. For example you might want to have separate names for a wyse 60 in 43 line mode (no screen switching), a wyse 60 in 24 line standard mode (2 screens available), a wyse 60 in 24 line ECON-80 mode (3 screens available) and even a wyse 60 in WYSE 50+ mode (6 screens available).
PortServer Port Numbers The PortServer provides two ranges of TCP/IP service numbers that you can connect to from other systems: 2001 - 2099 2101 - 2199 Telnet Connect Raw Connect A connect made to any 20XX port uses the Telnet protocol, providing full Telnet compatibility. You would use the 20XX ports in commands like: pr myfile | telnet dbps-nodename 2001 A connect to any 21XX service is a raw connection, passing 8-bit clean data at all times.
Specifications Network Compatibility Ethernet IEEE 802.3 standard 10BaseT (Twisted Pair) 10base2 (Thin Ethernet) Ports 8 or 16 RS-232 asynchronous serial ports with RJ-45 connectors 1 10baseT twisted-pair Ethernet port with an RJ-45 8-pin connector 1 10base2 Ethernet port with a BNC coaxial connector Power Requirements +5 volts ± 5% +12 volts ± 5% -12 volts ± 5% 1250 ma typical 250 ma typical 50 ma typical Environmental Ambient temperature Relative humidity Altitude 16.6° C (60° F) to 29.
Index —A— Abbreviations, 29 abort output char (ao), 63 admin, 32 aixon, 46 altip, 41 Altip, 113 Altpin, 46 wiring for modem, 109 Are you there? char (ayt), 63 arp, 42 Auto set port for auto login, 52 Auto connect port, 91 user, 90 Auto-connect port security, 91 Auto-connect user security, 90 —B— baud setting, 49 bin binary connection, 52 boot, 32 bootfile, 44 boothost, 44 filename, 44 break command, 49 Break char (brk), 63 —C— close, 34, 38 Close, 61 cmdprompt changing, 51 config, 43 cpconf, 33, 34 csiz
appendix, 93 Front Panel, 81 —M— —G— gateway, 43 Go ahead char (ga), 63 Group defining, 53 —H— Help screens, 30 high-order bit stripping, 49 Host host parameters, 47 set, 47 setting port as, 52 —I— IFC, 81 info, 34 info clear, 34 Interrupt process char (ip), 63 intr, 48 ipaddress, 43 ixoff, 46 ixon, 46 —N— nameserv, 43 netcx option, 43 newname set users, 58 newpass, 37 No Operation char (nop), 63 node name, 43 nodename, 64 —O— OFC, 81 onclr, 50 —K— Keys setting keys, 48 kill, 48 kill tty, 36 —L— Lin
—Q— Quick Start, 3 —R— Range, 39 RARP, 5 Remote Boot, 44 ri, 46 RJ Connectors, 103 RJ-11 4 pin, 107 RJ-11 6 pin, 106 RJ-45 10 pin, 104 RJ-45 8 pin, 105 Route routing information, 54 rts, 46 —S— Security, 89 Send send telnet character, 63 Sessions setting maximum, 53 switching between, 23 set altip, 41 config, 43 host, 47 set config bootfile, 44 boothost, 44 domain, 43 gateway, 43 ip, 43 myname, 43 nameserv, 43 submask, 44 set flow aixon, 46 altpin, 46 cts, 46 dcd, 46 ixoff, 46 ixon, 46 ri, 46 rts, 46 set
characters, 63 command, 26, 64 telnet escape character, 23, 48 Term terminal escape sequences, 55 Terminal device, 94 setting port as, 52 Termtype setting, 53 tesc, 23, 48 TFTP error messages, 45 tim2liv, 42 Trivial File Transfer Protocol error messages, 45 —U— User index, 53 Users table, 57 uucp, 99 —V— verbose, 51 —W— Who list current users, 60 write option, 51 —X— xoff set, 48 xoffa, 49 xon set, 48 xona, 49 Page 118 Index
