2000/08/02

		ComOS 3.9b31 Open Beta Release Note
		for the PortMaster 2 and PortMaster IRX

________________ Introduction

The new Lucent Technologies ComOS(R) 3.9b31 software release is now
available for open beta for the PortMaster(R) 2 and PortMaster
IRX(TM).  Note that ComOS 3.9b31 is needed for only a PortMaster 2R,
PortMaster 2ER, or IRX that is using Frame Relay.  It is not needed
on the PortMaster 25.

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 release of ComOS 3.9.

This release note documents commands and features added between ComOS
3.9b30 and ComOS 3.9b31 on the PortMaster 2 and PortMaster IRX. This
release note applies only to these PortMaster products.

_______ WARNINGS AND IMPORTANT NOTICES
                                
IMPORTANT: Any PortMaster running ComOS 3.9b31 requires 4MB of dynamic
RAM (DRAM).

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 must be running ComOS 3.5 or later to upgrade
to ComOS 3.9b31. If you are running an earlier release of ComOS, upgrade
to ComOS 3.5 first, reboot, then upgrade to ComOS 3.9b31.

IMPORTANT: Any PortMaster IRX running the Border Gateway Protocol (BGP)
requires 16MB of dynamic RAM (DRAM) to accommodate the more than 70,000
BGP paths in a full BGP feed.  However, memory limitations prevent an
IRX that is running a full BGP feed from injecting the routes into the
routing table.

_______________ Contents

Introduction
Bugs Fixed in ComOS 3.9b31
Reconfiguring NVRAM
New Features in ComOS 3.9b31
ComOS 3.9b31 Limitations
Upgrade Instructions
Technical Support

_______________ Bugs Fixed in ComOS 3.9b31

ComOS 3.9b31 fixes a bug introduced in ComOS 3.9b30 that prevented
Frame Relay from working.  This release includes no other changes.

_______________ Reconfiguring NVRAM

After loading the new ComOS 3.9b31 and rebooting, look for messages
like the following on the console screen to verify that ComOS has
loaded successfully.  If you are upgrading from ComOS 3.9b30 to 
ComOS 3.9b31, you might not see these messages.

Testing System Memory.... 1024K
Checking Boot Rom....
Calibrating.... 33MHz
Starting FLASH Boot.....
Loading Image at 0fff0000
17110  flash copy complete
Verifying Load Module Checksum...
Starting Load Module ...
Loading kernel... 691260 bytes
Testing High Memory ... . 4096K
Loading kernel extensions... 125952 bytes
Async found in slot 1
Found 11 ports....
ether0 active ... 16K shared-RAM
Reconfiguring FLASH...
   Malloc size 65534 at 18a208
   Opened modules STD file
   Read 64506 bytes at 18a208
   read 1 buffers
   Call flash format
   Call freecntl
   Call save
   Call f_open
   Write 64506 bytes at 18a208
done - rebooting

_______________ New Features in ComOS 3.9b31

No new features were added between ComOS 3.9b30 and ComOS 3.9b31.

_______________ ComOS 3.9b31 Limitations 

The ComOS 3.9b31 release has the same limitations as ComOS 3.9b30,
except that Frame Relay now works.

_______ Limitations on Upgrading and Downgrading

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

* Downgrading a PortMaster from ComOS 3.9b31 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.

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

_______________ Upgrade Instructions

IMPORTANT: Any PortMaster running ComOS 3.9b31 requires 4MB of dynamic
RAM (DRAM).

You can upgrade your PortMaster 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 comos" 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 Technical Support without rebooting.

The upgrade process on the PortMaster 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.9b31. If you are running an earlier release of ComOS, upgrade
to ComOS 3.5 first, reboot, then upgrade to ComOS 3.9b31.

Because of the increased size of the ComOS, two separate releases for the
PortMaster 2 with ISDN are now available---one for the ISDN running in the
United States (pm2_3.9b31-usa), and one for ISDN running internationally
(pm2_3.9b31-intl).  Note that ComOS 3.9b31 is only needed for PortMaster 2R,
PortMaster 2ER or IRX if they are using Frame Relay.

Use pm2_3.9b31-usa if your ISDN switch type is one of the following:
* NI-1
* DMS-100
* 5ESS (Custom)
* 5ESS-PTP

Use pm2_3.9b31-intl if your ISDN switch type is one of the following:
* NET3
* NET3 SWISS
* VN4
* KDD
* NTT

IMPORTANT: Any PortMaster IRX running the Border Gateway Protocol (BGP)
requires 16MB of dynamic RAM (DRAM) to accommodate the more than 70,000
BGP paths in a full BGP feed.  However, memory limitations prevent an
IRX that is running a full BGP feed from injecting the routes into the
routing table.

The installation software can be retrieved by FTP from
ftp://ftp.livingston.com/pub/le/software/. The upgrade image can be
found at ftp://ftp.livingston.com/pub/le/upgrades.

ComOS		Upgrade Image	Product
_________ 	_____________ 	_____________________________________
3.9b31		pm2_3.9b31-intl	PortMaster 2 (international ISDN)
3.9b31		pm2_3.9b31-usa	PortMaster 2 (USA ISDN)
3.9b31		irx_3.9b31	PortMaster IRX-111, -112, -114, -211

____________________________________________________________________

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, NavisRadius, and
NetworkCare 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 NetworkCare Technical Support

Lucent NetworkCare 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.9b31
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 NetworkCare 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).

