- - Release Notes 93000221S for PORTSERVER II Operating System 40001260R Version 3.0.13 Software Manual P/N 92000246B Software Manual P/N 92000271A February 17, 2000 Introduction These release notes provide information on PortServer II OS version 3.0.13. They include information on the following: Incompatibility between older versions of the PortServer II OS and this one, which can affect your configuration. 1. Pre-3.0 Incompatibility Notice 2. Pre-Rev K Model ROM Limitations 3. Limitations for Systems with 2 Mb of Memory 4. Upgrading flash ROM. 5. Enhancements and added feature sets. 6. Bug fixes in this release. These include both bugs reported in Problem Report numbers. 1.Pre-3.0 Incompatibility Notice This version (3.0) of the PortServer II OS is incompatible with versions older than 3.0. Certain parts of the non-volatile storage formats used to store configuration information have been changed. Consequently, if you want to use this version of the OS and preserve your current configuration, you must use the cpconf command to save your configuration to a host and then restore it once the new version of the PortServer II OS has been installed. 2.Pre-Rev K Model ROM Limitations The addition of Frame Relay to 3.0 and later versions of the OS causes the size of the boot image to exceed the space available in the PortServer II flash ROM for units built prior to the Rev K models. Consequently, you want to use a 3.0 or later OS with these older units, you must do one of the following: * Boot PortServer II via TFTP over the ethernet port. * Acquire a smaller version of the OS, which does not have Frame Relay, this is available from the Digi ftp site. 3.Limitations for Systems with 2 Mb of Memory Testing has determined that the PortServer II's previously standard 2 Mb of installed memory is inadequate in the following instances and is likely to require an expansion to at least 4 Mb. * Full 64 port configurations in which more than 50 asynchronous and/or TCP users are simultaneously using PortServer II. This include users accessing PortServer II via the ethernet connection or any type of connection using the serial ports. * Note: Exceeding this number of users is unlikely in RealPort environments because each RealPort connection is seen as a single user. This means that while that user may control more than one port, if there is only one host connected to the PortServer II using RealPort, it will use only a little more memory than someone making a telnet connection. If more than one host is using PortServer II as a RealPort server, each host will have it's own TCP connection, and therefore each is considered a user. It is unlikely that a site will have enough RealPort connections to cause problems. * Sites with heavy traffic on serial ports. Here the problem is simply throughput. Degradation of performance may indicate that additional memory is called for. 4.Upgrading Flash ROM Should it be necessary to update the PortServer II OS contained in Flash ROM on your PortServer II, the recommended procedure is: * Obtain the new version of the software from Digi and place it on your TFTP server. * Save your current configuration using cpconf. This should not be necessary, but it is advisable to maintain a backup of your current configuration when re-writing a sizable portion of flash. * Boot your portserver with the new operating system via TFTP, by using set config boothost=hostip bootfile=filename tftpboot=yes, and then rebooting your portserver. See page 45 of the User's Guide and Reference Manual for more details. This step ensures that you have a good copy of the new version of the software, and also that you can still boot your PortServer II in the unlikely event that your flash image gets corrupted in the process of writing it. * After booting your PortServer via TFTP, load the new version of the software into the flash ROM by using the command boot load=host:filename. If all goes well, the PortServer will reply "The image now in flash memory appears valid." * Now you can return your PortServer II to booting from its flash ROM image by entering the command set config tftpboot=no. 5.Enhancements *****PortServer II OS Driver***** * PR#817 - Added ability to specify DNS hostname in 'set port dest=' and 'set user autohost='. * PR#2326 - Added feature to change SNMP community string. a) get_request (default is "pubic"). b) set_request (default is "private"). * PR#2891 & PR#3462 - Added ability to specify telnet break character to either 'none', 'any' or 'Ctl-C'. * PR#3071 - Added ability to show how much RAM is installed in psII by doing 'set config ramsize=show'. * PR#3006 - Added "dev=rp" option for "set port". * Added ability to show the ROM BIOS version by doing 'set config romversion=show'. * Added Support for Telnet RFC779. * Added support for mixing of AMD M29F040 and SGS-Thomson M29F040B Eproms. * PR#400 - Added SNMP WRITE support for MIB2, RS232 MIB, and Char MIB. Note: A third party SNMP management tool along with the correct "set_request" community string is required to modify the READ/WRITE objects. The following MIB objects support READ/WRITE attributes. MIB2 (RFC 1213) sysContact sysName sysLocation ifAdminStatus (Read-Only) atIfIndex (Read-Only) atPhysAddress (Read-Only) atNetAddress (Read-Only) ipDefaultTTL ipForwarding ipRouteDest ipRouteIfIndex (Read-Only) ipRouteMetric1 ipRouteMetric2 (Unsupported) ipRouteMetric3 (Unsupported) ipRouteMetric4 (Unsupported) ipRouteNextHop ipRouteType ipRouteAge ipRouteMask ipRouteMetric5 (Unsupported) ipNetToMediaIfIndex (Read-Only) ipNetToMediaPhysAddress ipNetToMediaNetAddress ipNetToMediaType tcpConnState snmpEnableAuthenTraps RS232 MIB (RFC1317) rs232PortOutSpeed rs232AsyncPortBits rs232AsyncPortStopBits rs232AsyncPortParity rs232AsyncPortAutobaud (Read-Only) Character MIB (RFC 1316) charPortName (Read-Only) charPortReset charPortAdminStatus (Read-Only) charPortInFlowType charPortOutFlowType charPortAdminOrigin (Read-Only) charPortSessionMaximum ***** PortServer II BIOS ***** * Added recognition and setup for mix of AMD M29F040 & SGS-Thomson M29F040B Eproms. 6. Bug Fixes ***** PortServer II OS Driver ***** * PR#1147 - cpconf loads frame relay parameters properly. * PR#2596 - telnet break now passes correctly. * PR#3048 - psII no longer crashes if doing a kill on a psuedo tty. * PR#3176 - Elliminated extra CR needed for outgoing serial connections. * PR#3427 - Changed baud rate divisor to increase actual baud rate to spec. * PR#3478 - Fixed file transfer capabilities between psII's. Previous versions would not handle control characters properly. * PR#3710 - Fixed to denied user access to commandline if "set user name= commandline=off". ***** PortServer II BIOS ***** * If psII and boothost are on the same subnet and a gateway is specified, the psII will now go directly to the boothost instead of route to the gateway during a tftpboot. * Fixed RAM memory test.