1999/7/1

			ComOS 3.9b12 Open Beta Release Note


________________ Introduction

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

This open beta release is provided at no charge to all Lucent
customers.

This open beta release is recommended only for customers who wish to test
the new functionality before the FCS release of ComOS 3.9.

This release note documents commands and features added between ComOS
3.9b9 and ComOS 3.9b12 on the PortMaster 3. The modem code in ComOS
3.9b12 is the same modem code included in ComOS 3.8.2c2 for the PortMaster 3.

NOTE: Command syntax for new commands may change between this open beta
release and the general availability (GA) release of ComOS 3.9.

This release note applies only to the PortMaster 3.

Before upgrading, thoroughly read "Limitations" and "Upgrade
Instructions."

WARNING! The amount of nonvolatile ram (NVRAM) available for saving
configurations has been reduced from 128KB to 64KB. PortMaster
products with configurations greater that 64KB will lose some of
their configuration. For this reason, be sure to backup your
PortMaster configuration before upgrading to this release.

NOTE: Any PortMaster running ComOS 3.9b12 requires 4Mb of dynamic
RAM (DRAM).  Use 16MB if running BGP.


_______________ Export Restrictions

This open beta release of ComOS 3.9b12 does not include support for the
DES and 3DES encryption methods, and is available to any Lucent
customer worldwide.

The AH MD5 authentication feature of the coprocessor card is available
worldwide and is included in ComOS 3.9b12.

Because of export restrictions, the DES and 3DES features for ComOS 3.9b12
will be handled on a case by case basis outside of the standard beta
release process.  Any U.S. or Canadian owned company wishing to participate
in the beta of this feature should call Cary Hayward at 1-925-730-2637.  
This restricted release of ComOS 3.9b12enc168 which supports DES and 3DES
is available in open beta to Lucent customers in the USA and Canada.
To use DES or 3DES for encrypting data payloads you must install the
Coprocessor Card (PM3-VPN).  

Versions of ComOS 3.9 supporting DES and 3DES on the coprocessor card
will be made available to customers in other countries as export
licensing permits. Licensing approval is being sought at this time.

For more information, see the sections on "IP Security" and
"Coprocessor Card for PortMaster 3".


_______________ Contents

Introduction
Export Restrictions
Bugs Fixed 
Limitations
Troubleshooting
Upgrade Instructions
Technical Support


_______________ Bugs Fixed in ComOS 3.9b12

* A sporadic reboot problem has been fixed.  The stack trace displayed this 
message "Assertion failed: nbuf_p->bytes_left, file mdp_os.c, line 1586".


_______________ Limitations

* Lucent Remote Access 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,
and then refer to http://www.livingston.com/tech/bulletin/comos-modem.html.
If these instructions do not help, contact Lucent Remote Access Technical
Support.

* The number of L2TP sessions supported by the LNS is 64 for this release.

* 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.

* Downgrading a PortMaster 3 from ComOS 3.9b12 to a previous release
requires two successful downgrades. After the first successful
downgrade the PortMaster is operational, but without system messages.
The second downgrade applies the system messages.

* The PortMaster 3 can support either the stac compression card or the
IPSec coprocessor card, not both. Both cards use the same interface on
the PortMaster 3 motherboard.

* Neither the Internet Key Exchange (IKE) protocol nor the Internet
Security Association Key Management Protocol (ISAKMP) is supported in
this release.

* IPSec passive profiles are not supported in this release.

* NAT and IPSec cannot be configured to work together on the same port
in this release.

* This release does not support mixing of NFAS and non-NFAS PRIs in the
same chassis. If one line is used for NFAS, the other line must be used
for NFAS or left empty.

* NFAS operates only on National ISDN (NI-2) switch types.

* Configuring NFAS settings on a line that is not configured for ISDN
or unable to perform ISDN functions makes the line behave strangely.

* When you are using NFAS and a problem occurs on the physical PRI line
with the D channel, the line sometimes does not return to service until
you reset the D channel.

* When a PortMaster running NFAS is rebooted, you must sometimes reset
the D channel to return the PRI to service.

* You must NOT downgrade from ComOS 3.9b10 to any other ComOS 3.9
version without first disabling IPX and OSPF. To do so, enter the
following commands:

set ospf disable
set ipx off
save all
reboot

* Downgrading from ComOS 3.9b10 to ComOS 3.5 might change the Ether0 IP
address.

* You cannot use Inverse ARP on a Frame Relay interface with
subinterfaces . The primary Frame Relay interface does not
automatically map IP addresses to data link connection identifiers
(DLCIs). When you enter a "show arp frm1" command, no ARP tables
appear, and the PortMaster cannot ping across the Frame Relay cloud.

* Inbound maps are restricted to static address maps and/or static
TCP/UDP port maps only. Outbound maps do not have this limitation.

* In outsource mode, you cannot configure the PortMaster to send an
ICMP reject message if it refuses a request for a NAT session. The
"icmpreject" keyword does not work as a session-direction-fail-action
(SDFA) in outsource NAT mode.

* A ComOS online help file is not included. The "help" command is not
supported.




_______________ Troubleshooting

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 technical support:

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

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


_______________ Upgrade Instructions

You can upgrade your PortMaster 3 using PMVision 1.3 or greater, or 
pmupgrade 4.0 or greater 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, or
later releases. 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/pmvision13.txt for
installation instructions for PMVision 1.3.

*** CAUTION!  If the upgrade fails, do NOT reboot!  Contact
*** Lucent Remote Access 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! 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 backup 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.

IMPORTANT: Any PortMaster running ComOS 3.9b12 requires 4MB of RAM.
If you are running BGP, 16MB of RAM is required.

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.9b12           pm3_3.9b12       PortMaster 3

________________________________________________________________________

        Copyright and Trademarks

Copyright 1999 Lucent Technologies. All rights reserved.

PortMaster, ComOS, and ChoiceNet are registered trademarks of Lucent
Technologies, Inc. RADIUS ABM, PMVision, IRX, and PortAuthority are
trademarks 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 Remote Access Technical Support

Lucent Technologies Remote Access Business Unit (previously Livingston
Enterprises) provides technical support via voice, fax, electronic
mail, or through the World Wide Web at http://www.livingston.com/.
Specify that you are running ComOS 3.9b12 when reporting problems with
this release.

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

For North and South America 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 the Caribbean, or
1-925-737-2100 from elsewhere, for voice support. Otherwise, fax to
1-925-737-2110, or send email to support@livingston.com
(asia-support@livingston.com for Asia Pacific customers).

