ADSM-L

Re: [ADSM-L] Cannot define a path to a drive: help, please?

2007-06-19 11:16:35
Subject: Re: [ADSM-L] Cannot define a path to a drive: help, please?
From: Chris McKay <Chris.McKay AT YCDSB DOT CA>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 19 Jun 2007 11:15:29 -0400
I did try what Karel suggests, and in my particular case it didn't work,
but it might be worth a try.

http://www-1.ibm.com/support/docview.wss?rs=663&context=SSGSG7&q1=define+path&uid=swg21207777&loc=en_US&cs=utf-8&lang=en


"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> writes:
>Hi,
>
>Possibly you have to delete and redefine all your drives, paths and
>library in ITSM to pick up the added drive in the library.
>Afterall you have changed the library by adding a drive.
>
>
>Regards,
>
>Karel
>
>-----Original Message-----
>From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
>Joni Moyer
>Sent: dinsdag 19 juni 2007 16:12
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: Cannot define a path to a drive: help, please?
>
>Hi Chris,
>
>This is an EMC CDL 4400 with dual heads.  I am emulating an IBM 3584 and
>nothing has been changed on this system since I defined the library,
>drives, paths from a week ago.  I pretty much just went to add 1 more
>drive and it's path and I'm getting the error you see below where it
>doesn't want to recognize the element number.  At this point I'm not
>quite sure what the real issue is with the defining the path, but as you
>can see it's not liking the element number.
>
>********************************
>Joni Moyer
>Highmark
>Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966
>Fax: (717) 302-9826
>joni.moyer AT highmark DOT com
>********************************
>
>
>
>"Chris McKay" <Chris.McKay AT YCDSB DOT CA>
>Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>06/19/2007 10:05 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: Cannot define a path to a drive: help, please?
>
>
>
>
>
>
>Hi Joni,
>
>I did have this exact problem, but with a Windows server. What type of
>Library do you have??  Did you update any firmware lately?? We have a
>3584 library, and found the firmware was the problem. I had to downgrade
>the firmware, let it detect the drive define the drive, then update the
>firmware again.
>
>Hopefully this may be of some assistance.
>
>Take Care,
>
>Chris
>
>"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> writes:
>>Hi Everyone!
>>
>>I have a TSM server on AIX 5.3 and TSM is 5.3.4.2.  I have defined a
>>drive: vlto2-68 with define drive cdlb_dev vlto2-68.
>>
>>                               Library Name: CDLB_DEV
>>                                  Drive Name: VLTO2-68
>>                                 Device Type: UNKNOWN
>>                                     On-Line: Yes
>>                                Read Formats:
>>                               Write Formats:
>>                                     Element:
>>                                 Drive State: UNKNOWN
>>                                 Volume Name:
>>                                Allocated to:
>>                                         WWN:
>>                               Serial Number:
>>
>>I then tried to define a path to the drive and it will not let me:
>>
>>06/19/07 09:53:26     ANR2017I Administrator LIDZR8V issued command:
>>DEFINE PATH
>>                       tsmdev vlto2-68 srctype=server desttype=drive 
>>library=cd
>>                       lb_dev device=/dev/rmt68  (SESSION: 497257)
>>06/19/07 09:53:26     ANR8972E DEFINE PATH: Unable to find the element
>>number
>>                       for drive VLTO2-68 in library CDLB_DEV.
>(SESSION:
>>
>>                       497257)
>>
>>I have already defined 40 other drives & their paths successfully, but 
>>this one is giving me issues.  From the server it does appear as:
>>
>>  rmt68            U0.1-P2-I2/Q1-W2102000D77BD375D-LB000000000000   IBM
>>3580 Ultrium Tape Drive (FCP)
>>
>>        Manufacturer................IBM
>>        Machine Type and Model......ULT3580-TD2
>>        Serial Number...............1182255815
>>        Device Specific.(FW)........53Y2
>>
>>And since this is a virtual drive I then looked at the CDL and the 
>>serial numbers do match.
>>
>>Has anyone ever had this issue?  Does anyone have any suggestions on 
>>what I might be doing wrong?  Thanks in advance!
>>
>>********************************
>>Joni Moyer
>>Highmark
>>Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966
>>Fax: (717) 302-9826
>>joni.moyer AT highmark DOT com
>>********************************
>
>
>
>
>______________________________________________
>This message is for the sole use of the intended recipients and may
>contain confidential and privileged information. Any unauthorized
>review,
>use, disclosure or distribution is prohibited. If you are not an
>intended
>recipient, please contact the sender by reply email and destroy all
>copies
>of the original message. Thank you for your cooperation.
>
>




______________________________________________
This message is for the sole use of the intended recipients and may contain 
confidential and privileged information. Any unauthorized review, use, 
disclosure or distribution is prohibited. If you are not an intended recipient, 
please contact the sender by reply email and destroy all copies of the original 
message. Thank you for your cooperation.