toasters

toasters@lists.teaparty.net

3 participants
13534 discussions

Question regarding NVRAM battery
by Camillo Gornati 08 Oct '14

08 Oct '14

Hello all! We have 4 net app systems a FAS2020, 2 x FAS2020a and one FAS2040. The FAS2040 had a NVRAM battery losing power until it shut down because of the battery not having power. Purchased a battery, replaced, and still no charge. Now we though the problem was the controller, so i purchased a new controller, replaced CF CARD and inserted back in the chassis, noticed battery wasn’t charging either, now controller has shut down again and battery is not charging. Could someone give me a light on this one? Firmware issue? Thanks again!

5 6

FAS2040 config
by Camillo Gornati 06 Oct '14

06 Oct '14

Hello all! What is the best/most popular way to connect and configure network on a FAS2040? We have 2 controllers, e0a-e0d on wach controller. LACP trunk on e0a-e0b on both controllers each one connected to a diff. switch. Dont know exactly what to do with e0c, e0d. Should i add to the actual trunk and connect to a diff. switch? Should i create a new trunk and connect to what? Thanks very much in advance.

1 0

looking for thoughts on NetApp high end storage
by Rhodes, Richard L. 02 Oct '14

02 Oct '14

Hi Everyone, We currently use some low end IBM NSeries for a specific application. All of our other storage is from a large three letter vendor. We have never really considered NetApp for our high end Tier 1 storage. For our T1 three letter vendor storage we replicate bi-directionally between two datacenters. Years ago we used synchronous replication, but at the last rollover have changed to async replication due to write latencies. It's worked very well. The storage systems are roughly 5-10 seconds out of sync. I was looking at what OnTap supports for this kind of work. I see that in 7-mode it supports sync and semi-sync. Semi-sync seems interesting for what we do, except that you have to replicate within a Consistency Point. You have until the other half of nvram fills up to complete the current CP with replication. When I looked at C-mode, I can find no mention of sync or semi-sync at all. Q) Does C-mode support semi-sync? Q) If not, can normal async snapmirror support replication into the 10-15 second lag range? (note - T1 storage is almost all large Oracle DB's) Q) Any other idea on how you would implement a low lag async replication with NetApp? Thanks Rick ----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.

2 1

Replace controller
by Camillo Gornati 01 Oct '14

01 Oct '14

Hi all! In our environment, we have a FAS2020a and a FAS2020. FAS2020a had one controller bad, we installed a replacement we had, installed old the CF CARD, but system won’t boot, it says there is no disks for root volume. That is because all disks are assigned to old controller. How could we assign those disks to new controller without losing any data? Thanks in advance Camillo

6 8

CVE-2014-6271: remote code execution through bash
by Douglas Siggins 26 Sep '14

26 Sep '14

Looks like we are waiting for word from Netapp on this one: netapp% uname -a Data ONTAP xxxxxxx 8.2.1 Data ONTAP Release 8.2.1 amd64 netapp% Wed Sep 24 15:00:00 EDT [bosnamail20:kern.uptime.filer:info]: 3:00pm up 41 days, 39 mins, 603179098 NFS ops, 0 CIFS ops, 0 HTTP ops, 0 FCP ops, 0 iSCSI ops env x='() { :;}; echo vulnerable' bash -c "echo this is a test" vulnerable this is a test netapp% bash --version GNU bash, version 3.2.48(1)-release (x86_64-pc-freebsd) Copyright (C) 2007 Free Software Foundation, Inc. I doubt there are many vectors that this vuln would work, but still a little concerning.

4 3

7-mode / cDOT Co-existence?
by Ray Van Dolson 25 Sep '14

25 Sep '14

Have searched previous discussions on this, but seems like this is a bit of a moving target. Apologies if this has already been addressed to death. Considering FAS purchases now that N-Series is going away. Wanting to pull the plug and go cDOT on the new systems, but concerned about interoperability with the N-Series filers still on 7-mode. Biggest concern: Can I SnapVault from 7-mode to cDOT? It sounds like there's a way to do this via a migration tool, but less clear if regular 'ol SnapVault and SnapMirror work between the two platforms. Really hoping it works as the co-existence option will make our lives a lot easier. Ray

2 1

Balance monitoring Windows clients
by Andrew Laurence 24 Sep '14

24 Sep '14

Hi all, The documentation states that Balance needs a Windows administrator-level account. Will _only_ an administrator-level account do? By comparison, on a 'nix machine it doesn't actually need complete sudo/root access. It only needs these commands from sudo: /sbin/lvm, /sbin/scsi_id, /sbin/dmsetup Surely a more restrictive permissions set will fill the need on Windows as well? -- Andrew Laurence Office of Information Technology atlauren(a)uci.edu University of California, Irvine

1 0

What to do with 4 x 3020s and 9 Shelves?
by CH 24 Sep '14

24 Sep '14

Company closes and sells off their hardware…..before releasing the shelves they move around the drives in the shelves (for “security”) so now they cannot boot or more importantly get any license info to reinstall OnTap…. Anyway around this? I hate to trash all this hardware.

4 5

WideLink SymLinks on CDOT
by jamesr 22 Sep '14

22 Sep '14

All, Since you were all so helpful last time with regards to my TSM questions (and thanks for that!) I have run into another problem I'd like to pick your collective brains over. We have a CIFS only environment running CDOT and have a requirement to provide Directory SymLinks in a users home directory. I've managed to find fairly decent documentation on how to do this on 7-Mode systems but it seems lacking for CDOT. We use to use mklink (or some other powershell hackery) to create the symlinks but this doesn't work when talking to the new CIFS SVM. Has anyone managed this? Do you have a recipe we can follow to implement this? I've managed to create the Symlink translation entry like so: PS > Get-NcCifsSymlink CifsServer ShareName UnixPath CifsPath Locality ---------- --------- -------- -------- -------- REMOTE_SERVER REMOTE_SHARE /vol04/USERNAME/SymLink-Src/ / widelink But I think the next step is to create a 'real' unix type symlink on /vol04/USERNAME/SymLink-Src/ however I can't see how to do this. The file-create-symlink OnTAPI API call doesn't (seem?) to exist for CDOT (yet?). The only other possible option as I see it is to configure NFS and then mount the drive over NFS to create this symlink but I would prefer to avoid this as we don't have a requirement for NFS on these shares currently. Any help is greatly received as always! Cheers. -- James 'BR' Ray

2 1

snapvault memory allocation error
by Rhodes, Richard L. 22 Sep '14

22 Sep '14

Hi Everyone, Over the weekend we had a snapvault backup fail with memory allocation errors on the snapvault destination. This error occurred twice on the same volume, then hasn't come back. Can not allocate memory. (memory limit reached) (Cannot allocate memory) I run snapmirror and snapvault on all our volumes, but do it one operation at a time - NO concurrent snapvault or snapmirror operations. I search NOW and didn't come up with anything. This occurred on this particular volume twice in a row (6 hours apart - backups run every 6hours), not on any other volumes. This volume is 410GB with 900k inodes - not even close to our biggest volumes. So this error is not related to size (capacity or num inodes), but seems specific to this volume. Filers: IBM N3220 (NetApp FAS2240-2) OnTap: 8.1.2P1 7-Mode Here are the full messages on the SV destination filer. ___ Sat 09 20 07:43:05 EDT [rshd_0:debug]: root@[172.17.170.34_60065]:IN:ssh2 shell:SSH INPUT COMMAND is snapvault snap create -w v_fnce08p_cifs v_fnce08p_cifs tgt Sat 09 20 07:43:05 EDT v_fnce08p_cifs xfer:v_fnce08p_cifs Target_start dst Sat 09 20 07:43:06 EDT isnapr0664a:/vol/v_fnce08p_cifs/q_fnce08p_cifs isnabk0665a:/vol/v_fnce08p_cifs/q_fnce08p_cifs Request (Update) dst Sat 09 20 07:43:07 EDT isnapr0664a:/vol/v_fnce08p_cifs/q_fnce08p_cifs isnabk0665a:/vol/v_fnce08p_cifs/q_fnce08p_cifs Start ___ Sat 09 20 07:50:43 EDT [isnabk0665a:replication.dst.waflErr:error]: SnapVault: destination transfer from isnapr0664a:/vol/v_fnce08p_cifs/q_fnce08p_cifs to /vol/v_fnce08p_cifs/q_fnce08p_cifs : memory limit reached:Can not allocate memory. dst Sat 09 20 07:50:43 EDT isnapr0664a:/vol/v_fnce08p_cifs/q_fnce08p_cifs isnabk0665a:/vol/v_fnce08p_cifs/q_fnce08p_cifs Defer (memory limit reached) (Cannot allocate memory) dst Sat 09 20 07:51:00 EDT isnapr0664a:/vol/v_fnce08p_cifs/q_fnce08p_cifs isnabk0665a:/vol/v_fnce08p_cifs/q_fnce08p_cifs Request (Retry) dst Sat 09 20 07:51:01 EDT isnapr0664a:/vol/v_fnce08p_cifs/q_fnce08p_cifs isnabk0665a:/vol/v_fnce08p_cifs/q_fnce08p_cifs Restart (@ 929692 KB) dst Sat 09 20 07:51:04 EDT isnapr0664a:/vol/v_fnce08p_cifs/q_fnce08p_cifs isnabk0665a:/vol/v_fnce08p_cifs/q_fnce08p_cifs Abort (memory limit reached) (Cannot allocate memory) dst Sat 09 20 07:51:04 EDT isnapr0664a:/vol/v_fnce08p_cifs/q_fnce08p_cifs isnabk0665a:/vol/v_fnce08p_cifs/q_fnce08p_cifs Rollback_start slk Sat 09 20 07:51:30 EDT state.qtree_softlock.v_fnce08p_cifs.0001b0a2.252.q_fnce08p_cifs.src-qt.isnabk0665a:/vol/v_fnce08p_cifs/q_fnce08p_cifs.00000000.-01.1 Softlock_add (Transfer) dst Sat 09 20 07:51:37 EDT isnapr0664a:/vol/v_fnce08p_cifs/q_fnce08p_cifs isnabk0665a:/vol/v_fnce08p_cifs/q_fnce08p_cifs Rollback_end (42928 KB) slk Sat 09 20 07:51:37 EDT state.qtree_softlock.v_fnce08p_cifs.0001b0a2.252.q_fnce08p_cifs.src-qt.isnabk0665a:/vol/v_fnce08p_cifs/q_fnce08p_cifs.00000000.-01.1 Softlock_delete (Transfer) dst Sat 09 20 07:51:38 EDT isnapr0664a:/vol/v_fnce08p_cifs/q_fnce08p_cifs isnabk0665a:/vol/v_fnce08p_cifs/q_fnce08p_cifs Coalesce_end dst Sat 09 20 07:51:38 EDT isnapr0664a:/vol/v_fnce08p_cifs/q_fnce08p_cifs isnabk0665a:/vol/v_fnce08p_cifs/q_fnce08p_cifs Coalesce_start (isnabk0665a(1896301030)_v_fnce08p_cifs-base.2) dst Sat 09 20 07:51:38 EDT isnapr0664a:/vol/v_fnce08p_cifs/q_fnce08p_cifs isnabk0665a:/vol/v_fnce08p_cifs/q_fnce08p_cifs Coalesce_start (isnabk0665a(1896301030)_v_fnce08p_cifs-cleanup.0) dst Sat 09 20 07:51:40 EDT isnapr0664a:/vol/v_fnce08p_cifs/q_fnce08p_cifs isnabk0665a:/vol/v_fnce08p_cifs/q_fnce08p_cifs Coalesce_end ___ Sat 09 20 07:51:41 EDT [rshd_0:debug]: root@[172.17.170.34_60540]:IN:ssh2 shell:SSH INPUT COMMAND is snapvault status -l /vol/v_fnce08p_cifs/q_fnce08p_cifs tgt Sat 09 20 07:51:41 EDT v_fnce08p_cifs xfer:v_fnce08p_cifs Target_create_snapshot (v_fnce08p_cifs.0) tgt Sat 09 20 07:51:41 EDT v_fnce08p_cifs xfer:v_fnce08p_cifs Target_end vol Sat 09 20 07:54:43 EDT v_fnce08p_cifs Snapshot_replace (v_fnce08p_cifs.0) Thanks! Rick ----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.

1 0

Jump to page:

2026

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