ADSM-L

Re: Can't Define Drive Path

2005-04-04 14:43:06
Subject: Re: Can't Define Drive Path
From: Curtis Stewart <Curtis.Stewart AT LAWSON DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 4 Apr 2005 13:42:23 -0500
Once again, thanks Richard. I found an APAR that matched exactly. Stop and
start TSM then redifine the path and it worked. Something about TSM only
looking for the element number on initialization. I've only recently
started using this SCSI library, moved from an old 3494. Before that was
external STK libraries with ACSLS and Gresham..... Not having a real
library manager makes things different sometimes.

http://www-1.ibm.com/support/docview.wss?uid=swg1IC42633




curtis.stewart AT lawson DOT com



Andrew Raibeck <storman AT US.IBM DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/04/2005 09:57 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: Can't Define Drive Path






Curtis,

This is not my area of expertise, but have you tried shutting down and
restarting both TSM server and the library? That *might* do the trick.

Regarding the problem displaying message ANR8972E:

> 04/04/2005 09:10:57      << Message number 8972 not available for
language
>                           /USR/LIB/NLS/MSG/EN_US/ >> (SESSION: 50073)

Check the message catalog to ensure that it matches your installed TSM
server version, and that your language environment is configured correctly
(see the National Language Support appendix in the Quick Start book).

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2005-04-04
07:27:07:

> I recently had to have an LTO2 drive replaced in my STK L-700 tape
> library, and I can't create a drive path. It fails with the following
> error...
>
> 04/04/2005 09:10:57      ANR2017I Administrator 7760 issued command:
> DEFINE PATH
>                           msptsm01col LTO2-6 SRCTYPE=SERVER
DESTTYPE=DRIVE
>                           LIBRARY=L700LIB1 DEVICE=/dev/rmt9 ONLINE=YES
>                           AUTODETECT=YES  (SESSION: 50073)
> 04/04/2005 09:10:57      << Message number 8972 not available for
language
>                           /USR/LIB/NLS/MSG/EN_US/ >> (SESSION: 50073)
>
>
> I've deleted all the drive paths and the drive definition from TSM
without
> a problem, and confirmed they were all gone. I also deleted the device
> from the OS. I checked the director, and the FC drive is indeed logged
> into the SAN with the same WWPN as the previous drive, thanks to the
> persistent naming function of the L-700. After I deleted all the paths,
> and the drive from AIX, I verified it was indeed gone from them both.
> Then, ran cfgmgr to rediscover the drive. It gets discovered with the
same
> device name as before "/dev/rmt9", and shows up as available. I then,
> created the drive definition within TSM.
>
>
> 04/04/2005 08:59:29      ANR2017I Administrator 7760 issued command:
> DEFINE DRIVE
>                           L700LIB1 lto2-6 ELEMENT=505 ONLINE=YES
(SESSION:
> 49969)
>
> tsm: MSPTSM01COL>q drive l700lib1 lto2-6 f=d
>
>                                 Library Name: L700LIB1
>                                   Drive Name: LTO2-6
>                                  Device Type: UNKNOWN
>                                      On-Line: No
>                                 Read Formats:
>                                Write Formats:
>                                      Element: 505
>                                  Drive State: UNKNOWN
>                                 Allocated to:
>                                          WWN:
>                                Serial Number:
>               Last Update by (administrator): 7760
>                        Last Update Date/Time: 04/04/2005 09:15:21
> Cleaning Frequency (Gigabytes/ASNEEDED/NONE): NONE
>
> I double checked the element number by checking the  physical location
> against the element number in the library's remote managment software.
So,
> I'm sure that's right.
>
> Here's what the drive shows up as in AIX.
>
> rmt9  Available 1s-08-01     LTO Ultrium Tape Drive (FCP)
>
> Software Versions
> TSM Version:    5.2.4.1
> AIX 5.2 ML4
> Atape.driver               8.4.1.0  COMMITTED  IBM AIX Enhanced Tape and
>
> Anybody have any idea what I'm doing wrong?
>
> curtis.stewart AT lawson DOT com

<Prev in Thread] Current Thread [Next in Thread>