Intel® Ethernet Adapters and Devices User Guide

ID Date Version Classification
705831 11/28/2024 Public

A newer version of this document is available. Customers should click here to go to the newest version.

Document Table of Contents

Diagnostics in Intel® PROSet

Intel’s diagnostic software lets you test the adapter to see if there are problems with the adapter hardware, the cabling, or the network connection. Refer to About Intel® PROSet for an overview of this software.

Intel PROSet allows you to run the following types of diagnostic tests on supported Windows* operating systems:

  • Connection test: Verifies network connectivity by pinging the DHCP server, WINS server, and gateway.

  • Cable tests: Provides information about cable properties.

  • Hardware tests: Determines if the adapter is functioning properly.

Note:

The Cable Test is not supported on all adapters and will not run on Direct Attached Cables (DAC) or fiber cables. The Cable Test will only be available on adapters that support it.

In Intel® PROSet Adapter Configuration Utility (Intel® PROSet ACU), use the Diagnostics panel.

The availability of these tests is dependent on the adapter and operating system. Tests may be disabled if:

  • The port is used as a manageability port.

  • The tests are being run from a virtual machine.

Note:

Windows diagnostics are not supported on ports based on an Intel® Ethernet Controller I225 and will fail.

Testing from Windows PowerShell*

Intel provides two PowerShell* cmdlets within Intel PROSet for Windows PowerShell software for testing your device:

  • Test-IntelNetDiagnostics runs the specified test suite on the specified device. See the Test-IntelNetDiagnostics cmdlet help inside PowerShell plus the following table for more information.

  • Test-IntelNetIdentifyAdapter blinks the LED on the specified device.

The following table describes the possible result codes from the Test-IntelNetDiagnostics cmdlet (where <X>, in the following table, indicates a value returned in the message).

ResultCode

Result Code

Description

RESULT_​PING_​GATEWAY_​PASS

00

Successfully pinged gateway address <X>.

RESULT_​PING_​DHCP_​PASS

01

Successfully pinged DHCP address <X>.

RESULT_​PING_​DNS_​PASS

02

Successfully pinged DNS address <X>.

RESULT_​PING_​WINS_​PASS

03

Successfully pinged WINS address <X>.

RESULT_​TEST_​ALREADY_​RUNNING

04

An instance of this test is already running. You can only have one test running at a time.

RESULT_​TCPIP_​NOT_​BOUND

05

TCP/IP protocol is not configured. To run this test configure this connection to use the TCP/IP protocol.

RESULT_​INVALID_​IP

07

The IP address for this connection is invalid. Possible cause: The system may be waiting for a response from a DHCP server.

RESULT_​INVALID_​STATIC_​IP

09

The IP address for this connection is invalid.

RESULT_​ANS_​BOUND

18

You cannot run this test while the device is included in a team or VLAN.

RESULT_​FORCE_​LOW_​SPEED

19

Auto-negotiation is not enabled on the device. The device has been configured to force a lower speed.

RESULT_​AUTO_​NEG_​IN_​PROGRESS

20

Auto-negotiation is not complete on this device. Please wait and try again later.

RESULT_​CAT5_​CABLE_​NEEDED

21

A Category 5 (or better) cable is required to run at 1Gbps. The cable connected to the device either is not Category 5 (or better) or has faulty wires.

RESULT_​NOT_​MAX_​SPEED

22

Link speed: <X> Mbps. The link partner is not capable of higher speeds.

RESULT_​1000_​NOT_​CHOOSEN

23

The link partner is not advertising a compatible speed. Please check that the link partner supports 1Gbps.

RESULT_​POWER_​SAVER

24

Link speed has been reduced because a Power Saver option is enabled. Disable power saving in your OS settings and run the test again.

RESULT_​SELF_​FORCE_​LOW_​SPEED

25

The device is configured to force a lower speed.

RESULT_​NO_​CABLE_​PROBLEMS

26

No cable problems detected.

RESULT_​CANT_​RUN_​TEST

27

Could not run the test at this time. Please try again later.

RESULT_​BAD_​CONNECTION

33

The test detected a bad connection. Distance to problem: <X> meters.

RESULT_​REMOTE_​RECV_​PASS

34

Passed

RESULT_​REMOTE_​RECV_​FAIL

35

Failed

RESULT_​REMOTE_​RECV_​UNKNOWN

36

Cable quality is unknown.

RESULT_​REMOTE_​LOCAL_​PASS

37

Passed

RESULT_​REMOTE_​LOCAL_​FAIL

38

Failed

RESULT_​REMOTE_​LOCAL_​UNKNOWN

39

Cable quality is unknown.

RESULT_​POLARITY_​NORMAL

40

Cable polarity is normal.

RESULT_​POLARITY_​REVERSED

41

Cable polarity is reversed.

RESULT_​CABLE_​LENGTH

42

Cable length: <X> meters.

RESULT_​FULL_​SPEED

43

This device is running at full speed.

RESULT_​POOR_​AUTONEG

44

Cable quality is poor or no cable is connected. Possible causes: Faulty cable; faulty connector; or a speed/duplex mismatch. Verify that the speed/duplex setting on the switch/hub is configured for auto-negotiation.

RESULT_​QUALITY_​POOR

45

Cable quality is poor or no cable is connected. Possible causes: Faulty cable; faulty connector; or a speed/duplex mismatch.

RESULT_​QUALITY_​ADAQUATE

46

Cable quality is adequate.

RESULT_​QUALITY_​GOOD

47

Cable quality is good.

RESULT_​QUALITY_​EXCELLENT

48

Cable quality is excellent.

RESULT_​QUALITY_​UNKNOWN

49

Cable quality is unknown.

RESULT_​QUALITY_​IMPD_​MISMATCH

50

The test detected a frequency response that does not meet IEEE specifications.

RESULT_​NO_​LINK

51

This device does not have link. Make sure the cable is connected and the speed and duplex settings are configured correctly on the device and link partner.

RESULT_​EEPROM_​PASS

52

Passed

RESULT_​FIFO_​PASS

53

Passed

RESULT_​REGISTER_​PASS

54

Passed

RESULT_​INTERRUPT_​PASS

55

Passed

RESULT_​LOOPBACK_​PASS

56

Passed

RESULT_​EXTENDED_​LOOPBACK_​PASS

57

Passed

RESULT_​EEPROM_​FAIL

58

Failed

RESULT_​FIFO_​FAIL

59

Failed

RESULT_​REGISTER_​FAIL

60

Failed

RESULT_​INTERRUPT_​FAIL

61

Failed

RESULT_​LOOPBACK_​FAIL

62

Failed

RESULT_​EXTENDED_​LOOPBACK_​FAIL

63

Failed

RESULT_​NVM_​INTEGRITY_​PASS

64

Passed

RESULT_​NVM_​INTEGRITY_​FAIL

65

Failed

RESULT_​DEVICE_​NEEDS_​RESTART

66

This device requires a restart.

RESULT_​BOOTED

67

Could not run the test at this time. The device may be connected to a remote target. Disconnecting the cable will enable the test.

RESULT_​MANAGEABILITY_​SET

68

Could not run the test at this time. This device is used as a manageability port. Disconnecting the cable will enable the test.

RESULT_​TEST_​NOT_​SUPPORTED

69

The device does not support this test.

RESULT_​CONNECTION_​TEST_​FAILED

70

This test relies on a response from a gateway; DNS; DHCP; or WINS server and no such response was received. Any such server for this connection may be unavailable or misconfigured.

RESULT_​UNKNOWN_​CONNECTION

71

Cable integrity is unknown.

RESULT_​CONNECTION_​TEST_​FAILED_​APIPA

72

This test relies on a response from a gateway; DNS; DHCP; or WINS server and no such response was received. Any such server for this connection may be unavailable or misconfigured.This device is configured to automatically obtain an IP address but no DHCP server is present on the network. Windows selected an IP address using alternate private IP addressing.

RESULT_​THERMAL_​SENSOR_​PASS

73

Temperature is normal.

RESULT_​THERMAL_​SENSOR_​FAIL

74

Possible values: The device overheated and was stopped. The device overheated, and link speed was reduced.