Skip to main content
ONTAP MetroCluster

Refreshing a four-node MetroCluster FC configuration

Contributors netapp-aoife netapp-folivia netapp-thomi netapp-martyh

You can upgrade the controllers and storage in a four-node MetroCluster configuration by expanding the configuration to become an eight-node configuration and then removing the old disaster recovery (DR) group.

About this task

References to "old nodes" mean the nodes that you intend to replace.

  • You can only refresh specific platform models using this procedure in a MetroCluster FC configuration.

Enable console logging

NetApp strongly recommends that you enable console logging on the devices that you are using and take the following actions when performing this procedure:

Perform the refresh procedure

Use the following steps to refresh the MetroCluster FC configuration.

Steps
  1. Gather information from the old nodes.

    At this stage, the four-node configuration appears as shown in the following image:

    mcc dr group a
  2. Perform all of the steps in the four-node expansion procedure for your MetroCluster type.

    When the expansion procedure is complete, the configuration appears as shown in the following image:

    mcc dr group b
  3. Move the CRS volumes.

  4. Move the data from the old nodes to new nodes using the following procedures:

    1. Perform all the steps in Create an aggregate and moving volumes to the new nodes.

      Note You might choose to mirror the aggregate when or after it is created.
    2. Perform all the steps in Move non-SAN data LIFs and cluster management LIFs to the new nodes.

    3. Perform all the steps in Delete SAN LIFs no longer required from the original nodes.

  5. Follow the steps in the procedure for removing the old DR group.

    After you have removed the old DR group (DR group one), the configuration appears as shown in the following image:

    mcc dr group d