Sun Storage 7000 Series Software Updates

1. 

   Mar 18, 2009

   yurx149158 says:

   How long does version upgrade take ?

   How long does version upgrade take ?

   • Permalink

   1. 

      Mar 18, 2009

      Espen says:

      Hi, To upgrade takes as lon as a reboot of the alliance. The services is up an...

      Hi,
      To upgrade takes as lon as a reboot of the alliance.
      The services is up and running while the upgrade is done on a ZFS snapshot.

      • espen -

      • Permalink

   2. 

      Mar 19, 2009

      bosborn says:

      If your system is not very busy, it will take about 15 minutes. Note that once t...

      If your system is not very busy, it will take about 15 minutes. Note that once the bundle is loaded and added to the system, the system will perform a reboot.

      • Permalink

2. 

   May 28

   BluePrintsOnline says:

   Hi It is possible to download a older version we need the 2008.Q4.2.1 newer v...

   Hi

   It is possible to download a older version we need the 2008.Q4.2.1

   newer version are not supporter by VDI 3.0 see the VDI 3.0 release notes

   kind regards

   • Permalink

   1. 

      Jun 04

      Stefan82 says:

      I'm not sure if it's possible to download the old version. What I do know is th...

      I'm not sure if it's possible to download the old version.

      What I do know is that VDI 3.0.1 is supported with all software versions of the Storage 7000 when used in combination with the VMware Desktop provider. In combination with the VirtualBox desktop provider you are limited to the 2008.Q4.2.1 version and before.

      Kind Regards,
      Stefan

      • Permalink

3. 

   Sep 30

   dhneilson says:

   I was going to upgrade to the 2009.Q3.0.0 release since we use iSCSI extensively...

   I was going to upgrade to the 2009.Q3.0.0 release since we use iSCSI extensively, but with the minor release 2009.Q3.1.0 coming out, I don't know if I should wait because I can't get any details on the issues which Q3.1.0 fixes, such as CR 6876588, or CR 6876603, etc? I have looked all over Sunsolve and I can't find any reference to these CRs.

   • Permalink

   1. 

      Oct 19

      matt.weatherford says:

      dhneilson: I can tell you this: I lost 2 iSCSI LUNS when I upgraded to the fir...

      dhneilson:

      I can tell you this: I lost 2 iSCSI LUNS when I upgraded to the first Q3 release 2 days after it came out.
      I did not heed the "Old stuff will not be migrated warning"

      8 LUNS were fine and transitioned to the new iSCSI SAN/multi lun-per-target mode, but 2 showed up at "GUID <unknown>"
      and I never was able to get them working. Even rolling back to a pre-Q3 update snapshot had no effect.

      Had I not replicated to a friend's 7110 on a prior firmware in a panic afterwards, I'd have lost data.

      Be sure you have good backups of your iSCSI luns before performing the Q3 update. Assume you'll have to reset the device to factory defaults and clear your data off the box. When I did this and tried to import the old pool, it was not recognized (more GUID unknown errors) I had to wipe the ZPOOL as well.

      Sun stuff is great, but if you've worked with it for a while, updates sometimes have bugs, warnings are understated, and it often pays to wait. If this had been my software release, id have said "you will need to reset the 7xxx to factory defaults and recreate your ZPOOL after this upgrade" - thats what I had to do in the end.

      My $.02 worth

      Matt

      • Permalink

      1. 

         Oct 21

         kirkkosinski says:

         I'm using the Sun Storage VMware appliance for testing, and I also had a LUN wit...

         I'm using the Sun Storage VMware appliance for testing, and I also had a LUN with unknown GUID after the upgrade (I went from Q2.0 to Q3.1).The problem was that a new COMSTAR-compatible LUN was not automatically created, apparently because the ZFS pool version was not supported by COMSTAR and not automatically upgraded to a supported version.

         I successfully restored the LUN by manually upgrading the ZFS pool version, then re-creating the LUN. Before upgrading the ZFS pool version, sbdadm gave the error "could not create meta file" when trying to create the LUN.

         After this process, the web GUI still had problems (IIRC it was throwing libstmf errors), but it worked correctly after a reboot. After the reboot, the GUID showed up for the LUN, and the LUN was back to normal; I reconnected my test XenServer host to the LUN and all the data (two VHDs for a Windows VM) was intact. Here's the log of what I did... YMMV, please be careful with this stuff!

         sun-vmware# sbdadm list-lu
         sun-vmware# zpool list
         NAME     SIZE   USED  AVAIL    CAP  HEALTH  ALTROOT
         pool-0  27.8G  1.46G  26.3G     5%  ONLINE  -
         system  9.94G  3.71G  6.23G    37%  ONLINE  -
         sun-vmware# zpool upgrade pool-0
         This system is currently running ZFS pool version 18.
         
         Successfully upgraded 'pool-0' from version 14 to version 18
         
         sun-vmware# sbdadm list-lu
         sun-vmware# sbdadm create-lu /dev/zvol/rdsk/pool-0/local/test/testlun
         Created the following LU:
         
         GUID                    DATA SIZE           SOURCE
         \-------------------------------\-  \------------------\-  \---------------\-
         600144f00000000000004adef6ac0002  22548578304          /dev/zvol/rdsk/pool-0/local/test/testlun
         sun-vmware# sbdadm list-lu
         
         Found 1 LU(s)
         
         GUID                    DATA SIZE           SOURCE
         \-------------------------------\-  \------------------\-  \---------------\-
         600144f00000000000004adef6ac0002  22548578304          /dev/zvol/rdsk/pool-0/local/test/testlun
         

         Note: On the virtual appliance, I could only upgrade to Q3.1 if it was running the default Q2.0 software; if I tried to upgrade to an interim release (I tried Q2.3 and Q2.5), then to Q3.1, it failed 100% of the time during the Q3.1 upgrade. I allocated more RAM to the appliance (I gave it 3GB), which may have helped (it helped with upgrading to interim releases... with the default 1GB, the upgrade always failed).

         • Permalink

4. 

   Oct 23

   jrath says:

   We are using VMware Simulator of 7410 for our testing purpose as we can;t do the...

   We are using VMware Simulator of 7410 for our testing purpose as we can;t do the dev & test on the Real 7410s. But we faced the same problem when upgrading the Simulator.
   The first case was, the Simulator Contained Q2.5.0 and when we tried to upgrade with Q3.1.0, it failed many times.
   The second case was, the simulator was not applied with any Upgrades and directly the Q3.1.0 was applied. That succeeded.

   But, we were not able to create a single iSCSI Disk by any means (BUI/GUI). It always showed the libstmf error.

   The only way i found was to manually create a Zpool in the Simulator and then use Comstar Stack commands to creat ZFS files and iSCSI volumes on top of it using sbdadm.
   The iSCSI LUNS still didn't show the GUID yet. I had to restart akd (svcadm restart akd:default) to get that reflected (A reboot would also do).

   The story was same with Virtual Disk Simulator also.

   But, its high time that with such a major release Q3.1, the Sun Team should immediately fix the bugs with the Simulator Images. Because in certain environments, the concerned cannot dev&test on real 7410 systems. The Simulator is the only means available to them.

   JUST NOW I NOTICED THAT A LINK HAS BEEN ADDED TO THE "PREVIOUS RELEASES" section of this page in the top. The latest release is "2009.Q2.5.1 RELEASED ON 10/21/2009" . I don;t know why the latest release came in the previous release section.

   I have to download and test it and see if this works with the Q3.1. release in the simulator.

   Jagannathdas Rath
   Project Engineer, Wipro

   • Permalink

Sign up or Log in to add a comment or watch this page.