X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C88D29.74D994F0@onstor-exch02.onstor.net>; Sun, 23 Mar 2008 14:04:17 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Cougar FTI + bobcat Migration code ready for in-branch testing
Date: Sun, 23 Mar 2008 14:04:16 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E08FC3988@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E042F0132@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Cougar FTI + bobcat Migration code ready for in-branch testing
Thread-Index: AciMY6oXp9yk5Qd9SWG27Qnd4iMlVwAxG34Q
References: <BB375AF679D4A34E9CA8DFA650E2B04E042F0132@onstor-exch02.onstor.net>
From: "Manohar Divate" <manohar.divate@onstor.com>
To: "Larry Scheer" <larry.scheer@onstor.com>,
	"Vikas Saini" <vikas.saini@onstor.com>,
	"Sudharsan Srinivasan" <sudharsan@onstor.com>
Cc: "Tim Gardner" <tim.gardner@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>,
	"Sripal Surendiran (HCL)" <sripal.surendiran@onstor.com>,
	"Narain Ramadass" <narain.ramadass@onstor.com>,
	"John Rogers" <john.rogers@onstor.com>,
	"Paul Hammer" <paul.hammer@onstor.com>,
	"Sandrine Boulanger" <sandrine.boulanger@onstor.com>

Larry=20

Step no. 2 is expected per migration document but step no. 3 should NOT
Fail. (It is supposed to copy bobcat configuration from secondary
flash).
Then this build is NO GO.

-Manny


-----Original Message-----
From: Larry Scheer=20
Sent: Saturday, March 22, 2008 3:06 PM
To: Manohar Divate; Vikas Saini; Sudharsan Srinivasan
Cc: Tim Gardner; Andy Sharp; Sripal Surendiran (HCL); Narain Ramadass;
John Rogers; Paul Hammer; Sandrine Boulanger
Subject: Cougar FTI + bobcat Migration code ready for in-branch testing

I used system upgrade -s to install the cougar debug image on g4r5 to
test the basic installation.=20
I discovered the following issues with this build:

1. The cg_fti branch was not updated with all of the changes from the
dev branch the descr-$(PROD) files are not the latest. This introduced a
regression with ypbind fails to start if your root file system was
previously configured to run with ypbind on the SSC (many defects filed
agains this)

2. Although I had a fully configured system when I started nfxsh after
the installion and reboot I encountered the FTI screen in the CLI.=20

3. Selecting the option to copy the configuration from the secondary
flash failed.

4. Going through the FTI options via the CLI I needed to reenter all of
the original data.The system was already  configured with the proper
data however the FTI had no default information to choose from requiring
me to type in all the  information.

After I entered all the data the system rebooted and came up
sucecssfully. I was able to start nfxsh, see my volumes and virutal
servers.

Source code is located here:

/n/Build-Trees/R4.0.0.0/R4.0.0.0-FTI-032208

Installable Images are here:

Cougar Debug:
ftp://upgrade:password@10.2.0.2/R4.0.0.0-FTICGDBG-032208.tar.gz

Cougar Opt:
ftp://upgrade:password@10.2.0.2/R4.0.0.0-FTICG-032208.tar.gz

Just in case you need to check something on the other platforms:

Bobcat Debug:
ftp://upgrade:password@10.2.0.2/R3.3.0.0-FTIBCDBG-032208.tar.gz

Bobcat Opt:
ftp://upgrade:password@10.2.0.2/R3.3.0.0-FTIBC-032208.tar.gz

Cheetah Debug:
ftp://upgrade:password@10.2.0.2/R3.3.0.0-FTIDBG-032208.tar.gz

Cheetah Opt:
ftp://upgrade:password@10.2.0.2/R3.3.0.0-FTI-032208.tar.gz

























