Ref: 99960039
Title: ESD Release Note SW/200-TCP-NCS/150 v.3.0 - Part # 86-0075-00
date: 04-20-89

Copyright 3Com Corporation, 1991.  All rights reserved.

.BR;3Com Corporation
.BR;Software Release
.BR;SW/200-TCP-NCS/150 Version 3.0
.BR;March 20, 1989

Part Number: 86-0075-00
Revision: 05

.BR;TO:  CS/200 and CS/210 Users
.BR;FROM: 3Com Corporation
.BR;SUBJECT: SW/200-TCP-NCS/150 Version 3.0
.BR;DATE: March 20, 1989

Enclosed is a distribution diskette containing SW/200-TCP-NCS/150
Version 3.0 (Part Number: 83-0102-00) for use with your CS/200 or
CS/210 that is booted from an NCS/150.

This release memo describes the procedure for installing SW/200TCP-
NCS/150 Version 3.0 on the NCS/150.  It also lists the new features,
bugs fixed, known problems, and limi tations in this version of
SW/200-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/200-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/1 running SW/20-TCP Version 3.0 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.

Table 1 illustrates the hardware and firmware compatibility
requirements of SW/200-TCP-NCS/150 Version 3.0.

Table 1 Hardware/Firmware Compatibility

Product Software      Firmware

CS/210 SW/200-TCP-NCS/150 Version 3.0   F2 MMON 01D
         or later
CS/200 SW/200-TCP-NCS/150 Version 3.0   C1 MMON 01C
         or later
CS/200-B SW/200-TCP-NCS/150 Version 3.0   D2 MMON 00B
         or later

** 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 Series/200 server is booted from an NCS/150, install
SW/200-TCP-NCS/150 on the NCS/150.  To copy the software from the
distribution diskette to the SW/150-NCS-TCP diskette, follow these
steps:

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
only one or  two product types, it may be necessary to remove software
from the diskette to  make room for the file containing SW/200-TCP-
NCS/150 Version 3.0.  Because of  the increased size of this version
of the software, the SW/150-NCS-TCP diskette may be able to contain
only the file containing SW/200-TCP-NCS/150 Version 3.0.  Type "rm
<filename>" if you need to remove a file.

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

 rm /BIN/cs200t

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

 fsck -c

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

 cr /BIN/cs200t 222 rwx 101000

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

 cf #0 /BIN/cs200t

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

11. When the system prompts for the destination diskette, replace the
SW/200-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 Series/200 server is  not already bound to the NCS/150, you
should use the BInd command to enable  your
Series/200 server 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/200-TCP-
NCS/150, have been implemented in SW/200-TCP-NCS/150 Version 3.0.
Refer to the TCP/IP Connection Ser vice User's Guide for more
information on these features.

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

Communications Servers provide additional features to support Hewlett
Packard  devices.  These special features 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.

Bugs Fixed

Certain problems, which existed in previous versions of SW/200-TCP-
NCS/150, have been solved in SW/200-TCPNCS/150 Version 3.0.  These
problems and their resolutions are described 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.

Your Communications Server 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 alternative 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 fixed.

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
protocol 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 specification.

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

 Address cannot be broadcast at loopback.

Also, you must reassign existing Internet addresses that begin with
127.

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, if you entered the Name or Connect command on a CS/210 or
CS/200, on which the maximum number of sessions was being held, 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.

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 data forwarding problems when
Telnet was used in conjunction with the Berkeley 4.3 release of the
UNIX operating system.

A problem that arose when users connected via a dial-in modem to a
CS/200 or  CS/210 has been corrected.

Previously, for example, if user A failed to complete the autobaud-
autoparity  sequence, that is, <Return . Return>, and user B whose
terminal had a different  baud rate setting subsequently attempted to
connect to the same server, User B  could not make a successful
connection.  This was because the server failed to properly disconnect
User A.

The CS/210 or CS/200 running Version 3.0 can now reinitialize itself
in such  circumstances and successfully establish User B's connection.
However, in order  for it to do this, the UseDTR parameter must be set
to AsDCD and the DCD option on the modem must be set to drop the DCD
signal on disconnection.

The CS/210 or CS/200 no longer crashes if you do the following:

 - Enter the Connect command
 - Enter the ECM character
 - Set the BReakAction parameter to IGnore and the BReakChar parameter
   to ^C
 - RESume the session
 - Press and hold down the Control key and the "c" key simultaneously.

Limitations

Version 3.0 has the following limitations:

You cannot execute port specific 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 in SW/200-TCP-NCS/150 Version 3.0.

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.

Known Problems

SW/200-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/200-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:

Series/200 Installation Guide (6/88)
Part Number: 09-0151-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.
