Tape Drive Device state is Disabled in Device Configuration wizard

[Sushil_0488]

Hello All,

I have just started using NetBackup Software. I have installed NB 7.6.1 on RHEL 6.5 64-bit operating system hosted on IBM X3650M4 server.

This serve is used as Master as well as Media server. It is connected to IBM TS3100 tape using FC cable. (Direct connection)

Currently, I see issue while using the Device Configuration wizard on NB console.

I am getting NB tape drive device state as Unusable. Also when I click on properties, It is showing the status as Disabled 

Going further with Device configuration task will result in "Invalid Parameter (20)" notification.

I am attaching both screenshot here.

[Marianne]

We first need to see what the OS sees. Please show us output of 'scan' command (in /usr/openv/volmgr/bin)

[Sushil_0488]

Hello Marianne,

Below is the output of scan:

************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name  : "/dev/sg3"
Passthru Name: "/dev/sg3"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     3573-TL         D.00"
Vendor ID  : "IBM     "
Product ID : "3573-TL         "
Product Rev: "D.00"
Serial Number: "00L2U78BB844_LL0"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     3573-TL         00L2U78BB844_LL0"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-5
Number of Drives : 1
Number of Slots  : 21
Number of Media Access Ports: 1
Drive 1 Serial Number      : "10WT053429"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "-"
Passthru Name: "/dev/sg2"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     ULT3580-TD6     F9A0"
Vendor ID  : "IBM     "
Product ID : "ULT3580-TD6     "
Product Rev: "F9A0"
Serial Number: "10WT053429"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     ULT3580-TD6     10WT053429"
Device Type    : SDT_TAPE
NetBackup Drive Type: 16
Removable      : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x10000

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

Output of

$ cat /proc/scsi/scsi

Attached devices:
Host: scsi0 Channel: 02 Id: 00 Lun: 00
  Vendor: IBM      Model: ServeRAID M5110e Rev: 3.24
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi4 Channel: 00 Id: 00 Lun: 00
  Vendor: IBM SATA Model:  DEVICE 81Y3672  Rev: SA82
  Type:   CD-ROM                           ANSI  SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 00
  Vendor: IBM      Model: ULT3580-TD6      Rev: F9A0
  Type:   Sequential-Access                ANSI  SCSI revision: 06
Host: scsi2 Channel: 00 Id: 00 Lun: 01
  Vendor: IBM      Model: 3573-TL          Rev: D.00
  Type:   Medium Changer                   ANSI  SCSI revision: 05

[sdo]

What do these show?

lsssci -g

lsblk

[Marianne]

The output seems fine to me. Probably good idea to confirm that NetBackup has latest Device Mappings installed. https://sort.veritas.com/checklist/install/nbu_device_mapping

[mph999]

Device Name  : "-"
Passthru Name: "/dev/sg2"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     ULT3580-TD6     F9A0"

There is no /dev/nstX path sowing for the device name - this is the 'data' path needed for the drive to work.

Here is an example from my Linux server showing what it should be like.

Device Name  : "/dev/nst0"
Passthru Name: "/dev/sg6"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     ULT3580-TD5     0103"
 

You have an OS issue, not a NBU issue.  However, as Mariaane suggests, ensuring the Device mappings are up-to-date is a good idea.

[Marianne]

Oops! Missed that. You need to have the Linux st and sg driver installed.

[Sushil_0488 · Accepted solution]

Dear Marianne & mph999,

Device mapping was upto date already.

Ideally, nst0 devices should have been created at the server start time automatically.

However, in my case, lin_tape daemon was running on server and I think this was restricting the nst0 device creation.

So, I stopped the lin_tape service.

Server was reboot after this and the device created now.

************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name  : "/dev/sg3"
Passthru Name: "/dev/sg3"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     3573-TL         D.00"
Vendor ID  : "IBM     "
Product ID : "3573-TL         "
Product Rev: "D.00"
Serial Number: "00L2U78BB844_LL0"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     3573-TL         00L2U78BB844_LL0"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-5
Number of Drives : 1
Number of Slots  : 21
Number of Media Access Ports: 1
Drive 1 Serial Number      : "10WT053429"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "/dev/nst0"
Passthru Name: "/dev/sg2"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     ULT3580-TD6     F9A0"
Vendor ID  : "IBM     "
Product ID : "ULT3580-TD6     "
Product Rev: "F9A0"
Serial Number: "10WT053429"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     ULT3580-TD6     10WT053429"
Device Type    : SDT_TAPE
NetBackup Drive Type: 16
Removable      : Yes
Device Supports: SCSI-6
Flags : 0x0
Reason: 0x0
 

Any idea, if lin_tape daemon need to be started again ?

Thanks

Sushil