Contents:
The information in this section is intended for
system administrators with access to privileged commands and assumes
a knowledge of the TCP/IP protocol and UNIX system administration.
Creating
Startup Configuration Files
A startup configuration file is a set of commands
that the Communications Server downloads from the TCP/IP network and
executes at power-on or when you explicitly download and execute the
file with the EXECUTE command.
If you have several Communications Servers on
your network, you can save time and work by creating configuration file(s)
on a remote host and downloading the file(s) to all or specific Communications
Servers.
There are three types of configuration files:
standard, default, and server-specific.
1. Standard.
Used to set up generic parameters for all your
Communications Servers.
2. Default.
Used if your Communications Server determines
its Internet address from the network instead of locally (i.e., you
have not defined the Internet address locally with the DEFINE INTERNET
ADDRESS command or specified a startup file with the DEFINE SERVER
STARTUPFILE command).
3. Server-specific.
Used to set up configuration information specific
to a single Communications Server.
Creating
a Standard Configuration File
This section explains how to create a standard
configuration file with generic parameters for all your Communications
Servers. For example, you can use a standard configuration file to record
a host table for all Communications Servers. With the host table set
up, you can telnet or rlogin to remote hosts using the host's name-you
don't have to remember its Internet address.
You can create a standard configuration file
from a remote host or from the Communications Server.
Creating
a Standard Configuration File from a Remote Host
To create a standard configuration file from
a remote host:
Step 1.
Log in as root on the remote host where you
want to store the configuration file.
Step 2.
Change to the /tftpboot directory.
Step 3.
Use a text editor, such as vi or ed, to create
a standard configuration file with generic
parameters for all your Communications Servers.
Enter commands the same way you would enter
commands at the Communications Server prompt. Spaces and comments
are accepted. Use a pound sign (#) at the beginning of each line where
you want to set off comments.
The following example shows a standard configuration
file.
# System Administrator and Location of Server
CHANGE SYSTEM CONTACT `F. Gruber'
CHANGE SYSTEM LOCATION `Room 412,
Bldg 101'
# Communications Servers Host Table
CHANGE INTERNET HOST catnip ADDR
132.237.18.55
CHANGE INTERNET HOST netbox ADDR
132.237.6.51
# Communications Servers Gateway
CHANGE INTERNET GATEWAY 132.237.6.1
Step 4.
Proceed with 'Downloading the Configuration
File' later in this chapter to set up your Communications Server to
automatically download the configuration file every time it's powered-on.
Creating
a Standard Configuration File from the Server
If you have just configured a Communications
Server and you can't remember what you typed, or you don't want to retype
all of the configuration commands, you can use the LIST CHANGES command
to list all the changes you made to the Communications Server's permanent
database and redirect that list to a file on a remote host.
To create a standard configuration file from
your Communications Server:
Step 1.
Log in as root to the remote host where you
want to store the configuration file.
Step 2.
Change to the /tftpboot directory.
Step 3.
Create an empty file. This empty file will be
used to capture a list of all the changes you made to the Communications
Server's permanent database. Type:
# touch filename
Where filename is the name of the standard
configuration file you want to create.
Step 4.
Change the file permissions so the file is writeable
by everyone.
Type:
# chmod ugo+w filename
Where filename is the name of the standard
configuration file.
Step 5.
From your Communications Server prompt, in privileged
mode, type:
Local 1>> LIST CHANGES > filename HOST hostname
Where hostname is the name of the remote host
and filename is the name of the file you created in step 3.
Step 6.
Proceed with 'Downloading the Configuration
File' later in this chapter to set up your Communications Server to
automatically download the configuration file every time it's powered-on.
Creating
a Default Configuration File
You can create a default configuration file if
the Communications Server determines its Internet address from the network
instead of locally (i.e., you have not defined the Internet address
locally with the DEFINE INTERNET ADDRESS command or specified a startup
file with the DEFINE SERVER STARTUPFILE command). If the Communications
Server determines its Internet address from the network, the Communications
Server attempts to find and download the default configuration file
from the remote host.
To create a default configuration file:
Step 1.
Follow the procedure detailed in 'Creating a
Standard Configuration File,' except name the default configuration
file after your Communications Server's model number.
For example, if your Communications Server is
model ETS-8, name the default configuration file ETS-8.CFG. If you
have more than one Communications Server model, create a default configuration
file for each model. You can follow the instructions for creating
a standard configuration file from either a remote host or your Communications
Server.
You don't need to perform the last step of
the standard configuration file procedure, which sets up your Communications
Server to automatically download the configuration file every time
it is powered on. If a Communications Server determines its Internet
address from the network, the Communications Server automatically
finds and downloads the default configuration file.
Step 2.
Reboot your Communications Server.
Creating
a Server-Specific Configuration File
A server-specific configuration file is used
if you want to create a special configuration for a specific Communications
Server. For example, if you want to create a host table for all Communications
Servers on a network, but you want only one of those servers to be set
up for printers, use a standard configuration file for the host table
and a server-specific configuration file for the printer configuration
information.
To set up a server-specific configuration file,
create both a standard configuration file and a server-specific file.
The following instructions assume you have already created a standard
configuration file.
If you haven't already created a standard configuration
file, see 'Creating a Standard Configuration File' earlier in this chapter
for detailed instructions. You can follow the instructions for creating
a standard configuration file from either a remote host or the Communications
Server.
Using Web Configuration.
Invoke the Server's setup utility by entering
its IP address in a network-connected web-browser, (i.e. http://123.456.789.001).
When the Setup front page is displayed:
Step 1.
Press the 'Setup' button. Specify a valid
user name and password, if prompted.
Step 2.
Select the 'Server' (general server setup)
hyperlink from the main Setup screen.
Step 3.
Select the 'Startup Configuration Files'
hyperlink from the Setup Server screen.
Step 4.
Specify the configuration file name and
hostname. These define the location of the configuration file.
Step 5.
Press the Configure button when ready.
The input parameters are implemented immediately. The setup program
now confirms that the input has been accepted by displaying the Configuration
Results screen.
Using Command Line Configuration.
To create a server-specific configuration file:
Step 1.
Use a text editor, such as vi or ed, to add
the following special file notation to the last line of your standard
configuration file:
EXECUTE %@ HOST hostname
Where hostname is the name of the remote host
where the configuration files are stored.
When a Communications Server downloads the
standard configuration file from the remote host, the %@ symbols expand
to become the hexadecimal value of that Communications Server's Internet
address. The hexadecimal value of that server's Internet address is
used for the file name of the server-specific configuration file.
When the standard configuration file is run, the special notation
at the end of the file tells the remote host to execute the server-specific
configuration file.
The following example shows a standard configuration
file with a special file notation to execute a server-specific configuration
file.
# System Administrator and Location of Server
CHANGE SYSTEM CONTACT
`D. Middleton'
CHANGE SYSTEM LOCATION
`Room 412, Bldg 101'
# Communications Servers Host Table
CHANGE INTERNET HOST
netbox ADDR 132.237.18.55
CHANGE INTERNET HOST
catnip ADDR 132.237.6.51
# Communications Servers Gateway
CHANGE INTERNET GATEWAY
132.237.6.1
# Execute server-specific configuration files
EXECUTE %@ HOST
catnip
Step 2.
Use a text editor, such as vi or ed, to create
a server-specific configuration file.
(a)Enter parameters
the same way you would enter commands at the Communications Server
prompt. Spaces and comments are accepted. Use a pound sign (#) at
the beginning of each line you want to set off as a comment.
(b)Name the server-specific configuration file
the hexadecimal value of the Internet address of the Communications
Server that will download the file. For example, if the Communications
Server that will download the file has an Internet address of 132.237.6.51,
the server-specific file name would be 84ED0633. Enter only commands
specific to that Communications Server.
The following table lists the decimal numbers
0 through 255 and their hexadecimal equivalents.
Table 4-1 Decimal to Hexadecimal Conversion
The following example shows a server-specific
configuration file.
# Telnet Listener Settings for a Printer:
CHANGE
TELNET LISTENER 2008 PORTS 8 ENABLED
CHANGE
TELNET LISTENER 2008 IDENTIFICATION `HP
Laser
Jet II'
CHANGE
TELNET LISTENER 2008 CONNECTIONS ENABLED
# Port settings for printer:
CHANGE
PORT 8 ACCESS REMOTE
CHANGE
PORT 8 TELNET SERVER NEWLINE FROM
TERMINAL
<LF>
CHANGE
PORT 8 TELNET SERVER NEWLINE FROM HOST
<CRLF>
Downloading
the Configuration File
After you have created a standard configuration
file, specify that the Communications Server download the file. If you
also created a server-specific file, the standard configuration file,
with a special file notation, calls for the server-specific configuration
file.
For a Communications Server to automatically
download the configuration file(s) you created, make sure Trivial File
Transfer Protocol (TFTP) is enabled on the remote host. Then, from each
Communications Server, specify the standard configuration file and remote
host from which the Communications Server will download the standard
configuration file.
Note: TFTP
is a program (in UNIX & Windows NT) that allows the transfer of
files from one machine to another. Refer to your UNIX or NT manual page
for more information.
Step 1.Verify that TFTP is enabled.
(a) Change to the /etc directory.
(b) Open the inetd.conf file.
(c) Search through the inetd.conf file
until you find the tftp entry. (You might have two or more tftp
entries.)
(d) Make sure there is only one tftp
entry enabled (without a pound symbol [#] at the beginning of the
line). The following example shows the tftp -s entry enabled
(-s stands for secure mode).
tftp dgram
udp wait root
/etc/tftpd tftpd -s
# tftp dgram
udp wait root
/etc/tftpd tftpd
Step 2. Test
that TFTP is working properly.
(a) Change to the /tmp directory.
(b) Use TFTP to copy
the standard configuration file to the /tmp directory. Type:
# tftp localhost
Note: This example assumes you have a localhost
entry in your /etc/hosts file for testing purposes. Refer to your
UNIX documentation for more information.
The following prompt appears:
tftp>
Type:
get filename
Where filename is the name of the standard
configuration file you created in the /tftpboot directory.
Then press <Ctrl> D, and type:
# ls
The filename appears in the list of filenames,
which appear on your screen.
Step 3. From
your Communications Server prompt, specify the standard configuration
file you want to download to that server. In privileged mode, type:
Local 1>> CHANGE SERVER STARTUPFILE filename
HOST hostname
Where filename is the name of the standard
configuration file, and hostname is the name or Internet address of
the remote host where the file is stored.
Step 4. Download
the configuration file. To download the configuration file, you can
reboot the Communications Server or load it manually.
To reboot the Communications Server, in privileged
mode, type:
Local 1>> REBOOT
To manually load the configuration file, in
privileged mode type:
Local 1>> EXECUTE filename HOST hostname
Where filename is the name of the standard
configuration file, and hostname is the name or Internet address of
the remote host where the file is stored.
Step 5. Repeat
steps 3 and 4 on each additional Communications Server that you want
to download the configuration file.
