ONTAP FlexArray Documentation
Implementing Third-Party Storage
-
ONTAP FlexArray Documentation
-
ONTAP FlexArray Documentation
-
Implementing E-Series storage
-
Where to find information for configurations with storage arrays
-
Requirements for configuring E-Series storage arrays
-
Supported fabric-attached configurations for E-Series storage arrays
-
Implementing third-party storage
-
Where to find information for configurations with storage arrays
-
General configuration guidelines for all storage arrays
-
EMC VNX storage arrays
-
EMC Symmetrix storage arrays
-
Hitachi storage arrays
-
HP EVA storage arrays
-
HP XP storage arrays
-
IBM DS storage arrays
-
IBM XIV storage arrays
-
3PAR storage arrays
-
Required parameters for 3PAR arrays with ONTAP systems
-
Supported fabric-attached configurations
-
Installing FlexArray
-
FlexArray Virtualization technology overview—using array LUNs for storage
-
Zoning in a configuration with storage arrays
-
Planning a configuration with array LUNs
-
Where to find information for configurations with storage arrays
-
Planning for RAID implementation
-
Planning for ONTAP use of array LUNs
-
How array LUNs become available for ONTAP storage use
-
Factors that impact the number and size of array LUNs you need
-
Considering checksum type when planning array LUN size and number
-
Planning for LUN security on the storage arrays
-
Planning for paths to array LUNs
-
Requirements for redundant setup of components in a path
-
Required number of paths to an array LUN
-
Benefits of using multiple LUN groups
-
Planning a port-to-port connectivity scheme
-
Determining the array LUNs for specific aggregates
-
Setting up ONTAP to work with array LUNs
-
Commands for checking back-end configuration
-
Verifying installation with storage arrays
-
Checking for back-end configuration errors preventing system operation
-
Verifying that the back-end configuration matches the intended configuration
-
Managing array LUNs using ONTAP
-
Troubleshooting configurations with storage arrays
-
Invalid path setup examples
-
Relationship between zoning and host group configuration
-
Target queue depth customization
Site
This page
Sections
Sections
Sections
- ONTAP FlexArray Docs
-
Implementing E-Series storage
-
Where to find information for configurations with storage arrays
- ONTAP systems that can use array LUNs on storage arrays
-
Requirements for configuring E-Series storage arrays
-
Supported fabric-attached configurations for E-Series storage arrays
- Stand-alone basic configuration
- Stand-alone system with two 2-port array LUN groups
- Single 4-port array LUN group configuration
- Two 4-port array LUN group configuration
- Eight-port array LUN group configuration
- Attaching FC initiator port to multiple targets ports
- Sharing a target port with two FC initiator ports
- Supported direct-attached configurations with E-Series storage arrays
-
-
Implementing third-party storage
-
Where to find information for configurations with storage arrays
- Support for advanced features of storage arrays
- ONTAP systems that can use array LUNs on storage arrays
-
General configuration guidelines for all storage arrays
-
EMC VNX storage arrays
-
EMC Symmetrix storage arrays
-
Hitachi storage arrays
- Required parameters for Hitachi storage arrays with ONTAP systems
- Workaround when LUNs are not visible with Hitachi storage arrays
- Requirements for creating LUNs in dynamic pools
- Requirements for formatting array LUNs
- Requirements for using disks external to the storage array
- Guidelines for configuring ports on Hitachi storage arrays
- Hitachi storage array families
-
HP EVA storage arrays
-
HP XP storage arrays
- Required parameters for HP XP storage arrays with ONTAP
- Workaround when LUNs are not visible with HP XP storage arrays
- Requirements for creating LUNs in dynamic pools
- Requirements for formatting array LUNs
- Requirements for using disks external to the storage array
- Guidelines for configuring ports on HP XP storage arrays
- HP XP storage array families
-
IBM DS storage arrays
-
IBM XIV storage arrays
-
3PAR storage arrays
-
Supported fabric-attached configurations
- Stand-alone basic configuration
- Stand-alone system with two 2-port array LUN groups
- Single 4-port array LUN group configuration
- Two 4-port array LUN group configuration
- Eight-port array LUN group configuration
- Attaching FC initiator port to multiple targets ports
- Sharing a target port with two FC initiator ports
-
-
Installing FlexArray
-
FlexArray Virtualization technology overview—using array LUNs for storage
-
Zoning in a configuration with storage arrays
-
Planning a configuration with array LUNs
-
Planning for RAID implementation
-
Planning for ONTAP use of array LUNs
- How array LUNs are made available for host use
-
How array LUNs become available for ONTAP storage use
- Array LUN type supported by ONTAP
-
Factors that impact the number and size of array LUNs you need
- Factors impacting the required number of array LUNs
- Minimum number of array LUNs required per ONTAP system
- Spare array LUN requirement for core dumps
- Minimum and maximum array LUN sizes supported for ONTAP configurations
- Array LUN size required for the root volume
- Elements that reduce the usable space in an array LUN
-
Considering checksum type when planning array LUN size and number
- Location of the root volume
-
Planning for LUN security on the storage arrays
-
Planning for paths to array LUNs
-
Requirements for redundant setup of components in a path
-
Required number of paths to an array LUN
-
Benefits of using multiple LUN groups
- Array LUN name format
- Pre-cluster array LUN name format
- How the array LUN name is displayed in ONTAP
- Valid pathing: stand-alone system with a single 2-port array LUN group
- Valid pathing: a single 4-port array LUN group in a fabric-attached configuration
- Valid pathing: eight-port array LUN group configuration
-
-
Planning a port-to-port connectivity scheme
- Requirements for using FC initiator ports
- How FC initiator ports are labeled
- Configuring FC ports as initiators
- Rules for sharing an FC initiator port with multiple target ports
- Example configuration: shared FC initiator ports
- Rules for sharing a target port with multiple FC initiator ports
- Example configuration: shared target ports
- Checking the number of array LUNs visible on an FC initiator port
- Requirements for connecting to storage arrays
- Guidelines for connecting a V-Series system to native disk shelves
- FC initiator ports required for connection to native disks
- Example of non-optimized usage of a storage array target port
-
Determining the array LUNs for specific aggregates
- Rules for mixing storage in array LUN aggregates
- How the checksum type is determined for array LUN aggregates
- Checksum type considerations for adding spare array LUNs to aggregates
- Aggregate rules when the storage arrays are from the same family
- Aggregate rules when the storage arrays are from different vendors or families
- Preparing a storage array for use with ONTAP systems
- Connecting an ONTAP system to a storage array
- Setting up the switches
- Configuring LUN security
-
Setting up ONTAP to work with array LUNs
-
Commands for checking back-end configuration
-
Verifying installation with storage arrays
-
Checking for back-end configuration errors preventing system operation
- The storage errors show messages and their resolution
- Array LUN size is either smaller or larger than the supported values
- LUN IDs for the same LDEV do not match
- Volume Set Addressing is inconsistent
- Duplicate LUN IDs on a target port
- Fewer than two paths to an array LUN
- An access control LUN is presented to ONTAP
- All paths to an array LUN are on the same storage array controller
- Array LUNs are configured with conflicting failover modes
- Array LUN is marked foreign and has a reservation
-
Verifying that the back-end configuration matches the intended configuration
- Reasons for no LUNs in the array LUN group
- Reasons for fewer array LUN groups than expected
- Reasons for more array LUN groups than expected
- Reasons for more paths to an array LUN than expected
- Reasons for the incorrect number of LUNs in array LUN groups
- Reasons storage arrays are missing from command output
-
-
Managing array LUNs using ONTAP
- Modifying assignment of spare array LUNs
- Checking the checksum type of spare array LUNs
- Changing the checksum type of an array LUN
- Prerequisites to reconfiguring an array LUN on the storage array
- Changing array LUN size or composition
- Removing one array LUN from use by ONTAP
- Preparing array LUNs before removing an ONTAP system from service
-
Troubleshooting configurations with storage arrays
- Additional tasks after installing and testing an ONTAP configuration with array LUNs
- Obtaining WWPNs manually
-
Target queue depth customization
- Terminology comparison between storage array vendors
-
Edit on GitHub