From 63c592850b7a43af9119471cbf1beccd6ed3b6ec Mon Sep 17 00:00:00 2001 From: netapp-pcarriga Date: Fri, 11 Aug 2023 18:38:59 +0100 Subject: [PATCH 01/27] 1527472 Adding tables --- .../port_usage_fc_switches_91_and_later.adoc | 540 +++++++++++++++++- 1 file changed, 539 insertions(+), 1 deletion(-) diff --git a/_include/port_usage_fc_switches_91_and_later.adoc b/_include/port_usage_fc_switches_91_and_later.adoc index ae05df3c1..4f435c286 100644 --- a/_include/port_usage_fc_switches_91_and_later.adoc +++ b/_include/port_usage_fc_switches_91_and_later.adoc @@ -3211,4 +3211,542 @@ a| MDS module 1 port 16 |=== -// BURT 1448684, 12 JAN 2022 + +== Cisco 9132T port usage in MetroCluster 4-node and 8-node configurations running ONTAP 9.1 and later + +|=== +6+^h| Configurations using FibreBridge 7500N or 7600N using both FC ports (FC1 and FC2) +6+^h| Cisco 9132T +6+^h| MetroCluster 1 or DR Group 1 +| +| +| +2+^h| 4-node +h| 8-node +h| Component h| Port h| Connects to FC_switch... h| 9132T (1x LEM) h| 9132T (2x LEM) h| 9132T (2x LEM) +.8+a| +controller_x_1 +a| +FC-VI port a +a| +1 +a| +LEM1-1 +a| +LEM1-1 +a| +LEM1-1 +a| +FC-VI port b +a| +2 +a| +LEM1-1 +a| +LEM1-1 +a| +LEM1-1 +a| +FC-VI port c +a| +1 +a| +LEM1-2 +a| +LEM1-2 +a| +LEM1-2 +a| +FC-VI port d +a| +2 +a| +LEM1-2 +a| +LEM1-2 +a| +LEM1-2 +a| +HBA port a +a| +1 +a| +LEM1-5 +a| +LEM1-5 +a| +LEM1-3 +a| +HBA port b +a| +2 +a| +LEM1-5 +a| +LEM1-5 +a| +LEM1-3 +a| +HBA port c +a| +1 +a| +LEM1-6 +a| +LEM1-6 +a| +LEM1-4 +a| +HBA port d +a| +2 +a| +LEM1-6 +a| +LEM1-6 +a| +LEM1-4 +.8+a| +controller_x_2 +a| +FC-VI port a +a| +1 +a| +LEM1-7 +a| +LEM1-7 +a| +LEM1-5 +a| +FC-VI port b +a| +2 +a| +LEM1-7 +a| +LEM1-7 +a| +LEM1-5 +a| +FC-VI port c +a| +1 +a| +LEM1-8 +a| +LEM1-8 +a| +LEM1-6 +a| +FC-VI port d +a| +2 +a| +LEM1-8 +a| +LEM1-8 +a| +LEM1-6 +a| +HBA port a +a| +1 +a| +LEM1-11 +a| +LEM1-11 +a| +LEM1-7 +a| +HBA port b +a| +2 +a| +LEM1-11 +a| +LEM1-11 +a| +LEM1-7 +a| +HBA port c +a| +1 +a| +LEM1-12 +a| +LEM1-12 +a| +LEM1-8 +a| +HBA port d +a| +2 +a| +LEM1-12 +a| +LEM1-12 +a| +LEM1-8 +6+^h| MetroCluster 2 or DR Group 2 +.8+a| +controller_x_3 +a| +FC-VI port a +a| +1 +| +| +a| +LEM2-1 +a| +FC-VI port b +a| +2 +| +| +a| +LEM2-1 +a| +FC-VI port c +a| +1 +| +| +a| +LEM2-2 + +a| +FC-VI port d +a| +2 +| +| +a| +LEM2-2 +a| +HBA port a +a| +1 +| +| +a| +LEM2-3 +a| +HBA port b +a| +2 +| +| +a| +LEM2-3 +a| +HBA port c +a| +1 +| +| +a| +LEM2-4 +a| +HBA port d +a| +2 +| +| +a| +LEM2-4 +.8+a| +controller_x_4 +a| +FC-VI-1 port a +a| +1 +| +| +a| +LEM2-5 +a| +FC-VI-1 port b +a| +2 +| +| +a| +LEM2-5 +a| +FC-VI-1 port c +a| +1 +| +| +a| +LEM2-6 +a| +FC-VI-1 port d +a| +2 +| +| +a| +LEM2-6 +a| +HBA port a +a| +1 +| +| +a| +a| +HBA port b +a| +2 +| +| +a| +LEM2-7 +a| +HBA port c +a| +1 +| +| +a| +LEM2-8 +a| +HBA port d +a| +2 +| +| +a| +LEM2-8 +|=== + +|=== + +7+^h| MetroCluster 1 or DR Group 1 +| +| +| +| +2+^h| 4-node +h| 8-node +2+^h| FibreBridge 7500 using two FC ports h| Port h| Connects to FC_switch... h| 9132T (1x LEM) h| 9132T (2x LEM) h| 9132T (2x LEM) +.4+a| +Stack 1 +.2+a| +bridge_x_1a +a| +FC1 +a| +1 +a| +LEM1-13 +a| +LEM1-13 +a| +LEM1-9 +a| +FC2 +a| +2 +a| +LEM1-13 +a| +LEM1-13 +a| +LEM1-9 +.2+a| +bridge_x_1b +a| +FC1 +a| +1 +a| +LEM1-14 +a| +LEM1-14 +a| +LEM1-10 +a| +FC2 +a| +2 +a| +LEM1-14 +a| +LEM1-14 +a| +LEM1-10 +.4+a| +Stack 2 +.2+a| +bridge_x_2a +a| +FC1 +a| +1 +| +a| +LEM1-15 +a| +LEM1-11 +a| +FC2 +a| +2 +| +a| +LEM1-15 +a| +LEM1-1 +.2+a| +bridge_x_2b +a| +FC1 +a| +1 +| +a| +LEM1-16 +a| +LEM1-12 +a| +FC2 +a| +2 +| +a| +LEM1-16 +a| +LEM1-12 +.4+a| +Stack 3 +.2+a| +bridge_x_3a +a| +FC1 +a| +1 +| +a| +LEM2-1 +a| +LEM2-9 +a| +FC2 +a| +2 +| +a| +LEM2-1 +a| +LEM2-9 +.2+a| +bridge_x_3b +a| +FC1 +a| +1 +| +a| +LEM2-2 +a| +LEM2-10 +a| +FC2 +a| +2 +| +a| +LEM2-2 +a| +LEM2-10 +.4+a| +Stack y +.2+a| +bridge_x_ya +a| +FC1 +a| +1 +| +a| +LEM2-3 +a| +LEM2-11 +a| +FC2 +a| +2 +| +a| +LEM2-3 +a| +LEM2-11 +.2+a| +bridge_x_yb +a| +FC1 +a| +1 +| +a| +LEM2-4 +a| +LEM2-11 +a| +FC2 +a| +2 +| +a| +LEM2-4 +a| +LEM2-11 +|=== + +|=== +4+^h| Cisco 9132T +4+^h| MetroCluster 1 or DR Group 1 +.2+a| Port +2+^h| 4-node +h| 8-node +h| 9132T (1x LEM) h| 9132T (2x LEM) h| 9132T (2x LEM) +|ISL1 +|LEM1-15 +|LEM2-9 +|LEM1-13 +|ISL2 +|LEM1-16 +|LEM2-10 +|LEM1-14 +|ISL3 +| +|LEM2-11 +|LEM1-15 +|ISL4 +| +|LEM2-12 +|LEM1-16 +|ISL5 +| +|LEM2-13 +| +|ISL6 +| +|LEM2-14 +| +|ISL7 +| +|LEM2-15 +| +|ISL8 +| +|LEM2-16 +| +|=== + +// 2023 AUG 11, BURT 1537472 +// 2022 JAN , BURT 1448684 From f329096959c25854365398a39a54f15fda4e3240 Mon Sep 17 00:00:00 2001 From: netapp-pcarriga Date: Mon, 14 Aug 2023 12:24:52 +0100 Subject: [PATCH 02/27] 1537472 complete draft of new 9132T tables --- .../port_usage_fc_switches_91_and_later.adoc | 35 +++++++++++-------- .../concept_AFF_A900_cisco_port_config.adoc | 2 +- 2 files changed, 22 insertions(+), 15 deletions(-) diff --git a/_include/port_usage_fc_switches_91_and_later.adoc b/_include/port_usage_fc_switches_91_and_later.adoc index 4f435c286..efdb6bddb 100644 --- a/_include/port_usage_fc_switches_91_and_later.adoc +++ b/_include/port_usage_fc_switches_91_and_later.adoc @@ -3214,13 +3214,12 @@ MDS module 1 port 16 == Cisco 9132T port usage in MetroCluster 4-node and 8-node configurations running ONTAP 9.1 and later +The following tables show the port usage on a Cisco 9132T switch. The tables show the maximum supported configurations with four and eight controller modules in two DR groups. + |=== 6+^h| Configurations using FibreBridge 7500N or 7600N using both FC ports (FC1 and FC2) -6+^h| Cisco 9132T 6+^h| MetroCluster 1 or DR Group 1 -| -| -| +3+^h| 2+^h| 4-node h| 8-node h| Component h| Port h| Connects to FC_switch... h| 9132T (1x LEM) h| 9132T (2x LEM) h| 9132T (2x LEM) @@ -3497,6 +3496,7 @@ a| | | a| +LEM2-7 a| HBA port b a| @@ -3523,13 +3523,12 @@ a| LEM2-8 |=== -|=== +For 8-node configurations, you must perform the zoning manually because RCF files are not provided. +|=== +7+^h| Configurations using FibreBridge 7500N or 7600N using both FC ports (FC1 and FC2) 7+^h| MetroCluster 1 or DR Group 1 -| -| -| -| +4+^h| 2+^h| 4-node h| 8-node 2+^h| FibreBridge 7500 using two FC ports h| Port h| Connects to FC_switch... h| 9132T (1x LEM) h| 9132T (2x LEM) h| 9132T (2x LEM) @@ -3600,7 +3599,7 @@ a| a| LEM1-15 a| -LEM1-1 +LEM1-11 .2+a| bridge_x_2b a| @@ -3695,7 +3694,7 @@ a| a| LEM2-4 a| -LEM2-11 +LEM2-12 a| FC2 a| @@ -3704,13 +3703,21 @@ a| a| LEM2-4 a| -LEM2-11 +LEM2-12 |=== +[NOTE] +==== +* In 4-node configurations, you can cable additional bridges to ports LEM2-5 through LEM2-8 in 9132T switches with 2x LEMs. +* In 8-node configurations, you can cable additional bridges to ports LEM2-13 through LEM2-16 in 9132T switches with 2x LEMs. +* Only one (1) bridge stack is supported using 9132T switches with 1x LEM Module. +==== + +The following table shows ISL port usage for a Cisco 9132T switch. + |=== -4+^h| Cisco 9132T 4+^h| MetroCluster 1 or DR Group 1 -.2+a| Port +.2+h| Port 2+^h| 4-node h| 8-node h| 9132T (1x LEM) h| 9132T (2x LEM) h| 9132T (2x LEM) diff --git a/install-fc/concept_AFF_A900_cisco_port_config.adoc b/install-fc/concept_AFF_A900_cisco_port_config.adoc index ae41708b8..2dda7402e 100644 --- a/install-fc/concept_AFF_A900_cisco_port_config.adoc +++ b/install-fc/concept_AFF_A900_cisco_port_config.adoc @@ -137,6 +137,6 @@ h| Connects to FC_switch... h| 9132T (1x LEM) h| 9132T (2x LEM) [NOTE] ==== -* Additional bridges can be cabled to ports LEM2-5 through LEM2-8 in 9132T switches with 2x LEM Modules. +* You can cable additional bridges to ports LEM2-5 through LEM2-8 in 9132T switches with 2x LEM Modules. * Only one (1) bridge stack is supported using 9132T switches with 1x LEM Module. ==== From 6ef54487147a2a5951e24ca1a3e13075971da295 Mon Sep 17 00:00:00 2001 From: netapp-pcarriga Date: Mon, 14 Aug 2023 15:39:49 +0100 Subject: [PATCH 03/27] minor edit --- _include/port_usage_fc_switches_91_and_later.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_include/port_usage_fc_switches_91_and_later.adoc b/_include/port_usage_fc_switches_91_and_later.adoc index efdb6bddb..34f8ce4c0 100644 --- a/_include/port_usage_fc_switches_91_and_later.adoc +++ b/_include/port_usage_fc_switches_91_and_later.adoc @@ -3523,7 +3523,7 @@ a| LEM2-8 |=== -For 8-node configurations, you must perform the zoning manually because RCF files are not provided. +For 8-node configurations, you must perform the zoning manually because RCFs are not provided. |=== 7+^h| Configurations using FibreBridge 7500N or 7600N using both FC ports (FC1 and FC2) From 9ddb72efca63235a6d72a7d0fda714bd33491a16 Mon Sep 17 00:00:00 2001 From: netapp-pcarriga Date: Mon, 14 Aug 2023 16:23:56 +0100 Subject: [PATCH 04/27] Removing 9132T information --- .../port_usage_fc_switches_91_and_later.adoc | 305 ------------------ 1 file changed, 305 deletions(-) diff --git a/_include/port_usage_fc_switches_91_and_later.adoc b/_include/port_usage_fc_switches_91_and_later.adoc index 34f8ce4c0..b68dc2078 100644 --- a/_include/port_usage_fc_switches_91_and_later.adoc +++ b/_include/port_usage_fc_switches_91_and_later.adoc @@ -1893,229 +1893,9 @@ a| 32 |=== - -|=== - -4+^h| Cisco 9132T -4+^h| MDS module 1 -h| Component h| Port h| Switch 1 h| Switch 2 - -.8+a| -controller_x_1 -a| -FC-VI port a -a| -1 -a| -- -a| -FC-VI port b -a| -- -a| -1 -a| -FC-VI port c -a| -2 -a| -- -a| -FC-VI port d -a| -- -a| -2 -a| -HBA port a -a| -3 -a| -- -a| -HBA port b -a| -- -a| -3 -a| -HBA port c -a| -4 -a| -- -a| -HBA port d -a| -- -a| -4 -.8+a| -controller_x_2 -a| -FC-VI port a -a| -5 -a| -- -a| -FC-VI port b -a| -- -a| -5 -a| -FC-VI port c -a| -6 -a| -- -a| -FC-VI port d -a| -- -a| -6 -a| -HBA port a -a| -7 -a| -- -a| -HBA port b -a| -- -a| -7 -a| -HBA port c -a| -8 -a| -- -a| -HBA port d -a| -- -a| -8 -4+^h| -MDS module 2 -a| -Component -a| -Port -a| -Switch 1 -a| -Switch 2 -.8+a| -controller_x_3 -a| -FC-VI port a -a| -1 -a| -- -a| -FC-VI port b -a| -- -a| -1 -a| -FC-VI port c -a| -2 -a| -- -a| -FC-VI port d -a| -- -a| -2 -a| -HBA port a -a| -3 -a| -- -a| -HBA port b -a| -- -a| -3 -a| -HBA port c -a| -4 -a| -- -a| -HBA port d -a| -- -a| -4 -.8+a| -controller_x_4 -a| -FC-VI port a -a| -5 -a| -- -a| -FC-VI port b -a| -- -a| -5 -a| -FC-VI port c -a| -6 -a| -- -a| -FC-VI port d -a| -- -a| -6 -a| -HBA port a -a| -7 -a| -- -a| -HBA port b -a| -- -a| -7 -a| -HBA port c -a| -8 -a| -- -a| -HBA port d -a| -- -a| -8 -|=== - NOTE: The following table shows systems with two FC-VI ports. AFF A700 and FAS9000 systems have four FC-VI ports (a, b, c, and d). If using an AFF A700 or FAS9000 system, the port assignments move along by one position. For example, FC-VI ports c and d go to switch port 2 and HBA ports a and b go to switch port 3. |=== - 4+^h| Cisco 9250i Note: The Cisco 9250i switch is not supported for eight-node MetroCluster configurations. @@ -2519,72 +2299,6 @@ a| 16 |=== -Additional bridges for a second DR group or second MetroCluster configuration can be attached using ports 33 through 40 following the same pattern. - - -|=== - -4+^h| Cisco 9132T -h| FibreBridge 7500 using two FC ports h| Port h| Switch h| Switch 2 - -.2+a| -bridge_x_1a -a| -FC1 -a| -9 -a| -- -a| -FC2 -a| -- -a| -9 -.2+a| -bridge_x_1b -a| -FC1 -a| -10 -a| -- -a| -FC2 -a| -- -a| -10 -.2+a| -bridge_x_2a -a| -FC1 -a| -11 -a| -- -a| -FC2 -a| -- -a| -11 -.2+a| -bridge_x_2b -a| -FC1 -a| -12 -a| -- -a| -FC2 -a| -- -a| -12 -|=== - Additional bridges for a second DR group or second MetroCluster configuration can be attached using the same port numbers on the second MDS module. @@ -3191,27 +2905,8 @@ a| ISL 4 a| 48 -.4+a| -Cisco 9132T -a| -ISL 1 -a| -MDS module 1 port 13 -a| -ISL 2 -a| -MDS module 1 port 14 -a| -ISL 3 -a| -MDS module 1 port 15 -a| -ISL 4 -a| -MDS module 1 port 16 |=== - == Cisco 9132T port usage in MetroCluster 4-node and 8-node configurations running ONTAP 9.1 and later The following tables show the port usage on a Cisco 9132T switch. The tables show the maximum supported configurations with four and eight controller modules in two DR groups. From 4bdf8cad1f45c61c6c5f8bcb25c459d9b162f383 Mon Sep 17 00:00:00 2001 From: netapp-pcarriga Date: Mon, 14 Aug 2023 16:58:53 +0100 Subject: [PATCH 05/27] minor edit --- _include/port_usage_fc_switches_91_and_later.adoc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/_include/port_usage_fc_switches_91_and_later.adoc b/_include/port_usage_fc_switches_91_and_later.adoc index b68dc2078..baf9522bb 100644 --- a/_include/port_usage_fc_switches_91_and_later.adoc +++ b/_include/port_usage_fc_switches_91_and_later.adoc @@ -2299,8 +2299,7 @@ a| 16 |=== -Additional bridges for a second DR group or second MetroCluster configuration can be attached using the same port numbers on the second MDS module. - +Additional bridges for a second DR group or second MetroCluster configuration can be attached using ports 33 through 40 following the same pattern. |=== From d0c0d9f80f58cd710434c6c472e1846b1e4412b3 Mon Sep 17 00:00:00 2001 From: netapp-aoife Date: Thu, 21 Dec 2023 11:06:22 +0000 Subject: [PATCH 06/27] ONTAPDOC-1494, issue 341 --- upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc b/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc index 1836549cf..a74e858ae 100644 --- a/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc +++ b/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc @@ -11,7 +11,7 @@ summary: 'You can add four new nodes to the MetroCluster IP configuration as a s [.lead] Depending on your ONTAP version, you can expand your MetroCluster IP configuration by adding four new nodes as a new DR group. -Beginning with ONTAP 9.13.1, you can add four new nodes to the MetroCluster IP configuration as a third DR group. This creates a twelve-node MetroCluster configuration. +In ONTAP 9.13.1 and later, you can temporarily expand an eight-node MetroCLuster configuration to upgrade the controllers and storage. Refer to link:https://docs.netapp.com/us-en/ontap-metrocluster/upgrade/task_refresh_4n_mcc_ip.html[Refreshing a four-node or an eight-node MetroCluster IP configuration (ONTAP 9.8 and later)] for more information. Beginning with ONTAP 9.9.1, you can add four new nodes to the MetroCluster IP configuration as a second DR group. This creates an eight-node MetroCluster configuration. @@ -19,7 +19,7 @@ Beginning with ONTAP 9.9.1, you can add four new nodes to the MetroCluster IP co * The old and new nodes must be running the same version of ONTAP. -* This procedure describes the steps required to expand one four-node DR group. If you have an eight-node configuration (two DR groups), you must repeat the entire procedure for each DR group. +* This procedure describes the steps required to expand one four-node DR group. If you are refreshing an eight-node configuration and need to expand two DR groups, you must repeat the entire procedure for each DR group, expanding one at a time. * Verify that the old and new platform models are supported for platform mixing. + @@ -1059,6 +1059,10 @@ node_A_4-new false 4 entries were displayed. ---- +. Reboot each of the new nodes: ++ +`node reboot -node -inhibit-takeover true` + // 2023 Oct 24, ONTAPDOC-1201 // 2023 Oct 02, ONTAPDOC-1388 // 2023 SEP 1, ONTAPDOC-836 From 28cb639734c273e914b024160e5f759b48eb78d3 Mon Sep 17 00:00:00 2001 From: netapp-aoife Date: Mon, 8 Jan 2024 17:54:40 +0000 Subject: [PATCH 07/27] minor reword --- upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc b/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc index a74e858ae..a718bd2a7 100644 --- a/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc +++ b/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc @@ -11,7 +11,7 @@ summary: 'You can add four new nodes to the MetroCluster IP configuration as a s [.lead] Depending on your ONTAP version, you can expand your MetroCluster IP configuration by adding four new nodes as a new DR group. -In ONTAP 9.13.1 and later, you can temporarily expand an eight-node MetroCLuster configuration to upgrade the controllers and storage. Refer to link:https://docs.netapp.com/us-en/ontap-metrocluster/upgrade/task_refresh_4n_mcc_ip.html[Refreshing a four-node or an eight-node MetroCluster IP configuration (ONTAP 9.8 and later)] for more information. +In ONTAP 9.13.1 and later, you can temporarily expand an eight-node MetroCluster configuration to upgrade the controllers and storage. Refer to link:https://docs.netapp.com/us-en/ontap-metrocluster/upgrade/task_refresh_4n_mcc_ip.html[Refreshing a four-node or an eight-node MetroCluster IP configuration (ONTAP 9.8 and later)] for more information. Beginning with ONTAP 9.9.1, you can add four new nodes to the MetroCluster IP configuration as a second DR group. This creates an eight-node MetroCluster configuration. @@ -19,7 +19,7 @@ Beginning with ONTAP 9.9.1, you can add four new nodes to the MetroCluster IP co * The old and new nodes must be running the same version of ONTAP. -* This procedure describes the steps required to expand one four-node DR group. If you are refreshing an eight-node configuration and need to expand two DR groups, you must repeat the entire procedure for each DR group, expanding one at a time. +* This procedure describes the steps required to add one four-node DR group to an existing MetroCluster IP configuration. If you are refreshing an eight-node configuration and need to temporarily add two DR groups, you must repeat the entire procedure for each DR group, adding one at a time. * Verify that the old and new platform models are supported for platform mixing. + From 7602013ecea4254b35e7f98f66f13c037f6ac3bd Mon Sep 17 00:00:00 2001 From: netapp-pcarriga Date: Tue, 9 Jan 2024 13:23:21 +0000 Subject: [PATCH 08/27] Edits post review --- .../port_usage_fc_switches_91_and_later.adoc | 32 +++++++++---------- 1 file changed, 15 insertions(+), 17 deletions(-) diff --git a/_include/port_usage_fc_switches_91_and_later.adoc b/_include/port_usage_fc_switches_91_and_later.adoc index b7fac8209..a0bfca058 100644 --- a/_include/port_usage_fc_switches_91_and_later.adoc +++ b/_include/port_usage_fc_switches_91_and_later.adoc @@ -2906,18 +2906,20 @@ a| 48 |=== -== Cisco 9132T port usage in MetroCluster 4-node and 8-node configurations running ONTAP 9.1 and later +== Cisco 9132T port usage in MetroCluster 4-node and 8-node configurations running ONTAP 9.4 and later -The following tables show the port usage on a Cisco 9132T switch. The tables show the maximum supported configurations with four and eight controller modules in two DR groups. +The following table shows the port usage on a Cisco 9132T switch. The table shows the maximum supported configurations with four and eight controller modules in two DR groups. + +NOTE: For 8-node configurations, you must perform the zoning manually because RCFs are not provided. |=== -6+^h| Configurations using FibreBridge 7500N or 7600N using both FC ports (FC1 and FC2) -6+^h| MetroCluster 1 or DR Group 1 -3+^h| +7+^h| Configurations using FibreBridge 7500N or 7600N using both FC ports (FC1 and FC2) +7+^h| MetroCluster 1 or DR Group 1 +4+^h| 2+^h| 4-node h| 8-node -h| Component h| Port h| Connects to FC_switch... h| 9132T (1x LEM) h| 9132T (2x LEM) h| 9132T (2x LEM) -.8+a| +2+^h| Component h| Port h| Connects to FC_switch... h| 9132T (1x LEM) h| 9132T (2x LEM) h| 9132T (2x LEM) +2.8+a| controller_x_1 a| FC-VI port a @@ -2999,7 +3001,7 @@ a| LEM1-6 a| LEM1-4 -.8+a| +2.8+a| controller_x_2 a| FC-VI port a @@ -3081,8 +3083,8 @@ a| LEM1-12 a| LEM1-8 -6+^h| MetroCluster 2 or DR Group 2 -.8+a| +7+^h| MetroCluster 2 or DR Group 2 +2.8+a| controller_x_3 a| FC-VI port a @@ -3149,7 +3151,7 @@ a| | a| LEM2-4 -.8+a| +2.8+a| controller_x_4 a| FC-VI-1 port a @@ -3215,12 +3217,6 @@ a| | a| LEM2-8 -|=== - -For 8-node configurations, you must perform the zoning manually because RCFs are not provided. - -|=== -7+^h| Configurations using FibreBridge 7500N or 7600N using both FC ports (FC1 and FC2) 7+^h| MetroCluster 1 or DR Group 1 4+^h| 2+^h| 4-node @@ -3407,6 +3403,8 @@ LEM2-12 * Only one (1) bridge stack is supported using 9132T switches with 1x LEM Module. ==== +== Cisco 9132T port usage for ISLs in four and eight-node configurations in a MetroCluster configuration running ONTAP 9.1 or later + The following table shows ISL port usage for a Cisco 9132T switch. |=== From 9b11b65c5bb367c955205023b6bd6e687aa0b78b Mon Sep 17 00:00:00 2001 From: netapp-pcarriga Date: Tue, 9 Jan 2024 14:52:04 +0000 Subject: [PATCH 09/27] edits --- install-fc/task_install_the_brocade_fc_switch_rcf_file.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/install-fc/task_install_the_brocade_fc_switch_rcf_file.adoc b/install-fc/task_install_the_brocade_fc_switch_rcf_file.adoc index f3ae6b7e8..56b1b8ec2 100644 --- a/install-fc/task_install_the_brocade_fc_switch_rcf_file.adoc +++ b/install-fc/task_install_the_brocade_fc_switch_rcf_file.adoc @@ -13,7 +13,8 @@ When you configure a Brocade FC switch, you can install the switch configuration .About this task -These steps must be repeated on each of the Brocade FC switches in the MetroCluster fabric configuration. +* These steps must be repeated on each of the Brocade FC switches in the MetroCluster fabric configuration. +* You must provide any additional settings not documented in this procedure if they are required on the Inter-Switch Links (ISL) because of your specific DWDM configuration. .Steps From df1e4e38f031f6b54193ef1886ceda482fb067c0 Mon Sep 17 00:00:00 2001 From: netapp-aoife Date: Wed, 10 Jan 2024 12:04:24 +0000 Subject: [PATCH 10/27] Gh issue 298 --- ...data_protection_and_disaster_recovery.adoc | 20 ++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/manage/concept_understanding_mcc_data_protection_and_disaster_recovery.adoc b/manage/concept_understanding_mcc_data_protection_and_disaster_recovery.adoc index 59412df68..31336b2d3 100644 --- a/manage/concept_understanding_mcc_data_protection_and_disaster_recovery.adoc +++ b/manage/concept_understanding_mcc_data_protection_and_disaster_recovery.adoc @@ -100,7 +100,7 @@ The following table shows the state (online or offline) of an unmirrored aggrega |=== -h| Type of switchover h| State +h| Type of switchover h| MetroCluster IP state h| MetroCluster FC state a| Negotiated switchover (NSO) @@ -108,12 +108,22 @@ Negotiated switchover (NSO) a| Online +a| + +* Mirrored aggregates: Online +* Unmirrored aggregates: Offline + a| Automatic unplanned switchover (AUSO) a| Online +a| + +* Mirrored aggregates: Online +* Unmirrored aggregates: Offline + a| Unplanned switchover (USO) @@ -122,8 +132,16 @@ a| * If storage is not available: Offline * If storage is available: Online +a| + +* Mirrored aggregates: Online +* Unmirrored aggregates: Offline + +a| |=== +Learn more about <>. + NOTE: After a switchover, if the unmirrored aggregate is at the DR partner node and there is an inter-switch link (ISL) failure, then that local node might fail. The following illustration shows how disk pools are mirrored between the partner clusters. Data in local plexes (in pool0) is replicated to remote plexes (in pool1). From 58dc31b29a10028334dffd5703cf626bb5cd50e5 Mon Sep 17 00:00:00 2001 From: netapp-aoife Date: Wed, 10 Jan 2024 12:13:19 +0000 Subject: [PATCH 11/27] minor edits --- ..._data_protection_and_disaster_recovery.adoc | 18 +++++++----------- 1 file changed, 7 insertions(+), 11 deletions(-) diff --git a/manage/concept_understanding_mcc_data_protection_and_disaster_recovery.adoc b/manage/concept_understanding_mcc_data_protection_and_disaster_recovery.adoc index 31336b2d3..fb42129e8 100644 --- a/manage/concept_understanding_mcc_data_protection_and_disaster_recovery.adoc +++ b/manage/concept_understanding_mcc_data_protection_and_disaster_recovery.adoc @@ -100,19 +100,18 @@ The following table shows the state (online or offline) of an unmirrored aggrega |=== -h| Type of switchover h| MetroCluster IP state h| MetroCluster FC state +h| Type of switchover h| MetroCluster FC state h| MetroCluster IP state a| Negotiated switchover (NSO) a| -Online +Online a| +Offline -* Mirrored aggregates: Online -* Unmirrored aggregates: Offline - +NOTE: After the NSO is complete, you can manually bring unmirrored aggregates online. a| Automatic unplanned switchover (AUSO) @@ -120,9 +119,7 @@ a| Online a| - -* Mirrored aggregates: Online -* Unmirrored aggregates: Offline +Offline a| Unplanned switchover (USO) @@ -133,13 +130,12 @@ a| * If storage is available: Online a| - -* Mirrored aggregates: Online -* Unmirrored aggregates: Offline +Offline a| |=== + Learn more about <>. NOTE: After a switchover, if the unmirrored aggregate is at the DR partner node and there is an inter-switch link (ISL) failure, then that local node might fail. From e02055cce7c0f32d98240c9d18555258ebcbb27e Mon Sep 17 00:00:00 2001 From: netapp-aoife Date: Tue, 16 Jan 2024 10:38:43 +0000 Subject: [PATCH 12/27] ONTAPDOC-729, adding more checks --- transition/task_configure_transition.adoc | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) diff --git a/transition/task_configure_transition.adoc b/transition/task_configure_transition.adoc index d17defb5d..eea0b408d 100644 --- a/transition/task_configure_transition.adoc +++ b/transition/task_configure_transition.adoc @@ -684,6 +684,11 @@ Do you want to continue? {y|n}: y cluster_A::> .... +. Verify that all nodes in the cluster are healthy: ++ +`cluster show` ++ +The output should show that all nodes are reporting the 'health' field as `true`. . Confirm that takeover is possible and the nodes are connected by running the following command on both clusters: + @@ -700,12 +705,26 @@ Node_IP_1 Node_IP_2 true Connected to Node_IP_2 Node_IP_2 Node_IP_1 true Connected to Node_IP_1 ---- +. Confirm that all disks attached to the newly-joined MetroCluster IP nodes are present: ++ +`disk show` + +. Verify that all nodes are in `normal` mode: ++ +`metrocluster node show` + +. Verify the health of the MetroCluster configuration by running the following commands: ++ +.. `metrocluster check run` +.. `metrocluster check show` +.. `metrocluster interconnect mirror show` +.. `metrocluster interconnect adapter show` + . Move the MDV_CRS volumes from the old nodes to the new nodes in advanced privilege. .. Display the volumes to identify the MDV volumes: + NOTE: If you have a single mirrored data aggregate per site then move both the MDV volumes to this single aggregate. If you have two or more mirrored data aggregates, then move each MDV volume to a different aggregate. + - The following example shows the MDV volumes in the volume show output: + .... From 17da97b0df3c02099d73bb5f5e9251bf16a2a49f Mon Sep 17 00:00:00 2001 From: netapp-aoife Date: Tue, 16 Jan 2024 11:04:21 +0000 Subject: [PATCH 13/27] minor edits --- transition/task_configure_transition.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/transition/task_configure_transition.adoc b/transition/task_configure_transition.adoc index eea0b408d..d91ceaeb2 100644 --- a/transition/task_configure_transition.adoc +++ b/transition/task_configure_transition.adoc @@ -688,7 +688,7 @@ cluster_A::> + `cluster show` + -The output should show that all nodes are reporting the 'health' field as `true`. +The output should show that the `health` field for all nodes is displayed as `true`. . Confirm that takeover is possible and the nodes are connected by running the following command on both clusters: + From 0de1856fa9bf0735a5a842a9002e524575c83ff1 Mon Sep 17 00:00:00 2001 From: netapp-aoife Date: Tue, 16 Jan 2024 17:10:36 +0000 Subject: [PATCH 14/27] SME feedback --- transition/task_configure_transition.adoc | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/transition/task_configure_transition.adoc b/transition/task_configure_transition.adoc index d91ceaeb2..2673df23b 100644 --- a/transition/task_configure_transition.adoc +++ b/transition/task_configure_transition.adoc @@ -602,7 +602,7 @@ You must respond with `y` when you are prompted to continue into advanced mode a .. Configure the MetroCluster with the `-allow-with-one-aggregate true` parameter: + -`metrocluster configure -allow-with-one-aggregate true _node-name_` +`metrocluster configure -allow-with-one-aggregate true -node-name ` .. Return to the admin privilege level: + @@ -709,10 +709,6 @@ Node_IP_2 Node_IP_1 true Connected to Node_IP_1 + `disk show` -. Verify that all nodes are in `normal` mode: -+ -`metrocluster node show` - . Verify the health of the MetroCluster configuration by running the following commands: + .. `metrocluster check run` From 2901b187006cec2adce229405cfd103d08c1705c Mon Sep 17 00:00:00 2001 From: netapp-aoife Date: Tue, 16 Jan 2024 17:47:36 +0000 Subject: [PATCH 15/27] minor edit --- transition/task_configure_transition.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/transition/task_configure_transition.adoc b/transition/task_configure_transition.adoc index 2673df23b..d7f786b43 100644 --- a/transition/task_configure_transition.adoc +++ b/transition/task_configure_transition.adoc @@ -586,7 +586,7 @@ Multiple data aggregates a| From any node's prompt, configure MetroCluster: -`metrocluster configure _node-name_` +`metrocluster configure ` NOTE: You must run `metrocluster configure` and *not* `metrocluster configure -refresh true` From 9fd2095e355101de99fc6ad49a25f3b9d52d0eeb Mon Sep 17 00:00:00 2001 From: netapp-pcarriga Date: Thu, 18 Jan 2024 15:08:36 +0000 Subject: [PATCH 16/27] Minor updates --- _include/port_usage_fc_switches_91_and_later.adoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/_include/port_usage_fc_switches_91_and_later.adoc b/_include/port_usage_fc_switches_91_and_later.adoc index a0bfca058..e71eb8c26 100644 --- a/_include/port_usage_fc_switches_91_and_later.adoc +++ b/_include/port_usage_fc_switches_91_and_later.adoc @@ -1477,6 +1477,7 @@ a| The tables show the maximum supported configurations, with eight controller modules in two DR groups. For smaller configurations, ignore the rows for the additional controller modules. +NOTE: For Cisco 9132T, see <>. |=== @@ -2845,6 +2846,7 @@ Additional bridges can be attached using ports 25 through 48 following the same The following table shows ISL port usage. ISL port usage is the same on all switches in the configuration. +NOTE: For Cisco 9132T, see <>. |=== @@ -2906,6 +2908,7 @@ a| 48 |=== +[[cisco_9132t_port]] == Cisco 9132T port usage in MetroCluster 4-node and 8-node configurations running ONTAP 9.4 and later The following table shows the port usage on a Cisco 9132T switch. The table shows the maximum supported configurations with four and eight controller modules in two DR groups. @@ -3403,6 +3406,7 @@ LEM2-12 * Only one (1) bridge stack is supported using 9132T switches with 1x LEM Module. ==== +[[cisco_9132t_port_isl]] == Cisco 9132T port usage for ISLs in four and eight-node configurations in a MetroCluster configuration running ONTAP 9.1 or later The following table shows ISL port usage for a Cisco 9132T switch. From 0e1d751f6880e3c7eac1762960545b376bc724c4 Mon Sep 17 00:00:00 2001 From: netapp-aoife Date: Mon, 22 Jan 2024 13:31:56 +0000 Subject: [PATCH 17/27] minor edit --- ...nderstanding_mcc_data_protection_and_disaster_recovery.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/manage/concept_understanding_mcc_data_protection_and_disaster_recovery.adoc b/manage/concept_understanding_mcc_data_protection_and_disaster_recovery.adoc index fb42129e8..f69390ac9 100644 --- a/manage/concept_understanding_mcc_data_protection_and_disaster_recovery.adoc +++ b/manage/concept_understanding_mcc_data_protection_and_disaster_recovery.adoc @@ -100,7 +100,7 @@ The following table shows the state (online or offline) of an unmirrored aggrega |=== -h| Type of switchover h| MetroCluster FC state h| MetroCluster IP state +h| Type of switchover h| MetroCluster FC configuration state h| MetroCluster IP configuration state a| Negotiated switchover (NSO) @@ -813,6 +813,7 @@ If SVMs were deleted on the surviving site while the MetroCluster configuration * Deletes the corresponding SVMs on the partner site (the former disaster site). * Deletes any peering relationships of the deleted SVMs. +// 2023 Jan 22, GH issue 298 // 2023-APR-20, BURT 1532596 // 2023-FEB-28, ONTAPDOC-719 // 2022-JAN-20, BURT 1448684 From 6466740169e4d965cdecfb0832f039093c7b18d8 Mon Sep 17 00:00:00 2001 From: netapp-pcarriga Date: Tue, 23 Jan 2024 17:08:18 +0000 Subject: [PATCH 18/27] removing update not belonging to this JIRA --- install-fc/task_install_the_brocade_fc_switch_rcf_file.adoc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/install-fc/task_install_the_brocade_fc_switch_rcf_file.adoc b/install-fc/task_install_the_brocade_fc_switch_rcf_file.adoc index 56b1b8ec2..f3ae6b7e8 100644 --- a/install-fc/task_install_the_brocade_fc_switch_rcf_file.adoc +++ b/install-fc/task_install_the_brocade_fc_switch_rcf_file.adoc @@ -13,8 +13,7 @@ When you configure a Brocade FC switch, you can install the switch configuration .About this task -* These steps must be repeated on each of the Brocade FC switches in the MetroCluster fabric configuration. -* You must provide any additional settings not documented in this procedure if they are required on the Inter-Switch Links (ISL) because of your specific DWDM configuration. +These steps must be repeated on each of the Brocade FC switches in the MetroCluster fabric configuration. .Steps From ed6e6ee30f98c429f335591232e24623257edd04 Mon Sep 17 00:00:00 2001 From: Paula Carrigan <77334475+netapp-pcarriga@users.noreply.github.com> Date: Tue, 23 Jan 2024 17:33:16 +0000 Subject: [PATCH 19/27] Update _include/port_usage_fc_switches_91_and_later.adoc Co-authored-by: Aoife Hegarty <92876203+netapp-aoife@users.noreply.github.com> --- _include/port_usage_fc_switches_91_and_later.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_include/port_usage_fc_switches_91_and_later.adoc b/_include/port_usage_fc_switches_91_and_later.adoc index e71eb8c26..f461219bd 100644 --- a/_include/port_usage_fc_switches_91_and_later.adoc +++ b/_include/port_usage_fc_switches_91_and_later.adoc @@ -2913,7 +2913,7 @@ a| The following table shows the port usage on a Cisco 9132T switch. The table shows the maximum supported configurations with four and eight controller modules in two DR groups. -NOTE: For 8-node configurations, you must perform the zoning manually because RCFs are not provided. +NOTE: For eight-node configurations, you must perform the zoning manually because RCFs are not provided. |=== 7+^h| Configurations using FibreBridge 7500N or 7600N using both FC ports (FC1 and FC2) From 8d5a04e276a9651ed2ef73acc49c70b23ce4e7b0 Mon Sep 17 00:00:00 2001 From: netapp-pcarriga Date: Tue, 23 Jan 2024 17:38:30 +0000 Subject: [PATCH 20/27] edits post IE review --- .../port_usage_fc_switches_91_and_later.adoc | 20 +++++++++---------- install-ip/using_rcf_generator.adoc | 2 +- 2 files changed, 11 insertions(+), 11 deletions(-) diff --git a/_include/port_usage_fc_switches_91_and_later.adoc b/_include/port_usage_fc_switches_91_and_later.adoc index e71eb8c26..62250bcba 100644 --- a/_include/port_usage_fc_switches_91_and_later.adoc +++ b/_include/port_usage_fc_switches_91_and_later.adoc @@ -2909,18 +2909,18 @@ a| |=== [[cisco_9132t_port]] -== Cisco 9132T port usage in MetroCluster 4-node and 8-node configurations running ONTAP 9.4 and later +== Cisco 9132T port usage in MetroCluster four-node and eight-node configurations running ONTAP 9.4 and later The following table shows the port usage on a Cisco 9132T switch. The table shows the maximum supported configurations with four and eight controller modules in two DR groups. -NOTE: For 8-node configurations, you must perform the zoning manually because RCFs are not provided. +NOTE: For eight-node configurations, you must perform the zoning manually because RCFs are not provided. |=== 7+^h| Configurations using FibreBridge 7500N or 7600N using both FC ports (FC1 and FC2) 7+^h| MetroCluster 1 or DR Group 1 4+^h| -2+^h| 4-node -h| 8-node +2+^h| Four-node +h| Eight-node 2+^h| Component h| Port h| Connects to FC_switch... h| 9132T (1x LEM) h| 9132T (2x LEM) h| 9132T (2x LEM) 2.8+a| controller_x_1 @@ -3222,8 +3222,8 @@ a| LEM2-8 7+^h| MetroCluster 1 or DR Group 1 4+^h| -2+^h| 4-node -h| 8-node +2+^h| Four-node +h| Eight-node 2+^h| FibreBridge 7500 using two FC ports h| Port h| Connects to FC_switch... h| 9132T (1x LEM) h| 9132T (2x LEM) h| 9132T (2x LEM) .4+a| Stack 1 @@ -3401,8 +3401,8 @@ LEM2-12 [NOTE] ==== -* In 4-node configurations, you can cable additional bridges to ports LEM2-5 through LEM2-8 in 9132T switches with 2x LEMs. -* In 8-node configurations, you can cable additional bridges to ports LEM2-13 through LEM2-16 in 9132T switches with 2x LEMs. +* In four-node configurations, you can cable additional bridges to ports LEM2-5 through LEM2-8 in 9132T switches with 2x LEMs. +* In eight-node configurations, you can cable additional bridges to ports LEM2-13 through LEM2-16 in 9132T switches with 2x LEMs. * Only one (1) bridge stack is supported using 9132T switches with 1x LEM Module. ==== @@ -3414,8 +3414,8 @@ The following table shows ISL port usage for a Cisco 9132T switch. |=== 4+^h| MetroCluster 1 or DR Group 1 .2+h| Port -2+^h| 4-node -h| 8-node +2+^h| Four-node +h| Eight-node h| 9132T (1x LEM) h| 9132T (2x LEM) h| 9132T (2x LEM) |ISL1 |LEM1-15 diff --git a/install-ip/using_rcf_generator.adoc b/install-ip/using_rcf_generator.adoc index 1ef488eee..cfbf0693a 100644 --- a/install-ip/using_rcf_generator.adoc +++ b/install-ip/using_rcf_generator.adoc @@ -25,7 +25,7 @@ Use this cabling overview to verify your cabling. == Cabling eight-node MetroCluster configurations -For MetroCluster configuration running ONTAP 9.8 and earlier, some procedures that are performed to transition an upgrade require the addition of a second four-node DR group to the configuration to create a temporary eight-node configuration. Beginning with ONTAP 9.9.1, permanent 8-node MetroCluster configurations are supported. +For MetroCluster configuration running ONTAP 9.8 and earlier, some procedures that are performed to transition an upgrade require the addition of a second four-node DR group to the configuration to create a temporary eight-node configuration. Beginning with ONTAP 9.9.1, permanent eight-node MetroCluster configurations are supported. .About this task From 4d530ab578754f6ca46b140488b7ab8a841ad2ca Mon Sep 17 00:00:00 2001 From: netapp-aoife Date: Tue, 23 Jan 2024 17:56:34 +0000 Subject: [PATCH 21/27] add file comment --- transition/task_configure_transition.adoc | 1 + 1 file changed, 1 insertion(+) diff --git a/transition/task_configure_transition.adoc b/transition/task_configure_transition.adoc index d7f786b43..0654a52df 100644 --- a/transition/task_configure_transition.adoc +++ b/transition/task_configure_transition.adoc @@ -778,6 +778,7 @@ cluster_A MDV_CRS_d6b0b313ff5611e9837100a098544e51_B + `set -privilege admin` +// 2023 Jan 23, ONTAPDOC-729 // 22 Jun 2023, GH issue 243 // BURT 1448684, 21 JAN 2022 // BURT 1438441, 28 MAR 2022 From 0a6e593c13123a45923942f755b55d5a199726fe Mon Sep 17 00:00:00 2001 From: Aoife Hegarty <92876203+netapp-aoife@users.noreply.github.com> Date: Tue, 23 Jan 2024 18:22:53 +0000 Subject: [PATCH 22/27] Update transition/task_configure_transition.adoc Co-authored-by: Paula Carrigan <77334475+netapp-pcarriga@users.noreply.github.com> --- transition/task_configure_transition.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/transition/task_configure_transition.adoc b/transition/task_configure_transition.adoc index 0654a52df..9eda38e9d 100644 --- a/transition/task_configure_transition.adoc +++ b/transition/task_configure_transition.adoc @@ -688,7 +688,7 @@ cluster_A::> + `cluster show` + -The output should show that the `health` field for all nodes is displayed as `true`. +The output should display `true` for the `health` field for all nodes. . Confirm that takeover is possible and the nodes are connected by running the following command on both clusters: + From 1e85186b754b56945c13beacd93f0cad4df8730e Mon Sep 17 00:00:00 2001 From: netapp-aoife Date: Tue, 23 Jan 2024 18:56:46 +0000 Subject: [PATCH 23/27] SME edits and remove separate update --- .../task_expand_a_four_node_mcc_ip_configuration.adoc | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc b/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc index a718bd2a7..43ecf24bb 100644 --- a/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc +++ b/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc @@ -11,7 +11,7 @@ summary: 'You can add four new nodes to the MetroCluster IP configuration as a s [.lead] Depending on your ONTAP version, you can expand your MetroCluster IP configuration by adding four new nodes as a new DR group. -In ONTAP 9.13.1 and later, you can temporarily expand an eight-node MetroCluster configuration to upgrade the controllers and storage. Refer to link:https://docs.netapp.com/us-en/ontap-metrocluster/upgrade/task_refresh_4n_mcc_ip.html[Refreshing a four-node or an eight-node MetroCluster IP configuration (ONTAP 9.8 and later)] for more information. +In ONTAP 9.13.1 and later, you can temporarily expand an eight-node MetroCluster configuration to refresh the controllers and storage. Refer to link:https://docs.netapp.com/us-en/ontap-metrocluster/upgrade/task_refresh_4n_mcc_ip.html[Refreshing a four-node or an eight-node MetroCluster IP configuration (ONTAP 9.8 and later)] for more information. Beginning with ONTAP 9.9.1, you can add four new nodes to the MetroCluster IP configuration as a second DR group. This creates an eight-node MetroCluster configuration. @@ -19,7 +19,7 @@ Beginning with ONTAP 9.9.1, you can add four new nodes to the MetroCluster IP co * The old and new nodes must be running the same version of ONTAP. -* This procedure describes the steps required to add one four-node DR group to an existing MetroCluster IP configuration. If you are refreshing an eight-node configuration and need to temporarily add two DR groups, you must repeat the entire procedure for each DR group, adding one at a time. +* This procedure describes the steps required to add one four-node DR group to an existing MetroCluster IP configuration. If you are refreshing an eight-node configuration, you must repeat the entire procedure for each DR group, adding one at a time. * Verify that the old and new platform models are supported for platform mixing. + @@ -1059,10 +1059,7 @@ node_A_4-new false 4 entries were displayed. ---- -. Reboot each of the new nodes: -+ -`node reboot -node -inhibit-takeover true` - +// 2024 Jan 23, ONTAPDOC-1494 // 2023 Oct 24, ONTAPDOC-1201 // 2023 Oct 02, ONTAPDOC-1388 // 2023 SEP 1, ONTAPDOC-836 From 1b81f0a295e745c35774961ec0671065fc2ae80d Mon Sep 17 00:00:00 2001 From: netapp-aoife Date: Tue, 23 Jan 2024 19:02:30 +0000 Subject: [PATCH 24/27] minor edit --- upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc b/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc index 43ecf24bb..c2360f8f3 100644 --- a/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc +++ b/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc @@ -11,7 +11,7 @@ summary: 'You can add four new nodes to the MetroCluster IP configuration as a s [.lead] Depending on your ONTAP version, you can expand your MetroCluster IP configuration by adding four new nodes as a new DR group. -In ONTAP 9.13.1 and later, you can temporarily expand an eight-node MetroCluster configuration to refresh the controllers and storage. Refer to link:https://docs.netapp.com/us-en/ontap-metrocluster/upgrade/task_refresh_4n_mcc_ip.html[Refreshing a four-node or an eight-node MetroCluster IP configuration (ONTAP 9.8 and later)] for more information. +Beginning with ONTAP 9.13.1 and later, you can temporarily expand an eight-node MetroCluster configuration to refresh the controllers and storage. Refer to link:https://docs.netapp.com/us-en/ontap-metrocluster/upgrade/task_refresh_4n_mcc_ip.html[Refreshing a four-node or an eight-node MetroCluster IP configuration (ONTAP 9.8 and later)] for more information. Beginning with ONTAP 9.9.1, you can add four new nodes to the MetroCluster IP configuration as a second DR group. This creates an eight-node MetroCluster configuration. From 95c4a67274402d7116e6e253001168ebb974731e Mon Sep 17 00:00:00 2001 From: netapp-aoife Date: Wed, 24 Jan 2024 10:13:56 +0000 Subject: [PATCH 25/27] SME review --- ...anding_mcc_data_protection_and_disaster_recovery.adoc | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/manage/concept_understanding_mcc_data_protection_and_disaster_recovery.adoc b/manage/concept_understanding_mcc_data_protection_and_disaster_recovery.adoc index f69390ac9..d18f85656 100644 --- a/manage/concept_understanding_mcc_data_protection_and_disaster_recovery.adoc +++ b/manage/concept_understanding_mcc_data_protection_and_disaster_recovery.adoc @@ -109,9 +109,7 @@ a| Online a| -Offline - -NOTE: After the NSO is complete, you can manually bring unmirrored aggregates online. +Offline (Note 1) a| Automatic unplanned switchover (AUSO) @@ -119,7 +117,7 @@ a| Online a| -Offline +Offline (Note 1) a| Unplanned switchover (USO) @@ -130,11 +128,12 @@ a| * If storage is available: Online a| -Offline +Offline (Note 1) a| |=== +*Note 1*: In MetroCluster IP configurations, after the switchover is complete, you can manually bring the unmirrored aggregates online. Learn more about <>. From 3031b8c30e785891bc3efd45c0a87f96a67e488d Mon Sep 17 00:00:00 2001 From: netapp-aoife Date: Wed, 24 Jan 2024 13:35:40 +0000 Subject: [PATCH 26/27] minor edit --- upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc b/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc index c2360f8f3..2f8c52cd3 100644 --- a/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc +++ b/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc @@ -11,7 +11,7 @@ summary: 'You can add four new nodes to the MetroCluster IP configuration as a s [.lead] Depending on your ONTAP version, you can expand your MetroCluster IP configuration by adding four new nodes as a new DR group. -Beginning with ONTAP 9.13.1 and later, you can temporarily expand an eight-node MetroCluster configuration to refresh the controllers and storage. Refer to link:https://docs.netapp.com/us-en/ontap-metrocluster/upgrade/task_refresh_4n_mcc_ip.html[Refreshing a four-node or an eight-node MetroCluster IP configuration (ONTAP 9.8 and later)] for more information. +Beginning with ONTAP 9.13.1, you can temporarily expand an eight-node MetroCluster configuration to refresh the controllers and storage. Refer to link:https://docs.netapp.com/us-en/ontap-metrocluster/upgrade/task_refresh_4n_mcc_ip.html[Refreshing a four-node or an eight-node MetroCluster IP configuration (ONTAP 9.8 and later)] for more information. Beginning with ONTAP 9.9.1, you can add four new nodes to the MetroCluster IP configuration as a second DR group. This creates an eight-node MetroCluster configuration. From 436a4b6efef6ab781d581c3a57652cf8836ad96f Mon Sep 17 00:00:00 2001 From: Aoife Hegarty <92876203+netapp-aoife@users.noreply.github.com> Date: Wed, 24 Jan 2024 15:05:29 +0000 Subject: [PATCH 27/27] Update upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc Co-authored-by: Paula Carrigan <77334475+netapp-pcarriga@users.noreply.github.com> --- upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc b/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc index 2f8c52cd3..323d148ce 100644 --- a/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc +++ b/upgrade/task_expand_a_four_node_mcc_ip_configuration.adoc @@ -11,7 +11,7 @@ summary: 'You can add four new nodes to the MetroCluster IP configuration as a s [.lead] Depending on your ONTAP version, you can expand your MetroCluster IP configuration by adding four new nodes as a new DR group. -Beginning with ONTAP 9.13.1, you can temporarily expand an eight-node MetroCluster configuration to refresh the controllers and storage. Refer to link:https://docs.netapp.com/us-en/ontap-metrocluster/upgrade/task_refresh_4n_mcc_ip.html[Refreshing a four-node or an eight-node MetroCluster IP configuration (ONTAP 9.8 and later)] for more information. +Beginning with ONTAP 9.13.1, you can temporarily expand an eight-node MetroCluster configuration to refresh the controllers and storage. See link:https://docs.netapp.com/us-en/ontap-metrocluster/upgrade/task_refresh_4n_mcc_ip.html[Refreshing a four-node or an eight-node MetroCluster IP configuration (ONTAP 9.8 and later)] for more information. Beginning with ONTAP 9.9.1, you can add four new nodes to the MetroCluster IP configuration as a second DR group. This creates an eight-node MetroCluster configuration.