Ref: 99980041 Title: Release Note: CS/1 booting from diskette Ver 20060 Date: 3/30/87 Copyright 3Com Corporation, 1991. All rights reserved. Software Release SW/1-A/BSC/SDLC Version 20060 March 30, 1987 Part Number: 86-0043-00 Revision 04 TO: CS/1 Users FROM: Bridge Communications, Inc. SUBJECT: SW/1-A/BSC/SDLC Version 20060 DATE: March 30, 1987 Enclosed is the SW/1-A/BSC/SDLC Version 20060 diskette. This diskette is your distribution copy of SW/1-A/BSC/SDLC Version 20060 and should be used only to copy the system software onto the master diskette. The master may then be used to update the current working diskette. If your current working diskette is SW/1-A/BSC Version 17100 up to SW/1-A/BSC/SDLC Version 20030, Bridge recommends the following procedure to update your system to Version 20060 without losing port configurations, macros, and clearinghouse names. Otherwise, refer to pages 3 and 4 for the updating procedure. 1. Connect your 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 .br;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-A/BSC/SDLC Version 20060 diskette in the disk drive. After you press the return key, the following messages appear on the screen if the read completes successfully: .br;Reading ... OK Insert copy #n and hit return key If the message "read error" appears instead of the message "OK", contact an authorized Bridge service representative for assistance. 5. Remove the SW/1-A/BSC/SDLC Version 20060 diskette from the disk drive. Insert a blank, 48 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: .br;writing ... verifying ... OK copy completed Remove the diskette from the disk drive, and label it "SW/1- A/BSC/SDLC Version 20060". Store the distribution diskette in a safe place. 7. Insert your current working diskette in the disk drive. Then enter the following command after the prompt: > r 20B 3000 c600 8. Remove your working diskette and insert the SW/1-A/BSC/SDLC Version 20060 diskette in the disk drive. Enter the following commands to copy the port configurations, macros, and clearinghouse to the Version 20060 diskette. > w 26e 3000 200 > w 216 3200 400 > w 219 3600 1000 > w 225 4600 2a00 > w 23a 7000 400 > w 23d 7400 4000 > w 26d f400 200 9. Repeat steps 7 and 8 for each system being updated. If you are currently running SW/1-A/BSC/SDLC Version 2005x (where x represents a number from 0 to 9), use the following procedure to update your system to SW/1-A/BSC/SDLC Version 20060: 1. Connect your terminal to the console port of the CS/1. 2. Press the Reset switch. 3. Back up the distribution diskette by following steps 3 through 6 on pages 2 and 3. 4. Then copy the distribution diskette onto your SW/1-A/BSC/SDLC Version 2005x master diskette using the following command (provided the MCPU PROM on your CS/1 MCPU board is revision 9 or earlier): > co -p where n is the number of updated diskettes to be made. 5. When the system prompts for the first and last block numbers, enter the numbers as follows: > First block? 0 > Last block? 215 6. If the MCPU PROM on your CS/1 MCPU board is revision 1B or later, use the following command to copy the distribution diskette onto your SW/1-A/BSC/SDLC Version 2005x master diskette: > co -p 0 215 7. The following message appears on the screen: Insert master and hit return key Insert the SW/1-A/BSC/SDLC Version 20060 diskette in the disk drive. Then press the return key. The following messages appear on your screen if the read completes successfully: Reading ... OK Insert copy #n and hit return key If the message "read error" appears instead of the message "OK", contact an authorized Bridge service representative for assistance. 8. Remove the SW/1-A/BSC/SDLC Version 20060 diskette and insert the SW/1-A/BSC/SDLC Version 2005x diskette in the disk drive, then press the return key. 9. If the copy completes successfully, the following messages appear on the screen: writing ... verifying ... OK copy completed 10. Remove the diskette from the disk drive and label it "SW/1- A/BSC/SDLC MASTER VERSION 20060". Store the distribution diskette in a safe place. If you are not currently running SW/1-A/BSC Version 17100 or later, use the following command to copy the new release to a blank, 48 TPI, double-sided, double-density diskette: .br;> co where n is the number of copies to be made. You will need to rebuild the clearinghouse names, macros, and port configurations. Compatibility SW/1-A/BSC/SDLC 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;CS/200 running SW/200 Version 20000 or later .br;IVECS running SW/IVECS-A Version 10000 or later .br;NCS/150 running SW/150-NCS Version 10000 or later .br;NCS/1 running SW/1-NCS 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 The following chart illustrates the software and firmware compatibility for SW/1-A/BSC/SDLC 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 Version 20050 or earlier, have been implemented in SW/1- A/BSC/SDLC 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: .br;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 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 Version 20060: 1. If you have not updated all of your CS/1s to SW/1-A/BSC/SDLC Version 20000 or later, a connection from a CS/1 that runs SW/1-A/BSC Version 17100 or SW/1-A/BSC/SDLC Version 18610 to a CS/1 that runs SW/1-A/BSC/SDLC 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 diskette was SW/1-A/BSC/SDLC 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 of this parameter. However, the SIO-16 supports only single-range autobaud. Whether you set the BAud parameter to HI or LO 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 Version 20060 Following is the procedure for running the sysgen program on the CS/1. For further information on menu displays and parameters, please refer to the Configuration Guide. System generation is not required before installing 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. 1. Connect a terminal to the console port. 2. Insert the SW/1-A/BSC/SDLC Version 20060 diskette in the CS/1 disk drive, then press the Reset switch. The CS/1 displays the following messages: Power-up V1.0 MCPU-passed EC- passed SIO # 1 - passed SIO # 2 - passed (or not present) SIO # 3 - passed (or not present) SIO # 4 - passed (or not present) Bridge Communications MCPU Monitor 3. After the above messages, the system displays a ">" prompt. Enter "gn" and press the return key. 4. The CS/1 displays the Sysgen Utility V2.0 menu and a message at the bottom of the screen asking you to make a selection. 5. Enter 1 to select View/Alter Module Parameters, then press the return key. The CS/1 then displays the Module Select Menu and a message at the bottom of the screen asking you to make a selection. 6. To display a parameter module, enter the number of the module as it appears in the Module Select Menu, then press the return key. 7. After the list of parameters appears on the screen, you can change the value of a parameter by entering its number. Then enter the new value of the parameter at the prompt and press the return key. 8. Press to return to the Module Select Menu. 9. After system generation is complete, enter 2 to save all the parameters. 10. Enter 3, then press the return key to exit to the monitor. 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.