Ref: 10420008
Title: Release Notes: CS/1 TCP booting from NCS/2 Version 20000
Date: 12-21-87

Copyright 3Com Corporation, 1991.  All rights reserved.

Software Release

SW/1-TCP-NCS/2 Version 20000

December 21, 1987

Part Number: 86-0140-00
Revision 00


TO:          CS/1 Users

FROM:        Bridge Communications, Inc.

SUBJECT:     SW/1-TCP-NCS/2 Version 20000

DATE:        December 21, 1987

Enclosed is a distribution tape cartridge containing SW/1-TCP-
NCS/2 Version 20000 for use with CS/1s that are booted from an
NCS/2.

This release memo describes the new features and the fixed bugs
in this version of SW/1-TCP.

Compatibility

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

.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/100 running SW/100-TCP Version 11000 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;NCS/2 running SW/2-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/1-TCP-NCS/2 Version 20000:''



_____________________________________________________________________________________
|                      Table 1  Firmware/Software Compatibility                      |
|____________________________________________________________________________________|
|      |             |                                                               |
|Produc|   Software  |                            Firmware                           |
|      |             |   SIO        MCPU         EC/1 or EC/2        IBC/M     TRC/M |
|______|_____________|_______________________________________________________________|
|      |             |         |           |                     |           |       |
|CS/1  |SW/1-TCP-NCS/|M0ASYN 15|M1MMON     |M0EDL1 4BM0EDL2 00A  |N/A        |N/A    |
|      |             |M0ASYN 17|01B or late|or later or later,   |           |       |
|      |             |or later |           |         or M1IECM 01|           |       |
|      |             |         |           |         or later    |           |       |
|______|_____________|_________|___________|_____________________|___________|_______|
|CS/1-T|SW/1-TCP-NCS/|M0ASYN 15|M1MMON     |N/A      N/A         |N/A        |No PROM|
|      |             |M0ASYN 17|01K or late|                     |           |       |
|      |             |or later |           |                     |           |       |
|______|_____________|_________|___________|_____________________|___________|_______|
|      |             |         |           |                     |           |       |
|CS/1-B|SW/1-TCP-NCS/|M0ASYN 15|M1MMON     |N/A      N/A         |M2IBCM     |N/A    |
|      |             |M0ASYN 17|01G or late|                     |00E or late|       |
|      |             |or later |           |                     |           |       |
|______|_____________|_________|___________|_____________________|___________|_______|

Hardware_and_Firmware_Requirements_for_SIO-16_Boards

The following requirements must be met if your CS/1 running
SW/1-TCP-NCS/2 Version 20000 is equipped with one or more SIO-16
boards:

+ The M1MMON PROM Rev. 01G or later is required on the MCPU
board.

+ An EC/2, TRC/M, or IBC/M board must be installed on the
CS/1.

+ If the CS/1 is equipped with three or four SIO-16 boards,
the MCPU board must be upgraded to 12 MHz.  If it is
equipped with one or two SIO-16 boards, a 10 MHz MCPU board
can be used.

Installation

If you upgrade your system to SW/1-TCP-NCS/2 Version 20000, it is
recommended that you make backup copies of the files in
/usr/NCS/GLOBALS.  This is because SW/1-TCP-NCS/2 uses a new
format for the files contained in this directory.  When you run
SW/1-TCP-NCS/2 Version 20000, these files are automatically
updated.  But if for any reason you want to use a previous
version of SW/1-TCP-NCS/2 later, the updated files in this
directory cannot be used.



Follow these steps to create backup copies of the files in
/usr/NCS/GLOBALS:

1.  Follow the instructions in the NCS/2 Installation and
Operation Guide to log in to the NCS/2.  A command prompt
appears on the screen after you have logged in.

2.  At the command prompt, enter utility mode by typing: ut

3.  Change the current directory to /usr/NCS by typing: cd
/usr/NCS

4.  Create a new directory for the backup files.  In the
following example, the name of the directory is OLDGLOBALS.
cp GLOBALS/* OLDGLOBALS

5.  After the copy process is finished, a new prompt appears.
Type the following command to exit utility mode: exit
Because SW/1-TCP-NCS/2 Version 20000 runs on CS/1s that are
booted from an NCS/2, you must install the software on the NCS/2
disk, using the procedure described in Section 6.3 of the NCS/2
Installation and Operation Guide.

The CS/1 must be bound to the NCS/2 by the BInd command before it
can boot from the NCS/2.  Refer to Section 8.2 of the NCS/2
Installation and Operation Guide for information on the binding
procedure.

New_Features

The following features, which were not present in SW/1-TCP
Version 13000 or earlier, have been implemented in SW/1-TCP
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 to a host that does not handle
ICMP echo requests, the following message will appear:
Pinging ... Host is not responding

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

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

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



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

6.  SW/1-TCP-NCS/2 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,
or 802.5 if a Token Ring network is used, and SNAP
protocols.

9.  A new sysgen parameter, Skip Dead Ports, 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 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 caused the collision.

Because it is possible for a Communications Server or a
host to have an address collision with a product not
manufactured by Bridge Communications, the Ethernet address
shown in an actual audit trail record may contain different
digits from those in the example shown above.

11.  A new sysgen parameter called Maximum Number of SYNC
Retransmissions has been implemented in SW/1-TCP-NCS/2
Version 20000.

This parameter specifies the length of time the CS/1 will
try an entry in a global rotary during a TCP connection
attempt.

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
if a connect request contains more than one address in the
address list and the connect attempt for each address
fails.  In this case, the audit trail record displays only
the first address in the list, which is adequate for you to
identify the connection attempt.

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

16.  SW/1-TCP-NCS/2 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 DOMAIN.  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 DOMAIN, the syntax for
the SHow NAme command is as follows: SHow Name [<Domain
name>] [* [.] [<Target>]]

17.  A new global parameter, DomainName, specifies the default
domain string for all domain names entered on the server.

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

As a result of this newly created file, you can now assign
an Internet address to each of the 64 ports on a
LanSwitch/1.  Previously, you could assign Internet
addresses to 32 ports.

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/1-TCP-NCS/2 Version 20000 is booted for the first
time.  This change has no effect on your interface with the
CS/1.



19.  Previously, an LS/1 could support up to 64 sessions.  With
SW/1-TCP-NCS/2 Version 20000, more sessions can be
supported.  Each entry in Table 2 indicates the maximum
number of sessions supported for each type of network
controller board in the MCPU-based CS/1 or LS/1. ''

________________________________________________
|     Table 2  Number of Sessions Supported     |
|_______________________________________________|
|                                               |
|            Network Controller Board           |
| EC/1   EC/2*    EC/2+**      IBC/M     TRC/M  |
|                                               |
|  32     64         96         96         96   |
|                                               |
|    *   EC/2 board with 256 kilobytes of memory|
|   **   EC/2 board with 512 kilobytes of memory|
|_______________________________________________|

EC/1 is not supported by the 64-port LS/1.

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

21.  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. The CS/1 can
operate in Data General mode only if it is equipped with
SIO-16 boards.

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

23.  You can now define macros that contain conditional
statements on the CS/1.  Samples of these macros are
provided on the SW/1-TCP-NCS/2 Version 20000 distribution
tape cartridge, and more information regarding them is
included in this release memo.

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

25.  A new parity option is available for SIO-16 boards.  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/1-TCP-NCS/2 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/1 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 is supported on SIO-16 boards and SIO-A boards
with M0ASYN Rev. 18C or later.

26.  SW/1-TCP-NCS/2 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, in minutes, how far west
of Greenwich the server's site is located.

However, the NCS/2 does not support this feature.  If you
have an NCS on the network, it is recommended that the time
on the CS/1 be kept in Pacific Standard Time.

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

28.  The SIO-16 board now supports control signals RTS (Request
To Send) and CTS (Clear To Send).  Previously, only the DTR
(Data Terminal Ready) and DCD (Data Carrier Detect) control
signals were supported.

If you want to use the RTS/CTS instead of the DTR/DCD
signals, you must use the SETDefault command to set the
FlowControlTo and FlowControlFrom parameters to CTSRTS on
the SIO-16 port.  Then you must alter the wiring of the
modular DB-25 (terminal/host) adapter according to Figure
1.



Figure 1  Modular DB-25 Terminal/Host Adapter Pin Assignments



Table 3 shows the correspondence between RS-232-C names and
Bridge names for the signals available on the DB-25
connector. ''

_________________________________________
|     Table 3  Correspondence between    |
|     RS-232-C Names and Bridge Names    |
|________________________________________|
|                                        |
| RS-232-C   Bridge        Function      |
|   Name      Name                       |
|    BA      TXD/     Transmit Data      |
|    BB      RXD/     Receive Data       |
|    CA      RTS      Request to Send    |
|    CB      CTS      Clear to Send      |
|    CC      DSR      Data Set Ready     |
|    AB      GND      Signal Ground      |
|    CF      DCD      Data Carrier Detect|
|    CD      DTR      Data Terminal Ready|
|________________________________________|

Bugs_Fixed

The following problems, which were found in SW/1-TCP Version
13000 or earlier, have been fixed in SW/1-TCP 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/1-TCP-NCS/2 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/1 boards equipped with
T0ASYN Revision 18C or later.



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

5.  Several problems related 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/1-TCP-NCS/2 Version
20000:

1.  The increase in size of the SW/1-TCP-NCS/2 software image
may reduce the maximum number of sessions in the CS/1,
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/1-TCP-NCS/2
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.  A CS/1-B, which is used on a broadband network, may fail to
read the configuration parameters for port 0.  If port 0
needs to be configured, Bridge recommends that you define



an initmacro for the CS/1-B that includes the command "read
(!0) dp 0".

3.  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, and a secondary Name Server is defined.  In such a
case, the CS/1 may crash.

Sample_Macros_with_Conditional_Statements

The SW/1-TCP-NCS/2 Version 20000 distribution tape cartridge
includes a package of files that provide sample macros containing
conditional statements.  If you want to examine these sample
macros, or if you want to edit and define these macros on your
system, follow the instructions below:

1.  Follow the instructions in the NCS/2 Installation and
Operation Guide to log in to the NCS/2.  A command prompt
appears on the screen after you have logged in.



2.  Before defining the sample macros on your system, be sure
that the names of these macros do not conflict with those
of the existing macros.

The following is a list of the names of the sample macros:

+ connect

+ connect.menu

+ disc

+ error

+ exit

+ get

+ login

+ m1

+ m2

+ master

+ master.menu

+ motd

+ newlogin

+ res

+ setup

+ term.menu

+ term.sel

If there are conflicts in macro names, you must rename your
current macros.

3.  Type the following command to enter utility mode: ut

4.  After the utility prompt appears, use the following command
to change directory: cd /usr/ncs/local

5.  Type the following to unpack the sample macros into
individual files: cmacsrcunpac This message, which is
followed by a list of the macro names, appears: unpacking
conditional macro source into /usr/ncs/local/cmac.src If
the above message does not appear and the system displays
the "command not found" message, enter the following
command: rehash Then after the utility appears again,
repeat this step.

6.  After the prompt appears, use the following command to
change directory: cd cmac.src

7.  Use a text editor (e.g., vi) to edit each file in the
cmac.src directory.  Editing is necessary because some
sample macros contain host names and terminal control
sequences that are not applicable to your site.

After you have edited a macro, you must delete unnecessary
spaces in the file so that each macro file does not exceed
256 characters.

8.  After you finish editing the macros in the cmac.src
directory, use the following command to change directory:
cd /usr/ncs/local

9.  After the prompt appears, type the following command:
macmkinstall This command creates a shell script file that
can be used to define the modified macros.  The following
message is displayed for each macro in cmac.src: installing
<name> where <name> is the name of the macro.

10.  After the prompt appears, type the following command to
define the macros: install.newmacs The following message is
displayed for each macro defined: macro <name> created
where <name> is the name of the macro.

11.  The process of creating the macros is finished when the
utility prompt appears again.  The macros are now on the
NCS/2, ready to be invoked.

12.  If you encounter problems with the sample macros and wish
to undefine them all, type the following command at the
NCS/2 utility prompt: /usr/ncs/local/cmacuninstall

Documentation

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

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

+ CS/1 Installation Guide (10/87)
(Part Number: 09-0117-00)



+ NCS/2 Installation and Operation Guide (11/87)
(Part Number: 09-0110-01)

+ 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)

If you have any questions, contact an authorized Bridge service
representative for assistance.


