Solved: How to connect Master server with two shared robot...

tigerlover · ‎12-03-2014

The robot can be seen from system.

#cfgadm al

c4::500104f000affbb9 med-changer connected configured unknown

I finished all steps to do sg build and install but sgcan still didn't show the robot even though I can see them under /dev/sg

root@dvifap13:/dev/sg # ls -l | grep bb9
lrwxrwxrwx 1 root root 91 Dec 3 14:50 c0tw500104f000affbb9l0 -> ../../devices/pci@7c0/pci@0/pci@1/pci@0,2/fibre-channel@2/fp@0,0/sg@w500104f000affbb9,0:raw
lrwxrwxrwx 1 root root 91 Dec 3 14:50 c0tw500104f000affbb9l1 -> ../../devices/pci@7c0/pci@0/pci@1/pci@0,2/fibre-channel@2/fp@0,0/sg@w500104f000affbb9,1:raw

I manually created the robot, but it shows not enabled. I used the device configuration Wizard, it didn't show the newly configured robot, all drives in that library shows standalone drives.Please let me know how to configure to make the master server be able to see the shared two robots in the same library.

Thanks!

mph999 · ‎12-06-2014

OK, if the robot is there twice this might or might not be valid.

Some libraries use a control path, that is the robot is access via one of the drives, but a different lun, so you would see the WWN twice, once for the drive and once for the robot which would be correct.

If the robot is accessed via a direct link, you would only need it once - but if it was listed twice it shouldn't cause a problem, you would just have an extra unused file.

As a matter of interest, is this a IBM 3584 library ?

Is there are corresponding file in /dev/sg (look for the WWN) ?

If so, there should be a long path, if you take this path (or might be a single file ) and sticj /dev/sg/ infront of it ...

Run

/usr/openv/volmgr/bin/scsi_command -d /dev/sg/<file or path>

Does this return the scsi inquiry string for the library ?

From the look of the file snippets above, and if that file is there in /dev/sg it looks correct from a NBU view - there is always the possibility there is an issue elsewhere.

Martin

View solution in original post

mph999 · ‎12-03-2014

Until scan our scan shows the library, the wizard won't add it, and even if manually added it won't work.

Try these steps ... this is Mariannes method, similar to mine but it came up in the first search ...

# 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'm going to guess when you built the sg driver you followed atn that said to use the -ml and -my options in sg.build, which mostly these days is not required ( of os device files show wwn as opposed to target/ lun

if you are on Solaris x86 as opposed to Sparc then you'll need to disable mpxio as well.

If this still fails we'll need to see the sg.conf and links files from the bin/driver dir, output of ls -al /dev/rmt and cfgadm -al and cfgadm -al -o show_FCP_dev outputs.

Marianne · ‎12-04-2014

I am curious to know more about your environment.

Especially details about your subject mentioning 'two shared robots in one library'.

Please also tell us if this is Solaris SPARC or x86.
HBA on the server?

Does the robot have a unique WWN or shared with tape drive(s)?
Show us output of:
ls -l /dev/rmt/*cbn

Handy NetBackup Links

tigerlover · ‎12-04-2014

It is running on Sloaris 10. HBA on the Server but connecting through a SAN switch. Robot have unique WWN.

This host is connecting to three different libraries. One of them ( the new one I want to configure ) have dual robots and the library is partioned to two partitions. Robots are shared with another partition which is using for another environment.The "ffbb9" is the one NBU can not see.

c2::500104f00060540e           med-changer connected    configured   unknown
c2::500104f000605411           tape         connected    configured   unknown
c2::500104f000605414           tape         connected    configured   unknown
c2::500104f000605417           tape         connected    configured   unknown
c2::500104f00060541a           tape         connected    configured   unknown
c2::500104f000605444           tape         connected    configured   failed
c2::500104f00060544a           tape         connected    configured   unknown
c2::500104f00060a3dc           tape         connected    configured   unknown
c2::500104f00060a3e2           tape         connected    configured   unknown
c2::500104f00060a3e8           tape         connected    configured   unknown
c2::500104f00060a3eb           tape         connected    configured   unknown
c2::500104f00060a3f7           tape         connected    configured   failing
c2::500104f000affc2e           tape         connected    configured   failing
c2::500104f000affc31           tape         connected    configured   unknown
c2::500104f000affc34           tape         connected    configured   unknown
c2::500104f000affc3a           tape         connected    configured   unknown
c2::500104f000affc46           tape         connected    configured   unknown
c2::500104f000affc52           tape         connected    configured   unknown
c2::500104f000affc6a           tape         connected    configured   unknown
c2::500601673b202e44           disk         connected    configured   unknown
c2::500601673ca00c5d           disk         connected    configured   unknown
c2::500601683ca00c5d           disk         connected    configured   unknown
c2::5006016d3b242e44           disk         connected    configured   unknown
c3                             fc-fabric    connected    unconfigured unknown
c4                             fc-fabric    connected    configured   unknown
c4::500104f00060541d           tape         connected    configured   unknown
c4::500104f000605420           tape         connected    configured   unknown
c4::500104f000605423           tape         connected    configured   failed
c4::500104f000605426           tape         connected    configured   failing
c4::500104f000605429           tape         connected    configured   unknown
c4::500104f00060542c           tape         connected    configured   unknown
c4::500104f00060a3ca           med-changer connected    configured   unknown
c4::500104f00060a3d6           tape         connected    configured   failing
c4::500104f00060a3fa           tape         connected    configured   unknown
c4::500104f00060a400           tape         connected    configured   unknown
c4::500104f00060a403           tape         connected    configured   unknown
c4::500104f000affbb9           med-changer connected    configured   unknown
c4::500104f000affc37           tape         connected    configured   unknown
c4::500104f000affc3d           tape         connected    configured   unknown
c4::500104f000affc49           tape         connected    configured   unknown
c4::500104f000affc55           tape         connected    configured   unknown
c4::500104f000affc5e           tape         connected    configured   unknown
c4::500104f000affc61           tape         connected    configured   unknown
c4::500104f000affc6d           tape         connected    configured   failing
c4::500601603b202e44           disk         connected    configured   unknown
c4::500601603ca00c5d           disk         connected    configured   failing
c4::5006016e3b202e44           disk         connected    configured   unknown
c4::5006016e3ca00c5d           disk         connected    configured   unknown

root@dvifap12:/ # ls -al /dev/rmt | wc -l
843

root@dvifap12:/ # ls -l /dev/rmt/*cbn | wc -l
35

tigerlover · ‎12-04-2014

mph999, I tried your steps but the host still can not see the new robot.

The Master server is running on Solaris 10 and it clustered. The robot has a unique WWN not shared with drives.Master server has HBA cards but connecting to the robot through a SAN switch.It is connecting to 3 libraries the same time. One of the library( new one )has dual robots which are shared with another partition. The other partition is used by a different Master server.

"bb9" is the robot host can see but sgscan can not see.

c2::500104f00060540e           med-changer connected    configured   unknown
c2::500104f000605411           tape         connected    configured   unknown
c2::500104f000605414           tape         connected    configured   unknown
c2::500104f000605417           tape         connected    configured   unknown
c2::500104f00060541a           tape         connected    configured   unknown
c2::500104f000605444           tape         connected    configured   failed
c2::500104f00060544a           tape         connected    configured   unknown
c2::500104f00060a3dc           tape         connected    configured   unknown
c2::500104f00060a3e2           tape         connected    configured   unknown
c2::500104f00060a3e8           tape         connected    configured   unknown
c2::500104f00060a3eb           tape         connected    configured   unknown
c2::500104f00060a3f7           tape         connected    configured   failing
c2::500104f000affc2e           tape         connected    configured   failing
c2::500104f000affc31           tape         connected    configured   unknown
c2::500104f000affc34           tape         connected    configured   unknown
c2::500104f000affc3a           tape         connected    configured   unknown
c2::500104f000affc46           tape         connected    configured   unknown
c2::500104f000affc52           tape         connected    configured   unknown
c2::500104f000affc6a           tape         connected    configured   unknown
c2::500601673b202e44           disk         connected    configured   unknown
c2::500601673ca00c5d           disk         connected    configured   unknown
c2::500601683ca00c5d           disk         connected    configured   unknown
c2::5006016d3b242e44           disk         connected    configured   unknown
c3                             fc-fabric    connected    unconfigured unknown
c4                             fc-fabric    connected    configured   unknown
c4::500104f00060541d           tape         connected    configured   unknown
c4::500104f000605420           tape         connected    configured   unknown
c4::500104f000605423           tape         connected    configured   failed
c4::500104f000605426           tape         connected    configured   failing
c4::500104f000605429           tape         connected    configured   unknown
c4::500104f00060542c           tape         connected    configured   unknown
c4::500104f00060a3ca           med-changer connected    configured   unknown
c4::500104f00060a3d6           tape         connected    configured   failing
c4::500104f00060a3fa           tape         connected    configured   unknown
c4::500104f00060a400           tape         connected    configured   unknown
c4::500104f00060a403           tape         connected    configured   unknown
c4::500104f000affbb9           med-changer connected    configured   unknown
c4::500104f000affc37           tape         connected    configured   unknown
c4::500104f000affc3d           tape         connected    configured   unknown
c4::500104f000affc49           tape         connected    configured   unknown
c4::500104f000affc55           tape         connected    configured   unknown
c4::500104f000affc5e           tape         connected    configured   unknown
c4::500104f000affc61           tape         connected    configured   unknown
c4::500104f000affc6d           tape         connected    configured   failing
c4::500601603b202e44           disk         connected    configured   unknown
c4::500601603ca00c5d           disk         connected    configured   failing
c4::5006016e3b202e44           disk         connected    configured   unknown
c4::5006016e3ca00c5d           disk         connected    configured   unknown

root@dvifap12:/ # ls -al /dev/rmt | wc -l
843

root@dvifap12:/ # ls -l /dev/rmt/*cbn | wc -l
35

root@dvifap12:/ # sgscan
/dev/sg/c0t0l0: Disk (/dev/rdsk/c0t0d0): "FUJITSU MAY2073RCSUN72G"
/dev/sg/c0t1l0: Disk (/dev/rdsk/c0t1d0): "FUJITSU MAY2073RCSUN72G"
/dev/sg/c0tw500104f00060540el0: Changer: "STK     L700"
/dev/sg/c0tw500104f000605411l0: Tape (/dev/rmt/2): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500104f000605414l0: Tape (/dev/rmt/4): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500104f000605417l0: Tape (/dev/rmt/6): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500104f00060541al0: Tape (/dev/rmt/7): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500104f00060541dl0: Tape (/dev/rmt/17): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500104f000605420l0: Tape (/dev/rmt/19): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500104f000605423l0: Tape (/dev/rmt/20): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500104f000605426l0: Tape (/dev/rmt/12): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500104f000605429l0: Tape (/dev/rmt/13): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500104f00060542cl0: Tape (/dev/rmt/15): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500104f000605444l0: Tape (/dev/rmt/10): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500104f00060544al0: Tape (/dev/rmt/1): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500104f00060a3cal0: Changer: "STK     L700"
/dev/sg/c0tw500104f00060a3d6l0: Tape (/dev/rmt/18): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500104f00060a3dcl0: Tape (/dev/rmt/3): "IBM     ULT3580-TD2"
/dev/sg/c0tw500104f00060a3e2l0: Tape (/dev/rmt/5): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500104f00060a3e8l0: Tape (/dev/rmt/8): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500104f00060a3ebl0: Tape (/dev/rmt/9): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500104f00060a3f7l0: Tape (/dev/rmt/11): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500104f00060a3fal0: Tape (/dev/rmt/22): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500104f00060a400l0: Tape (/dev/rmt/16): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500104f00060a403l0: Tape (/dev/rmt/21): "IBM     ULTRIUM-TD2"
/dev/sg/c0tw500104f000affc2el0: Tape (/dev/rmt/32): "IBM     ULTRIUM-TD6"
/dev/sg/c0tw500104f000affc31l0: Tape (/dev/rmt/30): "IBM     ULTRIUM-TD6"
/dev/sg/c0tw500104f000affc34l0: Tape (/dev/rmt/31): "IBM     ULTRIUM-TD6"
/dev/sg/c0tw500104f000affc37l0: Tape (/dev/rmt/28): "IBM     ULTRIUM-TD6"
/dev/sg/c0tw500104f000affc3al0: Tape (/dev/rmt/29): "IBM     ULTRIUM-TD6"
/dev/sg/c0tw500104f000affc3dl0: Tape (/dev/rmt/26): "IBM     ULTRIUM-TD6"
/dev/sg/c0tw500104f000affc46l0: Tape (/dev/rmt/34): "IBM     ULTRIUM-TD6"
/dev/sg/c0tw500104f000affc49l0: Tape (/dev/rmt/27): "IBM     ULTRIUM-TD6"
/dev/sg/c0tw500104f000affc52l0: Tape (/dev/rmt/33): "IBM     ULTRIUM-TD6"
/dev/sg/c0tw500104f000affc55l0: Tape (/dev/rmt/24): "IBM     ULTRIUM-TD6"
/dev/sg/c0tw500104f000affc5el0: Tape (/dev/rmt/25): "IBM     ULTRIUM-TD6"
/dev/sg/c0tw500104f000affc61l0: Tape (/dev/rmt/23): "IBM     ULTRIUM-TD6"
/dev/sg/c0tw500104f000affc6al0: Tape (/dev/rmt/35): "IBM     ULTRIUM-TD6"
/dev/sg/c0tw500104f000affc6dl0: Tape (/dev/rmt/14): "IBM     ULTRIUM-TD6"
/dev/sg/c0tw500601603b202e44l0: Disk (/dev/rdsk/c4t500601603B202E44d0): "DGC     RAID 5"
/dev/sg/c0tw500601603ca00c5dl0: Disk (/dev/rdsk/c4t500601603CA00C5Dd0): "DGC     RAID 5"
/dev/sg/c0tw500601603ca00c5dl1: Disk (/dev/rdsk/c4t500601603CA00C5Dd1): "DGC     RAID 5"
/dev/sg/c0tw500601673b202e44l0: Disk (/dev/rdsk/c2t500601673B202E44d0): "DGC     RAID 5"
/dev/sg/c0tw500601673ca00c5dl0: Disk (/dev/rdsk/c2t500601673CA00C5Dd0): "DGC     RAID 5"
/dev/sg/c0tw500601673ca00c5dl1: Disk (/dev/rdsk/c2t500601673CA00C5Dd1): "DGC     RAID 5"
/dev/sg/c0tw500601683ca00c5dl0: Disk (/dev/rdsk/c2t500601683CA00C5Dd0): "DGC     RAID 5"
/dev/sg/c0tw500601683ca00c5dl1: Disk (/dev/rdsk/c2t500601683CA00C5Dd1): "DGC     RAID 5"
/dev/sg/c0tw5006016d3b242e44l0: Disk (/dev/rdsk/c2t5006016D3B242E44d0): "DGC     RAID 5"
/dev/sg/c0tw5006016e3b202e44l0: Disk (/dev/rdsk/c4t5006016E3B202E44d0): "DGC     RAID 5"
/dev/sg/c0tw5006016e3ca00c5dl0: Disk (/dev/rdsk/c4t5006016E3CA00C5Dd0): "DGC     RAID 5"
/dev/sg/c0tw5006016e3ca00c5dl1: Disk (/dev/rdsk/c4t5006016E3CA00C5Dd1): "DGC     RAID 5"

Guduru · ‎12-05-2014

Hi,

May i know what library is that? try to reinstall sg drivers

# cd /usr/openv/volmgr/bin/driver
# ../sg.build all -mt 15 -ml 20
#
# cat st.conf > /kernel/drv/st.conf
# rm /kernel/drv/sg.conf
# rem_drv sg
#
# ./sg.install

wwpn which is visible to cfgadm is the one you want to discover with sgscan ?

tigerlover · ‎12-05-2014

This is a Oracle SL 3000 library. I want sgscan to see:

c4::500104f000affbb9

I tried the steps you sent. Still can not sgscan the robot. Do you think a reboot is needed?

mph999 · ‎12-05-2014

A reboot sometimes fixes these things so yes, give that a go.

After you tried the steps I posted, you should have a (new) sg.links and sg.coonf file in

/usr/openv/volmgr/bin/driver

In these two files, do you see the WWN of the robot ?

(Feel free to post the files up here )

I gues this is the WWN as you highlighted it above.

500104f000affbb9

tigerlover · ‎12-05-2014

I can see them, but it shows two robots:

root@dvifap12# ls -l sg.conf
-r--------   1 root     root        6935 Dec 3 15:09 sg.conf
root@dvifap12# ls -l sg.lim^Hnks
sg.links: No such file or directory
root@dvifap12# ls -l sg.links
-r--------   1 root     root        7358 Dec 3 15:09 sg.links
root@dvifap12# grep bb9 sg.links
type=ddi_pseudo;name=sg;addr=w500104f000affbb9,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500104f000affbb9,1;       sg/c\N0t\A1l1
root@dvifap12# grep bb9 sg.conf
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500104f000affbb9";
name="sg" parent="fp" target=0 lun=1 fc-port-wwn="500104f000affbb9";

Guduru · ‎12-06-2014

is it after reboot? if not can you try with devfsadm -Cv and then cfgadm -al ....sgscan

mph999 · ‎12-06-2014

No no no ... if WWN are used as in this case you don;t need -mt -ml options. This creates (in this case ) 300 (20x15) device files that have no devices, which slows down anything that scans them, eg scan command, device wizard.

I appreciate this is not clear, as many technotes show this - the reason being every environment is different and when these TNs were written there were catch-all, that is a generic TN that woll work in most cases.

However, most environments now are configure via WWN, so the options are not necessary.

The way to tell is ls -al output - if you see WWN in the filenames, you're using WWN. If you see no WWN you are using targets/ luns.

mph999 · ‎12-06-2014

OK, if the robot is there twice this might or might not be valid.

Some libraries use a control path, that is the robot is access via one of the drives, but a different lun, so you would see the WWN twice, once for the drive and once for the robot which would be correct.

If the robot is accessed via a direct link, you would only need it once - but if it was listed twice it shouldn't cause a problem, you would just have an extra unused file.

As a matter of interest, is this a IBM 3584 library ?

Is there are corresponding file in /dev/sg (look for the WWN) ?

If so, there should be a long path, if you take this path (or might be a single file ) and sticj /dev/sg/ infront of it ...

Run

/usr/openv/volmgr/bin/scsi_command -d /dev/sg/<file or path>

Does this return the scsi inquiry string for the library ?

From the look of the file snippets above, and if that file is there in /dev/sg it looks correct from a NBU view - there is always the possibility there is an issue elsewhere.

Martin

Marianne · ‎12-06-2014

I am going through previous posts that shows more than one robot and lots of tape drives.
Just wondering - why so many devices added to a single server?

To get back to devices seen by cfgadm and sgscan:
cfgadm sees 3 robots:
c2::500104f00060540e           med-changer connected    configured   unknown
c4::500104f00060a3ca           med-changer connected    configured   unknown
c4::500104f000affbb9           med-changer connected    configured   unknown

sgscan shows 2 robots.
/dev/sg/c0tw500104f00060540el0: Changer: "STK L700"
/dev/sg/c0tw500104f00060a3cal0: Changer: "STK L700"

So, you have 2 existing L700 libraries and drives and now need to add another library and drives.

I am wondering once again why you want to present so many devices to one server?

Also curious about multiple tape drives in cfgadm output showing 'failing' or 'failed'.....
It does not look healthy.

As per Martin's post above - we need to see if the new robot is responding to scsi-commands.

Handy NetBackup Links

VOX

How to connect Master server with two shared robots in one library