TITLE: Release Notes for ComOS 3.3

SUMMARY:

Here are the release notes for ComOS 3.3. The upgrade image is available from ftp://ftp.livingston.com/pub/livingston/upgrades/pm2_3.3 You MUST also use the 12/29 version of pminstall to perform the upgrade. It is available at ftp://ftp.livingston.com/pub/livingston/upgrades/pminstall.tar

To upgrade, copy the appropriate file into your /usr/portmaster/data directory, install the new version of pminstall into your /usr/portmaster directory, THEN run /usr/portmaster/pminstall to upgrade.

WARNING! YOU MUST USE THE 12/29 VERSION OF PMINSTALL IN ORDER TO PERFORM THIS UPGRADE!

RELEASE NOTES FOR 3.1.4 --> 3.3

This document describes bug fixes and enhancements made to the PortMaster ComOS operating system between release 3.1.4 and 3.3. This release is only for the PM-2, PM-2R, PM-2E, PM-2ER. ComOS 3.3 will be released for the PM-25 (without ISDN) at a later time.

ComOS 3.3 Enhancements

  1. ISDN basic rate support has been added. This release added full support for the new ISDN expansion modules available on the PortMaster. Consult the MOD-10I-U product datasheet for a full list of supported capabilities; this datasheet is included with the MOD-10I-U 5 BRI expansion board.
  2. The ceiling on maximum active interfaces has been raised from 100 to 500 when more than 1MB of memory is found.
  3. ARP entries are now cleared on Frame Relay interfaces when LMI stops reporting the DLCI. This eliminates packet traffic on PVC's which have been disabled.
  4. Implemented idle timeouts on a per user basis. Idle timeouts can be set in the User Table or can be provided as part of the new RADIUS Idle-Timeout attribute.
  5. Implemented session limits from RADIUS. If radius returns a session time limit using the new Session-Timeout attribute, the user will be automatically disconnected when the time limit is exceeded.
  6. Implemented IP numbered interfaces for login users through the User Table. By using the "set user Username local-ip-address X.X.X.X" command, the PortMaster will advertise the local-ip-address as its IP address as to the serial interface. This function is not available in RADIUS.
  7. Implemented Port Limits on a per User basis, only for multilink V.120 and Multilink PPP users. If left unconfigured, port limits will not be imposed. MultiLink V.120 and Multilink PPP (MP) sessions will be allowed. If a port limit is set, the user will be limited to that number of ports on the PortMaster for multilink V.120 and Multilink PPP only. The command to do so is "set user Username maxports Number". This can be specified as part of the new RADIUS Port-Limit attribute.
  8. MultiLink PPP is now supported on ISDN interfaces. This is supported concurrently with the Lucent Multi-Line Load Balancing. The PortMaster will automatically detect and accept both Multi-Line Load Balancing and MultiLink PPP connections. Outbound, the PortMaster can be set to use MultiLink PPP via the Location Table by using the "set location Location_Name multilink on" command.
  9. Implemented MultiLink V.120 on ISDN interfaces. Second connections generate PowerLink128 RADIUS Accounting records.
  10. BOOTP Support has been added. Clients dialing into the PortMaster can now make BOOTP requests to determine IP address, Subnet Mask, Default Gateway, DNS server, and Domain Name. The PortMaster will only respond to BOOTP requests on its serial or ISDN lines.
  11. RADIUS Accounting has been extended to provide Called-Station-Id and Calling-Station-Id on ISDN dial-up connections.
  12. Memory management has been improved and Dynamic Load modules have been implemented. Device drivers now only load if the specific device is present in the PortMaster (ie. sync port or ISDN). In addition if SNMP or IPX are not needed they can be disabled to save memory. The commands "set ipx off" and "set snmp off" will cause the modules to not load. Any device drivers or subsystems not needed provide additional operational memory for the PortMaster. See the memory guidelines below for PortMaster memory requirements.

    IMPORTANT - to use IPX, you must now use the "set ipx on" command. If you are upgrading from a previous release and had IPX configured, it will default to on in this release. When turning IPX or SNMP off, you must do a "save all" and reboot the PortMaster before the change takes effect.

  13. Outbound PAP authentication is now supported. The PortMaster previously required the remote end to authenticate with CHAP. Now, by specifying a PAP username and Password in the Location Table dial script, the PortMaster can be authenticated by the remote end using PAP. This is done by setting the Send String in the last line of the dial script to contain the PAP information. The command is: 
    set Location_Name script Last_Line_No
"=PAP=UserName/Password"

    This will authenticate using PAP as user UserName with password Password.

  14. The administrator can now disable CHAP authentication requiring PAP authentication. This is enabled globally with the "set chap off" command.
  15. The PortMaster will now log Start records to RADIUS accounting at boot time.

Bug Fixes

  1. Users which have initiated a PPP connection using PPP autodetect and get authenticated and authorized as a SLIP user are now properly handled. Service will be denied and the PortMaster will cleanup the session. Previously a variety of symptoms would be experienced causing an incorrect active configuration.
  2. The PortMaster will no longer lose track of IP addresses it provided as assigned address from the pool. This bug caused the PortMaster to start giving out address 0.0.0.0 to dial-in hosts because it is out of addresses.
  3. The correct active user is retained for ports configured for host prompt.
  4. Serial port spurious interrupt handling has been extended to include detecting streams of framing errors. Some modems get confused about their configuration and begin sending continuous data to the PortMaster at a baud rate different than set on the PortMaster. This would cause all operation on the PortMaster to appear stopped for several minutes to several hours. The PortMaster now attempts to reset the modem and will continue to operate properly even if the modem does not recover.

UPGRADE INSTRUCTIONS

These upgrade instructions assume you have already installed the PMconsole software in /usr/portmaster. The file pminstall.tar includes new pminstall images for all platforms; after untarring it you can remove the versions that you won't be needing. 

# cd /usr/portmaster
# ftp ftp.livingston.com
	anonymous
	(enter your email address; it does not echo)
	binary
	cd pub/livingston/upgrades
	get pm2_3.3 data/pm2_3.3
	get pminstall.tar
	quit
# tar xvf pminstall.tar
# rm pminstall.tar
# ./pminstall

To upgrade to ComOS 3.3, run the new pminstall and choose the Upgrade PortMaster option, choose pm2_3.3 from the menu of upgrade choices, enter your PortMaster's hostname or IP address, enter your PortMaster's administrative password. pminstall will then upgrade your PortMaster to ComOS 3.3. READ THE FOLLOWING SECTION ON MEMORY USAGE BEFORE UPGRADING YOUR PORTMASTER!

NEW RADIUS ATTRIBUTES

To use the new RADIUS attributes with RADIUS 1.16, upgrade your PortMaster to ComOS 3.3 as described above, add the following lines to your /etc/raddb/dictionary file, kill your radiusd daemon and restart it. 

ATTRIBUTE       Session-Timeout         27      integer
ATTRIBUTE       Idle-Timeout            28      integer
ATTRIBUTE       Called-Station-Id       30      string
ATTRIBUTE       Calling-Station-Id      31      string
ATTRIBUTE       Port-Limit              62      integer

Idle-Timeout is expressed in seconds but is rounded to a minute boundary, and can be any value from 120 (2 minutes) to 14400 (4 hours). Session-Timeout is expressed in seconds but is rounded to a minute, and can be up to a year long. Note that Port-Limit only works with certain types of users; see the Enhancements section above for restrictions.

Here is an example /etc/raddb/users entry for a network user that is authenticated using a login script or PAP using her password from the UNIX /etc/passwd file, and uses PPP with an address assigned from the PortMaster's dynamic address assignment pool. She is only allowed to connect once concurrently per PortMaster. After 10 minutes (600 seconds) of idle time without any traffic she will be disconnected. After 2 hours (7200 seconds) elapsed time she will be disconnected regardless of what she's doing. 

#
# Example PPP user with address Assigned by PortMaster
  and limits
#
Pfn     Password = "UNIX"
        User-Service-Type = Framed-User,
        Framed-Protocol = PPP,
        Framed-Address = 255.255.255.254,
        Framed-MTU = 1500,
	Idle-Timeout = 600,
	Session-Timeout = 7200,
	Port-Limit = 1

MEMORY USAGE IN COMOS 3.3

PM-2E Memory Usage Guidelines

Release 3.3 will function on all existing PortMasters in about the same memory as release 3.1.4. Memory considerations are only required when adding ISDN modules to the PM-2E chassis. 

Model                 Async   Sync  ISDN   Base Memory
------------------    ------  ----  -----  -----------
PM-2E-10 + 1 ISDN     10      0       10      850K
PM-2E-10 + 2 ISDN     10      0       20      900K
PM-2E-20 + 1 ISDN     20      0       10      925K
PM-2ER-10 + 1 ISDN    10      1       10      875K
PM-2ER-10 + 2 ISDN    10      1       20      925K
PM-2ER-20 + 1 ISDN    20      1       10      950K

User Selectable Software Modules

Module          Memory Required
-----------     ---------------
SNMP            50K
IPX             20K

In addition to the base and module memory required, memory will be used to manage each table within the portmaster. The most common table requiring memory is the routing table. 5K per 100 routes should be budgeted. With these guidelines the standard 1MB (1024K) should work on most configurations. If user entries are being managed on the PM-2ER-20 + 1 ISDN and IPX and SNMP are required, the PortMaster should be upgraded to 4MB (4096K).

The PortMaster will auto-detect the physical installed memory. 30-pin 70ns SIMMs are required, and there must be 4 SIMMs, all of them either 256K, 1MB, or 4MB. Mixing SIMMs is not supported.

Copyright and Trademarks

© Copyright 1997 Lucent Technologies, Inc. All rights reserved.

The product names, "ComOS," "IRX," "PortMaster," "PMconsole," and "RADIUS" are trademarks belonging to Lucent Technologies, Inc.

All brand product names mentioned in this document are trademarks or registered trademarks of their respective manufacturers.

Notices

Lucent Technologies, Inc. makes no representations or warranties with respect to the contents or use of this manual, 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 InterNetworking Systems Technical Support

Every Lucent PortMaster or IRX¿ product comes with a one year hardware warranty. Lucent Technologies provides technical support via voice, FAX, and electronic mail. Technical support is available Monday through Friday 6am-5pm Pacific Time (GMT-8).

To contact Lucent InterNetworking Systems technical support by voice, dial 1-800-458-9966 within the US or 1-510-426-0770 outside the US, by FAX, dial 1-510-426-8951, by electronic mail, send mail to support@livingston.com, and through the World Wide Web at http://www.livingston.com/.