Hi Karel, I rebooted the server and then I was able to see the new drive and define the path without receiving any error messages.
I just want to thank everyone for your suggestions and support throughout my problem!!!! ******************************** Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] ******************************** "Bos, Karel" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> 06/19/2007 11:35 AM Please respond to "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> To ADSM-L@VM.MARIST.EDU cc Subject Re: Cannot define a path to a drive: help, please? Hi Joni, You only delete the library within ITSM, you don't delete any volumes with data on them. Your volumes are bound to a devices class and that isn't deleted. So your data should be fine. - delete path to drives - delete drives - delete path to library - delete library - define library - define path to library (wait till its ready for operations in the act log) - define drives - define path to drives -checkin libvolumes stat=scratch (private volumes will issue a "can't assing status scratch" error; -checkin libvolumes stat=private This is done many times with our every growing real 3584 library. An other this we have done before is rebooting the ITSM server. This does many detects (define drives) and will init the ITSM library as well, but: - Can take a LONG time to register the hardware change (library frame extention took more than an our to fail and with above proc it was done in 10 min.); - Can fail; - Needs system down time. Regards, Karel ________________________________ From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: dinsdag 19 juni 2007 17:24 To: ADSM-L@VM.MARIST.EDU Subject: Re: Cannot define a path to a drive: help, please? Hi Karel, I already have data that is written to media that are defined to cdlb_dev, so I couldn't possibly delete the library. I'm a little confused as to what my options would be at this point. I would only be able to delete the drives & paths & re-define, but deleting the library isn't really an option when data is already written is it? Just let me know either way. Thanks! ******************************** Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] ******************************** "Bos, Karel" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> 06/19/2007 10:56 AM Please respond to "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> To ADSM-L@VM.MARIST.EDU cc Subject Re: Cannot define a path to a drive: help, please? 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:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: dinsdag 19 juni 2007 16:12 To: ADSM-L@VM.MARIST.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 [EMAIL PROTECTED] ******************************** "Chris McKay" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> 06/19/2007 10:05 AM Please respond to "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> To ADSM-L@VM.MARIST.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@VM.MARIST.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 >[EMAIL PROTECTED] >******************************** ______________________________________________ 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.
??D i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . ? O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . ? T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e p r i v i l e g e d . I f y o u r e c e i v e t h i s e - m a i l i n e r r o r , p l e a s e n o t i f y t h e s e n d e r i m m e d i a t e l y a n d d e s t r o y i t . A s i t s i n t e g r i t y c a n n o t b e s e c u r e d o n t h e I n t e r n e t , t h e A t o s O r i g i n g r o u p l i a b i l i t y c a n n o t b e t r i g g e r e d f o r t h e m e s s a g e c o n t e n t . A l t h o u g h t h e s e n d e r e n d e a v o u r s t o m a i n t a i n a c o m p u t e r v i r u s - f r e e n e t w o r k , t h e s e n d e r d o e s n o t w a r r a n t t h a t t h i s t r a n s m i s s i o n i s v i r u s - f r e e a n d w i l l n o t b e l i a b l e f o r a n y d a m a g e s r e s u l t i n g f r o m a n y v i r u s t r a n s m i t t e d . ? O n a l l o f f e r s a n d a g r e e m e n t s u n d e r w h i c h A t o s O r i g i n s u p p l i e s g o o d s a n d / o r s e r v i c e s o f w h a t e v e r n a t u r e , t h e T e r m s o f D e l i v e r y f r o m A t o s O r i g i n e x c l u s i v e l y a p p l y . T h e T e r m s o f D e l i v e r y s h a l l b e p r o m p t l y s u b m i t t e d t o y o u o n y o u r r e q u e s t . ? A t o s O r i g i n N e d e r l a n d B . V . / U t r e c h t K v K U t r e c h t 3 0 1 3 2 7 6 2
