Trademark
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.
-
MetroCluster Documentation
-
Install a fabric-attached MetroCluster
-
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 the Cisco or Brocade FC switches manually
-
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
-
Configuring the MetroCluster hardware components
-
Configuring the ONTAP Mediator service for unplanned automatic switchover
-
Install a stretch MetroCluster configuration
-
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
-
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
-
Performing switchover, healing, and switchback
-
Performing switchover for tests or maintenance
-
Healing the configuration
-
Healing the configuration in a MetroCluster FC configuration
-
Install and Configure MetroCluster Tiebreaker
-
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
-
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
-
Disaster Recovery
-
Recovering from a multi-controller or storage failure
Site
Sections
Sections
Sections
Sections
Sections
Sections
Sections
Sections
Sections
- MetroCluster
- Release Notes
-
Install a fabric-attached MetroCluster
- Deciding whether to use the Fabric-attached MetroCluster Installation and Configuration Guide
- Preparing for the MetroCluster installation
- Choosing the correct installation procedure for your configuration
-
Cabling a fabric-attached MetroCluster configuration
-
Parts of a fabric MetroCluster configuration
- Required MetroCluster FC components and naming conventions
- Configuration worksheet for FC switches and FC-to-SAS bridges
-
Installing and cabling MetroCluster components
- Racking the hardware components
- Cabling the new controller module’s FC-VI and HBA ports to the FC switches
- Cabling 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
- Cabling the cluster interconnect in eight- or four-node configurations
- Cabling the cluster peering connections
- Cabling the HA interconnect, if necessary
- Cabling the management and data connections
-
Configuring the FC switches
- Configuring the FC switches by running a configuration file
-
Configuring Brocade FC switches with RCF files
-
Configuring the Cisco or Brocade FC switches manually
- Installing FC-to-SAS bridges and SAS disk shelves
-
-
Configuring hardware for sharing a Brocade 6510 FC fabric during transition
- Configuring the MetroCluster software in ONTAP
- Considerations for using virtual IP and Border Gateway Protocol with a MetroCluster configuration
- Testing the MetroCluster configuration
- Considerations when removing MetroCluster configurations
-
Planning and installing a MetroCluster configuration with array LUNs
- Planning for a MetroCluster configuration with array LUNs
- Supported MetroCluster configuration with array LUNs
- Requirements for a MetroCluster configuration with array LUNs
-
Installing and cabling the MetroCluster components in a configuration with array LUNs
- Racking the hardware components in a MetroCluster configuration with array LUNs
- Preparing a storage array for use with ONTAP systems
- Switch ports required for a MetroCluster configuration with array LUNs
-
Cabling the FC-VI and HBA ports in a MetroCluster configuration with array LUNs
- Cabling the FC-VI and HBA ports in a two-node fabric-attached MetroCluster configuration with array LUNs
- Cabling the FC-VI and HBA ports in a four-node fabric-attached MetroCluster configuration with array LUNs
- Cabling the FC-VI and HBA ports in an eight-node fabric-attached MetroCluster configuration with array LUNs
- Cabling the ISLs in a MetroCluster configuration with array LUNs
- Cabling the cluster interconnect in eight- or four-node configurations
- Cabling the cluster peering connections
- Cabling the HA interconnect, if necessary
- Cabling the management and data connections
-
Cabling storage arrays to FC switches in a 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
-
Setting 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
- Setting up the cluster
- Installing the license for using array LUNs in a MetroCluster configuration
- Configuring FC-VI ports on a X1132A-R6 quad-port card on FAS8020 systems
- Assigning ownership of array LUNs
- Peering the clusters
- Mirroring the root aggregates
- Creating data aggregates on, implementing, and verifying the MetroCluster configuration
-
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
- Considerations when using ONTAP in a MetroCluster configuration
- Where to find additional information
-
Install a MetroCluster IP configuration
- Deciding whether to use the MetroCluster IP Installation and Configuration Guide
- Preparing for the MetroCluster installation
-
Configuring the MetroCluster hardware components
- Configuring the MetroCluster software in ONTAP
- Considerations for using virtual IP and Border Gateway Protocol with a MetroCluster configuration
-
Configuring the ONTAP Mediator service for unplanned automatic switchover
- Preparing to install the ONTAP Mediator service
- Installing or upgrading the ONTAP Mediator service
- Configuring the ONTAP Mediator service from a MetroCluster IP configuration
- Connecting a MetroCluster configuration to a different ONTAP Mediator instance
- Changing the ONTAP Mediator password
- Changing the ONTAP Mediator user name
- Uninstalling the ONTAP Mediator service
- 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
- Deciding whether to use the Stretch MetroCluster Installation and Configuration Guide
- Preparing for the MetroCluster installation
- Choosing the correct installation procedure for your configuration
-
Cabling a two-node SAS-attached stretch MetroCluster configuration
-
Cabling a two-node bridge-attached stretch MetroCluster configuration
- 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
-
Installing and cabling MetroCluster components
- Installing FC-to-SAS bridges and SAS disk shelves
- Configuring the MetroCluster software in ONTAP
- Considerations for using virtual IP and Border Gateway Protocol with a MetroCluster configuration
- Testing the MetroCluster configuration
-
Connections in a stretch MetroCluster configurations with array LUNs
- Considerations when removing MetroCluster configurations
-
Using the Active IQ Unified Manager and ONTAP System Manager for further configuration and monitoring
- Considerations when using ONTAP in a MetroCluster configuration
- Transitioning from a stretch to a fabric-attached MetroCluster configuration
- Where to find additional information
-
Maintain the MetroCluster components
- Deciding whether to use the MetroCluster Maintenance Guide
- Where to find procedures for MetroCluster maintenance tasks
- MetroCluster failure and recovery scenarios
-
Performing FC-to-SAS bridge maintenance
- Support for FibreBridge 7600N bridges in MetroCluster configurations
- Support for FibreBridge 7500N bridges in MetroCluster configurations
- Enabling IP port access on the FibreBridge 7600N bridge if necessary
- Updating firmware on a FibreBridge bridge
- Replacing a single FC-to-SAS bridge
- Replacing a pair of FibreBridge 6500N bridges with 7600N or 7500N bridges
- Requirements for using other interfaces to configure and manage FibreBridge bridges
- Hot-replacing a failed power supply module
- In-band management of the FC-to-SAS bridges
- Securing or unsecuring the FibreBridge bridge
-
Performing FC switch maintenance and replacement
- Upgrading or downgrading the firmware on a Brocade FC switch
- Upgrading or downgrading the firmware on a Cisco FC switch
- Upgrading to new Brocade FC switches
- Replacing a Brocade FC switch
- Renaming a Brocade FC switch
- Disabling encryption on Brocade FC switches
- Changing ISL properties, ISL ports, or the IOD/OOD configuration on a Brocade switch
- Replacing a Cisco FC switch
- Changing speed of ISL ports on a Cisco FC switch
- Adding lSLs to a Cisco switch
-
Performing IP switch maintenance and replacement
- Adding, removing, or changing ISL ports nondisruptively
- Identifying storage in a MetroCluster IP configuration
-
Hot-adding storage to a MetroCluster FC configuration
- Hot-adding a SAS disk shelf in a direct-attached MetroCluster FC configuration using SAS optical cables
-
Hot-adding SAS storage to a bridge-attached MetroCluster FC configuration
- Hot-adding a stack of SAS disk shelves to an existing pair of FibreBridge 7500N bridges
- Hot-adding a stack of SAS disk shelves and bridges to a MetroCluster system
-
Hot-adding a SAS disk shelf to a stack of SAS disk shelves
- Hot-adding an IOM12 disk shelf to a stack of IOM6 disk shelves in a bridge-attached MetroCluster configuration
- Hot-removing storage from a MetroCluster FC configuration
- Replacing a shelf nondisruptively in a stretch MetroCluster configuration
- Replacing a shelf nondisruptively in a fabric-attached MetroCluster configuration
- When to migrate root volumes to a new destination
- Moving a metadata volume in MetroCluster configurations
- Renaming a cluster in MetroCluster configurations
- Powering off and powering on a data center
- Powering off an entire MetroCluster IP configuration
- Powering off an entire MetroCluster FC configuration
- Reconfiguring an FC switch layout configured before ONTAP 9.x
-
Port assignments for FC switches
- Using the Interoperability Matrix Tool to find MetroCluster information
- Where to find additional information
- Understanding MetroCluster data protection and disaster recovery
-
Performing switchover, healing, and switchback
-
Performing switchover for tests or maintenance
- Verifying that your system is ready for a switchover
- Sending a custom AutoSupport message prior to negotiated switchover
- Performing a negotiated switchover
- Output for the storage aggregate plex show command is indeterminate after a MetroCluster switchover
- Confirming that the DR partners have come online
-
Healing the configuration
- Performing a switchback
- Verifying a successful switchback
- Commands for switchover, healing, and switchback
- Monitoring the MetroCluster configuration
- Monitoring and protecting the file system consistency using NVFAIL
- Where to find additional information
-
-
Install and Configure MetroCluster Tiebreaker
- Deciding whether to use the MetroCluster Tiebreaker Software Installation and Configuration Guide
- Overview of the Tiebreaker software
- Installing the Tiebreaker software
- Configuring the Tiebreaker software
- Configuring SNMP settings for Tiebreaker software
- Monitoring the MetroCluster configuration
- Risks and limitations of using MetroCluster Tiebreaker in active mode
- Firewall requirements for MetroCluster Tiebreaker
- Where to find additional information
-
Transition from MetroCluster FC to MetroCluster IP
- Supported platforms for nondisruptive transition
-
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
- 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
- Transitioning from MetroCluster FC to MetroCluster IP configurations
- Sending a custom AutoSupport message after maintenance
- Restoring Tiebreaker or Mediator monitoring
-
-
Disruptively transitioning from a two-node MetroCluster FC to a four-node MetroCluster IP configuration (ONTAP 9.8 and later)
- Disruptively transitioning from MetroCluster FC to MetroCluster IP when retiring storage shelves (ONTAP 9.8 and later)
- Disruptively transitioning when existing shelves are not supported on new controllers (ONTAP 9.8 and later)
- Moving an FC SAN workload from MetroCluster FC to MetroCluster IP nodes
- Moving Linux iSCSI hosts from MetroCluster FC to MetroCluster IP nodes
- Where to find additional information
-
Upgrade or expand the MetroCluster configuration
- Choosing an upgrade or refresh method
- Upgrading controllers in a MetroCluster FC configuration using switchover and switchback
- Upgrading controllers in a MetroCluster IP configuration using switchover and switchback (ONTAP 9.8 and later)
- Refreshing a four-node MetroCluster FC configuration
- Refreshing a four-node MetroCluster IP configuration (ONTAP 9.8 and later)
-
Expanding a two-node MetroCluster FC configuration to a four-node configuration
- Verifying the state of the MetroCluster configuration
- Sending a custom AutoSupport message before adding nodes to the MetroCluster configuration
- Zoning for the new controller ports when adding a controller module in a fabric-attached MetroCluster configuration
-
Adding a new controller module to each cluster
- Preparing for the upgrade
- Clearing the configuration on a controller module
- Preparing cluster ports on an existing controller module
- Preparing the netboot server to download the image
- Setting the HA mode on the existing controller module
- Shutting down the existing controller module
-
Installing and cabling the new controller module
- Powering up both controller modules and displaying the LOADER prompt
- Changing the ha-config setting on the existing and new controller modules
- Setting the partner system ID for both controller modules
- Booting the existing controller module
- Assigning disks to the new controller module
- Netbooting and setting up ONTAP on the new controller module
- Mirroring the root aggregate on the new controller
-
Configuring intercluster LIFs
- Creating a mirrored data aggregate on each node
- Installing licenses for the new controller module
- Creating unmirrored data aggregates
- Installing the firmware after adding a controller module
- Refreshing the MetroCluster configuration with new controllers
- Enabling storage failover on both controller modules and enabling cluster HA
- Restarting the SVMs
-
Expanding a four-node MetroCluster FC configuration to an eight-node configuration
- Determining the new cabling layout
- Racking the new equipment
- Verifying the health of the MetroCluster configuration
- Checking for MetroCluster configuration errors with Config Advisor
- Sending a custom AutoSupport message prior to adding nodes to the MetroCluster configuration
-
Recabling and zoning a switch fabric for the new nodes
-
Configuring ONTAP on the new controllers
- Clearing the configuration on a controller module
- Assigning disk ownership in AFF systems
- Assigning disk ownership in non-AFF systems
- Verifying the ha-config state of components
- Booting the new controllers and joining them to the cluster
-
Configuring the clusters into a MetroCluster configuration
- Checking for MetroCluster configuration errors with Config Advisor
- Sending a custom AutoSupport message after to adding nodes to the MetroCluster configuration
- Verifying switchover, healing, and switchback
- Expanding a four-node MetroCluster IP configuration to an eight-node configuration
- Removing a Disaster Recovery group
- Where to find additional information
-
Disaster Recovery
- Legal notices
Edit on GitHub