MetroCluster Manuals ( CA08871-401 )
MetroCluster release notes
What's new in MetroCluster support for ONTAP features
What's new in MetroCluster features
What’s new in MetroCluster IP platform and switch support
Install a MetroCluster IP configuration
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.7 and later
ISL requirements
Our validated and MetroCluster-compliant switches
Considerations when deploying MetroCluster in shared layer 2 or layer 3 networks
Considerations for using MetroCluster-compliant switches
Requirements and limitations of MetroCluster-compliant switches
Network speeds and switch port modes for MetroCluster-compliant switches
Learn about unmirrored aggregates in MetroCluster IP configurations
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
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 36-port Cisco 9336C-FX2 switches
Platform port assignments for a 12-port Cisco 9336C-FX2 switch
Platform port assignments for a 36-port Cisco 9336C-FX2 switch connecting NS224 storage
Cable the controller data and management ports
Configure the MetroCluster IP switches
Choose the correct MetroCluster IP switch configuration procedure
Configure Cisco IP switches
Configure the MetroCluster software in ONTAP
How to configure eight-node Configurations
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
Configure the clusters into a MetroCluster configuration
Configure end-to-end encryption
Configure the MetroCluster Tiebreaker or ONTAP Mediator software
Configure ONTAP Mediator for unplanned automatic switchover
Prepare to install ONTAP Mediator
Configuring ONTAP Mediator from a MetroCluster IP configuration
Unconfigure ONTAP Mediator from the MetroCluster IP configuration
Connect a MetroCluster configuration to a different ONTAP Mediator instance
Testing the MetroCluster configuration
Remove MetroCluster configurations
Considerations when using ONTAP in a MetroCluster configuration
How to use the Active IQ Unified Manager and ONTAP System Manager for further configuration and monitoring
Install and Configure MetroCluster Tiebreaker
Overview of the Tiebreaker software
Install the Tiebreaker software
Tiebreaker installation workflow
Prepare to install the Tiebreaker software
Install the Tiebreaker software package
Choose your installation procedure
Install Tiebreaker 1.5
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
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
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
Commands for switchover, healing, and switchback
Monitor the MetroCluster configuration
Monitor and protecting the file system consistency using NVFAIL
Upgrade, refresh, or expand the MetroCluster configuration
Verify Ethernet switch monitoring in a MetroCluster IP configuration
The Ethernet switch health monitor (CSHM) automatically attempts to monitor the switches that it discovers; however, monitoring might not happen automatically if the switches are not configured correctly. You should verify that the health monitor is properly configured to monitor your switches.
