Intel's diagnostic software lets you test the adapter to see if there are any problems with the adapter hardware, the cabling, or the network connection. You can also use diagnostics to isolate problems during troubleshooting. There are four test programs documented here. Both test Intel® adapters, and operate identically.
DIAGS.EXE runs under MS-DOS* v6.22 or later. (It will not run from a Windows Command Prompt within any version of the Microsoft* Windows* operating system or in any other non MS-DOS operating system..)
DIAGS64.EFI for the EFI environment in Itanium®-based systems.
DIAGES64E.EFI for platforms based on the Intel® 64 Architecture
These utilities are designed to test hardware operation and confirm the adapter's ability to communicate with another adapter in the same network. They are not throughput measurement tools.
The utilities can test the adapter whether or not there is a responder present. In order to do a thorough test, however, you should set a responder system prior to starting the test. If there are hot keys, the letters will be highlighted.
|
NOTE: If there is an MS-DOS network driver present, such as NDIS2 or DOS-ODI, the test utility and/or the network driver could become unstable. You should reboot and ensure that there are no network drivers loaded. |
Boot to MS-DOS.
Navigate to the \APPS\TOOLS directory.
Type DIAGS, and press <Enter>
The test utility program automatically scans the hardware
and lists all Intel-based adapters. They are listed in the following manner:
If you have only one network connection in your system, this screen will be bypassed.
If you have a dual- or quad-port adapter, each port is listed separately starting with Port A, then Port B, etc. You can find the port information on the bracket label.
The test utility displays its main menu:
Boot to the EFI shell.
Navigate to the \TOOLS\EFI64\EndUser directory.
Type DIAGS64 or DIAGS64E and press <Enter>
If you have only one network connection in your system, this screen will be bypassed.
If you have a dual- or quad-port adapter, each port is listed separately starting with Port A, then Port B, etc. You can find the port information on the bracket label.
The test utility displays its main menu:
Selecting "View Adapter Configuration" will bring up the adapter configuration screen. This screen describes various properties of the adapter.
Press <F5> to view additional information on the PCI slot occupied by the adapter. This is primarily used for troubleshooting by technical support.
Press any key to return to Adapter Configuration.
Selecting "Test Adapter" from the Main Menu brings up the Test Menu. This allows you to test the adapter, select which tests to perform, or perform networking test.
Selecting this option brings up the test screen. While tests are being performed, a rotating spinner is shown letting the user know that the application is still "alive." The results of the tests are displayed as each test is performed. If multiple test passes are selected, then the results contain a count of test failures. A list containing zeros means that all tests have passed. Single tests will display "Passed" or "Failed" for each pass.
The test setup screen allows you to configure and select the specific tests desired. Each option is toggled by moving the cursor with the arrow keys and pressing <Enter> to change the option. The number of tests is simply entered from the keyboard in the appropriate box. If there is a gap in the menu, that means the test is not supported by your adapter. By default, local diagnostics run automatically, while network diagnostics are disabled.
|
NOTE: The test program will test attributes that are applicable to your adapter. Only supported tests are displayed. The screen shown here is an example of the types of tests performed. |
Device Registers - Test patterns are written, read and verified through the adapter's device registers to ensure proper functionality.
FIFOs - This utility will write test bit patterns to the adapter's FIFO buffers, to make sure the FIFOs are working properly. Not all adapters have FIFO, so it will not appear in all test lists.
EEPROM - Tests both the readability of the EEPROM as well as the integrity of the data stored in the EEPROM. It reads the EEPROM and calculates the checksum. This checksum is then compared to the checksum stored in the EEPROM. If values are not the same, the test reports failure.
Interrupt - This tests the adapter's ability to generate an interrupt. On EFI, interrupts are not supported. Therefore, this test sets the interrupt cause register and reads the interrupt set register, verifying the card internally registered an interrupt.
MAC Loopback and PHY Loopback - There are two internal loopback tests. These tests set the adapter in the appropriate loopback mode and send packets back through the adapter's receive circuitry and logic. These tests are chipset dependant and may not be selectable.
Link - This checks to see if the adapter has link or does not have link.
Network Test - The Network Test looks for a responder, and then sends packets. If no responder is found, then the test reports failure. If no link is found, it will also report a failure. If packets are received back from the responder, the test reports success.
|
NOTE: In some cases, the network test will fail if the adapter is connected to a switch with Spanning Tree Protocol (STP) enabled. |
The networking menu contains network specific tests such as Spanning Tree detection and Network test responder.
This allows the user to set up the adapter as a responder so a connected system can perform the network test portion of the diagnostics tests. Although you can use a variety of adapters as the responder and connect directly or through a switch, the best results are obtained with a cross-over cable and a same-type adapter.
When you press <Esc>, the responder operation is cancelled and control is immediately returned to the Networking menu.
Spanning trees can be troublesome in a networking configuration. The Detect Spanning Tree option attempts to detect if a spanning tree exists on the network. This is done by resetting the link and listening for spanning tree packets.
Last modified on 11/22/10 4:07p Revision 11
The Intel PCI NIC Identification Utility identifies Intel PCI NIC adapters and provides adapter properties and assigned resources. You can readily use this information in batch, script and configuration files for automation purposes.
The utility returns the following values:
SLOT (Slot number in decimal). The PCI logical slot number reported by the adapter, in decimal format. Not related to the physical slot number on the motherboard.
SLOTX (Slot number in hexadecimal, for Gigabit solutions). The PCI logical slot number reported by the adapter, in hexadecimal format. Not related to the physical slot number on the motherboard.
PCI ID (PCI device ID). Adapters sharing the same PCI ID can use the same driver. See the table at the end of this document showing the relationship between drivers and PCI IDs.
SSID (Sub System ID). The PCI subsystem ID and subvendor ID, displayed in hexadecimal. Each adapter model has a different SSID. The PCI ID identifies the adapter family; the SSID identifies the specific model.
RevID (PCI Revision ID). The PCI Revision ID reported by the adapter, in decimal format. The PCI Revision ID can be the only difference between some adapter SKUs.
MAC (MAC address). The 12-digit Ethernet ID assigned to the adapter. This number is also printed on the adapter label.
To run IDADAPT.EXE, you must start the computer in MS-DOS 6.22 or above. This utility should not be run from a Windows Command Prompt within any version of Microsoft Windows*, or in any other non-DOS operating systems.
IDADAPT.EXE can be run with no command line options, or with either of the following command line options:
|
/? |
Displays help information |
|
/B:<filename> |
Creates a file called <filename> and stores the adapter's properties in it. The file is formatted as a DOS batch file, and can be executed as such if <filename> ends in .BAT. Executing it will create environment variables from the adapter properties. Usage examples are listed below. |
Running the utility with no command line parameters displays the adapter properties on the screen. For example, if you enter IDADAPT in a computer with 2 Intel PCI adapters installed, the display would resemble the following:
NIC1 SLOT=43 SLOTX=0068 PCI ID=1229 SSID=10118086 MAC=0002B31FE072 RevID=4 NIC2 SLOT=47 SLOTX=0069 PCI ID=1031 SSID=10118086 MAC=0090270AAF73 RevID=4
In this example, the first adapter has the following properties:
Logical slot number is 43 (decimal)
Logical slot number is 0068 (hexadecimal)
PCI device ID is 1229
Sub System ID is 10118086
PCI Revision ID is 4
MAC address is 0002B31FE072
If the utility does not find any adapters, it reports "No supported adapters were found" and returns an error level of 1. You can use the error level for conditional branching in batch files.
If you run the utility using /B:<filename>, it creates a file with the name you specified. This file contains adapter properties in a batch file format. This is an example batch file:
SET NIC1_SLOT=43 SET NIC1_SLOTX=0068 SET NIC1_PCIID=1229 SET NIC1_SSID=10118086 SET NIC1_MAC=0002B31FE072 SET NIC1_REVID=4 SET NIC2_SLOT=47 SET NIC2_SLOTX=0069 SET NIC2_PCIID=1031 SET NIC2_SSID=10118086 SET NIC2_MAC=0090270AAF73 SET NIC2_REVID=4
When the name you assign to the file ends in .BAT, it can be executed in MS-DOS. Executing the file sets environment variables for each property of each adapter.
Once the environment variables are created by the batch file, you can insert the values into configuration files as needed. See examples below.
When using this batch file, remember that about 64 bytes of environment space will be needed for each adapter port found. Ensure that you make sufficient environment space available in your configuration. To set the available environment space in DOS, use the shell= command in the CONFIG.SYS file. For example, to set the environment space to 2048 bytes, you would use the following line in the CONFIG.SYS file (assuming you are booting from the A drive):
SHELL=A:\command.com a:\ /e:2048 /P
Important note concerning slot numbering
The decimal slot number (SLOT) returned by the utility is formatted in conventional style for both 10/100 and 10/100/1000 adapters. The conventional style consists of the PCI bus number plus the PCI device number. This will work in the PROTOCOL.INI for the NDIS 2 driver for both adapter families. However, this will not work for the DOS ODI driver for 1Gigabit capable adapters, or second port of a multiport 1Gigabit capable adapter in the PROTOCOL.INI for NDIS 2 drivers.
The hexadecimal slot number (SLOTX) returned by the utility is formatted differently for 1 Gigabit capable adapters. This newer format takes the conventional style and left-shifts it 3 bits. The low order 3 bits are used to specify the port number on multiport 1 Gigabit capable adapters.
You should always use the SLOTX parameter in the NET.CFG for the DOS ODI driver for 1 Gigabit capable adapters (E1000ODI.COM). Use of the SLOTX parameter in the PROTOCOL.INI for the NDIS 2 driver for the 1 Gigabit capable adapters (E1000.DOS) is optional unless attempting to use the second port of a multiport adapter.
When using the slot number in a PROTOCOL.INI, remember that the usage rules are different for hexadecimal values as opposed to decimal values. When using a hexadecimal value, the number must be preceded by 0x.
PROTOCOL.INI decimal value example:
Drivername = E1000$ SLOT = 47
PROTOCOL.INI hexadecimal value example:
Drivername = E1000$ SLOT = 0x0138
NET.CFG example
LINK DRIVER E1000 SLOT 0138
1. To create a startup disk that loads a Packet Driver named PCKTDRVR.COM on the second-found NIC, the AUTOEXEC.BAT file
might contain the following:IDADAPT /B:INTELSET.BAT IF ERRORLEVEL 1 GOTO NO_NIC CALL INTELSET.BAT PCKTDRVR 0x60 %NIC2_SLOT% GOTO END :NO_NIC ECHO NO ADAPTER FOUND!! PAUSE :END2. To create a startup disk that automatically detects the adapter model and loads the proper DOS ODI driver, the AUTOEXEC.BAT
file might contain the following:IDADAPT /B:INTELSET.BAT IF ERRORLEVEL 1 GOTO NO_NIC CALL INTELSET.BAT LSL IF "%NIC1_PCIID%" == "1229" GOTO PRO100 IF "%NIC1_PCIID%" == "2449" GOTO PRO100 IF "%NIC1_PCIID%" == "1000" GOTO PRO1000 IF "%NIC1_PCIID%" == "1001" GOTO PRO1000 IF "%NIC1_PCIID%" == "1002" GOTO PRO1000 IF "%NIC1_PCIID%" == "1003" GOTO PRO1000 IF "%NIC1_PCIID%" == "1004" GOTO PRO1000 GOTO NO_NIC :PRO100 E100BODI GOTO CONTINUE :PRO1000 E1000ODI GOTO CONTINUE :CONTINUE IPXODI VLM /V4 GOTO END :NO_NIC ECHO !! NO SUITABLE ADAPTER FOUND !! PAUSE :END
This utility does not work with any Intel PCMCIA, ISA, EISA or MCA bus adapters, or Intel network adapters of any architecture released prior to 1996.
IDADAPT.EXE will detect and return information on a maximum of sixteen adapter ports in a computer.
IDADAPT.EXE will not work if EMM386.EXE or a similar upper memory manager is loaded. If you must use EMM386 in your boot disk configuration due to memory limitations, you can set up your boot diskette to boot without EMM386, run IDADAPT and build a batch file with the adapter information, then change your configuration files to include EMM386 and reboot. Then run the resulting batch file to set the environment variables.
See idadapt.txt.
Last modified on 3/13/09 12:49p Revision 7
DOCS/index.htm 0000755 0000000 0000000 00000002164 10671254344 010331 0 ustar
The \APPS\TOOLS directory contains the diagnostic utility for Intel® Network Adapters.
Also included in this directory: idadapt.exe - an MS-DOS* utility used to enhance automated installation processes by capturing NIC identification and configuration properties.
If you are in a Microsoft* Windows* environment, you can use Intel® PROSet to perform diagnostic tests on your adapter.
To run the .EXE utilities, you must start the computer with MS-DOS version 6.22 or later. They will not run from a Windows Command Prompt within any version of Microsoft Windows, or in any other non-DOS operating system.
Last modified on 9/10/07 2:47p Revision 4
