Ref: 99960064 Title: ESD Rel.Note:SW/20-A/BSC/SDLC VER.22010 PART#:86-0195-00 REV.01 date: 03-01-89 Copyright 3Com Corporation, 1991. All rights reserved. 3Com Corporation Software Release SW/20-A/BSC/SDLC Version 22010 March 1, 1989 Part Number: 86-0195-00 Revision 01 TO: CS/1 Users FROM: 3Com Corporation SUBJECT: SW/20-A/BSC/SDLC Version 22010 DATE: March 1, 1989 Enclosed is a distribution diskette containing SW/20-A/BSC/SDLC Version 22010 (part number: 83-0166-00). This software, which is an updated version of SW/20-A/BSC/SDLC Version 22000, is to be used on an MCPU20-based CS/1. This release memo gives instructions for copying the distribution diskette. It also describes the bugs fixed since Version 22000, and the software's limitations and known problems. Compatibility SW/20-A/BSC/SDLC Version 22010 can operate with the following products and software releases: CS/1 running SW/1-A/BSC/SDLC Version 22000 or later CS/1-SNA running SW/1-SNA Version 13010 or later GS/1-X.25 running SW/1-X.25 Version 14030 or later CS/200 running SW/200-A/BSC/SDLC Version 22000 or later CS/210 running SW/200-A/BSC/SDLC Version 22000 or later IVECS running SW/IVECS-A Version 20060 or later NCS/150 running SW/150-NCS Version 11000 or later NCS/AT running SW/AT-NCS Version 11000 or later IB/1, IB/2, and IB/3 running SW/20-IB Version 11000 or later Personal computer running SW/PCS-XNS Version 10000 or later Table 1 illustrates the hardware and firmware compatibility for SW/20- A/BSC/SDLC Ver sion 22010. Table 1 Hardware/Firmware Compatibility Product Boards PROMS CS/1 SIO-16 No PROMS CS/1 MCPU20 M3 MMON 00D or later CS/1 EC/2 M1 IECM 01F or later If an Ethernet controller is used with the MCPU20-based CS/1, it must be an EC/2 board with 512 kilobytes of RAM. Also, an MCPU20 board must operate with a 96-TPI disk drive. Copying the Software ** NOTE ** When following the instructions in this release memo, be sure to press the Return key after typing each command. Before you use SW/20-A/BSC/SDLC Version 22010 on the CS/1, follow these steps to make a copy of the distribution diskette: 1. Attach a terminal to the console port of the CS/1. 2. Press the Reset switch on the CS/1. 3. Make a copy of the distribution diskette using the following command: > co where n is the number of copies to be made. The following message appears on the screen: insert master and hit return key 4. Insert the SW/20-A/BSC/SDLC Version 22010 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 your network supplier or 3Com for help. 5. Remove the SW/20-A/BSC/SDLC Version 22010 diskette from the disk drive. Insert a blank, 96-TPI, double-sided, double-density diskette in the disk drive. Press the Return key. 6. If an error message appears, remove and replace the diskette. If errors continue to occur, contact your network supplier or 3Com for help. If the copy completes successfully, the following messages appear on the screen: writing ... verifying ... OK copy completed Remove the diskette from the disk drive, and label it "SW/20- A/BSC/SDLC Version 22010." Store the distribution diskette in a safe place. You can now use the newly created diskette to upgrade your system. If your system is currently using SW/20-A/BSC/SDLC Version 20030 or earlier, it is rec ommended that you rebuild the macros, port configurations, and clearinghouse names. Otherwise, upgrade your system from SW/20-A/BSC/SDLC Version 20060 or 22000 to SW/20-A/BSC/SDLC Version 22010 using the following procedure without losing config uration, macro, and name information: 1. Insert your current working diskette in the disk drive. Then type the following command: > r 216 4003000 B200 2. After the system prompt appears again, remove the diskette and insert the newly created SW/20-A/BSC/SDLC Version 22010 diskette in the disk drive. You must wait for the disk drive's motor to stop before you go on to the next step. (approximately 20 seconds). This is necessary because the SW/20-A/BSC/SDLC Version 22010 diskette and earlier versions of the CS/1 software have different disk formats. 3. Type the following command: > w 216 4003000 B200 4. After the write is finished, remove the diskette from the disk drive. 5. For each system being upgraded, repeat steps 1 through 4. After completing step 4, be sure that the disk drive's motor has stopped before you start upgrading another system. Bugs Fixed The following is a list of problems that existed in SW/20-A/BSC/SDLC Version 22000 or earlier and have been fixed in SW/20-A/BSC/SDLC Version 22010: Setting the EOM parameter to disabled no longer causes problems when you transfer data to an X.25 host. Previously, if you set this parameter to disabled, it caused the End of Message bit to be turned on on every SPP packet. This caused data forwarding problems. Setting the ECMchar parameter to disabled on CS/1s using the SIO-16 board no longer causes null characters to be transmitted in separate packets. Previously, if you set the ECMchar parameter to disabled, each null character was sent to the CS/1 in a separate packet, increasing network traffic and data corruption. Known Problems The following is a list of Version 22010's known problems: Due to a memory limitation, the SHow CONFigurationS and SHow MACros commands no longer display output in alphabetical order. On the SIO-16 ports, the help menu of the BAud parameter displays LowAutoBaud and HiAutoBaud as options of this parameter. The SIO-16 boards, however, support only single-range autobaud. Setting the BAud parameter to LowAutoBaud or HiAutoBaud does not affect the baud rate, which ranges from 50 to 38.4K. Limitations The following is a list of Version 22010's limitations: The display generated by the SHow AllSessions command is limited to a maximum of 50 lines. Only three echo requests may be outstanding at any given time. If more than three users simultaneously enter the PIng command, the following message appears: Can't Ping now - try later Macros are cached in local memory on the CS/1. If you change or delete a macro, there is no guarantee that the change will flush the macro cache. This can cause unexpected results when macros are executed. To ensure proper execution of macros, use the ZeroMacro command to explicitly flush the local cache after changing or deleting a macro. If the CS/1s on the network receive file service, including macro file service, from an NCS, you should flush the macro cache in each Communications Server bound to the NCS every time a macro is changed or deleted on the NCS. If an NCS/150 or NC S/1 is providing the file service, use the REMOTE command to access each CS/1 bound to the NCS, and then use the ZeroMacro command on each CS/1 to flush the macro cache. If an NCS/AT is providing the file service, use the oneachserver utility on the NCS/AT. For example, at the utility prompt of the NCS/AT, type the following command: oneachserver -B zm Documentation The following manuals are provided with SW/20-A/BSC/SDLC Version 22010: Connection Service User's Guide for XNS and TCP/IP Protocols (6/88) Part Number: 09-0145-00 Connection Service User's Quick Reference Guide (12/85) Part Number: 09-0062-00 Network Management Guide (9/87) Part Number: 09-0067-02 Getting Started Guide (2/87) Part Number: 09-0043-01 Configuration Guide (2/88) Part Number: 09-0093-01 For more information on your CS/1 and network planning, refer to the following manuals: LAN Planning Guide (2/88) Part Number: 09-0085-01 CS/1 Installation Guide (10/87) Part Number: 09-0117-00 If you have any questions, contact your network supplier or 3Com for help.