10-16-2012 01:08 PM
Solved! Go to Solution.
10-17-2012 02:08 PM
Opps, given the opening question I kinda assumed this was meant to work via ACS ...
We all know what assumtion is ... - note to self, stop doing that ...
OK, sg build - if you are using san connected drives, the targets / luns are probably not required, as the drives will be configured via WWN no target /lun.
So Mariannes excellent is 100% correct, but if the below is true, we do not need to concern outselves with creating sg 'device' files that will not have devices - it will slow things down.
cfgadm -al or cfgadm -al -o show_FCP_dev should show if the tapes are using wwn or target lun. If san connected it should be wwn, so it's easy to just configure things that way, if it doesn't work, then try the other - with the copy/paste commands (below) it's no big deal if you have to re-run.
I might as well give the full details as I've started. Apart from cfgadm, ls -al on /dev/rmt/ gives the required details (I see Marianne has explained this also).
This is my server, it uses target/lun as the drive is scsi connected. ls -al on a device file shows
0cbn -> ../../devices/pci@1e,600000/pci@0/pci@9/pci@0,2/pci@1/scsi@2/st@5,0:cbn
The bit at the end ...
@5,0:cbn shows target 5, lun 0
So to get the max number of target/ lun, ls -al /dev/rmt/ and look for the highest target number and the highest lun number. These would be the values you put into the sg.build command.
This is my colleagues server, the drives are san connected ...
3cbn -> ../../devices/pci@1e,600000/SUNW,qlc@3/fp@0,0/st@w2103000d77640cc8,1:cbn
Straight away, we see there is no target/l lun as a WWN is shown.
Simple - if all the drives are WWN (which they are) we only need to use sg.build all (no mt -ml options required)
I would try this way first. Run the commands exactly as shown, in the order shown.
(If the mv commands fail, don't worry)
10-16-2012 02:51 PM
You need to read the device config guide.
http://www.symantec.com/docs/DOC5186
And the system admin guides might be useful also.
http://www.symantec.com/docs/DOC5157
http://www.symantec.com/docs/DOC5158
This is also useful
http://www.symantec.com/docs/TECH31526
Esp part 6.1.3 - the rpc info commands MUST respond with "ready and waiting"
If you have multiple interfaces on the media servers this post from Marianne might be useful
https://www-secure.symantec.com/connect/forums/drives-are-showing-avr-control-media-server
Martin
10-16-2012 07:37 PM
SL48 is not supported by ACSLS. Just configure your SAN so that the server can access SL48, and follow instructions in Device Configuration Guide.
in brief, run sg.build and sg.install like below, and after that, run device configuration wizard(Configure Storage Devices) in GUI.
# cd /usr/openv/volmgr/bin/driver
# ../sg.build all -mt 6 -ml 1
# rm /kernel/drv/sg.conf
# ./sg.install
# /usr/openv/volmgr/bin/scan
If your robot and drives all are visible in scan command, you can configure devices by wizard.
10-17-2012 07:47 AM
10-17-2012 08:36 AM
10-17-2012 02:08 PM
Opps, given the opening question I kinda assumed this was meant to work via ACS ...
We all know what assumtion is ... - note to self, stop doing that ...
OK, sg build - if you are using san connected drives, the targets / luns are probably not required, as the drives will be configured via WWN no target /lun.
So Mariannes excellent is 100% correct, but if the below is true, we do not need to concern outselves with creating sg 'device' files that will not have devices - it will slow things down.
cfgadm -al or cfgadm -al -o show_FCP_dev should show if the tapes are using wwn or target lun. If san connected it should be wwn, so it's easy to just configure things that way, if it doesn't work, then try the other - with the copy/paste commands (below) it's no big deal if you have to re-run.
I might as well give the full details as I've started. Apart from cfgadm, ls -al on /dev/rmt/ gives the required details (I see Marianne has explained this also).
This is my server, it uses target/lun as the drive is scsi connected. ls -al on a device file shows
0cbn -> ../../devices/pci@1e,600000/pci@0/pci@9/pci@0,2/pci@1/scsi@2/st@5,0:cbn
The bit at the end ...
@5,0:cbn shows target 5, lun 0
So to get the max number of target/ lun, ls -al /dev/rmt/ and look for the highest target number and the highest lun number. These would be the values you put into the sg.build command.
This is my colleagues server, the drives are san connected ...
3cbn -> ../../devices/pci@1e,600000/SUNW,qlc@3/fp@0,0/st@w2103000d77640cc8,1:cbn
Straight away, we see there is no target/l lun as a WWN is shown.
Simple - if all the drives are WWN (which they are) we only need to use sg.build all (no mt -ml options required)
I would try this way first. Run the commands exactly as shown, in the order shown.
(If the mv commands fail, don't worry)
10-18-2012 06:36 AM
10-18-2012 06:55 AM
'scan' command does not report WWN.
The device Inquiry string is returned by the scan command. WWN is not part of Inquiry string.
If library is fiber-connected, cfgadm commands will show WWN.
Did you manage to configure devices successfully in NBU?
I have never tried to use "Robot Diagnostic" in the GUI.
I prefer using 'robtest' from cmd to test robot functionality after devices have been added to NBU.
See http://www.symantec.com/docs/TECH83129 for robtest usage.
10-18-2012 07:22 AM
10-18-2012 07:27 AM
10-18-2012 07:32 AM
Now that NBU successfully detected and added the devices, can we agree that your query has been answered?
If so, please select the post that has helped you most and Mark as Solution.
10-18-2012 08:07 AM
Thank to all for help me.
Bye.