Hi Fred, Which NAS are you using? Things to double-check here are that your datamover definitions are correct (i.e. correct HLA, LLA, username and password). I witnessed similar errors (EMC Celerra) when I was given an incorrect IP address for the datamover, defined my TSM datamover against this and was unable to define any paths with the 'see previous error messages' error reported (after a 300 or so second wait). Once I'd got to the bottom of this and made sure the datamover had the correct IP address, the path definitions went through successfully almost immediately.
Good luck. David McClelland Customer Domain Expert - Transactions Shared Infrastructure Development Reuters 85 Fleet Street London EC4P 4AJ -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of fred johanson Sent: 20 May 2005 20:22 To: ADSM-L@VM.MARIST.EDU Subject: Path from NAS to existing Library/Drives We've attached a new NAS to an existing TSM system, with a 3584 and 6 3592s. Following the steps in Chapter 6 of the Admin Guide, everything went smoothly until step 6, Defining Tape Drives and Paths. Since the drives already exist in TSM it looks like all I should have to do is define the path from NAS to drive: def path nasbox tsmdrive srct=datamover destt=drive devi=name-supplied-by hardware-guy. This produced ANR1763E, i.e., Command Failed - see previous error messages. But there are none of those. I tried variations of case for the device name with the same result. However, when I went to the WebAdmin and tried, leaving off the device name and using the AutoDetect button, I got a success message - for all six drives. But q path f=d shows nothing in the device name. So, in my confusion, I ask, did I miss something when I used the CLI? or is there something amiss in the Admin Guide? are the paths really there and usable? Fred Johanson ITSM Administrator University of Chicago 773-702-8464 ----------------------------------------------------------------- Visit our Internet site at http://www.reuters.com To find out more about Reuters Products and Services visit http://www.reuters.com/productinfo Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.
