Clustered Data ONTAP® 8.3
MetroCluster Installation and Configuration Guide
MetroCluster documentation
Preparing for the MetroCluster installation
Differences between 7-Mode and clustered Data ONTAP MetroCluster configurations
Understanding the parts of the MetroCluster configuration
Local HA pair illustration
Redundant FC-to-SAS bridges
Redundant FC switch fabrics
The cluster peering network
Considerations for MetroCluster configurations with native disk shelves or array LUNs
Required MetroCluster components and naming guidelines
Considerations when transitioning from 7-Mode to clustered Data ONTAP
Configuration of new MetroCluster systems
Hardware setup checklist
Software setup checklist
Choosing the correct installation procedure for your system
Configuring the MetroCluster hardware components
Gathering required information and reviewing the workflow
FC switch and FC-to-SAS bridge worksheet
Hardware installation workflow
Installing and cabling MetroCluster components
Racking the hardware components
Cabling the FC-VI and HBA adapters to the FC switches
Cabling the ISLs between MetroCluster sites
Cabling the cluster interconnect
Cabling the cluster peering connections
Cabling the HA interconnect, if necessary
Cabling the management and data connections
Recommended port assignments for FC switches
Installing FC-to-SAS bridges and SAS disk shelves
Preparing for the installation
Installing the FC-to-SAS bridge and SAS shelves
Configuring the FC switches
Configuring the FC switches by running a configuration file
Configuring Brocade FC switches with configuration files
Configuring the Cisco FC switches with configuration files
Configuring the Cisco or Brocade FC switches manually
Configuring the Brocade FC switches
Reviewing Brocade license requirements
Setting the Brocade FC switch values to factory defaults
Configuring the basic switch settings
Configuring the E-ports on a Brocade FC switch
Configuring the non-E-ports on the Brocade switch
Configuring zoning on Brocade FC switches
Setting ISL encryption on Brocade 6510 switches
Disabling virtual fabric
Setting the payload
Setting the authentication policy
Enabling ISL encryption in a Brocade switch
Configuring the Cisco FC switches
Reviewing Cisco license requirements
Setting the Cisco FC switch to factory defaults
Configure the Cisco FC switch basic settings and community string
Acquiring licenses for ports
Enabling ports in a Cisco MDS 9148 switch
Configuring the F-ports on a Cisco FC switch
Assigning buffer-to-buffer credits to F-Ports in the same port group as the ISL
Creating and configuring the VSANs on Cisco FC switches
Configuring the E-ports on the Cisco FC switch
Configuring zoning on a Cisco FC switch
Ensuring the FC switch configuration is saved
Configuring hardware for sharing a Brocade 6510 FC fabric during transition
Reviewing Brocade license requirements
Racking the hardware components
Cable the new MetroCluster controllers to the existing FC fabrics
Configuring switch fabrics sharing between the 7-Mode and clustered MetroCluster configuration
Disabling one of the switch fabrics
Deleting TI zoning and configuring IOD settings
Ensuring ISLs are in the same port group and configuring zoning
Reenabling the switch fabric and verify operation
Configuring the MetroCluster software in Data ONTAP
Gathering required information and reviewing the workflow
Worksheet for IP network information for site A
Worksheet for IP network information for site B
Software configuration workflow
Similarities and differences between regular cluster and MetroCluster configurations
Verifying disk assignment in Maintenance mode
Assigning disk ownership shelf by shelf
Verifying the HA state of components is mcc in Maintenance mode
Running System Setup to configure the nodes and clusters
Configuring the clusters into a MetroCluster configuration
Peering the clusters
Configuring intercluster LIFs to use dedicated intercluster ports
Configuring intercluster LIFs to share data ports
Creating the cluster peer relationship
Mirroring the root aggregates
Creating a mirrored data aggregate on each node
Implementing the MetroCluster configuration
Configuring MetroCluster components for health monitoring
Configuring the MetroCluster FC switches for health monitoring
Configuring FC-to-SAS bridges for health monitoring
Checking the MetroCluster configuration
Checking for MetroCluster configuration errors with Config Advisor
Verifying local HA operation
Verifying switchover, healing, and switchback
Protecting configuration backup files
Planning and installing a MetroCluster configuration with array LUNs
Planning for a MetroCluster configuration with array LUNs
Requirements for a MetroCluster configuration with array LUNs
Implementation overview for a MetroCluster configuration with array LUNs
Connecting devices in a MetroCluster configuration with array LUNs
Switch zoning for a MetroCluster configuration with array LUNs
Setting up Data ONTAP after connecting devices in a MetroCluster configuration with array LUNs
Implementing a MetroCluster configuration with both disks and array LUNs
Planning a MetroCluster configuration with disks and array LUNs
Considerations for implementing a MetroCluster configuration with disks and array LUNs
Example of a MetroCluster configuration with disks and array LUNs
Using the OnCommand management tools for further configuration and monitoring
Requirements and limitations when using Data ONTAP in a MetroCluster configuration
Job schedules in a MetroCluster configuration
Cluster peering from the MetroCluster sites to a third cluster
Volume creation on a root aggregate
Networking and LIF creation guidelines for MetroCluster configurations
Volume or FlexClone command VLDB errors
Modifying volumes to set NVFAIL in case of switchover
Monitoring and protecting database validity by using NVFAIL
How NVFAIL protects database files
Commands for monitoring data loss events
Accessing volumes in NVFAIL state after a switchover
Recovering LUNs in NVFAIL states after switchover
Glossary of MetroCluster terms
Copyright information
Trademark information
How to send comments about documentation and receive update notification
