The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The XtremIO Storage Array is an all-flash system, based on a scale-out architecture. The system uses building blocks, called X-Bricks, which can be clustered together. The system operation, controlled by a stand-alone dedicated Linux-based server, is called the XtremIO Management Server (XMS). Each XtremIO cluster requires an XMS host, which can be either a physical or a virtual server. A single XMS host can manage multiple clusters, so a single cluster may not require its own XMS host. The array continues operating if it is disconnected from the XMS, but cannot be configured or monitored.
XtremIO array architecture is designed to deliver the full performance potential of flash. Linear scaling of all resources, such as CPU, RAM, SSDs, and host ports, is done in a balanced manner. This allows the array to achieve any desired performance level, while maintaining consistency of performance that is critical to predictable application behavior. The XtremIO Storage Array provides a high level of performance that is consistent over time, system conditions, and access patterns. It is designed for high-granularity true random I/O.
Cluster performance level is not affected by capacity utilization level, number of volumes, or aging effects. Moreover, performance is not based on a "shared cache" architecture and is not affected by the data set size or data access pattern. Due to its content-aware storage architecture, XtremIO provides:
Even distribution of data blocks, inherently leading to maximum performance and minimal flash wear
Even distribution of metadata
Freedom from hotspots in data or metadata
Easy setup and no tuning
Advanced storage functionality, including Inline Data Deduplication and Compression, thin provisioning, advanced data protection (XDP), snapshots, and more
The XtremIO connector allows you to monitor and manage the XtremIO volumes, initiator groups, LUN mappings, snapshots, and basic network configurations. It connects through the HTTPS protocol. In order to manage XtremIO in Cisco UCS Director, the XMS Host IP is used when adding a physical account in Cisco UCS Director.
The Task Library contains Cisco UCS Director tasks related to Cisco EMC XtremIO. You can view the Task Library using the following steps.
To manage EMC XtremIO, Cisco UCS Director uses the XMS Host IP.
Cisco UCS Director tests the connection to the EMC XtremIO storage system and XMS host. If that test is successful, it adds the XtremIO account and discovers all infrastructure elements in the storage system that are associated with that account. This discovery process and inventory collection cycle takes few minutes to complete.
The polling interval configured on the System Tasks tab on the window specifies the frequency of inventory collection. For more information about configuring the polling interval, see the Cisco UCS Director Network Devices Management Guide.
A Volume is a set of blocks, presented to the operating environment as a range of consecutive logical blocks with disk-like storage and I/O semantics. It is possible to define various percentages of disk space as Volumes in an active cluster.
The XtremIO Storage Array uses the term "Initiators" to refer to ports that can access a Volume. Initiators are managed in the XtremIO Storage Array by assigning them to an Initiator Group. The Initiators within an Initiator Group share access to one or more of the cluster's Volumes.
Initiators are added to the cluster by defining them in an Initiator Group. You can define Initiators when adding a group, or later define them by using the Edit Initiator Group option. To remove an Initiator, edit the group and delete the Initiator's properties.
When you map a volume to an initiator group, a Logical Unit Number (LUN) is assigned to that volume.
You can map multiple volumes to an initiator group. The initiator group's first mapped volume is assigned a LUN of 1. Additional mapped volumes are assigned LUNs in sequential order. You can also manually enter a LUN ID during mapping. These numbers cannot be changed later so any change must be specified during LUN creation.
Note | You cannot change a LUN ID after a volume is mapped to an initiator group. |
Consistency Groups (CG) are used to create a consistent image of a set of Volumes, usually used by a single application, such as a database. With XtremIO CGs, you can create a Snapshot of all Volumes in a group, using a single command. This ensures that all Volumes are created at the same time. Many operations that are applied on a single Volume can also be applied on a CG.
To establish an iSCSI connection for transferring data, first define an iSCSI portal. An iSCSI portal is an IPv4 address and port associated with a Target port. Each iSCSI Target can be associated with multiple portals. If an IP connection requires routing to remote networks, you can define routing rules that apply to the iSCSI Target ports only.
Snapshots are instantaneous copy images of Volume data. The state of the data captured is exactly as it appeared at the specific point in time that the Snapshot was created. This enables you to save the Volume data state and then access the specific Volume data whenever needed, including after the source Volume has changed.
A Snapshot can be taken either directly from a source Volume or from other Snapshots within a source Volume’s group (Volume Snapshot Group). XtremIO Snapshots are by default read-write, but can be created as read-only to maintain immutability.
The source data remains available without interruption, while the Snapshot can be used to perform other functions on the data. Changes made to the Snapshot’s source do not affect the Snapshot data.
XtremIO Snapshots are space-efficient both in terms of metadata consumed and physical capacity. Snapshots are implemented using redirect-on-write methodology. New writes to the source Volume (or Snapshot) are redirected to new locations, and only metadata is updated to point to the new data location. This method guarantees that there is no performance degradation while Snapshots are created.
Note | The Create Snapshot Set feature is also available under the Snapshots tab. The steps used to create a Snapshot Set are identical. |
Cisco UCS Director XtremIO provides the following System Reports:
The following reports are displayed as child reports under the Clusters Report.