toasters February 2015

toasters@lists.teaparty.net

34 participants
28 discussions

8.2.x on a 2240 or 3240?
by Philbert Rupkins 18 Feb '15

18 Feb '15

Hello Toasters, Just curious if anybody is running an ONTAP 8.2.x 7-mode release on a 2240, 3240 or comparable unit? If so, was there a noticeable increase in cpu utilization and/or client response time following the upgrade to 8.2.x? We are currently evaluating an 8.2.3 7-mode upgrade from 8.1.3. On 8.1.3, we do see periods in which average processor utilization is in the 80-90% range. We're told we may want to avoid upgrading those units to an 8.2 release as 8.2 requires an additional 10-20% cpu out of the gate. Thanks, Phil

4 5

IOPs from a controller
by Edward Rolison 14 Feb '15

14 Feb '15

Does anyone have a very rough rule of thumb as to IOPs you might expect out of a controller? I've got a FAS6280 that's starting to 'be a bit sluggish'. I'm inclined to shrug and say 'yes, it's doing 20K IOPs'. I know there's very much an 'it depends' in there - but 'very rough' is good enough for me here. (Disk wise - it's not particularly high on disk utilisation, nor is the network bandwidth particularly full).

7 9

Unstable cluster (or actually interconnects)
by Karsten Meinster 13 Feb '15

13 Feb '15

Hi all, We got some major issue's with our interconnects (or maybe ISL's at this moment I have no idea), some background first: We have a 3160 MC running Ontap 8.0.2 running stable for the last 3 years, however we are in the middle of upgrading to ontap 8.2 and for that we need to upgrade the FOS's to a higher version (we came from 6.3 and we want/need to go to 7). After we upgraded the first fabric to 7.0.0b everything seemed to work fine, however later on the day we saw a lot of errors on the netapps and on the switches, by then we changed some settings that helped us in the past for these errors (port based routing instead of exchange based which would actually be the best practice following the guides) and we started upgrading the second fabric to the intermediate FOS (6.4.2) and then immediately saw the errors coming up again at which time we stopped upgrading to 7.0.0. So long story short, we now have 2 fabrics, 1 running at 7.0.0b and one at 6.4.2b, which obviously is not recommended but we can't do much at the moment since things are extremely unstable connection wise. The switches themselves are set up by the best practice PDF that was available at that time, but even with the settings that changed in the meantime (basically only the portcfgfillword and I think the IOD and DLS options) we don't see any improvements, below some snippets of the log files, the data in the snippets are continuously popping up in our logfiles. The fabrics have a single ISL (so yeah data and CI data goes through the same ISL) and we have the old DS14 ESH4 shelfs. The weird thing is this really only happened after the FOS upgrade, we monitor all our devices quiet heavily and we haven't seen these kind of errors in the past, both the netapp errors as well as the switch errors(brocade by the way, well yeah FOS :)). At this time we're kind of clueless, Netapp support doesn't tell us much either we didn't get much further than asking for lots of log files and reseating SFP's which don't seem to work and we are still waiting (and calling) for the log analysis's. Sorry in advance for the weird buildup of this mail but we're making some long days at the moment ;-) If any more info might be helpfull I can send it ;-) (but don't want to flood the list right now). Thanks! Karsten Porterrshow on one of the switches (all switches give the same type of results, port 0 = FCVI, port 4 = ISL: nodes01witch10:root> porterrshow frames enc crc crc too too bad enc disc link loss loss frjt fbsy c3timeout tx rx in err g_eof shrt long eof out c3 fail sync sig tx rx ======================================================================================================================= 0: 16.5m 29.8m 0 0 0 0 0 0 90 0 4 4 4 0 0 0 0 1: 44.9m 22.9m 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2: 47.9m 22.3m 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4: 50.8m 59.2m 26 24 22 0 0 2 26 0 0 0 0 0 0 0 0 5: 14.2m 25.2m 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6: 14.7m 30.3m 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 7: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 9: 4.5m 3.4m 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 10: 861.6k 1.1m 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 12: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 13: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 14: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 15: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 16: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 17: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 18: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 19: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 20: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 21: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 22: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 23: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 nodes01witch10:root> node01*> Fri Feb 13 01:37:28 CET [node01: cf.fsm.takeoverByPartnerDisabled:notice]: Failover monitor: takeover of node01 by node02 disabled (unsynchronized log). Fri Feb 13 01:38:53 CET [node01: scsi.cmd.transportErrorEMSOnly:debug]: Disk device eetrsansw10:10.28: Transport error during execution of command: HA status 0x9: cdb 0x28:12a6c7b0:0060. Fri Feb 13 01:39:33 CET [node01: cf.nm.nicTransitionDown:warning]: Cluster Interconnect link 0 is DOWN Fri Feb 13 01:39:53 CET [node01: cf.rv.notConnected:error]: Connection for 'cfo_rv' failed. Fri Feb 13 01:39:53 CET [node01: cf.rv.notConnected:error]: Connection for 'cfo_rv2' failed. node01*> cf status node02 is up, takeover disabled because of reason (interconnect error) node01 has disabled takeover by node02 (interconnect error) VIA Interconnect is down (link 0 up, link 1 up). node01*> Fri Feb 13 01:40:03 CET [node01: cf.nm.nicTransitionDown:warning]: Cluster Interconnect link 1 is DOWN Thu Feb 12 19:00:14 CET [node01: scsi.cmd.notReadyCondition:notice]: Disk device eetrsansw10:9.32: Device returns not yet ready: CDB 0x2a:325a93d8:0200: Sense Data SCSI:not ready - Drive spinning up (0x2 - 0x4 0x1 0x2)(1705). Thu Feb 12 19:00:14 CET [node01: scsi.cmd.notReadyCondition:notice]: Disk device eetrsansw10:9.32: Device returns not yet ready: CDB 0x2a:325a95d8:0200: Sense Data SCSI:not ready - Drive spinning up (0x2 - 0x4 0x1 0x2)(1689). Thu Feb 12 19:00:14 CET [node01: scsi.cmd.notReadyCondition:notice]: Disk device eetrsansw10:9.32: Device returns not yet ready: CDB 0x28:325a9c90:0100: Sense Data SCSI:not ready - Drive spinning up (0x2 - 0x4 0x1 0x2)(1698). Thu Feb 12 19:00:14 CET [node01: scsi.cmd.notReadyCondition:notice]: Disk device eetrsansw10:9.32: Device returns not yet ready: CDB 0x28:325a9c58:0008: Sense Data SCSI:not ready - Drive spinning up (0x2 - 0x4 0x1 0x2)(1699). Thu Feb 12 19:00:14 CET [node01: scsi.cmd.notReadyCondition:notice]: Disk device eetrsansw10:9.32: Device returns not yet ready: CDB 0x2a:325a97d8:0200: Sense Data SCSI:not ready - Drive spinning up (0x2 - 0x4 0x1 0x2)(1686). Thu Feb 12 19:00:14 CET [node01: scsi.cmd.notReadyCondition:notice]: Disk device eetrsansw10:9.32: Device returns not yet ready: CDB 0x2a:325a99d8:0200: Sense Data SCSI:not ready - Drive spinning up (0x2 - 0x4 0x1 0x2)(1690). Thu Feb 12 19:00:14 CET [node01: scsi.cmd.notReadyCondition:notice]: Disk device eetrsansw10:9.32: Device returns not yet ready: CDB 0x2f:2f27b400:0400: Sense Data SCSI:not ready - Drive spinning up (0x2 - 0x4 0x1 0x2)(474). Thu Feb 12 19:00:14 CET [node01: scsi.cmd.notReadyCondition:notice]: Disk device eetrsansw10:9.32: Device returns not yet ready: CDB 0x2a:325a91d8:0200: Sense Data SCSI:not ready - Drive spinning up (0x2 - 0x4 0x1 0x2)(1768). Thu Feb 12 19:02:59 CET [node01: cf.nm.nicTransitionDown:warning]: Cluster Interconnect link 0 is DOWN Thu Feb 12 19:02:59 CET [node01: cf.nm.nicTransitionUp:info]: Interconnect link 0 is UP Thu Feb 12 19:03:19 CET [node01: cf.rv.notConnected:error]: Connection for 'cfo_rv' failed. Thu Feb 12 19:03:19 CET [node01: cf.rv.notConnected:error]: Connection for 'cfo_rv2' failed. Thu Feb 12 19:03:28 CET [node01: cf.nm.nicTransitionDown:warning]: Cluster Interconnect link 1 is DOWN Thu Feb 12 19:04:37 CET [node01: cf.nm.nicReset:warning]: Initiating soft reset on Cluster Interconnect card 1 due to rendezvous connection timeout Thu Feb 12 19:06:10 CET [node01: cf.fsm.takeoverByPartnerDisabled:notice]: Failover monitor: takeover of node01 by node02 disabled (unsynchronized log). Thu Feb 12 19:08:16 CET [node01: cf.ic.qlgc.viErr:error]: Qlogic VI FC Adapter: ISP_CS_VI_ERROR vinum = 0xa state = 0x3 code = 0x6 Thu Feb 12 19:13:09 CET [node01: cf.fsm.takeoverByPartnerDisabled:notice]: Failover monitor: takeover of node01 by node02 disabled (interconnect error). Thu Feb 12 19:18:14 CET [node01: cf.fsm.takeoverByPartnerDisabled:notice]: Failover monitor: takeover of node01 by node02 disabled (unsynchronized log). Thu Feb 12 19:20:47 CET [node01: cf.fsm.takeoverOfPartnerDisabled:notice]: Failover monitor: takeover of node02 disabled (interconnect error). Thu Feb 12 19:21:35 CET [node01: cf.fsm.takeoverByPartnerDisabled:notice]: Failover monitor: takeover of node01 by node02 disabled (unsynchronized log). Thu Feb 12 19:22:24 CET [node01: cf.fsm.takeoverOfPartnerDisabled:notice]: Failover monitor: takeover of node02 disabled (interconnect error). Thu Feb 12 19:29:13 CET [node01: cf.ic.qlgc.viErr:error]: Qlogic VI FC Adapter: ISP_CS_VI_ERROR vinum = 0x7 state = 0x3 code = 0x2 Thu Feb 12 19:29:33 CET [node01: cf.rv.notConnected:error]: Connection for 'cfo_rv' failed. Thu Feb 12 19:29:33 CET [node01: cf.rv.notConnected:error]: Connection for 'cfo_rv2' failed. Thu Feb 12 19:30:04 CET [node01: cf.nm.nicTransitionDown:warning]: Cluster Interconnect link 0 is DOWN Thu Feb 12 19:30:05 CET [node01: cf.nm.nicTransitionDown:warning]: Cluster Interconnect link 1 is DOWN Thu Feb 12 19:34:44 CET [node01: cf.fsm.takeoverByPartnerEnabled:notice]: Failover monitor: takeover of node01 by node02 enabled Thu Feb 12 19:36:54 CET [node01: cf.ic.qlgc.viErr:error]: Qlogic VI FC Adapter: ISP_CS_VI_ERROR vinum = 0xa state = 0x3 code = 0x6 Thu Feb 12 19:45:51 CET [node01: raid.mirror.aggrSnapUse:warning]: Aggregate Snapshot copies are used in SyncMirror aggregate 'aggr0'. That is not recommended. Thu Feb 12 19:51:57 CET [node01: cf.fsm.takeoverByPartnerDisabled:notice]: Failover monitor: takeover of node01 by node02 disabled (unsynchronized log). Thu Feb 12 19:58:42 CET [node01: cf.fsm.takeoverOfPartnerEnabled:notice]: Failover monitor: takeover of node02 enabled Thu Feb 12 20:00:16 CET [node01: cf.takeover.disabled:warning]: Controller Failover is licensed but takeover of partner is disabled due to reason : unsynchronized log. Thu Feb 12 20:00:43 CET [node01: cf.fsm.takeoverByPartnerEnabled:notice]: Failover monitor: takeover of node01 by node02 enabled Thu Feb 12 20:04:10 CET [node01: cf.fsm.takeoverOfPartnerEnabled:notice]: Failover monitor: takeover of node02 enabled Thu Feb 12 20:05:29 CET [node01: cf.fsm.takeoverByPartnerDisabled:notice]: Failover monitor: takeover of node01 by node02 disabled (interconnect error). Thu Feb 12 20:14:59 CET [node01: cf.fsm.takeoverByPartnerDisabled:notice]: Failover monitor: takeover of node01 by node02 disabled (interconnect error). Thu Feb 12 20:15:44 CET [node01: cf.ic.qlgc.viErr:error]: Qlogic VI FC Adapter: ISP_CS_VI_ERROR vinum = 0xa state = 0x3 code = 0x6 Thu Feb 12 20:16:04 CET [node01: cf.rv.notConnected:error]: Connection for 'cfo_rv' failed. Thu Feb 12 20:16:04 CET [node01: cf.rv.notConnected:error]: Connection for 'cfo_rv2' failed. Thu Feb 12 20:16:05 CET [node01: cf.nm.nicTransitionUp:info]: Interconnect link 1 is UP Thu Feb 12 20:16:06 CET [node01: cf.nm.nicTransitionDown:warning]: Cluster Interconnect link 0 is DOWN Thu Feb 12 20:16:06 CET [node01: cf.nm.nicTransitionDown:warning]: Cluster Interconnect link 1 is DOWN Fri Feb 13 01:00:17 CET [node02: cf.takeover.disabled:warning]: Controller Failover is licensed but takeover of partner is disabled due to reason : unsynchronized log. Fri Feb 13 01:02:35 CET [node02: cf.fsm.takeoverByPartnerEnabled:notice]: Failover monitor: takeover of node02 by node01 enabled Fri Feb 13 01:03:45 CET [node02: cf.ic.qlgc.viErr:error]: Qlogic VI FC Adapter: ISP_CS_VI_ERROR vinum = 0x8 state = 0x3 code = 0x6 Fri Feb 13 01:03:45 CET [node02: cf.nm.nicReset:warning]: Initiating soft reset on Cluster Interconnect card 0 due to ispfcvi2400 fatal VI error Fri Feb 13 01:12:36 CET [node02: cf.nm.nicTransitionDown:warning]: Cluster Interconnect link 0 is DOWN Fri Feb 13 01:12:42 CET [node02: cf.fsm.takeoverByPartnerEnabled:notice]: Failover monitor: takeover of node02 by node01 enabled Fri Feb 13 01:18:52 CET [node02: cf.fsm.takeoverOfPartnerEnabled:notice]: Failover monitor: takeover of node01 enabled Fri Feb 13 01:20:00 CET [node02: monitor.globalStatus.critical:CRITICAL]: Controller failover of node01 is not possible: unsynchronized log. /vol/db_p_mcs7_iscsi is full (using or reserving 98% of space and 0% of inodes, using 98% of reserve). Fri Feb 13 01:39:33 CET [node02: cf.ic.qlgc.viErr:error]: Qlogic VI FC Adapter: ISP_CS_VI_ERROR vinum = 0xa state = 0x3 code = 0x6 Fri Feb 13 01:39:54 CET [node02: cf.nm.nicTransitionDown:warning]: Cluster Interconnect link 0 is DOWN Fri Feb 13 01:39:54 CET [node02: cf.nm.nicTransitionDown:warning]: Cluster Interconnect link 1 is DOWN Fri Feb 13 01:39:54 CET [node02: cf.rv.notConnected:error]: Connection for 'cfo_rv2' failed. Fri Feb 13 01:52:48 CET [node02: ems.engine.inputSuppress:warning]: Event 'openssh.invalid.channel.req' suppressed 87 times since Fri Feb 13 00:00:04 CET 2015. Fri Feb 13 01:52:48 CET [node02: openssh.invalid.channel.req:warning]: SSH client (SSH-2.0-OpenSSH_5.3) from 10.132.0.72 sent unsupported channel request (10, env).

4 3

VLAN create vs. VLAN add
by Mike Brown 12 Feb '15

12 Feb '15

Thought I'd give this mailing list a try with a softball: I get the difference between vlan create and vlan add in 7-mode: "If a physical interface does not belong to any VLAN, you can use the vlan create command to make the interface a member of one or more VLANs. However, if the interface is already a member of a VLAN, you should use the vlan add command to add the interface to subsequent VLANs." but what's so different about each command behind the scenes such that using "add" is better if a VLAN interface has already been created for an interface group? I've been using "vlan create" in my /etc/rc files for years without noticing a difference. I'll update the way I use each command, but I was wondering what *real* difference was between the two (not just *when* to use them). So in programming, sometimes, one operation is simply more efficient than another or can be completed in less steps, cycles, instructions, or perhaps with some atomicity. I was thinking this might be the reason, but what do you think? Thanks, Mike -- Mike Brown michael.b.brown3(a)gmail.com Blog: http://VirtuallyMikeBrown.com Twitter: http://twitter.com/VirtuallyMikeB <http://twitter.com/#%21/VirtuallyMikeB> LinkedIn: http://linkedin.com/in/michaelbbrown

2 1

CIFS NOT WORKING
by Camillo Gornati 11 Feb '15

11 Feb '15

Hi all! Yesterday everything was working fine, today in the morning, we can ping the share, but cannot open it on windows. Any ideas?

4 3

Motherboard replacement on FAS3270 caused fabric wide issue
by Momonth 11 Feb '15

11 Feb '15

Hi All, I hit the following bug on one of the filer (FAS3260) I manage: http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=659544 This filer (filer-prod-204) works in HA mode with filer-prod-203. They are connected to two redundant FC SAN fabrics (one connection from each filer per fabric). There are more HA pairs connected to the same fabrics, eg filer-prod-201 / filer-prod-202. All of the filers we have are running in 'single-image' mode. We run FC SAN fabrics in "hard zoning mode". NetApp support conclusion was to replace motherboard on the filer and we proceeded with that. Here is an issue we had and I have no explanation to that, I hope you guys can help me with that: Once the filer-prod-204 got the motherboard replaced, powered on and entered HW diagnostics mode I've seen the messages as below *on every other filer* (eg. filer-prod-201), connected to the same fabric, causing issues on hosts (CentOS 6.4 mainly) attached to them: Fri Jan 30 20:07:45 CET [filer-prod-201: scsitarget.ispfct.targetReset:notice]: FCP Target 0c: Target was Reset by the Initiator at Port Id: 0x11000 (WWPN 5001438021e071ec) Fri Jan 30 20:07:46 CET [filer-prod-201: scsitarget.ispfct.targetReset:notice]: FCP Target 0c: Target was Reset by the Initiator at Port Id: 0x10200 (WWPN 50014380186abac4) ... Fri Jan 30 20:08:14 CET [filer-prod-201: scsitarget.ispfct.portLogin:notice]: FCP login on Fibre Channel adapter '0c' from '50:01:43:80:21:e0:71:ec', address 0x11000. Fri Jan 30 20:08:14 CET [filer-prod-201: scsitarget.ispfct.portLogin:notice]: FCP login on Fibre Channel adapter '0c' from '50:01:43:80:18:6a:ba:c4', address 0x10200. So every single initiator on the filer *not involved* in the maintenance were reset, then tried to login back, reset again and it looped like that until I disabled filer-prod-204's target ports on the FC switches. Once the filer-prod-204 booted up with OnTAP, the issue was gone. I know it because when I tried to re-enabled the filer-prod-204's target ports, I didn't see any message like above and everything is running fine since then. Does anyone have an idea what was happing here and why? Cheers, Vladimir

3 10

Check config
by Camillo Gornati 11 Feb '15

11 Feb '15

Hi all, today in the morning we had a little issue with our time sync, causing the CIFS service to stop working. Now that everything is back to normal, i would like to check with you guys how can check if my filer is 100% ok? We hava a FAS2040 (dual head fully licensed) 2 DS4243 24 disks on it. I want to know if in case of a hardware failure my my system will still be online, redundant. I am kind of new to netapp and assumed this system recently, hasn’t been configured by me. Any help will do it.. Thanks C.

4 3

IOPS Planning for the Deswizzle Process?
by Philbert Rupkins 10 Feb '15

10 Feb '15

Hello Toasters, We've unfortunately had to reduce the frequency of our volume snapmirror updates in order to allow for our destination aggregate to deswizzle. We highly prefer hourly volume snapmirror updates but it turns our our source volumes are large enough and/or have enough snapshots that the deswizzle process never completes on the destination aggregate. Our volume snapmirror destination aggregate is a single tray of SATA. Prior to reducing the frequency of snapmirror updates, the SATA aggregate was running at 90-100% utilization 24x7 with little to no IO to the filer from active clients. Needless to say, serving data from said aggregate was VERY SLOW despite the light IO (<300 IOPS) required by the clients sourcing their primary data from the SATA aggregate. We've done what we can to reduce the impact of deswizzling. Namely, cutting down on snapshots and reducing the volume size. I understand reducing volume size doesnt reduce the maxfiles setting which believe ultimately impact the amount of deswizzling necessary on the destination. I'm still digging into other options we can try but reducing the frequency of snapmirror updates seems to have the most impact. How does one plan for IOPs or disk utilization resulting from the deswizzle process? If I recall correctly, during our planning sessions with NetApp, our Netapp SE never touched on IOPs or number of spindles required to handle deswizzling while serving data from the same aggregate. In fact, I think our aggregates were size purely based on the amount of IO generated from active clients (not active clients + deswizzle). Thanks, Phil

2 3

Re: IOPS Planning for the Deswizzle Process?
by Philbert Rupkins 10 Feb '15

10 Feb '15

Can you expand upon why QSM wouldn't be a good choice for a general DR use case? We currently do not use "vfiler dr" and have no immediate plans to use it in the future. On Thu, Feb 5, 2015 at 2:28 PM, Peter-Paul Witta <paul.witta(a)cubit.at> wrote: > Great! > Just keep in mind QSM might not be the best choice for DR or vfilerDR use > cases... > > kind regards, > Ing. Peter-Paul Witta > Chief Technology Officer www.CUBiT.at > Mobile +436644542287 > Office +4317189880-0 > > Am 05.02.2015 um 21:17 schrieb Philbert Rupkins <philbertrupkins(a)gmail.com > >: > > Just a quick update. We're generally a volume snapmirror shop. I think > I read somewhere that VSM is generally recommended in most cases. > > However, I also read that Qtree SnapMirror is not subject to the same > deswizzling process that runs on the destination when using VSM. My > understanding is this is because VSM is block based whereas QSM is not. > The SnapMirror TR goes through a fairly decent list of the differences > between VSM and QSM. Since QSM does not require deswizzling, I think > we are going to give QSM a shot for the volumes with many snapshots. > Sure, we'll need to dedupe the QSM destination and figure out how to manage > snapshots, but QSM sounds like something we need to consider given the high > disk utilization resulting from the deswizzle process. > > -Phil > > On Tue, Feb 3, 2015 at 10:44 AM, Philbert Rupkins < > philbertrupkins(a)gmail.com> wrote: > >> Paul, >> >> Thanks for this tip. I cant find much about the wafl.deswizzle.enable >> option on the support site. I did find a document that says "This is a >> diagnostic mode option that should only be used as part of an action plan >> under NetApp Global Support supervision." I guess I'll be giving them a >> call. >> >> Did you find this option mentioned in another document somewhere? >> Quarterly, we refresh an environment on the remote side which involves >> promoting a (volume) snapmirror replica to a primary copy of the data. >> I just want to make sure I am not going to shoot myself in the foot (from a >> performance perspective) with this option when we break a snapmirror >> replica and use the destination as a primary copy. >> >> Thanks, >> Phil >> >> On Tue, Jan 27, 2015 at 2:04 PM, Peter-Paul Witta <paul.witta(a)cubit.at> >> wrote: >> >>> if you do not plan to use the destination regularily tun the >>> deswziller off. >>> otherwise you'd deswizzle lots of snapshots you'll never use active on >>> the destination anyway... >>> >>> greets, >>> paul >>> >>> >>> Am 27.01.15 um 20:55 schrieb Philbert Rupkins: >>> >>> Hello Toasters, >>> >>> We've unfortunately had to reduce the frequency of our volume >>> snapmirror updates in order to allow for our destination aggregate to >>> deswizzle. We highly prefer hourly volume snapmirror updates but it turns >>> our our source volumes are large enough and/or have enough snapshots that >>> the deswizzle process never completes on the destination aggregate. Our >>> volume snapmirror destination aggregate is a single tray of SATA. Prior to >>> reducing the frequency of snapmirror updates, the SATA aggregate was >>> running at 90-100% utilization 24x7 with little to no IO to the filer from >>> active clients. Needless to say, serving data from said aggregate was >>> VERY SLOW despite the light IO (<300 IOPS) required by the clients sourcing >>> their primary data from the SATA aggregate. >>> >>> >>> We've done what we can to reduce the impact of deswizzling. Namely, >>> cutting down on snapshots and reducing the volume size. I understand >>> reducing volume size doesnt reduce the maxfiles setting which believe >>> ultimately impact the amount of deswizzling necessary on the destination. >>> I'm still digging into other options we can try but reducing the frequency >>> of snapmirror updates seems to have the most impact. >>> >>> How does one plan for IOPs or disk utilization resulting from the >>> deswizzle process? If I recall correctly, during our planning sessions >>> with NetApp, our Netapp SE never touched on IOPs or number of spindles >>> required to handle deswizzling while serving data from the same aggregate. >>> In fact, I think our aggregates were size purely based on the amount of >>> IO generated from active clients (not active clients + deswizzle). >>> >>> Thanks, >>> Phil >>> >>> >>> _______________________________________________ >>> Toasters mailing listToasters@teaparty.nethttp://www.teaparty.net/mailman/listinfo/toasters >>> >>> >>> >>> -- >>> kind regards, +43-664-4542287 >>> Ing. Peter-Paul Witta +43-1-7189880-0 >>> CTO/techn. Geschaeftsleitung www.CUBiT.at >>> >>> >> > _______________________________________________ > Toasters mailing list > Toasters(a)teaparty.net > http://www.teaparty.net/mailman/listinfo/toasters > >

2 1

"iscsi interface disable" Effect on Existing iSCSI Portals
by Philbert Rupkins 10 Feb '15

10 Feb '15

Hello Toasters, We have a client looking to limit iscsi services to a dedicated interface. It looks like, by default, ONTAP is running iSCSI portals on all interfaces in both the pfiler (vfiler0) and all vfilers. Is "iscsi interface disable" on vfiler0 (physical filer) the best way to get rid of all of the extraneous iscsi portals? Will running "iscsi interface disable" on the physical filer get rid of the iscsi portal(s) on the physical filers and vfilers? Not sure if I'll need to run a portal/tpgroup specific command or if "iscsi interface disable" will get rid of the portals. 8.1.3 7-Mode. Thanks, Phil

2 4

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 February 2015