Setting required environmental variables in MetroCluster IP configurations

In MetroCluster IP configurations, you must retrieve the IP address of the MetroCluster interfaces on the Ethernet ports, and then use them to configure the interfaces on the replacement controller modules.

About this task

This task is required only in MetroCluster IP configurations.

Commands in this task are performed from the cluster prompt of the surviving site and from the LOADER prompt of the nodes at the disaster site.

From the surviving site, gather the IP addresses of the MetroCluster interfaces on the disaster site: metrocluster configuration-settings connection show
The required addresses are the DR Partner addresses shown in the Destination Network Address column.

If the systems are AFA DM5000F, AFA DM7100F, DM5000H, or DM7100H models, from the surviving site, and if you are not using the default VLAN IDs, determine the VLAN IDs: metrocluster configuration-settings interface show

The VLAN IDs are included in the Network Address column of the output.

Example

In this example the interfaces are e0a with the VLAN ID 120 and e0b with the VLAN ID 130:

Cluster-A::*> metrocluster configuration-settings interface show
DR                                                                     Config
Group Cluster Node     Network Address Netmask         Gateway         State
----- ------- ------- --------------- --------------- --------------- ---------
1    
      cluster_A             
              node_A_1
                  Home Port: e0a-120
                          172.17.26.10  255.255.255.0  -            completed
                  Home Port: e0b-130
                          172.17.27.10  255.255.255.0  -            completed

If the disaster site nodes are AFA DM5000F, AFA DM7100F, DM5000H, DM7100H, or FAS8700 models at the LOADER prompt for each of the disaster site nodes, set the following bootargs: setenv bootarg.mcc.port_a_ip_config local-IP-address/local-IP-mask,0,HA-partner-IP-address,DR-partner-IP-address,DR-aux-partnerIP-address,vlan-idsetenv bootarg.mcc.port_b_ip_config local-IP-address/local-IP-mask,0,HA-partner-IP-address,DR-partner-IP-address,DR-aux-partnerIP-address,vlan-id
Note
If the interfaces are using the default VLANs, the vlan-id is not necessary.
Example
The following commands set the values for node_A_1 using VLAN 120 for the first network and VLAN 130 for the second network:
setenv bootarg.mcc.port_a_ip_config 172.17.26.10/23,0,172.17.26.11,172.17.26.13,172.17.26.12,120 setenv bootarg.mcc.port_b_ip_config 172.17.27.10/23,0,172.17.27.11,172.17.27.13,172.17.27.12,130
The following commands set the values for node_A_2 using VLAN 120 for the first network and VLAN 130 for the second network:
setenv bootarg.mcc.port_a_ip_config 172.17.26.11/23,0,172.17.26.10,172.17.26.12,172.17.26.13,120 setenv bootarg.mcc.port_b_ip_config 172.17.27.11/23,0,172.17.27.10,172.17.27.12,172.17.27.13,130
Example
The following example shows the commands for node_A_1 when the default VLAN is used:
setenv bootarg.mcc.port_a_ip_config 172.17.26.10/23,0,172.17.26.11,172.17.26.13,172.17.26.12 setenv bootarg.mcc.port_b_ip_config 172.17.27.10/23,0,172.17.27.11,172.17.27.13,172.17.27.12
Example
The following example shows the commands for node_A_2 when the default VLAN is used:
setenv bootarg.mcc.port_a_ip_config 172.17.26.11/23,0,172.17.26.10,172.17.26.12,172.17.26.13 setenv bootarg.mcc.port_b_ip_config 172.17.27.11/23,0,172.17.27.10,172.17.27.12,172.17.27.13

From the surviving site, gather the UUIDs for the disaster site: metrocluster node show -fields node-cluster-uuid, node-uuid

Example

cluster_B::> metrocluster node show -fields node-cluster-uuid, node-uuid
  (metrocluster node show)
dr-group-id cluster     node     node-uuid                            node-cluster-uuid
----------- ----------- -------- ------------------------------------ ------------------------------
1           cluster_A   node_A_1 f03cb63c-9a7e-11e7-b68b-00a098908039 ee7db9d5-9a82-11e7-b68b-00a098
                                                                        908039
1           cluster_A   node_A_2 aa9a7a7a-9a81-11e7-a4e9-00a098908c35 ee7db9d5-9a82-11e7-b68b-00a098
                                                                        908039
1           cluster_B   node_B_1 f37b240b-9ac1-11e7-9b42-00a098c9e55d 07958819-9ac6-11e7-9b42-00a098
                                                                        c9e55d
1           cluster_B   node_B_2 bf8e3f8f-9ac4-11e7-bd4e-00a098ca379f 07958819-9ac6-11e7-9b42-00a098
                                                                        c9e55d
4 entries were displayed.
cluster_A::*>

Node	UUID
cluster_B	07958819-9ac6-11e7-9b42-00a098c9e55d
node_B_1	f37b240b-9ac1-11e7-9b42-00a098c9e55d
node_B_2	bf8e3f8f-9ac4-11e7-bd4e-00a098ca379f
cluster_A	ee7db9d5-9a82-11e7-b68b-00a098908039
node_A_1	f03cb63c-9a7e-11e7-b68b-00a098908039
node_A_2	aa9a7a7a-9a81-11e7-a4e9-00a098908c35

At the replacement nodes' LOADER prompt, set the UUIDs: setenv bootarg.mgwd.partner_cluster_uuid partner-cluster-UUID setenv bootarg.mgwd.cluster_uuid local-cluster-UUID setenv bootarg.mcc.pri_partner_uuid DR-partner-node-UUID setenv bootarg.mcc.aux_partner_uuid DR-aux-partner-node-UUID setenv bootarg.mcc_iscsi.node_uuid local-node-UUID

Set the UUIDs on node_A_1.

Example

The following example shows the commands for setting the UUIDs on node_A_1:

setenv bootarg.mgwd.cluster_uuid ee7db9d5-9a82-11e7-b68b-00a098908039
setenv bootarg.mgwd.partner_cluster_uuid 07958819-9ac6-11e7-9b42-00a098c9e55d
setenv bootarg.mcc.pri_partner_uuid f37b240b-9ac1-11e7-9b42-00a098c9e55d
setenv bootarg.mcc.aux_partner_uuid bf8e3f8f-9ac4-11e7-bd4e-00a098ca379f
setenv bootarg.mcc_iscsi.node_uuid f03cb63c-9a7e-11e7-b68b-00a098908039

Set the UUIDs on node_A_2:

Example

The following example shows the commands for setting the UUIDs on node_A_2:

setenv bootarg.mgwd.cluster_uuid ee7db9d5-9a82-11e7-b68b-00a098908039
setenv bootarg.mgwd.partner_cluster_uuid 07958819-9ac6-11e7-9b42-00a098c9e55d 
setenv bootarg.mcc.pri_partner_uuid bf8e3f8f-9ac4-11e7-bd4e-00a098ca379f
setenv bootarg.mcc.aux_partner_uuid f37b240b-9ac1-11e7-9b42-00a098c9e55d
setenv bootarg.mcc_iscsi.node_uuid aa9a7a7a-9a81-11e7-a4e9-00a098908c35

If the original systems were configured for ADP, at each of the replacement nodes' LOADER prompt, enable ADP, and, if running ONTAP 9.5, set bootarg.mcc.lun_part to true: setenv bootarg.mcc.adp_enabled true setenv bootarg.mcc.lun_part true
1. Set the variables on node_A_1.
  Example
  The following example shows the commands for setting the values on node_A_1:
  setenv bootarg.mcc.adp_enabled true setenv bootarg.mcc.lun_part true
2. Set the variables on node_A_2.
  Example
  The following example shows the commands for setting the values on node_A_2:
  setenv bootarg.mcc.adp_enabled true setenv bootarg.mcc.lun_part true
If the original systems were configured for ADP, at each of the replacement nodes' LOADER prompt, set the original system ID (not the system ID of the replacement controller module) and the system ID of the DR partner of the node: setenv bootarg.mcc.local_config_id original-sysID setenv bootarg.mcc.dr_partner dr_partner-sysID
Determining the system IDs of the old controller modules
1. Set the variables on node_A_1.
  Example
  The following example shows the commands for setting the system IDs on node_A_1:
  - The old system ID of node_A_1 is 4068741258.
  - The system ID of node_B_1 is 4068741254.
  setenv bootarg.mcc.local_config_id 4068741258 setenv bootarg.mcc.dr_partner 4068741254
2. Set the variables on node_A_2.
  Example
  The following example shows the commands for setting the system IDs on node_A_2:
  - The old system ID of node_A_ is 4068741260.
  - The system ID of node_B_ is 4068741256.
  setenv bootarg.mcc.local_config_id 4068741260 setenv bootarg.mcc.dr_partner 4068741256

Give documentation feedback