Ref: 10420002 Title: Release Notes: CS/50 TCP Booting from NCS150 ver 13010 Date: 7/30/87 Copyright 3Com Corporation, 1991. All rights reserved. Software Release SW/50-TCP Version 13010 July 30, 1987 Part Number: 86-0106-00 Revision 00 TO: CS/50 Users FROM: Bridge Communications, Inc. SUBJECT: SW/50-TCP Version 13010 DATE: July 30, 1987 Enclosed are a CS/50 and a distribution diskette containing SW/50-TCP Version 13010. This diskette should be used only to copy the software to the NCS/150 working diskette. This release memo gives the instructions for installing SW/50-TCP Version 13010 on the NCS/150. It also describes the features and compatibility of the software. Installing_SW/50-TCP_Version_13010_on_the_NCS/150 The NCS/150 working diskette can contain the software for only two product types at a time. Therefore, you must check the current contents of the diskette to ensure that there is enough room for SW/50-TCP. When the NCS/150 diskette contains the CS/50 software and software for the CS/1, CS/100, CS/200, or IVECS, it has enough room for support files for the CS/50 and one of the following: + 1 IVECS + 24 CS/1s + 24 CS/100s + 24 CS/200s To check the contents of the NCS/150 diskette, follow these steps: 1. Connect a terminal to port 0 of the NCS/150. 2. Insert the SW/150-NCS-UTIL diskette in the NCS/150 disk drive, then press the Reset key. 3. After the NCS/150 is finished booting, press the following sequence on the keyboard: . 4. Remove the SW/150-NCS-UTIL diskette, insert the SW/150 working diskette in the disk drive. Then enter the following command: ls /BIN 5. If the listing includes only the file ncs150, or the file ncs150 and one other file (cs1x, cs100x, or cs200x), proceed to step 8. 6. If the listing includes more than one file in addition to the file ncs150, the CS/1, CS/100, or CS/200 software must be removed from the diskette to make room for SW/50-TCP. 7. Remove the software for the product types that will not be supported by the NCS/150. For example, to remove the CS/1 software, use the following sequence of commands: chmod drwx BIN rm /BIN/cs1x If the software to be removed is for other Communications Servers, the pathname following the "rm" command should be "/BIN/cs100x" or "/BIN/cs200x". You should continue removing the software until there is only one software image in addition to the file ncs150. 8. Check and condense the file system on the working diskette using the FSChecK utility with the compact option: fsck -c 9. Create a file for the CS/50 by typing: cr /BIN/cs50x 190 rwx 101000 10. Ensure that the file has been created properly by entering the following command: ls -lx /BIN The address of the file, the current date, and the filename should be displayed. If the file has not been created properly, enter the following command to remove the file and return to step 9. rm 11. Copy SW/50-TCP Version 13010 to the NCS/150 diskette using the CopyFile utility: cf #0 /BIN/cs50x 12. When prompted for the source diskette, remove the NCS/150 working diskette and insert the SW/50-TCP distribution diskette. Then press the return key. 13. When prompted for the diskette that will hold the copy, remove the SW/50-TCP distribution diskette and insert the NCS/150 diskette in the disk drive. Then press the return key. 14. The copy process may require several passes. When the process is finished, the following message appears: Copy completed Some CS/50s do not include the 115/230 V slide switch described in the Series/50 Installation Guide. If present, this switch is located on the bottom of the CS/50 enclosure. If you wish to modify the CS/50 for use with a different voltage source than that specified on the back of the CS/50, and your unit does not have this switch, contact an authorized Bridge service representative for assistance. This modification must be performed by a Bridge-certified service technician if a 115/230 V slide switch is not provided on the bottom of the unit. Operating the CS/50 at an incorrect voltage setting may damage your server. Such a failure may void your warranty. Features SW/50-TCP Version 13010 has the following features: 1. The CS/50's port will match the terminal's baud rate when operating in Autobaud mode. If AutoBaud is selected, a must be entered if the terminal is operated at 150 baud or higher. must be entered if the terminal is operated at 134.5 baud or lower. The terminal may have a baud rate between 50 baud and 19.2K baud. If AutoParity is selected, a . sequence must be entered for baud rates of 150 or higher. A . sequence should be entered for baud rates of 134.5 or lower. AutoBaud and AutoParity are the default setting for terminal ports. 2. The NoMacroBreak or MacroBreak field has been added to the InterAction parameter. The NoMacroBreak option prevents users from breaking out of a macro while a macro is executing. When a NoMacroBreak option is set, the BREAK key is ignored. This feature can be used to prevent a user from breaking out of a macro in Global Network Manager privilege. 3. The BUffersize parameter in the port configuration can be set to a value smaller than the system buffer size. This feature is useful for PC-to-host file transfer applications that require smaller buffer sizes. 4. Whenever a disconnection from a host port is requested, either by a user typing the DisConnect command on the terminal or by the AutoDisconnect timer, the LogoffString will be transmitted to the host port before it closes down the circuit. LogoffString transmission is controlled by the string defined in the LogoffString parameter of the host-end server. The LogoffString can be up to 24 characters long. In order for the LogoffString to be transmitted, the AUtoLogoff parameter should be set to ON. This parameter can be set on a per-port basis. The LogoffString will not be transmitted if the disconnection is caused by the following conditions: a) A network manager uses the Listen command to listen out the host or terminal port. b) Traffic to the host port is totally flow controlled, and transmission of the LogoffString is not possible within a reasonable amount of time (currently six seconds). c) A user powers off the terminal before disconnecting the session and the UseDTRin parameter is set to AsDTR on the terminal port. The LogoffString and AUtoLogoff parameters have the following syntax: a) To set the LogoffString, enter: SETDefault LogoffString = "string" The "string" can contain any control characters; for example, "^M" for control-M, "^J" for control-J. b) To enable/disable AUtoLogoff on a particular port, enter: SETDefault (!portid) AUtoLogoff = [ON | OFF] The AUtoLogoff parameter is only available on a host port. c) To display the AUtoLogoff parameter for a particular port, enter: SHow (!portid) AUtoLogoff d) To display the LogoffString, enter: SHow LogoffString 5. Permanent virtual circuits (PVCs) support is implemented. Permanent Virtual Circuits allow automatic circuit reestablishment upon disconnection. Once a permanent virtual circuit is defined, it will be reestablished whenever the server is rebooted. After the PermanentVC parameter is set, the first connection attempt will begin in approximately 30 seconds. If the connection attempt fails or if the permanent virtual circuit is disconnected for any reason, the system will attempt to reestablish the circuit every 60 seconds. PVCs can be defined only on a host port. The destination end of the connection can be either a terminal or host port. The PVC may be defined on both ends of the circuit. In addition, PVCs may accept names. PermanentVC parameters have the following syntax: - SETDefault (!portid) PermanentVC = "
" Defines a permanent virtual circuit between a local host port and any port on the network.
can be either a physical address or a name. The name can be up to 12 characters long. - SETDefault (!portid) PermanentVC = "" Removes any previous PVC definition, but does not disconnect any existing connection. The existing circuits can be disconnected using the DisConnect or Listen command. - SHow (!portid) DefaultParameter PermanentVC Displays the current permanent virtual circuits. 6. The SHow AllSessions command has an option allowing it to display specified physical addresses or logical names of destination devices when a connection is established. For example, to display physical addresses of destination devices, use the following command: SHow AllSessions p To display logical names of destination devices, use the following command: SHow AllSessions 7. 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, CS/50, CS/100, or CS/200 with TCP/IP. For example, to perform an rlogin from a UNIX host to a non-UNIX host, enter the following command: rlogin User_Interface Refer to the Connection Service User's Guide for information on user interface commands. The commands not included in the Connection Service User's Guide are described below: - SETDefault (!) InternetPort = Assigns an Internet address to an individual physical or rotary port. - 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 specified gateway. - SETDefault PrimaryNameServer = Assigns an Internet address for the primary Name Server. The secondary Name Server will be queried if the primary Name Server does not yield a name to address resolution. - SETDefault SecondaryNameServer = Assigns an Internet address for the secondary Name Server. The primary Name Server will be queried if the secondary 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 and Default Gateway. - SHow VirtualPorts Displays the connection state (passive or active) of the physical port to which these virtual ports are connected. - SHow ARptable Displays the mapping between Internet addresses and Ethernet addresses of devices that communicate with the CS/50. The ARP always contains the unit's Internet address and the broadcast address. - ZeroArp Cleans up the contents of the ARP table. Normally, the software automatically removes an ARP entry if it cannot communicate with the device for more than 15 minutes. However, if the device has moved to a different location, this command can update the information in the ARP table faster. Compatibility SW/50-TCP Version 13010 operates with the following products and software releases: .br;NCS/AT running SW/AT-NCS Version 10000 or later .br;NCS/150 running SW/150-TCP-NCS Version 10000 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;CS/1 running SW/1-TCP Version 11000 or later .br;CS/1-SNA running SW/1-T-SNA Version 10000 or later .br;GS/3-IP running SW/3-IP Version 10000 or later .br;IVECS running SW/IVECS-TCP Version 13000 or later .br;TCPTerm Version 10000 or later Table 1 illustrates hardware and firmware compatibility of SW/50-TCP Version 13010. '' ____________________________________________ | Table 1 Software/Firmware Compatibility | |___________________________________________| | Product| Software | Firmware | | | | | | | | MP | | | | | | CS/50 | SW/50-TCP | E2 MMON Rev. 00B | |________|_____________|____________________| Documentation The current versions of the manuals for the CS/50 are: + Connection Service User's Guide (8/86) (Part number: 09-0063-01) + Network Management Guide (1/87) (Part number: 09-0067-01) + Configuration Guide (1/87) (Part number: 09-0093-00) + Getting Started Guide (1/87) (Part number: 09-0043-01) + Series/50 Installation Guide (8/87) (Part number: 09-0115-00) If you have any questions, please contact an authorized Bridge service representative for assistance. Trademarks UNIX is a registered trademark of AT&T.