Purity is the operating environment that queries and manages the FlashArray hardware, networking, and storage components. The Purity software is distributed with the FlashArray.
Purity provides two ways to administer the FlashArray: through the browser-based graphical user interface (Purity GUI) and the command-driven interface (Purity CLI).
Purity follows certain naming and numbering conventions.
Valid characters are letters (A-Z and a-z), digits (0-9), and the hyphen (-) character. Volume names may also include the underscore (_) character. The first and last characters of a name must be alphanumeric, and a name must contain at least one letter.
Most objects in Purity that can be named, including host groups, hosts, volumes, protection groups, volume and protection group suffixes, SNMP managers, and subnets may be 1-63 characters in length.
Array names may be 1-56 characters in length. The array name length is limited to 56 characters so that the names of the individual controllers, which are assigned by Purity based on the array name, do not exceed the maximum allowed by DNS.
Names are case-insensitive on input.
all represent the same volume.
Purity displays names in the case in which they were specified when created or renamed.
Volume sizes are specified as an integer, optionally followed by one of the suffix letters
S, K, M, G, T, P, denoting 512-byte sectors, KiB, MiB, GiB, TiB, and PiB,
respectively, where "Ki" denotes 2^10, "Mi" denotes 2^20, and so on.
If a suffix letter is not specified, the size is expressed in sectors.
Volumes must be between one megabyte and four petabytes in size. If a volume size of less than one megabyte is specified, Purity adjusts the volume size to one megabyte. If a volume size of more than four petabytes is specified, the Purity command fails.
Volume sizes cannot contain digit separators.
1000g is valid, but
1,000g is not.
FlashArray supports two versions of the Internet Protocol: IP Version 4 (IPv4) and IP Version 6 (IPv6). IPv4 and IPv6 addresses follow the addressing architecture set by the Internet Engineering Task Force.
An IPv4 address consists of 32 bits and is entered
in the form
ddd is a number ranging from
representing a group of 8 bits.
Here are some examples:
puredns setattr --domain mydomain.com --nameservers 192.0.2.10 purelog create --uri tcp://192.0.2.100:614 LOGSERVER2 purenetwork setattr --address 192.0.2.0/24 ct0.eth1 purenetwork setattr --address 192.0.2.0 --netmask 255.255.255.0 ct0.eth1 puresnmp create --host 192.0.2.255 --community SNMPMANAGER1 puresubnet create --prefix 192.0.2.0/24 --vlan 100 ESXHost001
An IPv6 address consists of 128 bits
and is written in in the form
xxxx is a hexadecimal number
representing a group of 16 bits.
Colons separate each 16-bit field.
Leading zeros can be omitted in each field.
Furthermore, consecutive fields of zeros can be shortened by
replacing the zeros with a double colon (
For example, IPv6 address
To use an IPv6 address in a URL or URI,
enclose the entire address in square brackets (
When specifying a URL or URI with a port number, append the port number after the
end of the entire address.
Here are some examples:
puredns setattr --domain mydomain.com --nameservers 2001:db8:85a3::8a2e:370:7334 purelog create --uri tcp://[2001:db8:85a3::8a2e:370:7334]:614 LOGSERVER2 purenetwork setattr --address 2001:db8:85a3::8a2e:370:7334/64 ct0.eth1 purenetwork setattr --address 2001:db8:85a3::8a2e:370:7334 --netmask 64 ct0.eth1 puresnmp create --host [2001:db8:85a3::8a2e:370:7334] --community SNMPMANAGER1 puresubnet create --prefix 2001:db8:85a3::/64 --vlan 100 ESXHost001
Storage Network Addresses
A Purity host is comprised of a host name and one or more WWNs or IQNs. The host cannot communicate with the array until at least one WWN or IQN has been associated with it.
Fibre Channel worldwide names (WWNs) follow the naming standards set by the
IEEE Standards Association.
WWNs are comprised of eight pairs of case-insensitive hexadecimal numbers,
optionally separated by colons.
iSCSI qualified names (IQNs) follow the naming structures set by
the Internet Engineering Task Force (see RFC 3720).
Like hosts, WWNs and IQNs must be unique in an array. A host can be associated with multiple storage network addresses, but a storage network address can only be associated with one host.