dougthomp
commented
2 months ago Thank you for your comment. I have assigned this issue to myself and will get to it as quickly as possible.
Open amadorloureiro opened 2 months ago
dougthomp
commented
2 months ago Thank you for your comment. I have assigned this issue to myself and will get to it as quickly as possible.
Page URL
https://docs.netapp.com/us-en/ontap-systems/a250/bootmedia-recovery-image-boot-non-2n-mcc.html
Page title
Boot the recovery image - AFF A250
Summary
In https://net2.netapp.com/api/documents/getdocument/Boot_Device-AFF_A250-ASA_A250-ASA_AFF-A250_AFF-C250_ASA-C250_FAS500f-008.pdf?5255872087990772 we have, at Section 10 : Select the Procedure For Transferring the System Files
1) Stop! There are two different procedures for transferring the system files: Procedure A: Restore the var file system using system node restore-backup command Procedure B: Restore the var file system using Update flash from backup config option The procedure to be followed is based on system configuration and status. a) IF this is an "HA" system and the TARGET node was successfully taken over by its PARTNER, follow Procedure A - go to section 11. || b) IF the PARTNER did not takeover or the PARTNER node cannot communicate with the TARGET node or this is a maintenance window, follow Procedure B - go to section 12. (A maintenance window and service outage may be required. Call NGS if you have questions.
But, at https://docs.netapp.com/us-en/ontap-systems/a250/bootmedia-recovery-image-boot-non-2n-mcc.html only: If your system has… Then… A network connection ... No network connection ... No network connection and is in a MetroCluster IP configuration ...
Can we make our documentation consistent, especially in the cases where we have a 2n or 4n MCC IP with nodes in SFO/SwitchOver?
Public issues must not contain sensitive information