User Guide PortServer TS 8/16 92000307_F
Digi International Inc. 2003. Digi, Digi International, the Digi logo, the Digi Connectware logo, the Making Device Networking Easy logo, Digi One, PortServer, and RealPort are trademarks or registered trademarks of Digi International, Inc. in the United States and other countries worldwide. All other trademarks are the property of their respective owners.
Ta b l e o f C o n t e n t s Chapter 1 Introduction Setup Overview ..................................................................................... 7 About Entering Commands on the Command Line ............................... 8 Supported Devices ................................................................................ 8 About This Guide................................................................................... 8 Other Documents in the Library..............................................
Chapter 6 Configuring Ports for Terminals and Computers Configuring Ports for Terminals: Web Interface .................................. 27 Commands for Configuring Ports for Terminals .................................. 27 Port Defaults........................................................................................ 27 Related Information ............................................................................. 27 About Computer Connections .......................................................
Chapter 13 Configuring SNMP About SNMP and the device server Agent .......................................... 57 Configuration Procedure: Web Interface .............................................58 Chapter 14 Configuring Users About Configuring Users ..................................................................... 59 Configuration Methods ........................................................................ 59 Common User Features ...................................................................
Verifying the RealPort Process: HP-UX .............................................. 81 Verifying the RealPort Process: Linux ................................................. 81 Verifying the RealPort Daemon: SCO ................................................. 81 Verifying the RealPort Process: Solaris............................................... 82 Verifying the RealPort Service: Windows NT ...................................... 82 Verifying the RealPort Service: Windows 2000 .........................
Introduction Chapter 1 Setup Overview This section provides an overview of the setup process. Step A: Plan Before beginning setup, consider the following: • How to assign an IP address to the Digi device’s Ethernet interface, which can be accomplished in a number of ways. See "Configuring the IP Address" on page 11. • How to configure serial ports. A key consideration is whether to use RealPort.
Step F: Configure Other Features as Required See the following for information on setting up other features: • "Configuring PPP" on page 29 • "Configuring Autoconnection" on page 35 • "Configuring IP Routing" on page 41 • "Configuring Security Features" on page 47 • "Configuring DNS" on page 55 About Entering Commands on the Command Line If you use the command line, you will find the commands needed within each chapter.
Digi One/PortServer TS Command Reference This online manual, available on the Access Resource CD, provides complete information on commands. RealPort Setup Guides These online manuals provide information on setting up servers for RealPort software. Digi Port Authority - Remote Device Monitor Setup Guide This online manual provides information on installing and using Digi Port Authority - Remote software.
Configuration Prerequisites Accessing the Command Line from a Locally-Connected Terminal Use this procedure to access the command line and the configuration from a terminal connected to one of the device server’s serial ports. 1. Connect a terminal or PC to a serial port on the device server. For a Windows HyperTerminal connection, use the cable that came in the package. 2. Configure the parameters of the terminal or terminal emulation software to work with the Digi serial port.
Configuring the IP Address Chapter 2 Options for Configuring the IP Address and Mask The device server IP address can be configured using the following methods: • With Digi Port Authority-Remote, a Digi utility • By updating the ARP table on a server and then pinging the Digi device (called ARP-Ping) • From the command line using the set config command (Configuring the Ethernet Interface from the Command Line) • Using a RARP server • Using a DHCP server The IP address and mask can also be changed using t
• • • • method, however, does not work for the initial IP address configuration." on page 11. That your Digi device is connected to the Ethernet network. That the Digi device has DHCP client turned on. This is the default setting and it will be on unless it was turned off. That you do not have a DHCP server to serve IP address. If you do, use the DHCP procedure. See "Configuring an IP Address using DHCP and RARP" on page 14. That you have installed Digi Port Authority-Remote version 2.01.11 or later.
3. Manually update the server’s ARP table using the Digi device’s MAC address and the IP address you want assigned to the Digi device. The following is an example of how this is done on a Windows NT 4.0 system: arp -s 143.191.2.1 00-00-9d-22-23-60 4. Ping the Digi device using the IP address just assigned. The following is an example: ping 143.191.2.1 The ping will probably time out before there is a response from the Digi device. 5. Wait a few seconds and then ping the Digi device again.
the boot command reboot the Digi device, which is required for the address change to take affect. set config ip=192.150.150.10 submask=255.255.255.0 dhcp=off set config gateway=192.150.150.11 boot action=reset Configuring an IP Address using DHCP and RARP About DHCP and RARP When the device server boots, it transmits a DHCP request and a RARP request. This continues until an address is assigned. Procedure To use RARP or DHCP follow these steps: 1. Set up an entry for an address on a DHCP or RARP server.
Chapter 3 Configuring Ports for RealPort About RealPort This section provides a brief introduction to RealPort. What is RealPort? RealPort is a feature that allows network-based host systems to use the ports of the device server as though they were the host system’s own ports, appearing and behaving as local ports to the network-based host. RealPort Advantages RealPort provides the following advantages: • It expands the number of ports available to the host system.
3. From the main menu, select Setup Wizards > RealPort. 4. To complete configuration, choose Next and then follow the prompts. 5. To return to the main Ports menu, choose Ports from the Menu again.
6. To complete RealPort setup, install and configure the RealPort driver. See the appropriate RealPort setup guide on the Access Resource CD. To configure Secure RealPort, see set config securerealport in Digi One/ PortServer TS Command Reference.
Chapter 3 Configuring Ports for RealPort
Configuring Ports for Printers Chapter 4 Configuration Considerations You should be aware of the following considerations if you intend to configure device server to handle printers. Using RealPort RealPort, a feature that allows network-based host systems to use the ports of the device server as though they were the host system’s own ports, is an easy and efficient way for printers to use device server ports. For information on this option, see "Configuring Ports for RealPort" on page 15.
Examples String Result ascii_1 Prints to port 1 and translates CR to CR/LF. ascii_8_f Prints to port 8, translates CR to CR/LF and prints a form feed at the end of the job. raw_1_d Prints to port 1 with no translation and appends a Ctrl-d to the end of the print job. Configuring Ports for Printers: Web Interface 1. Access the web interface by entering the device server IP address in a browser’s URL window. 2. Log on to the device server as root. The default password is dbps. 3.
For this connection type... Identify the port by specifying... 2000 plus the number of the port. Telnet Example: 2002 for port 2. 2100 plus the number of the port. Raw Example: 2102 for port 2. User Command Example 1 In this example, a user from the host server, specifies a standard Telnet connection on port 2 of a device server using IP address 199.250.38.15. cat myfile | telnet 199.250.38.
set altip group=2 ip=199.250.38.17 The following example displays a file on port 2 whose unique IP address is 199.250.38.17: cat myfile | telnet 199.250.38.
Configuring Ports for Modems Chapter 5 Tips on Configuring A Modem Here are some tips on configuring modems to work with device server: • Configure the modem so that DCD goes high when it receives an incoming connection request. • Configure the modem to answer an incoming call only when DTR is high, and to drop the line when DTR goes low. • For bidirectional connections, it is advisable to configure the nonvolatile parameters in the modem for incoming calls.
Commands for Configuring Ports for Modem Connections For configuring ports for modem connections use the following commands found in the Digi One/PortServer TS Command Reference : • set ports • set line • set flow Related Information • • • • • If you intend to run PPP traffic over this modem connection, see "Configuring PPP" on page 29.
available hunt group port.
Chapter 5 Configuring Ports for Modems
Configuring Ports for Te r m i n a l s a n d C o m p u t e r s Chapter 6 Configuring Ports for Terminals: Web Interface Use this procedure to configure a port from the web interface. 1. Access the web interface by entering the device server IP address in a browser’s URL window. 2. Log on to the device server as root. The default password is dbps. 3. From the main menu, choose Configure > Ports. 4. Choose the port from the port column. 5. Ensure that the Device type is set to Terminal. 6.
device. About Computer Connections Configuring computer connections is very similar to configuring terminal connections, which is discussed on page 27. Consequently, this section simply discusses the differences between these connection types.
Configuring PPP Chapter 7 Configuring Inbound PPP Connections: Command Line Use this section to configure simple inbound PPP connections from the command line. For information on fine-tuning PPP connections, see the set user command in the Digi One/PortServer TS Command Reference. Note: CHAP authentication works between two Digi devices. CHAP will be negotiated to PAP for all other connections Procedure 1.
set user name=pppin protocol=ppp netservice=on defaultaccess=netservice 5. To configure an IP address for the remote PPP user, enter the following command: set user name=name ipaddr=ip-address where • name is the user’s name • ip-address is one of the following: (a) A standard IP address in dotted decimal format. (b) 0.0.0.0, which means the remote user will supply the IP address. (c) ippool, which means that the user will be assigned an IP address from an IP address pool.
Configuring Outbound PPP Connections: Command Line This section describes how to configure outbound PPP connections. Use it to configure outbound only connections or to configure the outbound portion of bidirectional connections. Note: CHAP authentication works between two Digi devices. CHAP will be negotiated to PAP for all other connections Procedure 1.
• dialer=name is the name of a dialer script, either the Digi-supplied script or a user-created one 6. To create a PPP user, enter the following command: set user name=name protocol=ppp where name is the name of the PPP user Example set user name=pppout protocol=ppp 7.
set line range=3 baud=115000 set user name=pppout protocol=ppp set user name=pppout dialout=on outgoing=on device=gendialer set user name=pppout localipadr=0.0.0.
set user Field passpacket logpacket Description Causes a packet to be passed or blocked Filter causes incoming packets from an IP address to be accepted and packets from all other IP addresses to be blocked Causes the Digi device to send a message to the log file Filter that notifies the log anytime an ICMP packet is handled Packet Type 34 Example Type Identifier Echo reply 0 Destination unreachable 3 Source quench 4 Redirect 5 Echo request 8 Time exceeded for a datagram 11 Parameter pr
Chapter 8 Configuring Autoconnection About Autoconnection The autoconnection feature allows you to configure a user to access the device server and then be automatically connected to a host on the LAN. You can implement autoconnection in the following ways: • By port where all port users are automatically connected to the same host. The device server is completely transparent to them.
7. Configure the user. Be sure to specify the following: (1) Default Access: Autoconnect (2) Enable Autoconnect (3) The IP address that will be the destination for the autoconnect user (4) A Destination TCP port number, which determines the type of connection for this user (such as 23 for Telnet). 8. Choose Submit. 9. To return to the main User menu, choose User from the Menu again.
8. Specify a TCP port to use for this connection. If this is a connection to a serial port on another Digi device and you have not changed the base socket service, use the following conventions to specify a TCP port number: For This Type of Connection... Specify ... Example Telnet 2000 + port number To specify port 1, use 2001 Raw connection 2100 + port number To specify port 2, use 2102 9. If you want the autoconnection to launch immediately, choose Force DCD. 10. Choose Binary Mode. 11.
5. Choose UDP serial... at the bottom of the page. The UDP Serial Configuration page is displayed. 6. Fill in the requested information and choose Add destination at the bottom of the page. See the Help section for additional information on the settings. 7. Scroll to the bottom of the page. Under Description, choose upddest1. 8. Enter the requested information and choose Submit. You can change the Description as desired.
4. From the Port configuration screen, set the Device type to Printer, adjust other serial port communication parameters as required by the connected device, and then choose Submit.
Chapter 8 Configuring Autoconnection
Configuring IP Routing Chapter 9 Configuring Static Routes This section describes how to configure device server for static routes. Related Information See the set route command in the Digi One/PortServer TS Command Reference.
• • • • The address on the net field is IP address of a specific device, not a subnetwork address The wan name is the name of a PPP user. The metric field indicates that packets to this subnet will pass through two routers The gateway field indicates that all packets using this route are to be forwarded to the device at IP address 191.21.21.2. set route net=199.21.33.44 mask=255.255.255.255 metric=2 wannname=ppp1 gateway=199.21.21.
192.150.75.0 Router 187.100.46.9 Digi Device PPP set forwarding state=active poisonreverse=on splithorizon=on set user name=link1...netrouting=off Configuring Proxy ARP This section describes how to configure device server for Proxy ARP. Related Information See the set forwarding command in the Digi One/PortServer TS Command Reference.
Chapter 9 Configuring IP Routing
Chapter 10 Configuring the Digi Device for IA (Industrial Automation) About Modbus Modbus is a protocol that defines how devices in an industrial automation (IA) environment communicate. It specifies that a controlling unit, called a master, manages one or more units, called slaves. The protocol specifies that only the master may initiate communication. Slaves may only respond.
• If you configure a port for a master and the slaves are located on the network, TCP sockets, UDP sockets, and Modbus/TCP are all supported. Use the protocol required by the master. Configuring the User-Defined Protocol Digi One\PortServer TS 2/4 MEI devices support what Digi calls the “userdefined” protocol, which is any IA serial-port protocol with the following attributes: • All message packets are bounded by fixed header and trailer strings. • Each protocol request is followed by a single response.
Chapter 11 Configuring Security Features Controlling Access to the Configuration Controlling access of device server restricts access to the configuration by defining the following types of users: • The root user, who has unlimited access to device server commands. He or she can view any configuration table and change any configuration parameter. The root is identified by the user name root and must supply a password to be authenticated. The default root password is dbps.
supply a set logins command that specifies the following: set logins range=range login=off passwd=off Example: set logins range=1-2 login=off passwd=off Procedure for Changing a User’s Access Requirements To configure a user so that he or she does not have to specify a password when accessing an inbound port, supply a set user command that specifies the following: set user name=name password=off where name is a name to identify the user Example: set user name=user1 password=off Controlling Access to Outb
device server but then be automatically connected to a host on the LAN. You can implement autoconnection in the following ways: • By port where all port users are automatically connected to the same host. The device server is completely transparent to them. • By user where a user is required to login and may be required to supply a password, but once the user is authenticated, an automatic connection to a hosts made. For information on configuring autoconnection, see "Configuring Autoconnection" on page 35.
client implementation.
• • • • • A user logs into device server. device server collects login information and then checks to see if the user is in the local database of users. If the user is in the local database, device server handles authentication. If the user is not in the local database, device server submits an authentication request to the RADIUS server. The RADUIS server does one of the following: — If the user is validated, it passes this information to other devices and the user is permitted access.
Issuing User Passwords This section discusses how to issue user passwords. Related Information See the newpass and set user commands in the Digi One/PortServer TS Command Reference. Starting Point This procedure assumes that you have signed on as root and already configured the user to whom you will be issuing a password. Procedure 1. Issue a newpass command that identifies the user (on the name field) to whom this password will be issued. 2.
• key is the name of a file that contains the DSA public key. If your host’s implementation requires a complete path to the file, specify the path here as well. Example: set user name=secure loadkey=143.191.2.34:ssh-file Making Reverse SSH Connections to Ports The convention used to identify a port for a reverse SSH connection to a Digi device is to use 2500 + the port number. See the examples that follow for more information. Note: Only PortServer TS 8/16 supports reverse SSH version 2 server.
• Secure, which means that SSH is the only service available to inbound users • High, which means that SSH, HTTP, HTTPS, SNMP, and RealPort services are available to inbound users • Normal, which means all services are available • Custom, which means you can select services to turn off. The default service level is normal, which means that all services are available. Procedure Use this topic for information on using the web interface to turn services off. 1.
Configuring DNS Chapter 12 About the Domain Name System This section discusses key concepts of the domain name system. Purpose of DNS The domain name system maps domain names to information associated with these names, such as IP addresses.
periods: mn07.amalgamated.com In this example, mn07 is part of the higher-level domain called amalgamated.com. Configuration Procedures Procedure for Using a Name Server To configure a DNS server, enter the following command: set config domain=domain myname=name dns=ip-address where • domain is the domain in which the device server will reside • name is a DNS name for device server • ip-address is the IP address of a name server Example: set config domain=digi.com myname=poe dns=204.221.1.
Configuring SNMP Chapter 13 About SNMP and the device server Agent This section introduces SNMP and network management in TCP/IP networks, and it describes the device server agent.
• • • • Read-write for MIB II (RFC 1213), which is an Internet-standard MIB, consisting of managed objects from the systems, interfaces, IP, ICMP, TCP, UDP, transmission, and SNMP group Read-write for the character-stream devices using SMIv2 MIB (RFC 1658) Read-write for the RS-232-like hardware devices MIB (RFC 1659) Read-write for the device server IP Network Control Protocol of the Point-to-Point Protocol MIB (RFC 1473) Message Support The SNMP agent supports the Set, Get, GetNext, and Trap messages
Configuring Users Chapter 14 About Configuring Users Although it is not required, the device server is often configured to accommodate the requirements of particular users.
Default access type Defines the type of access the user is restricted to. Menu, command line, autoconnect, and outgoing and netservice are the types. This feature is configurable from the web interface. defaultaccess Menu access Defines the menu that is to be presented to a user with menu access. This feature is configurable from the web interface. menu Port access Defines the number of outbound ports a user connected over the LAN can access at one time.
Configuring Console Management Chapter 15 About Console Management The device server can be configured to remotely manage network devices, such as routers, switches, power units, and servers, which usually provide EIA-232 serial ports for management. Using the device server and TCP/IP utilities like reverse Telnet and SSH2, network administrators can access consoled serial ports from a single station over the LAN.
device for RADIUS authentication, see the chapter on Configuring RADIUS. See the following section on how to configure SSH for authentication.
Example: SSH2 and Menu Access In this example, a Digi device is configured to use an SSH2 public key, and it presents a menu to the administrator, from which he or she will select a device to manage. Key aspects of this configuration include the following: • Two ports to which the managed devices are connected specify dev=prn, a device type that does not spawn a login from the Digi device. • A menu specifies connect commands, which when selected provide connections to ports 1 and 2 and the managed systems.
a user connects directly to serial port 4 on a PortServer. Reverse telnet uses a socket numbering scheme starting with 2000 plus the port number. telnet 192.1.2.3 2004 A reverse telnet session can be authenticated on a Digi device with a RADIUS server. Note: 64 Ports must be configured for console management before they can be used for reverse telnet or reverse ssh. See "Configuring a Port for Autoconnection: Web Interface" on page 35.
SSH Direct to a Port (Reverse SSH) Reverse ssh is the same as a reverse telnet session except the communication session is encrypted. Reverse ssh uses the socket numbering scheme of 2500 + the port number. In the example below, the user establishes a connection to port 12 on a Digi device. ssh 192.1.2.3 2512 Users on a Linux system should use the following example for reverse ssh. ssh -lroot -p2512 192.1.2.
cific User ID (UID). Access to the port is then restricted to that particular user. 2. Protocol Protocols supported by the device server can be turned off to restrict the ways users can access ports. For example services such as telnet and http can be turned off with SSHv2 being the only method available to access. 3. Source IP Ports can also be restricted by the source IP of the computer wanting access.
4. To configure the power unit, choose Edit Power Unit hyperlink under the power unit you have added. 5. Choose the manufacturer, enter the number of outlets, and set the alarm thresholds. Choose Submit. The power unit is configured. Note: The alarm theshold monitors the electric current on an outlet. It warns the user by sounding an audible warning when a specific amperage level is reached on an outlet.
4. Choose Submit to save your configuration. Configuring Console Groups To assign groups to the power units, do the following: 1. From the menu, choose Configure > Power > and the Outlet you are configuring. The Outlet is listed in the Plugged Into column. 2. A configuration screen appears. In the Console Group field select a group from the pull down menu to assign the group to the Outlet. The Device Name and Plugged Into fields are already filled by the configuration utility. 3.
The Power Management options become accessible only when a Console Group or Device Name have been assigned. 4. Choose Submit to save the configuration. Configuring Port Buffering Note: Port buffering is supported on PortServer TS 2/4 MEI and PortServer TS 8/16 devices only. Serial ports store data or information in what are called buffers. Buffers are helpful to administrators who use them to monitor events on a system.
Chapter 15 Configuring Console Management
Chapter 16 Managing the OS and Configuration Upgrading the Firmware This section describes how to upgrade the firmware, which can be done from the web interface using HTTP or FTP. HTTP or TFTP Upgrade Procedure If your hardware is okay, make sure you are running the latest firmware version available. Check the Digi Support site (http://ftp.digi.com/support/ firmware) for the latest firmware and/or POST updates for your device 1. Download a copy of the firmware file. 2.
• Each line of the file must start with a set command, such as set user or set line. In other words, do not let commands wrap to the next line if your editor supports this function. HTTP Procedure 1. Access the web interface by entering the device server IP address in a browser’s URL window. 2. Log on to the device server as root. The default password is dbps. 3. From the main menu, choose Admin > HTTP CpConf. 4.
3. When the 1-5-1 LED pattern is displayed, release the button. The device boots up. Commands for Resetting the Configuration to Defaults Use the revert command to reset the configuration to factory defaults or the latest version stored in NVRAM. See the Digi One/PortServer TS Command Reference for complete information. Note: You can also use the range field on this command to define a range of ports with the serial, port, line, flow, keys and login options.
Chapter 16 Managing the OS and Configuration
Tr o u b l e s h o o t i n g Chapter 17 Symptom: PortServer TS 8/16 Does Not Boot Introduction Use the information provided in this discussion when PortServer TS 8/16 will not complete the boot cycle. Procedures Things to Try Check for hardware problems. Check for TFTP problems if PortServer TS 8/16 is booting from a TFTP host. See ...
Things to Try See ... See if you can ping the IP address. If you can ping the address, but cannot Telnet to it, you probably have a firewall problem. See the Firewall documentation for more information. "Pinging an IP Address" on page 80 Verify the network cabling. "Verifying the Network Cabling" on page 80 If you cannot resolve the problem, contact Digi.
PortServer TS 8/16. 1. Connect a terminal to a PortServer TS 8/16 port. 2. If the port is still using the default configuration, configure the terminal to use the following settings (Otherwise, configure the terminal to match the port configuration): • VT-100 emulation • 9600 baud • 8-bit characters • 1 stop bit • No parity 3. Reboot the PortServer TS 8/16. 4. When the front panel LEDs are all lighted, hold the Reset button and press the v key.
3. Reboot the PortServer TS 8/16 and press v when the LEDs begin to blink. POST output appears on the terminal screen. Verifying TFTP on a UNIX System Use this procedure to verify that TFTP is working correctly on your UNIX host. Note: This procedure, which uses a TFTP transfer of the Digi Device’s boot image between two UNIX hosts, enables you to compare the size of the boot image before and after it is transferred, enabling you to determine if TFTP is working properly. 1.
chmod 666 /tftpboot/ftp_file_name • Verify that the inetd.conf file is properly configured for tftp by displaying the file /etc/inetd.conf. An entry similar to this should be uncommented: tftp dgram udp something • • where something will vary with each operating system. For controlled TFTP access, make sure that the file /etc/tftpaccess.ctl exists and verify that it only allows access to public directories. If this file is not present, tftp will allow full access.
• 8-bit characters • 1 stop bit • No parity 3. Press Enter to get a logon prompt from the PortServer TS 8/16. 4. Log on to the PortServer TS 8/16. 5. Use the set config command to verify the PortServer TS 8/16 IP address. Checking for Duplicate IP Addresses Use this procedure to ensure that the PortServer TS 8/16 and another device are not using the same IP address. 1. From another system on the network, use the ping command to determine if the IP address is in use.
150 meters at higher speeds. Consult an Ethernet cable manufacturer for a recommended cable for your configuration. 2. Verify your Ethernet hub. See your Ethernet hub manual. Verifying the RealPort Process: AIX 1. Type the following: lsdev -Cc nts 2. If the sa devices are not in an available state, type the following from the AIX prompt: mkdev -1 sa# cfgmgr where # is the number of the Digi Device. Verifying the RealPort Process: HP-UX 1.
root 2254 1 0 Dec 13 ? 0:03/etc/necd -d /dev/cts0 -n root 2049 1 0 Dec 13 ? 0:01/etc/necd -d /dev/cts0 -n 2. If you do not see this information, restart the daemon by doing the following: a. Modify the /etc/rc2.d/S86ncxa file with the appropriate IP addresses. b. Reboot the server. Verifying the RealPort Process: Solaris Use this topic for information on verifying that the RealPort process is running on a Solaris system. 1. Type the following command: ps -ef|grep ncxd 2.
RealPort • Specify set ports dev=rp to define a device type. • • Configure serial line attributes on the RealPort host. Configure flow control on the RealPort host. Printer • For most printers, specify set ports dev=prn • • Use the set line command to configure serial line attributes that are consistent with peripheral requirements. Use the set flow command to configure flow control attributes that are consistent with peripheral requirements.
• Use the set flow command to configure flow control attributes that are consistent with peripheral requirements. Digi Contact Information Digi International 11001 Bren Road East Minnetonka, MN 55343 U.S.A Customer Service and Support World Wide Web: 84 http://support.digi.com email support@digi.com Telephone (U.S.
Specifications Chapter 18 Specifications LEDs LED Power Color Green (labeled PWR) Radio Signal Strength Status (Link) ACT Yellow State On Power detected Steady blinking Waiting for an IP address.
Device Server EIA 232/422/485 Switch Settings Switch Settings Function 1 2 3 4 Up Down Down Down EIA-422/485 Full-duplex Down Up Down EIA-485 half-duplex Down Down Up If up, termination.
Standard Models Specifications Power Requirements (Standard Models) 2-contact barrel connector +9 to +30 VDC 525 mA (max) external power supply RJ-45 Powered Ethernet +30 to +60 VDC 100 mA (max) Environmental Ambient temperature 0 to 50° Celsius 32 to 131° Fahrenheit Relative humidity 5% to 90% non-condensing Altitude 0 to 12,000 feet 0 to 3,658 meters Mechanical Chapter 18 Specifications Length 13.33 centimeters 5.25 inches Width 8.25 centimeters 3.25 inches Height 1.90 centimeters .
Specifications for Extended Temperature Models Power Requirements (Extended Temperature Models) 2-contact barrel connector +9 to +30 VDC 525 mA (max) external power supply Environmental Ambient temperature -35 to 70 °Celsius -31 to 158 °Fahrenheit Relative humidity 5% to 90% non-condensing Altitude 0 to 12,000 feet 0 to 3,658 meters Mechanical Length 13.33 centimeters 5.25 inches Width 8.25 centimeters 3.25 inches Height 1.90 centimeters .75 inches Weight .
• Consult the dealer or an experienced radio/TV technician for help. Labeling Requirements (FCC 15.19) This device complies with Part 15 of FCC rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Modifications (FCC 15.
Chapter 18 Specifications
Index C command line configuring access to 48 computer connections configuring 28 configuration remote 71 D DB9 pinouts 86 DNS configuring a host file 56 introduction to 55 Domain Name System introduction to 55 domain name system configuring a host file 56 E Ethernet interface, configuring 13 configuring 43 R RealPort features 15 remote configuration 71 routing configuring dynamic routes 42 configuring static routes 41 S security configuring access to inbound ports 47 configuring access to outbound por
