
              NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:              ATSUP.EXE Enhancements to AppleTalk
DOCUMENT ID:        TID000045
DOCUMENT REVISION:  A
DATE:               01JUL93
ALERT STATUS:       Yellow
INFORMATION TYPE:   Symptom Solution
README FOR:         ATSUP.EXE

NOVELL PRODUCT and VERSION:
NetWare for Macintosh 3.011

ABSTRACT:
This file contains enhancements and fixes made to problems in previous
releases of the NetWare AppleTalk Support Package.  In particular, this
file details major new functionality in the NetWare AppleTalk Support
Package v3.011 software.  It includes the newest APPLETLK.NLM and SNMP
Support.  It also includes a new ATCON.NLM.
_________________________________________________________________

DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. 
NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. 
HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION
ONLY.  NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS
INFORMATION.
_________________________________________________________________

Self-Extracting File Name:  ATSUP.EXE

Files Included     Size     Date        Time

   ATSUP.TXT          (This File)
   ORDER.FRM       3288    4-27-92      1:58p
PINSTALL.NLM      60157    1-21-92      5:31p
   ATCFG.NLM      47074    1-21-92      5:32p
   ATREM.NLM      51193    1-21-92      5:32p
   ATCON.NLM     178917    3-10-92      9:26a
APPLETLK.NLM     216504    3-04-92     11:05a
ATTOKLLC.NLM       2460    9-18-91      3:39p
ATLKSNMP.NLM       1403    3-03-92      6:32p


NETWARE APPLETALK SUPPORT PACKAGE v3.011 RELEASE NOTES
(c) Copyright 1992, Novell, Inc. All rights reserved.


Welcome to the NetWare AppleTalk Support Package v3.011! This file contains
enhancements and fixes made to problems in previous releases of the NetWare
AppleTalk Support Package. In particular, this file details major new
functionality in the NetWare AppleTalk Support Package v3.011 software:

- SNMP SUPPORT IN NETWARE APPLETALK SUPPORT PACKAGE
- NEW FUNCTIONALITY IN ATCON
- ADDITIONAL DDP CONNECTIONS SUPPORTED IN APPLETLK.NLM

For more information, please refer to sections in this READ_ME.1ST file
that describe these new features.

The NetWare AppleTalk Support Package Installation and Maintenance manual
documents this release of the NetWare AppleTalk Support Package software.
In addition, this file describes numerous enhancements. We recommend that
you print this file and save it as a reference to this new release of the
NetWare AppleTalk Support Package.

If you are receiving the NetWare AppleTalk Support Package software for the
first time, as part of the NetWare v3.11 UpDate program, you can acquire
the NetWare AppleTalk Support Package documentation mentioned above.
Information about pricing and shipping appears in the ORDER.FRM file, which
comes with the NetWare v3.11 UpDate program; please consult this file
before placing your order. To order these manuals using a credit card, you
can use one of the following methods:

-Call 800-336-3892 toll-free (for U.S. and Canadian orders only)
between 7:00 AM and 7:00 PM Central Time, Monday through Friday.
Please have your credit card and order information ready.

-You can print the ORDER.FRM file on any printer, write the order
information (for U.S. and Canadian orders only) on the form, and fax it
toll-free to 800-826-5399, 24 hours a day, seven days a week.

- For international orders using a credit card, you can call 512-834-6989
between 7:00 AM and 7:00 PM Central Time, Monday through Friday.

Please allow two to three weeks for delivery after completing your order.


IF YOU CURRENTLY USE NETWARE FOR MACINTOSH

If you are currently running NetWare for Macintosh v3.0 or v3.01 on your
server, you can take advantage of some of the new features of NetWare
AppleTalk Support Package v3.011, namely the support for SNMP and the
enhancements to the ATCON utility. To install the new modules in NetWare
AppleTalk Support Package v3.011 on your server, copy the APPLETLK.NLM and
ATCON.NLM files included in this package to SYS:SYSTEM. (This action
overwrites the copies of APPLETLK.NLM and ATCON.NLM that accompanied your
version of NetWare for Macintosh, so you may want to back them up first.)
Then either reboot your file server, or else reload APPLETLK.NLM at the
console.

Note that the new version of APPLETLK.NLM in this package will not increase
the number of AFP logins currently permitted for your copy of NetWare for
Macintosh v3.0 or v3.01.

If you are currently using NetWare for Macintosh v3.011, the new versions
of APPLETLK.NLM and ATCON.NLM in this release of the NetWare AppleTalk
Support Package are not necessary because they are already included in
NetWare for Macintosh v3.011.


GENERAL NOTE

Periodically, Novell provides patches to correct problems in its software
products. Before you apply a Novell patch, take a moment to read the
patch's release notes and to verify that the software you plan to update is
the correct version.


SUPPORTED LOCALTALK CARDS AND DRIVER

The DL/2 or DL2000 LocalTalk cards from Dayna Communications, Inc. are the
only LocalTalk cards that support the NetWare AppleTalk Support Package.
Version 3.14 of the Dayna driver is required to work with NetWare v3.11.
You can obtain LocalTalk cards and the driver for NetWare v3.11 by
contacting Dayna Communications:

Dayna Communications, Inc.
50 South Main Street, Fifth Floor
Salt Lake City, Utah 84144
Phone: 801-531-0600


ENHANCEMENTS in NetWare AppleTalk Support Package v3.011


SNMP SUPPORT IN NETWARE APPLETALK SUPPORT PACKAGE

With the release of Version 3.011, the NetWare AppleTalk Support Package
now includes support for SNMP (Simple Network Management Protocol)
operations. The SNMP protocol provides network management capabilities to
the network. With full implementations of SNMP, such as those in other
NetWare products, you can monitor network performance, isolate problems,
and control specific parameters used on the network. However, the support
for SNMP provided in APPLETLK.NLM does not enable you to control the
network using SNMP utilities. These limitations are detailed in "SNMP
Operations in the AppleTalk Network," a short section presented at the end
of this file.

In NetWare AppleTalk Support Package v3.011, APPLETLK.NLM now works
together with SNMP.NLM, the SNMP Agent running under NetWare v3.11. (Note:
SNMP.NLM is provided with NetWare v3.11; it is not provided with the
NetWare AppleTalk Support Package.) As a result of this instrumentation,
APPLETLK.NLM presents data regarding AppleTalk configuration and operations
in the network in accordance with the Internet document RFC-1243, which
describes the AppleTalk MIB I (Management Information Base).

SNMP.NLM is the SNMP Agent. The Agent receives SNMP requests and
distributes them to the appropriate managed NLM; the Agent also sends SNMP
replies on behalf of the managed NLM. When the Agent receives an SNMP
request for AppleTalk information, it passes the request to the AppleTalk
stack (APPLETLK.NLM). APPLETLK.NLM generates a response and then gives it
to the Agent, which in turn sends the reply to the original requestor. For
further information on the SNMP Agent (SNMP.NLM), please refer to pp 6-1
through 6-4 of the NetWare TCP/IP Transport Supervisor's Guide (Novell Part
# 100-000945-001), which is provided with NetWare v3.11.

You must have an SNMP management console application in order to retrieve
AppleTalk configuration and operational data. An SNMP management console
queries an SNMP-managed network device for information about the device.
Most SNMP consoles use the TCP/IP protocol to communicate with SNMP Agents
(that is, send SNMP requests and receive replies). APPLETLK.NLM allows an
SNMP console to communicate with the SNMP Agent using the Datagram Delivery
Protocol (DDP) as the basic transport. The NetWare AppleTalk Support
Package can also support SNMP over IP, but this requires that TCPIP.NLM
also be loaded on the NetWare server. Currently, SNMP.NLM does not support
the IPX protocol; therefore, the AppleTalk Management Information Base
cannot be accessed via IPX transport.

Enabling SNMP Support in the AppleTalk Network

To start AppleTalk SNMP operation, you must load three NLMs on the server:
APPLETLK.NLM, SNMP.NLM, and ATLKSNMP.NLM. The third NLM, ATLKSNMP.NLM,
activates support for SNMP instrumentation and transport in APPLETLK.NLM.

When loading these NLMs on your NetWare v3.11 server, you must observe this
load sequence:

load appletlk net=<net_number> zone={"<zone_list>"}
load snmp
load atlksnmp

After these NLMs are loaded, you can use an SNMP management console
application to retrieve SNMP data, using DDP for transport over the
network. ATLKSNMP.NLM remains loaded regardless of SNMP activity in the
network. If you unload ATLKSNMP.NLM, you will deactivate the SNMP support
within AppleTalk, but all other SNMP activity will continue unaffected.

If you want to use IP as the transport for obtaining information via SNMP,
you must load TCPIP.NLM in addition to APPLETLK.NLM, and bind IP to a card
appropriately. (Note: TCPIP.NLM autoloads SNMP.NLM, so loading SNMP
explicitly is not necessary.  If you want to supply options to SNMP.NLM,
then you must load SNMP.NLM before loading TCPIP.NLM.) Use commands such as
these:

load tcpip
bind ip to <board_name> addr=<ip_address>
load appletlk net=<net_number> zone={"<zone_list>"}
load atlksnmp

For more information about how SNMP works with the AppleTalk network that
the NetWare AppleTalk Support Package makes possible with NetWare, see
"SNMP Operations in the AppleTalk Network" at the end of this file.


NEW FUNCTIONALITY IN ATCON

A new option has been added to the ATCON main menu: "View Logs." The View
Logs option replaces the previous "View System Log" option. The View Logs
option enables users to view error and message logs devoted to more
specific areas of network functionality.

When you select View Logs in the ATCON main menu, a submenu appears
including these options:

- Printer Logs: Select this option to view messages about a specific
printer configured on the server. A list of text files containing messages
about each printer appears in a submenu; to view the messages, select one
of the text files in the submenu corresponding to the printer in which you
are interested. Note: If ATPS.NLM from NetWare for Macintosh is not also
running on your server, then there will be no ATPS (AppleTalk Print
Services) printers configured on the server. In that case, ATCON will
display a message informing you that no printer logs were found.

- System Log: Select this option to view system-specific messages.

- Volume Log: Select this option to view messages about a specific volume
on the server. A list of text files containing messages about each volume
appears in a submenu; to view the messages, select one of the text files in
the submenu corresponding to the volume in which you are interested. Note:
If AFP.NLM from NetWare for Macintosh is not also running on your server,
then the Volume Log option will return a message that no volume log was
found.

These new options for viewing specific message logs can help administrators
more quickly identify problems. By subdividing the message logs into
separate categories, administrators can avoid surveying messages they know
to be unrelated to their interest.


ADDITIONAL DDP CONNECTIONS SUPPORTED IN APPLETLK.NLM:

In the version of APPLETLK.NLM included in this release, the DDP protocol
allows allocation of dynamic sockets in the range from 15 to 127. The
standard range of dynamic sockets is from 128 through to 254. Many
services, such as AFP, ATPS, DAL, and Macintosh connections to Novell's
Communications Server, use dynamic sockets. Because each client connection
to any of these services consumes one socket, the previous version of DDP
in APPLETLK.NLM limited previous versions of the NetWare AppleTalk Support
Package to about 125 client connections. With the new version of DDP, the
NetWare AppleTalk Support Package v3.011 can now support 238 possible
simultaneous connections.

DDP sockets from 1 to 127 are defined as the "static range" according to
Inside AppleTalk from Apple Computer, Inc. Static sockets will be allocated
only when there are no dynamic sockets available.

It is possible to write experimental NLM programs that rely on the
availability of certain static sockets. If you have written an NLM like
this, be sure to load it before loading other clients, so that the static
socket on which your experimental NLM relies will be available.

It is possible that some client products may experience anomalies as a
result of our use of static sockets. A possible result would for be the
client to refuse to connect to a NetWare service.

If you prefer to avoid use of static sockets, you can use a new LOAD option
for APPLETLK.NLM, "-s". The -s option prohibits allocation of static
sockets. Notice that this option limits the possible number of sockets to
125, the old limit. However, the -s LOAD option will prevent a combination
of services, such as a large number of DAL users connected to the server
and simultaneous multiple NetWare for SAA connections, from breaching the
limit accidentally.


PROBLEMS RESOLVED IN APPLETLK.NLM:

(1) ATZONES.CFG problem: We fixed a problem that occurred during the
reading of the ATZONES.CFG file. This problem caused leading
non-alphanumeric characters (such as spaces or punctuation) in zone names
to be ignored. For example, a zone name like ".Tone Zone" would be read as
"Tone Zone" with the initial period dropped. This applied only to leading
non-alphanumeric characters, not those non-alphanumeric characters embedded
in the zone name.


KNOWN PROBLEMS IN NETWARE V3.11:

PROBLEM #1: The server might hang if IPX.COM is run under DOS before the
server is loaded.

CAUSE: This situation occurs only when the server binds a protocol to the
same network board that IPX.COM is using. NetWare is not designed to share
a network board with DOS.

SOLUTION: Add another network board to the server for use by IPX.COM. No
server protocols should be bound to this board.


PROBLEM #2: Error messages are generated about lost hardware interrupts.

CAUSE: There are two possible causes for these error messages. If the
server is a 486 system, there is a documented problem with lost hardware
interrupts with the 486 chip. If the server is a 386 system and is using
the NE/2 or NE2000 LAN driver, there exists a timing problem between the
LAN driver and the NetWare operating system.

SOLUTION: There is no apparent operational side effect to this problem, so
you can ignore these messages. If they are generated frequently, you can
instruct the system to stop displaying the messages by using this SET
command line:

SET Display Lost Interrupt Alerts = OFF


KNOWN PROBLEMS WITH SNMP SUPPORT:

PROBLEM #1: When the -i option specifying "no internal net" is used with
the LOAD APPLETLK command, the network-visible entities "NetWare Router"
and "SNMP Agent" will not be present in the router NBP table. ("SNMP Agent"
is present in the router NBP table only when SNMP support has been
activated, which occurs when ATLKSNMP.NLM is loaded.) The functional
consequence is that SNMP Consoles attempting to find the SNMP Agent via NBP
will be unable to do so. SNMP support will still be active, and SNMP
requests directed to the router on any interface (socket 8) will be
accepted.

CAUSE: All NBP entities are registered on the internal net.

SOLUTION: The workaround is *not* to use the -i option with SNMP support.
This, of course, will require that an internal net be configured when
APPLETLK.NLM is loaded. Note also that you cannot use the -i option if you
are using AppleTalk File or Print Services.


KNOWN PROBLEMS IN ATCON:

PROBLEM #1: On very large internets, the "View RTMP Table" function of
ATCON is practically unusable. When you select this function, the "Please
Wait" message displays for several minutes, and ATCON responds sluggishly
to keyboard input.

CAUSE: ATCON builds and displays an updated RTMP list every 5 seconds. When
the RTMP list is very large (covering several hundred or more networks),
the time required for ATCON to retrieve data from the router and build the
new list can be greater than 5 seconds. While it is building the new list,
ATCON does not process keyboard input.

SOLUTION: Bring the system console to the screen: press <Ctrl>+<Esc>, type
the numeral "1" and press <Enter>. From the system console,unload ATCON.
This course of action is faster than waiting for ATCON to process an <Esc>
keystroke to quit the "View RTMP Table" function.


KNOWN PROBLEMS IN APPLETLK.NLM:

PROBLEM #1: When the AppleTalk router in NetWare AppleTalk Support Package
v3.011 is on a multi-ring Token Ring network on which Apple Internet
Routers or the Macintosh workstation uses the Apple 4/16 Token Ring board,
the router requires a special NLM to communicate with Apple Internet
Routers.

CAUSE: The Apple Internet Router sends an 802.2 Test/Poll command to a node
when it needs to discover the Token Ring route (across bridges) to that
node. It waits to receive an 802.2 Test/Final (reply) frame, which will
contain the Token Ring route information, before sending AppleTalk frames
to the node.  The AppleTalk stack/router NLM does not respond to the
Test/Poll command.

SOLUTION: Install ATTOKLLC.NLM, which listens for and responds to these
Test/Poll frames. This NLM is not installed automatically during the
NetWare AppleTalk Support Package v3.011 installation.  To install this
NLM, you must manually copy ATTOKLLC.NLM from the NW-ATALK diskette to the
directory containing the NW-ATALK product. You should then load the NLM and
bind it to the Token Ring board that handles the "TOKEN-RING" frame type,
as described below. (Note: ATTOKLLC.NLM is included in the APPLETLK.EXE
file provided with the NetWare v3.11 UpDate software.) After installing the
NLM, follow these steps:

1.) Load the frame type "TOKEN-RING" for the Token Ring LAN driver being
used for AppleTalk. (This is the default frame type used when the board is
loaded, but it is not the frame type used by APPLETLK. If you are running
IPX and APPLETLK over the same Token Ring, this frame type is already
loaded.)

2.) Load the Token Ring Source Routing NLM "ROUTE.NLM" for the Token Ring
board with the "TOKEN-RING" frame type. Note that this is not the same
logical board to which APPLETLK is bound. (Again, if you are running IPX
and APPLETLK over the same Token Ring board and you have loaded ROUTE for
that board, this step has already been completed.)

3.) Load ATTOKLLC.NLM. There are no options for this NLM.

4.) Bind ATTOKLLC to the Token Ring board handling TOKEN-RING frames. Note
that this is not the same logical board to which APPLETLK is bound.

Here is an example of commands that correctly figure the server described
in this discussion:

file server name HEXAGONE
ipx internal net 1111111
load token frame=token-ring               # default frame type
load token int=2 port=320 frame=token-ring_snap name=tsnap
load route board=1
bind ipx to token net=222222
load appletlk net=50000 zone={"Server"}
bind appletlk to tsnap net=10-10 zone={"Paris"}
load route board=2
load attokllc
bind attokllc to token


SERVER ADMINISTRATION ISSUES:

(1) When you configure or remove previous versions of the NetWare AppleTalk
Support Package by using the ATCFG or ATREM modules (which are called by
INSTALL), the server's search path must include the directory containing
these modules. These modules are installed in SYS:SYSTEM. If you move them
to another location, make sure you change or add a search path to include
that location.

(2) If you are installing the NetWare AppleTalk Support Package v3.011 in a
Token-Ring Source Routing environment, note that you must load the ROUTE
module (ROUTE.NLM) for each Token-Ring frame type in use. Once you load
ROUTE, use the "board" parameter to specify the appropriate frame type.


****************************************************************

SNMP Operations in the AppleTalk Network

SNMP support in NetWare AppleTalk Support Package v3.011 is compliant with
the AppleTalk MIB I specification (described in a document from the
Internet community, RFC-1243). A MIB (Management Information Base) is a
collection of "objects" that can be accessed through SNMP. The AppleTalk
MIB I specifications describes the following groups of objects:

- LocalTalk Link Access Protocol (LLAP): Provides information about all
LocalTalk interfaces on the server. Only the objects llapInPkts and
llapOutPkts are supported.

- AppleTalk Address Resolution Protocol (AARP): The AARP is used to map
between AppleTalk node addresses and the addresses of the underlying
datalink layer, for datalinks other than LocalTalk.  This group provides a
view of AARP's Address Mapping table.

- AppleTalk Port (ATPort): An AppleTalk port is a logical connection to a
network over which AppleTalk packets can be transmitted. This group
provides information about the configuration of each AppleTalk port.

- Datagram Delivery Protocol (DDP): Provides statistical counters on the
operation of the DDP.

- Routing Table Maintenance Protocol (RTMP): Shows the table the AppleTalk
router uses to forward datagrams on the AppleTalk internet.

- Kinetics Internet Protocol (KIP): Provides status and routing information
in an Internet Protocol (IP) tunneling environment; because this version of
APPLETLK.NLM does not provide tunneling of AppleTalk encapsulated in IP
packets, this group is not supported.

- Zone Information Protocol (EXE): Shows the mapping of networks and zone
names the AppleTalk router knows about.

- Name Binding Protocol (NBP): Provides information on the NBP table
containing services registered with NBP, and statistics on NBP operation in
the server.

- AppleTalk Echo Protocol (AEP): Transport level protocol that can verify
the status of nodes on the internet. This group provides statistics on the
operation of AEP.


APPLETLK.NLM supports the Get and GetNext SNMP operations. It does not
support the Set and SetNext SNMP operations, nor does APPLETLK.NLM support
SNMP Traps.

For more information about SNMP support in AppleTalk and NetWare, please
consult these references:

"AppleTalk Management Information Base," Waldbusser, Steven (editor)
(document # RFC-1243); this document describes the AppleTalk MIB I.

"TCP/IP Transport Supervisor's Guide," pp. 6-1 to 6-5 (Novell Part #
100-000945-001); this publication is provided with NetWare v3.11.

"The Simple Book: An Introduction to Management of TCP/IP Based Internets,"
Rose, Marshall T. (Prentice-Hall, 1991).

RFC documents can be purchased through:

SRI International
Network Information Systems Center
333 Ravenswood Ave., Room EJ291
Menlo Park, CA  94025
phone: (415) 859-3695
fax: (415) 859-6028

******************************************************************

                    Apple Warranty Disclaimer

APPLE COMPUTER, INC. ("APPLE") MAKES NO WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, REGARDING
THE APPLETALK SOFTWARE. APPLE DOES NOT WARRANT, GUARANTEE OR MAKE
ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF
THE APPLETALK SOFTWARE IN TERMS OF ITS CORRECTNESS, ACCURACY,
RELIABILITY, CURRENTNESS OR OTHERWISE. THE ENTIRE RISK AS TO THE
RESULTS AND PERFORMANCE OF THE APPLETALK SOFTWARE IS ASSUMED BY
YOU. THE EXCLUSION OF IMPLIED WARRANTIES IS NOT PERMITTED BY SOME
STATES. THE ABOVE EXCLUSION MAY NOT APPLY TO YOU.

IN NO EVENT WILL APPLE, ITS DIRECTORS, OFFICERS, EMPLOYEES OR
AGENTS BE LIABLE TO YOU FOR ANY CONSEQUENTIAL, INCIDENTAL OR
INDIRECT DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS PROFITS,
BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, AND THE LIKE)
ARISING OUT OF THE USE OR INABILITY TO USE THE APPLETALK SOFTWARE
EVEN IF APPLE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
BECAUSE SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF
LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE
LIMITATIONS MAY NOT APPLY TO YOU. Apple's liability to you for
actual damages from any cause whatsoever, and regardless of the
form of the action (whether in contract, tort (including
negligence), product liability or otherwise), will be limited to
$50.
******************************************************************

