2000/02/29

		ComOS 3.9b28 Open Beta Release Note
			for the PortMaster 3

________________ Introduction

The new Lucent Technologies ComOS(R) 3.9b28 open beta software release
is now available for the PortMaster(R) 3 Integrated Access Server.

This open beta release is provided at no charge to all Lucent
customers, but is recommended only for customers who wish to test the
new functionality before the general availability (GA) release of ComOS
3.9.

This release note documents commands and features added between ComOS
3.9b26 and ComOS 3.9b28 on the PortMaster 3. This release note applies
only to the PortMaster 3.

ComOS 3.9b28 contains modem code version i12600e.

Before upgrading, thoroughly read "ComOS 3.9b28 Limitations" and
"Upgrade Instructions", and also review the "Limitations" section in
the ComOS 3.9b26 release notes if you have not already done so.

WARNING! Due to the increased size of ComOS, the amount of
nonvolatile RAM (NVRAM) available for saving configurations
has been reduced from 128KB to 64KB. PortMaster products with
configurations greater than 64KB will lose some of their configuration.
For this reason, be sure to back up your PortMaster configuration
before upgrading to this release. You can check the amount of memory
used for your configuration with the "show files" command. Ignore
any files that also include an uncompressed size.

WARNING! The PortMaster 3 must be running ComOS 3.5 or later to upgrade
to ComOS 3.9b28. If you are running an earlier release of ComOS,
upgrade to ComOS 3.5 first, reboot, then upgrade to ComOS 3.9b28.

NOTE: Any PortMaster running ComOS 3.9b28 requires 4MB of dynamic RAM
(DRAM). Use 32MB if you are running the Border Gateway Protocol (BGP)
so that the PortMaster 3 can store the more than 70,000 BGP paths in a
full BGP feed.


_______________ Export Restrictions

This release of ComOS 3.9b28, available to any Lucent customer
worldwide, does not include support for the Data Encryption System
(DES) and Triple DES (3DES) encryption methods.

See the release note for ComOS 3.9b26 for information on availability
of export-restricted versions of ComOS 3.9b28.


_______________ Contents

Introduction
Export Restrictions
Bugs Fixed in ComOS 3.9b28
ComOS 3.9b28 Modem Limitations
Troubleshooting Modems
Upgrade Instructions
Technical Support


_______________Bugs Fixed in ComOS 3.9b28

_______ Improperly Formatted RADIUS VSAs Now Handled Properly

When a RADIUS server sends an improperly formatted vendor-specific
attribute (VSA) to the PortMaster, it is now handled properly.
Previously, improperly formatted VSAs caused the PortMaster to enter an
infinite loop. The watchdog timer would then reboot the PortMaster.

_______ Network Buffer Handling Revised

This release changes the way network buffers are handled.

_______ Miscellaneous Modem Code Updates

The following modem bugs are fixed in ComOS 3.9b28, in addition to
those documented as fixed in the ComOS 3.9b27 release note:

* The near-end echo canceller has been removed from K56flex-to-V.34
rate negotiation to improve operation.

* The aggressiveness of rates on calls coming into the PortMaster has
been reduced. The PortMaster now monitors cyclic redundancy check (CRC)
errors on inbound calls and instructs client modems to drop their rates
if necessary.

* Disconnections due to Link Access Procedure for Modems (LAPM) errors
on V.90 and K56flex connections are now reported accurately.
Previously, these were reported as call Circuit Closed disconnections
because the network detected the disconnection before ComOS did.


_______________ ComOS 3.9b28 Modem Limitations

All nonmodem limitations are the same in ComOS 3.9b28 as they
were in ComOS 3.9b26.

* Support for the obsolete "True Digital V.34 Card" (MDM-PM3-8 and
MDM-PM3-10) has been removed from this release, except for support
of the V.110 protocol. The "True Digital 56K Card" (MDM-56K-8 and
MDM-56K-10) is still supported.

* Lucent is still fixing some problems with Rockwell HCF and Cirrus
Logic modems. If you experience any difficulties with modems, verify
that the client modem is running the latest firmware. Then refer to
http://www.livingston.com/tech/bulletin/comos-modem.html. If these
instructions do not help, contact Lucent NetCare(R) technical support.

* A PCTEL modem set for K56flex in its proprietary bit will be
incorrectly identified as being set for V.90 by the PortMaster. As
a result, the modem will fail V.90 negotiations with the PortMaster
and will fall back to V.34 rates.


_______________ Troubleshooting Modems

As part of modem troubleshooting, confirm that the client modem is
running the latest firmware before submitting a modem trouble report.

When making a report of a new modem problem, send the following
information to Lucent NetCare technical support:

* ComOS version
* Client modem manufacturer
* Client modem model
* Results on the client modem of commands ATI0 through ATI11
* Whether the problem is reproducible

Lucent might want to monitor your PortMaster while the client modem
reproduces the problem.


_______________ Upgrade Instructions

You can upgrade your PortMaster 3 using PMVision 1.9 or later, or
pmupgrade 4.3 or later from PMTools. 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 comos" command from the PortMaster command line interface.

See ftp://ftp.livingston.com/pub/le/software/java/pmvision19.txt for
installation instructions for PMVision 1.9.

*** CAUTION!  If the upgrade fails, do NOT reboot!  Contact
*** Lucent NetCare Technical Support without rebooting.

The upgrade process on the PortMaster 3 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.

WARNING! Due to the increased size of ComOS, the amount of NVRAM
available for saving configurations has been reduced from 128KB to
64KB. PortMaster products with configurations greater than 64KB will
lose some of their configuration. For this reason, be sure to back up
your PortMaster configuration before upgrading to this release. You can
check the amount of memory used for your configuration with the "show
files" command. Ignore any files that also include an uncompressed
size.

WARNING! The PortMaster must be running ComOS 3.5 or later to upgrade
to ComOS 3.9b28. If you are running an earlier release of ComOS,
upgrade to ComOS 3.5 first, reboot, then upgrade to ComOS 3.9b28.

IMPORTANT: Any PortMaster running ComOS 3.9b28 requires
4MB of DRAM. If you are running BGP, 32MB of DRAM is required
so that the PortMaster 3 can store the more than 70,000 BGP paths
in a full BGP feed.

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
_________	_____________	_______________________________
3.9b28		pm3_3.9b28	PortMaster 3

______________________________________________________________

        Copyright and Trademarks

Copyright 2000 Lucent Technologies. All rights reserved.

PortMaster, ComOS, ChoiceNet, and NetCare are registered trademarks of
Lucent Technologies. PMVision, IRX, PortAuthority, and NavisRadius are
trademarks of Lucent Technologies. All other marks are the property of
their respective owners.

	Notices

Lucent Technologies 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 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 NetCare Technical Support

Lucent NetCare Professional Services provides PortMaster technical
support via voice or electronic mail, or through the World Wide Web at
http://www.livingston.com/. Specify that you are running ComOS 3.9b28
when reporting problems with this release.

Internet service providers (ISPs) and other end users in Europe, the
Middle East, Africa, India, and Pakistan must contact their authorized
Lucent NetCare sales channel partner for technical support; see
http://www.livingston.com/International/EMEA/distributors.html.

For North America, the Caribbean and Latin America (CALA), and Asia
Pacific customers, technical support is available Monday through Friday
from 7 a.m. to 5 p.m. U.S. Pacific Time (GMT -8). Dial 1-800-458-9966
within the United States (including Alaska and Hawaii), Canada, and
CALA, or 1-925-737-2100 from elsewhere, for voice support. For email
support, send to support@livingston.com (asia-support@livingston.com
for Asia Pacific customers).

