Skip to main content

Dell PowerMax Family Site Planning Guide PowerMax 2500 and PowerMax 8500

Preface

As part of an effort to improve its product lines, Dell Technologies periodically releases revisions of its software and hardware. Functions that are described in this document may not be supported by all versions of the software or hardware. The product release notes provide the most up-to-date information about product features.

Contact your Dell Technologies representative if a product does not function properly or does not function as described in this document.

NOTE:This document was accurate at publication time. New versions of this document might be released on Dell Technologies Online Support (https://www.dell.com/support/home). Check to ensure that you are using the latest version of this document.

Purpose

This document is intended for use by customers and company representatives who want to plan the purchase and installation of a PowerMax 2500 or PowerMax 8500 system.

Audience

This document is intended for use by customers or company representatives.

Related documentation

Dell PowerMax Family Product Guide
Provides information about PowerMax 2500 and 8500 with PowerMaxOS 10, and PowerMax 2000 and 8000 arrays with PowerMaxOS 5978.
Dell PowerMaxOS 10.0.0.0 Release Notes
Describes new features and any limitations.
Dell PowerMax Family Security Configuration Guide
Shows how to securely deploy PowerMax arrays running PowerMaxOS.

Naming conventions

The PowerMaxOS 10 release introduces new terms to standardize terminology across the Dell Power platforms. The new terms are used interchangeably in this document. The new terms are:

Table 1. PowerMaxOS naming conventionsPowerMaxOS naming conventions
PowerMax 2500 and PowerMax 8500 PowerMax 2000 and PowerMax 8000
Node Director
Node Pair Engine
DME DAE
IB switch MIBE
PowerMax File eNAS

Typographical conventions

Dell Technologies uses the following type style conventions in this document:

Table 2. Typographical conventions used in this contentTypographical conventions used in this content
Font Description
Bold Used for names of interface elements

Examples: Names of windows, dialog boxes, buttons, fields, tab names, key names, and menu paths (what the user selects or clicks)

Italic Used for full titles of publications referenced in text
Monospace Used for:
  • System code
  • System output, such as an error message or script
  • Pathnames, filenames, prompts, and syntax
  • Commands and options
Monospace italic Used for variables
Monospace bold Used for user input
[ ] Square brackets enclose optional values.
| A vertical bar indicates alternate selections. The bar means "or".
{ } Braces enclose content that the user must specify, such as x or y or z.
... Ellipses indicate nonessential information that is omitted from the example.

Where to get help

Support, product and licensing information can be obtained as follows:

Product information
Dell Technologies technical support, documentation, release notes, software updates, or information about Dell Technologies products can be obtained at Dell Technologies Online Support (https://www.dell.com/support/home) (registration required) or on the PowerMax Info Hub (https://www.dell.com/support/kbdoc/en-us/000189115/powermax-info-hub-product-documentation-videos).
Technical support
To open a service request through Dell Technologies Online Support (https://www.dell.com/support/home), you must have a valid support agreement. Contact your Dell Technologies sales representative for details about obtaining a valid support agreement or to answer any questions about your account.

Your comments

Your suggestions help improve the accuracy, organization, and overall quality of the documentation. Send your comments and feedback to: powermaxcontentfeedback@dell.com


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\