toasters

toasters@lists.teaparty.net

3 participants
13514 discussions

Start a nNew thread

Re: max aggr size of 16TB
by Bert Kiers 05 Aug '10

05 Aug '10

1 0

RE: Having trouble with VIFs and VLANs
by Steve Losen 05 Aug '10

05 Aug '10

2 2

Having trouble with VIFs and VLANs
by Steve Losen 05 Aug '10

05 Aug '10

We are trying to use best practices for setting up a CF pair of FAS6040s on a VMWARE data network, but are having problems. Nothing on the data network can ping the netapp heads nor can the heads ping each other over the data network. The switch administrator has verified that the switch stack is configured correctly. He says the switch reports that the netapps have not negotiated LACP yet. I want to run by our netapp config commands to verify that I haven't missed any commands or done them in the wrong order. The switch is a stack of two units. One head is supposed to favor one unit and the other head is supposed to favor the other unit. Here are the rc commands. vif create lacp vifb -b ip e0b e6b vif create lacp vifc -b ip e0c e6c vif create single vif0 vifb vifc # favor switch unit 1 vif favor vifb vlan create vif0 201 202 ifconfig vif0-201 192.168.5.6 netmask 255.255.255.0 partner vif0-201 ifconfig vif0-202 192.168.15.6 netmask 255.255.255.0 partner vif0-202 On the other head I have this: vif create lacp vifb -b ip e0b e6b vif create lacp vifc -b ip e0c e6c vif create single vif0 vifb vifc # favor switch unit 2 vif favor vifc vlan create vif0 201 202 ifconfig vif0-201 192.168.5.8 netmask 255.255.255.0 partner vif0-201 ifconfig vif0-202 192.168.15.8 netmask 255.255.255.0 partner vif0-202 We are running ONTAP 7.3.2. Does this look correct? ifconfig -a shows that all the physical interfaces have negotiated auto-1000t-fd-up full duplex ping 192.168.15.8 (from 192.168.15.6) fails and vice versa. To troubleshoot this, I think I will delete all the vifs, create vifc again, and put the VLANs on it and put the IPs on vifc-201 and vifc-202 and see what that gets me. Steve Losen scl(a)virginia.edu phone: 434-924-0640 University of Virginia ITC Unix Support

4 4

Re: Having trouble with VIFs and VLANs
by chaim rieger 05 Aug '10

05 Aug '10

Anybody else getting these spam messages ? Or is it just me

1 0

max aggr size of 16TB
by lists＠up-south.com 04 Aug '10

04 Aug '10

Aside from goin up in ontap version to 8 (currently at 726 and going to 733) and upgrading hardware (currently a 3070) is the 16tb aggr size a hard limit ? Sent via BlackBerry from T-Mobile

7 10

RE: Having trouble with VIFs and VLANs
by Steve Losen 04 Aug '10

04 Aug '10

1 0

Re: Mixing I/O load type in an aggregate
by Page, Jeremy 02 Aug '10

02 Aug '10

I would intentionally mix assuming I can still meet io rrequirements, this generally will help balance since they have seperate io signatures...sequential reads versus small block mixed io etc. Fred Grieco <fredgrieco(a)yahoo.com> wrote: What is the best practice for mixing (or not mixing) different I/O load types in an aggregate? Should I keep similar loads together, or "mix and match" the sets. For instance, I am looking at placing a variety of different data sets on four aggregates. These data sets include sequential backups-to-disk, nfs and cifs file shares, and "QA-dev" luns. Should I keep all the backups on one aggregate, and all the file shares on another? What do you generally do? Are there situations that will adversely affect performance? TIA, Fred Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment.

1 0

Mixing I/O load type in an aggregate
by Fred Grieco 02 Aug '10

02 Aug '10

What is the best practice for mixing (or not mixing) different I/O load types in an aggregate? Should I keep similar loads together, or "mix and match" the sets. For instance, I am looking at placing a variety of different data sets on four aggregates. These data sets include sequential backups-to-disk, nfs and cifs file shares, and "QA-dev" luns. Should I keep all the backups on one aggregate, and all the file shares on another? What do you generally do? Are there situations that will adversely affect performance? TIA, Fred

1 0

Re: max aggr size of 16TB
by Fox, Adam 30 Jul '10

30 Jul '10

The other mode is Clustered ONTAP which is based on the GX (aka Spinnaker) version of ONTAP. It's intended for those running on that platform today. In 8.1, there will be a single ONTAP once again. 8.0 merges the code itself. We expect just about all current 7.x customers to move up to 7-mode and GX customers to move to clustered mode when going to 8.0. As far as migrations to 64-bit aggrs, that will depend but it will have to be logical not physical (no VSM, no vol/aggr copy). The right way will vary on your environment so in general I would recommend customers work with their account team and talk to the migration experts to talk about your specific scenario. It may not make sense to migrate in some cases as you can have both types of aggrs on a system. But even if you don't buy a migration service, talking to those folks can be beneficial. -- Adam Fox ------------------------ Typed with my thumbs on a very small keyboard. ----- Original Message ----- From: Bert Kiers <kiersb(a)xs4all.net> To: Fox, Adam Cc: lists(a)up-south.com <lists(a)up-south.com>; Toasters <toasters(a)mathworks.com> Sent: Fri Jul 30 18:10:42 2010 Subject: Re: max aggr size of 16TB On Fri, Jul 30, 2010 at 05:20:17PM -0400, Fox, Adam wrote: > Not exactly true. 7-mode in ONTAP 8 does have larger than 16T > aggregates, although it is for new aggregates. > How large depends on your model, but it can be as high as 100T out of > the gate with future increases to come in future releases. That is good to hear. But then, what is the difference between 7-mode and native? Any tips on how to migrate? We are thinking about breaking the sync- mirror relation in out FMC, the recreating one aggr on one side, do vol copy, then destroying the other side and reinitialize the sync mirror. The vol copy will however take too long as far as we know now. Now we have several aggr with 2 volumes each, close to 16 TB, with email and we cannot afford more than 1 or 2 hours downtime. Even at 10 GbE (which interfaces we don't have), it will take minimum 4.5 hours that way :( And breaking the mirror makes me nervous. Grtnx, -- Bert Kiers XS4ALL UNIX systeembeheerder, suspected terrorist 1984 was not meant as a manual

1 0

Re: max aggr size of 16TB
by Chaim Rieger 30 Jul '10

30 Jul '10

cant snapmirror from 32 to 64 bit, can snapvault though, i do think that 8.0 is ready for most use cases. thats all

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