Page 1 8VHU·V*XLGH PortServer II ® ,QWHOOLJHQW1HWZRUN&RPPXQLFDWLRQV DQG7HUPLQDO6HUYHU...
Page 3 © Digi International Incorporated 1995-1996. All Rights Reserved. Digi International™, PortServer II™, DigiWARE™, RealPort™, PORTS/16em™, PORTS/8em™, PORTS/8emp™ and the Digi logo are trademarks of Digi International Inc. All other registered and unregistered trademarks are the property of their respective holders.
Page 4 90030500B Page ii...
Page 5: Table Of Contents
Description of PortServer II Hardware........
Page 6 Installing and Connecting PortServer II ........
Page 7 Connecting PortServer II to serial devices ....... . . 35...
Page 8 PortServer II TCP/IP Port Numbers ........
Page 9 General ............96 Multiple Sessions .
Page 10 A filter that will bring up a connection when it detects any IP packet except DNS ..123 Tracing messages ............123 Chapter 9 Configuring Modem Connections.
Page 11 Configuring the SNMP Agent ......... 155 Monitoring SNMP status on PortServer II ....... . 156 Supported SMNP Variables .
Page 12 TFTP Error Messages on PortServer II ........
Page 13 Frame Relay Statistics ............204 Hardware Error Counts .
Page 14 Web Server: Access to Digi Information ....... . . 240...
Page 15 Federal Communications Commission (FCC) Statements Radio Frequency Interference (RFI) (FCC 15.105) The PortServer II has been tested and found to comply with the limits for Class A dig- ital devices pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential environment.
Page 16 Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada. Certification The Digi International PortServer II Intelligent Network Communications and Termi- nal Server meets the following standards: • FCC Part 15, Class A •...
Page 17: About This User's Guide
About this User’s Guide This PortServer II User’s Guide is designed to be read by an installer or network administrator who needs to install PortServer II, configure it for normal operation, and connect it to a network. You should use it with the PortServer II Command Reference Guide, which contains information on the operational and configuration commands.
Page 18: Which Chapters Should I Read
The Glossary contains a list of technical terms, and their explanations. Which chapters should I read? If you are not familiar with PortServer II, you should begin by reading Chapters 1 and 2 which provide a general description of PortServer II and its operation.
Page 19: Document Conventions
Courier text indicates a key or sequence of keys on the terminal that you should press. Other PortServer II Documentation For further information on PortServer II, refer to the following documents: • PortServer II Intelligent Network Communications and Terminal Server Com- mand Reference Guide 92000246 •...
Page 20 Page xviii About this User’s Guide 90030500B...
Page 21: Chapter 1 Introduction
Chapter 1 Introduction When should I read this Chapter? Read this chapter if you are unfamiliar with PortServer II, and want an overview of its functions and possible applications. In this Chapter This chapter introduces you to the PortServer II and describes its features. It includes...
Page 22: Features And Functions
ISDN terminal adapters, and modems. You can also attach parallel devices such as printers, if you use an expansion module with a parallel port. Because PortServer II is independent of the hardware connected to it, users can access any type of networked server running the TCP/IP protocol suite.
Page 23 The following peripherals are shown connected to the PortServer II: • Terminals. Any terminal that includes a standard RS-232 serial interface can be connected to a serial port. PortServer II communicates with the host computer through the Ethernet port using TCP/IP. Where multi-user systems are already installed, multiple host sessions are available, up to a limit of nine sessions per port.
Page 24 PortServer II’s capabilities. See Chapter 11, Configuring RealPort Connections for more information. • Local PCs. Any PC can be connected to a PortServer II serial port. The user has full access to all applications on the server. Typically, you run a terminal emulator or SLIP/PPP software package on the PC.
Page 25: Basic Operation
Basic Operation Configuration of serial ports Each PortServer II serial port can be configured for a specific type of device and/or service, for example, an asynchronous modem with PPP service. Once a port has been configured, it cannot be used with another type of device or service unless you recon- figure it.
Page 26: Modems And Dial-Up Links
(for example, a par- ticular time or day). A remote user or system may dial into PortServer II using a terminal emulator such as ProComm Plus. When traffic has finished, the connection may be hung up to reduce telephone costs.
Page 27: Slip And Cslip
“firewall”. Other filters block selected packets, for example, to block out broadcast messages. Filters are typically used to control access to specific hosts, net- works or services, and thus increase security on your system. If PortServer II detects packets that are blocked by a filter, it drops the packets.
Page 28: Snmp
The server can change port parameters such as baud rate and flow control. It is also possible for more than one server to control ports on the PortServer II; for example, one server may use the odd numbered ports, while another server may use the even numbered ports.
Page 29: Ethernet Connection And Dynamic Ip Addressing
PortServer II attempts to acquire its IP address automati- cally. Each device that connects to a PortServer II can have its own IP address and, if it does, PortServer II will route TCP/IP packets to and from the device transparently. This fea- ture permits PortServer II to operate as a router between all IP addressable hosts that are connected to its serial ports or to the Ethernet.
Page 30: Expanding Portserver Ii With Additional Ports
Description of PortServer II Hardware The Digi PortServer II intelligent terminal server allows you to connect up to 64 RS- 232 asynchronous serial devices (such as terminals and printers) to an Ethernet network. Both Twisted Pair (10BaseT) and Thinnet (10Base2) cabling connectors are provided on the side of the PortServer II box.
Page 31: Typical Applications
Figure 2 PortServer II - Local Devices and RealPort In this configuration, several “dumb” terminals are connected to the Ethernet by a PortServer II. This example shows that it is possible to connect different devices to the same PortServer II, including modems and printers. Features to note include: •...
Page 32: Terminal Server Configuration - Remote Devices And Realport
In this configuration, several “dumb” terminals are connected to a corporate applica- tion server by means of a PortServer II and the PSTN (Public Service Telephone Net- work) or Frame Relay. This example shows that it is also possible to connect a variety of different devices to the PortServer II in a “dial-up”...
Page 33: Terminal Server Configuration - Multiple Remote Devices At Several Locations
• The corporate application server is connected to the main corporate LAN. • The corporate LAN is connected to the PSTN by a PortServer II (see Chapter 9). • The corporate application server may be running RealPort software (see Chapter 11).
Page 34: Tip - Leased Lines
• Each remote location is connected to the PSTN by a PortServer II (see Chapter 9). • Each remote PortServer II can be configured to call the corporate server, or the corporate server can call each remote location. Alternatively, the configuration could allow either location to initiate a connection.
Page 35: Communications Server Configuration - Remote Dial-In Users At Several Locations
CSLIP. For example, they may use Windows 95’s HyperTerminal program to make PPP connections (see Chapter 9). • PortServer II can make a primary authentication of users, or the server may be a RADIUS server for ease of configuration (see Chapter 15, Configuring RADIUS).
Page 36: Communications Server Configuration - Dial-Out Access To The Internet
In this configuration, several satellite or remote users are provided with access to an ISP (Internet Service Provider) by a PortServer II and the PSTN (Public Service Tele- phone Network) or Frame Relay (see Chapter 14). This permits the user full access to all Internet options, including e-mail and World Wide Web (WWW) if they have the appropriate software installed on their terminals.
Page 37: Specifications
Specifications Network compatibility • Ethernet IEEE 802.3 standard • One 10BaseT twisted-pair Ethernet port with an RJ-45 8-pin connector • One 10Base2 Ethernet port with a BNC coaxial connector Ports • 16 EIA RS-232 synchronous/asynchronous serial ports, each with an RJ-45 con- nector •...
Page 38: Limits
Limits PortServer II includes the following limits: Users Maximum 64 internal users, regardless of whether expansion modules are connected. Use of an external RADIUS server allows additional users, up to the limit of the RADIUS server. WANs Maximum 128. 64 outgoing connections, waiting for traffic, and 64 established via RADIUS.
Page 39: Chapter 2 Operation
Chapter 2 Operation When should I read this Chapter? Read this chapter if you are unfamiliar with PortServer II, and want to learn about its controls, indicators, and connectors. In this Chapter This chapter describes the controls, indicators, and connectors on PortServer II, and describes how to interpret the displayed information.
Page 40: Portserver Ii Front Panel
The more LEDs that are lit, the greater the CPU activ- ity. If the alphanumeric display shows AC, PortServer II has powering up and is now in normal operating mode. Other indications on the display identify possible fault conditions. Refer to Chapter 17, Troubleshooting for information on fault codes.
Page 41: Pushbuttons
LED indicators. • Select diagnostic tests, as described in Chapter 17, Troubleshooting. • Reset PortServer II to factory default settings, as described in Chapter 17, Troubleshooting. 90030500B...
Page 42: Interpreting The Led Indicators
Interpreting the LED Indicators The LED indicators are used to display two different types of status information. If the alphanumeric display shows a port number, the LED indicators display serial port sta- tus information and the labels above the LEDs apply. If the alphanumeric display shows EA, the LED indicators display Ethernet activity and the labels below the LEDs apply.
Page 43: Ethernet Activity
PortServer II will still operate correctly. Receive Carrier Sense. Blinks when PortServer senses Ethernet carrier signal. Receive Blinks when PortServer II detects a packet destined for itself. 90030500B Operation Page 23...
Page 44 Lights when packets arrive faster than PortServer II can process them. Transmit Lights when PortServer II is transmitting a packet. Transmit Lights when PortServer II detects a collision on the net- work. This may be a collision between any packets, not nec-...
Page 45: Portserver Ii Side And Rear Panels
The connectors for the Ethernet cable, the power on/off switch, and the D.C. power supply are located on the left-hand side panel of PortServer II (viewed from the front), while the serial port connectors are on the rear panel. The locations of connectors are...
Page 46: Thinnet Connector, Twisted Pair Connector
Rear panel The rear panel provides 16 identical RS-232 compatible serial connectors. Port 1 is at the left, viewed from the rear. Port 8 Port 9 Port 1 Port 16 Figure 9 PortServer II Rear Panel Page 26 Operation 90030500B...
Page 47: Chapter 3 Installation
Read this chapter before you install and connect a PortServer II. In this Chapter This chapter describes how to install PortServer II, including site planning procedures and information on basic safety. It also includes descriptions of the cables that you will require.
Page 48: Before You Begin
• Have available a terminal (or PC with terminal emulation software) to configure PortServer II. Surveying the Installation Site 1. Identify the best location to place PortServer II. You may want to review the Site Environment requirements and the information given on Interference Limitation below.
Page 49 The electromagnetic pulse carried by lightning and similar high-energy phenomena can induce enough energy in cables to destroy PortServer II’s circuitry. If your installation site is subject to lightning strikes, you may want to consider lightning suppression and shielding.
Page 50: Recommended Maximum Distance Limitations
Recommended maximum distance limitations The maximum recommended length of each type of cable connection you may use with PortServer II are shown below. Note: Although PortServer II may operate adequately if you exceed a given limita- tion, performance may be degraded. Ethernet 10BaseT: Maximum distance of 330 ft (100 M) at a transmission rate of 10 megabits/second (10 Mbps).
Page 51: Inspecting Portserver Ii
Inspecting PortServer II Do not unpack PortServer II until you are ready to install it. When you unpack the shipping box, check that you have the following items: • One PortServer II unit • Power supply unit with integral cords •...
Page 52: Site Preparation
Interference from electrical equipment may cause intermittent failures. • Do not install PortServer II in an area where condensation, water, or other liquids may be present. This may cause a safety hazard and cause failure of the equip- ment.
Page 53: Safe Installation Practices
• PortServer II’s power supply is provided with a 3-wire plug, which includes a ground connection as a safety feature. If you are unable to insert the plug into your outlet, have an electrician replace the obsolete outlet.
Page 54: Installing And Connecting Portserver Ii
PC, modem, printer, or Ethernet). Detailed procedures are given in Connecting PortServer II to serial devices following. 4. Connect the power unit to PortServer II and to the power source. Do not switch on until instructed. Connecting PortServer II to the Ethernet LAN Connect your Ethernet network cable to the appropriate connector on the left-hand side of PortServer II.
Page 55: Connecting Portserver Ii To Serial Devices
Connecting PortServer II to serial devices General Each of PortServer II’s serial ports is provided with an RJ-45 10-pin jack socket. You can connect a serial device to the port using a cable terminated with any of the follow- ing plugs: •...
Page 56: Ten Pin Rj-45
Ten pin RJ-45 The ten pin RJ-45 plug carries all eight of the RS-232 signals supported by PortServer II, together with two ground lines, SG (Signal Ground) and GND (Chassis Ground). It includes two modem control lines, RI (Ring Indicator) and DCD (Data Carrier Detected).
Page 57: Eight Pin Rj-45
Eight pin RJ-45 The eight pin RJ-45 plug carries the RS-232 signals supported by PortServer II, except for the two modem control lines, RI (Ring Indicator) and DCD (Data Carrier Detected). It also provides the two ground lines, SG (Signal Ground) and GND (Chas- sis Ground).
Page 58: Six Pin Rj-11
Six pin RJ-11 The six pin RJ-11 plug is suitable for connections that require limited control signals, for example modems or printers that employ hardware handshaking. Pin 1 Pin 1 Pin 6 Pin 10 RJ-45 - 6 Pin Plug RJ-45 - 10 Pin Jack Signal Signal Figure 11 RJ-11 6 Pin Plug and Jack Wiring...
Page 59: Four Pin Rj-11
Four pin RJ-11 The four pin RJ-11 plug is suitable for connections that require only data signals, for example modems or printers that employ software handshaking. No hardware hand- shaking is available with this configuration. Pin 1 Pin 1 Pin 4 Pin 10 RJ-45 - 4 Pin Plug RJ-45 - 10 Pin Jack...
Page 60: Connecting The Configuration Terminal
Connecting the configuration terminal Connect a PC or terminal to Port 1 on the rear of PortServer II to use during the con- figuration procedure described in Chapter 4, Basic Configuration. You can subse- quently use this terminal for system management or other purposes. If you use a PC, you will require a terminal emulator program.
Page 61: Connecting To Terminals And Pcs
You can connect a terminal to any available serial port on PortServer II. 1. Obtain a suitable cable to connect the terminal to the serial port on PortServer II. The wires that must be available depend on whether the terminal requires hard- ware handshaking.
Page 62 2. Fit the DB-25 connector to the terminal. If your terminal does not have a DB-25 connector, you will also have to obtain an adapter. 3. Fit the RJ-11 or RJ-45 plug to PortServer II. If you use an RJ-11 plug, ensure that you center it on the jack.
Page 63: Connecting To Modems
You can connect a modem to any available serial port on PortServer II. 1. Obtain a suitable cable to connect the modem to the serial port on PortServer II. Most modems require a 10-pin cable; we suggest you obtain one of Digi Interna- tional’s RJ-45 to DB-25 straight-through cables:...
Page 64: Altpin
2. Fit the DB-25 connector to the modem. If your modem does not have a DB-25 connector, you will also have to obtain an adapter. 3. Fit the RJ-11 or RJ-45 plug to PortServer II. If you use an RJ-11 plug, ensure that you center it on the jack.
Page 65: Connecting To Printers
You can connect a printer to any available serial port on PortServer II. 1. Obtain a suitable cable to connect the printer to the serial port on PortServer II. The wires that must be available depend on whether the printer requires software (XON/XOFF) or hardware (DTR/DSR) handshaking.
Page 66 RJ-45 (8 pin) DB-25 Male 20 DTR =Cable Shield Figure 19 Printer cable with Hardware handshaking Note: Any cable you construct or obtain must be shielded to comply with FCC certi- fication requirements. The shield must be connected to Chassis Ground (GND) at one end of the cable.
Page 67: Connecting To Frame Relay
Connecting to Frame Relay If you plan to use PortServer II with a Frame Relay service, you must use a V24 cable similar to the one shown in Figure 20. One cable of this type is supplied with each PortServer II. An RJ-45 10-pin male connector is provided at the PortServer II end of the cable, and a DB-25 25-pin male connector is provided for the Frame Relay termi- nation.
Page 68: Wiring Ports For Specific Devices
PortServer II. DCD and DTR must be cross-connected between the PortServer II and the BBS server. When the server raises DTR to signal that it can receive calls, the PortServer II sees DCD go high. It then allows incoming connections from the Ethernet through the serial connection to the server.
Page 69: Dev=Hdial
Unlike dev=min, there is no two-second delay before the login is spawned. When PortServer II raises DTR, it brings DCD up at the host immediately. When the user logs out or the host drops DTR, PortServer II lowers its DTR and flushes data for two seconds.
Page 70: Dev=Prn (Printers)
Use this device type for a modem that is used for incoming communications only. DTR and DCD are supported. In this mode, PortServer II ignores all input until DCD appears. Then it “flushes” all input for two seconds to discard messages like RING and CONNECT, before it spawns a login or attempts a connection.
Page 71: Dev=Mio (Modem In & Out)
(Modem In & Out) Use this device type for a bi-directional modem, requiring full DTR/DCD support. When the modem is idle, PortServer II leaves DTR high so the modem will answer incoming calls. If DCD goes high when the device is idle, PortServer II assumes an incoming connec- tion has been requested and acts like a dev=min device until the device goes idle again.
Page 72: Connecting To The External Bus Interface
Connecting to the External Bus Interface PortServer II includes an External Bus Interface that permits connections to up to three external modules providing additional serial ports. Compatible external modules from the Digi International range of PORTS modules include: • PORTS/16em. Provides sixteen additional serial ports.
Page 73 Warning! Do not connect a PORTS module to PortServer II while power is switched on. This may cause severe electrical problems or dam- age to PortServer II and the PORTS module. Note: You may experience performance degradation when using expansion modules under heavy data throughput.
Page 74 Page 54 Installation 90030500B...
Page 75: Chapter 4 Basic Configuration
Basic Configuration When should I read this Chapter? Read this Chapter if you are going to configure a new PortServer II for the first time. If you want to change or add to the configuration of a previously configured PortServer II, refer to subsequent chapters.
Page 76: Entering Configuration Commands
If you enter insufficient letters for PortServer II to identify the command, it will return an error message. You may enter an asterisk (“*”) in place of “range=1-n” to specify all of the ports or tables entries of the same type.
Page 77: Editing Keystrokes
Escape character. Used to break out of the current session, either Ctrl [ Enter to another session or to the PortServer II command line. (You can change “[” to another character with the set keys command, as described in the Command Reference Guide.) Ctrl+c Interrupt character.
Page 78: Specifying The Range Of Set Configuration Commands
Specifying the range of set configuration commands As a part of a set command, you specify which port or table entry to which the com- mand applies. The set flow, set framerelay, set FrDcli, set keys, set line, set logins, and set ports commands are applied to a port or range of ports, while other set commands are applied to a table index.
Page 79: Saving Configuration Changes To Flash Rom
Saving configuration changes to flash ROM Each set command includes an option to save configuration changes into PortServer II's Flash Read Only Memory (ROM). If you logged in as root, save is on by default. If you are not logged in as root, save is off by default. Important: Changes made by a non-root user are valid only for the duration of their session.
Page 80: On-Line Help
“?” by itself or after part of a command line. The help screen will tell you which parameters are available to complete the command line. Help menu Enter a “?” after the PortServer II prompt with no other parameters to get the top level help screen, as shown below: login: root passwd: #>...
Page 81: Logging On To Portserver Ii
Chapter 17, Troubleshooting for details of how to restore the fac- tory-default settings for a port. 3. Switch on PortServer II. The power switch is located on the front of the case. Port- Server II’s Power On Self Test (POST) sequence will now run automatically. If it does not detect any errors, the alphanumeric display will show AC, and the LED indicators will light in sequence.
Page 82: Configuring The Ethernet Connection
#>set config myname=<node_name> For example, to set the node name to termserver, enter: #>set config myname=termserver 3. If applicable, enter the name of the domain that includes the PortServer II unit, using the following command: #>set config domain=<domain_name> For example, to set dgii.com as the domain name, enter: #>set config domain=dgii.com...
Page 83 Note: If you do not have a Domain Name Server, you can use the PortServer II’s set host command to build a table of names and IP addresses. (See the Command Reference Guide for the command syntax.) 5. Set your network sub-net mask, using the following command: #>set config submask=xxx.xxx.xxx.xxx...
Page 84: Configuring Portserver Ii Over The Ethernet
Configuring PortServer II over the Ethernet If you do not set the IP address during configuration, PortServer II will attempt to use RARP (Reverse Address Resolution Protocol) to determine its IP address. If this suc- ceeds, you can configure the remaining PortServer II parameters by connecting to it using telnet from an administration terminal, instead of using a local terminal con- nected directly to PortServer II.
Page 85: Testing The Network Connection
192.83.159.227 is alive #> If you do not see this message, check that you have set the IP address for PortServer II correctly, and have entered the address of the target machine correctly. Check also that you have connected the network cable to PortServer II correctly. You can also use PortServer II’s front panel to monitor Ethernet activity –...
Page 86: Portserver Ii Tcp/Ip Port Numbers
PortServer II TCP/IP Port Numbers PortServer II provides two ranges of TCP/IP service numbers to which you can con- nect from other systems: 2001 - 2099 Telnet Connect 2101 - 2199 Raw Connect A connection made to any 20XX port uses the Telnet protocol, providing full Telnet compatibility.
Page 87: Configuring A User
The configuration options available depend on their method of access, as described below. If you do not have users connecting to your PortServer II (for example, if you are using it as a printer server), you can ignore the rest of this chapter.
Page 88 This allows access any time except during the working week. AutoConnect If this is set to yes, the user may be automatically connected to another machine, without getting a local PortServer II command line prompt. AutoHost If AutoConnect is set to yes, this contains the IP address of the machine that the user is connected to.
Page 89 TCP stream with no modification. Command- If this is set to on, the user has access to the PortServer II com- mand line. If it is set to off, the user cannot issue PortServer II Line commands.
Page 90 As in step 2, you can include more than one parameter in each command. PortServer II displays the list of network parameters that you will configure for the user. If this is a new user, default settings are provided for the parameters, as...
Page 91 Keepup The name of a KeepUp filter that PortServer II will use to maintain the connection. See Chapter 9, Configuring Modem Connections for information on filters. LocalBusyDly...
Page 92 If this is set to 0.0.0.0, the IP address of PortServer II’s Ethernet interface is used. Loginscript The name of a script that PortServer II uses to log in to the remote system and start the network connection. See Chapter 9, Configuring Modem Connections for infor- mation on scripts.
Page 93 (Any password that the remote system returns must match the user’s password.) Passive If set to on, PortServer II waits for the remote system to begin PPP negotiations. If set to off, PortServer II may initiate negotiations.
Page 94: Using The Ip Pool
Using the IP Pool You can configure PortServer II to use a “pool” of IP addresses for devices connected to it. PortServer II then assigns an address from the pool each time a device requests a session. Creating a pool...
Page 95: Configuring A User For Manual Or Automatic Login And Connection To A Host
Configuring a user for manual or automatic login and connection to a host The procedures given below are typical methods of configuring a user’s connections to a host. The first procedure configures a user who must log in for each session with their own login and password.
Page 96 For example, to change the login prompt to Digi Int> on all 16 ports, enter: #>set logins logprompt="Digi Int>" range=1-16 The maximum login prompt length is 10 characters, and may include both letters and numbers.
Page 97: Configuring A New User For Automatic Login And Connection
If you specify an Rlogin session, Peter will automatically be logged in to corporate if his login on corporate is the same user name as his PortServer II login. You can also set AutoPort=Default to use the user’s default protocol or raw (no modification to data passing between the serial port and the TCP stream).
Page 98: Providing A Navigation Menu For Each User
For example, the following five commands specify a complete menu: set menu range=1 t1=“ Digi International Inc.” set menu range=1 t2=“Networking Products and Solutions” set menu range=1 m1=“Choose one of the following systems:”...
Page 99: Removing A User
3. Configure a user to the menu. For example: set user name=fred menu=1 DefaultAccess=menu Removing a user To remove a user’s login and associated information from PortServer II, enter the fol- lowing command: set user rmuser=<user_name> For example, to remove the user called Peter, enter:...
Page 100: Users Logging On To Portserver Ii
Users logging on to PortServer II When you have configured a user, he or she can log in to PortServer II (if permitted). Alternatively, PortServer II may route the login request to any autoconnect host that you have defined. To log in, the user enters a command in the format:...
Page 101: Using Configuration Commands
Command Reference Guide. altip Defines an alternate IP address for a PortServer II port or a group of ports, allowing (for example) it to be included in hunt groups. Sets ARP (Address Resolution Protocol) Table entries, which map IP addresses to Ethernet addresses.
Page 102 Sets terminal types and parameters for multiple sessions. time Sets or displays the time and date held by PortServer II. trace Records and displays trace messages that are held in the system log. user Sets the names of users who can log into PortServer II.
Page 103: Chapter 5 Configuring Terminals
When should I read this Chapter? Read this chapter if you want to connect an additional terminal to a previously- configured PortServer II, or if you want to change the configuration of a terminal that is already connected. In this Chapter This chapter describes how to configure PortServer II for connection to a terminal.
Page 104: Setting Up A Terminal
The following procedure assumes that you have connected the terminal that you wish to configure to PortServer II, following the procedures in Chapter 3, Installation. If the terminal is connected to PortServer II via a modem or a network, use the appropri- ate procedure from Chapters 8 through 10.
Page 105 For detailed information, refer to set ports in the Command Reference Guide. Take particular note of the save option that determines whether your changes are save permanently in PortServer II’s memory. 5. Set the flow control parameters using the following command: set flow [option] The options specify flow control, control character usage, and ALTPIN usage.
Page 106 Page 86 Configuring Terminals 90030500B...
Page 107: Chapter 6 Configuring Security
Chapter 4 Basic Configuration briefly described how you can provide each user with a password to increase security. This chapter covers the subject of security and includes information on configuring automatic logins to PortServer II. The Chapter includes the following topics:...
Page 108: Levels Of Security
Levels of Security PortServer II allows one of four types of security access levels to be associated with each user, as follows: • Root login. The root user has access to all PortServer II’s configurable parameters and consequently can change any of its functions. Root login is normally restricted to system administrators and managers.
Page 109: Root Login
Root Login root is provided as the only user when PortServer II is shipped. A default password of dbps is provided for the root user (see Chapter 4, Basic Configuration). The root login must always be present, and must always have a password. It is not possible to remove the root user entry, or delete the root user password.
Page 110: Regular User Login
If the set login write=on option is selected for a user's port, the user can save changes to the parameters of his or her own PortServer II port. The new parameters become the defaults available to other users who subsequently log in on that port. If the set login write=off option is selected, only the root user can save port set- tings.
Page 111: Regular User Login Without Password
Regular user login without password This configuration option does not require the user to enter his or her password when logging in. This feature is most useful in small, secure environments that do not have dial-up ports. It is not suitable for systems where security is a concern or where there are external network or dial-up connections.
Page 112: Autoconnect User Login
In this configuration, one or more ports may be configured to allow any user to log in at any time without a login or password. Any user can gain access to the PortServer II command line prompt. The configuration is only suitable for systems where security is not a major concern or if there is no possibility of unauthorized dial-up access.
Page 113: Auto Connection Of A User With Password Protection
In this configuration, a particular user is connected to a specific system after entering a login and password. This user cannot access the PortServer II command line prompt . You can specify that the connection is made using the rlogin protocol or telnet. Enter the following command: set user name=<user_name>...
Page 114: Autoconnect Port
A user on an auto-connected port can never escape to the PortServer II command line, run multiple sessions, or connect to another system. You can also specify a range of ports that are automatically connected to a host. You can specify that the connection is made using the rlogin protocol or telnet.
Page 115: Chapter 7 Configuring Multiple Sessions And Multiple Screens
Configuring Multiple Sessions and Multiple Screens When should I read this Chapter? Read this Chapter if you want to configure PortServer II to support multiple screens or multiple sessions on a previously-connected terminal. Read Chapter 5, Configuring Terminals before you read this chapter.
Page 116: General
General Any PortServer II user can run more than one session on a terminal if their permissions and operating system configuration allow this. Multiple Sessions Any user can start multiple sessions if his or her port is configured to allow multiple sessions.
Page 117: Starting Multiple Sessions
To temporarily escape from a session to the PortServer II command prompt to start another session, type the telnet escape character followed by a Carriage Return.
Page 118: Rlogin Session
Rlogin session To leave an rlogin session and return to the PortServer II command line, enter: Carriage Return ~ TESC Carriage Return To switch to another rlogin session, enter: Carriage Return ~ TESC <digit> where <digit> is a valid active session number in the range 1-9.
Page 119: Closing A Session
Closing a session To close a telnet session or an rlogin session, you can: • Log out of the remote system, which causes the remote system to close the session. • Escape to the command line and type the close command. You may also close rlogin sessions using the rlogin escape sequence: Carriage Return ~ .
Page 120: An Example Of Multiple Telnet Sessions
“login invalid...”. The user has to re-enter both user name and password. 2. Linda starts a session on Corporate. At the PortServer II prompt, Linda starts a session with the host called Corporate by typing: #>telnet corporate Note: She does not have to give an Ethernet address for Corporate if her network has domain name service.
Page 121 Corporate login prompt and returns to the PortServer II command line prompt using the telnet escape sequence: Ctrl–] 5. At the PortServer II command line prompt, Linda starts a session on the host com- puter called Engineering by typing: #>telnet engineering 6.
Page 122 Corporate session 1 was closed in step 10), logs out and closes the telnet session. 12. Linda logs out of PortServer II. The terminal displays the PortServer II command line prompt. Linda exits her session by entering: exit or quit Note: The exit and quit commands close all active telnet and/or rlogin sessions before exiting.
Page 123: Multiple Screens
<terminal_name> The PortServer II allows up to sixteen different terminal types to be configured. Each terminal type must have a distinct name, although a particular terminal may have several names if it can be used in more than one mode.
Page 124 However, if you escape to the PortServer II command line or open a fourth session, PortServer II will clear and reuse the earliest screen to display the requested session. You will then be able to switch between the new session and the two most recent sessions without losing screen context.
Page 125: Chapter 8 Configuring Wan Connections
Chapter 8 Configuring WAN Connections When should I read this Chapter? Read this chapter if you want to modify a user’s connection from one of PortServer II’s serial ports to a WAN (Wide Area Network). If you are modifying connections via a modem, you should read Chapter 9, Configuring Modem Connections before you read this chapter.
Page 126: Wan Connections Explained
WAN Connections Explained Each user can connect via PortServer II to other networks or to the Internet, in addition to the local Ethernet host(s). For each user, you must define a WAN (Wide Area Network) connection that specifies parameters such as the protocol to use. This information is stored by PortServer II in the WAN Connection Table, where it is referenced by a unique index number.
Page 127 A dialout connection also requires: • A Device Table entry. This defines the port that each modem is on, and any script that will cause the modem to dial out. A direct serial port connection also requires: • A Device Table entry. This defines the port the outgoing connection is made. A Frame Relay connection also requires: •...
Page 128: Incoming Wan Connections
Incoming WAN Connections How incoming connections are established When PortServer II receives an incoming WAN connection request, it verifies that the user’s login and password are contained in the User Table. If the verification is suc- cessful, it obtains the index called uid from the User Table. If it does not find a match, the request is referred to the RADIUS server, if one is defined.
Page 129 The IP mask that is applied to the address specified in IPAddr. If the mask is not 255.255.255.255, PortServer II assumes a router is present on the other end of the connection, and the router can forward packets to all other addresses on the network or subnet specified.
Page 130 CHAP. If set to both, the remote system negotiates what authentication is used. PapID The PAP authentication identifier that PortServer II will send to a remote system if requested. (Any identifier that the remote system returns must match the user name.)
Page 131 The CHAP key that PortServer II uses to generate a reply to the remote system. Passive If set to on, PortServer II waits for the remote system to begin PPP negotiations. If set to off, PortServer II may initiate negotiations.
Page 132: Verifying The Incoming Connection
LogPacket=<name> PassPacket=<name> For example: set user name=linda LogPacket=filter1 PassPacket=filter2 5. Optionally, you can configure PortServer II to drop the connection if there is no activity for a defined period. To do this, enter the following commands: set user name=<username> IdleTimeout=<timeout>...
Page 133: Outgoing Wan Connections
1. If the set user option dialout=on and no ActivateTime (described later) is defined, the connection is created immediately the user requests it. If a bringup filter is defined, PortServer II waits for the filter to trigger before dialing; if there is no bringup filter, the number is dialed immediately.
Page 134: How Ports Are Used
Any script must be configured before you create the device. See Chapter 9, Configuring Modem Connections for detailed information. set device name=vfast dialer=vfastscript ports=4 2. Configure the PortServer II port that will originate the outgoing connection requests, by entering a command similar to the following: set ports dev=<value> range=<value>...
Page 135 If set to an IP address, this specifies the remote host to connect to. If set to 0.0.0.0 or negotiated, the host and PortServer II negotiate the address to use; this option is useful if the host address is unknown, for example, if the host system uses an IP address pool.
Page 136 The CHAP key that PortServer II uses to generate a reply to the remote system. Passive If set to on, PortServer II waits for the remote system to begin PPP negotiations. If set to off, PortServer II may initiate negotiations.
Page 137 LogPacket=<name> PassPacket=<name> For example: set user name=linda LogPacket=filter1 PassPacket=filter2 5. Optionally, you can configure PortServer II to drop the connection if there is no activity for a defined period. To do this, enter the following commands: set user name=<username> IdleTimeout=<timeout>...
Page 138 6. If you configure an Idle Timer in the previous step, you should also configure a bringup filter. To do this, enter the following command: set user name=<username> Bringup=<filter_name> <filter_name> is the name of the bringup filter. For example: set user name=linda network Bringup=filter3 7.
Page 139: Verifying The Outgoing Connection
If there are no errors, the command line prompt is displayed. If there are any errors in the configuration, details are displayed. 2. If you use timed bring-up filters, reboot PortServer II to establish any outgoing connections. (See Chapter 17, Troubleshooting for reboot procedures). PortServer II then scans its User Table for outgoing connections that must be started because of an active AccessTime c onfiguration, then establishes those connections .
Page 140: Filters
Filters General Filters can be used in PPP, SLIP, and CSLIP connections to bringup a connection, to keep the connection up, to pass or block IP packets, and to log IP packets. Creating a filter To configure a filter, enter the following command: set filter name=<filtername>...
Page 141: Applying Actions To Source Or Destination
Applying actions to source or destination If an IP address or port is included in a filter, any match is valid for packets to and from the address or port, unless qualified with src (source only) or dst (destination only). For example: s1= 199.86.8.33 //Match if IP source or destination address is 199.86.8.33...
Page 142: Examples Of Filters That Perform Common Functions
Examples of filters that perform common functions Building a firewall with passpacket filters Filters can be defined to selectively pass or block IP packets based on: • Inbound or outbound packet IP address • Source or destination IP address • TCP/UDP port •...
Page 143: A Filter That Will Bring Up A Connection When It Detects Any Ip Packet Except Dns
A filter that will bring up a connection when it detects any IP packet except The following filter brings up a connection for any packet but dns. The first stanza is preceded by a “!”, so the filter brings up the connection when it detects IP packets that are not domain packets.
Page 144 Page 124 Configuring WAN Connections 90030500B...
Page 145: Chapter 9 Configuring Modem Connections
When should I read this chapter? Read this chapter before you add a dial-in or dial-out connection to a previously- configured PortServer II. If you have this type of connection to configure, you should read this chapter before you read Chapter 8, Configuring WAN Connections.
Page 146: About Modem Connections
User’s Guide. Refer to your modem documentation for assistance. You will also need to configure PortServer II for the protocol to use over the modem connection after you have configured the modem. Information on this is given in Chapter 8, Configuring WAN Connections.
Page 147: Configuring The Modem Connection
DTR is dropped. Configuring the Modem Connection 1. Set the relevant PortServer II serial port to the highest speed that the modem can accept without data corruption, by entering the following command: set line baud=<speed> range=<ports> [options] <speed>...
Page 148 #>set flow ixoff=off range=4 Note: For detailed information on the set flow command, see the Command Reference Guide . 4. Optionally, you can also set PortServer II to run initialization and test scripts, by entering: set modem option=<value> range=<ports> <value> is the name of the script to run. For example, to assign a test script called...
Page 149: Dialer And Login Scripts
Dialer and Login Scripts Creating or editing a script Scripts can dial modems on outgoing connections and login to remote systems. (See Chapter 8, Configuring WAN Connections). For example, if you dial in to PortServer II from a PC running Windows 95, you may need a script to work with your dialer program –...
Page 150: Script Commands
Script commands You can use the following commands in your scripts: Note: s indicates a state parameter. State parameters are described after the list of commands. Sets character size to n, and parity according to p. The value n must be 7 or 8.
Page 151: State Parameters
Exit, indicating remote system is busy. Exit, indicating remote system is down. PortServer II take action(s) if any of these exit commands are issued. For example, a retry timer is provided for both remote system busy and remote system down exit conditions.
Page 152: Escape Commands
Escape commands You can use any of the following escape commands in E, M, and [] command strings: The control character derived by the logical and-ing of ASCII character c and octal mask 037. This is the character transmitted by a standard ASCII keyboard when the Ctrl key is held down and the character c is depressed.
Page 153: Running A Script
Running a script When a script is invoked, the modem initializes to the state specified by commands C1 A80 H- D+1 D+2 Q0 T- S10 and the script executes beginning at line s1. As each state is entered, previous [] command strings are cleared, and execution proceeds from left to right.
Page 154: A Script That Tries Alternate Numbers
• “success” when it receives a connect signal. • “general failure” when there is a timeout. If “remote busy” is generated, PortServer II tries the next phone number from the System Table in the same script. If there are no more phone numbers, either because all numbers have been tried or there are no alternates, the connection attempt fails.
Page 155: A Script To Initialize A Hayes-Compatible Modem
A script to initialize a Hayes-compatible modem The following script initializes the modem and sets the data speed for 115.2Kbps. If the modem does not initialize correctly, it prints setup failed, otherwise it prints setup succeeded. s1=”M{at\r} [OK} s3 T4” s2=”M{at$k1&y0&f\r} [OK]3 T4”...
Page 156: Modem Pools
Modem Pools As an alternative to assigning a dedicated modem to each connection, you can configure a modem “pool”. Each PortServer II can be configured to look on a range of ports for an available modem. In the example command below, the PortServer II is configured for two modem pools, one using Ports 1 through 10, and the other Ports 11 and 12.
Page 157: Telnet And Modems
This section contains an example of how you can telnet from a terminal that is connected to Port 2 to a modem that is connected to Port 4 on the same PortServer II. You will telnet from the terminal on Port 2 to the modem on Port 4, use “AT” type modem commands to set a fixed DTE interface and baud rate, then call an information service.
Page 158: Configuring Cu And Uucp To Dial Out
The source code is available to customers, and you can also download binaries for most popular operating systems. RTTY is provided on an “as-is” basis by Digi International, but it is not covered by our unlimited technical support policy. Digi provides the source, internal documenta- tion in the source, and an unlimited distribution license when used with our products.
Page 159: Description Of Operation
/dev/ptys[cdef] for your pseudo-modem ports. If you want to use PortServer II ports 1-4, add the lines shown below to your “rc” startup script. The parameter “1” adds a one second delay after connection before sending data. (This ensures DTR high is established before the modem looks for “AT”...
Page 160 Note: The actual baud rates you enter are ignored by the pseudo-TTY device driver, but they must match the values in your Systems file. ACU ttysc ttysc 38400 hayes ACU ttysd ttysd 38400 hayes ACU ttyse ttyse 38400 hayes ACU ttysf ttysf 38400 hayes 3.
Page 161: Rtty Program
*connected to (PortServer II) node ncx, port 4. * rtty -dh ttypf ncx 2104 *To associate "ttysf" with a dial-in/dial-out (type mio) *modem attached to (PortServer II) node dbps port 13. * rtty -1d ttysf dbps 2113 90030500B Configuring Modem Connections...
Page 162 *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.", Page 142 Configuring Modem Connections 90030500B...
Page 163: Chapter 10 Configuring Tcp/Ip Routing
When should I read this Chapter? Read this Chapter if you are adding TCP/IP routing to a previously configured PortServer II, or if you want to modify an existing route. In this Chapter This Chapter describes how to configure the different types of routing that PortServer II supports.
Page 164: Types Of Routing Available
Types Of Routing Available You can configure PortServer II to act as an IP packet router (see Chapter 1 for a typ- ical system configuration, in which branch office users are connected to an Internet service provider). PortServer II supports two types of routing, Passive and Active. With passive routing, it takes packets in from hosts and routers connected to it, and decides where to for- ward them.
Page 165: Description Of Passive Routing
Ethernet interface. For example, if a dial-in user has an address on the same subnet as PortServer II, hosts on the same Ethernet interface as PortServer II can “ARP” for the IP address of the dial-in user, and PortServer II will respond to the ARP request with its Ethernet address.
Page 166: Passive Routing
Passive Routing To configure a PortServer II port for passive routing, proceed as follows: 1. Configure a WAN connection, as described in Chapter 8, Configuring WAN Con- nections. 2. If static routes are needed beyond those contained in the WAN connection, con- figure each route by entering a command in the format: set route net=<network_address>...
Page 167: Active Routing
Active Routing To configure a PortServer II port for active routing, proceed as follows: 1. Configure a WAN connection, as described in Chapter 8, Configuring WAN Connections. 2. If static routes are needed beyond those contained in the WAN connection, con- figure each route by entering a command in the format: set route net=<network_address>...
Page 168 Page 148 Configuring TCP/IP Routing 90030500B...
Page 169: Chapter 11 Configuring Realport Connections
When should I read this Chapter? Read this Chapter if you are connecting a terminal, printer, modem, or serial line to PortServer II and the associated host accesses the device using Digi International’s RealPort protocol, or if you want to modify an existing RealPort connection.
Page 170: Realport Basics
The ports on the PortServer II may be split among hosts; for example, one host can use the odd-numbered ports while another is using the even numbered ports. RealPort also allows one host to handle incoming modem calls on a port, while allowing other hosts to place outgoing calls if there is no current incoming call.
Page 171: Configuring Portserver Ii For Realport Operation
Configuring PortServer II for RealPort Operation To configure a PortServer II port to connect a “real” TTY to a host running RealPort: 1. Set authorization to allow the host running RealPort access to the serial port, by entering a command in the following format: set auth ip=<ipaddress>...
Page 172 RealPort connections, or to mio if you want incoming calls to go directly to PortServer II’s normal login interface. For other types of connection that need modem signals, set the device type to host. All of these device types...
Page 173: Chapter 12 Configuring Snmp
When should I read this Chapter? Read this Chapter if your system supports SNMP (Standard Network Management Protocol) and you want PortServer II to respond to SNMP requests. In This Chapter This Chapter describes how to configure PortServer II’s SNMP Agent.
Page 174: General
Trap PortServer II uses this message to asynchronously report a significant event to the SNMP host. A list of specific variables that PortServer II supports for each MIB is given at the end of this chapter. Page 154 Configuring SNMP...
Page 175: Configuring The Snmp Agent
Configuring the SNMP Agent To configure the SNMP Agent on a PortServer II, enter a command in the following format: snmp [run=off|on] [auth_trap=off|on] [trap_dest=<ipaddress>] [location=<portserver_id>] [snmp_name=<portserver_name>] [snmp_contact=<administrator_name>] • If you set run=off, the SNMP daemon is stopped and all SNMP reporting for the PortServer II is disabled.
Page 176: Monitoring Snmp Status On Portserver Ii
SNMP requests from a host or management station. Authentication traps are not being sent (off), but other standard traps are being sent to IP address 199.99.88.1. The values for the System portion of MIB II are set to identify the PortServer II, its name, and the name of the responsible administrator.
Page 177: Supported Smnp Variables
Supported SMNP Variables System Interfaces IP MIB ICMP MIB sysDescr ifNumber ipForwarding icmpInMsgs sysObjectID ifIndex ipDefaultTTL icmpInErrors sysUpTime ifDescr ipInReceives icmpInDestUnreachs sysContact ifType ipInHdrErrors icmpInTimeExcds sysName ifMtu ipInAddrErrors icmpInParmProbs sysLocation ifSpeed ipForwDatagrams icmpInSrcQuenchs sysServices ifPhysAddress ipInUnknownProtos icmpInRedirects ifAdminStatus ipInDiscards icmpInEchos ifOperStatus ipInDelivers icmpInEchoReps...
Page 178 System Interfaces IP MIB ICMP MIB ipNetToMediaIfIndex ipNetToMediaPhysAd- dress ipNetToMediaNetAd- dress ipNetToMediaType ipRoutingDiscards Address Translation Frame Relay DTE MIB frDlcmiIfIndex atIfIndex frDlcmiState atPhysAddress frDlcmiAddress atNetAddress frDlcmiAddressLen frDlcmiPollingInterval frDlcmiFullEnquiryInterval frDlcmiErrorThreshold frDlcmiMonitoredEvents frDlcmiMaxSupportedVCs frDlcmiMulticast frCircuitIfIndex frCircuitDlci frCircuitState frCircuitReceivedFECNs frCircuitReceivedBECNs frCircuitSentFrames frCircuitSentOctets frCircuitReceivedFrames frCircuitReceivedOctets frCircuitCreationTime frCircuitLastTimeChange...
Page 179 Character TCP MIB RS232 MIB SNMP MIB tcpRtoAlgorithm udpInData- rs232Number snmpInPkts charNumber grams tcpRtoMin udpNoPorts rs232PortIndex snmpOutPkts charPortIndex tcpRtoMax udpInErrors rs232PortType snmpInBadVersions charPortName tcpMaxConn udpOutData- rs232PortInSigNumber snmpInBadCommuni- charPortType grams tyNames tcpActiveOpens udpLocalAd- rs232PortOutSigNumber snmpInBadCommunity- charPortHardware dress Uses tcpPassiveOpens udpLocalPort rs232PortInSpeed snmpInASNParseErrs charPortReset tcpAttemptFails...
Page 180 Page 160 Configuring SNMP 90030500B...
Page 181: Chapter 13 Configuring Printer Connections
When should I read this Chapter? Read this Chapter if you want to configure a printer that you have connected to a PortServer II, or if you want to modify an existing printer connection. In this Chapter This Chapter describes how to configure a serial port to use with a printer.
Page 182: General
If so, the DTR line from the printer must be wired to an input to the PortServer II (usually CTS or DCD) that can be used for flow con- trol. Some printers use Printer Busy (pin 11) for output flow control. Refer to Chapter 3, Installation and your printer documentation for more information.
Page 183 CTS on PortServer II must be connected to DTR on the printer in this configura- tion. Important: If flow control is necessary, set the printer’s flow control to match the flow control on PortServer II.
Page 184: Printing A File Using Telnet Or Rsh
Printing a File using telnet or rsh The following section shows examples of commands you can use to print a file on a printer that is connected to Port 1 on the PortServer: Using telnet pr myfile | telnet ncx 2001 Using rsh pr myfile | rsh ncx 1 Troubleshooting...
Page 185: Printing Using Lpd Protocol
Printing using lpd Protocol Configuring the printer To use the lpd protocol to print to a printer connected to PortServer II, configure the print spooler on your system to print to a remote printer. Give the name or IP address of PortServer II as the remote system’s name.
Page 186: Queue Name Examples
Carriage Return/Line Feed pairs, and adds no extra characters to the end of the print stream. An example entry into the BSD style /etc/printcap file, with the PortServer II named nx5 and using ascii_1_f as the print queue name is shown below:...
Page 187: Chapter 14 Configuring Frame Relay
Configuring Frame Relay When should I read this Chapter? Read this Chapter if you want to use a Frame Relay service with PortServer II. In This Chapter This Chapter describes how to configure a serial port for Frame Relay service. The port must have already been configured as a WAN connection.
Page 188: What Is Frame Relay
“cloud”. This arrangement allows a server to make a “logical” connection to sev- eral other servers that are also connected to the service, but utilizing only one physical circuit. User Terminal User Terminal FR Switch PortServer II PortServer II DLCI DLCI Frame Relay Service...
Page 189: Specifying Frame Relay
When you implement Frame Relay service, you will need the following information: • The Link Management Interface (LMI). Each PVC that you implement is assigned an LMI specification. The LMI determines how often PortServer II will poll the network to obtain updates. The network service provider may specify one of several LMIs, including ANSI T1.617 Annex D, ITU (CCITT) Q.933 Annex...
Page 190: Designing A Network To Use With Frame Relay
Designing a network to use with Frame Relay This section provides some guidelines on upgrading your network to use a Frame Relay service. 5. Map PVC and 1. Determine performance determine business objectives rules 6. Calculate port 2. Review existing network connection speed 3.
Page 191 • Identify the number of users, the total number of packets transferred, and any variations at different times or on different days. • Determine the protocols used. • Note any points of congestion or slow responses experienced by users. 4. Map your PVC (physical circuit) and lay down business rules. •...
Page 192: Configuring A Frame Relay Port
• BECN. If <option> is on, configures the port to run at the fallback speed if the BECN bit is set in a received frame. FECN is ignored, even if you set BECN on. If you set BECN=off, PortServer II ignores the BECN bit. • lmi=<scheme> configures the Local Management scheme to use on the link, Rev1, AnnexD, or AnnexA.
Page 193 • enabled=on allows traffic on this connection, off disables the connection. • fallback= sets the period that PortServer II will use the fallback speed on this DLCI after receiving a BECN bit in a packet. BECN must be set to on in step 2 for this setting to be effective.
Page 194 IP addresses, by setting IPAddr to the remote IP address of the Frame Relay service. The local IP address should be set to 0, allowing the PortServer II’s Ethernet address to be used. 5. When configuration is complete, start the Frame Relay link by entering: set user <name>...
Page 195: Chapter 15 Configuring Radius
Chapter 15 Configuring RADIUS When should I read this Chapter? Read this Chapter if you want to configure PortServer II to use the RADIUS authenti- cation protocol on its dial-up connections. You must have RADIUS available on your server. In this Chapter This Chapter describes how to configure PortServer II to use RADIUS on all its dial- up connections.
Page 196: How Does Radius Work
UNIX password file, Network Information Services (NIS), and a separately- maintained RADIUS database. When a user logs into a PortServer II that is configured to use RADIUS, PortServer II collects login information such as username and password. It then looks in its local database of users for the username;...
Page 197: Configuring Radius
Configuring RADIUS To configure PortServer II to obtain user name and password authentication from a RADIUS server for users on all modem ports: 1. Configure a modem for each dial-in connection, as described in Chapter 9, Configuring Modems. 2. Enable RADIUS authentication on all dial-up ports by entering a command in the format: set radius run=on primary=<ipaddress>...
Page 198: Configuring Radius On A Server
Configuring RADIUS on a Server To use RADIUS with PortServer II, you must have at least one RADIUS server on your network. You can download the RADIUS server binary code from Digi Interna- tional’s FTP server, if you do not already have it installed.
Page 199: Chapter 16 Remote Configuration
Remote Configuration When should I read this Chapter? Read this Chapter if you want to configure PortServer II from a remote host. You can update both the PortServer II software and your own configuration file in this way. In this Chapter This Chapter describes how to transfer files to and from PortServer II by TFTP, and how to edit the configuration file.
Page 200: When Should I Use Remote Configuration
ROM or other hardware. To upgrade the software: 1. Obtain a copy of the new version of software from Digi International’s FTP server and place it on your TFTP server. The address of the Digi FTP server is given in Chapter 18, Digi Support Services.
Page 201 Alternatively, set tftp=smart, so that if PortServer II cannot find the file, it will not repeat the attempt. 3. Reboot PortServer II by switching power on and off, or by entering boot action=reset. When rebooting is complete, PortServer II will operate from the new version of software.
Page 202: Editing Portserver Ii's Configuration From A Remote Host
PortServer configuration file to a specified host for editing. After editing, you can write the modified configuration file back into PortServer II. You can also copy the file into another PortServer II, allowing you to copy similar configurations from one PortServer II to another.
Page 203: Editing The Configuration File
The number of lines in the file and their content depends on the previous configuration of the PortServer II. You can edit the file, according to the following guidelines: • If you add a line to the file, ensure it is in the same format as other lines for the same set command.
Page 204: Restoring A Portserver Ii Configuration File From A Host
Restoring a PortServer II configuration file from a host When you have completed editing of the configuration file: 1. Save it to the same location, overwriting the file you uploaded from PortServer II. 2. Copy the configuration file back to the PortServer II by entering the following command at PortServer II’s command line:...
Page 205: Tftp Error Messages On Portserver Ii
2. Repeat the TFTP command. 3. If the problem reoccurs: a. Press the arrow keys (< and >) on PortServer II’s front panel to reboot from internal Flash ROM b. Repeat the configuration command set host to ensure that the host’s IP address, and the path and file name of the configuration file are correct.
Page 206 Page 186 Remote Configuration 90030500B...
Page 207: Chapter 17 Troubleshooting
Chapter 17 Troubleshooting When should I read this Chapter? Read this Chapter if you have just installed PortServer II and want to check it is functioning correctly, or if you are having difficulty with a previously installed PortServer II. In This Chapter This Chapter contains information on basic diagnostic and fault tracing features.
Page 208: Power On Self Test
Power On Self Test The PortServer II Power On Self Test (POST) sequence is initiated after PortServer II is switched on, reset, or an internal watchdog timer expires. It comprises a series of basic tests that ensure the main components (such as the microprocessor, memory, and network interface controller) are functioning properly.
Page 209: Interpreting The Alphanumeric Display
PortServer II’s CPU is 100% utilized. Under normal operation between one and five LEDs should be lit, depending on the traffic. • AC indicates PortServer II has passed the tests and is now in normal operating mode. 90030500B...
Page 210: User Diagnostics
You can run diagnostics either from a terminal (or PC with terminal emulation soft- ware) connected to Port 1 or from PortServer II’s front panel. Diagnostics can be selected any time before the POST test described above finish. To select diagnostics: •...
Page 211 3. When you press ?, the diagnostics menu appears, as shown below. This lists the eight tests that you can select. These tests perform diagnostic checks on hardware within PortServer II. DIAGNOSTICS MENU--- A = All tests (except 9)
Page 212: Front Panel Display Diagnostics
Front panel display diagnostics 1. Press either the left or right pushbutton on the front panel during the POST tests to enter diagnostic mode. Check that all of the LEDs go OFF, the left alphanumeric display is blank, and the right alphanumeric display shows 1. The right decimal point blinks at one second intervals.
Page 213: Test 3 - Timer Test
Test 4 - Built-in UART and External EBI Internal Loopback Test This tests the UARTS within PortServer II, and also the external EBI expansion mod- ules with an internal loop-back test. It tests that the UARTs interrupt and that data loops back.
Page 214: Resetting Portserver Ii To Factory Defaults
Resetting PortServer II to Factory Defaults You can reset PortServer II to its factory default settings under a number of situations, for example: • You want to use a previously configured PortServer II in a different installation that will require a new configuration.
Page 215: Statistics
Statistics Viewing statistics You can use the info command to view PortServer II’s network statistics tables or to clear their contents (see the Command Reference Guide for more details). The infor- mation in the tables includes the statistics gathered since the tables were last cleared.
Page 216: Interpretation Of Statistics
The number of incoming datagrams that were discarded because the IP address in the IP header's destination field was not a valid address to be received at PortServer II’s network. This count includes invalid addresses (e.g., 0.0.0.0) and addresses of unsup- ported Classes (e.g., Class E).
Page 217 In a correctly configured network, this number should be zero or near to zero. ipForwDatagram The number of incoming datagrams for which PortServer II’s network was not the final IP destination. PortServer II’s attempts to find a route to forward these datagrams to their final destination(s) were not successful. ipOutRequests The total number of IP datagrams that local IP user protocols (including ICMP) sup- plied to IP in requests for transmission.
Page 218: Icpm Statistics
Note: This counter include datagrams counted in ipForwDatagrams if any such packets met this (discretionary) discard criterion. ipInUnknownProtos The number of datagrams that were addressed to PortServer II’s network and received successfully but were discarded because of an unknown or unsupported protocol. ICPM Statistics The following statistics are displayed if you enter info icpm.
Page 219 The number of ICMP Timestamp Reply messages received. icmpOutMsgs The total number of ICMP messages which PortServer II attempted to send. Note: This counter includes all those messages counted by icmpOutErrors. icmpOutEchos The number of ICMP Echo (request) messages sent.
Page 220: Tcp Statistics
icmpOutAdrMskR The number of ICMP Address Mask Reply messages sent. icmpOutEchoRp The number of ICMP Echo Reply messages sent. icmpOutRedirec The number of ICMP Redirect messages sent. icmpOutDstUnre The number of ICMP Destination Unreachable messages sent. icmpOutSrcQuen The number of ICMP Source Quench messages sent. icmpOutTimeExc The number of ICMP Time Exceeded messages sent.
Page 221: Udp Statistics
tcpPassiveOpen The number of times that TCP connections have made a direct transition to the SYN- RCVD state from the LISTEN state. tcpAttemptFail The number of times that TCP connections have made a direct transition to the CLOSED state from either the SYN-SENT state or the SYN-RCVD state, plus the number of times TCP connections have made a direct transition to the LISTEN state from the SYN-RCVD state.
Page 222: Interface Statistics
The total number of UDP datagrams that have been sent from PortServer II. udpNoPorts The total number of received UDP datagrams for which there was no application at the destination port. Interface Statistics The following statistics are displayed if you enter info if.
Page 223: Frame Statistics
The total number of octets transmitted from PortServer II’s interface, including fram- ing characters. ifOutUcastPkts The total number of packets that higher level protocols requested be transmitted to a subnetwork unicast address, including those packets that were discarded or not sent.
Page 224: Frame Relay Statistics
Out IP Number of IP frames sent. Out ARP Number of arp frames sent. Frame Relay Statistics The following statistics are displayed if you enter info framerelay. frCircuitReceivedFrames The number of frames received over this virtual circuit. frCircuitReceivedOctets The number of octets received over this virtual circuit. Received Fragments The number of fragments received over this virtual circuit.
Page 225 Sent Fragmented The number of frames that were fragmented before sending. frCircuitReceivedFECNs The number of frames received from the network indicating forward congestion. frErrType The type of error that was last seen on this interface. too long The number of frames received that exceeded the maximum frame size on this circuit. bad DLCI The number of frames that were received with an invalid DLCI.
Page 226 unknown DLCI The number of received frames with a DLCI indicating a PVC that is not configured. LMI unknown IE The number of Information Elements in received LMI packets that had an unrecog- nized type code. LMI unknown report The number of LMI reports received that had an unrecognized type code. status requests The number of LMI status requests sent.
Page 227 The first range value in the example above specifies the circuits. A single number, a range of numbers, and an “*” for all links may be entered. Even though a mixed range was requested, only Circuit 8 is up in this PortServer II 90030500B...
Page 228 (the other links requested are not set up for Frame Relay operation). By adding another index after the link index, it is possible to display the statis- tics for one, some, or all active PVCs for one, some, or all links. For example: #>...
Page 229: Hardware Error Counts
Hardware Error Counts In Overruns The number of times a data overrun occurred because PortServer II’s Ethernet con- troller was unable to place a received frame in memory. In Unaligned The number of times that misaligned frames arrived. In No Resource The number of times that an incoming frame could not be processed due to lack of available buffers.
Page 230: Trace Messages
Trace Messages When PortServer II encounters an error or unexpected situation, it may print trace messages to help the network administrator or other user identify the problem. You can select trace messages in a specific group if you know the source of the problem, or you can print all trace messages to help isolate a problem that you do not know the cause of.
Page 231: Explanation Of Trace Messages
Other errors may permit actions to be taken by the user to correct the problem encoun- tered. Digi Technical Support will also be happy to assist in resolving these problems. Certain messages caused by obscure errors are not listed below. If you see a message that is not listed below, you should contact Digi Technical Support for advice.
Page 232: Arp Messages
IP address. 4) another unit using our address <IP address> An ARP packet arrived from a unit using the IP address of the PortServer II. 5) gratuitous ARP found IP address conflict <IP address> Gratuitous ARP detected another box using the IP address of the PortServer II.
Page 233: Dns Messages
DNS messages (Option=DNS) 1) could not unlink host <name> by name *Internal error* 2) could not unlink alias <name1> for host <name2> *Internal error* 3) could not unlink host <name> by address *Internal error* 4) could not unlink secondary <IP address> host <name> by address *Internal error* Ethernet messages (Option=ether)
Page 234: Ip Messages
While attempting to send data to this <DLCI>, PortServer II has detected that it is not in service. 6) LCB is not up While attempting to send data on this LMI, PortServer II has detected that it is not in service. IP messages (Option=ip) 1) packet discarded from interface <name>: invalid buffering...
Page 235: Netcx Messages
or invalid. 7) couldn't add to route table (invalid metric) An attempt to add a route to the Route Table failed because metric was not 1 for a direct host address, greater than 3 for a direct net address, or 0 for an indirect address. 8) couldn't add to route table (invalid address) An attempt to add a route to the Route Table failed because the address is the same as the Ethernet's IP address.
Page 236: Netd Messages
3) tcp_netcx: send EOF error: <error number> *Internal error* NETD messages (Option=netd) 1) Could not set default router: max number of static routes already defined The default router could not be set. 2) could not open enet *Internal error* 3) could not configure enet for IP *Internal error* 4) could not configure enet for ARP *Internal error*...
Page 237: Inetd Messages
11) could not configure IP *Internal error* 12) could not configure altip *Internal error* INETD messages (Option=inetd) 1) could not create direct socket *Internal error* 2) could not bind direct socket *Internal error* 3) could not set listen on direct socket *Internal error* 4) could not set accept on port *Internal error*...
Page 238: Ppp Messages
10) couldn't bind entry %-d\n", index *Internal error* 11) couldn't set listen on entry %-d\n", index *Internal error* 12) escaped!! *Internal error* PPP messages (Option=ppp) 1) open(<port>): memory allocation failed. A memory allocation failed. 2) cid(<port>) Peer Rejected Protocol: <protocol number> The remote server rejected a protocol necessary for PPP operation.
Page 239: Routed Messages
The retry limit for unacknowledged TCP data has been reached; the TCP session will be aborted. WAN messages (Option=wan) 1) not enough memory to start dialing process PortServer II does not have sufficient memory available to dial out to create a connec- tion. 90030500B Troubleshooting Page 219...
Page 240 2) not enough memory to start user process PortServer II does not have sufficient memory available to create a connection. 3) malloc error dialing on port <port> A memory allocation failed. 4) link task received M_ERROR An error occurred in a lower layer (possibly the serial driver) and the link will be aborted.
Page 241 24) WAN couldn't connect interface to data stream *Internal error* 25) WAN couldn't send message, port probably locked up! A serial port may be stuck in one state. Try rebooting PortServer II to clear the prob- lem. If the condition persists, contact Digi Technical Support. 90030500B...
Page 242: Dialer Messages
27) connect mgr received an illegal msg *Internal error* 28) unable to open port <port> for frame relay PortServer II could not set the port for Frame Relay because the port appeared to be busy. 29) port <port> for frame relay: I_LINK fails...
Page 243: Warning Trace Messages
The remote system’s ARP response used a multicast address, so the mapping was ignored. 2) request timed-out for <IP address> No ARP response was received, and PortServer II timed out. DNS Messages (Option=dns) 1) entry <name> time-out, removing from list DNS mapping for <name>...
Page 244: Telnet Messages
Trace Debug command to identify the cause. 2) packet discarded from interface <name>: not a router The PortServer II is not configured as a router and a packet to be routed was received. 3) packet discarded from interface <name>: source route failure The PortServer II is not defined as a router and a packet to be routed using source routing was received.
Page 245 4) packet discarded from interface <name>: TCP broadcast A TCP broadcast message was received and discarded. 5) packet discarded from interface <name>: TCP header error A TCP packet had a header error, probably a TCP checksum error, and was discarded. 6) packet discarded from interface <name>: UDP altip address A UDP packet was received using an AltIP address and was discarded.
Page 246: Forwarder Messages
16) packet discarded to interface <name>: fragmentation data error The packet to be fragmented was in error, so the packet was discarded. Forwarder Messages (Option=fwdr) 1) packet discarded on interface <name>: <reason> The reason(s) for discarding the packet are detailed in associated Trace IP messages. Routed Messages (Option=routed) 1) adding dependency route for <index>...
Page 247: Netcx Messages
7) invalid route address family: <value> A RIP packet entry was found with an invalid address family, and the entry was ignored. 3) invalid source address: <IP address> A RIP packet sender was found with an invalid <IP address>, and the packet was ignored.
Page 248: Netd Messages
NETD Messages (Option=netd) 1) IP address is unknown - RARPing PortServer II will try to learn its IP address via RARP. INETD Messages (Option=inetd) 1) unexpected signal - <number> *Internal error* Serial Messages (Option=serial) 1) (<port>) spurious interrupt *Internal error* (possible hardware problem).
Page 249 5) <name>: Menu access enabled with no menu selected. The user was configured for access via a menu but no menu is defined. 6) <name>: Menu number references undefined menu The user is configured to use a menu that is not defined. 7) <name>: Syntax error in AccessTime string.
Page 250: Radius Messages
PortServer II. 3) Radius: Service not recognized, access denied. The RADIUS server indicated a type of service that PortServer II does not understand. 4) Radius: Protocol not recognized, access denied. A Framed Protocol value other than SLIP or PPP was specified.
Page 251: Ppp Messages
12) Radius: Ippool can only be used with 255.255.255.255 netmask The RADIUS server told PortServer II to give the user an IP address from the IP pool, but gave a netmask value that was not 255.255.255.255.
Page 252: Vj (Van Jacobsen) Messages
A packet was discarded because it is too small to be a PPP frame. This can happen when PortServer II is shifting into PPP mode at the beginning of a connection. 7) cid(<port>) Dropping <n> byte packet - Network layer down A data packet was received before PPP negotiations were finished.
Page 253: Wan Messages
Wan Messages (Option=wan) 1) IP Pool out of addresses, could not start <name> More users are trying to use dynamic IP addresses than there are addresses in the IP pool. 2) <name>: No phone numbers The user is configured to dial out, but there are no phone numbers listed in his or her profile.
Page 254: Dialer Messages
11) <name> failed verify The user is incorrectly configured. Use the wan verify command to find out why. 12) <name>: bad value for access time The access time during which the user can start a connection has a syntax error. 13) can't create route for interface=<name>...
Page 255: Tracing The Route To A Host
Many problems that you will encounter when using PortServer II in a network may be due to faults with external systems. This is especially true if you use PortServer II to connect to the Internet, where data may pass through many systems between source and destination.
Page 256: Examples Of Printout Generated By The Traceroute Command
Examples of printout generated by the traceroute command The following example includes replies from all intermediate Gateways: traceroute nis.nsf.net traceroute to nis.nsf.net (35.1.1.48), 30 hops max, 56 byte packet 1 helios.ee.lbl.gov (128.3.112.1) 19ms 19ms 2 lilac-dmc.Berkeley.EDU (128.3.216.1) 39ms 39ms 19ms 3 lilac-dmc.Berkeley.EDU (128.3.216.1) 39ms 39ms...
Page 257: Troubleshooting Frame Relay
2. If the Trace Log does not provide any assistance in identifying the problem, check the current state of PortServer II. You can do this by setting the Trace mode to concurrent with the following command: set trace mode=concurrent Frequently, the process that is failing to run will retry periodically.
Page 258 The detailed messages displayed should indicate the source of any problems with the Frame Relay link. If you require help in interpreting the debug messages dis- played, contact Digi Technical Support. Page 238 Troubleshooting 90030500B...
Page 259: Chapter 18 Digi Support Services
Digi Support Services When should I read this chapter? Read this chapter if you have a problem with PortServer II and need advice from Digi International support personnel, or if you want to download software or information. In This Chapter This chapter describes Digi International’s support services.
Page 260: Web Server: Access To Digi Information
You can access the Web server at http://www.dgii.com. Internet FTP Server: Access to Digi Drivers Purpose The Digi anonymous FTP server provides you with access to Digi drivers and related installation information. Address You can access the FTP server at ftp.dgii.com.
Page 261: Digi Bbs: Access To Drivers And Information
• Access to general and technical information about Digi’s products • Access to the most recent software driver updates and upgrades • An opportunity to leave messages for Technical Support regarding Digi products. Modem Support The Digi BBS supports the following: •...
Page 262: Customer Service
However, many problems are due to factors other than product defects. To save you time and possibly additional cost, Digi asks that you first try to resolve difficulties by contact- ing our technical support representatives at (612) 912-3456.
Page 263: Technical Support
Technical Support Introduction If you experience difficulty with a product, Digi has a staff of technical support specialists to assist you. Support Process Follow this process to resolve the problem with Digi products: • First, contact your Digi dealer or distributor. They provide first-level technical support and have the training to help you with any installation questions or difficulties you may have.
Page 264 Page 244 Digi Support Services 90030500B...
Page 265: Glossary
Glossary 10BaseT IEEE 802.3 specification, using twisted pair wiring and RJ-45 connectors. 10Base2 IEEE 802.3 specification network, using coaxial cables and BNC connectors. Sometimes called “thin Ethernet” or “Thinnet”. Address A data structure used to identify a unique entity, such as a particular process or network.
Page 266 Chapter 14, Configuring Frame Relay. Domain Name Service. A method of providing network devices with names, rather than numerical addresses. External Bus Interface, a Digi International standard for connecting external modules to devices such as PortServer Ethernet A baseband LAN, operating at 10 Mbps using CSMA/CD to operate over coaxial cable.
Page 267 Annex D or ITU (CCITT) Q.933 Annex A. Management Information Base. The database of parame- ters that an SNMP server can read from an SNMP-compat- ible device such as PortServer II. See RFC1213 for more information. Modem Modulator-demodulator. A device that converts digital signals for transmission over analog telephone lines, and vice versa.
Page 268 A message sent to test the reachability of a network device. Also (as a verb), to send a message to a device and wait for an acknowledgment. Port An interface on PortServer II that is associated with a serial connector. Point-to-Point Protocol. See RFC1331 for more informa- tion.
Page 269 Simple Network Management Protocol, a method of SNMP administering devices that are connected to an IP network. See RFC1157 for more information. TCP/IP Transmission Control Protocol/Internet Protocol. corresponds to Layer 4 of the OSI model, the data transport layer. IP corresponds to Layer 3 of the OSI model, the net- work layer.
Page 270 Page 250 Glossary 90030500B...
Page 271: Index
Index Configuration Abbreviating Commands 56 Abbreviations 56 access permissions 81 admin 90 active routing 147 Alphanumeric Display 20 alternate IP address 81 AC 20 ARP table 81 b 189 autoconnect port 94 E0 through E9 189 autoconnect user with password 93 EA 20 autoconnect user without password 93 PU 20...
Page 272 External Bus Interface (EBI) time and date 82 connector 10 trace messages 82 user 93 Factory Defaults user menu 78 resetting PortServer II to 194 users 67 FaxBack server 241 WAN 106 FECN 169 Configuration file File copying to a host 182...
Page 273 Network connection, testing 65 Rlogin session newpass 76 closing 99 controlling 98 On-line help 60 switching 98 Root login 89 Router, PortServer II as 9 PAP 6 Routing Passpacket filter 112 active 144 PassPacket filters 123 passive 144 Passpacket filters 117...
Page 274 RTTY 138 set framerelay 172 source code 141 set FrDLCI 81 set FrDlci 173 set host 81 Safety Warnings 33 set ippool 74 Script set key 58 dialer, repeat same number 134 set keys 81 running 133 set line 58 Scripts 7 set login 90 commands 130...
Page 275 IP Statistics 196 Explanation 211 TCP Statistics 200 Forwarder Messages 226 UDP Statistics 201 Frame Relay Messages 223 Viewing 195 Frame Relay messages 213 STREAMS 138 INETD Messages 228 support services 239 IP Messages 224 – IP messages 214 NetCX Messages 227 Tables 5 NetCX messages 215 TCP service ports 82...
Page 276 UUCP 138 Van Jacobsen TCP compression 110 wan 112 WAN Connection Incoming, verifying 112 outgoing, verifying 119 WAN Connections bidirectional 119 incoming 108 Outgoing 113 WAN connections 106 Warning Trace Messages 223 warrantee information 242 World Wide Web server 240 Page 256 Index 90030500B...
Page 277 WWW: http://www.dgii.com © 1996 Digi International. All rights reserved. The Digi logo is a trademark of Digi International. All brand names and product names are trademarks or registered trademarks of their respective holders. %...

Digi PortServer II User Manual

About this User's Guide

Chapter 1 Introduction

Chapter 2 Operation

Chapter 3 Installation

Chapter 4 Basic Configuration

Chapter 5 Configuring Terminals

Chapter 6 Configuring Security

Chapter 7 Configuring Multiple Sessions and Multiple Screens

Chapter 8 Configuring WAN Connections

Chapter 9 Configuring Modem Connections

Chapter 10 Configuring TCP/IP Routing

Chapter 11 Configuring Realport Connections

Chapter 12 Configuring SNMP

Chapter 13 Configuring Printer Connections

Chapter 14 Configuring Frame Relay

Chapter 15 Configuring RADIUS

Chapter 16 Remote Configuration

Chapter 17 Troubleshooting

Quick Links

Troubleshooting

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Digi PortServer II

Summary of Contents for Digi PortServer II