toasters

toasters@lists.teaparty.net

13514 discussions

RE: accessing local group
by Bui, Marcus 07 Jan '03

07 Jan '03

I called Netapp support and this are the recommendations. It did fix the problem. Thanks for all the input. 1. Remove the machine account for the Filer from the WindowsNT domain controller. 2. On the Filer, type: filer> cifs terminate 3. Issue these commands: filer> mv /etc/lclgroups.cfg /etc/lclgroups.old filer> mv /etc/filersid.cfg /etc/filersid.old filer> mv /etc/cifsconfig.cfg /etc/cifsconfig.old 4. Run cifs setup, and enter your apropriate information 5. Verify that you can join the WinNT domain, and that your users can now access and map the shares (if they cannot, please let me know, and please tell me what error messages you get) 6. If you dont want to re-create your shares manually from the Domain controller, Computer Manager, you can: cifs terminate mv /etc/cifsconfig.old /etc/cifsconfig.cfg cifs restart Cheers, Marcus -----Original Message----- From: Reinoud Reynders [mailto:reinoud.reynders@uz.kuleuven.ac.be] Sent: Thursday, January 02, 2003 4:18 PM To: Bui, Marcus; 'Fox, Adam'; toasters(a)mathworks.com Subject: Re: accessing local group An other possibility is that you run again 'cifs setup'. This do the job. You are than of course some minutes without CIFS. Best regards, Reinoud UZLEUVEN Belgium ----- Original Message ----- From: "Bui, Marcus" <Marcus_Bui(a)AIMFUNDS.COM> To: "'Fox, Adam'" <Adam.Fox(a)netapp.com>; <toasters(a)mathworks.com> Sent: Thursday, January 02, 2003 10:25 PM Subject: RE: accessing local group > I can mapped to the ETC folder, but unable to view/change the contents. Get > 'access denied'. > > -----Original Message----- > From: Fox, Adam [mailto:Adam.Fox@netapp.com] > Sent: Thursday, January 02, 2003 2:49 PM > To: 'Bui, Marcus' > Subject: RE: accessing local group > > > The key is to be in the Local Adminstrators group. When you > changed domains, perhaps this wasn't updated. Try taking a peek > at the filer etc\lclgroups.cfg on the filer and look at the SIDs > under the Administrators group. You can use the cifs lookup command > to decode the SIDs. If the Domain Admins Group isn't there, fix it > by changing the SIDs. BE VERY CAREFUL and have your old copy of this > file available either by copying it or having a known good copy in a > snapshot because you want to be careful and be able to fall back. > In order to make CIFS see changes in this file, you must terminate and > restart cifs (at least it's quicker than a reboot). > > Hope this helps. You may want to consider calling NTAP to walk you > through it, but that's how I would approach it. > > -- Adam Fox > NetApp Professional Services, NC > adamfox(a)netapp.com > > > > -----Original Message----- > From: Bui, Marcus [mailto:Marcus_Bui@AIMFUNDS.COM] > Sent: Thursday, January 02, 2003 2:39 PM > To: 'toasters(a)mathworks.com' > Subject: accessing local group > > > All, > > I have a test F85 (ONTAP 6.2.2) in an NT4 Domain but I am unable to access > the local group on the filer. The box was previously in W2K AD but was > moved to an NT4 domain. The filer is listed in the domain. I logged as > Domain Admin but still get 'access denied' when trying to access the filer's > local group. Did 'cifs testdc' and it is authenticating to the correct DC. > > Any suggestions is appreciated. > > thanks, > > Marcus Bui > >

1 0

LDAP auth ?
by Frank Bonnet 07 Jan '03

07 Jan '03

Hi Advice to netapp folks Monthes ago I asked if Ontap will support native LDAP (openldap) authentication ... I know active directory is supported BUT we do not want use M$ stuff here, we have a fully functionnal LDAP server running under UNIX ( Linux/Debian) and are satisfied with it. I repost my request as I have for now a brand new F87 that is not in production for now ( it will be in few weeks ) This machine would be a test platform if there is some beta ontap release that it supposed to support this kind of LDAP authentication. Thanks for any answer. -- Frank Bonnet

2 1

UK User group
by Clawson, Simon 07 Jan '03

07 Jan '03

Hi, We signed up to the UK user group late last year, and I was wondering if anyone has any idea when the next meeting will be? Simon Simon Clawson Mentor Graphics HDL Designer Series R&D Rivergate Systems Administrator London Road Berkshire RG14 2QB TEL: 01635 811409

1 0

Re: a what-if disaster recovery question?
by ScottUCE＠aol.com 07 Jan '03

07 Jan '03

Extra filer heads not only make great swap/failover boxes, but excellent on-site spares kits and test beds as well. As such, many of our customers are dropping NetApp's expensive hardware support on their F700's.........when they suffer a hardware failure, they can swap the failing part immediately; we then ship a replacement part that goes back into their failover filer/spares kit. F720, 740 and 760 filer heads (without licensing) can be purchased for pennies on the dollar :-) Scott Scott Fischmann Union Computer Exchange, Inc. 6233 Idylwood Lane Minneapolis, MN 55436 email: scott(a)unioncomputer.com phone: 952 935 7282 | fax: 952 935 5056 "Helping our customers make each dollar go further -- since 1991!" www.unioncomputer.com > Subj:Re: a what if disaster recovery question? > Date:1/6/2003 4:34:48 PM Central Standard Time > From:<A HREF="mailto:rb@telenor.net">rb(a)telenor.net</A> > To:<A HREF="mailto:DFinn@studentadvantage.com">DFinn(a)studentadvantage.com</A> > CC:<A HREF="mailto:toasters@mathworks.com">toasters(a)mathworks.com</A> > Sent from the Internet > > > > Daniel Finn <DFinn(a)studentadvantage.com> writes: > > > What if we have a failure in one of the heads of our F760s? We have a > spare > > F740 head, would we be able to just put that in place? Is the raid > > information stored on the disk or on firmware in the head? I'm mostly > > wondering what would happen to the data in this situation. > > All relevant raid and firmware information is stored on multiple > disks, so swapping heads is simple and straitforward. > > I have never swapped from a "larger" head to a "smaller" head, but > both heads are Alpha based, and it should work, atleast in theory, as > the HW is is more or less equivilant, but there are HW constraints on > max raw disk capasity, raw file system size, number of FC Host Bus > Adapters etc. These factors may trip an apparent easy swap - though. > > I have, on a couple of occations upgraded from F720 to F740 without > much ado. Only make sure to edit /etc/rc file ahead of shutdown. > > We keep a spare head for our F740s, but since the major load now is on > F8xx (soon to add a FAS960c), we won't keep a spare F740 head on location > anymore - not really important ... > > If disaster recovery is important, I would suggest a 'spare kit' or as > we do, service contract with a local agent with 24h delivery. > > > Also, are shelves swappable between F760s and F740s? > > Definitely yes, with or without disks > > >>>>>>>>>><.rune > > -- > Rune Bakken > Senior System Administrator > Telenor Business Solutions (Nextra), ManagedServices/*/IP-Services > Ph: +47 992 86 474 >

1 0

Re: a what if disaster recovery question?
by Rune Bakken 06 Jan '03

06 Jan '03

Daniel Finn <DFinn(a)studentadvantage.com> writes: > What if we have a failure in one of the heads of our F760s? We have a spare > F740 head, would we be able to just put that in place? Is the raid > information stored on the disk or on firmware in the head? I'm mostly > wondering what would happen to the data in this situation. All relevant raid and firmware information is stored on multiple disks, so swapping heads is simple and straitforward. I have never swapped from a "larger" head to a "smaller" head, but both heads are Alpha based, and it should work, atleast in theory, as the HW is is more or less equivilant, but there are HW constraints on max raw disk capasity, raw file system size, number of FC Host Bus Adapters etc. These factors may trip an apparent easy swap - though. I have, on a couple of occations upgraded from F720 to F740 without much ado. Only make sure to edit /etc/rc file ahead of shutdown. We keep a spare head for our F740s, but since the major load now is on F8xx (soon to add a FAS960c), we won't keep a spare F740 head on location anymore - not really important ... If disaster recovery is important, I would suggest a 'spare kit' or as we do, service contract with a local agent with 24h delivery. > Also, are shelves swappable between F760s and F740s? Definitely yes, with or without disks >>>>>>>>>><.rune -- Rune Bakken Senior System Administrator Telenor Business Solutions (Nextra), ManagedServices/*/IP-Services Ph: +47 992 86 474

1 0

a what if disaster recovery question?
by Daniel Finn 06 Jan '03

06 Jan '03

What if we have a failure in one of the heads of our F760s? We have a spare F740 head, would we be able to just put that in place? Is the raid information stored on the disk or on firmware in the head? I'm mostly wondering what would happen to the data in this situation. Also, are shelves swappable between F760s and F740s? Thanks Dan

2 1

Odd log entry
by Stephen C. Woods 06 Jan '03

06 Jan '03

We're stumped, it appears as though someone issued a disk swap command on one of our filers, however none of us did. NetApp Release 5.1.2R3 on a 540. Is there some other reason that this might occur, disk or SCSI bus glitch? As far as we can tell nothing has changed in the disk farm (syconfig -r matches the weekly email from this week). <scw> Thu Jan 2 10:08:52 PST [disk_config_admin]: *** NOTICE *** A disk has been swapped (removed or added) to a modular storage shelf. The system will wait 15 seconds and then check the status of all disk drives. Thu Jan 2 10:09:26 PST [disk_config_admin]: *** NOTICE *** Disk unit status check has completed. ----- Stephen C. Woods; UCLA SEASnet; 2567 Boelter hall; LA CA 90095; (310)-825-8614 Unless otherwise noted these statements are my own, Not those of the University of California. Internet mail:scw@seas.ucla.edu

3 2

RE: mounting foreign root volume (multiple root volumes) causes p anick
by Chuck Tomasi 06 Jan '03

06 Jan '03

Vol status will tell you which one is the "root" (default boot) volume. To change it use vol options. You can have as many "stand by" root volumes as you like, but it will only boot from the marked "root" under the options column output from vol status. --Chuck -----Original Message----- From: steve(a)hq.newdream.net [mailto:steve@hq.newdream.net] Sent: Friday, January 03, 2003 12:52 PM To: toasters(a)mathworks.com Subject: mounting foreign root volume (multiple root volumes) causes panick Does anyone know if you can mount two (or more) root volumes on one filer and how tell it which on to boot from? I had a filer/shelf with a corrupt vol0. However there was user data on there I wanted to get at. So I mounted it on another test filer whose root volume was named boot, but the filer now complained about having two root volumes (boot and vol0). Thu Jan 2 21:09:00 GMT [fmmbx_instanceWorke:info]: Disk 4.1 is a primary mailbox disk Thu Jan 2 21:09:00 GMT [fmmbx_instanceWorke:info]: Disk 4.0 is a primary mailbox disk Thu Jan 2 21:09:00 GMT [fmmbx_instanceWorke:info]: normal mailbox instance on primary side Thu Jan 2 21:09:01 GMT [raid.assim.tree.multipleRootVols:error]: Volumes vol0 and boot both claim to be the root volume. 2 root volumes found: vol0 boot PANIC: 2 root volumes found, 2 of which are online. in process rc on release NetApp Release 6.3.1 on Thu Jan 2 21:09:02 2003 version: NetApp Release 6.3.1: Wed Nov 20 13:00:54 PST 2002 cc flags: 1 I was trying to boot both as readonly so I could boot off a previous inode on the corrupt vol0. Anyone know if there is a way to specify which volume to boot from when you are mounting multiple root volumes on one filer? I've already gotten the data in another fashion but I thought it should be able to mount two root volumes on one filer. Steve

1 0

mounting foreign root volume (multiple root volumes) causes panick
by steve＠hq.newdream.net 06 Jan '03

06 Jan '03

Does anyone know if you can mount two (or more) root volumes on one filer and how tell it which on to boot from? I had a filer/shelf with a corrupt vol0. However there was user data on there I wanted to get at. So I mounted it on another test filer whose root volume was named boot, but the filer now complained about having two root volumes (boot and vol0). Thu Jan 2 21:09:00 GMT [fmmbx_instanceWorke:info]: Disk 4.1 is a primary mailbox disk Thu Jan 2 21:09:00 GMT [fmmbx_instanceWorke:info]: Disk 4.0 is a primary mailbox disk Thu Jan 2 21:09:00 GMT [fmmbx_instanceWorke:info]: normal mailbox instance on primary side Thu Jan 2 21:09:01 GMT [raid.assim.tree.multipleRootVols:error]: Volumes vol0 and boot both claim to be the root volume. 2 root volumes found: vol0 boot PANIC: 2 root volumes found, 2 of which are online. in process rc on release NetApp Release 6.3.1 on Thu Jan 2 21:09:02 2003 version: NetApp Release 6.3.1: Wed Nov 20 13:00:54 PST 2002 cc flags: 1 I was trying to boot both as readonly so I could boot off a previous inode on the corrupt vol0. Anyone know if there is a way to specify which volume to boot from when you are mounting multiple root volumes on one filer? I've already gotten the data in another fashion but I thought it should be able to mount two root volumes on one filer. Steve

2 1

未承諾広告※出会いチャット！
by cocoa 06 Jan '03

06 Jan '03

MÒRNu \\\\\\\\\\\\\\\ @@@@@@ßÅ·àŠ@PoÅR~I @@@PñÌ[ÌóMÅR~ªáŠ¿á€I @TChrWlXH@ûüH@à€MûÍ[Ü©¹ \\\\\\\\\\\\\\\ ±ÌéæÉQÁó]ÌûÍºLÌ[AhXÉMûÌ[AhXðÔMµÄŸ³¢B @@@@@@momoko_club2003@yahoo.co.jp V é æ ú{ÅåÌ`bg[ªnodmµÜµœBià¿ëñ³¿j lXÈoï¢ðßé Èœ¥ñ²pº³¢B http://www.gg-koukoku.com/index.html [ÌóMðó]µÈ¢ûÍºLÜÅÔMº³¢B me465156(a)members.interq.or.jp Z@@sæâÀ8-19-3 3F sdk@090-1214-7883 RÌ®

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