TCP/IP Release Document
Software Version 2.1
Part No. 005498
Revision 04
This document describes TCP/IP
software Version 2.1.
The release notes for standard DOMAIN
software and other optional products
are documented in other sets of
release notes and are located in the
system /DOC directory.
APOLLO COMPUTER INC.
330 Billerica Road
Chelmsford, Massachusetts 01824
c 1986 Apollo Computer Inc.
All rights reserved.
Printed in U.S.A.
Print date: April, 1986
This document was formatted using the FMT tool distributed with the DOMAIN
computer system.
APOLLO and DOMAIN are registered trademarks of Apollo Computer Inc.
AEGIS, DGR, DOMAIN/BRIDGE, DOMAIN/DFL-100, DOMAIN/DQC-100, DOMAIN/Dialogue,
DOMAIN/IX, DOMAIN/Laser-26, DOMAIN/PCI, DOMAIN/SNA, DOMAIN/VACCESS, D3M,
DPSS, DSEE, GMR, and GPR, are trademarks of Apollo Computer Inc.
MULTIBUS is a trademark of the Intel Corporation.
ETHERNET is a registered trademark of Xerox Corporation
Apollo Computer Inc. reserves the right to make changes in specifications and
other information contained in this publication without prior notice, and the
reader should, in all cases, consult Apollo Computer Inc. to determine
whether any such changes have been made.
THE TERMS AND CONDITIONS GOVERNING THE SALE OF APOLLO COMPUTER INC. HARDWARE
PRODUCTS AND THE LICENSING OF APOLLO COMPUTER INC. SOFTWARE CONSIST SOLELY OF
THOSE SET FORTH IN THE WRITTEN CONTRACTS BETWEEN APOLLO COMPUTER INC. AND ITS
CUSTOMERS. NO REPRESENTATION OR OTHER AFFIRMATION OF FACT CONTAINED IN THIS
PUBLICATION, INCLUDING BUT NOT LIMITED TO STATEMENTS REGARDING CAPACITY,
RESPONSE-TIME PERFORMANCE, SUITABILITY FOR USE OR PERFORMANCE OF PRODUCTS
DESCRIBED HEREIN SHALL BE DEEMED TO BE A WARRANTY BY APOLLO COMPUTER INC. FOR
ANY PURPOSE, OR GIVE RISE TO ANY LIABILITY BY APOLLO COMPUTER INC.
WHATSOEVER.
IN NO EVENT SHALL APOLLO COMPUTER INC. BE LIABLE FOR ANY INCIDENTAL,
INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING BUT NOT
LIMITED TO LOST PROFITS) ARISING OUT OF OR RELATING TO THIS PUBLICATION OR
THE INFORMATION CONTAINED IN IT, EVEN IF APOLLO COMPUTER INC. HAS BEEN
ADVISED, KNEW OR SHOULD HAVE KNOWN OF THE POSSIBILITY OF SUCH DAMAGES.
THE SOFTWARE PROGRAMS DESCRIBED IN THIS DOCUMENT ARE CONFIDENTIAL INFORMATION
AND PROPRIETARY PRODUCTS OF APOLLO COMPUTER INC. OR ITS LICENSORS.
Reader_Notice
This document resides online in the /doc directory.
To print a copy of this document, use the PRF command with the -npag and -pr
options.
PRF <file_pathname> -PR <printer_name> -NPAG
iii
CONTENTS
CHAPTER 1 OVERVIEW OF TCP/IP VERSION 2.1 . . . . . . . . . . . . . . . 1-1
CHAPTER 2 SOFTWARE INSTALLATION PROCEDURES. . . . . . . . . . . . . . 2-1
CHAPTER 3 CHANGES IN DOCUMENTATION . . . . . . . . . . . . . . . . . . 3-1
CHAPTER 4 BUGS AND BUG FIXES . . . . . . . . . . . . . . . . . . . . . 4-1
Contents iv
CHAPTER 1
OVERVIEW OF TCP/IP SOFTWARE VERSION 2.1
TCP/IP Version 2.1 provides new features and enhancements for the DOMAIN
Transmission Control Protocol/Internet Protocol (TCP/IP) Product, a
product that provides file transfer and remote log-in capabilities between
DOMAIN nodes and other systems, via an ETHERNET gateway. These changes
include:
o The software has been rewritten to increase throughput.
o All TCP/IP users must be TCP/IP hosts.
o DOMAIN Telnet now supports inbound Telnet sessions.
o Gateways provide improved routing services and dynamically update
their routing tables.
o Configuration procedures have been improved.
The remainder of this chapter further describes the changes in TCP/IP for
Version 2.1, and their implications for system configuration. It also
describes revision requirements for standard software on nodes that run
Version 2.1 TCP/IP. Be sure to also read the new manuals shipped with this
software release. (See Chapter 3 for a description of these manuals).
NOTE: If you have both the DOMAIN/IX and TCP/IP products, YOU MUST
INSTALL THE DOMAIN/IX PRODUCT BEFORE YOU INSTALL TCP/IP. Chapter 2
provides instructions for installing TCP/IP.
TCP/IP 1-1 Version 2.1
1.1 PERFORMANCE ENHANCEMENTS AND REVISION COMPATIBILITY
TCP/IP Version 2.1 substantially enhances data throughput. This performance
enhancement was obtained by reorganizing and rewriting much of the TCP/IP
code. Much of the TCP/IP software was moved from the tcpserver to
lower-level code. As a result of these changes, Nodes running TCP/IP Version
2.1 must also run AEGIS or DOMAIN/IX SR9.2.3, and nodes running SR9.2.3
cannot run any TCP/IP release previous to Version 2.1.
TCP/IP no longer employs the "MBX mailboxes" software structure that was used
in the versions that were released with DOMAIN SR8.1 and SR9.0. As a
result of this change, all nodes that use Version 2.1 TCP/IP must be TCP/IP
hosts. (However, if one node running SR9.0 software is a TCP/IP host, other
SR9.0 nodes can use the SR9.0 version of TCP/IP without being a host; they
must link to the SR9.0 host.
The standard Version 2.1 gateway software does not support TCP/IP
communication from nodes that run SR8.1 TCP/IP. (It does support
communication from nodes running SR9.0 TCP/IP.) We provide hybrid gateway
software that will support networks with mixed TCP/IP revision levels from
SR8.1 through Version 2.1. However, this hybrid version of the tcpserver
program DOES NOT include the performance enhancements provided by Version
2.1. The hybrid tcpserver is identical to the hybrid version that was
shipped with SR9.0 and will run on gateway nodes that run SR9.0 through
SR9.2.3 standard software, as well as on those that run SR8.1 standard
software.
When you install Version 2.1 TCP/IP software on the gateway node, the
software installation procedures ask you whether you need compatibility with
SR8.1. (see Chapter 2 for more information on the installation procedure.)
Respond affirmatively if there will be nodes in the network that run SR8.1
TCP/IP. The installation procedure will then install the hybrid tcpserver.
Also, the REMAINDER of TCP/IP software on the gateway (such as the ftp and
telnet programs) will not be updated, and will remain at the SR8.1 revision
level. So, if you wished to use the gateway as a host, it would not have
changes provided in Version 2.1 or SR9.0 TCP/IP, such as inbound Telnet or
binary file transfer.
Version 2.1 1-2 TCP/IP
1.2 NEW FEATURES
DOMAIN TCP/IP now supports inbound Telnet sessions. (These were previously
only supported by DOMAIN/IX Telnet). An AEGIS node that runs the
telnetserver process will accept Telnet requests from other TCP/IP hosts.
All DOMAIN gateways are now prime, or routing, gateways. They can determine
the most efficient path to a remote destination, and reroute the message on a
more efficient path.
Additionally, all gateways now run a process that uses the routing
information protocol (RIP) to update the gateway's routing tables. DOMAIN/IX
gateways run the routed daemon; AEGIS gateways run the RIP_SERVER process.
Previously, only DOMAIN/IX supported the RIP protocol. The RIP_SERVER and
routed processes continuously update the gateway's tables of routes to remote
destinations so that the tables reflect changes in the Internet topology.
The node configuration process has been improved. The installation procedure
places the configuration files in their required locations and creates the
necessary links to other nodes. This new configuration has resulted in the
relocation of some files. There is no longer a /sys/node_data[.nodeid]/tcp
directory. A files that were in this directory, except for the thishost and
networks files, are now in the /sys/tcp directory. The networks and thishost
files are now located in the /sys/node_data[.nodeid] directory. The
installation procedure automatically moves any existing thishost or networks
file to the required location. Managing___TCP/IP-Based___Communications
Products describes in detail how to configure TCP/IP and lists configuration
file locations.
As part of the changes in configuration procedure, we have introduced a new
concept, called the administrative node, which you will encounter during the
installation procedure. The administrative node is the node that contains
(typically) network-wide TCP/IP configuration information such as the files
in the /sys/tcp/hostmap directory. Other TCP/IP hosts access these files
through links. In previous releases, we used the same linking method, but
recommended that you install the master files on the gateway (which in many
cases is diskless). You can now install these files on any node, such as a
file server, by designating it as an administrative node.
TCP/IP 1-3 Version 2.1
CHAPTER 2
INSTALLATION PROCEDURES
This chapter describes how to install TCP/IP Version 2.1. You can add this
software to a node or DOMAIN System server that is running the SR 9.2 or
SR9.2.3 version of the AEGIS or DOMAIN/IX operating system. If a node is not
running SR9.2 or SR9.2.3, follow the appropriate software update procedures.
These procedures are described in Installing__DOMAIN__Software (Order No.
008860 Revision 00).
After you install the software, configure TCP/IP as described in Managing
TCP/IP-Based_Communications__Products. You must complete these procedures
before you can use TCP/IP software.
2.1 WHICH INSTALLATION PROCEDURE TO USE
This section describes two installation procedures. While these procedures do
not describe all possible methods of installing software, they are relatively
simple and will enable you to install software on any network. Determine
which one to use before going any further.
o Use the installation procedures for system administrators if you are
a system administrator creating a source area. For more information
about source areas, see Installing__Domain__Software. You can use
cartridge tape, magnetic tape, or a floppy disk.
You can also use this procedure to install software on a node
directly from source media if there is no source area. However, you
should note that this procedure creates an install directory and
installs the installation software on the node in addition to the
product you are installing.
o Use the installation procedure for users if you are a user
installing software onto a node. You can only use this procedure if
your system administrator first installs the software in a source
area.
TCP/IP 2-1 Version 2.1
2.2 CONVENTIONS AND TERMINOLOGY
The terms and conventions used in these procedures are as follows:
o The Work node is the node with a keyboard and display that you are
using to enter the commands to do the software installation.
o The Target is the place where you are installing software.
The Target node is the node or DOMAIN Server Processor (DSP) on which
you are installing or updating (i.e., the node that contains the
target area). If the target node has a keyboard and a display (i.e.,
it is not a DSP), the work node and the target node can be the same.
The Target area is the directory to which you are installing new
software. For user installations it is normally the entry directory
of the node on which you are installing software. However, you do
not have to install the new software into an entry directory, for
example, if you are a system administrator creating a source area in
a subdirectory.
NOTE: When you are installing software to update a diskless node,
the target is the partner node's entry directory.
o A Secure network is a network where log in privileges and access to
files and directories is controlled. A secure network has a registry
of user accounts. An open network does not have registries or user
accounts.
o A Source area is an on-line master area of DOMAIN software.
Typically, an administrator installs software from distribution media
into the source area and users install software from the source area
over the network. The source area (that is, the highest level
directory in the source area) can be a node's entry directory (in
which case the software will also be used by that node) or any
subdirectory. You can put different software products in different
source areas.
On secure newtorks you enable a source area by running the
INIT_SOURCE program. In this case users who do not have sufficient
rights to modify their system directory can use the installation
procedures for users, described below, to install software from the
source area.
o Source media is the media that you get the software from. the source
media can be floppy disks, magnetic tape, cartridge tape, or another
node in the network.
o Angle brackets ( < > ) enclose the name of a key on the keyboard.
Version 2.1 2-2 TCP/IP
2.3 INSTALLATION PROCEDURE FOR SYSTEM ADMINISTRATORS
Use these procedures to install the software from floppy or tape source media
onto a source area. The target area becomes the source area for subsequent
software installations using the procedure for users, described in the next
section. If you have a secure network, you must have system administrator
rights to use this procedure.
2.3.1 Setting Up Source Areas
If you are a system administrator creating a source area, you can install
the software into a target area that is not at the entry directory (/)
level. (Of course, the node will not boot off of the new software; it will
only boot from the software at the entry directory level.) You can install
various optional software products into a source area and then use this
source area to selectively install optional products on the nodes in the
network.
For example, first create a directory //node/tcp/version2.1_source_area.
Then, when installing from tape or floppy into this area, use
//node/tcp/version2.1_source_area as the target area name. Once you create
this source area users can install software on their nodes by setting their
working directory to //node/tcp/version2.1_source_area and following the
user installation directions.
2.3.2 Installing the Software
NOTES: If you have a secure network, %.sys_admin must have ownership
rights to all files and directories in the source area. Therefore
you must ensure that the source area directory (the target for
this intsallation procedure) gives %.sys_admin ownership rights in
its own ACL, in its intial file ACL, and in its initial directory
ACL.
You can enter q or quit at any prompt in the procedure to abort the
installation and return to the Shell.
1) Log in to a work node as a person with system administrator rights
(i.e., person.sysadmin)
2) Set your working directory to the target area where you are
installing the software. The target will become the source area for
user installations. It can be at node level (like //thunder) or it
can be in a subdirectory (like //thunder/tcp/version2.1).
$ wd //target <RETURN>
TCP/IP 2-3 Version 2.1
3) Insert the source media into the drive and enter the RBAK command
shown below. If you are using a tape cartridge, use the CT option
shown in the example. If you are using a magnetic tape, use the M0
(Mzero) option. If you are using a floppy, use the F0 (Fzero)
option. If TCP/IP is supplied on more than one volume (for example,
on two floppy disks), only do this step with the first volume. This
procedure creates an install directory in the target area and writes
the installation software to the directory.
$ rbak -dev ct -f 1 install -as install -l -ms -force -sacl -du
$ rbak -dev m0 -f 1 install -as install -l -ms -force -sacl -du
$ rbak -dev f0 -f 1 install -as install -l -ms -force -sacl -du
4) Set your working directory to the install directory in the target
area.
$ wd //thunder/tcp/version2.1/install <RETURN>
5) Do this step only if you have a secure network and you are enabling
a source area. You must have system administrator rights to do this
step.
Type initsource at the Shell prompt. Then enter the pathname of your
source area.
$ initsource <RETURN>
Please enter the name of the SR9.2 SOURCE AREA/NODE
for your network (e.g., '//NODE/SR9.2_SOURCE_AREA'):
//thunder/tcp/version2.1 <RETURN>
The SR9.2 source area/node for your network
has been set to: //thunder/tcp/version2.1
6) Execute the install Shell script and follow the prompts. Use the
-my_sid option in the install command. This will apply your ACL
rights (that is, the sys_admin ACL rights) to the installed files,
and will cause the install script to display the media prompt. You
MUST use the -my_sid option if you used step 5 to create a source
area.
$ install -mysid <RETURN>
Version 2.1 2-4 TCP/IP
7) The program prompts for the installation type. The following prompt
list is a sample; your list may not include all these options and
they may be listed in another order. Enter OPT and press <RETURN>.
Software installation TYPES are:
STD -- Install SR9.2 standard software
RESTART -- Restart the software installation.
ACL -- Set acl's for existing software
CLEANUP -- Run the Cleanup Procedure for ADD MODE
installations
DOMAIN_IX -- Install the DOMAIN/IX software
OPT -- Install optional software (e.g., Pascal, FORTRAN)
Please Enter Installation Type: OPT <RETURN>
8) Enter the name of the optional product that you want to install, in
this case TCP, and press <RETURN>.
Name Description Disk Blocks Needed
(Adding New Software)
TCP TCP/IP 900
OTHER If the optional product that you would like to install
is not listed above, choose OTHER.
*Note: When you choose OTHER, you are asked a few questions
then shown a display of Apollo's optional products. Check
with your system administrator to determine which products
your site has purchased and in which directory these
products have been installed.
Enter the name of a single product you would like to install: TCP
9) You are then prompted for the name of the target area. Enter the
pathname of the target node or directory (e.g., the source area you
are creating) and press <RETURN>.
The TARGET is the node or subdirectory on which you are installing
software. (e.g., '//my_node' or '//my_node/subdirectory')
Enter Target:
10) Indicate whether you are installing software on a gateway to another
network. A bridge to a DOMAIN network is also a gateway. Also answer
YES if you are creating a source area that will contain all TCP/IP
software.
Is the installation to //TARGET a GATEWAY install ?
Enter YES or Y or NO or N :
TCP/IP 2-5 Version 2.1
11) If you answered YES in step 10 you are asked whether you are
performing an SR8 Compatible install. Answer YES to install a version
of gateway software that will allow nodes that run SR8 software to
use the gateway. Otherwise enter NO and continue with step 12.
Is the installation to //TARGET a SR8_COMPATIBLE install ?
Enter YES or Y or NO or N :
NOTE: If you are creating a source area that will include the SR8
compatible gateway software, you must run the installation
procedure twice; the first time, answer YES to this
question to install only the SR8 compatible software. When
this installation completes, select CONTINUE in step 18
and install all other TCP/IP software in the source area.
You cannot install the software in the reverse order, that
is, by first answering NO to this question.
If you answer YES, you are asked for the name of the TCP/IP
Administrator node. You must enter the name of an existing node on
your network. When you complete this step, skip to step 16.
Please enter the name of the TCP/IP ADMINISTRATOR node on which
the sys/tcp/hostmap DIRECTORY resides (e.g. //SERVER)
Enter node name or type 'quit':
NOTE: If you are installing the SR8 compatible software in a
source area that will also include Version 2.1 TCP/IP
administrative node software, you can enter the name of
any node on your network. When you install the rest of the
software you will be asked if you wish to replace the links
with TCP/IP administrator software. At that point, enter
YES to replace the dummy link and install the software.
12) Indicate whether you are installing software for a diskless node.
Is the installation to //TARGET a DISKLESS install ?
Enter YES or Y or NO or N :
If you specify YES, the procedure asks you for the id of the diskless
node. Enter the hexadecimal node ID.
Please enter the NODE ID of the TARGET DISKLESS NODE that the tcp
software will be installed for. (e.g., 260d):
Enter hex node id:
Version 2.1 2-6 TCP/IP
13) Indicate whether this is a TCP/IP administrative node that will
maintain a copy of the host mapping files. Also answer YES if you
are creating a source area that will contain all TCP/IP software.
Is the installation to //TARGET an TCP/IP ADMINISTRATOR install ?
Enter YES or Y or NO or N :
14) The following question appears if you DID NOT specify a GATEWAY
installation in step 10. Indicate whether this node is a client,
that is a TCP/IP host.
Is the installation to //TARGET a CLIENT install ?
Enter YES or Y or NO or N :
15) If you DID NOT specify an administrative installation in step 13, You
are asked for the TCP/IP administrative node's name.
Please enter the name of the TCP/IP ADMINISTRATOR node on which
the sys/tcp/hostmap DIRECTORY resides (e.g. //SERVER)
Enter node name or type 'quit':
16) The procedure prompts you for the source media if you did not do step
5, or if you did step 5 and included the -my_sid option in the
install command in step 6. Enter the appropriate source media and
press <RETURN>.
Source MEDIA is one of:
CTAPE -- Cartridge Tape
MTAPE -- Magnetic Tape
FLOPPY -- 8" or 5 1/4" Floppies
NET -- An area on the network with valid Software
Enter Source Media:
17) Since you are using magnetic tape, cartridge tape, or floppy disks,
the procedure asks you to insert the media into the drive. Do so and
press <RETURN>. (If the disk is already installed, the installation
process begins immediately.) If the release consists of multiple
diskettes, you are prompted to install the next disk and press
<RETURN> as each diskette's software is installed.
TCP/IP 2-7 Version 2.1
18) The procedure installs the software and lists the files that are
copied. If you are installing software on a gateway, the procedure
also creates a ddf (device descriptor file). It then asks you if you
wish to rerun the installation, install other optional software, or
finish. Check the transcript pad for any errors by searching
backwards for a question mark. If there are errors, correct the
problem before you rerun the installation.
Note that you cannot change any of the installation parameters when
you select rerun; the procedure uses your previous answers and skips
to step 17.
Options:
RERUN -- There were errors in the transcript
pad and you wish to rerun the installation.
FINISH -- The installation ran to completion error free.
There is no additional optional software you
wish to install.
CONTINUE -- Install additional optional software.
Enter an option:
19) Do this step if you selected FINISH, there were no errors during the
installation, and you are updating software on a node that is already
a TCP/IP gateway or client. If you are installing software on a node
that did not run TCP/IP, continue with the configuration procedures
described in Managing TCP/IP-Based Communications Products.
a. Use the Display Manager shut command to shut down the targt
node.
<cmd> shut <RETURN>
b. After the SUCCESSFUL SHUTDOWN message and the > prompt
appear, reboot the node by typing the following at the
prompt: RE <RETURN> <RETURN> EX AEGIS <RETURN>.
> RE
> <RETURN>
> <RETURN>
MD REV xx/xx/xx
> EX AEGIS <RETURN>
You are finished with the installation procedures. Refer to Chapters 3 and 4
of Managing__TCP/IP-Based__Communications__Products for information about
configuring your system.
Version 2.1 2-8 TCP/IP
2.4 INSTALLATION PROCEDURE FOR USERS
Use this procedure if you are installing TCP/IP software on a node from the
network. Ask your system administrator for the name of the source area for
the software. If you are installing software on a disked node, the target is
that node. If you are installing software for a diskless node, the target is
the diskless node's partner node.
NOTE: You can enter q, or quit at any prompt in the procedure to abort
the installation and return to the Shell.
1) Log in to a work node as yourself; the work node can be the target
node or any other node on the network. Start a Shell on the work
node.
2) Set your working directory to //Source_area/install. The system
administrator will provide you with the pathname of the source area.
$ wd //source_area/install <RETURN>
3) Execute the install Shell script and follow the prompts.
NOTE: If your system administrator has enabled the source area,
you can use the -mysid option in the install command to
use your ACL rights for the installation, rather than the
rights that are assigned to sys_admin.
$ install <RETURN>
4) The program prompts you for an installation type. (The following
prompt list is a sample; your list may not include all these options
and they may be listed in another order.) Enter OPT and press
<RETURN>.
Software installation TYPES are:
STD -- Install SR9.2 standard software
RESTART -- Restart the software installation.
ACL -- Set acl's for existing software
CLEANUP -- Run the Cleanup Procedure for ADD MODE
installations
DOMAIN_IX -- Install the DOMAIN/IX software
OPT -- Install optional software (e.g., Pascal, FORTRAN)
Please Enter Installation Type: OPT <RETURN>
TCP/IP 2-9 Version 2.1
5) Enter the name of the optional product that you want to install, in
this case TCP, and press <RETURN>. (The following prompt list is a
sample; your list may include other options.)
Name Description Disk Blocks Needed
(Adding New Software)
TCP TCP/IP 900
OTHER If the optional product that you would like to install
is not listed above, choose OTHER.
*Note: When you choose OTHER, you are asked a few questions,
then shown a display of Apollo's optional products. Check
with your system administrator to determine which products
your site has purchased and in which directory these
products have been installed.
Enter the name of a single product you would like to install: TCP
6) You are then prompted for the name of the target. Enter the name of
the target node, preceded by slashes, and press <RETURN>. Remember
that if you are installing software for a diskless node, the target
is the diskless node's partner.
The TARGET is the node or subdirectory on which you are installing
software. (e.g., '//my_node' or '//my_node/subdirectory')
Enter Target:
7) Indicate whether you are installing software on a gateway to another
network. A bridge to a DOMAIN network is also a gateway.
Is the installation to //TARGET a GATEWAY install ?
Enter YES or Y or NO or N :
8) If you answered YES in step 7 you are asked whether you are
performing an SR8 Compatible install. Answer YES to install a version
of the tcpserver that will allow nodes that run SR8 software to use
the gateway. (In this case, only the tcpserver, and no other
software, gets insalled.) Otherwise enter NO and continue with step
9.
Is the installation to //TARGET a SR8_COMPATIBLE install ?
Enter YES or Y or NO or N :
Version 2.1 2-10 TCP/IP
If you answer Yes, you are asked for the name of the TCP/IP
Administrator node. You must enter the name of an existing node on
your network. When you complete this step, skip to step 13.
Please enter the name of the TCP/IP ADMINISTRATOR node on which the
sys/tcp/hostmap DIRECTORY resides (e.g. //SERVER)
Enter node name or type 'quit':
9) Indicate whether you are installing software for a diskless node.
Is the installation to //TARGET a DISKLESS install ?
Enter YES or Y or NO or N :
If you specify yes, the procedure asks you for the id of the diskless
node. Enter the hexadecimal node ID.
Please enter the NODE ID of the TARGET DISKLESS NODE that the tcp
software will be installed for. (e.g., 260d):
Enter hex node id:
10) Indicate whether this is an administrative node that will maintain a
copy of the host mapping files.
Is the installation to //TARGET an TCP/IP ADMINISTRATOR install ?
Enter YES or Y or NO or N :
11) The following question appears if you DID NOT specify a GATEWAY
installation. Indicate whether this node is a client, that is a
TCP/IP host.
Is the installation to //TARGET a CLIENT install ?
Enter YES or Y or NO or N :
12) If you DID NOT indicate that this was an administrative node, You
are asked tor the TCP/IP administrative node's name.
Please enter the name of the TCP/IP ADMINISTRATOR node on which
the sys/tcp/hostmap DIRECTORY resides (e.g. //SERVER)
Enter node name or type 'quit':
TCP/IP 2-11 Version 2.1
13) Depending on how your system administrator has set up the source
area, the installation program may ask for the source media. If it
does not, skip to step 14. The procedure also prompts you for the
source media if you included the -my_sid option in the install
command in step 3. Enter NET and press <RETURN>.
Source MEDIA is one of:
CTAPE -- Cartridge Tape
MTAPE -- Magnetic Tape
FLOPPY -- 8" or 5 1/4" Floppies
NET -- A area on the network with valid Software
Enter Source Media: net
After you enter NET as the source media, the procedure asks for the
source area. Enter the name of the source area that was provided by
your system administrator.
The SOURCE AREA is the node or subdirectory from which you are
copying software. (e.g., '//node' or '//node/subdirectory')
Enter Source Area:
14) The procedure installs the software and lists the files that are
copied. If you are installing software on a gateway, the procedure
also creates a ddf (device descriptor file). It then asks you if you
wish to rerun the installation, install other optional software, or
finish. Check the transcript pad for any errors. If there are errors,
correct the problem before you rerun the installation.
Options:
RERUN -- There were errors in the transcript
pad and you wish to rerun the installation.
FINISH -- The installation ran to completion error free.
There is no additional optional software you
wish to install.
CONTINUE -- Install additional optional software.
Enter an option:
15) Do this step if you selected FINISH, there were no errors during
the installation, and you are updating software on a node that is
already a TCP/IP gateway or client. If you are installing software on
a node that did not run TCP/IP, continue with the configuration
procedures described in Managing TCP/IP-Based Communications
Products.
Version 2.1 2-12 TCP/IP
a. Use the Display Manager shut command to shut down the target
node.
<cmd> shut <RETURN>
b. After the SUCCESSFUL SHUTDOWN message and the > prompt
appear, reboot the node by typing the following at the
prompt: RE <RETURN> <RETURN> EX AEGIS <RETURN>.
> RE
> <RETURN>
> <RETURN>
MD REV xx/xx/xx
> EX AEGIS <RETURN>
You are finished with the installation procedures. Refer to Chapters 3 and 4
of Managing__TCP/IP-Based__Communications__Products for information about
configuring your system.
TCP/IP 2-13 Version 2.1
2.5 TCP/IP Files
The following sections list the files and links that are installed during a
Client, Server, and Gateway installation.
2.5.1 Client Files
The following files are installed on a Client node:
com/ftp
com/host
com/tcpstat
com/telnet
doc/tcp.2.1.release_notes
sys/tcp/ftp_server
sys/tcp/makegate
sys/tcp/networks_template
sys/tcp/setroute
sys/tcp/tcpinit
sys/tcp/tcpreset
sys/tcp/tcp_server
sys/tcp/telnet_server
sys/tcp/thishost_template
2.5.2 Gateway Files
The following files are installed on a Gateway node in_addition_to all Client
node files:
sys/tcp/ether_diag
sys/tcp/lib/build_ddf.sh
sys/tcp/lib/ether.lib
Version 2.1 2-14 TCP/IP
sys/tcp/lib/ether_int.lib
sys/tcp/maphost
sys/tcp/rip_server
The following file is installed if you specify that the gateway will be SR8
compatible. No other files are installed in this case.
sys/tcp/tcp_server.sr8.gateway
2.5.3 Administrative Files
The following files are installed on the Administratve node:
sys/tcp/hostmap/hashnic
sys/tcp/hostmap/hosts.txt
sys/tcp/hostmap/local.txt
sys/tcp/hostmap/makehdb
sys/tcp/hostmap/makehost.sh
sys/tcp/hostmap/ndb_format
sys/tcp/hostmap/sortnic
2.5.4 Links
The installation procedure creates the following links on client and gateway
nodes. //ADMIN indicates the administrative node that you specify during the
installation procedure. TARGET is the target area where the software is
being installed.
FROM TO
TARGET/com/net TARGET/com/hosts
TARGET/sys/tcp/gateways //ADMIN/sys/tcp/gateways
TARGET/sys/tcp/hostmap //ADMIN/sys/tcp/hostmap
TARGET/sys/tcp/hosts.hst //ADMIN/sys/tcp/hosts.hst
TARGET/sys/tcp/networks `node_data/networks
TARGET/sys/tcp/thishost `nod_data/thishost
TCP/IP 2-15 Version 2.1
CHAPTER 3
CHANGES TO DOCUMENTATION
The TCP/IP document set has been changed as of this release. TCP/IP is now
documented in two manuals:
o Managing_TCP/IP-Based_Communications_Products, Order Number 008543,
Revision 00
o Using_Telnet_and_FTP, Order Number 008667, Revision 00
These manuals replace Managing__TCP/IP-Based_Communications_Products, Order
Number 008543, which is now obsolete. The new manuals reflect all the
changes listed in Chapter 1 of this document and provide additional
information.
Managing_TCP/IP-Based_Communications__Products Describes how to configure,
manage, and troubleshoot DOMAIN TCP/IP-Based communications software,
including the COM-ETH and SFW-TCP software, DOMAIN/VACCESS-1 software, and
the TCP/IP implementation that is provided as part of DOMAIN/VACCESS.
Using__Telnet_and_FTP Describes how to use the Telnet remote terminal emulator
and FTP file transfer program that are supplied as part of TCP/IP and
DOMAIN/VACCESS software.
Additionally, Using__DOMAIN/VACCESS-1 describes how to use this new product;
and Appendix J to DOMAIN/IX_Programmer's__Reference__for__BSD4.2 contains a
subset of the information in Managing_TCP/IP-Based_Communications_Products
that is relevant to BSD4.2 TCP/IP.
TCP/IP 3-1 Version 2.1
CHAPTER 4
ERRORS CORRECTED
4.1 BUGS
This section documents known bugs in the TCP/IP documentation, software
installation procedures, and software.
4.1.1 BUGS IN DOCUMENTATION
Make the following corrections to Managing TCP/IP-Based Communications
Products.
o On page 4-17 the order of the lines in the .profile file are
reversed. They should be:
PATH=:.:/bin:/usr/bin:/usr/ucb:/com:~/com
export PATH
o On page 5-5, Task 2, line 1, the file pathname is missing a "/"
character between "hostmap" and "local.txt". The line should read:
Edit the /sys/tcp/hostmap/local.txt file on ....
o On page 5-9, Task 2, line 7, the file pathname is missing "/tcp"
between "/sys" and "hostmap". The line should read:
/sys/tcp/hostmap/local.txt from the ....
TCP/IP 4-1 Release 2.1
o On page 6-6, at the bottom of the page, the output of the example
/sys/tcp/tcp_server -version command is incorrect. the example should
look as follows:
$ /sys/tcp/tcp_server -version
Apollo TCP/IP server Version 2.1, Fri Mar 7 15:50:59 1986
o On page 6-15 the second sentence is incorrect. It should read:
Most hosts display two reports, one for the network and one
for the software loopback interface.
o On page B-11 the network numbers used in the example are not valid
Type C DARPA Internet numbers. A valid example follows:
Display the network for the networks NORWAY and
198.2.4.
$ net norway 198.2.4
norway: 198.2.3
sweden: 198.2.4
o On page C-3, paragraph 3, (the second paragraph in the Connection
timed out entry) can be confusing. It should be replaced by the
following two paragraphs:
Check that either routed or ripserver is running on the
gateway. Also check the foreign host to see if it
recognizes your DOMAIN network.
If the foreign host runs UNIX you can use the netstat -r
command at that host to check the networks that it
recognizes. If the DOMAIN network does not appear on the
listing, use the following command to add your network:
4.1.2 BUGS IN TCP/IP SOFTWARE
The following bugs currently exist in the TCP/IP software:
o It takes a finite amount of time for the tcpserver to start
running, and the telnetserver and ftpserver can not initialize
correctly before the tcpserver is running. Therefore, the
cps /sys/tcp/ftpserver command or cps /sys/tcp/telnetserver
command must__not immediately follow the cps /sys/tcp/tcpserver
command in your startup file.
Release 2.1 4-2 TCP/IP
If your telnetserver or ftpserver does not initialize properly when
you reboot your node or restart the Display Manager (DM), try
increasing the number of (other) commands that immediately follow
the cps /sys/tcp/tcpserver command in your startup file.
o If you run the on-line test etherdiag at the same time that other
hosts on the ETHERNET network are sending broadcast packets, the test
may not run properly. The test may ignore any packets that it did
not send itself.
o If you send two telnet IP (^ip) commands in a row, with no
intervening input, the second one is received by the foreign host as
the character 't'.
4.1.3 RESTRICTIONS IN TCP/IP SOFTWARE
The TCP/IP ftp and telnet commands are case-sensitive. You must use
lower-case for these commands.
4.2 BUG FIXES
The following TCP/IP bugs have been corrected since SR9.0:
o The way FTP constructs the automatically-supplied PORT command before
doing a data transfer has been changed. The previous method could
cause FTP to be unable to perform data transfers when it was run on
a gateway.
o A bug which caused ftpserver to be unable to transfer more than 50
files in a single session has been fixed.
o Data broadcast on the ring is now received by the sender. This
matches the behavior on the ETHERNET, where a broadcaster always
receives his own message.
o A bug in that could cause tcpserver to die if it received a UDP
datagram containing more than 1024 bytes of data has been fixed.
o The DOMAIN TCP/IP FTP list command did not work. If you ran FTP from
a remote host to a DOMAIN host running the DOMAIN TCP/IP ftpserver,
the results were unpredictable. This problem has been corrected.
o Only ETHERNET types in the range 1000 through 1015 are now treated as
BSD4.2 trailer types. Previously, all ETHERNET types above 1000 were
assumed to be trailer types. This caused the tcpserver to crash if
it received a valid ETHERNET type greater than 1015.
TCP/IP 4-3 Release 2.1
o In previous versions, if TCP/IP did not recieve a maximum segment
size option on a listening connection, it would assume a maximum
segment size of zero and would therefore never send any data. This
problem was seen in communications with BSD4.3 Unix systems and
TOPS-20 systems. Now, there is a default maximum segment size of 512
bytes.
o The tcpserver now sets the PUSH bit if it is sending all the data
supplied by the user. In previous versions the PUSH bit was not
sent. Some TCP implementations only deliver data to the user when
their buffer fills or the PUSH bit is set in the incoming segment.
These implementations would not deliver all the data send by the
TCP_SERVER.
o The host command did not work. It now works correctly.
Release 2.1 4-4 TCP/IP