Success: mhvtl on Solaris via iSCSI - with a little trouble

by **nia** » Tue Feb 02, 2010 3:41 am

See my post regarding iSCSI Target here:
http://mhvtl.nimsa.us/viewtopic.php?f=23&t=32#p104

I am attempting to connect a Solaris 10 system to a Linux mhvtl iSCSI target, but can not attach to the medium Changer. Unlike Tape drives which do come online:

Here are the steps that I take to configure the Solaris Initiator:

CODE: SELECT ALL: Enable the iSCSI initiator service #svcadm enable iscsi_initiator Enable the discovery method as ‘SendTargets’ # iscsiadm modify discovery --sendtargets enable Add the target using the IP:PORT (port = 3260) # iscsiadm add discovery-address 192.168.0.19:3260 The connection should now be established. To verify run: # iscsiadm list target –S

CODE: SELECT ALL: # iscsiadm list target -S Target: iqn.2010-23.us.nimsa:changer Alias: - TPGT: 1 ISID: 4000002a0000 Connections: 1 Target: iqn.2010-23.us.nimsa:tape.1 Alias: - TPGT: 1 ISID: 4000002a0000 Connections: 1 LUN: 0 Vendor: QUANTUM Product: SDLT600 OS Device Name: /dev/rmt/0 Target: iqn.2010-23.us.nimsa:tape.2 Alias: - TPGT: 1 ISID: 4000002a0000 Connections: 1 LUN: 0 Vendor: QUANTUM Product: SDLT600 OS Device Name: /dev/rmt/1 Target: iqn.2010-23.us.nimsa:tape.3 Alias: - TPGT: 1 ISID: 4000002a0000 Connections: 1 LUN: 0 Vendor: QUANTUM Product: SDLT600 OS Device Name: /dev/rmt/2 Target: iqn.2010-23.us.nimsa:tape.4 Alias: - TPGT: 1 ISID: 4000002a0000 Connections: 1 LUN: 0 Vendor: QUANTUM Product: SDLT600 OS Device Name: /dev/rmt/3 Target: iqn.2010-23.us.nimsa:tape.5 Alias: - TPGT: 1 ISID: 4000002a0000 Connections: 1 LUN: 0 Vendor: IBM Product: ULT3580-TD4 OS Device Name: /dev/rmt/4 Target: iqn.2010-23.us.nimsa:tape.6 Alias: - TPGT: 1 ISID: 4000002a0000 Connections: 1 LUN: 0 Vendor: IBM Product: ULT3580-TD4 OS Device Name: /dev/rmt/5 Target: iqn.2010-23.us.nimsa:tape.7 Alias: - TPGT: 1 ISID: 4000002a0000 Connections: 1 LUN: 0 Vendor: IBM Product: ULT3580-TD4 OS Device Name: /dev/rmt/6 Target: iqn.2010-23.us.nimsa:tape.8 Alias: - TPGT: 1 ISID: 4000002a0000 Connections: 1 LUN: 0 Vendor: IBM Product: ULT3580-TD4 OS Device Name: /dev/rmt/7

dmesg:

CODE: SELECT ALL: Feb 2 01:23:47 solaris10 genunix: [ID 936769 kern.info] st0 is /iscsi/[hidden email]%3Atape.10001,0 Feb 2 01:23:47 solaris10 scsi: [ID 365881 kern.info] /iscsi/[hidden email]%3Atape.10001,0 (st0): Feb 2 01:23:47 solaris10 <Quantum Super DLT 600> Feb 2 01:23:47 solaris10 scsi: [ID 799468 kern.info] st1 at iscsi0: name 0000iqn.2010-23.us.nimsa%3Atape.20001,0, bus address 0000iqn.2010-23.us.nimsa%3Atape.20001,0 Feb 2 01:23:47 solaris10 genunix: [ID 936769 kern.info] st1 is /iscsi/[hidden email]%3Atape.20001,0 Feb 2 01:23:47 solaris10 scsi: [ID 365881 kern.info] /iscsi/[hidden email]%3Atape.20001,0 (st1): Feb 2 01:23:47 solaris10 <Quantum Super DLT 600> Feb 2 01:23:47 solaris10 scsi: [ID 799468 kern.info] st2 at iscsi0: name 0000iqn.2010-23.us.nimsa%3Atape.30001,0, bus address 0000iqn.2010-23.us.nimsa%3Atape.30001,0 Feb 2 01:23:47 solaris10 genunix: [ID 936769 kern.info] st2 is /iscsi/[hidden email]%3Atape.30001,0 Feb 2 01:23:47 solaris10 scsi: [ID 365881 kern.info] /iscsi/[hidden email]%3Atape.30001,0 (st2): Feb 2 01:23:47 solaris10 <Quantum Super DLT 600> Feb 2 01:23:47 solaris10 scsi: [ID 799468 kern.info] st3 at iscsi0: name 0000iqn.2010-23.us.nimsa%3Atape.40001,0, bus address 0000iqn.2010-23.us.nimsa%3Atape.40001,0 Feb 2 01:23:47 solaris10 genunix: [ID 936769 kern.info] st3 is /iscsi/[hidden email]%3Atape.40001,0 Feb 2 01:23:47 solaris10 scsi: [ID 365881 kern.info] /iscsi/[hidden email]%3Atape.40001,0 (st3): Feb 2 01:23:47 solaris10 <Quantum Super DLT 600> Feb 2 01:23:47 solaris10 scsi: [ID 799468 kern.info] st4 at iscsi0: name 0000iqn.2010-23.us.nimsa%3Atape.50001,0, bus address 0000iqn.2010-23.us.nimsa%3Atape.50001,0 Feb 2 01:23:47 solaris10 genunix: [ID 936769 kern.info] st4 is /iscsi/[hidden email]%3Atape.50001,0 Feb 2 01:23:47 solaris10 scsi: [ID 365881 kern.info] /iscsi/[hidden email]%3Atape.50001,0 (st4): Feb 2 01:23:47 solaris10 <IBM Ultrium Gen 4 LTO> Feb 2 01:23:47 solaris10 scsi: [ID 799468 kern.info] st5 at iscsi0: name 0000iqn.2010-23.us.nimsa%3Atape.60001,0, bus address 0000iqn.2010-23.us.nimsa%3Atape.60001,0 Feb 2 01:23:47 solaris10 genunix: [ID 936769 kern.info] st5 is /iscsi/[hidden email]%3Atape.60001,0 Feb 2 01:23:47 solaris10 scsi: [ID 365881 kern.info] /iscsi/[hidden email]%3Atape.60001,0 (st5): Feb 2 01:23:47 solaris10 <IBM Ultrium Gen 4 LTO> Feb 2 01:23:47 solaris10 scsi: [ID 799468 kern.info] st6 at iscsi0: name 0000iqn.2010-23.us.nimsa%3Atape.70001,0, bus address 0000iqn.2010-23.us.nimsa%3Atape.70001,0 Feb 2 01:23:47 solaris10 genunix: [ID 936769 kern.info] st6 is /iscsi/[hidden email]%3Atape.70001,0 Feb 2 01:23:47 solaris10 scsi: [ID 365881 kern.info] /iscsi/[hidden email]%3Atape.70001,0 (st6): Feb 2 01:23:47 solaris10 <IBM Ultrium Gen 4 LTO> Feb 2 01:23:47 solaris10 scsi: [ID 799468 kern.info] st7 at iscsi0: name 0000iqn.2010-23.us.nimsa%3Atape.80001,0, bus address 0000iqn.2010-23.us.nimsa%3Atape.80001,0 Feb 2 01:23:47 solaris10 genunix: [ID 936769 kern.info] st7 is /iscsi/[hidden email]%3Atape.80001,0 Feb 2 01:23:47 solaris10 scsi: [ID 365881 kern.info] /iscsi/[hidden email]%3Atape.80001,0 (st7): Feb 2 01:23:47 solaris10 <IBM Ultrium Gen 4 LTO> Feb 2 01:23:47 solaris10 genunix: [ID 242387 kern.warning] WARNING: Page83 data not standards compliant SPECTRA PYTHON 5500 Feb 2 01:23:47 solaris10 iscsi: [ID 248668 kern.warning] WARNING: iscsi driver unable to online iqn.2010-23.us.nimsa:changer lun 0

As you can see, the tape drives come online but not the medium changer:

CODE: SELECT ALL: WARNING: Page83 data not standards compliant SPECTRA PYTHON 5500 WARNING: iscsi driver unable to online iqn.2010-23.us.nimsa:changer lun 0

I was able to test the tape drives using mt and tar. They were fine, but the medium changer is not there.

After much investingating I found that Solaris is unable to find a driver to load for the medium changer ..

And after I ran across this this useful doc from Sun, the problem was fixed.

http://uk.sun.com/products/complementary/storage/vtl/pdf/Solaris_quickstart_01.pdf

I copy/paste the doc here as well:

CODE: SELECT ALL: · Configuring Solaris to recognise the changer. On the previous page we connected the VTL, however Solaris only fully recognised the two tape drives and did not completely identify the changer. To complete the configuration perform the following steps: · Configure the driver aliases Using your preferred text editor, open the file /etc/driver_aliases find the section: " sgen "scsa,08.bfcp" sgen "scsa,08.bvhci" " replace it with: " sgen "scsiclass,08" " Save changes and go to “Update Driver” section below If there is no sgen section in /etc/driver_aliases close the editor and run the command: # add_drv -m '* 0660 root sys' -v sgen The /etc/driver_alises file will be created with the correct sgen entries · Update Driver Run: #update_drv sgen Restart the host system: #reboot Once Solaris has restarted run command: #devfsadm -i iscsi

Success: Now I can see the medium changer device.

CODE: SELECT ALL: # ls -ls /dev/scsi/changer/ total 2 2 lrwxrwxrwx 1 root root 86 Feb 2 02:05 c2t0d0 -> ../../../devices/iscsi/[hidden email]%3Achanger0001,0:changer

CODE: SELECT ALL: /opt/csw/sbin/mtx -f /dev/scsi/changer/c2t0d0 status Storage Changer /dev/scsi/changer/c2t0d0:8 Drives, 204 Slots ( 4 Import/Export ) Data Transfer Element 0:Full (Storage Element 10 Loaded):VolumeTag = SDLT10S3 Data Transfer Element 1:Empty Data Transfer Element 2:Empty Data Transfer Element 3:Empty Data Transfer Element 4:Empty Data Transfer Element 5:Empty Data Transfer Element 6:Empty Data Transfer Element 7:Empty Storage Element 1:Full :VolumeTag=SDLT01S3 Storage Element 2:Full :VolumeTag=SDLT02S3 Storage Element 3:Full :VolumeTag=SDLT03S3 Storage Element 4:Full :VolumeTag=SDLT04S3 Storage Element 5:Full :VolumeTag=SDLT05S3 Storage Element 6:Full :VolumeTag=SDLT06S3 Storage Element 7:Full :VolumeTag=SDLT07S3 Storage Element 8:Full :VolumeTag=SDLT08S3 Storage Element 9:Full :VolumeTag=SDLT09S3 Storage Element 10:Empty Storage Element 11:Full :VolumeTag=SDLT11S3 Storage Element 12:Full :VolumeTag=SDLT12S3 . . . .

Also, another resource suggested that additional entries should be added to /kernel/drv/sgen.conf file

CODE: SELECT ALL: The file /kernel/drv/sgen.conf, which is basically all commented out needs to have the following lines: device-type-config-list="changer","sequential"; inquiry-config-list= "*", "*"; name="sgen" class="scsi" target=0 lun=0; name="sgen" class="scsi" target=1 lun=0; name="sgen" class="scsi" target=2 lun=0; name="sgen" class="scsi" target=3 lun=0; name="sgen" class="scsi" target=4 lun=0; name="sgen" class="scsi" target=5 lun=0; name="sgen" class="scsi" target=6 lun=0; name="sgen" class="scsi" target=7 lun=0; name="sgen" class="scsi" target=8 lun=0;

by **ghazih80** » Wed Feb 03, 2010 2:13 am

Nice write up ..

Thanks

by **nia** » Wed Feb 03, 2010 2:34 am

Thanks, great software.

by **tsunami_liao** » Fri Mar 26, 2010 11:51 pm

greate! I successful bring the changer online by following your instraction, but how can I let the netbackup recognize them?
seems the solaris will use sgen driver for the iscsi device, but netbackup is not support sgen driver.

by **nia** » Sat Mar 27, 2010 4:27 am

but how can I let the netbackup recognize them?

Don't you have tape devices under /dev/rmt/ and library under /dev/scsi/changer/ ? have you tried to use them in netbackup ? Netbackup uses tape devices as /dev/rmt/*cbn

by **root** » Sun Mar 28, 2010 3:23 pm

Try - /usr/openv/volmgr/bin/sgscan

by **prejdarov** » Fri Apr 16, 2010 6:39 pm

Hmm, NetBackup doesn't seem to like /dev/scsi/changer/cXtXdX as a robot file. Complains that cannot communicate with the robot.

by **markh794** » Wed May 05, 2010 2:29 am

NetBackup uses two interfaces to tape drives.
The normal 'st' for data.
The 'sg' path for out-of-band-management (TapeAlert etc).

Starting with NetBackup 6.0, BOTH st & sg drivers have to be correctly configured for successful operation.

Unfortunately, the 'sg' driver supplied with NetBackup does NOT support (read does NOT work) iSCSI attached devices.

If you would like to see this added, please follow the following instructions:
How to submit an Enhancement Request for NetBackup - http://seer.entsupport.symantec.com/docs/318008.htm

(Mind you, who in their right mind would attach iSCSI tape drives/libraries in a production enterprise environment. iSCSI is great for testing & virtual hosts. Most enterprise environments use fibre-channel.)

Cheers
Mark

Success: mhvtl on Solaris via iSCSI - with a little trouble

Success: mhvtl on Solaris via iSCSI - with a little trouble

Success: mhvtl on Solaris via iSCSI - with a little trouble

Re: Success: mhvtl on Solaris via iSCSI - with a little trouble

Re: Success: mhvtl on Solaris via iSCSI - with a little trouble

Re: Success: mhvtl on Solaris via iSCSI - with a little trou

Re: Success: mhvtl on Solaris via iSCSI - with a little trou

Re: Success: mhvtl on Solaris via iSCSI - with a little trou

Re: Success: mhvtl on Solaris via iSCSI - with a little trou

Re: Success: mhvtl on Solaris via iSCSI - with a little trou