toasters

toasters@lists.teaparty.net

13520 discussions

Re: Any script to analyse Autosupport weekly log???
by Steven Lim 24 May '06

24 May '06

Hi Chris, The "Autosupport Dashboard" is a great tool. That's exactly what I need. Thanks for the help. Cheers, Steven On 5/24/06, Chris Madden <maddenca(a)yahoo.com> wrote: > Hi, > > NetApp recently introduced viewing of ASUP data and proactive > recommendations on the NOW website; it's called the "AutoSupport Dashboard" > and is here: https://now.netapp.com/eservice/ASUPSearchServlet > > The ASUP viewing will show you all ASUPs submitted to NetApp, but the > proactive recommendations require at least 2 x the WEEKLY_LOG ASUPs to have > been received. > > Hope that helps. > > Cheers, > -Chris > > > -----Original Message----- > From: Blake Golliher [mailto:thelastman@gmail.com] > Sent: Wednesday, May 24, 2006 07:07 > To: Steven Lim > Cc: Toasters > Subject: Re: Any script to analyse Autosupport weekly log??? > > Does DFM not capture it all for you? What are you looking for that DFM > doesn't get for you? Or are you looking more at proactive stuff, predicting > when a disk will fail that kinda stuff? > > -Blake > > On 5/23/06, Steven Lim <steven.kblim(a)gmail.com> wrote: > > Hi Guys, > > > > Anyone of you have any scripts that analyse a list of autosupport and > > generate a summary of problems/potential problems?? Although if there > > is any fault, ASUP will sent out a seperate mail but this is only for > > critical problem, what bout NOT critical error?? I have also DFM > > monitoring these filers. > > > > Many thanks. > > > >

1 0

AW: command usage summary, 2006
by Geissler, Norbert 24 May '06

24 May '06

Hi Tim, fine tool to get an overview of command usage ! I made a small enhancement, because due to security reasons we don't use rsh but ssh for remote administration of filers... Feel free to use this enhanced script below in the future. Norbert =================== enhanced cmd summary script begin ============================ #!/usr/local/bin/perl # # This script summarizes command and api usage on a # Network Appliance filer running Data ONTAP. In other words, it counts # how many times each command/sub-command has been used, by # looking at the auditlogs. # # Usage on Unix is: # # cd /mnt/$FILER/etc # where /mnt/$FILER is the mounted root volume # perl cmd_summary.pl # # or on Windows: # # cd F: # where F: is the mounted root volume # cd \etc # perl cmd_summary.pl # # In other words, change directories to the /etc directory of the # filer's root volume, and run this script. The script looks at # the messages file and all the auditlog files, and summarizes # command and api usage. # # The output of the command will look like this: # ############################################################################ # System tweety (ID 0033611543) is running NetApp Release 7.0.1 # count=167 rsh=sysconfig -a # count=28 rsh=version # count=11 rsh=options autosupport.enable # count=167 ssh=sysconfig -a # count=28 ssh=version # count=571 api=options-get # count=100 api=options-set # count=23 cons=version ############################################################################ # # The lines in this output specify the frequency count of things invoked in # three categories: rsh (commands submitted using rsh), cons (commands # submitted using telnet or on the serial console), and api (things executed # using the ONTAPI API interface). # fourth category added: ssh (commands submitted using ssh) # my %rshusage; my %sshusage; my %consusage; my %apiusage; my $system = ""; my $anyerr = 0; foreach $f (<messages log/auditlog*>) { if ( ! open(FF, $f) ) { print STDERR "Error: unable to open $f - $!\n\n" ."This program must be run in the " ."'etc' directory of the filer's root volume.\n\n"; $anyerr = 1; next } while (<FF>) { if ( /kern.log.rotate:/ || /log_rotate:/ ) { chop; $system = $_; $system =~ s/.*System /System /; } elsif ( /RSH INPUT COMMAND/ ) { my $s = $_; $s =~ s/.*RSH INPUT COMMAND is //; my @words = split(/[\s;]/,$s); my $cmd = $words[0]." ".$words[1]; if ( $words[0] ne "" ) { if ( not defined $rshusage{$cmd} ) { $rshusage{$cmd} = 1; } else { $rshusage{$cmd} += 1; } } } elsif ( /SSH INPUT COMMAND/ ) { my $s = $_; $s =~ s/.*SSH INPUT COMMAND is //; my @words = split(/[\s;]/,$s); my $cmd = $words[0]." ".$words[1]; if ( $words[0] ne "" ) { if ( not defined $sshusage{$cmd} ) { $sshusage{$cmd} = 1; } else { $sshusage{$cmd} += 1; } } } elsif ( /IN:console shell:/ ) { my $s = $_; $s =~ s/.*console shell://; my @words = split(/\s/,$s); my $cmd = $words[0]." ".$words[1]; if ( $words[0] ne "" ) { if ( not defined $consusage{$cmd} ) { $consusage{$cmd} = 1; } else { $consusage{$cmd} += 1; } } } elsif ( /Java_Thread.*:API:in:/ && ! /relog syslog/ ) { chop; my $api = $_; $api =~ s/[^<]*<//; $api =~ s/\/?>.*//; if ( not defined $apiusage{"Java-$api"} ) { $apiusage{"Java-$api"} = 1; } else { $apiusage{"Java-$api"} += 1; } } elsif ( /:API:in:/ && ! /relog syslog/ ) { chop; my $api = $_; $api =~ s/.*\/admin\'><//; $api =~ s/.*version="..."><//; $api =~ s/\/?>.*//; if ( not defined $apiusage{$api} ) { $apiusage{$api} = 1; } else { $apiusage{$api} += 1; } } } } if ( $system ne "" ) { print("$system\n"); } foreach $key ( sort { $rshusage{$b} <=> $rshusage{$a} } keys %rshusage ) { print("count=$rshusage{$key} rsh=$key\n"); } foreach $key ( sort { $sshusage{$b} <=> $sshusage{$a} } keys %sshusage ) { print("count=$sshusage{$key} ssh=$key\n"); } foreach $key ( sort { $consusage{$b} <=> $consusage{$a} } keys %consusage ) { print("count=$consusage{$key} cons=$key\n"); } foreach $key ( sort { $apiusage{$b} <=> $apiusage{$a} } keys %apiusage ) { print("count=$apiusage{$key} api=$key\n"); =================== enhanced cmd summary script end ============================ -----Ursprüngliche Nachricht----- Von: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] Im Auftrag von Tim Thompson Gesendet: Mittwoch, 24. Mai 2006 00:00 An: toasters(a)mathworks.com Betreff: command usage summary, 2006 The following is a request similar to one made here a little over a year ago. The recent survey about advanced commands was very useful, and reminded us that it would be good to refresh and augment our data about command usage. Attached below is a perl script that will look at the auditlogs of a filer running Data ONTAP and summarize command, sub-command, and api usage. Only a summary is produced - it shouldn't contain any customer-sensitive information. It will not put any load on the filer, and should consume only a minute or so of CPU time on the machine running the perl script (depending on how large your auditlog files are). We would greatly appreciate it if anyone using Data ONTAP could run this script on as many filers as possible and send the output to usage(a)netapp.com (a special address set up to collect this data). Usage is described in the comments at the top of the script. If you don't feel comfortable running a script you've received through email, you can run the identical script that you can find in the Toolchest section of NetApp's NOW site: http://now.netapp.com/NOW/download/tools/cmd_summary/ Thanks very much for your help. ...Tim Thompson...Network Appliance, Inc...tjt(a)netapp.com... #!/usr/local/bin/perl # # This script summarizes command and api usage on a # Network Appliance filer running Data ONTAP. In other words, it counts # how many times each command/sub-command has been used, by # looking at the auditlogs. # # Usage on Unix is: # # cd /mnt/$FILER/etc # where /mnt/$FILER is the mounted root volume # perl cmd_summary.pl # # or on Windows: # # cd F: # where F: is the mounted root volume # cd \etc # perl cmd_summary.pl # # In other words, change directories to the /etc directory of the # filer's root volume, and run this script. The script looks at # the messages file and all the auditlog files, and summarizes # command and api usage. # # The output of the command will look like this: # ############################################################################ # System tweety (ID 0033611543) is running NetApp Release 7.0.1 # count=167 rsh=sysconfig -a # count=28 rsh=version # count=11 rsh=options autosupport.enable # count=571 api=options-get # count=100 api=options-set # count=23 cons=version ############################################################################ # # The lines in this output specify the frequency count of things invoked in # three categories: rsh (commands submitted using rsh), cons (commands # submitted using telnet or on the serial console), and api (things executed # using the ONTAPI API interface). my %rshusage; my %consusage; my %apiusage; my $system = ""; my $anyerr = 0; foreach $f (<messages log/auditlog*>) { if ( ! open(FF, $f) ) { print STDERR "Error: unable to open $f - $!\n\n" ."This program must be run in the " ."'etc' directory of the filer's root volume.\n\n"; $anyerr = 1; next } while (<FF>) { if ( /kern.log.rotate:/ || /log_rotate:/ ) { chop; $system = $_; $system =~ s/.*System /System /; } elsif ( /RSH INPUT COMMAND/ ) { my $s = $_; $s =~ s/.*RSH INPUT COMMAND is //; my @words = split(/[\s;]/,$s); my $cmd = $words[0]." ".$words[1]; if ( $words[0] ne "" ) { if ( not defined $rshusage{$cmd} ) { $rshusage{$cmd} = 1; } else { $rshusage{$cmd} += 1; } } } elsif ( /IN:console shell:/ ) { my $s = $_; $s =~ s/.*console shell://; my @words = split(/\s/,$s); my $cmd = $words[0]." ".$words[1]; if ( $words[0] ne "" ) { if ( not defined $consusage{$cmd} ) { $consusage{$cmd} = 1; } else { $consusage{$cmd} += 1; } } } elsif ( /Java_Thread.*:API:in:/ && ! /relog syslog/ ) { chop; my $api = $_; $api =~ s/[^<]*<//; $api =~ s/\/?>.*//; if ( not defined $apiusage{"Java-$api"} ) { $apiusage{"Java-$api"} = 1; } else { $apiusage{"Java-$api"} += 1; } } elsif ( /:API:in:/ && ! /relog syslog/ ) { chop; my $api = $_; $api =~ s/.*\/admin\'><//; $api =~ s/.*version="..."><//; $api =~ s/\/?>.*//; if ( not defined $apiusage{$api} ) { $apiusage{$api} = 1; } else { $apiusage{$api} += 1; } } } } if ( $system ne "" ) { print("$system\n"); } foreach $key ( sort { $rshusage{$b} <=> $rshusage{$a} } keys %rshusage ) { print("count=$rshusage{$key} rsh=$key\n"); } foreach $key ( sort { $consusage{$b} <=> $consusage{$a} } keys %consusage ) { print("count=$consusage{$key} cons=$key\n"); } foreach $key ( sort { $apiusage{$b} <=> $apiusage{$a} } keys %apiusage ) { print("count=$apiusage{$key} api=$key\n"); } exit($anyerr);

1 0

Geschäfts-Vorschlag!
by gooman1＠virgilio.it 24 May '06

24 May '06

Geschäfts-Vorschlag! Von:joy Gooman Email:joygooman@netscape.net Sehr geehrte Damen u. Herren, Geschäfts-Vorschlag! Sicher sind Sie verwundert, diese Nachricht von jemandem zu erhalten, den sie nicht personlich kennen. Der Grund weshalb ich mich an Sie wende ist das ich Simon Muzenda in, der erstgeborene Sohn von Azabeya Zulue, einem der bekanntesten schwarzen Farmer in Zimbabwe. Er wurde vor kurzem im Laufe des Landstreites in meinem Land ermordet. Ich erhielt Ihre Adresse durch das Interne und habe mich entschieden mich an Sie zu wenden. Bevor mein Vater starb, nahm er mich mit nach Johannesburg um dort einen Betrag von 9,5 Millionen US$ (Neun Millionen funfhunderttausend US Dollar) bei einer privaten Sicherheitsfirma zu deponieren. Er hat die drohende Gefahr geahnt und daher diesen Betrag in einer Kassette dort hinterlegt, die er als normales Wertgut deklarierte um keinen Verdacht zu erwecken. Die Kosten für die Hinterlegung gering zu halten. Niemand weiss also von dem Bargeld in dieser Kassette. Ursprunglich war dieser Betrag für neue Maschinen und Chemikalien für seine Farm gedacht, ausserdem wollte er neues Farmland in Swaziland erwerben. Das Landproblem entstand als der Präsident von Zimbabwe, Mr. Robert Mugabe, seine neue Landreform durchsetzte bei der nur die reichen weissen Farmer und einige wenige schwarze Farmer Vorteile verschafft wurden, für alle anderen war die Existenz nun bedroht. Daraus resultierten dann schlielich die Unruhen die sich ausbreiteten und denen viele Menschen zum Opfer fielen und ihr Leben lassen mussten. Leider ist mein Vater ebenfalls eines dieser Opfer das sein Leben verlor. Vor diesem Hintergrund bin ich mit der Familie unter lebensgefährlichen Umständen aus Zimbabwe nach Holland geflohen, hier haben wir politisches Asyl beantragt. Das in Sudafrika zuruckgelassene Geld wollen wir nun der Sicherheit wegen auf ein Konto hier bertragen. Das Gesetz in Holland verbietet es aber Menschen die politisches Asyl beantragt haben während dieses Verfahrens ein Konto zu erschaffnen oder irgendwelche Transfers die über die hollandische Grenze hinausgehen abzuwickeln. Als der erstgeborene Sohn bin ich nun für meine ganze Familie verantwortlich und habe die Rolle meines Vaters als Bewacher und Beschitzer ubernommen. Nun stehe ich vor dem Problem dieses Geld ohne Wissen der afrikanischen Regierung hierher zu transferieren, ansonsten wurde man uns den gesamten Betrag enteignen, dieses Geld ist aber alles das uns noch geblieben ist. Die Südafrikanische Regierung unterstutzt wohl die Regierung Zimbabwes, so dass auch dort nichts von meinem Vorhaben bekannt werden darf. Die Zukunftsplane beider Länder sind wohl genauso ähnlich wie es deren politische Vergangenheit ist.Als Geschäftsmann suche ich nun nach einem Partner dem ich voll und ganz vertrauen kann, dem ich meine und auch die Zukunft meiner ganzen Familie anvertrauen kann. Ich möchte Sie wissen lassen, dass mein Plan völlig ohne Risiko ist, falls Sie mir und meiner Familie helfen wollen. Alles worum ich Sie bitte, ist eine Vereinbarung mit der hollandischen Niederlassung der Sicherheitsfirma zu treffen, das hinterlegte Wertgut auszuhändigen. Ich meinerseits habe bereits Anweisung gegeben die Kassette von Sudafrika nach Holland zu senden. Vorher allerdings müssen noch einige wichtige Formalitäten erledigt werden, wie die Änderung des Begunstigten an diesem Wertgut. Weiterhin habe Ich vor diese Geld nach Erhalt möglichst gut und gewinnbringend zu investieren. Ich möchte Ihnen zwei Vorschläge unterbreiten.Erstens biete ich Ihnen einen Teil der Gesamtsumme an, wenn Sie bereit, Ihr eigenes Konto für diese Transaktion zur Verfugung zu stellen.Oder aber Sie sind an einer Partnerschaft mit mir interessiert um diese Summe profitabel in Ihrem Land zu investieren.Egal welcher Vorschlag Ihnen mehr zusagt, zögern Sie nicht mir Ihre Entscheidung mitzuteilen. Für alle entstehenden Unkosten habe ich 5% des Gesamtbetrages ingeplant. Sollten Sie nicht an einer Partnerschaft mit mir interessiert sein, biete ich Ihnen 25% des Betrages an und werde die verbleibenden 70% für meine Investitionen in Ihrem Land nutzen.Sie können mich jederzeit unter dieser e-Mail Adresse erreichen: (joygooman(a)netscape.net ) Ich bitte Sie jedoch um Ihre absolute Verschwiegenheit in dieser Angelegenheit Dritten gegenuber. Gott schutze Sie! Hochachtungsvoll Ihr ergebene, Dr. Joy Gooman joygooman(a)netscape.net

1 0

RE: downgrading the firmware on NetApp drives
by Matti Ryymin 24 May '06

24 May '06

In maintenance mode you'll find the commands label wipe <diskid> and label makespare <diskid> Those two commands given in this order should help you to get the disk recognized by your version of ontap. -Matti- _____ From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Glenn Walker Sent: 24. toukokuuta 2006 6:23 To: Nathan G. Mitchell; George, Andrew; toasters(a)mathworks.com Subject: RE: downgrading the firmware on NetApp drives Label erase 7.54 is the command if I recall. My recommendation is to call NetApp support and have them walk you through it. The BEST course of action is to have the drive with the 'bad' label replaced via RMA. Glenn _____ From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Nathan G. Mitchell Sent: Tuesday, May 23, 2006 10:29 PM To: George, Andrew; toasters(a)mathworks.com Subject: RE: downgrading the firmware on NetApp drives I wish the old machine still existed so that I could zero the old drive on that machine. That would sure help! Even in priv set diag I don't see the disk_erase_label command. The bad drive is 7.54. What would be the syntax for the command and what priv would I have to use to execute it? I hope I don't do something horrible and erase all the disklabels or something. Am I looking in the wrong place? How do I use the "ok" at the boot prompt? -- nate _____ From: George, Andrew [mailto:georgea@anz.com] Sent: Tuesday, May 23, 2006 9:20 PM To: Nathan G. Mitchell; toasters(a)mathworks.com Subject: RE: downgrading the firmware on NetApp drives Hi, Thats not a firmware problem thats the disk label. Essentially the disk was removed from a filer running a later version of OnTap so the version of OnTap in the filer thats trying to read it can't understand it. Theres two possible ways of fixing it (that I know of, one of the gurus might no a better way) 1) Put the disk back in the old system (or a system running a later version of OnTap) and then zero the disk 2) Reboot the filer and use the label erase command (I might be rmisrmembering the actual command..it's documented on Now) which is a command from the Ok prompt Andrew _____ From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Nathan G. Mitchell Sent: Wednesday, 24 May 2006 10:10 AM To: toasters(a)mathworks.com Subject: downgrading the firmware on NetApp drives I found a 36GB NetApp drive for my f740 with FC9 shelves and when I put it in the machine, it said: Tue May 23 19:14:07 EDT [raid.assim.disk.badlabelversion:error]: The label on disk 7.54 (S/N 3CD0FN3X000021098HUD) is a newer version than that supported by this software. Either remove the disk or upgrade the system software. Of course, the disk_fw_update command didn't work because the versio of the firmware is NEWER than what's supported by my OS (Data Ontap 6.4.4p7). How does one go aboot DOWNGRADING the firmware on a NetApp drive? -- nate

1 0

Any script to analyse Autosupport weekly log???
by Steven Lim 24 May '06

24 May '06

Hi Guys, Anyone of you have any scripts that analyse a list of autosupport and generate a summary of problems/potential problems?? Although if there is any fault, ASUP will sent out a seperate mail but this is only for critical problem, what bout NOT critical error?? I have also DFM monitoring these filers. Many thanks.

2 1

RE: downgrading the firmware on NetApp drives
by Glenn Walker 24 May '06

24 May '06

Label erase 7.54 is the command if I recall. My recommendation is to call NetApp support and have them walk you through it. The BEST course of action is to have the drive with the 'bad' label replaced via RMA. Glenn ________________________________ From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Nathan G. Mitchell Sent: Tuesday, May 23, 2006 10:29 PM To: George, Andrew; toasters(a)mathworks.com Subject: RE: downgrading the firmware on NetApp drives I wish the old machine still existed so that I could zero the old drive on that machine. That would sure help! Even in priv set diag I don't see the disk_erase_label command. The bad drive is 7.54. What would be the syntax for the command and what priv would I have to use to execute it? I hope I don't do something horrible and erase all the disklabels or something. Am I looking in the wrong place? How do I use the "ok" at the boot prompt? -- nate ________________________________ From: George, Andrew [mailto:georgea@anz.com] Sent: Tuesday, May 23, 2006 9:20 PM To: Nathan G. Mitchell; toasters(a)mathworks.com Subject: RE: downgrading the firmware on NetApp drives Hi, Thats not a firmware problem thats the disk label. Essentially the disk was removed from a filer running a later version of OnTap so the version of OnTap in the filer thats trying to read it can't understand it. Theres two possible ways of fixing it (that I know of, one of the gurus might no a better way) 1) Put the disk back in the old system (or a system running a later version of OnTap) and then zero the disk 2) Reboot the filer and use the label erase command (I might be rmisrmembering the actual command..it's documented on Now) which is a command from the Ok prompt Andrew ________________________________ From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Nathan G. Mitchell Sent: Wednesday, 24 May 2006 10:10 AM To: toasters(a)mathworks.com Subject: downgrading the firmware on NetApp drives I found a 36GB NetApp drive for my f740 with FC9 shelves and when I put it in the machine, it said: Tue May 23 19:14:07 EDT [raid.assim.disk.badlabelversion:error]: The label on disk 7.54 (S/N 3CD0FN3X000021098HUD) is a newer version than that supported by this software. Either remove the disk or upgrade the system software. Of course, the disk_fw_update command didn't work because the versio of the firmware is NEWER than what's supported by my OS (Data Ontap 6.4.4p7). How does one go aboot DOWNGRADING the firmware on a NetApp drive? -- nate

2 1

RE: downgrading the firmware on NetApp drives
by Nathan G. Mitchell 24 May '06

24 May '06

I wish the old machine still existed so that I could zero the old drive on that machine. That would sure help! Even in priv set diag I don't see the disk_erase_label command. The bad drive is 7.54. What would be the syntax for the command and what priv would I have to use to execute it? I hope I don't do something horrible and erase all the disklabels or something. Am I looking in the wrong place? How do I use the "ok" at the boot prompt? -- nate ________________________________ From: George, Andrew [mailto:georgea@anz.com] Sent: Tuesday, May 23, 2006 9:20 PM To: Nathan G. Mitchell; toasters(a)mathworks.com Subject: RE: downgrading the firmware on NetApp drives Hi, Thats not a firmware problem thats the disk label. Essentially the disk was removed from a filer running a later version of OnTap so the version of OnTap in the filer thats trying to read it can't understand it. Theres two possible ways of fixing it (that I know of, one of the gurus might no a better way) 1) Put the disk back in the old system (or a system running a later version of OnTap) and then zero the disk 2) Reboot the filer and use the label erase command (I might be rmisrmembering the actual command..it's documented on Now) which is a command from the Ok prompt Andrew ________________________________ From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Nathan G. Mitchell Sent: Wednesday, 24 May 2006 10:10 AM To: toasters(a)mathworks.com Subject: downgrading the firmware on NetApp drives I found a 36GB NetApp drive for my f740 with FC9 shelves and when I put it in the machine, it said: Tue May 23 19:14:07 EDT [raid.assim.disk.badlabelversion:error]: The label on disk 7.54 (S/N 3CD0FN3X000021098HUD) is a newer version than that supported by this software. Either remove the disk or upgrade the system software. Of course, the disk_fw_update command didn't work because the versio of the firmware is NEWER than what's supported by my OS (Data Ontap 6.4.4p7). How does one go aboot DOWNGRADING the firmware on a NetApp drive? -- nate

1 0

RE: downgrading the firmware on NetApp drives
by George, Andrew 24 May '06

24 May '06

Hi, Thats not a firmware problem thats the disk label. Essentially the disk was removed from a filer running a later version of OnTap so the version of OnTap in the filer thats trying to read it can't understand it. Theres two possible ways of fixing it (that I know of, one of the gurus might no a better way) 1) Put the disk back in the old system (or a system running a later version of OnTap) and then zero the disk 2) Reboot the filer and use the label erase command (I might be rmisrmembering the actual command..it's documented on Now) which is a command from the Ok prompt Andrew _____ From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Nathan G. Mitchell Sent: Wednesday, 24 May 2006 10:10 AM To: toasters(a)mathworks.com Subject: downgrading the firmware on NetApp drives I found a 36GB NetApp drive for my f740 with FC9 shelves and when I put it in the machine, it said: Tue May 23 19:14:07 EDT [raid.assim.disk.badlabelversion:error]: The label on disk 7.54 (S/N 3CD0FN3X000021098HUD) is a newer version than that supported by this software. Either remove the disk or upgrade the system software. Of course, the disk_fw_update command didn't work because the versio of the firmware is NEWER than what's supported by my OS (Data Ontap 6.4.4p7). How does one go aboot DOWNGRADING the firmware on a NetApp drive? -- nate

1 0

downgrading the firmware on NetApp drives
by Nathan G. Mitchell 24 May '06

24 May '06

I found a 36GB NetApp drive for my f740 with FC9 shelves and when I put it in the machine, it said: Tue May 23 19:14:07 EDT [raid.assim.disk.badlabelversion:error]: The label on disk 7.54 (S/N 3CD0FN3X000021098HUD) is a newer version than that supported by this software. Either remove the disk or upgrade the system software. Of course, the disk_fw_update command didn't work because the versio of the firmware is NEWER than what's supported by my OS (Data Ontap 6.4.4p7). How does one go aboot DOWNGRADING the firmware on a NetApp drive? -- nate

1 0

command usage summary, 2006
by Tim Thompson 23 May '06

23 May '06

The following is a request similar to one made here a little over a year ago. The recent survey about advanced commands was very useful, and reminded us that it would be good to refresh and augment our data about command usage. Attached below is a perl script that will look at the auditlogs of a filer running Data ONTAP and summarize command, sub-command, and api usage. Only a summary is produced - it shouldn't contain any customer-sensitive information. It will not put any load on the filer, and should consume only a minute or so of CPU time on the machine running the perl script (depending on how large your auditlog files are). We would greatly appreciate it if anyone using Data ONTAP could run this script on as many filers as possible and send the output to usage(a)netapp.com (a special address set up to collect this data). Usage is described in the comments at the top of the script. If you don't feel comfortable running a script you've received through email, you can run the identical script that you can find in the Toolchest section of NetApp's NOW site: http://now.netapp.com/NOW/download/tools/cmd_summary/ Thanks very much for your help. ...Tim Thompson...Network Appliance, Inc...tjt(a)netapp.com... #!/usr/local/bin/perl # # This script summarizes command and api usage on a # Network Appliance filer running Data ONTAP. In other words, it counts # how many times each command/sub-command has been used, by # looking at the auditlogs. # # Usage on Unix is: # # cd /mnt/$FILER/etc # where /mnt/$FILER is the mounted root volume # perl cmd_summary.pl # # or on Windows: # # cd F: # where F: is the mounted root volume # cd \etc # perl cmd_summary.pl # # In other words, change directories to the /etc directory of the # filer's root volume, and run this script. The script looks at # the messages file and all the auditlog files, and summarizes # command and api usage. # # The output of the command will look like this: # ############################################################################ # System tweety (ID 0033611543) is running NetApp Release 7.0.1 # count=167 rsh=sysconfig -a # count=28 rsh=version # count=11 rsh=options autosupport.enable # count=571 api=options-get # count=100 api=options-set # count=23 cons=version ############################################################################ # # The lines in this output specify the frequency count of things invoked in # three categories: rsh (commands submitted using rsh), cons (commands # submitted using telnet or on the serial console), and api (things executed # using the ONTAPI API interface). my %rshusage; my %consusage; my %apiusage; my $system = ""; my $anyerr = 0; foreach $f (<messages log/auditlog*>) { if ( ! open(FF, $f) ) { print STDERR "Error: unable to open $f - $!\n\n" ."This program must be run in the " ."'etc' directory of the filer's root volume.\n\n"; $anyerr = 1; next } while (<FF>) { if ( /kern.log.rotate:/ || /log_rotate:/ ) { chop; $system = $_; $system =~ s/.*System /System /; } elsif ( /RSH INPUT COMMAND/ ) { my $s = $_; $s =~ s/.*RSH INPUT COMMAND is //; my @words = split(/[\s;]/,$s); my $cmd = $words[0]." ".$words[1]; if ( $words[0] ne "" ) { if ( not defined $rshusage{$cmd} ) { $rshusage{$cmd} = 1; } else { $rshusage{$cmd} += 1; } } } elsif ( /IN:console shell:/ ) { my $s = $_; $s =~ s/.*console shell://; my @words = split(/\s/,$s); my $cmd = $words[0]." ".$words[1]; if ( $words[0] ne "" ) { if ( not defined $consusage{$cmd} ) { $consusage{$cmd} = 1; } else { $consusage{$cmd} += 1; } } } elsif ( /Java_Thread.*:API:in:/ && ! /relog syslog/ ) { chop; my $api = $_; $api =~ s/[^<]*<//; $api =~ s/\/?>.*//; if ( not defined $apiusage{"Java-$api"} ) { $apiusage{"Java-$api"} = 1; } else { $apiusage{"Java-$api"} += 1; } } elsif ( /:API:in:/ && ! /relog syslog/ ) { chop; my $api = $_; $api =~ s/.*\/admin\'><//; $api =~ s/.*version="..."><//; $api =~ s/\/?>.*//; if ( not defined $apiusage{$api} ) { $apiusage{$api} = 1; } else { $apiusage{$api} += 1; } } } } if ( $system ne "" ) { print("$system\n"); } foreach $key ( sort { $rshusage{$b} <=> $rshusage{$a} } keys %rshusage ) { print("count=$rshusage{$key} rsh=$key\n"); } foreach $key ( sort { $consusage{$b} <=> $consusage{$a} } keys %consusage ) { print("count=$consusage{$key} cons=$key\n"); } foreach $key ( sort { $apiusage{$b} <=> $apiusage{$a} } keys %apiusage ) { print("count=$apiusage{$key} api=$key\n"); } exit($anyerr);

1 0

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