- MetroCluster docs
-
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
- 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.1 or later
-
Port assignments for FC switches when using AFF A900 systems
- Port assignments for FC switches when using AFF A900 or FAS9500 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
- Install FC-to-SAS bridges and SAS disk shelves
-
Configure hardware for sharing a Brocade 6510 FC fabric during transition
- 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
-
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
-
How to use 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
- 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
-
Considerations for using MetroCluster-compliant switches
- 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 a Cisco 9336C-FX2 shared switch
- 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 the MetroCluster software in ONTAP
-
Configure the MetroCluster software using the CLI
- 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
- Configure end-to-end encryption
- Verify switchover, healing, and switchback
- Configure the MetroCluster Tiebreaker or ONTAP Mediator software
- Protect configuration backup files
-
Configure the MetroCluster software using System Manager
-
-
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
- How the ONTAP Mediator supports automatic unplanned switchover
- Manage the ONTAP Mediator with System Manger
- 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
- Choose the correct installation procedure for your configuration
-
Cable a two-node SAS-attached stretch MetroCluster configuration
-
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
- 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
- Considerations when removing MetroCluster configurations
-
How to use 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
-
Install and configure MetroCluster Tiebreaker
- What's new
- Overview of the Tiebreaker software
-
Install the Tiebreaker software
- 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
-
Perform switchover, healing, and switchback
-
Perform switchover for tests or maintenance
- Overview
- Limitations when the system is in switchover
- 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
- Perform a switchback
- Verify a successful switchback
- Commands for switchover, healing, and switchback
- Use System Manger to perform switchover and switchback (MetroCluster IP configurations only)
- Monitor the MetroCluster configuration
- Monitor and protecting the file system consistency using NVFAIL
- Where to find additional information
-
-
Maintain the MetroCluster components
-
Prepare for MetroCluster maintenance
- Enable console logging before performing maintenance tasks
- Remove ONTAP Mediator or Tiebreaker monitoring before performing maintenance tasks
- MetroCluster failure and recovery scenarios
- How to use the Interoperability Matrix Tool to find MetroCluster information
- Where to find procedures for MetroCluster maintenance tasks
-
Maintenance procedures for MetroCluster FC configurations
- Modify a switch or ATTO bridge IP address for health monitoring
-
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
- Change the vendor or model of an FC switch
- Replace a shelf nondisruptively in a fabric-attached MetroCluster configuration
-
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
- 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
- Power off and power on a single site in a MetroCluster FC configuration
- Power off an entire MetroCluster FC configuration
-
Maintenance procedures for MetroCluster IP configurations
- Modify the properties of a MetroCluster IP interface
-
IP switch maintenance and replacement
- Replace an IP switch or change the use of existing MetroCluster IP switches
- Online or offline MetroCluster IP interface ports
- 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
- Add, remove, or change ISL ports nondisruptively on Cisco IP switches
- How to identify storage in a MetroCluster IP configuration
- Add shelves to a MetroCluster IP configuration using shared storage MetroCluster switches
- Configure end-to-end encryption in a MetroCluster IP configuration
- Power off and power on a single site in a MetroCluster IP configuration
- Power off an entire MetroCluster IP configuration
-
Maintenance procedures for all MetroCluster configurations
- Replace a shelf nondisruptively in a stretch MetroCluster configuration
- When to migrate root volumes to a new destination
- Move a metadata volume in MetroCluster configurations
- Rename a cluster in MetroCluster configurations
- Check the health of a MetroCluster configuration
- 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
- Enable console logging
- 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)
- 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
- 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
- Enable console logging
- Verify the state of the MetroCluster configuration
- Send a custom AutoSupport message before adding nodes 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
- 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
- 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
- Enable console logging
- 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
-
Configure ONTAP on the new controllers
- 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
- Enable console logging
- 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