-------------------------------------------------------------------
  Notes on Novell Subdirectory Organization, Configuration Files
                      and Custom Counters
-------------------------------------------------------------------

CONTENTS
--------

   Directory Structure

   Section 1: Configuration File Parameters

   Section 2: Load, Bind and Configuration Files

   Section 3: Sample Configuration Files

   Section 4: Custom Counters


Directory Structure
-------------------

This directory contains the following files:

   README.TXT  - This file.


There is one subdirectory for the NetWare environment:

   \SRVODI     This subdirectory contains the ATMworks 350 driver 
               for Novell NetWare 3.12, 4.02 and 4.1 server 
               systems.  In addition, it contains driver 
               configuration files and a README.TXT file to 
               explain how to install the driver.


Section 1: Configuration File Parameters
----------------------------------------

The load command line for the ATMworks 350 3.12/4.x ODI Server 
Driver may contain the following command line parameters.  These
parameters are listed in alphabetical order in this section.
Refer to sections 2 and 3 for more information on how these
parameters can be combined.

The ATM addresses referenced in the command line parameters below
contain a 13 byte prefix, a 6 byte ESI, and a 1 byte selector.  
The address can be entered as nnnnnn..., or nn nn nn..., or 
nn-nn-nn... for a total of twenty bytes in hexadecimal notation 
(nn is one hexadecimal byte).  The letters A-F can be entered in 
either upper or lower case.  For example, a valid ATM address
follows: 
             
39-99-99-00-00-00-00-08-00-2B-A5-68-80-AA-00-03-02-FF-11-00

The only required parameter is the PCICARD parameter.  All other
parameters are optional.  Default values are provided for each
parameter.  LAN Emulation is the default, it requires no parameters
for selection.  If Classical IP is preferred, the Classical IP
parameters must be provided on the command line.

COMMAND LINE PARAMETERS:
------------------------

   AN2_DISABLE - FLOWmaster flow control disable.  The ATMworks 
             350 NetWare driver, by default, operates with  
             FLOWmaster flow control when the NIC is connected 
             to a Digital Equipment Corporation GIGAswitch/ATM 
             device.  FLOWmaster is per-hop, per-VC, credit-based  
             flow control.  FLOWmaster delivers high performance 
             and insures that no cells are lost because of 
             congestion.  To disable FLOWmaster flow control, 
             use the AN2_DISABLE parameter.
             
		 Default:  FLOWmaster flow control enabled             
 
   CLIP_CLIENT - Classical IP client. This keyword specifies 
             whether the driver uses Classical IP.  If you 
             configure the NetWare server to be a Classical 
             IP client, then you must also provide the 
             CLIP_PROT_ADDR_LOCAL, CLIP_SUBNET_MASK, 
             and CLIP_SERVER_ATM_ADDR parameters.

             Note that a station can be only a Classical IP
             client or a Classical IP server.  If you include
             both CLIP_CLIENT and CLIP_SERVER parameters the 
             driver will fail to initialize.  

		 Default:  none

   CLIP_PROT_ADDR_LOCAL - Local Classical IP protocol address. 
             This parameter provides the IP address for a
             station configured for Classical IP.  For information
             on IP addressing refer to the Novell TCP/IP Transport
             Supervisor's Guide.  Enter the address in dot notation 
             format where nnn is a decimal value in the range 
             0 - 255:

             nnn.nnn.nnn.nnn
		 Default:  none

   CLIP_SERVER - Classical IP server. This keyword specifies 
             whether the driver uses Classical IP.  The station  
             becomes the Classical IP ARP server.  If you configure 
             the NetWare server to be a Classical IP server, then 
             also include the CLIP_PROT_ADDR_LOCAL and 
             CLIP_SUBNET_MASK parameters.

             Note that a station can be only a Classical IP
             client or a Classical IP server.  If you include
             both CLIP_CLIENT and CLIP_SERVER parameters the 
             driver will fail to initialize.  

             Also, there must be only one Classical IP ARP server
             in a logical IP subnet.

		 Default:  none

   CLIP_SERVER_ATM_ADDR - Classical IP ARP server's ATM address. If 
             you configure the NetWare server to be a Classical 
             IP client, then this parameter is required.  It 
             provides the ATM address of the Classical IP ARP server.

		 Default:  none

   CLIP_SUBNET_MASK - Classical IP subnet mask. If you configure
             the driver for Classical IP, this parameter is 
             required.  It indicates how to partition IP 
             addresses into subnetwork addresses and local host 
             addresses.  Refer to the NetWare 4 TCP/IP Reference  
             for more information.  Enter the mask in dot notation 
             format where nnn is a decimal number from 0 - 255: 

             nnn.nnn.nnn.nnn
		 Default:  none

   LES_ADDR - LAN Emulation Server (LES) address.  In order for 
             the NetWare server to join an Emulated LAN the address
             of the LES must be available.  This address may be
             provided using this parameter.  If this parameter is 
             not used, the LAN Emulation Configuration Server is 
             used to locate the LES.  This parameter is valid only
             in a configuration file used to start LAN Emulation.
             It will be ignored in any other configuration file. 
                
		 Default:  none
                
   LIS -     Classical IP Logical IP Subnet (LIS).  This parameter
             enables you to set up PVCs to remote stations. This 
             version of the driver can accept a maximum of two LIS 
             parameters, each containing up to eight PVCs.
             
             The format for entering this parameter follows:
                
             LIS = [PVC=(VPI=n, VCI=n, 
                         PROT_ADDR_REMOTE=nnn.nnn.nnn.nnn,
                         ATM_ADDR_REMOTE=nn-nn-nn-nn-nn-nn-nn-...),
                    PVC=(VPI=n, VCI=n,
                         PROT_ADDR_REMOTE=nnn.nnn.nnn.nnn,
                         ATM_ADDR_REMOTE=nn-nn-nn-nn-nn-nn-nn-...),
                    ...]
                
             where: PVC  - requests a permanent virtual circuit 
                           and contains additional parameters
                           required for the PVC.
             
                           VPI - Virtual Path Identifier:
                                 0
                            
                           VCI - Virtual Channel Identifier: 
                                 31 - 255
                            
                           PROT_ADDR_REMOTE - The IP protocol
                                 address of the station to which 
                                 the PVC will be established.
                                 This will be either the end 
                                 station's address, if the end
                                 station is in the same LIS as the
                                 local station, or it will be the IP    
                                 address of a router/gateway if the 
                                 end station is in a different LIS.
                            
                           ATM_ADDR_REMOTE - The remote station's 
                                 ATM address, 20 bytes in hexadecimal 
                                 notation.  This will be either the 
                                 end station's address, if the end
                                 station is in the same LIS as the
                                 local station, or it will be the ATM    
                                 address of a router/gateway if the 
                                 end station is in a different LIS.
               
             The brackets, [ ], are required to group all the 
             parameters for a single LIS.  The parentheses, (), are 
             required to group all the parameters for a PVC within 
             a LIS.  

             Refer to section 3 for additional information.

		 Default:  none

   LOOP_TIME - Loop Timing controls the source of the timing for
             the ATMworks 350 transmitter.  When enabled, Loop 
             Timing causes the transmit timing to be derived from
             the receiver inputs.  When disabled (default), the
             transmit timing is derived from an on-board crystal.

		 Default:  disabled
                
   MTU_SIZE - Message Transfer Unit (MTU) size.  Enter the maximum 
             MTU size that can be supported by this configuration.

             Values:  1514  Ethernet
                      4542  FDDI, Token-Ring
                      9232  Classical IP
                     18188  Token-Ring
  		 Default: 1514
                    
             
   NO_SIG -  Disable signaling. This parameter can be used if PVCs 
             are used exclusively and signaling is not required (no 
             SVCs are being used).  Note that PVCs can be used
             while signaling is active.

		 Default:  enabled

               
   PCICARD - PCI card index. Enter the instance number of the 
             ATMworks 350 associated with the driver being loaded.
             The first ATMworks 350 is numbered 1.  Starting 
             with the ATMworks 350 in the PCI slot closest to the 
             CPU chip and proceeding outward, the next ATMworks 
             350 would be number 2.  
             
             The ATMworks 350 uses a PCI-to-PCI bridge chip.  Not 
             all BIOSs are able to configure PCI-to-PCI bridge chips.
             Use your system's setup utility or plug-and-play 
             configuration utility to ensure that the PCI slot
             is enabled and supports a bus master device.  Or, use 
             the PCI viewer distributed on this kit (for DECpc XL 
             466d2 systems) to view the PCI configuration of your
             system.  Refer to the README.TXT file in the \pcicfg 
             directory of Disk 1 for additional information.
             
             Range:   1 - 16
             Default: none
                                
   SDH     - Synchronous Digital Hierarchy (SDH) framing.  The 
             default ATM framing is Synchronous Optical Network 
             (SONET).  To select SDH framing over the ATM link, add 
             the SDH parameter to the command line.  The framing is 
             controlled at the Physical layer of the ATMworks 350.

		 Default:  SONET


   XMTBUFS - Transmit buffers. Transmit buffers are used to
             assemble ATM packets from Ethernet formatted TCBs
             prior to transmission.  The number of transmit buffers
             allocated for the first load command will be used for
             all subsequent logical boards loaded for the instance
             of the ATMworks 350.  More transmit buffers might 
             increase performance, but will also use additional 
             memory resources.
             
             Range:   1 - 128
             Default: 8
   


Section 2: Load, Bind and Configuration Files
---------------------------------------------

ATM is complex and as a result the driver is more complex.  The 
NetWare installation procedure imposes parameter size limitations
that are exceeded by driver parameter sizes such as the ATM address.  
NetWare allows the load command line to include a configuration 
file.  The configuration file contains as many command line 
parameters as your installation requires.  Each command line 
parameter can be listed on a separate line for readability.  The
configuration file generally has the same name as the driver and 
uses a .cfg extension.  However, fixed file names have been 
selected to identify the function each configuration file provides.
The installation procedure provides configuration files for LAN 
Emulation, Classical IP client setup, Classical IP server setup, 
setting up PVCs from a Classical IP client station,  setting up
PVCs from a Classical IP arp server station,  and a generic file,
DGLPB.CFG, that you can customize for your installation.  

Examples of various load and bind command lines and the associated
configuration file are shown below.  Section 3 provides additional
information on the content of the configuration files.

This driver supports either IPX or IP over LAN emulation.  It also
supports IP over Classical IP.  Both LAN emulation and Classical IP
can be configured to run at the same time by using different frame
types.  NetWare uses the Ethernet_II frame type for IP as well as
IPX.  

If your network uses IP, you can configure the driver to use the
Ethernet_II frame type and either the ELAN.CFG file for LAN 
Emulation, or the CLIPxxxx.CFG or PVCxxxx.CFG files for Classical 
IP.  

If your network uses IPX, you can configure the driver to use any 
of the frame types (provided Ethernet_II is not being used 
simultaneously for IP).  Use the ELAN.CFG file for LAN emulation. 

Example 1: IPX over LAN Emulation with the LAN Emulation Server
           address specified:

  load dglpb name=dglpb_8022 frame=Ethernet_802.2 pcicard = 1
      xmtbufs = 16 @elan.cfg

  bind ipx dglpb_8022 net=12345678

   ELAN.CFG:

   LES_ADDR = 3999990000000008002BA56880AA000302FF1100

   Note:  The LES_ADDR is optional.  This can be omitted if your
   ATM switch can provide the LES address through the LECS.


Example 2: IP over LAN Emulation

  load dglpb name=dglpb_eii frame=Ethernet_eii pcicard = 1
      xmtbufs = 16 @elan.cfg

  bind ip dglpb_eii arp=yes mask=255.255.255.0 addr=195.1.1.2

   ELAN.CFG:
      empty file

   Note:  The LES_ADDR is optional.  This can be omitted if your
   ATM switch can provide the LES address through the LECS.

Example 3: TCP/IP over Classical IP with the NetWare server 
           acting as a Classical IP client:

  load dglpb name=dglpb_eii frame=Ethernet_II pcicard = 1
      xmtbufs = 16 @clipclnt.cfg

  bind ip dglpb_eii arp=yes address=196.1.1.2 mask=255.255.255.0

   CLIPCLNT.CFG:

   CLIP_CLIENT
   CLIP_PROT_ADDR_LOCAL = 196.1.1.2
   CLIP_SUBNET_MASK = 255.255.255.0
   CLIP_SERVER_ATM_ADDR = 3999990000000008002BA5688008002B2241D83A


Example 4: TCP/IP over Classical IP with the NetWare server 
           acting as the Classical IP ARP server:

  load dglpb name=dglpb_eii frame=Ethernet_II pcicard = 1 
       xmtbufs = 16 @clipsrvr.cfg
  
  bind ip dglpb_eii arp=yes address=196.1.1.2 mask=255.255.255.0

   CLIPSRVR.CFG:

   CLIP_SERVER
   CLIP_PROT_ADDR_LOCAL = 196.1.1.2
   CLIP_SUBNET_MASK = 255.255.255.0

Example 5: IPX and IP over LAN Emulation 

  load dglpb name=dglpb_8022 frame=Ethernet_802.2 pcicard = 1
      xmtbufs = 16 @elan.cfg

  load dglpb name=dglpb_eii frame=Ethernet_II pcicard = 1 
      xmtbufs = 16 @elan.cfg
  
  bind ipx dglpb_8022 net=12345678

  bind ip dglpb_eii arp=yes address=195.1.1.2 mask=255.255.255.0


   ELAN.CFG:
        empty file

Example 6: IPX over LAN Emulation and IP over Classical IP

  This example shows how to load IPX using LAN Emulation and
  IP using Classical IP simultaneously.  Note that additional
  frame types can be loaded for use over LAN Emulation.

  load dglpb name=dglpb_8022 frame=Ethernet_802.2 pcicard = 1
      xmtbufs = 16 @elan.cfg

  load dglpb name=dglpb_eii frame=Ethernet_II pcicard = 1 
      xmtbufs = 16 @clipclnt.cfg
  
  bind ipx dglpb_8022 net=12345678

  bind ip dglpb_eii arp=yes address=196.1.1.2 mask=255.255.255.0


   ELAN.CFG:
        empty file

   CLIPCLNT.CFG:

   CLIP_CLIENT
   CLIP_PROT_ADDR_LOCAL = 196.1.1.2
   CLIP_SUBNET_MASK = 255.255.255.0
   CLIP_SERVER_ATM_ADDR = 3999990000000008002BA5688008002B2241D83A


NOTE:  In the above examples, the ATM addresses are presented in 
the format that allows them to fit on one line.  You can format them 
as 39-99-99-00-00-00-00-... in your configuration files to aid in 
readability.  Also, the load command must be entered on one line.

Section 3: Sample Configuration Files
--------------------------------------

The .CFG files are samples only.  They provide examples of how to
enter the command line parameters.  Change all IP and ATM addresses
to those in your ATM network.

The following samples show how the command line parameters can be
grouped.  PCICARD is a required parameter and, in general, will be
listed on the command line even though it could be contained in the
configuration file.   

1. ELAN.CFG

   This configuration file contains the minimum number of 
   parameters needed to start LAN Emulation.  Replace "n" with a 
   parameter value within the range specified above.  The LES_ADDR 
   (LAN Emulation Server ATM address) is optional.  If not 
   specified, the driver uses the LAN Emulation Configuration 
   Server (LECS) to obtain the LES address.  The MTU_SIZE for this 
   version of the driver defaults to 1516 regardless of what size
   is specified.  XMTBUFS and PCICARD will be on the command line 
   as a result of the installation procedure.  It is likely that 
   this configuration file will be empty for many installations.

   LES_ADDR = nn-nn-nn-nn-nn...
   MTU_SIZE = 1516
   
2. CLIPCLNT.CFG

   To set up Classical IP s0 that your NetWare server is a 
   Classical IP client (presuming there is another system in the  
   network that is the Classical IP ARP server), use the following 
   command line parameters.  With the following configuration 
   parameters, SVCs are used.

   CLIP_CLIENT
   CLIP_PROT_ADDR_LOCAL = nnn.nnn.nnn.nnn
   CLIP_SERVER_ATM_ADDR = nn nn nn nn nn...
   CLIP_SUBNET_MASK = nnn.nnn.nnn.nnn
                
3. CLIPSRVR.CFG

   To set up Classical IP to make your NetWare server the Classical
   IP ARP server, use the following command line parameters.  With 
   the following configuration parameters, SVCs are used.

   CLIP_SERVER
   CLIP_PROT_ADDR_LOCAL = nnn.nnn.nnn.nnn
   CLIP_SUBNET_MASK = nnn.nnn.nnn.nnn

4. PVCCLNT.CFG

   You can set up 8 PVCs in each of two Classical IP Logical
   IP Subnets (LIS).  The NO_SIG parameter is optional.  
   Signaling can be active even if you are using PVCs exclusively.
   You may use a mixture of SVCs and PVCs as shown in the following
   examples.

   The PROT_ADDR_REMOTE is the IP address of the remote end station.  
   If the remote end station is in a different LIS, this address must 
   be the IP address of a router/gateway.

   The ATM_ADDR_REMOTE is the ATM address of either the remote end
   station or a router/gateway. 

   In the following examples the CLIP parameters activate Classical
   IP.  PVCs are only supported with Classical IP.  An end station 
   may be a Classical IP server or a Classical IP server.

   Example 1.  Point to Point PVC
   
   A PVC can be set up between two end stations without an
   intervening switch.

      End station A <---------------------> End station B
      196.1.1.2               PVC           196.1.1.1
      prefix: 39999900000...                prefix: 399999000...
      esi: 08002B803448                     esi: 08002B2241D8
      sel: 00                               sel: 3A

   If end station A is a NetWare server, its configuration file
   will contain the following parameters for this example.  

   CLIP_CLIENT
   CLIP_PROT_ADDR_LOCAL = 196.1.1.2
   CLIP_SERVER_ATM_ADDR = 3999990000000000000000000008002B2241D83A
   CLIP_SUBNET_MASK = 255.255.255.0
   LIS = [PVC=(VPI=0, VCI=84, PROT_ADDR_REMOTE=196.1.1.1,
         ATM_ADDR_REMOTE=3999990000000000000000000008002B2241D83A)]

   Note that the end station B will need to set up a PVC to
   end station A using whatever procedures are appropriate for
   the operating system running on that station.


   Example 2.  PVC to an End Station with a switch

   A PVC can be set up to an end station via a switch.  Station
   A sets up a PVC using the configuration file listed below.
   Station B must set up a PVC using whatever commands the
   operating system on that station requires.  The switch must
   be configured to connect the two PVCs. Also, if there are  
   multiple switches between your end station and the remote  
   station, you must configure each switch to support the PVCs.

      End station A                         End station B
      196.1.1.2                             196.1.1.1
      prefix: 39999900000...                prefix: 399999000...
      esi: 08002B803448                     esi: 08002B2241D8
      sel: 00                               sel: 3A
           |                                        |
           |                                        | 
           -----------------> switch <---------------
              pvc    3999990000000008002BA56880    pvc
                           esi: AA000302FF
                           sel: 11


   CLIP_CLIENT
   CLIP_PROT_ADDR_LOCAL = 196.1.1.2
   CLIP_SERVER_ATM_ADDR = 3999990000000008002BA5688008002B2241D83A
   CLIP_SUBNET_MASK = 255.255.255.0
   LIS = [PVC=(VPI=0, VCI=84, PROT_ADDR_REMOTE=196.1.1.1,
         ATM_ADDR_REMOTE=3999990000000008002BA5688008002B2241D83A)]


   Example 3.  PVC to an End Station in a different LIS

   When the end station you wish to communicate with is in a
   different LIS, a PVC must be set up to a router/gateway which
   will ultimately communicate with the remote end station.   The 
   DS400 must set up a PVC to the switch. It must also be configured
   as the ARP server.

   The switch must be set up to connect the two PVCs. Also, 
   if there are multiple switches between your end station and 
   the remote station, you must configure each switch to support 
   the PVCs.



     -----------------------------|------------------------------|
     | End station A              |           End station B      |
     | 196.1.1.2                  |           198.1.1.1          |
     | esi: 08002B803448          |           ethernet addr:     |
     | sel: 00                    |              08002B684937    |
     |      |                     |               |              |
     |      | pvc                 |               |              |
     |      |                     |               |              |
     |    switch                  |               |              |
     |      |      pvc            |               |              |
     |      -----------------> DS400 <-------------              |
     |              196.1.1.254   |     198.1.1.254              |
     |              atm: 3999990000000008002BA56880              |
     |                     esi: 08002B794327                     |
     |                     sel: 00                               |
     |                            |                              |
     ---------LIS 1---------------|-------------LIS 2-------------

   CLIP_CLIENT
   CLIP_PROT_ADDR_LOCAL = 196.1.1.2
   CLIP_SERVER_ATM_ADDR = 3999990000000008002BA5688008002B79432700
   CLIP_SUBNET_MASK = 255.255.255.0
   LIS = [PVC=(VPI=0, VCI=84, PROT_ADDR_REMOTE=196.1.1.254,
         ATM_ADDR_REMOTE=3999990000000008002BA5688008002B79432700)]


Section 4: Custom Counters
---------------------------

The NetWare MONITOR utility displays counters for the ATMworks 350
NetWare 3.12/4.x ODI Server Driver.  In addition to the generic 
Ethernet counters, there are ATMworks 350 specific counters, 
displayed under the heading of Custom Statistics.  Their meanings  
are described below.

   Total packets sent 
      This count includes the number of packets sent by the protocols
      as well as the number of packets generated and sent internally
      by the driver.

   Total packets received
      The driver receives packets that are used by signaling, ILMI,
      etc. that are not passed up a protocol stack.  This counter
      includes all of these packets as well as packets passed up to
      protocol stacks.

   Packets received with inconsistent length
      This counter indicates a cache coherency problem. It should 
      remain zero.  If an inconsistency is noted, the incoming 
      packet is dropped.

   Packets received with DMA error
      The ATMworks 350 has detected a DMA error.  If this error is 
      reported, the ATMworks 350 is reset.

   Partial packets received
      This counter is incremented when the end-of-packet indicator
      is not set in an incoming packet.  The generic CRC counter
      will also be incremented.  The packet is dropped.

   Packets received with length not 0mod4
      All packets sent and received must be a multiple of four
      bytes.  A packet received with this error indication is 
      dropped.

   Packets received > 65k in length
      The length of the received packet exceeds the AAL5 maximum 
      allowable length.  The packet is dropped.

   Packets received < 48 bytes in length
      The minimum packet size for ATM is 48 bytes.  A packet 
      received with less than 48 bytes is dropped.

   Packets received with CRC errors
      The ATMworks 350 has detected a CRC error on a received   
      packet.  These errors are accumulated  for all incoming 
      packets.  If a packet with a CRC error is handed to a 
      protocol stack, then the CRC error count in the generic 
      statistics should also be updated.

   Transmit packets with DMA error
      A DMA error occurred on a transmit.  The ATMworks 350 is 
      reset.

   Receive ring descriptor unavailable
      There is a mismatch between the number of receive ring 
      descriptors and the number of receive buffers.  For this
      version of the driver, this counter should always be zero
      because dynamic ring allocation is not being done.

   Large buffers (1584 bytes) allocated
      Large buffers are allocated during driver initialization
      for internal use by the driver.  This value shows how many
      have been allocated.  If additional resources are required,
      the driver will attempt to allocate them and increment
      this value.

   Large buffers used
      This counter indicates how many of the large buffers 
      are being used.  If this value reaches a predefined 
      threshold, additional large buffers are 
      allocated by the driver, as long as memory is available. 

   Medium buffers (576 bytes) allocated
      Medium-sized buffers are allocated during driver 
      initialization for internal use by the driver.  This value 
      shows how many have been allocated.  If additional resources
      are required, the driver will attempt to allocate them and 
      increment this value.
        
   Medium buffers used
      This counter indicates how many of the medium buffers 
      are being used.  If this value reaches a predefined 
      threshold, additional large buffers are 
      allocated by the driver, as long as memory is available. 

   Small buffers (144 bytes) allocated
      Small-sized buffers are allocated during driver 
      initialization for internal use by the driver.  This value 
      shows how many have been allocated.  If additional resources
      are required, the driver will attempt to allocate them and 
      increment this value.

   Small buffers used
      This counter indicates how many of the small buffers 
      are being used.  If this value reaches a predefined 
      threshold, additional large buffers are 
      allocated by the driver, as long as memory is available. 

   Tiny buffers (48 bytes) allocated
      Tiny-sized buffers are allocated during driver 
      initialization for internal use by the driver.  This value 
      shows how many have been allocated.  If additional resources
      are required, the driver will attempt to allocate them and 
      increment this value.

   Tiny buffers used
      This counter indicates how many of the tiny buffers 
      are being used.  If this value reaches a predefined 
      threshold, additional large buffers are 
      allocated by the driver, as long as memory is available. 

   Receive buffers allocated
      A fixed number of receive buffers are allocated for this
      version of the driver.  Receive buffers are used to
      populate the receive ring providing host memory for DMA
      operations from the ATMworks 350.

   Receive buffers used
      This value reflects the number of buffers that have been
      placed on the receive ring.

   Receive buffer size
      The receive buffer size is based on the MTU_SIZE provided
      on the command line. If the MTU_SIZE is not provided, then
      this size is based on whether LAN Emulation or Classical
      IP has been requested.

   Transmit buffers allocated
      This value reflects the number of transmit buffers
      requested when the driver was loaded.  Transmit buffers
      are used strictly for packets being transmitted by
      protocol stacks.  The number allocated can impact
      performance but will also impact the available memory
      on the server.

   Transmit buffers used
      This counter indicates the number of transmit buffers in
      use.  When a packet is transmitted by a protocol stack, one
      of these buffers is allocated and the ATM packet assembled.
      When the transmit DMA completes, the buffer is returned to
      the driver's transmit buffer pool.  The value seen in this
      counter is not accurate because interrupts are disabled when
      the buffer is allocated and the DMA of the transmit buffer
      started.  It is quite possible that the DMA will complete
      and the report processed while interrupts remain disabled.
      As a result, the MONITOR utility cannot run and update its
      counters.  By the time MONITOR runs, the transmit buffer has
      been freed.

   Transmit buffer size
      The transmit buffer size is based on the MTU_SIZE provided
      on the command line. If the MTU_SIZE is not provided, then
      this size is based on whether LAN Emulation or Classical
      IP has been requested.

   Timers allocated
      A timer is an internal structure used by the driver to
      generate periodic callbacks to a particular function.
      These structures are allocated from server memory during 
      driver initialization.  Additional timers are allocated if 
      the preallocated timer pool runs low.

   Timers used
      This counter indicates the actual number of timers that
      have been allocated by driver functions.

   External buffers allocated
      This counter shows the number of buffers that have been 
      allocated directly from the NetWare operating system.  This
      count does not include the memory used for timers, tiny,
      small, medium, and big buffers.

   Link status change, up <--> down
      The driver periodically examines Physical layer registers
      to determine the state of the link.  This counter provides
      an indication of the physical link state.  A large number
      of state transitions might mean that there is a hardware
      problem, a fiber problem, or a switch problem.  An even
      value indicates the link is down, an odd value indicates
      the link is up.  (The ATMworks 350 LEDs also provide the link
      state:  The # indicator shows the link state and the "C" 
      indicator shows the module state.  The LEDs are lit in the 
      enabled state and extinguished in the disabled state.)

   LAN Emulation Availability
      When this value is 1, the station has joined an emulated
      LAN.  This should occur when LAN emulation is requested 
      (by the lack of the CLIP_CLIENT or CLIP_SERVER parameters 
      in a configuration file used to load the ATMworks 350 driver). 
      If the emulated LAN or switch goes down, this "counter" will
      be reset.  If you are using LAN emulation, the value must
      be 1 to connect to a remote station.

   Classical IP Availability
      When the local station is the Classical IP server and this 
      value is 1, the Classical IP module has registered its ATM
      address.  The ARP server is now available to Classical IP
      Clients.  This statistic has no meaning for a Classical IP
      client since it is up to the Classical IP ARP server to
      detect the presence of the client.

   FLOWmaster flow control
      By default, the driver enables FLOWmaster flow control.  The
      value of this statistic will be 1.  FLOWmaster can be enabled,
      but it is actually only used if the NIC is connected to
      a Digital Equipment Corporation GIGAswitch/ATM device.  This
      indicator shows whether the AN2_DISABLE command line parameter
      was used to disable FLOWmaster (0).

   
   SUNI Counters
   -------------

   SUNI is an acronym used by PMC-Sierra, Inc., the makers of
   the physical layer chip used on the ATMworks 350.  It stands
   for Saturn User Network Interface.  SUNI counters indicate
   the state of the physical layer of the ATMworks 350.  These
   counters are generally zero.  The values of these counters
   will increase dramatically if the ATM switch is rebooted or 
   if there is a problem with the cabling, the ATMworks 350, or 
   the switch.

   SUNI error registers are read once per second and these
   counters are updated.


   SUNI RSOP BIP-8 errors
      The Receive Section Overhead Processor (RSOP) provides frame
      synchronization, descrambling, and section level alarm and
      performance monitoring.  An incoming signal is monitored
      by calculating the section Bit Interleaved Parity (BIP)-8 error 
      detection code on the scrambled data of the complete frame and 
      comparing the results with the BIP-8 code extracted from the 
      following frame.  Differences in the codes indicate that a 
      section level bit error has occurred.  Up to 64000 bit errors 
      can be detected per second.

   SUNI RLOP BIP-8/24 errors
      The Receive Line Overhead Processor (RLOP) provides line 
      level alarm and performance monitoring.  The error monitor
      calculates the received line BIP-8/24 error detection code
      based on the line overhead and synchronous payload envelope 
      of the data stream.  The calculated BIP code is compared to
      the BIP-8/24 code extracted from the following frame. 
      Any differences indicate that a line layer bit error has
      occurred.  Up to 768000 bit errors can be detected per
      second.

   SUNI RLOP FEBE errors
      Far End Block Errors (FEBE) are used to monitor an outgoing
      signal.  This count is obtained by comparing the 
      calculated BIP-24 and the BIP-24 in the incoming signal
      at the far end.  The result is inserted into a section error
      reporting byte and sent back.  The error is logged at the 
      near end section termination point. 

   SUNI RPOP BIP-8 errors
      Receive Path Overhead Processor (RPOP) provides pointer 
      interpretation, extraction of path overhead, extraction 
      of the synchronous payload envelope, and path level alarm
      and performance monitoring.  The error monitor detects
      path BIP-8 errors by comparing the path BIP-8 byte from
      the current frame to the path BIP-8 computed for the
      previous frame.

   SUNI RPOP FEBE errors
      Far End Block Errors are detected by the Receive Path
      Overhead Processor by extracting the FEBE from the 
      current frame.

   SUNI RACP Uncorrectable HCS errors
      The Receive ATM Cell Processor (RACP) performs ATM cell  
      Header Check Sequence (HCS) verification.  The HCS is a 
      CRC-8 calculation over the first 4 octets of the ATM cell 
      header. Cells containing multiple bit errors are not 
      corrected and the cells are dropped.
      
   SUNI RACP Correctable HCS errors
      Cells containing single bit HCS errors are corrected and
      passed to the receive FIFO or can be dropped if the
      corrected HCS header content match the pattern contained
      in the Match Header Pattern and Match Header Mask registers.



***TRADEMARKS***

ATMworks, Digital, FLOWmaster, and GIGAswitch are trademarks of 
Digital Equipment Corporation. 

NetWare and Novell are registered trademarks and NetWare 
Loadable Module, NLM, and ODI are trademarks of Novell, Inc.
