Ref: 99980122
Title: SW/200-TCP-NCS/150 Version 20000
Date: 11/18/87

Copyright 3Com Corporation, 1991.  All rights reserved.

Enclosed is a distribution diskette containing SW/200-TCP-NCS/150
Version 20000, which runs on both the CS/200 and CS/200-B.  These
Communications Servers can be booted from an NCS/150.

This diskette is your distribution copy of the software and
should be used only to copy the software onto the NCS/150.

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

.h1;Compatibility

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

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


Table 1 illustrates the hardware and firmware compatibility for
SW/200-TCP-NCS/150 Version 20000.

__________________________________________
| Table 1  Software/Firmware Compatibility|
|_________________________________________|
|                                         |
|  Product      Software       Firmware   |
|                                         |
| CS/200       SW/200-TCP-   C1MMON 01C   |
|              NCS/150       or later     |
|                                         |
| CS/200-B     SW/200-TCP-   D2MMON 00B   |
|              NCS/150       or later     |
|_________________________________________|

.h1;Software Installation

Because the CS/200 is a diskless unit, it must be supported by a
Network Control Server.  You must copy SW/200-TCP-NCS/150 Version
20000 from the distribution diskette to the SW/150-NCS diskette
using the following steps:

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.

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 for 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 1dc 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-NCS/150 Version
20000 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 20000 diskette with
the NCS/150 diskette. Then press the Return key.  The
copying process is finished when this message is displayed:

     Copy completed

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

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

.h1;NewFeatures

The following features, which were not present in SW/200-TCP-
NCS/150 Version 13010, have been implemented in SW/200-TCP-
NCS/150 Version 20000.  For detailed information on the features,
examples, and screen displays, refer to the Connection Service
User's Guide.

1.  A new User Interface command, PIng, is available to
generate an Internet Control Message Protocol (ICMP) echo
request message to a specified host.

The abbreviation for the PIng command is "PI"; a single "P"
character is the abbreviation for the Pause command.  If
the echo request message is sent to a Communications Server
running software version 13010 or earlier or a host that
does not handle ICMP echo requests, the following message
will appear: PINGing ... Host is not responding

2.  SW/200-TCP-NCS/150 Version 20000 now handles and responds
to appropriate incoming ICMP messages.

3.  The CS/200 now processes Internet packets with Internet
option information.

4.  The CS/200 now reassembles fragmented Internet packets.

5.  A new parameter, NetMapBroadcast, has been added to
SW/200-TCP.  It controls the transmission of netmap
broadcast packets from the CS/200.

6.  SW/200-TCP-NCS/150 Version 20000 supports a receive window
size of 1024 bytes to increase efficiency during large-
scale data transfers.

7.  In addition to cleaning up the contents of the ARP table,
the ZeroArp command clears out the gateway table stored in
the server.

8.  A new global parameter, MacType, has been added.  Its
possible values are IEEE and Enet.

This parameter determines the protocol used at the Media
Access Control (MAC) level.  The default value is Enet,
which is compatible with other Bridge Ethernet and
Broadband products.  IEEE refers to the use of the 802.3
and SNAP protocols.

9.  If another Communications Server or any host on the network
has the same Internet address as the server to which you
are connected, it is considered an address collision.

Previously, address collisions were not reported.  Now the
SHow ARptable command displays a modified arptable
indicating addresses that are involved in a collision.

Also, after an address collision, the audit trail record
shows the Internet address and Ethernet address of the
Communications Server or host that causes the collision.
The type of this audit trail record is "AC".

The format for the audit trail record generated after an
address collision is as follows: MM.DD HH.MM.SS
III.III.III.III  AC  CCC.CCC.CCC.CCC %08000200HHHH In the
audit trail record above, "AC" is the type of the record.
"III.III.III.III" is the source Internet address.
"CCC.CCC.CCC.CCC" and "%08000200HHHH" are the Internet
address and Ethernet address that cause the collision.

10.  It used to be difficult to identify the connect/disconnect
pair in an audit trail record for a given session.  Now the
connect and disconnect audit trail records indicate the
port numbers and session numbers to identify the pair.

Also, the CF (Connect Fail) audit trail record is generated
for a connect request that contains more than one address
in the address list.

The new format of the Connect audit trail record is as
follows.  MM.DD HH.MM.SS III.III.III.III.  N NN CD
CCC.CCC.CCC.CCC The new format of the Disconnect audit
trail record is as follows: MM.DD HH.MM.SS III.III.III.III.
N NN DC CCC.CCC.CCC.CCC In the audit trail records above,
"N" is the session number, and "NN" is the port number.

11.  The Connect command has been modified to allow the
Precedence level and Type of service parameters to be
specified.  It also allows specification of multiple
addresses and the destination TCP port number.

12.  Previously, setting the LongBreakAction parameter to InBand
or OutofBand did not generate actions.  Now if you set
BreakAction to InBand or OutofBand, it will generate Telnet
signals exactly the same as BReakAction.

13.  A new session parameter, XmitBinary, is implemented.  Its
default value is OFF, which is for the transmission of
seven-bit ASCII data.  If XmitBinary is ON, it allows you
to have an eight-bit data path in your Telnet session with
the host.  However, this is possible only if the DataBits
parameter is 8.

14.  SW/200-TCP-NCS/150 Version 20000 supports a domain name
resolver, which can be used to translate names to Internet
addresses.  A new global parameter, NsType, has been added.
Its possible values are IEN116 and DomainName.  It
determines whether the domain name resolver or the IEN116
name service is used for address translation.

When the NsType parameter is set to DomainName, the syntax
for the SHow NAme command is as follows: SHow Name [<Domain
name>] [* [.] [<Target>]]

15.  Because space in the UI globals file has been allocated new
global parameters, the Internet address information has
been moved from the globals file to a newly created file.

If you use an NCS as the file server, you may notice a file
called "/GLOBALS/ipadr.C009C8D0", where C009C8D0 is an
example of the Internet address of the CS/1.  It is created
when SW/200-TCP-NCS/150 Version 20000 is booted for the
first time.  This change has no effect on your interface
with the CS/200.

16.  A new command, RFM, is implemented to enable the network
manager to enter commands to the RFM/5 on a broadband
network.

17.  A new option, DataGeneral, has been added to the DeVice
parameter.  This option puts the terminal in Data General
mode, in which both the Bridge User Interface and the
Serial I/O module's operations are altered.

18.  LF is now treated as a command delimiter for the Bridge
User Interface.  Therefore, both CR and LF will be
recognized as the end of the command line.

19.  You can define macros that contain conditional statements
on the CS/200 running SW/200-TCP-NCS/150 Version 20000.

20.  The SHow AllSession command displays a list of names (and
optionally physical addresses) to which the terminal ports
are connected.

The command also shows the address of the other end of the
connection when it is a passive-end connection or an
interconnection.

21.  Data is usually folded modulo 128 for control character
detection.  However, on some eight-bit extended ASCII
terminals, control characters such as XON and XOFF have
unique representations within the 256-character set.  They
should not be folded before being sent to the User
Interface or being recognized by the SIO processor.

SW/200-TCP-NCS/150 Version 20000 enables you to override
the data folding by setting PARIty to a new option called
DoNotFold.  You can select this option in conjunction with
None, Even, or Odd parity.  For example, you can type: setd
PARIty = Even DoNotFold Because of this new option, it is
now possible to use eight-bit control characters with or
without parity.  The DoNotFold option, however, should be
used only when the DataBits parameter is set to 8.  To
reset the special PARIty option, type: setd PARIty = 0 When
the DoNotFold option is set, the control characters sent
over the network from the CS/200 are taken to be eight bits
long.  Only a single character is recognized as ECM, BREAK,
XON, XOFF, or EDIT.

For example, with the DoNotFold option, the character
encoded as 00010001 will be recognized as XON, and the
character encoded as 10010001 will be passed as data.
Without the DoNotFold option, both bit patterns will be
interpreted as an XON character, because the uppermost bit
is ignored.

22.  SW/200-TCP-NCS/150 now supports universal time for network
communications spanning different time zones.  Two new
global parameters have been implemented to support this
feature.

The DaylightSavingsTime parameter specifies the
displacement, in minutes, from non-Daylight Savings Time.
The TimeZone parameter specifies the displacement, in
minutes, west of Greenwich the server's site is located.

However, the NCS/150 does not support this feature.  It is
recommended that the time on the CS/200 be kept in Pacific
Standard Time.

23.  A new global parameter, AUditTrailType, is implemented.  It
specifies the format of the time-stamp for audit trail
messages.  The two formats are Local time and Universal
time.

.h1;Bugs;Fixed

The following problems, which were found in SW/200-TCP-NCS/150
Version 13010 or earlier, have been fixed in SW/200-TCP-NCS/150
Version 20000:

1.  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.

2.  Previously, if the ECHOMask included control characters,
some characters (e.g., backspace) did not function normally
in Command mode.  SW/200-TCP-NCS/150 Version 20000 has
fixed this problem.  If you include a control character in
the ECHOMask, type "res" and then enter the ECM character.
Editing in Command mode will return to normal.

3.  Previously, when a host was flow-controlled, a terminal,
even in Command mode, would not function after you had
entered four or more characters from the keyboard.  It
would be locked up until the host terminated the flow
control or the network manager used the Listen command on
the port.

Now, if the same situation occurs, you can enter the ECM
character to continue the operation of the terminal,
because the ECM character will be processed as an out-of-
band signal.

4.  A problem that previously caused a connection to jam and
CS/200s to infinitely exchange old packets has been
corrected.

5.  Several problems relating to stalling during data transfer
have been fixed.

6.  The retransmit alarm now functions correctly to ensure
proper connections.

7.  The SHow STAT <Hour> command displays statistics for the
time specified.  Previously, the displayed statistics were
for one hour earlier than the time requested.

8.  If BReakAction is set to InBand, the break signal from your
keyboard will be mapped to the Telnet interrupt process
(IP) signal.  If it is set to OutofBand, it will be mapped
to the Telnet break signal (BREAK).  If it is set to both
InBand and OutofBand, both the IP signal and BREAK are
generated.

9.  When set to CTSRTS, the FlowControl parameters now cause
the transmit data stream to stop within three byte times
instead of one packet time.

.h1;Limitations

The following are the limitations of SW/200-TCP-NCS/150 Version
20000:

1.  At the time when a connection is made, 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.  The increase in size of the software image may lead to
reduced disk space on the SW/150-NCS diskette.  This limits
the number of macros and names that can be defined.

.h1;Known Problems

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

1.  If the remote end of an inactive session is disconnected,
the SHow SESsions and SHow AllSessions commands still show
that the local end is connected.  The disconnection message
only appears 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) will not operate
correctly if <name> is not defined on a primary Name Server
but on a secondary Name Server.  In such a case, the CS/200
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 will appear:
Resolving...Resolver: improper name (primary)

4.  Sometimes the "improper name" error message may not be
terminated with a carriage return.  As a result, the prompt
will appear 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 response will appear
on the screen: Connecting...Resolver: improper namecs/200t>
In this example, "cs/200t>" is the prompt.

.h1;Documentation

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

 + Series/200 Installation Guide (6/87)
 (Part number: 09-0060-01)

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

 + 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 (1/87)
 (Part number: 09-0093-00)

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

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