2000/27/11 ComOS 4.2c2 Release Note for the PortMaster 4 _______________ Introduction The Lucent Technologies ComOS(R) 4.2c2 software release is now available for general availability (GA) for the PortMaster(R) 4 Integrated Access Concentrator. This release note applies only to the PortMaster 4. This release is provided at no charge to all Lucent customers. This release note documents commands and features added and bugs fixed between ComOS 4.2 and ComOS 4.2c2 on the PortMaster 4. ComOS 4.2c1 was provided to a few customers, but was never officially released. For clarity, this release note includes two "Bugs Fixed" sections -- one for bugs fixed in ComOS 4.2c1 and one for bugs fixed in ComOS 4.2c2. This release contains the same modem code as did ComOS 4.2 for the PortMaster 4. Before upgrading, thoroughly read "Upgrade Instructions." _______________ Contents Introduction Supporting Documents Bug Fixed in ComOS 4.2c2 Bugs Fixed in ComOS 4.2c1 Improvements to ComOS 4.2c2 L2TP LNS Improvements Collect Call Blocking Improved for Brazilian Customers Upgrade Instructions Technical Support _______________ Supporting Documents * PortMaster 4 User Manual Addendum For detailed installation and configuration instructions, simple troubleshooting instructions, and command descriptions for ComOS 4.2c2 on the PortMaster 4, see this addendum at http://www.livingston.com/tech/docs/manuals.html. * PortMaster 4 Installation Guide * PortMaster 4 Configuration Guide * PortMaster 4 Command Line Reference For general PortMaster 4 documentation, see these manuals, also at http://www.livingston.com/tech/docs/manuals.html. (Or see the PortMaster 4 User Manual binder, which contains these manuals in printed form). * MIB for PortMaster 4 SNMP Agent For ComOS 4.2 extensions to the PortMaster Management Information Base (MIB), go to ftp://ftp.livingston.com/pub/le/snmp/le42.mib. _______________ Bug Fixed in ComOS 4.2c2 ComOS 4.2c2 fixes a rare problem in which the Ether1 interface stopped transmitting packets after the Ethernet chip encountered a memory contention error. This release improves error reporting and recovery algorithms so that other similar but even more unlikely problems with Ether1 will be reported and handled gracefully. _______________ Bugs Fixed in ComOS 4.2c1 The following bugs were fixed in ComOS 4.2c1: * Previously, timing problems that occurred during the dismantling of Layer 2 Tunneling Protocol (L2TP) sessions caused various problems, including reboots of the Quad T1 or Tri E1 boards. These timing problems are now fixed. * Previously, the disconnection of one channel of a Multilink PPP connection occasionally created problems on the remaining channels, which sometimes caused a Quad T1 or Tri E1 board to reboot. This behavior has been corrected. * On a PortMaster 4 functioning as an L2TP access concentrator (LAC), an unstable line carrying L2TP sessions previously caused the system to crash. The system would reboot when trying to report multiple harmless low-memory references. This behavior has been corrected. ______________ Improvements to ComOS 4.2c2 The following commands and improvements were added in ComOS 4.2c1 and retained in ComOS 4.2c2. _______ L2TP Improvements The number of L2TP sessions supported when the PortMaster 4 is functioning as an L2TP network server (LNS) has been increased to between 62 and 64 L2TP sessions per Quad T1 board. In ComOS 4.2, only about 46 to 50 L2TP session were supported per Quad T1 board. _______ Collect Call Blocking Improved for Brazilian Customers For a Tri E1 board that is already configured to multifrequency robbed bit signaling (MFR2) mode, the keywords "cbwait1" and "cbwait2" in the "set Line0 mfr2" command allow you to change collect call blocking on a per-line basis. These keywords are useful only for MFR2 profile 6, which is used in Brazil for collect call blocking. For example: set line0 mfr2 cbwait1 4 set line0 mfr2 cbwait2 20 The "cbwait1" and "cbwait2 values are specified in system ticks (1 tick = 55 ms). The default value for cbwait1 is 3 (165 ms). The default value for cbwait2 is 18 (1 second). If the value of either keyword is set to 0, the default value is used. Either value cannot be higher than 255 ticks. For these values to take effect, you must save the configuration and reboot the Tri E1 board. _______________ Upgrade Instructions You can upgrade your PortMaster 4 using PMVision 1.11, or pmupgrade from PMTools 4.4. Alternatively, you can upgrade using the older programs pminstall 3.5.3, PMconsole 3.5.3, or PMconsole for Windows 3.5.1.4. You can also upgrade using TFTP with the "tftp get" command from the PortMaster command line interface. See ftp://ftp.livingston.com/pub/le/software/java/pmvision111.txt for installation instructions for PMVision 1.11. *** CAUTION! If the upgrade fails, do NOT reboot! Contact *** Lucent NetworkCare(TM) technical support without rebooting. The upgrade process on the PortMaster 4 erases the configuration area from nonvolatile memory and saves the current configuration into nonvolatile memory. Never interrupt the upgrade process, or loss of configuration information can result. This upgrade does not otherwise affect your stored configuration in the PortMaster 4. The installation software can be retrieved by FTP from ftp://ftp.livingston.com/pub/le/software/, and the upgrade image can be found at ftp://ftp.livingston.com/pub/le/upgrades/: ComOS Upgrade Image Product _________ _____________ _______________________________ 4.2c2 pm4_4.2c2 PortMaster 4 __________________________________________________________ Copyright and Trademarks Copyright 2000 Lucent Technologies Inc. All rights reserved. PortMaster, ComOS, and ChoiceNet are registered trademarks of Lucent Technologies Inc. PMVision, IRX, PortAuthority, NetworkCare, and eSight are trademarks of Lucent Technologies. PolicyFlow is a service mark of Lucent Technologies Inc. All other marks are the property of their respective owners. Notices Lucent Technologies Inc. makes no representations or warranties with respect to the contents or use of this publication, 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 NetworkCare Technical Support Lucent NetworkCare Professional Services provides PortMaster technical support through the World Wide Web at http://www.esight.com/. Click "Contact Us" on the eSight(TM) home page for support information. Customers, sales channel partners, and value-added resellers (VARs) with active service agreements or contracts can call the following telephone numbers for technical support: o Within the United States (including Alaska and Hawaii), dial 1-800-272-3634. o Outside the United States, dial +1-510-769-6001. Specify that you are running ComOS 4.2c2 when reporting problems with this release.