Topic
  • 17 replies
  • Latest Post - ‏2016-03-13T21:42:47Z by john16
SystemAdmin
SystemAdmin
4779 Posts

Pinned topic DS4700 Firmware Downgrade from the 07.15.10.01 to the 06.60.17.00 version

‏2008-11-22T10:37:56Z |
Hi,

I had an issue migrating two EXP710s with their existing arrays from a DS4400 with 06.12.56.00 firmware version to a new DS4700 with 07.15.10.01 firmware version as described in this previous thread.

So, now, I have to downgrade the DS4700 firmware version from 07.15.10.01 to the 06.60.17.00 version to make the migration work.

This downgrade operation cannot be done neither by the Storage Manager nor by the Firmware Upgrade Tool as Mr rscotka said in his post (see the link to the previous thread).

Could you please provide me some information about the downgrade procedure using the serial port of the DS4700?
I guess that I have to downgrade the NVSRAM version too as it is linked to the firmware version. Is it possible and how?

Best regards,

Meryem Belhadj
System Engineer
Updated on 2012-05-17T02:09:55Z at 2012-05-17T02:09:55Z by csu007
  • Samostrelov_Aleksey
    Samostrelov_Aleksey
    4 Posts

    Re: DS4700 Firmware Downgrade from the 07.15.10.01 to the 06.60.17.00 version

    ‏2008-11-26T12:35:54Z  
    Try to use smcli first.

    In Windows command prompt enter:
    C:\Program Files\IBM_DS4000\client>smcli controller_A_IP controller_B_IP

    When this utility get connected to storage system enter:
    download storagesubsystem firmware, NVSRAM file="C:\FW_DS4700_07360800.dlp","C:\N1814D47R1036V12.dlp" activatenow=TRUE;

    C:\FW_DS4700_07360800.dlp - path to firmware file
    C:\N1814D47R1036V12.dlp - path to NVSRAM file

    This command will flash firmware and NVSRAM.
    Note that this command works even if storage system not in optimal state! SM client or Firmware upgrade tool doesn't support it.
    For smicli usage refer to IBM System Storage DS4000 and Storage Manager V10.10
    http://www.redbooks.ibm.com/redbooks/pdfs/sg247010.pdf
  • SystemAdmin
    SystemAdmin
    4779 Posts

    Re: DS4700 Firmware Downgrade from the 07.15.10.01 to the 06.60.17.00 versi

    ‏2008-11-26T18:41:37Z  
    Meryem,

    Just in case you run into difficulties with SMCli:

    I'm posting the instructions I got from RAID Support at LSI (the makers of the DS4000/5000
    product line). None of this will help you if you don't have the DB9 to mini-DIN adapter
    required to connect to the DS4700 serial port. You'll need Hyperterminal or other
    capable terminal application with Xmodem file transfer capabilities.
    ....................

    Below are the steps to download through the shell, and as per my earlier note, these steps MUST be performed via SERIAL connection. the steps of which are outlined in the attached document

    -> M

    value = 0 = 0x0

    ->

    NOTICE: The BOOT OPERATIONS MENU has been invoked too late for

    proper operation of some activities, including Isolation Diagnostics.

    You may wish to restart this controller again and press Control-B

    IMMEDIATELY after seeing the start-up indicator ("-=<###>=-").

    BOOT OPERATIONS MENU

    1) Perform Isolation Diagnostics 10) Serial Interface Mode Menu

    2) Download Permanent File 11) Display Hardware Configuration

    3) Reserved 12) Change Hardware Configuration Menu

    4) Dump NVSRAM Group 13) Development Options Menu

    5) Patch NVSRAM Group 14) Display Memory Error Log

    6) Set Real Time Clock 15) Manufacturing Setup Menu

    7) Display Board Configuration R) Restart Controller

    8) Special Services Menu Q) Quit Menu

    9) Display Exception Message

    -> 2

    At this point you will see an ASCII character on the screen over and over again, you will need to go to the file download option in your terminal program and download the NVSRAM, and after that the controller firmware. This may take some time, and it is recommended that you perform this action before the maintenance window, (since it specifically involves the ds4800 only)

    After it is complete you will use exit and perform the same steps on the alternate controller. (with two computers attached serially this could be done in tandem, by connections separately to each controller)

    after the download is complete perform sysWipe at the prompt
    Attachment (from above):
    Steps to gain Serial Shell Access to Controller:

    1. Connect a PC, running a terminal program, to the RS-232 port on the back of the controller module, using the serial cable supplied with the array (null-modem, not straight through).

    2. Confirm the terminal settings:

    -Set the com-port to the port configured on the PC

    -9600 baud (19200 for 2772 controller)

    -8 bits

    -no parity

    -1 stop bit

    -xon-xoff for flow control (may need to be changed depending on terminal program)

    3. Issue a BREAK sequence (Press CTRL-BREAK for Hyperterm/WINterm) until prompted for either "escape for shell" or "space bar to set baud rate."

    4. If baud rate

    -is not 9600, set it to that number. Issue a BREAK sequence until prompted "escape for shell." Press Escape.

    .......................................
    I would recommend that you go for a higher connection rate as a 9600 baud transfer will
    be particularly slow. It could take around 45 minutes per controller if you
    connect at 115,200 and maybe slower if you're using a laptop that uses a USB to Serial
    adapter. (The mention of a cable being supplied with the unit is erroneous though the
    small adapter for the serial port should have been shipped with it. Any null modem
    cable would be ok...if you have McData switches, they DO come with the right cable.
    Brocade's supplied serial cable is a straight cable so will not work without a null
    modem adapter.)

    Also, the sysWipe command recommended at the end will pretty much destroy any array information present on the system drives if they're connected. Be careful.....as in CAREFUL!

    Your best probability for success is to open a case with IBM Support and have it
    escalated. I highly recommend it.
  • SystemAdmin
    SystemAdmin
    4779 Posts

    Re: DS4700 Firmware Downgrade from the 07.15.10.01 to the 06.60.17.00 versi

    ‏2008-11-28T10:34:29Z  
    Meryem,

    Just in case you run into difficulties with SMCli:

    I'm posting the instructions I got from RAID Support at LSI (the makers of the DS4000/5000
    product line). None of this will help you if you don't have the DB9 to mini-DIN adapter
    required to connect to the DS4700 serial port. You'll need Hyperterminal or other
    capable terminal application with Xmodem file transfer capabilities.
    ....................

    Below are the steps to download through the shell, and as per my earlier note, these steps MUST be performed via SERIAL connection. the steps of which are outlined in the attached document

    -> M

    value = 0 = 0x0

    ->

    NOTICE: The BOOT OPERATIONS MENU has been invoked too late for

    proper operation of some activities, including Isolation Diagnostics.

    You may wish to restart this controller again and press Control-B

    IMMEDIATELY after seeing the start-up indicator ("-=<###>=-").

    BOOT OPERATIONS MENU

    1) Perform Isolation Diagnostics 10) Serial Interface Mode Menu

    2) Download Permanent File 11) Display Hardware Configuration

    3) Reserved 12) Change Hardware Configuration Menu

    4) Dump NVSRAM Group 13) Development Options Menu

    5) Patch NVSRAM Group 14) Display Memory Error Log

    6) Set Real Time Clock 15) Manufacturing Setup Menu

    7) Display Board Configuration R) Restart Controller

    8) Special Services Menu Q) Quit Menu

    9) Display Exception Message

    -> 2

    At this point you will see an ASCII character on the screen over and over again, you will need to go to the file download option in your terminal program and download the NVSRAM, and after that the controller firmware. This may take some time, and it is recommended that you perform this action before the maintenance window, (since it specifically involves the ds4800 only)

    After it is complete you will use exit and perform the same steps on the alternate controller. (with two computers attached serially this could be done in tandem, by connections separately to each controller)

    after the download is complete perform sysWipe at the prompt
    Attachment (from above):
    Steps to gain Serial Shell Access to Controller:

    1. Connect a PC, running a terminal program, to the RS-232 port on the back of the controller module, using the serial cable supplied with the array (null-modem, not straight through).

    2. Confirm the terminal settings:

    -Set the com-port to the port configured on the PC

    -9600 baud (19200 for 2772 controller)

    -8 bits

    -no parity

    -1 stop bit

    -xon-xoff for flow control (may need to be changed depending on terminal program)

    3. Issue a BREAK sequence (Press CTRL-BREAK for Hyperterm/WINterm) until prompted for either "escape for shell" or "space bar to set baud rate."

    4. If baud rate

    -is not 9600, set it to that number. Issue a BREAK sequence until prompted "escape for shell." Press Escape.

    .......................................
    I would recommend that you go for a higher connection rate as a 9600 baud transfer will
    be particularly slow. It could take around 45 minutes per controller if you
    connect at 115,200 and maybe slower if you're using a laptop that uses a USB to Serial
    adapter. (The mention of a cable being supplied with the unit is erroneous though the
    small adapter for the serial port should have been shipped with it. Any null modem
    cable would be ok...if you have McData switches, they DO come with the right cable.
    Brocade's supplied serial cable is a straight cable so will not work without a null
    modem adapter.)

    Also, the sysWipe command recommended at the end will pretty much destroy any array information present on the system drives if they're connected. Be careful.....as in CAREFUL!

    Your best probability for success is to open a case with IBM Support and have it
    escalated. I highly recommend it.
    Hi,

    I thank you very much for your support.
    We downgraded the firmware level of the DS4700 to the 6.60 version using the serial port procedure that the IBM support sent us (the same you posted here) and it worked.

    Best regards!

    Meryem Belhadj
    System Engineer
  • SystemAdmin
    SystemAdmin
    4779 Posts

    Re: DS4700 Firmware Downgrade from the 07.15.10.01 to the 06.60.17.00 versi

    ‏2010-01-13T13:23:23Z  
    Try to use smcli first.

    In Windows command prompt enter:
    C:\Program Files\IBM_DS4000\client>smcli controller_A_IP controller_B_IP

    When this utility get connected to storage system enter:
    download storagesubsystem firmware, NVSRAM file="C:\FW_DS4700_07360800.dlp","C:\N1814D47R1036V12.dlp" activatenow=TRUE;

    C:\FW_DS4700_07360800.dlp - path to firmware file
    C:\N1814D47R1036V12.dlp - path to NVSRAM file

    This command will flash firmware and NVSRAM.
    Note that this command works even if storage system not in optimal state! SM client or Firmware upgrade tool doesn't support it.
    For smicli usage refer to IBM System Storage DS4000 and Storage Manager V10.10
    http://www.redbooks.ibm.com/redbooks/pdfs/sg247010.pdf
    Hi,

    Can i use the same procedure for downgrading DS4800 firmware from 07.60.28.00 to 07.50

    Or please suggest me a downgrade procedure for DS4800
  • SystemAdmin
    SystemAdmin
    4779 Posts

    Re: DS4700 Firmware Downgrade from the 07.15.10.01 to the 06.60.17.00 version

    ‏2011-04-13T10:29:22Z  
    Hi
    I had a similar case

    But in my case I wanted to add new drives in my EXP810
    These drive contained no data. :-)

    The disks had been inserted into a system running FW 7.xx earlier before and I had an unsupported DACSTORE.

    I got this commands from IBM
    The commands to clear the dacstore of the affected drives
    The devnum is taken from datacollection.

    isp cfgWipeEnclosure,devnum

    Execute command, drive in slot should show some activity with the LEDs, after that reseat the drive.
    Continue with the remaining drives one at a time.
    Validate via GUI.
  • Stan1234
    Stan1234
    1 Post

    Re: DS4700 Firmware Downgrade from the 07.15.10.01 to the 06.60.17.00 versi

    ‏2012-03-12T14:46:14Z  
    Meryem,

    Just in case you run into difficulties with SMCli:

    I'm posting the instructions I got from RAID Support at LSI (the makers of the DS4000/5000
    product line). None of this will help you if you don't have the DB9 to mini-DIN adapter
    required to connect to the DS4700 serial port. You'll need Hyperterminal or other
    capable terminal application with Xmodem file transfer capabilities.
    ....................

    Below are the steps to download through the shell, and as per my earlier note, these steps MUST be performed via SERIAL connection. the steps of which are outlined in the attached document

    -> M

    value = 0 = 0x0

    ->

    NOTICE: The BOOT OPERATIONS MENU has been invoked too late for

    proper operation of some activities, including Isolation Diagnostics.

    You may wish to restart this controller again and press Control-B

    IMMEDIATELY after seeing the start-up indicator ("-=<###>=-").

    BOOT OPERATIONS MENU

    1) Perform Isolation Diagnostics 10) Serial Interface Mode Menu

    2) Download Permanent File 11) Display Hardware Configuration

    3) Reserved 12) Change Hardware Configuration Menu

    4) Dump NVSRAM Group 13) Development Options Menu

    5) Patch NVSRAM Group 14) Display Memory Error Log

    6) Set Real Time Clock 15) Manufacturing Setup Menu

    7) Display Board Configuration R) Restart Controller

    8) Special Services Menu Q) Quit Menu

    9) Display Exception Message

    -> 2

    At this point you will see an ASCII character on the screen over and over again, you will need to go to the file download option in your terminal program and download the NVSRAM, and after that the controller firmware. This may take some time, and it is recommended that you perform this action before the maintenance window, (since it specifically involves the ds4800 only)

    After it is complete you will use exit and perform the same steps on the alternate controller. (with two computers attached serially this could be done in tandem, by connections separately to each controller)

    after the download is complete perform sysWipe at the prompt
    Attachment (from above):
    Steps to gain Serial Shell Access to Controller:

    1. Connect a PC, running a terminal program, to the RS-232 port on the back of the controller module, using the serial cable supplied with the array (null-modem, not straight through).

    2. Confirm the terminal settings:

    -Set the com-port to the port configured on the PC

    -9600 baud (19200 for 2772 controller)

    -8 bits

    -no parity

    -1 stop bit

    -xon-xoff for flow control (may need to be changed depending on terminal program)

    3. Issue a BREAK sequence (Press CTRL-BREAK for Hyperterm/WINterm) until prompted for either "escape for shell" or "space bar to set baud rate."

    4. If baud rate

    -is not 9600, set it to that number. Issue a BREAK sequence until prompted "escape for shell." Press Escape.

    .......................................
    I would recommend that you go for a higher connection rate as a 9600 baud transfer will
    be particularly slow. It could take around 45 minutes per controller if you
    connect at 115,200 and maybe slower if you're using a laptop that uses a USB to Serial
    adapter. (The mention of a cable being supplied with the unit is erroneous though the
    small adapter for the serial port should have been shipped with it. Any null modem
    cable would be ok...if you have McData switches, they DO come with the right cable.
    Brocade's supplied serial cable is a straight cable so will not work without a null
    modem adapter.)

    Also, the sysWipe command recommended at the end will pretty much destroy any array information present on the system drives if they're connected. Be careful.....as in CAREFUL!

    Your best probability for success is to open a case with IBM Support and have it
    escalated. I highly recommend it.
    Hello,

    I was performing serial port Firmware Upgrade throug M menu but had power down during upload.

    After restart "M" menu doesn't work at all ( nothing happens ) and on serial port you get following:
    "
    ->
    -> ic
    ˙ˇÔé_^Ć^éĺCBŹ¸jĘ+˙
    Press within 5 seconds: for Service Interface, <BREAK> for baud rate ->
    Send <BREAK> for Service Interface or baud rate change
    Undefined symbol: dbgShell (binding 1 type 0)
    Undefined symbol: sasExpanderFreeImages (binding 1 type 0)
    Undefined symbol: __ctype_toupper (binding 1 type 0)
    Undefined symbol: bcmPciCfgRmw (binding 1 type 0)
    Undefined symbol: loadIocFwFromFlash (binding 1 type 0)
    Undefined symbol: bcmGetParentBridgeIndexByBus (binding 1 type 0)
    Undefined symbol: sasExpanderLoadFwImages (binding 1 type 0)
    ld error: Module contains undefined symbol(s) and may be unusable.
    Undefin*** Expired
    lexChoices (binding 1 type 0)
    Undefined symbol: _ZNSt9exceptionD2Ev (binding 1 type 0)
    Undefined symbol: dqSave (binding 1 type 0)
    Undefined symbol: netCfgCheckIfNameValid (binding 1 type 0)
    Undefined symbol: netCfgGetIpv6AddrType (binding 1 type 0)
    Undefined symbol: netCfgCheckNeedsAttnCode (binding 1 type 0)
    Undefined symbol: _ZNKSt12_String_base5_XranEv (binding 1 type 0)
    Undefined symbol: __cxa_call_unexpected (binding 1 type 0)
    Undefined symbol: netCfgGetSpeedDuplex (binding 1 type 0)
    Undefined symbol: _ZNKSt12_String_base5_XlenEv (binding 1 type 0)
    Undefined symbol: parseIPv6AddrStringPublic (binding 1 type 0)
    Undefined symbol: menuExecute (binding 1 type 0)
    Undefined symbol: dqRelabelQueue (binding 1 type 0)
    Undefined symbol: bcmWriteBuffer (binding 1 type 0)
    Undefined symbol: stringEncrypt (binding 1 type 0)
    Undefined symbol: bcmDisplayLEDSequenceClear (binding 1 type 0)
    Undefined symbol: _ZNKSt9exception4whatEv (binding 1 type 0)
    Undefined symbol: __ctype_toupper (binding 1 type 0)
    Undefined symbol: _ZTVN10__cxxabiv119__pointer_type_infoE (binding 1 type 0)
    Undefined symbol: _ZTVN10__cxxabiv120__si_class_type_infoE (binding 1 type 0)
    Undefined symbol: makeIPv6AddrString (binding 1 type 0)
    Undefined symbol: _Unwind_SjLj_Register (binding 1 type 0)
    Undefined symbol: __cxa_end_catch (binding 1 type 0)
    Undefined symbol: _ZTISt9exception (binding 1 type 0)
    Undefined symbol: bcmDisplayLEDPatternSequence (binding 1 type 0)
    Undefined symbol: netCfgGetInfoCurrent (binding 1 type 0)
    Undefined symbol: __cxa_pure_virtual (binding 1 type 0)
    Undefined symbol: dqEnableOtherLevelForAllWriters (binding 1 type 0)
    Undefined symbol: in6addr_loopback (binding 1 type 0)
    Undefined symbol: bcmGetHostBoardModelNameFromBoardId (binding 1 type 0)
    Undefined symbol: sxInteractiveSessionStart (binding 1 type 0)
    Undefined symbol: _Unwind_SjLj_Resume (binding 1 type 0)
    Undefined symbol: netCfgGetInfoStored (binding 1 type 0)
    Undefined symbol: dqstoreSavedList (binding 1 type 0)
    Undefined symbol: _ZNSt8ios_base4InitC1Ev (binding 1 type 0)
    Undefined symbol: _ZTVSt9exception (binding 1 type 0)
    Undefined symbol: _ZTVN10__cxxabiv117__class_type_infoE (binding 1 type 0)
    Undefined symbol: __cxa_throw (binding 1 type 0)
    Undefined symbol: dqCopyQueue (binding 1 type 0)
    Undefined symbol: ZdlPvS (binding 1 type 0)
    Undefined symbol: netCfgCheckNetworkInitialized (binding 1 type 0)
    Undefined symbol: __cxa_bad_cast (binding 1 type 0)
    Undefined symbol: _ZTVN10__cxxabiv121__vmi_class_type_infoE (binding 1 type 0)
    Undefined symbol: netCfgGetIpAssignInfo (binding 1 type 0)
    Undefined symbol: bcmReadBuffer (binding 1 type 0)
    Undefined symbol: netCfgSetSpeedDuplex (binding 1 type 0)
    Undefined symbol: _ZNSt8ios_base4InitD1Ev (binding 1 type 0)
    Undefined symbol: __cxa_begin_catch (binding 1 type 0)
    Undefined symbol: __cxa_allocate_exception (binding 1 type 0)
    Undefined symbol: __gxx_personality_sj0 (binding 1 type 0)
    Undefined symbol: _ZNSt9exceptionD1Ev (binding 1 type 0)
    Undefined symbol: _vkiRebootHookAdd (binding 1 type 0)
    Undefined symbol: sysMemMtrrRegionModifyWCToWB (binding 1 type 0)
    Undefined symbol: _vkiGetString (binding 1 type 0)
    Undefined symbol: __cxa_bad_typeid (binding 1 type 0)
    Undefined symbol: netCfgGetScopeId (binding 1 type 0)
    Undefined symbol: dqGetPercentFull (binding 1 type 0)
    Undefined symbol: dqwSetOtherLevel (binding 1 type 0)
    Undefined symbol: sysMemMtrrRegionModifyWBToWC (binding 1 type 0)
    ld error: Module contains undefined symbol(s) and may be unusable.

    PSV Initialization
    ==================
    ERROR 9F.01: Flash file "Diagnostics" is corrupt or has unresolved references
    ERROR 9F.01: Flash file "RAID" is corrupt or has unresolved references
    Kernel initialization complete

    Network Ready
    fei0: LinkUp event
    fei1: LinkDown event

    ->
    -> ic
    7Ti_^F^ieCB,8jJ
    Press within 5 seconds: for Service Interface, <BREAK> for baud rate ->
    Send <BREAK> for Service Interface or baud rate change
    Undefined symbol: dbgShell (binding 1 type 0)
    Undefined symbol: sasExpanderFreeImages (binding 1 type 0)
    Undefined symbol: __ctype_toupper (binding 1 type 0)
    Undefined symbol: bcmPciCfgRmw (binding 1 type 0)
    Undefined symbol: loadIocFwFromFlash (binding 1 typ"

    Actually you can log on to shell, in there listing tasks gives :
    "
    -> i

    NAME ENTRY TID PRI STATUS PC SP ERRNO DELAY

    ------------
    ---
    --------
    -------
    tExcTask excTask 1fffece4 0 PEND 5d76f3 1fffec2c 30065 0
    tLogTask logTask 1fffc344 0 PEND 5d76f3 1fffc27c 0 0
    tShell shell 1ffb4b44 1 READY 5fd290 1ffb4778 1c0001 0
    tVkiLog vkiLogTask 1ff78b00 4 PEND 53a73b 1ff78a24 0 0
    tNetTask netTask 1ffbe028 50 PEND 53a73b 1ffbdfbc 0 0
    tDhcpcState5768b0 1ffb8b48 56 PEND 53a73b 1ffb8aac 0 0
    tDhcpcReadTdhcpcRead 1ffb759c 56 PEND 53a73b 1ffb73a0 3d0002 0
    tSubSys subSysIntHan 1ff2e4e8 100 PEND 53a73b 1ff2e48c 0 0
    tNetReset netUtilTask 1ff4d50 100 PEND 5d76f3 1ff4ca8 30065 0
    tVkiIdle vkiIdle 1ff8c5b4 250 READY 4bcf70 1ff8c4fc 0 0
    "

    Not possible to get in by DS4000 Storage manager.

    Any idea what we can do it this case ?

    Stan
  • mmaliakas
    mmaliakas
    11 Posts

    Re: DS4700 Firmware Downgrade from the 07.15.10.01 to the 06.60.17.00 version

    ‏2012-03-21T13:43:09Z  
    Hi
    I had a similar case

    But in my case I wanted to add new drives in my EXP810
    These drive contained no data. :-)

    The disks had been inserted into a system running FW 7.xx earlier before and I had an unsupported DACSTORE.

    I got this commands from IBM
    The commands to clear the dacstore of the affected drives
    The devnum is taken from datacollection.

    isp cfgWipeEnclosure,devnum

    Execute command, drive in slot should show some activity with the LEDs, after that reseat the drive.
    Continue with the remaining drives one at a time.
    Validate via GUI.
    hello

    i need to clear the dacstore of a specific drive. how can i generate the datacollection to find the appropriate drive devnum?
    thanks in advanced
  • mmaliakas
    mmaliakas
    11 Posts

    Re: DS4700 Firmware Downgrade from the 07.15.10.01 to the 06.60.17.00 version

    ‏2012-03-21T14:31:22Z  
    • mmaliakas
    • ‏2012-03-21T13:43:09Z
    hello

    i need to clear the dacstore of a specific drive. how can i generate the datacollection to find the appropriate drive devnum?
    thanks in advanced
    ok i have found the devnum of the drive.the drive is located at the controller enclosure (85)

    i try to execute the following command through telnet

    isp cfgWipe85,0x0000000a

    and i receive

    isp cfgWipe85,0x0000000a
    C interp: unknown symbol name 'cfgWipe'.
    any help?
  • SystemAdmin
    SystemAdmin
    4779 Posts

    Re: DS4700 Firmware Downgrade from the 07.15.10.01 to the 06.60.17.00 version

    ‏2012-03-27T21:38:40Z  
    • mmaliakas
    • ‏2012-03-21T14:31:22Z
    ok i have found the devnum of the drive.the drive is located at the controller enclosure (85)

    i try to execute the following command through telnet

    isp cfgWipe85,0x0000000a

    and i receive

    isp cfgWipe85,0x0000000a
    C interp: unknown symbol name 'cfgWipe'.
    any help?
    1. Do a "collect all support data"
    From there you should be able to get hold of the Enclosure and devnum.

    2. From which DS are you trying to run the cfgWipe command?
    The one with 07.15.10.01 to the 06.60.17.00 version.
    Could be a version issue

    Have you tried to:
    Put the disk into the DS with version 07.15.10.01
    Run the isp cfgWipeEnclosure,devnum command
    Take out the disk
    Put the disk into the DS with version 06.60.17.00

    If it doesn't work, open a case with IBM Support.
  • mmaliakas
    mmaliakas
    11 Posts

    Re: DS4700 Firmware Downgrade from the 07.15.10.01 to the 06.60.17.00 version

    ‏2012-03-28T08:16:01Z  
    1. Do a "collect all support data"
    From there you should be able to get hold of the Enclosure and devnum.

    2. From which DS are you trying to run the cfgWipe command?
    The one with 07.15.10.01 to the 06.60.17.00 version.
    Could be a version issue

    Have you tried to:
    Put the disk into the DS with version 07.15.10.01
    Run the isp cfgWipeEnclosure,devnum command
    Take out the disk
    Put the disk into the DS with version 06.60.17.00

    If it doesn't work, open a case with IBM Support.
    thanks for the reply.

    i try the command from the 07.xx.xx firmware and through a telnet session
    i will check also with the 06.xx.xx firmware and i will try to find the serial cable of the storage. maybe it doesn't work the telnet connection

    if you are sure about the syntax of the command (isp cfgWipe) i will search it better

    thank you!
  • SystemAdmin
    SystemAdmin
    4779 Posts

    Re: DS4700 Firmware Downgrade from the 07.15.10.01 to the 06.60.17.00 version

    ‏2012-03-28T11:44:06Z  
    • mmaliakas
    • ‏2012-03-28T08:16:01Z
    thanks for the reply.

    i try the command from the 07.xx.xx firmware and through a telnet session
    i will check also with the 06.xx.xx firmware and i will try to find the serial cable of the storage. maybe it doesn't work the telnet connection

    if you are sure about the syntax of the command (isp cfgWipe) i will search it better

    thank you!
    Hi
    Probably syntax!

    You wrote that you found the devNum of the drive and that the drive is located at the controller enclosure (85)

    Are you sure about the Enclosure ID?
    85?
    I mean how many enclosures do you have?
    Please recheck Enclosure ID in storageSubsystemProfile.txt

    Open stateCaptureData.dmp with notepad or wordpad and recheck devNum.
    If you search for "dacstore" in the file you might find something like this:



    13:13:13.313
    mel C0001 MelE
    CRITICAL Event:0x2229 Cat:0x4 Pri:1 Log:0 Action:0x0 Origin:0xa1

    ID:0x13 LUN:0x13 Dev:0x0000000a
    Data:0x00000000 Drive failed by controller

    13:13:13.313 ssmDriveSp cfg vffff drvNew
    devNum:x0000000a ev:Fail srcOp:x00000000 arg:161

    13:13:13.313 tVkiLog vkiCE ffff CE_WARN
    13/13/13-13:13:13 (GMT) (ssmDriveSpinTask): WARN: Unsupported dacstore: dev = 0x0000000a


    I suppose that you have enabled the remote login?
    Use putty or something and execute the following command through telnet:

    isp cfgWipe 85,0000000a

    or

    isp cfgWipe 85,0000000a;

    Skip the 0x in the begining.
    Ok ?

    Good luck
  • mmaliakas
    mmaliakas
    11 Posts

    Re: DS4700 Firmware Downgrade from the 07.15.10.01 to the 06.60.17.00 version

    ‏2012-03-30T10:31:50Z  
    Hi
    Probably syntax!

    You wrote that you found the devNum of the drive and that the drive is located at the controller enclosure (85)

    Are you sure about the Enclosure ID?
    85?
    I mean how many enclosures do you have?
    Please recheck Enclosure ID in storageSubsystemProfile.txt

    Open stateCaptureData.dmp with notepad or wordpad and recheck devNum.
    If you search for "dacstore" in the file you might find something like this:



    13:13:13.313
    mel C0001 MelE
    CRITICAL Event:0x2229 Cat:0x4 Pri:1 Log:0 Action:0x0 Origin:0xa1

    ID:0x13 LUN:0x13 Dev:0x0000000a
    Data:0x00000000 Drive failed by controller

    13:13:13.313 ssmDriveSp cfg vffff drvNew
    devNum:x0000000a ev:Fail srcOp:x00000000 arg:161

    13:13:13.313 tVkiLog vkiCE ffff CE_WARN
    13/13/13-13:13:13 (GMT) (ssmDriveSpinTask): WARN: Unsupported dacstore: dev = 0x0000000a


    I suppose that you have enabled the remote login?
    Use putty or something and execute the following command through telnet:

    isp cfgWipe 85,0000000a

    or

    isp cfgWipe 85,0000000a;

    Skip the 0x in the begining.
    Ok ?

    Good luck
    yes id 85 is the Controller Enclosure not a Expansion. it's the default id
  • SystemAdmin
    SystemAdmin
    4779 Posts

    Re: DS4700 Firmware Downgrade from the 07.15.10.01 to the 06.60.17.00 version

    ‏2012-04-05T06:15:12Z  
    • mmaliakas
    • ‏2012-03-30T10:31:50Z
    yes id 85 is the Controller Enclosure not a Expansion. it's the default id
    Did the commands solve your problem ?
  • mmaliakas
    mmaliakas
    11 Posts

    Re: DS4700 Firmware Downgrade from the 07.15.10.01 to the 06.60.17.00 version

    ‏2012-04-05T14:01:08Z  
    Did the commands solve your problem ?
    the isp cfgWipeEnclosure,devnum worked in a DS4800 Storage with 06.xx.xx firmware.
    with a DS4700 with 07.xx.xx it doesn't work

    anyway problem solved!!

    thank you very much!
  • csu007
    csu007
    2 Posts

    Re: DS4700 Firmware Downgrade from the 07.15.10.01 to the 06.60.17.00 version

    ‏2012-05-17T02:09:55Z  
    My system is DS4700 and my firmware version is 6.16.97.

    My Enclosure id is 58, and my devnum is 0xd, therefore I tried to use isp cfgWipe58,0xd command, but I got "unknown symbol name 'cfgWipe85'" error.
    Then I also tried isp cfgWipe1,0xd command, but I got the following messages and the disk is still not recognized by the storage. Any help or command would be highly appreciated.

    
    -> isp cfgWipe1,0xd value = 122714632 = 0x7507a08 -> 05/17/12-02:06:45 (GMT) (ProcessLargeHandler): ERROR: cfg::DriveManager::handleEvent(PFA) can
    't find devnum 13 05/17/12-02:06:45 (GMT) (T2): WARN:  Unsupported dacstore: dev = 0xd 05/17/12-02:06:45 (GMT) (T2): WARN:  Unsupported dacstore: dev = 0xd 05/17/12-02:06:45 (GMT) (T2): WARN:  Unsupported dacstore: dev = 0xd 05/17/12-02:06:45 (GMT) (T2): WARN:  Unsupported dacstore: dev = 0xd 05/17/12-02:06:45 (GMT) (T2): WARN:  Unsupported dacstore: dev = 0xd 05/17/12-02:06:45 (GMT) (T2): WARN:  Unsupported dacstore: dev = 0xd 05/17/12-02:06:45 (GMT) (T2): WARN: Unsupported dacstore: dev = 0xd 05/17/12-02:06:45 (GMT) (T2): WARN:  Unsupported dacstore: dev = 0xd 05/17/12-02:06:45 (GMT) (T2): WARN:  Unsupported dacstore: dev = 0xd 05/17/12-02:06:45 (GMT) (T2): WARN:  Unsupported dacstore: dev = 0xd 05/17/12-02:06:45 (GMT) (T2): WARN:  Unsupported dacstore: dev = 0xd
    
  • 163zsm
    163zsm
    2 Posts

    Re: DS4700 Firmware Downgrade from the 07.15.10.01 to the 06.60.17.00 versi

    ‏2014-06-15T11:39:14Z  
    Meryem,

    Just in case you run into difficulties with SMCli:

    I'm posting the instructions I got from RAID Support at LSI (the makers of the DS4000/5000
    product line). None of this will help you if you don't have the DB9 to mini-DIN adapter
    required to connect to the DS4700 serial port. You'll need Hyperterminal or other
    capable terminal application with Xmodem file transfer capabilities.
    ....................

    Below are the steps to download through the shell, and as per my earlier note, these steps MUST be performed via SERIAL connection. the steps of which are outlined in the attached document

    -> M

    value = 0 = 0x0

    ->

    NOTICE: The BOOT OPERATIONS MENU has been invoked too late for

    proper operation of some activities, including Isolation Diagnostics.

    You may wish to restart this controller again and press Control-B

    IMMEDIATELY after seeing the start-up indicator ("-=<###>=-").

    BOOT OPERATIONS MENU

    1) Perform Isolation Diagnostics 10) Serial Interface Mode Menu

    2) Download Permanent File 11) Display Hardware Configuration

    3) Reserved 12) Change Hardware Configuration Menu

    4) Dump NVSRAM Group 13) Development Options Menu

    5) Patch NVSRAM Group 14) Display Memory Error Log

    6) Set Real Time Clock 15) Manufacturing Setup Menu

    7) Display Board Configuration R) Restart Controller

    8) Special Services Menu Q) Quit Menu

    9) Display Exception Message

    -> 2

    At this point you will see an ASCII character on the screen over and over again, you will need to go to the file download option in your terminal program and download the NVSRAM, and after that the controller firmware. This may take some time, and it is recommended that you perform this action before the maintenance window, (since it specifically involves the ds4800 only)

    After it is complete you will use exit and perform the same steps on the alternate controller. (with two computers attached serially this could be done in tandem, by connections separately to each controller)

    after the download is complete perform sysWipe at the prompt
    Attachment (from above):
    Steps to gain Serial Shell Access to Controller:

    1. Connect a PC, running a terminal program, to the RS-232 port on the back of the controller module, using the serial cable supplied with the array (null-modem, not straight through).

    2. Confirm the terminal settings:

    -Set the com-port to the port configured on the PC

    -9600 baud (19200 for 2772 controller)

    -8 bits

    -no parity

    -1 stop bit

    -xon-xoff for flow control (may need to be changed depending on terminal program)

    3. Issue a BREAK sequence (Press CTRL-BREAK for Hyperterm/WINterm) until prompted for either "escape for shell" or "space bar to set baud rate."

    4. If baud rate

    -is not 9600, set it to that number. Issue a BREAK sequence until prompted "escape for shell." Press Escape.

    .......................................
    I would recommend that you go for a higher connection rate as a 9600 baud transfer will
    be particularly slow. It could take around 45 minutes per controller if you
    connect at 115,200 and maybe slower if you're using a laptop that uses a USB to Serial
    adapter. (The mention of a cable being supplied with the unit is erroneous though the
    small adapter for the serial port should have been shipped with it. Any null modem
    cable would be ok...if you have McData switches, they DO come with the right cable.
    Brocade's supplied serial cable is a straight cable so will not work without a null
    modem adapter.)

    Also, the sysWipe command recommended at the end will pretty much destroy any array information present on the system drives if they're connected. Be careful.....as in CAREFUL!

    Your best probability for success is to open a case with IBM Support and have it
    escalated. I highly recommend it.

    can you tell me ,what's the password of "15) Manufacturing Setup Menu",or how to change the submodel id?

  • john16
    john16
    9 Posts

    Re: DS4700 Firmware Downgrade from the 07.15.10.01 to the 06.60.17.00 version

    ‏2016-03-13T21:42:47Z  

    HI,

     

    can any body give me firmware 7.15 dlp files of ds4700 i am unable to upgrade from 6 to 7.15 using utility 5SMFWUpgInstaller-WS32-10.36.35.10

     

    or any alternative i am thinking to do using M menu