*896-066-B*
January 1995
Bay Networks, Inc. Corporate Headquarters
4401 Great America Parkway
Santa Clara, CA 95054
8 Federal Street
Billerica, MA 01821
Release Notes for the
Model 3395A Terminal
Server Software
Version 5.3
ii 896-066-B
© 1995 by Bay Networks, Inc. All rights reserved.
Trademarks
SynOptics and SynOptics Communications are registered trademarks of Bay Networks, Inc. Bay
Networks, LattisNet, and Lattis System 3000 are trademarks of Bay Networks, Inc.
Other brand and product names are registered trademarks or trademarks of their respective holders.
Statement of Conditions
In the interest of improving internal design, operational function, and/or reliability, Bay Networks,
Inc. reserves the right to make changes to the products described in this document without notice.
Bay Networks, Inc. does not assume any liability that may occur due to the use or application of the
product(s) or circuit layout(s) described herein.
Federal Communications Commission (FCC) Statement
Note: This equipment has been tested and found to comply with the limits for a Class A digital
device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable
protection against harmful interference when the equipment is operated in a commercial
environment. This equipment generates, uses, and can radiate radio frequency energy. If it is not
installed and used in accordance with the instruction manual, it may cause harmful interference to
radio communications. Operation of this equipment in a residential area is likely to cause harmful
interference, in which case users will be required to take whatever measures may be necessary to
correct the interference at their own expense.
Electromagnetic Emissions
Meets requirements of:
FCC Part 15, Subparts A and B, Class A
EN 55 022 (CISPR 22:1985), Class A
General License VDE 0871, Class B (AmtsblVfg No. 243/1991 and Vfg 46/1992)
VCCI Class 1 ITE
896-066-B 1
Introduction
Release Notes for the Model 3395A Terminal Server Software Version 5.3
include information about the Multiprotocol Communication Server software
Version 5.3 (hereafter referred to as V5.3). V5.3 runs on Lattis System 3000
™
Model 3395A Terminal Servers.
New Features
V5.3 provides several new features and enhancements, which provide greater
flexibility in making remote access connections and enhanced ease of
configu-ration and security. The new or enhanced features include:
• IPX over PPP features
• Automatic protocol detection
• IP and IPX packet filtering
• PPP enhancements
• CCL enhancements
• Miscellaneous enhancements
Except for the miscellaneous enhancements, all new and enhanced features are
described further in a new guide,
Configuring the Model 3395A Access Serving
Features
(Bay Networks part number 893-826-A).
IPX Over PPP
In Novell NetWare networks, communication is handled using a protocol
known as Internetwork Packet Exchange (IPX). IPX is a connectionless,
datagram protocol, which means that each packet contains all the information
necessary to deliver it to the final destination. The PPP specification defines
many network control protocols (NCPs) for establishing various network layer
protocols. IPX Control Protocol (IPXCP) is one such network control protocol,
and specifies a means for handling IPX traffic running over a PPP link.
CAUTION:
V5.3 parameter files are not backwards compatible with
parameter files for previous versions of Multiprotocol Communication Server
software. Bay Networks™ recommends that you save a renamed copy of your
parameter file on the network or on separate media, before you upgrade to
V5.3.
NOTE:
V5.3 requires multimegabyte memory capacity. Memory for the
Model 3395 Terminal Server cannot be expanded. Be sure that you have a
Model 3395A Terminal Server with at least one set of expansion SIMMs to
support the multimegabyte image. Memory expansion for the Model 3395A
server is available by ordering the Model 773 SIMM Memory Option Kit.
Release Notes for the Model 3395A Terminal Server Software Version 5.3
2 896-066-B
With V5.3 software, an access server can provide transparent access to IPX
services, devices, or networks. Specific applications include:
• Connecting a remote (dial-in) workstation or PC to the network.
This is a typical remote office or user-to-LAN application. Figure
1
depicts this IPXCP configuration.
Figure 1. Basic IPXCP configuration using an access server
In this application, the users at the remote IPX clients have access to the Novell
services offered on the Novell NetWare network (unless the network manager
chooses to limit that access). The user dials in when he or she needs access to
the services, and disconnects when the services are no longer needed.
• Connecting a remote network to the local network through a serial port.
In this application, the port functions as a router connecting two networks.
Figure
2 illustrates an IPX configuration.
5433
Remote
IPX clients
Ethernet Local Area
Network (LAN)
Model 3000 Chassis
with Model 3395A
Server
PPP links
Modems
Modems
Novell NetWare
File Servers
Novell NetWare NetworkRemote Users
Printers
896-066-B 3
New Features
Figure 2. IPX "LAN-to-LAN" configuration using access servers
In this application, the users at one Ethernet LAN have access to all Novell
services offered at the other Ethernet LAN, and vice versa. In Figure
2, the PPP
link between the access servers is a local connection that would typically be a
null-modem connection. The connection will normally be a permanent link.
• Connecting a host, workstation, or PC directly to the network through a
connection to a serial port (usually a null-modem cable).
This application would be useful for connecting a device that does not
support an Ethernet connection to the access server so that it has access to
services available on the Novell network. The PC or workstation needs an
IPX client program and the ability to communicate over a PPP link.
IPX is a keyed software feature and requires a password to be enabled on the
access server. Contact your Bay Networks sales representative or distributor for
more information about obtaining a password and the documentation, which
describes how to configure this feature on the Model 3395A server.
5434
Model 3000 Chassis
with Model 3395A
Server running PPP
Model 3000 Chassis
with Model 3395A
Server running PPP
Ethernet Local Area
Network (LAN) 2
Ethernet Local Area
Network (LAN) 1
PC's
Novell NetWare
File Server
Novell NetWare
File Server
Host
Systems
VAX/VMS
System
UNIX System
PPP
Link
Release Notes for the Model 3395A Terminal Server Software Version 5.3
4 896-066-B
IPX implementation of the Model 3395A server includes the following
features:
• IPX client support
The access server can communicate with any RFC 1552-compliant IPXCP
(IPX over PPP) client software implementation. A version of the Stampede
Remote Office client software is qualified for use with Model 3395A servers.
Contact your sales representative or distributor for more information.
• Tested with Stampede, Inc. Remote Office IPXCP client software package
• Standard NetWare addressing methods
The IPX protocol specifies the address of each system using a network
number, node number, and socket number. Network numbers identify
NetWare network segments. Node numbers identify individual nodes on a
network segment. Socket numbers identify the different applications
within a single host. The multiprotocol software uses this standard
addressing method. For information about IPX addressing, refer to
Novell
System Concepts
supplied with your Novell NetWare software.
• Setup and administration using native procedures
You use the IPX client setup and administration procedures to configure
the remote IPX client. The IPX client setup activities are described in the
documentation supplied with your IPX client software package. You use
Model 3395A server commands to configure the access server.
• IPX RIP and SAP support
In some network configurations, an access server operates as an
asynchronous IPX router. IPX routers exchange information about the
networks where they are attached, and the networks they can reach,
through IPX Router Information Protocol (IPX RIP) packets. IPX routers
use RIP information to route IPX packets. Each IPX router maintains a
table of RIP information that it has received from other routers. IPX
routers also broadcast RIP packets to neighboring routers periodically.
Servers in an IPX network (such as file servers and print servers) advertise
their services through Service Advertising Protocol (SAP) packets. IPX
servers also answer requests by clients who are looking for their services.
IPX routers are responsible for broadcasting SAP information to other
IPX routers in the network, and functioning as a proxy for servers on other
networks.
Each IPX router maintains a table of SAP information that it has received
from neighboring routers and servers.
NOTE:
When a NetWare client wants to connect to a service, the client
broadcasts a request for the service. All IPX routers that have the service
in their SAP tables respond to the request, based on the split horizon
algorithm.
896-066-B 5
New Features
RIP and SAP route-propagation is performed using a “split horizon
algorithm.”
• Compatibility with Model 3395A server security mechanisms
IPX can be used in conjunction with all Model 3395A server access
security methods, including Kerberos and SecurID authentication.
• Product support
The IPX feature is supported on Model 3395A servers that have six or
more wires and can run the TS3395m.img multimegabyte load image.
Automatic Protocol Detection
Access server ports can be configured to accept connections made via different
protocols, using Automatic Protocol Detection (APD). Using APD, ports will
automatically determine the protocol being used to make a connection and
adjust port settings appropriately. Alternatively, by not enabling APD, ports can
be dedicated for use by a single access serving protocol. Key features of APD
include:
• An individual port can be configured to accept any connections made via
ARAP, PPP, SLIP (which includes CSLIP), and interactive protocols, as
well as all or none of these.
• Ports can be configured to limit the amount of time spent in an attempt to
determine which protocol is being used to make a connection. When the
time expires, then the port will either default to a specific protocol, or log
out the connection, as specified by the server manager.
IP and IPX Packet Filtering
A Model 3395A server has a single network interface (Ethernet connection)
and multiple, separate, asynchronous interfaces (serial ports). Each interface
can be configured with IP or IPX filters. These filters are used to allow certain
IP or IPX traffic to pass through the server. The filters can specify network
destination or source address, protocol, packet type, as well as other
filter-specific criteria. Filtering is disabled by default.
The software can be configured to filter IP traffic, based on the following
criteria:
• Source or destination address or network (internet-address and/or subnet)
• IP packet type (port number, protocol, setting of TCP SYN bit)
NOTE:
This algorithm indicates that when broadcasting RIP routes or
SAP announcements to a given network, an individual router should only
include data that the other network is not likely to know. For example, a
router must not advertise a route to a network that it had learned from
that network.
Release Notes for the Model 3395A Terminal Server Software Version 5.3
6 896-066-B
The software can be configured to filter IPX traffic, based on the following
criteria:
• Source or destination address or network (IPX network number and node
number)
• IPX packet type
The multiprotocol software also permits you to configure the software to limit
broadcasting, learning, and use of IPX RIP route or SAP service information.
You can create import and export filters for these packets.
Import filters enable you to control the information that a server adds to its IPX
RIP or SAP table. The server either accepts or discards routes and services that
meet the criteria, based on instructions from the filter.
Export filters enable you to control the routing or service information that a
router sends to the network. The router either advertises or hides routes or
services that meet the criteria, based on instructions from the filter.
PPP Enhancements
A number of enhancements have been made to the PPP implementation. They
include the following changes:
• There is a new command to specify the frequency at which the port(s) will
send a Link Control Protocol (LCP) echo request packet over the PPP link
to the connection partner. The command is:
DEFINE PORT
port-list
PPP KEEPALIVE TIMER
time
SET PORT
port-list
PPP KEEPALIVE TIMER
time
• Valid values for
time
are 0 through 255 (seconds). The default is 0, which
means that the PPP link will not send LCP echo request packets.
• There is a new command to specify the amount of time which the port(s)
should wait to receive an LCP echo reply packet from the connection
partner before terminating the PPP link. The command is:
DEFINE PORT
port-list
PPP KEEPALIVE TIMEOUT
time
SET PORT p
ort-list
PPP KEEPALIVE TIMEOUT
time
• Valid values for
time
are 0 through 255 (seconds). The default is 0, which
means that the PPP link will not look for LCP echo reply packets. The
presence of other PPP traffic does not affect this timeout period (that is, if
the connection partner does not send an LCP echo reply packet, the link
will be terminated even if other traffic has been sent).
• There is a new command to specify the range of Internet addresses that the
PPP link will allow to be negotiated. Internet addresses outside the range
will not be permitted by the link. The command is:
DEFINE PORT
port-list
PPP IP REMOTE ADDRESS RANGE
addr-range
SET PORT
port-list
PPP IP REMOTE ADDRESS RANGE
addr-range
896-066-B 7
New Features
• Valid values for
addr-range
are two Internet addresses separated by a
hyphen. The first Internet address in the address range represents the
lowest acceptable address. The second Internet address in the address
range represents the highest acceptable address.
• There is a new command to specify whether or not PPP negotiation
packets will be logged in the verbose accounting log, and the format in
which they will be logged. This should only be used as a diagnostic tool in
the event of interoperability problems.
DEFINE PORT
port-list
PPP PACKET LOGGING
setting
SET PORT
port-list
PPP PACKET LOGGING
setting
Valid values for
setting
include NONE, INTERPRETED, or RAW. The
default is NONE.
CCL Enhancements
Command Control Language (CCL) scripts are files that contain commands
that initialize a modem, configure communication between the modem and the
device to which it is connected, and manage call-answering and call-hang-up
activities.
CCL scripts were originally designed to be used with AppleTalk Remote
Access Protocol (ARAP). While CCL scripts are required for ARAP
connections, beginning with V5.3 they can also be used to initialize the port
and modem for other types of connections (PPP, SLIP, interactive, etc.). There
are some benefits to using CCL scripts even at ports where ARAP connections
will not be used. First, you can use CCL scripts as an easy way of programming
the modems. Second, you can think of a CCL as an alternate method of
“autobauding” the serial port connected to the modem, since the CCL will
determine the appropriate port speed and set it accordingly.
The Model 3395A server software kit provides CCL scripts for selected
modem types that have been tested with Model 3395A servers. Model 3395A
servers also supply CCL scripts that have been modified to take advantage of
the following features:
• Kerberos and SecurID authentication features when making ARAP
connections. (These CCL scripts were first made available in V5.2.)
• V.42 LAPM error correction or V.42bis data compression for
“non-ARAP” connections (PPP, SLIP, interactive, etc.) at ports that use
Automatic Protocol Detection (APD) to support both ARAP and
non-ARAP connections. (These CCL scripts are new for V5.3.)
AppleTalk Remote Access (Version 1) required that modem connections be
made without using any error correction or data compression methods. The
modified CCL scripts allows the server to accept ARAP connections without
using error correction and data compression, while non-ARAP connections can
negotiate these options.
You do not need to use a CCL script with these modifications if APD is not
enabled at the port, or if ARAP is not among the connection types (protocols)
that will be accepted at a port where APD is enabled.
Release Notes for the Model 3395A Terminal Server Software Version 5.3
8 896-066-B
Miscellaneous Enhancements
The following miscellaneous enhancements have been made to the
Model 3395A Terminal Server:
• UNIX-like interface (ULI) enhancements
The ULI displays information about IPX sessions, SERVER, and PORT
parameters in the ifconfig and netstat displays. The ifconfig command
displays and modifies information about Internet characteristics, and the
netstat command displays information about protocol sessions.
Software kit changes
The following changes have been made to the Model 3395A server software
kits:
• UNIX PC diskette now available
A UNIX-format floppy diskette containing the host.tar, ccl.tar, and
apgen.tar archives is now available. The latest version of the ccl.tar archive
contains CCL scripts that support modem-based (V.42bis) compression
for "non-ARAP” connections. This diskette is included
with the Model 770-05 Version 5.3 Terminal Server Software Kit.
• Macintosh CCL diskette available
A Macintosh-compatible floppy diskette containing a variety of CCL
scripts is available. This diskette is included with the Model 770-05
Version 5.3 Terminal Server Software Kit.
Contact your local Bay Networks sales representative or distributor for
more information about these products.
Notes and Restrictions
Saving the Parameter File
Bay Networks recommends that you save a renamed copy of your parameter
file on the network or on separate media, before you upgrade to V5.3.
Upgrading to V5.3 overwrites the existing parameter file on the parameter
servers, and you might need the saved copy if you ever wanted to reload an
earlier version of Model 3395A server software.
NOTE:
V5.3 parameter files are not backwards compatible with parameter
files for previous versions of the Model 3395A server software.
896-066-B 9
Notes and Restrictions
Flash Card Vendors
T
able 1 lists vendors that currently support flash cards for the Model 3395A
server.
Compatibility with ACE/Server Software
V5.3 SecurID client software is based on V1.1 of the ACE/Server software
supplied by Security Dynamics Technologies, Inc. V5.3 will operate with ACE/
Server host running ACE/Server software V1.1, or later.
AppleTalk Remote Access (ARAP) Notes
The following notes apply to the AppleTalk Remote Access implementation:
• When there is no TFTP script server available on the network, CCL scripts
and dial-back scripts will be unavailable.
• ARAP supports only one login password, which is shared by all ARAP
users. When Kerberos or SecurID authentication are performed, a
username may be used which has an associated password and/or passcode.
• When Kerberos or SecurID authentication are not used, the server does
not restrict access by user name. A user can login via remote access using
any user name, as long as the user specifies the correct server password.
Specific user names are only used for locating a telephone number for
dial-back.
• In order to prevent AppleTalk “name collisions,” it is unadvisable to have
more than one remote access server with a given name on an AppleTalk
network.
CCL Notes
The following notes apply to using modem-based compression with V5.3:
• ARAP connections cannot use modem-based compression (compression
must be done by the communication server).
Typically, CCL scripts contain commands that prevent the modem from
negotiating V.42 LAM-M error correction or V.42bis compression. If you
want to use modem-based V.42 LAM-M error correction or V.42bis
compression for connections that are made using particular protocols
(excluding ARAP), you must use CCL scripts which permit this feature to
be negotiated. Refer to Chapter 8 of
Configuring the Model 3395A Access
Serving Features
for more information.
Table 1. 1 MB flash card vendors
Vendor name Part number
Mitsubishi
MF81M1-G1EAT01
Fujitsu MB98A1011-20
Centennial FL01M-15-10131-01
Panasonic BNT-0111HFRE
Intel IMC001FLKA-200
Release Notes for the Model 3395A Terminal Server Software Version 5.3
10 896-066-B
• Modem-based MNP error correction is not supported at ports that use
CCL scripts.
APD Notes
The following notes apply to using APD with V5.3:
• In order to use APD, the port must be configured with PORT ACCESS set
to LOCAL. Therefore, APD cannot be used with dial-out or dial-back
ports.
Known Problems in V5.3
T
able 2 lists the known problems in the Model 3395A server V5.3 software and
their workarounds.
Problems Fixed
The following problems have been fixed with the V5.3 release:
• ARAP connections disconnected
Rarely, a unit established an ARAP session and then immediately (within
1 second) disconnected the session. This problem affected units running
ts3395m.img with ARAP and APD enabled.
• Disabling PPP
Table 2. Known problems with V5.3 software
Problem description Comments/workaround
Incorrect PAP status shown in display.
When PAP authentication is not enabled at
a port at which PPP is enabled, the "PAP
Status" field of the SHOW/LIST/MONITOR
PPP STATUS display incorrectly shows the
status as "OPEN" rather than "N/A."
Be aware that "OPEN" indicates that PAP is
not enabled at a port which has PPP
enabled.
Autoconfigured subnet-mask not used
by server.
When a unit has a predefined subnet mask
(that is, one specified with the DEFINE
SERVER INTERNET SUBNET MASK
subnet-mask
command) and the server
manager subsequently decides to use the
"AUTOCONFIGURE ENABLED" option,
when the unit is reinitialized, it still uses the
predefined subnet mask, rather than
calculating the correct mask (based on the
class of network) and using the calculated
value.
Immediately after reinitializing a unit, use
the SET SERVER INTERNET SUBNET
MASK AUTOCONFIGURE ENABLED
command, or manually specify the desired
subnet mask with a DEFINE SERVER
INTERNET SUBNET MASK
subnet-mask
command.
896-066-B 11
Documentation Overview
The server did not free up packet buffers (system resources) allocated to
a PPP link when one used the SET PORT port-list PPP DISABLED
command and then logged out the port to terminate the PPP link. This
problem affected units running ts3395m.img with PPP enabled.
• Modem control
– For dial in/out modems (that is, the PORT ACCESS characteristic is
set to DYNAMIC), when the PORT AUTOBAUD characteristic was
set to DISABLED, for modem applications that supported use of the
RING signal, the port could not be logged in.
– When dialing in to a remote access port (that is, the PORT ACCESS
characteristic is set to REMOTE and the PORT MODEM CONTROL
characteristic is set to ENABLED) using a modem application that
does not support RING, characters received by the port from the
modem were sent to the host making the remote connection, even
before the modem asserted DCD.
– In dial-in modem configurations (that is, one in which the PORT
ACCESS characteristic is set to LOCAL), any characters received by
the port before DCD was observed became part of the username after
the port was logged in. This could have been a problem when the
modem issued spurious characters while it tried to complete making
the connection.
• Duplicate entries in the SHOW/ MONITOR MANAGER CLIENT display
After a unit was set to default parameters and reinitialized, the SHOW/
MONITOR MANAGER CLIENT display would occasionally show
duplicate client entries for that unit.
• ULI command
There were two issues related to ULI commands:
– The “lpc status” command accepted multiple printer names but only
reported the status of the first printer. For example, “lpc status printer1
printer2 printer3” only showed the status for printer1.
– The “lprm” command accepted multiple job numbers but only acted on
the last job number entered.
• Incorrect HELP text
The HELP text for the DEFINE SERVER ARAP PASSWORD indicated
that the default password is ACCESS. The correct password is access.
Documentation Overview
One of the following documents is supplied with your V5.3 software:
• LattisNet Model 3395 Software Installation Guide, UNIX/DOS, which
describes procedures that you use to install Model 3395A server software
on UNIX hosts. This guide is only supplied with UNIX software kits (Bay
Networks part number 893-184-B).
Release Notes for the Model 3395A Terminal Server Software Version 5.3
12 896-066-B
• LattisNet Model 3395 Software Installation Guide, VMS, which describes
procedures that you use to install Model 3395A server software on VAX/
VMS hosts. This guide is only supplied with VMS software kits (Bay
Networks part number 893-163-B).
The Model 3395/3395A Documentation Set, Version 5.2 (Bay Networks part
number DS595-3395-52) includes the following manuals:
• The Model 3395/3395A Commands Reference describes the commands
that you use at the access server to control and monitor access server
operation, connect and manage terminal sessions, and configure ports,
services, and so on (Bay Networks part number 893-159-C).
• The Model 3395/3395A Software Management Guide describes
procedures that you use to manage Model 3395A server software (Bay
Networks part number 893-158-C).
• The Model 3395/3395A Error Messages Reference explains the meaning
of the status and error messages that may appear while you are using the
software. For some error messages, it gives a brief explanation of what
you can do to correct the error (Bay Networks part number 893-768-A).
• Using the Model 3395/3395A Terminal Server is a getting-started guide
for first-time access server users and nontechnical users. This guide
contains introductory information about the access server and the
commands available at secure ports. (Bay Networks part number
893-386-B)
• Using the Model 3395/3395A UNIX Operating System-Like Interface
provides a list of available ULI commands and options (Bay Networks
part number 893-764-A).
896-066-B 13
Documentation Clarifications and Additions
Documentation Clarifications and Additions
The following documentation clarification should be noted for Chapter 18 of
the Model 3395/3395A Software Management Guide Supplement 5.1 (Bay
Networks part number 893-762-A):
• To configure a port to require a privileged nested menu, you need to use
following two commands:
DEFINE/SET PORT PRIVILEGED NESTED MENUS
DEFINE/SET PORT NESTED MENUS REQUIRED
These commands must be typed in the order shown.
Obtaining Load Images for Multimegabyte Servers
By default, the Model 3395A server loads the standard load images when you
initialize them. These load images are named ts3395.img and ts3395m.img.
(The server needs at least 3 MB of memory to see the “m” image.)
The SHOW SERVER ALTERNATE STATUS display lists the amount of
memory on the terminal server in the Installed Memory field.
A Model 3395A server can obtain a load image from the network, or locally,
from a memory card. The next sections explain the procedures you use in each
of these cases.
Updating a Local Memory Card
To update the image on a flash memory card requires a two-step process. First,
load both new load images onto a network host. This can be a UNIX host, a
VAX/VMS host, or a LattisNet
®
loader. When you have loaded both images on
the network host, rename both image names from “.img” to “.sys.” Insert the
memory card into the card drive of the terminal server and format the card:
TS3395>>> format card
XXX format. WARNING: all data will be lost.
Press the RETURN key to start the format, any other character to abort.
Press the RETURN key to format the card. This message appears:
Format in progress, please wait. xx% complete
/
