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.
The Gigabit adapter driver for Novell NetWare is packaged in the file E1000E.lan for PCI-Express adapters. 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. |
From the NetWare console, type NWCONFIG for (NW5.x, NW6.x) and press <Enter>.
From the Configuration Options screen choose Driver options, and press <Enter>.
Choose Configure network drivers, and press <Enter>. If any drivers are already loaded, a list of them appears.
Select an additional driver, and press <Enter>. A list of drivers should appear.
Insert the CD or floppy disk you have created, and choose Install an unlisted driver by pressing <Insert>.
|
NOTE: To mount a CD, use cdrom. |
If you're using a floppy disk, insert the disk in drive A: and press <Enter>. If you have mounted the CD as a NetWare volume press <F3>, and enter the source path (PRO1001000:/pro1000/nwserver/).
The driver name is displayed: Intel® PRO/1000e. Press <Enter> to select it.
A prompt appears asking if you want to copy the driver. Select Yes and press <Enter>.
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.
|
|
NOTES: 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. |
| If your system contains more than one network adapter, you can find the valid slot numbers for your adapters by pressing <Alt>-<Esc> to switch to the console screen in NetWare. Type LOAD E1000E (for PCI-Express adapters) and press <Enter>. The driver will attempt to load and prompt you with the available slot numbers. To abort the driver load, note the slot numbers, and press <Esc>. Use <Alt>-<Esc> to switch back to the Install screen and enter the correct slot number. |
To complete the driver installation process, go back to the Configuration Options screen by pressing <Esc> until you see the Configuration Options screen.
Choose Exit to return to the server console prompt.
|
NOTES: 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. |
| If you are installing multiple adapters, repeat the driver installation process for each adapter in the server. | |
| 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. |
If you are using NetWare 6.x the following installation instructions apply:
From the NetWare console, type HDETECT, and press <Enter>.
From the first NetWare Installation screen (displaying Platform Support and Hot Plug modules) choose Continue, and press <Enter>.
From the second NetWare Installation screen (displaying Network Boards) choose Modify, and press <Enter>. Then choose Network Boards and press <Enter>.
At the next screen (displaying only Network Boards) choose Modify.
Choose Add by pressing <Insert>.
Insert the CD or floppy disk you have created, and choose Install an Unlisted Driver by pressing <Insert>.
Go to step #6 in the above Installing the Driver and follow through step #11.
The default setting for auto-negotiation is enabled. Change this only to match your link partner.
|
NOTES: If you disable auto-negotiation the adapter will not operate at gigabit speed (1000 Mbps). |
| You cannot change the speed or duplex of Gigabit adapters that use fiber cabling. |
Use keyword commands in AUTOEXEC.NCF to force speed and duplex modes as follows:
Speed = 10 | 100 (10 Mbps, 100 Mbps)
This should be followed by one of the following:
Forceduplex = 1 | 2 (half, full)
Autoneg = see table below for settings and values
These keywords are not available in INETCFG. To use these or any of the advanced keywords, either configure the drivers manually, or change them in AUTOEXEC.NCF.
The default setting is auto-negotiation. In this mode, the adapter advertises all supported speed and duplex combinations and will link at the highest common speed/duplex combination.
If you manually set (force) speed to 10 or 100, you must force both speed and duplex, and auto-negotiation must be disabled. Also, ensure that the link partner settings match these settings. When the Speed and Forceduplex parameters are forced, the Autoneg parameter is ignored.
Use the Autoneg parameter when more control is required. This parameter is a bitmap, based on the following table, that specifies which speed and duplex settings the adapter advertises to a link partner. When this parameter is used, the Speed and Forceduplex parameters must not be specified.
|
Setting |
1000 Full |
N/A |
100 Full |
100 Half |
10 Full |
10 Half |
|
Value |
32 |
16 |
8 |
4 |
2 |
1 |
This parameter is the sum of the values of each setting to advertise. For example, to advertise 1000-Full, 100-Full, and 100-Half modes, the parameter would be set to 32 + 8 + 4 = 44.
 |
CAUTION: When the Speed and Forceduplex keywords are used, Autoneg 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. |
To set up for Jumbo Frames, use the following commands:
SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE = <jumbo frame size>
For PCI-Express adapters: LOAD E1000E FRAME=ETHERNET_II JUMBO = <jumbo frame size>
At the switch, make sure you set the Jumbo Frame size to be at least 22 bytes larger than that of the server.
Jumbo Frames are only supported on NetWare 6 and above.
Jumbo Frames are supported only with gigabit (and faster) adapters operating with gigabit (and faster) link partners. Additionally, your switch infrastructure must support Jumbo Frames.
Some Intel gigabit adapters that support Jumbo Frames
have a frame size limit of 9238 bytes, with a corresponding MTU size
limit of 9216 bytes. The adapters with this limitation are based on the
Intel® 82571EB, 82572EI, 82573L, 82566, 82567, 82575 and 80003ES2LAN
controller. These correspond to the following product names:
Intel® 82574L Gigabit
Network Connection
Intel® Gigabit
CT Desktop Adapter
Intel® 82567LM Gigabit Network Connection
Intel® PRO/1000 PT Server Adapter
Intel® PRO/1000 PT Desktop Adapter
Intel® PRO/1000 PT Network Connection
Intel® PRO/1000 PT Dual Port Server Adapter
Intel® PRO/1000 PT Dual Port Network Connection
Intel® PRO/1000 PF Server Adapter
Intel® PRO/1000 PF Network Connection
Intel® PRO/1000 PF Dual Port Server Adapter
Intel® PRO/1000 PB Server Connection
Intel® PRO/1000 PL Network Connection
Intel® PRO/1000 EB Network Connection with I/O
Acceleration
Intel® PRO/1000 EB Backplane Connection with I/O
Acceleration
Intel® PRO/1000 PT Quad Port Server Adapter
Intel® PRO/1000 PF Quad Port Server Adapter
Intel® Gigabit VT Quad Port Server Adapter
Intel® Gigabit PT Quad Port Server ExpressModule
Intel® 82567LM-3 Gigabit Network Connection
Intel® 82567LF-3 Gigabit Network Connection
Intel® 82576 Gigabit Dual Port Network Connection
Intel® Gigabit ET Dual Port Server Adapter
Intel® Gigabit EF Dual Port Server Adapter
Intel® 82576 Gigabit Dual Port Server Network Connection
Adapters based on the
Intel® 82542, 82573V/E, 82562V, and 82566 controllers do not support Jumbo
Frames. These correspond to the following product names:
Intel® 82567V Gigabit Network Connection
Intel® 82567LF Gigabit Network
Connection
Intel® PRO/1000 Gigabit Server Adapter
Intel® PRO/1000 PM Network Connection
Intel® 82562V 10/100 Network Connection
Intel® 82566DM Gigabit Network Connection
Intel® 82566DC Gigabit Network Connection
Intel 82566MM Gigabit Network Connection
Intel 82566MC Gigabit Network Connection
Intel 82562GT 10/100 Network Connection
Intel 82562G 10/100 Network Connection
Jumbo Frames only work with IP.
Ethernet_II must be the only frame type loaded for the board.
The MAXIMUM PHYSICAL RECEIVE PACKET SIZE setting must be set to the size of the jumbo frame.
The Intel driver includes the Wake on PME assertion feature for NetWare 6.5 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=1 on the command line. |
The following adapters support WoL* only on Port A:
Wake On LAN is not supported for the Intel Gigabit VT Quad Port Server Adapter.
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.
Last modified on 7/30/08 9:10a Revision 41
Intel® Ethernet network adapters are enabled for use in selected servers equipped with PCI Hot Plug support and running Novell NetWare* 6.5.
|
NOTES:
If you replace an adapter in a Hot Plug slot, do not place the removed adapter back into
the same network until the server has rebooted. The two adapters may have the same
virtual
MAC address and create a conflict. PCI Hot Plug only works between identical Intel network adapters. Hot swapping is supported. In other words, you can remove an adapter and replace it with another adapter of the same type in the same slot. |
For more information on setting up and using Hot Plug support in your server, see your server's documentation.
Make sure you have the latest NetWare support pack installed before using Hot Plug. If teaming options are not used, the driver will unload when the slot power is off and reload when the slot is powered again. The keyword, PERSIST, can be used to control this behavior as follows:
0 = Never persist
1 = Always persist
2 = Auto persist (default).
Last modified on 12/16/10 3:27p Revision 6
The following NetWare* keywords are applicable for the E1000E driver.
| Parameter | Values | Default Value | Description |
|---|---|---|---|
| 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. |
| Frame | ethernet_802.2 ethernet_802.3 ethernet_snap ethernet_ii | ethernet_802.2 | Configures the adapter to process the valid NetWare Ethernet frame. |
| Speed | 0, 10, 100 | 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 link partner. Gig speed can only be achieved by auto-negotiation. This setting has no effect on fiber adapters which are defined to be 1000 Mbps. |
| ForceDuplex | 0 2 | 0 | On copper-based adapters, forces the duplex mode. 1 - indicates half duplex, 2 - indicates full duplex. If this parameter is not specified, or is set to 0, the adapter will auto-negotiate to the best possible link. If it cannot auto-negotiate, it will default to half-duplex. This setting has no effect on fiber adapters which are defined to be full duplex. |
| 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. 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. |
| FlowControl | 0 - 3 | 3 | Controls the ability of the adapter to advertise flow control capabilities. Default is to allow both TX and RX flow control. 0 is off, 1 is RX, 2 is TX, 3 is both. |
| Jumbo | 0-16128 | 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. |
| RxChecksum | 0-1 | 0 | When set to 1' 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 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. This option only works on supported OS versions. Unlike other keywords, this setting is tracked on a per-frame-type basis, and only works on Ethernet II and Ethernet SNAP frame. |
| WaitForLink | 0 -1 | 0 |
Controls whether or not the driver will wait for link before finishing initialization. A value of 1 causes the driver to wait until auto-negotiation is complete before finishing initialization and returning to the command prompt. A value to 0 will cause the driver to initialize faster, but also may cause it to display incorrect link information when it loads. |
| Poll | 0 - 2 | 0 (2 for 82547-based adapters & beyond) |
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 | 2 | 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. The default value, 2, sets the driver in auto-persistency mode. |
| TxDescriptors | 32-128 | 96 | TxDescriptors 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. |
| RxDescriptors | 8-128 (parameter must be in multiples of 8) | 64 | RxDescriptors 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. |
| PMEDisable | 0-1 | 0 | Enable/Disable the waking of the system by asserting PME when a Magic Packet is received while powered down. |
| CoalesceBuffers | 32-128 | 96 | Coalesce Buffers are used to copy fragments of a transmit packet into contiguous memory before assigning them a transmit descriptor. This reduces the number of transmit descriptors required for each packet transmission. |
Last modified on 11/04/09 9:19a Revision 9
This version of E1000ODI.COM requires latest version of the VLM client (version 1.21 or greater).
Refer to the Novell NetWare documentation for complete installation instructions.
In CONFIG.SYS, add the line LASTDRIVE=Z. In NET.CFG, under the NetWare DOS REQUESTER section (indented), add the line FIRST NETWORK DRIVE=<the first unused drive letter>.
Support for promiscuous mode is not available as ASM does not include a receive monitor stack. If needed, load RXMONSTK.COM from the VLM client kit. RXMONSTK.COM should be loaded before E1000ODI.COM and after LSL.COM in autoexec.bat.
If running EMM386, make sure you are using v4.49 or later (ships with DOS 6.22).
AUTOEXEC.BAT:
CD\NWCLIENT
LSL
E1000ODI
IPXODI
NETX (or VLM optional)
CONFIG.SYS:
DEVICE=C:\WINDOWS|HIMEM.SYS
BUFFERS=30,0
FILES=60 (This can be set to more than 60 to improve performance.)
LASTDRIVE=Z (for NETX LASTDRIVE=F or first available drive letter)
NET.CFG:
LINK DRIVER E1000ODI
FRAME ETHERNET_802.2
PROTOCOL IPX EO Ethernet_802.2
NETWARE DOS REQUESTER
FIRST NETWORK DRIVE = F
Last modified on 8/22/06 2:34p Revision 4
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.
For optimal performance by the SNMP agent, install the appropriate NetWare drivers:
The SNMP agent package is compliant with the following driver versions:
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 http://support.novell.com.
Register to receive Traps by adding the IP address of the management station to the list in the SYS:\ETC\TRAPTARG.CFG file.
| 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. |
Last modified on 5/10/07 10:57a Revision 9