Depending on your capcity requirements, be sure to also check out the AFF C190, but make sure you understand the limits around expansion.  ... View more

As SpindleNinja indicated, you'll have to recreate the IFGRP. If a0b has the correct VLAN(s) on it, migrate your LIFs form a0a to a0b, tear down a0a and rebuild from there. VLANs on top of IFGRPs are also a good idea, per SN. ... View more

To expand on what TMAC said, why not wait until 9.6 goes GA? Also, check out Upgrade Advisor inside of ActiveIQ, that'll help you with what you need to check before an upgrade. ... View more

Thanks to software-based disk ownership, as netrz mentioned, this is fine.   The math around stacks is easy and is as follows: Each stack requires two ports per controller, ie: four in an HA-pair for MPHA.   A FAS8020 equipped with 2 x 4-port SAS cards per controller, along with its on-board ports would have 10 SAS ports per controller and could have up to 5 stacks of disk. The limit however of 480 target devices (disks/SSDs/LUNs) still exists and is a hard limit. ... View more

If you don't already the licenses, I wouldn't advise buying it now as the model FAS you have is going End of Support in 12 months. You would be better off contacting your local NetApp sales rep and discussing a new appliance or looking at one of the software-defined versions like ONTAP Select or Cloud Volumes ONTAP. I'm sorry I don't know what you're saying about e0M, but if you paste the contents of the file /etc/rc in here, I can see what you've got setup. ... View more

Hi Bob,   You're right, if you're using domain as your primary authentication method for ssh, there is not secondary option. If you're using local account or nsswitch as your primary method, then you can use publickey for your secondary. ... View more

Have you tried rebooting the node yet? Sounds like it might need it and better to reboot it under your terms than if it decides to core dump and reboot on its terms. If you have already rebooted it, I suggest opening up a support ticket. ... View more

My assumption here is that this device is no longer under support but if it is, I would highly recommend getting c-mode licensing and upgrading it to 9.1, the latest that is supported. Once you're on 8.3+, you can do Advanced Disk Partitioning and recoup a lot of space lost to root aggregates.   However, since my assumption is that it is no longer under support, then we have to work with what you've mentioned. Since you're on 7-mode, there's no requirement for a dedicated root aggregate so you're going to lose 2 disks to RAID for either controller. If you're trying to squeeze as much space out of it as possible and you can forgo high-availability, I would consider removing the second controller and devoting all 12 disks to the now, single-controller. That way you would lose 2 disks to RAID and keep one spare,  giving you just under 4TB of usable storage. Otherwise, if you want to keep HA, I would do 6 drives per controller, losing 2 to RAID and 1 spare each. You'll end up with about 1.3TB of usable storage per controller. You could also consider running RAID-4 and you'd end up with about 1.8TB of usable storage per controller.   Since you're using iSCSI, best practice is to not use LACP. Assign IPs to all four 10Gig ports and let MPIO sort out pathing.   I'm not sure what you mean about e0M being partners in the same subnet. If you're saying they're in the same subnet, that's fine, your out of band module will also be in that subnet, I can't remember if it was an SP or BMC on that model, but the wrench port has two interfaces behind it, e0M and your out of band.   You may want to spend some time reading the documentation located here. ... View more

While I'm not 100% here, this is worth a shot. vSphere 6.7 disabled TLS 1.0 and 1.1, I would try re-enabling 1.1 and seeing if that resolves the issue. Have a look at this VMware document. ... View more

The exams are constantly updated to reflect the new and deprecated feature, roughly on a yearly cadence at this point. The original NCDA for Clustered ONTAP was released in 2013 and was labelled NS0-156 and has been incrementing since. The last NCDA 7-mode exam, now deprecated was NS0-155.   At some point this exam will collide with other specializations and a re-numbering will likely happen. ... View more

That's an interesting one, are you able to create a new, encrypted volume from scratch on either node?   I'm wondering if this is support ticket-worthy, the only hardware requirement as far as I know is the processor needs to support the AES-NI instruction set which the one in the FAS2750 definitely does.  ... View more

It might be easier if you elaborate on why you need to know this. You could try mounting /vol/vol0 and looking at the meta data for vol0 as well as any files located therein. But depending what you're actually trying to figure out, you can also login to https://activeiq.netapp.com/ and find out when the device shipped, see the screenshot. ... View more

My take on the documentation is that no matter what method of primary authentication you're using, local account or LDAP/NIS, the second factor can only be publickey. If you want to use an external Identity Provider other than AD/LDAP/NIS, the only applications supported are http and ontapi, not ssh. You can verify this yourself by going to the command line and typing:   security login create -user-or-group-name "domain\group" -application ontapi -authentication-method ? Then do the same as above but swap ontapi for any of the other applications. ... View more

Hi there,   I like to do these things at the command line:   security login create -user-or-group-name "domainname\ROGroup" -application http -role readonly -vserver svm_95_nas -authentication-method domain You may want to do multiple entries for the application modifier if you want them to have access other methods as well, typically "http, ontapi, ssh".   Then add those users to the AD Group called "ROGroup" or whatever you call it in your domain. ... View more

What's the status of this issue?  ... View more

Since you used some other CIFS license, it's likely you used the improper Base license as well, try applying the following Base license:   SMKQROWJNQYQSDAAAAAAAAAAAAAA Which should change your cluster serial and make CIFS work. ... View more

Since I'm not internal to NetApp I am unable to login to that IP, I did however look up the licenses here and the appropriate one is actually:   KUUNCAFTVDDCMAXAGAAAAAAAAAAA Not the one you entered. ... View more