Netbackup 7.5.0.4 Solaris 10 Tape Library SL150

[Joe_Saliby]

Hello,

I am facing an issue while configuring the tape library SL150 on Netbackup.

The scenario is the following:

Netbackup Server running on Solaris:

                    Oracle Solaris 10 8/11 s10x_u10wos_17b X86

Sl150 is connected via SAS, and there is one drive. The HBA card installed on the server is a 6GB card. I applied the following solution,  http://www.symantec.com/docs/HOWTO90258. for now i can see the tape robot but the drive it says " Attached to remote host" "Drive address 1 is already occupied by a drive"

Thanks for your support.

BR // Joe Saliby

[Marianne]

.... but the drive it says " Attached to remote host" "Drive address 1 is already occupied by a drive"

Where do you see this message?

Please show us output of
/usr/openv/volmgr/bin/scan 

Also show us what the OS sees:

cfgadm -al 

ls -l /dev/rmt/*cbn

[Joe_Saliby]

The two messages that i see are from the netbackup GUI, when trying to configure sotrage devices. I see the robot but i cannot select the Drive under it. And when i double click, to check the drive, i see the other message D"rive address 1 is already occupied by a drive"

Here is the ouput of the above commands:

# /usr/openv/volmgr/bin/scan
************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name  : "/dev/sg/c0tw500104f000cd6b5dl1"
Passthru Name: "/dev/sg/c0tw500104f000cd6b5dl1"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "STK     SL150           0182"
Vendor ID  : "STK     "
Product ID : "SL150           "
Product Rev: "0182"
Serial Number: "464970G+1320SY0949"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "STK     SL150           464970G+1320SY0949"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-5
Number of Drives : 1
Number of Slots  : 30
Number of Media Access Ports: 4
Drive 1 Serial Number      : "HU1236R1DT"
Flags : 0x0
Reason: 0x0
#
============================================================

# cfgadm -al
Ap_Id                          Type         Receptacle   Occupant     Condition
c0                             scsi-bus     connected    configured   unknown
c0::dsk/c0t0d0                 disk         connected    configured   unknown
c0::dsk/c0t1d0                 disk         connected    configured   unknown
c0::dsk/c0t2d0                 disk         connected    configured   unknown
c0::dsk/c0t3d0                 disk         connected    configured   unknown
c4                             scsi-sas     connected    configured   unknown
c4::rmt/0                      tape         connected    configured   unknown
c4::sg/c0tw500104f000cd6b5dl1  unknown      connected    configured   unknown
c5                             scsi-sas     connected    unconfigured unknown
c6                             fc           connected    unconfigured unknown
c7                             fc           connected    unconfigured unknown
sata0/0::dsk/c2t0d0            cd/dvd       connected    configured   ok
usb0/1                         usb-hub      connected    configured   ok
usb0/1.1                       unknown      empty        unconfigured ok
usb0/1.2                       usb-storage  connected    configured   ok
usb0/1.3                       unknown      empty        unconfigured ok
usb0/1.4                       unknown      empty        unconfigured ok
usb0/1.5                       unknown      empty        unconfigured ok
usb0/1.6                       unknown      empty        unconfigured ok
usb0/2                         unknown      empty        unconfigured ok
usb1/1                         usb-hub      connected    configured   ok
usb1/1.1                       unknown      empty        unconfigured ok
usb1/1.2                       unknown      empty        unconfigured ok
usb1/1.3                       unknown      empty        unconfigured ok
usb1/1.4                       unknown      empty        unconfigured ok
usb1/1.5                       unknown      empty        unconfigured ok
usb1/1.6                       unknown      empty        unconfigured ok
usb1/1.7                       usb-hub      connected    configured   ok
usb1/1.7.1                     unknown      empty        unconfigured ok
usb1/1.7.2                     unknown      empty        unconfigured ok
usb1/1.7.3                     unknown      empty        unconfigured ok
usb1/1.8                       usb-device   connected    configured   ok
usb1/2                         unknown      empty        unconfigured ok
================================================================

# ls -l /dev/rmt/*cbn
lrwxrwxrwx   1 root     root          90 Sep  1 13:19 /dev/rmt/0cbn -> ../../devices/pci@0,0/pci8086,3c0a@3,2/pci1000,30b0@0/iport@8/tape@w500104f000cd6b5d,0:cbn
#

Thanks!

[Joe_Saliby]

Hi Marianne,

The above message are from the netbackup GUI, when trying to configure the storage devices. i see the drive under the robot, but it is written next to it: Attached to a remote host. And when i try to double click on it --> to check the box i see the other message: "Drive address 1 is already occupied by a drive"

Here it the output of the commands above:

Thanks!

============================

# /usr/openv/volmgr/bin/scan
************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name  : "/dev/sg/c0tw500104f000cd6b5dl1"
Passthru Name: "/dev/sg/c0tw500104f000cd6b5dl1"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "STK     SL150           0182"
Vendor ID  : "STK     "
Product ID : "SL150           "
Product Rev: "0182"
Serial Number: "464970G+1320SY0949"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "STK     SL150           464970G+1320SY0949"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-5
Number of Drives : 1
Number of Slots  : 30
Number of Media Access Ports: 4
Drive 1 Serial Number      : "HU1236R1DT"
Flags : 0x0
Reason: 0x0
#
=================================

# cfgadm -al
Ap_Id                          Type         Receptacle   Occupant     Condition
c0                             scsi-bus     connected    configured   unknown
c0::dsk/c0t0d0                 disk         connected    configured   unknown
c0::dsk/c0t1d0                 disk         connected    configured   unknown
c0::dsk/c0t2d0                 disk         connected    configured   unknown
c0::dsk/c0t3d0                 disk         connected    configured   unknown
c4                             scsi-sas     connected    configured   unknown
c4::rmt/0                      tape         connected    configured   unknown
c4::sg/c0tw500104f000cd6b5dl1  unknown      connected    configured   unknown
c5                             scsi-sas     connected    unconfigured unknown
c6                             fc           connected    unconfigured unknown
c7                             fc           connected    unconfigured unknown
sata0/0::dsk/c2t0d0            cd/dvd       connected    configured   ok
usb0/1                         usb-hub      connected    configured   ok
usb0/1.1                       unknown      empty        unconfigured ok
usb0/1.2                       usb-storage  connected    configured   ok
usb0/1.3                       unknown      empty        unconfigured ok
usb0/1.4                       unknown      empty        unconfigured ok
usb0/1.5                       unknown      empty        unconfigured ok
usb0/1.6                       unknown      empty        unconfigured ok
usb0/2                         unknown      empty        unconfigured ok
usb1/1                         usb-hub      connected    configured   ok
usb1/1.1                       unknown      empty        unconfigured ok
usb1/1.2                       unknown      empty        unconfigured ok
usb1/1.3                       unknown      empty        unconfigured ok
usb1/1.4                       unknown      empty        unconfigured ok
usb1/1.5                       unknown      empty        unconfigured ok
usb1/1.6                       unknown      empty        unconfigured ok
usb1/1.7                       usb-hub      connected    configured   ok
usb1/1.7.1                     unknown      empty        unconfigured ok
usb1/1.7.2                     unknown      empty        unconfigured ok
usb1/1.7.3                     unknown      empty        unconfigured ok
usb1/1.8                       usb-device   connected    configured   ok
usb1/2                         unknown      empty        unconfigured ok
 

=============================

# ls -l /dev/rmt/*cbn
lrwxrwxrwx   1 root     root          90 Sep  1 13:19 /dev/rmt/0cbn -> ../../devices/pci@0,0/pci8086,3c0a@3,2/pci1000,30b0@0/iport@8/tape@w500104f000cd6b5d,0:cbn
#

[Marianne]

Okay, the OS sees the tape drive but NBU does not.

See if rebuiding the sg driver fixes the problem:

# cd /usr/openv/volmgr/bin/driver
# /usr/openv/volmgr/bin/sg.build all 

Install the new sg driver configuration:

# /usr/bin/rm -f /kernel/drv/sg.conf
# /usr/openv/volmgr/bin/driver/sg.install

Check/verify config:

# /usr/openv/volmgr/bin/sgscan
# /usr/openv/volmgr/bin/scan

[Joe_Saliby]

I just tried the above.  Now I cannot see the robot neither the tape drive from the sgscan and scan.

I think because in the following solution:  http://www.symantec.com/docs/HOWTO90258  we edit manually the etc/devlink.tab and the sg.install will change the /etc/devlink.tab file.

[Marianne]

If you follow the above steps exactly, it will modify devlinks.tab.

So, perform these 2 steps:

# cd /usr/openv/volmgr/bin/driver            (This folder is important. 'buiding blocks' are created here.)
# /usr/openv/volmgr/bin/sg.build all 

Now show us contents of sg.conf and sg.links in this folder. 
These 2 files will determine the contents of devlinks.tab and /kernel/drv/sg.conf when 'sg.install' is run.

[Joe_Saliby]

Hello Marianne,

Here it is:

================

# cd /usr/openv/volmgr/bin/driver           
# pwd
/usr/openv/volmgr/bin/driver
 

# /usr/openv/volmgr/bin/sg.build all
The file ./st.conf should be appended to /kernel/drv/st.conf.
A reboot may be necessary to create any new device files.
Created file ./sg.conf.
Created file ./sg.links.
 

# ls -lrt
total 108
-r--------   1 root     bin          726 Sep 16  2012 sg.links.template
-r--------   1 root     bin         5650 Sep 16  2012 sg.links.all
-r-x------   1 root     bin         4778 Sep 16  2012 sg.install
-r--------   1 root     bin          824 Sep 16  2012 sg.conf.template
-r--------   1 root     bin         4769 Sep 16  2012 sg.conf.all
-r--------   1 root     bin        31792 Sep 16  2012 sg
-rw-r--r--   1 root     root         546 Sep  2 14:32 st.conf
-rw-r--r--   1 root     root         587 Sep  2 14:32 sg.conf
-rw-r--r--   1 root     root         726 Sep  2 14:32 sg.links
#
=============================

# cat sg.conf
# Configuration file for SCSA Generic.
#
name="sg" class="scsi" target=0 lun=0;
name="sg" class="scsi" target=0 lun=1;
name="sg" class="scsi" target=1 lun=0;
name="sg" class="scsi" target=1 lun=1;
name="sg" class="scsi" target=2 lun=0;
name="sg" class="scsi" target=2 lun=1;
name="sg" class="scsi" target=3 lun=0;
name="sg" class="scsi" target=3 lun=1;
name="sg" class="scsi" target=4 lun=0;
name="sg" class="scsi" target=4 lun=1;
name="sg" class="scsi" target=5 lun=0;
name="sg" class="scsi" target=5 lun=1;
name="sg" class="scsi" target=6 lun=0;
name="sg" class="scsi" target=6 lun=1;
#
#
======================================================
# cat sg.links
# begin SCSA Generic devlinks file - creates nodes in /dev/sg
type=ddi_pseudo;name=sg;addr=0,0;       sg/c\N0t0l0
type=ddi_pseudo;name=sg;addr=0,1;       sg/c\N0t0l1
type=ddi_pseudo;name=sg;addr=1,0;       sg/c\N0t1l0
type=ddi_pseudo;name=sg;addr=1,1;       sg/c\N0t1l1
type=ddi_pseudo;name=sg;addr=2,0;       sg/c\N0t2l0
type=ddi_pseudo;name=sg;addr=2,1;       sg/c\N0t2l1
type=ddi_pseudo;name=sg;addr=3,0;       sg/c\N0t3l0
type=ddi_pseudo;name=sg;addr=3,1;       sg/c\N0t3l1
type=ddi_pseudo;name=sg;addr=4,0;       sg/c\N0t4l0
type=ddi_pseudo;name=sg;addr=4,1;       sg/c\N0t4l1
type=ddi_pseudo;name=sg;addr=5,0;       sg/c\N0t5l0
type=ddi_pseudo;name=sg;addr=5,1;       sg/c\N0t5l1
type=ddi_pseudo;name=sg;addr=6,0;       sg/c\N0t6l0
type=ddi_pseudo;name=sg;addr=6,1;       sg/c\N0t6l1
# end SCSA devlinks
# pwd
/usr/openv/volmgr/bin/driver

BR // Joe Saliby

[Marianne · Accepted solution]

I have had a look at the TN that you posted, but also remembered similar issues a while ago.

The issues was caused by the Solaris driver used for the 6GB SAS card.
The only solution at the time was to replace the card with 3GB SAS card that is using a different driver.

See this post: https://www-secure.symantec.com/connect/forums/solaris-111-sas-lto6-neo-400s-library-can-not-bring-n... 

Please also remember to disable Solaris multipathing as per NetBackup Device Configuration Guide:  http://www.symantec.com/docs/DOC5186

To disable MPxIO
1 Use a text editor to open the following file:
/kernel/drv/fp.conf
2 Change the mpxio-disable value from no to yes. After the change, the line in the file should appear as follows:
mpxio-disable="yes"
3 Save the changes and exit from the text editor.