Yes, we've tried "btpasswd -p -u root" and "btpasswd -p -u root -h <hostname>". With no luck at all...
-----Original Message----- From: Jeff Krueger [mailto:jkrueger@qualcomm.com] Sent: Monday, April 17, 2000 7:24 PM To: Rainchik, Aleksandr (MED, Non GE) Cc: toasters@mathworks.com Subject: Re: NDMP backups stopped after network upgrade
This could be caused by the BudTool password being out of sync.
The command "btpasswd -p -u root" should allow you to change this for all your NDMP aware NetApps. You could also use "btpasswd -p -u root -h <hostname>" to change it on a per-host basis if they are different.
Be sure you know what you're doing before you change the password though. It would probably be a good idea to get BudTool (Legato) support involved.
-- Jeff
-- ------------------------------------------------------------------------ ---- Jeff Krueger E-Mail: jeff@qualcomm.com NetApp File Server Lead Phone: 858-651-6709 IT Engineering and Support Fax: 858-651-6627 QUALCOMM, Incorporated Web: www.qualcomm.com
From "Rainchik, Aleksandr (MED, Non GE)" on Mon, 17 Apr 2000 17:04:52 CDT:
Hello,
We are using Budtool 4.6.1 to backup three NetApps F740 (Ontap 5.2.1P2D10). After our network has been down completely for about 15 minutes, we can't do backups any more... NDMP authorization failure for user root. Look
at
the end of this message for what we have in NetApp log files.
So,
a) ndmpd is running on NetApp. b) I can telnet, or rsh to NetApp as user root just fine. c) ndmp_hostinfo is also working perfect and I can telnet to port 10000
on NetApp. But, when I connect there, I get 5-6 garbage letters
only.
If I telnet to port 10000 to NetApp in another department, with newer Ontap, I get the same garbage _and_ the string "Connection successful".
Does
it make any sense to NDMP gurus? :)
d) we've tried rebooting one NetApp and that didn't help. e) we've tried btpasswd to create a new password for user root. Didn't help f) NIS is fine. I can do ypwhich or ypcat on filer...
Any ideas? Is there any way to run ndmpd in "verbose" or "debug" mode?
Mon Apr 17 12:00:00 CDT [statd]: 12:00pm up 11 days, 18:13 143494298 NFS ops, 961447 CIFS ops, 22 HTTP ops Mon Apr 17 13:00:00 CDT [statd]: 1:00pm up 11 days, 19:13 143588178 NFS ops, 962932 CIFS ops, 22 HTTP ops Mon Apr 17 13:00:11 CDT [ndmp_session_0]: ../common/ndmpd/connect.c:196 ndmpdConnectClientAuth: MD5 authorization failure by user: root. Mon Apr 17 13:00:11 CDT [ndmp_session_0]: ../common/ndmpd/comm.c:838 message 0x746f2061 not supported. Mon Apr 17 13:00:11 CDT [ndmp_session_0]: ../common/ndmpd/comm.c:1037 ndmp_process_messages: unexpected reply message: 0x746f2061. Mon Apr 17 13:59:21 CDT [ndmp_session_0]: ../common/ndmpd/connect.c:196 ndmpdConnectClientAuth: MD5 authorization failure by user: root. Mon Apr 17 13:59:21 CDT [ndmp_session_0]: ../common/ndmpd/comm.c:838 message 0x746f2061 not supported. Mon Apr 17 13:59:21 CDT [ndmp_session_0]: ../common/ndmpd/comm.c:1037 ndmp_process_messages: unexpected reply message: 0x746f2061. Mon Apr 17 13:59:32 CDT [ndmp_session_0]: ../common/ndmpd/connect.c:196 ndmpdConnectClientAuth: MD5 authorization failure by user: root. Mon Apr 17 14:00:00 CDT [statd]: 2:00pm up 11 days, 20:13 144027002 NFS ops, 998979 CIFS ops, 22 HTTP ops Mon Apr 17 14:22:28 CDT [ndmp_session_0]: ../common/ndmpd/connect.c:196 ndmpdConnectClientAuth: MD5 authorization failure by user: root. Mon Apr 17 15:00:00 CDT [statd]: 3:00pm up 11 days, 21:13 144202255 NFS ops, 999196 CIFS ops, 22 HTTP ops