AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080716120401.57f50576@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<andy.sharp@onstor.com>,<sripal.surendiran@onstor.com>,<john.keiffer@onstor.com>,<vikas.saini@onstor.com>,<sudharsan@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#mh/Mailbox/sent	0	20080715082917.0bd922d6@ripper.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 16 Jul 2008 12:04:18 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Andrew Sharp <andy.sharp@onstor.com>
Cc: Sripal <sripal.surendiran@onstor.com>, john.keiffer@onstor.com,
 vikas.saini@onstor.com, Sudharsan Srinivasan <sudharsan@onstor.com>
Subject: Re: Defect  TED00024695 NCM FTI - no easy way to know which node of
 a Cougar-in-a-box you are about to configure Assigned
Message-ID: <20080716120418.193b9d97@ripper.onstor.net>
In-Reply-To: <20080715082917.0bd922d6@ripper.onstor.net>
References: <ONSTOR-EXCH01khsCxo00002b0c@onstor-exch01.onstor.net>
	<487C98EB.5040908@onstor.com>
	<20080715082917.0bd922d6@ripper.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Go ahead and use g6r5 and g7r5.  Just for kicks, do a system config
copy on each filer before you start with the system config reset's.
Not a big deal if the config is lost, however.

g6r5 console:

telnet 10.2.5.235 9021

g7r5 console:

telnet 10.2.5.235 9026

Let me know if you need any more info.

Thanks,

a


On Tue, 15 Jul 2008 08:29:17 -0700 Andrew Sharp <andy.sharp@onstor.com>
wrote:

> Excellent.  I'll get a cougar for you.
> 
> Cheers,
> 
> a
> 
> On Tue, 15 Jul 2008 18:02:43 +0530 Sripal
> <sripal.surendiran@onstor.com> wrote:
> 
> > John,
> > 
> > I don't have Cougar filer that supports cluster-in-a-box. I have
> > made changes to my code. I need a filer to test it. Please let me
> > know if you have Cougar that supports cluster-in-a-box.
> > 
> > Alternatively, If you can test the changes at your convenient time,
> > then you can take my changes at following path 
> > /homes/sripal/work/dev/linux/rootfs/sbin/dhclient-script and copy it
> > to /sbin/ folder of cougar box and let me know the result.
> > 
> > Thanks,
> > Sripal.
> > 
> > P.S
> > I will do "system config reset" on the Cougar to bring it to FTI.
> > 
> > andy.sharp@onstor.com wrote:
> > > Severity: 2-Major
> > > Build: Submittal 29
> > > Note_Entry: 
> > > Sripal, this one is actually a bit of a problem when you have a
> > > cluster in a box cougar - both nodes come up to the same default
> > > IP address, correct? We need to make the second node come up to a
> > > different default IP address, ideally the current default IP
> > > address +1.  You should be able to tell by looking at the MAC
> > > address of the sc0 or sc1 ports which node it is. Let me know if
> > > you have any questions. Release_Project: Cougar
> > > Description: I figured out that we don't say what gateway we are
> > > connected to. When to systems in the lab are in the un-initialized
> > > state, it has been hard to figure out which system you are
> > > accessing from the default IP https://178.18.250.250.
> > >
> > > I would think that for this problem we should be able to tell the
> > > user whether they are accessing the TOP or BOTTOM nasgateway blade
> > > based on the MAC address. In other words, check the MAC and
> > > present on the FTI screen (or even the login page of the default
> > > IP) which blade has been accessed...
> > >
> > > Note: Workaround could be to tail the log files and see which one
> > > gets connected to based on the sscccc messages. Otherwise just
> > > direct connect via a laptop, but that kind of defeats the use of
> > > NCM FTI anyway.
> > >
> > >   
> > 
