Intel PRO/1000 Adapters CE1000 (Server Driver)
E1000ODI
(Gigabit ODI client for DOS)
Intel PRO/100 Adapters CE100B (Server Driver)
NetWare* iANS Keywords
The following NetWare keywords apply to the CE1000 driver. These
parameters are used with the LOAD <driver>
command (in autoexec.ncf).
Syntax: <command>=<parameter>
Parameter |
Valid Range |
Default Value |
Description |
||
---|---|---|---|---|---|
Autoneg | 0 - 255 | 0 | Controls auto-negotiation on copper-based adapters. When this parameter is used, the Speed and ForceDuplex parameters must NOT be specified. See Speed and Duplex in the NetWare Drivers section for values. This setting has no effect on fiber adapters, which are defined to not negotiate speed or duplex to any value but 1000 Mbps, full duplex. | ||
CoalesceBuffers | 1 - 65535 | 96 | Coalesce Buffers are used to copy fragments of a transmit packet into before assigning them a transmit descriptor. This reduces the number of transmit descriptors required for each packet transmission. Each Coalesce buffer is 2048 bytes. | ||
FlowControl | 0 = off 1 = RX flow control 2 = TX flow control 3 = RX/TX flow control |
3 | Controls the ability of the adapter to advertise flow control capabilities. Default is to allow both TX and RX flow control. | ||
Forceduplex |
0 = auto-negotiate 1 = half duplex 2 = full duplex
|
0 |
Auto-negotiate: The adapter negotiates with the switch whether to use full- or half-duplex. If unsuccessful, the adapter defaults to half-duplex. You must have an auto-negotiating switch (an NWay* switch) to get full-duplex support using auto-negotiation. Full duplex: The adapter sends and receives packets at the same time. This improves the performance of your adapter. Half duplex: The adapter communicates in one direction at a time. It either sends or receives. This setting has no effect on fiber adapters, which are defined to be full-duplex.
|
||
Frame |
ethernet_802.2 ethernet_802.3 ethernet_snap ethernet_ii |
ethernet_802.2 |
Configures the adapter to process the valid NetWare Ethernet frame types. |
||
Jumbo |
0 - 16380 |
0 |
Enables jumbo frames and sets the maximum frame size. Setting this parameter to 0 disables jumbo frames and causes the adapter to use standard 1514 bytes frames. This feature is only available in NetWare 6.x. |
||
Name | n/a | None | Assigns a
unique name to the board's configuration. You can use this optional
parameter to identify network boards when you have more than one network
board of the same type installed in the file server. The name can be 17
characters long. Syntax: |
||
Persist | 0 = disable persistency 1 = driver to remain persistent during hot-plug events 2 = auto-persistency mode |
2 (auto-detect) | Controls whether the driver remains persistent during a hot-plug event. When persistency is disabled, the driver always unloads during hot-plug. In auto-persistency mode, the driver only remains persistent when it is used with iANS (teaming/VLANs). | ||
Pmedisable | 0 = enabled 1 = disabled |
0 | Systems that support Power Management Event
(PME) are powered up when the adapter receives a Magic Packet*. This
capability is enabled by default.
To disable this feature, enter |
||
Poll |
0 = no polling (interrupt mode) |
0 |
Controls whether or not the driver loads in polling mode. When Poll is set to auto-detect, 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. |
||
RxDescriptors | 8 - 65535 | 64 | Rx descriptors tell the hardware where to DMA received packets. For each RX descriptor the driver will also allocate a receive buffer. Each descriptor is 16 bytes and each buffer is 2048 bytes. | ||
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. |
||
Speed |
0 |
0 |
On copper-based adapters, forces the line speed to the specified value in Mbps. If this parameter is not specified, or is set to 0, the adapter will auto-negotiate to the best possible link based on the link partner. Gigabit speed can only be achieved by auto-negotiation. This setting has no effect on fiber adapters, which are defined to be 1000 Mbps. |
||
TxDescriptors | 8 - 65535 | 96 | Tx descriptors are used to tell the hardware where the fragments of a transmit packet are in host memory. A transmit packet can use one or more descriptors. Most transmits require three or four descriptors. Each descriptor is 16 bytes. | ||
WaitForLink |
0 = on |
1 |
Controls whether or not the driver will wait for link before finishing initialization. When enabled, this keyword causes the driver to wait until auto-negotiation is complete before finishing initialization and returning to the command prompt. Disabling this value may cause the driver to initialize faster, but may also cause it to display incorrect link information when it loads. |
||
XsumRX |
0 = disable offloading |
0 |
When this feature is enabled, the driver and hardware can "offload" the calculation of the TCP or UDP checksum values for received TCP or UDP packets, when the stack supports such operation. When this feature is disabled, the checksum is calculated normally by the TCP/UDP protocol layers. Non-TCP/UDP packets (such as IPX) are not affected by this parameter. Unlike other keywords, this setting is tracked on a per-frame-type basis, and only works on Ethernet_II and Ethernet_SNAP frame types. |
||
XsumTX |
0 = disable offloading |
0 |
When this feature is enabled, the driver and hardware can "offload" the calculation of the TCP or UDP checksum values for transmitted TCP or UDP packets, when the stack supports such operation. When this feature is disabled, the checksum is calculated normally by the TCP/UDP protocol layers. Non-TCP/UDP packets (such as IPX) are not affected by this parameter. Unlike other keywords, this setting is tracked on a per-frame-type basis, and only works on Ethernet_II and Ethernet_SNAP frame types. |
The following NetWare Keywords apply to the E1000ODI driver.
Parameter |
Valid Range |
Default Value |
Description |
---|---|---|---|
Slot | 0 - FFFFh | auto-configure if possible | The driver uses the value of the parameter
to determine which adapter to control.
If the value does not correctly indicate a valid slot number or the adapter is already in use, an error message is displayed and the driver treats this as a fatal error. |
SpeedDuplex | 0 - 3 | auto-detected during initialization | 0=Force speed to 10Mb and duplex to half. 1=Force speed to 10Mb and duplex to full. 2=Force speed to 100Mb and duplex to half. 3=Force speed to 100Mb and duplex to full. >3=ignored + error message displayed. Auto-detection by the controller is disabled and the speed and duplex modes are set as specified. The controller will not be able to auto-detect the mode until the driver is reloaded. If the SpeedDuplex mode does not match the actual mode of the port in use, the driver may or may not function for certain levels of traffic and then begin to lose frames. The SpeedDuplex parameter is valid for copper-based controllers and will be ignored when used on a fiber-based adapter. Gigabit copper adapters currently cannot be forced to 1000 Mbps due to limitations in the IEEE specification. |
The following NetWare Keywords apply to the CE100B driver. These
parameters are used with the LOAD <driver>
command (in autoexec.ncf).
NOTE: The Intel PRO/100+ Dual Port Server Adapter does not support TCP checksum offloading. |
Syntax: <command>=<parameter>
Parameter |
Values |
Default Value |
Description |
||
---|---|---|---|---|---|
Autoneg | 0 - 255 | 0 | Controls auto-negotiation on copper-based adapters. When this parameter is used, the Speed and ForceDuplex parameters must NOT be specified. See Speed and Duplex in the NetWare Drivers section for values. | ||
CoalesceBuffers | 1 - 65535 | 96 | Coalesce Buffers are used to copy fragments of a transmit packet into before assigning them a transmit descriptor. This reduces the number of transmit descriptors required for each packet transmission. Each Coalesce Buffer is 2048 bytes. | ||
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. | ||
Forceduplex | 0 = auto-negotiate 1 = half duplex 2 = full duplex |
0 |
Auto-negotiate: The adapter negotiates with the switch whether to use full- or half-duplex. If unsuccessful, the adapter defaults to half-duplex. You must have an auto-negotiating switch (an NWay* switch) to get full-duplex support using auto-negotiation. Full duplex: The adapter sends and receives packets at the same time. This improves the performance of your adapter. Half duplex: The adapter communicates in one direction at a time. It either sends or receives.
|
||
Frame | ethernet_802.2 ethernet_802.3 ethernet_ii ethernet_snap | Ethernet_802.2 |
Configures the adapter to process the valid NetWare Ethernet frame types. |
||
Name | n/a | None | Assigns a unique
name to the board's configuration. You can use this optional parameter to
identify network boards when you have more than one network board of the
same type installed in the file server. The name can be 17 characters long.
Syntax: |
||
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. Syntax: |
||
Persist | 0 = disable persistency 1 = driver to remain persistent during hot-plug events 2 = auto-persistency mode |
2 (auto-detect) | Controls whether the driver remains persistent during a hot-plug event. When persistency is disabled, the driver always unloads during hot-plug. In auto-persistency mode, the driver only remains persistent when it is used with iANS (teaming/VLANs). | ||
Pmedisable | 0 = enabled 1 = disabled |
0 | Systems that support Power Management Event
(PME) are powered up when the adapter receives a Magic Packet. This
capability is enabled by default.
To disable this feature, enter |
||
Poll | 0 = no polling (interrupt mode) 1 = on 2 = auto-detect |
1 | Controls whether or not the driver loads in polling mode. When Poll is set to auto-detect, 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. | ||
RxDescriptors | 8 - 65535 | 64 | Rx descriptors tell the hardware where to DMA received packets. For each RX descriptor the driver will also allocate a receive buffer. Each descriptor is 16 bytes and each buffer is 2048 bytes. | ||
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. |
||
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 do not 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 are setting FORCEDUPLEX to either half or full. |
||
Txchecksum | 0 - 1 | 0 | When set to 1 the driver and hardware can "offload" calculating the TCP or UDP checksum values for transmitted TCP or UDP packets, when the stack supports such operations. When set to 0 the checksum is calculated normally by the TCP/UDP protocol layers. Non-TCP/UDP packets (such as IPX) are not affected by this parameter. Unlike other keywords, this setting is tracked on a per-frame basis, and only works on Ethernet_II and Ethernet_SNAP frame types. | ||
TxDescriptors | 8 - 65535 | 96 | Tx descriptors are used to tell the hardware where the fragments of a transmit packet are in host memory. A transmit packet can use one or more descriptors. Most transmits require three or four descriptors. Each descriptor is 16 bytes. | ||
Txthreshold | 0-254 | 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. |
Please read all restrictions and disclaimers.