toasters

toasters@lists.teaparty.net

3 participants
13514 discussions

Re: Oddball SnapMirror issue
by Raj Patel 18 May '08

18 May '08

> Try backing off SnapMirror's TCP window (options snapmirror.window_size) > to lower the effective throughput, or nail down 'kbs' options in your > snapmirror.conf. Yup - tried the "options snapmirror.window_size 32768" and throttling the mirror speed down. I still don't understand why, if the connection was ropey, it didn't just keep trying to establish the baseline rather than just giving up and failing to initialise. I'll have to see what our networking guys come up with on the ipsec side. Cheers, Raj.

1 0

Aggregates on Multistore
by Cristian Rojas 18 May '08

18 May '08

Hi guys, wondering if its ok to have 2 storage groups on 2 separate aggregates for Exchange, 1 would be dedicated to mailboxes and the other one to logs. Im not sure if this would work on a vfiler, I think ive heard all the resources of the vfiler need to be part of the same aggr. Anyone doing anything like this? Thanks Cris

2 1

Nearstore option usage?
by Adam McDougall 18 May '08

18 May '08

So we have some FAS3040 and a nearstore license and I'd like to figure out how I can take advantage of it. It was required for A-SIS but I'd like to look into identifying 'old' data in my largest volume and segregating it off of fibre channel disks. What is required and how can I get started? It seems hard to find info on NOW about this. The closest thing so far was the following document which hints strongly at the capability but not how. Any tips? Thanks. http://now.netapp.com/NOW/products/NearStore_option/

3 2

Oddball SnapMirror issue
by Raj Patel 16 May '08

16 May '08

We've got two FAS 270's in different cities. They're connected by a 10mb pipe with routers (running ipsec) & firewalls (checkpoint splat) seperating each datacenter. The primary san is fine and runs all our prod volumes (7.0.5) which are mirrored to our secondary san (7.0.6). Recently I had to recreate the mirror relationship for some volumes as they'd fallen far out of sync due to some firewall work. What I am seeing is one volume is syncing fine, one has a small lag and two are stuck with a status of 'Pending with restart checkpoint' after I re-initialised the transfer. snapmirror status -l shows this for one of the two that just don't get properly initialised Source: 10.1.45.7:sqlprod01 Destination: adcsan1:sqlprod01_mirror Status: Pending with restart checkpoint Progress: 38376 KB State: Unknown Lag: - Mirror Timestamp: - Base Snapshot: - Current Transfer Type: Retry Current Transfer Error: volume is not online; cannot execute operation Contents: - Last Transfer Type: - Last Transfer Size: - Last Transfer Duration: - Last Transfer From: - Our firewalls rules have been relaxed to allow free-flow between these devices (instead of just the SnapMirror ports) and the routers and circuit haven't changed at all between it working fine and not working now. The volume that is mirroring OK seems fine and still syncs fine - granted the updates are small whereas the three non-working volumes have to sync quite a lot of data. I've tried deleting the mirrored volumes, recreating them, setting up the mirror relationship again (with a variety of scheduling and bandwidth throttling options) and doing a destination SAN reboot. What are the best options to troubleshoot this or insuring a successful mirror ? Has anyone had issues with dropped or stalled SnapMirror baseline transfers via an IPSec tunnel or Firewall ? Thanks in advance, Raj. PS As an addendum it looks like it starts a transfer, stalls and from then on subsequent mirrors fail because its not online (ie the initialisation fails ?) What I don't understand is why it just can't carry on with the initialisation regardless of the interruption by resuming the mirror operation ?

6 14

R: MSCS and snapmirror question
by Milazzo Giacomo 16 May '08

16 May '08

Of course but that guy said he's migrating on the same filer to another aggregate. ________________________________ Da: Patrick van Helden [mailto:pvh@databasement.eu] Inviato: ven 16/05/2008 19.12 A: Milazzo Giacomo; Klise, Steve; toasters(a)mathworks.com Oggetto: RE: MSCS and snapmirror question Guys, Please be aware that MSCS will keep track of the lun serials. So you would probably need to set the lun serial numbers back to the original ones when your snapmirroring to another filer. Regards, Patrick van Helden Databasement BV pvh(a)databasement.eu -----Oorspronkelijk bericht----- Van: owner-toasters(a)mathworks.com namens Milazzo Giacomo Verzonden: vr 5/16/2008 18:01 Aan: Klise, Steve; toasters(a)mathworks.com Onderwerp: R: MSCS and snapmirror question You will not have issues. And you don't need to update your mirror. If you simply power off you clusters no i/o activity will be performer on LUNs. Then you can simply copy (vol copy) the volume(s) containing your LUNs, rename the new volumes as the old (in case of iSCSI LUNs and if you don't want to recreate the connections) and restart you clusters. In case your nodes (but it will not happen) will loose the LUNs with Snapdrive you can safely reconnect them starting with the quorum one, on first node then restarting the cluster service, then on the second node and so on with all other cluster shared LUNs Regards -----Messaggio originale----- Da: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] Per conto di Klise, Steve Inviato: venerdì 16 maggio 2008 15.50 A: toasters(a)mathworks.com Oggetto: MSCS and snapmirror question I am migrating from an aggregate to another aggregate in the same filer (6030). The LUNS are attached to print clusters, 2 node and 3 node clusters (WIndows 2003 sp2 x86 etc). I have snapmirrored the volumes. If I stop the cluster service on the windows boxes, do a snapmirror update, the disconnected the quorum and other resource disks, do a snapmirror update, release the snapmirror, remove and replace the disks with snapdrive with the same disk letters. fire up the cluster service.. Will that work? has anyone done that before? Any gotchas? Any help is greatly appreciate!

1 0

VIF weirdness
by Page, Jeremy 16 May '08

16 May '08

I am having a great deal of difficulty getting my filer's 10g interfaces connected to a pair of 3750E switches I am trying to use for my storage network's backbone. I can inconsistently ping other objects on the network (there really is nothing there yet, we are just getting started, but I do have a host and an RLM card just for troubleshooting purposes), but they cannot ping each other. From a remote host (172.1.2.5) I can ping everything but array1. If I bring down either of the two stacked switches (which brings down one port of each VIF member pairs) everything works. array01> ping 172.1.0.1 172.1.0.1 is alive array01> ping 172.1.0.2 array01> ping 172.1.0.4 ping: wrote 172.1.0.4 64 chars, error=Host is down ping: wrote 172.1.0.4 64 chars, error=Host is down array01> Thu May 15 13:28:33 EDT [gvr-array01: nis_worker_0:info]: Local NIS group update successful. array01> ping 172.1.2.5 172.1.2.5 is alive array02> ping 172.1.0.1 array02> ping 172.1.0.4 172.1.0.4 is alive array02> ping 172.1.0.4 172.1.0.4 is alive array02> ping 172.1.0.250 172.1.0.250 is alive array02> ping 172.1.2.5 no answer from 172.1.2.5 array01> ifconfig -a e0a: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 02:a0:98:08:22:b7 (auto-1000t-fd-up) flowcontrol full trunked lan0 e0b: flags=108042<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 00:a0:98:08:22:b6 (auto-unknown-cfg_down) flowcontrol full e0c: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 02:a0:98:08:22:b7 (auto-1000t-fd-up) flowcontrol full trunked lan0 e0d: flags=108042<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 00:a0:98:08:22:b4 (auto-unknown-cfg_down) flowcontrol full e2a: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 02:a0:98:08:22:b6 (auto-10g_sr-fd-up) flowcontrol full trunked tgif e2b: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 02:a0:98:08:22:b6 (auto-10g_sr-fd-up) flowcontrol full trunked tgif lo: flags=1948049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 8160 inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1 ether 00:00:00:00:00:00 (VIA Provider) lan0: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 inet 10.28.17.213 netmask 0xffffff00 broadcast 10.28.17.255 partner 10.28.17.214 (not in use) ether 02:a0:98:08:22:b7 (Enabled virtual interface) tgif: flags=4948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500 inet 172.1.0.1 netmask 0xffff0000 broadcast 172.1.255.255 partner 172.1.0.2 (not in use) ether 02:a0:98:08:22:b6 (Enabled virtual interface) nfo enabled array02>ifconfig -a e0a: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 02:a0:98:0c:1a:37 (auto-1000t-fd-up) flowcontrol full trunked lan0 e0b: flags=108042<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 00:a0:98:0c:1a:36 (auto-unknown-cfg_down) flowcontrol full e0c: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 02:a0:98:0c:1a:37 (auto-1000t-fd-up) flowcontrol full trunked lan0 e0d: flags=108042<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 00:a0:98:0c:1a:34 (auto-unknown-cfg_down) flowcontrol full e2a: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 02:a0:98:0c:1a:36 (auto-10g_sr-fd-up) flowcontrol full trunked tgif e2b: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 02:a0:98:0c:1a:36 (auto-10g_sr-fd-up) flowcontrol full trunked tgif lo: flags=1948049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 8160 inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1 ether 00:00:00:00:00:00 (VIA Provider) lan0: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 inet 10.28.17.214 netmask 0xffffff00 broadcast 10.28.17.255 partner 10.28.17.213 (not in use) ether 02:a0:98:0c:1a:37 (Enabled virtual interface) tgif: flags=4948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500 inet 172.1.0.2 netmask 0xffff0000 broadcast 172.1.255.255 partner 172.1.0.1 (not in use) ether 02:a0:98:0c:1a:36 (Enabled virtual interface) nfo enabled This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee. Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately.

4 3

Multistore Setup
by Cristian Rojas 15 May '08

15 May '08

Hi list, this is my env: -FAS960 -OnTAP 7.2.3 -2 Aggr -Installed Multistore License -Created vfilers: lgsstpnas02> vfiler status vfiler0 running excvfiler1 running But cant ping the ip of the vfiler assigned to e6b. Here my network interfaces: e0 Up 192.168.215.95 Modify Up Down e5b Down 10.223.61.90 Modify Up Down e6b Up 10.223.61.91 Modify Up Down e7b Down -- Modify Up Down e9b Down -- Modify Up Down vifp32 Up 10.223.59.111 Modify Up Down RemoveTrunk - e5a Up -- Modify - e6a Up -- Modify vifpriv Up 192.168.56.4 Modify Up Down RemoveTrunk - e7a Up -- Modify - e9a Up -- Modify lo Up 127.0.0.1 The two cisco 3750 on top are trunked so I should be able to reach any vlan in my network. Any hint anyone? Thanks! Cris ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

3 3

RE: VIF weirdness
by Page, Jeremy 15 May '08

15 May '08

They are 10 gig cards, they are only in a VIF with themselves (no other cards). It's a 3070 with 2 copper 100/1000 2 FC gig and 2 FC 10g connections. The 2 1000 are on our production network as lan0 VIF for CIFS/NFS, the fibre gig is not used and the two 10g FC are VIF tgif on the storage only network (no routing etc, private for storage devices and the hosts using them only). They are plugged into stacked 3750e boxes, I tried putting them on the same switch just to make sure it was not a stacking thing with no real change. The oddness is that occasionally a single packet will get through, and if I bring the interfaces up and down it may change who can get to what. ________________________________ From: Webster, Stetson [mailto:Stetson.Webster@netapp.com] Sent: Thursday, May 15, 2008 2:13 PM To: Page, Jeremy; toasters(a)mathworks.com Subject: RE: VIF weirdness Are these 10g TOE cards? Are they in a VIF with other 'non-TOE' cards? Stetson M. Webster Onsite Professional Services Engineer PS - North Amer. - East NetApp 919.250.0052 Mobile Stetson.Webster(a)netapp.com www.netapp.com <http://www.netapp.com/> ________________________________ From: Page, Jeremy [mailto:jeremy.page@gilbarco.com] Sent: Thursday, May 15, 2008 1:32 PM To: toasters(a)mathworks.com Subject: VIF weirdness I am having a great deal of difficulty getting my filer's 10g interfaces connected to a pair of 3750E switches I am trying to use for my storage network's backbone. I can inconsistently ping other objects on the network (there really is nothing there yet, we are just getting started, but I do have a host and an RLM card just for troubleshooting purposes), but they cannot ping each other. >From a remote host (172.1.2.5) I can ping everything but array1. If I bring down either of the two stacked switches (which brings down one port of each VIF member pairs) everything works. array01> ping 172.1.0.1 172.1.0.1 is alive array01> ping 172.1.0.2 array01> ping 172.1.0.4 ping: wrote 172.1.0.4 64 chars, error=Host is down ping: wrote 172.1.0.4 64 chars, error=Host is down array01> Thu May 15 13:28:33 EDT [gvr-array01: nis_worker_0:info]: Local NIS group update successful. array01> ping 172.1.2.5 172.1.2.5 is alive array02> ping 172.1.0.1 array02> ping 172.1.0.4 172.1.0.4 is alive array02> ping 172.1.0.4 172.1.0.4 is alive array02> ping 172.1.0.250 172.1.0.250 is alive array02> ping 172.1.2.5 no answer from 172.1.2.5 array01> ifconfig -a e0a: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 02:a0:98:08:22:b7 (auto-1000t-fd-up) flowcontrol full trunked lan0 e0b: flags=108042<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 00:a0:98:08:22:b6 (auto-unknown-cfg_down) flowcontrol full e0c: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 02:a0:98:08:22:b7 (auto-1000t-fd-up) flowcontrol full trunked lan0 e0d: flags=108042<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 00:a0:98:08:22:b4 (auto-unknown-cfg_down) flowcontrol full e2a: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 02:a0:98:08:22:b6 (auto-10g_sr-fd-up) flowcontrol full trunked tgif e2b: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 02:a0:98:08:22:b6 (auto-10g_sr-fd-up) flowcontrol full trunked tgif lo: flags=1948049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 8160 inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1 ether 00:00:00:00:00:00 (VIA Provider) lan0: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 inet 10.28.17.213 netmask 0xffffff00 broadcast 10.28.17.255 partner 10.28.17.214 (not in use) ether 02:a0:98:08:22:b7 (Enabled virtual interface) tgif: flags=4948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500 inet 172.1.0.1 netmask 0xffff0000 broadcast 172.1.255.255 partner 172.1.0.2 (not in use) ether 02:a0:98:08:22:b6 (Enabled virtual interface) nfo enabled array02>ifconfig -a e0a: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 02:a0:98:0c:1a:37 (auto-1000t-fd-up) flowcontrol full trunked lan0 e0b: flags=108042<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 00:a0:98:0c:1a:36 (auto-unknown-cfg_down) flowcontrol full e0c: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 02:a0:98:0c:1a:37 (auto-1000t-fd-up) flowcontrol full trunked lan0 e0d: flags=108042<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 00:a0:98:0c:1a:34 (auto-unknown-cfg_down) flowcontrol full e2a: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 02:a0:98:0c:1a:36 (auto-10g_sr-fd-up) flowcontrol full trunked tgif e2b: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 02:a0:98:0c:1a:36 (auto-10g_sr-fd-up) flowcontrol full trunked tgif lo: flags=1948049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 8160 inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1 ether 00:00:00:00:00:00 (VIA Provider) lan0: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 inet 10.28.17.214 netmask 0xffffff00 broadcast 10.28.17.255 partner 10.28.17.213 (not in use) ether 02:a0:98:0c:1a:37 (Enabled virtual interface) tgif: flags=4948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500 inet 172.1.0.2 netmask 0xffff0000 broadcast 172.1.255.255 partner 172.1.0.1 (not in use) ether 02:a0:98:0c:1a:36 (Enabled virtual interface) nfo enabled This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee. Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately. This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee. Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately.

2 3

Re: Multistore Setup
by Villabroza, Gerald 14 May '08

14 May '08

Cristian Rojas wrote: > Hi Gerald, thanks for your questions, these is the output: > > lgsstpnas02> vfiler status -r > vfiler0 running > ipspace: default-ipspace > IP address: 10.223.59.111 [vifp32] > IP address: 192.168.56.4 [vifpriv] > IP address: 192.168.215.95 [e0] > Path: / [/etc] > UUID: 00000000-0000-0000-0000-000000000000 > > excvfiler1 running > ipspace: excfiler-ipspace > IP address: 10.223.61.91 [e6b] > Path: /vol/excvfiler [/etc] > UUID: bd4cee12-1905-11dd-84ee-00a0980159d1 > > > ---------------------------0------------------------- >> 2. is the ip address in the output pingable from someplace? > No, not even from the filer :( It won't be pingable from the filer because routed is off. This is requried for Multistore. Try configuring a system on the same network using an IP in the same subnet. Ping the the vfiler from there and ping the system from the vfiler. > ---------------------------0------------------------- >> 3. are you using vlans or ipspaces? > Ipspaces > > lgsstpnas02> ipspace list > Number of ipspaces configured: 2 > default-ipspace (e0 e9b e5b e7b vifp32 vifpriv) > excfiler-ipspace (e6b) > > ---------------------------0------------------------- >> 4. what does 'vfiler run excvfiler1 run route -s'say? > > lgsstpnas02> vfiler run excvfiler1 route -s > > ===== excvfiler1 > Routing tables > > Internet: > Destination Gateway Flags Refs Use Interface > default 10.223.61.254 UGS 0 0 e6b > 10.223.61/24 link#7 UC 0 0 e6b > 10.223.61.254 link#7 UHL 1 0 e6b That default route doesn't look right for the e6b ip. What subnet mask is used for the e6b ifconfig statement? -=-=- gerald villabroza <geraldv at stanford.edu> technical lead, its storage, stanford university

1 0

RE: cannot create incremental snapshot
by Somavarapu, Nagender 12 May '08

12 May '08

Hi Chaim, setting fractional_reserve to 0 has some side effects with LUNs which could be undesirable. You may like to understand this option in more detail before disabling it. thanks S Nagender -----Original Message----- From: Chaim Rieger [mailto:lists@up-south.com] Sent: Friday, May 09, 2008 12:04 AM To: Stephen C. Losen Cc: toasters(a)mathworks.com Subject: Re: cannot create incremental snapshot Stephen C. Losen wrote: > > You probably need to set the fractional reserve on the source volume > to zero: > > vol options qryndbcore fractional_reserve 0 > > > > Steve Losen scl(a)virginia.edu phone: 434-924-0640 > > University of Virginia ITC Unix Support > that did the trick thanx

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