cancel
Showing results for 
Search instead for 
Did you mean: 

missing path issues

Android
Level 6
Partner Accredited Certified

OK I'll try to make this as clear as possible on the first run.  The end user is running NetBackup 6.5.1 on a Solaris server. They have 10 physical tape drives and 18 virtual tape drives. They are connected through a FC SAN on Cisco switches using Qlogic HBA's


Initially they had "missing path" reported for two of the physical drives.  Acting on their own they decided to run sg.build before contacting anyone for help. Afterward they lost almost all of their paths because they did not run sg.build with the -ml or -mt switches.  

 

 When I first got involved I asked them to run from within the /volmgr/bin/driver directory, sg.build with the -ml 30 and -mt 30 to override their execution with the defaults.  They could not a boot -r at the time so I had them run a devfsadm.  This brought back all but one of the physical drives and only 5 of the 18 virtual drives from the VTL.  They were finally able to schedule a boot -r and there has been no change in behavior.  Below you will find the output of sgscan and tpconfig -d:

 

bash-3.00# ./sgscan
/dev/sg/c0tw200800a0b8138d34l0: Disk (/dev/rdsk/c2t200800A0B8138D34d0): "STK     BladeCtlr B220"
/dev/sg/c0tw200800a0b8138d34l1: Disk (/dev/rdsk/c2t200800A0B8138D34d1): "STK     BladeCtlr B220"

/dev/sg/c0tw200900a0b8138d34l0: Disk (/dev/rdsk/c3t200900A0B8138D34d0): "STK     BladeCtlr B220"

/dev/sg/c0tw200900a0b8138d34l1: Disk (/dev/rdsk/c3t200900A0B8138D34d1): "STK     BladeCtlr B220"

/dev/sg/c0tw2102001b32455c81l0: Tape (/dev/rmt/26): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw2102001b32455c81l1: Tape (/dev/rmt/25): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw2103001b32655c81l0: Changer: "SUN     VTL"

/dev/sg/c0tw2103001b32655c81l1: Tape (/dev/rmt/35): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500000e014ecafc1l0: Disk (/dev/rdsk/c1t1d0): "FUJITSU MAW3147FCSUN146G"

/dev/sg/c0tw500000e014ee7c41l0: Disk (/dev/rdsk/c1t0d0): "FUJITSU MAW3147FCSUN146G"

/dev/sg/c0tw500104f0006dac2fl0: Changer: "STK     L700"

/dev/sg/c0tw50050763006102b2l0: Tape (/dev/rmt/9): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500507630061773el0: Tape (/dev/rmt/17): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw5005076300618818l0: Tape (/dev/rmt/15): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw5005076313602a21l0: Tape (/dev/rmt/16): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500507631360a75bl0: Tape (/dev/rmt/13): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500507631360a7eel0: Tape (/dev/rmt/10): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500507631360a875l0: Tape (/dev/rmt/12): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500507631360a87cl0: Tape (/dev/rmt/14): "IBM     ULTRIUM-TD2"
bash-3.00#

bash-3.00# ./tpconfig -d

Id  DriveName           Type   Residence

   Drive Path                                                       Status

****************************************************************************

0   IBMULTRIUM-TD20      hcart2 TLD(0)  DRIVE=1
   /dev/rmt/15cbn                                                   UP

1   IBMULTRIUM-TD21      hcart2 TLD(0)  DRIVE=2
   /dev/rmt/9cbn                                                    UP

2   IBMULTRIUM-TD22      hcart2 TLD(0)  DRIVE=3
   /dev/rmt/17cbn                                                   UP

3   IBMULTRIUM-TD23      hcart2 TLD(0)  DRIVE=4
   /dev/rmt/8cbn                                                    DOWN

4   IBMULTRIUM-TD24      hcart2 TLD(0)  DRIVE=5
   /dev/rmt/16cbn                                                   UP

5   IBMULTRIUM-TD25      hcart2 TLD(0)  DRIVE=6
   MISSING_PATH:/dev/rmt/7cbn:1110247551                            DOWN

6   IBMULTRIUM-TD26      hcart2 TLD(0)  DRIVE=7
   /dev/rmt/10cbn                                                   UP

7   IBMULTRIUM-TD27      hcart2 TLD(0)  DRIVE=8
   /dev/rmt/12cbn                                                   UP

8   IBMULTRIUM-TD28      hcart2 TLD(0)  DRIVE=9
   /dev/rmt/13cbn                                                   UP

9   IBMULTRIUM-TD29      hcart2 TLD(0)  DRIVE=10
   /dev/rmt/14cbn                                                   UP

10  IBM.ULTRIUM-TD2.000  hcart2 TLD(1)  DRIVE=2
   /dev/rmt/35cbn                                                   UP

11  IBM.ULTRIUM-TD2.001  hcart2 TLD(1)  DRIVE=4
   MISSING_PATH:/dev/rmt/34cbn:0TI0D00204                           DOWN

12  IBM.ULTRIUM-TD2.002  hcart2 TLD(1)  DRIVE=6
   MISSING_PATH:/dev/rmt/33cbn:0TI0D00206                           DOWN

13  IBM.ULTRIUM-TD2.003  hcart2 TLD(1)  DRIVE=8
   MISSING_PATH:/dev/rmt/32cbn:0TI0D00208                           DOWN

14  IBM.ULTRIUM-TD2.004  hcart2 TLD(1)  DRIVE=10
   MISSING_PATH:/dev/rmt/31cbn:0TI0D0020A                           DOWN

15  IBM.ULTRIUM-TD2.005  hcart2 TLD(1)  DRIVE=12
   MISSING_PATH:/dev/rmt/30cbn:0TI0D0020C                           DOWN

16  IBM.ULTRIUM-TD2.006  hcart2 TLD(1)  DRIVE=14
   MISSING_PATH:/dev/rmt/29cbn:0TI0D0020E                           DOWN

17  IBM.ULTRIUM-TD2.007  hcart2 TLD(1)  DRIVE=16
   MISSING_PATH:/dev/rmt/28cbn:0TI0D0020G                           DOWN

18  IBM.ULTRIUM-TD2.008  hcart2 TLD(1)  DRIVE=18
   MISSING_PATH:/dev/rmt/27cbn:0TI0D0020I                           DOWN

19  IBM.ULTRIUM-TD2.009  hcart2 TLD(1)  DRIVE=1
   /dev/rmt/26cbn                                                   UP

20  IBM.ULTRIUM-TD2.010  hcart2 TLD(1)  DRIVE=3
   /dev/rmt/25cbn                                                   UP

21  IBM.ULTRIUM-TD2.011  hcart2 TLD(1)  DRIVE=5
   MISSING_PATH:/dev/rmt/24cbn:0TI0D00205                           DOWN

22  IBM.ULTRIUM-TD2.012  hcart2 TLD(1)  DRIVE=7
   MISSING_PATH:/dev/rmt/23cbn:0TI0D00207                           DOWN

23  IBM.ULTRIUM-TD2.013  hcart2 TLD(1)  DRIVE=9
   MISSING_PATH:/dev/rmt/22cbn:0TI0D00209                           DOWN

24  IBM.ULTRIUM-TD2.014  hcart2 TLD(1)  DRIVE=11
   MISSING_PATH:/dev/rmt/21cbn:0TI0D0020B                           DOWN

25  IBM.ULTRIUM-TD2.015  hcart2 TLD(1)  DRIVE=13
   MISSING_PATH:/dev/rmt/20cbn:0TI0D0020D                           DOWN

26  IBM.ULTRIUM-TD2.016  hcart2 TLD(1)  DRIVE=15
   MISSING_PATH:/dev/rmt/19cbn:0TI0D0020F                           DOWN

27  IBM.ULTRIUM-TD2.017  hcart2 TLD(1)  DRIVE=17
   MISSING_PATH:/dev/rmt/18cbn:0TI0D0020H                           DOWN


Currently defined robotics are:

TLD(0)     robotic path = /dev/sg/c0tw500104f0006dac2fl0

TLD(1)     robotic path = /dev/sg/c0tw2103001b32655c81l0

 

 

 

 Somewhat at a loss here.  If the devices are visible to the OS why are they not being picked up by the application? Any help?

1 ACCEPTED SOLUTION

Accepted Solutions

Android
Level 6
Partner Accredited Certified
This issue has been resolved. After looking at the sg.conf file again it was realized that the correct options were not passed to the -ml switch when it was run the second time with options and only three LUN's were being built for each target.

View solution in original post

3 REPLIES 3

Android
Level 6
Partner Accredited Certified
This issue has been resolved. After looking at the sg.conf file again it was realized that the correct options were not passed to the -ml switch when it was run the second time with options and only three LUN's were being built for each target.

Sanjeev_Rohila
Not applicable

Drive Name               Label   Ready  RecMID  ExtMID  Wr.Enbl.  Type
    Host                       DrivePath                            Status
=============================================================================
IBM.ULTRIUM-TD3.000      No      No                     No        hcart3
    brc-backup11               {4,0,1,0}                            TLD
    g1_ecs2b_ms001             {3,0,0,0}                            TLD
    g1_ecs3b_ms001             {3,0,0,0}                            TLD
    g1gsn1bms021               {4,0,2,0}                            TLD
    g1gsn1bms023               {4,1,0,0}                            TLD
    g1gsn1bms024               {4,1,0,0}                            SCAN-TLD

IBM.ULTRIUM-TD3.001      No      No                     No        hcart3-Clean
    brc-backup11               {4,0,3,0}                            TLD
    g1_ecs3b_ms001             {3,0,1,0}                            TLD
    g1gsn1bms021               MISSING_DRIVE:F09956E094             DOWN-TLD
    g1gsn1bms022               {4,1,2,0}                            TLD
    g1gsn1bms023               {4,1,2,0}                            TLD
    g1gsn1bms024               {4,1,2,0}                            SCAN-TLD

IBM.ULTRIUM-TD3.002      No      No                     No        hcart3
    brc-backup11               {4,0,4,0}                            TLD
    g1_ecs3b_ms001             {3,0,2,0}                            TLD
    g1gsn1bms021               MISSING_DRIVE:F09956E090             DOWN-TLD
    g1gsn1bms023               {4,1,1,0}                            SCAN-TLD
    g1gsn1bms024               {4,1,1,0}                            TLD

IBM.ULTRIUM-TD3.003      No      No                     No        hcart3
    brc-backup11               {4,0,5,0}                            SCAN-TLD
    g1_ecs3b_ms001             {3,0,4,0}                            TLD
    g1gsn1bms021               MISSING_DRIVE:F09956E09C             DOWN-TLD
    g1gsn1bms023               MISSING_DRIVE:F09956E09C             DOWN-TLD

    g1gsn1bms024               {4,1,4,0}                            TLD

IBM.ULTRIUM-TD3.005      No      No                     No        hcart3
    brc-backup11               {4,0,7,0}                            TLD
    g1_ecs3b_ms001             {3,0,3,0}                            TLD
    g1gsn1bms021               MISSING_DRIVE:F09956E098             DOWN-TLD
    g1gsn1bms023               MISSING_DRIVE:F09956E098             DOWN-TLD

    g1gsn1bms024               {4,1,3,0}                            SCAN-TLD

Could someone help on this issue ??

Marianne
Level 6
Partner    VIP    Accredited Certified
Sanjeev, this issue has been resolved.

Please start a new thread and include details of you O/S and NBU versions.