1999/11/4

			ComOS 3.9b24 Open Beta Release Note
				for PortMaster 3


________________ Introduction

The new Lucent Technologies ComOS(R) 3.9b24 software release 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, but is recommended only for customers who wish to test the
new functionality before the general availability (GA) release of ComOS
3.9.

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

This release note documents commands and features added between ComOS
3.9b12 and ComOS 3.9b24 on the PortMaster 3. The modem code in ComOS
3.9b24 is an upgrade to the modem code included in ComOS 3.9b12 for the
PortMaster 3.

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 back up your PortMaster
configuration before upgrading to this release.

NOTE: Any PortMaster running ComOS 3.9b24 requires 4MB of dynamic RAM
(DRAM). Use 16MB if you are running the Border Gateway Protocol (BGP).


_______________ Export Restrictions

Although this open beta release of ComOS 3.9b24 is available to any
Lucent customer worldwide, it does not include support for the Data
Encryption System (DES) and Triple DES (3DES) encryption methods.

HOwever, the Authentication Header (AH) RSA Data Security, Inc.  MD5
Message-Digest Algorithm (MD5) authentication feature of the IPSec
encryption ("coprocessor") card is available worldwide and is included
in ComOS 3.9b24.

Because of export restrictions, the DES and 3DES features for ComOS
3.9b24 will be handled on a case-by-case basis outside of the standard
beta release process.  Any US-owned or Canadian-owned company wishing
to participate in the beta release of this feature can call Cary
Hayward at 1-925-730-2637.

This restricted release of ComOS 3.9b24enc168, which supports DES and
3DES, is available in open beta form to Lucent customers in the United
States and Canada. To use DES or 3DES for encrypting data payloads, you
must install the IPSec ("coprocessor") card (PM3-VPN).

Versions of ComOS 3.9 supporting DES and 3DES on the IPSec encryption
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 "IPSecurity (IPSec)" and
"Coprocessor Card for PortMaster 3" in the ComOS 3.9b8 release note.


_______________ Contents

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


_______________ Bugs Fixed in ComOS 3.9b24

* The shortcut "sh mo" has been restored for the"show modem" command.

* The Open Shortest Path First (OSPF) protocol no longer sends
individual host advertisements for users currently dialed in that have
already been advertised as part of the assigned address pool network.


_______________ Limitations

* The network address translator (NAT) translates only TCP, UDP, and
ICMP packets. Point-to-Point Tunneling Protocol (PPTP) traffic is not
translated.

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

* The extended Link Access Procedure for Modems (LAPM) (V.42) timeout
in the ComOS 3.9b24 modem code keeps the Sega Dreamcast modem from
connecting.

* A Layer 2 Tunneling Protocol (L2TP) network server (LNS) can suppport
only 94 L2TP sessions in 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.9b24 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 encryption ("coprocessor") card, but 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.

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

* This release does not support mixing of non-facility associated
signaling (NFAS) and non-NFAS ISDN Primary Rate Interfaces (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 is 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 Address Resolution Protocol (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 NAT maps are restricted to static address maps and/or static
TCP/UDP port maps only. Outbound NAT maps do not have this limitation.

* A ComOS online help file is not included in this release; therefore,
the "help" command is not supported.


_______________ 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 theclient 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.7 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/pmvision17.txt for
installation instructions for PMVision 1.7.

*** 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! 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.9b24. If you are running an earlier release of ComOS,
upgrade to ComOS 3.5 first, reboot, then upgrade to ComOS 3.9b24.

IMPORTANT: Any PortMaster running ComOS 3.9b24 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.9b24		pm3_3.9b24	PortMaster 3


________________________________________________________________________

        Copyright and Trademarks

Copyright 1999 Lucent Technologies. All rights reserved.

PortMaster, ComOS, ChoiceNet, and NetCare are registered trademarks of
Lucent Technologies. PMVision, IRX, and PortAuthority 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.9b24
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 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. Otherwise,
send email to support@livingston.com (asia-support@livingston.com for
Asia Pacific customers).

