Oops - I could have sworn I said these are RedHat Linux server.
On Tue, May 14, 2013 at 11:51 AM, James Choate <jcho...@chooses1.com> wrote: > For Windows there is an IBMtape driver that needs to be loaded. > Check this URL: > http://www-01.ibm.com/support/docview.wss?uid=swg21428656 > > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Ehresman,David E. > Sent: Tuesday, May 14, 2013 9:45 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Re: TS3500/3584 managed by Linux host > > Don't know about Windows, but since it is an IBM device, on AIX you use > Atape and on Linux you use lintape instead of the TSM drivers. So for > unix, the answer is no. > > David > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Zoltan Forray > Sent: Tuesday, May 14, 2013 11:29 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Re: TS3500/3584 managed by Linux host > > With the TS3500 scheduled to appear next Monday, I am triple-checking my > list of things to do in preparation of the install, Memorial Day weekend. > > I have a question related to the server software. In the past, when > installing a TSM server, I always excluded/ignored the option of installing > the TIVsm-tsmscsi modules since I didn't have any SCSI devices. > > But with the TS3500 being seen as a "SCSI device", do I need to install > this missing module/feature on all of my TSM servers? > > > On Mon, Apr 15, 2013 at 12:44 PM, David Bronder <david-bron...@uiowa.edu > >wrote: > > > TSM controls the library via a second LUN on one or more of the tape > > drives. By default (or by the IBM CE at installation time), the first > > drive in the library has the control path enabled, but you can enable > > it on additional drives (I believe lin_tape should handle failover for > > them). On AIX, they would be discovered as smc* devices; a quick bit > > of Googling suggests with lin_tape, they're /dev/IBMchanger* devices. > > You define the library using the control path device. > > > > On the network side, though, you'll likely want TCP port 80 and/or 443 > > open to the 3584 from somewhere to use the library's web interface, > > but that's unlikely to be needed from your TSM server unless you use > > the Java CLI from there to monitor or perform tasks on the library. > > > > If you're using a TS3000 System Console to manage your library, that's > > a whole other beast, which I've avoided so far. Maybe someone else > > can offer insight there, if you need to know. > > > > I'll defer to someone actually using AME or TKLM for drive encryption > > to speak to the networking requirements there. I'd guess that for > > AME, all communication is via the tape device, though. > > > > =Dave > > > > > > Zoltan Forray wrote: > > > > > > Thanks for the reply but I need more details than that. Does it > > > need > > it's > > > own fibre connection or does it piggy-back on one of the drives, in > > > this case TS1130? What does it look like on a server? Does it have > > > a separate drivers? For instance, my drives appear as > > > /dev/IBMtapenn due to installation of lin_tape? How do I define the > TSM path to the library? > > > > > > On Mon, Apr 15, 2013 at 11:51 AM, Thomas Denier < > > > thomas.den...@jeffersonhospital.org> wrote: > > > > > > > -----Zoltan Forray wrote: ----- > > > > > > > > >I am trying to prepare for the move from our 3494 to a TS3500/3584. > > > > > > > > > >With the 3494, it needed port 3494 open on the host system that > > > > >was the library manager, for the ibmatl program to function. > > > > > > > > > >What ports are needed open through the firewall of the Linux > > > > >servers that are library managers (is it as simple as 3584?)? > > > > >How about for AME? > > > > >Any > > > > >additional ports needed for this function from the TS3500 to each > > > > >library manager server (I assume the keys are only stored with > > > > >the server that manages the tapes, not each server that uses a > > > > >tape - or is this a bad/wrong assumption?) > > > > > > > > A TS3500 is eithter a relabeled 3584 or a compatible successor to > > > > the 3584; different Web sites give conflicting information on this > > > > point. > > > > > > > > All communications between the TSM server code and a TS3500 travel > > > > over the SAN connections between the two. > > > > > > > > Thomas Denier > > > > Thomas Jefferson University Hospital > > > > > > > > > -- > > Hello World. David Bronder - Systems > > Architect > > Segmentation Fault ITS-EI, Univ. of > > Iowa > > Core dumped, disk trashed, quota filled, soda warm. > > david-bron...@uiowa.edu > > > > > > -- > *Zoltan Forray* > TSM Software & Hardware Administrator > Virginia Commonwealth University > UCC/Office of Technology Services > zfor...@vcu.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 > -- *Zoltan Forray* TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.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
