X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7F0C1.7E5AD624@onstor-exch02.onstor.net>; Thu, 6 Sep 2007 12:07:04 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7F0C1.7E5AD624"
Content-class: urn:content-classes:message
Subject: RE: 32 vsvr's
Date: Thu, 6 Sep 2007 12:07:04 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E03E9A318@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E056BD34B@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: 32 vsvr's
Thread-Index: AcfwvLSk2SFF+Ct9SaGFc50RYBnF8QAA8qTw
From: "Chris Vandever" <chris.vandever@onstor.com>
To: "Brian DeForest" <brian.deforest@onstor.com>,
	"dl-Software" <dl-software@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7F0C1.7E5AD624
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Contrary to my earlier statements, the code claims to support 32 vsvrs
NOT including mgmt vsvrs, if you believe it.  This means that indeed you
should still be able to add gateways to the cluster even when you
already have the maximum number of vsvrs:

/* Starting release 1.2, the max number of VS in a cluster is limited
 * to 32. This number does not include the mgmt VS that is created
 * per filer.
 */
#define VS_MAX_VS_IN_CLUSTER_LIMIT_FROM_R_1_2   32

Most of the code uses a larger value for fixed length arrays, although
who knows whether all of the code uses this value or their own define or
a hard-coded value:

/* Maximum number of VS allowed in the cluster. Note: ID # 0 is reserved
as
 * INVALID. Hence for a 8 bit value 256-1 is the most that we can
assign.
 */
#define VS_MAX_VS_IN_CLUSTER 255

ChrisV
_____________________________________________
From: Brian DeForest=20
Sent: Thursday, September 06, 2007 12:33 PM
To: dl-Software
Subject: 32 vsvr's

There are several Zonda bugs (SSC app core dumps and processor crashes)
that were tested using 32 vsvr's AND the mgmt vsvr. =20

First question is whether our 32 vsvr limit includes the mgmt vsvr, or
should it be 31 + the mgmt vsvr?  =20

Secondly, and this is more of a heads up, it seems likely that various
apps will properly handle >32 vsvrs while others might march off the end
of arrays, resulting in memory or stack corruptions (as is the case in
some of the defects where the stack looks garbled).

Brian


------_=_NextPart_001_01C7F0C1.7E5AD624
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: 32 vsvr's</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Contrary to my earlier statements, the =
code</FONT></SPAN><SPAN LANG=3D"en-us"><I></I></SPAN><SPAN =
LANG=3D"en-us"><I> <FONT SIZE=3D2 =
FACE=3D"Arial">claims</FONT></I></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial"> to support 32 =
vsvrs</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> =
<FONT SIZE=3D2 FACE=3D"Arial">NOT including mgmt =
vsvrs</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">, if you believe =
it</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Arial">.&nbsp; This means that indeed you should still =
be able to add gateways to the cluster even when you already have the =
maximum number of vsvrs</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">:</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Lucida =
Console">/* Starting release 1.2, the max number of VS in a cluster is =
limited</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Lucida =
Console">&nbsp;* to 32. This number does not include the mgmt VS that is =
created</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Lucida =
Console">&nbsp;* per filer.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Lucida =
Console">&nbsp;*/</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Lucida =
Console">#define VS_MAX_VS_IN_CLUSTER_LIMIT_FROM_R_1_2&nbsp;&nbsp; =
32</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Most =
of the code uses a larger</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">valu</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">e for fixed length arrays</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">, although who knows whether all of the code uses this =
value or their own define or a hard-coded value</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">:</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Lucida =
Console">/* Maximum number of VS allowed in the cluster. Note: =
ID</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
SIZE=3D2 FACE=3D"Lucida Console">#</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Lucida =
Console"> 0 is reserved as</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Lucida =
Console">&nbsp;* INVALID. Hence for a 8 bit value 256-1 is the most that =
we can assign.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Lucida =
Console">&nbsp;*/</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Lucida =
Console">#define VS_MAX_VS_IN_CLUSTER 255</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">ChrisV</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Brian DeForest<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Thursday, September 06, =
2007 12:33 PM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> dl-Software<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> 32 vsvr's</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">There =
are several Zonda bugs (SSC app core dumps and processor crashes) that =
were tested using 32 vsvr&#8217;s AND the mgmt vsvr.&nbsp; =
</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">First =
question is whether our 32 vsvr limit includes the mgmt vsvr, or should =
it be 31 + the mgmt vsvr?&nbsp;&nbsp; </FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Secondly, and this is more of a heads up, it seems likely =
that various apps will properly handle &gt;32 vsvrs while others might =
march off the end of arrays, resulting in memory or stack corruptions =
(as is the case in some of the defects where the stack looks =
garbled).</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Brian</FONT></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C7F0C1.7E5AD624--
