Thanks for the reply. Of course, not supported does not necessarily mean it won't work i.e. I've got a few Connect X MNEH cards working perfectly fine in Windows 2012.
Anyway, are you saying that these will work fine on Windows 2008R2? I guess I'll check now.
Some of the ConnectX Cards will work, it depends on the firmware, but they are not supported for Windows 2012. Some of the RDMA features won't/don't work. I have not used them with Windows Server 2008R2.
Have you looked at SDP to just not use tcp all together?
Has worked great for me a year or two ago
We have and it's a lot faster, but I don't see how using SDP on a router that forwards IP traffic would work.
Hi~
I'm finding another ISR9024D-M on somewhere.
I'm also change to IB firmware working platform to CentOS.
After some work proceed some error was corrected and below is result.
Most big problem is can't access via console.
Is there any solution to INITIALIZE U-BOOT AREA?
Hi Mike,
Thanks but kind of know all you've posted already. I'll see what happens on Windows 28kr2 / Centos I guess.
Thanks
Drew
Hi~
If you have a ConnectX-2 VPI firmware above 2.9.8350 then you can use it!
If Mellanox support ConnectX-2 EN INTERIM firmware you can use it on WS2k12.
Good luck!
Henry, in regards to stock price, we can't comment on such matters.
Hi, I have a setup with a Mellanox SX1036 Ethernet switch and 2 servers, each with Mellanox ConnectX-2 HCA cards. Each HCA card has one of its (Ethernet) network ports connected to a port on the SX1036 switch, and are configured to 10 Gbps -- links are up and running. I'd like to use "iperf" to do some network performance testing. So, I've installed iperf on both servers and am ready to go. I was hoping that someone could point me to good examples of using "iperf" with a similar setup, i.e. servers with Mellanox HCAs communicating through a Mellanox switch. Thanks!
I'm succeed In-Band Firmware update and my 4036 doesn't report firmware problem anymore.....
But console wasn't come back.
I think that there is a some of initial configuration was corrupted.
If I use mlxburn command ...
Is there any method use mlxburn command with ISR BOOT INITIAL CONFIG.INI ?
If that's true, can you send me a ISR9024D-M initializing configration file?
or Any method correct console configuration in EEPROM via IB In-Band connection?
i am upgrading firmware version for my InfiniHost III EX MT 25208 card from 4.6.2 to 4.8.200 .
on command :
"mstflint -d 10:00.0 -i fw-25208-4_8_200-MHEL-CF128-T.bin bmstflint -d 10:00.0 -i fw-25208-4_8_200-MHEL-CF128-T.bin "
it gives error :
Current FW version on flash: N/A
New FW version: N/A
Read and verify Invariant Sector - DIFF DETECTED
Invariant sector mismatch. Address 0x27c in image: 0x23000094, while on flash: 0x20000094
The invariant sector can not be burnt in a failsafe manner.
You can perform the FW update without burning the invariant sector by
by specifying the -skip_is flag.
See FW release notes for details on invariant sector updates.
-E- Failsafe burn error: Invariant sector mismatch
IS IT SAFE TO TRY WITH -skip_is OR wat is the fix
Thanks
Ugh, the Jive commenting system seems to be messing up the formatting of the above post. It looks fine in the advanced editor, but is screwy when actually displayed.
The info in it is still all correct however.
This is very interesting.
I haven't picked up my switch yet, hopefully next week.
As a thought, with the Mellanox adapter cards it's possible to customise their behaviour when burning/creating firmware using flint. So far, when I've been buying cards off of eBay I've been making a dump/backup of both the firmware that comes with each card and the options it was burned with. (using the comand "mstflint -d [card address] dc > filename.fw")
I wonder if it's possible for you to remotely do something similar, to remotely dump firmware configuration for the 9024D-M switch?
If so, you might be able to get someone else here to dump theirs for a 9024D-M switch (with the console working), and compare the difference. Then hopefully fix yours.
Hmmm, that "N/A" for the "Current FW version on flash:" is a bit worrying.
Next thought, is that command you're quoting correct? It kind of looks like you've doubled up the options or the command or something?
If you do go ahead and burn the card with -skip_is, would you be ok to report back if it works? I think I used to do something similar with the old Infinihost III cards I bought on eBay several years ago, but I'm not sure. It's been a long time. That it's not detecting the current firmware version definitely worries me. I think it should be detecting that ok.
Have you made a backup of the firmware and config options already on the card? (mstflint can do this too)
I always do, just in case. Haven't needed to revert to original firmware yet on any of the IB cards I've bought from eBay, but if I do at least I'll be prepared (I hope).
Hi Andy,
Are you using Mellanox OFED, or the CentOS 6.4 supplied Infiniband drivers?
If you're using Mellanox OFED, are you sure you need to?
Asking because the easiest way for new Infiniband users using CentOS is to just use the included Infiniband packages:
$ sudo yum groupinstall "Infiniband Support"
That installs a bunch of drivers for Infiniband adapters (including most/all Mellanox cards), and things should "just work".
My understanding (might be incomplete) is that Mellanox OFED is more optimised/better for some stuff. But, if you don't need that "some stuff", why make things more complicated?
If you do need the Mellanox OFED later on, you can remove the inbuild CentOS Infiniband packages pretty easily:
$ sudo yum groupremove "Infiniband Support"
Hopefully that's helpful.
(note - edited for typo fixes)
Yeah, as Yair Ifergan mentioned, don't connect port 0 to port 0, then port 1 to port 1.
If you're connecting two boxes directly to each other, connect both of their port 0's to port 1 on the other. eg Kind of like crossing over the cables. Then run OpenSM (opensmd) on both. That way all 4 ports should come up as "ACTIVE".
I do this (using RHEL/CentOS) and it works fine with IPoIB layered on top. I can give you the CentOS ifcfg-ethx files, but I'm not sure they'd be helpful as Debian/Ubuntu does networking differently.
Sorry for the delay, I was travelling internationally, but am back home now.
I've just spun up RHEL 5.x in a VM locally to see where things are installed.
It looks like Infiniband support on RHEL 5.x stores everything in files under /etc/ofed/, unlike RHEL 6.x.
There is an /etc/ofed/openib.conf file in there. Have you tried changing the setting in there yet?
Hi!
I was test all command for my corrupted old InfiniScale III switch Voltaire ISR9024D-M.
Latese MFT 3.0 for Linux and Windows edition doesn't support it anymore.
And I was build old CentOS 5.2 (with OFED 2.0 - the last ibspark embbeded edition) system for recover my switch.
I found very interesting point...
flint, mstflint support Infiniscale IV switch, HCA only.
InfiniScale III was not...
mlxburn was support ISR9024D-M.
But whenever if you excute the mlxburn command that call the spark or ibspark (with -inband)
spark command is last option for ISR9024D-M now!
Because of MFT 2.1 or above will running in safeburn mode only when burnning on blank EEPROM
or corrupted...)
That caused my choice.
I'm also purchased another ISR9024D-M for export the normal firmware with normal u-boot configuration
from it.
(include baudrate, mac address, etc...)
fortunately spark support ri command to export current image to local disk.
But can't support dc command like flint....
I'll overwrite on corrupted EEROM with normal exported img file with spark ~ bb command.
(block burn. that's all overwrite on EEPROM)
Next...
I'll reburn with variety switch combination for recover original sysguid, nodeguide, bsn.
If my old one hasn't hardware problem then I can recover it...
The last interesting thing is i2c port.
That's for FAE or advanced users only interface.
I'll be back again in near future...
Thank you for your reply.
Hi Justin
Many thanks for the detailed information - really appreciated. I really need my primary machine running under Windows so I guess I need to mess around with W2K8R2 (but its a shame if I have to regress the OS to get it to work - just bought a Myricom 10gb card just in case) but I have a spare card or two so I'm going to brush up on my not very good Centos skills and give your instructions a bash!
Cheers
Drew