toasters May 2007

toasters@lists.teaparty.net

64 participants
41 discussions

RE: Removing shelves from FAS940
by Learmonth, Peter 08 May '07

08 May '07

Hi Paul Just halt and unplug the shelves. If there are other shelves (mk2 with LRC?) on the loop, make sure they are terminated. When it reboots, as long as all disks from any vols/aggrs on those shelves are gone, the assimilation process will be happy. If even one disk is still present it will complain of broken vols/aggrs, but otherwise function just fine. It sounds like you don't have any exports, shares, LUNs on those shelves, so all you have to do is migrate the root vol. You can use ndmpcopy for that. I typically name the new root vol "root" and leave it that way. ndmpd on ndmpcopy /etc /vol/root/etc (going from memory, but I think you need to specify the destination directory. Play with it...) Don't forget vol options root root Enjoy Peter Share and Enjoy! Peter ... Sent from one of those phone+email doohicky things... I reserve the right to be wrong. -----Original Message----- From: Paul Letta [mailto:letta@jlab.org] Sent: Tuesday, May 08, 2007 07:07 AM Pacific Standard Time To: toasters(a)mathworks.com Subject: Removing shelves from FAS940 Hello, I have a FAS940 (7.1.1.1) that has multiple shelves. I want to remove 4 of the older shelves to take them out of service. These 4 shelves contain /vol/vol0, which is the root vol. My plan is: 1) move the root vol to another volume 2) reboot filer off of the new root volume. 3) Halt filer 4) Remove the 4 old shelves (all remaining shelves are DS14Mk2's) 5) boot filer Do I need to do anything before I halt the filer (like vol offline, vol destroy) ? What will the filer do when it boots up the second time and is now missing the 4 shelves ? The /etc directory is really the only data that is in use on these old shelves now, so a destroy is ok, but the cautious side of me would rather save old /vol/vol0 on these shelves -- just in case. I have searched for this answer, and even opened a support case, but I've only found "probably" type answers. Thanks ! Paul

1 0

Removing shelves from FAS940
by Paul Letta 08 May '07

08 May '07

Hello, I have a FAS940 (7.1.1.1) that has multiple shelves. I want to remove 4 of the older shelves to take them out of service. These 4 shelves contain /vol/vol0, which is the root vol. My plan is: 1) move the root vol to another volume 2) reboot filer off of the new root volume. 3) Halt filer 4) Remove the 4 old shelves (all remaining shelves are DS14Mk2's) 5) boot filer Do I need to do anything before I halt the filer (like vol offline, vol destroy) ? What will the filer do when it boots up the second time and is now missing the 4 shelves ? The /etc directory is really the only data that is in use on these old shelves now, so a destroy is ok, but the cautious side of me would rather save old /vol/vol0 on these shelves -- just in case. I have searched for this answer, and even opened a support case, but I've only found "probably" type answers. Thanks ! Paul

2 1

The simulator and vmware esx
by James Beal 07 May '07

07 May '07

I sent this from my un-subscribed work address so if we get two copies apologies. I have been banging my head against the traditional problem with the simulator and not being able to see the network. Its interesting to discover that esx has an option (Security) under each network "vswitch". The security tab has a policy exceptions area. There is an option for Promiscuous mode, the simulator doesn't talk to the network by default, you need to allow promiscuous mode access to the virtual switch. Once you know the option is there in esx its obvious how it should be set I just didn't know it existed. I haven't seen this recorded as a solution to the problem yet and thought people may be interested. james

4 3

Re: Solaris Oracle NFS mount options
by Adloori, Shanthi 07 May '07

07 May '07

Hi Carl, The TR-3322 that you mentioned in your email is a great start and has basic fundamentals of NFS protocol but it is rather an outdated one. For the current and latest mount options recommendations, please refer to the following URLs - these options are well tested and have been validated with Oracle. NetApp Database Portal FAQ available from the NOW site: http://now.netapp.com/NOW/knowledge/docs/bpg/db/oracle_faq.shtml NOW site (recommended mount options): http://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb7518 Oracle Metalink: metalink doc for mount options: -- note 359515.1 https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_ database_id=NOT&p_id=359515.1 Regarding protocol performance comparison - please check out: TR-3496: ORACLE 10g PERFORMANCE - PROTOCOL COMPARISON ON SUN SOLARIS http://www.netapp.com/library/tr/3496.pdf Regarding more information on forcedirectio or llock on Solaris - please refer to: http://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb6570 According to our experts: You should use DirectIO for the REDO Logs as it reduces CPU overhead on the host. There is no benefit by using llock and caching REDO Log IO. Bypassing the FS cache for REDO traffic is a good thing, especially for high SPARC CPU count systems and any AMD based systems even as of Solaris 10 U2. It has to do with CPU DTLB tear downs, etc. Using llock in addition to forcedirectio does not gain anything on Solaris, thus it's EITHER-OR. We are also in the process of merging the content of TR-3322 with TR-3496 and we will remove TR-3322 from the web to avoid any further confusion. Please let us know if you have any questions. Thanks, Shanthi Adloori Sr. Manager, Oracle Alliance Engineering 408.822.7828 | Network Appliance | shanthi(a)netapp.com ------------------------------------------------------------------------ -------- From: Sto Rage(c) [mailto:netbacker@gmail.com] Sent: Wednesday, May 02, 2007 11:31 AM To: Carl Howell Cc: toasters(a)mathworks.com Subject: Re: Solaris Oracle NFS mount options Yeah, the Netapp documents are not consistent. This is what we have for our oracle mounts: nfs 2 yes rw,bg,vers=3,proto=tcp,hard,intr,rsize=32768,wsize=32768,forcedirectio,l lock <<--- For all data files, redo logs and arch log volumes. and no forceddirectio for the Oracle binaries volume nfs 2 yes rw,bg,vers=3,proto=tcp,hard,intr,rsize=32768,wsize=32768,llock Is this correct? It seems to be working OK for us now, we are yet to go into production though, its only a few developers working on the database. BTW, we are on Solaris 10. -G On 5/2/07, Carl Howell <chowell(a)uwf.edu> wrote: In TR-3322 it says that the mount point for the redo logs should have the forcedirectio option on and the mount point for the data files should have it off. KB7518, which appears to be more recent, doesn't say anything about mount options for redo log volumes, but I assume you should have either forcedirectio or llock on both the mount points for your redo logs and data files. Is this correct? Thanks, - Carl

4 3

Moving vfiler inside filer
by JacekN 06 May '07

06 May '07

IHAC who has NetApp filer with mixed disks: FC and SATA. He initially configured many vfilers (aka MultiStore) on SATA drives (using FlexVols) but now decided to move vfilers from SATA to FC aggregates. The problem is to minimize downtime (each vfiler has several huge data volumes). vfiler migrate could be a good (although not perfect) solution but it has to be performed between distinct filers (volume names must match). I am considering the following scenario: - create new vfiler - create corresponding volumes - make baseline SnapMirror transfer (I tried ndmpcopy but it does not fit to the solution) - unmount clients - close shares/exports on the moved volume - make incremental SnapMirror transfer - recreate shares - remount clients - repeat above steps for next volumes I do not like this solution because: - it requires SnapMirror license (VolCopy requires extreme long downtime, ndmpcopy is file level incremental and does not synchronize removed files/dirs), - it requires significant amount of work on client side (new server, new export name). Any better ideas will be appreciated! Best regards, Jacek Nogala --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 000738-3, 2007-05-05 Tested on: 2007-05-06 20:38:57 avast! - copyright (c) 1988-2007 ALWIL Software. http://www.avast.com

1 0

RE: Esx RDM mappings
by Asbjørn Bjørkelund 04 May '07

04 May '07

Hello, It's in a different datastore. Asbjorn -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Davies,Matt Sent: 4. mai 2007 13:11 To: Asbjorn Bjorkelund; toasters(a)mathworks.com Subject: RE: Esx RDM mappings Hi, Are you storing the mappings with the RDM or in a separate datastore ? Thanks Matt -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Asbjorn Bjorkelund Sent: 04 May 2007 11:04 To: toasters(a)mathworks.com Subject: Esx RDM mappings Hello we have experienced problems with raw device mappings. Several times has the RDM metafiles been corrupt, and vm's have not been able to boot until we recreate the metafile. One time this happened the filer had an uncontrolled shutdown, and later on when we tried to reboot the vm's they couldn't find their LUN's, and we had to recreate the mapping file to be able to boot them. Environment: ESX 2.5.2 HP Proliant DL385 with Emulex HBA FAS3020 OnTap 7.2.2 Is there anyone who has experienced similar problems with RDM mappings? Regards Asbjorn -- View this message in context: http://www.nabble.com/Esx-RDM-mappings-tf3691225.html#a10319989 Sent from the Network Appliance - Toasters mailing list archive at Nabble.com. _____________________________________________________________ This e-mail (including all attachments) is confidential and may be privileged. It is for the exclusive use of the addressee only. If you are not the addressee, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately at help(a)generalatlantic.com <mailto:help@generalatlantic.com>. Thank You.

2 1

Esx RDM mappings
by Asbjorn Bjorkelund 04 May '07

04 May '07

Hello we have experienced problems with raw device mappings. Several times has the RDM metafiles been corrupt, and vm's have not been able to boot until we recreate the metafile. One time this happened the filer had an uncontrolled shutdown, and later on when we tried to reboot the vm's they couldn't find their LUN's, and we had to recreate the mapping file to be able to boot them. Environment: ESX 2.5.2 HP Proliant DL385 with Emulex HBA FAS3020 OnTap 7.2.2 Is there anyone who has experienced similar problems with RDM mappings? Regards Asbjorn -- View this message in context: http://www.nabble.com/Esx-RDM-mappings-tf3691225.html#a10319989 Sent from the Network Appliance - Toasters mailing list archive at Nabble.com.

2 1

battery F87
by Phil Hill 04 May '07

04 May '07

Hi all, does anybody know, were to buy NVRAM-Batteries for F87? I can't find the parts anywhere. Following infos are on our broken battery: P/N:271-01848 ES-3059 Model: 340848 PSC510000 E0150C thanks in advance Phil

2 1

RE: Capacity FAS960 with mixed configutaion FC & Sata disk
by Sels Roger 04 May '07

04 May '07

Hi, I thought the max supported TB's in a configuration is software based. In that regard, you can mixed "any shelf" with "any shelf" until you reach the software limit. In my opinion the limitation is not based on the number and type of shelfs. Cheers, Roger -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Zalam Sudisno Sent: vr 04 mei 07 4:03 To: toasters(a)mathworks.com Subject: Capacity FAS960 with mixed configutaion FC & Sata disk Dear all, Now we have FAS960 with uses mixed configuration disk, 4 Shelves FC disk X 14 X 144GB, and another loop we have 2 Shelves SATA disk X 14 X 250GB. we don't have remaining Expantion slot again ( all expantion slot we are already uses) if we are check from FAS calculator Max Capacity for FAS960 with 144 Gb FC disk up to 12 Shelves, with 300 Gb FC disk up to 6 Shelves with 250 GB disk ATA up to 8 Shelves with 500 Gb disk ATA up to 4 Shelves But we not clear with Max capacity on mixed configuration disk. My question is : 1. How many Shelves we can add with FC disk 144Gb or 300GB ? 2. How many Shelves we can add with SATA disk 250 or 500Gb ? Thanks & Regards D I S N O PT. Mandawani Mandiri.

1 0

Not explicitly NetApp, but this seems like the right crowd to ask: Linux (RHEL4.4), iSCSI & NetApp connectivity problems...
by Demaagd, Dave 04 May '07

04 May '07

Some information on the physical layout: 3 subnets in question - a general server VLAN, a '3rd party developer' server VLAN that is heavily firewalled off from everything else, a dedicated unmanaged switch LAN that is intended to segregate iSCSI traffic from the rest of the network. The first two run on the same switch fabric. 4 initiators in question - All RHEL4.4, all current packages and errata applied, all have confirmed connectivity (ping and telnet to port 3260). The NetApp is an IBM N5200 (rebadged NetApp 3020) running DOT 7.1. Interface layout looks like this: e0a is connected to the general server VLAN, e0b is connected to the iSCSI LAN, e0c and e0d are used as crossover cable connections (which I am trying to eliminate by implementing the iSCSI LAN). The e0a interface has iSCSI targeting disabled, it is enabled (the default setting) on b c and d. HostA - on the 3rd party VLAN (eth0) and the iSCSI LAN (eth1) HostB - on the general server VLAN (eth0) and the iSCSI LAN (eth1) HostC - on the general server VLAN (eth0) and connected to the NetApp via a crossover (eth1) NetApp - on the general server VLAN, the iSCSI LAN, and using 2 ports for crossover (interface layout given above) The story/problem (as I see it): Was trying to hook HostA up to the NetApp to get some extra disk space for it. Software installed clean, no special settings - just set the DiscoveryAddress to the NetApp iSCSI LAN address in iscsi.conf, set the initiator name, mapped the initiator name/group to a LUN, and figured that would be it (that config worked great with the crossover connections). Fired up the daemon, saw the connection on both ends, iscsi-ls shows the LUN on the initiator. But, if I try to do anything that actially looks at it from a device level (fdisk -l, cat /proc/scsi/scsi, etc), I get a mess of 'ping timeout, failed command, session dropped, session established' loops before it finally gives up a few minutes later (usually gives up, sometimes it locks so hard I may as well reboot the box). After messing with additional parameters that looked promising (particularly the PingTimeout option) in iscsi.conf without success, I came up with the hypothesis that maybe there was some strange interaction because the primary network interface for this machine is on is heavily firewalled (no outbound, period; only inbound is on port 80 and 22). To test this hypothesis, I set up HostB, identical packages/network layout as HostA, and it worked great. Figured that kinda added weight to my hypothesis above. Would deal with that later, I was happy. The problem came in last night when I attempted to change HostC from the crossover connection to the iSCSI LAN. Stopped services, unmounted drives, changes network and iSCSI parameters, started things back up again. Lo and behold, the same thing that happened to HostA was happening to HostC. Fortunately, was able to roll this back very easily, so nobody but myself was irritated. Been searching around today to see if I can find information about similar problems on the web, found a couple things that didn't help (but were interesting reading, and I did manage to get some performance boosts out of them), and I thought it was time that I should ask someone who might have experience in this kind of thing before I pull out too much hair. I really hope that this is something simple that I'm overlooking. Log files/packet traces/general details available if needed (don't want to spam too many people with info that may not be applicable)... -- Dave DeMaagd, DOL QA Engineering dave.demaagd(a)dig.com | (818) 623-3755 | (818) 262-7958

1 0

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 May 2007