Ref: 99980095
Title: SW/200-TCP-CS/210 Version 20100
Date: 8/1/88

Copyright 3Com Corporation, 1991.  All rights reserved.

Enclosed is a distribution diskette containing SW/200-TCP Version
20100 (part number: 83-0102-01), which is to be used on the CS/
210.

This release memo contains the instructions for making a copy of
the distribution diskette.  It also describes the new features
and bugs fixed since SW/200-TCP Version 20000.

.h1;Compatibility

SW/200-TCP 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 Version 20100    F2 MMON 01D
                                         or later

.h1;Software Copy

Before you run SW/200-TCP Version 20100 on the CS/210, you should
make a copy of the distribution diskette using the following
procedure.  Press the Return key after typing each command
described below.

1.  Attach a terminal to port 0 of the CS/210.

2.  After you make sure that there is no diskette in the disk
drive, power on the CS/210.  Then the Self Test LED turns on.


3.  After the Self Test LED turns off, the Boot State LED lights
briefly.  After the Boot State LED turns off, the Self Test
LED flashes on and off.  Press the hardware interrupt switch
on the CS/210.  For further information on the location and
operation of the hardware interrupt switch, refer to section
2 of the Series/200 Installation Guide.

4.  Press the Return key.  The monitor prompt (>) appears.

5.  Perform firmware configuration on the CS/210 if necessary.
Otherwise, go on the the next step.

Refer to section 3.8 of the Series/200 Installation Guide for
further information on firmware configuration.  After
firmware configuration, return to the monitor prompt (>).

6.  At the monitor prompt (>), enter the following command to
make a copy of the distribution diskette:

    co <n>

where n the the number of copies to be made.

7.  The following message appears on the screen:

    insert master and hit return key

Insert the SW/200-TCP Version 20100 diskette in the disk
drive.  Then press the Return key.

The following messages appear on the screen if the read
completes successfully:

    reading ... OK
    insert copy 1 and hit return key

In the actual display, the number in the message may vary
according to the number of copies you have made.  If the
message "read error" appears instead of the message "OK",
contact an authorized 3Com service representative for
assistance.

8.  Remove the SW/200-TCP distribution diskette from the disk
drive.  Insert a blank, 135 TIP, double-sided, double-
density, 3 1/2 diskette in the disk drive.  Then press the
Return key.

9.  If the copy completes successfully, the following messages
appear on the screen:

    formatting ... writing ... verifying ... OK
    copy completed

Remove the diskette from the disk drive, and label it "SW/200-
TCP Version 20100".  Store the distribution diskette in a
safe place.  You can now use the newly created diskette on
your system.

                      ** NOTE **

A valid Internet address must be assigned to the CS/210
before it can be booted and connected to the network.  Use
the Sysgen program to set the Internet address.  For further
information on the Sysgen program, refer to the following
section and the Configuration Guide.

.h1;Sysgen

Sysgen is available for the CS/210 running SW/200-TCP Version
20100 and is necessary to assign an Internet address to the CS/
210.  The Sysgen parameters and default values for the CS/210 are
the same as for the CS/200 booted from an NCS/2 or NCS/AT.  Refer
to the sections on the CS/200 in the Configuration Guide
(February 1988 edition) for further information on the Sysgen
program.

To start the Sysgen program, follow these steps:

1.  Attach a terminal to port 0 on the CS/210.

2.  After you make sure that there is no diskette in the disk
drive of the CS/210, power on the CS/210.  Then the Self Test
LED turns on.

3.  After the Self Test LED turns off, the Boot State LED lights
briefly.  After the Boot State LED turns off, the Self Test
LED flashes on and off.  Press the hardware interrupt switch
on the CS/210.  For further information on the location and
operation of the hardware interrupt switch, refer to section
2 of the Series/200 Installation Guide.

4.  Press the Return key.  Then the monitor prompt (>) appears.

5.  Perform firmware configuration if necessary.  Otherwise, go
on to the next step.

Refer to section 3.8 of the Series/200 Installation Guide for
further information on firmware configuration, return to the
monitor prompt (>).

6.  Insert in the disk drive the SW/200-TCP Version 20100
diskette that you created in the software copy procedure.

7.  At the Monitor prompt (>), enter the following command to
invoke the Sysgen program:

    bt 1d

8.  The Sysgen program is invoked, and the Main Menu is
displayed.  Refer to the Configuration Guide for further
information on the Sysgen program.

.h1;New Features

The following features, which were not present in SW/200-TCP
Version 20000 or earlier, have been implemented in SW/200-TCP
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 operation
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
Version 20000 but have been fixed in SW/200-TCP 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 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.

.h1;Documentation

The following manuals provided with SW/200-TCP-CS/210:

*   Connection Service User's Guide for XNS and TCP/IP Protocols
    (6/88)
    Part Number: 09-0145-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

For related information, refer to the manuals listed belows:

*   Series/200 Installation Guide (6/88)
    Part Number: 09-0151-00

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

If you have any questions, please contact an authorized 3Com
service representative for assistance.

