Check their firmware and if possible, use another OS to test them. I found it simplest to use the boot image at the bottom of the page here to update the firmware.I could use some direct help here real quick if anyone has the answer. I have 3 IB HCAs. 1 MHEA28-XTC and 2 MHGH28-XTC. The MHEA28-XTC installs fine with the OFED driver package and was up and running right away on my Windows 7 machine, even without a reboot. The 2 MHGH28-XTC cards both refuse to function (in windows7). I've tried the OFED package, I've tried the windows drivers windows finds and installs and I've tried the drivers I found on Mellanox's website. I've tried the cards in 2 different windows 7 machines that are highly different hardware (i5 ivy bridge and a i7 950) and they report the same problem on each card and each machine:
This device cannot start. (Code 10)
When both of the MHGH28-XTC cards arrived they were packed very poorly and the brackets on both of them were bent at a 45 degree angle. I wanted to toss this out there and see if just maybe this issue was a common one with an easy fix I somehow missed, otherwise I'll be contacting the seller/ebay/paypal for a RMA/refund based on the poor packaging and bent brackets.
Thanks!
Check their firmware and if possible, use another OS to test them. I found it simplest to use the boot image at the bottom of the page here to update the firmware.
[seq-read]
rw=read
ioengine=libaio
iodepth=1
size=8g
directory=/home/max/Away
fadvise_hint=0
blocksize=8k
direct=0
numjobs=1
nrfiles=1
runtime=10m
time_based
In theory, but no experience besides CX-2 to CX-2. CX-2 with EN can do mtu of 9600 vs 16K for my Intel AT cards. You have to use connectx_port_config to switch one or both ports. You can find supported port configs here. Also, check if the switch can deal with Ethernet.Has anyone used a ConnectX-2/3 VPI IB card as an Ethernet adapter with a QSFP to SFP+ cable?
Can this actually replace say, an Intel X520-DA2?
Yeah, I saw the port configs on page 17 of the ConnectX-2 user manual. On page 38 they also show the Windows driver setting to choose the port protocol, but just prior to that the screenshot shows Device Manager with the card as an IPoIB adapter. Does this really function as Ethernet on a physical layer or does it do the encapsulation and is therefore working in IPoIB (and thus not supporting bridging, MAC spoofing, and whatever else)?In theory, but no experience besides CX-2 to CX-2. CX-2 with EN can do mtu of 9600 vs 16K for my Intel AT cards. You have to use connectx_port_config to switch one or both ports. You can find supported port configs here. Also, check if the switch can deal with Ethernet.
max@TT:~$ sudo ibping -S
max@TC2:~$ sudo ibping -G 0x0002c903004a9ba3
Pong from TT.(none) (Lid 10): time 0.304 ms
Pong from TT.(none) (Lid 10): time 0.253 ms
Pong from TT.(none) (Lid 10): time 0.253 ms
Pong from TT.(none) (Lid 10): time 0.251 ms
Pong from TT.(none) (Lid 10): time 0.254 ms
Pong from TT.(none) (Lid 10): time 0.251 ms
Pong from TT.(none) (Lid 10): time 0.256 ms
Pong from TT.(none) (Lid 10): time 0.253 ms
Pong from TT.(none) (Lid 10): time 0.250 ms
Pong from TT.(none) (Lid 10): time 0.255 ms
max@TC2:~$ ping 10.0.0.1
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
64 bytes from 10.0.0.1: icmp_req=1 ttl=64 time=0.880 ms
64 bytes from 10.0.0.1: icmp_req=2 ttl=64 time=0.114 ms
64 bytes from 10.0.0.1: icmp_req=3 ttl=64 time=0.112 ms
64 bytes from 10.0.0.1: icmp_req=4 ttl=64 time=0.109 ms
64 bytes from 10.0.0.1: icmp_req=5 ttl=64 time=0.110 ms
64 bytes from 10.0.0.1: icmp_req=6 ttl=64 time=0.109 ms
64 bytes from 10.0.0.1: icmp_req=7 ttl=64 time=0.106 ms
64 bytes from 10.0.0.1: icmp_req=8 ttl=64 time=0.106 ms
64 bytes from 10.0.0.1: icmp_req=9 ttl=64 time=0.110 ms
^C
--- 10.0.0.1 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 7998ms
rtt min/avg/max/mdev = 0.106/0.195/0.880/0.242 ms