XtremIO XMS version 6.3.0 and higher supports IPv6 and IPv4 connections (Dual Stack) to the management port concurrently for user’s connection.
The following list provides usage guidelines for the primary and secondary IP addresses and gateway addresses:
• The primary IP address and gateway address versions are set during initialization and cannot be modified.
• The secondary IP address and gateway addresses are optional and can be added or removed. The secondary IP address and gateway address versions are based on the primary IP address and gateway address.
• Use the add-xms-secondary-ip-address command to add the secondary IP address and default gateway.
○ Command structure:
add-xms-secondary-ip-address (xms-secondary-ip-and-sn=<string> | xms-secondary-gw-addr=<string>)
The following is an example for the add-xms-secondary-ip-address command:
xmcli(admin)>
add-xms-secondary-ip-address xms-secondary-ip-sn="fd12:3456:789a:1::4/64"
xms-secondary-gw-addr="fd12:3456:789a:1::1"
XMS Secondary address added Successfully xmcli (admin)>
xmcli (admin)> show-xms-info Ethernet Interfaces:
Name Index IP Secondary-IP MAC-Address State Received-Bytes Received-Packets Sent-Bytes Sent-Packets Dropped-Packets Eth0 1 10.234.136.40 fd12:3456:789a:1 4 up 1451340 11648 749704 6600 0 Are you sure you want to remove IP settings?
Are you sure? (Yes/No): yes
XMS Secondary address removed Successfully xmcli (admin)>
XtremIO
A stand-alone Linux-based server called XtremIO Management Server (XMS) controls the system operation of the XtremIO storage array.
The XMS host is deployed as a VM on the VxBlock 1000 management infrastructure. XtremIO can continue operation when disconnected from the XMS, but cannot be managed.
For more information, see the Dell EMC XtremIO User Guide.
In Managing Tags, locate the following tasks:
• Creating and Assigning a New Tag
• Assigning Tags to Storage Elements
• Modifying Tags
• Untagging an Object
• Removing a Tag
In Managing Volumes and Copies, locate the following tasks:
• Creating a Volume
• Modifying Volume Properties
○ Renaming a Volume
○ Resizing a Volume
In Collecting Performance Data, locate the following tasks:
• Refreshing a Volume
• Removing a Volume
• Managing Volume Tags
In Managing Initiator Groups, locate the following tasks:
• Creating an Initiator Group
• Renaming an Initiator Group
• Removing an Initiator Group
• Managing Initiator Group Tags
• Modifying the Initiators List in an Initiator Group In Managing Initiators, locate the following tasks:
• Renaming an Initiator
• Modifying an Initiator’s Operating System
• Removing an Initiator
• Renaming an Initiator
In Mapping, locate the following tasks:
• Generating LUN Mappings for Volumes and Initiator Groups
• Deleting LUN Mapping for Selected Volumes and Initiator Groups
• Modifying LUN Mapping for Selected Volumes and Initiator Groups In Cluster Operations, locate the following tasks:
• Managing the Virtual XMS
• Deploying a Virtual XMS
• Expanding the Virtual XMS Configuration
• Backing up the Virtual XMS
Managing IP Configuration and Dual Stack Configuration
XtremIO XMS version 6.3.0 and higher supports IPv6 and IPv4 connections (Dual Stack) to the management port concurrently.
The following list provides usage guidelines for the primary and secondary IP addresses and gateway addresses:
• The primary IP address and gateway address versions are set during initialization and cannot be modified.
• The secondary IP address and gateway addresses are optional and can be added or removed. The secondary IP address and gateway address versions are based on the primary IP address and gateway address.
• Use the add-xms-secondary-ip-address command to add the secondary IP address and default gateway.
○ Command structure:
add-xms-secondary-ip-address (xms-secondary-ip-and-sn=<string> | xms-secondary-gw-addr=<string>)
The following is an example for the add-xms-secondary-ip-address command:
xmcli(admin)>
add-xms-secondary-ip-address xms-secondary-ip-sn="fd12:3456:789a:1::4/64" xms-secondary-gw-addr="fd12:3456:789a:1::1"
XMS Secondary address added Successfully xmcli (admin)> show-xms-info
Ethernet Interfaces:
Name Index IP Secondary-IP MAC-Address State Received-Bytes Received-Packets Sent-Bytes Sent-Packets Dropped-Packets Eth0 1 10.234.136.40 fd12:3456:789a:1 4 up 1451340 11648 749704 6600 0 Are you sure you want to remove IP settings? Y Are you sure? (Yes/No): Yes
XMS Secondary address removed Successfully
When creating LUNs or adding new servers, use fewer, larger LUNs on XtremIO storage arrays. For applications requiring the most optimal performance, do not use more than 32 server initiators per XtremIO front-end port.
The following table provides the maximum blade server count for the 10 GB connectivity option:
XtremIO storage array X-Brick count
FC ports per fabric Maximum compute chassis
(w/ Cisco UCS 6296UP FIs) Maximum blade server counts (w/ Cisco UCS 6296UP FIs)
1 2 64 32 half width, full-width, or double-height, full-width blades
2 4 64 64 half width, full-width, or double-height, full-width blades
4 8 64 128 half width, full-width, or double-height, full-width
blades
6 12 64 192 half width, full-width, or 128 double-height, full-width
blades
8 16 64 256 half width, full-width, or 128 double-height, full-width
blades
The following table provides the maximum blade server count for the 40 GB connectivity option:
XtremIO storage array
X-Brick count FC ports per fabric Maximum compute chassis
(w/ Cisco UCS 6296UP FIs) Maximum blade server counts (w/ Cisco 6296UP FIs)
1 2 8 32 half width, 32 full-width, or 16
double-height, full-width blades
2 4 16 64 half width, 64 full-width, or 32
double-height, full-width blades
4 8 32 128 half width, 128 full-width, or 64
double-height, full-width blades
6 12 32 192 half width, 128 full-width, or 64
double-height, full-width blades
8 16 32 256 half width, 128 full-width, or 64
double-height, full-width blades
• To balance host clusters, zone four array front-end ports to a single server or spread the VMware vSphere ESXi cluster across several X-Brick building blocks.
• If host clusters are heavily imbalanced in the number of hosts, zone the clusters differently. Ensure that all X-Brick building blocks have similar I/O loads. For larger host clusters, consider configuring eight paths depending on I/O requirement.
• For servers with two vHBAs, zone each vHBA to both XtremIO Storage Controllers on a single X-Brick building block. If the XtremIO array has multiple X-Brick building blocks, zone the vHBAs to different X-Brick building blocks.
○ vHBA 0 -> X1-SC1-FC1 and X1-SC2-FC1
○ vHBA 1 -> X2-SC1-FC2 and X2-SC2-FC2
• An example of four X-Brick building blocks and four clusters:
Cluster Port
Cluster Port
Cluster 3 X1-SC1-P2
X1-SC2-P2 X3-SC1-P1 X3-SC2-P1
Cluster 4 X2-SC1-P2
X2-SC2-P2 X4-SC1-P1 X4-SC2-P1
• For servers with four vHBAs, zone each vHBA to one XtremIO storage controller for four paths as follows:
vHBA XtremIO storage controller
vHBA 0 X1-SC1-FC1
vHBA 1 X1-SC2-FC2
vHBA 2 X2-SC1-FC1
vHBA 3 X2-SC2-FC2
• If there is only one VMware vSphere ESXi cluster that is connected to the XtremIO cluster, zone the vHBAs to every XtremIO front-end port in the fabric for hosts with 2 vHBAs.
• If there are four vHBAs, zone each vHBA to half the ports in the fabric.
• For ESXi clusters on VxBlock Systems, zone four paths per server. Increase up to eight paths depending on application requirements.
• VMware vSphere has a limit of 1024 device paths per server. Consider this limit when configuring more than two vHBAs.
• XtremIO has a limit of 16,000 paths and 1024 initiators per XtremIO cluster.
• Configure volumes with a block size of 512 bytes.
• Format VMware vSphere ESXi VMs as Thick Provision Eager Zeroed.