Netware Command Line Parameters and Keywords -- C100

# NetWare* Command Line Parameters and Keywords

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

To view the keywords for Advanced Network Services (ANS), such as VLANs, click here.

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. In this mode, the driver will only remain persistent when it is used with ANS (teaming/VLANs)
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.

`Last modified on 2/03/05 10:16a 12`