Damn it... should have researched this better...
Thanks anyway! Just made a windows application to generate the "codes" using that information for the next time I need one. PM me if someone is interested.
Just in case anyone was having the same problem as I did... This thread ended up saving me!
So I bought a new Supermicro X11DPH-I and a cheap ES CPU just to test the board. However the motherboard came with bios v3.0c which didn't detect the CPU. It would hang on POST with a message saying "PEI...
Ok, I was not sure if it was that or the ones that go on the cables.
Found this better deal on ebay. It's a lot of them, but for that price I wouldn't mind the extra ones... :D
Got the cable for 100Gb and... it works! :)
This is actually connecting 2 cards back to back, one with original firmware in Linux CentOS and the other with the flashed version (12.23.1020) in Windows server 2016.
Cable from this tread. STH forum rules! :cool:
Now to find a 100Gb switch...:rolleyes:
I've already got mines and I've been doing some connectivity tests with the FW that comes with them. They are detected in windows as ConnectX-4 with the standard drivers which is nice. They are also in Ethernet mode by default. This is what I get from flint (replaced MAC and GUID)
C:\Program...
According to this mellanox doc 834972-B22 is the equivalent to MFA1A00-E005. And looking to their cable documentation, cables MFA1A00-Exxx are infiniband. The Ethernet ones are MFA1A00-Cxxx.
If they work with Ethernet it would be interesting to know.
I'm not angry, it was supposed to be a worried face. I've beem looking out for one of these for some time.
Just checked the Mellanox doc's and it can only be this model. Can you confirm?
So, I also manage to modify one of these switches :)
Thanks mpogr for sharing your knowledge!
The one thing that really pissed me off was how noisy these little things are!
Instead of buying new low speed fans which would be just as expensive as the switch, I decided I would have to use the...
I tried that. Plugged both ends of the cable on the switch. With 1m cable I get link and with "show inventory" command I see this:
...
System has 24 transceiver slots
Port Manufacturer Model Serial Number Rev
---- ---------------- ---------------- ---------------- ----
1...
Looks like the fan speeds do actually work after power cycling the switch. They just take a minute to slow down.
- EDIT-
Nop.. after leaving the switch off for one day, and them powering it on again, it ignores the fan settings and slows down for a bit, then goes back up to "normal jet speeds"...
Mine came with version 4.12.7.1. So the enable3px file works fine. Just checked and it is always present even after power cycling the switch.
The one thing that does not stays after power cycle is the damn fan speed setting (environment fan-speed override 30). It is stored in the running...
When I did it the first time it continued to detect the cables/qsfp. Didn't went back to check if the file remains in the filesystem, but my guess is that it does. Otherwise a write command probably may have had save that along with the running config.
When I bought it it came factory reseted to...
So I've been playing with the fan settings and this baby handles the fans at 30% without any problem. Temperatures are between 28 and 42ºC idling. And the noise is a LOT less. Wow.. Also the power draw is a bit less.
Anyway, going back to the subject... Bought a few QSFP+ cables and a RJ45 1GBe...
Finally I got the switch and after some time playing with it here are my findings.
It came with EOS version 4.12.7.1 and had no configuration on it. By default it did not detect any transceiver nor DAC cable. After running "touch /mnt/flash/enable3px" in bash it detectec my generic amphenol made...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.