ADSM-L

Re: [ADSM-L] Tape library possible replacement - push/pull

2013-02-04 16:08:07
Subject: Re: [ADSM-L] Tape library possible replacement - push/pull
From: Steve Roder <spr AT BUFFALO DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 4 Feb 2013 15:59:43 -0500
On 02/04/2013 02:32 PM, Zoltan Forray wrote:
Thanks for the "explanations" but I still don't understand.  Does the fibre
channel connection replace the 3494 IP link?  I think read that you still
need IP for CLI?

Yes, the TSM server will be configured to talk to the Library Manager of the 3584 via scsi LUN1 of your tape drives, where scsi LUN0 is the drive. The 3584 is a typical SCSI tape library. The IP access to the 3584 is for Administrative access to the LM, and will be on port 80 of the IP address assigned to the LM. This is used for configuring the library, installing code updates, etc. Via this access, you can enable/disable the control port on the drives in the logical library. At least one is required, and the rest are optional, and can be used for "control point failover". If you enable the control point on a drive, you then need to go to your TSM server, and discover this device in the OS (cfgmgr in AIX). Atape on AIX will configure an additional smc instance (rmtX are the drives). You will not use ibmatl for the 3584. Within TSM, you will drive your library to use the smc device. Something like this:

define library 3584 libtype=scsi shared=no
define path tsmt 3584 srctype=server desttype=library device=/dev/smc4
define drive 3584 d1 online=yes element=257 cleanfreq=none
define drive 3584 d2 online=yes element=258 cleanfreq=none
define drive 3584 d3 online=yes element=259 cleanfreq=none
define drive 3584 d4 online=yes element=260 cleanfreq=none

define path tsmt d1 srctype=server desttype=drive library=3584 -
       device=/dev/rmt4 online=yes
define path tsmt d2 srctype=server desttype=drive library=3584 -
       device=/dev/rmt5 online=yes
define path tsmt d3 srctype=server desttype=drive library=3584 -
       device=/dev/rmt6 online=yes
define path tsmt d4 srctype=server desttype=drive library=3584 -
       device=/dev/rmt7 online=yes

You can determine the element numbers of each drive via the Admin login to the 3584.

I think in Linux you will install IBMtape for both the smc and rmt device drivers.

Hope this makes sense, and helps.

Steve Roder
University at Buffalo




Are the drives still separate when it comes to paths (other than being
defined as part of a library)?  Is the fibre connection to the library the
way the library communicates with the drives (like the old RS422 in the
3494)?  or how the TSM library manager server communicates with the
library/TS3500?

With the 3494, you used a driver called ibmatl which used /etc/ibmatl.conf
(this is RedHat Linux) to define the IP/host connection to the library.
  How do you configure a TS3500?

On Mon, Feb 4, 2013 at 2:06 PM, Remco Post <r.post AT plcs DOT nl> wrote:

On 4 feb. 2013, at 19:43, Zoltan Forray <zforray AT VCU DOT EDU> wrote:

As this project moves forward, I am doing more and more research since I
am
unfamiliar with this beast (3494 has been my baby since it was installed
in
1995).

The book talks about "*to communicate with a server, the IBM System
Storage
TS3500 Tape Library uses a Fibre Channel interface (also called a
port).*"
Why?  What is this "fibre channel interface" used for?   The 3494 use IP
to
communicate/manage the library and the drives inside the library used
fibre
plus an RS422 connection to the library manager.
Because that is the way a 3584 works…. 'in band'. leftovers from when the
3584 was still midrange and midrange libraries are controlled in band. BTW,
with modern ts3500's features like control path failover are inclusive and
losing one tape drive does not mean that the library is uncontrollable.


--
*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
--

Met vriendelijke groeten/Kind regards,

Remco Post
r.post AT plcs DOT nl
+31 6 24821622