Request doc changesEdit this pageLearn how to contribute
ON THIS PAGE
    • Product and Solutions
    • Support and Training
    • Cloud Central
    • Community
    • Blog
    • Customer Stories
    • Contact
    Menu bars
    netapp-mark netapp-logo
    English globe
    • English
    • 日本語
    • 한국어
    • 简体中文
    • 繁體中文
    • Deutsch
    • Español
    • Français
    • Italiano
    Available PDFs
    • PDF of this doc site
      • Install a fabric-attached MetroCluster
        • Prepare for the MetroCluster installation
        • Cable a fabric-attached MetroCluster configuration
          • Parts of a fabric MetroCluster configuration
          • Install and cable MetroCluster components
            • Port assignments for FC switches when using AFF A900 systems
          • Configure the FC switches
            • Configure Brocade FC switches with RCF files
            • Configure the Cisco FC switches with RCF files
        • Configure hardware for sharing a Brocade 6510 FC fabric during transition
          • Configure switch fabrics sharing between the 7-Mode and clustered MetroCluster configuration
        • Plan and install a MetroCluster configuration with array LUNs
          • Install and cable the MetroCluster components in a configuration with array LUNs
            • Cable the FC-VI and HBA ports in a MetroCluster configuration with array LUNs
            • Cable storage arrays to FC switches in a MetroCluster configuration
          • Switch zoning in a MetroCluster configuration with array LUNs
          • Set up ONTAP in a MetroCluster configuration with array LUNs
          • Implement a MetroCluster configuration with both disks and array LUNs
        • How to use the Active IQ Unified Manager and ONTAP System Manager for further configuration and monitoring
      • Install a MetroCluster IP configuration
        • Prepare for the MetroCluster installation
          • How to use layer 3 wide-area networks
        • Configure the MetroCluster hardware components
          • Cable the MetroCluster IP switches
          • Configure the MetroCluster IP switches
            • Configure Cisco IP switches
        • Configure the MetroCluster software in ONTAP
        • Configure the ONTAP Mediator service for unplanned automatic switchover
      • Install a stretch MetroCluster configuration
        • Prepare for the MetroCluster installation
        • Cable a two-node SAS-attached stretch MetroCluster configuration
          • Install and cable MetroCluster components for two-node SAS-attached stretch configurations
        • Cable a two-node bridge-attached stretch MetroCluster configuration
          • Install and cable MetroCluster components
        • Connections in a stretch MetroCluster configurations with array LUNs
        • How to use the Active IQ Unified Manager and ONTAP System Manager for further configuration and monitoring
      • Install and Configure MetroCluster Tiebreaker
        • Install the Tiebreaker software
      • Understand MetroCluster data protection and disaster recovery
      • Perform switchover, healing, and switchback
        • Perform switchover for tests or maintenance
          • Heal the configuration
            • Heal the configuration in a MetroCluster FC configuration
      • Maintain the MetroCluster components
        • FC-to-SAS bridge maintenance
        • FC switch maintenance and replacement
        • IP switch maintenance and replacement
        • Hot add storage to a MetroCluster FC configuration
          • Hot add SAS storage to a bridge-attached MetroCluster FC configuration
            • Hot add a SAS disk shelf to a stack of SAS disk shelves
        • Port assignments for FC switches
      • Transition from MetroCluster FC to MetroCluster IP
        • Transition nondisruptively from a MetroCluster FC to a MetroCluster IP configuration (ONTAP 9.8 and later)
          • Prepare for transition from a MetroCluster FC to a MetroCluster IP configuration
          • Transition from MetroCluster FC to MetroCluster IP configurations
        • Disruptively transition from a two-node MetroCluster FC to a four-node MetroCluster IP configuration (ONTAP 9.8 and later)
      • Upgrade, refresh, or expand the MetroCluster configuration
        • Start here - Choose your procedure
        • Expand a two-node MetroCluster FC configuration to a four-node configuration
          • Add a new controller module to each cluster
            • Install and cable the new controller module
            • Configure intercluster LIFs
        • Expand a four-node MetroCluster FC configuration to an eight-node configuration
          • Recable and zone a switch fabric for the new nodes
          • Configure ONTAP on the new controllers
            • Configure the clusters into a MetroCluster configuration
              • Configure intercluster LIFs
      • Recover from a disaster
        • Recover from a multi-controller or storage failure
          • Prepare for switchback in a MetroCluster IP configuration
          • Prepare for switchback in a MetroCluster FC configuration 
    Collection of separate PDF docs

    Creating your file...

    This may take a few minutes. Thanks for your patience.
    Your file is ready
    All ONTAP product documentation
    • MetroCluster
    • Release Notes
    • Install a fabric-attached MetroCluster
      • Overview
      • Prepare for the MetroCluster installation
        • Differences among the ONTAP MetroCluster configurations
        • Cluster peering
        • Considerations for MetroCluster configurations with native disk shelves or array LUNs
        • Considerations when transitioning from 7-Mode to ONTAP
        • Considerations for ISLs
        • Considerations for using TDM/WDM equipment with fabric-attached MetroCluster configurations
        • Requirements for using a Brocade DCX 8510-8 switch
        • Considerations when using unmirrored aggregates
        • Firewall usage at MetroCluster sites
      • Choose the correct installation procedure for your configuration
      • Cable a fabric-attached MetroCluster configuration
        • Overview
        • Parts of a fabric MetroCluster configuration
          • Overview
          • Illustration of the local HA pairs in a MetroCluster configuration
          • Illustration of redundant FC-to-SAS bridges
          • Redundant FC switch fabrics
          • Illustration of the cluster peering network
        • Required MetroCluster FC components and naming conventions
        • Configuration worksheet for FC switches and FC-to-SAS bridges
        • Install and cable MetroCluster components
          • Rack the hardware components
          • Cable the new controller modules FC-VI and HBA ports to the FC switches
          • Cable the ISLs between MetroCluster sites
          • Port assignments for systems using two initiator ports
          • Port assignments for FC switches when using ONTAP 9.0
          • Port assignments for FC switches when using ONTAP 9.1 and later
          • Port assignments for FC switches when using AFF A900 systems
            • AFF A900 Brocade port usage for controllers running ONTAP 9.10.1 or later
            • AFF A900 Brocade port usage for ISLs running ONTAP 9.10.1 or later
            • AFF A900 Cisco port usage controllers running ONTAP 9.10.1 or later
            • AFF A900 Cisco port usage for ISLs running ONTAP 9.10.1 or later
          • Cabling the cluster interconnect in eight- or four-node configurations
          • Cable the cluster peering connections
          • Cable the HA interconnect, if necessary
          • Cable the management and data connections
        • Configure the FC switches
          • Configure Brocade FC switches with RCF files
            • Reset the Brocade FC switch to factory defaults
            • Download the Brocade FC switch RCF file
            • Install the Brocade FC switch RCF file
          • Configure the Cisco FC switches with RCF files
            • Reset the Cisco FC switch to factory defaults
            • Download and install the Cisco FC switch NX-OS software
            • Download and install the Cisco FC RCF files
          • Configure the Brocade FC switches manually
          • Configure the Cisco FC switches manually
        • Install FC-to-SAS bridges and SAS disk shelves
      • Configure hardware for sharing a Brocade 6510 FC fabric during transition
        • Overview
        • Review Brocade license requirements
        • Rack the hardware components
        • Cable the new MetroCluster controllers to the existing FC fabrics
        • Configure switch fabrics sharing between the 7-Mode and clustered MetroCluster configuration
          • Disable one of the switch fabrics
          • Delete TI zoning and configure IOD settings
          • Ensure ISLs are in the same port group and configure zoning
          • Reenable the switch fabric and verify operation
      • Configure the MetroCluster software in ONTAP
      • Considerations for using virtual IP and Border Gateway Protocol with a MetroCluster configuration
      • Test the MetroCluster configuration
      • Considerations when removing MetroCluster configurations
      • Plan and install a MetroCluster configuration with array LUNs
        • Plan for a MetroCluster configuration with array LUNs
        • Supported MetroCluster configuration with array LUNs
        • Requirements for a MetroCluster configuration with array LUNs
        • Install and cable the MetroCluster components in a configuration with array LUNs
          • Rack the hardware components in a MetroCluster configuration with array LUNs
          • Prepare a storage array for use with ONTAP systems
          • Switch ports required for a MetroCluster configuration with array LUNs
          • Cable the FC-VI and HBA ports in a MetroCluster configuration with array LUNs
            • Cable the FC-VI and HBA ports in a two-node fabric-attached MetroCluster configuration with array LUNs
            • Cable the FC-VI and HBA ports in a four-node fabric-attached MetroCluster configuration with array LUNs
            • Cable the FC-VI and HBA ports in an eight-node fabric-attached MetroCluster configuration with array LUNs
          • Cable the ISLs in a MetroCluster configuration with array LUNs
          • Cable the cluster interconnect in eight- or four-node configurations
          • Cable the cluster peering connections
          • Cable the HA interconnect, if necessary
          • Cable the management and data connections
          • Cable storage arrays to FC switches in a MetroCluster configuration
            • Overview
            • Example of cabling storage array ports to FC switches in a two-node MetroCluster configuration
            • Example of cabling storage array ports to FC switches in a four-node MetroCluster configuration
            • Example of cabling storage array ports to FC switches in an eight-node MetroCluster configuration
        • Switch zoning in a MetroCluster configuration with array LUNs
          • Requirements for switch zoning in a MetroCluster configuration with array LUNs
          • Example of switch zoning in a two-node MetroCluster configuration with array LUNs
          • Example of switch zoning in a four-node MetroCluster configuration with array LUNs
          • Example of switch zoning in an eight-node MetroCluster configuration with array LUNs
        • Set up ONTAP in a MetroCluster configuration with array LUNs
          • Verifying and configuring the HA state of components in Maintenance mode
          • Configuring ONTAP on a system that uses only array LUNs
          • Set up the cluster
          • Install the license for using array LUNs in a MetroCluster configuration
          • Configuring FC-VI ports on a X1132A-R6 quad-port card on FAS8020 systems
          • Assign ownership of array LUNs
          • Peer the clusters
          • Mirror the root aggregates
          • Create data aggregates on, implementing, and verifying the MetroCluster configuration
        • Implement a MetroCluster configuration with both disks and array LUNs
          • Overview
          • Considerations when implementing a MetroCluster configuration with disks and array LUNs
          • Example of a two-node fabric-attached MetroCluster configuration with disks and array LUNs
          • Example of a four-node MetroCluster configuration with disks and array LUNs
      • How to use the Active IQ Unified Manager and ONTAP System Manager for further configuration and monitoring
        • Synchronize the system time using NTP
      • Considerations when using ONTAP in a MetroCluster configuration
      • Where to find additional information
    • Install a MetroCluster IP configuration
      • Overview
      • Prepare for the MetroCluster installation
        • Differences among the ONTAP MetroCluster configurations
        • Deciding between ONTAP Mediator and MetroCluster Tiebreaker
        • Considerations for MetroCluster IP configurations
        • Automatic drive assignment and ADP systems in ONTAP 9.4 and later
        • Cluster peering
        • ISL requirements
        • How to use layer 3 wide-area networks
          • Modifying address, netmask, and gateway in a MetroCluster IP
        • Sharing private layer 2 networks
        • How to use MetroCluster-compliant switches
        • How to use TDM/xWDM and encryption equipment with MetroCluster IP configurations
        • Unmirrored aggregates in a MetroCluster IP configuration
        • Firewall usage at MetroCluster sites
        • Considerations for using virtual IP and Border Gateway Protocol with a MetroCluster configuration
      • Configure the MetroCluster hardware components
        • Parts of a MetroCluster IP configuration
        • Required MetroCluster IP components and naming conventions
        • Rack the hardware components
        • Cable the MetroCluster IP switches
          • How to use the port tables with the RcfFileGenerator tool or multiple MetroCluster configurations
          • Platform port assignments for Cisco 3132Q-V switches
          • Platform port assignments for Cisco 3232C or Cisco 9336C switches
          • Platform port assignments for Broadcom supported BES-53248 IP switches
          • Platform port assignments for NVIDIA supported SN2100 IP switches
        • Cable the controller data and management ports
        • Configure the MetroCluster IP switches
          • Configure Broadcom IP switches
          • Configure Cisco IP switches
            • Configure basic settings
            • Configure MACsec encryption on Cisco 9336C switches
          • Configure NVIDIA IP switches
      • Configure the MetroCluster software in ONTAP
        • Overview
        • How to configure eight-node Configurations
        • Gather required information
        • Similarities and differences between standard cluster and MetroCluster configurations
        • Verify the ha-config state of components
        • Restoring system defaults on a controller module
        • Manually assigning drives to pool 0
        • Setting up ONTAP
        • Configure the clusters into a MetroCluster configuration
        • Verify switchover, healing, and switchback
        • Configure the MetroCluster Tiebreaker or ONTAP Mediator software
        • Protect configuration backup files
      • Configure the ONTAP Mediator service for unplanned automatic switchover
        • Prepare to install the ONTAP Mediator service
        • Configuring the ONTAP Mediator service from a MetroCluster IP configuration
        • Unconfigure the ONTAP Mediator service from the MetroCluster IP configuration
        • Connect a MetroCluster configuration to a different ONTAP Mediator instance
        • Risks and limitations of using MetroCluster automatic forced switchover
      • Testing the MetroCluster configuration
      • Considerations when removing MetroCluster configurations
      • Considerations when using ONTAP in a MetroCluster configuration
      • Where to find additional information
    • Install a stretch MetroCluster configuration
      • Overview
      • Prepare for the MetroCluster installation
        • Differences between the ONTAP MetroCluster configurations
        • Cluster peering
        • Considerations when using unmirrored aggregates
        • Firewall usage at MetroCluster sites
      • Choose the correct installation procedure for your configuration
      • Cable a two-node SAS-attached stretch MetroCluster configuration
        • Overview
        • Parts of a two-node SAS-attached stretch MetroCluster configuration
        • Required MetroCluster hardware components and naming guidelines for two-node SAS-attached stretch configurations
        • Install and cable MetroCluster components for two-node SAS-attached stretch configurations
          • Overview
          • Rack the hardware components
          • Cable the controllers to each other and the storage shelves
          • Cable the cluster peering connections
          • Cable the management and data connections
      • Cable a two-node bridge-attached stretch MetroCluster configuration
        • Overview
        • Parts of a two-node bridge-attached stretch MetroCluster configuration
        • Required MetroCluster hardware components and naming conventions for two-node bridge-attached stretch configurations
        • Information gathering worksheet for FC-to-SAS bridges
        • Install and cable MetroCluster components
          • Rack the hardware components
          • Cable the controllers to each other
          • Cable the cluster peering connections
          • Cable the management and data connections
        • Install FC-to-SAS bridges and SAS disk shelves
      • Configure the MetroCluster software in ONTAP
      • Considerations for using virtual IP and Border Gateway Protocol with a MetroCluster configuration
      • Test the MetroCluster configuration
      • Connections in a stretch MetroCluster configurations with array LUNs
        • Overview
        • Example of a stretch MetroCluster configuration with array LUNs
        • Examples of two-node stretch MetroCluster configurations with disks and array LUNs
        • Example of a stretch MetroCluster configuration with E-Series storage arrays
      • Considerations when removing MetroCluster configurations
      • How to use the Active IQ Unified Manager and ONTAP System Manager for further configuration and monitoring
        • Overview
        • Synchronizing the system time using NTP
      • Considerations when using ONTAP in a MetroCluster configuration
      • Transitioning from a stretch to a fabric-attached MetroCluster configuration
      • Where to find additional information
    • Install and Configure MetroCluster Tiebreaker
      • What's new
      • Overview of the Tiebreaker software
      • Install the Tiebreaker software
        • Prepare to install
        • Configure admin access to ONTAPI and SSH
        • Install dependencies
        • Secure the installation
        • Install the software package
        • Upgrade the host
      • Configure the Tiebreaker software
      • Configure SNMP settings for Tiebreaker software
      • Monitor the MetroCluster configuration
      • Risks and limitations of using MetroCluster Tiebreaker in active mode
      • Firewall requirements for MetroCluster Tiebreaker
      • MetroCluster Tiebreaker event log files
      • Where to find additional information
    • Understand MetroCluster data protection and disaster recovery
      • How MetroCluster protects data and provides disaster recovery
    • Perform switchover, healing, and switchback
      • Perform switchover for tests or maintenance
        • Overview
        • Verify that your system is ready for a switchover
        • Send a custom AutoSupport message prior to negotiated switchover
        • Perform a negotiated switchover
        • Verify that the SVMs are running and the aggregates are online
        • Heal the configuration
          • Heal the configuration in a MetroCluster FC configuration
            • Overview
            • Heal the data aggregates after negotiated switchover
            • Heal the root aggregates after negotiated switchover
          • Heal the configuration in a MetroCluster IP configuration (ONTAP 9.4 and earlier)
        • Perform a switchback
        • Verify a successful switchback
      • Commands for switchover, healing, and switchback
      • Monitor the MetroCluster configuration
      • Monitor and protecting the file system consistency using NVFAIL
      • Where to find additional information
    • Maintain the MetroCluster components
      • Where to find procedures for MetroCluster maintenance tasks
      • MetroCluster failure and recovery scenarios
      • Remove ONTAP Mediator or Tiebreaker monitoring before performing maintenance tasks
      • FC-to-SAS bridge maintenance
        • Support for FibreBridge 7600N bridges in MetroCluster configurations
        • Support for FibreBridge 7500N bridges in MetroCluster configurations
        • Enable IP port access on the FibreBridge 7600N bridge if necessary
        • Update firmware on a FibreBridge bridge
        • Replace a single FC-to-SAS bridge
        • Replace a pair of FibreBridge 6500N bridges with 7600N or 7500N bridges
        • Requirements for using other interfaces to configure and manage FibreBridge bridges
        • Hot-replace a failed power supply module
        • In-band management of the FC-to-SAS bridges
        • Secure or unsecure the FibreBridge bridge
      • FC switch maintenance and replacement
        • Upgrade or downgrade the firmware on a Brocade FC switch
        • Upgrade or downgrade the firmware on a Cisco FC switch
        • Upgrade to new Brocade FC switches
        • Replace a Brocade FC switch
        • Rename a Brocade FC switch
        • Disabling encryption on Brocade FC switches
        • Changing ISL properties, ISL ports, or the IOD/OOD configuration on a Brocade switch
        • Replace a Cisco FC switch
        • Changing speed of ISL ports on a Cisco FC switch
        • Adding lSLs to a Cisco switch
      • IP switch maintenance and replacement
        • Replace an IP switch or change the use of existing MetroCluster IP switches
        • Upgrade firmware on MetroCluster IP switches
        • Upgrade RCF files on MetroCluster IP switches
        • Upgrade RCF files on Cisco IP switches using cleanupfiles
        • Rename a Cisco IP switch
      • Modify a switch or ATTO bridge IP address for health monitoring
      • Add, remove, or change ISL ports nondisruptively
      • How to identify storage in a MetroCluster IP configuration
      • Add shelves to a MetroCluster using shared Storage/MetroCluster switches
      • Hot add storage to a MetroCluster FC configuration
        • Hot add a SAS disk shelf in a direct-attached MetroCluster FC configuration using SAS optical cables
        • Hot add SAS storage to a bridge-attached MetroCluster FC configuration
          • Hot add a stack of SAS disk shelves to an existing pair of FibreBridge 7500N bridges
          • Hot add a stack of SAS disk shelves and bridges to a MetroCluster system
          • Hot add a SAS disk shelf to a stack of SAS disk shelves
            • Preparing to hot-add SAS disk shelves
            • Hot add a disk shelf
          • Hot add an IOM12 disk shelf to a stack of IOM6 disk shelves in a bridge-attached MetroCluster configuration
      • Hot-remove storage from a MetroCluster FC configuration
      • Replace a shelf nondisruptively in a stretch MetroCluster configuration
      • Replace a shelf nondisruptively in a fabric-attached MetroCluster configuration
      • When to migrate root volumes to a new destination
      • Move a metadata volume in MetroCluster configurations
      • Rename a cluster in MetroCluster configurations
      • Power off and power on a data center
      • Power off an entire MetroCluster IP configuration
      • Power off an entire MetroCluster FC configuration
      • Reconfigure an FC switch layout configured before ONTAP 9.x
      • Port assignments for FC switches
        • Port assignments for systems using two initiator ports
        • Port assignments for FC switches when using ONTAP 9.0
        • Port assignments for FC switches when using ONTAP 9.1 and later
      • How to use the Interoperability Matrix Tool to find MetroCluster information
      • Where to find additional information
    • Transition from MetroCluster FC to MetroCluster IP
      • Choose your transition procedure
      • Transition nondisruptively from a MetroCluster FC to a MetroCluster IP configuration (ONTAP 9.8 and later)
        • Overview
        • Prepare for transition from a MetroCluster FC to a MetroCluster IP configuration
          • Requirements for nondisruptive FC-to-IP transition
          • How transition impacts the MetroCluster hardware components
          • Workflow for nondisruptive MetroCluster transition
          • Considerations for IP switches
          • Switchover, healing, and switchback operations during nondisruptive transition
          • Alert messages and tool support during transition
          • Example naming in this procedure
        • Transition from MetroCluster FC to MetroCluster IP configurations
          • Verify the health of the MetroCluster configuration
          • Remove the existing configuration from the Tiebreaker or other monitoring software
          • Generating and applying RCFs to the new IP switches
          • Move the local cluster connections
          • Prepare the MetroCluster IP controllers
          • Configure the MetroCluster for transition
          • Move the data to the new drive shelves
          • Remove the MetroCluster FC controllers
          • Complete the transition
        • Send a custom AutoSupport message after maintenance
        • Restore Tiebreaker or Mediator monitoring
      • Disruptively transition from a two-node MetroCluster FC to a four-node MetroCluster IP configuration (ONTAP 9.8 and later)
        • Overview
        • Example naming in this procedure
        • Prepare for disruptive FC-to-IP transition
        • Transition the MetroCluster FC nodes
        • Connect the MetroCluster IP controller modules
        • Configure the new nodes and completing transition
        • Return the system to normal operation
      • Disruptively transition from MetroCluster FC to MetroCluster IP when retiring storage shelves (ONTAP 9.8 and later)
      • Disruptively transition when existing shelves are not supported on new controllers (ONTAP 9.8 and later)
      • Move an FC SAN workload from MetroCluster FC to MetroCluster IP nodes
      • Move Linux iSCSI hosts from MetroCluster FC to MetroCluster IP nodes
      • Where to find additional information
    • Upgrade, refresh, or expand the MetroCluster configuration
      • Start here - Choose your procedure
        • Choose controller upgrade, system refresh, or expansion
        • Choose controller upgrade procedure
        • Choose system refresh procedure
        • Choose expansion procedure
      • Upgrade controllers in four-node MetroCluster IP using switchover and switchback with "system controller replace" commands (ONTAP 9.13.1 and later)
      • Upgrade controllers in MetroCluster FC using switchover and switchback
      • Upgrade controllers (AFF A700/FAS9000 to AFF A900/FAS9500) in a MetroCluster FC configuration using switchover and switchback (ONTAP 9.10.1 or later)
      • Upgrade controllers in four-node MetroCluster FC using switchover and switchback with "system controller replace" commands (ONTAP 9.10.1 and later)
      • Upgrade controllers in MetroCluster IP using switchover and switchback (ONTAP 9.8 and later)
      • Upgrade controllers (AFF A700/FAS9000 to AFF A900/FAS9500) in MetroCluster IP using switchover and switchback (ONTAP 9.10.1 or later)
      • Refresh a four-node MetroCluster FC configuration
      • Refresh a four-node or an eight-node MetroCluster IP configuration (ONTAP 9.8 and later)
      • Expand a two-node MetroCluster FC configuration to a four-node configuration
        • Overview
        • Verify the state of the MetroCluster configuration
        • Send a custom AutoSupport message before adding noxdes to the MetroCluster configuration
        • Zone for the new controller ports when adding a controller module in a fabric-attached MetroCluster configuration
        • Add a new controller module to each cluster
          • Overview
          • Prepare for the upgrade
          • Clear the configuration on a controller module
          • Prepare cluster ports on an existing controller module
          • Prepare the netboot server to download the image
          • Set the HA mode on the existing controller module
          • Shut down the existing controller module
          • Install and cable the new controller module
            • Prerequisites and installation
            • Cable the new controller module's FC-VI and HBA ports to the FC switches
            • Cabling the new controller module's cluster peering connections
          • Power up both controller modules and displaying the LOADER prompt
          • Change the ha-config setting on the existing and new controller modules
          • Set the partner system ID for both controller modules
          • Boot the existing controller module
          • Assign disks to the new controller module
          • Netboot and set up ONTAP on the new controller module
          • Mirror the root aggregate on the new controller
          • Configure intercluster LIFs
            • Configure intercluster LIFs on dedicated ports
            • Configure intercluster LIFs on shared data ports
          • Create a mirrored data aggregate on each node
          • Install licenses for the new controller module
          • Create unmirrored data aggregates
          • Install the firmware after adding a controller module
        • Refresh the MetroCluster configuration with new controllers
        • Enable storage failover on both controller modules and enable cluster HA
        • Restart the SVMs
      • Expand a four-node MetroCluster FC configuration to an eight-node configuration
        • Overview
        • Determining the new cable layout
        • Rack the new equipment
        • Verify the health of the MetroCluster configuration
        • Check for MetroCluster configuration errors with Config Advisor
        • Send a custom AutoSupport message prior to add nodes to the MetroCluster configuration
        • Recable and zone a switch fabric for the new nodes
          • Disconnect the existing DR group from the fabric
          • Recable and reconfigure the switches
        • Configure ONTAP on the new controllers
          • Clear the configuration on a controller module
          • Assign disk ownership in AFF systems
          • Assign disk ownership in non-AFF systems
          • Verify the ha-config state of components
          • Boot the new controllers and join them to the cluster
          • Configure the clusters into a MetroCluster configuration
            • Configure intercluster LIFs
              • Configure intercluster LIFs on dedicated ports
              • Configure intercluster LIFs on shared data ports
            • Mirror the root aggregates
            • Implement the MetroCluster configuration
            • Create a mirrored data aggregate on each node
            • Configure FC-to-SAS bridges for health monitoring
            • Move a metadata volume in MetroCluster configurations
            • Check the MetroCluster configuration
        • Check for MetroCluster configuration errors with Config Advisor
        • Send a custom AutoSupport message after to add nodes to the MetroCluster configuration
        • Verify switchover, healing, and switchback
      • Expand a MetroCluster IP configuration
      • Remove a Disaster Recovery group
      • Where to find additional information
    • Recover from a disaster
      • Workflow for disaster recovery
      • Perform a forced switchover after a disaster
      • Choosing the correct recovery procedure
      • Recover from a multi-controller or storage failure
        • Before you begin
        • Replace hardware and boot new controllers
        • Prepare for switchback in a MetroCluster IP configuration
          • Overview
          • Set required environmental variables in MetroCluster IP configurations
          • Power on the equipment at the disaster site (MetroCluster IP configurations)
          • Configure the IP switches (MetroCluster IP configurations)
          • Verify storage connectivity to the remote site (MetroCluster IP configurations)
          • Reassign disk ownership for pool 1 disks on the disaster site (MetroCluster IP configurations)
          • Boot to ONTAP on replacement controller modules in MetroCluster IP configurations
          • Restore connectivity from the surviving nodes to the disaster site (MetroCluster IP configurations)
          • Verify automatic assignment or manually assign pool 0 drives
          • Assign pool 1 drives on the surviving site (MetroCluster IP configurations)
          • Delete failed plexes owned by the surviving site (MetroCluster IP configurations)
          • Perform aggregate heal and restore mirrors (MetroCluster IP configurations)
        • Prepare for switchback in a MetroCluster FC configuration
          • Verify port configuration (MetroCluster FC configurations only)
          • Configure the FC-to-SAS bridges (MetroCluster FC configurations only)
          • Configure the FC switches (MetroCluster FC configurations only)
          • Verify the storage configuration
          • Power on the equipment at the disaster site
          • Assign ownership for replaced drives
          • Perform aggregate healing and restore mirrors (MetroCluster FC configurations)
          • Reassign disk ownership for root aggregates to replacement controller modules (MetroCluster FC configurations)
          • Boot the new controller modules (MetroCluster FC configurations)
        • Prepare the nodes for switchback in a mixed configuration (recovery during transition)
        • Complete recovery
      • Recover from a non-controller failure
    • Legal notices
    • docs.netapp.com
    • ONTAP
    • ONTAP MetroCluster

    Illustration of redundant FC-to-SAS bridges

    01/20/2022 Contributors netapp-thomi

    FC-to-SAS bridges provide protocol bridging between SAS attached disks and the FC switch fabric.

    mcc hw architecture shelf stacks
    Related information

    Illustration of the local HA pairs in a MetroCluster configuration

    Redundant FC switch fabrics

    Illustration of the cluster peering network

    • © 2023 NetApp, Inc.
    • Terms of Use
    • Privacy Policy
    • Cookie Policy
    • Cookie Settings
    • Send feedback about this page
    • blog blog@
    • community community@
    • twitter twitter@
    • facebook facebook@
    • linkedin linkedin@
    • youtube youtube@
    • slideshare slideshare@