toasters March 2016

toasters@lists.teaparty.net

33 participants
20 discussions

FDMI reporting with qla2xxx driver on Linux
by Momonth 09 Dec '16

09 Dec '16

Hi, I recently noticed that qla2xxx (Qlogic HBAs) driver on Linux is capable of reporting FDMI. By default it sends "Linux-default", and I'm failing to see how to change it to actual host name as it becomes way more handy then =) Any ideas? Cheers, Vladimir

2 3

badlock
by Weber, Mark A 12 Apr '16

12 Apr '16

Any NetApp people know if badlock will impact ONTAP? http://badlock.org/ http://www.theregister.co.uk/2016/03/22/badlock_bug/ thanks m

2 2

NetApp SDK for cDOT: any API call fails if a cluster node is not available
by Momonth 31 Mar '16

31 Mar '16

Hi All, We extensively use NetApp API calls to monitor 7Mode filers, and took the same approach for cDOT monitoring. Here is a very unpleasant discovery: 1. Take one node (or more nodes) *offline*, eg power it off for maintenance. 2. Try to run *any* API call against cluster interface and get the following error: OUTPUT: <results reason="RPC: Port mapper failure - RPC: Timed out" status="failed" errno="13001"></results> It effectively makes your cluster wide monitoring useless. Any ideas? Is it a feature or a bug? Cheers, Vladimir

3 9

metro under high latency
by josef radinger 30 Mar '16

30 Mar '16

hi i have a metro cluster (rather old) which is currently responding very slowly. 7-mode 8.1.4 there is only one aggregate per head, filled at around 72% one one head and 79% on the other head. attached is a statit and sysstat -x 1 from one head. i see lots of partial stripes and only several full stripes. i assume this should mean not enough free space, which should imho not be a problem at my aggregates. what is the correct procedure for performing a free space reallocation? i did: * stop all volume-reallocates * disable read_reallocation on all volumes * raid.lost_write.enable off * aggr options aggr0 resyncsnaptime 5 * reallocate start -A -o aggr0 * wait for finish of reallocate * aggr options aggr0 resyncsnaptime 60 * enable read_reallocation on all volumes * reenable all volume-level reallocates my aggregates have options: aggr options aggr0 root, diskroot, nosnap=off, raidtype=raid_dp, raidsize=20, ignore_inconsistent=off, snapmirrored=off, resyncsnaptime=60, fs_size_fixed=off, snapshot_autodelete=on, lost_write_protect=on, ha_policy=cfo, hybrid_enabled=off, percent_snapshot_space=5%, free_space_realloc=off any advice? josef

6 13

any easiest way to run the commands during 7mode to cluster mode
by Yuvaraja Shivaram 26 Mar '16

26 Mar '16

hi All, since 7mode migrations to cluster mode involved lot of commands to be entered at cmode command prompt ,is there any easy way or script where we can run the commands easily. please let me know on that ... regards Yuvaraja

2 1

after snapmirror cutover source volume bacame same size of source...any idea what is the issue?
by Yuvaraja Shivaram 26 Mar '16

26 Mar '16

Hi all, when i performed the snapmirror cutover in 7mode...the destination volume size became the same size of source..any idea what could be problem and how to avoid this in future.. in verson... 8.2p5 regards Yuvaraja

2 1

Transition snapmirror to regular snapmirror
by Basil 23 Mar '16

23 Mar '16

I am trying to migrate a replicated volume to CDOT, but I can't use 7mtt. My plan is to set up a transition snapmirror and do the cutover manually. I can't start the regular snapmirror of the CDOT transition snapmirror target, though. I get "Using a transition volume as a snapmirror source volume is not supported". I have a long outage window, but would prefer to pre-seed the mirror of the new volume. What would you folks suggest?

5 7

any good doc for cluster mode , please share with me
by Yuvaraja Shivaram 22 Mar '16

22 Mar '16

hi all, i am new user to this site.. any good doc for cluster mode , please share with me

2 1

Moving shelves with root aggr and root vol (7-mode) from one Filer to another
by Martin 22 Mar '16

22 Mar '16

Hi, I have one 7-mode Filer that I will be decommissioning which has data on it I need to migrate to another 7-mode Filer. We don't have space to mirror the data to the new Filer, want to reuse the shelves on the new Filer and this is a quicker cut over. The four DS4243 shelves have a single aggregate (aggr0) with various volumes on it (exported via NFS) including the root volume for the controller (vol0). I found the KB on moving shelves and aggregates between controllers but it doesn't mention what to do about a Filer that has vol0 and root aggr on the shelves. My plan is: 1. Disable disk auto assign on both source and destination Filer on both controllers options disk.auto_assign off 1. Reboot the source controller into maintenance mode 2. Offline aggr0 aggr offline aggr0 3. Uknown the disks on the shelves on the source controller disk assign disk_name -s unowned -f 4. Shutdown the Source Filer and power off along with shelves 4. Power down the destination Filer and add SAS card to new Filer (not enough SAS ports for new loop) 5. Physically moves shelves from source Filer to destination Filer 6. Cable shelves and change shelf IDs along with a powercycle to ensure shelf IDs don't conflict 7. Assign the disks on the new Filer disk assign disk_name 8. As the aggregate is aggr0 and new Filer also has aggr0 it gets renamed to aggr0(1) and foreign 9. Check the status of the new aggregate aggr status aggr_name 10. Rename the new aggregate from aggr0(1) to aggr1 aggr rename aggr0(1) aggr1 11. Online the aggregate on the destination Filer as it is longer labelled as foreign aggregate. aggr online aggr1 12. Check the aggregate status on the destination Filer aggr status aggr1 13. Export the volumes on the destination Filer via /etc/exports and exportfs -r -- View this message in context: http://network-appliance-toasters.10978.n7.nabble.com/Moving-shelves-with-r… Sent from the Network Appliance - Toasters mailing list archive at Nabble.com.

6 8

disk ownership question
by Mark Flint 22 Mar '16

22 Mar '16

Hi list. I have a 3170 running 8.0P1 7-Mode, and am having a problem with auto-assignment of disks. The unit reports that it can’t do auto-assign, because not all of the disks on the loop are owned by the same controller. I was under the impression that software ownership made that unnecessary (you can laugh), but it seems not. KB from 2014 says the same thing. So, question is, has anyone done anything like this (had to reassign a shedload of disks) to make auto-assign work, and could they pass any info on how I can fix this please? Thanks, Mark

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 March 2016