MetroCluster Documentation
Install a fabric-attached MetroCluster
Preparing for the MetroCluster installation
Cabling a fabric-attached MetroCluster configuration
Parts of a fabric MetroCluster configuration
Installing and cabling MetroCluster components
Configuring the FC switches
Configuring Brocade FC switches with RCF files
Configuring the Cisco FC switches with RCF files
Configuring hardware for sharing a Brocade 6510 FC fabric during transition
Configuring switch fabrics sharing between the 7-Mode and clustered MetroCluster configuration
Planning and installing a MetroCluster configuration with array LUNs
Installing and cabling the MetroCluster components in a configuration with array LUNs
Cabling the FC-VI and HBA ports in a MetroCluster configuration with array LUNs
Cabling storage arrays to FC switches in a MetroCluster configuration
Switch zoning in a MetroCluster configuration with array LUNs
Setting up ONTAP in a MetroCluster configuration with array LUNs
Implementing a MetroCluster configuration with both disks and array LUNs
Using the Active IQ Unified Manager and ONTAP System Manager for further configuration and monitoring
Install a MetroCluster IP configuration
Preparing for the MetroCluster installation
Configuring the MetroCluster hardware components
Cable the MetroCluster IP switches
Configure the MetroCluster IP switches
Configure Cisco IP switches
Configuring the MetroCluster software in ONTAP
Configuring the ONTAP Mediator service for unplanned automatic switchover
Install a stretch MetroCluster configuration
Preparing for the MetroCluster installation
Cabling a two-node SAS-attached stretch MetroCluster configuration
Installing and cabling MetroCluster components for two-node SAS-attached stretch configurations
Cabling a two-node bridge-attached stretch MetroCluster configuration
Installing and cabling MetroCluster components
Connections in a stretch MetroCluster configurations with array LUNs
Using the Active IQ Unified Manager and ONTAP System Manager for further configuration and monitoring
Install and Configure MetroCluster Tiebreaker
Understand MetroCluster data protection and disaster recovery
Performing switchover, healing, and switchback
Performing switchover for tests or maintenance
Healing the configuration
Healing the configuration in a MetroCluster FC configuration
Maintain the MetroCluster components
Performing FC-to-SAS bridge maintenance
Performing FC switch maintenance and replacement
Performing IP switch maintenance and replacement
Hot-adding storage to a MetroCluster FC configuration
Hot-adding SAS storage to a bridge-attached MetroCluster FC configuration
Hot-adding a SAS disk shelf to a stack of SAS disk shelves
Port assignments for FC switches
Transition from MetroCluster FC to MetroCluster IP
Transitioning nondisruptively from a MetroCluster FC to a MetroCluster IP configuration (ONTAP 9.8 and later)
Preparing for transition from a MetroCluster FC to a MetroCluster IP configuration
Transitioning from MetroCluster FC to MetroCluster IP configurations
Disruptively transitioning from a two-node MetroCluster FC to a four-node MetroCluster IP configuration (ONTAP 9.8 and later)
Upgrade or expand the MetroCluster configuration
Expanding a two-node MetroCluster FC configuration to a four-node configuration
Adding a new controller module to each cluster
Installing and cabling the new controller module
Configuring intercluster LIFs
Expanding a four-node MetroCluster FC configuration to an eight-node configuration
Recabling and zoning a switch fabric for the new nodes
Configuring ONTAP on the new controllers
Configuring the clusters into a MetroCluster configuration
Configuring intercluster LIFs
Recover from a disaster
Recovering from a multi-controller or storage failure
Preparing for switchback in a MetroCluster IP configuration
Preparing for switchback in a MetroCluster FC configuration
Contributors
Download PDF of this page
NETAPP, the NETAPP logo, and the marks listed on the NetApp Trademarks page are trademarks of NetApp, Inc. Other company and product names may be trademarks of their respective owners.
Edit on GitHub