AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<john.keiffer@onstor.com>,<larry.scheer@onstor.com>,<dl-qa@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	BB375AF679D4A34E9CA8DFA650E2B04E0AF1DE8A@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 17 Jul 2008 09:55:14 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "John Keiffer" <john.keiffer@onstor.com>
Cc: "Larry Scheer" <larry.scheer@onstor.com>, "dl-QA" <dl-qa@onstor.com>
Subject: Re: Submittal 31 is available
Message-ID: <20080717095514.7d05c3aa@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0AF1DE8A@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E056C9727@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E0AF1DE8A@onstor-exch02.onstor.net>
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

Perfectly possible.  Http is not a perfect protocol.  Better than ftp,
but still not perfect.

On Thu, 17 Jul 2008 07:22:57 -0700 "John Keiffer"
<john.keiffer@onstor.com> wrote:

> Larry,
> 
>  
> 
> I have successfully upgraded 3 Cougar systems. I did run into a
> problem on one of the filers though. I ran the system upgrade
> command, but it failed. Since it seemed to be working on the other
> filers, I just issued the command again and it worked. However, can
> you explain what might have caused this the first time I tried it?
> 
>  
> 
> 07/17/08 07:13:41 g5r10 diag> system upgrade -s -f
> http://10.2.0.21/upgrade/R4.0.0.0CG-071608.tar.gz
> 
> Checking file system...
> 
> Mounting secondary disk...done.
> 
> Downloading external system software distribution.
> 
> --07:13:43--  http://10.2.0.21/upgrade/R4.0.0.0CG-071608.tar.gz
> 
>            => `R4.0.0.0CG-071608.tar.gz'
> 
> Connecting to 10.2.0.21:80... connected.
> 
> HTTP request sent, awaiting response... 200 OK
> 
> Length: 79,673,438 (76M) [application/x-gzip]
> 
>  
> 
> 100%[===================================================================
> =============================================>] 79,673,438    11.11M/s
> ETA 00:00
> 
>  
> 
> 07:13:50 (11.17 MB/s) - `R4.0.0.0CG-071608.tar.gz' saved
> [79673438/79673438]
> 
>  
> 
>  
> 
> gzip: stdin: invalid compressed data--format violated
> 
> tar: Unexpected EOF in archive
> 
> tar: Error is not recoverable: exiting now
> 
> Download failed.
> 
> Unmounting /mnt1/onstor/conf...done.
> 
> Unmounting /mnt1/var...done.
> 
> Unmounting /mnt1/...done.
> 
> % Command failure.
> 
>  
> 
> Thanks,
> 
> John
> 
>  
> 
> ________________________________
> 
> From: Larry Scheer 
> Sent: Wednesday, July 16, 2008 4:34 PM
> To: dl-Cougar; dl-QA
> Subject: Submittal 31 is available
> 
>  
> 
> Cougar_Submittal_31_Notes
> Submittal 31 was delayed for a fix to a problem encountered during
> acceptance testing. QA please see section 12 for additional things to
> look for while testing. 
> 
> ________________________________
> 
> Project Cougar Submittal Notes
> 
>  
> 
>  
> 
>  
> 
>  
> 
>  
> 
> Project
> 
> Cougar 4.0
> 
> Submittal#
> 
> 28
> 
> Date
> 
> July 16 2008
> 
>  
> 
>  
> 
>  
> 
> 
> 
> 
>  
> 
> TABLE OF CONTENTS
> 
>  
> 
> 1.       Features & Functions included in this submittal 4
> 
> 2.       Specific Installation/Configuration Information. 5
> 
> 2.1.      Cluster Database. 5
> 
> 2.2.      Required PROM version and configuration. 5
> 
> 2.3.      Configuration files for both Beta Release and GA Candidate.
> 6
> 
> 2.4.      HTTP and FTP use with the upgrade server 8
> 
> 2.5.      Configuring the automounter and ypbind. 8
> 
> 2.6.      How to enable DMALLOC monitoring. 9
> 
> 3.       Source tree information. 9
> 
> 3.1.      Perforce label 9
> 
> 3.2.      Last EverON Perforce change list 9
> 
> 3.2.1.    Submittal GA Candidate. 9
> 
> 3.3.      Source tree location. 9
> 
> 3.3.1.    Submittal GA Candidate. 9
> 
> 3.4.      BSD distribution images for System W upgrade. 9
> 
> 3.4.1.    Submittal GA Candidate. 9
> 
> 4.       System upgrade information. 10
> 
> 4.1.      System upgrade information for EverON.. 10
> 
> 4.2.      Location of Cougar distribution images. 10
> 
> 4.2.1.    Submittal GA Candidate. 10
> 
> 4.3.      Prom settings for compact flash boot 10
> 
> 5.       SSC PROM Upgrade instructions. 11
> 
> 6.       Runtime PROM Upgrade instructions. 11
> 
> 7.       Restrictions/limitations in this submittal 12
> 
> 7.1.      Restrictions in this submittal 12
> 
> 7.2.      Restrictions from previous submittal that still apply to
> this submittal 12
> 
> 7.3.      Problems encountered during Acceptance Testing. 12
> 
> 8.       Details of New Features introduced in submittal 12. 13
> 
> 8.1.      I/O Coalescing. 13
> 
> 8.2.      Root level storage command. 13
> 
> 8.3.      TXRX command: nfsperftest 13
> 
> 8.4.      FC diag command: scsiadmin trace. 13
> 
> 8.5.      New Analytics. 13
> 
> 9.       Requirements to boot from Compact Flash. 14
> 
> 10.     New/Changed/Obsolete modules/binaries. 14
> 
> 10.1.       Changed in submittal 18. 14
> 
> 10.2.       Introduced in submittal 2: 14
> 
> 10.3.       Introduced in submittal 14: 14
> 
> 11.     Troubleshooting tips. 14
> 
> 12.     Special focus/concerns/additional testing. 14
> 
> 13.     Pre-submittal tests results. 15
> 
> 13.1.       Build verification test results. 15
> 
> 13.2.       Acceptance test results. 15
> 
>  
> 
>  
> 
> 
> 
> 
>  
> 
> 
> 1.       Features & Functions included in this submittal
> 
> 
> New features
> 
>  
> 
> Specific P1 - P2 bug fixes; in particular changes were added to
> support the scsi-3 Target Port Groups needed for vendors such as
> Fujitsu, Nexsan, IBM and Pillar. See section 12 for special focus.
> 
>  
> 
> If your filer is running a build older than submittal 30 please review
> section 2 for important installation and configuration information.
> 
>  
> 
> This submittal was built with DMALLOC support; see section 2.6 for
> instructions on how to turn on DMALLOC monitoring.
> 
>  
> 
> Particular fixes 
> 
>  
> 
> TED 22684 - S-Soak (G2R5): NDMP Snapshot Extension, snapshot restore
> fails due browsing
> 
> TED 23328 - Secondary filer mounting a mirror target not updating its
> caches after a mirror session
> 
> TED 23399 - Clustering needs to restart apps when it gets a new clusDb
> to avoid inconsistencies
> 
> TED 23916 - 2 messages printing in SSC console after reboot about
> unkown option and no such file or dir
> 
> TED 23932 - Fujitsu - Pick up LUN Capacity expansion sense keys
> 
> TED 23933 - Fujitsu - Vendor unique sense codes we can choose to
> impliment
> 
> TED 24132 - SNMP crash running Sub24 Dev
> 
> TED 24202 - support.sh session didnt complete and was consuming 100%
> of the CPU on SSC
> 
> TED 24495 - crontab corrupted in cluster environment
> 
> TED 24618 - scsi_sendReadRspWithData (sd=0x1002ecfe00, eCode=11,
> csum=0, transSeqId=0, dataOffset=0x0, isMirror=1) at scsi-msg.c:5047
> 
> TED 24619 - S-Soak (G12R9) - vol delete CLI succeeds but volume not
> deleted
> 
> TED 24640 - Restore fails with sub29 and Veritas DMA
> 
> TED 24701 - preferred port not stored for Fujitsu E4000, stays open on
> failover path
> 
> TED 24709 - Cougar FP2 crash - TLBL in fs_logReleaseReplayBitmap()
> 
> TED 24724 - $MRHUNG line in console output after reboot regarding
> support.sh
> 
> TED 24731 - volume exception while killing a mirror session
> 
> TED 24733 - S-Soak (G2R5): Volume exception during mirror - snapInfo
> lock timeout
> 
> TED 24752 - Volume exception followed by forced meek - nx-d_buildup -
> fs_removeLink: Link Entry not found - first eek did not fix errors
> 
> TED 24754 - FP crash - TLBL in ultranew_memcpy_doubleword_loop() while
> dumping lock structures in Volume Exception
> 
> TED 24769 - Lun device name missing model with scsi sho all
> 
>  
> 
> Perforce change lists since last submittal
> 
>  
> 
> Change 30058 on 2008/07/16 by billn@billn-dev ' Change 30057 by
> billn@billn-de'
> 
> Change 30053 on 2008/07/16 by deepakv@pinky '   Integrate change 30050
> from '
> 
> Change 30051 on 2008/07/16 by jobia@jobi:jobi '   Change 30048 by
> jobia@jobi:j'
> 
> Change 30043 on 2008/07/15 by henryl@henryl-linux '   Integrate p4
> change 30042'
> 
> Change 30041 on 2008/07/15 by andys@ripper 'Integrate 30037 from dev
> branch'
> 
> Change 30033 on 2008/07/15 by svatic@schandra-linux '   Integrating
> herewith the fix'
> 
> Change 30031 on 2008/07/15 by amitb@amitb-default '   Integrate p4
> 30029 from dev '
> 
> Change 30025 on 2008/07/15 by billn@billn-dev ' Change 30022 by
> billn@billn-de'
> 
> Change 30024 on 2008/07/15 by billn@billn-dev ' Change 30021 by
> billn@billn-de'
> 
> Change 30020 on 2008/07/15 by henryl@henryl-linux '   Integrate p4
> change 30019 fr'
> 
> Change 30012 on 2008/07/14 by henryl@henryl-linux '   Integrate p4
> change 30010 fr'
> 
> Change 30011 on 2008/07/14 by chrisv@chrisv-r40 'Integrate #29999 from
> dev into '
> 
> Change 30009 on 2008/07/14 by amitb@amitb-default '   Integrate p4
> 30008 Origi'
> 
> Change 30006 on 2008/07/14 by rendellf@rendellf-test 'TED24132: SNMP
> crash running Su'
> 
> Change 30002 on 2008/07/14 by maximk@maximk-13 ' integrate 29998
> 24618 scsi_se'
> 
> Change 30001 on 2008/07/14 by andys@ripper 'Integrate 30000 from dev
> to r40'
> 
> Change 29997 on 2008/07/14 by larrys@build-k3-depot 'Reverting dmalloc
> changes that '
> 
> Change 29996 on 2008/07/14 by larrys@build-k3-depot 'Updating main
> with code from de'
> 
>  
> 
> 
> 2.       Specific Installation/Configuration Information
> 
> 
> 2.1.               Cluster Database
> 
> 
> If you are running a build older than submittal 30 the following
> instructions should be followed before upgrading.
> 
>  
> 
> With change list #29983 the clusDb has a new version number.  It is
> now version 3.3.
> 
>  
> 
> Save a copy of your existing clusDb (/onstor/conf/cluster.db.DB0)
> before you install a build with this code.
> 
>  
> 
> As with every clusDb upgrade, you cannot downgrade to a previous
> revision once you install a build with a new cluster database version.
> Saving a copy of your old clusDb is the only way around this (other
> than sys config reset, of course.)
> 
>  
> 
> If you are running a multi-node cluster, you must upgrade all nodes,
> as various CLI commands may be unavailable in a partially upgraded
> cluster.
> 
> 
>  
> 
> For debugging purposes an upgrade of the cluster database is logged
> with at elog level ERROR.
> 
>  
> 
> There is no need to be concerned. A successful upgrade message will be
> similar to:
> 
>  
> 
> 0:0:cluster2:ERROR: cluster_upgrade_db_runtime: ClusDb update
> complete; successfully updated version from 0x30200 to 0x30300
> 
>  
> 
> 
> 2.2.               Required PROM version and configuration
> 
> 
> Verify your SSC, TXRX, and FP PROMs are version: Cougar-prom-1.0.7:
> Tue Jun 3 15:19:57 2008.
> 
> If not follow the instructions in section 5 to upgrade your SSC PROM
> and the instructions in section 6 to upgrade your FP and TXRX PROMs.
> 
>  
> 
> You must have you SSC, TXRX, and FP PROM autoload and autoreboot
> settings configured identically.
> 
>  
> 
> Recommended settings:
> 
> env set autoload on
> 
> env set autoreboot off
> 
> Configure your SSC prom in the SSC console as explained in section 4.3
> 
>  
> 
> Configure your TXRX PROM with rcon; example:
> 
> rcon  1 0
> 
> TXRX0:1 > env set autoload on
> 
> TXRX0:2 > env set autoreboot off
> 
> <ctrl> c
> 
> Configure your FP PROM with rcon; example:
> 
> rcon  1 2
> 
> FP0:1 > env set autoload on
> 
> FP0:2 > env set autoreboot off
> 
> <ctrl> c
> 
>  
> 
> 
> 2.3.               Configuration files for both Beta Release and GA
> Candidate 
> 
> 
> Before doing an upgrade or a flash install check your configuration
> files for up-to-date format changes and proper configuration as
> outlined in this section.
> 
> The format of configuration files preserved between upgrades and
> flash_install.sh have changed over time. Check the following files for
> correct configuration as indicated.
> 
> Hosts:
> 
> /etc/hosts (default example with no SC interfaces configured shown)
> 
>             127.0.0.1               localhost
> 
>  
> 
> Hosts.user:
> 
> Remove /etc/hosts.user if its contents look like this:
> 
> 127.0.0.1               localhost
> 
>  
> 
> NTP Conf file (shown configured with two ntp servers)
> 
> /etc/ntp.conf
> 
> # /etc/ntp.conf, configuration for ntpd
> 
>  
> 
> driftfile /var/lib/ntp/ntp.drift
> 
> statsdir /var/log/ntpstats/
> 
>  
> 
> statistics loopstats peerstats clockstats
> 
> filegen loopstats file loopstats type day enable
> 
> filegen peerstats file peerstats type day enable
> 
> filegen clockstats file clockstats type day enable
> 
>  
> 
>  
> 
> # By default, exchange time with everybody, but don't allow
> configuration.
> 
> # See /usr/share/doc/ntp-doc/html/accopt.html for details.
> 
> restrict -4 default kod notrap nomodify nopeer noquery
> 
> restrict -6 default kod notrap nomodify nopeer noquery
> 
>  
> 
> # Local users may interrogate the ntp server more closely.
> 
> restrict 127.0.0.1
> 
> restrict ::1
> 
>  
> 
> # You do need to talk to an NTP server or two (or three).
> 
> #server ntp.your-provider.example
> 
> server 10.0.0.18 iburst
> 
> server 10.2.0.2 iburst
> 
>  
> 
> Time Zone file (should be an ascii file; example shows the time zone
> for Campbell, CA)
> 
> /etc/timezone 
> 
> US/Pacific
> 
>  
> 
> Mail Name file (an unconfigured file will contain the name localhost)
> 
> /etc/mailname
> 
>    <your filer's hostname>
> 
>  
> 
> Addroutes:
> 
>  
> 
> If you are running a pre-sub27 build, before flash_install or system
> upgrade remove /etc/network/if-up.d/addroutes on the primary flash.
> 
>  
> 
> After flash_install or system upgrade and a reboot -s, verify
> /etc/network/if-up.d/addroutes is as follows:
> 
>  
> 
> #!/bin/sh
> 
> #
> 
> #  File:  /etc/network/if-up.d/addroutes 
> 
> # 
> 
> # This file is executed by if-up (via run-parts) for every interface
> configured
> 
> # as auto in /etc/network/interfaces.  A success status must be
> returned to
> 
> # run-parts upon completion to prevent from reporting false negatives.
> Route
> 
> # add completion status is captured in $rtlog.
> 
> # 
> 
> # The route-up files created in /tmp indicate the interface that a
> route was 
> 
> # successfully added.
> 
> #
> 
>  
> 
> rtlog=/tmp/route-add.log
> 
>  
> 
> # Only add routes to the eth0 and eth1 interfaces 
> 
> if [[ $IFACE == eth? ]] ; then
> 
>     touch $rtlog
> 
>     
> 
>     #if defaultroute exists and route is not up read its contents to
> setup
> 
>     #the default route
> 
>     if [ -f /etc/defaultroute -a ! -f /tmp/default-route-up ] ; then
> 
>         while read MYGATE ; do
> 
>  
> 
>             # only create the tmp file if the route succeeds for this
> interface
> 
>             echo -e "Adding default route on ${IFACE}... \c" >>$rtlog
> 
>             route add default gw $MYGATE 2>>$rtlog && {
> 
>                 echo "$IFACE" >/tmp/default-route-up 
> 
>                 echo "done." >>$rtlog
> 
>             } || true
> 
>         done < /etc/defaultroute
> 
>     fi
> 
>  
> 
>     #if static routes were set by nfxsh read the route data
> 
>     if [ -f /etc/routes.ssc ] ; then
> 
>         while read NET MASK GW ; do 
> 
>  
> 
>             # if route is already up skip it
> 
>             if [ -f /tmp/${NET}-route-up ] ; then
> 
>                 continue
> 
>             fi
> 
>  
> 
>             # only create the tmp file if the route succeeds for this
> interface
> 
>             echo -e "Adding $NET route on ${IFACE}... \c" >>$rtlog
> 
>             route add -net $NET netmask $MASK gw $GW 2>>$rtlog && {
> 
>                 echo "$IFACE" >/tmp/${NET}-route-up
> 
>                 echo "done." >>$rtlog
> 
>             } || true
> 
>         done < /etc/routes.ssc
> 
>     fi
> 
> fi
> 
>  
> 
> Default Route:
> 
>  
> 
> After an install if you do not have a default route do the following:
> 
> From the SSC console, in nfxsh add a default route for the SSC or
> create /etc/defaultroute as shown:
> 
> /etc/defaultroute
> 
>             10.2.0.1
> 
>  
> 
> SSC Network Interfaces (single port example shown) Note that auto eth1
> is commented out.
> 
> /etc/network/interfaces 
> 
> # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
> 
> # /usr/share/doc/ifupdown/examples for more information.
> 
>  
> 
> # The loopback network interface
> 
> auto lo
> 
> iface lo inet loopback
> 
>  
> 
> # The primary network interface
> 
> auto eth0
> 
> iface eth0 inet static
> 
>   address 10.2.203.12
> 
>   netmask 255.255.0.0
> 
>  
> 
> # The secondary network interface
> 
> #auto eth1
> 
> iface eth1 inet static
> 
> # address not_configured
> 
> # netmask not_configured
> 
>  
> 
> If you are running a release older than submittal 19 it is recommended
> you save your cluster files and use flash_install to update your NAS
> Gateway without copying the configuration files. Restore your cluster
> files after the flash install and running the FTI.
> 
>  
> 
> A system copy init followed by system upgrade -s will efficiently
> upgrade an initialized flash card. It will copy the configuration data
> and files from the primary flash to the standby flash.
> 
>  
> 
> 
> 2.4.               HTTP and FTP use with the upgrade server
> 
> 
> An upgrade server is available that supports both FTP and HTTP
> download.
> 
> 
>  
> 
> If your system has DNS services configured you can use its hostname
> jump.onstor.lab. Because not all systems have DNS configured all URLs
> published in this document will use the IP address for
> jump.onstor.lab.
> 
> Upgrade example using HTTP URL:
> 
> g4r5 diag> system upgrade -f -s
> http://10.2.0.21/upgrade/R4.0.0.0CG-071608.tar.gz
> 
>  
> 
> If you need to use the FTP syntax with this server use the same paths
> as the previous server. Only the IP address has changed. Example of
> new server FTP URL:
> 
> Bobcat Optimized
> 
> ftp://upgrade@10.2.0.21/home/upgrade/R3.3.0.0BC-071608.tar.gz
> 
>  
> 
> Cougar Debug:
> 
> ftp://upgrade@10.2.0.21/R4.0.0.0CGDBG-071608.tar.gz
> 
>  
> 
> 
> 2.5.               Configuring the automounter and ypbind
> 
> 
> Remove /etc/defaultdomain if you have no desire to run the automounter
> and you are having ypbind problems. Production root file systems will
> not be configured with /etc/defaultdomain.
> 
>  
> 
> If you want to run the automounter and ypbind make sure these two
> configuration files agree with each other.
> 
> The correct settings for /etc/defualtdomain and /etc/yp.conf are as
> follows:
> 
>  
> 
> /etc/defaultdomain:
> 
>   agilestorage
> 
> /etc/yp.conf:
> 
>   domain agilestorage server 10.0.0.21
> 
>  
> 
> /etc/defaultdomain:
> 
>   onstorlab
> 
> /etc/yp.conf:
> 
>   domain onstorlab server 10.2.0.4
> 
>  
> 
> 
> 2.6.               How to enable DMALLOC monitoring
> 
> 
> This submittal is built with DMALLOC support. To turn on DMALLOC's
> built-in memory monitoring and analysis perform the following steps:
> 
> Edit /etc/default/onstor
> 
> Change line 4 from:
> 
> #export DMALLOC_OPTIONS=debug=0x4f4ed03,inter=100
> 
> Change line 4 to:
> 
> export DMALLOC_OPTIONS=debug=0x4f4ed03,inter=100
> 
> Reboot the system
> 
>  
> 
> 
> 3.       Source tree information
> 
> 
>  
> 
> 
> 3.1.               Perforce label 
> 
> 
> cougar-sub31
> 
>  
> 
> 
> 3.2.               Last EverON Perforce change list
> 
> 
> 3.2.1.        Submittal GA Candidate
> 
> 
> //depot/r400rel/...@30058
> 
>  
> 
> 
> 3.3.               Source tree location
> 
> 
> 3.3.1.         Submittal GA Candidate
> 
> 
> /n/Build-Trees/R4.0.0.0/ R4.0.0.0-071608-sub31/nfx-tree
> 
> /n/Build-Trees/R4.0.0.0/ R4.0.0.0-071608-sub31/linux
> 
> 
>  
> 
> 
> 3.4.               BSD distribution images for System W upgrade
> 
> 
> 3.4.1.        Submittal GA Candidate
> 
> 
>  
> 
> R3.3.0.0 images are here:
> 
> Cheetah optimized:
> 
> http://10.2.0.21/upgrade/R3.3.0.0-071608.tar.gz
> <http://10.2.0.21/upgrade/R3.3.0.0-071608.tar.gz> 
> 
> Cheetah debug:
> 
> http://10.2.0.21/upgrade/R3.3.0.0DBG-071608.tar.gz
> <http://10.2.0.21/upgrade/R3.3.0.0DBG-071608.tar.gz> 
> 
>  
> 
> Bobcat optimized:
> 
> http://10.2.0.21/upgrade/R3.3.0.0BC-071608.tar.gz
> <http://10.2.0.21/upgrade/R3.3.0.0BC-071608.tar.gz> 
> 
> Bobcat debug:
> 
> http://10.2.0.21/upgrade/R3.3.0.0BCDBG-071608.tar.gz
> <http://10.2.0.21/upgrade/R3.3.0.0BCDBG-071608.tar.gz> 
> 
>  
> 
> FTP example for 3.2.0.4 and older nfxsh programs that don't support
> http:
> 
> ftp://upgrade@10.2.0.21/home/upgrade/R3.3.0.0BC-071608.tar.gz
> 
>  
> 
>  
> 
> 
> 4.       System upgrade information
> 
> 
>  
> 
> 
> 4.1.               System upgrade information for EverON
> 
> 
>  
> 
> System upgrade on Linux systems uses wget to pull files from ftp or
> http servers. The syntax of wget is slightly different from ftp. You
> do not add the ftp user directory to the path specified on the
> command line. 
> 
>  
> 
> Use system upgrade as you would normally for subsequent updates.
> 
>  
> 
> 
> 4.2.               Location of Cougar distribution images
> 
> 
> 4.2.1.        Submittal GA Candidate
> 
> 
> Cougar debug:
> 
> http://10.2.0.21/upgrade/R4.0.0.0CGDBG-071608.tar.gz
> 
> Cougar optimized:
> 
> http://10.2.0.21/upgrade/R4.0.0.0CG-071608.tar.gz
> 
>  
> 
> FTP example for those who fear change:
> 
> ftp://upgrade@10.2.0.21/R4.0.0.0CG-071608.tar.gz
> 
>  
> 
> 
> 4.3.               Prom settings for compact flash boot
> 
> 
> Set your prom environment as follows: 
> 
> SSC-PROM> env view
> 
>       Current Environment Settings:
> 
>  
> 
>        autoload       = on         ( off on )
> 
>        autoreboot     = off        ( off on )
> 
>        load_src       = disk    ( disk network )
> 
>        load_opts      = mAt        ( m/s|A/a|d|t )
> 
>        boot_dev       = sda1        ( sda1 sdb1 sc1 )
> 
>        upgrade_prom   = yes        ( no yes )
> 
>        env_reset      = no         ( no yes )
> 
>        autolinkenable = f          (SP.0 enabled, SP.1 enabled, SP.2
> enabled, SP.3 enabled)
> 
>        hw_qt          = off        ( off on )
> 
>        hw_ft          = off        ( off on )
> 
>        hw_diag        = off        ( off on )
> 
>  
> 
> SSC PROM> env set autoload on
> 
> SSC PROM> env set autoreboot off
> 
> SSC PROM> env set load_src disk
> 
> SC PROM> env set boot_dev sda1
> 
>    Note: The upper compact flash slot (compact flash 0) is boot_dev =
> sda1. The lower compact flash slot (compact flash 1) is boot_dev =
> sdb1
> 
>  
> 
> 
> 5.       SSC PROM Upgrade instructions
> 
> 
> This procedure updates the SSC PROM. It is done while the system is
> down and from the SSC console.
> 
> Connect to your SSC console via a telnet session. (Find something else
> to do  if you don't know how to do this.)
> 
> Shut the system down from the NFX Shell:
> 
> -          nfxsh
> 
> -          system reboot -y
> 
> When the system starts rebooting type:
> 
> -          <ctrl> e
> 
> Upgrade the standard and recovery SSC PROMs
> 
> -          bsd rt add 10.0.0.0 255.255.0.0 10.2.0.1
> 
> -          bsd ip add fp0 <ip-address> 255.255.0.0 -  Use the
> ip-address of your cougar - 
> 
> -          prom upgrade 10.0.0.143 rel-proms/sibfimg_cg.bin
> 
> -          prom upgrade 10.0.0.143 rel-proms/sibyte_cg.bin
> 
>  
> 
> 
> 6.       Runtime PROM Upgrade instructions
> 
> 
> Close all rcon sessions you have open before you run this procedure.
> 
> This procedure upgrades the FP and TXRX PROM images from runtime.
> 
> -          Login as root
> 
> -          nfxsh
> 
> -          port show all - Note what links are up, you will need to
> re-enable the sp2.n interfaces at the end of this procedure.
> 
> -          prom upgrade files
> http://10.2.0.21/upgrade/PROM-1.0.7-CG.tar.gz
> 
> This will get the PROM files and place them in the /boot dir on CF 
> 
> -          prom upgrade standard
> 
> Takes about 5 minutes, system will reboot upon successful PROM
> upgrade 
> 
>  
> 
> After the system reboots upgrade the Recovery PROMs. The PROM
> distribution file is on the compact flash.
> 
> -          Login as root
> 
> -          nfxsh
> 
> -          port enable all - if needed - 
> 
> -          prom upgrade recovery
> 
> Takes about 1.5 minutes, system will reboot upon successful PROM
> upgrade
> 
>  
> 
> Due to a prom upgrade bug the ports are disabled and not re-enabled
> automatically. Your volumes are not visible to the virtual servers
> after the reboots. You need to manually enable the links by
> performing the following steps.
> 
> After the system reboots
> 
> -          Login is root
> 
> -          nfxsh
> 
> -          port enable all
> 
>  
> 
> 
> 7.       Restrictions/limitations in this submittal
> 
> 
> 7.1.               Restrictions in this submittal
> 
> 
> *         You must upgrade your systems with the latest firmware;
> follow the instructions in sections 5 and 6.
> 
> *         It is recommended you run eek on your volumes to test for
> corruption
> 
>  
> 
> 
> 7.2.               Restrictions from previous submittal that still
> apply to this submittal
> 
> 
> DMIP mirror sessions between cougar and cheetah will fail with:
> SANM_AG: no listening session.
> 
>  
> 
> You need to have your autoload and autoreboot settings on your TXRX
> and FP cores match your SSC settings.
> 
> *         For the SSC you need to be in the SSC console to set the
> prom enviroment
> 
> *         For the TXRX and FP you can use rcon  to set the prom
> environment
> 
>  
> 
> 
> 7.3.               Problems encountered during Acceptance Testing
> 
> 
> Ran into a problem introduced by change list 30021, 300334 created for
> defect TED00024701
> 
> Filed defect TED00024769 and delayed submittal 31 until a fix was
> submitted.
> 
> Problem description:
> 
> After installing submittal 31, one bobcat had its management volume
> disappear. A lun sho disk -t free did not show any free luns. After a
> while free luns did reappear. However the management volume was MIA. 
> 
> Elog snippet:
> 
> Jul 15 20:32:40 eng155 : 0:0:vsd:ERROR: vsd_mountVolProc : Aborting
> mount operation for VS 1; 1 volume(s) owned but only 0 found
> 
> Jul 15 20:32:43 eng155 : 0:0:spm:INFO: spm_pollAddDevice: Found
> dev[LSI__] wwn[0x0] lun[0] type[0] sid[0] size[20971392]
> 
> Running vol sho eng155-corevol I see the device name for the volume is
> missing the model number
> 
> LUN List
> 
> Idx   Device Name                       Size (MiB)
> 
> --------------------------------------------------
> 
> 1     LSI__                             10239.94
> 
> -------------------------------------------------
> 
> Correct device name is LSI_E4600A_R46_eng155_core
> 
>  
> 
> A scsi show all also displays the device incorrectly. 
> 
> 16    LSI__                                                    DISK
> INF-01-00         0     OPENED     0610
> 
>  
> 
> 
> 8.       Details of New Features introduced in submittal 12
> 
> 
> 8.1.               I/O Coalescing
> 
> 
> Coalescing is only enabled for user read and write.
> 
> Do not test diag commands
> 
> Do not use nfxsh to modify the file system defaults
> 
>  
> 
> 
> 8.2.               Root level storage command
> 
> 
> Usage: storage view dev stats -d
> 
> Output changed substantially; it only lists LUNS that are non-zero
> 
>  
> 
> 
> 8.3.               TXRX command: nfsperftest
> 
> 
> Run this using rcon to the ACPU. The options have changed, run without
> arguments to get online help.
> 
> You can specify volume names.
> 
> This exercises the whole system including the NCPU. 
> 
>  
> 
> 
> 8.4.               FC diag command: scsiadmin trace
> 
> 
> New option: sds sds 
> 
> This gives copious amount of output. It shows every SCSI descriptor.
> 
>  
> 
> 
> 8.5.               New Analytics
> 
> 
> A great deal of analytics have been added the SCSI code. Expect to see
> more asserts in SCSI code when the SCSI debug analytics are tripped.
> 
>  
> 
> 
> 9.       Requirements to boot from Compact Flash
> 
> 
> Booting from compact flash requires the latest prom release see
> sections 5 and 6 for instructions on how to upgrade your PROMs.
> 
> QA cougar systems should already be running the latest PROM revision
> as it was a requirement for previous submittals.
> 
>  
> 
> Booting from compact flash requires you to install 1 Gbyte Compact
> Flash cards into the upper and lower slots of your cougar. Run the
> flash_install.sh script from your NFS root per the instructions found
> here: http://wiki.onstor.net/wiki/Flash_initialization
> 
>  
> 
> Use the feature of flash_install.sh that copies the configuration
> files from the running OS to the compact flash.
> 
>  When you see:
> 
>      Is this an upgrade? If you answer yes the current configuration
> will be copied to the new flash [N] 
> 
> Answer 'Y' to copy your configuration information from the NFS root to
> your compact flash.
> 
>  
> 
> A system copy init followed by system upgrade -s will efficiently
> upgrade an initialized flash card. It will copy the configuration data
> and files from the primary flash to the standby flash.
> 
>  
> 
> 
> 10. New/Changed/Obsolete modules/binaries
> 
> 
> 10.1.            Changed in submittal 18
> 
> 
> Change 28776 reordered the startup of the SSC daemons. Clustering
> starts before sdm and evm, since both use clustering. Sdm now queries
> clustering at initialization rather than waiting 30 sec. Snmpd and asd
> are delayed until just before the start of sscccc.
> 
>  
> 
> 
> 10.2.           Introduced in submittal 2:
> 
> 
> Changes 27104 and 27105 remove the reference to the name "agile" from
> nearly everywhere.
> 
> It also changes the name and location of trace files and logs.
> 
>  
> 
> The elog is now in /var/log/onstor/messages
> 
> The trace files are stored in /var/onstor
> 
> Samba logs are in /var/log/onstor/samba
> 
>  
> 
> 
> 10.3.            Introduced in submittal 14:
> 
> 
> The cluster_contrl process was removed from /onstor/etc/pmtab and is
> now started by the cluster_server process. You should be able to kill
> any cluster_server or cluster_contrl process and all 3 will be
> restarted in the correct sequence.
> 
>  
> 
> 
> 11. Troubleshooting tips
> 
> 
> Turn elog level to info.
> 
> Watch elogs: Have elog display enable and watch elogs on ssc console,
> or run tail -f /var/log/onstor/messages
> 
>  
> 
> 
> 12. Special focus/concerns/additional testing
> 
> 
> Changes were added to support the scsi-3 Target Port Groups needed for
> vendors such as Fujitsu, Nexsan, IBM and Pillar.Try as many SAN
> vendors as possible, looking for device name issues, or missing luns.
> 
>  
> 
> 
> 13. Pre-submittal tests results
> 
> 
> 13.1.           Build verification test results
> 
> 
>  
> 
> Test run
> 
> Pass/Fail/Not run
> 
> Upgrade on cougar
> 
> Pass
> 
> NFS traffic (no jumbo frames)
> 
> Pass
> 
> CIFS traffic (no jumbo frames)
> 
> Pass
> 
> Failover
> 
> Not run
> 
>  
> 
>  
> 
> 
> 13.2.           Acceptance test results
> 
> Test Run
> 
> Pass/Fail/Not run
> 
> Snapshot 
> 
> Pass
> 
> Mirror 
> 
> Pass
> 
> Use of NCM for Configuration and Setup
> 
> N/A
> 
> NFS and CIFS Traffic
> 
> Pass 
> 
> Upgrade/Flash_install  on Cheetah and Bobcat
> 
> Not Tested
> 
> Smbtorture
> 
> Pass
> 
> Online eek
> 
> N/A
> 
> Quota reporting
> 
> N/A
> 
> FTI
> 
> Not tested
> 
> NDMP Backup/Restore
> 
> N/A
> 
>  
> 
