KEPCO IEPS 1000 Series Service manual

IEPS 1000 Series
Network Device Server (NDS)
Administrator’s Guide
KESSLER-ELLIS PRODUCTS
10 Industrial Way East
Eatontown, NJ 07724
800-631-2165 • 732-935-1320
Fax [phone]
http://www.kep.com
990187 REV:D 05/12/09

Table of Contents
CHAPTER 1: INTRODUCTION...................................................................................3
CHAPTER 2: CONFIGURATION................................................................................5
Device Server Configuration ..........................................................................................5
Setting the IP Address....................................................................................................5
DHCP/BOOTP..............................................................................................................5
NativeCOM...................................................................................................................5
Assigning a Temporary IP Address via the Network.....................................................6
How to Use the Serial Ports ...........................................................................................7
Configuring NativeCOM Ports for Windows..................................................................7
Configuring Printers (via LPR/LPD) ..............................................................................7
Configuring Outgoing Network Connections.................................................................8
Configuring Incoming Network Connections via Telnet Server .....................................8
Configuring Modem Emulation......................................................................................9
Configuration via the Web Browser Interface.............................................................10
Serial Settings ............................................................................................................11
Port Services...............................................................................................................14
Service Types.........................................................................................................................14
Phone Number Translation.........................................................................................17
Network Translation....................................................................................................19
Protocol Settings ........................................................................................................20
Raw or Secure TCP ...............................................................................................................21
(Secured) Simple POS Terminal Protocols............................................................................21
(Secured) Converted POS Terminal Protocols ......................................................................21
Paymentech™ NetConnect Conversion.................................................................................22
First Horizon Internet Gateway...............................................................................................22
SSL Options ...........................................................................................................................23
Type of Peer........................................................................................................................... 23
Peer Identity Verification.........................................................................................................23
List of Allowable Ciphers........................................................................................................24
Network Settings ........................................................................................................26
IP Address..............................................................................................................................26
IP Netmask.............................................................................................................................27
TCP Keep-Alive......................................................................................................................28
DNS Settings..............................................................................................................29
IP Routing...................................................................................................................31
Time Settings..............................................................................................................33
Security Settings.........................................................................................................34
System Password...................................................................................................................34
Network Isolation Configuration .............................................................................................35

Online Update.............................................................................................................36
CHAPTER 3: EXAMPLE APPLICATIONS ...............................................................39
Connect Peripherals to a Windows Host.....................................................................39
Connect Peripherals to a Unix Host.............................................................................39
Setup a Terminal or Modem to Connect to a Host......................................................40
Ethernet-based Serial Multiplexer................................................................................40
Ethernet-based Console Server...................................................................................41
Replacing a Dial-Up Modem Connection.....................................................................41
Accessing the Device Server from a Remote Network...............................................42
CHAPTER 4: TROUBLESHOOTING AND UPDATING ...........................................43
System Log....................................................................................................................44
Serious System Error Codes ......................................................................................45
Port Status.....................................................................................................................46
OS Information..............................................................................................................48
Network Information .....................................................................................................49
Network Interfaces........................................................................................................50
Log/Debug Settings ......................................................................................................51
Ping................................................................................................................................53
Reset/Reboot.................................................................................................................54
Flash Management........................................................................................................55
Flash Update..............................................................................................................56
Download Flash Information.......................................................................................56
Restore Factory Defaults............................................................................................57
PDA Compaction........................................................................................................57
Other Debugging...........................................................................................................58
CHAPTER 5: MODEM EMULATION........................................................................59
Modes.............................................................................................................................59
Escape Sequence..........................................................................................................59
Types of TCP/IP connections .......................................................................................59
Outgoing and Incoming Calls.......................................................................................60
AT Commands...............................................................................................................60
Supported Commands................................................................................................61
S-Registers....................................................................................................................63
Supported S-registers.................................................................................................63
Response Codes...........................................................................................................63
Modem Signal Behavior................................................................................................64
Phone Numbers.............................................................................................................65
Port Settings..................................................................................................................65
CHAPTER 6: LICENSE INFORMATION ..................................................................66
INDEX...................................................................................................69

Page 3
Chapter 1: Introduction
The IEPS-1000 Device Server family provides communication between peripheral
devices and computers connected to a network. When a device server is connected to your
LAN and to one or more peripherals, it manages peripheral traffic over the network, routing
it to the correct device.
As system administrator, you will have responsibility for setting up and configuring the
device server to meet your usage requirements. The device server has been designed to
make your job easy. If you are using the serial port(s) from Systech's NativeCOM, you need
only set the IP address and related parameters. This can be done with DHCP/BOOTP or
with the NativeCOM utilities. The remaining configuration will be on the host or hosts that
are accessing the device server. The hardware is simple to install, and a browser interface
ensures that management is just as simple. In addition to configuration tools, the
communications server provides tools for monitoring and managing your port activity and
for diagnosing and troubleshooting system problems.

Page 5
Chapter 2: Configuration
Device Server Configuration
Before configuring the device server, you must assign it an IP address as described below.
After it has an IP address, the device server is configured primarily through the web
browser interface. If you are using NativeCOM to access the serial ports, no other
configuration is necessary beyond setting the IP address and potentially the network mask
and gateway.
Setting the IP Address
The factory default configuration for the device server has no IP address. To use the device
server you must assign it an IP address. There are several ways to do this.
DHCP/BOOTP
If the device server does not have an IP address, or if it obtained a temporary one via the
temporary method described below, it will attempt to get one from a DHCP/BOOTP server
on the local network. If an IP address is obtained from a DHCP server, the device server will
also ask the DHCP server for a subnet mask, a default gateway, and a DNS name and server.
NativeCOM
You can also configure your device server’s IP address using NativeCOM. NativeCOM is a
Windows software package provided free of charge by Systech. The NativeCOM
Networked COM ports software makes remote serial communication ports (e.g. EIA-
232/485/422 ports on the device server) available to Windows programs as local COM
ports. Applications from a PC running Microsoft Windows 95, Windows 98, Windows NT,
Windows 2000 or Windows XP can access and use the remote serial ports. For further
information on configuring and using Networked COM ports and assigning an IP address to
your device server, see the NativeCOM manual. The NativeCOM software and manual are
available on the CD you received with your device server and from the Systech web site
(www.systech.com).
You can use the NativeCOM Configuration Utility, NativeCOM Port Server Utility, or
NCCTool to assign an IP address to your device server. Once you have done this,
DHCP/BOOTP is disabled. The NativeCOM Configuration Utility and the Port Server

Page 6
Utility always use the default subnet mask for the given IP address class. If you are
subnetting your network, the NCCTool allows you to override the default subnet mask.
Assigning a Temporary IP Address via the Network
If your device server has booted without an IP address, you can assign it a temporary IP
address using another TCP/IP system on your network. All TCP/IP systems include a
standard utility called “ARP” that can be used to assign this IP address to the device server.
The ARP command allows you to manually associate your device server’s hardware
Ethernet address (the “MAC address”) with an IP address on your network. On most Unix
and Windows systems this command looks like this:
arp-s<IP><Ethernetaddress>
<IP> is the IP address you want to assign to the device server and <Ethernet address> is the
unique Ethernet hardware address that is printed on the bottom of the device server (e.g.
“00:80:44:xx:xx:xx”). Note that under Windows, this address should be specified as “00-80-
44-xx-xx-xx” (dashes in between instead of ":" as on the label).
After you have established this ARP mapping, use ping, telnet, or a web browser to contact
the temporary IP address. The device server will see the network packets destined for its
hardware address and temporarily adopt the destination IP address from the packets. The
device server will always use the default netmask for the IP address’s class (see IP Netmask
for more information).
WARNINGS:
1. This method only temporarilyassigns an IP address. The device server will lose this
IP address when it reboots. After you have set the temporary address, you should
use a web browser to access the
2. page and permanently set the IP address.
3. This method only works if the device server does not already have an IP address.
Once the device server obtains an IP address from any other source, this method will
no longer work. To re-enable this method, you must clear out the device server’s IP
address and reboot it.
After you have permanently set the IP address on the device server, it is a good idea to
remove the permanent ARP entry that you previously added to your system. To do this,
execute the following command:
arp-d<IP>
Removing the ARP entry will not affect your ability to communicate with the device in any
way.

Page 7
How to Use the Serial Ports
The device server serial port(s) can be used in several different ways:
•As Windows COM ports via NativeCOM
•As network printer ports via LPR/LPD
•They can initiate TCP/IP network connections to remote hosts (outgoing
connections) optionally using SSL security
•They can accept TCP/IP network connections from remote hosts (incoming
connections)
•They can simulate a dial-up modem connection over TCP/IP (via Modem
Emulation) also optionally using SSL security
The following sections describe each of these configurations in more detail.
If you will only be accessing the serial ports via NativeCOM, no further configuration is
necessary on the device server (unless you need to change the serial port electrical
interfaces). Otherwise, you will need to configure the desired service and set up the proper
serial parameters for your device (the device server serial ports default to 9600 baud, 8 data
bits, no parity, 1 stop bit, and no flow control).
For more information on configuring the serial settings, see the section entitled Serial
Settings.
Configuring NativeCOM Ports for Windows
The device server is pre-configured to work with NativeCOM. To use NativeCOM, select
the device server from the configuration utility and create a COM port as described in the
NativeCOM manual. NativeCOM controls the serial port settings from the host.
NOTE: NativeCOM overrides all the serial parameters set via the web browser, with the
exception of the “Require DCD” and “Electrical Interface” settings. NativeCOM requires
that the “Require DCD” setting be set to “no”, which is the default setting. If you change
this parameter, be sure to reset it for use with NativeCOM.
For more information on configuring NativeCOM ports, please see the NativeCOM
documentation.
Configuring Printers (via LPR/LPD)
All Windows and Unix systems support network-based printing via the LPD (or LPR)
protocol. Although you can also use NativeCOM or Systech RTN to indirectly set up a
network printer, it is usually preferable to use the LPD protocol because it is a simpler and
more efficient way to print. It is also easier to share a printer among multiple hosts when
using the LPD protocol.

Page 8
When configuring an LPD printer, you must provide two pieces of information to the host:
the IP address of the device server and the name of the LPD print queue. The name of the
print queue for serial port 1 should usually be port1 (or portN for serial port N). If you are
printing simple text and want to enable extra character formatting for carriage-returns and
new-lines, use fport1(or fportNfor port N).
Before configuring your host system to use LPD, be sure to configure the correct serial
parameters on the device server (see the section on Serial Settings). All ports are
automatically accessible via LPR on port 515.
To configure a printer under Windows, follow the instructions for adding an “LPR port” in
the Windows Add Printer documentation. Although this process varies depending on
which version of Windows you have, in general you must:
1. Make sure that you have installed LPR/LPD printer support
2. Select Add Printer
3. Choose to add a Local Printer
4. Create a new LPR Port
5. Specify the IP address of the device server
6. Specify the name of the print queue on the device server
To configure a printer under Unix, follow the instructions for your Unix host.
Configuring Outgoing Network Connections
The device server can be configured to initiate TCP connections to remote hosts. This
configuration can be configured for both telnet- and raw-mode protocols (with or without
SSL security). It is generally used when the device server must initiate the network
connection to the remote host.
This option can provide telnet logins for terminals attached to the device server, or it can
establish raw data paths for other serial devices. To configure a port for outgoing TCP
network connections:
1. Configure the correct serial parameters on the serial port (see Serial Settings)
2. Configure the desired TCP session parameters (see Port Services)
Configuring Incoming Network Connections via Telnet Server
The device server is pre-configured to accept incoming TCP connections from Systech RTN
for Unix or other TCP socket-based applications. Each Systech serial port accepts incoming
TCP connections on two TCP ports: an 8000-series port (for raw data), and a 9000-series port
(for telnet data).
The 8000-series port (8001 for port 1, or 800N for port N) is a raw data path that passes all
data back and forth between the network and the serial device without further processing. It

Page 9
should be used by applications that support simple TCP connections and do not implement
the telnet protocol. There is no protocol involved beyond TCP/IP.
The 9000-series port (9001 for port 1, or 900N for port N) implements the telnet protocol and
supports the following telnet options: SUPPRESS GOAHEAD, BINARY, ECHO, COM-
PORT-OPTION and TIMING MARK. It should be used by the Systech RTN utility, and by
other applications that support telnet.
Once you configure the serial parameters via the web browser, the port is ready for use by
RTN or your custom application (see Serial Settings). For more information on configuring
RTN, see the Systech RTN documentation.
Configuring Modem Emulation
The device server can be configured to allow legacy devices that interact with a Hayes-
compatible modem emulation interface to communicate over a TCP/IP network instead of a
phone line. When modem emulation is enabled, the device server will respond to AT
commands generated by the attached device. After receiving the dial command, the device
server will make a TCP connection to the specified host. The device server will also accept
incoming TCP/IP connections and generate the appropriate response codes. As with
incoming network connections, each Systech serial port accepts incoming TCP connections
on two TCP ports: an 8000-series port (for raw data), and a 9000-series port (for telnet data).
To enable modem emulation:
1. Configure the correct serial parameters on the serial port (see Serial Settings)
2. Enable modem emulation and configure the desired outgoing connection parameters
(see Port Services)
Once modem emulation is enabled, verify correct operation by connecting a terminal to the
appropriate serial port and issuing an 'AT' command. If the device server returns the 'OK'
result code, modem emulation is now functioning properly. You may now establish an
outgoing connection with the 'ATD' command (see Phone Numbers for more information
on IP address formats). A phone number translation table is also available to convert phone
numbers to IP Addresses or Hostnames.

Page 10
Configuration via the Web Browser Interface
Once the device server has an IP address, you can use a web browser to monitor and
configure it. Simply specify the IP address of the device server as the address or URL in
your browser and you will see a web page that is similar to the following:

Page 11
Select the section you wish to access from the menu of links on the left side. The following
pages discuss each of these sections.
Serial Settings
The Serial Settingspage allows you to specify the baud rate, character size, parity, stop bits,
and flow control behavior for each serial port:
NOTE: NativeCOM, (or any RFC-2217 Telnet client with COM-PORT-OPTION
support) overrides the baud rate, size, parity, stop bits and flow control parameters.
The default port settings are as shown above.
Enabling flow control enables it on both input and output.
The inactivity timeout shuts down the service on the port if there is no input or output in the
specified timeout period.

Page 12
Port Services
By default, all ports are configured to accept incoming TCP connections from TCP/telnet
clients and no outgoing service is configured. You may configure the ports to initiate
outgoing raw TCP or telnet connections to remote servers. In addition, the modem
emulation feature may be enabled to allow a serial port to mimic a modem interface.
For incoming connections, the ports are numbered as follows:
Port
Incoming
Telnet Port
Raw TCP
Port
Port1 9001 8001
Port2 9002 8002
Port3 9003 8003
Port4 9004 8004
When using the modem service on a port, the phone number will be translated to a
host/port pair then a TCP connection will be established to the remote host.
When using outgoing connections on a port, the settings configured on the Serial Settings
page will be applied to the port, and a TCP connection will be established to the remote host.
If Require carrier/Generate hangups is set, the service will wait for the presence of the DCD
modem signal before connecting.
Once connected, data received on the port is sent to the remote server over the network
connection and data received on the network connection is sent out the port.
The following screen shot represents most of the options available for configuration.
Depending on the Service Type you have selected, not all of these options will be displayed.

Page 13

Page 14
Service Types
No Outgoing Service
Selecting this option disables outgoing port services on the specified port. Incoming
connections are still allowed. All port services options will reset to defaults.
Modem Service
Selecting this option will enable modem emulation on both the incoming and outgoing
network connections. See Modem Emulation for details on commands and responses. The
target peer (specified in the Phone Number Translation table and configured in the Protocol
Settings page) determines the type of outgoing connection that will be made.
When Modem Service is selected, you may also configure the Source TCP Port(see below)
and enable or disable automatically detecting the serial baud rate.
The Modem Emulation service has the ability to automatically detect when the baud rate of
the attached device is different from the one configured on the serial port. In many cases, it
is possible to guess the speed of the attached device and to automatically switch the serial
port to match that speed.
The downside of this functionality is that it is not always 100% reliable, and in some
instances can cause inappropriate baud rate changes to be made that will cause
communications to break down. In general, you should only enable this option if your
application uses multiple baud rates and requires autobauding support. Otherwise, it is best
to disable it.

Page 15
Outgoing Network Connection
Selecting this option enables an outgoing connection to the specified host. The Network
Connection Options(below) identify the host.
Outgoing Telnet Connection
Selecting this option enables an outgoing telnet connection to the specified host. The
Network Connection Optionsidentify the host and the Telnet Options(below) configure
the specific type of telnet connection.
Network Connection Options
Destination Hostname/IP Address
Specify the IP address or Host name of the remote host in the Destination IP Addressfield.
Destination TCP Port
Specify the destination TCP port. The default port for telnet servers is 23, but it is usually
different for other types of servers.
Source TCP Port
In most cases, the value used for the source port is arbitrary and you can leave this field set
to 0 for "any". However, if your server or firewall has specific requirements you may specify
an explicit source port number in the Source TCP Portfield. If this port is not available
when the TCP service starts up, an error will occur and the TCP service will reset and try
again.
Require carrier/Generate hangups
If you have configured a serial port with an outgoing service, you may want to delay the
TCP connection establishment until an attached terminal is powered up or an attached dial-
in modem has received a call. In this case, select the Require carrier/Generate hangups
option. The TCP session will not begin until the device server senses the presence of DTR
(in DCE mode) or DCD (in DTE mode) on the port and it will close the TCP session if
DTR/DCD is lost.
Telnet clients usually do not want the operation of the port to be affected by the presence,
absence, or loss of modem signals. You probably do not want this option selected for those
applications.
Restart Delay
The Restart Delay keeps the TCP service from constantly retrying if the remote host
becomes unavailable, or in the event of network errors or other unexpected situations.
When the TCP session ends, it will pause for the number of seconds specified by the Restart
Delay. The default value (and minimum value) for the Restart Delayis 1 second.

Page 16
Wait for Keyboard Hit
You may configure the TCP connection to wait for a “keyboard hit” before starting the TCP
session. Enabling this mode will display a message on the serial port (after DCD is present if
DCD is required to use the port) asking the user to type a character to begin the TCP session.
Telnet Options
The following options apply only if an Outgoing Telnet Connection is configured.
Telnet Mode
The TCP service can connect to a server using the telnet protocol in either Binary mode (8-
bit) or Human mode (7 bit, performs line and character processing for terminals). The telnet
client will negotiate telnet parameters with the remote telnet server. The parameters that it
will request are as follows:
•Binary mode: DO BINARY, WILL BINARY
•Human mode: DO SUPPRESS GOAHEAD, WILL SUPPRESS GOAHEAD
The device server also supports the following telnet modes if negotiated by the remote telnet
server: ECHO, COM-PORT-OPTION, TERMINAL-TYPE, and TIMING MARK. (Note that
the device server does not support local echo. However, it will accept a WILL ECHO
request for remote echoing and will respond with DO ECHO.)
Terminal Type
If the remote host requests the DO-TERMINAL-TYPE telnet option, and the Terminal Type
field is configured, the device server will respond with this value. This field is useful when
you are connecting serial terminals to the device server and the remote host needs to know
how to format output to the terminal. Otherwise, you can leave this blank.
Quiet Mode
By default, the telnet session will display various status messages as it makes, loses, or
breaks connections to the remote server. Selecting Quiet Modewill suppress these
messages. This is useful when using serial devices that may be confused by these status
messages.
Telnet Escape Character
When the telnet client is in the 7-bit “Telnet mode”, it parses serial input for a special escape
character. The default escape character is “CTRL-]” (or ASCII 29). If it sees this character, it
breaks into the telnet command mode and displays a command prompt that allows the user
to execute some telnet session commands. You may specify a different character (as decimal
ASCII) to use as the Telnet Escape Character, or specify -1 to disable this feature entirely.

Page 17
Phone Number Translation
This table can be used to translate phone numbers into IP addresses or Hostnames. If an
attached device dials one of the specified telephone numbers, the corresponding IP address
and port are used to make the TCP connection. Note that all non-numeric characters except
the “,” (comma) in the phone number are ignored.
When modem emulation is enabled, detect the phone number from ATD commands.
Although the IP address of the remote host can be embedded directly into the ATD
command, certain devices can't always be easily configured to do this.
The Default Translation entry is used if the dialed phone number is not found in the list.
(The dial backup number is not used in the NDS product.)
The phone number table has a number of features to ease initial configuration. When an
attached device dials a number that is not in the table, the device server creates a dummy
entry in the table. This entry will consist of just the phone number. Until you fill in the
remainder of the entry (IP Address/Hostname and Port) and save it, this entry will not be
used.
Once you have created and saved an entry in the table, a link to the associated entry on the
Protocol Settings page appears on the right. If the protocol is not yet defined, this link,
“Define protocol”, will create a new entry on the Protocol Settings page, otherwise the link
will be “Edit protocol”.

Page 18
The translation table screen allows you to add up to 5 new entries at a time. A total of 64
entries may be configured including the default entry.
In the example above, if the attached device dials 18005551212, the port will be connected to
the host at 192.168.1.100 on TCP port 5004. This host is not yet defined, so it will use the
default TCP protocol. If the attached device dials any other number, the port will be
connected to host.testloc.com:5003, whose protocol is defined. And the terminal has actually
dialed 555-1212, generating an automatic, but not yet saved, entry.