Easiest way....reboot the whole system. OR... 1. Halt TSM 2. rmdev -dl /dev/smc0 3. cfgmgr -v 4. Start TSM 5. show slots cdlb_dev
I've always just rebooted if I can get the downtime. Bill Boyer "A life? Cool! Where can I download one of those?" - ?? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Tuesday, June 19, 2007 11:25 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Cannot define a path to a drive: help, please? Hi Bill, I did a show slots cdlb_dev and I do only see the original 40 drives. I did have cfgmgr run and it did pick up the new drive definition (/dev/rmt68), but as you can see with the show slots, it doesn't see the new drive I added. When you say to reinitialize, what steps would I go through to do so? I wanted to make sure that I didn't misunderstand what you were stating below. Also, isn't this a little archaeic for TSM? If I ever have to add another drive to this environment this is a really messy way of doing it.... PVR slot information for library CDLB_DEV. Library : CDLB_DEV Product Id : 03584L32 Support module : 4 Mount count : 0 Drives : 40 Slots : 4096 Changers : 2 Import/Exports : 10 Device : /dev/smc0 Drive 0, element 257 Drive 1, element 258 Drive 2, element 259 Drive 3, element 260 Drive 4, element 261 Drive 5, element 262 Drive 6, element 263 Drive 7, element 264 Drive 8, element 265 Drive 9, element 266 Drive 10, element 267 Drive 11, element 268 Drive 12, element 269 Drive 13, element 270 Drive 14, element 271 Drive 15, element 272 Drive 16, element 273 Drive 17, element 274 Drive 18, element 275 Drive 19, element 276 Drive 20, element 277 Drive 21, element 278 Drive 22, element 279 Drive 23, element 280 Drive 24, element 281 Drive 25, element 282 Drive 26, element 283 Drive 27, element 284 Drive 28, element 285 Drive 29, element 286 Drive 30, element 287 Drive 31, element 288 Drive 32, element 289 Drive 33, element 290 Drive 34, element 291 Drive 35, element 292 Drive 36, element 293 Drive 37, element 294 Drive 38, element 295 Drive 39, element 296 Changer 0, element 1 Changer 1, element 2 ImpExp 0, element number 769 ImpExp 1, element number 770 ImpExp 2, element number 771 ImpExp 3, element number 772 ImpExp 4, element number 773 ImpExp 5, element number 774 ImpExp 6, element number 775 ImpExp 7, element number 776 ImpExp 8, element number 777 ImpExp 9, element number 778 ******************************** Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] ******************************** "William Boyer" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> 06/19/2007 10:25 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? I think what you need to do is have the library device in AIX re-initialize. I believe that TSM is only reporting on what the Atape device driver knows about the last time it was initialized at the last boot or cfgmgr. Try stopping TSM and 'rmdev -l /dev/smc(x)' to put it to s defined state, or just go ahead and 'rmdev -dl /dev/smc(x)' and remove the defition from the system. Then run your cfgmgr and bring up TSM and try your def path again. I don't believe that the TSM library definition and the Atape information are dynmically updated when you do anything to change the configuraiton at the library. Like adding drives. You can verify what TSM thinks is installed with the 'show slots <libraryname>'. This will list how many drives and their elements. If this doesn't match the actual configuration...reinitialize. Bill Boyer "Hit any user to continue..." - ?? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Tuesday, June 19, 2007 10:12 AM 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.