Hey everyone,

is there a possibility to recover/newly create a failed node with the help of the ONTAP Select deploy VM?

In my scenario I'm using the ONTAP Select Deploy VM in version 2.6 and set up a 2-Node Cluster in evalualtion mode.

I then deleted one node directly on the ESXi server to simulate a crash of that ESXi Server.

After using the "deloy refresh" button the deploy VM is aware of the missing cluster node, but I cannot find a way to "reinstall" a new node inte the existing 2-Node cluster.

Any suggestions here?

Thanks in advance

Hi,

I have many Netapp clusters using software version 8.3.2 at the moment and proceed to NDUs to reach version 9.2P1. I did a 2-step upgrade as I had to upgrade to version 9.1XX prior to reaching 9.2XX.

The hardware is FAS2552.

The NDUs themselves ran fine but what surprised me was to see that they generated :

- temporary critical PSU-related alerts (Power supply) that disappeared after 20 minutes --> it happend for the 2 clusters I upgraded
- many emergency events such as "link has gone down unexpectedly", or "all links down", or "controller failover is not possible, version mismatch", or finally "Out of cluster quorum"

It appears to me that these are normal behaviour (except the "links has gone unexpectedly") and standard monitoring events, but I am wondering if this will appear for all upgrades ? What is your experience ?

I precize that I do not have further issues, but just want to ensure that this is totally fine.

Thank you in advance.

I need to provision security access via AD groups as we have a ot of admins that need access.

If I use the following commands to provision security, the commands are accepted by ONTAP but AD credential sets will not grant access to putty or GUI.

security login create -vserver NFS -username "DOMAIN\AD Group" -application ontapi -authmethod domain -role admin
security login create -vserver NFS -username "DOMAIN\AD Group" -application ssh -authmethod domain -role admin

Kindly help ...

I cannot seem to find a way to enable Access Based Enumeration (ABE) via the NetApp Powershell Toolkit v4.5 and OnTap 9.0P2. Can anyone tell me how?

I went to the system manager and enabled it there, so it does show up in the share properties from the CLI:

prdc-ramp-01::> cifs share show -share-name ShareName1 -instance

                                      Vserver: vs0
                                        Share: ShareName1
                     CIFS Server NetBIOS Name: CifsServerName1
                                         Path: /ShareName1
                             Share Properties: access-based-enumeration
                                               browsable
                                               changenotify
                                               oplocks
                                               show-previous-versions
                           Symlink Properties: enable
                                               read_only
                      File Mode Creation Mask: -
                 Directory Mode Creation Mask: -
                                Share Comment: -
                                    Share ACL: Everyone / Full Control
                File Attribute Cache Lifetime: -
                                  Volume Name: ShareName1
                                Offline Files: manual
                Vscan File-Operations Profile: standard
            Maximum Tree Connections on Share: 4294967295
                   UNIX Group for File Create: -

But, if I use the PSK to get the Share Properties, it doesn't show up:

PS E:\Powershell> $Share | Select-Object {$_.ShareProperties}

$_.ShareProperties
------------------
{oplocks, browsable, changenotify, show_previous_versions}



I would think that this would be a value for the ShareProperties, but the help file for the Add-NcCifsShare doesn't even list it as an option:

-ShareProperties <String[]>
The list of properties for this CIFS share. Possible values:
"oplocks" - This specifies that opportunistic locks (client-side
caching) are enabled on this share.
"browsable" - This specifies that the share can be browsed by
Windows clients.
"showsnapshot" - This specifies that Snapshots can be viewed and
traversed by clients.
"changenotify" - This specifies that CIFS clients can request for
change notifications for directories on this share.
"homedirectory" - This specifies that the share is added and enabled
as part of the CIFS home directory feature. The configuration of this
share should be done using CIFS home directory feature interface.
"attributecache" - This specifies that connections through this share
are caching attributes for a short time to improve performance.

Let's say we have an SVM with total of 10 Volumes, and 5 of them is required to DR. I can either take out 5 no DR required volumes, and convert the SVM to SVM-DR. 

For these 5 no DR required volumes, I would have to put them to a new created SVM, and then all LIF's to access these volumes will have to be different, and therefore or user access, either to NFS or CIFS will have to be also changed as new SVM/LIF's got changed. 

Am I correct?

I am a NetApp newb of the first degree. I inherited these things with zero knowledge and a mandate to keep it running. I am extra lucky in my learning curve, in that the support has been allowed to expire and will not be renewed.

I have a FAS202 with two additional shelves. The software is DataOnTap 7.3.7P1. I am running two aggregates in addition to the OS. One of the aggregates is a RAID4  with three raid groups of four disks each. All the drives are 2TB drives of the exact same model and manufacture.

I returned from holdiay to find that my aggregate was in a failed/partial condition. In actuallity, 6 disks failed while I was on holiday. That'll teach me I guess. Calling up the condition of the aggregate, I see that one of the drives has failed but I have no idea which one to swap. I replaced two of the drives and they both were listed with bad labels. I cleared the label off of one of the drives that I replaced and made it a spare (I read later that this was a poor choice) so I haven't done anything with the other. I also have not replaced any of the other failed drives in the system since every single one shows this "bad label" error and I am not sure how to fix that before putting a drive in.

Additionally, I see that my parity disk on RG1 is stuck at 83%. I am no storage guru, but I am pretty sure that can't be good.

I am fortunate that I had only moved about 30 out of about 120 VMs to this storage so, there's that. I would rather NOT have to rebuild 30 VMs though. I would be eternally grateful if someone could help me find the magic to do a coupel things:

Tell me how to properly prepare a previously utilized disk for placement into the FAS2020 so that it sees a disk to use in the failed array

Determine which disk to replace in the failed array

Get the repair process started so that I might recover my failed aggregate.

Thanks in advance.

I perform test at lab, if fact is prepare for 1 of my customer want to implement 7m tiebreaker on production.

my lab.

metro cluster fmc ontap 8.2.5 7m

windows 2008 - OCUM 5.2R1 - MCTB 2.4

when i turn off power on 1 of controller and 2 brocades from 1 site.

CFOD is not trigger and sometimes it show on ocum but when i access to live nodes, it not takeover.

how to check on tiebreaker in debug mode to make sure CFOD can perform?

I would like to mount a volume from another NAS via iscsci on my Netapp filer with NetApp Release 8.2.4P4 7-Mode and then create shares on this volume. This would allow me to offer more storage to my clients without buying new hardware (I want to use an already existing NAS) and the users would not have to change anything in their configuration, since I would migrate some shares to the iscsi target.

So the question is, whether my Netapp Filer can be usesd as a iscsi initiator (client). Is it possible? If not, are there altenatives for achivieng a similar result?

Kind regards,

Andreas

Hello,

I tried searching documentation without success.

Is it possible to convert a non snaplock aggregate to snaplock enterprise mode? (Running Ontap 9.1P9, two node bridge attached metrocluster)

Thank you 

Lorenzo

Looking for documentation to configure boot from SAN from a HP-UX Itanium HP rx2800 i4 Itanium Servers.   2port 8GB AH401A Qlogic HBA  HPUX 11i V3.  NetApp A300 

Hello,

We have a NetApp FAS2220 running Ontap 8.1.4P1 7-Mode, and we're now testing it on Windows 10.
We have a slow performance problem when opening MS office files on CIFS share from Win10.

The test file is Excel 2010 document which size is 1.5MB.
Antivirus software and other management software is all the same between Windows 7 and 10.


Test result is as follows:

1. From inside our office network (via Wifi)

When opening CIFS share folder using Windows Explorer, it takes alittle bit more time to display all files in the folder.
Average time to open the test file is below.
---------------------
Win7 ---> 2-3 sec
Win10---> 3-4 sec
---------------------

2. From outside our office network (via SSTP-VPN over 4G)

The performance is getting slower. The average time to open the file is below.
---------------------
Win7 ---> 10-15 sec
Win10---> 25-30 sec
---------------------
#You can be frustrated when accessing the file from outside office network.


This problem seems to occur only on office documents, there are no slow down when accessing other file type, such as PDFs.
And we're testing Windonws10 using MS Surface pro and HP Laptop, but the result is the same.

Have you seen similar problem before and know any solution to speed up the performance?

Thank you.

When upgrading OnTap minor release versions (P1 -> P5), the following cmdlet works as expected:

Invoke-NcClusterHaTakeover -Controller $connectedController -Node $controllerBNode

When upgrading OnTap major release versions (9.2 -> 9.3), the following cmdlet produces the following error message:

Failed to initiate takeover. Reason: version mismatch. Note: If you are performing a Data ONTAP non-disruptive upgrade or downgrade, use the (privilege: advanced) 
"-option allow-version-mismatch" parameter. 

This is all well and good and so I add AllowVersionMismatch switch parameter as follows:

Invoke-NcClusterHaTakeover -Controller $connectedController -Node $controllerBNode -AllowVersionMismatch

But receive the same error message:

Failed to initiate takeover. Reason: version mismatch. Note: If you are performing a Data ONTAP non-disruptive upgrade or downgrade, use the (privilege: advanced) 
"-option allow-version-mismatch" parameter. 

I'm hoping it is obvious what I missing and/or how I elevate to "set -privilege advanced" from the Netapp Powershell CLI.  I have considered performing this takeover step with Invoke-NcSSH, but I am hoping there is a more elegant way and that I am just missing a step or something obvious.  (Invoke-NcSsh option mentioned here: https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/Do-we-have-any-DataONTAP-powershell-toolkit-cmdlet-to-set-privilege-level-for/td-p/116795)

The parameter help talks about cleanly halting the node to be taken over but this doesn't quite make sense to me - is it a clue to someone else?  I am not familiar with proatively halting a node during a NDU:

    -AllowVersionMismatch
        If specified, allow takeover if the partner was running an incompatible operating system version and was cleanly halted.  This option is used for non-disruptive upgrade (NDU).

Thanks in advance for your insight!

I'm trying to create a 2 node cluster on ESXi 6.5u1 with Ontap Deploy 2.6.1 (9.3) on local storage in the nodes.

The virtual switches are vDS but I also tried using standard vSwitches as a test without any luck.

I can step through all the deployment options without issue and the network testing also completed.

However, after it deploys the node it fails when creating the cluster.

The error is 

status': 'failed', 'current-status-message': "Error during external mediator mailbox setup for local node NODE-1, Reason: entry doesn't exist", 'is-complete': 'false'}]

I'm not seeing any errors before that.  I can ping all the node IP's.  And I've tried several different network configs (like combining the managment/data networks and seperating) 

Any thoughts?  I did some seraching on netapps KB's but did not see much at all.

I've been playing around with Ontap Select 9.3 for our remote branch solution.

I've been able to get it installed and running and have started  my preformance testing.

Each node has an internal Intel NVME PCI-E Flash card.  I've deployed the 2 node cluster using the "small" config. 

I'm seeing terrible write latency....steady 200ms+ when preforming a storage vmotions.  Volumes are presented as NFS like our physcal netapps are.

I can actually storage vmotion faster between two old test SATA Netapp's than I can to/from the Ontap Select w/ NVME.

Looking at the preformance graphs shows the underlying NVME datastore has sub 1ms latnecy between the Node VM and the datastore.

So it looks like the latency is within the ontap stack.

I certianly woud not expect baremetal speed.  But considering we are using very fast NVME PCI-E cards I'd expect much better preformance than we are seeing.

This same gear was also used for a vSAN test and its preformance was way way higher.

So is there somthing I'm missing?   I do see the virtual e0a adapters are set to 1000GB full but changing it to 10GB Full did not seem to help.   These host are all connected via 40GB Mellanox switches.

I've also tried disabling dedup/compression on the volume but that did not see to any impact either.

Hi all

I am reletively new to NetApp and ONTAP so please be gentle...

I work for a hospital and we have a Netapp storage system running in 7-Mode using ONTAP 8.2.4P6, a previous colleague of mine used to manage this system and unfortunately became a single point of failure once he left.

We are trying to find out when one of our shelves was installed, can anyone advise if this is possible?

Thanks

Richard

I just setup a new netapp server running 7mode and for some reasons I am unable to assign unix group permissions on the qtrees that I have created. I am using a Red Hat server that is currently running as a NIS. I have the volumes automounted so I am able to access them but when I try and run a chgrp or chown I get an error saying invalid group. I have used those commands to assign group permissions to local folders on the server with no issues. Is there something I need to do on the netapp side so that I can assign these group permissions?

Thank you.

Hi All,

We added 2 nodes (node3 and node4) and configured the management lifs. However I cannot even ping the gateway from the managament lifs for Node3 and node4.  Any help will be appreciated.

           Logical   Status     Network           Current       Current Is

Vserver     Interface Admin/Oper Address/Mask       Node         Port   Home

----------- ---------- ---------- ------------------ ------------- ------- ----

Cluster

           Node1_clus1 up/up 169.254.209.114/16 Node1     e1a     true

           Node1_clus2 up/up 169.254.218.15/16 Node1     e2a     true

           Node3_clus1 up/up 169.254.233.0/16 Node3         e0c     true

           Node3_clus2 up/up 169.254.242.42/16 Node3       e0e     true

           Node4_clus1 up/up 169.254.72.231/16 Node4         e0c     true

           Node4_clus2 up/up 169.254.85.227/16 Node4         e0e     true

           Node2_clus1   up/up  169.254.126.40/16 Node2         e1a     true

           Node2_clus2   up/up   169.254.60.62/16   Node2         e2a     true

Vserver2

           test2       up/up   136.171.87.106/24 Node1     a0a-1187 true

vserver1

           Node1_icl1 up/up   136.171.211.105/24 Node1     a0a-211 true

           Node1_mgmt0 up/up 136.171.211.101/24 Node1     a0a-211 true

           Node3_mgmt1 up/up 136.171.211.107/24 Node3       a0a-211 true

           Node4_mgmt1 up/up 136.171.211.109/24 Node4       a0a-211 true

           labnas00_mgmt0 up/up 136.171.211.100/24 Node2         a0a-211 true

           Node2_icl1   up/up   136.171.211.104/24 Node2         a0a-211 true

           Node2_mgmt0   up/up   136.171.211.102/24 Node2        a0a-211 true

Vserver3

           Node1_lif1 up/up   136.171.211.200/24 Node1     a0a-211 true

           Node2_lif1   up/up   136.171.211.201/24 Node2         a0a-211 true

I am using Netapp Ontap 9.1 and WFA  4.1.0.0.2.

I want to enable/disable encryption using Netapp WFA but I am not able to see option to enable/disable encryption on volume

We are plannng to upgrade ONTAP to 9.2P2 from 9.1P6. Last year when we were upgrading from 9.0RC1 to 9.1P6, we we were able to see HP SN1000Q in compatibility checks with required driver versions. Now not able to find them in IMT. Host OS is ESXi 6.5 and is compatible to ONTAP 9.2 but not able to find driver compatibility.
HBAs details are as mentioned below, 

HBA model - HP SN1000Q

Driver - v2.1.50.0

Firmware - v8.02.00 and v8.02.51, planning to upgrade to 9.2P2. How to check their compatibility now ? Please help on this

Hi All,

      I'm looking to integrate our clusters into AD so that when we log into the CLI/GUI we can do so with our AD logons.  Maybe I'm missing something but the only thing I can see in the documentation is that you can set up a domain tunnel from a data vserevr.  This isn't what I'm after as when you log onto the CLI to admin the filer you login to the cluster vserver.  I've not really seen much mentioned of RADUIS apart from using that as the authentication method for CHAPS using ISCSI.

Could anyone point me in the right direction of getting ontap 8.3.2 working with AD lognos for the cluster level CLI. 

Cheers

Chris