AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070727134424.2c8ec6a6@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<mtracy@css.glasshouse.com>,<dl-cstech@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	037501c7d089$820633d0$805f3090@glasshousetech.com
X-Sylpheed-End-Special-Headers: 1
Date: Fri, 27 Jul 2007 13:44:38 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Michael Tracy" <mtracy@css.glasshouse.com>
Cc: "DL-CStech" <dl-cstech@onstor.com>
Subject: Re: issues during upgrade to 3.0.0.2
Message-ID: <20070727134438.779c589f@ripper.onstor.net>
In-Reply-To: <037501c7d089$820633d0$805f3090@glasshousetech.com>
References: <037501c7d089$820633d0$805f3090@glasshousetech.com>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Fri, 27 Jul 2007 16:05:41 -0400 "Michael Tracy"
<mtracy@css.glasshouse.com> wrote:


You failed to mention what version you were upgrading *from*.

> Hi all
> 
> Having problems upgrading to 3.0.0.2 using the Release Notes process.
> 
> Any assistance would be appreciated.
> 
> Michael
> 
> 
> 
> My comments are below in red
> 
> =============================================================
> 
> To upgrade NAS Gateways to the new software version, follow this
> procedure: 
> 
> Step 1: (Optional) To capture the current system configuration, run
> the following command to send it to ONStor Customer Support: 
> 
> system get all -c 
> 
> CASENUM CASENUM is your customer case number under which to upload
> the collected information to an ONStor server via SSL. If you do not
> have an existing case number in the system, you need to open a case
> and upload the files to it. 
> 
> Step 2: (Optional) If you are upgrading multiple NAS Gateways in a
> cluster, use the vsvr move command to move virtual servers on the NAS
> Gateway being upgraded to other NAS Gateways. 
> 
> Step 3: Log in to the management interface of the NAS Gateway as the
> root user. The original root password is back-door. 
> 
> Step 4: Change the directory to /tmp. 
> 
> # cd /tmp 
> 
> Step 5: Download the installation script and distribution files by
> typing the following commands: 
> 
> # ftp ftp://ftp.onstor.com/outbound/software/EverON/RELEASE/
> PLATFORM/everon-RELEASE-install.sh 
> 
> Where RELEASE is the release number and PLATFORM is 22xx for the
> Bobcat 2200 series or 44xx for the Cheetah SF4400 series. 
> 
> Note! The value of RELEASE is associated with a specific version of
> the EverON software. For example, the 3.0.0.1 script will not work
> for the 3.0.0.2 release.
> 
> The following are examples of the ftp command for Bobcat and Cheetah
> and release 3.0.0.2: Bobcat: 
> 
> # ftp ftp://ftp.onstor.com/outbound/software/EverON/3.0.0.2/
> 22xx/everon-3.0.0.2-install.sh 
> 
> This command didn't seem to do anything. After trying it several
> times and seeing nothing in /tmp, I eventually  manually downloaded
> the script to /tmp
> 
> Cheetah: 
> 
> # ftp ftp://ftp.onstor.com/outbound/software/EverON/3.0.0.2/
> 44xx/everon-3.0.0.2-install.sh 

All these examples in your email have an extra space in them (after
the version number and trailing slash). I'm assuming that you didn't
have that space there when you were running the commands for real.

> Step 6: Execute install program. 
> 
> # sh everon-RELEASE-install.sh 
> 
> sh everon-3.0.0.2-install.sh 
> 
> Step 7: Program prompts for the following information: 
> 
> - Would the user like to run in interactive mode? 
> 
> - Yes - you will be prompted to reboot 
> 
> - No - you will not be prompted to reboot 
> 
> chose 'yes'
> 
> - The ftp URL of the distribution 
> 
> prompted for the tarball location -  using the default Onstor site so
> I just hit enter
> 
> 
> 
> Please enter the ftp or http URL of the distribution:
> [ftp://support.onstor.com/outbound/software/EverON/3.0.0.2/22xx/EverON-3.0.0.2BC                                             .tar.gz]
> 
> This will take at least 138 seconds to download.
> Thank you for your patience.
> 
> Downloading external system software distribution.
> hookup: 228: Onstor src ip = 0x0
> Connected to support.onstor.com.
> 220 ProFTPD 1.3.0 Server (ONStor ASSIST) [66.201.51.83]
> 331 Anonymous login ok, send your complete email address as your
> password.
> 230-###########################################################################
> 230-#            *** WELCOME TO THE ONSTOR SUPPORT FTP SERVER
> ***             # 230-#          *** THIS SITE IS FOR CUSTOMERS AND
> PARTNERS ONLY ***           #
> 230-#
> # 230-# Please upload all files to the
> directory: /incoming                     #
> 230-#
> # 230-# All files uploaded MUST have "caseXXXX-" at the beginning of
> the        # 230-# filename, where XXXX is the case number. For
> example:                   #
> 230-#
> # 230-#
> case1234-system_get_all.tar.gz
> #
> 230-#
> # 230-# NOTE: Files with filenames not in the correct (caseXXXX-)
> format will   # 230-# be deleted on a regular basis and will not be
> transferred to support.   #
> 230-###########################################################################
> 230 Anonymous access granted, restrictions apply. Remote system type
> is UNIX. Using binary mode to transfer files. 200 Type set to I 250
> CWD command successful 250 CWD command successful Retrieving
> outbound/software/EverON/3.0.0.2/22xx/EverON-3.0.0.2BC.tar.gz local:
> EverON-3.0.0.2BC.tar.gz remote: EverON-3.0.0.2BC.tar.gz 229 Entering
> Extended Passive Mode (|||57813|)
> 
> 100% |**************************************************| 46603 KB
> 38:59 226 Transfer complete.
> 47722288 bytes received in 2339.80 seconds (19.92 KB/s)
> 221 Goodbye.
> Please try again.
> 
> Please enter the ftp or http URL of the distribution:
> [ftp://support.onstor.com/outbound/software/EverON/3.0.0.2/22xx/EverON-3.0.0.2BC.tar.gz]
> 
> This will take at least 138 seconds to download.
> Thank you for your patience.
> 
> Definitely took more than 138 seconds. More like 20-30 minutes.
> 
> It seemed to complete but then prompted me again. Never told me what
> happened just seemed prompted me to restart. Hit enter again and the
> process is downloading again. On the 3rd attempt now.   What am I
> missing here?
> 
> ------------------------Haven't gotten past here
> yet-------------------------------------
> 
> Step 8: (Optional) Program finishes installation and prompts user if
> they wish to reboot. 
> 
> This happens only if you replied Yes to running in the interactive
> mode. 
> 
> Step 9: System reboots and is running 3.0.0.2 on what was the standby
> flash. 
> 
> Step 10: Wait until the upgraded NAS Gateway finishes rebooting, then
> verify that it has rejoined the cluster by running the cluster show
> cluster command on another NAS Gateway in the cluster. The resulting
> output contains the State field. If the upgraded NAS Gateway has
> successfully rebooted and rejoined the cluster, the State field
> displays UP. 
> 
> Note! After the first NAS Gateway is upgraded, but before the second
> NAS Gateway is upgraded, you cannot run any commands that write to
> the cluster database, for example, any volume create or share add
> commands. However, you can run commands that read from the cluster
> database, for example, cluster show cluster. 
> 
> Step 11: After the upgraded NAS Gateway has rebooted, repeat this
> procedure on any other NAS Gateway you want to upgrade. 
> 
> Step 12: (Optional) To capture the updated system configuration, run
> the following command to send it to ONStor Customer Support: 
> 
> system get all -c 
> 
> CASENUM CASENUM is your customer case number under which to upload
> the collected information to an ONStor server via SSL. If you do not
> have an existing case number in the system, you need to open a case
> and upload the files to it.
