free iscsi license First, that's wrong. Software package for FAS3200 came with one "free" protocol license of choice - this could have been iSCSI, but could also have been something else. But this absolutely does not matter in this case, because you are not buying anything from NetApp, so it does not matter whether NetApp was offering anything free or not. What matters technically is what license codes you got from your supplier. And I do not imply that you can legally use them! EULA that you must read and accept before you can download software includes "non-transferrable" clause. But again, IANAL so you are really better off contacting NetApp officially (which also answers your question about price of software). It is not something that can be settled in forum discussion. Otherwise yes, you can use NetApp to host ESX datastores, using any of iSCSI, FCP or NFS protocol. It does not matter whether it is redundant HA pair or not; being non-redundant just restricts your ability to do maintenance work on it non-disruptively.
... View more
I never tried this myself but this has good chances to work, as long as boot device is the same. But I would definitely open case with NetApp to have support if something hits wrong.
... View more
IANAL so I skip licensing question. Single controller will protect against drive failure, but will not protect against controller failure (or any component inside controller). Normal FAS configuration consists of two controllers (HA pair). Also for disks you will need to have supply of spares when they start to fail.
... View more
You cannot reduce aggregate nor can you destroy root aggregate - you will need to reinstall filer. You may be able convert raid_dp aggregate to raid4, this gives you additional spare disk to create new root aggregate. Old aggregate will be destroyed anyway, so it does not matter. Or you can reassign spare from m other controller.
... View more
If all SATA disks are owned by the other controller, that is not possible. You cannot relocate root disk to aggregate owned by another controller. You need free SATA disks to create aggregate owned by controller with SAS disks and then relocate root volume to this aggregate. You may be able to change disk ownership of spare disks if you have enough of them.
... View more
If there is any user (beyond root), controller will ask for login name. CIFS configurationusually adds local administrator user. If you are sure you do not need it, just delete all additional users.
... View more
I'm confused. This document says exactly the same - create separate LIF(s) for data and management. So where is your problem? Sorry, I really do not understand.
... View more
cDOT Hyper-v documentation specifically stats that the DATA LIFs be set up as the CIFS server and the name has to be different than the SVM name Can you provide link to documentation? Since this is two data ports from the same SVM if I join the AD domain using the management LIF I cannot join the DOMAIN a second time from the DATA LIF correct? You do not join LIF, you join SVM. Let's wait until you show documentation you mentioned.
... View more
No, pass-through works only for administrative access to cluster. Just add another LIFs to SVM that are able to contact domain controller. You can also restrict data protocols through these LIFs if this is security concern.
... View more
Which version of cDOT? In 8.3 volumes are not deleted immediately, but put into delete queue and finally destroyed after 12 hours (I think this is default period). This gives you chance to undo accidental volume deletion.
... View more
Yes, that's possible, but there is no real reason to have second VIF at all - you can just as well have single mode VIF between multi mode VIF and physical interface.
... View more
Yes, you are right, sorry for mixing up 7-Mode and C-Mode. Well, I think filer may notify host that preferred path changed so host simply continues IO over remaining LIF. But yes, I would be interested in final answer too.
... View more
You need to disable ADP and reinstall (reinitialize root aggregate/volume). Do you have access to this article? How to disable Advanced Drive Partitioning (ADP)
... View more
Ah, OK, it is just misleading parameter name. Windows iSCSI initiator LinkDownTime in reality defines IO request timeout, so it is exactly as I explained - when path becomes unavailable, host waits for configured timeout before switching over to another path. When you perform SFO all paths continue to be available, so it is just time required to flip disk ownership between controllers.
... View more
Taking LIF down is not related to LinkDownTime - interface on host is still up, there is no link problem. Timeout most like corresponds to IO request timeout after which MPIO on host retries on different path. In case of SFO there is short pause when access to aggregate is switched to partner, both (all) paths are alive and function correctly.
... View more