X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C88C68.E240F4C8@onstor-exch02.onstor.net>; Sat, 22 Mar 2008 15:05:48 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C88C68.E240F4C8"
Content-class: urn:content-classes:message
Subject: Cougar FTI + bobcat Migration code ready for in-branch testing
Date: Sat, 22 Mar 2008 15:05:48 -0700
Message-ID: <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: AciMY6oXp9yk5Qd9SWG27Qnd4iMlVw==
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Manohar Divate" <manohar.divate@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>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C88C68.E240F4C8
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

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


























------_=_NextPart_001_01C88C68.E240F4C8
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>Cougar FTI + bobcat Migration code ready for in-branch =
testing</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>I used system upgrade -s to install the cougar debug =
image on g4r5 to test the basic installation.<BR>
I discovered the following issues with this build:<BR>
<BR>
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)<BR>
<BR>
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.<BR>
<BR>
3. Selecting the option to copy the configuration from the secondary =
flash failed.<BR>
<BR>
4. Going through the FTI options via the CLI I needed to reenter all of =
the original data.The system was already&nbsp; configured with the =
proper data however the FTI had no default information to choose from =
requiring me to type in all the&nbsp; information.<BR>
<BR>
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.<BR>
<BR>
Source code is located here:<BR>
<BR>
/n/Build-Trees/R4.0.0.0/R4.0.0.0-FTI-032208<BR>
<BR>
Installable Images are here:<BR>
<BR>
Cougar Debug:<BR>
<A =
HREF=3D"ftp://upgrade:password@10.2.0.2/R4.0.0.0-FTICGDBG-032208.tar.gz">=
ftp://upgrade:password@10.2.0.2/R4.0.0.0-FTICGDBG-032208.tar.gz</A><BR>
<BR>
Cougar Opt:<BR>
<A =
HREF=3D"ftp://upgrade:password@10.2.0.2/R4.0.0.0-FTICG-032208.tar.gz">ftp=
://upgrade:password@10.2.0.2/R4.0.0.0-FTICG-032208.tar.gz</A><BR>
<BR>
Just in case you need to check something on the other platforms:<BR>
<BR>
Bobcat Debug:<BR>
<A =
HREF=3D"ftp://upgrade:password@10.2.0.2/R3.3.0.0-FTIBCDBG-032208.tar.gz">=
ftp://upgrade:password@10.2.0.2/R3.3.0.0-FTIBCDBG-032208.tar.gz</A><BR>
<BR>
Bobcat Opt:<BR>
<A =
HREF=3D"ftp://upgrade:password@10.2.0.2/R3.3.0.0-FTIBC-032208.tar.gz">ftp=
://upgrade:password@10.2.0.2/R3.3.0.0-FTIBC-032208.tar.gz</A><BR>
<BR>
Cheetah Debug:<BR>
<A =
HREF=3D"ftp://upgrade:password@10.2.0.2/R3.3.0.0-FTIDBG-032208.tar.gz">ft=
p://upgrade:password@10.2.0.2/R3.3.0.0-FTIDBG-032208.tar.gz</A><BR>
<BR>
Cheetah Opt:<BR>
<A =
HREF=3D"ftp://upgrade:password@10.2.0.2/R3.3.0.0-FTI-032208.tar.gz">ftp:/=
/upgrade:password@10.2.0.2/R3.3.0.0-FTI-032208.tar.gz</A><BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C88C68.E240F4C8--
