X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8C019.CBE46E68@onstor-exch02.onstor.net>; Tue, 27 May 2008 09:50:40 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8C019.CBE46E68"
Content-class: urn:content-classes:message
Subject: RE: Bobcat to Cougar migration strategy related questions
Date: Tue, 27 May 2008 09:50:40 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E09CB80EB@onstor-exch02.onstor.net>
In-Reply-To: <483BF128.5070703@onstor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Bobcat to Cougar migration strategy related questions
Thread-Index: Aci/7UkeO0jgJXIbTcqoW47oxfBSdwAK7wKw
From: "Sandrine Boulanger" <sandrine.boulanger@onstor.com>
To: "Sripal Surendiran (HCL)" <sripal.surendiran@onstor.com>,
	"Brian Stark" <brian.stark@onstor.com>
Cc: "Narain Ramadass" <narain.ramadass@onstor.com>,
	"Tim Gardner" <tim.gardner@onstor.com>,
	"Dennis Arellano" <dennis.arellano@onstor.com>,
	"Sudharsan Srinivasan" <sudharsan@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8C019.CBE46E68
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

You can always find a solution to delete the old mgmt vsvr and volumes.
It's better if we find a solution with admin commands rather than
root/diag commands, but there's always a way to do it.

If you don't zone the luns seen by mgmt and core volumes, they won't
show up.

Then you can use, in the mgmt vsvr context:

1.    System delete corevolume NAME force

2.    Vsvr delete force mountedVol [only if mgmt volume still appears in
the mounted list of the vsvr)

3.    Vsvr delete force volume MGMT_VOLUME_NAME

4.    Vsvr delete

To be able to recognize the old from the new mgmt vsvr, there should be
a note to save the mgmt vsvr name before you shut down your
cheetah/bobcat cluster.

=20

-----Original Message-----
From: Sripal Surendiran (HCL)=20
Sent: Tuesday, May 27, 2008 4:32 AM
To: Brian Stark
Cc: Narain Ramadass; Tim Gardner; Dennis Arellano; Sudharsan Srinivasan;
Andy Sharp; Sandrine Boulanger
Subject: Re: Bobcat to Cougar migration strategy related questions

=20

Brian,

=20

If we don't change the MAC address, we will end up with system having=20

two management VSVR: the one which was already created using old MAC=20

address and the other one created with new MAC address.

=20

I see certain problems in this scenario:

=20

1. The old mgmt VSVR will own mgmt volume and core volume.

2. The old mgmt VSVR will not be the active mgmt VSVR. Hence we need to=20

delete the mgmt & core volume and create it in a new mgmt VSVR.

3. nfxsh will allow the user to delete old mgmt volume. But it will not=20

allow the user to delete core volume, since old mgmt VSVR is not a=20

active mgmt VSVR now.

4. We cannot delete the old mgmt VSVR, since it still owns volume.

=20

We will end up in the same scenario for down slot in case of =20

cluster-in-a-box, even if you change the MAC address for upper slot as=20

that of the Bobcat . Please correct me if I went wrong somewhere.

=20

Thanks,

Sripal.

=20

Brian Stark wrote:

> Hi Narain,

>=20

> The original plan was to migrate the MAC address from the
Cheetah/Bobcat

> to the chassis level MAC address on the Cougar, which would then

> preserve zoning on the top slot but not the bottom slot. =20

>=20

> However, it was decided in a core team meeting that having to rezone
for

> one slot but not another was too confusing for a customer.  Rather
than

> doing this, we will not document the migration of MAC address of

> Bobcat/Cougar to the chassis MAC on Cougar, which therefore means both

> slots will require rezoning.  The same applies for single node

> migrations since we won't be changing the Cougar MAC address that's

> assigned at the factory.

>=20

> Each slot uses the chassis level MAC address as its base MAC address
as

> follows:

>=20

> Top slot base MAC -- chassis MAC + 0x00

> Bottom slot base MAC -- chassis MAC + 0x80

>=20

> The formula to then derive the MAC/WWN for the ports from the slot
base

> MAC address is the same as we've used on Bobcat.

>=20

>=20

> Thanks,

> Brian

>=20

>=20

>  =20

>> -----Original Message-----

>> From: Narain Ramadass=20

>> Sent: Wednesday, May 21, 2008 3:19 PM

>> To: Sripal Surendiran (HCL); Brian Stark

>> Cc: Tim Gardner; Dennis Arellano; Sudharsan Srinivasan

>> Subject: Bobcat to Cougar migration strategy related questions

>>=20

>> Brian,

>>=20

>> I thought you mentioned in the Cougar meeting last week that=20

>> customers migrating from a Bobcat or Cheetah cluster to a=20

>> Cougar cluster-in-a-box would be asked to change the zoning=20

>> and LUN masking settings in the SAN for both slots. While=20

>> preparing the migration strategy document we had assumed that=20

>> the SAN changes would only made for the bottom slot Cougar=20

>> and that the top slot Cougar would take the MAC address from=20

>> one of the Bobcats or Cheetahs that it was replacing.

>>=20

>> Sripal is working on the migration document and needs the=20

>> authoritative word on this so he can update it before passing=20

>> it onto Dennis for inclusion in Cougar documentation. Can you=20

>> please clarify?=20

>>=20

>> Further - for customers migrating from a single node BC or CH=20

>> - would the SAN changes still be mandated or would they be=20

>> requested to change the MAC address on the CG from the seep?

>>=20

>> Sripal,

>>=20

>> Tim mentioned today that we would additionally require a=20

>> table in the migration document that defines how the sc, sp=20

>> and fp port addresses are created from the MAC address. Pls=20

>> keep in mind that since this will be a Cougar in a box - the=20

>> formulae are required (and are different) for the top and=20

>> bottom slots.

>>=20

>> Pls let us know if there are any other issues that require=20

>> attention before the document can be handed over to Dennis.

>>=20

>> Thanx,

>> Narain.=20

>>    =20

=20


------_=_NextPart_001_01C8C019.CBE46E68
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:navy;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 77.95pt 1.0in 77.95pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:932856809;
	mso-list-type:hybrid;
	mso-list-template-ids:-490077420 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dnavy>

<div class=3DSection1>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>You can always find a solution to delete the old mgmt vsvr and =
volumes.
It's better if we find a solution with admin commands rather than =
root/diag
commands, but there's always a way to do =
it.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>If you don't zone the luns seen by mgmt and core volumes, they =
won't
show up.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Then you can use, in the mgmt vsvr =
context:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'><span
style=3D'mso-list:Ignore'>1.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]>System
delete corevolume NAME force<o:p></o:p></p>

<p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'><span
style=3D'mso-list:Ignore'>2.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]>Vsvr
delete force mountedVol [only if mgmt volume still appears in the =
mounted list
of the vsvr)<o:p></o:p></p>

<p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'><span
style=3D'mso-list:Ignore'>3.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]>Vsvr
delete force volume MGMT_VOLUME_NAME<o:p></o:p></p>

<p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'><span
style=3D'mso-list:Ignore'>4.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]>Vsvr
delete<o:p></o:p></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>To be able to recognize the old from the new mgmt vsvr, there =
should be
a note to save the mgmt vsvr name before you shut down your =
cheetah/bobcat
cluster.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>-----Original Message-----<br>
From: Sripal Surendiran (HCL) <br>
Sent: Tuesday, May 27, 2008 4:32 AM<br>
To: Brian Stark<br>
Cc: Narain Ramadass; Tim Gardner; Dennis Arellano; <st1:PersonName =
w:st=3D"on">Sudharsan
 Srinivasan</st1:PersonName>; <st1:PersonName w:st=3D"on">Andy =
Sharp</st1:PersonName>;
Sandrine Boulanger<br>
Subject: Re: Bobcat to Cougar migration strategy related =
questions</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Brian,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>If we don't change the MAC address, we will end up with system =
having <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>two management VSVR: the one which was already created using old =
MAC <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>address and the other one created with new MAC =
address.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>I see certain problems in this =
scenario:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>1. The old mgmt VSVR will own mgmt volume and core =
volume.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>2. The old mgmt VSVR will not be the active mgmt VSVR. Hence we =
need to
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>delete the mgmt &amp; core volume and create it in a new mgmt =
VSVR.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>3. nfxsh will allow the user to delete old mgmt volume. But it =
will not
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>allow the user to delete core volume, since old mgmt VSVR is not =
a <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>active mgmt VSVR now.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>4. We cannot delete the old mgmt VSVR, since it still owns =
volume.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>We will end up in the same scenario for down slot in case =
of&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>cluster-in-a-box, even if you change the MAC address for upper =
slot as <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>that of the Bobcat . Please correct me if I went wrong =
somewhere.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Sripal.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Brian Stark wrote:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Hi Narain,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;<o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; The original plan was to migrate the MAC address from the
Cheetah/Bobcat<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; to the chassis level MAC address on the Cougar, which would =
then<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; preserve zoning on the top slot but not the bottom =
slot.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;<o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; However, it was decided in a core team meeting that having =
to
rezone for<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; one slot but not another was too confusing for a =
customer.&nbsp; Rather
than<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; doing this, we will not document the migration of MAC =
address of<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Bobcat/Cougar to the chassis MAC on Cougar, which therefore =
means
both<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; slots will require rezoning.&nbsp; The same applies for =
single node<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; migrations since we won't be changing the Cougar MAC =
address
that's<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; assigned at the factory.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;<o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Each slot uses the chassis level MAC address as its base =
MAC
address as<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; follows:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;<o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Top slot base MAC -- chassis MAC + =
0x00<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Bottom slot base MAC -- chassis MAC + =
0x80<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;<o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; The formula to then derive the MAC/WWN for the ports from =
the slot
base<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; MAC address is the same as we've used on =
Bobcat.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;<o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;<o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Brian<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;<o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;<o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&nbsp;&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; -----Original Message-----<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; From: Narain Ramadass <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; Sent: Wednesday, May 21, 2008 3:19 =
PM<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; To: Sripal Surendiran (HCL); Brian =
Stark<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; Cc: Tim Gardner; Dennis Arellano; <st1:PersonName =
w:st=3D"on">Sudharsan
 Srinivasan</st1:PersonName><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; Subject: Bobcat to Cougar migration strategy related =
questions<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt;<o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; Brian,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt;<o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; I thought you mentioned in the Cougar meeting last week =
that <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; customers migrating from a Bobcat or Cheetah cluster to =
a <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; Cougar cluster-in-a-box would be asked to change the =
zoning <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; and LUN masking settings in the SAN for both slots. =
While <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; preparing the migration strategy document we had =
assumed that <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; the SAN changes would only made for the bottom slot =
Cougar <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; and that the top slot Cougar would take the MAC address =
from <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; one of the Bobcats or Cheetahs that it was =
replacing.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt;<o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; Sripal is working on the migration document and needs =
the <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; authoritative word on this so he can update it before =
passing <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; it onto Dennis for inclusion in Cougar documentation. =
Can you <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; please clarify? <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt;<o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; Further - for customers migrating from a single node BC =
or CH <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; - would the SAN changes still be mandated or would they =
be <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; requested to change the MAC address on the CG from the =
seep?<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt;<o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; Sripal,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt;<o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; Tim mentioned today that we would additionally require =
a <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; table in the migration document that defines how the =
sc, sp <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; and fp port addresses are created from the MAC address. =
Pls <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; keep in mind that since this will be a Cougar in a box =
- the <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; formulae are required (and are different) for the top =
and <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; bottom slots.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt;<o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; Pls let us know if there are any other issues that =
require <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; attention before the document can be handed over to =
Dennis.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt;<o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; Thanx,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt; Narain. <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C8C019.CBE46E68--
