ii 893-418-E
© 1994 by SynOptics Communications, Inc. All rights reserved.
Trademarks
SynOptics, SynOptics Communications, and LattisNet are registered trademarks of SynOptics
Communications, Inc. Lattis System 3000 and SynOptics Press are trademarks of SynOptics
Communications, 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, SynOptics
Communications, Inc. reserves the right to make changes to the products described in this document
without notice.
SynOptics Communications, 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
V5.1 Release Notes
893-418-E 1
Introduction
These Release Notes cover the LattisNet® Terminal Server Software Version 5.1 (hereafter referred to as
V5.1). Version 5.1 runs on Lattis System™ 3000 Model 3395/3395A Terminal Servers.
This document includes the following sections:
• New Features
• Notes and Restrictions for Model 3395 V5.1
• Known Problems in V5.1
• Problems Fixed in V5.1
• Documentation Overview
Note: Model 3395 software Version 5.1 is distributed as an included capability of Version 5.2.
Several capabilities of this software image require expanded memory. The base Model 3395
Terminal Servers have 1 MB of memory. At least one Model 773 2 MB memory option is
recommended to be installed for Version 5.1/5.2 operation.
New Features
V5.1 supports several new features and enhancements.
Extended Command Processor
As with previous versions of LattisNet terminal server software, V5.1 provides a command processor that is
similar to Digital DECserver terminal servers. The command processor includes a superset of the commands
offered on DECserver units that run the DEC LAT protocol. Similarity to the DEC command processor
makes it easier for users of DEC equipment to learn how to use and manage SynOptics® Model 3395A
Terminal Servers.
In addition to the DECserver-like interface, V5.1 offers a new command processor which provides a UNIX-
like user interface (in UNIX environments this is called a shell). This shell includes a set of commands and
system processes (called daemons in UNIX and TCP/IP environments) that provide functions similar to
those available on a UNIX host computer. Just as on UNIX hosts, there are UNIX-like server commands
that are available to all users, and commands that are available only to privileged users (superusers). This
compatibility with standard UNIX shells makes it easier to use and manage LattisNet products in UNIX and
TCP/IP environments.
V5.1 Release Notes
2893-418-E
The UNIX-like interface (ULI) and DECserver like interface (DLI) co-exist on the server. Both are enabled
by default. For the convenience of current users of the 3395A, the DLI is activated as the run-time default.
A user can activate a particular command processor at their port with a single command and can easily
switch from one command processor to the other. Also, commands from one processor are accessible even
when the other command processor is activated.
More details about extended command processor operation are included in the following sections:
• UNIX-like Commands Available for all Users
• Additional UNIX-like Commands for Superusers (Privileged Commands)
• New Commands to Enable the ULI
• New Command to Access ULI commands from the DLI or Switch to the ULI
• New Command to Access DECserver Commands from the UNIX User Interface or Switch
to the DLI
• Daemon Support
UNIX-like Commands Available for all Users
New commands have been added that are similar to UNIX commands. Table 1 defines the available
commands.
V5.1 Release Notes
893-418-E 3
Table 1. UNIX-like commands for all users
Command Function
alias Assign or view user-defined command “aliases”
arp Display the internet-to-Ethernet address translation table
connect Establish a session to a LAT or Telnet destination.
dli Issue a DECserver style command from the UNIX like interface
exit • If in superuser mode, return to normal user mode.
• If port is configured with DLI disabled, disconnect all active
sessions (jobs) and/or logout the port.
• All other port configurations, switch to DLI.
fg Bring a session to the “foreground.” This command allows the user to
make a background session the active session.
help, ? Display a brief description of one or more commands/options. Only
superusers can view privileged commands.
history Display recently-issued terminal server commands, so that one or more
specific commands can be edited and/or re-issued
hosts Display information about the domain-names available in the network
ifconfig Display Internet-related network parameters (internet-address, subnet-
mask, and broadcast address)
jobs Display session (jobs) that are currently connected to the port
kill Disconnect one or more sessions (jobs) from a port
lock Prevent other users from having access to currently connected sessions
(jobs) at a port
logout Disconnect all sessions (jobs) on the port and log out the port
lpc Check printer status
lpq Display the contents of a printer queue
netstat Display statistics about network-related activity or objects
ppp Enable PPP (Point-to-Point Protocol) on a port
queues Display the service connection queue (a list of connection requests made
to the server from the network)
rlogin Connect to a remote host using the rlogin protocol
services Display information about available LAT services
set Set values for “shell” and environment objects.
slip Enable SLIP (Serial Line Interface Protocol) on a port
source Execute a command script
stty Display port characteristics
su Become privileged (a superuser).
telnet Connect to a host using the Telnet protocol
tn3270 Connect to an IBM host using the TN3270 protocol
unalias Delete an alias that the user defined previously
unset Reset values for environment objects to defaults
who Display information about the names and port numbers of users who are
currently logged into this server
xremote Establish an Xremote session
V5.1 Release Notes
4893-418-E
Additional UNIX-like Commands for Superusers (Privileged Commands)
The commands described in Table 2 are intended to be used by those who are considered UNIX superusers,
that is, users that have special system access privileges.
Table 2. UNIX-like commands for superusers
Command Function
arp Display or modify the Internet-to-Ethernet address translation table
boot Re-initialize the server (optionally, obtain a dump)
ifconfig Configure internet-related network parameters (internet-address, subnet-mask,
and broadcast address)
lpc Manage line printers and printer queues
lprm Remove a print job from a queue
ping Elicit a response from a specified Internet destination to determine whether or
not it is on the network.
These commands are covered in more detail in Using the Model 3395/3395A Terminal Server UNIX
Operating System-like Interface.
New Commands to Enable the ULI
V5.1 provides a new privileged command, the DEFINE SERVER ULI ENABLED|DISABLED command,
to enable or disable the ULI. The UNIX-like command interface is enabled by default. The change takes
effect after you re-initialize the terminal server.
After the UNIX-like interface is enabled for the server, it can be enabled for one or more ports using a new
command, the DEFINE PORT port-list ULI ENABLED|DISABLED|PRIMARY|ONLY command. This
command specifies whether or not the UNIX-like command interface is available at a particular port, is the
default interface activated at the port, or is the only interface for the port. By default, the ULI is enabled for
the server, but is not activated at all ports. This command is covered in more detail in the V5.1 Supplement
of Commands Reference for the Model 3395/3395A Terminal Server.
New Command to Access ULI Commands from the DLI or Switch to the ULI
V5.1 includes a new command, ULI uli-command, that provides full access to UNIX-like commands, for
users who are using the DECserver like command interface. To use this command, the ULI must be enabled
at the server and port, but not activated. You can activate the ULI by typing ULI by itself (that is, without
including a uli-command). This command is covered in more detail in the V5.1 Supplement of Commands
Reference Guide for the Model 3395/3395A Terminal Server.
New Command to Access DLI Commands from the ULI or Switch to the DLI
V5.1 includes a new command, dli dli-command, which provides full access to DECserver like commands,
for users at ports for which the UNIX-like command interface is activated. You can activate the DLI by
typing DLI by itself (do not include a dli-command). This command is covered in more detail in Using the
3395/3395A Terminal Server UNIX Operating System-like Interface.
V5.1 Release Notes
893-418-E 5
Daemon Support
V5.1 improves the integration of LattisNet terminal servers into TCP/IP networks and UNIX environments
through support for a number of UNIX daemons. These daemons enhance the UNIX “look and feel” of the
server and present or use information that is typically available in a TCP/IP network.
V5.1 supports two types of daemons: server daemon implementations, and host-based daemons. Server
daemon implementations run at the server. Typically, these implementations respond to requests or process
information from the network. Host based daemons run at a UNIX host, and are used to make connections
to the server or to send data to a port. Each of these are described below.
The server daemon implementations that are supported by V5.1 include:
• lpd
This daemon provides a method for sending print jobs between UNIX systems (in this case, the server
behaves as though it were a UNIX host) and managing jobs that are in a print queue, using a protocol
that is defined in RFC 1179. The lpd command is supported in V5.1 by implementing software at the
server that responds to print requests, queries, or changes made at an lpd-compliant host, such as a
UNIX host. The Berkeley UNIX system uses lpr, lpc, lprm, and lpq commands to make print requests,
queries or changes. The AT&T System V UNIX uses lpstat, enable, and disable commands for these
functions. The lpc, lpq, and lprm commands are also available on the terminal server.
• fingerd
This daemon provides a method for exchanging information between hosts about users who are logged
on to a server, using a Finger User Information Protocol (RFC 1288). The fingerd command is
supported in V5.1 by implementing software at the server that responds to requests for information
about a user made at a UNIX host using the finger command.
This daemon provides a method for exchanging routing information among gateways or hosts, using
the Routing Information Protocol that is defined in RFC 1058. The terminal server uses this protocol
to learn about Internet routes from other hosts or gateways. In the LattisNet routed implementation, the
server listens for routing messages and updates its internal routing tables, without transmitting any
routing information to the default primary or secondary gateways or to hosts; that is, the server is a
silent router.
Note that in previous releases, LattisNet servers only updated their internal routing tables by listening
to and storing ICMP re-direct messages.
• rwhod
This daemon provides a method for collecting information about domain names on the network by
listening to rwho messages and adding currently unknown domain-names to the domain-name table.
Note that in previous releases, LattisNet servers only updated their domain name tables when the server
itself requested a domain-name from a domain name server.
• syslogd
This daemon provides a central facility to log messages about events that occur on the server. When
this daemon is enabled, the server generates records of these events which are suitable for processing by
a host-based syslog daemon. These messages can be logged at the server and/or in a file at a UNIX
host. More information about the records that can be logged can be found later in this release memo in
the description of the Enhanced Event Accounting feature.
There are a number of new DEFINE SERVER DAEMON daemon-name ENABLED| DISABLED
commands for enabling and disabling individual daemons that are described in Supplement V5.1 of
Commands Reference for the Model 3395/3395A Terminal Server. Daemons are disabled by default. A
description of how you configure and use these daemons is contained in the Software Management
Guide Supplement. There are also new lpd related commands, for managing lpd queues at a server.
These commands are described in Supplement V5.1 of Commands Reference for the Model
3395/3395A Terminal Server.
V5.1 Release Notes
6893-418-E
Also, there is now a “Daemon(s):” field on the SHOW|MONITOR SERVER ALTERNATE STATUS
and the SHOW|LIST|MONITOR UNIT displays. This field lists any daemons that are enabled at the
server.
The new host-based daemon supplied with V5.1 is:
• csportd
This daemon provides a general-purpose tool for making connections to a port and piping data to or
from that port. One could use this connection to send a file or user data to a port for printing to
PostScript printers or as a permanent connection between a host and a specific port. The csportd
command is a LattisNet-proprietary daemon and is implemented as a utility at a UNIX host. The
csportd command can be used in place of tsvr_ptyd and tsvr_filter, which are still included in the
software kit.
The csportd command comes with an installation script and a MAN page. The utility must be copied
from a UNIX media kit, then compiled and installed using the installation script.
Nested Menus
The nested menus feature on the terminal server allows you to create a series of menus with options that
can execute terminal server commands, execute scripts stored at a host, or open another menu. (For previous
versions, there was only one menu level.) By using nested menus, a server manager can create a customized
user interface for each user. Applications where this might be used include: providing very non-technical
users with a simple user interface, providing a multi-lingual user interface, or providing restricted access to
the server and network services where security is a concern.
You can enable or require nested menus at specific ports directly or via a user's login script. You create the
nested menus in a menu file that resides on a host called a script server. The terminal server obtains the
menu file from the script server when the server is initialized and uses the menus to override the LattisNet
command interface.
The Software Management Guide for the Model 3395/3395A Terminal Server includes information about
how to create login scripts. You cannot enable both the nested menus feature and the menu feature on the
same port. Refer to Supplement V5.1 of Software Management Guide for the Model 3395/3395A Terminal
Server for information about configuring and using nested menus.
Support for Van Jacobson Compression of Packets Transmitted
over Serial Line Internet Protocol (SLIP) Links
The SLIP implementation has been modified so that links can transmit and receive packets that have been
compressed using the Van Jacobson compression algorithm (refer to RFC 1144). Compression allows
SLIP links to operate with higher throughput (actual performance depends on your application). The SLIP
implementation continues to support the transmission of uncompressed packets, since not all remote
devices can use compression.
The set-up activities for establishing SLIP links are nearly identical to those contained in the Software
Management Guide for the Model 3395/3395A Terminal Server. For the situation where the port initiates
activity on the SLIP link, V5.1 provides a new command, the DEFINE|SET PORT INTERNET CSLIP
ENABLED/ DISABLED command that allows you to specify whether or not the port can initiate
communications with a remote device using compressed SLIP (CSLIP) packets. This command is covered
in Supplement V5.1 of Commands Reference for the Model 3395/3395A Terminal Server. For the situation
where the remote device initiates activity on the SLIP link, the port automatically detects whether or not
the remote device is using compressed SLIP packets. The port uses the same type (compressed or
uncompressed) of packets as the remote device. The port does this whether you have SLIP or CSLIP
enabled.
You can examine the Enabled Characteristics field on the SHOW|LIST|MONITOR PORT
CHARACTERISTICS display to determine if the port can initiate activity on the SLIP link using
compressed SLIP packets. If it is enabled, CSLIP is listed.
V5.1 Release Notes
893-418-E 7
Enhanced Event Accounting
Previous versions of the Accounting feature allowed the terminal server to store user session connection
information in an accounting log. The information available included:
• The port number where the connection was made or attempted.
• The username of the port.
• Whether the connection was a local connection or a remote connection.
• The time when the connection was first made and when it was disconnected.
• The reason why a session was terminated.
• The amount of data received by the port from the connected device and sent by the port to
the connected device.
V5.1 offers several new accounting enhancements that you can use with the existing Accounting feature.
These include the following:
• A Verbose accounting mode in which additional event types are logged. (You enable this
feature with the DEFINE|SET SERVER VERBOSE ACCOUNTING
ENABLED|DISABLED command.) Using this mode, the Accounting feature now logs
information about the following events:
– Messages from UNIX daemons (lpd, rwhod, fingerd, and routed).
– Information about PPP, SLIP, and CSLIP activity.
– Information about syntax errors that occur in a Nested Menu file.
• A more readable log file. When you enable Verbose accounting, the system formats the log
entries in a more readable format than the default log file.
• The ability to filter out certain priorities of messages from the daemons by specifying the
minimum priority for which events are recorded in the log file. (Session related entries are
always logged.) When you do, the server logs only those messages from the daemons that
have a priority equal to or below the one you specify. You do this with the DEFINE|SET
SERVER VERBOSE PRIORITY number LOG FACILITY type command.
• The ability to log messages to a remote host with a record format that is suitable for
processing by the host's syslog daemon. To enable this daemon, use the command,
DEFINE SERVER DAEMON SYSLOGD ENABLED internet-address command.
• The ability to clear the log file without initializing the terminal server with the CLEAR
SERVER ACCOUNTING command.
Refer to Supplement V5.1 of Software Management Guide for the Model 3395/3395A Terminal Server for
information about Configuring and using Accounting. The new commands are described in Supplement 5.1
of Commands Reference for the Model 3395/3395A Terminal Server Supplement 5.1.
SNMP Enhancements
V5.1 improves manageability of the server via SNMP. With V5.1, all characteristics that can be managed
from the server user interface can also be managed via SNMP.
Simplified Flash Card Loading
A new version, V2.6, of the flash card loader file (mcffs1.sys) is included with V5.1. Using this loader file,
the server looks for the appropriate image for the amount of memory that the server contains. If the server
is capable of using the multi-megabyte load image, and that image is contained on the flash card, the server
loads that image. If the server cannot find the multi-megabyte load image, it looks for the default (one-
megabyte) load image specified by the ROM configuration menu. This feature provides an easy way for
Model 3395A Terminal Server users to upgrade their servers to run a multi-megabyte load image.
All flash cards that are used for loading Model 3395A Terminal Servers contain the mcffs1.sys file. Use the
SHOW MANAGER FILES command to determine the version of file on your flash card.
V5.1 Release Notes
8893-418-E
More Flexible Flash Card Formats
With V5.1, the FORMAT CARD command will format flash memory cards differently than for previous
releases. This allows larger load images to be stored on a flash card. Table 3 shows the sizes of each area for
different FORMAT CARD options. Refer to the Software Installation Guide for SynOptics Loaders, and to
the “Updating Parameter Files on Flash Memory Cards” section of these release notes for more information.
Table 3. Area sizes for the FORMAT CARD options
Option Area 1MB Flash Card
File Size (Bytes)
1 1 64856
2 196513
3 524093
4 None
2 1 64856
2 720641
3 None
4 None
3 1 64856
2 720641
3 None
4 None
The area sizes on flash cards for Options 1, 2, and 3 are nearly the same as for previous releases. The flash
card listed in Table 3 is also called Version 2 card.
Terminal servers continue to read flash cards that were formatted to previous format standards.
Obtaining Load Images for Multi-Megabyte Terminal
Servers
By default, Model 3395 Terminal 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 megabytes 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 3395 Terminal 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 <RETURN> to start format, any other character to abort.
Press the <Return> key to format the card. This message appears:
Format in progress, please wait. xx% complete
V5.1 Release Notes
893-418-E 9
Updating the One-Megabyte Image
After the formatting is complete, enter one of the following versions of the GET CARD LOAD FILE
command, depending on where the load image files are located:
If the file exists on a VAX/VMS host, or a LattisNet loader, enter this format
TS3395>> get card load fil" ts3395.sys" ETHERNET ADDRESS ethernet-
address
If the file exists on a UNIX host, enter this format:
TS3395>> get card load file "ts3395.sys" internet address internet-
address
When you have loaded V5.1 of ts3395.sys, reinitialize the terminal server to load the new image.
TS3395>> initialize
V5.1 Release Notes
10 893-418-E
Updating the Multi-Megabyte Image
To obtain the new load image, enter the GET CARD LOAD FILE command again, with the new image
name:
If the file exists on a VAX/VMS host, or a LattisNet loader, enter this format
TS3395>> get card load file "ts3395m.sys" ethernet address ethernet
address
If the file exists on a UNIX host, enter this format:
TS3395>> get card load file "ts3395m.sys" internet address internet-
address
When you have loaded V5.1 of “ts3395m.sys," reinitialize the terminal server to load the new, larger,
image.
TS3395>> INITIALIZE
Notes and Restrictions for Model 3395 V5.1
Saving the Parameter File
SynOptics recommends that you save a renamed copy of your parameter file on the network or on separate
media, before you upgrade to V5.1. V5.1 parameter files are not backwards compatible with parameter files
for previous versions of Model 3395 software.
Note: Upgrading to V5.1 overwrites the existing parameter file on the parameter servers.
Save a copy of parameter files for previous versions of Model 3395 software in case you ever want to reload
an earlier version.
Notes on SNMP
Unsupported MIB objects
Model 3395 3395A Terminal Servers do not support the MIB objects that correspond to the following
commands:
• SHOW|LIST MANAGER EVENTS
• PURGE MANAGER LOG FILES
• PURGE MANAGER DUMP FILES
• DEFINE MANAGER ... DUMP MERIT
• DEFINE MANAGER ... DUMP ENABLED|DISABLED
• DEFINE MANAGER ... DUMP SIZE
• DEFINE MANAGER LOG FILES
• DEFINE SERVER EVENTLOG
V5.1 Release Notes
893-418-E 11
Primary Gateway Address
Setting the primary gateway address (ipGatewayAddress1 in the Internet MIB) will not return a response.
Setting this location clears the arp table so that the return packet cannot find the address of the requesting
client.
Performance Impact of SNMP Getnext Processing
Intense use of SNMP Getnext processing may degrade terminal server performance.
Bootstrap Server MIB
Objects in the named table of the Bootstrap Server MIB must use Ethernet addresses only. The object ID
namedIdentificationType can only be ethernet Address and named Identification must have a length of six
bytes. The named table is read only.
RFC 1316
Ports described by the character MIB, with values of dynamic and network for the Object ID
charAdminOrigin, show one active session when they are in listening state. This is consistent with the
SHOW PORT STATUS display.
Port Security
When you use SNMP SET processing on port security objects, you must have the set values for all five
objects in the same physical record and the record cannot contain any other set values. For example, the
following list shows the content of a single physical record that performs SNMP set processing on one
entry in the port security table.
snmpset -h 123.109.61.12 1.3.6.1.4.1.33.10.9.5.1.3.1 IPAddr 1111 \
1.3.6.1.4.1.33.10.9.5.1.4.1 IPAddr 255.0.0.0 \
1.3.6.1.4.1.33.10.9.5.1.5.1 Integer 2 \
1.3.6.1.4.1.33.10.9.5.1.6.1 Integer 1 \
1.3.6.1.4.1.33.10.9.5.1.7.1 OctetString "111111111111111"
SNMP GET and SET processing and Terminal Server Databases
SNMP GET processing reads the operational database, while SNMP SET processing modifies both the
operational database and the permanent database. Because of this, you may want to keep all ports Non-
privileged or Secure if the terminal server is managed by SNMP. This reduces the chance that the permanent
and operational databases will become unsynchronized. In the case of tables with a variable number of
entries, such as local services or domain names, this can be particularly significant.
The port security table and the menu table are accessed by an index number that may or may not point to
the same data item in the two databases.
TN3270 Devices
If you add a new entry to the TN3270 device table in the Internet MIB, SNMP will copy the VT100 device
table.
V5.1 Release Notes
12 893-418-E
TN3270 Language
If you add a new entry to the TN3270 language table in the Internet MIB, SNMP will copy the
USENGLISH table.
Addressing TN3270 Keytable/Screentable
If you are addressing the TN3270 keytable or screentable, you must use an existing device name.
Language Tables
If you are addressing an EBCDIC to ASCII or ASCII to EBCDIC language table, you must use an existing
language table name.
IP Routing Tables
You can add more than one entry to the IP routing table with the same destination address, but SNMP will
only return one of the entries.
Named Table
The Named Table is now entirely read-only. To change an entry in this table, access it with its client table
address (LattisNet Bootstrap Services MIB).
Creating and Deleting Entries in SNMP Table
Use the following guidelines to create and delete SNMP tables entries:
• To create an SNMP entry: Send an SNMP set request with a unique (non existent) objectId,
and the table status value set to valid.
– The objectId contains the keys needed to create the table entry. No other values are
required to create the entry. Any additional values needed will be given defaults by the
agent.
– Any table item that is part of the key will be read-only to prevent conflicting entries.
(Most keys in standard MIBs are read/write.)
• To delete an SNMP entry: Send an SNMP set request with the ObjectId of the table entry
you want to delete, and the table status entry set to invalid.
V5.1 Release Notes
893-418-E 13
The following tables are affected by these guidelines:
• latOfferedServiceTable
• lpdQueueTable
• namedTable (domain names)
• port SecurityTable
• parameterServerTable
• client Table
• rotaryTable
• tn3270DeviceTable
• tn3270LanguageTable
• networkLoginServerTable
Experimental MIBs
Four experimental MIBs, Ethernet-like Interface type (RFC 1284) MIB, Character MIB, RS-232-like MIB,
and Parallel-Printer-Like MIB have been removed in this release. The final branch positions for these four
MIBs are listed in Table 4.
Table 4. MIB branch positions
MIB Position
Ethernet (dot3) RFC 1284 1.3.6.1.2.1.10.7
Character RFC 1316 1.3.6.1.2.1.19
RS-232 RFC 1317 1.3.6.1.2.1.10.33
Parallel RFC 1318 1.3.6.1.2.1.10.34
All SNMP accessible counters have been changed to 4-byte unsigned numbers. Previously, some had been
2 bytes and some had been signed. All counters now reset to zero at 32 bits rather than locking at
4,294,967,295.
Special Note To Model 3395 Xremote Users
Xremote requires at least two megabytes of memory on a terminal server.
If you were previously running Xremote on your multi-megabyte terminal server, you must use the
appropriate load image for multi-megabyte terminal servers, ts3395m.img. See the section, “Load Images
for Multi-Megabyte Terminal Servers,” in these release notes, for information about how to load the new
images on your server.
V5.1 Release Notes
14 893-418-E
Known Problems in V5.1
Solicited LAT Service from a DECserver 700 Terminal Server
A terminal server running V4.4 or greater rejects a queued LAT service from a DECserver 700 terminal
server when a destination port on the terminal server is free and should be able to process the queued request.
HELP Text Issues
There are three HELP issues:
• The help text for the SET|DEFINE PORT PRIVILEGED NESTED MENU command should
be PRIVILEGED NESTED MENU ENABLE|DISABLE.
• The lpq command requires the -Pprinter argument. This argument is not optional as the help
text indicates.
• The lprm command requires both the -Pprinter and job job-number arguments. These
arguments are not optional as the help text indicates.
Duplicate Entries in the MONITOR|SHOW MANAGER CLIENT
Display
After terminal server is set to default parameters and reinitialized, the MONITOR|SHOW MANAGER
CLIENT display can occasionally show duplicate client entries for that terminal server.
Cannot Enable SLIP at Dynamic Access Ports
If you connect to a port configured for dynamic access, that is, the PORT ACCESS characteristic is set to
DYNAMIC, you cannot enable a SLIP or CSLIP link using the SET PORT IP SLIP ENABLED
command. You can specify a port access of LOCAL instead.
Duplicate Entries in the MONITOR|SHOW PARAMETER SERVER
Display
The MONITOR|SHOW PARAMETER SERVER display occasionally shows duplicate parameter server
entries for a given parameter server.
PAP Only Uses Password for Authentication
When PAP is enabled on a PPP link, the username is not used for authentication of the remote device's
connection. Only the login password is used.
Enabling PAP on the port specifies that the server requires the peer to authenticate itself, and that the server
sends a PAP password when authentication is requested by the peer. This password must be configured on
the server with the DEFINE|SET SERVER PPP PAP REMOTE PASSWORD command.
V5.1 Release Notes
893-418-E 15
Communication Server Port Daemon (csportd) Issues
There are three issues related to the csportd daemon:
• The operation of the csportd daemon running at the host will be suspended for an indefinite
period of time (“hang”) if you use the -e option (EOR reflection) with the -P (pipe) option.
• The csportd daemon running at the host will be suspended for an indefinite period of time
(“hang”) if you use the -e option (EOR reflection) and the default session mode of the
communication server serial port is set to transparent.
• Example 5 of the UNIX man page supplied with the csportd daemon is incorrect. It should
say:
To create a permanent connection to the port which can be used
by the system to provide a "hardwire" connection to a terminal
attached to the Comm Server port, do the following: (BSD systems
only!) Add the following line to /etc/ttytab.
ttyCS1 "/usr/etc/getty CommServer" unknown on local secure
Add the following entry to /etc/gettytab
CommServer:\
:p8:lm=\r\n\r\nWelcome to %h\r\nlogin\72 :
Start up csportd.
% csportd -T/dev/ttyCS1 -i CommServer 5 &
Signal the init process to read /etc/ttytab.
% kill -HUP 1
The login prompt should now appear on the terminal connected to
the Comm Server port.
SNMP Tools Can Cause Terminal Server to Fail
In rare circumstances, if you use SNMP tools to perform a GetNext operation of the system description
MIB object, data corruption by the SNMP tools will cause the terminal server to fail. The system
description MIB object is a string that consists of several items including the domain-name and system
identification/welcome text string (“Welcome to the LattisNet Terminal Server”). When this string is larger
than 127 characters, the SNMP tools process the string improperly and return corrupted data to the server,
which eventually causes the server to fail. This problem has been seen when MIT SNMP tools are used.
If you use SNMP GetNext operations to manage your terminal server, you can prevent the terminal server
from failing by limiting the system description string to 127 or fewer characters. To do this, you may want
to use a shorter domain-name or system identification/welcome text string. You can use an SNMP Get
1.3.6.1.4.1.33.13.1.9 operation to determine the length of the system description string. Then use an
SNMP Set 1.3.6.1.4.1.33.13.1.9 operation to shorten the welcome text so that the total string is 127
characters or less.
V5.1 Release Notes
16 893-418-E
SNMP MIB Object Anomalies
Table 5 lists anomalous behavior for various SNMP objects.
Table 5. SNMP MIB object anomalies
Object Name Anomaly
aToEValue SNMP Get operations return incorrect values.
basicLoginPassword Unable to set to the null ("") string.
basicPrivilegedPassword Unable to set to the null ("") string.
deviceName SNMP Get operations normally return "F1 " unless a get card
operation is in progress in which case "F1 ." is returned.
eToAValue SNMP Get operations return incorrect values.
ipRouteAge SNMP Set operations return the error, "badValue" when
“noSuchName” should be returned.
ipRouteDest SNMP Set operations return the error, "badValue" when
“noSuchName” should be returned.
tn3270DeviceName SNMP Set operations return the error, "genErr" when “noSuchName”
should be returned.
tn3270KeyDescription Unable to set a value for this object.
tn3270KeyName SNMP Set operations return the error, "badValue" when
“noSuchName” should be returned.
tn3270LanguageName SNMP Set operations return the error, "genErr" when “noSuchName”
should be returned.
tn3270PortDeviceName Unable to set to the null ("") string.
tn3270PortLanguageName Unable to set to the null ("") string.
tn3270ScreenCharacterSequence SNMP Get operations return incorrect values. Unable to set a value
for this object.
tn3270ScreenCharacterSequence Unable to set a value for this object.
PppIpcpAsyncConfigBrdcast SNMP Get operation returns incorrect values. Unable to set a value
for this object.
xPppIpcpConfigVJCompSlots Allowable range is 3 to 15.
xPppIpcpStatusState SNMP Set operations return the error, “badValue” when
“noSuchName” should be returned.
xPppLinkOpen Always returns passive (2) regardless of the status of the port PPP
link.
V5.1 Release Notes
893-418-E 17
There are three modem control issues.
• For dial in/out modems that support RNG, the port cannot be logged into. After the port asserts DTR
and observes DCD, the port Status does not change from Available to Login, even when carriage-return
characters or other characters are received by the port. Since the port does not get logged on, it deasserts
DTR after 120 seconds. For dial in/out modems that do not support RNG, logging into the port from a
dial-in connection works properly.
• For dialing into remote access ports, that is, the PORT ACCESS characteristic is set to REMOTE,
that do not support RNG, the documentation states that the “server permits data flow after the assertion
of DCD.” However, with modem control enabled on the port, and the PORT ACCESS characteristic
set to REMOTE, all characters received by the port from the modem are sent to the host making the
remote connection to the port even before DCD is asserted.
• In the dial in/out modem configuration, that is, one in which the PORT ACCESS characteristic is set
to DYNAMIC, if the modem sends characters before it asserts DCD, although they are recognized by
the port, they are ignored after DCD is observed (within 15 seconds). To be more specific, in the case
when 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 is logged in. When the PORT ACCESS
characteristic is set to DYNAMIC, this does not happen.
ULI Command Issues
There are four issues relating to ULI commands:
• The lpc status command accepts multiple printer names but only reports the status of the first printer.
For example, the command lpc status printer1 printer2 printer3 will only show the status for printer1.
• The lprm command accepts multiple job numbers but will only act on the last job number entered.
• The stty command will not return a warning if the eof char and local char parameters are set to
characters already assigned to other stty parameters.
• The lpc create command accepts the -p argument without a port-list. The queue will be created without
any ports.
IPX Printing (XPRINTER) Issues
The CLEAR XPRINTER ALL command may cause operation of several printers to be suspended on a
Novell printer server. You can use the CLEAR PRINTER printer command to clear printers individually.
Problems Fixed In V5.1
This section lists previous problems that have been fixed in version 5.1.
SNMP SETs on PPP Characteristics
Previously, you could not perform SNMP SETs on any Point-to-Point Protocol (PPP) characteristics. You
can now perform SNMP SETs on these characteristics.
PPP and Autobaud
When you disabled PPP on the port, the terminal server did not automatically enable the AUTOBAUD
feature. The server now enables the AUTOBAUD feature.
Updating Parameter Files on Flash Memory Cards
The SHOW|MONITOR PARAMETER SERVER display sometimes showed the local parameter file to be
current when no updated parameter file had been written to the memory card. This appeared to happen only
if the parameter directory on the memory card was empty and did not contain the defaults.sys file or the
parameter file. This display now shows this information accurately.
V5.1 Release Notes
18 893-418-E
SLIP- and PPP-Related Objects
SLIP- and PPP-related objects are in the MIB II Interface Table (ifTable). The interface numbers for these
objects are 1 for the Ethernet object, and 1+port-number for all other objects in the ifTable. However, the
counters for the serial interfaces returned a value of zero if a SNMP GET or GETNEXT command was used
on them. These counters now return the correct values.
Documentation Overview
The Model 3395 standard documentation set includes the following manuals. You can purchase this
documentation set from SynOptics with the order code 980-249.
•Commands Reference for the Model 3395/3395A Terminal Server, which describes the commands
that you use at the terminal server to control and monitor terminal server operation, connect and
manage terminal sessions, and configure ports, services, etc.
•Commands Reference for the Model 3395/3395A Terminal Server Supplement 5.1 , which
describes the new or modified commands which are available with V5.1 that you use at the terminal
server to control and monitor Terminal Server operation, connect and manage terminal sessions, and
configure ports, services, etc.
•Software Management Guide for the Model 3395/3395A Terminal Server, which describes
procedures that you use to manage Model 3395 software.
•Software Management Guide for the Model 3395/3395A Terminal Server Supplement 5.1, which
describes procedures that you use to manage Model 3395 software features that were introduced in
V5.1.
• Error Messages Reference for the Model 3395/3395A Terminal Server, which explains the meaning
of the status and error messages that may appear while you are using the Model 3395 software. For
some error messages, it gives a brief explanation of what you can do to correct the error.
•Using the Model 3395/3395A Terminal Server, which is a getting-started guide for first-time
terminal server users and non-technical users. This guide contains introductory information about
the Terminal Server and the commands available at secure ports.
•Using the Model 3395/3395A UNIX Operating System-like Interface, which provides a list
of available ULI commands and options.
/
