toasters April 2003

toasters@lists.teaparty.net

95 participants
102 discussions

CIFSDispatcher Error
by Kumar, Rahul 30 Apr '03

30 Apr '03

Fellow Toasters, On one of the F820, running Ontap 6.3.1R1 we are seeing lots of [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated We have reset the machine account in win2k nativemode domain a few times but it doesn't seem to be helping. This error is not being seen on our 3 other filers Regards Rahul

1 0

i need help making sense of what happened here
by Daniel Finn 29 Apr '03

29 Apr '03

Today a disk failed, but different from what I'm used to seeing. It appears now that I look at it that disk 4.19 failed and it took spare disk 4.38 and began rebuilding on that. What seems strange though is that it kept trying to read or write to disk 4.19 until I physically pulled the disk out. Why would this have happened? na3m-be> sysconfig -v NetApp Release 6.1.2R2: Thu Mar 21 02:30:01 PST 2002 System ID: 0016794273 (na3m-be) slot 0: System Board (NetApp System Board V N4) Tue Apr 29 08:00:00 EDT [kern.uptime.filer:info]: 8:00am up 7 days, 19:27 230387 NFS ops, 537297 CIFS ops, 0 HTTP ops Tue Apr 29 08:56:39 EDT [ispfc_timeout:warning]: 4.19 (0x02000013) (0xfffffc0001778348,0x1c,0/0,4947/0/0,70908/0): command timeout, quiescing drive to allow outstanding I/O to complete. Tue Apr 29 08:56:42 EDT [ispfc_timeout:error]: 4.19 (0x02000013): global device timer timeout, initiating device recovery. Tue Apr 29 08:56:42 EDT [ispfc_timeout:warning]: Resetting device 4.19 (0x02000013) to clear outstanding I/O. Tue Apr 29 08:57:18 EDT [ses_admin:error]: No more valid paths to Enclosure Services in shelf 2 on channel 4. Tue Apr 29 08:57:18 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 08:57:23 EDT [asup.sent.mail:notice]: System Notification mail sent Tue Apr 29 08:58:00 EDT [monitor.globalStatus.critical:CRITICAL]: Disk shelf configuration error. Tue Apr 29 08:59:38 EDT [scsi.cmd.transportError:error]: Device 4.19: Transport error during execution of command: HA status 0x9: cd b 0x4d. Tue Apr 29 08:59:38 EDT last message repeated 7 times Tue Apr 29 09:00:00 EDT [kern.uptime.filer:info]: 9:00am up 7 days, 20:27 230776 NFS ops, 537297 CIFS ops, 0 HTTP ops Tue Apr 29 09:00:00 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 09:00:20 EDT [scsi.cmd.underrun:error]: Device 4.19: Received a data underrun: cdb 0x12. Not all the data was received. Possible transmission error. I/O will be retried. Tue Apr 29 09:00:20 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 09:00:21 EDT [ses_admin:error]: No more valid paths to Enclosure Services in shelf 2 on channel 4. Tue Apr 29 09:00:21 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 09:00:26 EDT [asup.sent.mail:notice]: System Notification mail sent Tue Apr 29 09:01:37 EDT [ispfc_timeout:warning]: 4.19 (0x02000013) (0xfffffc0001773f08,0x1c,0/0,4958/0/4947,72354/5372): command tim eout, quiescing drive to allow outstanding I/O to complete. Tue Apr 29 09:01:40 EDT [ispfc_timeout:error]: 4.19 (0x02000013): global device timer timeout, initiating device recovery. Tue Apr 29 09:01:40 EDT [ispfc_timeout:warning]: Resetting device 4.19 (0x02000013) to clear outstanding I/O. Tue Apr 29 09:02:24 EDT [scsi.cmd.underrun:error]: Device 4.19: Received a data underrun: cdb 0x12. Not all the data was received. Possible transmission error. I/O will be retried. Tue Apr 29 09:02:25 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 09:02:25 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x1d: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:02:25 EDT last message repeated 3 times Tue Apr 29 09:02:25 EDT [ses_admin:error]: Enclosure control failed via 4.19 (shelf 2), searching for alternate path Tue Apr 29 09:02:25 EDT [ses_admin:error]: No more valid paths to Enclosure Services in shelf 2 on channel 4. Tue Apr 29 09:02:25 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 09:02:26 EDT [asup.sent.mail:notice]: System Notification mail sent Tue Apr 29 09:02:55 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 09:02:56 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x1d: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:02:56 EDT last message repeated 3 times Tue Apr 29 09:02:56 EDT [ses_admin:error]: Enclosure control failed via 4.19 (shelf 2), searching for alternate path Tue Apr 29 09:02:56 EDT [ses_admin:error]: No more valid paths to Enclosure Services in shelf 2 on channel 4. Tue Apr 29 09:02:56 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 09:02:56 EDT [asup.sent.mail:notice]: System Notification mail sent Tue Apr 29 09:03:12 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 09:03:12 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x1d: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:03:12 EDT last message repeated 3 times Tue Apr 29 09:03:12 EDT [ses_admin:error]: Enclosure control failed via 4.19 (shelf 2), searching for alternate path Tue Apr 29 09:03:12 EDT [ses_admin:error]: No more valid paths to Enclosure Services in shelf 2 on channel 4. Tue Apr 29 09:03:12 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 09:03:13 EDT [asup.sent.mail:notice]: System Notification mail sent Tue Apr 29 09:03:29 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 09:03:29 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x1d: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:03:29 EDT last message repeated 3 times Tue Apr 29 09:03:29 EDT [ses_admin:error]: Enclosure control failed via 4.19 (shelf 2), searching for alternate path Tue Apr 29 09:03:29 EDT [ses_admin:error]: No more valid paths to Enclosure Services in shelf 2 on channel 4. Tue Apr 29 09:03:29 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 09:03:29 EDT [asup.sendError.throttled:info]: Too many autosupport messages in too short a time: throttling CONFIGURATION _ERROR!!! mail. Tue Apr 29 09:03:50 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 09:03:50 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x1d: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:03:50 EDT last message repeated 3 times Tue Apr 29 09:03:50 EDT [ses_admin:error]: Enclosure control failed via 4.19 (shelf 2), searching for alternate path Tue Apr 29 09:03:50 EDT [ses_admin:error]: No more valid paths to Enclosure Services in shelf 2 on channel 4. Tue Apr 29 09:03:50 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 09:03:50 EDT [asup.sendError.throttled:info]: Too many autosupport messages in too short a time: throttling CONFIGURATION _ERROR!!! mail. Tue Apr 29 09:04:06 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 09:04:07 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x1d: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:04:07 EDT last message repeated 3 times Tue Apr 29 09:04:07 EDT [ses_admin:error]: Enclosure control failed via 4.19 (shelf 2), searching for alternate path Tue Apr 29 09:04:07 EDT [ses_admin:error]: No more valid paths to Enclosure Services in shelf 2 on channel 4. Tue Apr 29 09:04:07 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 09:04:07 EDT [asup.sendError.throttled:info]: Too many autosupport messages in too short a time: throttling CONFIGURATION _ERROR!!! mail. Tue Apr 29 09:04:25 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 09:04:25 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x1d: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:04:25 EDT last message repeated 3 times Tue Apr 29 09:04:25 EDT [ses_admin:error]: Enclosure control failed via 4.19 (shelf 2), searching for alternate path Tue Apr 29 09:04:25 EDT [ses_admin:error]: No more valid paths to Enclosure Services in shelf 2 on channel 4. Tue Apr 29 09:04:25 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 09:04:25 EDT [asup.sendError.throttled:info]: Too many autosupport messages in too short a time: throttling CONFIGURATION _ERROR!!! mail. Tue Apr 29 09:04:44 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 09:04:44 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x1d: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:04:44 EDT last message repeated 3 times Tue Apr 29 09:04:44 EDT [ses_admin:error]: Enclosure control failed via 4.19 (shelf 2), searching for alternate path Tue Apr 29 09:04:44 EDT [ses_admin:error]: No more valid paths to Enclosure Services in shelf 2 on channel 4. Tue Apr 29 09:04:44 EDT [monitor.shelf.configError:CRITICAL]: Configuration error on disk storage shelf attached to slot 4. Please c heck drive placement. Tue Apr 29 09:04:44 EDT [asup.sendError.throttled:info]: Too many autosupport messages in too short a time: throttling CONFIGURATION _ERROR!!! mail. Tue Apr 29 09:05:00 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x28:00cc2f18:0008: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:05:00 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x28:00cc2ff8:0008: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:05:00 EDT [raid.diskFailed:CRITICAL]: Read on data disk 4.19 in volume vol1, RAID group 1, failed; reverting to degrad ed mode. Tue Apr 29 09:05:00 EDT [raid_admin:CRITICAL]: Label write on 4.19 (S/N LKJ781640000101937T4) failed. Tue Apr 29 09:05:00 EDT [raid_admin:CRITICAL]: Label write on 4.19 (S/N LKJ781640000101937T4) failed. Tue Apr 29 09:05:02 EDT [raid_admin:CRITICAL]: Read on data disk 4.19 in volume vol1, RAID group 1, failed; entered degraded mode. Tue Apr 29 09:05:02 EDT [raid_admin:notice]: One disk is missing from volume vol1, RAID group 1. A "hot spare" disk (4.38) is available and the missing disk will be reconstructed on the spare disk. Tue Apr 29 09:05:02 EDT [dyn_dev_qual_admin:info]: Successfully updated /etc/.broken_disks file on local FS for disk 4.19 SEAGATE S T118202FC LKJ781640000101937T4 Tue Apr 29 09:05:02 EDT [asup.sent.mail:notice]: System Notification mail sent Tue Apr 29 09:05:03 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 09:05:03 EDT [scsi.cmd.checkCondition:error]: Device 4.19: Check Condition: CDB 0x1d: Sense Data not ready - (0x2 - 0x4 0x0 0x2). Tue Apr 29 09:05:03 EDT last message repeated 3 times ^ The following continued to be reported to the log file until I physically pulled the drive and replaced it with a spare. The log file continues below: Tue Apr 29 10:12:54 EDT [ispfc_timeout:warning]: Resetting Fibre Channel adapter 4. Tue Apr 29 10:13:00 EDT [scsi.cmd.selectionTimeout:error]: Device 4.19: Adapter/target error: HA status 0x7: cdb 0x12. Targeted dev ice did not respond to requested I/O. I/O will be retried. Tue Apr 29 10:13:00 EDT [scsi.cmd.noMorePaths:error]: Device 4.19: No more paths to device: cdb 0x12. All retries have failed. Tue Apr 29 10:13:17 EDT [ispfc_timeout:warning]: 4.19 (0x02000013) (0xfffffc0001779998,0x12,0/0,1/0/0,98110/0): command timeout, qui escing drive to allow outstanding I/O to complete. Tue Apr 29 10:13:27 EDT [monitor.shelf.configError.ok:CRITICAL]: Configuration error previously reported on disk storage shelf attac hed to slot 4 has been corrected. Tue Apr 29 10:13:30 EDT [dyn_dev_qual_admin:info]: Now downloading firmware file /etc/disk_fw/ST118202FC.NA27.LOD on 1 disk ... Tue Apr 29 10:14:00 EDT [monitor.globalStatus.nonCritical:warning]: Disk on adapter 4, shelf 2, bay 3, failed. Tue Apr 29 10:15:00 EDT [dyn_dev_qual_admin:info]: Firmware downloaded on disk 4.19 Tue Apr 29 10:15:00 EDT [dyn_dev_qual_admin:info]: Media Access test successful on disk 4.19 Tue Apr 29 10:15:00 EDT [dyn_dev_qual_admin:info]: Firmware is up-to-date on all disk drives Tue Apr 29 10:15:00 EDT [raid_disk_admin:notice]: Disk 4.19 (S/N LKH21431000020030EDP) has been added to incomplete volume vol1(1). Tue Apr 29 10:15:00 EDT [monitor.globalStatus.ok:info]: The system's global status is normal. Tue Apr 29 11:00:00 EDT [kern.uptime.filer:info]: 11:00am up 7 days, 22:27 233428 NFS ops, 537525 CIFS ops, 0 HTTP ops Tue Apr 29 11:23:21 EDT [consumer:notice]: Reconstruction of data disk in volume vol1, RAID group 1, complete. Tue Apr 29 11:23:21 EDT [download.update:info]: Begin bootblock update, prototype is 4.8 Tue Apr 29 11:23:29 EDT [download.updateDone:info]: Bootblock update completed Thanks Dan

2 1

Re: 2 telnet sessions
by Dirk Schmiedt 26 Apr '03

26 Apr '03

Sorry, if you get this email twice. My provider T-Online changed their policy of sending emails with a non-t-online from: field in april 2003. They told me the emails would be delivered, but ... :-( So here's the mail again: Dirk Schmiedt wrote: > Jeff Burton wrote: > >> If you are on Unix you can use the below very simple script to simulate >> a command line from as many machines as you want. > > .... > Simple but neat. :-) > >> Until you are comfortable with this script I would NEVER run "dangerous" >> commands like 'halt', 'ifconig e0 down', ... It should work fine, but >> use at your own risk. >> > 100% confirmation. > > rsh filer license > >> license not found. Type '?' for a list of commands > > > Try: > > rsh filer "priv set -q advanced ; license " > > If someone don't know about this "advanced" mode., then you should not > use it. Go to the advanced ONTAP NetApp training first, please. > If you know about the semantic content, you might like this > suggestion. :-) > > Smile & regards > Dirk >

1 0

ISCSI
by Steven Boyer GD mail deployed 26 Apr '03

26 Apr '03

Anybody using ISCSI if so in what capacity, and what kind of I/O are you seeing. I am particularly interested in ISCSI to tape libraries. Thanks Steven

1 0

Crossovers cable to NetApp
by Robert Borowicz 25 Apr '03

25 Apr '03

Does anybody do a direct connect from a Sun or whatever to the NetApp via a crossover 100Bt cable? If so what considerations did you make when ifconfig'ing the Sun? Did you use static routes? TIA -Rob --- Robert K. Borowicz Mgr. Infrastructure Support Railroad Commission ITS O: 512-936-2401 C: 512-576-2300

2 1

Looking for 220V powers for Shelf...
by John Enger 25 Apr '03

25 Apr '03

I am looking for 2 powermodules for Netapp-shelf (FC6?). The powers I have are 110V, and thus unusable here in Norway. The part code of my 110V powermodules are XLPSU-NA1. I need the 220V version. Does anyone have any spares? This is for home-experimentation, and I do not wish to pay like 2-300 $ for each power... Can anyone help? John Enger

2 1

(no subject)
by John Enger 25 Apr '03

25 Apr '03

1 0

RE: Duplicating filers
by Waters, G Scott DSTI 25 Apr '03

25 Apr '03

Why not just look at clustering the two filers?? ... or am I missing something? - Scott W. -----Original Message----- From: Hunter Wylie [mailto:hwylie@stpaultel.com] Sent: Thursday, April 24, 2003 2:36 PM To: 'Michael Homa'; toasters(a)mathworks.com Subject: RE: Duplicating filers Michael, In theory it might work on a "perfect" day "but" the number and type of simple failure scenarios would make the perfect day highly improbable. I suggest you take a simpler approach that many of my very large customers use to achieve very high availability, very short mean time to repair, simplicity and low cost. Buy a used F740 (head) configured like the biggest one you have, a spare 36 and 18 GB disk and a FC9 disk shelf. When something breaks and you have an idea it's "head associated - down the dying F740 and power it off, unhook LAN connections, FC disk cable, etc. and attach them to the spare F740 racked between the original two heads. Cable lengths can get you if you are not careful. Watch your power load on the rack/circuit. If it is shelf associated, shut down the system, power it down, remove the old shelf cable and attach the new one, move all the drives and power up. In both cases the system will comeback on line with all the old identities re-established, no DNS hacks. This technique is used by one of the largest on-line retailers in the world. They love it. No software licenses are needed on the spare system as long as it is "NEVER" used in parallel production with the two other systems. In this mode it is strictly a replacement spare part. If you want to use it in any other mode you must acquire software licenses with it. The nice thing about this solution is it is simple to test. Send me an email if you want to figure out the exact parts you will need. Hunter M. Wylie 21193 French Prairie Rd St. Paul, Oregon 97137 Bus: 503-633-8900 FAX: 503-633-8901 Cell: 503-880-1947 http://www.itmls.com/ -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Michael Homa Sent: Thursday, April 24, 2003 10:24 AM To: toasters(a)mathworks.com Subject: Duplicating filers Hi. My name is Michael Homa and I'm a member of the Systems Group at the University of Illinois at Chicago. Some background --------------- We have two F740 filers: netapp1 and netapp2. o Both of them are at ONTAP 6.2.1. o Each has a different admin host. o Both have two FC9 data shelves. On netapp1, one shelf contains 18GB drives; the other shelf, 36GB drives. On netapp2, both shelves have 36GB drives. o Netapp1 has one volume, vol0, and two raid groups, rg0 and rg1. o Netapp2 has two volumes, volboot and vol0, and each volume has a single raid group, rg0. Netapp1 is the "center of our universe" and is NFS-mounted to almost all of our production servers. Netapp2 currently functions solely as the recipient of the snapmirroring of netapp1. I've been asked to undertake a project in which I make netapp2 be a duplicate of netapp1. In the event that netapp1 becomes unavailable (maybe a catastrophic hardware failure), we want to re-cable netapp2 to the network, monkey with DNS, and reboot the box. In effect, for all intents and purposes, make it netapp1. It's a good idea in theory but maybe in practice it won't work out. Nope. Now that I think about it, it doesn't even sound like a good idea in theory but my boss has asked me to try it so what the heck. Has anyone attempted this? I'm looking for suggestions, ideas, "gotchas." I don't need to reinvent the wheel; I'm more than willing to learn (borrow, steal) from others. Thanks. Michael Homa Academic Computing and Communication Center University of Illinois at Chicago email: mhoma(a)uic.edu

4 3

RE: FC9 & DS14 on same FC-AL adapter...
by Waters, G Scott (DSTI) 25 Apr '03

25 Apr '03

I am curious about the 56 disk rule. To what does it apply. I ask that because I currently have a filer with 63 disk in one loop and no *known* problems. Please enlighten me. Thanks. - Scott W. -----Original Message----- From: Clawson, Simon [mailto:simon_clawson@mentorg.com] Sent: Wednesday, April 16, 2003 11:26 AM To: 'jeff.mery(a)ni.com'; toasters(a)mathworks.com Subject: RE: FC9 & DS14 on same FC-AL adapter... Yes. We have FC7, FC9 and DS14 on the same loop. The rules are - the shelves must be linked in order of oldest to newest - FC7 -> FC9 -> DS14. You cannot have more than 56 disks on one loop. Simon -----Original Message----- From: jeff.mery(a)ni.com [mailto:jeff.mery@ni.com] Sent: 16 April 2003 16:16 To: toasters(a)mathworks.com Subject: FC9 & DS14 on same FC-AL adapter... Fellow Toasters, Does anyone know if FC9 and DS14 shelves can co-exist on the same FC-AL adapter? If so, are there any special rules that must be followed (i.e. DS14s at beginning/end/certain shelf IDs etc.)? Thanks in advance, Jeff Mery, MCP National Instruments ------------------------------------------------------------------------ - "Allow me to extol the virtues of the Net Fairy, and of all the fantastic dorks that make the nice packets go from here to there. Amen." TB - Penny Arcade ------------------------------------------------------------------------ -

2 1

Duplicating filers
by Michael Homa 25 Apr '03

25 Apr '03

Hi. My name is Michael Homa and I'm a member of the Systems Group at the University of Illinois at Chicago. Some background --------------- We have two F740 filers: netapp1 and netapp2. o Both of them are at ONTAP 6.2.1. o Each has a different admin host. o Both have two FC9 data shelves. On netapp1, one shelf contains 18GB drives; the other shelf, 36GB drives. On netapp2, both shelves have 36GB drives. o Netapp1 has one volume, vol0, and two raid groups, rg0 and rg1. o Netapp2 has two volumes, volboot and vol0, and each volume has a single raid group, rg0. Netapp1 is the "center of our universe" and is NFS-mounted to almost all of our production servers. Netapp2 currently functions solely as the recipient of the snapmirroring of netapp1. I've been asked to undertake a project in which I make netapp2 be a duplicate of netapp1. In the event that netapp1 becomes unavailable (maybe a catastrophic hardware failure), we want to re-cable netapp2 to the network, monkey with DNS, and reboot the box. In effect, for all intents and purposes, make it netapp1. It's a good idea in theory but maybe in practice it won't work out. Nope. Now that I think about it, it doesn't even sound like a good idea in theory but my boss has asked me to try it so what the heck. Has anyone attempted this? I'm looking for suggestions, ideas, "gotchas." I don't need to reinvent the wheel; I'm more than willing to learn (borrow, steal) from others. Thanks. Michael Homa Academic Computing and Communication Center University of Illinois at Chicago email: mhoma(a)uic.edu

3 2

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 April 2003