Sun L280
Hello, I have seen a number of messages in regard to this, so hopefully someone can help me here. I have a sun e220r connected to a sun L280 and I have a couple questions. First of all, is there a way that I can confirm that my server actually sees the tape library and the drive? Also, I am new to this type of config and I was wondering what I need to do to configure the st.conf file and other files to get the library to work. Any help is appreciated. Ed Smith
FW: Sun L280
Hello, A little more information: I am running Solaris 8 I have an A1000 connected to the 220R (works fine) I have installed the suggested patches for Amanda and L280 Thanks... Ed -Original Message- From: Smith, Ed Sent: Wednesday, August 14, 2002 1:41 PM To: amanda-users Subject: Sun L280 Hello, I have seen a number of messages in regard to this, so hopefully someone can help me here. I have a sun e220r connected to a sun L280 and I have a couple questions. First of all, is there a way that I can confirm that my server actually sees the tape library and the drive? Also, I am new to this type of config and I was wondering what I need to do to configure the st.conf file and other files to get the library to work. Any help is appreciated. Ed Smith
Re: Sun L280
On Wed, Aug 14, 2002 at 03:40:47PM -0500, [EMAIL PROTECTED] wrote: Hello, I have seen a number of messages in regard to this, so hopefully someone can help me here. I have a sun e220r connected to a sun L280 and I have a couple questions. First of all, is there a way that I can confirm that my server actually sees the tape library and the drive? Also, I am new to this type of config and I was wondering what I need to do to configure the st.conf file and other files to get the library to work. Any help is appreciated. Not sure what you mean in regard to this. Are you having trouble? What kind? What have you tried? What errors did you encounter? First source of answers is the documentation that comes with the L280. I once watched an installer putting in a Sun DLT drive who did not consult the docs in the box. He just knew what to do. The little lines at the start of the installation manual that said you must edit the st.conf file were deemed unnecessary when pointed out to him. Frustrated he gave up after 4 hours and was leaving for the day. While he was packing up I followed the instructions and had it running before he was ready to leave. Don't have the docs? Shame! Call your Sun rep for replacements and meanwhile go to docs.sun.com. As it is an HP unit (surestore autoloader 718) you can get some info at hp.com support-storage-tape-manuals. HP dat changers and drives (not familiar with dlt) have VERY specific dip switch settings for using them on Solaris. You would think a Sun branded HP drive is already setup properly but ... RE st.conf, as this is a Sun product, your st.conf may already have the needed entries (mine doesn't). If installed correctly there should be devices in /dev/rmt. Presence of the devices does not mean correct installation, but absence means incorrect installation. mt can be used to manipulate the drive (not changer, just drive). dd/tar/ufsdump/cat can be used to read and write to the drive. Does the drive come with a program similar to mtx to control the changer? Maybe (i don't know the answer) the freeware mtx will work for dlt changers. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: FW: Sun L280
On Wed, Aug 14, 2002 at 03:49:30PM -0500, [EMAIL PROTECTED] wrote: Hello, A little more information: I am running Solaris 8 I have an A1000 connected to the 220R (works fine) I have installed the suggested patches for Amanda and L280 [clip] can help me here. I have a sun e220r connected to a sun L280 and I have a couple questions. First of all, is there a way that I can confirm that my server actually sees the tape library and the drive? The low-tech way to make sure the box sees your new SCSI devices is to do a clean halt to boot prompt then: OK reset-all OK probe-scsi-all Confirm the target addresses are what you expected them to be. Bring it back up with: OK boot -r FOR THE TAPE: IIRC, the drive in that box is a DLT-7000, right? For that drive, with Solaris 8, you won't need to touch st.conf. After the 'boot -r' you should have /dev/rmt/0* (if you've never had a tape drive on this box before), and you should be able to 'mt -f /dev/rmt/0n status'. The devices will be: 0l*:20G (DLT4000, compression off) 0m*:40G (DLT4000, compression on) 0h*:35G (DLT7000, compression off) 0*: 70G (DLT7000, compression on) 0c*:70G (DLT7000, compression on) 0u*:70G (DLT7000, compression on) You can download a nice Solaris st.conf PDF from Quantum, but you don't need it. FOR THE CHANGER: --- These days, for Solaris 8, I'm recommending sgen(7D) and mtx. Even if you don't end up using chg-zd-mtx, mtx itself is nice to have, and the mtx source includes a nice little contrib/config_sgen_solaris script. You end up with an sgen.conf something like: device-type-config-list=changer; 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; name=sgen class=scsi target=9 lun=0; name=sgen class=scsi target=10 lun=0; name=sgen class=scsi target=11 lun=0; name=sgen class=scsi target=12 lun=0; name=sgen class=scsi target=13 lun=0; name=sgen class=scsi target=14 lun=0; name=sgen class=scsi target=15 lun=0; (You don't *need* every possible target, of course). This ends up making /dev/scsi/changer/cXtYd0. -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
RE: Sun L280
Hello, I was able to see the changer and the drive, but mt says my drive is either offline or no tape loaded (and is correct, no tape loaded). /dev/rmt/0n: no tape loaded or drive offline However, I was not able to get the sgen.conf to work correctly. I couldn't get the config_sgen_solaris script to work without a CVROOT set. Any ideas what I can do from here?Thanks... Ed FOR THE TAPE: IIRC, the drive in that box is a DLT-7000, right? For that drive, with Solaris 8, you won't need to touch st.conf. After the 'boot -r' you should have /dev/rmt/0* (if you've never had a tape drive on this box before), and you should be able to 'mt -f /dev/rmt/0n status'. The devices will be: 0l*:20G (DLT4000, compression off) 0m*:40G (DLT4000, compression on) 0h*:35G (DLT7000, compression off) 0*: 70G (DLT7000, compression on) 0c*:70G (DLT7000, compression on) 0u*:70G (DLT7000, compression on) You can download a nice Solaris st.conf PDF from Quantum, but you don't need it. FOR THE CHANGER: --- These days, for Solaris 8, I'm recommending sgen(7D) and mtx. Even if you don't end up using chg-zd-mtx, mtx itself is nice to have, and the mtx source includes a nice little contrib/config_sgen_solaris script. You end up with an sgen.conf something like: device-type-config-list=changer; 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; name=sgen class=scsi target=9 lun=0; name=sgen class=scsi target=10 lun=0; name=sgen class=scsi target=11 lun=0; name=sgen class=scsi target=12 lun=0; name=sgen class=scsi target=13 lun=0; name=sgen class=scsi target=14 lun=0; name=sgen class=scsi target=15 lun=0; (You don't *need* every possible target, of course). This ends up making /dev/scsi/changer/cXtYd0. -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
Re: Sun L280
On Wed, Aug 14, 2002 at 05:38:32PM -0500, [EMAIL PROTECTED] wrote: Hello, I was able to see the changer and the drive, but mt says my drive is either offline or no tape loaded (and is correct, no tape loaded). /dev/rmt/0n: no tape loaded or drive offline However, I was not able to get the sgen.conf to work correctly. I couldn't get the config_sgen_solaris script to work without a CVROOT set. Any ideas what I can do from here?Thanks... Dude, just delete the line! It doesn't do anything. -Jay- -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
Re: Setting up Sun L280
Thanks once again for your help John. You provided plenty of food for thought. On Wed, 2 May 2001, John R. Jackson wrote: So far I have tried the following : - built and installed sst form the 2.4.2p2 source. I have a /dev/rsst1 and running sstest '/dev/rsst1 rew' I get 'Device rewound, status = 0x0'. ... You tried to rewind a tape changer? I'm surprised it didn't stick its tongue out at you and drop all the tapes on the floor. :-) I should have been paying a bit more attention ;) You might grab: ftp://gandalf.cc.purdue.edu/pub/amanda/atl_op Got it. That's a little test program I use to exercise my ATL robot through the sst interface. After you chmod +x it, try these things: atl_op -h # to see the help message atl_op -f /dev/rsst1 -v inquiry But there are other problems you need to look at first ... - I have built the latest mtx from sourceforge : # mtx -f /dev/rsst1 inquiry Product Type: Disk Drive Ummm, that would seem to be a very bad thing. You're talking to a disk drive, not your changer. :-) That, in turn, implies /dev/rsst1 is not pointing where you want it to. Were any other /dev/rsst* devices created? What does rsst1 point to? Only /dev/rsst1 was created which as you say points to the drive not the changer. I tried to change the sst.conf file as follows : name=sst parent=/pci@1f,2000/scsi@1/sst@1,0:character target=1 lun=0;A but this caused a kernel panic ! I created the link by hand : ln -s ../devices/pci@1f,2000/scsi@1/sst@1,0:character rsst2 and now I can : # ./atl_op -f /dev/rsst2 inquiry atl_op: device typeCHANGER atl_op: removeable atl_op: vendor HP atl_op: productC6280-7000 atl_op: revision_level 2.10 but still get : # ./mtx -f /dev/rsst2 status mtx: Request Sense: Long Report=yes mtx: Request Sense: Valid Residual=no mtx: Request Sense: Error Code=0 (Unknown?!) mtx: Request Sense: Sense Key=No Sense mtx: Request Sense: FileMark=no mtx: Request Sense: EOM=no mtx: Request Sense: ILI=no mtx: Request Sense: Additional Sense Code = 00 mtx: Request Sense: Additional Sense Qualifier = 00 mtx: Request Sense: BPV=no mtx: Request Sense: Error in CDB=no mtx: Request Sense: SKSV=no READ ELEMENT STATUS Command Failed but doing an inquiry produces the same results as atl_op and inventory causes some changer activity but nothing to stdin. The following gets logged to /var/adm/messages : unix: WARNING: /pci@1f,2000/scsi@1/sst@1,0 (sst2) Error for Command: undecoded cmd 0xb8Error Level: Fatal unix: Requested Block: 0 Error Block: 0 unix: Vendor: HP Serial Number: 99255B9697 unix: Sense Key: Illegal Request unix: ASC: 0x24 (invalid field in cdb), ASCQ: 0x0, FRU: 0x0 What do you get if you do this: find /devices -name 'sst*' # find /devices -name 'sst*' /devices/pci@1f,4000/scsi@3/sst@1,0:character /devices/pci@1f,2000/scsi@1/sst@1,0:character The top one is an internal disk drive (I think) and the bottom one is the changer. What did the system reboot say (e.g. /var/adm/messages) when it scanned the devices, in particular about your changer or the sst devices? unix: sst0:found Direct Access device at tgt1, lun0 unix: sst0:Vendor/Product ID = IBM DDRS34560SUN4.2G unix: sst0 at glm0: unix: target 1 lun 0 unix: sst0 is /pci@1f,4000/scsi@3/sst@1,0 unix: sst1:No response from target 1, lun 0 unix: sst2:found Changer device at tgt1, lun0 unix: sst2:Vendor/Product ID = HP C6280-7000 unix: sst2 at glm2: unix: target 1 lun unix: sst2 is /pci@1f,2000/scsi@1/sst@1,0 unix: sst3:No response from target 1, lun 0 What do I need to do ?? Thanks once again John. Cheers, Adam.
Re: Setting up Sun L280
So, if I understand correctly, /dev/rsst2 is now correctly pointing at the proper device and works when doing a simply inquiry, both from atl_op and mtx. But doing other things with mtx does not work. My guess, then, is that you need to post to the mtx mailing list (see the instructions on the mtx project page at www.sourceforge.net), tell them what version you're using and ask what's going on and how to debug it. FWIW, I've got pretty much the latest mtx and cannot get it to work on my Solaris system, either, although I think the symptoms are different. But it is reportedly supposed to work on Solaris, so the developers probably just need to work with you (and me, for that matter) a bit to find out what's wrong. Adam. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Setting up Sun L280
So far I have tried the following : - built and installed sst form the 2.4.2p2 source. I have a /dev/rsst1 and running sstest '/dev/rsst1 rew' I get 'Device rewound, status = 0x0'. ... You tried to rewind a tape changer? I'm surprised it didn't stick its tongue out at you and drop all the tapes on the floor. :-) You might grab: ftp://gandalf.cc.purdue.edu/pub/amanda/atl_op That's a little test program I use to exercise my ATL robot through the sst interface. After you chmod +x it, try these things: atl_op -h # to see the help message atl_op -f /dev/rsst1 -v inquiry But there are other problems you need to look at first ... - I have built the latest mtx from sourceforge : # mtx -f /dev/rsst1 inquiry Product Type: Disk Drive Ummm, that would seem to be a very bad thing. You're talking to a disk drive, not your changer. :-) That, in turn, implies /dev/rsst1 is not pointing where you want it to. Were any other /dev/rsst* devices created? What does rsst1 point to? What do you get if you do this: find /devices -name 'sst*' What did the system reboot say (e.g. /var/adm/messages) when it scanned the devices, in particular about your changer or the sst devices? Adam. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
