toasters

toasters@lists.teaparty.net

13514 discussions

Monitoring Tools for Failure Detection
by Ben Rockwood 13 Apr '02

13 Apr '02

Hello Masters of Toast, I'm looking for some input and suggestions on something I'm preparing to take up, any suggestions or comments are appreciated... There are several tools avalible (namely MRTG and Cricket) for monitoring Filers (and I suppose NetCache's too), but I've not found these tools adiquate. The problem is that these tools are best at graphing statical information over a period of time, which is important to most of you for reporting and monitoring the performance of your Filers. However, in my case, I'm not really interested in the performance of the filers. What I am interested in is general health and failure detection. At one point the filers were monitored by logging in each day and manually checking via sysconfig -r, then (unwilling to log into every filer for quick checks) I decided to implement a small tool which could via SNMP do basic checking and reporting of filers basic vitals via a single command. I'm now becoming unsatisfied with this tool, and preparing to build a much more complex tool that can do more than simply look for failures in componants, but also do analysis on networking and fibre channel statistics, automated failure detection to a paging system, as well as offer both CLI and CGI interfaces. A later version would probly grow to include trapping. So the question is this. Am I wasting my time? Is there already a sutable tool to do this? I understand that NetApp has a GUI tool that can do almost anything you want with the filers via SNMP, but I'm uninterested in this type of tool. Whats important to me is getting a complete picture of a filers (or set of filers) health at a glance by issuing a single command or by executing a single CGI script. Would this tool be useful or of any interest to others? Thank You. Ben Rockwood brockwood(a)homestead-inc.com

3 2

NDMP restore on NT server
by SreeHarsha.V.Kannantha 13 Apr '02

13 Apr '02

Hi, I have to restore the data from our offsite tape directly on to NT server not on the filer. Has anybody done the restore of NDMP backed up data from filer directly on to a NT server. Thanks SreeHarsha

1 0

RE: time sync issue
by Surlow, Jim 12 Apr '02

12 Apr '02

Igor, I believe that the NTP protocol recommends 3 time servers as part of the algorithm calls for checking for network latency, and keeping in mind that the "authority" time server may drift as well. If you think that your 740 is "more stable", add that to the list of time servers (I think that the filer will allow a query), then it will get even more interesting. I know that on unix servers, it is suggested that localhost be added as a low priority host - that way, just in case the network bogs down, it can rely on the local clock without having to reset it all the time. Hope this helps, Jim -----Original Message----- From: Igor Schein [mailto:igor@txc.com] Sent: Friday, April 12, 2002 4:00 PM To: toasters(a)mathworks.com Subject: time sync issue Hi, I have 2 filers, 740 running 6.1.1R2 and 840 running 6.2R1. I have the same timed setup on both machines: timed.enable on timed.log on timed.max_skew 30m timed.min_skew 50 timed.proto ntp timed.sched hourly timed.servers ntphost1 Here's how the messages look for 740 filer: Time reported by time server ntphost1 is Fri Apr 12 13:10:54 GMT 2002 (skew +0.088 secs). Time reported by time server ntphost1 is Fri Apr 12 14:08:34 GMT 2002 (skew +0.055 secs). Time reported by time server ntphost1 is Fri Apr 12 14:57:16 GMT 2002 (skew +0.129 secs). Time reported by time server ntphost1 is Fri Apr 12 17:11:09 GMT 2002 (skew +0.051 secs). Time reported by time server ntphost1 is Fri Apr 12 18:01:03 GMT 2002 (skew +0.058 secs). Time reported by time server ntphost1 is Fri Apr 12 19:01:11 GMT 2002 (skew +0.116 secs). Time reported by time server ntphost1 is Fri Apr 12 19:55:54 GMT 2002 (skew +0.080 secs). Time reported by time server ntphost1 is Fri Apr 12 20:06:43 GMT 2002 (skew +0.054 secs). Time reported by time server ntphost1 is Fri Apr 12 20:37:57 GMT 2002 (skew +0.098 secs). Time reported by time server ntphost1 is Fri Apr 12 21:05:39 GMT 2002 (skew +0.102 secs). The skew is always positive and always small ( 0.1 secs or less ). Now here're the messages for 840 filer: Time reported by time server ntphost1 is Fri Apr 12 12:05:10 GMT 2002 (skew -0.177 secs). Time reported by time server ntphost1 is Fri Apr 12 13:05:32 GMT 2002 (skew -0.221 secs). Time reported by time server ntphost1 is Fri Apr 12 13:52:17 GMT 2002 (skew +0.238 secs). Time reported by time server ntphost1 is Fri Apr 12 14:03:44 GMT 2002 (skew -0.065 secs). Time reported by time server ntphost1 is Fri Apr 12 16:08:06 GMT 2002 (skew -0.101 secs). Time reported by time server ntphost1 is Fri Apr 12 17:00:57 GMT 2002 (skew -0.102 secs). Time reported by time server ntphost1 is Fri Apr 12 18:06:15 GMT 2002 (skew -0.199 secs). Time reported by time server ntphost1 is Fri Apr 12 18:53:44 GMT 2002 (skew +0.185 secs). Time reported by time server ntphost1 is Fri Apr 12 19:08:31 GMT 2002 (skew -0.243 secs). Time reported by time server ntphost1 is Fri Apr 12 20:01:58 GMT 2002 (skew -0.140 secs). The skew's sign jumps back and forth, and the absolute value is over 0.2 secs ( becomes as high as 0.3 secs, which prompts make utility on clients to complain ). What can be wrong with the clock on 840 filer? I suppose I can change timed.sched to sync more frequently, but I am just curious about the nature of the issue. Thanks Igor

1 0

time sync issue
by Igor Schein 12 Apr '02

12 Apr '02

Hi, I have 2 filers, 740 running 6.1.1R2 and 840 running 6.2R1. I have the same timed setup on both machines: timed.enable on timed.log on timed.max_skew 30m timed.min_skew 50 timed.proto ntp timed.sched hourly timed.servers ntphost1 Here's how the messages look for 740 filer: Time reported by time server ntphost1 is Fri Apr 12 13:10:54 GMT 2002 (skew +0.088 secs). Time reported by time server ntphost1 is Fri Apr 12 14:08:34 GMT 2002 (skew +0.055 secs). Time reported by time server ntphost1 is Fri Apr 12 14:57:16 GMT 2002 (skew +0.129 secs). Time reported by time server ntphost1 is Fri Apr 12 17:11:09 GMT 2002 (skew +0.051 secs). Time reported by time server ntphost1 is Fri Apr 12 18:01:03 GMT 2002 (skew +0.058 secs). Time reported by time server ntphost1 is Fri Apr 12 19:01:11 GMT 2002 (skew +0.116 secs). Time reported by time server ntphost1 is Fri Apr 12 19:55:54 GMT 2002 (skew +0.080 secs). Time reported by time server ntphost1 is Fri Apr 12 20:06:43 GMT 2002 (skew +0.054 secs). Time reported by time server ntphost1 is Fri Apr 12 20:37:57 GMT 2002 (skew +0.098 secs). Time reported by time server ntphost1 is Fri Apr 12 21:05:39 GMT 2002 (skew +0.102 secs). The skew is always positive and always small ( 0.1 secs or less ). Now here're the messages for 840 filer: Time reported by time server ntphost1 is Fri Apr 12 12:05:10 GMT 2002 (skew -0.177 secs). Time reported by time server ntphost1 is Fri Apr 12 13:05:32 GMT 2002 (skew -0.221 secs). Time reported by time server ntphost1 is Fri Apr 12 13:52:17 GMT 2002 (skew +0.238 secs). Time reported by time server ntphost1 is Fri Apr 12 14:03:44 GMT 2002 (skew -0.065 secs). Time reported by time server ntphost1 is Fri Apr 12 16:08:06 GMT 2002 (skew -0.101 secs). Time reported by time server ntphost1 is Fri Apr 12 17:00:57 GMT 2002 (skew -0.102 secs). Time reported by time server ntphost1 is Fri Apr 12 18:06:15 GMT 2002 (skew -0.199 secs). Time reported by time server ntphost1 is Fri Apr 12 18:53:44 GMT 2002 (skew +0.185 secs). Time reported by time server ntphost1 is Fri Apr 12 19:08:31 GMT 2002 (skew -0.243 secs). Time reported by time server ntphost1 is Fri Apr 12 20:01:58 GMT 2002 (skew -0.140 secs). The skew's sign jumps back and forth, and the absolute value is over 0.2 secs ( becomes as high as 0.3 secs, which prompts make utility on clients to complain ). What can be wrong with the clock on 840 filer? I suppose I can change timed.sched to sync more frequently, but I am just curious about the nature of the issue. Thanks Igor

1 0

RE: Discrepancy between quota report and actual quota size
by Surlow, Jim 12 Apr '02

12 Apr '02

Paul, I use 6.0.1R3 and noticed this as well when I started using user quotas. Here's the issue - the user quota is for the user on the partition NOT the home directory itself. So, for instance, I have users who own files in other users' home directories. Doing a 'du -k' (I only use our filer for NFS/Unix, not for CIFS/NT) of that other user's home directory will report much more than what the quota report shows. This is exactly what you are seeing. Jim Surlow CSG Systems -----Original Message----- From: Maglinger, Paul [mailto:PMAGLINGER@scvl.com] Sent: Friday, April 12, 2002 2:55 PM To: 'NetApps list server' Subject: Discrepancy between quota report and actual quota size Running a 740 filer with 6.1.1R2P1. Just recently implemented user quotas on the home directories. Now when I bring up a quota report, the home directories show up but the amount the report is showing does not match the actual amount of data in the folder. I'm not talked a few K, but in one instance the report shows 4M of data when actually it is 1.2G. Thoughts? Remember, you are unique... just like everyone else! _____ Paul Maglinger, A+, CA, CET, MCSE Systems Administrator Shoe Carnival Inc. (812)867-4674 pmaglinger(a)scvl.com <mailto:pmaglinger@scvl.com> _____

1 0

Discrepancy between quota report and actual quota size
by Maglinger, Paul 12 Apr '02

12 Apr '02

Running a 740 filer with 6.1.1R2P1. Just recently implemented user quotas on the home directories. Now when I bring up a quota report, the home directories show up but the amount the report is showing does not match the actual amount of data in the folder. I'm not talked a few K, but in one instance the report shows 4M of data when actually it is 1.2G. Thoughts? Remember, you are unique... just like everyone else! _____ Paul Maglinger, A+, CA, CET, MCSE Systems Administrator Shoe Carnival Inc. (812)867-4674 pmaglinger(a)scvl.com <mailto:pmaglinger@scvl.com> _____

1 0

FW: ndmpcopy speed test
by Summers, John 12 Apr '02

12 Apr '02

NDMP copy (within a filer). 2nd example is from a Solaris (2.6?) to a filer. Note: This was from a F630 filer on a 100tx-fd connection. Light load on the subnet. John Summers Subject: ndmpcopy speed test John, I did some ndmpcopy speed test and here's the results: -- Using the loopback on a 630 -- limited to 10Mbps --or-- 1.5MBps ultra5-rtp@root> ./ndmpcopy f630-rtp:/vol/vol0 f630-rtp:/vol/vol2 Password: Connecting to f630-rtp. Connecting to f630-rtp. f630-rtp: CONNECT: Connection established. f630-rtp: CONNECT: Connection established. f630-rtp: LOG: DUMP: f630-rtp: LOG: creating "/vol/vol0/../snapshot_for_backup.55" snapshot. f630-rtp: LOG: DUMP: f630-rtp: LOG: Using Full Volume Dump f630-rtp: LOG: DUMP: f630-rtp: LOG: Date of this level 0 dump: Thu Mar 7 12:41:56 2002. f630-rtp: LOG: DUMP: f630-rtp: LOG: Date of last level 0 dump: the epoch. f630-rtp: LOG: DUMP: f630-rtp: LOG: Dumping /vol/vol0/ to NDMP connection f630-rtp: LOG: DUMP: f630-rtp: LOG: mapping (Pass I)[regular files] f630-rtp: LOG: DUMP: f630-rtp: LOG: mapping (Pass II)[directories] f630-rtp: LOG: DUMP: f630-rtp: LOG: estimated 112610 KB. f630-rtp: LOG: DUMP: f630-rtp: LOG: dumping (Pass III) [directories] f630-rtp: LOG: RESTORE: f630-rtp: LOG: Thu Mar 7 12:42:00 2002: Begin level 0 restore f630-rtp: LOG: RESTORE: f630-rtp: LOG: Thu Mar 7 12:42:00 2002: Reading directories from the backup f630-rtp: LOG: DUMP: f630-rtp: LOG: dumping (Pass IV) [regular files] f630-rtp: LOG: RESTORE: f630-rtp: LOG: Thu Mar 7 12:42:00 2002: Creating files and directories. f630-rtp: LOG: RESTORE: f630-rtp: LOG: Warning: cannot create directory etc: File exists f630-rtp: LOG: RESTORE: f630-rtp: LOG: Warning: cannot create directory tmp: File exists f630-rtp: LOG: RESTORE: f630-rtp: LOG: The file: ./restore_symboltable could not be restored with its original name. f630-rtp: LOG: RESTORE: f630-rtp: LOG: It has been renamed to: ./rstabRENAME3C8B5BA4 f630-rtp: LOG: RESTORE: f630-rtp: LOG: Thu Mar 7 12:42:01 2002: Writing data to files. f630-rtp: LOG: RESTORE: f630-rtp: LOG: Thu Mar 7 12:43:09 2002: Restoring NT ACLs. f630-rtp: LOG: DUMP: f630-rtp: LOG: dumping (Pass V) [ACLs] f630-rtp: LOG: DUMP: f630-rtp: LOG: 112587 KB f630-rtp: LOG: DUMP: f630-rtp: LOG: DUMP IS DONE f630-rtp: LOG: DUMP: f630-rtp: LOG: Deleting "/vol/vol0/../snapshot_for_backup.55" snapshot. f630-rtp: LOG: RESTORE: f630-rtp: LOG: RESTORE IS DONE f630-rtp: HALT: The operation was successful! Waiting for f630-rtp to halt too. The transfer was successful, but the source filer hasn't halted yet. Elapsed time: 0 hours, 1 minutes, 22 seconds. f630-rtp: HALT: The operation was successful! The transfer is complete. Elapsed time: 0 hours, 1 minutes, 23 seconds. -- sysstat is showing a throughput of ~1.8MBps ultra5-rtp@root> rsh f630-rtp sysstat -sx 5 CPU NFS CIFS HTTP Total Net kB/s Disk kB/s Tape kB/s Cache Cache CP CP Disk in out read write read write age hit time ty util 1% 0 0 0 0 0 0 11 40 0 0 >60 100% 3% T 3% 0% 0 0 0 0 0 0 0 0 0 0 >60 100% 0% - 0% 1% 0 0 0 0 0 0 9 39 0 0 >60 100% 3% T 4% 0% 0 0 0 0 0 0 0 0 0 0 >60 100% 0% - 0% 1% 0 0 0 0 0 0 9 39 0 0 >60 100% 3% T 4% 4% 0 0 0 0 1 1 349 82 0 0 >60 97% 12% 2 16% 85% 0 0 0 0 825 825 1695 2046 0 0 >60 96% 22% F 32% 48% 0 0 0 0 1291 1291 1580 12759 0 0 >60 99% 100% : 100% 68% 0 0 0 0 2685 2685 2947 8422 0 0 >60 100% 78% B 69% 42% 0 0 0 0 1902 1902 1924 6442 0 0 >60 100% 66% F 51% 47% 0 0 0 0 2568 2568 2543 5582 0 0 >60 100% 49% F 45% 27% 0 0 0 0 1715 1715 1683 1229 0 0 >60 99% 13% F 11% 33% 0 0 0 0 1570 1569 1764 4264 0 0 >60 98% 38% : 34% 45% 0 0 0 0 2244 2244 2140 5722 0 0 >60 100% 50% F 46% 20% 0 0 0 0 1240 1240 2329 0 0 0 >60 99% 0% - 86% 26% 0 0 0 0 951 951 1330 5629 0 0 >60 100% 48% F 59% 20% 0 0 0 0 1339 1339 1806 0 0 0 >60 98% 0% - 66% 46% 0 0 0 0 1757 1757 2380 5375 0 0 >60 99% 48% F 64% 22% 0 0 0 0 1401 1401 1287 0 0 0 >60 100% 0% - 14% CPU NFS CIFS HTTP Total Net kB/s Disk kB/s Tape kB/s Cache Cache CP CP Disk in out read write read write age hit time ty util 56% 0 0 0 0 1951 1951 1756 6995 0 0 >60 100% 72% F 59% 47% 0 0 0 0 48 48 79 3974 0 0 >60 100% 49% Z 32% 0% 0 0 0 0 0 0 0 0 0 0 >60 100% 0% - 0% 12% 0 0 0 0 0 0 96 5488 0 0 >60 100% 42% T 41% 1% 0 0 0 0 0 0 3 18 0 0 >60 100% 2% : 2% 18% 642 0 0 642 135 217 0 0 0 0 >60 100% 0% - 0% ============================================= -- ndmpcopy via the 100Mbps link: ultra5-rtp@root> ./ndmpcopy f810-rtp:/vol/vol0 f630-rtp:/vol/vol2 Password: Connecting to f810-rtp. Connecting to f630-rtp. f810-rtp: CONNECT: Connection established. f630-rtp: CONNECT: Connection established. f810-rtp: LOG: DUMP: f810-rtp: LOG: creating "/vol/vol0/../snapshot_for_backup.5" snapshot. f810-rtp: LOG: DUMP: f810-rtp: LOG: Using Full Volume Dump f810-rtp: LOG: DUMP: f810-rtp: LOG: Date of this level 0 dump: Thu Mar 7 12:43:34 2002. f810-rtp: LOG: DUMP: f810-rtp: LOG: Date of last level 0 dump: the epoch. f810-rtp: LOG: DUMP: f810-rtp: LOG: Dumping /vol/vol0/ to NDMP connection f810-rtp: LOG: DUMP: f810-rtp: LOG: mapping (Pass I)[regular files] f810-rtp: LOG: DUMP: f810-rtp: LOG: mapping (Pass II)[directories] f810-rtp: LOG: DUMP: f810-rtp: LOG: estimated 195915 KB. f810-rtp: LOG: DUMP: f810-rtp: LOG: dumping (Pass III) [directories] f630-rtp: LOG: RESTORE: f630-rtp: LOG: Thu Mar 7 12:44:10 2002: Begin level 0 restore f630-rtp: LOG: RESTORE: f630-rtp: LOG: Thu Mar 7 12:44:10 2002: Reading directories from the backup f810-rtp: LOG: DUMP: f810-rtp: LOG: dumping (Pass IV) [regular files] f630-rtp: LOG: RESTORE: f630-rtp: LOG: Thu Mar 7 12:44:12 2002: Creating files and directories. f630-rtp: LOG: RESTORE: f630-rtp: LOG: Warning: cannot create directory etc: File exists f630-rtp: LOG: RESTORE: f630-rtp: LOG: Warning: cannot create directory tmp: File exists f630-rtp: LOG: RESTORE: f630-rtp: LOG: Thu Mar 7 12:44:13 2002: Writing data to files. f630-rtp: LOG: RESTORE: f630-rtp: LOG: Thu Mar 7 12:45:07 2002: Restoring NT ACLs. f810-rtp: LOG: DUMP: f810-rtp: LOG: dumping (Pass V) [ACLs] f810-rtp: LOG: DUMP: f810-rtp: LOG: 194475 KB f810-rtp: LOG: DUMP: f810-rtp: LOG: DUMP IS DONE f810-rtp: LOG: DUMP: f810-rtp: LOG: Deleting "/vol/vol0/../snapshot_for_backup.5" snapshot. f810-rtp: HALT: The operation was successful! Waiting for f630-rtp to halt too. f630-rtp: LOG: RESTORE: f630-rtp: LOG: RESTORE IS DONE f630-rtp: HALT: The operation was successful! The transfer is complete. Elapsed time: 0 hours, 1 minutes, 12 seconds. -- sysstat showing a throughput of ~4.850 MBps CPU NFS CIFS HTTP Total Net kB/s Disk kB/s Tape kB/s Cache Cache CP CP Disk in out read write read write age hit time ty util 1% 0 0 0 0 0 0 9 39 0 0 >60 100% 3% T 3% 1% 0 0 0 0 0 0 0 0 0 0 >60 100% 0% - 0% 1% 0 0 0 0 11 1 8 40 0 0 >60 92% 3% T 3% 48% 0 0 0 0 708 15 9 551 0 0 >60 95% 8% F 4% 76% 0 0 0 0 3036 63 212 12866 0 0 >60 100% 100% B 97% 96% 0 0 0 0 4835 100 181 10638 0 0 >60 100% 87% F 82% 100% 0 0 0 0 5087 105 178 10726 0 0 >60 100% 87% F 82% 63% 0 0 0 0 3220 67 107 6211 0 0 >60 100% 56% F 50% 100% 0 0 0 0 4991 103 175 10579 0 0 >60 100% 87% F 80% 95% 0 0 0 0 4901 101 161 9847 0 0 >60 100% 82% F 77% CPU NFS CIFS HTTP Total Net kB/s Disk kB/s Tape kB/s Cache Cache CP CP Disk in out read write read write age hit time ty util 100% 0 0 0 0 5268 109 171 10368 0 0 >60 100% 85% F 81% 35% 0 0 0 0 1582 33 95 5522 0 0 >60 100% 46% F 43% 7% 0 0 0 0 483 10 0 0 0 0 >60 100% 0% - 0% 81% 0 0 0 0 4305 89 124 7385 0 0 >60 100% 63% F 57% 87% 0 0 0 0 3066 63 167 10077 0 0 >60 100% 89% F 84% 0% 0 0 0 0 0 0 0 0 0 0 >60 100% 0% - 0% 1% 0 0 0 0 0 0 0 0 0 0 >60 100% 0% - 0% 12% 0 0 0 0 0 0 92 5349 0 0 >60 100% 42% T 40% 0% 0 0 0 0 0 0 0 0 0 0 >60 100% 0% - 0% 1% 0 0 0 0 0 0 11 40 0 0 >60 100% 3% T 3% 0% 0 0 0 0 0 0 0 0 0 0 >60 100% 0% - 0% 1% 0 0 0 0 0 0 12 42 0 0 >60 100% 4% T 4% 1% 0 0 0 0 0 0 0 0 0 0 >60 100% 0% - 0% 0% 0 0 0 0 0 0 0 0 0 0 >60 100% 0% - 0%

1 0

automatic drive mapping from a cifs client to the filer...
by sdolive＠ngco.com 12 Apr '02

12 Apr '02

I created a share on an F740 (Ontap 6.0.1R3) and am trying to map a drive from a CIFS client (Windows 2000) automatically at logon point. I have no problems mapping the drive once I am logged on but would like it so that when a user logs onto the 2000 machine the drive gets mapped automatically. I have followed the microsoft suggestion which is copying the autoexnt, instexnt and servmess.dll files to the winnt/system32 root. I have also created a batch file whcih contains the following line 'net use j: \\filer\x03. I have tried the starting the service with the local account and also the administrators account but still nothing. I have also added another command to the batch file (md test) and when the service is started it creates the directory test but does not map the drive. Is their anyone out there who has experienced the same problem? Thanks, Shaun Technical Services 416-235-2122 sdolive(a)ngco.com

4 3

NDMP Speed
by ADMIN 12 Apr '02

12 Apr '02

Does anyone have a base line transfer speed using NDMP copy from one filer to another using 100 Full? I know there are a not of network variable that can fluctuate the speed. I am just trying to get a base line. Thanks

1 0

62R1 and NDMP copy
by ADMIN 12 Apr '02

12 Apr '02

I am in the process of planning a upgrade of a F7XX Filer to version 6.2R1 has anyone done this from version 5X? I am also wanting to try out the NDMP Copy built into 62R1. Does anyone have any good things or bad to say about it? I tried it in the past using a older version and a UNIX host and it sucked. Have they really made it better by integrating it into the OnTap code? Thanks for you help in advance

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters