Veritas-bu

Re: [Veritas-bu] MPT driver and SG

2008-07-22 07:47:16
Subject: Re: [Veritas-bu] MPT driver and SG
From: Jon Bousselot <jon-bousselot AT pacbell DOT net>
To: Martin Ruslan <mit.martin AT gmail DOT com>
Date: Tue, 22 Jul 2008 04:27:21 -0700 (PDT)
Martin,
I checked the files I downloaded, and the 6.5.2 was indeed the A version.
NB_6.5.2A.solaris_x86_305652.tar
The other necessary patch files (client, java, ndmp) were applied, and were the correct version.

The files I used on the sparc version I'll have to check later. 

Sun is working on the ticket now, so when they fix it, I'll let you know what it was.
-Jon

----- Original Message ----
From: Martin Ruslan <mit.martin AT gmail DOT com>
To: Jon Bousselot <jon-bousselot AT pacbell DOT net>
Cc: VERITAS-BU AT mailman.eng.auburn DOT edu
Sent: Monday, July 21, 2008 9:01:15 PM
Subject: Re: [Veritas-bu] MPT driver and SG

Hi Jon,
I've looked to the NBU6.5 HCL, and the SL24 supported either with FC, or SCSI.
Since you already upgraded to 6.5.2, and Symantec already released the 6.5.2a, why don't you try to go with it.
you can check here: http://seer.entsupport.symantec.com/docs/305652.htm
there's some robot issue fixed on this release version.

mTz

On Mon, Jul 21, 2008 at 11:13 AM, Jon Bousselot <jon-bousselot AT pacbell DOT net> wrote:
On the Sparc Solaris 10 system:
SL500 library, two LTO4 drives - fiber.
L100 library, two LTO3 drives - all scsi.

The L100 is currently connected to a Solaris 9 system, and is working fine, but I need to move it to the Solaris 10 T2000 system.

On the x86 system:
SL24, one LTO4 drive, cannot attach to the robot after 6.5.2 patch, and had a lot of problems finding the robot at 6.5.

-Jon




----- Original Message ----
From: Martin Ruslan <mit.martin AT gmail DOT com>
To: jon-bousselot AT pacbell DOT net
Cc: VERITAS-BU AT mailman.eng.auburn DOT edu
Sent: Sunday, July 20, 2008 8:24:08 PM
Subject: Re: [Veritas-bu] MPT driver and SG

Hi Jon..
How many tape library do you have?
and can you give the tape library brand and type?
looks like you need to do the device mappings.

And btw, if you only had one tape library, the robot only attached to one master/media server.
unless you partitioned it

regards,
mTz


On Sat, Jul 19, 2008 at 10:47 AM, Jon Bousselot <jon-bousselot AT pacbell DOT net> wrote:
http://www.auscert.org.au/render.html?it=9490

Has anyone encountered this bug and the documented workaround did not
fix the problem?

I've encountered a variety of problems that I can relate to this.

1. Sun Sparc system with fiber attached tape/robot, had the bad patches
but not the workaround, and sg sees the tapes and robot just fine.  The
sg driver worked fine at version 6.5 and 6.5.2.

2. Same Sun Sparc system with scsi card added, workaround patches
applied, and sg cannot see the robot on the scsi bus, only the drives.
The robot and drives on the fiber card are still there and working just
fine.

3. Sun x86 system with fiber attached tape, did not have the workaround,
sg sees only the tape.  After the workaround, sg sees the tape and robot
and I could setup the devices.  After 6.5.2 patch, sg does not see the
robot any more.

I've done the sg.build, and run sgscan a dozen times.  Reconfigure
boots, devfsadm, cfgadm, luxadm probe...   it seems Solaris can see all
the devices down either type of controller, but SG refuses to bind to
the robot.
On the Sparc system, I'm moving the library off of a working 6.5.2
Solaris 9 media server that is being decommissioned, so I know the
library and drives are good.
The x86 system is a new install.

-Jon
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
<Prev in Thread] Current Thread [Next in Thread>