Ref: 99960054
Title: ESD Rel.Note:SW/20-TCP-NCS/150 Ver.3.0 Part#:86-0137-00 Rev.02
date: 03-20-89

Copyright 3Com Corporation, 1991.  All rights reserved.

Software Release
SW/20-TCP-NCS/150 Version 3.0
March 20, 1989

Part Number: 86-0137-00
             Revision: 02

TO:  CS/1 Users
FROM: 3Com Corporation
SUBJECT: SW/20-TCP-NCS/150 Version 3.0
DATE: March 20, 1989

Enclosed is a distribution diskette containing SW/20-TCP-NCS/150
Version 3.0 (Part Number: 83-0161-01).  This software runs on a CS/1
that is equipped with an MCPU20 board and booted from an NCS/150.

This release memo describes the procedure for installing SW/20TCP-
NCS/150 Version 3.0 on the NCS/150.  It also lists the new features,
fixed bugs, limitations, and known prob lems in this version of SW/20-
TCP-NCS/150.

** NOTE **

3Com changed its software version numbering scheme in early 1989.
Instead of  using a five-digit number, such as 20060, 3Com now uses
two- or three-digit  numbers, such as 2.2 and 2.21.  Higher version
numbers represent more recent  releases.  For
example, 2.21 is more recent than 2.2, 2.2 is more recent than  20060,
and 20060 is more recent than 20000.

Compatibility

SW/20-TCP-NCS/150 Version 3.0 operates with the following products and
software releases:

 CS/1 running SW/1-TCP Version 20000 or later
 CS/50 running SW/50-TCP Version 3.0 or later
 IB/3 running SW/20-IB Version 11000 or later
 NCS/2 running SW/2-NCS Version 2.0 or later
 NCS/AT running SW/AT-NCS Version 2.0 or later
 CS/200 running SW/200-TCP Version 20000 or later
 CS/210 running SW/200-TCP-CS/210 Version 3.0 or later
 CS/100 running SW/100-TCP Version 3.0 or later
 Personal computer running SW/1-PCS Version 20000 or later

If an Ethernet controller is used with the MCPU20-based CS/1, it must
be an EC/2 board with 512 kilobytes of RAM.  Also, an MCPU20 must
operate with a 96-TPI disk drive.

If your CS/1 is equipped with one or more SIO-16 boards, the version
number of the SIO-16 software must be 11070 or later.

Hardware and Firmware Requirements of SIO-16 Boards

The following requirements must be met if your CS/1 running SW/1TCP-
NCS/AT Version 3.0 is equipped with one or more SIO-16 boards:

The M1 MMON PROM Rev. 01G or later is required on the MCPU board.

An EC/2 with 512K memory, TRC/M, or IBC/M board must be installed on
the  CS/1.

If the CS/1 is equipped with three or four SIO-16 boards, the MCPU
board must be  upgraded to 12 MHz.  If it is equipped with one or two
SIO-16 boards, a 10 MHz  MCPU board can be used.

** NOTE **

You must press the Return key after you type each command in
procedures  described in this release memo.

Refer to Chapter 3 of the TCP/IP Connection Service User's Guide for
an  explanation of the notation used in commands referenced in this
release memo.

Installation

Because your CS/1 is booted from an NCS/150, install SW/20-TCP-NCS/150
on the NCS/150.

If your CS/1 is equipped with one or more SIO-16 boards, skip to the
procedure for In stalling SW/20-TCP-NCS/150 Version 3.0 on an NCS/150
with SIO-16 Boards on page 5 of this release memo.

Otherwise, follow these steps to install SW/20-TCP-NCS/150 Version 3.0
on the NCS/150:

1. Attach a terminal to port 0 of the NCS/150.

2. Insert the SW/150-NCS-TCP-UTIL diskette in the NCS/150 disk drive,
then press  the Reset switch.

3. After the NCS/150 has finished booting, enter the following
sequence on the  keyboard:

 <RETURN>.<RETURN>

That is, press the Return key, the period (.) key, and the Return key
in succession.

4. Remove the SW/150-NCS-TCP-UTIL diskette, then insert the SW/150-
TCP-NCS  diskette in the disk drive.  Type the following command:

 ls -lx /BIN

This command displays the contents of the software image currently
available on  the SW/150-TCP-NCS diskette.

5. Because the SW/150-TCP-NCS diskette can contain the software for
one or two  product types only, it may be necessary to remove software
from the diskette to  make room for the file containing SW/20-TCP-
NCS/150 Version 3.0.  Because of  the increas
ed size of the new software, the SW/150-TCP-NCS diskette may be able
to contain only SW/20TCP-NCS/150 Version 3.0.  Type "rm <filename>" if
you  need to remove a file.

6. If the file cs20t already exists, remove it by typing the
following:

 rm /BIN/cs20t

7. Perform a file system check by typing the following command:

 fsck -c

8. Create a file named cs20t on the SW/150-TCP-NCS diskette by typing
the  following command:

 cr /BIN/cs20t 218 rwx 4004000

9. To copy the software image from the SW/20-TCP-NCS/150 Version 3.0
distribution diskette to the newly-made cs20t file on the SW/150-TCP-
NCS  diskette, type the following command:

 cf #0 /BIN/cs20t

10. When the system prompts for the source diskette, remove the
SW/150-TCP-NCS  diskette. Insert the SW/20-TCP-NCS/150 Version 3.0
diskette.  Then press the  Return key.

11.  When the system prompts for the destination diskette, replace the
SW/20-TCP- NCS/150 Version 3.0 diskette with the SW/150-TCP-NCS
diskette.  Then press  the Return key.  The copying process is
finished when the following message is  displayed:

 Copy completed

Installing SW/20-TCP-NCS/150 Version 3.0 on an NCS/150 with SIO-16
Boards

If your CS/1 is equipped with one or more SIO-16 boards, use the
following procedure to install SW/20-TCP-NCS/150 Version 3.0 on the
NCS/150:

1. Attach a terminal to port 0 of the NCS/150.

2. Insert the SW/150-NCS-TCP-UTIL diskette in the NCS/150 disk drive,
then press  the Reset switch.

3. After the NCS/150 has finished booting, enter the following
sequence on the  keyboard:

 <RETURN>.<RETURN>

That is, press the Return key, the period (.) key, and the Return key
in succession.

4. Remove the SW/150-NCS-TCP-UTIL diskette, then insert the SW/150-
NCS-TCP  diskette in the disk drive.  Type the following command:

 ls -lx /BIN

This command displays the contents of the software image currently
available on  the SW/150-NCS-TCP diskette.

5. Because the SW/150-NCS-TCP diskette can contain the software for
one product  type only, it may be necessary to remove software from
the diskette to make room  for the file containing SW/20-TCP-NCS/150
Version 3.0.  Because of the  increased size
of the new software, the SW/150-NCS-TCP diskette may be able to  hold
only the file containing SW/20-TCP-NCS/150 Version 3.0.  Type "rm
<filename>" if you need to remove a file.

6. If the file cs20t already exists, remove it by typing the
following:

 rm /BIN/cs20t

7. Remove existing SIO-16 driver files from the SW/150-NCS-TCP
diskette.

If the file /BIN/sio16driver exists, remove it by typing:

 rm /BIN/sio16driver

If the file /BIN/sio16.11030 exists, remove it by typing:

 rm /BIN/sio16.11030

If the file /BIN/sio16.11050 exists, remove it by typing:

 rm /BIN/sio16.11050

If the file /BIN/sio16.11060 exists, remove it by typing

 rm /BIN/sio16.11070

8. Perform a file system check by typing the following command:

 fsck -c

9. Create a file named cs20t on the SW/150-NCS-TCP diskette by typing
the  following command:

 cr /BIN/cs20t 218 rwx 4004000

10. Create a file for the SIO-16 driver by typing the following:

 cr /BIN/sio16.11070 2a rw

11. If the file named /BIN/sio16diags already exists on the SW/150-
NCS-TCP diskette,  continue on to step 12.

If the file named /BIN/sio16diags does not already exist on the
SW/150-NCS-TCP  diskette, type the following command to create this
file:

 cr /BIN/sio16diags 8 rw

Then continue on to step 13.

12. Type the following command to copy the software image, SIO-16
driver file, and  sio16diags file from the SW/20TCP-NCS/150 Version
3.0 distribution diskette to  the newly-made files on the SW/150-NCS-
TCP diskette.

 cf #0 /BIN/cs20t cf #1 /BIN/sio16.11070 cf #2  /BIN/sio16diags

13. When the system prompts for the source diskette, remove the
SW/150-NCS-TCP  diskette. Insert the SW/20-TCP-NCS/150 Version 3.0
diskette.  Then press the  Return key.

14. When the system prompts for the destination diskette, replace the
SW/20-TCP- NCS/150 Version 3.0 diskette with the SW/150-NCS-TCP
diskette.  Then press  the Return key.  The copying process is
finished when the following message is  displayed:

 Copy completed

After you install the software, you will have to redefine the global
parameters,  clearinghouse names, macros, and port configurations.  If
your CS/1 is not already  bound to the NCS/150, you should use the
BInd command to enable your CS/1 to  boot
from the NCS/150.  Refer to Section 5.3 of the NCS/150 Installation
and  Operation Guide for information on using the BInd command.

New Features

The following features, which were not available in SW/20-TCP-NCS/150
Version 20100, have been implemented in SW/20-TCP-NCS/150 Version 3.0:

The audit trail record codes, IX for ICMP transmitted and IR for ICMP
received,  now display more information to aid in network fault
analysis.

Additional features have been provided to support Hewlett Packard
devices.  These  include default parameter settings, context-sensitive
flow-control and spare XON  forwarding.

The SHow SESsion command has a new option, M.  This option displays
the  Internet address and the TCP port number on the destination side
of a connection.  The new syntax for the SHow SESsion command is as
follows:

 SHow (!<port number>) SESsion M

 For example, if you enter this command:

 sh (!1) ses m

 the screen display generated is similar to the following:

 CONCTD from 192.9.205.071:099:006

This display shows that port 1 of the host server is connected from
port 6 of a  Communications Server with the address of 192.9.205.071.
The number  immediately following the Internet address ("099" in this
example) may be  disregarded.

This feature only works if the destination server is a Communications
Server  manufactured by 3Com.

In accordance with the latest updates in the TCP/IP implementation of
the Berkeley  release 4.3 of the UNIX operating system, this version
has implemented  retransmission and round-trip algorithms, delayed
acknowledgements, superior  silly-window avoidance behavior, and
improved timer handling and disconnection procedures.

The effects of these implementations include higher data throughput
and more  reliable connections.

When entering commands in remote mode, the response timeout period has
been  increased from 12 to 28 seconds.  This is particularly useful
for Communications  Servers that are booted from an NCS/2, which often
requires a response time of  more than
12 seconds.

The LongBReakAction parameter is now available for both host and
terminal  ports.  Previously this parameter could not be set for host
ports. For more  information on this parameter, refer to the TCP/IP
Connection Service User's  Guide.

To deny access to all devices on the network, set the access level
parameter to  "address list" and check that there are no entries in
the address list.

Bugs Fixed

Certain problems, which existed in previous versions of SW/20-TCP-
NCS/150, have been solved in SW/20-TCPNCS/150 Version 3.0.  These
problems and their resolutions are de scribed below.

If you attempt to save default port parameters in a non-numbered file
and you do  not have global network manager privilege level, the
system now displays the error  message "Insufficient privilege" after
you enter the SAve command.

Previously, this message or the system prompt was not displayed until
the user  pressed the Break key.

Only a global network manager can save default port parameters in a
non-numbered  file.

The Domain name resolver no longer attempts to search infinitely for a
canonical  name when two canonical names that are aliases for each
other have been defined  by error in the Domain name server database,
and you specify one of these names  with
the Connect or SHow NAme command.

Previously, you had to reboot the server to terminate this infinite
loop.

Previously, if you entered the command, SH NAmes or SH NAmes *, the
Domain  name server failed to respond and the system crashed after the
timeout period had  expired.

These commands are no longer valid so you must specify a name. If you
attempt to  issue these commands without specifying a name, the
following error message  appears:

 can only show unique Domain names

You can now establish interconnections properly.  Previously, when
certain  interconnections were requested, the system crashed.

You can now specify the local broadcast address when you enter the
global network  manager form of the Broadcast command without
disrupting the network.   Previously, this command caused extremely
heavy traffic on the network.

The SHow LinePRotocol command now displays correct information.
Previously,  it always showed the value of the LinePRotocol parameter
as BYTEsynchronous.   Also, you can no longer change the value of this
parameter with the SETD  command.

You can now simultaneously run three or more recursive macros that
contain  Connect or DisConnect commands.  Previously, the system
crashed within three  hours of invoking the macros.

Setting the NetAscii parameter of a port to UseNul no longer causes
spurious ^A  characters to be inserted in the data stream sent to that
port.

The CS/1 now consistently passes special characters, for example,
<CR>, as data.   Previously, it often failed to do this in incoming
connections, and processed them  instead.

When the DataForward parameter is set as the result of an echo
negotiation by a  destination server using the Telnet protocol, it no
longer automatically changes to  None after the echo has been
negotiated.

An error, which caused the Domain name resolver to fail to respond to
inquiries  under certain circumstances, has been corrected.

This version attempts to establish connections to permanent circuits
(PVCs)  according to the order in which the connection requests are
received.  Previously,  priority was always given to the attempt to
connect to the lowest numbered PVC.

Also, you can successfully establish more than one PVC.  Previously,
you could  not reliably do this.

Domain name requests are sent to the NCS/AT address specified by the
FileServer- Address parameter if both the PrimaryNS and SecondaryNS
parameters are not  defined.

Previously, no alternate address was available to respond to these
requests.

Network errors are now recorded in the audit trail record with the
code "NE."  Previously, they were coded as "EE."

The boot time displayed by the SHow VERsion command now displays the
actual  boot time.

Previously, the time was computed.

Previously, you could not perform certain file transfer tasks if,
after establishing the  connection, you disabled the ECM character
with the following command:

 SET ECMchar = disabled

For example, if you attempted to transfer files from a personal
computer, setting  this parameter sometimes caused data loss.  This
resulted in failure of the file  transfer.

This problem has been corrected.

The session number field in the audit trail messages coded CD and DC
has been  replaced by a four-digit field which indicates the TCP port
number.

Previously the session number field always displayed 0, regardless of
the session  number.

You can no longer assign an Internet address beginning with 127 to a
Communications Server or a port.  This number is reserved for loopback
according  to the TCP/IP protocol implementation.  Existing addresses
which start with 127  must be reassigned.

If you attempt to assign an Internet address beginning with 127, the
following error  message is displayed:

 Address cannot be broadcast at loopback.

When forwarding data, the Telnet code now removes the ASCII control
character  NUL when it follows the control character CR.  Previously,
it failed to do this,  which caused problems when Telnet was used in
conjunction with the Berkeley 4.3 release of the UNIX operating
system.

When two Communications Servers on the network have the same Internet
address,  you can now issue commands from a source server that specify
the source server as  the destination.

Previously, for example, if ServerA and ServerB had the same Internet
address and  you issued the PIng command from ServerA, ServerB was
pinged instead of  ServerA.

A problem with the Domain name resolver, which arose on Communications
Servers on which the maximum number of sessions was being held, has
been  corrected.

Previously, for example, if a CS/20 had the maximum number of
sessions, and you  entered the Name or Connect command, the Domain
name resolver did not respond  and the following error message was
displayed:

 No memory resource

Even if the number of sessions was reduced, the Domain name resolver
still did not  respond.

The system no longer crashes if you perform the following sequence of
steps:

 - Enter the Connect command
 - Enter the ECM Character to escape to command mode
 - Set the BReakAction parameter to Ignore and the BreakChar parameter
   to   ^C
 - Resume the session
 - Hold the Control and C keys down simultaneously

Limitations

Version 3.0 has the following limitations:

You can change the virtual port configurations with the SETDefault
command only  on the first virtual port on your Communications Server.
If you attempt to change  other virtual port configurations with this
command, the following error message is
displayed:

 Portid out of range

Also, if you change the configurations for the first virtual port, you
must enter the  ReaD command before the changes can take effect.
These changes take effect on all  virtual ports.

You cannot execute commands that specify the Internet address of a
destination  server port number that is the same as the address of the
destination server itself.

For example, if the port number address 129.213.1.1 is defined on a
server with  the same address and you enter the following command:

 Listen 129.213.1.1

 the following error message is displayed:

 Invalid remote command

 Sysgen is not available on SW/20-TCP-NCS/150 Version 3.0.

Known Problems

SW/20-TCP-NCS/150 Version 3.0 has the following known problems:

When using the IEN116 Name Server, the command SHow (<name>) VERSion
does not function correctly if <name> is defined on a secondary name
server but  not on a primary name server.

If, when entering a macro, you press the Break key before the macro
input has been  fully entered, the portion of the macro that has been
entered is executed.   Consequently, an error message is usually
displayed.

To prevent this, after you press the Break key while typing a macro,
press the  Return key twice before entering the next command.

Documentation

The following manuals are shipped with SW/20-TCP-NCS/150 Version 3.0:

 TCP/IP Connection Service User's Guide (3/89)
 (Part Number: 09-0173-00)

 Network Management Guide (9/87)
 (Part Number: 09-0067-02)

 Getting Started Guide (2/87)
 (Part Number: 09-0043-01)

 Configuration Guide (2/88)
 (Part Number: 09-0093-01)

 TCP/IP Connection Service Quick Reference Guide (3/89)
 (Part Number: 09-0165-00)

For more information on network planning, refer to the following:

 CS/1 Installation Guide (10/87)
 (Part Number: 09-0117-00)

 LAN Planning Guide (2/88)
 (Part Number: 09-0085-01)

 NCS/150 Installation and Operation Guide (4/86)
 (Part Number: 09-0071-00)

If you have any questions, contact your network supplier or 3Com for
help.

Trademarks

UNIX is a registered trademark of AT&T Bell Laboratories.

3Com Corporation
