Ref: 10420009
Title: Release Notes: CS/1 TCP Booting Standalone
Date: 9-2-87

Copyright 3Com Corporation, 1991.  All rights reserved.

Software Release

SW/1-TCP Version 20000

September 2, 1987

Part Number: 86-0018-00
Revision 05


TO:          CS/1 Users

FROM:        Bridge Communications, Inc.

SUBJECT:     SW/1-TCP Version 20000

DATE:        September 2, 1987

Enclosed is a distribution diskette containing SW/20-TCP Version
20000 to be installed on a CS/1.  This release memo describes the
procedure for installing the software, the new features of and
the bugs fixed in this version of SW/1-TCP.

Compatibility

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

.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;GS/3 running SW/3-IP Version 10000 or later
.br;PC running TCPTerm Version 10000 or later
.br;PC running SW/1-PCS Version 10000 or later

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

____________________________________________________________________
|              Table 1  Firmware/Software Compatibility             |
|___________________________________________________________________|
|      |       |                                                    |
|Produc|Softwar|                      Firmware                      |
|      |       |   SIO       MCPU20       EC/2     IBC/M    TRC/M   |
|______|_______|____________________________________________________|
|      |       |         |           |            |     |           |
|CS/1  |SW/1-TC|M0ASYN 15|M3MMON     |M0EDL2 00A  |N/A  |N/A        |
|      |       |M0ASYN 17|00B or late|or later    |     |           |
|      |       |or later |           |or M1IECM 01|     |           |
|      |       |         |           |or later    |     |           |
|______|_______|_________|___________|____________|_____|___________|
|CS/TR |SW/1-TC|M0ASYN 15|M3MMON     |N/A         |N/A  |No PROMs   |
|      |       |M0ASYN 17|00B or late|            |     |           |
|      |       |or later |           |            |     |           |
|______|_______|_________|___________|____________|_____|___________|
|      |       |         |           |            |     |           |
|______|_______|_________|___________|____________|_____|___________|




If your CS/1 is equipped with one or more SIO-16 boards, the
following hardware configurations are required:

+ The SIO-16 board must use SIO16 Driver Version 11030.

+ An SIO-16, EC/2, TRC/M, or IBC/M board must be installed.

Installation

Before you run SW/1-TCP Version 20000 on the CS/1, you should
make a backup copy of the distribution diskette using the
following procedure:

1.  Connect a terminal to the console port of the CS/1.

2.  Press the Reset switch.

3.  Make a backup copy of the distribution diskette using the
following command: > co <n> where n is the number of copies
to be made.

4.  The following message appears on the screen: insert master
and hit return key Insert the SW/1-TCP Version 20000
diskette in the disk drive.  After you 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 Bridge service
representative for assistance.

5.  Remove the SW/1-TCP diskette from the disk drive.  Insert a
blank, 96 TPI, double-sided, double-density diskette in the
disk drive, then press the Return key.

6.  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/20-TCP Version 20000".  Store the
distribution diskette in a safe place.



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:

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 syntax is as
follows: PIng <hostname || ipaddress> [timer value] The
default value of the timer is 20 seconds, and its maximum
value is 300 seconds.  After the command is entered, the
echo request messages will be sent once every second to the
host until the host responds or until the timer expires.

If the host responds, this message will be displayed:
PINGing ... Host is alive Otherwise, this message will be
displayed: PINGing ... Host is not responding The PIng
command is not interruptable.

2.  SW/1-TCP Version 20000 now correctly handles and responds
to all incoming ICMP messages, which facilitates the
communication between the host computer and the CS/1.

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

4.  The CS/1 correctly reassembles fragmented IP packets.

5.  A new parameter, NetMapBroadcast, has been added to SW/1-
TCP.  You can change the value of this parameter with the
SETDefault command as follows: setd NetMapBroadcast [OFF ||
ON] When the NetMapBroadcast parameter is set to OFF, the
CS/1 stops transmitting netmap broadcast packets although
it continues to receive them.

6.  SW/1-TCP Version 20000 supports a receive window size of
400 (hexadecimal) bytes and an arbitrary application-
determined transmit output queue size.  This reduces the
load on the host computer when large data transfers are
performed between Communications Servers.

7.  SW/1-TCP Version 20000 supports Universal Time.  Two new
parameters have been added: TimeZone and
DayLightSavingsTime.

The TimeZone parameter is set to indicate the difference in
hours between your local time and the Greenwich Mean Time.
It should be positive if your site is west of Greenwich,
and negative otherwise.



The DayLightSavingsTime parameter can be set to ON or OFF.
If it is ON, it indicates that Daylight Savings Time is
currently in effect.  The DayLightSavingsTime parameter
being ON does not mean that Daylight Savings Time is
observed at this site and as a result the CS/1 should check
the date to determine the time.  The CS/1 no longer
determines the time based on the date.

8.  In addition to cleaning up the contents of the ARP table,
the ZeroArp command clears out the gateways tables as well.

9.  A new global parameter, MacType, has been added.  It can be
altered with the SETD command, and its possible values are
802.3 and Enet.  The default value is Enet, which is
compatible with other Bridge Ethernet and Broadband
products.

If MacType is set to 802.3, the Communication Server sends
only IEEE 802.3 packets, with all higher protocols included
in 802.3 using the LLC/SNAP protocols.  The server,
however, can receive both Ethernet 802.3 packets.  This
feature ensures that a CS/1 running SW/1-TCP Version 20000
can communicate with another server running TCP/IP software
version 13000 or earlier.

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

11.  If another Communication Server on the network has the same
Internet address as that of 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.

The following is an example of the output generated by the
SHow ARptable command: XXX.XXX.XXX.XXX
XXX.XXX.XXX.XXX XXX.XXX.XXX.XXX ***



XXX.XXX.XXX.XXX XXX.XXX.XXX.XXX
XXX.XXX.XXX.XXX *** n address collisions *** In the display
above, XXX.XXX.XXX.XXX represents an Internet address.  The
address involved in an address collision is followed by
three asterisks (*), and "n" in the message indicates the
number of address collisions.

Also, the audit trail record generated after an address
collision has a different format than that in SW/1-TCP
Version 13000 or earlier.  An example is shown below: MM.DD
HH.MM.SS  III.III.III.III  AC   CCC.CCC.CCC.CCC
%08000200HHHH In this example, III.III.III.III represents
the source Internet address, and CCC.CCC.CCC.CCC represents
the address causing the collision.  The type of audit trail
record is AC for a server involved in an address collision.

12.  A new sysgen parameter called maximal number of SYNC
retransmissions has been implemented in SW/1-TCP Version
20000.

This parameter specifies the number of SYNC packet
retransmissions 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 is, the more SYNC packet
retransmssions it needs.

13.  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.  The
following are two audit trail records: CONNECT:

MM.DD HH.MM.SS  III.III.III.III  N NN CD  CCC.CCC.CCC.CCC

DISCONNECT:

MM.DD HH.MM.SS  III.III.III.III  N NN DC  CCC.CCC.CCC.CCC
In these audit trail records, the first "N" represents the
session number, and "NN" following the session number is
the port number.

Also, the CF (Connect Fail) audit trail record is generated
for a connect request that contains more than one address
in the address list.  In this case, the audit trail record
only displays the first address, but this should be
adequate to uniquely identify the connection attempt.



14.  The Connect command has been modified to allow two extra
parameters, precedence level and type, to be specified.
The syntax of the Connect command is as follows: Connect
<address> [,<address>] [ECM] [@TCP port#] [$Precedence [D]
[T] [R]] The precedence level ranges from 0 (lowest) to 7
(highest), and it must be an integer.  The default value of
this parameter is 0.  It decides the priority of the
session.

If type is D (Delay), the data will be transmitted as soon
as possible.  If it is T (Throughput), the server will
maximize the amount of data transmitted  for a given period
of time.  If you want to minimize errors during data
transmission, specify type to be R (Reliability).

15.  The Connect command, as described in item 14, supports
global rotaries and allows you to specify the destination
TCP port number.

If multiple addresses are specified, the host server will
attempt to connect to the first address.  If that fails, it
will attempt to connect to other addresses specified until
it has tried all the addresses or a successful connection
is made.

You can specify as many addresses as the buffer permits.  A
minimum buffer size of 80 bytes is supported.  Addresses
specified can be physical addresses or names, or a
combination of both, in any order.  The names can be IEN116
names or domain names.  If the Name Server is a domain Name
Server, a name can be translated to multiple addresses.
Name resolution error is considered a major error, which
causes a connection attempt to abort.

You can specify the TCP port number on the host end.  If
you do not specify, the port number will default to the
standard Telnet port (port 23).



When multiple addresses are specified, you are not notified
of the error for each connection failure.  You are notified
of the error of the last connection.

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

Because some hosts treat the interrupt process signal and
the break signal differently, you can modify the
BReakAction parameter to control the signal that the CS/1
generates.

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

18.  A new session parameter, XmitBinary, is implemented.  Its
value can be ON or OFF.  Its default value is OFF, which is
for the transmission of seven-bit ASCII data.  If it is ON,
it allows you to have an eight-bit data path in your Telnet
session with the host.

When a new session is created, Telnet will negotiate with
its peer to turn on the XMITBINARY option if the XmitBinary
parameter is set to ON.  The XMITBINARY option ensures that
the parity bit in an eight-bit character be preserved.

If it is set to OFF, Telnet will not initiate this option
negotiation, but it will accept this option if requested by
the peer.

You can alter the value of the XmitBinary parameter using
the SET command during a session.  It will take effect
immediately.  The host can turn down the request for the
XMITBINARY option at any time.  Telnet does not report
whether the negotiation succeeds.  Also, because the
transmit and receive channels are independent, Telnet
cannot guarantee both channels have the same option
simultaneously.

The purpose of the XmitBinary parameter is that you can
request a change of option.  The current value of this
parameter may not indicate the status of the option,
because the negotiation may not be successful.

19.  If the Internet address of a Communication Server has not
been initialized, its Internet address will be



000.000.000.000.  A server with this address will be
isolated from the network.  You can still communicate with
the server, but any command related to the network (e.g.,
Connect, REMote) will result in the "timeout failure" error
message.

You can use the SHow NetMap command to check whether the
Internet address of your server has been initialized.  The
first entry of the netmap is the Internet address of your
server.

20.  SW/1-TCP 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, which
determines whether the domain name resolver or the IEN116
name service is used for address translation.

The possible values of NsType are Domain and Ien116.  The
value of NsType, which can be changed with a SETD command,
affects the execution of commands that reference names.
For example, both the Connect and SHow NAmes commands will
refer to the NsType parameter to decide whether the IEN116
Name Server or the domain Name Server will be queried.
Network management commands that include names in
parentheses (e.g., SHow <hostname> VERSion) also base the
name queries on the NsType parameter.  Prior to SW/1-TCP
Version 20000, only the IEN116 name service can be
utilized.

To utilize the domain name service, SW/1-TCP Version 20000
implements a new global parameter called DOmain.  This
parameter is referred to when NsType is set to Domain, and
is ignored if NsType is Ien116.

DOmain can be set to a string of up to 128 characters.  The
domain resolver will append this string to all names that
do not include a dot.  For example, if you set DOmain to
"mv.bridge.com", the command "c vax1" would cause
"vax1.mv.bridge.com" to be sent out in a domain request.

After a domain request is sent out, the local cache, which
contains some name/address associations, is searched.  If a
valid entry is found, the information is returned.
Otherwise, the resolver refers to the PrimaryNameServer
parameter to determine which server stores the database for
the domain name service.  The database, which contains all
the name/address associations, is searched.  If the search
fails, the search will be repeated using the database in
the device whose address is specified by the
SecondaryNameServer parameter.



Although the database must be present on the network for
domain name service to function, currently, none of the
Bridge servers store this database.  If the
PrimaryNameServer is 0.0.0.0 or the address of the local
server, the domain resolver will skip the address and refer
to the SecondaryNameServer.  This is because neither the
boot source of the local server nor the local server itself
can be the device storing the database.

If the search of the database fails on both the primary and
secondary Name Servers, a message indicating failure will
be sent to you.  Otherwise, the appropriate information is
sent.  Meanwhile, the name and address are entered in the
cache.

The purpose of the cache is to allow the domain resolver to
locally retrieve information regarding name/address
associations.  While you cannot insert or delete an entry
from the cache, you can flush the cache with the ZeroCache
command.  This command will delete all the entries in the
cache.  Because the database for domain name service does
not reside in a Bridge product, the NAME and UNNAME
commands always refer to the IEN116 server present on a
Bridge server, regardless of the value of NsType.
Another change associated with this feature is that because space
in the UI globals file has been allocated to NsType and DOmain,
the Internet address file must be removed from the global 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/1-TCP
Version 20000 is booted for the first time.  This change has no
effect on your interface with the CS/1.

21.  A new kernel parameter, NameServer, is implemented.  It is
listed as option 5 on the Kernel Parameters menu in the
sysgen program.

Its possible values are 0, which selects the IEN116 to be
the name service, 1, which selects the domain name service,
and 2, which allow 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.

22.  Previously, a LanSwitch/1 could support up to 64 sessions.
SW/1-TCP Version 20000 now can support more sessions.  Each
entry in Table 2 indicates the maximum number of sessions
supported for each combination of boards in the CS/1 or
LS/1. ''



___________________________________
|              Table 2             |
|   Number of Sessions Supported   |
|__________________________________|
|           |                      |
|           |       CPU Board      |
|  Network  |     MCPU       MCPU20|
| Controller|                      |
|   Board   |  CS/1   LS/1         |
|___________|______________________|
|           |                      |
| EC/1      |   32     -       -   |
|           |                      |
| EC/2      |   64     64      -   |
|           |                      |
| EC/2+     |   96     96     128  |
|           |                      |
| IBCM      |   96     96     128  |
|           |                      |
| TRCM      |   96     96     128  |
|___________|______________________|

In the table, EC/2 refers to the EC/2 board with 256
kilobytes of memory, and EC/2+ refers to the EC/2 board
with 512 kilobytes of memory.

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

The syntax for this command is as follows: rfm <string> The
string in the command represents any command available on
the RFM/5.  When you enter this command, the CS/1 will pass
the RFM command to the RFM/5 as if the command had been
entered through a terminal attached to the RFM/5.  The PROM
on the RFM/5 must be R9RFM5 Revision 01B or later, which is
not yet available, for this new command to function.
Attempts to use the RFM command with earlier PROMs will
generate the following error message: Old RFM PROM, command
interface not supported

24.  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 DeVice
parameter will control the default parameter settings for
the Data General environment.  Whenever it is set, the
Bridge User Interface will configure the port for a set of
default Data General parameters.  Therefore, you should set
the DeVice parameter before you alter other parameters.



Standard default parameters are not restored when DeVice is
set to Default.  The default parameter settings are made
only when the DeVice parameter is changed by the SETDefault
command.
The parameter settings after the DeVice parameter is set to
DataGeneral Terminal are shown in Table 3.''

___________________________________________________
| Table 3  Data General Terminal Parameter Settings|
|__________________________________________________|
|                                                  |
| Parameter         Setting                        |
|                                                  |
| BreakAction       OutofBand                      |
| BreakChar         Disabled                       |
| DeVice            (Terminal, Glass, DataGeneral) |
| ECMChar           ^\                             |
| ERAse             ^?                             |
| FlowControlFrom   (None)                         |
| FlowControlTo     (XonXoff)                      |
| IdleTimer         1                              |
| LineErase         ^U                             |
| ReprintLine       ^A                             |
| UseDTRin          Ignore                         |
| UseDCDout         (AlwaysAssert, NoToggle)       |
| Verbatim          ^P                             |
| WordErase         ^B                             |
| XOFF              ^S                             |
| XON               ^Q                             |
|__________________________________________________|



Table 4 shows the parameter settings when DeVice is set to
DataGeneral Host. ''

_______________________________________________
| Table 4  Data General Host Parameter Settings|
|______________________________________________|
|                                              |
| Parameter         Setting                    |
|                                              |
| DeVice            (Host, Glass, DataGeneral) |
| FlowControlFrom   (CTSRTS)                   |
| FlowControlTo     (None)                     |
| IdleTimer         1                          |
| UseDTRin          AsDTR                      |
| UseDCDout         (OnConnect, NoToggle)      |
|______________________________________________|

The new features specific to Data General terminals become
effective when you set DeVice to DataGeneral.  These features are
described below:

1. For the terminal interface, Data General ^S/^Q will be used.
The ^S/^Q flow control method is used to control data going from
the host to the terminal.  The ^S and ^Q characters, which are
the flow control characters, can be embedded in terminal
responses.  As a result, the CS/1 and the host have to
determine, based on the context of the data stream, whether or
not the ^Q and ^S characters are XON/XOFF.

SW/1-TCP Version 20000 now supports Data General context
sensitive ^S/^Q, which is in force when DeVice is DataGeneral
and FlowControlFrom is XONXOFF, so that the flow control
operates properly.

2. A link-level escape character, which is the ^P character, is
implemented to allow a Data General terminal to deliver the flow
control characters to a Data General host over the network on
which back-to-back servers are used.

Any character following ^P will be delivered to the network as
data.  A ^P not preceded by another ^P will be removed from the
data stream by the Communications Server.  Any ^ that follows ^P
will take precedence over the ^P deletion algorithm. Note that
^P deletion is performed only when FlowControlFrom is ^Q and
DeVice is DataGeneral.

If you set the Verbatim character to ^P, you must supply spare
^Ps to allow the Bridge User Interface to complete its
transparency operation.  For instance, to send ^Q to the Bridge
User Interface, you must type ^P^P^P^Q.



3. You may need to pass a ^Q forward to the application program
despite that ^S/^Q flow control is in effect.  The CS/200 now
can perform spare ^Q forwarding when it is in Data General mode
and FlowControlFrom is XON/XOFF, so that the ^Q can be forwarded
properly.

All ^S characters not preceded by ^^, ^, or ^P will be removed
from the data stream and will begin flow control of data from
the server.  The first ^Q character received after any number of
^S characters will be removed from the data stream.  This will
cause the pending flow control condition to stop.

If a ^Q is not preceded by ^^, ^, or ^P, and is not the first ^Q
character received after a ^S character, it will be forwarded as
data.

If you are in a Data General environment, the BreakChar
parameter must be set to Disabled.  Otherwise, it may cause
problems with flow control operations.  Also, if the
terminal's parity and the server's parity do not match,
line editing may not work properly.

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

26.  The BAud parameter now includes an option called AutoBaudLF
to allow autobaud on the LF character.  All baud rates that
can be set on the CS/1 from 75 bps to 19.2 Kbps may be
detected.  This feature is supported on SIO-boards only.

27.  You can define conditional macros on the CS/1 running
SW/1-TCP Version 20000.  For further information on the
syntax and control structure of conditional macros, refer
to the appendix of this release memo.

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 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.  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 repertoire.
They should not be folded before being sent to the User
Interface or being recognized by the SIO processor.

SW/1-TCP Version 20000 enable 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-TR 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 only.

4.  Previously, when a host was flow-controlled, a terminal
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 listened
out 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 sent from the terminal to
the server as an out-of-band signal.  This feature exists
only if you have M0ASYN Rev. 18C or later on the SIO board.

5.  If you enter "SHow ALL" on a terminal port, the names and
physical addresses to which the port is connected are
shown.  However, if you use SW/1-TCP Version 13000 or
earlier, entering this command on a host port will only
generate the message "passive end".  If the connection is
done by interconnect, only the message "via interconnect"
was shown.  The SHow ALL command shows no information on
the Internet address to which the port is connected.



SW/1-TCP Version 20000 now shows the address of the other
end of the connection when it is a passive-end connection
or an interconnection.  The following is an example of the
display generated by a SHow ALL command on the host side:
!9 CONCTD from XXX.XXX.XXX.XXX XXX.XXX.XXX.XXX in the above
example represents the Internet address to which the port
is connected.

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

7.  When data is being transferred, connections on the network
will no longer stall.

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

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

10.  The Break Action now works properly when set to Inband or
OutofBand.  When set to Inband, the Break Action is mapped
to the Telnet IP (Interrupt Process) signal; when set to
OutofBand, it is mapped to the Telnet Break signal.

Limitations

The following are the limitations of SW/1-TCP Version 20000:

1.  Because of the newly created PIng command, it is necessary
to rename the abbreviation for the Pause command to avoid
ambiguity.  You must type "pa" instead "p" for the PAuse
command.  As a result, you must also change the
abbreviation for the PAuse command in all the macros that
contain this command.

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

3.  The Internet address checks do not include a check of the
subnet field (for all 0s or all 1s).

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

5.  When the NsType parameter is set to Domain, you can only
supply unique names with the SHow NAmes command.  Wildcard



characters, such as an asterisk (*), are not accepted.
Requests such as "SHow NAmes" or "SHow NAmes *" will result
in the following response: Resolver: can only show unique
DOMAIN names

Known_Problems

The following is a list of known problems in SW/1-TCP 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, which 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 there is a secondary Name Server defined.  This might
crash the CS/1.

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)

+ Series/1 Installation Guide (11/86)
(Part Number: 09-0022-05)

+ Connection Service User's Guide (8/86)
(Part Number: 09-0063-01)

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

+ Network Management Guide (1/87)
(Part Number: 09-0043-01)

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



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


