Just got a 25gb Intel NIC and installed the drivers. They show up in Windows 10 adapter list just fine. I plugged in an Intel 25gb Transceiver and fiber cable but the link wont come up. I verified that I can see a transmit light out one side of the transceiver so it has power and seems to be trying, I also verified the transceiver on my switch end is fine, and verified the fiber cable has transmit and receive on the proper side. I tried out a ConnectX-5 NIC in its place and everything works fine with that using the same transceiver and fiber cable, so only the Intel NIC is having the issue. Anyone have any ideas to try that I might be overlooking before I send the NIC back as defective?
In the IntelProSet Utility, run all the self-tests starting with the Hardware-Test (lowest one in the list).
Edit: Dumb question, does the E810 show up under Performance in Taskmanager? I remember having flow-control enabled and that made windows be weird about my E810
I don’t have any Ethernet category under the performance tab in task manager. That is odd. I assume because there is no network connectivity maybe? edit: yes, on my Mellanox NIC it does show up but if I unplug the cable then the category disappears. So that area is only there when a valid connection is present.
I ran the hardware test and everything says passed. The only other test it let’s me is the connection test. Which fails with no connection.
I the proset utility I forced 25gb instead of auto negotiation in the adapter settings and forced 25gb on my switch ports. I also tried enabling a setting called “Auto configuration of No FEC modules” just to see if it would help. It still won’t detect any cable plugged in. According to the help area at the bottom of proset, FEC can improve link stability at cost of latency, so figured it was worth a try. Turning the auto setting on or off didn’t help, and manually specifying an FEC mode did not help either.
My flow control in the adapter settings defaulted to disabled. I tried turning it on, but no changer in behavior.
Does the E810 show up under Network Devices?
If it does, it is not a hardware-issue, I think.
My settings (using 10G link using FS.com transceivers branded as such):
| Setting | value | Note |
|---|---|---|
| Auto-Conf of Non-FEC-Modules | Deactivated | |
| Receive buffer | 512 | |
| EncapOverhead | 0 | |
| FEC-Mode | Auto FEC-Mode | |
| Flow Control | Auto Negotiate | Changing this to anything else makes me loose the connection |
| Interrupt Modulation | Active | |
| Interrupt Mod. Rate | Adaptive | |
| IPv4 Checksum offloading | Rx and Tx active | |
| Jumbo Frame | 4088 Byte | |
| Large-Send Offload IPv4 | Active | |
| Large-Send Offload IPv6 | Active | |
| Local MAC | default | |
| Max RSS-Ques | 16 | |
| Max RSS-Ques per VF | 4 | |
| MDD Reset | deactivated | |
| Network Direct | iWARP | |
| Package and VLAN | both active | |
| PTP Hardware Timestamp | inactive | |
| RDMA Max VF | 0 | |
| RDMA VF | deactivated | |
| ROCEv2 Framesize | 1024 | |
| RSS receive scaling | active | |
| Software timestamp | deactivated | |
| TCP-Checksum offloading IPv4 | Rx and Tx active | |
| TCP-Checksum offloading IPv6 | Rx and Tx active | |
| Transmit buffer | 512 | |
| UDP-Checksum offloading IPv4 | Rx and Tx active | |
| UDP-Checksum offloading IPv6 | Rx and Tx active | |
| UDP-Segmentation offloading IPv4 | active | |
| UDP-Segmentation offloading IPv6 | active | |
| Protocol | active | |
| Connection status on shutdown | active |
1 Like
Yes it does. It doesn’t seem like a hardware problem in the NIC to me either since the driver installed fine, the proset utility opens fine and sees the NIC, and a hardware test says everything passes. But I also tried a bunch of different transceivers and fiber cables and none of them work, and yet they do work in another brand NIC. It would seem to be a software configure issue, but I have tried changing everything the driver let’s me change.
Ill try those settings when I get home today and see if it helps.
I tried those settings, well everything but the very last one as that does not appear in my adapter configure list.
I also tried all options for flow control
And I tried forcing both 25gb and 10gb speed instead of auto negotiation.
I tried a genuine Intel 25gb transceiver, a genuine Ubiquiti transceiver, and a 10GTEK brand transceiver. I looked up the Intel data sheet to verify that the NIC is open to any transceivers too and it is. I also swapped between the Ubiquiti and 10GTEK transceivers on the switch as well just to change things up.
I tried two different OM4 fiber cables as well.
Nothing I have done will let the NIC detect a cable plugged in.
So I put the ConnectX-5 back in just now and it came right up working fine again.
Thanks for the help on this, but I guess I’ll just be sending this Intel NIC back and buying a ConnectX-6 to replace it.
1 Like
Very strange.
Shame the E810 did not play along nicely.