Video Screencast Help

NetBackup 7.5.0.3 not detecting IBM TS3310 robot

Created: 23 Jan 2013 • Updated: 25 Jan 2013 | 15 comments
Willie_SA's picture
This issue has been solved. See solution.

OS           -        UNIX Solaris 10 on SUN SPARC 64 bit

NBU         -       7.5.0.3

When attempting to create storage devices in NBU the robot is not detected. Robot fibre connected via switch.

CFGADM shows drives but not robot.

I looked at the compatibility list and found:

System Storage TS3310

(Machine Type 3576) -

Fibre Channel

IBM^^^^^3576-MTL Multi LUN TLD 160G, 200G, 400G, 606G IBM medium changer driver 6.1.4.8 and above is compatible on Windows.

 

 

Does this mean that the robot is supported/compatible on Windows only??

 

Discussion Filed Under:

Comments 15 CommentsJump to latest comment

Marianne's picture

You may have to re-create the NBU sg drivers to add robot device name.

Please post output of sgscan.

*** EDIT ***

as well as output of this as well:

# cd /dev/rmt
# ls -l *cbn

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Willie_SA's picture

Thank you - will get outputs.

I do not think any sgdrivers has been/was loaded.

Will update shortly.

Willie_SA's picture

Output as requested,

I think I see the 2 drives only.

(xfmedia):/dev/rmt# /usr/openv/volmgr/bin/sgscan

#

#WARNING: detected StorEdge Network Foundation connected devices not in

#         SG configuration file:

#

#    Device World Wide Port Name 5006016d3ea02a0f

#    Device World Wide Port Name 500601693ea02a0f

#    Device World Wide Port Name 500308c09add2005

#    Device World Wide Port Name 5006016d3ea01b96

#    Device World Wide Port Name 500601683ea01b96

#    Device World Wide Port Name 500601653ea02a0f

#    Device World Wide Port Name 500601603ea02a0f

#    Device World Wide Port Name 500308c09add209d

#    Device World Wide Port Name 500601653ea01b96

#    Device World Wide Port Name 500601603ea01b96

#

#    See /usr/openv/volmgr/NetBackup_DeviceConfig_Guide.txt chapter

#    "Special configuration for "Sun StorEdge Network Foundation" HBA/Driver"

#    for information on how to use sg.build and sg.install to

#    configure these devices

#

 

/dev/sg/c0t0l0: Disk (/dev/rdsk/c1t0d0): "FUJITSU MAP3367N SUN36G"

/dev/sg/c0t1l0: Disk (/dev/rdsk/c1t1d0): "FUJITSU MAP3367N SUN36G"

 

------------------

 

 

(xfmedia):/dev/rmt# ls -l *cbn

lrwxrwxrwx   1 root     root          83 Jan 17 14:44 0cbn -> ../../devices/pci@1e,600000/pci@3/fibre-channel@5/fp@0,0/st@w500308c09add209d,0:cbn

lrwxrwxrwx   1 root     root          83 Jan 17 14:51 1cbn -> ../../devices/pci@1e,600000/pci@3/fibre-channel@4/fp@0,0/st@w500308c09add2005,0:cbn

 

Willie_SA's picture

Hi Marianne,

 

Just to raise my first concern again - are we sure this library is UNIX Solaris compatible/capable?

Marianne's picture

Yes, it is compatible with all supported NBU media servers.
HCL makes special reference to Windows drivers for the medium changer that is not applicable to any other OS.

sgscan sees 2 disks only - please rebuild sg driver:

 

Do the following:

# 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

 

(I am aware that Martin's method is different, but as I've said - this has always worked for me.)

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
mph999's picture

Some of the IBM libraries use one of the drives as a 'control path' to make the robot visiable to the OS.

This is set on the library, and whatever drive is used, the robot is the 'same path as the drive' but an extra lun'.

If the library works this way , you have to add an extra line in the sg.conf and sg.links files using the same WWN as the WWN of the drive, but give it a different lun than the drive.

Note, not sure is all IBM libraries work this way.

However, first thing to do is see if the OS can see the robot.

cfgadm -al -show_FCP_dev

Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Willie_SA's picture

Hi,

 

Let me do the Marianne move and lets see what the sg scan looks like after that.

Will post sg scan output.

TX

Willie_SA's picture

OK after the commands/process it seems that the sgscan now picked up 2 connections to robot and 1 connection each to a drive = 2 x drives.
I asked for the output of cfgadm -al to see if robot and drives are in output.

(xfmedia):/usr/openv/volmgr/bin/driver# /usr/openv/volmgr/bin/sgscan

/dev/sg/c0t0l0: Disk (/dev/rdsk/c1t0d0): "FUJITSU MAP3367N SUN36G"
/dev/sg/c0t1l0: Disk (/dev/rdsk/c1t1d0): "FUJITSU MAP3367N SUN36G"
/dev/sg/c0tw500308c09add2005l0: Tape (/dev/rmt/1): "IBM ULT3580-TD3"
/dev/sg/c0tw500308c09add2005l1: Changer: "IBM 3576-MTL"
/dev/sg/c0tw500308c09add209dl0: Tape (/dev/rmt/0): "IBM ULT3580-TD3"
/dev/sg/c0tw500308c09add209dl1: Changer: "IBM 3576-MTL"
/dev/sg/c0tw500601683ea01b96l0: Disk (/dev/rdsk/c2t500601683EA01B96d0): "DGC LUNZ"
/dev/sg/c0tw500601693ea02a0fl0: Disk (/dev/rdsk/c2t500601693EA02A0Fd0): "DGC LUNZ"
/dev/sg/c0tw5006016d3ea01b96l0: Disk (/dev/rdsk/c2t5006016D3EA01B96d0): "DGC LUNZ"
/dev/sg/c0tw5006016d3ea02a0fl0: Disk (/dev/rdsk/c2t5006016D3EA02A0Fd0): "DGC LUNZ"

Marianne's picture

As per Martin's post, the robot is visibile as lun 1 via both tape drives.

You are good to go - run Device Config Wizard.
NBU will config robot on one path only.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Willie_SA's picture

Here output of new 'cfgadm -al

Seems there is still no robot/mchanger

(xfmedia):/# cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c0::dsk/c0t0d0 CD-ROM connected configured unknown
c1 scsi-bus connected configured unknown
c1::dsk/c1t0d0 disk connected configured unknown
c1::dsk/c1t1d0 disk connected configured unknown
c1::sg/c0t0l0 unknown connected configured unknown
c1::sg/c0t0l1 unknown connected configured unknown
c1::sg/c0t1l0 unknown connected configured unknown
c1::sg/c0t1l1 unknown connected configured unknown
c1::sg/c0t2l0 unknown connected configured unknown
c1::sg/c0t2l1 unknown connected configured unknown
c1::sg/c0t3l0 unknown connected configured unknown
c1::sg/c0t3l1 unknown connected configured unknown
c1::sg/c0t4l0 unknown connected configured unknown
c1::sg/c0t4l1 unknown connected configured unknown
c1::sg/c0t5l0 unknown connected configured unknown
c1::sg/c0t5l1 unknown connected configured unknown
c1::sg/c0t6l0 unknown connected configured unknown
c1::sg/c0t6l1 unknown connected configured unknown
c2 fc-fabric connected configured unknown
c2::500308c09add2005 tape connected configured unknown
c2::500601683ea01b96 disk connected configured unknown
c2::500601693ea02a0f disk connected configured unknown
c2::5006016d3ea01b96 disk connected configured unknown
c2::5006016d3ea02a0f disk connected configured unknown
c3 fc-fabric connected configured unknown
c3::500308c09add209d tape connected configured unknown
c3::500601603ea01b96 disk connected configured unknown
c3::500601603ea02a0f disk connected configured unknown
c3::500601653ea01b96 disk connected configured unknown
c3::500601653ea02a0f disk connected configured unknown
c4 scsi-bus connected configured unknown
c4::sg/c1t0l0 unknown connected configured unknown
c4::sg/c1t0l1 unknown connected configured unknown
c4::sg/c1t1l0 unknown connected configured unknown
c4::sg/c1t1l1 unknown connected configured unknown
c4::sg/c1t2l0 unknown connected configured unknown
c4::sg/c1t2l1 unknown connected configured unknown
c4::sg/c1t3l0 unknown connected configured unknown
c4::sg/c1t3l1 unknown connected configured unknown
c4::sg/c1t4l0 unknown connected configured unknown
c4::sg/c1t4l1 unknown connected configured unknown
c4::sg/c1t5l0 unknown connected configured unknown
c4::sg/c1t5l1 unknown connected configured unknown
c4::sg/c1t6l0 unknown connected configured unknown
c4::sg/c1t6l1 unknown connected configured unknown
usb0/1 unknown empty unconfigured ok
usb0/2 unknown empty unconfigured ok

Willie_SA's picture

Martin - can you please double check the command :

(xfmedia):/# cfgadm -al -show_FCP_dev
cfgadm: sub-option "how_FCP_dev" unknown
cfgadm: print or sort fields must be one of: ap_id, r_state, o_state, condition, status_time, status_time_p, info, type, busy, physid, class

mph999's picture

Ahh, yes, my error, missed the o

cfgadm -al -o show_FCP_dev

M

 

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Marianne's picture

cfgadm is only reporting the wwn for the tapes, not the lun numbers. As you can see in sgscan output, the robot is lun1 on the tape drives' wwn.

I would go ahead with Device Config Wizard at this point.

One last check perhaps is:
/usr/openv/volmgr/bin/scan

This will verify that robot knows about the drives in the robot, number of slots, etc...

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Willie_SA's picture

Marianne procedure worked - sgscan.
We could detect robot and drives.
Thank you