I wish there was a 9024D FAQ out there with all the different tricks and commands you guys have been using.
Recently I purchased a 9024D (not the M ver) and through some commands I’ve found my firmware version:
mlxburn -fwver -dev lid-2 -query
-I- FW Version: 1.0.5
Is that the most recent firmware and do I need to run a version of linux to burn the software properly. I’m a little confused at all of the different methods being used over the course of reading 2 or 3 threads worth.
Hi~ Yairi~
I think something about firmware update logic.
If firmware location address and boot up configuration (include console buadrate, etc) location address is different on EEPROM, What can I do?
Can I reconfigure boot up configuration in EEPROM?
Hi,
I am sure that it is doable but unfortunately i don’t have access to such switch and these things aren’t documented anywhere. it will take some common sense with zero documented knowledge to get done.
why do you want to change the baudrate, and other addresses anyhow?
Hi~!
I was found some cached information on my telnet application.
Because of some ppc-boot configuration was deleted and I can’t access console.
(I was execute printenv command and result was cached on my telnet application)
I want correct the value and reset my switch to factory default.
I’m also purchased another switch.
I’ll try recover old one next week.
Thank you!
I was build a OFED 1.2 based firmware work system last week.
(OFED can update blank EEPROM. 1.2.1 and above can’t via -nofs option… )
When you receive a 9024D-M, can you extract your rom image for me?
(Your firmware boot area have a correct console configuration, probably)
I think general update firmware does not have a console configuration.
It just update the EEPROM and recover current configuration parameters.
You can extrance current firmware via below command.
mst start
mst ib add
mst status → You can find your 9024D-M’s lid number (SW_MT23089_0008fxxxxxxxxxxx_lid-0x000x)
spark -d lid-0x000x q → Query your switch’s information
spark -d lid-0x000x v → Query your switch’s firmware information
spark -d lid-0x000x ri ./backup.img → Backup your switch’s firmware to local disk.
Have a nice day~
Are you able to access any kind of console over the ethernet, instead of com1?
I’m kind of thinking you could update your parameters using the Get/Store configuration dialog in the Device Manager java gui. It seems to have every parameter possible in there.
???
Yes, 1.0.5 is the most up2date firmware this product ever had.
as for documents, as a service to this dear group i packaged a bunch of documents for you guys.
keep in mind - this product was EOL’d long time ago. there is no official support for it. just a bunch of good people whiling to assist ;-)
checkout the following FTP account. you should find a ZIP file there. also, there are a few discussions on this site that can help you guys. just search the site for 9024
ftp server: ftp.support.mellanox.com
user: 9024-d
pass: 9024-d_eol
Good luck!
Ahhhh. Yeah, I don’t have a serial cable.
Well, actually I do have the cable, but none of the computer gear I have has a serial port. I’d have to buy a usb to serial converter or something.
So this doesn’t work?
=> setenv bootcmd “run addip sec prim”
=> saveenv
Oh well, at least we tried. You helped me learn a lot in the process. Thank you.
i don’t think i have access to those.
No worries. Was only a slim hope anyway.
GridVision 5.1.1 came with firmware 1.0.0 for the 9024D-M.
Firmware 1.0.5 isn’t in there, but can be found with some creative Googling for “voltaire_fw_images.tar”.
What’s the output from “help” by itself?
=> setenv baudrate=38400
=> saveenv
=> printenv
------> disappear baudrate=38400
=> setenv baudrate 38400
=> saveenv
=> printenv
------> recover baudrate=38400
You can only edit the parameter list that show via printenv command.
You are correct…
But I don’t have any idea what can I do…
This problem was originated my confused factory-default reset procedure.
I’ll drop the corrupted 9024D-M except PSU, Fan modules.
I’ll present newly arrive 9024D-M to my friend and some spare parts.
And I decide use QDR switched fabric only…
(Unfortunatly 4036 hasn’t GUI and CLI command about IB partition, only have a export/import partition.conf …)
I was thought that 9024D-M will be a Master SM of 4036 switch that have a GUI Grid Vision.
It’s a true that 9024D-M can support SM off-mode QDR 4036 switch.
But 9024D-M was very difficult collect a information about it.
I’ll move to another QDR or FDR switch.
Thank you for your advice.
(Especially Mr. Clift and Community support steps…)
Have a good day…
Below is my QDR fabric’s performance sample.
This method isn’t for me.
I was find your solution via googling in last month.
My corrupted 9024D-M don’t show me a any message via serial console port…
(Console port and Ethernet port configuration was gone and there isn’t any interface for user)
Therefore I can’t input anything via console interface.
The last resort is i2c port with MTUSB-1.
But I don’t have it and I’m not a FAE.
I have normal configuration, too.
Because I purchased another normal 9024D-M switch…
But your support is always good and kind…
Thank you…
Sure!
But deleted configuration include serial console baudrate and MAC address of MGMT ethernet port…IOI
2013/6/25 justinclift <socialmedia@mellanox.com mailto:socialmedia@mellanox.com >
**
Mellanox Interconnect Community
http://community.mellanox.com/?et=watches.email.thread
Mellanox (old Voltaire) ISR9024D-M recover flash area
reply from justinclift<Infrastructure & Networking - NVIDIA Developer Forums Infrastructure & Networking - NVIDIA Developer Forums >in
InfiniBand/VPI Switch Systems - View the full discussionhttp://community.mellanox.com/message/2057?et=watches.email.thread#2057
Did you ever find a way to read the existing EEPROM (not firmware) from a good 9024D-M?
Asking because I found this when logged into mine:
/usr/mst/bin
drwxrwxr-x 2 root root 1024 Nov 10 2008 .
drwxrwxr-x 3 root root 1024 Nov 10 2008 …
-rwxrwxr-x 1 root root 76948 Nov 10 2008 eburn
-rwxrwxr-x 1 root root 24673 Nov 10 2008 i2c
-rwxrwxr-x 1 root root 17519 Nov 10 2008 mread
-rwxrwxr-x 1 root root 25001 Nov 10 2008 mtserver
-rwxrwxr-x 1 root root 17547 Nov 10 2008 mwrite
EBURN - Command line EEPROM burning tool
Usage:
/usr/mst/bin/eburn <EEPROM_image_file> [options…]
Options:
-h - Print this message
-s - Silent mode - do not print progress
-v - Verify only, do not burn
-d <DEBUG_LEVEL> - Debug level 0, 1, 2. Default is 0 (none)
-sysguid <SYS_GUID> - Update system guid
-nodeguid <NODE_GUID> - Update node guid
-L - Lock i2c semaphor
-R - Route i2c open (used only for ISR9024 flavors)
-W - WriteProtect remove (used only for ISR9024-SM/DM)
-dev - Burn using dev
-lid - Burn using lid
-self_burning - Use this flag only for ISR9024 self burning
-LidA1 - Lid used for advanced test - this is must option
-ForceA1 - Halt advanced Test:
test - firmware higher than 1.0.0 could be burn only on A1 chip
check with vendorMAD the chip version , INI version, BoardType
That looks like it will burn an EEPROM image to a remote 9024D-M, in-band. Which I think would solve your problem.
Now, if we can just get a working EEPROM file…
(yes, I am very persistent)
I take this back. With further investigation, the “eburn” command seems to write firmware images to an EEPROM.
So, it’s the same thing we already know how to do. Not much use.
I,m also agree it…:)
