X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C880A0.9518100E@onstor-exch02.onstor.net>; Fri, 7 Mar 2008 15:14:16 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: second mgmt vsvr
Date: Fri, 7 Mar 2008 15:14:16 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E08C0F3A3@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0346B06C@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: second mgmt vsvr
Thread-Index: Ach/6RFDYwEWrDz3TeSrtHklpO4WlAAeoz8QAABpbE8AAM9AQAAARRK4AA2d+pA=
References: <BB375AF679D4A34E9CA8DFA650E2B04E0346B06C@onstor-exch02.onstor.net>
From: "John Keiffer" <john.keiffer@onstor.com>
To: "John Rogers" <john.rogers@onstor.com>,
	"Sandrine Boulanger" <sandrine.boulanger@onstor.com>,
	"dl-QA" <dl-qa@onstor.com>,
	"dl-Cougar" <dl-Cougar@onstor.com>


Okay, it looks like we have a much bigger problem then. I have just =
tried to complete the workflow in which I was going to copy existing =
data from the old mgmt vol to the new one, after which I was going to =
delete the old...

Old =3D vol_mgmt_1879

New =3D vol_mgmt_67415

But after 2 fp crashes I have found that the core files are writing to =
the old mgmt volume and not the new one.=20

So I am not clear on which mgmt volume should/can be deleted at this =
point.

Here is the port and chassis info for reference:

03/07/08 14:03:56 g5r10 diag> port show all
Port Show All
          Link      Link      Interface   Frame
Port      State     Speed       Type      Size           WWN
=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
sp2.0     UP        2 Gbit     F_PORT     2048      50007340000757a0
sp2.1     UP        2 Gbit     F_PORT     2048      50007340000757a1
sp2.2     DISABLED  0 Gbit     N/A        2048      50007340000757a2
sp2.3     DISABLED  0 Gbit     N/A        2048      50007340000757a3
fp1.0     UP        1 Gbit     GE_ETH     1500      0:7:34:7:57:91
fp1.1     UP        1 Gbit     GE_ETH     1500      0:7:34:7:57:91
fp1.2     UP        1 Gbit     GE_ETH     1500      0:7:34:7:57:93
fp1.3     UP        1 Gbit     GE_ETH     1500      0:7:34:7:57:93
03/07/08 14:12:28 g5r10 diag> exit
g5r10:~# chassis view seep

PCB SEEP Info (sig=3DCB01)
  Model Number:         ONS-SYS-6700
  Board Serial Number:  0746050006
  Board Revision:       3.0
  Deviation:
  Result of ICT:        =DC@
  Date of ICT:
  Result of FT:
  IP addr:              10.2.10.5
  IP mask:              255.255.0.0
  MAC addr:             000734075700

Invalid Chassis SEEP signature (sig=3D????)

g5r10:~#

-----Original Message-----
From: John Rogers=20
Sent: Friday, March 07, 2008 7:41 AM
To: John Keiffer; Sandrine Boulanger; dl-QA; dl-Cougar
Subject: Re: second mgmt vsvr

if you got any other digit in the last two nibbles then 2 or a then it =
will change again in the second spin of sub11. This information should =
be sent to the cougar team so that everyone can benefit from the =
workaround.=20

-----Original Message-----
From: John Keiffer
To: John Rogers; Sandrine Boulanger; dl-QA
Sent: Fri Mar 07 07:35:57 2008
Subject: RE: second mgmt vsvr


So if we want to get keep the contents of the old mgmt vol, we will have =
to create and run a new mirror. Then copy the data to the new mgmt vol. =
That sound like a reasonable workaround?=20

Can we expect that we will be getting another new MAC address after they =
fix the WWN issue?

-----Original Message-----
From: John Rogers=20
Sent: Friday, March 07, 2008 7:10 AM
To: John Keiffer; Sandrine Boulanger; dl-QA
Subject: Re: second mgmt vsvr

The managetment vsvr is directly derived from the mac address. So if the =
seep get munged a new one gets created. You fix the seep you can delete =
the bogus one.=20

In this case and the case for all systems with the new sub11 with wwn =
changes, a new mgmt vsvr will be created because the mac address =
changed.  The mac address is where the wwn also is derived from.=20

So this new vsvr will not be able to be deleted because it is the new =
mgmt vsvr and the old one will have to be deleted.=20

-----Original Message-----
From: John Keiffer
To: Sandrine Boulanger; dl-QA
CC: John Rogers
Sent: Fri Mar 07 07:03:18 2008
Subject: RE: second mgmt vsvr

Did you get your answer? In the past Max said this was caused by seep =
corruption for the MAC address. However, your MAC address is okay (as is =
the one on g5r10). I believe it has something to do with the WWN problem =
for boards in the bottom slot.

John R said that the last niblits of the WWN for the sp ports should be =
1x, 2x, or ax, and the defect would be that the bottom boards are =
showing up as 9x in Sub11.=20

What sucks is that the new mgmt vsvr (for this new issue) can't be =
deleted like it could with the old issue. I didn't file a defect for =
this behavior yet. Did anyone else?

P.S. If I got any of that confused, please correct me. :-)

_____________________________________________
From: Sandrine Boulanger=20
Sent: Thursday, March 06, 2008 4:21 PM
To: dl-QA
Subject: second mgmt vsvr

I upgraded to sub#11 and after reboot, the vsvr don't come online and I =
have a second mgmt vsvr. What was causing this in the past?

g14r10:~# nfxsh

Welcome to the ONStor NAS Gateway.

g14r10 diag> vsvr show
Virtual servers on nas gateway g14r10

 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    Disabled                          VS_MGMT_1876
2    Disabled                          G14R10-1
3    Enabled                           VS_MGMT_67412
g14r10 diag> system show chassis

 module     cpu         state
----------------------------------------------
 SSC        SSC         UP
 NFPNIM     TXRX0       UP
            TXRX1       UP
            FP0         UP
            FP1         UP
            FP2         UP
            FP3         UP
----------------------------------------------
g14r10 diag> exit
g14r10:~# chassis view seep

PCB SEEP Info (sig=3DCB01)
  Model Number:         ONS-SYS-6700
  Board Serial Number:  0801050051
  Board Revision:       3.1
  Deviation:
  Result of ICT:
  Date of ICT:
  Result of FT:
  IP addr:              10.2.10.14
  IP mask:              255.255.0.0
  MAC addr:             000734075400

Invalid Chassis SEEP signature (sig=3D????)

g14r10:~#
