Then I'm with you. I do not see any fundamental reason why this should not work with C-Mode. Unfortunately I have never seen any explanation that goes beyond "it is not supported, there could be issues". Hopefully someone from NetApp will chime in.
... View more
Not sure if these things were part of the Ontap Upgrade They are. Current Data ONTAP (8.2.3 definitely does it) automatically initiates upgrade of SP firmware to included version.
... View more
In this case there is no supported way to do it online. Hot shelf unplug is supported starting with 8.2.1 and even then only for shelves containing unused unowned disks.
... View more
Even the infinite volume, which has a max capacity of 20 PB, seems to be limited to 100 TiB per node. Max 10 nodes I got only 1 PB. How to reach the 20 PB? Use more than one volume per node.
... View more
First, e0M does not support VLAN 🙂 But you again confuse port and LIF. VLAN cannot be *on* LIF. LIF is associated with failover group which containes ports; these ports can of course be VLANs, but LIF does not know or care.
... View more
You confuse port and LIF. Nothing prevents having two LIFs on the same e0M port where one LIF is restricted to local node and another LIF can failover to another node. What TR tries to say, that if in the past physical node connectivity to management network was enough, now you may need to explicitly configure LIFs in this management network for each SVM.
... View more
# volume modify -vserver VSERVER -volume VOLUME -caching-policy none You are right of course. It allows also more fine-grained control than just all or nothing. Thank you for correcting!
... View more
You could also do it with a LUN since we support NAS to SAN ODX. Wow! Could you share link to Microsoft description of this feature? Thank you!
... View more
Storage pool allows sharing of SSD capacity between multiple aggregates (even on different controllers); If you have just one aggregate, traditional flash pool is easier to manage. I am not aware of a possibility to disable caching for individual volumes.
... View more
I assume you are using C-Mode. Windows NFSv3 clients are supported starting with cDOT 8.2.3 and require explicit SVM configuration. See 8.2.3 release notes for details.
... View more
Data corruption due to incorrect cabling looks very unlikely (I have never heard about it). The worst that may happen - disks will be missing so some aggregate will be incomplete. If this happens to be root aggregate, system does not boot. No special config is needed to swap cards. You may want to disable fcp service but that's not really required.
... View more
Snap reserve for volumes containing LUNs is useless, there is no need to set it. It makes sense only in NAS environment (and even there it is not to reserve anything, but to hide some space from clients). If you really do not care about consistency of data on LUN then yes, it is just as simple as configuring scheduled snapshot. There is really no difference (from NetApp side) whether it is BOOT or not.
... View more
No, in 7-Mode it is near to impossible to get right. The problem is, 7-Mode iSCSI does not use ALUA so it relies on simple IP failover. If you have direct controller connection and controller goes down, IP is moved to partner, but host is still connected to the same controller that is not available anymore. So it cannot access target IP. But C-Mode is using ALUA where LIFs themselves do not migrate. So host has two (or more) independent paths to two different controllers. I honestly fail to understand how switch connection differs from direct connection here.
... View more
Unfortunately we do not support SAN configurations (FCP, iSCSI or FCoE) directly attached to FAS storage systems, as we are providing high availablity by using ALUA and MPIO. This does not explain why direct host connection with iSCSI is impossible. Host having 2 ethernet adapters, each to different controller, and using MPIO over these two adapters. What does not work in this configuration? FCoE is not possible because it requires management instance which is normally implemented by switches and FC may have problems with NPIV as you mentioned. But I miss the reason why iSCSI should not work.
... View more
"Cannot get it to work" does not give much starting point. Explain what you have done, what you expected and what are results. And start with telling which version and mode of Data ONTAP you have.
... View more
If it has the same part number it will work. It is always recommended to use latest disk firmware for all drives, so you may consider update other disks as well.
... View more
You told it to ping 172.17.2.94, why do you expect it to magically start pinging 10.1.8.20 instead? If you want to connect (or ping) 10.1.8.20, just say so. If you want name FILERB on secondary resolve to 10.x.x.x address - add this name to /etc/hosts on secondary with this address. As to why traffic to 172.17.2.94 goes via 10.x.x.x - I presume that is how your routing table looks like. Please paste "netstat -rn" output on secondary.
... View more
It's easier to just move volumes now, for this maintenance, and care about LS mirrors later. You will need to remove all volumes to offline aggregates anyway, so destroy any existing mirrors.
... View more
IP is resolved from hostname you specify in "snapvault start" command. You can use IP address directly here. I am not sure what happens if you give IP alias which is not the same as primary hostname (I know that SnapMirror was rather picky here); but you can try. Using IP address is always an option.
... View more