Skip to main content
ONTAP MetroCluster

Transitioning the MetroCluster FC nodes

Contributors netapp-martyh netapp-aoife netapp-thomi NetAppZacharyWambold

You must gather information from the existing MetroCluster FC nodes, send an autosupport message announcing the start of maintenance, and transition the nodes.

Gathering information from the existing controller modules before the transition

Before transitioning, you must gather information for each of the nodes.

This task is performed on the existing nodes:

  • node_A_1-FC

  • node_B_1-FC

    1. Gather the output for the commands in the following table.

Category Commands Notes


system license show

Shelves and numbers of disks in each shelf and flash storage details and memory and NVRAM and and network cards

system node run -node node_name sysconfig

Cluster network and node management LIFs

system node run -node node_name sysconfig network interface show -role "cluster,node-mgmt,data"

SVM information

vserver show

Protocol information

nfs show iscsi show cifs show

Physical ports

network port show -node node_name -type physical network port show

Failover Groups

network interface failover-groups show -vserver vserver_name

Record the names and ports of failover groups that are not clusterwide.

VLAN configuration

network port vlan show -node node_name

Record each network port and VLAN ID pairing.

Interface group configuration

network port ifgrp show -node node_name -instance

Record the names of the interface groups and the ports assigned to them.

Broadcast domains

network port broadcast-domain show


network ipspace show

Volume info

volume show and volume show -fields encrypt

Aggregate Info

storage aggregate show and storage aggr encryption show andstorage aggregate object-store show

Disk ownership information

storage aggregate show and storage aggr encryption show andstorage aggregate object-store show


storage failover mailbox-disk show and security key-manager backup show

Also preserve the passphrase used to enable key-manager. In the case of external key-manager you will need the authentication information for the client and server.


security key-manager show


security key-manager external show


systemshell local kenv kmip.init.ipaddr ip-address


systemshell local kenv kmip.init.netmask netmask


systemshell local kenv kmip.init.gateway gateway


systemshell local kenv kmip.init.interface interface

Sending a custom AutoSupport message prior to maintenance

Before performing the maintenance, you should issue an AutoSupport message to notify NetApp technical support that maintenance is underway. This prevents them from opening a case on the assumption that a disruption has occurred.

This task must be performed on each MetroCluster site.

  1. To prevent automatic support case generation, send an Autosupport message to indicate maintenance is underway.

    1. Issue the following command: system node autosupport invoke -node * -type all -message MAINT=maintenance-window-in-hours

      maintenance-window-in-hours specifies the length of the maintenance window, with a maximum of 72 hours. If the maintenance is completed before the time has elapsed, you can invoke an AutoSupport message indicating the end of the maintenance period:system node autosupport invoke -node * -type all -message MAINT=end

    2. Repeat the command on the partner cluster.

Transitioning, shutting down, and removing the MetroCluster FC nodes

In addition to issuing commands on the MetroCluster FC nodes, this task includes physical uncabling and removal of the controller modules at each site.

This task must be performed on each of the old nodes:

  • node_A_1-FC

  • node_B_1-FC

    1. Stop all client traffic.

    2. On either of the MetroCluster FC nodes, for example node_A_1-FC, enable transition.

      1. Set the advanced privilege level: set -priv advanced

      2. Enable transition: metrocluster transition enable -transition-mode disruptive

      3. Return to admin mode: set -priv admin

    3. Unmirror the root aggregate by deleting the remote plex of the root aggregates.

      1. Identify the root aggregates: storage aggregate show -root true

      2. Display the pool1 aggregates: storage aggregate plex show -pool 1

      3. Delete the local plex of the root aggregate: aggr plex delete aggr-name -plex plex-name

      4. Offline the remote plex of the root aggregate: aggr plex offline root-aggregate -plex remote-plex-for-root-aggregate

        For example:

         # aggr plex offline aggr0_node_A_1-FC_01 -plex plex4
    4. Confirm the mailbox count, disk autoassign, and transition mode before proceeding using the following commands on each controller:

      1. Set the advanced privilege level: set -priv advanced

      2. Confirm that only three mailbox drives are shown for each controller module: storage failover mailbox-disk show

      3. Return to admin mode: set -priv admin

      4. Confirm that the transition mode is disruptive: metrocluster transition show

    5. Check for any broken disks: disk show -broken

    6. Remove or replace any broken disks

    7. Confirm aggregates are healthy using the following commands on node_A_1-FC and node_B_1-FC:storage aggregate showstorage aggregate plex show

      The storage aggregate show command indicates that the root aggregate is unmirrored.

    8. Check for any VLANs or interface groups: network port ifgrp show``network port vlan show

      If none are present, skip the following two steps.

    9. Display the list of LIfs using VLANs or ifgrps: network interface show -fields home-port,curr-port``network port show -type if-group | vlan

    10. Remove any VLANs and interface groups.

      You must perform these steps for all LIFs in all SVMs, including those SVMs with the -mc suffix.

      1. Move any LIFs using the VLANs or interface groups to an available port: network interface modify -vserver vserver-name -lif lif_name -home- port port

      2. Display the LIFs that are not on their home ports: network interface show -is-home false

      3. Revert all LIFs to their respective home ports: network interface revert -vserver vserver_name -lif lif_name

      4. Verify that all LIFs are on their home ports: network interface show -is-home false

        No LIFs should appear in the output.

      5. Remove VLAN and ifgrp ports from broadcast domain:: network port broadcast-domain remove-ports -ipspace ipspace -broadcast-domain broadcast-domain-name -ports nodename:portname,nodename:portname,..

      6. Verify that all the vlan and ifgrp ports are not assigned to a broadcast domain: network port show -type if-group | vlan

      7. Delete all VLANs: network port vlan delete -node nodename -vlan-name vlan-name

      8. Delete interface groups: network port ifgrp delete -node nodename -ifgrp ifgrp-name

    11. Move any LIFs as required to resolve conflicts with the MetroCluster IP interface ports.

      You must move the LIFs identified in step 1 of Mapping ports from the MetroCluster FC nodes to the MetroCluster IP nodes.

      1. Move any LIFs hosted on the desired port to another port: network interface modify -lif lifname -vserver vserver-name -home-port new-homeport``network interface revert -lif lifname -vserver vservername

      2. If necessary, move the destination port to an appropriate IPspace and broadcast domain. network port broadcast-domain remove-ports -ipspace current-ipspace -broadcast-domain current-broadcast-domain -ports controller-name:current-port``network port broadcast-domain add-ports -ipspace new-ipspace -broadcast-domain new-broadcast-domain -ports controller-name:new-port

    12. Halt the MetroCluster FC controllers (node_A_1-FC and node_B_1-FC): system node halt

    13. At the LOADER prompt, synchronize the hardware clocks between the FC and IP controller modules.

      1. On the old MetroCluster FC node (node_A_1-FC), display the date: show date

      2. On the new MetroCluster IP controllers (node_A_1-IP and node_B_1-IP), set the date shown on original controller: set date mm/dd/yy

      3. On the new MetroCluster IP controllers (node_A_1-IP and node_B_1-IP), verify the date: show date

    14. Halt and power off the MetroCluster FC controller modules (node_A_1-FC and node_B_1-FC), FC-to-SAS bridges (if present), FC switches (if present) and each storage shelf connected to these nodes.

    15. Disconnect the shelves from the MetroCluster FC controllers and document which shelves are local storage to each cluster.

      If the configuration uses FC-to-SAS bridges or FC back-end switches, disconnect and remove them.

    16. In Maintenance mode on the MetroCluster FC nodes (node_A_1-FC and node_B_1-FC), confirm no disks are connected: disk show -v

    17. Power down and remove the MetroCluster FC nodes.

At this point, the MetroCluster FC controllers have been removed and the shelves are disconnected from all controllers.

transition 2n remove fc nodes