Searching: firmware - 177 Results Found

Legacy Other I updated my E Class firmware to Service Release 2.4/2.4.1 from 3.29.0000.00 and now my E Class is in maintenance mode. What do I do next?
Ken Chou posted this 01 October 2009

Applications/cables/firmware required:

  1. Zterm (http://homepage.mac.com/dalverson/zterm/)

  2. TftpServer (http://www.versiontracker.com/dyn/moreinfo/macosx/18561)

  3. Vtrak E-Class Service Release 2.4.1 firmware (10.05.2270.04

  4. Serial cable that came with the E Class

  5. USB to Serial Adapter (not required if you are going to use an Xserve to connect to the E Class)

Procedure:

  1. Download 10.05.2270.04v2 from www.promise.com (http://www.promise.com/support/download/download2eng.asp?productId=199&category=all&os=100&go=GO)

  2. Install and setup the TftpServer on your Xserve, MacPro or Macbook/Pro. Change the current path, using “Change Path” to point to the folder where you extracted the image to.

    3. Power off the E Class. If you have a J Class attached to the E Class, power off the E Class, then all the J Class attached to the E Class.

    4. Remove all the cables from both controllers except for the Ethernet cable on Controller 1

    5. Remove Controller 2

    6. Install Zterm.

    7. Connect to Controller 1 using the serial cable that came with the E Class. In Zterm, configure the connection Data Rate = 115200, Data Bits = 8, Parity = None, Stop Bits = 1, No Flow Control.


    8. Power up the E Class. Hit control-c when prompted by boot process.

    9. Set-up networking on the E Class.



    10. Flash the E Class with 10.05.2270.04v2 firmware.                                                                                                        


    11. While the firmware is being flashed onto the E Class, you should be able to see the flash progress…



    12. When flashing is complete, redboot will return you to the PBL_RAM> prompt.



    13. Power down the E Class, remove Controller 1 and insert Controller 2.

    14. Connect the serial and Ethernet cables to Controller 2.

    15. Repeat steps 7 to 11 for Controller 2.

    16. Power off the E Class.

    17. Insert both controllers

    18. Restore all cabling removed in Step 4 including SAS cabling to the J Class subsystem/s.

    19. Boot up the J and E Class subsystem.

    20. Update to SR 2.5 (10.06.2270.00). Follow the firmware upgrade instructions provided in the firmware package.

Legacy Other Linux: Qlogic with Sansurfer failover does not work with E-class subsystem.
Ken Chou posted this 31 August 2009


Problem: Qlogic Fiber Channel HBA + Sansurfer that suports failover does not
         work with on Linux with E-class running firmware 2.28.0000.00 or later.


In this example there is one LUN on the subsystem and 2 paths to the subsystem.

        [root@localhost ~]# fdisk -l

        Disk /dev/sda: 21.4 GB, 21475491840 bytes
        64 heads, 32 sectors/track, 20480 cylinders
        Units = cylinders of 2048 * 512 = 1048576 bytes

        Disk /dev/sda doesn't contain a valid partition table

        Disk /dev/sdb: 21.4 GB, 21475491840 bytes
        64 heads, 32 sectors/track, 20480 cylinders
        Units = cylinders of 2048 * 512 = 1048576 bytes

        Disk /dev/sdb doesn't contain a valid partition table

        Disk /dev/sdc: 250.0 GB, 250059350016 bytes


With sansurfer failover enabled you should see only /dev/sda as the Qlogic driver is providing the failover, instead we see the same LUN twice as /dev/sda and /dev/sdb.

=====================================================================

Solution: From the serial port or telnet as administrator enter the
          following command


        -------------------------------------------------------------
        Promise VTrak Command Line Interface (CLI) Utility
        Version: 3.31.0000.00 Build Date: Nov 26, 2008
        -------------------------------------------------------------

        Login: administrator
        Password: *
        -------------------------------------------------------------
        Type help or ? to display all the available commands
        Type menu to enter Menu Driven Configuration Utility
        -------------------------------------------------------------

        administrator@cli> ctrl -a mod -s "commonwwnn=enable"

        administrator@cli> shutdown -a restart


The subsystem must be restarted for this setting to take effect.

If failover is already configured you should see only /dev/sda after the reboot.


        [root@localhost ~]# fdisk -l

        Disk /dev/sda: 21.4 GB, 21475491840 bytes
        64 heads, 32 sectors/track, 20480 cylinders
        Units = cylinders of 2048 * 512 = 1048576 bytes

        Disk /dev/sda doesn't contain a valid partition table

        Disk /dev/sdc: 250.0 GB, 250059350016 bytes


====================================================================

Discussion:

The default setting for the commonwwnn was changed at E-class firmware version 3.28.0000.00 on up.

If your unit had older firmware the old setting may persist unless the "factorydefaults" are reset on the subsystem by the administrator (please see the product user manual on setting factory defaults)




Close