X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7811F.2E27BC73@onstor-exch02.onstor.net>; Tue, 17 Apr 2007 11:35:32 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7811F.2E27BC73"
Content-class: urn:content-classes:message
Subject: FW: Installation Issues
Date: Tue, 17 Apr 2007 11:35:32 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E034373A2@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Installation Issues
Thread-Index: AceAehf2xAdT6G14RwWj2IPJn0a4HAAAAAIwAABBwvAAADLMUAAAX89DAABgQDAAAWUmsAAcslBwAAnCBRA=
From: "Jay Michlin" <jay.michlin@onstor.com>
To: "dl-Software" <dl-software@onstor.com>
Cc: "Eric Crutchlow" <eric.crutchlow@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7811F.2E27BC73
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello all,
=20
The email below is background reading about some of the problems our
Porfessional Services team is seeing during installs and upgrades at
customer sites. Most of that is invisible to us most of the time. And in
the same way, most of our challenges in Software Development are
invisible to field people most of the time.=20
=20
We'll all benefit by understanding better what life is like in other
parts of the company, so I offer the email below for your interest.
There are no assignments or action items in it. Just information worth
seeing.
=20
jay
=20

________________________________

From: Eric Crutchlow=20
Sent: Tuesday, April 17, 2007 8:57 AM
To: Jay Michlin; Paul Hammer; Sandrine Boulanger; Ed Kwan
Cc: Caeli Collins
Subject: RE: Installation Issues



Jay,

=20

I appreciate your thoughts on the matter, and obviously I have not made
my case. Please allow me to do so now.

=20

Prior to Sudheesh's meeting, the field was encountering the problems we
have outline below (the installation issues list). From that meeting and
the subsequent meeting with your group, we have made strides to educate
and focus our efforts. The investment of time has produced the
installations issues list and help get several serious bugs addressed. I
think we would all agree that the time spent in these meetings were
productive and needed.

=20

But lets review were the fields' time has been spent. Two recent
examples will illustrate this well; BAE and Fandango.=20

=20

One year ago, we attempted to demo to BAE and the system failed. We lost
a sale (I have not been given the details, but if it would be helpful,
please let me know). A year later, BAE lets us do another demo. Scott
Moyer (our SE) went to BAE and attempted to install a two node cluster.
He hits the PM on initial config error and attempts to configure the
system anyway. He basically goes through four flash cards and now has no
way to continue the install. Bill Duffy and I are at a customer's site
in San Diego performing an install. Bill gets called away to help Scott.
Eventually, he cuts short his stay with me to immediately fly to
Philadelphia and help. The customer is wondering what is going on and is
getting ready to throw us out. Scott has wasted 8 hours. Bill now spends
two days to get everything working as well as make sure the customer
understands that the Bobcats are reliable and will work for them. Now
ONStor has invested 24 hours on a possible sale.

=20

Luckily, BAE is impressed with Bill's 'performance'. As fate would have
it, BAE's current system fail shortly thereafter and they decide to
purchase the systems ASAP. Bill helped with the migration and so far no
issues.=20

=20

A few weeks ago I installed Fandango with a two node cluster and no
issues. Last Thursday they contacted me and said that they changed their
network addresses and would like to update there Bobcat's. The reaction
to the fact that the only way they could do this was by resetting the
boxes was not well received. But I assured them that since they haven't
gone into production, this would not be a major problem and would only
take 1.5 hours. I first broke the cluster, upgraded to 2.2.2.2, and then
performed the sys config reset. I ran into the PM problem that Scott hit
at BAE. Rebooting didn't work and I executed a second sys config reset
which did. 1.5 turned into 4 hours. We left the systems that day setup
with no vservers except for the management ones. Later that night at
2am, there was a cpu crash (see issue #5). Now Fandango is waiting on us
to explain this before going live.=20

=20

And so with the two meetings we have had, we have created the list and
are addressing the issues. As outlined below, the future releases will
do a better job. But Delorean is a month away and ONStor must address
these issues in the current release. And we are. Again, these two short
meetings have helped us make strides.

=20

The GUI has always been an issue and one that I was working on with
Charissa prior to the meetings. When the field reported issues with PM
or the GUI, the response has been they were not reproducible. As such
the field became very frustrated and has not filed defects. This is
unacceptable. Charissa has been willing to work with me on this and is
making progress to resolve it. She is a great example of your suggestion
of ongoing engagements.=20

=20

But until the two meetings, this was the only ongoing engagement we had.

=20

We have not directly addressed the fields' view of the support
organization (CS, QA, Dev). We need to change that. The meetings were a
start and well worth the time.

=20

The field has also been told many times that items are WAD. My recent
experience with Bill (defect 18502) illustrates this point. WAD is being
touted too many times. This contributes to the 'mythology' of how our
systems work and serves no purpose. As I stated before, if something is
WAD, it must be documented and the documentation must be easily
accessible to a user. In my opinion, this is either in the SAG or GUI
documentation. Management needs to address this and communicate it to
the team. There should not be (cannot be) confusion on what WAD is for
any particular component of our systems. I do not underestimate the
challenge of this nor am I proposing the meetings I am requesting
directly address this.

=20

And so I put it to the team; by having two meeting to create the
installation issues list we have helped focus future development efforts
as outlined by Jay. We are also addressing the issues in the current
release (no resolutions as of yet, but as Jay has stated, everyone is
committed to fixing them). Prior to the two meetings, our method for
dealing with this was ongoing engagements. I believe this has not worked
and we need to change. I am only asking for one meeting for one-half
hour, every two weeks (my apologizes Jay if I mis-communicated this as a
weekly meeting). I will create an agenda and keep minutes to ensure the
meetings are organized and effective. Our goal will be to address the
issues and improve teamwork. More importantly, I propose that if we can
incorporate these effort into our other meetings and processes, we no
longer need this one.

=20

As I have illustrated with BAE and Fandango, we are already spending the
time and have lost/jeopardized sales because of it. Is meeting once
every two weeks not worth the investment?=20

Regards,=20

Eric Crutchlow=20
Professional Services Manager=20
t: 408-376-3113=20
f: 408-963-2409=20
m: 408-596-1155=20

________________________________

From: Eric Crutchlow
Sent: Mon 4/16/2007 3:53 PM
To: Paul Hammer; Sandrine Boulanger; Ed Kwan; Jay Michlin
Subject: Installation Issues

When: Occurs every 2 weeks on Thursday effective 4/19/2007 from 1:00 PM
to 1:30 PM (GMT-08:00) Pacific Time (US & Canada).

Where: TBD=20

*~*~*~*~*~*~*~*~*~*=20

I'm following up with the installation issues meeting we had a few weeks
ago to resolve the issues PS and the SE's are seeing in the field. The
meeting will be every two weeks and I will keep minutes with action
items. The goals are to resolve the current list (see below) and put
processes in place to deal with future installation/eval issues as part
of normal escalations. Once these two goals are reached, we can
determine if there is any further need for additional meetings.

The following is a list of issues we currently are addressing:=20

1) Prior to init config on a new nas, get errors. Reboot off of 2nd
flash and no problems.=20

2) Do init config 1st time. After reboot, the nas generates pm errors.
If you reboot, you get init config, but this time the nas remembers the
default route you entered the first time. 2nd reboot and everything is
fine. We also see this with config resets.

3) Upgrades from 1.3.3.x to 2.x seems to work fine, but when you try and
move the vs from the 1.3.3.x server to the 2.x, won't work. A cluster
show cluster on the 2.x nas reports the cluster name as 'na'.  You kill
ncmd on the 1.3.3.x nas  and now cluster name is right and you can move
vs.

4) System copy all. Do a compare and get errors. If you reboot the nas,
perform another copy all, compare works. We wonder if flash has space
issues.

5) New install of a two node cluster. One of the nodes will reboot with
a cpu crash. Just happened at an install Bill did yesterday.

6) An upgrade takes 15 - 20 minutes. Compare another 10 - 15. This takes
a lot of time, especially if you get an error and have to start over.
You can waste 1 - 1.5 hours this way.


------_=_NextPart_001_01C7811F.2E27BC73
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD><TITLE>Installation =
Issues</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3020" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType name=3D"country-region"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><o:SmartTagType=20
name=3D"City"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><o:SmartTagType=20
name=3D"place"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><o:SmartTagType=20
name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
font-face {
	FONT-FAMILY: Tahoma
}
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.emailstyle18 {
	FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; =
FONT-FAMILY: Arial; TEXT-DECORATION: none
}
SPAN.EmailStyle19 {
	FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; =
FONT-FAMILY: Arial; TEXT-DECORATION: none; mso-style-type: personal
}
SPAN.EmailStyle20 {
	FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; =
FONT-FAMILY: Arial; TEXT-DECORATION: none; mso-style-type: =
personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D090202918-17042007>Hello all,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D090202918-17042007></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D090202918-17042007>The email below is background reading about =
some of the=20
problems our Porfessional Services team is seeing during installs and =
upgrades=20
at customer sites. </SPAN></FONT><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D090202918-17042007>Most of that is invisible to us most of the =
time. And=20
in the same way, most of our challenges in Software Development are =
invisible to=20
field people most of the time. </SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D090202918-17042007><FONT face=3DArial color=3D#0000ff =
size=3D2>We'll=20
all benefit by understanding better what life is like in other parts of =
the=20
company, so I offer the email below for your interest. There are no =
assignments=20
or action items in it. Just information worth =
seeing.</FONT></SPAN></DIV>
<DIV><SPAN class=3D090202918-17042007><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D090202918-17042007><FONT face=3DArial color=3D#0000ff =

size=3D2>jay</FONT></SPAN></DIV>
<DIV><SPAN class=3D090202918-17042007></SPAN>&nbsp;</DIV>
<DIV><BR></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Eric Crutchlow =
<BR><B>Sent:</B> Tuesday,=20
April 17, 2007 8:57 AM<BR><B>To:</B> Jay Michlin; Paul Hammer; Sandrine=20
Boulanger; Ed Kwan<BR><B>Cc:</B> Caeli Collins<BR><B>Subject:</B> RE:=20
Installation Issues<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Jay,<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I appreciate your thoughts =
on the=20
matter, and obviously I have not made my case. Please allow me to do so=20
now.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Prior to Sudheesh&#8217;s =
meeting, the=20
field was encountering the problems we have outline below (the =
installation=20
issues list). From that meeting and the subsequent meeting with your =
group, we=20
have made strides to educate and focus our efforts. The investment of =
time has=20
produced the installations issues list and help get several serious bugs =

addressed. I think we would all agree that the time spent in these =
meetings were=20
productive and needed.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">But lets review were the =
fields&#8217;=20
time has been spent. Two recent examples will illustrate this well; BAE =
and=20
Fandango. <o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">One year ago, we attempted =
to demo=20
to BAE and the system failed. We lost a sale (I have not been given the =
details,=20
but if it would be helpful, please let me know). A year later, BAE lets =
us do=20
another demo. <st1:PersonName w:st=3D"on">Scott Moyer</st1:PersonName> =
(our SE)=20
went to BAE and attempted to install a two node cluster. He hits the PM =
on=20
initial config error and attempts to configure the system anyway. He =
basically=20
goes through four flash cards and now has no way to continue the =
install.=20
<st1:PersonName w:st=3D"on">Bill Duffy</st1:PersonName> and I are at a =
customer&#8217;s=20
site in <st1:City w:st=3D"on"><st1:place w:st=3D"on">San=20
Diego</st1:place></st1:City> performing an install. Bill gets called =
away to=20
help Scott. Eventually, he cuts short his stay with me to immediately =
fly to=20
<st1:City w:st=3D"on"><st1:place =
w:st=3D"on">Philadelphia</st1:place></st1:City> and=20
help. The customer is wondering what is going on and is getting ready to =
throw=20
us out. Scott has wasted 8 hours. Bill now spends two days to get =
everything=20
working as well as make sure the customer understands that the Bobcats =
are=20
reliable and will work for them. Now ONStor has invested 24 hours on a =
possible=20
sale.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Luckily, BAE is impressed =
with=20
Bill&#8217;s &#8216;performance&#8217;. As fate would have it, =
BAE&#8217;s current system fail shortly=20
thereafter and they decide to purchase the systems ASAP. Bill helped =
with the=20
migration and so far no issues. <o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">A few weeks ago I =
installed Fandango=20
with a two node cluster and no issues. Last Thursday they contacted me =
and said=20
that they changed their network addresses and would like to update there =

Bobcat&#8217;s. The reaction to the fact that the only way they could do =
this was by=20
resetting the boxes was not well received. But I assured them that since =
they=20
haven&#8217;t gone into production, this would not be a major problem =
and would only=20
take 1.5 hours. I first broke the cluster, upgraded to 2.2.2.2, and then =

performed the sys config reset. I ran into the PM problem that Scott hit =
at BAE.=20
Rebooting didn&#8217;t work and I executed a second sys config reset =
which did. 1.5=20
turned into 4 hours. We left the systems that day setup with no vservers =
except=20
for the management ones. Later that night at 2am, there was a cpu crash =
(see=20
issue #5). Now Fandango is waiting on us to explain this before going =
live.=20
<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">And so with the two =
meetings we have=20
had, we have created the list and are addressing the issues. As outlined =
below,=20
the future releases will do a better job. But Delorean is a month away =
and=20
ONStor must address these issues in the current release. And we are. =
Again,=20
these two short meetings have helped us make=20
strides.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The GUI has always been an =
issue and=20
one that I was working on with Charissa prior to the meetings. When the =
field=20
reported issues with PM or the GUI, the response has been they were not=20
reproducible. As such the field became very frustrated and has not filed =

defects. This is unacceptable. Charissa has been willing to work with me =
on this=20
and is making progress to resolve it. She is a great example of your =
suggestion=20
of ongoing engagements. <o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">But until the two =
meetings, this was=20
the only ongoing engagement we had.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">We have not directly =
addressed the=20
fields&#8217; view of the support organization (CS, QA, Dev). We need to =
change that.=20
The meetings were a start and well worth the =
time.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The field has also been =
told many=20
times that items are WAD. My recent experience with Bill (defect 18502)=20
illustrates this point. WAD is being touted too many times. This =
contributes to=20
the &#8216;mythology&#8217; of how our systems work and serves no =
purpose. As I stated=20
before, if something is WAD, it must be documented and the documentation =
must be=20
easily accessible to a user. In my opinion, this is either in the SAG or =
GUI=20
documentation. Management needs to address this and communicate it to =
the team.=20
There should not be (cannot be) confusion on what WAD is for any =
particular=20
component of our systems. I do not underestimate the challenge of this =
nor am I=20
proposing the meetings I am requesting directly address=20
this.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">And so I put it to the =
team; by=20
having two meeting to create the installation issues list we have helped =
focus=20
future development efforts as outlined by Jay. We are also addressing =
the issues=20
in the current release (no resolutions as of yet, but as Jay has stated, =

everyone is committed to fixing them). Prior to the two meetings, our =
method for=20
dealing with this was ongoing engagements. I believe this has not worked =
and we=20
need to change. I am only asking for one meeting for one-half hour, =
every two=20
weeks (my apologizes Jay if I mis-communicated this as a weekly =
meeting). I will=20
create an agenda and keep minutes to ensure the meetings are organized =
and=20
effective. Our goal will be to address the issues and improve teamwork. =
More=20
importantly, I propose that if we can incorporate these effort into our =
other=20
meetings and processes, we no longer need this =
one.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">As I have illustrated with =
BAE and=20
Fandango, we are already spending the time and have lost/jeopardized =
sales=20
because of it. Is meeting once every two weeks not worth the investment? =

<o:p></o:p></SPAN></FONT></P>
<DIV>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Regards,</SPAN></FONT>=20
<o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Eric =
Crutchlow</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Professional Services=20
Manager</SPAN></FONT> <BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">t: =
408-376-3113</SPAN></FONT>=20
<BR><FONT face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">f:=20
408-963-2409</SPAN></FONT> <BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">m: =
408-596-1155</SPAN></FONT>=20
<o:p></o:p></P></DIV>
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =

face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV></DIV>
<DIV>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma"> Eric=20
Crutchlow<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Mon =
4/16/2007=20
3:53 PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Paul =
Hammer;=20
Sandrine Boulanger; Ed Kwan; Jay Michlin<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Installation=20
Issues</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">When: Occurs every 2 weeks =
on=20
Thursday effective 4/19/2007 from 1:00 PM to 1:30 PM (GMT-08:00) Pacific =
Time=20
(US &amp; <st1:place w:st=3D"on"><st1:country-region=20
w:st=3D"on">Canada</st1:country-region></st1:place>).</SPAN></FONT><o:p><=
/o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Where: TBD</SPAN></FONT>=20
<o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">*~*~*~*~*~*~*~*~*~*</SPAN></FONT>=20
<o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">I'm=20
following up with the installation issues meeting we had a few weeks ago =
to=20
resolve the issues PS and the SE's are seeing in the field. The meeting =
will be=20
every two weeks and I will keep minutes with action items. The goals are =
to=20
resolve the current list (see below) and put processes in place to deal =
with=20
future installation/eval issues as part of normal escalations. Once =
these two=20
goals are reached, we can determine if there is any further need for =
additional=20
meetings.</SPAN></FONT><o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">The=20
following is a list of issues we currently are addressing:</SPAN></FONT> =

<o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">1)=20
Prior to init config on a new nas, get errors. Reboot off of 2nd flash =
and no=20
problems.</SPAN></FONT> <o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">2)=20
Do init config 1st time. After reboot, the nas generates pm errors. If =
you=20
reboot, you get init config, but this time the nas remembers the default =
route=20
you entered the first time. 2nd reboot and everything is fine. We also =
see this=20
with config resets.</SPAN></FONT><o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">3)=20
Upgrades from 1.3.3.x to 2.x seems to work fine, but when you try and =
move the=20
vs from the 1.3.3.x server to the 2.x, won&#8217;t work. A cluster show =
cluster on the=20
2.x nas reports the cluster name as &#8216;na&#8217;.&nbsp; You kill =
ncmd on the 1.3.3.x=20
nas&nbsp; and now cluster name is right and you can move=20
vs.</SPAN></FONT><o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">4)=20
System copy all. Do a compare and get errors. If you reboot the nas, =
perform=20
another copy all, compare works. We wonder if flash has space=20
issues.</SPAN></FONT><o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">5)=20
New install of a two node cluster. One of the nodes will reboot with a =
cpu=20
crash. Just happened at an install Bill did=20
yesterday.</SPAN></FONT><o:p></o:p></P>
<P><FONT face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">6)=20
An upgrade takes 15</SPAN></FONT> <FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">&#8211;</SPAN></FONT><FONT face=3DArial=20
size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"> 20 =
minutes. Compare=20
another 10</SPAN></FONT> <FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">&#8211;</SPAN></FONT><FONT face=3DArial=20
size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"> 15. This =
takes a lot=20
of time, especially if you get an error and have to start over. You can =
waste=20
1</SPAN></FONT> <FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">&#8211;</SPAN></FONT><FONT face=3DArial=20
size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"> 1.5 hours =
this=20
way.</SPAN></FONT><o:p></o:p></P></DIV></DIV></DIV></BODY></HTML>

------_=_NextPart_001_01C7811F.2E27BC73--
