toasters

toasters@lists.teaparty.net

2 participants
13529 discussions

RE: CIFS in Workgroup mode
by Alan McLachlan 16 Apr '03

16 Apr '03

Robert, One problem is that in workgroup mode NTFS security isn't available. In fact, no real security is available... There appear to be two options to using a filer in a Novell environment: 1) The "gateway" Novell server approach. This involves using a Novell server running Novell NFS Services (with lots of CPU and RAM) with a direct back-to-back link to the filer to act as an I/O path. Clients and application hosts only see the Novell server, while the filer thinks the Novell server is a Unix NIS server that also happens to be it's only client :o). Security is a subset of Novell permissions as available by mapping Unix permissions. The drawback here is that the Novell server itself will be an I/O bottleneck. 2) eDirectory and Windows integration. For this you need a DC, as you have identified. The Windows DC runs the Novell eDirectory client and the security is synchronised with Novell Account Manager. All clients that need to access the filer need to have the CIFS redirector running. Permissions are mapped by Novell Account Manager. An issue with approach 2 is that when passwords are changed by a helpdesk directly in eDirectory, they may not be synchronised immediately. If anyone has found a workaround for this please respond. regards, Alan. -----Original Message----- From: Robert Borowicz [mailto:rbaus@swbell.net] Sent: Wednesday, 16 April 2003 6:26 AM To: toasters(a)mathworks.com Subject: CIFS in Workgroup mode Does anybody run CIFS shares in workgroup mode? That is not booted/authenticated with a PDC? I have the joy of trying to make my machine work in a Novell environment and no DC and would love to share ideas with other lucky souls like me.... TIA -Bob Borowicz **** ASI Solutions Disclaimer **** The material transmitted may contain confidential and/or privileged material and is intended only for the addressee. If you receive this in error, please notify the sender and destroy any copies of the material immediately. ASI will protect your Privacy according to the 10 Privacy Principles outlined under the new Privacy Act, Dec 2001. This email is also subject to copyright. Any use of or reliance upon this material by persons or entities other than the addressee is prohibited. E-mails may be interfered with, may contain computer viruses or other defects. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. **** END OF MESSAGE ****

1 0

CIFS in Workgroup mode
by Robert Borowicz 15 Apr '03

15 Apr '03

Does anybody run CIFS shares in workgroup mode? That is not booted/authenticated with a PDC? I have the joy of trying to make my machine work in a Novell environment and no DC and would love to share ideas with other lucky souls like me.... TIA -Bob Borowicz

2 1

dell LTO
by Rogers, Jamie 15 Apr '03

15 Apr '03

Has anyone ever used a Dell 122 LTO for backups on a 760 running 6.3.1 or earlier? Jamie.

1 0

RE: Data ONTAP 5.3.7R3 on a n F520
by Joe C Ropar 15 Apr '03

15 Apr '03

Andy, I killed the threads but there are two other processes listed relating to ndmp: ndmpdclassloader ndmpdserver Should those be deleted also? After deleting the threads I was still unable to delete the snapshots. Thanks, Joe Ropar "Hatcher, Andy" <Andy.Hatcher(a)netapp.com> 04/15/2003 01:12 PM To: "Joe C Ropar" <Joe_C_Ropar(a)raytheon.com> cc: Subject: RE: Data ONTAP 5.3.7R3 on a n F520 It's: kill -9 <threadname> I think you'll also have problems if the thread name has a space in it. [No quoting available.] -- Andy Hatcher ahatcher(a)netapp.com > -----Original Message----- > From: Brian Long [mailto:brilong@cisco.com] > Sent: Tuesday, April 15, 2003 10:43 AM > To: Joe C Ropar > Cc: toasters(a)mathworks.com > Subject: Re: Data ONTAP 5.3.7R3 on a n F520 > > > Joe, > > Please remember jsh is COMPLETELY UNSUPPORTED. If it crashes > your filer, I'm not responsible and neither is Netapp :) > > Having said that, you should try kill with other options. > It's been a long time since I used this. Maybe you need to > kill PID (i.e. 517). > > /Brian/ > > On Tue, 2003-04-15 at 13:11, Joe C Ropar wrote: > > Brian, > > Thanks for the reply. > > I'm in the java shell and ps in fact returns several Ndmpd threads > > even though > ndmpd status indicates no sessions active. > > > > But when I try to kill, the following returns: > > > > jsh> kill Thread-517 > > Arg expected > > > > Is there a switch I'm missing, like kill -9 <threadName> > > > > By the way the filer is running the most current version of > ONTAP for > > the model ( F520 ) and has been rebooted in the last 42 days which > > postdates the timestamp on the snapshots. > > It looks like the kill solution or boot from floppy into maintenance > > mode and deleting them are going to be the only workable > > solutions. > > > > > > Regards, > > Joseph C. Ropar > > Unix Systems Administrator > > Raytheon Systems Company > > cell (214) 869-7901 > > desk (972) 952-4306 > > e-mail jropar(a)raytheon.com > > > > > > > > > > Brian Long > > <brilong(a)cisco.com> > > > > 04/14/2003 12:42 PM > > > > To: Joe > > C Ropar > > <Joe_C_Ropar(a)raytheon.com> > > cc: > > toasters(a)mathworks.com > > Subject: > > Re: Data ONTAP 5.3.7R3 > > on a n F520 > > > > > > There is an unsupported java shell you can invoke and kill the ndmp > > sessions. Even though ndmpd says no active sessions, it > probably has > > some snapshots locked. > > > > filer> java netapp.cmds.jsh > > jsh> ps > > <grab thread names for ndmpd sessions> > > jsh> kill threadName > > jsh> exit > > filer> snap delete vol0 snapshot-name > > > > /Brian/ > > > > On Mon, 2003-04-14 at 12:25, Joe C Ropar wrote: > > > Greetings, > > > First time caller. > > > > > > I have a 520 for which "snap list" returns several > > snapshot_for_backup > > > ( busy ) lines. > > > These are old and for some reason were not deleted > automatically. I > > > cannot delete them manually either. > > > > > > I have tried setting "snap sched vol0 0 0 0" turned "vol options > > vol0 > > > nosnap on" > > > and was still unable to delete the snapshots. > > > > > > Below is the output of snap list. > > > > > > Any suggestions on how to get rid of the unwanted > snapshots would be > > > appreciated. > > > > > > Volume vol0 working............................................. > > > > > > %/used %/total date name > > > ---------- ---------- ------------ -------- > > > 1% ( 1%) 1% ( 1%) Apr 14 09:02 hourly.0 > > > 2% ( 1%) 1% ( 1%) Apr 14 07:02 hourly.1 > > > 2% ( 1%) 1% ( 1%) Apr 14 00:01 weekly.0 > > > 2% ( 1%) 1% ( 1%) Apr 13 17:02 hourly.2 > > > 2% ( 1%) 1% ( 1%) Apr 13 15:02 hourly.3 > > > 2% ( 1%) 2% ( 1%) Apr 13 13:02 hourly.4 > > > 3% ( 1%) 2% ( 1%) Apr 13 11:02 hourly.5 > > > 3% ( 1%) 2% ( 1%) Apr 13 00:01 nightly.0 > > > 3% ( 2%) 2% ( 1%) Apr 12 00:01 nightly.1 > > > 8% ( 7%) 6% ( 5%) Apr 11 00:03 nightly.2 > > > 9% ( 7%) 6% ( 5%) Apr 10 00:02 nightly.3 > > > 32% (28%) 29% (24%) Sep 20 21:48 > snapshot_for_backup.498 (busy) > > > 33% (28%) 30% (24%) Sep 18 23:37 > snapshot_for_backup.496 (busy) > > > 33% (27%) 31% (23%) Sep 14 01:28 > snapshot_for_backup.495 (busy) > > > 34% (26%) 33% (22%) Sep 09 19:52 > snapshot_for_backup.494 (busy) > > > 36% (26%) 35% (22%) Aug 07 21:41 snapshot_for_backup.481.old > > > (busy) > > > > > > > > > Regards, > > > Joseph C. Ropar > > > Unix Systems Administrator > > > Raytheon Systems Company > > > cell (214) 869-7901 > > > desk (972) 952-4306 > > > e-mail jropar(a)raytheon.com > > > > >

2 1

Re: Data ONTAP 5.3.7R3 on a n F520
by Joe C Ropar 15 Apr '03

15 Apr '03

Brian, Thanks for the reply. I'm in the java shell and ps in fact returns several Ndmpd threads even though > ndmpd status indicates no sessions active. But when I try to kill, the following returns: jsh> kill Thread-517 Arg expected Is there a switch I'm missing, like kill -9 <threadName> By the way the filer is running the most current version of ONTAP for the model ( F520 ) and has been rebooted in the last 42 days which postdates the timestamp on the snapshots. It looks like the kill solution or boot from floppy into maintenance mode and deleting them are going to be the only workable solutions. Regards, Joseph C. Ropar Unix Systems Administrator Raytheon Systems Company cell (214) 869-7901 desk (972) 952-4306 e-mail jropar(a)raytheon.com Brian Long <brilong(a)cisco.com> 04/14/2003 12:42 PM To: Joe C Ropar <Joe_C_Ropar(a)raytheon.com> cc: toasters(a)mathworks.com Subject: Re: Data ONTAP 5.3.7R3 on a n F520 There is an unsupported java shell you can invoke and kill the ndmp sessions. Even though ndmpd says no active sessions, it probably has some snapshots locked. filer> java netapp.cmds.jsh jsh> ps <grab thread names for ndmpd sessions> jsh> kill threadName jsh> exit filer> snap delete vol0 snapshot-name /Brian/ On Mon, 2003-04-14 at 12:25, Joe C Ropar wrote: > Greetings, > First time caller. > > I have a 520 for which "snap list" returns several snapshot_for_backup > ( busy ) lines. > These are old and for some reason were not deleted automatically. > I cannot delete them manually either. > > I have tried setting "snap sched vol0 0 0 0" turned "vol options vol0 > nosnap on" > and was still unable to delete the snapshots. > > Below is the output of snap list. > > Any suggestions on how to get rid of the unwanted snapshots would be > appreciated. > > Volume vol0 > working............................................. > > %/used %/total date name > ---------- ---------- ------------ -------- > 1% ( 1%) 1% ( 1%) Apr 14 09:02 hourly.0 > 2% ( 1%) 1% ( 1%) Apr 14 07:02 hourly.1 > 2% ( 1%) 1% ( 1%) Apr 14 00:01 weekly.0 > 2% ( 1%) 1% ( 1%) Apr 13 17:02 hourly.2 > 2% ( 1%) 1% ( 1%) Apr 13 15:02 hourly.3 > 2% ( 1%) 2% ( 1%) Apr 13 13:02 hourly.4 > 3% ( 1%) 2% ( 1%) Apr 13 11:02 hourly.5 > 3% ( 1%) 2% ( 1%) Apr 13 00:01 nightly.0 > 3% ( 2%) 2% ( 1%) Apr 12 00:01 nightly.1 > 8% ( 7%) 6% ( 5%) Apr 11 00:03 nightly.2 > 9% ( 7%) 6% ( 5%) Apr 10 00:02 nightly.3 > 32% (28%) 29% (24%) Sep 20 21:48 snapshot_for_backup.498 (busy) > 33% (28%) 30% (24%) Sep 18 23:37 snapshot_for_backup.496 (busy) > 33% (27%) 31% (23%) Sep 14 01:28 snapshot_for_backup.495 (busy) > 34% (26%) 33% (22%) Sep 09 19:52 snapshot_for_backup.494 (busy) > 36% (26%) 35% (22%) Aug 07 21:41 snapshot_for_backup.481.old > (busy) > > > Regards, > Joseph C. Ropar > Unix Systems Administrator > Raytheon Systems Company > cell (214) 869-7901 > desk (972) 952-4306 > e-mail jropar(a)raytheon.com

2 1

RE: Legato and NDMP
by Mike Ball 15 Apr '03

15 Apr '03

Gavin, How long is the root password on the Netapp? You will need to make sure it is 8 characters or less otherwise a NDMP connection will not be able to be made from the Legato Server. Mike -----Original Message----- From: Gavin Kelman [mailto:gavin@metahusky.net] Sent: Tuesday, April 08, 2003 4:42 AM To: toasters(a)mathworks.com Subject: Legato and NDMP We've just received a nice new F825, which we're trying to integrate into our exsiting Legato Networker backup system. I've been speaking to our Legato support, but they're not getting very far, and each day that passes is another day for us without backups. We have a Quantum ATL1500 jukebox directly attached (Robot controller and one drive) to a Sun box, which is a Legato storage node. The 2nd SCSI drive is connected to the back of our F825, which picks it up fine, and is configured as an NDMP device in Networker. Now, the problem is, Networker complains that it can't establish an NDMP connection to the F825, even tho NDMP is enabled on the F825, and I've double-checked the username is root and the password is correct. Attempting to do an inventory in nwadmin fails on either device in the jukebox. Also, NDMP doesn't do incrementals the normal way, so I was thinking of just backing up the F825 over the NFS mounts, but I hear that's not a good idea with Legato. We're running DOT 6.3.1r1 and Legato Networker 6.1.3. Anyone have any suggestions, apart from "stop using Legato"? Cheers, Gavin. -- Gavin Kelman Phone : 07967 360 822 Unix Administrator Email : gavin(a)metahusky.net

1 0

RE: Enterprise Vault for Exchange
by Parsons Alastair (UK) 15 Apr '03

15 Apr '03

We have been using KVS Enterprise Vault on an F820, quite successfully, for about a year and a half. We set it up on its own volume and there were no special requirements as far as the filer was concerned. Cheers Alastair -----Original Message----- From: Bui, Marcus [mailto:Marcus.Bui@aiminvestments.com] Sent: 14 04 2003 18:02 To: 'toasters(a)mathworks.com' Subject: Enterprise Vault for Exchange Hi Toasters, I have an F820 that will be used for MS Exchange archiving of PST. The product use is Enterprise Vault for Exchange by KVInc. I'm finding out more details about the product but is basically stores PST in compress single instance. Is anyone currently using the product? Any 'gotchas' or specific requirement setup on the Filer? thanks, Marcus Bui ======================================================= This electronic message contains information from the mmO2 plc Group which may be privileged or confidential. The information is intended to be for the use of the individual(s) or entity named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please notify us by telephone or email (to the numbers or address above) immediately. Please note that as of May 1st we will no longer be accepting email for any btcellnet.net, btcellnet.co.uk or cellnet.co.uk addresses. From this date all mail should be addressed to O2.com =======================================================

3 2

RE: rsh sysstat (was: 2 telnet sessions)
by Ehrhart, Rick 14 Apr '03

14 Apr '03

Be careful about running non-terminating commands from rsh. See burt 88028 for details. When a non-terminating command executed via rsh is aborted, it leaves a rsh session hanging of the filer. If the abortions continue, all the rsh sessions will be used up. Try rsh <filer> "sysstat -c <count> 1". The count is the number of times the sysstat will execute. - Rick - ----------------------------------------------------------------- Rick Ehrhart Network Appliance "I believe in nothing, Everything is sacred." > -----Original Message----- > From: Neto, Antonio Jose Rodrigues > Sent: Monday, April 14, 2003 8:59 AM > To: devnull(a)adc.idt.com; toasters(a)mathworks.com > Subject: RE: 2 telnet sessions > > > Hi, > > Could I give a suggestion? > > Enable rsh. > > tty1 > #rsh filer sysstat 1 > > tty2 > #telnet filer > > Hope this helps > > regards > > neto > > -----Original Message----- > From: devnull(a)adc.idt.com [mailto:devnull@adc.idt.com] > Sent: Monday, April 14, 2003 12:26 PM > To: toasters(a)mathworks.com > Subject: 2 telnet sessions > > > Dear Toasters, > > I am trying to see if its possible to connect to the filer > via more than 1 > telnet session. > > The only "options" i see is telnet.enable > > I would like to be able to connect to the filer via 2 telnet sessions, > maybe even run sysstat under 1 and do "work" on the other. > > Please advice, > > Thanks, > > /dev/null > > devnull(a)adc.idt.com > > P.S: Running ancient versions 6.1.1R2 and 6.1.2R1. >

1 0

Remove
by Justen, Joel 14 Apr '03

14 Apr '03

Will someone please ask the administrator of this list to remove me? Thanks ************************************************************************** This email and any files transmitted with it are confidential and is intended solely for the use of the individual or entity to whom they are addressed. If you have received this E-mail in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMESweeper in accordance with the ThyssenKrupp Budd E-Mail Policy. **************************************************************************

1 0

RE: 2 telnet sessions
by Moritz.Willers＠ubsw.com 14 Apr '03

14 Apr '03

run as many 'fsh' (filer shell) on Unix host as you want to one filer. fsh requires the Term::Shell module. - Moritz #!/usr/bin/perl -wT # @(#) $Id: fsh,v 1.5 2003/03/20 12:45:14 willers Exp $ # Moritz.Willers(a)ubsw.com, Perot Systems, 2002 use strict; my $filer = shift || 'filer'; $filer =~ m/^(\w+)$/; $filer = $1; # untaint die "check on hostname argument failed. stopping right here\n" unless defined $filer; FSH->new($filer)->cmdloop; exit 0; package FSH; use English; use vars qw($dir $filer $getroot); BEGIN { # untaint ($dir = $0) =~ m#(.*/)#go; $dir = $1; $ENV{PATH} = "/usr/bin"; } use lib "$dir/../lib/perl"; use base qw(Term::Shell); sub init { my $self = shift; $filer = ${$self->{API}{args}}[0]; $getroot = $UID == 0 ? undef : -x '/usr/bin/pbrun' ? '/usr/bin/pbrun' : -x '/usr/bin/sudo' ? '/usr/bin/sudo' : -x '/sbclocal/bin/sudo' ? '/sbclocal/bin/sudo' : die "Can't find sudo or pbrun\n"; } sub prompt_str { my $self = shift; return "$filer> "; } sub run_ { ; } # don't exit on empty input line sub catch_run { my ($self, @stuff) = @_; my @cmd = ('/usr/bin/rsh', $filer, @stuff); unshift @cmd, ($getroot) if (defined $getroot); system(@cmd); } sub run_help { print qq(fsh - filer shell Commands: exit - exits the filer shell help - prints this screen type ? to get the help on the filer commands ); } 1; __END__ =head1 NAME fsh - filer shell =head1 SYNOPSIS fsh [hostname] =head1 DESCRIPTION I<fsh> is a non-interactive shell to a NetApp filer with comandline editing and history functionality. It has been written to allow more than one administrator at a time to have a shell on the filer. It executes all commands on the filer via rsh and thus only allows for the non interactive filer commands, type '?' at the prompt to see them. The I<fsh> must be executed on a host that has trusted access to the filer via rsh, i.e. the maintenance server. If executed as unpriviledged user it will prepend every execution of rsh by sudo. This slows command execution down considerably. It is recommended to run the fsh as root. If no hostname is given it will execute all commands on I<filer>. The shell uses GNU readline (3) for the command prompt. The behaviour of the command line can be changed with settings in the I<.inputrc>, e.g. adding set editing-mode vi will enable vi command line editing. See the readline (3) manpage for details. =head1 AUTHOR Moritz.Willers(a)ubsw.com, Perot Systems, 2002 =cut Visit our website at http://www.ubswarburg.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.

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