X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7DEA5.3F09CB3A@onstor-exch02.onstor.net>; Tue, 14 Aug 2007 10:59:31 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: error for eth1 on ssc console for linux on bobcat
Date: Tue, 14 Aug 2007 10:59:31 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E04FA7CF4@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0221597D@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: error for eth1 on ssc console for linux on bobcat
Thread-Index: AcfeocKyWP4Nnp0CSwmxtRUInE18igAAR4OwAAAt0NAAAGGioA==
References: <BB375AF679D4A34E9CA8DFA650E2B04E0267A49C@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0221597D@onstor-exch02.onstor.net>
From: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>
To: "Larry Scheer" <larry.scheer@onstor.com>,
	"Sandrine Boulanger" <sandrine.boulanger@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>

It is not specific to bobcat linux and it was fixed. I have normal vsvr
names on my bobcat

vsvr show all
Virtual servers on nas gateway eng131

 ID  State                             Name
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
1    Enabled                           VS_MGMT_563
2    Enabled                           ENG131

>-----Original Message-----
>From: Larry Scheer
>Sent: Tuesday, August 14, 2007 11:55 AM
>To: Sandrine Boulanger; Andy Sharp
>Cc: Maxim Kozlovsky
>Subject: RE: error for eth1 on ssc console for linux on bobcat
>
>I think we want to start filing defects against cougar in ClearQuest if
I
>am remembering what Tim said correctly. Max, Andy, any comment?
>Much of what we find in Bobcat-Linux applies to Cougar as well. For
>instance the unusual mgmt vsvr name is a candidate for cougar defect.
>
>But in this case this defect is specific to bobcat-linux so maybe we
have a
>separate category for bobcat-linux kernel bugs?
>
>-----Original Message-----
>From: Sandrine Boulanger
>Sent: Tuesday, August 14, 2007 11:43 AM
>To: Andy Sharp
>Cc: Larry Scheer; Maxim Kozlovsky
>Subject: RE: error for eth1 on ssc console for linux on bobcat
>
>By the way, where do we keep track of existing defects for Cougar right
>now?
>
>-----Original Message-----
>From: Andy Sharp
>Sent: Tuesday, August 14, 2007 11:35 AM
>To: Sandrine Boulanger
>Cc: Larry Scheer; Maxim Kozlovsky
>Subject: Re: error for eth1 on ssc console for linux on bobcat
>
>Yes, this is a known bug.  Probably won't be fixed until after cougar,
>if there ever is such a time.
>
>On Tue, 14 Aug 2007 11:27:05 -0700
>"Sandrine Boulanger" <sandrine.boulanger@onstor.com> wrote:
>
>> eth1: Setting full-duplex based on negotiated link capability.
>> eth1: Tx/Rx process did not stop in 2000 usec.
>> eth1: Wake-up event 0xffffffff
>> eth1: Setting full-duplex based on negotiated link capability.
>> eth1: Tx/Rx process did not stop in 2000 usec.
>> eth1: Wake-up event 0xffffffff
>> eth1: Setting full-duplex based on negotiated link capability.
>> eth1: Tx/Rx process did not stop in 2000 usec.
>> eth1: Wake-up event 0xffffffff
>> eth1: Setting full-duplex based on negotiated link capability.
>> eth1: Tx/Rx process did not stop in 2000 usec.
>> eth1: Wake-up event 0xffffffff
>> eth1: Setting full-duplex based on negotiated link capability.
