Forum Discussion

Creole-Kid's avatar
Creole-Kid
Level 3
12 years ago
Solved

Unable to see medium changer

**** Moved to new discussion from https://www-secure.symantec.com/connect/forums/unable-see-robotic-media-changer ****

Hi,

I also am faced with NetBackup 7.5.0.5 not seeing the FC connected tape library or drives under Solaris 11.1.  The OS can see the tape drives.  The library connection piggy backs on one of the tape drive fc links.  I have run the 'sg.build all' and 'sg.install' scripts but the results are not successful.  Strangely, the sg.conf file located at /kernel/drv does not change to the new one created by the sg.build script.  The date is correct on the file but it does not contain any of the wwn information.  Any help is greatly appreciated.

Creole-Kid

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

Truncated cfgadm output:

c14::50050763124c0016          tape         connected    configured   unknown
c14::50050763124c0207          tape         connected    configured   unknown
c15                            fc-fabric    connected    configured   unknown
c15::50050763124c0149          tape         connected    configured   unknown
c15::50050763124c0162          tape         connected    configured   unknown
========================================================
ls -l /dev/rmt/*cbn outout:
root@tigerfish:/usr/openv/volmgr/bin# ls -l /dev/rmt/*cbn
lrwxrwxrwx   1 root     root          87 Jun  5 13:18 /dev/rmt/0cbn -> ../../devices/pci@7a,0/pci8086,340e@7/pci1077,15d@0/fp@0,0/tape@w50050763124c0016,0:cbn
lrwxrwxrwx   1 root     root          88 Jun  5 13:18 /dev/rmt/0dcbn -> ../../devices/pci@7a,0/pci8086,340e@7/pci1077,15d@0/fp@0,0/tape@w50050763124c0016,0:dcbn
lrwxrwxrwx   1 root     root          87 Jun  5 13:18 /dev/rmt/1cbn -> ../../devices/pci@7a,0/pci8086,340e@7/pci1077,15d@0/fp@0,0/tape@w50050763124c0207,0:cbn
lrwxrwxrwx   1 root     root          88 Jun  5 13:18 /dev/rmt/1dcbn -> ../../devices/pci@7a,0/pci8086,340e@7/pci1077,15d@0/fp@0,0/tape@w50050763124c0207,0:dcbn
lrwxrwxrwx   1 root     root          89 Jun  5 13:30 /dev/rmt/2cbn -> ../../devices/pci@7a,0/pci8086,340e@7/pci1077,15d@0,1/fp@0,0/tape@w50050763124c0162,0:cbn
lrwxrwxrwx   1 root     root          90 Jun  5 13:30 /dev/rmt/2dcbn -> ../../devices/pci@7a,0/pci8086,340e@7/pci1077,15d@0,1/fp@0,0/tape@w50050763124c0162,0:dcbn
lrwxrwxrwx   1 root     root          89 Jun  5 13:30 /dev/rmt/3cbn -> ../../devices/pci@7a,0/pci8086,340e@7/pci1077,15d@0,1/fp@0,0/tape@w50050763124c0149,0:cbn
lrwxrwxrwx   1 root     root          90 Jun  5 13:30 /dev/rmt/3dcbn -> ../../devices/pci@7a,0/pci8086,340e@7/pci1077,15d@0,1/fp@0,0/tape@w50050763124c0149,0:dcbn
=========================================================================
fcinfo hba-port output:
HBA Port WWN: 21000024ff44b8b0
        Port Mode: Initiator
        Port ID: 30600
        OS Device Name: /dev/cfg/c14
        Manufacturer: QLogic Corp.
        Model: QLE2562
        Firmware Version: 5.6.4
        FCode/BIOS Version:  BIOS: 3.00; fcode: 3.15; EFI: 2.21;
        Serial Number: BFD1216A16612
        Driver Name: qlc
        Driver Version: 20120717-4.01
        Type: N-port
        State: online
        Supported Speeds: 2Gb 4Gb 8Gb 
        Current Speed: 8Gb 
        Node WWN: 20000024ff44b8b0
        Max NPIV Ports: 255
        NPIV port list:
HBA Port WWN: 21000024ff44b8b1
        Port Mode: Initiator
        Port ID: 40600
        OS Device Name: /dev/cfg/c15
        Manufacturer: QLogic Corp.
        Model: QLE2562
        Firmware Version: 5.6.4
        FCode/BIOS Version:  BIOS: 3.00; fcode: 3.15; EFI: 2.21;
        Serial Number: BFD1216A16612
        Driver Name: qlc
        Driver Version: 20120717-4.01
        Type: N-port
        State: online
        Supported Speeds: 2Gb 4Gb 8Gb 
        Current Speed: 8Gb 
        Node WWN: 20000024ff44b8b1
        Max NPIV Ports: 255
        NPIV port list:
============================================================
fcinfo remote-port -p 21000024ff44b8b0
Remote Port WWN: 50050763124c0207
        Active FC4 Types: SCSI
        SCSI Target: yes
        Port Symbolic Name: IBM     ULTRIUM-HH5     BBNF
        Node WWN: 50050763124c0206
Remote Port WWN: 50050763124c0016
        Active FC4 Types: SCSI
        SCSI Target: yes
        Port Symbolic Name: IBM     ULTRIUM-HH5     BBNF
        Node WWN: 50050763124c0015
============================================================
fcinfo remote-port -p 21000024ff44b8b1
Remote Port WWN: 50050763124c0162
        Active FC4 Types: SCSI
        SCSI Target: yes
        Port Symbolic Name: IBM     ULTRIUM-HH5     BBNF
        Node WWN: 50050763124c0161
Remote Port WWN: 50050763124c0149
        Active FC4 Types: SCSI
        SCSI Target: yes
        Port Symbolic Name: IBM     ULTRIUM-HH5     BBNF
        Node WWN: 50050763124c0148
=============================================================
Below is a display of the Library as LUN 1 via one of the tape drive WWN port numbers:
 
fcinfo remote-port -lsp 21000024ff44b8b0 50050763124c0207
                   
Remote Port WWN: 50050763124c0207
        Active FC4 Types: SCSI
        SCSI Target: yes
        Port Symbolic Name: IBM     ULTRIUM-HH5     BBNF
        Node WWN: 50050763124c0206
        Link Error Statistics:
                Link Failure Count: 0
                Loss of Sync Count: 0
                Loss of Signal Count: 0
                Primitive Seq Protocol Error Count: 0
                Invalid Tx Word Count: 26
                Invalid CRC Count: 0
        LUN: 0
          Vendor: IBM     
          Product: ULTRIUM-HH5     
          OS Device Name: /dev/rmt/1n
        LUN: 1
          Vendor: QUALSTAR
          Product: RLS-85          
          OS Device Name: /devices/pci@7a,0/pci8086,340e@7/pci1077,15d@0/fp@0,0/medium-changer@w50050763124c0207,1
 
 
 
 
  • sg.build script will only update files in /usr/openv/volmgr/bin/driver.

    Check files like sg.links and sg.conf in this folder before running sg.install. 
    I have experienced situations where I had to edit above 2 files manually to add device entries before running sg.install.

    sg.install will populate /etc/devlinks.tab and /kernel/drv/sg.conf with entries in the usr/openv/volmgr/bin/driver files.

  • sg.build script will only update files in /usr/openv/volmgr/bin/driver.

    Check files like sg.links and sg.conf in this folder before running sg.install. 
    I have experienced situations where I had to edit above 2 files manually to add device entries before running sg.install.

    sg.install will populate /etc/devlinks.tab and /kernel/drv/sg.conf with entries in the usr/openv/volmgr/bin/driver files.

  • Thank you Marianne!!!!

    Your first sentence is what helped me to understand and resolve my problem.

    I was running sg.build from within the /usr/openv/volmgr/bin directory.  Therefore, the new sg.conf and sg.links files were created in the /usr/openv/volmgr/bin directory.  Subsequently, the sg.install was copying the files from the /usr/openv/volmgr/bin/driver directory which were never updated.  

    I copied the newly built sg.conf and sg.links file to the /usr/openv/volmgr/bin/driver directory and executed the sg.install script.  Voila!!!  Total success!

    Thanks again, Marianne

    Creole-Kid.

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

    root@tigerfish:/usr/openv/volmgr/bin/driver# cd ..

    root@tigerfish:/usr/openv/volmgr/bin# cp sg.conf driver
    root@tigerfish:/usr/openv/volmgr/bin# cp sg.links driver
    root@tigerfish:/usr/openv/volmgr/bin# cd driver
     
    ===========================================
    root@tigerfish:/usr/openv/volmgr/bin/driver# more 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;
    name="sg" parent="fp" target=0 lun=0 fc-port-wwn="50050763124c0207";
    name="sg" parent="fp" target=0 lun=1 fc-port-wwn="50050763124c0207";
    name="sg" parent="fp" target=0 lun=0 fc-port-wwn="50050763124c0016";
    name="sg" parent="fp" target=0 lun=1 fc-port-wwn="50050763124c0016";
    name="sg" parent="fp" target=0 lun=0 fc-port-wwn="50050763124c0162";
    name="sg" parent="fp" target=0 lun=1 fc-port-wwn="50050763124c0162";
    name="sg" parent="fp" target=0 lun=0 fc-port-wwn="50050763124c0149";
    name="sg" parent="fp" target=0 lun=1 fc-port-wwn="50050763124c0149";
    ======================================================
    root@tigerfish:/usr/openv/volmgr/bin/driver# more 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
    type=ddi_pseudo;name=sg;addr=w50050763124c0207,0;       sg/c\N0t\A1l0
    type=ddi_pseudo;name=sg;addr=w50050763124c0207,1;       sg/c\N0t\A1l1
    type=ddi_pseudo;name=sg;addr=w50050763124c0016,0;       sg/c\N0t\A1l0
    type=ddi_pseudo;name=sg;addr=w50050763124c0016,1;       sg/c\N0t\A1l1
    type=ddi_pseudo;name=sg;addr=w50050763124c0162,0;       sg/c\N0t\A1l0
    type=ddi_pseudo;name=sg;addr=w50050763124c0162,1;       sg/c\N0t\A1l1
    type=ddi_pseudo;name=sg;addr=w50050763124c0149,0;       sg/c\N0t\A1l0
    type=ddi_pseudo;name=sg;addr=w50050763124c0149,1;       sg/c\N0t\A1l1
    # end SCSA devlinks
    root@tigerfish:/usr/openv/volmgr/bin/driver# ls
    sg                 sg.conf.all        sg.conf.template   sg.links           sg.links.sav       st.conf
    sg.conf            sg.conf.sav        sg.install         sg.links.all       sg.links.template  st.conf.sav
    root@tigerfish:/usr/openv/volmgr/bin/driver# ./sg.install
     
            Copied files to /kernel/drv/amd64.
     
    Doing add_drv of the sg driver
    Creating /dev/sg.
    Added entry in /etc/devlink.tab file.
    Made links in /dev/sg
    root@tigerfish:/usr/openv/volmgr/bin/driver# cd ..
    root@tigerfish:/usr/openv/volmgr/bin# ./sgscan
    /dev/sg/c0tw50050763124c0016l0: Tape (/dev/rmt/0): "IBM     ULTRIUM-HH5" 
    /dev/sg/c0tw50050763124c0149l0: Tape (/dev/rmt/3): "IBM     ULTRIUM-HH5" 
    /dev/sg/c0tw50050763124c0162l0: Tape (/dev/rmt/2): "IBM     ULTRIUM-HH5" 
    /dev/sg/c0tw50050763124c0207l0: Tape (/dev/rmt/1): "IBM     ULTRIUM-HH5" 
    /dev/sg/c0tw50050763124c0207l1: Changer: "QUALSTARRLS-85"
    ========================================================