--------------------------------------------------------------------
Installing the ATMworks 350 NetWare 3.12/4.x ODI Server Driver
on NetWare 3.12, 4.02 and 4.1 Servers
--------------------------------------------------------------------
CONTENTS
--------
Directory Structure
System Requirements
Section 1: Installing the NetWare 3.12/4.x ODI Server Driver
on NetWare 4.02
Section 2: Installing the NetWare 3.12/4.x ODI Server Driver
on NetWare 4.1
Section 3: Installing the NetWare 3.12/4.x ODI Server Driver
on NetWare 3.12
Section 4: Hints for Selecting Proper Ethernet Frame Types
Section 5: Configuration File Parameters
Section 6: Load, Bind and Configuration Files
Section 7: Sample Configuration Files
Section 8: Custom Counters
Section 9: ATMworks 350 LED States
Directory Structure
-------------------
This directory contains the following files:
README.TXT - This file contains the installation instructions
for the ATMworks 350 NetWare 3.12/4.x ODI server
driver, DGLPB.LAN.
DGLPB.LAN - Digital ATMworks 350 NetWare ODI server driver
that runs on NetWare 3.12, 4.02 and 4.1 servers.
DGLPB.LDI - Driver installation information file used by the
NetWare 4.x installation utility (INSTALL.NLM) to
install and configure the Digital ATMworks 350
NetWare ODI server driver.
CLIPCLNT.CFG - A sample configuration file containing the
command line parameters used for a Classical IP
client. Update this configuration file with
the ATM address of the Classical IP ARP server
and your local IP address and subnet mask.
CLIPSRVR.CFG - A sample configuration file containing the
command line parameters used for a Classical
IP ARP server. Update this configuration file
with your local IP address and subnet mask.
DGLPB.CFG - A sample configuration file containing all of
the command line parameters supported by the
ATMworks 350 driver. Not all commands should be
used at one time. This file provides the
commands in one place for future reference and
configuration file modification.
ELAN.CFG - A sample configuration file containing
command line parameters used for LAN Emulation.
This file is empty because LAN Emulation needs
no parameters, it is the default service.
Ethertsm.nlm - Novell's Ethernet Topology Specific Module, v2.50,
for NetWare 3.12 and 4.x.
Msm.nlm - Novell's ODI Media Support Module, v2.50, for
NetWare 4.x.
Msm.31x - Novell's ODI Media Support Module, v2.50 for
NetWare 3.12.
PVCCLNT.CFG - A sample configuration file containing the
command line parameters needed to set up PVCs
for a Classical IP client.
PVCSRVR.CFG - A sample configuration file containing the
command line parameters needed to set up PVCs
for a Classical IP ARP server.
System Requirements
-------------------
Operating System: Novell NetWare 3.12, 4.02 or 4.1
Unused PCI bus master full-size slot
Rev 2.1 PCI compliant system
.5MB disk space for ATMworks 350 driver
.5MB memory for ATMworks 350 driver
Minimum system memory requirements depend on the modules
loaded in your server. Preliminary testing with the
ATMworks 350 driver in a NetWare server with three or four
Windows NT clients indicate the following minimum requirements:
16MB RAM if not running TCP/IP or NetWare/IP
24MB RAM if running TCP/IP or NetWare/IP
Optional System Software (tested versions):
-------------------------------------------
NetWare/IP: v2.1 for NetWare 4.1
TCP/IP: v2.02i or later for NetWare 3.12
v2.02l or later for NetWare 4.02
v3.00b or later for NetWare 4.10
Section 1: Installing the NetWare 4.x ODI Server Driver on 4.02
----------------------------------------------------------------
To install the ATMworks 350 NetWare 3.12/4.x ODI server driver on a
NetWare 4.02 file server, perform the following steps.
I. Verify that the ATMworks 350 network interface card (NIC) is
properly configured and installed. Refer to the "ATMworks 350
Installation and Service" guide for instructions.
II. Install the ATMworks 350 NetWare 3.12/4.x ODI server driver,
then configure and load the driver.
The ATMworks 350 driver has a number of possible
configurations and resulting installation options. This
driver supports LAN Emulation as well as Classical IP. IPX
and IP run over LAN Emulation simultaneously as long as
different frame types are used. IP runs over Classical IP.
Classical IP and LAN Emulation can run simultaneously provided
different frame types are used.
For version 4.02 of NetWare, the LAN driver installation
procedure assumes that you are installing a driver that only
uses the IPX protocol. If you are using the IPX protocol,
install the driver following the instructions in sections A
and B below. To install the driver for TCP/IP, use the
instructions in sections A and C.
A. To install the driver files, perform the following steps.
1. Load INSTALL.NLM.
2. From the "Select an Installation Method" menu, select
"Maintenance/Selective Install".
3. From the "Installation Options" menu, select "LAN Driver
Options".
4. While in the "Select a LAN Driver" screen, press the
<Insert> key to select the "Load a LAN driver not
listed" option.
5. Place the DOS-format Distribution Diskette (Disk 2) into
the server floppy drive, then press <Enter> to scan for
the NetWare 3..12/4.x ODI server driver using the default
path of A:\.
6. From the "Select a new LAN driver to install" menu,
select DGLPB.LAN, "Digital Equipment Corporation
ATMworks 350" driver. Press <Enter> and follow the
instructions to install the driver files.
7. Select YES in response to the question: "Do you want
driver A:\NOVELL\SRVODI\DGLPB.LAN copied to the server?".
This will copy the driver, the installation information
file, and sample configuration files to sys:\system. It
will also copy the Msm.nlm, Msm31x.nlm, and Ethertsm.nlm
to sys:\system. You should save your original versions
of the Novell nlm files.
B. To install the Digital ATMworks 350 NetWare driver for use
with the IPX protocol and LAN emulation, perform the
following steps.
1. From the "Driver DGLPB parameters" menu select the
parameters required for this installation. Refer to
section 5 for additional information.
2. PCI card index. Enter the PCI card index for the
Digital ATMworks 350 card to be configured. This
parameter represents the instance or index of this
Network Interface Card (NIC) if there are multiple
Digital ATMworks 350 NICs installed. If only one NIC
is installed, select the default value of 1. This
parameter is mandatory.
3. Transmit buffers. Enter the number of transmit buffers
available to the ATMworks 350 for all loaded frame types.
The range is 1 - 128 and the default is 8. Each buffer
is 1584 bytes in length to account for ATM overhead.
More buffers might increase performance, but will use
more memory.
4. Configuration file. Press the <Enter> key to obtain
a list of the configuration files available on this
kit. Sample configuration files (CLIPCLNT.CFG,
CLIPSRVR.CFG, DGLPB.CFG, ELAN.CFG, PVCCLNT.CFG,
PVCSRVR.CFG) were copied to sys:\system during step A.
The "custom" option uses the DGLPB.CFG file. You must
edit that file for your configuration prior to
loading the driver.
For LAN emulation using IPX, accept the default file,
LAN Emulation, which will place the @ELAN.CFG parameter
onto the command line.
Because the installation procedure will load the driver,
make sure that the configuration file copied in step A
has been updated with the correct parameters for your
installation. Using a client or NWSHELL after
installation, or any DOS based PC prior to installation,
the configuration file can be updated with parameters
needed for your network. A complete list of parameters
is contained in section 5.
5. Press the <Enter> key to see the "Frame Type List" menu.
Select the frame types to be used for IPX over LAN
Emulation and press the <Enter> key. If your network
uses TCP/IP and you intend to load the driver and bind
it to IP, do not select the Ethernet_II frame type for
IPX. See Section C for more information about installing
this driver with TCP/IP.
6. Press the <F10> key to exit this menu and load the
driver.
7. The "Network address to bind IPX to DGLPB (frame xxxxx)"
menu pops up. Enter the network number to be used for
this logical board. If you selected multiple frame
types for the ATMworks 350, this menu will appear once
for each frame type. Enter a unique network number for
each frame type.
8. If the driver does not load, use the Alt-Esc key
sequence to switch to the system console and view the
driver load error message. If you have TCP/IP
installed on your system, use INETCFG to view the
console log file and see the load failure messages if
the message scrolled off the console command screen.
9. If the driver loads successfully, a notice appears to
remind you to update your AUTOEXEC.NCF file. From the
"Installation Options" menu, select "NCF Files Options".
From the "Available NCF Files Options" menu, select
"Create AUTOEXEC.NCF file" or "Edit AUTOEXEC.NCF file".
Verify the new AUTOEXEC.NCF parameters, make any changes,
and save the new file. NOTE: In many cases, the LAN
Emulation configuration file @ELAN.CFG does not show up
on the command line. If all the parameters that you
require to start LAN emulation are on the command line
(typically, PCICARD and XMTBUFS are the only parameters
needed), then you can ignore this parameter. However,
if you updated the ELAN.CFG file and added LES_ADDR,
for instance, then add @ELAN to the command line.
C. To install the Digital ATMworks 350 NetWare driver for
use with TCP/IP and either LAN Emulation or Classical IP,
perform the following steps.
1. Perform the steps in section A above to copy the driver
and configuration files to sys:\system.
2. Load INETCFG.NLM if you have NetWare/IP installed on
your system.
3. Select "Boards".
4. Press the <Insert> key to add a board to your
configuration. Or, if you are adding TCP/IP support to
an existing board, skip to step 6.
5. The parameters used by INSTALL are available to INETCFG.
Enter a board name. Enter the PCICARD number for this
board. Enter the number of transmit buffers. Select
the configuration file name to be used for this load.
Press <Esc> to exit this menu.
6. Select "Bindings".
7. Press the <Insert> key to add a binding.
8. Select TCP/IP and press <Enter>. This assumes that the
TCP/IP protocol has been enabled on your server. If not,
use the protocols option to add TCP/IP support.
9. Select a board to bind to TCP/IP and press <Enter>.
10. Enter an IP address for this server.
11. Enter the subnetwork mask for the network.
12. Press <Esc> to exit this menu and respond "YES" to
update the configuration.
13. Press <Esc> to exit.
14. If you choose to not use inetcfg, edit the autoexec.ncf
file as explained above in B.9 to add load and bind
commands for TCP/IP. For example:
load dglpb name=dglpb_eii frame=ethernet_ii pcicard=1
xmtbufs=16 @elan
bind ip dglpb_eii arp=yes mask=255.255.255.0
addr=195.1.1.2
(Note: the load and bind command lines are entered on
one line on the NetWare server, not two as shown above)
D. If TCP/IP is not installed on your server or you do not
use inetcfg, and additional frame types are desired, use
the INSTALL utility and the "NCF Files Option" menu item
to edit the AUTOEXEC.NCF file and add any additional LOAD
and BIND commands. Or, select multiple frame types for
IPX in section B, step 5.
III. Verify the installation.
A NetWare 4.02 system not running TCP/IP can verify or alter
the configuration parameters for the ATMworks 350 by
selecting the INSTALL option "NCF File Options". Select
"Edit AUTOEXEC.NCF file" to verify or alter the load and bind
command lines.
A system running TCP/IP and inetcfg can verify the
configuration by running INETCFG.NLM. View the configuration
to ensure that the installation went as planned.
IV. Restart NetWare to use the ATMworks 350.
When you are satisfied with the installation and the
configuration parameters, DOWN the server, and EXIT to DOS.
Make sure that the configuration file contains the correct
values for your network. Failure to join an Emulated LAN
will occur if you select LES_ADDR and have an error in the
LES ATM address. Or, a failure to connect to another node
on an IP network will occur if your IP address or the ARP
server's ATM address is incorrect.
Restart the server with the ATMworks 350 NetWare 3.12/4.x ODI
server driver by entering the following command at the DOS
prompt:
SERVER
The changes made to the STARTUP.NCF and AUTOEXEC.NCF files or
to the NetWare/IP files in section II above take effect.
Section 2: Installing the NetWare 3.12/4.x ODI Server Driver
on NetWare 4.1
---------------------------------------------------------------
NOTE: Please refer to the release notes in the root directory of
this installation disk for information about installing required
patches before installing the ATMworks 350 NetWare 3.12/4.x ODI
Server Driver.
To install the ATMworks 350 NetWare 3.12/4.x ODI server driver on a
NetWare 4.1 file server, perform the following steps.
I. Verify that the ATMworks 350 network interface card (NIC) is
properly configured and installed. Refer to the "ATMworks 350
Installation and Service" guide for instructions.
II. Install the ATMworks 350 NetWare 3.12/4.x ODI server driver,
then configure and load the driver.
The ATMworks 350 driver has a number of possible
configurations and resulting installation options. This
driver supports LAN Emulation as well as Classical IP. IPX
and IP run over LAN Emulation simultaneously as long as
different frame types are used. IP runs over Classical IP.
Classical IP and LAN Emulation can run simultaneously provided
different frame types are used.
The NetWare 4.1 installation procedure assumes that the
IPX protocol will be used. Additional protocol types
can be selected, but this results in an incorrect installation
and, on occasion, the installation hangs trying to
determine IPX network numbers to use. For this reason, it is
recommended that this driver be installed as a LAN Emulation
driver using the IPX protocol. Additional load commands and
bindings can then be added by either editing the AUTOEXEC.NCF
file or by using INETCFG.NLM. See section C below for more
information.
A. To install the driver files, perform the following steps.
1. Load INSTALL.NLM.
2. From the "Installation Options" menu, select "Driver
options".
3. From the "Driver Option" menu, select "Configure network
drivers".
4. From the "Additional Driver Actions" menu, select
"Select a[n additional] driver".
5. While in the "Select a driver" screen, press the
<Insert> key to select the "Install an unlisted driver"
option.
6. Place the DOS-format Distribution Diskette (Disk 2) into
the server floppy drive, then press <Enter> to scan for
the NetWare 3.12/4.x ODI server driver using the default
path of A:\.
7. From the "Select a driver to install" menu, select
DGLPB.LAN, "Digital Equipment Corporation ATMworks 350"
driver. Press <Enter> and follow the instructions to
install the driver files.
8. Select YES in response to the question: "Do you want to
copy the driver DGLPB.LAN?". This will copy the driver
and sample configuration files to sys:\system. It will
also copy the Msm and Ethertsm files. It is recommended
that you save the original copies of these files.
B. To install the Digital ATMworks 350 NetWare driver for use
with the IPX protocol and LAN emulation, perform the
following steps. Refer to section 5 for descriptions of
the command line parameters.
1. From the "Board DGLPB(_x) (Driver DGLPB) Actions" menu,
select "Select/Modify driver parameters and protocols".
2. IPX is the default, do not select any other protocols.
3. Use the down arrow to move to the "DGLPB(_x) Parameters"
menu.
4. PCI card index. Enter the PCI card index for the
Digital ATMworks 350 card to be configured. This
parameter represents the instance or index of this
NIC if there are multiple Digital ATMworks 350
NICs installed. If only one ATMworks 350 is installed,
select the default value of 1. This parameter is
mandatory.
5. Transmit buffers. Enter the number of transmit buffers
available to the ATMworks 350 for all frame types. The
range is 1 - 128 and the default is 8. Each buffer is
1584 bytes in length to account for ATM overhead. More
buffers might increase performance, but will use more
memory.
6. Configuration file. Press the <Enter> key to obtain
a list of the configuration files available on this
kit. Sample configuration files (CLIPCLNT.CFG,
CLIPSRVR.CFG, DGLPB.CFG, ELAN.CFG, PVCCLNT.CFG,
PVCSRVR.CFG) were copied to sys:\system during step A.
The "custom" option uses the DGLPB.CFG file. You must
edit that file for your configuration prior to
loading the driver.
For LAN emulation using IPX, accept the default LAN
Emulation which will place the @ELAN.CFG parameter on
the command line.
Because the installation procedure will load the driver,
make sure that the configuration file copied in step A
has been updated with the correct parameters for your
installation. Using a client or NWSHELL after
installation, or any DOS based PC prior to installation,
the configuration file can be updated with parameters
needed for your network. A complete list of parameters
is contained in section 5.
7. While the installation focus in on the "DGLPB Parameters"
menu, press the <F3> key to see the "Frame Type List".
Select the frame types to be used for IPX over LAN
Emulation and press the <Enter> key. If your network
uses TCP/IP and you intend to load the driver and bind
it to IP, do not select the Ethernet_II frame type for
IPX. See section C for more information about installing
this driver with TCP/IP.
Press the <F10> key to exit this menu.
8. Press the <F10> key to save the parameters and return to
the "Board DGLPB(_x) (Driver DGLPB) Action" menu.
9. Select "Save parameters and load driver" to complete the
installation of this instance of the driver.
10. If the driver does not load, use the Alt-Esc key
sequence to switch to the System Console and view the
driver load error message. If you have NetWare/IP
installed on your system, use INETCFG to view the
console log file and see the load failure messages if
the message scrolled off the console command screen.
11. The installation procedure will scan for network numbers
and provide a selection that you can accept by pressing
the <Enter> key or change by editing the selection. Or,
you can abort the bind, in which case, you will have to
complete the bind manually.
Note: If attempting to install two protocol types,
the default IPX and TCP/IP simultaneously, this step
never completes. If this occurs, DOWN the server and
reinstall the driver with only IPX selected.
The installation procedure asks if you would like to
install another network driver. It is recommended that
you answer NO and edit AUTOEXEC.NCF or use INETCFG.NLM
to add additional instances of this driver's load and bind
commands for another protocol such as TCP/IP.
C. To install the Digital ATMworks 350 NetWare driver for
use with TCP/IP and either LAN Emulation or Classical IP,
perform the following steps.
1. Perform the steps in Section A above to copy the driver
and configuration files to sys:\system.
2. Load INETCFG.NLM if you have NetWare/IP installed on
your system.
3. Select "Boards".
4. Press the <Insert> key to add a board to your
configuration. Or, if you are adding TCP/IP support to
an existing board, skip to step 6.
5. The parameters used by INSTALL are available to INETCFG.
Enter a board name. Enter the PCICARD number for this
board. Enter the number of transmit buffers. Select
the configuration file name to be used for this load.
Press <Esc> to exit this menu.
6. Select "Bindings".
7. Press the <Insert> key to add a binding.
8. Select TCP/IP and press <Enter>.
9. Select a board to bind to TCP/IP and press <Enter>.
10. Enter an IP address for this server.
11. Enter the subnetwork mask for the network.
12. Press <Esc> to exit this menu and respond "YES" to
update the configuration.
13. Press <Esc> to exit.
D. If NetWare/IP is not installed on your server and
additional frame types are desired, use the INSTALL.NLM
and the "NCF Files Option" menu item to edit the
AUTOEXEC.NCF file and add any additional LOAD and BIND
commands. Or, select multiple frame types for IPX in
section B, step 7.
III. Verify the installation.
A NetWare 4.1 system not running NetWare/IP can verify or
alter the configuration parameters for the ATMworks 350 by
selecting the INSTALL option "NCF File Options". Select
"Edit AUTOEXEC.NCF file" to verify or alter the load and bind
command lines.
A system running NetWare/IP can verify the configuration by
running INETCFG.NLM. View the configuration to ensure that
the installation went as planned.
IV. Restart NetWare to use the ATMworks 350.
When you are satisfied with the installation and the
configuration parameters, DOWN the server, and EXIT to DOS.
Make sure that the configuration file contains the correct
values for your network. Failure to join an emulated LAN
will occur if you select LES_ADDR and have an error in the
LES ATM address. Or, a failure to connect to another node
on an IP network will occur if your IP address or the ARP
server's ATM address is incorrect.
Restart the server with the ATMworks 350 NetWare 3.12/4.x ODI
server driver by entering the following command at the DOS
prompt:
SERVER
The changes made to the STARTUP.NCF and AUTOEXEC.NCF files or
to the NetWare/IP files in section II above take effect.
Section 3: Installing the NetWare 3.12/4.x ODI Server Driver
on NetWare 3.12
---------------------------------------------------------------
To install the ATMworks 350 NetWare 3.12/4.x ODI server driver on a
NetWare 3.12 file server, perform the following steps.
I. Verify that the ATMworks 350 network interface card (NIC) is
properly configured and installed. Refer to the "ATMworks 350
Installation and Service" guide for instructions.
II. Install the ATMworks 350 NetWare 3.12/4.x ODI server driver,
then configure and load the driver.
The ATMworks 350 driver has a number of possible configurations
and resulting installation options. This driver supports LAN
Emulation as well as Classical IP. IPX and IP run over LAN
Emulation simultaneously as long as different frame types are
used. IP runs over Classical IP. Classical IP and LAN
Emulation can run simultaneously provided different frame
types are used.
III. Copy the NetWare 3.12/4.x ODI server driver files to either a
DOS partition (Step IIIA.) or a NetWare partition (Step IIIB
or IIIC.) of your NetWare server hard disk.
A. To copy the files to a DOS partition, enter the following
commands:
COPY A:\NOVELL\SRVODI\DGLPB.LAN C:\
COPY A:\NOVELL\SRVODI\DGLPB.CFG C:\
COPY A:\NOVELL\SRVODI\ELAN.CFG C:\
COPY A:\NOVELL\SRVODI\CLIPCLNT.CFG C:\
COPY A:\NOVELL\SRVODI\CLIPSRVR.CFG C:\
COPY A:\NOVELL\SRVODI\PVCCLNT.CFG C:\
COPY A:\NOVELL\SRVODI\PVCSRVR.CFG C:\
Copy version 2.50 of the Novell NLMs:
COPY A:\NOVELL\SRVODI\Msm31x.nlm C:\
COPY A:\NOVELL\SRVODI\Ethertsm.nlm C:\
You may substitute C:\ with another DOS partition and
subdirectory.
B. To copy the files to a NetWare partition, you can use the
NetWare 3.x Command Processor (NWSHELL). Contact Novell
for information on acquiring NWSHELL.NLM.
1. Load the NetWare 3.x Command Processor (NWSHELL.NLM) by
entering the following command at the server System
Console prompt:
:LOAD NWSHELL
2. Change to the SYS:SYSTEM directory by entering the
following command:
CD SYS:SYSTEM
3. Copy the driver files to the current directory by
entering the following commands:
COPY A:\NOVELL\SRVODI\DGLPB.LAN
COPY A:\NOVELL\SRVODI\DGLPB.CFG
COPY A:\NOVELL\SRVODI\ELAN.CFG
COPY A:\NOVELL\SRVODI\CLIPCLNT.CFG
COPY A:\NOVELL\SRVODI\CLIPSRVR.CFG
COPY A:\NOVELL\SRVODI\PVCCLNT.CFG
COPY A:\NOVELL\SRVODI\PVCSRVR.CFG
Copy version 2.50 of the Novell NLMs. First save the
existing versions.
MKDIR drivers
COPY ethertsm.nlm drivers\ethertsm.nlm
COPY msm.nlm drivers\msm.nlm
and/or
COPY msm31x.nlm drivers\msm31x.nlm
Update the permissions of the existing ethertsm and
msm files so they can be removed.
FLAG ethertsm.nlm +N
FLAG msm31x.nlm +N
DEL ethertsm.nlm
DEL msm31x.nlm
COPY A:\NOVELL\SRVODI\Msm31x.nlm
COPY A:\NOVELL\SRVODI\Ethertsm.nlm
4. Enter "exit" to log out of the session then press any
key to return to the System Console prompt.
C. To copy the files to a NetWare partition from a NetWare
client, map a drive (F:, for example) to the sys:\system
directory on the NetWare server. Note that this assumes
that you have an existing LAN and an Ethernet or FDDI NIC
and driver that allows you to connect to the server.
COPY A:\NOVELL\SRVODI\DGLPB.LAN F:
COPY A:\NOVELL\SRVODI\DGLPB.CFG F:
COPY A:\NOVELL\SRVODI\ELAN.CFG F:
COPY A:\NOVELL\SRVODI\CLIPCLNT.CFG F:
COPY A:\NOVELL\SRVODI\CLIPSRVR.CFG F:
COPY A:\NOVELL\SRVODI\PVCCLNT.CFG F:
COPY A:\NOVELL\SRVODI\PVCSRVR.CFG F:
Create a subdirectory on sys:\system to save the old
msm31x.nlm and/or msm.nlm, and ethertsm.nlm (called
drivers).
COPY F:msm31x.nlm F:drivers\msm31x.nlm
COPY F:ethertsm.nlm F:drivers\ethertsm.nlm
DEL F:msm31x.nlm
DEL F:ethertsm.nlm
COPY A:\NOVELL\SRVODI\Msm31x.nlm F:msm31x.nlm
COPY A:\NOVELL\SRVODI\Ethertsm.nlm F:ethertsm.nlm
IV. Perform the following steps to configure the NetWare 3.12
server to use the Digital ATMworks 350 3.12/4.x ODI server
driver.
You can automatically load the server driver by adding the
appropriate instructions to the AUTOEXEC.NCF file. You can
also issue these commands directly from the System Console.
1. From the System Console, load INSTALL:
:LOAD INSTALL
2. Select "System Options."
3. Select "Edit AUTOEXEC.NCF file."
4. Add the following lines to AUTOEXEC.NCF to automatically
load and bind the new driver every time the server is
started:
NOTE: Refer to sectons 6 and 7 for additional load,
bind, and configuration file information.
a. If you installed the driver files on NetWare 3.12 using
Step IIIA, enter the following commands (all the load
command line parameters should be entered on a single
line. They are shown here on two lines for readability.)
LOAD C:\DGLPB frame=ETHERNET_802.2 pcicard=1 xmtbufs=16
@elan.cfg
BIND IPX TO DGLPB net=xxxxxxxx
b. If you installed the driver files on NetWare 3.12 using
Step III B or C, enter the following commands:
LOAD DGLPB frame=ETHERNET_802.2 pcicard=1 xmtbufs=16
@elan.cfg
BIND IPX TO DGLPB net=xxxxxxxx
c. Make sure that msm31x.nlm is loaded prior to loading
DGLPB.LAN, or rename sys:\system\msm31x.nlm to
sys:\system\msm.nlm so that DGLPB.LAN will autoload
it.
V. Shut down the server by entering "DOWN" at the system console
and then enter "EXIT" to return to the DOS prompt.
VI. Restart the server with the ATMworks 350 NetWare 3.12/4.x ODI
server driver.
Enter the following command at the DOS prompt:
SERVER
The changes made to the STARTUP.NCF and AUTOEXEC.NCF files in
step IV above take effect.
Section 4: Hints for Selecting Proper Ethernet Frame Types
-----------------------------------------------------------
It is important to specify the correct Ethernet frame type to
interoperate with Novell NetWare clients. If using the IPX
protocol, match the driver's frame type with that of the clients.
If using TCP/IP or NetWare/IP, then select Ethernet_II as the frame
type.
To allow client connections from all supported frame types, you can
load the server driver multiple times, once for each frame type.
You must bind a protocol for each instance. See the NetWare
documentation for information about how to do this.
Section 5: 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 6 and 7 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 service, it requires no parameters
for selection. If Classical IP service 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 TCP/IP documentation
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). A Logical IP
Subnet consists of the switches and communications
lines that connect host systems (end stations).
The communications paths may be set up automatically
using Switched Virtual Circuits (SVC), or manually
with Permanent Virtual Circuits (PVC). The LIS command
line parameter and its sub-parameters enables you to
set up PVCs to end stations connected to the same
LIS as your local system.
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 7 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 6: Load, Bind and Configuration Files
---------------------------------------------
ATM is complex and as a result the driver is more complex. The
NetWare installation procedure imposes command line 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 ATMworks 350 NetWare driver uses
configuration files to contain the command line parameters that
are optional. 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,
PVC setup from a Classical IP client station, PVC setup from a
Classical IP arp server station, and a generic file, DGLPB.CFG,
that contains all of the command line parameters available. You
can customize the generic file for your installation.
Examples of various load and bind command lines and the associated
configuration file are shown below. Section 7 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 7: 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 examples 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. 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 = 39-99-99-00-00...
MTU_SIZE = 1516
2. CLIPCLNT.CFG
To set up Classical IP so 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 = 196.1.1.2
CLIP_SERVER_ATM_ADDR = 39-99-99-00-00...
CLIP_SUBNET_MASK = 255.255.255.0
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 = 196.1.1.2
CLIP_SUBNET_MASK = 255.255.255.0
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 client.
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
Novell server
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 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 end station B.
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
Novell server
196.1.1.2 196.1.1.1
prefix: 39999900000... prefix: 399999000...
esi: 08002B803448 esi: 08002B2241D8
sel: 00 sel: 3A
| |
| pvc pvc |
--------------------> switch <---------------
prefix: 3999990000000008002BA56880
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, an edge device which is configured as a router, 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 |
| Novell server | |
| 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 8: 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.
Note: This version of the driver uses 1516 byte buffers
rounded up to an integral number of ATM cells.
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.
If this count increases and reaches the value of buffers
allocated then you may need to increase the number of
transmit buffers in the XMTBUFS command line parameter.
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.
Note: This version of the driver uses 1516 byte buffers
rounded up to an integral number of ATM cells.
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. Refer to section 9 for additional
information useful in determining link 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 used only 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.
Section 9: ATMworks 350 LED States
----------------------------------
The ATMworks 350 contains two amber LEDs that indicate the state
of the NIC and its connection to the ATM network.
Indicator LED Meaning
--------- --- -------
C OFF The NIC has not been initialized
by the driver.
C ON The driver successfully initialized
the NIC.
# OFF The physical layer link is down. No
signal is detected. Or, on startup,
the driver has not yet checked the
signal state. (The physical level
signal state is checked once per
second.)
# ON The physical layer link is up.
***TRADEMARKS***
ATMworks 350 and Digital are trademarks of Digital Equipment
Corporation.
NetWare and Novell are registered trademarks and NetWare
Loadable Module and NLM are trademarks of Novell, Incorporated.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.