vfiler = multistore Sure, but paragraph from block management guide quoted by OP does not say a single word about multistore (it talks about HA pair), nor does multistore guide say anything about target portal groups. That is why I find it extremely confusing.
... View more
Interesting. I have never noticed this before; and I have never seen it mentioned in any document from NetApp (technical reports, training materials etc). Even though I’m rather skeptical here, why not. Actually usually configuration is symmetrical, so same interfaces get the same target portal tag. But that’s exactly what makes me skeptical - there is no reason to assume that a) interface configuration is symmetrical or b) that both controllers even have the same interfaces.
... View more
I'm not sure I understand how portal group is related to failover. During failover virtual instance of controller is started on partner. It has exactly the same configuration, there is nothing to match against. So you simply need to ensure that every interface has matching partner interface, that's all.
... View more
What is value of “options cf.mode” on both controllers (when booted normally, not in maintenance)? Poster you show is for C-Mode, it does not apply to 7-Mode.
... View more
Oh, that makes a difference. If port 1d was never connected in the first place, then it could be anything - adapter in slot 1, SFPs on port 1c (both of them) or AT-FCX module. In theory even defective disk could block loop. I’d start with power cycling shelf itself; obvious next step is to connect to another port. Sorry, but the only way here is to troubleshoot on site by replacing components.
... View more
Personally I would split connection to each loop/stack across two adapters. May be this was created as example of adding SAS to existing DS14 cluster, where you would avoid moving existing connections. I sent comment to TR publisher, let’s see if we get any response ☺
... View more
You can pull previous configuration from ASUP. Being able to compare would help. Based on what you have shown so far, you have one genuinely failed disk (1b.26) as well as HBA in slot 1 - looks like second ASIC that connects to ports c and d failed. But I do not quite understand how it helps you - you would need to open case with NetApp to get replacement anyway, and it is their job to troubleshoot and determine failed part. You have enough free ports to connect shelf using multipath. This would help to mitigate this issue (not panic, but shelves would have been found after reboot).
... View more
Not really export, but define export policy that is using krb5. Changes to export policy are instantaneous as far as I know, but may apply to new mount requests only.
... View more
See tr-3958 for more up-to-date version. Deduplicated data limit is max volume size, which is 50TB for 8.1.4 on FAS3240. It has nothing to do with deduplication rate - if you have 50TB of data that cannot be deduplicated, you still have 50TB of data that must be processed by engine. When deduplication limit is reached, extra data won’t be deduplicated (or compressed) until logical amount of data falls below limit.
... View more
No. It needs at least two PSU providing power. It also needs all four PSU fans; physically removing PSU will cause shutdown after 2 minutes.
... View more
I wonder - was it yours question just recently? As was determined, SnapDrive reverts volume to consistent snapshot which deletes base SnapMirror snapshot. As long as some other common snapshot still exists, it should be possible to resync though.
... View more
Sounds like a http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=813566; see also https://forums.netapp.com/thread/39503. For mixed path - I believe this message should be generated only once, on reboot. I may be wrong though. You could open case, quoting above bug for downrev problem. The more people complain, the more chances it will eventually be fixed.
... View more