OK, trying again...another previous post to this forum I saved about this 
library:

The SL3000 is set to HLI by default. I'm told this is what you'd use with 
ACSLS. But for those of us who prefer FC... In SLConsole, select Tools / Select 
Active Cells from the menu. Go to the "Select Active Cells" tab, then change 
the "Interface Type" pulldown from HLI to FC-SCSI. Click Apply.

To tie this thread back to NetBackup, I first noticed the problem when 
volmgr/bin/scan said the robot had zero drives (though it did list the drives 
separately). The device configuration wizard detected all the devices as well, 
but said the robot was not serialized and all the drives had the limitation of 
being standalone. Obviously all fixed after changing the interface type.

Renee

-----Original Message-----
From: Clooney, David [mailto:david.clooney AT bankofamerica DOT com] 
Sent: Wednesday, March 11, 2009 10:51 AM
To: Renee Carlisle; VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: RE: STK SL3000 - NBU 6.5.3

Thanks Renee

Unfortunately we have applied the device mappings your technote
specifies.

Regards

 
David Clooney
Enterprise Storage Services
 
Internal X66059
External +44 20 8760 6059
david.clooney AT bankofamerica DOT com
 

-----Original Message-----
From: Renee Carlisle [mailto:rcarlisle AT serverwarecorp DOT com] 
Sent: 11 March 2009 14:31
To: Clooney, David; VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: RE: STK SL3000 - NBU 6.5.3

David,

I saw this in a posting a few months back...since we resell the STK line
I hung onto it in case I ever needed it....it may or may not resolve
your issue...let us know:

Symptoms
Users of NetBackUp version 6.x cannot configure a new SL3000 tape
library.

When installing a new SL3000 tape library, users of Symantics Veritas
NetBackUp cannot configure the library.

Resolution
Configuring NetBackUp to work with SL3000 requires a package update

When installing an SL3000 with Veritas NetBackUp 6.0 or 6.5.  And the
library is connected  via Fibre Channel, NetBackUp will fail to
configure the library properly.
Netbackup doesn't contain the SL3000 library mappings.

The fix is provide by Symantic for the Veritas NetBackUp products in the
form of a package update.
The
 following link will provide the package update for download, package
install instructions and other package details.
http://seer.entsupport.symantec.com/docs/302598.htm
Note: the link provided is outside Sun Microsystem control and could be
deleted, changed or moved without the knowledge of Sun.  Contact
Symantics for problems, information or support concerning the referenced
package.
Symantic Document ID: 302598 

Renee

-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Clooney,
David
Sent: Wednesday, March 11, 2009 9:31 AM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] STK SL3000 - NBU 6.5.3

Hi All

Hit another snag in a new deployment, seem to be requiring knowledge
from the group on a number of occasions over the last couple of months,
its appreciated.

Our DR environment has just acquired an STK SL3000 and we are having
issues with the robotic config in NBU.

If you run the wizard the results are that NBU interprets the library as
remote for some unknown reason.

We have downloaded the device mappings and applied successfully however
don't seem to be able to get it working.

The T10kB drives in the library are fine.

The library and drives are dual pathed and visible down both paths

c5::500104f000ad41c8,0         med-changer  connected    configured
unknown
c5::500104f000ad41d8,0         tape         connected    configured
unknown
c5::500104f000ad41e1,0         tape         connected    configured
unknown
c5::500104f000ad41e4,0         tape         connected    configured
unknown
c5::500104f000ad41ed,0         tape         connected    configured
unknown
c6                             fc           connected    unconfigured
unknown
c7                             fc-fabric    connected    configured
unknown
c7::500104f000ad41c8,0         med-changer  connected    configured
unknown
c7::500104f000ad41d8,0         tape         connected    configured
unknown
c7::500104f000ad41e1,0         tape         connected    configured
unknown
c7::500104f000ad41e4,0         tape         connected    configured
unknown
c7::500104f000ad41ed,0         tape         connected    configured
unknown

additionally scan -chnager finds the library and robot no problem

************************************************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name  : "/dev/sg/c0tw500104f000ad41c8l0"
Passthru Name: "/dev/sg/c0tw500104f000ad41c8l0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "STK     SL3000          2.05"
Vendor ID  : "STK     "
Product ID : "SL3000          "
Product Rev: "2.05"
Serial Number: "571000200222"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-5
Number of Drives : 4
Number of Slots  : 200
Number of Media Access Ports: 26
Drive 1 Serial Number      : "572004000580"
Drive 2 Serial Number      : "572004000573"
Drive 3 Serial Number      : "572004000561"
Drive 4 Serial Number      : "572004000267"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "/dev/sg/c1tw500104f000ad41c8l0"
Passthru Name: "/dev/sg/c1tw500104f000ad41c8l0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "STK     SL3000          2.05"
Vendor ID  : "STK     "
Product ID : "SL3000          "
Product Rev: "2.05"
Serial Number: "571000200222"
WWN          : ""
WWN Id Type  : 0
Device Identifier: ""
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-5
Number of Drives : 4
Number of Slots  : 200
Number of Media Access Ports: 26
Drive 1 Serial Number      : "572004000580"
Drive 2 Serial Number      : "572004000573"
Drive 3 Serial Number      : "572004000561"
Drive 4 Serial Number      : "572004000267"
Flags : 0x0
Reason: 0x0

However, even I I try add the library through tpconfig I just don't seem
to be able to get is working.

Anyone know of any gotach'a with this particular library??

Regards
 
David Clooney
Enterprise Storage Services
 



Notice to recipient:
The information in this internet e-mail and any attachments is
confidential and may be privileged. It is intended solely for the
addressee. If you are not the intended addressee please notify the
sender immediately by telephone. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted to
be taken in reliance on it, is prohibited and may be unlawful.

When addressed to external clients any opinions or advice contained in
this internet e-mail are subject to the terms and conditions expressed
in any applicable governing terms of business or client engagement
letter issued by the pertinent Bank of America group entity.

If this email originates from the U.K. please note that Bank of America,
N.A., London Branch and Banc of America Securities Limited are
authorised and regulated by the Financial Services Authority.  For all
U.K. corporate disclosures, please refer to
www.bankofamerica.com/ukcompanies

_______________________________________________
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