The only way known to me is to clear mailboxes thus returning HA state to uninitalized. I hesitate to recommend it though as disk ownership in Data ONTAP 8 is different from 7G and I do not have first hand experience with this situation. So advice to contact support remains valid. 🙂 ... View more

If partner does not boot due to RAM issue, I would move RAM from another filer and tried to bring it up. Otherwise you will need to destroy HA pair, but that potentially means data loss. Best is to open case with support. ... View more

It depends on current disk ownership and whether you are using ADP or not. ... View more

@sgrant wrote: https://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=1105827 Publicly visible information does not mention IBACP supprot anywhere. Just to be sure - is it really about IBACP or just about removing "unsupported" flag? ... View more

@timmwestedt wrote: How to tell Ontap to use internal Infiniband IC's insetad of "externel" cluster ports c0a and c0b? You need to set psm-cc-config? LOADER variable (setenv psm-cc-config? true). Question mark is part of variable name.     ... View more

@andris wrote: There's a non-public bug Feature Request that allows ADP to include external shelves on FAS26xx, starting with ONTAP 9.1. If you're running ONTAP 9.2, the new Option 9 (ADP) boot menu option is the cat's meow. Oh! Now it became even more confusing. 😞 Do you refer to the same feature as Alex (ADP on external shelves withoout internal disks) or you mean that it is possible to force ADP on external disks even with internal disks present? ... View more

Well, the error is "no data or parity disk". Of course it is possible that disk labels were upgraded to newer version in which case one indeed needs newer (Data) ONTAP. But that's just speculation without seeing full boot log. But if the problem is simply that root aggregate had been lost, then no netboot is needed.   ... View more

You do not need netboot to reinitalize disks. Simply interrupt boot with ^C when prompted for special boot menu and select 4. This will keep your existing NetApp binaries on boot device.   Do not forget that you will need to re-enter all your licenses. If you did not record them, you need access to support site to fetch. ... View more

@AlexDawson wrote: I was earlier relying on an internal doc on ADP released July 2017. Do you mean SE presentation? Indeed, it says exactly opposite 🙂 Would be nice to align them.   @AlexDawson wrote: Clearly only one is correct - I will find out and update. Much appreciated! ... View more

@AlexDawson wrote: only in the internal shelves ONTAP 9.x release notes explicitly say: "Beginning with ONTAP 9.0, root-data partitioning is supported by the FAS2600 series on hard disk drives (HDDs) in external disk shelves." If what you say is true, I expect release notes to be fixed. ... View more

What is possible: initialize filer using special boot menu 4 (this creates 3 disks root aggregate); sanitize remaining disks; initialize filer again making sure it goes to sanitized disks (e.g. by physically removing three disks) and sanitize the remaining ones, this leaves us with original content securely wiped and only default content on three disks. It should be good enough. Alternative is to connect shelves to another filer and sanitize from there. ... View more

@philipp_pluess wrote: what would be the fastest, best way to move data from a qtree to a parent volume. Just mount volume and use host tool (simple "mv" should suffice - as this is NFS I assume you are using Unix/Linux) to move data. Hopefully you do not have large number of objects in top level directory. ... View more

This is called CFT (Copy Free Transition) but it still requires new node(s) with enough disks for root aggregates, probably as swing gear. ... View more

@AlexDawson wrote: however system diag/crash logs will not be retained through this process. Not only that, but any non-default content of root volume will be lost. This includes updated firmware files or DQP. So I can imagine corner case when user has brand new disks requiring updated DQP; then it won't be available on new root. I am not sure what are the consequences though (hopefully it comes up and allows installing missing files). But as there is apparently no way to be alerted about such situation, this requires user to manally track any extra files that may have been installed.   ... View more

In 7G after 4 in special boot menu you need to perform "software update" in Data ONTAP to fill in root volume content. You also need to enter all licenses again - did you record them before wiping your system? ... View more

First, this is data migration to new platform, so you must always plan for downtime; you can only possibly influence length and number of required downtimes. So if "another way" means "no downtime" - no, this is not possible.   As for swing gear - if using 7MTT CBT, yes - migration from 7G is qualified up to 8.2 and 2650 is supported starting with 9.1, so you cannot migrate (using 7MTT) directly. While migration can be done without using 7MTT, estimating whether it is feasible in your particular case far exceeds the scope of forum format. One thing is sure - doing this without 7MTT will irequire more manual work (and so be more error prone).   Hmm ... if your filer is used exclusively for ESXi datastores - you could simply setup new filer as additional datastore and do storage vMotion. This would be completely transparent and without downtime. ... View more

That's exactly the reason to open the case - so support can investigate it. ... View more

It's almost certainly hardware issue. You need to open case to get it replaced. ... View more

And what was the issue with multipath.conf? ... View more

I am not aware of any documented way to relocate shelves between different clusters keeping data intact. You can add third node to cluster, but it will require wiping it clean losing configuration. ... View more

Cumulative is total size of all snapshots up to this one. ... View more

DS4243 has SAS interface, not IB. ... View more