Ref: 09720002
Title: Release Note: CS/100 booting from NCS/150 ver. 20000
Date: 11/17/87

Copyright 3Com Corporation, 1991.  All rights reserved.

Enclosed is a software distribution diskette containing SW/100-
TCP-NCS/150 Version 20000 for use with CS/100s that are booted
from an NCS/150.

This memo describes the procedure for installing the software,
the new features of, and bugs fixed in this version of SW/100-
TCP-NCS/150.

Compatibility

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

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

Table 1 illustrates the firmware and software compatibility of
SW/100-TCP-NCS/150 Version 20000:

______________________________________________________
|       Table 1  Software/Firmware Compatibility      |
|_____________________________________________________|
| Product|       Software     |        Firmware       |
|        |                    |                       |
|        |                    |     SIO         MP    |
|        |                    |                       |
| CS/100 |  SW/100-TCP-NCS/150|  T0ASYN 1B   T1MMON 2A|
|        |                    |  or later    or later |
|________|____________________|_______________________|


Installation

If you wish to sysgen SW/100-TCP-NCS/150 Version 20000, the
sysgen should be performed on the CS/100 disk-based unit using
the distribution diskette before installing SW/100-TCP-NCS/150
Version 20000 on the SW/150-NCS-TCP diskette.  If several CS/100s
are booted from the NCS/150, they all share the same sysgenned
CS/100 software.

If you upgrade your system to SW/100-TCP-NCS/150 Version 20000
and you do not have a backup copy of your current SW/150-NCS-TCP
diskette, it is recommended that you make a backup copy before
the installation.  Refer to Section 4.6.3 of the NCS/150
Installation and Operation Guide for the disk copy procedure.

Because SW/100-TCP-NCS/150 runs on CS/100s that are booted from
an NCS/150, you must install the software on the SW/150-NCS-TCP
diskette, using the following procedure:

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

2.  Insert the SW/150-NCS-TCP-UTIL diskette in the NCS/150 disk
drive.

3.  Press the Reset switch.

4.  When the NCS/150 has finished booting, press the following
sequence on the keyboard: <RETURN>.<RETURN>

5.  Remove the SW/150-NCS-TCP-UTIL diskette, insert the
SW/150-NCS-TCP diskette in the disk drive, and enter the
following command: rm /BIN/cs100x This removes any existing
cs100x file.  If the error message "File not found" appears
on the screen, disregard it.

6.  Perform a file system check by entering the following
command: fsck -c

7.  Create a cs100x file on the SW/150-NCS-TCP diskette using
the following command: cr /BIN/cs100x 19a rwx 240000

8.  To ensure that the file is created properly, enter the
following command: ls -lx /BIN/cs100x You should see the
following display on the screen:
0240000....33400..date../BIN/cs100x If the above display
does not appear, enter "rm /BIN/cs100x" to remove the
cs100x file, then go back to Step 6.

9.  To copy the software image from the SW/100-TCP-NCS/150
Version 20000 diskette to the newly created cs100x file on
the SW/150-NCS-TCP diskette, enter the following command:
cf #0 /BIN/cs100x When the system prompts for the source
diskette, remove the SW/150-NCS-TCP diskette.  Insert the
SW/100-TCP-NCS/150 Version 20000 distribution diskette and
press the Return key.

When the system prompts for the destination diskette,
insert the SW/150-NCS-TCP diskette and press the Return
key.  When the copying process is finished, the following
message appears on the screen: copy completed

10.  Remove the SW/100-TCP-NCS/150 distribution diskette and
store it in a safe place.

11.  Before the CS/100 can boot from the NCS/150, it must be
bound to the NCS/150 by the BInd command. Refer to the
NCS/150 Installation and Operation Guide for information on
the binding procedure.

New Features

The following features, which were not present in SW/100-TCP-
NCS/150 Version 13000 or earlier, have been implemented in
SW/100-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.  If the echo request
message is sent to a Communications Server running software
version 13000 or earlier, or a host which does not handle
ICMP ECHO requests, the following message will appear:
PINGing ... Host is not responding

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

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

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

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

6.  SW/100-TCP-NCS/150 Version 20000 supports a receive window
size of 1024 bytes to facilitate 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 as well.

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.  A new sysgen parameter, the Skip Dead Ports parameter, has
been added to the Virtual Terminal Parameters menu in the
sysgen program.  This parameter determines how a host
server processes a connect request.

The host enables a port by keeping the Data Terminal Ready
(DTR) signal raised.  If the Skip Dead Ports parameter on
the host server is 1, the host server will repeat the
connect request when a port with DTR low is encountered.
The request will be repeated until an enabled port is found
or all rotary ports have been tried.  If the parameter is
set to 0, a connection request is considered to have failed
as soon as a disabled port is encountered.

The default value of this parameter is 1.

10.  If another Communications Server 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.

11.  A new sysgen parameter called Maximum Number of SYNC
Retransmissions has been implemented.  It determines the
length of time within which a CS/100 will try each entry in
a global rotary.

The parameter can be altered on the TCP Parameter menu.
The default value is 4, the minimum 2, and the maximum 20.

The more unreliable your network, the greater the Maximum
Number of SYNC Retransmissions should be.

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

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

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

15.  A new session parameter, XmitBinary, is implemented.  Its
default value is OFF, which limits transmission to 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 set to 8.

16.  SW/100-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.

Related to the NSType parameter is the NameServer
parameter, which is a new kernel parameter in the Sysgen
program.  Its possible values are 0, which selects the
IEN116 name service, 1, which selects the Domain name
service, and 2, which allows both to be used as the name
service.  If the value is 0 or 1, you cannot change the
name service by setting the NsType parameter.  Only when
NameServer is 2 can you use NsType to select the name
service for resolving names.

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

17.  Because space in the UI globals file has been allocated to
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/100.  It is
created when SW/100-TCP-NCS/150 Version 20000 is booted for
the first time.  This change has no effect on your
interface with the CS/100.

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 containing conditional statements on
the CS/100 running SW/100-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/100-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/100 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.

This feature only functions with CS/100 boards equipped
with T0ASYN Revision 18C or later.

22.  SW/100-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 and NCS/AT do not support this
feature.  If you have an NCS on the network, it is
recommended that the time on the CS/100 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.

Bugs Fixed

The following problems, which were found in SW/100-TCP-NCS/150
Version 13000 or earlier, have been fixed in SW/100-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/100-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 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.

This feature only functions on CS/100 boards equipped with
T0ASYN Revision 18C or later.

4.  A problem that previously caused a connection to jam and
CS/100s 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 BReakAction is set to OutofBand, it will
be mapped to the Telnet break signal (BREAK).  If
BReakAction is set to both InBand and OutofBand, both the
IP signal and BREAK are generated.

Limitations

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

1.  The increase in size of the SW/100-TCP-NCS/150 software
image may reduce the maximum number of sessions in the
CS/100, depending on the data link configurations.

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

Known Problems

The following is a list of known problems in SW/100-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/100
may crash.

Documentation

For further information on the CS/100 and network planning, refer
to the following manuals:

LAN Planning Guide (9/86)
(Part Number: 09-0085-00)

Series/100 Installation Guide (10/85)
(Part Number: 09-0023-02)

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

Configuration Guide (1/87)
(Part Number: 09-0093-00)

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

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

