Netbackup Robot Driver

Only tape drives use 'nstx' device names, not the robot.

Robot uses /dev/sg device name.

Please show us output of '/usr/openv/volmgr/bin/scan' command. 

PS:

Have you had a look at  the Linux chapter in NetBackup Device Configuration Guide as suggested in your other post from yesterday? 
This one:  Drivers 

Dear Marianne,

plz find the output

It seems that 'scan' is not seeing any devices?

Have you checked that the OS can see devices with 'cat /proc/scsi/scsi' as suggested in Device Config Guide?

Also see the following extract from the same manual:

About the Linux 2.6 kernel tape drive device files
For tape drive device files, NetBackup uses the /dev/nstx files (n indicates the no
rewind device file). The Linux driver should create the device files automatically.
If the device files do not exist, see the Linux documentation for information about
how to create them.
 

PS:
Is it possible that you can copy the text instead of taking screenshots?
 

Thanks Marianne.

pls find below o/p

 ls -l /dev/sg*
crw-rw---- 1 root disk 21, 0 Apr 30 20:14 /dev/sg0
crw-rw---- 1 root disk 21, 1 Apr 30 20:14 /dev/sg1
crw-rw---- 1 root disk 21, 2 Apr 30 20:14 /dev/sg2
crw-rw---- 1 root disk 21, 3 Apr 30 20:14 /dev/sg3
 

But It is not showing for nst

ls -l /dev/nst*
ls: /dev/nst*: No such file or directory

should I need to create the nst manually and how to create.

Have you used lsmod command (as per Device Config Guide) to check that st and sg drivers are loaded?

Please show us output of '/sbin/lsmod' and 'cat /proc/scsi/scsi'.

You really need to speak to your Linux support team. 

All I know is what the manual says:

The Linux driver should create the device files automatically.
If the device files do not exist, see the Linux documentation for information about
how to create them.
 

As a Backup Admin/Support person, this is my requirement before getting involved from NBU side.

Visibility of devices at OS level is between the SAN/Storage Admins and the server/Linux admins.

PS:
As per my post in your other discussion, please double-check OS version with:
'cat /etc/redhat-release'.

Hi Marianne,

pls find the Output...

 /sbin/lsmod
Module                  Size  Used by
st                     39161  0
sr_mod                 15751  0
cdrom                  41063  1 sr_mod
fuse                   73115  0
8021q                  20014  0
garp                    7289  1 8021q
stp                     2139  1 garp
llc                     5560  2 garp,stp
bonding               122479  0
ipv6                  333733  60
dm_round_robin          2491  0
dm_multipath           19096  1 dm_round_robin
uinput                  8505  0
microcode             113888  0
pcspkr                  1966  0
ghes                    7081  0
hed                     2306  1 ghes
sxge                   38527  0
sg                     30233  0

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

cat /proc/scsi/scsi
Attached devices:
Host: scsi4 Channel: 01 Id: 00 Lun: 00
  Vendor: LSI      Model: Logical Volume   Rev: 3000
  Type:   Direct-Access                    ANSI  SCSI revision: 06
Host: scsi4 Channel: 00 Id: 00 Lun: 00
  Vendor: HITACHI  Model: H109060SESUN600G Rev: A606
  Type:   Direct-Access                    ANSI  SCSI revision: 06
Host: scsi4 Channel: 00 Id: 01 Lun: 00
  Vendor: HITACHI  Model: H109060SESUN600G Rev: A606
  Type:   Direct-Access                    ANSI  SCSI revision: 06
Host: scsi5 Channel: 00 Id: 00 Lun: 00
  Vendor: ORACLE   Model: SSM              Rev: PMAP
  Type:   Direct-Access                    ANSI  SCSI revision: 00
 

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

Your OS is not seeing the robot or tape drives.

Please check with your SAN/Storage Admins and the server/Linux admins as suggested previously.

There is honestly nothing we can do from NBU point of view.

Once 'cat /proc/scsi/scsi' and 'scan' can see the devices, you can proceed to add them to NBU using the Device Config Wizard.

Thanks a lot Marianne...

issue has been resolved now..we performed Zoning again and its work....