2 Replies Latest reply: Jan 12, 2012 1:27 AM by User205128 RSS

    Firmware upgrade for storagetek 6140

    User205128
      Hello Everyone,

      I'd plan to upgrade my storagetek 6140 firmware, yet I'm not so sure what is affected to the storage during upgrading.
      Should I upgrade it to baseline version is "06.60.22.10" or latest of 07.60.53.10 version

      Kindly share your ideas with this issue.

      Description: CRM Storage is at revision "N399X-619843-004" baseline version is "N399X-660843-003"
      Tray.85.Controller.B is at revision "06.19.25.10" baseline version is "06.60.22.10"
      Tray.85.Controller.A is at revision "06.19.25.10" baseline version is "06.60.22.10"
      Tray.00.IOM.B is at revision "9884" baseline version is "98D3"
      Tray.00.IOM.A is at revision "9884" baseline version is "98D3"
      Tray.85.Drive.09 is at revision "0691" baseline version is "3192"
      Tray.85.Drive.14 is at revision "3092" baseline version is "3192"
      Tray.85.Drive.03 is at revision "0691" baseline version is "3192"
      Tray.85.Drive.15 is at revision "0691" baseline version is "3192"
      Tray.85.Drive.07 is at revision "3092" baseline version is "3192"
      Tray.85.Drive.10 is at revision "0691" baseline version is "3192"
      Tray.85.Drive.11 is at revision "0691" baseline version is "3192"
      Tray.85.Drive.05 is at revision "0691" baseline version is "3192"
      Tray.85.Drive.12 is at revision "0691" baseline version is "3192"
      Tray.85.Drive.06 is at revision "0691" baseline version is "3192"


      Thanks,
      Vutha
        • 1. Re: Firmware upgrade for storagetek 6140
          910309
          Assuming you have redundant configuration, you may upgrade controllers' firmware within 6.x range without outage. Disk firmware always need outage.
          Upgrading to 7.x firmware line is a multi-step process and requires downtime, data backup, etc. because it re-organizes certain aspects of data storage on the array. Volumes, profiles, etc. are left intact.

          So - if you cannot afford downtime, upgrade to 6.60. If you may do that, upgrade to newest FW. One action complements the other, because upgrading to 7.x requires having 6.60.

          Hope that helps
          • 2. Re: Firmware upgrade for storagetek 6140
            User205128
            Hello Damian,

            Thanks for your reply.


            Let's say if I don't do firmware update, what will affect for the future?
            Currently, from server side got the same error as below



            8:14:30 rkppdb1 qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(1): Loop OFFLINE
            Dec 31 18:14:31 rkppdb1 qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(3): Loop OFFLINE
            Dec 31 18:14:31 rkppdb1 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g600a0b80002a0ad00000033347198b5f (sd5):
            Dec 31 18:14:31 rkppdb1      SCSI transport failed: reason 'tran_err': retrying command
            Dec 31 18:14:31 rkppdb1 qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(0): Loop OFFLINE
            Dec 31 18:14:54 rkppdb1 qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(2): Loop ONLINE
            Dec 31 18:14:54 rkppdb1 qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(1): Loop ONLINE
            Dec 31 18:14:54 rkppdb1 qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(0): Loop ONLINE
            Dec 31 18:14:54 rkppdb1 qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(3): Loop ONLINE
            Dec 31 18:14:55 rkppdb1 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g600a0b800029976a0000033d47198aea (sd4):
            Dec 31 18:14:55 rkppdb1      Error for Command: write(10) Error Level: Retryable
            Dec 31 18:14:55 rkppdb1 scsi: [ID 107833 kern.notice]      Requested Block: 58607857 Error Block: 58607857
            Dec 31 18:14:55 rkppdb1 scsi: [ID 107833 kern.notice]      Vendor: SUN Serial Number:
            Dec 31 18:14:55 rkppdb1 scsi: [ID 107833 kern.notice]      Sense Key: Not Ready
            Dec 31 18:14:55 rkppdb1 scsi: [ID 107833 kern.notice]      ASC: 0x4 (LUN is becoming ready), ASCQ: 0x1, FRU: 0x0
            Dec 31 18:14:55 rkppdb1 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g600a0b80002a0ad00000033347198b5f (sd5):
            Dec 31 18:14:55 rkppdb1      Error for Command: write(10) Error Level: Retryable
            Dec 31 18:14:55 rkppdb1 scsi: [ID 107833 kern.notice]      Requested Block: 105013137 Error Block: 105013137
            Dec 31 18:14:55 rkppdb1 scsi: [ID 107833 kern.notice]      Vendor: SUN Serial Number:
            Dec 31 18:14:55 rkppdb1 scsi: [ID 107833 kern.notice]      Sense Key: Not Ready
            Dec 31 18:14:55 rkppdb1 scsi: [ID 107833 kern.notice]      ASC: 0x4 (LUN is becoming ready), ASCQ: 0x1, FRU: 0x0
            Dec 31 18:15:00 rkppdb1 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g600a0b800029976a0000033d47198aea (sd4):
            Dec 31 18:15:00 rkppdb1      Error for Command: write(10) Error Level: Retryable
            Dec 31 18:15:00 rkppdb1 scsi: [ID 107833 kern.notice]      Requested Block: 58607857 Error Block: 58607857
            Dec 31 18:15:00 rkppdb1 scsi: [ID 107833 kern.notice]      Vendor: SUN Serial Number:
            Dec 31 18:15:00 rkppdb1 scsi: [ID 107833 kern.notice]      Sense Key: Not Ready
            Dec 31 18:15:00 rkppdb1 scsi: [ID 107833 kern.notice]      ASC: 0x4 (LUN is becoming ready), ASCQ: 0x1, FRU: 0x0
            Dec 31 18:15:01 rkppdb1 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g600a0b80002a0ad00000033347198b5f (sd5):
            Dec 31 18:15:01 rkppdb1      Error for Command: write(10) Error Level: Retryable
            Dec 31 18:15:01 rkppdb1 scsi: [ID 107833 kern.notice]      Requested Block: 105013137 Error Block: 105013137
            Dec 31 18:15:01 rkppdb1 scsi: [ID 107833 kern.notice]      Vendor: SUN Serial Number:
            Dec 31 18:15:01 rkppdb1 scsi: [ID 107833 kern.notice]      Sense Key: Not Ready
            Dec 31 18:15:01 rkppdb1 scsi: [ID 107833 kern.notice]      ASC: 0x4 (LUN is becoming ready), ASCQ: 0x1, FRU: 0x0
            Dec 31 18:15:06 rkppdb1 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci



            Thanks,
            Vutha