holy necropost, Batman!   You *do* realize that the post you replied to is almost 10 years old? It was on a 7-mode system so your links are not helping much. Also, Space Allocatiuon has already been suggested (and ruled out) as a reason a few posts earlier. ... View more

Sorry, but this is totally incorrect. The link you posted is for ONTAP Tools for vSphere, not for ONTAP itself. Please do not post irrelevant answers as these may confuse the OP ... View more

@bwells wrote: I was able to get the 9.5 simulator working in QEMU/KVM.  I used virt-manager and GNS3 to manage it.   1. Convert vmdk's to qcow2 format using qemu-img 2. Move qcow2 files to a location where virt-manager can find them or browse to 3. Create your vm in virt-manager and select import disk option 4. Add disk one  5 Set memory to no less than 5 gb of ram and cpu to no less than 2 6. Name it and select customize 7. Add remaining qcow2 disks and make sure they are all ide 8. Add 3 more NICs that are e1000  9. Make sure you change from Spice to VNC 10. Boot VM 11. When "CTRL-C for boot menu", hit CTRL-C 12. In boot menu select option 4 (disk have been setup for vmware and we need to zero those out) 13. Follow all netapp procedures from there This worked fine for me using both in virt-manager and GNS3 using Ontap 9.5.  This works, but from my experience it is very brittle: If the VM crashes for any reason (i.e. any improper shutdown), it will not come back up and panic, with lots of errors in the md-devices and being unable to mount its root directory.   This also happens for VMware and makes it very hard to actually use the simulator (i.e. you cannot show how the system recovers from an unexpected failure, because, well, it usually won't recover at all 😉 )   I think this works better with ONTAP select, but setting that up without the deploy VM is very undocumented   Does anyone have a solution for that problem? ... View more

Hi Sean,   what bootargs do you set in the env file? Is there a list somewhere on how to configure, say, 2-node clusters with IP addresses and all?   Maybe you could share your script?    thanks -Michael ... View more

Have you ever found a solution for that issue? We have seen the same issue occur recently and we're equally baffled. Our config is very similar ... View more

First, do not use "mixed" security style. Ever. It only leads to problems. Use the permission style of the majority of users/accesses. When in doubt, use NTFS. But not mixed.   Second, you need something called "user name mapping" configured on your cDOT system, where you map UNIX users to Windows users. This is a required step. You can read about it in the NFS File Access Reference Guide (here) and in the CIFS File Access Reference Guide (here). Note that it might be a bit much to take in if you're completely new to ONTAP.... Your partner that sold you the system should be able to help you with the implementation   -Michael ... View more

You can do a (disruptive) head upgrade from the single node to one of the new systems configured as single node. Then, when the cluster is running on the new controller, add the second node (HA partner) to it to make it an HA pair.   Or, find a (temporary) second controller of the same model as the single node you have (you can borrow them through your Partner from NetApp, it's called Swing Gear), temporarily make a 2-node cluster out of your single system, and then use the regular way to upgrade your cluster hardware and remove the old controllers   -Michael ... View more

@Overz wrote:   So than as you initially suggested the only way to solve this isue is to add cables.   There is another option: You can set the failover policy of that lif to "disabled". That will signal the system that you do not intend this interface to failover and it shuts up the warning message. ... View more

If you're a complete NFS shop, what do you need CIFS for? If it's only for 1 share that 2 or 2 users access, you can also use Microsoft's NFS for Windows, for example.   That being said, it's been possible for a few months now (since OnTap 9.0) to run an SVM in Workgroup mode without AD. See the man page for the "vserver cifs create -workgroup" command.   -Michael ... View more

There is the volume explore command that is available from the cluster shell.   But it's a diag-mode command and can potentially be dangerous as it allows you to alter (i.e. destroy) arbitrary data on your disks, so be careful with it    The syntax can be found in the man page and with "volume explore help", but the "scope" parameter is rather complicated, so I'll just mention the general syntax for listing a directory: volume explore -format dir -scope <vserver>:<volume>/<path...>   For example: cl1::*> volume explore -format dir -scope Infra:iso/Microsoft found 1454.64/Microsoft to be inode 1454.96 directory data from block 1454.96@0 at location 1454@42693152b entry 0: inum 96, generation 156613115, name "." entry 1: inum 64, generation 1565554427, name ".." entry 2: inum 97, generation 156630775, name "Windows 2008R2" (8.3 "WINDOW~1") entry 3: inum 98, generation 156631151, name "Windows 2012R2" (8.3 "WINDOW~2") entry 4: inum 101, generation 156635340, name "Windows 2012" (8.3 "WINDOW~3") entry 5: inum 103, generation 156640115, name "Windows 2003R2" (8.3 "WINDOW~4") entry 6: inum 20097, generation 156643561, name "_WSUS Update ISOs" (8.3 "_WSUSU~1") entry 7: inum 19467, generation 157064132, name "Windows 8.1" (8.3 "WINDOW~1.1") entry 8: inum 19468, generation 157064706, name "Windows 7" (8.3 "WINDOW~5") entry 9: inum 19470, generation 157069086, name "Windows 8" (8.3 "E0K0000~") entry 10: inum 19475, generation 157471053, name "Windows 2003" (8.3 "K0K0000~") entry 11: inum 19477, generation 157475446, name "Windows 2008" (8.3 "M0K0000~") entry 12: inum 29674, generation 164062243, name "Windows 10" (8.3 "AWT0000~") entry 13: inum 29675, generation 415758740, name "Windows 2016 TP5" (8.3 "BWT0000~")   You can also read file contents, file metadata (timestamps etc.), and even system files with that command:   Metadata: cl1::*> volume explore -format inode -scope Infra:iso/Microsoft found 1454.64/Microsoft to be inode 1454.96 inode 1454.96 generation 156613115 at location 1454@45369601b+2368:192 type 2.3, flags 0x02, flags2 0x00 size 4096, blockcount 1, future_blocks 0, level 1 umask 0777, uid 0, gid 1, xinode 29673, sinode 0, nlink 14, av-gen-num 0 ctime 28-Apr-2016 14:11:12, mtime 28-Apr-2016 14:11:12, atime 03-Feb-2017 15:48:14 ptr[0]: pvbn 1308139785, vvbn 42693152 Note that if your directory or file contains spaces, you cannot access it with that command, you have to use the 8.3 short name or inode number then.     hope that helps   regards -Michael ... View more

The SVM has to be in an AD domain, otherwise you will not get any CIFS functionality.   The clients that connect to the NetApp can be either other AD members (domain computers) or standalone computers (i.e. computers running in Workgroup mode). Note that if you try to connect to the SVM on the NetApp cluster from a computer which is NOT part of the same domain, you will have to supply a username and password to connect. This can be either a domain user (using "DOM\User"-style usernames) or a local user created on the SVM (see the vserver cifs users-and-groups local-user create command). This is the same, actually, as with Windows servers and computers without any NetApp involved   Also, if you really need CIFS with Workgroup style authentication, it is possible that this might be added to Data OnTap at a later date (all documentation, for example, says it is "not yet available" or "currently not possible")....   Regards -Michael ... View more