98/04/22

			ComOS 3.8b15 Open Beta Release Note


		Introduction

The new Lucent Remote Access (formerly Livingston Enterprises) 
ComOS(R) 3.8b15 beta software release is now available in Open Beta for
the PortMaster(R) 3 Integrated Access Server.  This release note
applies only to the PortMaster 3.  This open beta release is provided
at no charge to all Lucent customers.

This release note documents commands and features added between ComOS
release 3.7.2 and 3.8b15 on the PortMaster 3.

Note - This open beta release is recommended only for customers who
wish to test the new functionality before the FCS release of ComOS
3.8, particularly for V.90 dial-in.

WARNING!  Asynchronous Dial-out is not supported in this beta release;
do not use this release if you use dial-out locations with the modems.
Dial out calls will connect, and then drop within a few seconds.
ISDN dial-out is supported in this beta release.  Dialout will be
supported by FCS.

WARNING!  SLIP is not supported in this beta release.

See "Limitations" for more information before upgrading.

Note - ComOS 3.8 will be the last release supporting the old "True
Digital V.34 cards."  Starting with ComOS 3.9 only the "True Digital
56K cards" will be supported.

Note - You must use PMconsole(TM) 3.5.3 or Amber (Java PMconsole) when
upgrading to ComOS 3.8b15; see "Upgrade Instructions" below.  If you
are running Microsoft Windows 95 or Windows NT 4.0, you must use
PMconsole for Windows 3.5.1.4 or Amber.  Read "Upgrade Instructions"
thoroughly before upgrading.


		Contents

Introduction
Bugs Fixed in ComOS 3.8b15
New Features in ComOS 3.8b15
	V.90 Support
	T1 Card Support
	Async Multilink PPP (MP) via Modem Connection
	MP Packets No Longer Fragment for NEC Aterm
	X.75 Support for European ISDN
	Longer Filters
	Alternate RADIUS and ChoiceNet Ports
	RADIUS Authentication before Call Acceptance on PRI (Call Check)
	RADIUS Class Support
	Ethernet Subinterfaces
	OSPF Support over PPP Dialup
	New Command show route to-dest <Ipaddress>
	SNMP Modem Table
	SNMP Traps and Alarm Management
	Detailed Ptrace
	New PMconsole Support
	Command Line Context-Sensitive Help
	Updated Help
	Lastcall Command
	Reset Modem Command
	"show M0" Command Displays Card Type
How to use RADIUS Call Check
T1 Card Configuration
Limitations in ComOS 3.8b15
	No Dialout with modems
	No V.22 on V.34 card
	No SLIP support
Upgrade Instructions



		Bugs Fixed in ComOS 3.8b15

ComOS 3.8b15 fixes a bug where Stac compression would sometimes lose
netbufs, leading to the PortMaster 3 hanging.

In a previous release, Stac compression in conjunction with MultiChassis
PPP (MCPPP) caused netbuf loss, leading to the PortMaster 3 hanging.
This is now fixed.

In a previous release the PortMaster 3 could get stuck sending and
receiving RESET_REQUEST and RESET_ACKNOWLEDGEMNET packets used in STAC
compression to re-synchronize the compressor and the decompressor. This
is now fixed.

There was a bug in ComOS 3.8b13 where Frame Relay over the T1 Card was
not able to perform LMI or Annex-D.  This is fixed in 3.8b15.

There was a bug in 3.8b13 where the DLCI list for the T1 Card was
not saved by the "save all" command.  This is fixed in 3.8b15.

The "/" character is now permitted in usernames in the location table.

When attached to a port and doing an outbound "atdt" command, receiving
cause code 17 (User Busy) now displays a "BUSY" message.  Previous
releases displayed a misleading "NO CARRIER" message.

V.8bis tone has been improved. The volume of the V.8bis tone has been
lowered, to allow some of the older 14.4 Kbps modems to connect more
reliably.

A problem that caused modems to become stuck in the TEST state has been
fixed.  In previous releases this problem would cause "dead air"
in the US (where a user would dial in and receive no tones),
and would cause "Ring No Answer" on a-law circuits.  This is now fixed.

The "show all" speed mis-reporting problem has been fixed.  In previous
releases there were cases where a "show all" would still show the speed
of "64000" or "56000" depending on how the port was configured for
ISDN, instead of the speed the user had connected at.  This is now
fixed.

The following bugs are fixed in ComOS open beta release 3.8b15, and
were fixed in ComOS open beta release 3.8b13 as well.

Dial-out locations using PPP would sometimes fail to connect to remote
systems, and "show session" would report direction as "IN" before
disconnecting.  This problem is fixed.

Previously an unwanted addition after an upgrade of a null ethernet
incoming route-filter would filter all inbound ethernet traffic.  This
problem is fixed.

Previously, Data over Voice calls incremented the total number of
calls on a modem but did not increment the total connects, making the
statistics invalid.  This has been fixed.  Data over Voice calls no
longer increment the total number of calls on a modem.

The following bugs were fixed in ComOS interim release 3.7.2c3 and are
fixed in ComOS open beta release 3.8b15 as well.

During system startup, the Stac compression card on the PortMaster 3
sometimes failed to initialize.  This problem is now fixed.  This
release is recommended for any PortMaster 3 using the Stac compression
card.

When Redhat Linux incorrectly sends out-of-window TCP data on a Telnet
or rlogin session from the PortMaster, the PortMaster was temporarily
reporting a large window size that was confusing Linux.  The
PortMaster now properly advertises a window size of zero (0) until the
TCP window is emptied, for better interoperability with versions of
Linux that have this problem.

When the ISDN device driver runs out of receive buffers, an error
condition occurs that causes an immediate system reboot.  This symptom
has been reported as "random reboots" and will generally always send
the console message "munich_next_rd: NO BLOCKS" just before the
PortMaster reboots.  Running out of receive buffers is now properly
handled, and no longer causes a reboot.

The modem code for the "True Digital 56K Card" has been improved.
A software condition that caused the modem to not generate initial
modem tones during the answer sequence has been fixed.
Interoperability problems with several V.34 modems have been fixed.
The occasional failure to properly complete self-test has been fixed.
A problem that caused many rate renegotiations, and which sometimes
resulted in disconnection, has been fixed.

A "No Tone" problem has been fixed.  For example, suppose a user
connected to port S0 allocates modem (DSP) M0.  The user on S0
disconnects, and at the same time another user dials in on S1.  Because
the modem was already back in the ready state, S1 allocated M0.  When
S0 ran its cleanup process, it reinitialized the modem, disconnecting
the user on S1 before he heard any tones.  The console displayed the
error message "m_comio_save != NULL" to identify this behavior.

If M0 is active when "set M0 on" is entered on the command line, the
modem used to suspend service for a minute or two.  This problem is
fixed.

The LAPM code in the modems has been improved with regard to the LAPM
timer and the Echo Canceller training.



		New Features in ComOS 3.8b15

The following commands and features have been added in ComOS 3.8b15.


	V.90 Support

V.90 is now supported for Lucent and 3Com chipset client modems dialing
in.  V.90 with Rockwell chipset client modems is not supported in this
beta release, but K56flex with Rockwell chipset client modems is still
supported.  Most Rockwell modems default to K56flex.

V.90 is supported only for u-law in this beta release.

V.90 is not supported for dialout in this beta release.


	T1 Card Support

The PortMaster 3 T1 (PM3-SYNC-T1) Card is now supported; see "T1 Card
Configuration" below for more information.


	Async Multilink PPP (MP) via Modem Connection

The PortMaster 3 now supports Multilink PPP (MP) connections per RFC
1717 over asynchronous PPP dialup connections.


	MP Packets No Longer Fragment for NEC Aterm

Because the NEC Aterm ISDN terminal adapter (TA) does not accept
fragmented Multilink PPP (MP) packets, ComOS now detects this during
negotiation and sends only nonfragmented frames.


	X.75 Support for European ISDN

X.75 is now supported for European ISDN.


	Longer Filters

The PortMaster 3 now supports a maximum of 256 filter rules per
filter.  An error message is generated when the number of filter rules
exceeds the limit.


	Alternate RADIUS and ChoiceNet Ports

The UDP port to send RADIUS Authentication, RADIUS Accounting, and
ChoiceNet(R) requests is now configurable.  Different ports can be
specified for the primary and secondary servers.

 set authentic [2] Ipaddress [Port]
 set accounting [2] Ipaddress [Port]
 set choicenet [2] Ipaddress [Port]

The Port is optional, and if not specified defaults to 1645 for RADIUS,
1646 for RADIUS accounting, and 1647 for ChoiceNet, the same as in
previous releases.

If using the Livingston RADIUS server, use the -p flag to specify the
port it will listen to for RADIUS requests; it will listen for RADIUS
accounting requests on the port one higher than that.


	RADIUS Authentication before Call Acceptance on PRI (Call Check)

After receiving the command "set call-check on", the PortMaster 3 sends
a RADIUS access-request for any incoming call before accepting the
call.  The PortMaster 3 expects to receive one of the following
replies: 1) a RADIUS access-accept to accept the call and connect the
user via a netdata connection to a given host and TCP port, 2) a RADIUS
access-accept to accept the call and perform the usual RADIUS
authentication, or 3) a RADIUS access-reject to reject the call.

set call-check on | off

This command enables or disables the call-check feature.

If call-check is enabled, the "show global" command displays the
words "(Call Check Enabled)" after the ISDN switch type.

NOTE!  If call-check is enabled but no RADIUS support is configured, 
all dial-in users receive either a busy condition or dead air.
 
The dictionary on the RADIUS server must be modified to include this
entry (which might change for the full release of ComOS 3.8):

VALUE           Service-Type    Call-Check-User         129

For more information see "How to use Call Check" below.


	RADIUS Class Support

A RADIUS access-accept packet can now return Class (attribute 25, a
string).  The PortMaster will then send the unmodified Class attribute
in the accounting-request packets for that session.  To use Class
with RADIUS server 1.16, 2.0 or 2.0.1, update the dictionary to
include the following line:

ATTRIBUTE       Class			25      string


	Bandwidth Allocation Control Protocol (BACP) Supported

BACP has been implemented, in accordance with RFC 2125.

Because BACP and Bandwidth Allocation Protocol (BAP) are both
negotiated protocols, no special commands are needed to turn them on.
The only requirement for use of BAP and BACP is setting directory
numbers on the serial ports so that the PortMaster can offer a second
number to the client dialing in.  Use the following command to set a
directory number:

set <S10> directory <Number>

Replace <S10> with an ISDN port and <Number> with the access telephone
number for that port.

Example:

Command> set s0 directory 5105551234

BACP supports local exchange telephone numbers.

If a long-distance BACP user is configured to dial a local exchange
telephone number, the PortMaster now checks the Called-Station-Id when a
second channel is requested.  In this configuration the
directory numbers should not be set.


	Ethernet Subinterfaces

Multiple logical Ethernet interfaces are now allowed on one Ethernet port,
for situations that require them.

The MAC address and packet filters for subinterfaces is the same as for
the primary interface.  IPX, RIP, OSPF, and route propagation are not
supported on the subinterfaces.

Example:

add subinterface <Name>
delete subinterface <Name>
show subinterface
show table subinterface
set subinterface <Name> port <Portlabel>
set subinterface <Name> address <Ipaddress> | <Ipaddress>/<NM>
set subinterface <Name> netmask <Netmask>
set subinterface <Name> broadcast high | low
 
add subinterface <Name>
 
This command adds a subinterface entry to the subinterface table.  The
Name is used to reference the subinterface configuration in the
subinterface table, and has a maximum length of 11 characters.
It is not the name of the interface or the port the subinterface is
associated with.

Command> add subinterface enet2
New subinterface enet2 successfully added

delete subinterface <Name>

This command removes a subinterface entry from the table.

show subinterface show table subinterface

This command displays the subinterface table.

Command> show subinterface Subinterface Interface Addr
Netmask      Broadcast Addr   Port Name 
------------ ---------------- ---------------- ---------------- ---------
enet2        192.168.55.6     255.255.255.0    192.168.55.255   ether0

set subi <Name> port <Portlabel>
 
This command associates the subinterface configuration with a
physical port.
 
Command> set subinterface enet2 port ether0
enet2 changed from to ether0
 
set subinterface <Name> address <Ipaddress> | <Ipaddress>/<NM>
 
This command sets the IP address or an IP address and netmask for the
subinterface configuration.
 
Command> set subinterface enet2 address 192.168.55.6
enet2 changed from 0.0.0.0 to 192.168.55.6
 
Command> set subinterface enet2 address 192.168.55.6/27
enet2 changed from 192.168.55.6/24 to 192.168.55.6/27
 
set subinterface <Name> netmask <Netmask>
 
This command sets the netmask in dotted decimal notation for the
subinterface configuration.  This command is not needed if the netmask
is set using the classless interdomain routing (CIDR) notation (/xx) in
the previous command.

Command> set subinterface enet2 netmask 255.255.255.0 
enet2 netmask changed from 0.0.0.0 to 255.255.255.0

set subinterface <Name> broadcast high | low

This command sets the broadcast address for the subinterface.

Command> set subinterface enet2 broadcast high
enet2 broadcast address changed from low to high

ifconfig
 
The new subinterface is displayed in the "ifconfig" output.  The interface
name is system generated.
 
Command> ifconfig
ether0: flags=16<IP_UP,IPX_DOWN,BROADCAST,OSPF>
	inet 172.16.110.68 netmask fffffff0 broadcast 172.16.110.64
	area 0.0.0.64 ospf-state DROTHER mtu 1500
et01: flags=106<IP_UP,IPX_DOWN,BROADCAST,PRIVATE>
	inet 192.168.55.6 netmask ffffff00 broadcast 192.168.55.255 mtu 1500


	OSPF Support over PPP Dialup

OSPF support has been added to locations and network user profiles, for
use as dialup backup to leased lines or Frame Relay only.

Example:

Netuser OSPF commands:

set netuser <Name> ospf on|off
set netuser <Name> ospf COst <1-65535>
set netuser <Name> ospf HEllo-interval <10-120>
set netuser <Name> ospf DEad-time <40-1200>
set netuser <Name> ospf POint-to-multipoint | NBma | WAn-as-stub-ptmp
set netuser <Name> ACcept-rip on | off

Example: 

Command> set netuser test ospf on
	Username: test                   Type: Dial-in Network User
Address: Negotiated          Netmask: 255.255.255.255
	Protocol: PPP                 Options: Quiet, Compression
	MTU: 1500              Async Map: 00000000
 Port Limit: 30              Idle Timeout: 0 minutes
	OSPF: on
OSPF accept-rip: off
 OSPF cost: 1
OSPF Hello Int: 10
OSPF Dead Time: 40
OSPF(WAN Type): nbma
route-filter
	incoming:
	outgoing:

Location OSPF commands:

set location <Name> ospf on|off
set location <Name> ospf COst <1-65535>
set location <Name> ospf HEllo-interval <10-120>
set location <Name> ospf DEad-time <40-1200>
set location <Name> ospf POint-to-multipoint | NBma | WAn-as-stub-ptmp
set location <Name> ACcept-rip on | off

Command> show location test
Location: test                     Type: Manual
 Destination: Negotiated            Netmask: 255.255.255.255
Protocol: PPP                   Options: Quiet, VJ-Comp, Analog
	Group: 1                   Max Ports: 1
Idle Timeout: 0 minutes           High Mark: 0 bytes
	Mtu: 1500                Async Map: 00000000
Username: test1                Password: test1
	Telephone: 5551212
 
	OSPF: on
OSPF accept-rip: on
 OSPF cost: 1
OSPF Hello Int: 10
OSPF Dead Time: 40
OSPF(WAN Type): nbma
 

	New Command show route to-dest <Ipaddress>
 
This command shows the route in the routing table that is used to
forward an IP packet with a destination address of Ipaddress.  This
command is useful for debugging routing problems.
 
show route to-dest <Ipaddress>
 
Example:
 
The "show routes" command shows the complete routing table for this PortMaster.
 
Command> show routes
Destination        Mask Gateway              Source  Flag Met  Interface
-----------------  ---- -------------------- ------- ---- ---  ---------
0.0.0.0             0   172.16.110.2        local   NS     1  ether0
172.16.110.64      27   172.16.110.4        rip     ND     2  ether0
172.16.0.0         27   172.16.110.9        rip     ND     3  ether0
172.16.110.0       27   172.16.110.3        local   NL     1  ether0
192.168.32.0       24   172.16.110.9        rip     ND     2  ether0
10.0.0.0            8   172.16.110.9        rip     ND     3  ether0

Use "show route to-dest" to look for the particular route in the
routing table that would forward an IP packet with a destination
address of 172.16.110.68:

Command> show route to-dest 172.16.110.68
Destination        Mask Gateway              Source  Flag Met  Interface
-----------------  ---- -------------------- ------- ---- ---  ---------
172.16.110.64       27   172.16.110.4        rip     ND     2  ether0

The displayed route above is a network route with a 27-bit subnet
mask.  The route covers IP addresses 172.16.110.64 through
172.16.110.95.  The PortMaster displayed this route because
172.16.110.68 is a member of this subnet.

The next example shows a case where the default route is the route used
to forward the packet.

Command> show route to-dest 192.168.10.2
Destination        Mask Gateway              Source  Flag Met  Interface
-----------------  ---- -------------------- ------- ---- ---  ---------
0.0.0.0              0   172.16.110.2        local   NS     1  ether0


	SNMP Modem Table

Support is included for a new SNMP MIB to display the information seen
from the "show modem" command.  The MIB is available from
ftp://ftp.livingston.com/pub/le/snmp/le38.mib


	SNMP Traps and Alarm Management

A trap is a notification of an event.  An alarm is an instance of a
trap.  If SNMP is on and a reader is specified, the reader gets
traps for PRI, modem, and BRI failures.  In order for traps to be
sent, an SNMP host must be set.  The MIB for the traps is available
from ftp://ftp.livingston.com/pub/le/snmp/le38trap.mib

show alarms [<Alarm-id>]
clear alarms all | <Alarm-id>

Example:

Command> show alarms
Alarm Id    Age    Severity   Alarm Message
--------   ------  ---------  ------------------------------------------
4763864     19:11      0      T1 line(0) down
4764168     19:09      0      Modem failure: card(0) modem(8)
4772816     19:09      0      Modem failure: card(0) modem(9)

Command> show alarm 4763864
------------------------ Alarm Details --------------------------
Alarm Id: 4763864               Alarm Message: T1 line(0) down
Age in minutes:  19:11          Alarm repeated: 1 times
Severity: 0                     Reported: SNMP

Command> clear alarm 4763864
Command> show alarm
Alarm Id    Age    Severity   Alarm Message
--------   ------  ---------  ------------------------------------------
4764168     19:11      0      Modem failure: card(0) modem(8)

4772816     19:11      0      Modem failure: card(0) modem(9)

Command> clear alarm all
Command> show alarm
Alarm Id    Age    Severity   Alarm Message
--------   ------  ---------  ------------------------------------------

The "show alarms" command displays a list of each trap that occurred,
except that each recurring trap is summarized and identified by an
asterisk (*). This handling of duplicates is similar to a recurring
message in syslog.  For now, "Reported" is always SNMP and "Severity"
is always 0.


	Detailed Ptrace

An extended version of ptrace now exists that displays the Ethernet
frame for any packet matching the filter specified with the ptrace
command.  This command might not work with PPP packets, and might
display garbage past the end of the packet for UDP packets.

ptrace <Filtername> dump <0-1514>

Command> add filter u
New Filter successfully added
Command> set filter u 1 permit udp
Filter u updated
Command> ptrace u dump 128
Packet Tracing Enabled
IN  ether0 UDP from 172.16.110.4.520 to 172.16.110.0.520
ffffffff ffff00c0 05001228 08004500 005c0db9 0000ff11 0000ac10 6e04ac10
6e000208 02080048 2b580201 00000002 0000ac10 6e400000 00000000 00000000
00010002 0000c0a8 37000000 00000000 00000000 00020002 0000c0a8 0a000000
00000000 00000000 0002c392 e5e50000 00000000 00000000 00000000 04813200
IN  ether0 UDP from 172.16.110.9.520 to 172.16.110.31.520
ffffffff ffff00c0 05031d8a 08004500 0034416e 0000ff11 0000ac10 6e09ac10
6e1f0208 02080020 ed5d0201 00000002 0000ac10 6ec00000 00000000 00000000
00018d45 fe356330 61382030 61303030 30303020 30303030
IN  ether0 UDP from 172.16.110.5.520 to 172.16.110.31.520
ffffffff ffff00c0 050028ce 08004500 007022b0 0000ff11 0000ac10 6e05ac10
6e1f0208 0208005c dfd10201 00000002 0000ac10 6e600000 00000000 00000000
00020002 0000ac10 6ee80000 00000000 00000000 00010002 0000ac10 6ee00000
00000000 00000000 00010002 0000ac10 6e500000 00000000 00000000 0002ce43
Command> ptrace
Packet Tracing Disabled 


	New PMconsole Support

The new version of PMconsole (not out yet) using Java is supported by
ComOS 3.8.  Older versions of PMconsole are still supported as well.


	Command Line Context-Sensitive Help

The command line parser has been improved, and the help system has been
updated and improved.  Context-sensitive help is now available; you can
enter a question mark (?) at any point on the command line and press
Return to get a list of the keywords or values that can be entered at
that point.  Keywords use capitals to indicate the shortest permitted
abbreviation.  The "!!" command now repeats the last command (except
for any "?" in it), and you can add additional information to complete
the command.

Example:

Command> set snmp ?
ON OFf Readcommunity Writecommunity
Command> !! readcommunity ?
set snmp  readcommunity ?
 string256  NONE <CR>
Command> !! public
set snmp  readcommunity  public
SNMP read community changed to: public


	Updated Help
 
Online help from the "help" command has been updated to include all
current commands.

Example:

Command> help
add           - Add entry to table         ptrace     - Trace packet traffic
attach        - Connect direct to port     quit|exit  - Quit Console
delete        - Remove entry from table    reboot     - Restart the system
dial          - dial to a location         reset      - Reset session/port
erase         - Erase element of FLASH     rlogin     - Establish rlogin session
help          - list available commands    save       - Save current config
ifconfig      - View/configure interface   set        - Set configuration
ip|ipx        - Sets the environment       show       - Show configuration
max pmconsole - PMconsole session limit#   telnet     - Establish Telnet session
tftp          - Transfer file from host    ping       - Send ICMP packet to Dest
traceroute    - Use ICMP to detect route   pmlogin    - Establish PMD session   
version       - Display ComOS version      !!         - Repeat last command

Use "help [command]" for more ...


	Lastcall Command

This command is now available for both the "True Digital V.34 Card" and
"True Digital 56K Card".  It was available only for the 56K card in ComOS
3.7.2c3.

Use this command when you want to hot-swap a modem card without
disconnecting users.  If the modem m0 is active, you can enter the
command "set m0 lastcall" to force the modem into ADMIN mode as soon as
the user logs out.  If no user is logged in on the modem when the
command is given, the modem immediately enters the ADMIN state.
Because this ADMIN mode is not saved, a reboot brings it back to normal
operation.  The "set M0 on" command returns the modem to normal
operation without affecting the current user.

The modem status displayed by the "show M0" and "show modems" commands
is ACT(LC) instead of ACTIVE, to show that the modem status is Active
(Last Call).

If circuits are available to the PortMaster 3 but no modems
are available, the PortMaster 3 sends a user busy signal back to
the Telco when another call comes in; as a result the user receives a
busy signal instead of being forwarded to the next line in the hunt
group.  To prevent this behavior, the Telco might be able to configure
the line for "forward when busy."


	Reset Modem Command

The "reset M0" command has been added, to reset the modem and reload
its DSP code.  The "set M0 on" command does the same thing, plus places
the modem in READY state.


	"show M0" Command Displays Card Type

The "show M0" command now displays the Card Type.  This will either be
"ADI Chipset" for the "True Digital V.34 Card" or "Lucent Chipset" for
the "True Digital 56K Card".

If the card type is a Lucent Chipset, "show M0" will not print the
"Connection Failures".



		How to use RADIUS Call Check

After receiving the command "set call-check on", the PortMaster 3 sends
a RADIUS access-request for any incoming call before accepting the
call.  The PortMaster 3 expects to receive one of the following
replies: 1) a RADIUS access-accept to accept the call and connect the
user via a netdata connection to a given host and TCP port, 2) a RADIUS
access-accept to accept the call and perform the usual RADIUS
authentication, or 3) a RADIUS access-reject to reject the call.

set call-check on | off

This command enables or disables the call-check feature.

If call-check is enabled, the "show global" command displays the
words "(Call Check Enabled)" after the ISDN switch type.

NOTE!  If call-check is enabled but no RADIUS support is configured, 
all dial-in users receive either a busy condition or dead air.
 
The dictionary on the RADIUS server must be modified to include this
entry (which might change for the full release of ComOS 3.8):

VALUE           Service-Type    Call-Check-User         129

Call Check is available on the PortMaster 3 to allow an ISP to check
the phone number before answering the call.  Typical applications might
be to hang up and call the user back with no charge incurred for
connecting the user in the first place, or to limit how many people can
call a given number.  (Both of those require changes to the RADIUS
server as well.)  It also allows redirecting a call, to support virtual
POPs.  If the customer called one number, you authenticate as normally;
if they called a different number, you can accept the call but forward
all data through a netdata (TCP clear) connection to an IP address and
port of your choosing, where some other process would deal with the
user.

The incoming access-accept has a user-name set to be the
Calling-Station-Id, and a Service-Type of Call-Check-User (129 for now, but
likely to change by FCS), and all the usual info, but no password
(because the call hasn't been accepted yet, so there's been no
login/password).  Three example user entries might be like this:

# send back an access-accept to ask for login & password for this user
# he will need a usual user entry as well
9255551112	Service-Type = Call-Check-User, Calling-Station-Id = "9255551112", Called-Station-Id = "5553333"

fred	Auth-Type = System
	Service-Type = Framed-User,
	Framed-Protocol = PPP,

# Don't accept calls from this phone number
9255551113	Service-Type = Call-Check-User, Calling-Station-Id = "9255551113", Auth-Type = Reject

# redirect calls to 5552222 to host via NetData
DEFAULT	Service-Type = Call-Check-User, Calling-Station-Id = "9255551111", Called-Station-Id = "5552222"
	Service-Type = Login-User,
	Login-IP-Host = virtual.edu.com,
	Login-Service = TCP-Clear,
	Login-TCP-Port = 2000



		T1 Card Configuration

The T1 card (PM3-SYNC-T1) can be installed in any available modem slot
of a PortMaster 3 running ComOS 3.8b13 or later.  Only one T1 card is
supported in the PortMaster 3.  If additional T1 cards are inserted,
they are ignored.

The T1 Card operates the same as leased line operation of built-in
ports on the PortMaster 3 with a few exceptions.  When installed, it is
identified as "line2" and has all of the same settings as line0 and
line1.  Unused settings are ignored.  All of the line framing and
encoding types are supported.  Valid line types are "T1" and
"Fractional".  (Setting ISDN just defaults to T1 operation.) When set
to fractional, the T1 card supports only one line group.  The first
line group found (numerically) is used for the configuration.  The
fractional line group supports any number of time slots and also
supports 56K channels.

In addition to "line2", a new port will be added to the list of active
ports.  This will either be "W24" in a single PRI PortMaster 3 or "W48"
in a two PRI PortMaster 3.

If the Stac compression card is present in the PortMaster 3, Stac
compression can be enabled for the T1 line.


	Clocking

The T1 Card has one new command which is only valid for line2:
 
 set line2 clock internal | external

When internal is selected, a built in 1.544MHz crystal will drive the line.
This can be used for dry wire configurations or back-to-back connections.
When external is selected, the built in DSU/CSU will extract clock from 
the line.  External is the default.


	Fractional T1 Configuration

The T1 Card is defined as line2 in the PortMaster 3.  To configure the
card for fractional T1, use the following command:

 set line2 fractional

To set the channel group for fractional T1, use the following command:

 set line2 group <Cgroup> channel <Channel-list>

<Cgroup> is a group number from 1 to 63, or "none" to unassign channels.
<Channel-list> is a list of channels from 1 to 24, separated by spaces.
The channel numbers do not have to be contiguous.

To set the channel rate to 56 Kbps or 64 Kbps for a channel group, use
the following command:

 set line2 group <Cgroup> 56k | 64k

Note that 56 Kbps is typically used for D4 framing while 64 Kbps is used
for framing types other than D4.  64 Kbps is the default.

 save all
 reboot

If the group and the channel for fractional T1 is not set and the unit
is rebooted, you will lose the line.


	T1 Configuration

To configure the card for full T1, use the following commands:

 set line2 t1
 save all
 reboot


	Frame Relay Configuration

Refer to the "Using Frame Relay" chapter of the "Configuration Guide for
the PortMaster Products".


	Point to Point Configuration

Refer to the "Configuring a Synchronous WAN Port" chapter of the
Configuration Guide for the PortMaster Products.


	LED Indication

The LED indication of the T1 card is the same as on Line0 and Line1 of
the PortMaster 3. 

Red light only - CSU/DSU is not synchronized with switch/remote.

Red light and Green light - CSU/DSU is up and synchronized.  WAN port 
is idle or connecting.

Green light only - Port is established and fully operational.


	Troubleshooting the T1 Card

If the T1 Card is not installed correctly, the "show line2"
command displays the following error:

line2 is not available

This indicates that the card is either not present or not installed
correctly.  Remove the card, wait 5 seconds, and re-insert the card
carefully.

When the card is pulled out, the console will display the message
"Card Service: Stopping wancard in slot 0"

When the card is put in the console will display the message:
Card Service: Starting wancard in slot 0
WANCTL version 0.0
WANCTL: sync_init - found device

The "show alarms" command detects when line2 goes down (for example, if
the T1 cable is pulled out).  It does not show an alarm if the card is
removed.

Command> show alarms
Alarm Id    Age    Severity   Alarm Message
--------   ------  ---------  ------------------------------------------
2851352         0      0      T1 line(2) down
   
Command> show alarm 2851352
------------------------ Alarm Details --------------------------
Alarm Id: 2851352               Alarm Message: T1 line(2) down
Age in minutes:      0          Alarm repeated: 1 times
Severity: 0                     Reported: SNMP


	Limitations

The T1 Card is hot swappable.  However, after pulling the card out from
the PortMaster 3 slot you must wait a few seconds before inserting it
back in.  If you pull the card out and insert it back in immediately,
the PortMaster 3 will be locked up, and you must cycle power.

There was a bug in ComOS 3.8b13 where Frame Relay over the T1 Card was
not able to perform LMI or Annex-D.  This is fixed in 3.8b15.

ComOS 3.8b13 does not save the DLCI list when using Frame Relay
with the T1 Card.  This problem is fixed in ComOS 3.8b15.




		Limitations in ComOS 3.8b15


	No Dialout with Modems

Asynchronous Dial-out is not supported in this beta release.  Do not
use this release if you use dial-out locations with the modems.  ISDN
dial-out is supported in this beta release.  Dialout will be supported
by FCS.


	No V.22 on V.34 card

V.22 is no longer supported on the "True Digital V.34 Card" and
will not be supported in future releases.


	No SLIP support

SLIP is not supported in this beta release.



	Upgrade Instructions

WARNING! YOU MUST USE PMINSTALL VERSION 3.5.3 OR LATER TO PERFORM THIS
UPGRADE! If you are upgrading using PMconsole for Windows, you must use
PMconsole for Windows version 3.5.1.4 or later.  You can also use Amber
(Java PMconsole) to perform this upgrade.

*** NOTE!  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
the nonvolatile memory.  Never interrupt the upgrade process, or loss
of configuration information can result.

This upgrade does not affect your stored configuration in the
PortMaster. If you want to back up your PortMaster configuration before
upgrading, choose the Backup PortMaster button in PMconsole for
Windows, or run pmreadconf on UNIX.  The pmreadconf utility takes three
arguments: the hostname or IP address of the PortMaster, the
administrative password for the PortMaster, and the name of the file to
place the configuration in.  If you ever need to reload the
configuration, move the backup file into the /usr/portmaster/data
directory and run pminstall to reload it.  Here is an example:

cd /usr/portmaster
pmreadconf Pmname Pmpassword data/Pmname.conf
chmod 600 data/Pmname.conf

The installation software can be retrieved by FTP from
ftp://ftp.livingston.com/pub/le/software/System/Tarfile.tar.Z.
Replace System and Tarfile.tar.Z with the names of the files.  You
can retrieve the upgrade image at the same time. The following example
shows an administrator retrieving the SunOS pminstall and PortMaster 3
upgrade image:

umask 22
mkdir /usr/portmaster
cd /usr/portmaster
ftp ftp.livingston.com
 (Enter anonymous)
 (Enter your email address; it will not echo.)
	binary
	cd /pub/le/software/sun4
	get pm_3.5.3_sun4.tar.Z pm.tar.Z
	cd /pub/le/upgrades
	get pm3_3.8b15
	quit
uncompress pm.tar.Z
tar xvf pm.tar
rm pm.tar
mv pm3_3.8b15 data
pminstall

PMconsole 3.5.1.4 for Windows 95 and Windows NT 4.0 is available on
ftp://ftp.livingston.com/pub/le/software/pc/pmw3514.exe in a
self-extracting file.  Transfer that file via FTP, run the file to
install PMconsole for Windows, move the upgrade file into the data
directory, run PMconsole for Windows, and click on the Upgrade icon.

PMconsole for the following operating systems can be found under
ftp://ftp.livingston.com/pub/le/software/

bsdi/pm_3.5.3_BSDOS_2.0.tar.Z           BSD/OS 2.0 and 2.1
sgi/pm_3.5.3_IRIX_5.2.tar.Z             SGI Irix 5.2
linux/pm_3.5.3_Linux.tar.Z              Linux 1.2.13 ELF
rs6000/pm_3.5.3_RS6000_4.1.tar.Z        RS6000 AIX 4.1
alpha/pm_3.5.3_alpha_T3.0.tar.Z         Digital Alpha OSF/1 T3.0
hp/pm_3.5.3_hp9000_10.01.tar.Z          HP 9000 HP/UX 10.01
sun4/pm_3.5.3_sun4.tar.Z                SunOS 4.1.4, 5.5.1 on Sparc
sun86/pm_3.5.3_sun86_5.5.tar.Z          Solaris x86 2.5.1
pc/pmw3514.exe                          Windows 95 and Windows NT 4.0
java/amber12b1.tar			Java on UNIX
java/amber12b1.zip			Java on Windows 95 and NT

See ftp://ftp.livingston.com/pub/le/software/java/amber12b1.txt for
installation instructions for the Amber (Java PMconsole) open beta release
1.2b1.

The following upgrade image is available at
ftp://ftp.livingston.com/pub/le/upgrades/

ComOS           Upgrade Image   Product
_________       _____________   _____________________________________
3.8b15          pm3_3.8b15      PortMaster 3

The following 3 lines should be added to your RADIUS dictionary before
running ComOS 3.8b15.  Then kill and restart radiusd.

ATTRIBUTE       Class			25      string
ATTRIBUTE	Vendor-Specific		26	string
VALUE           Service-Type    Call-Check-User         129


	Copyright and Trademarks

Copyright 1998 Lucent Technologies. All rights reserved.

PortMaster, ComOS, and ChoiceNet are registered trademarks of Lucent
Technologies, Inc. RADIUS ABM, PMVision, PMconsole, and IRX are
trademarks of Lucent Technologies, Inc. ProVision is a service mark 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/.
Please specify that you are running ComOS 3.8b15 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 6 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).
