I'm not sure, but this might be licensing problem - for TS3310 to use full slots capacity with the expansion module customer needs to buy "extension" license.
The second thing that comes to my mind - are they sure they installed expansion module correctly - the procedure is quite complicated though well described in installation manual. Anyway, I did the installation of TS3310 with the expansion module about two weeks ago and I had to read the procedure four or five times to do everything correctly. Hope this may help You, Tomasz Hubicki -- Tomasz Hubicki TSS Technical Support tel. +48 42 6756356 Centrum Komputerowe ZETO S.A. http://www.ckzeto.com.pl -------- Wiadomość oryginalna -------- Nadawca: Wanda Prather <[EMAIL PROTECTED]> Adresat: Tomasz Hubicki <[EMAIL PROTECTED]> Temat: TS3310 Expansion Drawer Data: 2006-10-09 16:31 > TSM 5.3.2 on Win2K3 > > Has anyone successfully > 1) Added the Expansion drawer to a TS3310 and > 2) Reconfigured the TS3310 to use all 18 I/O slots with TSM? > > I have a customer that added the expansion drawer a while back, but > continued using the original 6 I/O slots. > > Now they want to use all 18 I/O slots. > > I removed the tapes so I could delete the TS3310 partition and recreate i= > t > from the TS3310 front panel (that's requried to change the I/O slots).=20 > The drawer unlocked as it should. > > Then when I told TSM to do a checkin, I could SEE that the arm moved down > and scanned the additional slots, but the result was a "SCSI BUS RESET" > I/O error (see below). > > If I delete the library from TSM and add it back, I get exactly the same > I/O error during the DEFINE PATH, so I don't think it has to do with arm > movement. > > I'm stumped as to whether this is a libary hardware problem, a library > firmware problem, a Windows driver problem, a TSM device support > problem...any guesses? > > 09/14/2006 16:31:02 ANR8300E I/O error on library UAWIN17_TS3310 > (OP=3D8401C08C, CC=3D210, KEY=3DFF, ASC=3DFF, ASCQ=3DFF, SENSE=3D**NONE**= > , =20 > Description=3DThe device was reset due to device power-up, SCSI bus reset= > , > or manual tape load/eject). Refer to Appendix D in the 'Messages' manual > for recommended ction. (SESSION: 10) > > Thanks! > >
