Networking Connectivity
Intel® PRO/100 S Server Adapter
NetWare* Server and Client Installation Notes

End of interactive support disclaimer
Intel no longer provides e-mail, chat, or phone support for this discontinued software. Product support information on the Intel Web site is provided for reference and subject to the "Terms of use".

Intel will not provide updates for this software.


Contents

Installing the driver

Configuring speed and duplex

Wake on PME

Installing multiple adapters

Command line parameters

SNMP agent extension

Novell NetWare Client32 for DOS


Installing the driver support pack requirements
  • Novell NetWare* 5.1 requires Support Pack 7, Netware 6.0 requires Support Pack 5, and Netware 6.5 requires Support Pack 2.
Installing the driver

The 100 adapter driver for Novell NetWare 5.x and 6.x is packaged in the ce100.lan file. To install the driver package and setup the driver for a network adapter, use the following steps.

Note Prior to installing, either load the DOS or NetWare drivers for your server's CD-ROM drive or create a floppy disk from the CD on a different computer. For more information, refer to the Make a Driver Disk section of this guide.
  1. From the NetWare console, type NWCONFIG for version 5.x and 6.x and press ENTER.

  2. From the Configuration Options screen, choose Driver options and press Enter.

  3. Choose Configure network drivers and press Enter. If any drivers are already loaded, a list of them appears.

  4. Select an additional driver and press Enter. A list of drivers appears.

  5. Insert the CD or floppy disk you've created and choose Install an unlisted driver by pressing Insert.

    Note To mount a CD, use cdrom.
  6. If you're using a floppy disk, insert the disk in drive A and press Enter. If you've mounted the CD as a NetWare volume, press F3 andenter the source path (PRO1001000:/pro100/nwserver/).

  7. The driver name is displayed: 100 Network Connection. Press Enter to select it.

  8. A prompt appears asking if you want to copy the driver. Select Yes and press Enter.

  9. The next screen asks for parameters for loading the driver. To modify any driver parameters or protocols, highlight Select/Modify driver parameters and protocols and press Enter. If you have multiple adapters, enter the slot number for the adapter you are currently configuring. When finished configuring the driver, select Save parameters and load driver to continue.

    Note If your system contains a single network adapter, you may enter any number for the slot. The driver will automatically detect the correct slot number and load successfully.
    Note If your system contains more than one network adapter, you can find the valid slot numbers for your adapters by pressing - to switch to the console screen in NetWare. Type LOAD CE100B and press . The driver will attempt to load and prompt you with the available slot numbers. Note the slot numbers, and press to abort the driver load. Use - to switch back to the Install screen and enter the correct slot number.
  10. To complete the driver installation process, go back to the Configuration Options screen by pressing Esc until you see the Configuration Options screen.

  11. Choose Exit to return to the server console prompt.

    Note If the adapter cannot transmit or receive after installation, you may need to modify the frame type or LOAD and BIND statements in the AUTOEXEC.NCF file.
    Note If you are installing multiple adapters, repeat the driver installation process for each adapter in the server.
    Note Some switches can take several seconds to auto-negotiate and establish a link with the adapter. This may result in a false "could not establish link" error message. Use the monitor or check the adapter lights to determine valid connection information.
Installing with Netware 6.x

If you are using Netware 6.x the following installation instructions apply:

  1. From the NetWare console, type HDETECT, and press Enter.

  2. From the first NetWare Installation screen (displaying Platform Support and Hot Plug modules) choose Continue, and press Enter.

  3. From the second NetWare Installation screen (displaying Network Boards) choose Modify, and press Enter. Then choose Network Boards and press Enter.

  4. At the next screen (displaying only Network Boards) choose Modify.

  5. Choose Add by pressing Insert.

  6. Insert the CD or floppy disk you have created, and choose Install an Unlisted Driver by pressing Insert.

  7. Go to step #6 in the above installation instructions and follow through step #11.


Configuring speed and duplex setting full duplex

For each adapter in AUTOEXEC.NCF, edit the LOAD command and add the following options (you must include the equal sign for servers):

FORCEDUPLEX=2
SPEED=100 (or 10 if 10BASE-T)
Setting speed

If you manually set (force) speed to 10 or 100, you must force both speed and duplex, and auto-negotiation must be disabled. (Also be sure that the link partner settings match these settings.) The Autoneg parameter is ignored.

Using autoneg

Use the Autoneg parameter when more control is required. When this parameter is used, the Speed and Forceduplex parameters must not be specified. This parameter is a bitmap, based on the following table that specifies which speed and duplex settings the adapter advertises to a link partner.

Setting N/A 100 Full 100 Half 10 Full 10 Half
Value 16 8 4 2 1

This parameter is the sum of the values of each setting to advertise. For example, to advertise 100-Full and 100-Half modes, the parameter would be set to 8 + 4 = 12.


Caution
When the Speed and Forceduplex keywords are used, auto-negotiation is disabled. To ensure that link is established correctly, auto-negotiation must be disabled on the link partner, and the link should be forced to the same speed and duplex mode used on the adapter.


Wake on PME

The Intel driver includes the Wake on PME assertion feature for NetWare 5.x and 6.x systems. This feature allows users to select a single adapter in a system and configure that adapter to wake a system from an off state.

Note Wake on PME is enabled by default. To disable Wake on PME, enter the option pmedisable=0 on the command line.

Installing multiple adapters

The server drivers use the PCI slot number to identify each installed adapter. You can correlate the PCI slot number to the port by using the Ethernet address that is printed on a label on the adapter.

If you are installing a driver in a computer with existing Intel adapters, the drivers are updated automatically.


NetWare* command line parameters and keywords

The following NetWare* keywords are applicable for the 100 adapter drivers. These parameters are used with the LOAD driver command.

Syntax: command=parameter

Example usage: Load CE100b Speed=100 ForceDuplex=2 Name=eo83

Parameter

Values

Default Value

Description

SPEED 10, 100 10

The adapter automatically senses speed. If it is unable to auto-sense (including no network cable), SPEED defaults to 10. Make sure to match the adapter to the speed/duplex of your switch (if set). If you don't have an auto-negotiating switch and are forcing the duplex mode, you must specify the speed. You must set SPEED to either 10 or 100 if you're setting FORCEDUPLEX to either half or full.

Syntax: SPEED=value

FORCEDUPLEX 0 = autonegotiate

1 = half duplex

2 = full duplex

depends on card type

Duplex Support and Default listed by Card Type:

Auto-negotiate: The adapter negotiates with its link partner.
Full duplex: The adapter sends and receives packets at the same time.
Half duplex: The adapter communicates in one direction at a time.

Note: If you use the FORCEDUPLEX command, you must also set the SPEED parameter to either 10 or 100.

Syntax: FORCEDUPLEX=value

SLOT 1-valid slot # None

This is a standard keyword parameter predefined by NetWare to specify the physical slot of the installed adapter. When multiple adapters reside in a system, the SLOT keyword is used to distinguish which physical adapter is being loaded. If multiple adapters do exist in a system and the command line does not contain the SLOT keyword, the system will build a list of adapter slots and prompt the user to select an adapter to be loaded.

Syntax: SLOT=value

FRAME Ethernet_802.2 Ethernet_802.3 Ethernet_II Ethernet_SNAP Ethernet_802.2

Configures the adapter to process the valid NetWare Ethernet frame.

Syntax: FRAME=value

TXTHRESHOLD 0-200 16 Represents the threshold for transmits from extender SRAM FIFO (output buffer). If value is 16 then the bytes are set at 128 (16x8). In this case, the LAN controller transmits after copying 128 bytes from the host memory. The maximum number that you can specify is 200 (200x8=1600 bytes) which ensures there will not be any underruns.

Syntax: TXTHRESHOLD=value

NODE n/a The adapter's assigned address (UAA Universal Address) Specifies a locally administered address (LAA) unique to each adapter. The node address is a 12-digit hexadecimal number; the second digit must be one of the following digits: 2, 6, A, or E.

02AA => LAA, 02 is set by the driver if not specified.
00A0 => Typical Intel address (default)

Syntax: NODE=xNxxxxxxxxxx (where N must = 2, 6, A, or E; x = hexadecimal number)

FLOWCONTROL 0 = off
1 = RX flow control
2 = TX flow control
3 = RX/TX flow control
2 Controls the ability of the adapter to advertise flow control capabilities. Default is to allow TX flow control.
POLL 0 -2 1 Controls whether or not the driver loads in polling mode. 0 means no polling (e.g. interrupt mode), 1 means polling is forced on, and 2 means auto-detect. In this case, the driver will query the OS to determine whether or not polling is supported and will enable polling support accordingly. If supported by the OS, polling can decrease CPU usage by the driver when under heavy network load.
PERSIST 0 - 2 0 Controls whether the driver remains persistent during a hot plug event. Setting this parameter to 0 disables persistency; the driver will always unload during Hot Plug operations. Setting this parameter to 1 forces the driver to remain persistent during hot plug events. Setting this parameter to 2 sets the driver in auto-persistency mode.
TxBuffers 8 - 65535 20 TXBuffers tells the hardware where the fragments of a transmit packet are in host memory. A transmit packet can use 1 or more descriptors. Most transmits require 3 or 4 descriptors. Each descriptor is 16 bytes.
RxBuffers 8 - 65535 30 RXBuffers tells the hardware where to DMA received packets. For each RX buffer, the driver will also allocate a receive descriptor. Each descriptor is 16 bytes and each buffer is 2048 bytes.


SNMP agent extension for NetWare*

Overview

The LANAgent module extends the SNMP agent for NetWare* to provide information on Intel adapters.

The following information describes how to enable the NetWare SNMP module to support the Intel LAN Adapters MIB.


Prerequisites

For optimal performance by the SNMP agent, install the appropriate NetWare drivers:

For 100 adapters: ce100.lan

For Gigabit PCI-X* adapters: e1000.lan

For Gigabit PCI Express* adapters: e1000e.lan

The SNMP agent package is compliant with the following driver versions:

CE100b.lan: ver 4.11 and above

E1000.lan: ver 3.03 and above

E1000E.lan: ver 3.03 and above

iANS.lan : ver 4.14 and above


Installation instructions

At the server prompt enter:

Load path\LANAgent

Configure the SNMP community name according to the Novell* documentation. For example, to enable GET and SET for any community name enter:

Load SNMP ControlCommunity=

For more information, go to Novell Technical Support.

Register to receive Traps by adding the IP address of the management station to the list in the SYS:\ETC\TRAPTARG.CFG file.


Available commands

Command

Default

Description

-h

help

n/a

View the help description.

cache_time=nn

50 (5 seconds)

Define a time period in which the data structure is considered valid. Two consecutive queries within that time will not cause update of the data. nn is an integer value set to 1/10 second.

trap_time=nn

10 (1 second)

Define the time period between two consecutive trap checks. The units are the same as for cache_time.

status

n/a

View the current values for cache_time and trap_time.


Novell NetWare Client32* for DOS tips (Client32 for DOS)
  • Avoid the following message when loading the driver:

    "Do you want to load another frame type for a previously loaded board? Y/N".

    add the slot number to the LOAD line in STARTNET.BAT. By default it is located in the \NOVELL\CLIENT32 directory.

    When you reboot, you will be prompted with the correct value. Modify the STARTNET.BAT again, and use that value. If the slot is not specified correctly, only the first frame type loads. The Speed, Forceduplex and Iomapmode parameters take their default values when they are not specified.

  • CONFIG.SYS must contain the LASTDRIVE=Z statement.

  • NET.CFG must contain FIRST NETWORK DRIVE = F indented under the NetWare DOS Requester section.

  • Verify that the PRO/100 or PRO/1000 adapter passes the diagnostics test by running the DIAGS.EXE diagnostics program found on the root of the CD. If the adapter fails diagnostics it will not function correctly running Client32.

  • Using the 32-bit .LAN driver with Client32 requires CLIENT32.NLM dated 10/09/96 or later. The driver does not load with older versions.

  • If you encounter the error message:

    "An attempt to load CE100B.LAN failed because the module references an undefined external: MSMHardwareFailure", you need to update the NetWare client files. Download ODI33x.EXE (where x=latest revision number) from Novell's electronic services and run the update utility.


Sample files

CONFIG.SYS

DEVICE=C:\DOS\HIMEM.SYS
BUFFERS=30,0
FILES=60
LASTDRIVE=Z (for NETX LASTDRIVE=F or first available drive letter)

AUTOEXEC.BAT

prompt $P$G
path=c:\dos;C:\NOVELL\CLIENT32\
SET TEMP=C:\TEMP
@CALL C:\NOVELL\CLIENT32\STARTNET

STARTNET.BAT

SET NWLANGUAGE=ENGLISH
LOAD C:\NOVELL\CLIENT32\NIOS.EXE
LOAD C:\NOVELL\CLIENT32\NBIC32.NLM
LOAD C:\NOVELL\CLIENT32\LSLC32.NLM
LOAD C:\NOVELL\CLIENT32\CMSM.NLM
LOAD C:\NOVELL\CLIENT32\ETHERTSM.NLM
LOAD C:\NOVELL\CLIENT32\CE100B.LAN SPEED=0 IOMAPMODE=0 FORCEDUPLEX=0 FRAME=ETHERNET_802.2 SLOT2
Pause REM LOAD C:\NOVELL\CLIENT32\CE100B.LAN REM SPEED=0 IOMAPMODE=0 FORCEDUPLEX=0 FRAME=ETHERNET_802.3 SLOT2
LOAD C:\NOVELL\CLIENT32\TRANNTA.NLM
LOAD C:\NOVELL\CLIENT32\IPX.NLM
LOAD C:\NOVELL\CLIENT32\SPX_SKTS.NLM
LOAD C:\NOVELL\CLIENT32\CLIENT32.NLM @

Note If you are loading multiple frame types, you must specify the slot number of the adapter on the load lines.

NET.CFG

Link Driver E100BODI
; Remove the semi-colon in front of the frame type you will use.
; This frame type must match what the NetWare server is using.
; FRAME Ethernet_802.2
; FRAME Ethernet_802.3
; FRAME Ethernet_SNAP
; FRAME Ethernet_II

NetWare DOS Requester
FIRST NETWORK DRIVE = F
NETWARE PROTOCOL BIND NDS
; If you know the name of your preferred server, remove the; semi-colon below and enter the preferred server name after; the equal sign.
; preferred server =

Protocol IPX
IPX SOCKETS 60

This applies to:

Intel® Ethernet Server Adapter I340-F4
Intel® Ethernet Server Adapter I340-T4
Intel® Ethernet Server Adapter I350-F2
Intel® Ethernet Server Adapter I350-F4
Intel® Ethernet Server Adapter I350-T2
Intel® Ethernet Server Adapter I350-T4
Intel® Gigabit EF Dual Port Server Adapter
Intel® Gigabit ET Dual Port Server Adapter
Intel® Gigabit ET Quad Port Server Adapter
Intel® Gigabit ET2 Quad Port Server Adapter
Intel® PRO/100 M Desktop Adapter
Intel® PRO/100 S Desktop Adapter
Intel® PRO/100 S Dual Port Server Adapter
Intel® PRO/100 S Server Adapter
Intel® PRO/1000 GT Desktop Adapter
Intel® PRO/1000 GT Quad Port Server Adapter
Intel® PRO/1000 MF Server Adapter
Intel® PRO/1000 MF Server Adapter (LX)
Intel® PRO/1000 MT Dual Port Server Adapter
Intel® PRO/1000 MT Server Adapter
Intel® PRO/1000 PF Dual Port Server Adapter
Intel® PRO/1000 PF Quad Port Server Adapter
Intel® PRO/1000 PF Server Adapter
Intel® PRO/1000 PT Desktop Adapter
Intel® PRO/1000 PT Dual Port Server Adapter
Intel® PRO/1000 PT Quad Port Low Profile Server Adapter
Intel® PRO/1000 PT Quad Port Server Adapter
Intel® PRO/1000 PT Server Adapter
Intel® PRO/1000 XF Server Adapter

Solution ID: CS-008445
Last Modified: 17-Nov-2014
Date Created: 18-Jan-2004
Back to Top