Digi PortServer II, Руководство пользователя

Страница: 84 / 277

Page 64 Basic Configuration 90030500B
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.
If you want to use this method of configuration, a RARP server should be available on
the network. Consult your operating system and network software documentation for
further information. (On many UNIX systems, this information can be found in the
manual entry for
rarpd
).
Note:
If you do not have a RARP server, you can configure most PortServer II
parameters using telnet. However, you must set PortServer II’s IP address
with a local terminal before you can use telnet.
Running RARP on the server
To use RARP to assign IP addresses to PortServer II’s on your network, the RARP
daemon must be running on the network host. The RARP server maintains a database
of mappings between Ethernet (MAC) addresses and protocol (IP) addresses. When a
client such as PortServer II requests an IP address, the RARP daemon accesses the
database and returns the appropriate address.
Note: The example below is for an SCO server; the file names and responses on
your system may differ.
To enable RARP on a server:
1. Ensure that TCP/IP is running on the server.
2. Add each PortServer II on your network to the /etc/hosts file, in the following for-
mat:
# @(#)hosts 1.2 Lachman System V STREAMS TCP source
# SCCS IDENTIFICATION
127.0.0.1 localhost
132.147.144.246 dgii dgii.com
3. Add each PortServer II on your network to the /etc/ethers file, in the following
format:
# @(#)ethers 4.1 Lachman System V STREAMS TCP source
# SCCS IDENTIFICATION
#