Ref: 99980096
Title: SW/200-TCP-NCS/150 Version 20100
Date: 4/25/88

Copyright 3Com Corporation, 1991.  All rights reserved.

This release memo contains the instructions for installing
software on the NCS/150.  It also describes the new
features and bugs fixed since SW/200-TCP-NCS/150 Version
20000.

.h1;Compatibility

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

    NCS/150 running SW/150-TCP-NCS Version 11000 or later
    NCS/AT running SW/AT-NCS Version 11000 or later
    NCS/2 running SW/2-NCS Version 10000 or later
    CS/1 running SW/1-TCP Version 20000 or later
    CS/1 running SW/20-TCP Version 20000 or later
    CS/1-SNA running SW/1-T-SNA Version 13000 or later
    CS/50 running SW/50-TCP Version 13010 or later
    CS/100 running SW/100-TCP Version 20000 or later
    GS/1-IP running SW/20-IP-X.25 Version 10000 or later
    GS/3-IP running SW/3-IP Version 10000 or later
    IVECS running SW/IVECS-TCP Version 13010 or later
    Personal Computer running TCPTerm Version 10010 or later
    Personal Computer running SW/1-PCS Version 10010 or later

The following table illustrates the hardware and firmware
compatibility for SW/200-TCP Version 20100.

           Hardware/Firmware Compatibility
---------------------------------------------------------
 Product              Software                     Firmware

 CS/210   SW/200-TCP-NCS/150 Version 200100   F2MMON 01D or later

 CS/200   SW/200-TCP-NCS/150 Version 20100    C1MMON 01C or later

CS/200-B  SW/200-TCP-NCS/150 Version 20100    D2MMON 00B or later


.h1;Software Installation

Use the following steps to copy SW/200-TCP-NCS/150 Version 20100
from the distribution diskette to the SW/150-NCS diskette.  Press
the Return key after entering each command.

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

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

3.  After the NCS/150 is finished booting, press the following
sequence on the keyboard:

    <RETURN>.<RETURN>

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

    ls -lx /BIN

This command displays the list of software images currently
available on the SW/150-NCS diskette.

5.  Because the NCS/150 diskette can contain software images for
two product types only, it may be necessary to remove
software from the diskette to make room the the CS/200 file.
This can be done by typing "rm <filename>".

6.  If a cs200x file already exists, remove it by typing:

    rm /BIN/cs200x

7.  Perform a file system check with the compact option by
entering the following command:

    fsck -c

8.  Create a CS/200 file on the SW/150-NCS using the following
command:

    cr /BIN/cs200x 1f0 rwx 101000

9.  To copy the file, enter the following command:

    cf #0 /BIN/cs200x

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

11. When the system prompts for the destination diskette, replace
the SW/200-TCP-NCS/150 Version 20100 diskette withe the NCS/
150 diskette.  Then press the Return key.  The copying
process is finished when this message is displayed:

    Copy completed

                    ** NOTE **

The SW/200-TCP-NCS/150 diskette is a double-sided, double
density, 48 TPI diskette.  Copies of the SW/200-TCP-NCS/150
diskette can be made on MCPU-based Series/1 hardware only.

The CS/210 or CS/200 must be bound to the NCS/150 before it can
be booted from the NCS/150.  For the binding procedure, refer to
the NCS/150 Installation and Operation Guide.

                    ** NOTE **

If you need to press the Reset switch on the CS/210, do so
only when the prompt (e.g., Monitor prompt, Remote prompt) is
displayed on the screen.  Pressing the Reset switch before
the prompt appears may yield unpredictable results.

.h1;New Features

The following features, which were not present in SW/200-TCP-NCS/
150 Version 20000, have been implemented in SW/200-TCP-NCS/150
Version 20100:

1.  SW/200-TCP Version 20100 can be used on the CS/210, which
supports the 3 1/2-inch floppy disk drive.  The CS/210 can
now be booted from the local diskette.  It can also store to
and retrieve from the local diskette the macros,
configurations, and global parameters.

Firmware configuration can be done on the CS/210 to determine
whether it will be booted from the local diskette or a
Network Control Server.  The boot source determines the
origin of the macros, configurations, and global parameters.
For more information about firmware configuration, refer to
the Series/200 Installation Guide dated June 1988.

2.  The LongBReakAction port parameter now works for ports
configured as Host and ports configured as Terminal.

3.  The XmitBinary parameter, which is a Telnet port parameter,
now works for ports configured as Host and ports configured
as Terminal.

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

    SHow (!<port number>) SESion M

For example, if you enter this command:

    sh (!1) ses m

the screen display generated is similar to the following:

    CONCTD from 192.002.013.004:002:024

This display shows that port 1 of the host server is
connected from the terminal server whose Internet address is
192.003.013.004.  The number 024 is the number of the
physical port on this terminal server used in this
connection.  The number immediately following the Internet
address ("002" in this example) has no meaning and should be
disregarded.  This feature works only if the server is a
Communications Server manufactured by 3Com.

5.  The FlowControlFrom and FlowControlTo parameters can be set
to ENQ-ACK.  Hewlett-Packard terminals and hosts use this
flow control method.

.h1;Bugs Fixed

The following is a list of problems that existed in SW/200-TCP-
NCS/150 Version 20000 but have been fixed in SW/200-TCP-NCS/150
Version 20100:

1.  The "SHow NAmes*" command is no longer allowed when NsType is
set to DOMAIN.  Previously, the system might crash when
responding to this command.

2.  Previously, when there were more than three of four permanent
virtual circuits on a single server, the reliability of these
circuits was reduced.  This problem no longer exists.

3.  A problem that eliminated "keep-alive" TCP packets could
cause one end of a connection to remain indefinitely when the
server on the other end had been rebooted.  This has been
fixed.

.h1;Limitations

The following is a list of limitation of SW/200-TCP Version
20100:

1.  At the time when the CS/210 running SW/200-TCP makes a
connection, the routes are established using the default
gateway.  Changing the default gateway after connection does
not affect the already established routes.

You can however, use the ZeroArp command to clear out the
gateway table stored in the server.

2.  Macros are cached in local memory on the CS/200.  If you
change or delete a macro, there is no guarantee that the
change will flush the macro cache.  This can cause unexpected
results when macros are executed.  To ensure proper exectuion
of macros, use the ZeroMacro command to explicitly flush the
local cache after changing or deleting a macro.

If the CS/200 receives file service, which includes macro
file service, from an NCS, it is recommended that you flush
the macro cache in each Communications Server bound to the
NCS every time a macro is changed or deleted on the NCS.  If
an NCS/150 is providing the file service, use the REMOTE
command to access each CS/200 bound to the NCS/150, and then
use the ZeroMacro command on each CS/200 to flush the macro
cache.  If an NCS/2 or NCS/AT is providing the file service,
use the oneachserver utility on the NCS.  For example, at the
utility prompt of the NCS/AT or the NCS/2, enter the
following command:

    oneachserver -B zm

.h1;Known Problems

The following is a list of known problems in SW/200-TCP-NCS/150
Version 20100:

1.  If the remote end of an inactive session is disconnected, the
SHow SESions and SHow AllSessions commands still show that
the local end is connected.  The disconnection message
appears only if a user resumes that session.  This problem
does not occur on an active session.

2.  When you use the IEN116 Name Server, a network manager
command (e.g., SHow (<name>) VERSion) does not operate
correctly if <name> is not defined on a primary name server
and a secondary name server is defined.  In this case, the CS/
210 may crash.

3.  When an invalid name is passed to the domain name resolver,
"(primary)" is appended to the error message although it is
not necessary.

For example, if the following command with the invalid name
is entered:

    sh na a..b

the following message appears:

    Resolving...Resolver: improper name (primary)

4.  Sometimes the "improper name" error message is not ended with
a return character.  As a result, the prompt appears on the
same line as the error message.

For example, if the following command with the invalid name
is entered:

    connect a..b

the following appears on the screen:

    Connecting...Resolver: improper namesCS/200T>

In this example, "CS/200T>" is the prompt.

5.  The "SHow NAmes*" command is not allowed.  A name must be
supplied to the command.

6.  Pressing the Break key during disk access may yield
unpredicatable results.  For example, after entering the "sh
macros" command, if you press the Break key before the system
returns the results and then you enter the "sh confs"
command, a list of macro names is still displayed, instead of
a list of configuration file names.

7.  After a fatal error occurs on the CS/210, the attempt to
upload the image from the CS/210 to the NCS yields unpredict-
able results if the firmware configuration parameter Auto-
reboot has been set to "Upload then reboot."  To avoid this
problem perform firmware configuration to set the parameter
to either "Reboot only" or "Boot monitor."  Setting the
parameter to "Boot monitor" allows you to save memory dump on
a diskette after the CS/210 has crashed.

.h1;Documentation

Refer to the following manuals for information on the CS/200,
CS/210 and network planning:

*   Series/200 Installation Guide (6/88)
    Part Number: 09-0060-02

*   Connection Service User's Guide (11/87)
    Part Number: 09-0063-02

*   Connection Service User's Quick Reference Guide (12/85)
    Part Number: 09-0062-00

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

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

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

*   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, please contact an authorized Bridge
service representative for assistance.

