Release Notes for 3.1 --> 3.1.1

SUMMARY:

This document describes bug fixes and enhancements made to the PortMaster operating system between release 3.1 and 3.1.1. This release note and earlier ones are available on ftp://ftp.livingston.com/pub/livingston.

Enhancements

  1. The administration prompt has now been enhanced to display the "System Name" followed by a ">" instead of "Command>" on PortMasters which have had their System Name set (with "set sysname").
  2. Support was added for extended length messages coming from the RADIUS server. Messages can now be up to 2000 bytes long. This is accomplished by concatenating multiple "Port-Message" fields together.
  3. Scheduler latency improvements. The speed in which certain events are processed has been increased. This was accomplished by decreasing the rate at which certain non-critical events were being processed. The effect being that high priority events are processed more quickly.
  4. The Annex-D version of LMI has been added for use with Frame Relay. The command "set annex_d Interval" where "Interval" is the number of seconds between LMI requests will enable this feature. Setting "Interval" to zero (0) or enabling the older LMI will disable Annex-D.
  5. "show netconns" now truncates the hostname to fewer characters to assure that the TCP or UDP port number is not truncated.
  6. Small packet from ethernet performance enhancement. Small packets (less that 128 bytes) are now loaded directly into internal NetBufs from the Ethernet controller. This eliminates a duplicate copy, decreasing latency and enhancing throughput.
  7. "show arp frmW1" on PM2R and PM2eR now shows DLCI as well as Q.922 address. (Actually, added in 3.1)
  8. RADIUS User-Name increased from 31 characters to 63.

Bug Fixes

  1. The PortMaster "PANIC" during a save command has been fixed. After upgrading to 3.1 approximately 1% of the installed systems would experience a system PANIC when trying to save data to the FLASH file system. The bug which caused this has been removed.
  2. Users being prompted for a host, which are being authenticated by RADIUS will no longer be given the "Missing password entry" message.
  3. Inverse ARP compatibility. Inverse ARP in earlier releases was not compatible with other vendors' implementations. This has been fixed. In addition, a feature to maintain backward compatibility was added.
  4. Sync ports will now properly restart after a loss of carrier or a port reset. This only affects the PM2eR series. In some cases, after resetting the sync port, the only way to get the port to become operational was to reboot. This has been fixed.
  5. A memory leak in the IPX SAP subsystem has been removed. This leak occurred in networks with unstable, rapidly changing SAP tables.

Copyright and Trademarks

© Copyright 1997 Lucent Technologies, Inc. All rights reserved.

The product names, "ComOS," "IRX," "PortMaster," "PMconsole," and "RADIUS" are trademarks belonging to Lucent Technologies, Inc.

All brand product names mentioned in this document are trademarks or registered trademarks of their respective manufacturers.

Notices

Lucent Technologies, Inc. makes no representations or warranties with respect to the contents or use of this manual, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Lucent Technologies, Inc. reserves the right to revise this publication and to make changes to its content, any time, without obligation to notify any person or entity of such revisions or changes.

Contacting Lucent InterNetworking Systems Technical Support

Every Lucent PortMaster or IRX¿ product comes with a one year hardware warranty. Lucent Technologies provides technical support via voice, FAX, and electronic mail. Technical support is available Monday through Friday 6am-5pm Pacific Time (GMT-8).

To contact Lucent InterNetworking Systems technical support by voice, dial 1-800-458-9966 within the US or 1-510-426-0770 outside the US, by FAX, dial 1-510-426-8951, by electronic mail, send mail to support@livingston.com, and through the World Wide Web at http://www.livingston.com/.