Hi, using a NetApp-box: do you see the drives with a sysconfig -t and sysconfig -m? You might also be stumbeling over ndmpd-authorisation on the Netapp. We saw a default of 16 characters for the password... On the NetApp get the WWN of the drive with a 'storage' command (not sure, could be 'storage show tape' or similar) to check the switch zoning and compare with the path on the TSM Server. TSM Version is 5.2.3.3, ontap 7.0.1 in a test environment.
Just my two cents.. Regards, Markus Date: Mon, 23 May 2005 09:17:27 +0100 From: David McClelland <[EMAIL PROTECTED]> Subject: Re: Path from NAS to existing Library/Drives 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: [email protected] 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=3Ddatamover destt=3Ddrive devi=3Dname-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=3Dd 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 -- Diese E-Mail enth�lt vertrauliche und/oder rechtlich gesch�tzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt�mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet. Wir haben alle verkehrs�blichen Ma�nahmen unternommen, um das Risiko der Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anh�nge an dieser Nachricht durchzuf�hren. Wir schlie�en au�er f�r den Fall von Vorsatz oder grober Fahrl�ssigkeit die Haftung f�r jeglichen Verlust oder Sch�den durch virenbefallene Software oder E-Mails aus. Jede von der Bank versendete E-Mail ist sorgf�ltig erstellt worden, dennoch schlie�en wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden. ______________________________________________________________________ This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail or of parts hereof is strictly forbidden. We have taken precautions to minimize the risk of transmitting software viruses but nevertheless advise you to carry out your own virus checks on any attachment of this message. We accept no liability for loss or damage caused by software viruses except in case of gross negligence or willful behaviour. Any e-mail messages from the Bank are sent in good faith, but shall not be binding or construed as constituting any kind of obligation on the part of the Bank.
