Table of ContentsView in Frames

Checking the MetroCluster configuration

You can check that the components and relationships in the MetroCluster configuration are working correctly. You should do a check after initial configuration and after making any changes to the MetroCluster configuration. After you run the metrocluster check run command, you then display the results of the check with the metrocluster check show command.

About this task

If the metrocluster check run command is issued twice within a short time, on either or both clusters, a conflict can occur and the command might not collect all data. Subsequent metrocluster check show commands will not show the expected output.

Steps

  1. Check the configuration: metrocluster check run
    Example
    The following example shows the output for a healthy MetroCluster configuration:
    controller_A_1::> metrocluster check run
    
    Last Checked On: 9/24/2014 17:10:33
    
    Component           Result
    ------------------- ---------
    nodes               ok
    lifs                ok
    config-replication  ok
    aggregates          ok
    4 entries were displayed.
    
    Command completed. Use the "metrocluster check show -instance" command or sub-commands in "metrocluster check" directory for detailed results.
    To check if the nodes are ready to do a switchover or switchback operation, run "metrocluster switchover -simulate" or "metrocluster switchback 
    -simulate", respectively.
    
    
    
  2. Display more detailed results from the most recent metrocluster check run command: metrocluster check aggregate showmetrocluster check config-replication showmetrocluster check lif showmetrocluster check node show
    The metrocluster check show commands show the results of the most recent metrocluster check run command. You should always run the metrocluster check run command prior to using the metrocluster check show commands to ensure that the information displayed is current.
    Example
    The following example shows the metrocluster check aggregate show output for a healthy MetroCluster configuration:
    controller_A_1::> metrocluster check aggregate show
    
    Last Checked On: 8/5/2014 00:42:58 
    
    Node                  Aggregate             Check                 Result
    --------------------- --------------------- --------------------- ---------
    controller_A_1     aggr0_controller_A_1_0
                                                mirroring-status      ok
                                                disk-pool-allocation  ok
                          controller_A_1_aggr1
                                                mirroring-status      ok
                                                disk-pool-allocation  ok
    controller_A_2     aggr0_controller_A_2
                                                mirroring-status      ok
                                                disk-pool-allocation  ok
                          controller_A_2_aggr1
                                                mirroring-status      ok
                                                disk-pool-allocation  ok
    controller_B_1     aggr0_controller_B_1_0
                                                mirroring-status      ok
                                                disk-pool-allocation  ok
                          controller_B_1_aggr1
                                                mirroring-status      ok
                                                disk-pool-allocation  ok
    controller_B_2     aggr0_controller_B_2
                                                mirroring-status      ok
                                                disk-pool-allocation  ok
                       controller_B_2_aggr1
                                                mirroring-status      ok
                                                disk-pool-allocation  ok
    16 entries were displayed.