Process for Booting the OS and Performing a
Switchback in 2-node MCC (MetroCluster Clustered)
Page 1 of 3 30-May-23
I. Boot the Operating System and Perform a Switchback
Step Action Description
1 At the LOADER-A|B prompt of the TARGET system, enter: autoboot to boot ONTAP.
2 After the console stops printing messages, press the <enter> key. (The system boots up to a "login>" prompt.)
Loading X86_64/freebsd/image1/kernel:0x100000/3375736 0x538280/3221872
.... Many typical system startup
..... messages removed for clarity
.....
******************************* These are
* Press Ctrl-C for Boot Menu. * typical Boot strap console
******************************* messages. If the partner did not
..... takeover OR this is a stand-alone
system, you should eventually get a
login: "login" prompt when you
hit <enter>.
FOLLOW for Motherboard / Controller FRU REPLACEMENT ONLY:
(For other FRU replacements, skip to step 3 below)
Install the Evaluation license keys now!
S A) Please inform the customer that License keys are required to enable value-add features (such as protocols, SnapMirror,
etc.). For ONTAP 8.2.x or higher, software licenses keys are locked to the Controller Serial Number. After controller
replacement, new license keys will need to be re-created by NetApp for the new Controller Serial Number and
T
installed by the customer.
B) For a 2-Node MetroCluster (one node on each side): Engage the Customer to call NGS for them to generate Evaluation
O Licenses for the replacement node. Customer needs to install the evaluation license keys on the replacement node
prior to switchback to avoid loss of software features. Failure to install the license keys may result in error
P messages when attempting to perform a 'swichback' later in this Action Plan.
Note: An Eval key is typically issued for a 90 day period. Read (C) below for info about new Permanent license keys.
C) Inform the customer that NetApp will validate the controller replacement through ASUP or the 'sysconfig -a' sent from the
customer and they should receive an email in a few days with instructions to install the new permanent license keys .
3 After the Evaluation License Keys are installed on the replacement node, login to the DR PARTNER System and
enter: metrocluster heal -phase aggregates to resynchronize the data aggregates.
site_B::> metrocluster heal -phase aggregates
[Job 3266] Job is queued: MetroCluster Heal Aggregates Job.
....
[Job 3266] Job succeeded: Heal Aggregates is successful.
If the healing is vetoed, re-issue the "metrocluster heal" command with the –override-vetoes parameter to
NOTE
override any soft vetoes that prevent the healing operation.
4 Enter: metrocluster operation show to verify that the operation has been completed
site_B::> metrocluster operation show
Operation: heal-aggregates
State: successful Verify the 'heal-aggregates' operation is
Start Time: 8/11/2016 [Link] successful without error.
End Time: 8/11/2016 [Link]
Errors: -
5 Continue with Section I on next page.
Process for Booting the OS and Performing a
Switchback in 2-node MCC (MetroCluster Clustered)
Page 2 of 3
I. Boot the Operating System and Perform a Switchback
Step Action Description
6 Enter: storage aggregate show to check the state of the aggregates.
7 Enter: metrocluster heal -phase root-aggregates to heal the root aggregates.
site_B::> metrocluster heal -phase root-aggregates
[Job 3267] Job is queued: MetroCluster Heal Root Aggregates Job.
....
[Job 3267] Job succeeded: Heal Root Aggregates is successful.
If the healing is vetoed, re-issue the "metrocluster heal" command with the –override-vetoes parameter to
NOTE
override any soft vetoes that prevent the healing operation.
8 Enter: metrocluster operation show to verify that the operation has been completed.
site_B::> metrocluster operation show
Operation: heal-root-aggregates
State: successful
Start Time: 8/11/2016 [Link] Verify the 'heal-root-aggregates'
End Time: 8/11/2016 [Link] operation is successful without error.
Errors: -
9 Enter: metrocluster switchback to perform a switchback.
a) Enter: y to the question "Do you want to continue? {y/n} .
site_B::> metrocluster switchback
Warning: switchback is about to start. It will stop all the switched over data
Vservers on cluster "siteB" and automatically restart them on cluster
"siteA".
Do you want to continue? {y|n}: y
[Job 3269] Job is queued: MetroCluster Switchback Job.
......
......
[Job 3269] Job succeeded: Switchback is successful. Verify the switchback is successful.
site_B::> If not, report it to NGS.
10 Enter: metrocluster show and check the progress of the switchback operation. The switchback operation is complete when
the output displays normal.
Site_B::> metrocluster show The output might be in a different
format for Clustered ONTAP 9.x.
Cluster Configuration State Mode
------------------------------ ---------------------- ------------------------
Local: Site_B configured normal
Remote: Site_A configured normal
Site_B::>
The switchback operation is complete when the output displays 'normal' for both nodes.
11 Enter: system health alert show and verify that there are no health alert. If any 'health alert', report it to NGS.
a) Login to the TARGET system and enter the same command in step 11. If any 'health alert', report it to NGS.
12 If the Boot Device was replaced, enter: version and verify the ONTAP version.
13 Continue with Section I on next page.
Process for Booting the OS and Performing a
Switchback in 2-node MCC (MetroCluster Clustered)
Page 3 of 3
III. Boot the Operating System and Perform a Switchback
Step Action Description
14 Enter the following commands to check that the MetroCluster components are healthy. If not all components are OK, report it
to NGS.
metrocluster check run
metrocluster check show
Example Only
site_A::> metrocluster check run
The operation has been started and is running in the background. Wait for it to complete and
run "metrocluster check show" to view the results. To check the status of the running
metrocluster check operation, use the command,
"metrocluster operation history show -job-id 2408"
site_A::> metrocluster operation history show -job-id 2408
Operation State Start Time End Time
----------------------------- -------------- ---------------- ----------------
check in-progress 8/11/2016 [Link] -
........ Wait about 30 seconds and re-issue the command.
........
site_A::> metrocluster operation history show -job-id 2408
Operation State Start Time End Time
----------------------------- -------------- ---------------- ----------------
check successful 8/11/2016 [Link] 8/11/2016 [Link]
site_A::> metrocluster check show
Last Checked On: 8/11/2016 [Link]
Component Result
------------------- ---------
nodes ok
lifs ok
config-replication ok
aggregates ok
If not all listed are OK, report it to NGS.
clusters ok
5 entries were displayed.
site_A::>
15 Enter: set -priv advanced to set the privilege level to "advanced".
16 Enter: metrocluster switchover -simulate and check whether the switchback operation is completed without errors.
site_A::> metrocluster switchover -simulate
[Job 3271] Job is queued: MetroCluster Negotiated Switchover Job - Simulation.
.......
....... If 'Switchover simulation' is not successful, report it to NGS.
[Job 3271] Job succeeded: Switchover simulation is successful.
17 Is 'Switchover simulation' successful?
Yes - Return to the Master Action Plan and continue with section "Complete system setup, Registration, Submit logs,
Part return" or "Send Autosupport, Enable Options, Submit logs, Part Return".
No - Report the failure to NGS.
