Determining the system IDs and VLAN IDs of the old controller modules

After you have replaced all hardware at the disaster site, you must determine the system IDs of the replaced controller modules. You need the old system IDs when you reassign disks to the new controller modules. If the systems are AFF A220, AFF A250, AFF A400, AFF A800, FAS2750, FAS500f, FAS8300, or FAS8700 models, you must also determine the VLAN IDs used by the MCC IP interfaces.

Before you begin

All equipment at the disaster site must be powered off.

About this task

This discussion provides examples for two and four-node configurations. For eight-node configurations, you must account for any failures in the additional nodes on the second DR group.

For a two-node MetroCluster configuration, you can ignore references to the second controller module at each site.

The examples in this procedure are based on the following assumptions:
  • Site A is the disaster site.
  • node_A_1 has failed and is being completely replaced.
  • node_A_2 has failed and is being completely replaced.

    node _A_2 is present in a four-node MetroCluster configuration only.

  • Site B is the surviving site.
  • node_B_1 is healthy.
  • node_B_2 is healthy.

    node_B_2 is present in a four-node MetroCluster configuration only.

The controller modules have the following original system IDs:
Number of nodes in MetroCluster configuration Node Original system ID
Four node_A_1 4068741258
node_A_2 4068741260
node_B_1 4068741254
node_B_2 4068741256
Two node_A_1 4068741258
node_B_1 4068741254

Procedure

  1. From the surviving site, display the system IDs of the nodes in the MetroCluster configuration.
    Number of nodes in MetroCluster configuration Use this command
    Four or eight metrocluster node show -fields node-systemid,ha-partner-systemid,dr-partner-systemid,dr-auxiliary-systemid
    Two metrocluster node show -fields node-systemid,dr-partner-systemid
    In this example for a four-node MetroCluster configuration, the following old system IDs are retrieved:
    • Node_A_1: 4068741258
    • Node_A_2: 4068741260
    Disks owned by the old controller modules are still owned these system IDs.
    metrocluster node show -fields node-systemid,ha-partner-systemid,dr-partner-systemid,dr-auxiliary-systemid 
    
    dr-group-id cluster    node      node-systemid ha-partner-systemid dr-partner-systemid dr-auxiliary-systemid 
    ----------- ---------- --------  ------------- ------ ------------ ------ ------------ ------ -------------- 
    1           Cluster_A  Node_A_1  4068741258    4068741260          4068741254          4068741256            
    1           Cluster_A  Node_A_2  4068741260    4068741258          4068741256          4068741254            
    1           Cluster_B  Node_B_1  -             -                   -                   -                     
    1           Cluster_B  Node_B_2  -             -                   -                   -                     
    4 entries were displayed.
    In this example for a two-node MetroCluster configuration, the following old system ID is retrieved:
    • Node_A_1: 4068741258
    Disks owned by the old controller module are still owned this system ID.
    metrocluster node show -fields node-systemid,dr-partner-systemid
    
    dr-group-id cluster    node      node-systemid dr-partner-systemid  
    ----------- ---------- --------  ------------- ------------  
    1           Cluster_A  Node_A_1  4068741258    4068741254           
    1           Cluster_B  Node_B_1  -             -                              
    2 entries were displayed.
  2. For MetroCluster IP configurations using the ONTAP Mediator service, get the IP address of the ONTAP Mediator service: storage iscsi-initiator show -node * -label mediator
  3. If the systems are AFF A220, AFF A400, FAS2750, FAS8300, or FAS8700 models, determine the VLAN IDs: metrocluster interconnect show
    The VLAN IDs are included in the adapter name shown in the Adapter column of the output.
    In this example the VLAN IDs are 120 and 130:
    metrocluster interconnect show
                              Mirror   Mirror
                      Partner Admin    Oper
    Node Partner Name Type    Status   Status  Adapter Type   Status
    ---- ------------ ------- -------- ------- ------- ------ ------
    Node_A_1 Node_A_2 HA      enabled  online
                                               e0a-120 iWARP  Up
                                               e0b-130 iWARP  Up
             Node_B_1 DR      enabled  online
                                               e0a-120 iWARP  Up
                                               e0b-130 iWARP  Up
             Node_B_2 AUX     enabled  offline
                                               e0a-120 iWARP  Up
                                               e0b-130 iWARP  Up
    Node_A_2 Node_A_1 HA      enabled  online
                                               e0a-120 iWARP  Up
                                               e0b-130 iWARP  Up
             Node_B_2 DR      enabled  online
                                               e0a-120 iWARP  Up
                                               e0b-130 iWARP  Up
             Node_B_1 AUX     enabled  offline
                                               e0a-120 iWARP  Up
                                               e0b-130 iWARP  Up
    12 entries were displayed.