MetroCluster Manuals ( CA08871-401 )

MetroCluster Manuals

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.7

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

Cable the controller data and management ports

Configure Cisco IP switches

Configure basic settings

Configure MACsec encryption on Cisco 9336C 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 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

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

Upgrade, refresh, or expand the MetroCluster configuration

Expand a MetroCluster IP configuration

Remove a Disaster Recovery group

to Japanese version

Risks and limitations of using MetroCluster automatic forced switchover

Beginning with ONTAP 9.12.1, you can enable the MetroCluster automatic forced switchover feature in a MetroCluster IP configuration. This feature is an extension of the Mediator-assisted unplanned switchover (MAUSO) feature.

Switchover upon detection of a site failure happens automatically when you enable the MetroCluster automatic forced switchover feature. You can use this feature to supplement the MetroCluster IP automatic switchover capability.

When you allow a MetroCluster IP configuration to operate in automatic forced switchover mode, the following known issues might lead to data loss:

  • The nonvolatile memory in the storage controllers is not mirrored to the remote disaster recovery (DR) partner on the partner site.

You might encounter scenarios that are not mentioned. Fujitsu is not responsible for any data corruption, data loss, or other damage that might arise from enabling the MetroCluster automatic forced switchover feature. Do not use the MetroCluster automatic forced switchover feature if the risks and limitations are not acceptable to you.
Top of Page