One more question about this. The book isn't very clear about whether a
separate fibre cable is needed between the library and our SAN switch for
communications. From the book:
*The host server attaches to the library by using fiber cables that connect
directly to a drive canister or through the library’s patch panel.*
Does that mean a separate fibre cable goes to the second connector of the
3592 designated as the "control path" drive(s)?
On Thu, Apr 25, 2013 at 1:22 PM, Richard Rhodes <rrhodes AT firstenergycorp DOT
com
> wrote:
> We only have one virt lib defined. You can see the virt CAP slots in a
> "show slots" cmd . . . .
>
> ImpExp 0, element number 769
> ImpExp 1, element number 770
> ImpExp 2, element number 771
> ImpExp 3, element number 772
> ImpExp 4, element number 773
> ImpExp 5, element number 774
> ImpExp 6, element number 775
> ImpExp 7, element number 776
> ImpExp 8, element number 777
> ImpExp 9, element number 778
> ImpExp 10, element number 779
> ImpExp 11, element number 780
> ImpExp 12, element number 781
> ImpExp 13, element number 782
> ImpExp 14, element number 783
> ImpExp 15, element number 784
>
> I've at times wondered if you have more than one virt lib if the element
> numbers would be the same for them, or, unique.
>
> Rick
>
>
>
>
>
> From: "Prather, Wanda" <Wanda.Prather AT ICFI DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 04/25/2013 01:04 PM
> Subject: Re: Equating current 3494 configuration to TS3500
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
>
> I have seen similar weirdness and I never could figure it out exactly,
> either.
>
> From watching the web interface, as far as I can tell when you put tapes
> in the door, the arm moves them into a slot, and those slots are assigned
> a SCSI slot address that corresponds to an I/O door.
>
> When they are checked in by TSM, I don't think the cartridges actually
> move, they just get assigned new slot numbers that correspond to a storage
> slot.
>
> So I'm not sure when you need physical slots free and when you don't.
> (I just learned not to put more tapes in the I/O door than there are
> virtual slots defined, or the checkin won't find them.)
>
> Anybody else have rapport with virtual I/O slots?
> W
>
>
>
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Richard Rhodes
> Sent: Thursday, April 25, 2013 10:28 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500
>
> The virtual I/O slots can be very confusing.
>
> One time we filled our library up due to needing as many tape as possible.
> Every slot was full with either a real tape or cleaning cartridge. Later
> we tried to eject a tape that was bad. The checkout cmd failed. Long
> store short - there were no open slots in the library, and this made it so
> the checkout couldn't move the tape to to the virtual export slot, which
> would have put the tape in the CAP. I really don't understand this - you
> would think it could checkout a tape into the CAP door without needing
> open slots. After we removed a cleaning cartridges (freeing up one
> slot), the checkout worked correctly. From what we understand, you need
> as many open slots in the library as you have virtual I/O slots (CAP door
> slots), or at least for as many tapes you would want to checkout
> concurrently.
>
> At least that's what we think happened, which could very well be wrong! As
> I said, I've found this confusing. The manuals for the 3584 don't really
> explain this interaction.
>
>
> Rick
>
>
>
>
>
>
>
> From: "Prather, Wanda" <Wanda.Prather AT ICFI DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 04/25/2013 09:47 AM
> Subject: Re: Equating current 3494 configuration to TS3500
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
>
> The "virtual I/O slots" only get involved when you put cartridges in
> through the 16/32 slot physical I/O door.
> For the initial library load, just open the BIG doors and put the tapes
> directly into the slots yourself.
>
> Then for a SCSI library, the syntax for CHECKIN is slightly different than
> for your 3494.
>
> checkin libv bubba search=yes status=scratch checklabel=barcode waitt=0
> volrange=TS1000,TS1999
> checkin libv bubba search=bulk status=scratch checklabel=barcode waitt=0
>
> Search =YES tells TSM to checkin from the INSIDE library slots.
> Search=bulk tells TSM to checkin what's in the I/O door (with ALMS, it's a
> virtual I/O door, but TSM doesn't' know that.)
>
>
> FWIW:
> For the 3494, TSM just tells the 3494 what it wants done, and doesn't know
> or care where in the library tapes are located.
> All the inventory management is done outboard by the 3494.
> If TSM tells the 3494 to mount a cartridge, he doesn't need to know where
> the cartridge is, that's handled by the 3494
>
> For a SCSI library, including the TS3500 doing business as a 3584, TSM has
> to figure out what tapes are in what slots at checkin time, and saves the
> slot numbers in devconfig so he can send the appropriate commands for
> cartridge movement. (e.g., take cartridge from slot 1024, load in drive
> position 6). That's why the checkin commands are different.
>
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Zoltan Forray
> Sent: Thursday, April 25, 2013 4:37 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500
>
> Again thank you for this additional useful piece of information. But now
> this brings up another issue/question.
>
> If I am limited to no more than 255 unassigned tapes, how do I do a
> mass/bulk checkin of my 1200 plus tapes we are transferring from the 3494?
>
> -------------
> Zoltan Forray
> TSM Software & Hardware Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> zforray AT vcu DOT edu - 804-828-4807
> Don't be a phishing victim - VCU and other reputable organizations will
> never use email to request that you reply with your password, social
> security number or confidential personal information. For more details
> visit http://infosecurity.vcu.edu/phishing.html
> On Apr 24, 2013 10:34 PM, "Prather, Wanda" <Wanda.Prather AT icfi DOT com>
> wrote:
>
> > Thank you both for the kind words; I think it's just a matter of
> > surviving long enough to have all the battle scars - BTDTGTTS.
> >
> > In the interest of completeness, here's one other thing that is
> > different from the 3494:
> > When you create your logical libraries, modify the "maximum VIO
> > cartridges" setting.
> > I believe the default is still 16.
> >
> > AFAIK, with a 3494 you can just keep stuffing cartridges in the I/O
> > door, and it will keep filing them away with an INSERT category code.
> >
> > In the TS3500 w/ALMS, you put cartridges in the physical I/O door, and
> > the library puts them into the "virtual" I/O door of the appropriate
> > library partition. But if you put more through the physical door than
> > the library has virtual I/O slots (before you do a checkin and clear
> > the virtual I/O slots), weirdness will ensue. Your checkin will not
> > "see" the extra cartridges.
> >
> > I don't' know of any reason not to set the "maximum VIO cartridges" to
> > the max setting, which I think is 255. Somebody else might have a
> > better idea if there is a downside to that.
> >
> > W
> >
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> > Of Zoltan Forray
> > Sent: Wednesday, April 24, 2013 2:39 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: [ADSM-L] Equating current 3494 configuration to TS3500
> >
> > Thanks for all the responses - it has been immensely educational and I
> > have much less trepidation about the upcoming
> > unload-pull-out-3494-push-in-reload-3584 weekend. I am going to miss
> > my
> > 3494 - been using it since 1995!
> >
> > I agree that Wanda has some of the best documentation/experiences with
> > TSM, et-al - she should be writing for IBM/Redbooks!
> >
> >
> > On Wed, Apr 24, 2013 at 8:35 AM, Arbogast, Warren K
> > <warbogas AT indiana DOT edu
> > >wrote:
> >
> > > Zoltan,
> > > The Web Specialist can be used with an https interface, and a
> > > physical console to the 3584 is available. I have little experience
> > > with the physical console, but you could determine whether it has
> > > the features and suits your needs better than the Web Specialist.
> > >
> > > Wanda just wrote the Red Book on setting up a 3584. It's more
> > > complete, easier to comprehend and better organized than anything
> > > you will find in the official documentation.
> > >
> > > With best wishes to all,
> > > Keith Arbogast
> > > Indiana University
> > >
> >
> >
> >
> > --
> > *Zoltan Forray*
> > TSM Software & Hardware Administrator
> > Virginia Commonwealth University
> > UCC/Office of Technology Services
> > zforray AT vcu DOT edu - 804-828-4807
> > Don't be a phishing victim - VCU and other reputable organizations
> > will never use email to request that you reply with your password,
> > social security number or confidential personal information. For more
> > details visit http://infosecurity.vcu.edu/phishing.html
> >
>
>
>
>
> -----------------------------------------
> The information contained in this message is intended only for the
> personal and confidential use of the recipient(s) named above. If the
> reader of this message is not the intended recipient or an agent
> responsible for delivering it to the intended recipient, you are hereby
> notified that you have received this document in error and that any
> review, dissemination, distribution, or copying of this message is
> strictly prohibited. If you have received this communication in error,
> please notify us immediately, and delete the original message.
>
--
*Zoltan Forray*
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html
|
