Ref: 10420001
Title: Release Note: CS/1 booting from NCS/1 ver 20060
Date: 3/30/88

Copyright 3Com Corporation, 1991.  All rights reserved.

Software Release

SW/1-A/BSC/SDLC-NCS/1 Version 20060

March 30, 1987

Part Number: 86-0100-00
Revision 00


TO:          CS/1 Users

FROM:        Bridge Communications, Inc.

SUBJECT:     SW/1-A/BSC/SDLC-NCS/1 Version 20060

DATE:        March 30, 1987

Enclosed is the distribution tape cartridge containing SW/1-
A/BSC/SDLC-NCS/1 Version 20060. This software is for CS/1s that
are booted from an NCS/1.

This release memo contains the instructions for installing
software on the NCS/1. It also describes new features of and bugs
fixed in SW/1-A/BSC/SDLC-NCS/1.

Installing Software on the NCS/1

To copy the software from the SW/1-A/BSC/SDLC-NCS/1 Version 20060
tape cartridge to the NCS/1, follow these steps:

1.  After logging in to the NCS/1, hold the distribution tape
cartridge so that the window that contains the word "SAFE" is
in the top left corner. Insert the cartridge in the tape
drive slot at the top of the NCS/1 pedestal unit.

2.  Open the Utilities window on the screen by performing these
steps:

a.  Move the mouse on the mouse pad until the mouse cursor is
positioned on the UTIL icon at the bottom of the screen.

b.  Press the left mouse button to open the Utilities window.

c.  Release the mouse button.

3.  Move the mouse on the mouse pad until the mouse cursor is
positioned inside the Utilities window. At the utilities
prompt (NCS1%), type:

taperead

4.  When the file is copied from the tape to the disk, it will be
listed on the screen.

5.  If tape read errors or disk write errors occur, unload the
cartridge from the tape drive. Then reload it and reinvoke
the Taperead utility. If errors continue to occur, contact an
authorized Bridge service representative for assistance.



6.  When the file has been successfully copied, the utilities
prompt will reappear. Unload the tape cartridge.



Compatibility

SW/1-A/BSC/SDLC-NCS/1 Version 20060 can operate with the
following products and software releases:

.br;CS/100 running SW/100-A/BSC Version 12000 or later
.br;CS/1-X.25 running SW/1-X.25 Version 14000 or later
.br;CS/1-HSM running SW/1-HSM Version 11010 or later
.br;CS/1-SNA running SW/1-SNA Version 10000 or later
.br;GS/1 running SW/2-CS-ICS Version 14000 or later
.br;GS/3 running SW/3 Version 14000 or later
.br;GS/4 running SW/4 Version 10000
.br;GS/6 running SW/6 Version 10000 or later
.br;GS/300 running SW/300 Version 10000 or later
.br;NCS/150 running SW/150-NCS Version 10000 or later
.br;NCS/1 running SW/1-NCS Version 10010 or later
.br;CS/200 running SW/200-A Version 20000 or later
.br;IVECS running SW/IVECS-A Version 10000 or later
.br;PC running EtherTerm Version 12000 or later
.br;IB/1 and IB/2 running SW/IB Version 10000 or later
.br;
.br;The following chart illustrates the software and firmware
compatibility for SW/1-A/BSC/SDLC-NCS/1 Version 20060:

''

_____________________________________________________________________
|                   SOFTWARE/FIRMWARE COMPATIBILITY                  |
|____________________________________________________________________|
|          |            |                   Firmware                 |
|  Product |   Software |                                            |
|          |            |     SIO        MCPU         ESB or EC/2    |
|__________|____________|____________________________________________|
| CS/1-A   |  SW/1-     |  SIODL 14 |  MPUMON 9 |  M0EDL1 4B|  M0EDL2|
|          |  A/BSC/SDLC|  or later |  M1MMON 1B|           |  00A or|
|          |            |  M0ASYN   |  or later |           |  later |
|          |            |  15A or   |           |           |        |
|          |            |  later    |           |           |        |
|__________|____________|___________|___________|___________|________|
| CS/1-BSC |  SW/1-     |  SIOBSC 2 |  MPUMON 9 |  M0EDL1 4B|  M0EDL2|
|          |  A/BSC/SDLC|  or later |  M1MMON 1B|           |  00A or|
|          |            |  M1SYNC 1B|  or later |           |  later |
|          |            |  or later |           |           |        |
|__________|____________|___________|___________|___________|________|
| CS/1-SDLC|  SW/1-     |  M1SYNC 1B|  MPUMON 9 |  M0EDL1 4B|  M0EDL2|
|          |  A/BSC/SDLC|  or later |  M1MMON 1B|           |  00A or|
|          |            |           |  or later |           |  later |
|__________|____________|___________|___________|___________|________|



If you have an SIO-16 in the CS/1, the  following  configurations
must be used:

1.  For the CS/1 with one  or  more  SIO-16s,  an  EC/2  must  be
installed  in  the  CS/1. In addition, the MCPU PROMs must be
M1MMON Revision 1G or later.

2.  For the CS/1 with three or four SIO-16s, the MCPU board  must
be  upgraded  to 12MHz. One or two SIO-16s can be used with a
10MHz MCPU board.

New Features

The  following  features,  which  were  not  present   in   SW/1-
A/BSC/SDLC-NCS/1  Version 20050 or earlier, have been implemented
in SW/1-A/BSC/SDLC-NCS/1 Version 20060:

1.  In addition to the SETDefault command, the SET command can be
used  to  alter  the  buffer  size of an individual port. For
instance, to change the current buffer size of a port  to  56
bytes, type:

set BUffersize = 56
To change the buffer size of the host, the REMoteSET  command
can be used with the same syntax shown above.

Setting the buffer size to be smaller than the system  buffer
size,  which  is  usually  82  bytes,  will actually create a
buffer of the specified  size.  If  the  specified  value  is
greater  than  the  system  buffer  size, more buffers of the
system buffer size  will  be  created  instead  of  a  bigger
buffer.

The SET command will not take  effect  immediately  during  a
session.  The  additional buffers created by the command will
not be used until the buffers currently allocated to the port
have been exhausted.

2.  It now takes 4 seconds for the Communications Server to
deliver the audit trail data to the NCS. It used to take 90
seconds.

The 4-second timer can be sysgenned. This is done by
modifying the Statistics Monitor timer value. Please refer to
the Configuration Guide for further information.

3.  The server will accept from the netmap packet a clock value
that is lower than the current value. For example, if the
clock on the NCS is set back to year 1970, all the system
clocks of the servers on the network will be changed within
45 seconds to this new value.



Bugs Fixed

The following problems have been corrected in SW/1-A/BSC/SDLC-
NCS/1 Version 20060:

1.  The audit trail records now show the actual number of rotary
ports used. In the past, the rotary ports used count was
always zero according to the audit trail records.

2.  It is no longer possible for a port to be trapped in the
WAIT-FOR-CONNECT state forever or for the PVC (Permanent
Virtual Circuit) to suddenly stop working.

3.  The data link drivers can now detect all known deadlock
situations properly.  Running the servers on a noisy network
will not crash the servers or cause the servers to drop from
the netmap.  However, the PROM on the EC/2 board must be
M0EDL2 01A or later for this to work.

Known Problems

The following is a list of current problems in SW/1-A/BSC/SDLC-
NCS/1 Version 20060:

1.  If you have not updated all of your CS/1s to SW/1-
A/BSC/SDLC-NCS/1 Version 20000 or later, a connection from a
CS/1 that runs SW/1-A/BSC/SDLC-NCS/1 Version 17100 or SW/1-
A/BSC/SDLC-NCS/1 Version 18610 to a CS/1 that runs SW/1-
A/BSC/SDLC-NCS/1 Version 20000 or later may cause a delay of
approximately four seconds.

2.  If the FlowControlTo and FlowControlFrom parameters are both
set to None, resetting one of the parameters to XonXoff or
ENQACK causes the other to be automatically set to XonXoff or
ENQACK. Note that this problem does not occur for the other
two options (None and CTSRTS).

3.  If your working software was SW/1-A/BSC/SDLC-NCS/1 Version
20030 or earlier before being updated to Version 20060, the
LogoffString may contain garbage characters when the software
is first booted. In order to eliminate these garbage
characters, use the following command:

SETDefault LogoffString = ""

4.  Due to a memory limitation, the SHow CONFiguration and SHow
MACro commands no longer display output in alphabetical
order.



5.  On the SIO-16's ports, the help menu of the BAud parameter
displays LowAutoBaud and HiAutoBaud as options.  However, the
SIO-16 only supports single-range autobaud. Whether you set
the BAud parameter to LO or HI will not affect the baud rate,
which will range from 50 to 38.4K to match the terminal's
baud rate.

6.  There are no Clear to Send (CTS) and Request to Send (RTS)
lines for the SIO-16. However, on the SIO-16's ports, the
help menu of the FlowControlTo and FlowControlFrom parameters
displays CTSRTS as an option of these parameters.

Features of Synchronous Data Link Control (SDLC) Interface

To activate the bit-synchronous parameter menu, the user must set
the LinePRotocol parameter to BITsynchronous (provided the SIO-
SMS or SIO-STS board installed in the CS/1 has M1 SYNC SIO PROMs
of Revision 1A or later).

The bit-synchronous software supports third-party connections
only. In order to establish a third-party connection, the network
manager must make the connection via an asynchronous terminal
connected to the network. Alternately, the interconnection
service can be established by the use of the "init"  macro. The
"init" macro must be installed by the network manager from an
asynchronous terminal connected to the network.

Since the Connection Service commands are not available directly
to a bit-synchronous port, parameters for a bit-synchronous port
are set remotely from an asynchronous terminal. Refer to the
Configuration Guide for the configuration instructions.

Procedure to Sysgen SW/1-A/BSC/SDLC-NCS/1 Version 20060

Please refer to the NCS/1 Installation and Operation Guide for
instructions to run the sysgen program on the NCS/1.

System generation is not required before you install the
software. It is used to alter the values of certain parameters.
Bridge does not recommend altering those values by sysgen without
a specific need.



Documentation

The current versions of the manuals for the CS/1 are listed
below:

+ Series/1 Installation Guide (11/86)

+ Connection Service User's Guide (8/86)

+ Connection Service User's Quick Reference Guide (12/85)

+ Network Management Guide (1/87)

+ Configuration Guide (1/87)

+ Getting Started Guide (1/87)

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


