Skip to main content

Implementing the MetroCluster configuration

You must run the metrocluster configure command to start data protection in a MetroCluster configuration.

Before you begin

  • There should be at least two non-root mirrored data aggregates on each cluster.

    You can verify this with the storage aggregate show command.

    Note
    If you want to use a single mirrored data aggregate, then see 1 for instructions.
  • The ha-config state of the controllers and chassis must be mccip .

About this task

You issue the metrocluster configure command once, on any of the nodes, to enable the MetroCluster configuration. You do not need to issue the command on each of the sites or nodes, and it does not matter which node or site you choose to issue the command on.

The metrocluster configure command automatically pairs the two nodes with the lowest system IDs in each of the two clusters as disaster recovery (DR) partners. In a four-node MetroCluster configuration, there are two DR partner pairs. The second DR pair is created from the two nodes with higher system IDs.

  1. Configure the MetroCluster in the following format:
    If your MetroCluster configuration has...Then do this...
    Multiple data aggregatesFrom any node's prompt, configure MetroCluster: metrocluster configure node-name
    A single mirrored data aggregate
    1. From any node's prompt, change to the advanced privilege level:

      set -privilege advanced

      You need to respond with y when you are prompted to continue into advanced mode and you see the advanced mode prompt (*>).

    2. Configure the MetroCluster with the

      -allow-with-one-aggregate true parameter: metrocluster configure -allow-with-one-aggregate true node-name
    3. Return to the admin privilege level:

      set -privilege admin

    Example

    Note
    The best practice is to have multiple data aggregates. If the first DR group has only one aggregate and you want to add a DR group with one aggregate, you must move the metadata volume off the single data aggregate. For more information on this procedure, see Moving a metadata volume in MetroCluster configurations.
    The following command enables the MetroCluster configuration on all of the nodes in the DR group that contains controller_A_1:
    cluster_A::*> metrocluster configure -node-name controller_A_1

    [Job 121] Job succeeded: Configure is successful.

  2. Verify the networking status on site A: network port show

    Example

    The following example shows the network port usage on a four-node MetroCluster configuration:

    cluster_A::> network port show
    Speed (Mbps)
    Node Port IPspace Broadcast Domain Link MTU Admin/Oper
    ------ --------- --------- ---------------- ----- ------- ------------
    controller_A_1
    e0a Cluster Cluster up 9000 auto/1000
    e0b Cluster Cluster up 9000 auto/1000
    e0c Default Default up 1500 auto/1000
    e0d Default Default up 1500 auto/1000
    e0e Default Default up 1500 auto/1000
    e0f Default Default up 1500 auto/1000
    e0g Default Default up 1500 auto/1000
    controller_A_2
    e0a Cluster Cluster up 9000 auto/1000
    e0b Cluster Cluster up 9000 auto/1000
    e0c Default Default up 1500 auto/1000
    e0d Default Default up 1500 auto/1000
    e0e Default Default up 1500 auto/1000
    e0f Default Default up 1500 auto/1000
    e0g Default Default up 1500 auto/1000
    14 entries were displayed.

  3. Verify the MetroCluster configuration from both sites in the MetroCluster configuration.
    1. Verify the configuration from site A: metrocluster show

      Example

      cluster_A::> metrocluster show

      Configuration: IP fabric

      Cluster Entry Name State
      ------------------------- ------------------- -----------
      Local: cluster_A Configuration state configured
      Mode normal
      Remote: cluster_B Configuration state configured
      Mode normal
    2. Verify the configuration from site B: metrocluster show

      Example

      cluster_B::> metrocluster show

      Configuration: IP fabric

      Cluster Entry Name State
      ------------------------- ------------------- -----------
      Local: cluster_B Configuration state configured
      Mode normal
      Remote: cluster_A Configuration state configured
      Mode normal