Mellanox (old Voltaire) ISR9024D-M recover flash area

Infrastructure & Networking Switches and Gateways InfiniBand/VPI Switch Systems
21

CAUTION!

IF YOU HAVE NOT CONSOLE CABLE, DON’T COMMIT FACTORY DEFAULT COMMAND on any

other IB switch.

Basically ISR9024D-M has a factory default configuration (192.168.1.2).

If you commit factory default command on CLI, you can connect default ip

address 192.168.1.2.

But another switches(Not ISR9024D-M) have default configuration DHCP for

management ethernet port.

If you want run the printenv command you must have a serial console cable.

I’m attache a normal ISR9024D-M boot log.

It was captured via console cable only.

You can run the printenv command in PPC-Boot console via serial console

cable.

.

.

.

PPCBoot 1.1.6 (Nov 16 2004 - 08:21:51)

CPU: IBM PowerPC 440 Rev. C

Board: Artesyn Technologies PM/PPC-440gp

Artesyn Monitor Version 1.5.0

VCO: 800 MHz

CPU: 400 MHz

PLB: 133 MHz

OPB: 66 MHz

EPB: 66 MHz

I2C: ready

DRAM: ECC Init …Done 128 MB

FLASH: 64 MB

Initializing board as Monarch…

Scanning for PCI devices…

Scanning PCI devices on bus 0

LOCALE VEND DEV REV BASE0 BASE1 BASE2 BASE3 BASE4 BASE5

22

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.

688×538 52.7 KB

Most big problem is can’t access via console.

Is there any solution to INITIALIZE U-BOOT AREA?

23

Hi inbusiness,

can you post here the text you see on your screen?

just connect console cable to your 9024D-M, power it up, let it boot until it stops, copy all the text and post here.

we’ll try to help.

24

Hmmm, have you done an nmap scan across all of the 192.168.0.0/16 subnet (on both eth and IB networks), just to see if it’s using a different IP address or something?

25

Hi!

Is there any good news…

Below is current view on my another 4036.

779×250 32.3 KB

There is a another question.

If I purchase another 9024D-M then can I update in-band firmware update with -lid number?

26

Hi,

one at a time

your 9024D-M - according to the printscreen you sent, it looks like the boot process is stopping somewhere at the very early stages.

when you get to the prompt => try to type the commands “boot” or “reset” and see what happens.

As for the 4036 switch: looks like it works.

you should be logging in as admin user (default password is 123456). check the version (“version show”)

27

I’m succeed In-Band Firmware update and my 4036 doesn’t report firmware problem anymore…

1138×432 66.1 KB

829×376 55.7 KB

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?

28

Hi!

I’m also tried with WinMFT via spark.exe

Below is result

this picture shows to me that only all boot sections were normal.

Another command “spark -d lid-7 swreset” was executed perfectly!

Below is another simulation command result.

Burnning simulation test to Primary image was successfull!

But I2C read error was occured again…

another option is -pe_i2c (also -se_i2c).

How can I find Primary, Secondary I2C address?

Is it must connect with your I2C cable and module?

29

Thank you so very much.

There is switch’s revision issue for firmware revision.

DDR switch require minimum 0.8.6.

I’ll try it…:)

2013/6/7 justinclift <socialmedia@mellanox.com mailto:socialmedia@mellanox.com >

**

Mellanox Interconnect Community

<Infrastructure & Networking - NVIDIA Developer Forums Infrastructure & Networking - NVIDIA Developer Forums >

Re: 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 discussion<Infrastructure & Networking - NVIDIA Developer Forums Infrastructure & Networking - NVIDIA Developer Forums >

30

Hmmm, I take that back. This is a dump of the configuration from my switch (upgraded to firmware 1.0.5):

ebay_voltaire_isr9024d-m_original-repository.new_firmware-1.0.5

There doesn’t seem to be anything in there related to com1. But, it’s a very long file (much longer than from firmware 0.8.6), and I could have just been looking for an incorrect string. So it still might help.

Out of curiosity, where are you running the “printenv” command? I can run it on the switch here and copy-n-paste the output if it’s helpful.

As a thought, when logged into the system via telnet there is a “factory-default” command in the config menu. It’s description is:

Switches back to factory default, and reboots the system.

Maybe that would work?

31

I was also tried that in-band firmware burnning and eburn, too. eburn command possible if you can login into your ISR9024 switch with root account. I think eburn is very helpful when if you failed firmware update and your switch can’t boot up normally…:)

I was mentioned about MTUSB-1 i2c connection device can debug and update firmware and EEPROM, too.

But that’s not a general user prupose device and firmware updating is very long time consuming operation that above 45 minutes…:(

Anyway whenever you tried help me, I appriciate for hour kinds and passions.

I pray you have a nice journey with infiniband.

See you again…

Thank you…:)

from my iPhone

      1. 16:49 justinclift <socialmedia@mellanox.com mailto:socialmedia@mellanox.com > 작성:

Mellanox Interconnect Community

Mellanox (old Voltaire) ISR9024D-M recover flash area

reply from justinclift in InfiniBand/VPI Switch Systems - View the full discussion

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.

Reply to this message by replying to this email, or go to the message on Mellanox Interconnect Community

Start a new discussion in InfiniBand/VPI Switch Systems by email or at Mellanox Interconnect Community

Following Mellanox (old Voltaire) ISR9024D-M recover flash area in these streams: Inbox

32

Below is the command lists on PPC-Boot mode (Not safe mode)…

PPCBoot 1.1.6 (Nov 16 2004 - 08:21:51)

CPU: IBM PowerPC 440 Rev. C

Board: Artesyn Technologies PM/PPC-440gp

Artesyn Monitor Version 1.5.0

VCO: 800 MHz

CPU: 400 MHz

PLB: 133 MHz

OPB: 66 MHz

EPB: 66 MHz

I2C: ready

DRAM: ECC Init …Done 512 MB

FLASH: 64 MB

Initializing board as Monarch…

Scanning for PCI devices…

Scanning PCI devices on bus 0

LOCALE VEND DEV REV BASE1 BASE2 BASE3 BASE4 BASE5

00,0d,0 10b5 9056 ba 80000000 b0800000 80200000 80400000 … …

In: serial

Out: serial

Err: serial

Net: EMAC0, EMAC1

BEDBUG:ready

Hit any key to stop autoboot: 0

=> clear

Unknown command ‘clear’ - try ‘help’

=> help

as - assemble memory

autoscr - run script from memory

base - print or set address offset

bdinfo - print Board Info structure

bootelf - Boot from an ELF image in memory

bootm - boot application image from memory

bootp - boot image via network using BootP/TFTP protocol

bootvx - Boot vxWorks from an ELF image

bootd - boot default, i.e., run ‘bootcmd’

break - set or clear a breakpoint

cmp - memory compare

coninfo - print console devices and informations

continue- continue from a breakpoint

cp - memory copy

crc32 - checksum calculation

date - get/set/reset date & time

dhcp - invoke DHCP client to obtain IP/boot params

ds - disassemble memory

echo - echo args to console

erase - erase FLASH memory

flinfo - print FLASH memory information

getdcr - Get an IBM PPC 4xx DCR’s value

go - start application at address ‘addr’

help - print online help

imd - i2c memory display

imm - i2c memory modify (auto-incrementing)

inm - memory modify (constant address)

imw - memory write (fill)

icrc32 - checksum calculation

iprobe - probe to discover valid I2C chip addresses

iloop - infinite loop on address range

isdram - print SDRAM configuration information

iminfo - print header information for application image

irqinfo - print information about IRQs

loadb - load binary file over serial line (kermit mode)

loads - load S-Record file over serial line

loop - infinite loop on address range

md - memory display

mm - memory modify (auto-incrementing)

mtest - simple RAM test

mw - memory write (fill)

next - single step execution, stepping over subroutines.

nm - memory modify (constant address)

printenv- print environment variables

protect - enable or disable FLASH write protection

rarpboot- boot image via network using RARP/TFTP protocol

rdump - Show registers.

reset - Perform RESET of the CPU

run - run commands in an environment variable

saveenv - save environment variables to persistent storage

setdcr - Set an IBM PPC 4xx DCR’s value

setenv - set environment variables

sleep - delay execution for some time

where - Print the running stack.

step - single step execution.

tftpboot- boot image via network using TFTP protocol

and env variables ipaddr and serverip

version - print monitor version

? - alias for ‘help’

pci_enum - Enumerates and displays PCI Bus Enumeration Info

pci_info - Displays PCI Bus Enumeration Info

prog_i2c - Programs default i2c bootstrap settings

moninit - Copies PPCBoot monitor into Soldered Flash

monship - Erases soldered flash, inits environment variables

initenv - Initializes Board Environment variables

um - destructive memory test

=>

33

inbusiness Infrastructure & Networking - NVIDIA Developer Forums - This URL might be useful (not sure). It’s the publicly published source repository for mstflint:

http://git.openfabrics.org/git?p=~orenk/mstflint.git http://git.openfabrics.org/git?p=~orenk/mstflint.git

It uses git, and the git history in there goes back many years, through to January 2005. It’s unfortunate there aren’t any tags in that repo (ie for each public release), but it could still be useful for working with older gear.

34

The firmware in the FTP location pointed out by yairi Infrastructure & Networking - NVIDIA Developer Forums worked for me.

I just logged into the switch (via ethernet cable) using telnet on 192.168.1.2, admin/123456, did the “enable” (password “voltaire”), then did the upgrade:

ISR9024D-2200# update software /home/jc/9024D-M/

Getting files from remote server…

pImage.ibswlrm 100% |*****************************| 22087 KB 00:00 ETA

Image Name: Linux Multiboot-Image 2.4.21-pmp

Created: Mon Nov 10 09:03:12 2008

Image Type: PowerPC Linux Multi-File Image (gzip compressed)

Data Size: 22617215 Bytes = 22087.12 kB = 21.57 MB

Load Address: 0x00000000

Entry Point: 0x00000000

Contents:

Image 0: 780745 Bytes = 762 kB = 0 MB

Image 1: 21836455 Bytes = 21324 kB = 20 MB

Erasing blocks: 173/173 (100%)

Writing data: 22087k/22087k (100%)

Verifying data: 22087k/22087k (100%)

Software upgrade completed

Upgrade flag turned on, repository merge will be performed on next reboot

ISR9024D-2200# Connection closed by foreign host.

That “/home/jc/9024D-M/” is the directory on my FTP server holding the software update file (“pImage.ibswlrm”).

Then the switch automatically reset and came back about 2 minutes later. Logging in again, it seems reasonably happy:

$ telnet 192.168.1.2

Trying 192.168.1.2…

Connected to 192.168.1.2.

Escape character is ‘^]’.

ISR9024D-2200 login: admin

Password:

Welcome to Voltaire Switch ISR9024D-2200

Welcome to initial switch configuration

Please change the default root password

Insert new (up to 8 characters) password: ******

Please retype new password: ******

OK

switch configuration done

The built-in test will start in 5 seconds - press enter to skip the tests

0

Checking for latest firmware revision… done

ALERT: One of the switch ASIC is out of revision

Please refer to proper documentation for firmware upgrade procedure.

Checking internal low memory requirement… done

Checking for degraded link width (1X)… done

Checking the status of system processes… done

Checking the HOQ Value… done

Checking for duplicate GUID (please wait)… done

ISR9024D-2200> version show

ISR 9024 version: 5.1.1

date: Nov 10 2008 10:57:18 AM

build Id:872

ISR9024D-2200>

I remember reading last night something about that ALERT message (“One of the switch ASIC is out of revision”). I think it can be ignored. Though, I’ll look into it later on, just to be sure.

Logging into the GridVision web UI on the switch, it has definitely changed, so that’s a good sign.

From the nearby box with spark on it, I queried the firmware again, expecting that to be upgraded too. It turns out that’s not automaticly part of the software upgrade:

$ sudo spark -d /dev/mst/SW_MT23089_0008f10400412200_lid-0x0002 q

Query:

FW Version: 0.8.6

Node GUID: 0x0008f10400412200

System Image GUID: 0x0008f10400412201

Node Description: ISR9024D-M Voltaire

Board Serial Number: NO_BSN

PSID: VLT1110030900

It turns out the software upgrade copies the newer firmware to the switch, but doesn’t automatically burn it. The “update firmware” command worked when run on the switch (via telnet):

update firmware chassis

Local system <ISR9024 DDR (managed)>

Local System_GUID 0008f10400412201, Node_GUID 0008f10400412200

Upgrade firmware from 00.08.06 to 01.00.00

eburn: try to lock i2c semaphor.

eburn: lock of i2c semaphor succeed.

eburn: write protect open - succeed

eburn: open route to i2c device succeed

FirmwareImage = firmware.ISR9024_DM.img

ImageFWVersion = 01.00.00

ChipSystemGUID = 0008f10400412201

ChipNodeGUID = 0008f10400412200

ImagePSID = VLT1110031011

ImageBoardType = 111

ChipHWDEV = 0x1a1

ChipFWVersion = 00.08.06

ChipPSID = VLT1110030900

ChipBoardType = 111

Invalidate PBR…0x56

Verifying PBR…0x56 Valid

Verifying PBR…0x52 Valid

Burning …

BURN - Verifying …

VERIFY - 100%

Verifying PBR…0x56 Valid

Verifying PBR…0x52 Valid

eburn: write protect close

Firmware upgrade completed

Restart switch to apply new firmware

ISR9024D-2200# reload

Reboot the system? [yes|no] yes

ISR9024D-2200# Hangup

$ sudo spark -d /dev/mst/SW_MT23089_0008f10400412200_lid-0x0002 q

Query:

FW Version: 1.0.0

Node GUID: 0x0008f10400412200

System Image GUID: 0x0008f10400412201

Node Description: ISR9024D-M Voltaire

Board Serial Number: NO_BSN

PSID: VLT1110031011

I think all that’s needed now, is to manually update the software to version 1.5.

Hopefully some of this (long) post is useful.

35

This might be helpful too. It’s the switch settings for the ISR9024D-M, as exported using the GridVision Device Manager GUI:

ebay_voltaire_isr9024d-m_original-repository.new

The settings were exported like this:

Screenshot of ISR9024 config backup/restore GUI dialog

36

just out of curiasity, why are you looking to change the boudrate? what’s wrong with the default?

37

Thank you so very much.

There is switch’s revision issue for firmware revision.

DDR switch require minimum 0.8.6.

I’ll try it…:)

2013/6/7 justinclift <socialmedia@mellanox.com mailto:socialmedia@mellanox.com >

**

Mellanox Interconnect Community

<Infrastructure & Networking - NVIDIA Developer Forums Infrastructure & Networking - NVIDIA Developer Forums >

Re: 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 discussion<Infrastructure & Networking - NVIDIA Developer Forums Infrastructure & Networking - NVIDIA Developer Forums >

38

Good timing, I was just doing this anyway.

Try this out:

ebay_voltaire_isr9024d-m_original-firmware.img

I used slightly different instructions to extract it:

mst start

Starting MST (Mellanox Software Tools) driver set

Loading MST PCI module - Success

Loading MST PCI configuration module - Success

Create devices

mst ib add --add-non-mlnx

-I- Discovering the fabric - Running: ibdiagnet -skip all

-I- Added 4 in-band devices

mst status |grep SW_

/dev/mst/SW_MT23089_0008f10400412200_lid-0x0002

spark -d /dev/mst/SW_MT23089_0008f10400412200_lid-0x0002 q

Query:

FW Version: 0.8.6

Node GUID: 0x0008f10400412200

System Image GUID: 0x0008f10400412201

Node Description: ISR9024D-M Voltaire

Board Serial Number: NO_BSN

PSID: VLT1110030900

spark -d /dev/mst/SW_MT23089_0008f10400412200_lid-0x0002 v

Primary Image:

DEV OFFSET SIZE TYPE STATUS

56 000000 000028 PLL OK

56 000028 003c40 BOOT OK

56 003c68 0000c8 SPECIAL OK

56 003d30 0003c4 IWI OK

56 0040f4 000018 HBI OK

56 00410c 000028 NBI OK

56 004134 000028 NBI OK

56 00415c 000020 NBI OK

56 00417c 000020 NBI OK

56 00419c 000f00 RMW OK

56 00509c 000010 JUMP OK

56 0050ac 01ab48 CODE OK

57 00fbf4 00000c LAST OK

Secondary Image:

DEV OFFSET SIZE TYPE STATUS

52 000000 000028 PLL OK

52 000028 003c40 BOOT OK

52 003c68 0000c8 SPECIAL OK

52 003d30 0003c4 IWI OK

52 0040f4 000018 HBI OK

52 00410c 000028 NBI OK

52 004134 000028 NBI OK

52 00415c 000020 NBI OK

52 00417c 000020 NBI OK

52 00419c 000f00 RMW OK

52 00509c 000010 JUMP OK

52 0050ac 01ab48 CODE OK

53 00fbf4 00000c LAST OK

spark -d /dev/mst/SW_MT23089_0008f10400412200_lid-0x0002 ri ebay_voltaire_isr9024d-m_original-firmware.img

  • Reading primary image - OK

  • Reading secondary image - OK

  • Writing image file …

Seems all good here.

(note - updated with reuploaded firmware (now with .img file extension))

39

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.

40

There is my mis-typing point.

In: serial

Out: serial

Err: serial

Net: EMAC0, EMAC1

BEDBUG:ready

Hit any key to stop autoboot: 0 → *At this point - you can enter

PPC-Console mode*

booting secondary, press ^c to abort —> *It’s a leading to boot

from primary image*

booting…

  1. Booting image at d0a00000 …

Image Name: Linux Multiboot-Image 2.4.21-pmp

Created: 2006-08-24 11:41:03 UTC

Image Type: PowerPC Linux Multi-File Image (gzip compressed)

Data Size: 20363540 Bytes = 19886 kB = 19 MB

Load Address: 00000000

Entry Point: 00000000

Contents:

Image 0: 780651 Bytes = 762 kB = 0 MB

.

2013/6/7 최재훈 <inbusiness.jhchoi@gmail.com mailto:inbusiness.jhchoi@gmail.com >

CAUTION!

IF YOU HAVE NOT CONSOLE CABLE, DON’T COMMIT FACTORY DEFAULT COMMAND on any

other IB switch.

Basically ISR9024D-M has a factory default configuration (192.168.1.2).

If you commit factory default command on CLI, you can connect default ip

address 192.168.1.2.

But another switches(Not ISR9024D-M) have default configuration DHCP for

management ethernet port.

If you want run the printenv command you must have a serial console cable.

I’m attache a normal ISR9024D-M boot log.

It was captured via console cable only.

You can run the printenv command in PPC-Boot console via serial console

cable.

.

.

.

PPCBoot 1.1.6 (Nov 16 2004 - 08:21:51)

CPU: IBM PowerPC 440 Rev. C

Board: Artesyn Technologies PM/PPC-440gp

Artesyn Monitor Version 1.5.0

VCO: 800 MHz

CPU: 400 MHz

PLB: 133 MHz

OPB: 66 MHz

EPB: 66 MHz

I2C: ready

DRAM: ECC Init …Done 128 MB

FLASH: 64 MB

Initializing board as Monarch…

Scanning for PCI devices…

Scanning PCI devices on bus 0

LOCALE VEND DEV REV BASE0 BASE1 BASE2 BASE3 BASE4 BASE5