Ref: 99980033 Title: Release Note: CS/100 booting from diskette Ver 12010 Date: 11/25/86 Copyright 3Com Corporation, 1991. All rights reserved. Software Release SW/100-TCP Version 12010 and SW/100-T-UTIL Version 11000 November 25, 1986 Part Number: 86-0020-00 Revision 03 To: CS/100 Users From: Bridge Communications, Inc. Subject: SW/100-TCP Version 12010 and SW/100-T-UTIL Version 11000 Date: November 25, 1986 Enclosed are the SW/100-TCP Version 12010 and SW/100-T-UTIL Version 11000 diskettes. These diskettes are your dis- tribution copy of SW/100-TCP Version 12010 and SW/100-T-UTIL Ver- sion 11000; they should be used only to copy the system software onto the master diskettes. The master diskettes may then be used to update your current working diskette. Bridge recommends the following procedure to update your system to Version 12010 without losing names, port configura- tions, and macros. If you are currently running SW/100-TCP Version 11000 or later, follow these steps to update your system to SW/100-TCP Version 12010: 1. Connect your terminal to port 0. 2. Insert the SW/100-T-UTIL Version 11000 diskette into the CS/100 disk drive, then press the Reset switch. After the Utilities diskette is finished booting, press the following sequence on the keyboard: . 3. After the CS/100 has finished its self-test, to copy the software from the SW/100-TCP Version 12010 distribution diskette onto the SW/100-TCP Version 11000 or later diskette, enter the following command: > co -p where n is a number of updated diskettes to be made > First block? 0 > Last block? 144 ***** NOTE ***** After performing the software update, you will have to redefine the global parameters, rotary port assignment, rotary's Internet addresses, port's Internet addresses, Primary Name Server, Secondary Name Server, Default Gateway, and resysgen the software to define the server's Internet address and other sysgen parameters. 4. The following message appears on the screen: Insert Master Disk #n (hit to continue, q to quit) 5. Remove the utilities diskette and label it "SW/100-T-UTIL MASTER VERSION 11000". Insert the SW/100-TCP Ver- sion 12010 distribution diskette into the disk drive. If the read completes successfully, the following messages appear on your screen: Reading ... OK Insert copy #n and hit return key 6. Follow the message instructions. If the message "read error" appears instead of the message "OK", contact Bridge Communications, your local Systems Engineer, or Technical Support for assistance. 7. Remove the SW/100-TCP Version 12010 diskette, in- sert the SW/100-TCP Version 11000 master diskette in the disk drive, then press the return key. 8. If the copy completes successfully, the following messages appear on your screen: writing ... verifying ... OK copy completed 9. Remove the SW/100-TCP Version 11000 diskette and label it "SW/100-TCP MASTER VERSION 12010". Store the dis- tribution diskette in a safe place. 10. The SW/100-TCP Version 12010 master diskette may now be used to update current working diskettes using the "co " command. SOFTWARE AND FIRMWARE COMPATIBILITY SW/100-TCP Version 12010 operates with the following pro- ducts and software releases: .br;NCS/150 running SW/150-NCS-TCP Version 10000 or later .br;CS/1 running SW/1-TCP Version 10110 or later .br;CS/1-SNA running SW/1-SNA3270-T Version 10000 or later .br;GS/3-IP running SW/3-IP Version 10000 or later .br;TCPTerm Version 10000 or later The following chart illustrates the software and firmware compatibility for SW/100-TCP Version 12010 and SW/100-T-UTIL Version 11000: NEW FEATURES The following new features have been implemented in SW/100-TCP Versions 11000, 12000, and 12010: 1. The Name Server no longer needs the !net! field when naming or unnaming a logical name. Moreover, the "!" is not allowed in defining a logical name. In addition, a hyphen (-) is now allowed within names. 2. SW/100-TCP Version 12000 is compatible with T1ASYN PROMs Revision 1B or higher on the SIO area. 3. A secondary Name Server has been added. This feature is useful for a large network. 4. The Internet addresses of the Name Server, Default Gateway, and Communications Server physical and rotary ports can now be defined via the User Interface commands. The new User Interface commands are listed below: - SETDefault (!) InternetPort = Assigns Internet addresses to individual physical or rotary ports. - SETDefault (!) InternetPort = 0.0.0.0 Removes the Internet address of an individual physical or rotary port. - SETDefault DefaultGateway = Allows all remote net packets to be sent to the gate- way. The gateway should be able to return an Internet Control Message Protocol (ICMP) REDIRECT if it is not the optimal first hop. - SETDefault PrimaryNameServer = Assigns an Internet address for the primary Name Server. The primary Name Server will be queried first for name resolution. The primary Name Server's Internet address can be de- fined to be on a remote network. - SETDefault SecondaryNameServer = Assigns an Internet address for the secondary Name Server. The secondary Name Server will be queried if the primary Name Server does not yield a name to address resolution. - SHow InternetPorts Replaces the SHow InternetMap command. It displays the Internet address of the Communications Server itself and all other Internet addresses associated with the Communications Server (physical and rotary ports). - SHow InternetServers Displays Internet addresses of the Name Servers, Default Gateway, and the Boot Server if the CS/100 is booted from the NCS/150. - SHow VirtualPorts Displays the connection state (passive or active) of the physical port to which these virtual ports are connected. 5. Subnets are now supported. Refer to the Appendix for more detailed descriptions of subnets. 6. Passive-end or host-side RLOGIN is supported. The RLOGIN feature allows a login from a UNIX* host to a non- UNIX host front-end by the CS/1 or CS/100 running SW/1-TCP or SW/100-TCP, respectively. For example, to perform an rlogin from a UNIX host to a non-UNIX host, enter the following command: rlogin 7. The number of physical ports can be limited via sysgen. Refer to pages 8 through 11 for sysgen instruc- tions. This feature is useful in increasing the number of shared ses- sions per port. 8. Up to 20 full-duplex sessions are supported. Refer to pages 8 through 11 for sysgen instructions. 9. A new sysgenable parameter "Buffer load factor" has been added. This parameter controls the amount of system buffer allocated during initialization. Refer to pages 8 through 11 for sysgen instructions. The following new features have been implemented in SW/100-TCP Version 12000: 1. Supports Audit Trail for all connections, disconnec- tions, and relevant statistics. Note that this feature works in conjunction with the NCS/150 running SW/150-NCS-TCP. 2. One more buffer is now available for disk ac- cess. This feature reduces the probability of getting the "Can't - No Memory" message in response to User Interface com- mands that require disk I/O (e.g., name lookup). 3. FlushVC in the BReakAction parameter now works if the remote host responds to Telnet DO-TIMING-MARK commands. The following new features have been implemented in SW/100-TCP Version 12010: 1. ARP now sends requests for all IP addresses defined on the server at startup time. This feature allows the ARP tables of all other servers on the network to update their entries. 2. The long break capability is now supported. This feature allows a CS/100 to interface with equipment or certain hosts such as Gandalf* and Micom* that rely solely on long break to indicate disconnection. A CS/100 can transmit and receive long break when the corresponding parameter is set. Note that this feature only works with T1ASYN PROMs Revision 1B or later. BUGS FIXED The following problems have been corrected in SW/100-TCP Versions 11000, 12000, and 12010: 1. The TCP retransmission algorithm has been improved. 2. Users can now use the Broadcast 255.255.255.255 command to broadcast a message. Note that this command does not work in remote mode. The following problems have been corrected in SW/100-TCP Version 12000: 1. Several disconnection problems have been fixed. 2. If a connection is established to a busy port across a network, the message "Remote is Busy" appears instead of the message "Remote is disabled or non-existent". 3. A fatal error no longer occurs if there is a termi- nal port with noisy DCD and DTR lines that has UseDTRin set to AsDTR. 4. A fatal error no longer occurs if a terminal port has a device connected to it that is constantly generating characters. The following problems have been corrected in SW/100-TCP Version 12010: 1. Telnet now correctly disconnects its virtual ports. This eliminates the "Remote is Busy" message in some situa- tions. 2. When a SHow SESsions command is performed on a two- digit port with an active session, the welcome string no longer disappears. 3. Telnet now sends the Interrupt Process command to transmit the break character. 4. The software now sends RESET packets in response to TCP packets when there is no connection. 5. The Ethernet Agent module has been enhanced to prevent the CS/100 from malfunctioning when it is running out of memory. KNOWN PROBLEMS The following is a list of current problems in SW/100-TCP Version 12010: 1. The message "Remote is Busy" appears when the remote system is out of memory. 2. When creating a macro to establish a session with ECM and RESume after transmitting a string, if the connection fails due to a busy or disabled destination port, the macro buffer will be lost. If this problem occurs repeatedly, macros will no longer be executed. In this case, the CS/100 must be rebooted in order for macros to be executed again. 3. If the host crashes and the user continues to enter characters on the terminal, the terminal port will hang. After a few minutes, the terminal port will be reactivated au- tomatically. However, this terminal port can also be reactivated by putting it in listen mode from another terminal. 4. In order to use the local floppy as the Name Server database, the primary Name Server must be defined to be that unit's Internet address. 5. The SHow STATisticS command occasionally displays incorrect information. PROCEDURE TO SYSGEN A CS/100 RUNNING SW/100-TCP VERSION 12010 Following is the procedure for running the sysgen pro- gram on a CS/100 running SW/100-TCP. 1. Connect a terminal to port 0. 2. Insert the SW/100-T-UTIL Version 11000 diskette in the CS/100 disk drive, then press the Reset switch. When the Utilities diskette is finished booting, enter the following se- quence on the terminal key board: . 3. The system displays a welcome message and a ">" prompt. Enter "gn" and press the return key. 4. You will be prompted to load the system diskette. Remove the Utilities diskette, insert the SW/100-TCP Version 12010 diskette, then press the return key. 5. The CS/100 displays the "Sysgen Utility V2.0" menu and a message at the bottom of the screen asking you to make a selection: Sysgen Utility V2.0 1. View/Alter Module Parameters 2. Save Parameters 3. Exit to Monitor Enter selection: 6. Enter 1 to select "View/Alter Module Parameters", then press the return key. The CS/100 then displays the "Module Select Menu" and a message at the bottom of the screen asking you to make a selec- tion. Module Select Menu 1. Kernel Parameters 2. Data Link Parameters 3. IP Parameters 4. TCP Parameters 5. User Interface Parameters 6. Virtual Terminal Parameters 7. Statistics Monitoring Parameters 8. Service Listener Port List (ESC to return to main menu) Select module: 7. Enter 1 to select "Kernel Parameters". The "Kernel Parameters" display is as follows: Kernel Parameters Parameters Current Value 1. Max. no. of ports 0xE 2. Max. no. of sessions 0x14 3. Buffer size 0x34 4. Buffer load factor 0x40 Kernel Submenu 5. View/Modify SYSINIT Table A) Enter 1 to specify the maximum number of physical ports that you would like to use on the Communications Server. B) Enter 2 to specify the maximum number of sessions that you would like to use on the Communications Server. C) Enter 3 to specify the buffer size. The default buffer size is 52 bytes. Note that if you wish to increase the buffer size, the maximum number of sessions should be decreased. D) Enter 4 to specify the buffer load factor. Note that this parameter allows you to control the utili- zation of shared memory. The higher the number, the more buffer will be allocated. This parameter is useful when the number of sessions or the buffer size is increased. If the "panic 94" message appears on the console port, the buffer load factor should be decreased. E) Press to return to the "Module Select Menu". 8. Enter 3 to select "IP Parameters". The "IP Parameters" display is as follows: IP Parameters Parameter Current Value 1. Network to IP mailbox 0xC 2. Client to IP mailbox 0xC 3. Server Internet address 000.000.000.000 4. Server subnet mask not a subnet A) Select option 3 to enter the Internet address of the Communications Server. B) Select option 4 to enter the server subnet mask if your network topology requires the definition of subnetworks. Refer to SUBNETS in the Appendix for more detailed descrip- tions of subnets. In order to avoid malfunctioning of the system, do not define a subnet mask if subnetworking is not in use. C) Press ESC to return to the "Module Select Menu". 9. Enter 8 to select "Service Listener Port List". The "Service Listener Well Known Ports" menu display is as follows: Service Listener Well Known Ports 1. 23 (17) 2. 513 (201) 3. (Add new service here) A) 23 is a number assigned to the Telnet Service Listener Port. B) 513 is a number assigned to the Rlogin Service Listener Port. C) The assigned Service Listener Ports can be found in the RFC (Request for Comment) 943 document. Up to eight Service Ports are allowed in this menu. These Service Ports can be used in a variety of ways. They can be used to "export" the TCP interface to the serial line. In this case, a host could bind a process to that line which could accept incoming data units from the active side of the particular service and generate whatever responses would be ap- propriate for that service protocol. Note that the Service Ports are only available on the passive end of a connection. There is no way to select the remote service when connecting from a terminal on the CS/100 running SW/100-TCP. You will always get a Telnet service. 10. Press ESC to return to the "Module Select Menu". 11. Press ESC to return to the "Sysgen Utility V2.0" menu. 12. Enter 2 to save all the parameters. 13. Enter 3, then press the return key to exit to the monitor. Appendix SUBNETS Overview If a private network wishes to establish communica- tions to a public TCP/IP network (e.g., ARPANET), the public net- work first assigns a unique network number to the private network. In this case, all stations on this private network will have this unique network number. Gateways internal to this network may be used to further subdivide the network into segments by in- corporating subnetworking as described below. Definition of Subnets and the Subnet Mask An Internet address consists of 32 bits divided into four 8-bit subfields. Normally, these subfields are divided between the and fields. Some TCP/IP networks, however, have in- serted an additional field between the and fields called . The subnet field is used to indicate the particular physical segment. The field is formed by taking the leading bits from the field. The field is assigned in the sysgen program under the "Server subnet mask" option in the "IP Parame- ters" menu. However, if your network does not use subnets, do not assign a subnet mask. When entering the subnet mask, enter the decimal instead of binary representation. The subnet mask is then defined as follows: It is a 32-bit number divided into four equal sub- fields. Each bit that coincides with the network field (the 8, 16, and 24 most significant bits for a class A, B, and C Internet address, respectively) is always set to 1. The remaining bits in the host field that are set to 1 define the subnet field to be incorporated. The subnetwork address is then ob- tained by performing the logical AND operation of the Internet ad- dress with the selected subnet mask field. For the subnet addressing to be meaningful, all the servers on this private network must be sysgenned with identical subnet masks. Example 1: The subnets of a class A Internet address might be de- fined as follows: 126.(11110000) (00000000) (00000000) In this example, the number of subnets defined on this network is 16 and the subnet mask is (11111111) (11110000) (00000000) (00000000), which is the binary equivalent of 255.240.000.000 decimal. The possible subnetwork addresses for this network would then be: 126.0.0.0 126.128.0.0 126.16.0.0 126.144.0.0 126.32.0.0 126.160.0.0 126.48.0.0 126.176.0.0 126.64.0.0 126.192.0.0 126.80.0.0 126.208.0.0 126.96.0.0 126.224.0.0 126.112.0.0 126.240.0.0 Example 2: The subnets of a class B Internet address might be de- fined as follows: 129.000.(11100000) (00000000) In this example, the number of subnets is 8 and the sub- net mask is (11111111) (11111111) (11100000) (00000000), which is the binary equivalent of 255.255.224.000 decimal. The possible subnetwork addresses for this network would then be: 129.0.0.0 129.0.128.0 129.0.32.0 129.0.160.0 129.0.64.0 129.0.192.0 129.0.96.0 129.0.224.0 Example 3: The subnets of a class C Internet address might be de- fined as follows: 193.129.130.(11000000) In this example, the number of subnets is 4 and the sub- net mask is (11111111) (11111111) (11111111) (11000000), which is the binary equivalent of 255.255.255.192 decimal. The possible subnetwork addresses for this network would then be: .br;193.129.130.0 193.129.130.128 .br;193.129.130.64 193.129.130.192 Note that in the three examples above, the numbers in parentheses are in binary format. DOCUMENTATION The current manuals for the CS/100 running SW/100-TCP are listed below: o Series/100 Installation Guide (10/85) o Network Management Guide (3/86) o Connection Service User's Guide (8/86) Trademarks UNIX is a registered trademark of Bell Laboratories. Gandalf is a trademark of Gandalf Corporation. Micom is a trademark of Micom Corporation. If you have any questions, please contact Bridge Commun- ications, your local Systems Engineer, or Technical Support for as- sistance.