MD3000i Firmware

Hello MRBNET,

What is your current version of firmware and what version are you trying to upgrade to, as you didn’t list that in your original post.  Also when you did the firmware upgrade was all I/O stopped and did you happen to pull a support bundle from the unit before you started the firmware upgrade?  Last were there any errors on the system prior to starting the upgrade?

Please let us know if you have any other questions.

Hello Sam,

I don't have any info about the failed update. This is getting re-provisioned so there is no current config. There is a copy of a profile printed indicating there were 2 controllers in this enclosure at one point. It looks like this controller is in a slave mode looking for the primary controller. Is there any way to reset it from the console?

This should be the current version of the controller:

Current configuration                                      

           Firmware version:         07.35.39.64                    

              Appware version:       07.35.39.64                    

              Bootware version:      07.35.39.64                    

           NVSRAM version:           N1532-735890-005

Hello MRBNET,

With the configuration & error stating that it can see the slave controller and not the primary controller what you can do is to swap the controllers and put the slave(right side of the unit if looking at the MD3000i from the back) with the primary controller and try to see if the system will come up with just the primary controller (was slave controller). If the MD3000i comes up with the primary controller in then add in the secondary controller and check the serial output to ensure that it comes up.

Now if you wanted to just try & reset the array here is the way you would do that.

1. Startup a terminal emulation program like putty, teraterm, minicom or hyperterminal using these terminal settings (115200-8-n-1).

2. Send a from the terminal shell. This is accomplished by within HyperTerminal or Putty, use from within Minicom on Linux systems.

3. When prompted for input within 5 seconds, press for the service interface menu. Also the S needs to be caps otherwise will not work

4. The user will then be prompted for a password. The Password is: supportDell

5. The menu options available are.

1) Display IP Configuration

2) Change IP Configuration

3) Reset Storage Array (SYMbol) Password

Q) Quit Menu

Please let us know if you have any other questions.

I cannot seem to get into the service interface menu. The prompt comes up to press "S" but nothing happens when I press that. The line returns like it is sending the character to the terminal.

It will just continue on to the following.

03/21/14-15:04:19 (GMT) (tRAID): NOTE:  QLProcessSystemError: Restart RISC

03/21/14-15:04:19 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE failed.  Stat f000

03/21/14-15:04:19 (GMT) (tRAID): NOTE:  QLRebootTimer: Status after Get FW State 4543

03/21/14-15:04:19 (GMT) (tRAID): NOTE:  QLRebootTimer: QLGetFwState failed

03/21/14-15:04:20 (GMT) (tRAID): NOTE:  QLStartFw: Downloading Driver's FW image 03.00.01.47 from 03157520 4c0c8 bytes , result 0

03/21/14-15:04:47 (GMT) (tRAID): WARN:  QLMailboxCommand: Cmd = 0069, completion timeout

03/21/14-15:04:47 (GMT) (tRAID): WARN:  QLMailboxCommand: command completion timeout, cmd = 0x69

03/21/14-15:04:48 (GMT) (tRAID): NOTE:  Qlogic coredump file written to '6B53VK1:/tmp/QLogic_Coredump_port_0_6B53VK1',rc 204E50, expected 204E50

03/21/14-15:04:48 (GMT) (tRAID): WARN:  Qlogic coredump file write failed.fclose returned -1

03/21/14-15:04:48 (GMT) (tRAID): NOTE:  QLProcessSystemError: Restart RISC

03/21/14-15:04:48 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE failed.  Stat f000

03/21/14-15:04:48 (GMT) (tRAID): NOTE:  QLRebootTimer: Status after Get FW State 4543

03/21/14-15:04:48 (GMT) (tRAID): NOTE:  QLRebootTimer: QLGetFwState failed

03/21/14-15:04:50 (GMT) (tRAID): NOTE:  QLStartFw: Downloading Driver's FW image 03.00.01.47 from 03157520 4c0c8 bytes , result 0

It restarts after a couple tries.

Hello MRBNET,

Since you switched the controllers and still getting the same error on the primary slot of the MD3000i then it looks like the midplane of the MD 3000i is what is causing the issue & if the system was under warranty then we would replace the midplane.  The output that you posted the controller is trying to start but it can’t get the correct state from the MD3000i enclosure & midplane to move to the next step in the boot up.  

Please let us know if you have any other questions.

Hi,

I too have had a firmware update failure when trying to upgrade our MD3000i controller from v6 to the latest v7 firmware.  I followed the instructions in the readme file that came with the firmware files.  I ran the Cross Generation Upgrade Utility program.  The firmware was uploaded ok, but during the Activating stage, the MD3000i controller became unresponsive.  Now I cannot connect to it at all.  I have tried rebooting the unit and I tried swapping the primary controller with the slave, but still the same unresponsive issue.  I can ping the slave IP address but no other network lights are on and hence I cannot ping any other IP address.  Can anyone help me get this unit back working again?

I need to do the same thing.  Can someone please PM with the login and password for VxWorks.  Tech Support can't / wont give it out and I have not been as lucky to find it online.