Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell PowerVault ME4 Series Storage System CLI Guide

PDF

Command syntax

General rules for specifying commands

Command names and parameter names are not case sensitive.

Parameters enclosed in square brackets ([ ]) are optional. Do not type the bracket characters.

Parameter values separated by ’|’ characters are options. Enter only one of the values. Unless specified otherwise, enumerated values are not case sensitive.

Parameter values in italics are variables. Substitute text that is appropriate for the task you want to perform. Unless specified otherwise, variable values such as names of users and volumes are case sensitive and have a maximum length in bytes. When encoded in UTF-8, a single character can occupy multiple bytes. Typically:
  • 1 byte per character for English, French, German, and Spanish
  • 3 bytes per character for Chinese, Japanese, and Korean

Unless otherwise specified, a parameter value can include spaces and printable UTF-8 characters except: " , < > \

A parameter value that includes a space must be enclosed in double quotes. Unless specified otherwise, if you include leading or trailing spaces with a value (such as a name) in double quotes, those spaces are treated as part of the value.

Parameters can be entered in any order. However, for a parameter with no keyword, if you want to specify a value that is partially or entirely the same as the keyword of an optional parameter, you must specify the optional parameter before the value. For example, to create a user named base you must specify the optional base parameter before the name base: create user base 2 base

Specifying drawers

In an enclosure with drawers:
  • Disk drawers are specified by enclosure ID and drawer number. Enclosure IDs increment from 0. Drawer IDs increment from 0 in each enclosure. Example: 2.1
  • Disks are specified without the drawer number, as described below.

Specifying disks

Disks are specified by enclosure ID and slot number. Enclosure IDs increment from 0. Disk IDs increment from 0 in each enclosure. You can specify:
  • A disk. Example: 1.4
  • A hyphenated range of disks. Example: 1.4-7
  • A comma-separated list of individual disks, ranges, or both (with no spaces). Example: 1.4,1.6-9
  • A RAID 10 or 50 disk group with disks in subgroups separated by colons (with no spaces). RAID-10 example:1.1-2:1.3-4:1.7,1.10

Specifying disk groups

You can specify:
  • A disk group by its name or serial number. A unique serial number is automatically assigned when a disk group is created, and does not change for the life of the disk group.
  • A list of disk-group names or serial numbers separated by commas (with no spaces). Not all commands support lists. Example: dg1,"Disk group 1"

Specifying pools

For virtual storage, you can specify:
  • A pool by its name or serial number.
  • A list of pool names or serial numbers separated by commas (with no spaces). Not all commands support lists. Example: A,B

Specifying volumes

You can specify:
  • A volume by its name or serial number. A unique serial number is automatically assigned when a volume is created, and does not change for the life of the volume.
  • A list of volume names or serial numbers separated by commas (with no spaces). Not all commands support lists. List example: vd1_v1,"Vol #1".

Specifying volume groups

For virtual storage, you can specify:
  • A volume group by its name in the format volume-group.*, where * represents all volumes in the group. Example: TestVolumes.*

Specifying ports

Controller module host ports are specified by port number only (to use the same port in both controllers) or by controller ID and port number (to specify a port in one controller).

In a 2U12 or 2U24 enclosure, the top controller module ID is A and the bottom controller module ID is B. In a 5U84 enclosure, the left controller module ID is A and the right controller module ID is B. Controller module IDs are not case sensitive.

Port IDs increment from 0 in each controller module.

You can specify:
  • A port ID in both controllers. Example: 1
  • A port ID in one controller. Example: A1
  • A hyphenated range of IDs. Do not mix controller IDs in a range. Example: b1-b2 or 1-2
  • A comma-separated list of IDs, ranges, or both (with no spaces). Example: A1,b1-b2 or A1,2

Specifying initiators and hosts

You can specify:
  • An FC initiator by its nickname or 16-hex-digit WWPN.
  • A SAS initiator by its nickname or 16-hex-digit WWPN.
  • An iSCSI initiator by its nickname or node name (typically the IQN).
  • A host by name in the format host-name.*, where * represents all initiators in the host. Example: Mail_Server.*

Specifying host groups

For virtual storage, you can specify:
  • A host group by name in the format host-group.*.*, where the first * represents all hosts in the group and the second * represents all initiators in those hosts. Example: TestLab.*.*

Specifying fan modules

In a 5U84 enclosure:
  • Fan modules are specified by enclosure ID and module number.
  • Enclosure IDs increment from 0.
  • Module IDs increment from 0 in each enclosure.
Example: 1.1

User password rules

  • The value is case sensitive.
  • The value can have 8–32 characters.
  • The value can include printable UTF-8 characters except a space or: " ' , < > \
  • A value that includes only printable ASCII characters must include at least one uppercase character, one lowercase character, one numeric character, and one non-alphanumeric character. This rule does not apply if the password contains UTF-8 characters that are outside the range of printable ASCII characters.

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: <>()\