__________________________________________________________
AUTO BUSMASTER FAMILY ODI NETWARE LAN DRIVER, VERSION 1.34
About This File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . 2
MPCO LAN Driver Installation Procedure . . . . . . . . . . . . . . . . 3
NetWare Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Configurable MPCO LAN Driver Parameters . . . . . . . . . . . . . . . . 5
Sample MPCO.CFG Configuration File for NetWare Server . . . . . . . . . 8
MPCO LAN Driver Performance Tuning . . . . . . . . . . . . . . . . . . 9
NetWare Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
16/4 Auto Busmaster Family Adapter Custom Statistic Counters . . . . 10
Messages for the MPCO LAN Driver . . . . . . . . . . . . . . . . . . 14
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 1
ABOUT THIS FILE
This file describes the use of the Auto Busmaster Family ODI NetWare LAN
Driver (MPCO.LAN) with any of the 16/4 Auto Busmaster Family Adapters listed
below:
16/4 Auto Busmaster PCI Adapter
16/4 Auto Busmaster MC 32 Adapter
The term "16/4 Auto Busmaster Family Adapter" is used in this document to
refer to any of the adapters listed above. This file is an extension of the
16/4 AUTO BUSMASTER FAMILY ADAPTER INSTALLATION AND TESTING INSTRUCTIONS that
are shipped with the respective adapter.
This file describes the installation and configuration of the 16/4 Auto
Busmaster Family Adapter Open Datalink Interface (ODI) NetWare MPCO LAN
driver. It contains information about the following topics:
o Supported platforms
o Software installation procedures
o Configurable MPCO LAN driver parameters
o Performance tuning the MPCO LAN driver
o 16/4 Auto Busmaster Family Adapter Custom Statistic Counters
o Messages for the MPCO LAN driver
SUPPORTED PLATFORMS
The MPCO LAN driver is supported in any of the hardware environments
supported by the 16/4 Auto Busmaster Family Adapters. See the 16/4 AUTO
BUSMASTER FAMILY ADAPTER INSTALLATION AND TESTING INSTRUCTIONS for
information about supported hardware.
The following operating system environments are supported:
o Novell NetWare 3.1x
o Novell NetWare 4.0
o Novell Netware for OS/2
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 2
MPCO LAN DRIVER INSTALLATION PROCEDURE
This section describes how to install the MPCO LAN driver on the NetWare
Server platform.
See the 16/4 AUTO BUSMASTER FAMILY ADAPTER INSTALLATION AND TESTING
INSTRUCTIONS that is shipped with the adapter for instructions on how to
install the 16/4 Auto Busmaster Family Adapter.
NetWare Server
This section describes how to install the MPCO LAN driver on a NetWare
Server.
To install the MPCO LAN driver on a NetWare Server, perform the following
steps:
1. Choose a target directory path on the diskette or the fixed disk (for
example, C:\NW) for installation of the MPCO LAN driver and its
associated files. All files (in step 2, below) should be copied to this
target directory.
2. Copy the following files to the target directory:
o MSM.NLM
o TOKENTSM.NLM
o ETHERTSM.NLM
o MPCO.LAN
If you are installing on NetWare 3.11, copy the following NetWare 3.11
specific modules to the target directory:
o PATCHMAN.NLM
o LSLENH.NLM
o MSM31X.NLM
3. Add the following lines to the STARTUP.NCF file:
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 3
Set Minimum Packet Receive Buffers = 48
NOTES:
1. If an 16/4 Auto Busmaster Family Adapter is installed in a 16-bit
slot in your computer or the adapter is a 16-bit adapter, add
Set Reserved Buffers Below 16 Meg = 48
2. If more than one 16/4 Auto Busmaster Family Adapter is installed
in your computer, increase the value for the
above parameters by 48 times the number of
installed 16/4 Auto Busmaster Family Adapters.
4. Add the following lines to the AUTOEXEC.NCF file:
Add the following two lines for NetWare 3.11 only:
LOAD C:\NW\PATCHMAN.NLM
LOAD C:\NW\LSLENH.NLM
LOAD C:\NW\MPCO.LAN @MPCO.CFG
NOTES:
a. @MPCO.CFG is an optional command line parameter (see step 5, below).
b. MPCO.LAN automatically loads the MSM.NLM (MSM31X.NLM if running
Novell NetWare 3.1x) TOKENTSM.NLM and ETHERTSM.NLM modules.
See NOVELL NETWARE SYSTEM ADMINISTRATION for more information about the
AUTOEXEC.NCF and STARTUP.NCF files.
5. If you need to change any MPCO LAN driver parameter values from their
defaults, these parameters can be specified on the command line when the
MPCO LAN driver is loaded, or they can be specified by creating an
MPCO.CFG configuration file. If the optional @MPCO.CFG command line
parameter is used to specify an MPCO.CFG configuration file, then the
configuration file must be located in the same directory as the MPCO.LAN
file. You can use any text editor to create or edit the MPCO.CFG file.
See "Sample MPCO.CFG Configuration File for NetWare Server" for a sample
MPCO.CFG file.
6. For your convenience, a copy of the LSLENH.NLM, PATCHMAN, MSM.NLM,
MSM31X.NLM, TOKENTSM.NLM, ETHERTSM.NLM, and MONITOR.NLM have been shipped
on the adapter options diskette. PLEASE CONTACT NOVELL TO ENSURE YOU
HAVE THE LATEST COPY OF THESE FILES.
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 4
CONFIGURABLE MPCO LAN DRIVER PARAMETERS
The following parameters can be configured at the NetWare Server by setting
keywords on the command line or in the MPCO.CFG file. A sample MPCO.CFG file
is shown in "Sample MPCO.CFG Configuration File for NetWare Server."
SLOT=
This keyword defines the slot number of the corresponding 16/4 Auto
Busmaster Family Adapter in the computer. To avoid being prompted to
enter a slot number when the MPCO LAN driver is loaded, specify this
keyword in the AUTOEXEC.NCF file. This keyword must be within the
range of 1-802.
o 1-8
For 16/4 Auto Busmaster MC 32 Adapter
o 17-24
For 16/4 Auto Busmaster PCI Adapter config m1 off
FRAME=
This keyword defines the frame type to be used with the 16/4 Auto
Busmaster Family Adapter when loading the MPCO LAN driver.
For token-ring 16/4 Auto Busmaster Family Adapters the default value
for this keyword is TOKEN-RING. The value for this keyword must be
one of the following ascii strings:
o TOKEN-RING
o TOKEN-RING_SNAP
For ethernet 16/4 Auto Busmaster Family Adapters the default value for
this keyword is is ETHERNET_802.2 on versions of NetWare later than
3.11 and ETHERNET_802.3 for NetWare 3.11 and earlier. The value for
this keyword must be one of the following ascii strings:
o ETHERNET_802.2
o ETHERNET_802.3
o ETHERNET_II
o ETHERNET_SNAP
NODE=
This keyword is used to set a locally administered address for the
16/4 Auto Busmaster Family Adapter. A local address must contain 12
hexadecimal characters and can be specified in either MSB (Most
Significant Bit) or LSB (Least Significant Bit) format.
To specify a MSB node address the letter "M" immediately follows the
last digit of the node address. If an "M" or "L" is not specified
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 5
after the last digit of the node address, the default format for the
address is MSB for token-ring and LSB for ethernet 16/4 Auto Busmaster
Family Adapters. This keyword is specified on the command line or in
the MPCO.CFG as NODE for the NetWare Server. See "Sample MPCO.CFG
Configuration File for NetWare Server" for a sample MPCO.CFG file.
If a node address is specified in MSB format, the characters must be
within the range 400000000000-7FFFFFFFFFFF (for example,
400000000001M). This same address specified in LSB format would be
020000000080L with an "L" optionally appended to the end.
NOTES:
1. Do not assign the same local address to 2 or more stations.
Severe station communication or network failures may occur when 2
or more stations are assigned the same address.
2. If you do not assign a locally administered address, the adapter
uses the universally administered address permanently embedded on
the adapter.
RXBUFFERS=
This keyword defines the number of receive buffers used by the MPCO
LAN driver.
The value for this keyword must be: 4, 8, 16, 32, or 64; the default
is 32. (Receive buffer size is defined by the server SET command.
See NOVELL NETWARE SYSTEM ADMINISTRATION for more information.)
TXBUFFERS=
This keyword defines the number of transmit buffers used by the MPCO
LAN driver.
The value for this keyword must be: 1, 2, 4, 8, or 16; the default is
16. (Maximum transmit frame size is defined by the server SET command.
See NOVELL NETWARE SYSTEM ADMINISTRATION for more information.)
TXINTSOFF
This keyword will reduce CPU utilization in server environments when
using the standard IPX protocol. Reducing CPU utilization (shown on
the monitor screen) may improve performance if CPU utilization is very
high (above 80% utilized). This option should not be used if Novell's
packet burst protocol (PBURST.NLM) is loaded, as performance on packet
burst links may be significantly degraded. Use of this option is
recommended only for servers using the standard IPX protocol.
DATARATE
This keyword will set the Data Rate for the 16/4 Auto Busmaster PCI
Adapter only. It does not affect the adapter configuration for any
other 16/4 Auto Busmaster Family Adapter.
The value for this keyword must be: A, 16, 4 (AutoSense, 16MBPS,
4MBPS); the default is A.
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 6
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 7
SAMPLE MPCO.CFG CONFIGURATION FILE FOR NETWARE SERVER
; The following keywords are generic ODI keywords for MPCO
; when using the 16/4 Auto Busmaster Family Adapter:
;
NODE=400000002222M
FRAME=TOKEN-RING_SNAP
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 8
MPCO LAN DRIVER PERFORMANCE TUNING
This section describes how to get the best performance from the 16/4 Auto
Busmaster Family Adapter and MPCO LAN driver.
NetWare Server
The maximum frame size that can be sent or received by a token-ring 16/4 Auto
Busmaster Family Adapter configured at a 4-Mbps data rate is 4496 bytes and
at a 16-Mbps data rate is 17996 bytes. The maximum frame size that can be
sent or received by an ethernet 16/4 Auto Busmaster Family Adapter is 1518.
Since frame sizes are typically negotiated between the NetWare server and
workstations, it is best to configure receive buffer sizes at the server that
equal the maximum transmit buffer size at workstations. For this reason,
increasing your receive buffer size to a value that is too big only increases
the amount of memory that is used by NetWare and may not increase the
performance of the 16/4 Auto Busmaster Family Adapter or NetWare.
Since the MPCO.LAN driver uses NetWare receive buffers to receive frames, the
size of receive buffers used by the MPCO.LAN driver is configurable by
changing the size of the NetWare receive buffers. To obtain the best
performance from the 16/4 Auto Busmaster Family Adapter edit the STARTUP.NCF
file and modify the following NetWare parameter according to your
configuration as indicated below:
If a token-ring and/or ethernet 16/4 Auto Busmaster Family Adapter
is installed in your NetWare Server increase the following
parameter as shown
below:
Set Maximum Physical Receive Packet Size = 4202
If only an ethernet 16/4 Auto Busmaster Family Adapter is installed
in your NetWare Server increase the following parameter
as shown below:
Set Maximum Physical Receive Packet Size = 1518
If the above parameter is not found in the STARTUP.NCF, use the NetWare set
command to view system parameters and ensure that the default for this
parameter is greater than the values approriate for your configuration. If
it is less, specify the above parameter in the STARTUP.NCF. See
"Configurable MPCO LAN Driver Parameters" regarding the TXINTSOFF keyword
that may improve performance of the NetWare server.
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 9
16/4 AUTO BUSMASTER FAMILY ADAPTER CUSTOM STATISTIC COUNTERS
The custom statistic counters give the user information that is specific to
the 16/4 Auto Busmaster Family Adapter and MPCO LAN driver. There follow
descriptions of the custom statistic counters and what action, if any, you
should take based on these counters.
Token-ring Utilization Percentage:
DESCRIPTION: This counter indicates the percentage of the token-ring
bandwidth that is used. This counter is updated every 30
seconds.
CAUSE/ACTION: None.
MAC Frame Count:
DESCRIPTION: This counter indicates the number of token-ring Media Access
Control (MAC) frames sent by the MPCO driver.
CAUSE/ACTION: None. These MAC frames were built and requested to be sent
by a protocol stack. This counter is only valid for
token-ring 16/4 Auto Busmaster Family Adapters.
Receive Collisions:
DESCRIPTION: This counter indicates the number of frames that experienced
a collision while being received by an ethernet 16/4 Auto
Busmaster Family Adapter.
CAUSE/ACTION: If this counter steadily increases, it may indicate a
problem with your ethernet 16/4 Auto Busmaster Family
Adapter or your ethernet network. Run the adapter
diagnostic tests located on the Option Diskette that were
shipped with the 16/4 Auto Busmaster Family Adapter. If
there are no problems with the adapter, reload the MPCO LAN
driver. If this problem persists, contact your network
administrator.
Receive Frames Discarded:
DESCRIPTION: This counter indicates the number of frames that were
received by the 16/4 Auto Busmaster Family Adapter but were
discarded by the MPCO LAN driver because they were received
with an error.
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 10
CAUSE/ACTION: If this counter steadily increases, it may indicate a
problem with your computer or the 16/4 Auto Busmaster Family
Adapter. Run the adapter diagnostic tests located on the
Option Diskette that were shipped with the 16/4 Auto
Busmaster Family Adapter. If there are no problems with the
adapter, reload the MPCO LAN driver. If this problem
persists, contact your network administrator.
Transmit Frames Discarded:
DESCRIPTION: This counter indicates the number of frames that could not
be transmitted by the 16/4 Auto Busmaster Family Adapter and
were discarded by the MPCO LAN driver.
CAUSE/ACTION: Possible explanations for this problem are as follows:
The 16/4 Auto Busmaster Family Adapter is not responding.
Run the adapter diagnostic tests located on the Option
Diskette that was shipped with the 16/4 Auto Busmaster
Family Adapter. If there are no problems with the adapter,
reload the MPCO driver. If a problem was found, follow the
instructions supplied with the diagnostic tests to correct
the problem.
If your 16/4 Auto Busmaster Family Adapter is connected to a
token-ring network, the token-ring network may be
experiencing problems and, therefore, the 16/4 Auto
Busmaster Family Adapter could not transmit these frames.
If this problem persists, contact your network
administrator.
Adapter Hardware Errors:
DESCRIPTION: This counter indicates the number of hardware errors
reported by the 16/4 Auto Busmaster Family Adapter.
CAUSE/ACTION: The 16/4 Auto Busmaster Family Adapter and MPCO LAN driver
may recover from these errors.
If this counter continues to increase, Run the adapter
diagnostic tests located on the Option Diskette that was
shipped with the 16/4 Auto Busmaster Family Adapter. If
there are no problems with the adapter, reload the MPCO LAN
driver. If a problem was found, follow the instructions
supplied with the diagnostic tests to correct the problem.
Adapter Detected Parity Errors:
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 11
DESCRIPTION: This counter is incremented when the 16/4 Auto Busmaster
Family Adapter detects a parity error while data is being
transferred between the 16/4 Auto Busmaster Family Adapter
and the computer.
CAUSE/ACTION: If this counter continues to increase, it may indicate a
problem with your computer or the 16/4 Auto Busmaster Family
Adapter. Run the adapter diagnostic tests located on the
Option Diskette that was shipped with the 16/4 Auto
Busmaster Family Adapter. If there are no problems with the
adapter reload the MPCO LAN driver. If a problem was found,
follow the instructions supplied with the diagnostic tests
to correct the problem.
Adapter RAM Access Errors:
DESCRIPTION: This counter is incremented when the 16/4 Auto Busmaster
Family Adapter reports a RAM access violation.
CAUSE/ACTION: If this counter continues to increase, and you are
experiencing problems with the 16/4 Auto Busmaster Family
Adapter, run the adapter diagnostic tests located on the
Option Diskette that was shipped with the 16/4 Auto
Busmaster Family Adapter. If there are no problems with the
adapter, reload the MPCO LAN driver. If this problem still
exists, contact your network administrator.
System Bus Errors:
DESCRIPTION: This counter indicates the number of System Bus errors that
were detected.
CAUSE/ACTION: The 16/4 Auto Busmaster Family Adapter detected an error
with the System bus while accessing or attempting to access
the bus.
If this counter continues to increase, run the diagnostics
on the reference diskette that came with your computer to
test for problems with the Micro Channel bus.
Receive Hardware Mismatch Errors:
DESCRIPTION: This counter is incremented when the MPCO LAN driver detects
a difference between the hardware reported frame length and
the frame length field in the IPX, IP, ARP or RARP protocol
header.
CAUSE/ACTION: If this counter continues to increase, contact your network
administrator.
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 12
Receive Overrun Errors:
DESCRIPTION: This counter is incremented when the 16/4 Auto Busmaster
Family Adapter receives data from the network faster than it
can be moved into computer memory.
CAUSE/ACTION: If this counter continues to increase, run the diagnostics
on the reference diskette that came with your computer to
test for problems with the system bus. If this problem
still persists, contact your network administrator.
Transmit Underrun Errors:
DESCRIPTION: This counter is incremented when the 16/4 Auto Busmaster
Family Adapter attempts to transmit a frame to the network
but cannot move the data fast enough from computer memory to
the 16/4 Auto Busmaster Family Adapter.
CAUSE/ACTION: If this counter continues to increase, run the diagnostics
on the reference diskette that came with your computer to
test for problems with the system bus. If this problem
still persists, contact your network administrator.
Transmit Checksum Errors:
DESCRIPTION: This counter is incremented when the transmission of a frame
completes and the checksum value for the frame is incorrect.
CAUSE/ACTION: If this counter continues to increase, contact your network
administrator.
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 13
MESSAGES FOR THE MPCO LAN DRIVER
MPCO-xx-071: The matching virtual adapter could not be found.
Cause: An error occurred while trying to load another copy
of the MPCO LAN driver to support an additional
frame type (FRAME= parameter) on an
16/4 Auto Busmaster Family Adapter. The MSM could not find
a previous copy of the MPCO LAN driver required
to load the specified frame type.
Action: Obtain the most current copy of the MSM.NLM or
MSM31X.NLM (if running NetWare version 3.1x), and then
reload the MPCO LAN driver for the desired frame
types. If this error persists, contact your
network administrator. Refer to the
NOVELL NETWARE SYSTEM ADMINISTRATION manual
for information about loading and unloading LAN
drivers.
MPCO-xx-072: A resource tag is unavailable.
Cause: The NetWare operating system was unable to allocate
memory for a resource tag. The MPCO LAN driver
did not load because required internal resources
were not available. There may be too many NetWare
Loadable Modules (NLMs) running in the NetWare Server.
Action: Unload the NLMs that are loaded but are not being used,
and then load the MPCO LAN driver. If this error
persists, down, exit and then restart the server. Load
the MPCO LAN driver before loading NLMs. This may
require you to edit the AUTOEXEC.NCF file before restarting
the server. Refer to NOVELL NETWARE SYSTEM ADMINISTRATION
for information about the AUTOEXEC.NCF file.
MPCO-xx-073: Unable to allocate memory.
Cause: The NetWare operating system was unable to allocate
memory for the MPCO LAN driver. The MPCO
LAN driver did not load.
Action: Unload the NetWare Loadable Modules (NLMs) that are
loaded but are not being used, and then load the MPCO
LAN driver. If this error persists, down, exit and then
restart the server. Load the MPCO LAN driver before
loading NLMs. This may require you to edit the
AUTOEXEC.NCF file before restarting the server. Refer to
NOVELL NETWARE SYSTEM ADMINISTRATION for information
about the AUTOEXEC.NCF file.
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 14
MPCO-xx-074: The hardware interrupt cannot be set.
Cause: The NetWare operating system was unable to set the
hardware interrupt level requested by the MPCO
LAN driver. The MPCO LAN driver did not load.
Action: Try to load the MPCO LAN driver again. If the error
persists, contact your network administrator.
MPCO-xx-075: The MLID cannot be registered with the LSL.
Cause: The MPCO LAN driver could not be registered with the
Link Support Layer (LSL) module. The maximum number of
LAN drivers have already been loaded or there was not
enough memory to load the MPCO LAN driver. The MPCO
LAN driver did not load.
Action: Unload LAN drivers that are not being used and then
load the MPCO LAN driver. If this error persists,
down, exit and then restart the server. Load the MPCO
LAN driver before loading other LAN drivers. This may
require you to edit the AUTOEXEC.NCF file before restarting
the server. Refer to NOVELL NETWARE SYSTEM ADMINISTRATION
for information about the AUTOEXEC.NCF file.
MPCO-xx-076: The polling procedure cannot be added.
Cause: Too many polling processes are registered with
the NetWare operating system. The MPCO LAN
driver did not load.
Action: Unload LAN drivers or NetWare Loadable Modules that
are loaded but are not being used. Try to load the
MPCO LAN driver again. If this error persists,
contact your network administrator.
MPCO-xx-077: The event notification routine cannot be registered.
Cause: The NetWare operating system was unable to allocate
memory to register the MPCO LAN driver event
notification routine. The MPCO LAN driver did
not load.
Action: Unload LAN drivers or NetWare Loadable Modules that
are loaded but are not being used. Try to load the
MPCO LAN driver again. If this error persists,
contact your network administrator.
MPCO-xx-078: The firmware file cannot be read.
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 15
Cause: The Netware operating system was unable to load the
MPCO LAN driver. The MPCO LAN driver was not
loaded.
Action: Obtain another copy of the MPCO LAN driver from
the original distribution diskette. Reload the MPCO
LAN driver. If this error persists, contact your network
administrator.
MPCO-xx-084: Unable to allocate memory below 16 Megabyte boundary.
Cause: The Netware operating system ran out of memory buffers
below 16 megabytes. The MPCO LAN driver was not
loaded.
Action: Set the Reserved Buffers Below 16 Meg parameter in the
STARTUP.NCF to a larger number.
MPCO-xx-086: The driver parameter block is too small.
Cause: The MPCO.LAN file is designed to run with an older
version of the MSM.NLM. The MPCO LAN driver was
not loaded.
Action: Obtain an older version of the MSM.NLM or a newer
version of the MPCO.LAN file.
MPCO-xx-087: The media parameter block is too small.
Cause: The TOKENTSM.NLM NetWare Loadable Module (NLM) is
designed to run with an older version of the MSM.NLM
or MSM31X.NLM if running NetWare Version 3.1x.
Action: Obtain an older version of the MSM.NLM (MSM31X.NLM
if running NetWare Version 3.1x) or a new version of
the TOKENTSM.NLM.
MPCO-xx-091: The hardware configuration conflicts.
Cause: The MPCO LAN driver requested use of a hardware
resource that was already being used by another
hardware device. The MPCO LAN driver did not load.
Action: Change the hardware configuration of the
16/4 Auto Busmaster Family Adapter or the hardware
configuration of the conflicting hardware device.
MPCO-xx-092: Cannot schedule AES without an HSM routine.
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 16
Cause: The MPCO.LAN file is damaged.
Action: Obtain another copy of the MPCO LAN driver from
the original distribution diskette. Reload the MPCO
LAN driver. If this error persists, contact your network
administrator.
MPCO-xx-093: Cannot schedule interrupt time call back without an
HSM routine.
Cause: The MPCO.LAN file is damaged.
Action: Obtain another copy of the MPCO LAN driver from
the original distribution diskette. Reload the MPCO
LAN driver. If this error persists, contact your network
administrator.
MPCO-xx-094: Cannot set hardware interrupt without an HSM routine.
Cause: The MPCO.LAN file is damaged.
Action: Obtain another copy of the MPCO LAN driver from
the original distribution diskette. Reload the MPCO
LAN driver. If this error persists, contact you network
network administrator.
MPCO-xx-095: Cannot add polling without an HSM routine.
Cause: The MPCO.LAN file is damaged.
Action: Obtain another copy of the MPCO LAN driver from
the original distribution diskette. Reload the MPCO
LAN driver. If this error persists, contact your network
administrator.
MPCO-xx-126: The group bit in the node address override was cleared.
Cause: The address specified for the node address parameter
is an incorrect adapter node address. The group
address bit for the node address specified had been
set. The group address bit was cleared by the MPCO
LAN driver. The MPCO LAN driver was loaded.
Action: Correct the node address parameter to specify a
locally administered address according to the
IBM TOKEN-RING NETWORK ARCHITECTURE REFERENCE.
On a DOS or OS/2 workstation, change the node address
parameter in the NET.CFG file. On a NetWare Server,
change the node address parameter specified on the
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 17
command line when the MPCO LAN driver was loaded,
or change the node address specified in the
MPCO.CFG configuration file.
MPCO-xx-127: The local bit in the node address override was set.
Cause: The address specified for the node address parameter
is an incorrect adapter node address. The node address
specified does not have the locally administered address
bit set. The locally administered address bit was set
by the MPCO LAN driver. The MPCO LAN driver was
loaded.
Action: Correct the node address parameter to specify a
locally administered address according to the
IBM TOKEN-RING NETWORK ARCHITECTURE REFERENCE.
On a DOS or OS/2 workstation, change the node address
parameter in the NET.CFG file. On a NetWare server
change the node address parameter specified on the
command line when the MPCO LAN driver was loaded,
or change the node address specified in the
MPCO.CFG configuration file.
MPCO-xx-200: Initializing the 16/4 Auto Busmaster Family Adapter ... please
wait.
CAUSE: The 16/4 Auto Busmaster Family Adapter initialization process
has started.
ACTION: None.
MPCO-xx-201: Connecting the 16/4 Auto Busmaster Family Adapter to the
network.
CAUSE: The 16/4 Auto Busmaster Family Adapter is connecting to an
ethernet or token-ring network.
ACTION: None.
MPCO-xx-202: The 16/4 Auto Busmaster Family Adapter is closed.
CAUSE: The MPCO LAN driver could not connect the 16/4 Auto Busmaster
Family Adapter to the network due to previously reported
hardware problems. The MPCO LAN driver has closed the
adapter and has generated an alert after unsuccesfully trying
to connect the adapter to the network after several times.
ACTION: Follow the recommended action for correcting any error
messages displayed by the MPCO LAN driver before this one.
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 18
MPCO-xx-204: The 16/4 Auto Busmaster Family Adapter requires a computer with
a
Micro Channel or Industry Standard Architecture (ISA) bus.
CAUSE: The 16/4 Auto Busmaster Family Adapter will work only in a
computer that supports the IBM Micro Channel Architecture or
the Industry Standard Architecture.
ACTION: Install the 16/4 Auto Busmaster Family Adapter in a computer
that supports the IBM Micro Channel Architecture or the
Industry Standard Architecture.
MPCO-xx-205: The MPCO LAN driver was not loaded
because of an incorrect keyword value.
CAUSE: The value for one of the keywords specified on the command
line or in the MPCO.CFG file was not within the allowable
range. The MPCO LAN driver did not load.
ACTION: Correct the value of the keyword displayed in the message
that was displayed above this error message, and reload the
MPCO LAN driver.
MPCO-xx-207: The 16/4 Auto Busmaster Family Adapter could not be reset.
CAUSE: The MPCO LAN driver timed out while waiting for the 16/4 Auto
Busmaster Family Adapter to complete a hardware reset. The
MPCO LAN driver did not load.
ACTION: Restart your computer and try to load the MPCO LAN driver
again. If this error persists, contact your network
administrator.
MPCO-xx-209: The MPCO LAN driver failed to initialize the 16/4 Auto Busmaster
Family Adapter.
CAUSE: There was a problem while initializing the 16/4 Auto
Busmaster Family Adapter. There may be previous error
messages above this one or the 16/4 Auto Busmaster Family
Adapter may not be responding.
ACTION:
Correct any problems with error
messages displayed above this error
message, and then reload the MPCO LAN
driver.
If this is the only error message that is displayed, restart
your computer and check the adapter by running the 16/4 Auto
Busmaster Family Adapter diagnostic tests packaged with the
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 19
adapterx. Then, reload the MPCO LAN driver. If this error
persists, contact your network administrator.
MPCO-xx-210: Could not find an 16/4 Auto Busmaster Family Adapter in this
computer.
CAUSE: There is no 16/4 Auto Busmaster Family Adapter installed in
this computer or the PCI configuration for the system has
disabled the 16/4 Auto Busmaster PCI Adapter . The MPCO LAN
driver did not load.
ACTION: Install an 16/4 Auto Busmaster Family Adapter in this
computer if it has a 80386 or higher microprocessor or
reconfigure the PCI configuration , and then reload the MPCO
LAN driver.
MPCO-xx-211: The 16/4 Auto Busmaster Family Adapter was not found in the
specified slot(MC) or specified DMA Channel(ISA).
CAUSE: There is no 16/4 Auto Busmaster Family Adapter in the
slot(MC) or DMA(ISA) specified by the SLOT(MC) or DMA(ISA)
keyword.
ACTION: Correct the SLOT(MC) or DMA(ISA) keyword so that it indicates
a slot(MC) number or DMA(ISA) value in which an 16/4 Auto
Busmaster Family Adapter is located, and then reload the MPCO
LAN driver.
If there is an 16/4 Auto Busmaster Family Adapter in the
specified slot(MC) or DMA(ISA), contact your network
administrator.
MPCO-xx-212: Insufficient memory available for configured transmit and
receive buffers.
CAUSE: During initialization of the MPCO LAN driver, there was
insufficient memory available for the configured number of
transmit and receive buffers.
ACTION: Increase the number of buffers that the server operating
system can allocate by editing the STARTUP.NCF file on the
server. Increase the Minimum Packet Receive Buffers server
parameter in the STARTUP.NCF file by the total number of
transmit and receive buffers that the MPCO LAN driver is
using. Down, exit, and then restart the NetWare Server.
If the 16/4 Auto Busmaster Family Adapter is installed in a
16-bit slot in your computer add or increase the following
parameter in the STARTUP.NCF file:
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 20
Set the Reserved Buffers Below 16 Meg = total transmit and
receive buffers used by the MPCO LAN driver.
If this error still persists, unload the LAN drivers and
NetWare Loadable Modules (NLMs) that are loaded but are not
being used at the NetWare Server.
If this error still persists, decrease the number of buffers
that are being used by the MPCO LAN driver by specifying the
transmit and receive keywords for the MPCO LAN driver. See
"Configurable MPCO LAN Driver Parameters" for information
about specifying keywords for the operating system that you
are using.
MPCO-xx-213: The slot(MC) or DMA(ISA) to use for the 16/4 Auto Busmaster
Family Adapter
was not specified.
CAUSE: The MPCO LAN driver prompted the user to select a slot(MC)
number or DMA(ISA) value that has an 16/4 Auto Busmaster
Family Adapter installed but no choice was made.
ACTION: None. The MPCO LAN driver was not loaded.
MPCO-xx-215: The value specified for RXBUFFERS is not valid.
The value for RXBUFFERS has been changed to xx.
VARIABLE DATA: Valid RXBUFFERS values (xx) are 4, 8, 16, 32 or 64.
CAUSE: An incorrect value was specified for RXBUFFERS either on the
command line or in the MPCO.CFG file for the server. The
MPCO LAN driver changed the value for RXBUFFERS to the value
given in this error message.
ACTION: None. However, to keep this message from being displayed
when the MPCO LAN driver is loaded, change the value
specified by the RXBUFFERS keyword to one of the supported
values displayed above. See "Configurable MPCO LAN Driver
Parameters" for the supported values.
MPCO-xx-216: The value specified for TXBUFFERS is not valid.
The value for TXBUFFERS has been changed to xx.
VARIABLE DATA: Valid TXBUFFERS values (xx) are 1, 2, 4, 8, 16.
CAUSE: An incorrect value was specified for TXBUFFERS either on the
command line or in the MPCO.CFG file for the server. The
MPCO LAN driver changed the value for TXBUFFERS to the value
given in this error message.
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 21
ACTION: None. However, to keep this message from being displayed
when the MPCO LAN driver is loaded, change the value
specified by the TXBUFFERS keyword to one of the supported
values for your operating system. See "Configurable MPCO LAN
Driver Parameters" for the supported values.
MPCO-xx-219: The 16/4 Auto Busmaster Family Adapter reported an internal
error
when it was opened.
CAUSE: The open adapter command issued by the MPCO LAN driver to
connect to the netork failed. An alert was generated by the
MPCO LAN driver.
ACTION: Restart the computer and try to load the MPCO LAN driver
again. If this message continues to occur, check the adapter
by running the adapter diagnostic tests located on the Option
Diskette that was shipped with the 16/4 Auto Busmaster Family
Adapter. If there is a problem with the adapter hardware,
contact your network administrator. If there are no problems
with the adapter hardware, report this problem to your
support center.
MPCO-xx-221: The 16/4 Auto Busmaster Family Adapter received a disconnect
frame
from another adapter on the network.
CAUSE: The 16/4 Auto Busmaster Family Adapter received a disconnect
frame request that was sent by another adapter at a remote
station. The 16/4 Auto Busmaster Family Adapter installed in
this computer disconnected from the network.
ACTION: To connect the 16/4 Auto Busmaster Family Adapter back to the
network, unload the MPCO LAN driver and then reload it. If
this error persists, contact your network administrator.
MPCO-xx-223: The 16/4 Auto Busmaster Family Adapter failed to connect to the
network; another adapter is using the same node address.
CAUSE: The 16/4 Auto Busmaster Family Adapter could not connect to
the network because another station is using the same value
that was specified for the node address parameter at your
station.
ACTION: Change the node address parameter value specified for your
station. This parameter is specified as NODE= at the NetWare
Server. See "Configurable MPCO LAN Driver Parameters" for
more information about configuration parameters.
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 22
MPCO-xx-224: The 16/4 Auto Busmaster Family Adapter detected a wire fault
error
and closed the adapter.
CAUSE: The connection between the 16/4 Auto Busmaster Family Adapter
and the LAN has been broken. The adapter or the adapter
cable may have developed a problem.
ACTION: Check the connection between the adapter and cable by running
the adapter diagnostic tests located on the Option Diskette
that was shipped with the 16/4 Auto Busmaster Family Adapter.
MPCO-xx-225: The token-ring network is beaconing.
CAUSE: The token-ring LAN segment to which the 16/4 Auto Busmaster
Family Adapter is connected is beaconing. The ring is
experiencing an error condition detected by the adapter when
there is either a signal loss (possibly caused by a broken
line) or no token circulating the ring within the predefined
time limit.
ACTION: Contact your network administrator.
MPCO-xx-228: A Micro Channel error occurred; the adapter was reset.
CAUSE: An error was detected with the Micro Channel bus while data
was being transferred between the 16/4 Auto Busmaster Family
Adapter and the computer. This condition is reported as an
alert.
ACTION: The adapter will retry the data transfer, and the MPCO LAN
driver Micro Channel Error statistics counter will be
incremented.
If this error persists, check the adapter by running the
adapter diagnostic tests located on the Option Diskette that
was shipped with the 16/4 Auto Busmaster Family Adapter, and
check your computer by running the hardware diagnostic tests.
If this error still persists, contact your support center or
place of purchase of the 16/4 Auto Busmaster Family Adapter.
MPCO-xx-229: The 16/4 Auto Busmaster Family Adapter reported a hardware
error.
CAUSE: The 16/4 Auto Busmaster Family Adapter reported an adapter
hardware error. The adapter was closed.
ACTION: The MPCO LAN driver will increment the Adapter Hardware Error
counter, issue an alert, and try to reset the adapter. The
MPCO LAN driver may recover from this error. If not, run the
16/4 Auto Busmaster Family Adapter diagnostic tests packaged
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 23
with the adapter. If there are no problems with the adapter,
reload the MPCO LAN driver. If a problem was found, follow
the instructions supplied with the diagnostic tests to
correct the problem.
MPCO-xx-231: The alert condition was corrected.
CAUSE: The 16/4 Auto Busmaster Family Adapter, MPCO LAN driver, or
network has recovered from a previously reported alert
condition.
ACTION: None.
MPCO-xx-232: The 16/4 Auto Busmaster Family Adapter detected a parity error.
CAUSE: The 16/4 Auto Busmaster Family Adapter detected a parity
error while data was being transferred between the 16/4 Auto
Busmaster Family Adapter and the computer.
ACTION: The MPCO LAN driver will increment the Adapter Detected
Parity Error counter, and this condition is reported as an
alert. The 16/4 Auto Busmaster Family Adapter and MPCO LAN
driver may recover from this error. If not, run the 16/4
Auto Busmaster Family Adapter diagnostic tests packaged with
the adapter. If there are no problems with the adapter,
reload the MPCO LAN driver. If a problem was found, follow
the instructions supplied with the diagnostic tests to
correct the problem.
MPCO-xx-233: The 16/4 Auto Busmaster Family Adapter reported a RAM access
violation.
CAUSE: The 16/4 Auto Busmaster Family Adapter reported a RAM access
violation. The MPCO LAN driver may have tried to access RAM
on the 16/4 Auto Busmaster Family Adapter that was not
accessible.
ACTION: The MPCO LAN driver will increment the Adapter RAM Access
Error counter, and this condition is reported as an alert.
The 16/4 Auto Busmaster Family Adapter and MPCO LAN driver
may recover from this error. If not, run the 16/4 Auto
Busmaster Family Adapter diagnostic tests packaged with the
adapter. If there are no problems with the adapter, reload
the MPCO LAN driver. If a problem was found, follow the
instructions supplied with the diagnostic tests to correct
the problem.
MPCO-xx-234: The 16/4 ISA Busmaster Adapter did not complete POS setup.
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 24
CAUSE: The MPCO LAN driver timed out while waiting for the 16/4 ISA
Busmaster Adapter to complete POS initialization. The MPCO
LAN driver did not load.
ACTION: Restart your computer and try to load the MPCO LAN driver
again. If this error persists, contact your network
administrator.
MPCO-xx-235: The 16/4 ISA Busmaster Adapter needs 64K of I/O ports to run in
I/O mode. This system contains only 1K of I/O ports. Set the 16/4 ISA
Busmaster Adapter to memory-mapped mode.
CAUSE: The 16/4 ISA Busmaster Adapter needs more than 1K of I/O
ports because all of the selectable I/O ports are above the
1K boundary.
ACTION: Either, set switch 7 of the 16/4 ISA Busmaster Adapter's
switch block to respond to memory mapped addresses or install
this adapter in a system with 64K of I/O ports.
MPCO-xx-236: Two 16/4 ISA Busmaster Adapters were found with identical DMA
channel switch settings.
CAUSE: Two 16/4 ISA Busmaster Adapters with duplicate DMA channel
values were found in the computer.
ACTION: Verify the settings of switches 9 and 10 for each
16/4 ISA Busmaster Adapter in the computer.
Each 16/4 ISA Busmaster Adapter must have a
unique DMA channel value.
MPCO-xx-237: Check the connection of the adapter cable to the
16/4 Auto Busmaster Family Adapter.
CAUSE: The 16/4 Auto Busmaster Family Adapter detected an error when
connecting to the network This error can occur if there is
no adapter cable connected to the 16/4 Auto Busmaster Family
Adapter or there is an error in the network cabling.
ACTION: Check the connection of the adapter cable to the adapter and
ethernet network. If the 16/4 Auto Busmaster Family Adapter
is connected to the network by a coaxial cable, check with
your network administrator to make sure the network cabling
is properly terminated.
MPCO-xx-238: Check the connection of the UTP adapter cable to the
16/4 Auto Busmaster Family Adapter.
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 25
CAUSE: The 16/4 Auto Busmaster Family Adapter is configured to use
the unsheilded twisted pair (UTP) connector on the adapter.
A UTP cable is not connected to the adapter UTP connector or
the UTP cable is not connected to the network.
ACTION: If there is no UTP cable connected to the 16/4 Auto Busmaster
Family Adapter UTP connector, connect one and then reload the
MPCO LAN driver. If there is already a UTP cable connected
to the 16/4 Auto Busmaster Family Adapter, check with your
network administrator to make sure that the UTP cable is
properly connected to the network.
MPCO-xx-239: Check the connection of the STP adapter cable to the
16/4 Auto Busmaster Family Adapter.
CAUSE: The 16/4 Auto Busmaster Family Adapter is configured to use
the sheilded twisted pair (STP) connector on the adapter. A
STP cable is not connected to the adapter STP connector or
the STP cable is not connected to the network.
ACTION: If there is no STP cable connected to the 16/4 Auto Busmaster
Family Adapter STP connector, connect one and then reload the
MPCO LAN driver. If there is already a STP cable connected
to the 16/4 Auto Busmaster Family Adapter, check with your
network administrator to make sure that the STP cable is
properly connected to the network.
MPCO-xx-240: Check the connection of the AUI adapter cable to the
16/4 Auto Busmaster Family Adapter.
CAUSE: The 16/4 Auto Busmaster Family Adapter is erx., check with
your network administrator to make sure that the STP cable is
properly connected to the network.
MPCO-xx-241:
Check the connection of the coax adapter cable to the 16/4
Auto Busmaster Family Adapter.
CAUSE: The 16/4 Auto Busmaster Family Adapter is configured to use
the coax connector on the adapter. A coax adapter cable is
not connected to the adapter coax connector or the coax cable
is not connected to the network.
ACTION: If there is no coax cable connected to the 16/4 Auto
Busmaster Family Adapter coax connector, connect one and then
reload the MPCO LAN driver. If there is already a coax cable
connected to the 16/4 Auto Busmaster Family Adapter, check
with your network administrator to make sure that the coax
cable is properly connected to the network.
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 26
MPCO-xx-242: 16/4 Auto Busmaster Family Adapter is configured for Token-ring
but is
connected to an ethernet network.
CAUSE: The adapter is incorrectly connected.
ACTION: Connect the adapter to a Token-Ring Network.
MPCO-xx-243: The IBM Streamer Family Adapter is configured for
Ethernet but is connected to a token-ring network.
CAUSE: The adapter is incorrectly connected.
ACTION: Connect the adapter to an Ethernet Network.
MPCO-xx-244: The configured ring speed for the IBM Streamer Family
Adapter is incorrect. Change the ring speed to xx Mbps.
CAUSE: The adapter is configured to the wrong ring speed.
ACTION: Configure the adapter to the correct (xx) speed.
MPCO-xx-245: The IBM Streamer Family Adapter ring speed was temporarily
changed to xx Mbps to match the token-ring network.
CAUSE: The adapter is connected to an intelligent hub and was opened
at the wrong speed. The driver automatically changed the ring
speed to match.
ACTION: Configure the adapter for xx Ring Speed.
MPCO-xx-248: The IBM Streamer Family Adapter detected a parity error.
CAUSE: The 16/4 Auto Busmaster Family Adapter detected a parity
error while data was being received from the network by the
16/4 Auto Busmaster Family Adapter.
ACTION: The MPCO LAN driver will increment the Adapter Detected
Parity Error counter, and this condition is reported as an
alert. The 16/4 Auto Busmaster Family Adapter and MPCO LAN
driver may recover from this error. If not, run the 16/4
Auto Busmaster Family Adapter diagnostic tests packaged with
the adapter. If there are no problems with the adapter,
reload the MPCO LAN driver. If a problem was found, follow
the instructions supplied with the diagnostic tests to
correct the problem.
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 27
MPCO-xx-249: The value specified for DATARATE is not valid.
The Data Rate will default to AutoSense.
CAUSE: An incorrect value was specified for DATARATE either on the
command line or in the MPCO.CFG file for the server. The MPCO
LAN driver changed the value for DATARATE to the value given
in this error message.
ACTION: None. However, to keep this message from being displayed
when the MPCO LAN driver is loaded, change the value
specified by the DATARATE keyword to one of the supported
values for your operating system. See "Configurable MPCO LAN
Driver Parameters" for the supported values.
MPCO-xx-250: Invalid configuration detected, Interrupt 0 not allowed.
CAUSE: The MPCO LAN driver detected an invalid interrupt level. The
interrupt level is assigned by the system.
ACTION: Reconfigure the system PCI Slot which contains the 16/4 Auto
Busmaster PCI Adapter to a valid interrupt level (1-15).
MPCO-xx-251: Unable to read PCI PCR register.
CAUSE: The MPCO LAN driver cannot access the 16/4 Auto Busmaster PCI
Adapter
ACTION: Check the adapter by running the 16/4 Auto Busmaster Family
Adapter diagnostic tests packaged with the adapter. If there
is a problem with the adapter hardware, contact your network
administrator. If there are no problems with the adapter
hardware, report this problem to your support center.
MPCO-xx-252: Unable to write PCI PCR register.
CAUSE: The MPCO LAN driver cannot access the 16/4 Auto Busmaster PCI
Adapter
ACTION: Check the adapter by running the 16/4 Auto Busmaster Family
Adapter diagnostic tests packaged with the adapter. If there
is a problem with the adapter hardware, contact your network
administrator. If there are no problems with the adapter
hardware, report this problem to your support center.
MPCO-xx-253: Unable to read PCI IO Address register.
CAUSE: The MPCO LAN driver cannot access the 16/4 Auto Busmaster PCI
Adapter
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 28
ACTION: Check the adapter by running the 16/4 Auto Busmaster Family
Adapter diagnostic tests packaged with the adapter. If there
is a problem with the adapter hardware, contact your network
administrator. If there are no problems with the adapter
hardware, report this problem to your support center.
MPCO-xx-254: Unable to setup PCI routines for this instance.
CAUSE: The MPCO LAN driver cannot access the 16/4 Auto Busmaster PCI
Adapter
ACTION: Check the adapter by running the 16/4 Auto Busmaster Family
Adapter diagnostic tests packaged with the adapter. If there
is a problem with the adapter hardware, contact your network
administrator. If there are no problems with the adapter
hardware, report this problem to your support center.
MPCO-xx-255: Unable to read PCI GPR register.
CAUSE: The MPCO LAN driver cannot access the 16/4 Auto Busmaster PCI
Adapter
ACTION: Check the adapter by running the 16/4 Auto Busmaster Family
Adapter diagnostic tests packaged with the adapter. If there
is a problem with the adapter hardware, contact your network
administrator. If there are no problems with the adapter
hardware, report this problem to your support center.
MPCO-xx-256: Unable to read PCI GPR register.
CAUSE: The MPCO LAN driver cannot access the 16/4 Auto Busmaster PCI
Adapter
ACTION: Check the adapter by running the 16/4 Auto Busmaster Family
Adapter diagnostic tests packaged with the adapter. If there
is a problem with the adapter hardware, contact your network
administrator. If there are no problems with the adapter
hardware, report this problem to your support center.
MPCO-xx-257: Unable to read PCI ILR register.
CAUSE: The MPCO LAN driver cannot access the 16/4 Auto Busmaster PCI
Adapter
ACTION: Check the adapter by running the 16/4 Auto Busmaster Family
Adapter diagnostic tests packaged with the adapter. If there
is a problem with the adapter hardware, contact your network
administrator. If there are no problems with the adapter
hardware, report this problem to your support center.
Auto Busmaster Family ODI NetWare LAN Driver, Version 1.34 29