AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<rendell.fong@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
FMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	4885CFB3.2020807@onstor.com
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 22 Jul 2008 06:15:10 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Rendell Fong <rendell.fong@onstor.com>
Subject: Fw: 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: <20080722061510.1a2183de@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


FYI


Begin forwarded message:

Date: Tue, 22 Jul 2008 17:46:51 +0530
From: Sripal <sripal.surendiran@onstor.com>
To: Andrew Sharp <andy.sharp@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


Thanks Andy,

I have finished my testing with these filers.

I just noticed that  "system show version" in down slot doesn't show 
valid MAC address. I am not sure this is a valid behavior. Are we 
reading wrong address in seep? Just FYI.

g7r5 diag> system show version

chassis
--------
  Model number: ONS-SYS-6700
  System revision: 4.0
  System serial number: 0804050006
  MAC addr: 00:07:34:07:80:00-------> Shows top slot MAC address

g7r5:~# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:07:34:07:80:80--->Actual MAC 
address.
          inet addr:10.2.5.7  Bcast:10.2.255.255  Mask:255.255.0.0
         
Thanks,
Sripal.

Andrew Sharp wrote:
> 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.
>>>>
>>>>   
>>>>         

