X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C88C8A.D971E950@onstor-exch02.onstor.net>; Sat, 22 Mar 2008 19:08:56 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C88C8A.D971E950"
Content-class: urn:content-classes:message
Subject: RE: sub13 issues
Date: Sat, 22 Mar 2008 19:08:56 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E042F0133@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: sub13 issues
Thread-Index: AciL5vhUs+/0FYfqQtu0SHCR0dTVzwAU5CZCAAqm0DAAAypIIgAGCRK8
References: <BB375AF679D4A34E9CA8DFA650E2B04E03B5B70E@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E03B5B712@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E08FC3945@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0353B545@onstor-exch02.onstor.net>
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Chris Vandever" <chris.vandever@onstor.com>,
	"John Keiffer" <john.keiffer@onstor.com>,
	"Vikas Saini" <vikas.saini@onstor.com>,
	"dl-QA" <dl-qa@onstor.com>,
	"dl-hcl-qa" <dl-hcl-qa@onstor.com>,
	"dl-Cougar" <dl-Cougar@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C88C8A.D971E950
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

John,
  Just a guess here, check /etc/network/interfaces on each host in the =
cluster to see if there is a non-existant interface configured in one or =
more of the hosts. If there is, that means at one time the second =
management interface was configured on that gateway when the OCT was =
run. Removing the non-existant interface from that file will keep the =
system from starting it at boot time.

That is one way I know you can get into the scenario Chris is =
describing.

Larry


-----Original Message-----
From: Chris Vandever
Sent: Sat 3/22/2008 4:09 PM
To: John Keiffer; Vikas Saini; dl-QA; dl-hcl-qa; dl-Cougar
Subject: RE: sub13 issues
=20
The problem is that part of clustering is trying to use the non-existent =
SC2 interface that's configured and ACTIVE according to ifconfig.  The =
rest of clustering (like the heartbeats) is using the correct interface =
and working fine.

If anyone can offer any insight into why a non-existent interface is =
coming up active, I'd appreciate it.

ChrisV


-----Original Message-----
From: John Keiffer
Sent: Sat 3/22/2008 2:40 PM
To: Vikas Saini; dl-QA; dl-hcl-qa; dl-Cougar
Subject: RE: sub13 issues
=20

Regarding 22821: Both systems CAN ping each other and the network. The =
issue is that they think they can't sync up the clusterDB or something. =
I'm not sure.

-----Original Message-----
From: Vikas Saini=20
Sent: Saturday, March 22, 2008 9:43 AM
To: Vikas Saini; dl-QA; dl-hcl-qa; dl-Cougar
Subject: sub13 issues
Importance: High

Hi All,
   so far we have seen following issues on sub13

1) An issue where "vol create" failed with timeout error message. elogs =
displayed lun label read problem. defect 22921 and 22923

2) OPS dropping to zero problem resurfaced on John K system(g6r10,g5r10) =
and g11r204(system is still in that state incase someone wants to have a =
look)

3) Manny also saw an issue where OPS are dropping to zero for a second =
or two.(on g10r204).

4) TXRX crash causing FP crash problem is still happening. this needs to =
be fixed ASAP. defect 22448

5) A couple of issues with system upgrade. defect 22919 and a few =
others.

Apart from these, 22821 where John K's cluster is still messed and not =
able ping each other. we need some resolution on that.
=20

Thanks
Vikas








------_=_NextPart_001_01C88C8A.D971E950
Content-Type: text/html;
	charset="iso-8859-1"
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=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>RE: sub13 issues</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>John,<BR>
&nbsp; Just a guess here, check /etc/network/interfaces on each host in =
the cluster to see if there is a non-existant interface configured in =
one or more of the hosts. If there is, that means at one time the second =
management interface was configured on that gateway when the OCT was =
run. Removing the non-existant interface from that file will keep the =
system from starting it at boot time.<BR>
<BR>
That is one way I know you can get into the scenario Chris is =
describing.<BR>
<BR>
Larry<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Chris Vandever<BR>
Sent: Sat 3/22/2008 4:09 PM<BR>
To: John Keiffer; Vikas Saini; dl-QA; dl-hcl-qa; dl-Cougar<BR>
Subject: RE: sub13 issues<BR>
<BR>
The problem is that part of clustering is trying to use the non-existent =
SC2 interface that's configured and ACTIVE according to ifconfig.&nbsp; =
The rest of clustering (like the heartbeats) is using the correct =
interface and working fine.<BR>
<BR>
If anyone can offer any insight into why a non-existent interface is =
coming up active, I'd appreciate it.<BR>
<BR>
ChrisV<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: John Keiffer<BR>
Sent: Sat 3/22/2008 2:40 PM<BR>
To: Vikas Saini; dl-QA; dl-hcl-qa; dl-Cougar<BR>
Subject: RE: sub13 issues<BR>
<BR>
<BR>
Regarding 22821: Both systems CAN ping each other and the network. The =
issue is that they think they can't sync up the clusterDB or something. =
I'm not sure.<BR>
<BR>
-----Original Message-----<BR>
From: Vikas Saini<BR>
Sent: Saturday, March 22, 2008 9:43 AM<BR>
To: Vikas Saini; dl-QA; dl-hcl-qa; dl-Cougar<BR>
Subject: sub13 issues<BR>
Importance: High<BR>
<BR>
Hi All,<BR>
&nbsp;&nbsp; so far we have seen following issues on sub13<BR>
<BR>
1) An issue where &quot;vol create&quot; failed with timeout error =
message. elogs displayed lun label read problem. defect 22921 and =
22923<BR>
<BR>
2) OPS dropping to zero problem resurfaced on John K system(g6r10,g5r10) =
and g11r204(system is still in that state incase someone wants to have a =
look)<BR>
<BR>
3) Manny also saw an issue where OPS are dropping to zero for a second =
or two.(on g10r204).<BR>
<BR>
4) TXRX crash causing FP crash problem is still happening. this needs to =
be fixed ASAP. defect 22448<BR>
<BR>
5) A couple of issues with system upgrade. defect 22919 and a few =
others.<BR>
<BR>
Apart from these, 22821 where John K's cluster is still messed and not =
able ping each other. we need some resolution on that.<BR>
<BR>
<BR>
Thanks<BR>
Vikas<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C88C8A.D971E950--
