Dell Emc Xtremio Storage Array: Admin Cli Guide
Dell Emc Xtremio Storage Array: Admin Cli Guide
Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without
notice.
The information in this publication is provided as is. Dell makes no representations or warranties of any kind with respect to the
information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use,
copying, and distribution of any Dell software described in this publication requires an applicable software license.
Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be property of their respective
owners.
For the most up-to-date regulatory document for your product line, go to Dell EMC Online Support (https://support.emc.com).
Preface
Chapter 1 Introduction
Using the Command Line Interface (CLI) ........................................................ 8
Accessing the CLI via an SSH Client ......................................................... 9
Accessing the CLI via an SSH Key Authentication................................... 10
Using the CLI Help....................................................................................... 10
General Guidelines................................................................................ 10
Using Filters .......................................................................................... 11
Specifying Output Parameters ............................................................... 12
Setting Output Display .......................................................................... 13
Objects Naming Limitations ........................................................................ 13
Completion Codes ...................................................................................... 14
As part of an effort to improve its product lines, Dell EMC periodically releases revisions of
its software and hardware. Therefore, some functions described in this document might
not be supported by all versions of the software or hardware currently in use. The product
release notes provide the most up-to-date information on product features.
Contact your Dell EMC technical support professional if a product does not function
properly or does not function as described in this document.
Note: This document was accurate at publication time. Go to Dell EMC Online Support
(https://support.emc.com) to ensure that you are using the latest version of this
document.
This document provides specific information on XtremIO clusters that are managed by
XMS versions 6.3.0 and 6.3.1. For XtremIO clusters that are managed by earlier XMS
versions, refer to the appropriate XtremIO product documents which are provided for
these versions.
Purpose
This document provides the required information for using the EMC XtremIO Storage Array.
Audience
This document is intended for the Dell host storage administrator, system administrator,
or operator who will be involved in managing the XtremIO Storage Array.
Related Documentation
The following Dell EMC publications provide additional information:
XtremIO Storage Array Host Configuration Guide
XtremIO Storage Array Site Preparations Guide for X2 Cluster Type
XtremIO Storage Array Site preparations Guide for X1 Cluster Type
XtremIO Storage Array Security Configuration Guide
XtremIO Storage Array User Guide
XtremIO Storage Array RESTful API Guide
XtremIO Storage Array XIOS Release Notes
XtremIO Storage Array XMS Release Notes
Preface 5
Preface
Introduction 7
Introduction
Note: In Storage Controllers running XIOS version 4.0.25-22 (or later) and in XMS running
version 4.2.2-18 (or later) the sshd configuration was enhanced to disable weak ciphers
for SSL connectivity. This was done to enhance security and resolve some vulnerabilities
that occurred when this algorithm was used. Due to this change, some older versions of
the PuTTY SSH client and WinSCP SFTP client may cause an error when accessing or
transferring files to or from the XMS. For further details, refer to Dell EMC KB# 504645
(https://support.emc.com/kb/504645).
To avoid such errors, make sure that WinSCP and PuTTY (or any SSH client and SFTP client
used) are updated to the most recent version to enable accessing and transferring files to
or from the XMS.
Note: The CLI access via SSH requires two sets of credentials. The first set is generic to any
user. The second set is user-specific according to the user assigned to you by the System
or Storage Administrator.
Using Filters
All show commands, i.e. commands that provide information about the system (rather
than manipulate it) support the option to filter the displayed results of the command. Any
object property can be selected as a filter.
If you want to use multiple filters, separate them with a logical AND or a logical OR, using
ampersand (&) and comma, respectively. The filter implements all AND rules first and then
all OR rules on the received results.
The filters are based on a logical statement as described in the following table.
Numeric • eq - equal
• ne - not equal
• ge - greater equal
• gt - greater than
• lt - less than
• le - less equal
Filter syntax:
Filter=property1:OPERATOR:value&property2:OPERATOR:value
Filter example:
show-volumes filter=Vol-Size:gt:1T&vol-name:like:ProdTime
For the usage of filters, see “help-filters” on page 30.
Some of the "show" type commands enables using the vertical input parameter, which
displays the command output as a list, as shown in the following example:
Completion Codes
The following table contains a list of general completion codes that can be returned by any
command.
unauthorized_command The user account which issued this command does not have the
required authorization level.
invalid_input Invalid values were entered with the command. For example, a
string was entered for a property that requires an IP address.
no_sys_response_retrying The management server lost communication with the cluster after a
command was issued and it is not known if the command
completed successfully.
This error should clear once communication with the cluster has
been restored.
uncertain_object_error The current state of the component for which this command was
issued is not known.
An uncertainty_error completion code has already been issued for
this component.
If this completion code appears, some XMCLI commands display
"pending" under the certainty-state field. If this persists, contact
XtremIO.
invalid_in_cur_sys_state The command is invalid because of the current Cluster State. For
example, a stop-cluster command was issued and the cluster is
already stopped.
Introduction
This chapter lists all admin-level CLI commands.
For each command, the following information is provided:
Command name
Command description
Command usage syntax
Input and output parameters details
Command usage example
add-remote-protection-volume-pair Pairs a source and target Volumes and adds them 244
to the Remote Protection Session.
refresh-xms-ssh-key Generates a new unique SSH key on the XMS and 117
updates all related clusters accordingly.
show-slots Displays the list of all DAE(s) SSD slots and their 65
properties.
show-snapshot-sets Displays the list of Snapshot Sets and their data. 168
General
exit
The exit admin-level command closes the CLI terminal.
Displayed data is removed upon exiting the CLI terminal and does not appear when the
terminal is reopened.
Usage:
exit
help
The help admin-level command displays the list of all available CLI commands, or
provides full usage information of a specified command.
Using the help command followed by a string or a partial string displays all available CLI
command names that contain that string.
Usage:
help
help dae
help-filters
The help-filters admin-level command displays the list of all available CLI
commands output filters and syntax examples.
Usage:
help-filters
For information and usage examples of available output filters, see “Using Filters” on
page 11.
quit
The quit admin-level command closes the CLI terminal.
Displayed data is removed upon exiting the CLI terminal and does not appear when the
terminal is reopened.
Usage:
quit
rename
The rename admin-level command renames a component of the XtremIO Storage Array.
Usage:
rename ( new-caption=<string> | new-name=<string> ) (
tar-id=<name or index> | vol-id=<name or index> | ig-id=<name
or index> | initiator-id=<name or index> | usr-id=<name or
index> | cg-id=<name or index> | xms-id=<name or index> |
volume-snapshot-group-id=<name or index> | tg-id=<name or
index> | tag-id=<name or index> | snapshot-set-id=<name or
index> | cluster-id=<name or index> | scheduler-id=<name or
index> )
NOTE! At least one property from the following list is
mandatory: new-name, new-caption.
NOTE! At least one property from the following list is
mandatory: xms-id, cluster-id, tar-id, vol-id, ig-id,
initiator-id, usr-id, volume-snapshot-group-id, cg-id, tg-id,
tag-id, snapshot-set-id, scheduler-id.
NOTE! All object IDs should be renamed using the new-name
parameter, except tags which should be renamed using the
new-caption parameter.
General 31
Admin CLI Commands
IMPORTANT
For renaming tag-id use the new-caption parameter. For all other objects, use the
new-name parameter.
Example:
rename vol-id="voltest" new-name="voltest1"
Maintenance
General
add-cluster
The add-cluster admin-level command adds a Cluster to the list of Clusters managed
by the XMS.
Usage:
add-cluster sc-mgr-host=<Host name> [ force ]
Example:
add-cluster sc-mgr-host="1.2.3.4"
remove-cluster
The remove-cluster admin-level command removes a Cluster from the list of Clusters
managed by the XMS.
Usage:
remove-cluster cluster-id=<id: name or index>
cluster-psnt=<cluster PSNT>
NOTE! When providing the cluster index as the cluster-id
parameter, it is required to provide the xms-name parameter as
well; alternatively, it is possible to provide the cluster name
as cluster-id.
Example:
remove-cluster cluster-id="My_Cluster"
cluster-psnt="XIO###########"
show-clusters
The show-clusters admin-level command displays the main properties and the status
of clusters managed by the XMS.
Usage:
show-clusters [cluster-id=<id: name or index> ]
[duration=<number of seconds>] [cluster-id=<cluser ID>]
[frequency=<number of seconds>] [vertical] [ filter ]
Maintenance 33
Admin CLI Commands
Example:
show-clusters vertical
Vol-Size The total amount of disk space defined for all Volumes in the
cluster
Logical-Space-In-Use The total logical address space written to the cluster before
deduplication
Size-and-Capacity The number of X-Bricks and the cluster’s capacity of the cluster
show-clusters-upgrade
The show-clusters-upgrade admin-level command displays clusters’ NDU status.
Usage:
show-clusters-upgrade [ duration=<seconds> ] [ cluster-id=<id:
name or index> ] [ frequency=<seconds> ] [ filter=<> ]
Example:
show-clusters-upgrade
Activation-Time A time stamp indicating when the current software was activated
Upgrade-Failure-Reason Indicates whether the upgrade has failed and specify the failure
reason.
Maintenance 35
Admin CLI Commands
show-clusters-upgrade-progress
The show-clusters-upgrade-progress admin-level command displays indicators
of the clusters’ NDU progress.
Usage:
show-clusters-upgrade-progress [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter=<> ]
Example:
show-clusters-upgrade-progress
FRU Replacement
show-technician-port-tunnels
The show-technician-port-tunnels admin-level command shows the status of
the defined XMS technician port tunnels.
Usage:
show-technician-port-tunnels [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<List of property strings> ]
Example:
show-technician-port-tunnels
Maintenance 37
Admin CLI Commands
modify-technician-port-tunnel
The modify-technician-port-tunnel admin-level command creates or terminates
an XMS technician port tunnel to a specific Storage Controller.
Usage:
modify-technician-port-tunnel sc-id=<id: name or index> ( open
| close ) [ cluster-id=<id: name or index> ]
NOTE! Exactly one property from the following list is
mandatory: open, close.
Example:
modify-technician-port-tunnel sc-id="X1-SC1" open
add-ssd
The add-ssd admin-level command adds an SSD to the X-Brick and initializes it.
Usage:
add-ssd brick-id=<name or index> ssd-uid=<string> [
cluster-id=<id: name or index> ] [ is-foreign-xtremapp-ssd ] [
is-encrypted-unreadable-ssd ] [ ssd-name=<string> ]
Example:
add-ssd brick-id="X1" ssd-uid="wwn-0x5000000000000000"
is-foreign-xtremapp-ssd
Maintenance 39
Admin CLI Commands
show-ssds-diagnostic
The show-ssds-diagnostic admin-level command displays SSDs’ diagnostic
information.
Usage:
show-ssds-diagnostic [ duration=<seconds> ] [ cluster-id=<id:
name or index> ] [ frequency=<seconds> ] [ vertical ] [
filter=<> ] [ prop-list=<list of property strings> ]
Example:
show-ssds-diagnostic
Slot The X-Brick’s DAE slot number in which the SSD is inserted
Last-IO-Err-Type The error type of the last I/O (none, ssd_error or timeout)
activate-storage-controller
The activate-storage-controller admin-level command activates a replaced or
deactivated Storage Controller.
Usage:
activate-storage-controller sc-id=<name or index> [
cluster-id=<id: name or index> ]
Example:
activate-storage-controller sc-id="X1-SC1"
deactivate-storage-controller
The deactivate-storage-controller admin-level command deactivates an active
Storage Controller (e.g. for replacing purposes).
Note: Deactivating a Storage Controller will stop any processing done on the Storage
Controller and will impact system performance, as well as prevent host access to its target
ports.
Usage:
deactivate-storage-controller sc-id=<name or index> [
cluster-id=<id: name or index> ]
Example:
deactivate-storage-controller sc-id="X1-SC1"
Maintenance 41
Admin CLI Commands
show-nvrams
Example:
show-nvrams duration=60 frequency=10
show-bbus
The show-bbus admin-level command displays the Battery Backup Units information.
Usage:
show-bbus [ duration=<seconds> ] [ cluster-id=<id: name or
index> ] [ frequency=<seconds> ] [ filter=<> ] [
prop-list=<list of property strings> ] [ vertical ]
Maintenance 43
Admin CLI Commands
Example:
show-bbus cluster-id=1 vertical
Input Indicates whether there is an external power feed to the BBU (on or
off)
Battery-Charge (%) The percentage of the battery charge. If the BBU is unreachable or
disabled, this parameter is NULL.
Voltage The input voltage of the BBU. If the BBU is unreachable or disabled,
this parameter is NULL.
show-bricks
The show-bricks admin-level command displays a list of X-Bricks and their associated
cluster.
Usage:
show-bricks [ duration=<seconds> ] [ cluster-id=<id: name or
index> ] [ frequency=<seconds> ] [ filter=<> ] [
prop-list=<list of property strings> ]
Example:
show-bricks duration=60 frequency=10
Maintenance 45
Admin CLI Commands
control-led
The control-led admin-level command helps locating a specific hardware component
by turning on its identification LED.
Note: The Identification LEDs can be either Steady On/Off or Blinking On/Off depending
on the component they are on. Refer to the XtremIO Storage Array User Guide for the valid
values for each LED type.
Usage:
control-led entity=<'SSD', 'DAELCC', 'LocalDisk',
'StorageController', 'DAE'> led-mode=<off, blinking, on>
object-id-list=<list of ids: name or index> [ inverse-mode ] [
cluster-id=<id: name or index> ] [ brick-id=<name or index> ] [
slot-num-list=<list of integers> ]
Example:
control-led entity=SSD object-id=["wwn-0x5000000000000000"]
led-mode=blinking
power-on-dae-slots
Example:
power-on-dae-slots
Maintenance 47
Admin CLI Commands
power-off
The power-off admin-level command powers off a an entire cluster or a Storage
Controller.
Powering off a Storage Controller will prevent host access to its target ports. Powering off
the entire cluster will stop cluster services.
Usage:
power-off [ sc-id=<id: name or index> ] [ cluster-id=<id: name
or index> ] [ force ] [ shut-down-reason=<free text> ]
Example:
power-off sc-id="X1-SC1"
Unless otherwise requested by Dell EMC Global Tech Support, this command should not
be used to shut down the Cluster. For instructions on shutting down the cluster, refer to
the XtremIO Storage Array User Guide.
power-on
The power-on admin-level command powers up a Storage Controller.
Powering on a Storage Controller brings the Target ports back online.
Usage:
power-on sc-id=<id: name or index> [ cluster-id=<id: name or
index> ]
Example:
power-on sc-id="X1-SC1"
shutdown-xms
The shutdown-xms admin-level command stops the XMS service or shuts down the
machine.
Usage:
shutdown-xms [ shutdown-type=<service (default), machine> ]
Example:
shutdown-xms shutdown-type="machine"
start-cluster
The start-cluster admin-level command starts cluster services and allows a user to
access the storage array.
Usage:
start-cluster [ cluster-id=<id: name or index> ] [ force ]
Example:
start-cluster cluster-id=1
Maintenance 49
Admin CLI Commands
stop-cluster
The stop-cluster admin-level command stops cluster services.
Note: Stopping cluster services prevents all hosts from accessing the storage array.
Usage:
stop-cluster cluster-psnt=<PSNT> [ cluster-id=<id: name or
index> ] [ abort-start-attempt ] [ force ]
NOTE! The following property is mandatory: cluster-psnt
NOTE! Only one property from the following list is allowed:
force, abort-start-attempt
Example:
stop-cluster cluster-psnt="XIO###########"
Note: Do not use this command unless specifically instructed to do so by Dell EMC Global
Tech Support.
restart-xms
The restart-xms admin-level command restarts the XMS service.
Usage:
restart-xms [ restart-type=<service (default), machine> ]
Example:
restart-xms
Hardware Diagnostics
show-daes
The show-daes admin-level command displays the list of DAEs and their properties.
Usage:
show-daes [ duration=<seconds> ] [ cluster-id=<id: name or
index> ] [ frequency=<seconds> ] [ filter=<> ] [
prop-list=<List of property string> ]
Example:
show-daes
Maintenance 51
Admin CLI Commands
show-daes-controllers
The show-daes-controllers admin-level command displays the list of DAE
controllers (referred to as LCCs in X1 cluster type) and their properties.
Usage:
show-daes-controllers [ duration=<seconds> ] [ cluster-id=<id:
name or index> ] [ frequency=<seconds> ] [ vertical ] [
filter=<> ] [ prop-list=<list of property strings> ]
Example:
show-daes-controllers vertical
show-daes-row-controllers
Maintenance 53
Admin CLI Commands
Example:
show-daes-row-controllers vertical
Identify-Led The DAE Row Controller’s identify LED state (on or off)
Status-Beacon The DAE Row Controller’s status LED state (on or off)
show-daes-controllers-sas-ports
The show-daes-controllers-sas-ports admin-level command displays the DAE
Controllers (referred to as LCCs in X1 cluster type) SAS ports information.
Usage:
show-daes-controllers-sas-ports [ duration=<seconds> ] [
dae-id=<name or index> ] [ frequency=<seconds> ] [
cluster-id=<id: name or index> ] [ vertical ]
Example:
show-daes-controllers-sas-ports
Maintenance 55
Admin CLI Commands
show-daes-row-controllers-sas-ports
Example:
show-daes-row-controllers-sas-ports
show-daes-psus
The show-daes-psus admin-level command displays the list of DAE PSUs and their
properties.
Usage:
show-daes-psus [ duration=<seconds> ] [ cluster-id=<id: name or
index> ] [ frequency=<seconds> ] [ vertical ] [ filter=<> ] [
prop-list=<List of property strings> ]
Example:
show-daes-psus
Input Indicates whether there is input power to the supply (on or off).
Maintenance 57
Admin CLI Commands
show-daes-fans
The show-daes-fans admin-level command displays the list of DAE fans and their
properties.
Usage:
show-daes-fans [ duration=<seconds> ] [ cluster-id=<id: name or
index> ] [ frequency=<seconds> ] [ vertical ] [
jbod-index=<name or index> ]
-index
Example:
show-daes-fans jbod-index=1
show-infiniband-switches
The show-infiniband-switches admin-level command displays InfiniBand
Switches’ information.
Usage:
show-infiniband-switches [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
vertical ] [ filter=<> ] [ prop-list=<List of property string> ]
Example:
show-infiniband-switches
Maintenance 59
Admin CLI Commands
show-infiniband-switches-ports
The show-infiniband-switches-ports admin-level command displays InfiniBand
Switches’ port information.
Usage:
show-infiniband-switches-ports [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
vertical ] [ filter=<> ] [ prop-list=<List of property strings>
]
Example:
show-infiniband-switches-ports
Link-Rate-In Gbps Link rate in Giga bit per second (usually 40Gbps)
Maintenance 61
Admin CLI Commands
show-infiniband-switches-psus
The show-infiniband-switches-psus admin-level command displays InfiniBand
Switches’ PSUs information.
Usage:
show-infiniband-switches-psus [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
vertical ] [ filter=<> ] [ prop-list=<list of property strings>
]
Example:
show-infiniband-switches-psus
show-local-disks
The show-local-disks admin-level command displays the Storage Controllers’ local
disks information.
Usage:
show-local-disks [ duration=<seconds> ] [ cluster-id=<id: name
or index> ] [ frequency=<seconds> ] [ vertical ] [ filter=<> ] [
prop-list=<List of property strings> ]
Example:
show-local-disks
UID Unique ID
Disk-Expected-Type The disk type the cluster expects to have for the drive (SSD or
HDD)
Maintenance 63
Admin CLI Commands
show-leds
The show-leds admin-level command displays the values for the identification and
status LEDs.
Usage:
show-leds [ duration=<seconds> ] [ cluster-id=<id: name or
index> ] [ frequency=<seconds> ]
Example:
show-leds
show-slots
The show-slots admin-level command displays the list of all DAE(s) SSD slots and their
properties.
Usage:
show-slots [ duration=<seconds> ] [ cluster-id=<id: name or
index> ] [ frequency=<seconds> ] [ filter=<> ] [
prop-list=<List of property strings> ]
Example:
show-slots
UID The unique identifier (WWN) of the disk inserted in the slot
Maintenance 65
Admin CLI Commands
show-ssds
The show-ssds admin-level command displays a list of DAE SSDs and their properties.
Usage:
show-ssds [ brick-id=<id: name or index> ][ duration=<seconds>
] [ cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
vertical ] [ filter=<> ] [ prop-list=<List of property strings>
]
Example:
show-ssds
Slot # The X-Brick’s DAE slot number in which the SSD is inserted
DPG-Name The name of the XDP group to which the SSD is associated
show-ssd
The show-ssd admin-level command displays the properties of a single DAE SSD.
Usage:
show-ssd ssd-id=<name or index> [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<list of property strings> ]
Maintenance 67
Admin CLI Commands
Example:
show-ssd ssd-id="wwn-0x5000cca04e05faa0"
Slot # The X-Brick’s DAE slot number in which the SSD is inserted
DPG-Name The name of the XDP group to which the SSD is associated
show-storage-controllers
The show-storage-controllers admin-level command displays a list of Storage
Controllers and their properties.
Usage:
show-storage-controllers [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
vertical ]
Example:
show-storage-controllers
Cluster-Name The name of the cluster to which the Storage Controller belongs
Maintenance 69
Admin CLI Commands
Stop-Reason The reason for the Storage Controller’s stop (if any)
show-storage-controllers-fw-versions
The show-storage-controllers-fw-versions admin-level command displays
the Storage Controllers’ firmware version information.
Usage:
show-storage-controllers-fw-versions [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<List of property strings> ]
Example:
show-storage-controllers-fw-versions
show-storage-controllers-infiniband-ports
The show-storage-controllers-infiniband-ports admin-level command
displays the Storage Controllers’ InfiniBand port information.
Usage:
show-storage-controllers-infiniband-ports [ duration=<seconds>
] [ cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
vertical ] [ filter=<> ] [ prop-list=<list of property strings>
]
Example:
show-storage-controllers-infiniband-ports
Maintenance 71
Admin CLI Commands
show-storage-controllers-info
The show-storage-controllers-info admin-level command displays the Storage
Controllers’ information.
Usage:
show-storage-controllers-info [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
vertical ] [ filter=<> ] [ prop-list=<list of property strings>
]
Example:
show-storage-controllers-info
Cluster-Name The name of the cluster to which the Storage Controller belongs
show-storage-controllers-psus
The show-storage-controllers-psus admin-level command displays a list of the
Storage Controller’s PSUs and their properties.
Usage:
show-storage-controllers-psus [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
vertical ] [ filter=<> ] [ prop-list=<list of property strings>
]
Maintenance 73
Admin CLI Commands
Example:
show-storage-controllers-psus
Input Indicates whether there is input power to the supply (on or off).
show-storage-controllers-sas-ports
The show-storage-controllers-sas-ports admin-level command displays the
Storage Controllers’ SAS ports information.
Usage:
show-storage-controllers-sas-ports [ duration=<seconds> ] [
sc-id=<id: name or index> ] [ cluster-id=<id: name or index> ] [
frequency=<seconds> ] [filter=<> ] [ prop-list=<list of
property strings> ]
Example:
show-storage-controllers-sas-ports
Maintenance 75
Admin CLI Commands
show-storage-controllers-sensors
The show-storage-controllers-sensors admin-level command displays a list of
Storage Controllers sensors and their properties.
Usage:
show-storage-controllers-sensors [ sensor-type=<'temperature',
'power_unit', 'current', 'fan', 'voltage', 'processor',
'power_supply'> ] [ sc-id=<id: name or index> ] [
cluster-id=<id: name or index> ] [ faulty-only ] [
frequency=<seconds> ] [ duration=<seconds> ] [ filter ]
Example:
show-storage-controllers-sensors
show-target-sfp
The show-target-sfp admin-level command displays monitoring data and warning
thresholds of an SFP that is plugged in a specified Target port.
Usage:
show-target-sfp tar-id=<name or index> [ cluster-id=<name or
index> ]
Example:
show-target-sfp tar-id="X1-SC1-iscsi1"
Maintenance 77
Admin CLI Commands
show-targets-sfps
The show-targets-sfps admin-level command displays monitoring data of SFPs that
are plugged-in target ports.
Usage:
show-targets-sfps [ filter=<> ]
Example:
show-targets-sfps sc-id="X1-SC1"
Maintenance 79
Admin CLI Commands
Troubleshooting
Test connectivity
show-discovered-initiators-connectivity
The show-discovered-initiators-connectivity admin-level command
displays a list of Initiator ports discovered by the Storage Controllers.
Usage:
show-discovered-initiators-connectivity [ target-details ] [
cluster-id=<id: name or index> ] [iscsi-portal-details=<true,
false> ]
Example:
show-discovered-initiators-connectivity
show-initiators-connectivity
The show-initiators-connectivity admin-level command displays a list of
configured Initiator ports and the number of available paths.
Usage:
show-initiators-connectivity [ target-details ] [
cluster-id=<id: name or index> ]
Example:
show-initiators-connectivity
Troubleshooting 81
Admin CLI Commands
test-ip-connectivity
The test-ip-connectivity admin-level command verifies the connectivity between
a Storage Controller and a specified IP address.
Usage:
test-ip-connectivity sc-id=<name or index> ip-addr=<IP Address>
interface=<ISCSI1, ISCSI2, ISCSI3, ISCSI4 or sc_management> [
cluster-id=<name or index> ]
NOTE! The following properties are mandatory: interface,
ip-addr, sc-id
Example:
test-ip-connectivity interface=ISCSI1 ip-addr="10.0.0.1"
sc-id="X1-SC1"
test-ip-connectivity-netcat
The test-ip-connectivity-netcat admin-level command verifies the connectivity
between a source IP address and a specified destination IP address and TCP/UDP port.
Usage:
test-ip-connectivity-netcat src-host-ip=<IP address>
dst-host-ip=<IP address> dest-port-number=<Integer> [
connection-type=<TCP, UDP> ] [ cluster-id=<name or index> ]
NOTE! The following properties are mandatory: src-host-ip,
dst-host-ip, dest-port-number
Example:
test-ip-connectivity-netcat src-host-ip="10.10.10.1"
dst-host-ip="1.2.3.4" dest-port-number=12
test-ip-connectivity-ping
The test-ip-connectivity-ping admin-level command verifies ping connectivity
between a source IP address and a destination IP address.
Usage:
test-ip-connectivity-ping src-host-ip=<IP address>
dst-host-ip=<IP address> [ ping-size=<Integer> ] [
df-flag=<True, False> ] [ cluster-id=<name or index> ]
NOTE! The following properties are mandatory: src-host-ip,
dst-host-ip
Example:
test-ip-connectivity-ping src-host-ip="10.10.10.1"
dst-host-ip="1.2.3.4"
Troubleshooting 83
Admin CLI Commands
test-xms-storage-controller-connectivity
The test-xms-storage-controller-connectivity admin-level command
verifies the connectivity between the XMS and a Storage Controller.
Usage:
test-xms-storage-controller-connectivity sc-id=<name or index>
[ cluster-id=<name or index> ] [ packet-size=<positive integer>
]
Example:
test-xms-storage-controller-connectivity sc-id="X1-SC1"
Log Bundle
create-debug-info
The create-debug-info admin-level command creates a log bundle.
Usage:
create-debug-info [ sc-mgr-host=<Host name> ] [ cluster-id=<id:
name or index> ] [ with-perf-data ] [ with-vmcore ] [ force ] [
debug-info-name=<string> ] [ datetime=<date-time string> ] [
debug-level=<small, medium (default)> ]
Example:
create-debug-info
remove-debug-info
The remove-debug-info admin-level command deletes an existing log bundle.
Usage:
remove-debug-info debug-info-id=<name or index>
Example:
remove-debug-info debug-info-id=1
Troubleshooting 85
Admin CLI Commands
show-debug-info
The show-debug-info admin-level command lists the log bundles that were created on
the XMS.
Usage:
show-debug-info [ duration=<seconds> ] [ frequency=<seconds> ]
Example:
show-debug-info
Cluster-Name The name of the cluster to which the Storage Controller belongs
Health Check
run-health-check-assessment
The run-health-check-assessment admin-level command, runs a Health Check
Script on the cluster.
Usage:
run-health-check-assessment [ cluster-id=<id: Name or Index> ]
[ tech-password=<String> ]
Example:
run-health-check-assessment cluster-id=1
show-debug-info
Cluster-Name The name of the cluster to which the Storage Controller belongs
Troubleshooting 87
Admin CLI Commands
Administration
User management
add-user-account
The add-user-account admin-level command creates a new user account to XMS.
Usage:
add-user-account usr-name=<string> role=<'read_only', 'admin',
'configuration', 'technician'> ( password=<string> |
public-key=<public key> ) [ inactivity-timeout=<integer> ]
NOTE! Only one property from the following list must be
selected: password, public-key.
Example:
add-user-account role=configuration usr-name="New_User"
password="p@ssw0rd"
modify-user-account
The modify-user-account admin-level command modifies an XMS user account’s
parameters.
Usage:
modify-user-account usr-id=<name or index> ( password=<string>
| public-key=<public key> | usr-name=<string> |
role=<'read_only', 'admin', 'configuration', 'technician'> |
inactivity-timeout=<integer> )
NOTE! At least one property from the following list is
mandatory: password, public-key, role, usr-name,
inactivity-timeout.
IMPORTANT
The following parameter group is exclusive (you can select only one parameter from the
group): [password, public-key]
Example:
modify-user-account usr-id="Existing_User" role=administrator
Administration 89
Admin CLI Commands
remove-user-account
The remove-user-account admin-level command removes an XMS user account.
If the account is currently active (i.e. a command is in progress), account removal may fail.
Only users with administrative roles can remove other user accounts. Users cannot
remove their own accounts.
Usage:
remove-user-account usr-id=<name or index>
Example:
remove-user-account usr-id="user1"
show-user-accounts
The show-user-accounts admin-level command displays the XMS user account
information.
Usage:
show-user-accounts [ duration=<seconds> ] [ frequency=<seconds>
]
Example:
show-user-accounts duration=300 frequency=10
Inactivity-Timeout The number of minutes with no activity after which the user needs
to re-login
modify-password
The modify-password admin-level command modifies the XMS user account’s
password. If the usr-id parameter is not provided, then the current XMS user account’s
password is modified.
Usage:
modify-password [ password=<string> ] [ usr-id=<name or index>
]
Example:
modify-password usr-id="admin" password="123456"
add-ldap-config
The add-ldap-config admin-level command adds a new LDAP configuration profile to
the LDAP configuration table.
Usage:
add-ldap-config
server-urls=<["ldap://ad.example.com","ldaps://ad.example.com:3
001"]>
roles=<["admin:CN=SuperUsers,DC=example,DC=com","read_only:CN=U
sers,DC=example,DC=com"]>
search-filter=<(sAMAccountName={username})> [
binddn=<CN=<value>,OU=<value>,DC=<value>,DC=<value>> ] [
bindpw=<password> ] [ timeout=<(default: 1500)> ] [
search-base=<OU=<value>,DC=<value>,DC=<value>> ] [
user-to-dn-rule=<{username}@example.com> ] [
cache-expire-hours=<Credentials cache expiration (default: 24
hours)> ] [ ca-cert-data=<string> ]
Administration 91
Admin CLI Commands
Example:
add-ldap-config
server-urls=["ldap://ad.example.com","ldaps://ad.example.com:30
01"] search-filter="sAMAccountName={username}"
roles=["admin:CN=SuperUsers,DC=example,DC=com","read_only:CN=Us
ers,DC=example,DC=com"] binddn="CN=Test
User,OU=Users,DC=exmaple,DC=com"
[search-base="OU=support,DC=help,DC=com"
user-to-dn-rule="{username}@example.com"
remove-ldap-config
The remove-ldap-config admin-level command removes an LDAP configuration
profile from the LDAP configuration table.
Usage:
remove-ldap-config ldap-config-id=<index>
Example:
remove-ldap-config ldap-config-id=1
modify-ldap-config
The modify-ldap-config admin-level command modifies an LDAP configuration
profile.
Usage:
modify-ldap-config ldap-config-id=<index> (
binddn=<CN=<value>,OU=<value>,DC=<value>,DC=<value>> |
server-urls=<["ldap://ad.example.com","ldaps://ad.example.com:3
001"]> | user-to-dn-rule=<{username}@example.com> |
cache-expire-hours=<Credentials cache expiration (default: 24
hours)> |
roles=<["admin:CN=SuperUsers,DC=example,DC=com","read_only:CN=U
sers,DC=example,DC=com"]> | ca-cert-data=<string> |
search-base=<OU=<value>,DC=<value>,DC=<value>> |
search-filter=<(sAMAccountName={username})> | bindpw=<password>
| timeout=<(default: 1500)> )
NOTE! At least one property from the following list is
mandatory: binddn, server-urls, user-to-dn-rule,
cache-expire-hours, roles, ca-cert-data, search-base,
search-filter, bindpw, timeout.
Administration 93
Admin CLI Commands
Example:
modify-ldap-config ldap-config-id=1
binddn="CN=alexs,DC=app-lab,DC=xtremio,DC=com"
search-base="OU=guiadmin,DC=app-lab,DC=xtremio,DC=com"
search-filter="userPrincipalName={username}"
roles=["configuration:CN=XtremIOread,OU=guiadmin,DC=app-lab,DC=
xtremio,DC=com"] server-urls=["ldap://10.82.36.84"]
show-ldap-configs
The show-ldap-configs admin-level command lists the LDAP server configurations
and their parameters.
Usage:
show-ldap-configs [ duration=<seconds> ] [ frequency=<seconds>
]
Example:
show-ldap-configs
Search-Base The starting point for the search in the directory tree. Comprises of
multiple objects separated by commas, including:
• cn: common name
• ou: organizational unit
• o: organization
• c: country
Role-Mapping The list of XMS roles (Active Directory group mapping roles)
Credentials-Expiration The time in hours (1 to 24) before the cached user authentication
expires and re-authentication is required
CA-Cert-File Certificate file for server validation (when LDAPS protocol is used)
modify-dns-servers
The modify-dns-servers admin-level command sets or modifies the IP address of
the primary and/or secondary DNS server.
Usage:
modify-dns-servers ( primary=<IP Address> | secondary=<IP
Address> )
NOTE! At least one property from the following list is
mandatory: primary, secondary.
Example:
modify-dns-server primary="1.2.3.4"
show-dns-servers
The show-dns-servers admin-level command displays the IP addresses of the
primary and secondary DNS servers (if configured).
Usage:
show-dns-servers
Example:
show-dns-servers
Administration 95
Admin CLI Commands
show-remote-servers-status
The show-remote-servers-status admin-level command displays a list of all
external servers (NTP, DNS, primary gateway and, if configured, secondary gateway), their
IP addresses and connectivity information.
Usage:
show-remote-servers-status
Example:
show-remote-servers-status
Certificate Management
create-server-certificate-signing-request
The create-server-certificate-signing-request admin-level command
instructs the server to generate a public-private key pair and a certificate signing request
(CSR) that can be sent to a third party certification authority (CA) for signing.
Usage:
create-server-certificate-signing-request [
cert-alt-name=<alternative name e.g. IP=1.2.3.4
DNS.1=server.example.com DNS.2=1.2.3.4> ] [ cert-state=<string>
] [ cert-org-name=<string> ] [ cert-email=<Email address> ] [
cert-ip=<IP address> ] [ cert-common-name=<domain name, e.g.
xms.example.com> ] [ server-key-size=<integer between 2048 and
4096> ] [ cert-locality=<string> ] [
cert-org-unit-name=<string> ] [ server-key-string=<string> ] [
cert-country=<Two-letter ISO_3166-1 country code, e.g. US> ]
Example:
create-server-certificate-signing-request
Administration 97
Admin CLI Commands
install-self-signed-server-certificate
The install-self-signed-server-certificate admin-level command installs
the new self-signed certificate.
Usage:
install-self-signed-server-certificate [cert-ip=<IP address>
|cert-common-name=<domain name, e.g. xms.example.com> ]
[cert-alt-name<subject alternative name, e.g. IP=1.2.3.4
DNS.1=server.exmaple.com DNS.2=1.2.3.4> ]
[server-certificate-signing-request-string=<string> ] [
server-key-string=<string> ]
example:
install-self-signed-server-certificate
cert-common-name="xms.example.com"
show-server-certificate
The show-server-certificate admin-level command displays the currently loaded
certificate.
Usage:
show-server-certificate
example:
show-server-certificate
show-server-certificate-signing-request
The show-server-certificate-signing-request admin-level command
displays the certificate signing request.
Usage:
show-server-certificate-signing-request
example:
show-server-certificate-signing-request
modify-server-certificate
The modify-server-certificate admin-level command initiates loading of a
signed certificate and a key. It is possible to load a signed certificate, matching the current
CSR or a signed certificate paired with a private key.
Usage:
modify-server-certificate server-certificate-string=<string> [
chain-certificate-string=<string> ] [
server-key-string=<string> ]
Administration 99
Admin CLI Commands
modify-clusters-parameters
The modify-clusters-parameters admin-level command modifies the following
cluster parameters:
SNMP Heartbeat
SSH timeout while copying logs
ESX device connectivity mode
Obfuscated Log Bundle
ODX Mode
Performance Data Collection mode
Replication TCP Port
Installation type
Usage:
modify-clusters-parameters [ ( enable-heartbeat |
disable-heartbeat ) | iscsi-tcp-port=<integer> |
odx-mode=<enabled, disabled> | obfuscate-debug=<enabled,
disabled> | debug-create-timeout=<normal, high, none> |
replication-tcp-port=<integer> |
esx-device-connectivity-mode=<apd, pdl> |
performance-data-collection=<enabled, disabled> |
installation-type=<standard_installation_rpq ] [
installation-type=<standard_installation, rpq> ]
[installation_type-details=<string> ] [ entity=<Volume> ] [
cluster-id=<name or index> ]
NOTE! At least one property from the following list is
mandatory: iscsi-tcp-port, odx-mode, replication-tcp-port,
obfuscate-debug, debug-create-timeout,
esx-device-connectivity-mode, disable-heartbeat,
enable-heartbeat, performance-data-collection,
installation-type
NOTE! Only one property from the following list is allowed:
enable-heartbeat, disable-heartbeat
NOTE! When enabling performance-data-collection, the entity
property is mandatory.
debug-create-timeout Debug info creation ’high’, ’none’, ’normal’ At least one of the
timeout following parameters
must be selected:
esx-device-connectivit Device connectivity ’apd’ (currently this • debug-create-timeou
y-mode mode value cannot be t
modified)
• esx-device-connectivi
disable-heartbeat Disables SNMP N/A ty-mode
Heartbeat. • disable-heartbeat
• enable-heartbeat
enable-heartbeat Enables SNMP N/A • iscsi-tcp-port
Heartbeat.
• obfuscate-debug
iscsi-tcp-port iSCSI TCP Port Integer • odx-mode
• performance-data-col
obfuscate-debug Obfuscates debug enabled, disabled lection
info. • replication-tcp-port
odx-mode ODX mode enabled, disabled • installation-type
Example:
modify-clusters-parameters cluster-id="My_Cluster"
odx-mode=enabled obfuscate-debug=enabled
Administration 101
Admin CLI Commands
modify-cluster-thresholds
The modify-cluster-thresholds admin-level modifies the properties for thin
provisioning soft limits for connected clusters.
Usage:
modify-cluster-thresholds vaai-tp-limit=<range 0-100> [
cluster-id=<name or index> ]
Example:
modify-cluster-thresholds vaai-tp-limit=89
show-clusters-data-protection-properties
The show-clusters-data-protection-properties admin-level command
displays clusters’ data protection properties.
Usage:
show-clusters-data-protection-properties [cluster-id=<id: name
or index> ] [ duration=<seconds> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<list of property strings> ]
Example:
show-clusters-data-protection-properties
Min-SSDs-Per-Healthy-DPG The minimum number of active SSDs for a healthy state Data
Protection Group
Max-SSDs-Per-DPG The maximum number of SSDs allowed per Data Protection Group
show-clusters-info
The show-clusters-info admin-level command displays additional information,
which is not displayed in the show-clusters command, about configured clusters.
Usage:
show-clusters-info [cluster-id=<id: name or index> ] [
duration=<seconds> ] [ frequency=<seconds> ] [ vertical ] [
filter ]
Administration 103
Admin CLI Commands
Example:
show-clusters-info vertical duration=300 frequency=10
Activation-Time Time stamp of cluster activation in DATE & TIME format, e.g. Tue
Oct 8 11:12:42 2013
Start-Time Time stamp of cluster start in DATE &TIME format (e.g. Tue Oct 8
11:12:42 2013)
PSNT The cluster’s Product Serial Number Tag (assigned by Dell EMC)
show-clusters-parameters
The show-clusters-parameters admin-level command displays configured clusters
parameters.
Usage:
show-clusters-parameters [cluster-id=<id: name or index> ] [
duration=<seconds> ] [ frequency=<seconds> ] [ filter=<> ] [
prop-list=<list of property strings> ]
Example:
show-clusters-parameters
iSCSI-TCP--Port The cluster’s iSCSI listen TCP port number (default 3260)
Replication-TCP-Port The cluster’s replication TCP port number (default value is 1758)
ESX-Device-Connectivity-Mode Indicates the connectivity mode (currently, the mode is APD and
cannot be modified).
Administration 105
Admin CLI Commands
show-clusters-savings
The show-clusters-savings admin-level command displays a list of data-reduction
related values per cluster.
Usage:
show-clusters-savings [cluster-id=<id: name or index> ] [
duration=<seconds> ] [ frequency=<seconds> ] [ filter=<> ] [
prop-list=<List of property strings> ]
Example:
show-clusters-savings
Data-Reduction-Ratio The cluster’s data reduction ratio (calculated using the data
deduplication and data compression)
Thin-Provisioning-Ratio The cluster’s thin provisioning ratio (used disk space compared to
allocated disk space)
Compression-Factor The cluster’s compression factor (calculated using the unique data
on the SSD compared to the physical capacity used)
show-memory-usage
The show-memory-usage admin-level command shows the current memory usage
parameters.
Usage:
show-memory-usage [cluster-id=<id: name or index> ] [
duration=<seconds> ] [ frequency=<seconds> ] [ filter=<> ] [
prop-list=<list of property strings> ]
Example:
show-memory-usage
Administration 107
Admin CLI Commands
show-clusters-thresholds
The show-clusters-thresholds admin-level command displays thin provisioning
soft limits for the connected clusters.
Usage:
show-clusters-thresholds [cluster-id=<id: name or index> ] [
duration=<seconds> ] [ frequency=<seconds> ] [ filter=<> ] [
prop-list=<list of property strings> ]
Example:
show-clusters-thresholds
set-context
The set-context admin-level command sets a cluster context in a multiple cluster
environment and renders the need to specify the cluster ID.
Usage:
set-context ( all | cluster-id=<id: name or index> )
NOTE! At lease one property from the following list is
mandatory: all, cluster-id
NOTE! Only one property from the following list is allowed: all,
cluster-id.
Example:
set-context all
modify-ssh-firewall
The modify-ssh-firewall command admin-level modifies the lock mode of the SSH
firewall.
Usage:
modify-ssh-firewall ssh-firewall-mode=<'locked', 'unlocked'> [
cluster-id=<name or index> ]
Example:
modify-ssh-firewall ssh-firewall-mode=locked
Administration 109
Admin CLI Commands
show-xenvs
The show-xenvs admin-level command displays the list of Storage Controller
X-Environments, their state and CPU utilization.
Usage:
show-xenvs [ duration=<seconds> ] [ cluster-id=<id: name or
index> ] [ frequency=<seconds> ] [ filter=<> ] [
prop-list=<list of property strings> ]
Example:
show-xenvs cluster-id=1
show-cluster-dae-temperature-thresholds
Example:
show-cluster-dae-temperature-thresholds
Administration 111
Admin CLI Commands
modify-cluster-dae-temperature-thresholds
Example:
modify-cluster-dae-temperature-thresholds
dae-temperature-clear-hysteresis=2 monitor-mode=enabled
show-cluster-ssd-temperature-thresholds
Example:
show-clusters-ssd-temperature-thresholds
Administration 113
Admin CLI Commands
show-xms
The show-xms admin-level command displays the XMS machine’s parameters.
Usage:
show-xms [ duration=<seconds> ] [ frequency=<seconds> ]
Example:
show-xms duration=300 frequency=10
Min-TLS-Version The minimal TLS version supported by the XMS (1.0 (default),
1.1 or 1.2)
show-xms-info
The show-xms-info admin-level command displays information on server statistics,
disk usage and Ethernet interfaces.
Usage:
show-xms-info [ duration=<seconds> ] [ frequency=<seconds> ]
Example:
show-xms-info duration=300 frequency=10
Administration 115
Admin CLI Commands
IP Interface IP address
show-xms-parameters
The show-xms-parameters admin-level command displays the XMS’s parameters.
Usage:
show-xms-parameters [ duration=<seconds> ] [
frequency=<seconds> ]
Example:
show-xms-parameters duration=300 frequency=10
show-xms-esrsve-registration
The show-xms-esrsve-registration admin-level command displays registration
status of clusters to primary/secondary ESRS-VE gateways.
Usage:
show-xms-esrsve-registartion [ duration=<seconds> ] [
frequency=<seconds> ] [ cluster-id=<id: name or index> ]
Example:
show-xms-esrsve-registration duration=300 frequency=10
refresh-xms-ssh-key
The refresh-xms-ssh-key admin-level command generates a new unique SSH key
on the XMS and updates all related clusters accordingly.
Usage:
refresh-xms-ssh-key
Example:
refresh-xms-ssh-key
Administration 117
Admin CLI Commands
show-exported-configurations
The show-exported-configurations admin-level command displays a list of the
available XMS/cluster configuration backups.
Usage:
show-exported-configurations
Example:
show-exported-configurations
Example:
show-exported-configurations
Note: For details on how to copy an exported configuration file from an XMS to another
XMS, refer to the XtremIO Storage Array User Guide.
export-xms-cluster-configuration
The export-xms-cluster-configuration admin-level command exports a
backup file containing all XMS and cluster objects to a downloadable file.
Usage:
export-xms-cluster-configuration [ cluster-id=<name or index> ]
[ prefix=<string> ]
Example:
export-xms-cluster-configuration
import-xms-cluster-configuration
The import-xms-cluster-configuration admin-level command imports XMS
and cluster configuration from a configuration file.
Usage:
import-xms-cluster-configuration filename=<file name (string)>
[ ( all | objects-to-import=<UserAccount, Tag, InitiatorGroup,
Volume, ConsistencyGroup, Scheduler, Target, Initiator,
IscsiPortal, IscsiRoute, LdapConfig, LunMapping, SyrNotifier,
EmailNotifier, SnmpNotifier, SyslogNotifier, AlertDefinition,
DNS, Chap, NTP> ) ] [ cluster-id=<name or index> ] [
import-cluster-name ] [ snapshots ]
NOTE! Only one property from the following list must be
selected: all, objects-to-import.
Example:
import-xms-cluster-configuration filename="backup1"
objects-to-import=[Volume, InitiatorGroup, Initiator] snapshots
Administration 119
Admin CLI Commands
remove-exported-configuration
The remove-exported-configuration admin-level command removes an XMS and
cluster configuration file.
Usage:
remove-exported-configuration filename=<string>
Example:
remove-exported-configuration filename="backup1"
modify-xms-parameters
The modify-xms-parameters admin-level command modifies one or more of the
XMS’s parameters.
Usage:
modify-xms-parameters (
advisory-notifications-processing=<enabled,disabled> |
appsync-mode=<enabled, disabled> | cloud-iq-reporting=<true,
false> | default-user-inactivity-timeout=<integer> |
max-repeating-alert=<integer 10-100000> | min-tls-version=<e.g.
"1.0", "1.1", "1.2"> | xms-server-ldap-authentication=<enabled,
disabled> | debug-info-auto-collect=<enabled, disabled> )
NOTE! At least one property from the following list is
mandatory: default-user-inactivity-timeout,
max-repeating-alert, advisory-notifications-processing,
min-tls-version, appsync-mode, cloud-iq-reporting,
xms-server-ldap-authentication, debug-info-auto-collect.
Example:
modify-xms-parameters default-user-inactivity-timeout=30
max-repeating-alert=10
Administration 121
Admin CLI Commands
add-xms-secondary-ip-address
The add-xms-secondary-ip-address admin-level command adds a secondary XMS
IP address and default gateway.
Usage:
add-xms-secondary-ip-address ( xms-secondary-ip-and-sn=<string>
| xms-secondary-gw-addr=<string> )
Example:
add-xms-secondary-ip-address xms-secondary-gw-addr="10.10.10.1"
remove-xms-secondary-ip-address
The remove-xms-secondary-ip-address admin-level command removes a
secondary XMS IP address and default gateway.
Usage:
remove-xms-secondary-ip-address
Example:
remove-xms-secondary-ip-address
set-interactive-mode
The set-interactive-mode admin-level command sets interactive/non-interactive
mode for the XMS, to enable running CLI scripts.
Usage:
set-interactive-mode [ disable ]
Example:
set-interactive-mode
show-timezones
The show-timezones admin-level command displays the list of available timezones.
Usage:
show-timezones
Example:
show-timezones
show-datetime
The show-datetime admin-level command displays time-related information.
Usage:
show-datetime
Example:
show-datetime
Administration 123
Admin CLI Commands
modify-datetime
The modify-datetime admin-level command sets or modifies the cluster’s date and
time, timezone, or NTP server parameters.
Usage:
modify-datetime ( datetime=<date-time string> |
ntp-servers=<list of NTP servers> | timezone=<time zone> )
NOTE! At least one property from the following list is
mandatory: datetime, ntp-servers, timezone.
Example:
modify-datetime datetime="2016-01-01 10:00:00"
modify-login-banner
The modify-login-banner admin-level command modifies the login banner text.
Usage:
modify-login-banner banner=<ascii string>
Example:
modify-login-banner banner="New_Banner"
show-server-name
The show-server-name admin-level command displays the server name, according to
the name configuration mode, as follows:
Fixed mode - The server name is manually set by the user (using modify-server-name).
DNS mode - The server name is drawn from reverse DNS lookup (enabled, using
modify-server-name).
Dynamic mode - The server name is set according to the user’s URL request.
Usage:
show-server-name
Example:
show-server-name
modify-server-name
The modify-server-name admin-level command defines or modifies the XMS’s URL.
The user can also enable/disable reverse DNS lookup to retrieve the URL, based on the
XMS’s IP address.
Usage:
modify-server-name ( server-name=<e.g. xms.example.com> |
enable-reverse-dns | enable-user-url )
NOTE! At least one property from the following list is
mandatory: server-name, enable-reverse-dns, enable-user-url.
Example:
modify-server-name server-name="XMS.domain.com"
Administration 125
Admin CLI Commands
restore-xms-simulator-configuration
The restore-xms-simulator-configuration admin-level command restores
XMS and cluster objects from an exported configuration or a log bundle.
Usage:
restore-xms-simulator-configuration
Example:
restore-xms-simulator-configuration
XMS Notifiers
modify-email-notifier
The modify-email-notifier admin-level command modifies the Email notification
settings.
Usage:
modify-email-notifier [ ( add-recipient=<added recipient> |
remove-recipient=<removed recipient> | recipient-list=<list of
recipients> ) ] [ company-name=<company name> ] [
contact-details=<contact details> ] [ disable ] [ enable ] [
mail-password=<password for smtp mail relay> ] [
mail-relay-address=<IP or DNS for smtp mail relay> ] [
mail-user=<user for smtp mail relay> ] [
reset-configuration=<N\A> ] [ sender=<Sender> ]
NOTE! Only one property from the following list is allowed:
add-recipient, remove-recipient, recipient-list
Administration 127
Admin CLI Commands
Example:
modify-email-notifier
recipient-list=["[email protected]","[email protected]"]
transport=smtp mail-relay-address="smtp.domain.com"
mail-user="user" mail-password="123456" sender="[email protected]"
send-email-notification
The send-email-notification admin-level command verifies the Email notification
configuration by sending a test message containing a user-defined text.
Usage:
send-email-notification text
Example:
send-email-notification text="Test_Email"
show-email-notifier
The show-email-notifier admin-level command displays the Email notification
settings.
Usage:
show-email-notifier [ duration=<seconds> ] [
frequency=<seconds> ]
Example:
show-email-notifier
modify-snmp-notifier
The modify-snmp-notifier admin-level command modifies the SNMP notification
settings.
Usage:
modify-snmp-notifier [enable |disable ] [enable-heartbeat
|disable-heartbeat ] [ heartbeat-frequency=<minutes (5-1440)> ]
[ username=<string> ] [ remove-recipient=<Remove one recipient
from the list> ] [ community=<string> ] [ priv-key=<string> ] [
port=<port number> ] [ add-recipient=<Add one recipient to the
list> ] [ auth-key=<string> ] [ recipient-list=<list of
recipients> ] [ version=<v1, v2c or v3> ] [ auth-protocol=<md5,
sha, no_auth> ] [ priv-protocol=<des, aes128, no_priv> ]
Administration 129
Admin CLI Commands
IMPORTANT
The following groups are exclusive (you can select only one of the parameters in a group):
[enable, disable], [enable-heartbeat, disable-heartbeat], [add-recipient, remove-recipient,
recipient-list]
Example:
modify-snmp-notifier enable-heartbeat
add-recipient="host.example.com"
send-snmp-notification
The send-snmp-notification admin-level command verifies the SNMP notification
configuration by sending a test message, containing a user-defined text.
Usage:
send-snmp-notification text
Example:
send-snmp-notification text="SNMP notification"
show-snmp-notifier
The show-snmp-notifier admin-level command displays SNMP notification
configuration.
Usage:
show-snmp-notifier [ duration=<seconds> ] [ frequency=<seconds>
]
Example:
show-snmp-notifier
Administration 131
Admin CLI Commands
modify-syr-notifier
The modify-syr-notifier admin-level command modifies the ESRS (EMC Secure
Remote Support) notification parameters.
Usage:
modify-syr-notifier ( enable | disable |
reset-configuration=<N\A> | site-name=<name (can contain
spaces)> | frequency=<hours> | connection-type=<esrsvegw,
esrsgw, email> ) [ email-server=<Hostname or IP for mail
server> ] [ esrs-gw-host=<IP for ESRS Gateway> ] [
esrs-gw-host-secondary=<IP for ESRS Gateway> ] [
email-user=<Mail server username> ] [ email-password=<Email
server password> ] [ email-sender=<Sender name> ] [
username=<Windows NT user name> ] [ password=<PIN + RSA FOB> ]
NOTE! At least one property from the following list is
mandatory: site-name, connection-type, frequency, enable,
disable, reset-configuration.
Example:
modify-syr-notifier connection-type=esrsgw
send-syr-notification
The send-syr-notification admin-level command verifies the SYR notification
configuration by sending a test message, containing a user-defined text.
Usage:
send-syr-notification [ test-event ] [ cluster-id=<name or
index> ]
Example:
send-syr-notification
show-syr-notifier
The show-syr-notifier admin-level command displays the ESRS (EMC Secure
Remote Support) notification configuration.
Usage:
show-syr-notifier [ duration=<seconds> ] [ frequency=<seconds>
]
Example:
show-syr-notifier
Site Name Indicates the customer’s site where the cluster is installed.
PSNT The cluster’s Product Serial Number Tag (assigned by Dell EMC)
Administration 133
Admin CLI Commands
modify-syslog-notifier
The modify-syslog-notifier admin-level command adds or removes servers from
the Syslog server list. There can be up to 6 Syslog targets.
Usage:
modify-syslog-notifier ( enable | disable ) [
remove-target=<remove one target from the list> ] [
add-target=<add one target to the list> ] [ targets=<list of
syslog targets with optional port. required when enabling> ]
NOTE! At least one property from the following list must be
selected: disable, enable.
IMPORTANT
At least one parameter should be specified.
Example:
modify-syslog-notifier add-target="10.10.10.10"
show-syslog-notifier
The show-syslog-notifier admin-level command displays the Syslog server
notification status.
Usage:
show-syslog-notifier [ duration=<seconds> ] [
frequency=<seconds> ]
Example:
show-syslog-notifier
send-syslog-notification
The send-syslog-notification admin-level command checks the Syslog
notification configuration by sending a notification per the set configuration, containing
the supplied text.
Usage:
send-syslog-notification text
Example:
send-syslog-notification text="Syslog text"
Administration 135
Admin CLI Commands
IP Addresses
modify-ip-addresses
The modify-ip-addresses admin-level command modifies the XMS and/or Storage
Controllers’ management IP configuration.
Note: For the detailed procedure of changing IP configurations, refer to the XtremIO
Storage Array User Guide.
Usage:
modify-ip-addresses ( sc-ip-list=<[sc-id=value
sc-ip-sn="value",...]> | xms-ip-sn=<IP Address/Subnet> |
xms-gw-addr=<IP Address> | sc-gw-addr=<IP Address> ) [
cluster-id=<id: name or index> ]
NOTE! At least one property from the following list is
mandatory: xms-ip-sn, xms-gw-addr, sc-gw-addr, sc-ip-list.
Example:
modify-ip-addresses sc-gw-addr="10.10.10.1"
show-ip-addresses
The show-ip-addresses admin-level command displays the XMS and Storage
Controllers’ managment IP configuration.
Usage:
show-ip-addresses [ duration=<seconds> ] [ cluster-id=<id: name
or index> ] [ frequency=<seconds> ] [ filter=<> ] [
prop-list=<list of property strings> ]
Example:
show-ip-addresses
Administration 137
Admin CLI Commands
Provisioning
Tag Management
create-tag
The create-tag admin-level command creates a Tag for an entity.
Usage:
modify-tag tag-id=<name or index> caption=<string> [
xms-id=<name or index> ]
Example:
create-tag entity=Volume tag-name="New_Tag"
modify-tag
The modify-tag admin-level command modifies a specified Tag caption.
Usage:
modify-tag tag-id=<Tag ID> caption=<new caption> [xms-id=<XMS
ID>]
Example:
modify-tag tag-id="Old_Name" caption="New_Name"
remove-tag
The remove-tag admin-level command deletes a Tag from the tags list.
Usage:
remove-tag tag-id=<name or index>
Example:
remove-tag tag-id=13
show-tag
The show-tag admin-level command displays the details of the specified Tag.
Usage:
show-tag tag-id=<name or index> [ prop-list=<list of property
strings> ]
Example:
show-tag tag-id="My_Tag"
Object-List List of all objects assigned with the specified Tag (name and index)
Provisioning 139
Admin CLI Commands
show-tags
The show-tags admin-level command displays a list of Tags and their details.
Usage:
show-tags [ entity=<string> ] [ prop-list=<list of property
strings> ]
Example:
show-tags entity="Volume"
tag-object
The tag-object admin-level command tags the specified object.
Usage:
tag-object tag-id=<name or index> entity=<string>
entity-details=<name or index> [ cluster-id=<id: name or index>
]
Example:
tag-object entity=Volume entity-details="vol1"
tag-id="/Volume/myTag1"
Provisioning 141
Admin CLI Commands
untag-object
The untag-object admin-level command removes a Tag from the specified object.
Usage:
untag-object tag-id=<name or index> entity=<string>
entity-details=<name or index> [ cluster-id=<id: name or index>
]
Example:
untag-object entity=Volume entity-details="My_Vol"
tag-id="My_Tag"
add-volume
The add-volume admin-level command creates a new Volume.
Usage:
add-volume vol-name=<string> vol-size=<integer suffixed by
[kmgtp]> [ alignment-offset=<range 0-31> ] [
application-type=<Epic, Hyper-V VMs, Oracle DB, Other DB, SAP,
VDI, VMware VMs, Others> ] [ cluster-id=<name or index> ] [
lb-size=<512 or 4096> ] [ management-locked ] [
qos-enabled-mode=<enabled, disabled, monitor_only> ] [
qos-policy-id=<id: name or index> ] [ small-io-alerts=<enabled
or disabled> ] [ tag-list=<list of ids: name or index> ] [
unaligned-io-alerts=<enabled or disabled> ] [
vaai-tp-alerts=<enabled or disabled> ]
Provisioning 143
Admin CLI Commands
Example:
add-volume cluster-id="My_Cluster" vol-name="New_Volume"
vol-size="1t"
modify-volume
The modify-volume admin-level command modifies a Volume’s parameters.
Usage:
modify-volume vol-id=<name or index> ( application-type=<Epic,
Hyper-V VMs, Oracle DB, Other DB, SAP, VDI, VMware VMs, Others>
| qos-enabled-mode=<enabled, disabled, monitor_only> |
qos-policy-id=<id: name or index> | remove-qos-policy |
vaai-tp-alerts=<enabled or disabled> | small-io-alerts=<enabled
or disabled> | vol-access=<string> | vol-size=<integer suffixed
by [kmgtp]> | unaligned-io-alerts=<enabled or disabled> |
vol-name=<new volume name (rename)> |
management-locked=<enabled or disabled> ) [ cluster-id=<id:
name or index> ]
NOTE! The following property is mandatory: vol-id
NOTE! At least one property from the following list is
mandatory: application-type, qos-enabled-mode, qos-policy-id,
remove-qos-policy, vol-size, vol-name, small-io-alerts,
unaligned-io-alerts, vaai-tp-alerts, vol-access,
management-locked.
read_access - SCSI
read commands and
discovery commands
can succeed. Write
commands will fail.
write_access - The
host can write to the
Volume.
Example:
modify-volume vol-id="Volume" vol-size="2t"
Provisioning 145
Admin CLI Commands
remove-volume
The remove-volume admin-level command removes a Volume.
Usage:
remove-volume vol-id=<name or index> [ cluster-id=<id: name or
index> ]
Example:
remove-volume vol-id="vol1"
show-volumes
The show-volumes admin-level command displays the list of Volumes and related
information.
Usage:
show-volumes [sg-id=<name or index> ][ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
tag-list=<List of ids: name or index> ] [ filter=<> ] [
prop-list=<List of property strings> ]
Example:
show-volumes cluster-id=1 tag-list=["tag1","tag2"]
VSG-Space-In-Use The total user data space written to the Volume Snapshot Group
before deduplication and compression
Created-From-Volume The Volume that was the Snapshot source for this Volume
NAA-Identifier The SCSI Network Address Authority (NAA) identifier for the Volume
Creation-Time The date and time of the Volume or Snapshot creation in UTC
timezone
Provisioning 147
Admin CLI Commands
show-volume
The show-volume admin-level command displays the specified Volume’s information.
Usage:
show-volume vol-id=<name or index> [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
vertical ] [ filter=<> ] [ prop-list=<List of property strings>
]
Example:
show-volume vol-id="vol1" vertical
Logical-Space-In-Use The total user data space written to the Volume Snapshot Group
before deduplication and compression
Created-From-Volume The Volume that was the Snapshot source for this volume
NAA-Identifier The SCSI Network Address Authority (NAA) identifier for the Volume,
as exposed to the Initiators
Provisioning 149
Admin CLI Commands
show-volume-snapshot-groups
The show-volume-snapshot-groups admin-level command displays the list of
Volume Snapshot Groups and their parameters.
Usage:
show-volume-snapshot-groups [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<List of property strings> ]
Example:
show-volume-snapshot-groups
create-repurpose-copy
The create-repurpose-copy admin-level command creates a Repurpose Copy of a
Consistency Group or a Snapshot Set.
Usage:
create-repurpose-copy [ ( from-consistency-group-id=<id: name
or index> | from-snapshot-set-id=<id: name or index> |
from-volume-list=<list of IDs: name or index> ) ]
new-consistency-group-name=<string> [
new-snapshot-set-name=<string> ] [ new-vol-suffix=<string> ] [
cluster-id=<id: name or index> ] [
management-locked=<Enabled/Disabled> ] [ qos-policy-id=<name or
index> ] [ qos-enabled-mode=<enabled, disabled, monitor_only> ]
NOTE! At least one property from the following list is
mandatory: [ from-consistency-group-id, from-snapshot-set-id,
from-volume-id ]
NOTE! Only one property from the following list is allowed: [
from-snapshot-set-id, from-consistency-group-id, from-volume-id
].
Example:
create-repurpose-copy from-consistency-group-id=1
new-vol-suffix="_my-vol"
Provisioning 151
Admin CLI Commands
create-protection-copy
Example:
create-protection-copy from-consistency-group-id=1
new-vol-suffix="_my-vol"
create-snapshot
The create-snapshot admin-level command creates a Copy of the specified Volume.
Usage:
create-snapshot ( snapshot-set-id=<id: name or index> |
volume-list=<list of ids: name or index> |
consistency-group-id=<id: name or index> | tag-list=<list of
ids: name or index> ) [ snapshot-type=<"regular", "readonly"> ]
[ snapshot-set-name=<string> ] [ snap-suffix=<string> ] [
cluster-id=<id: name or index> ]
NOTE! At least one property from the following list is
mandatory: consistency-group-id, snapshot-set-id, volume-list,
tag-list.
Example:
create-snapshot consistency-group-id="CG1"
snap-suffix="_Snapshot"
Provisioning 153
Admin CLI Commands
create-snapshot-and-reassign
The create-snapshot-and-reassign admin-level command creates a Snapshot
from a specified Volume/Snapshot, Consistency Group, or Snapshot Set and reassigns the
Volume identity characteristic to the created Snapshot. When the command is used to
refresh a Snapshot Set, a Snapshot Set Tag can be used to specify the refreshed object.
Note: creating and reassigning a snapshot can be done between single Volumes, between
a Snapshot Set and a Consistency Group (or vice versa) and between two Snapshot Sets.
Usage:
create-snapshot-and-reassign ( from-snapshot-set-id=<id: name
or index> | from-snapshot-set-tag-id=<id: name or index> |
from-consistency-group-id=<id: name or index> |
from-volume-id=<id: name or index> ) (
to-snapshot-set-tag-id=<id: name or index> |
to-consistency-group-id=<id: name or index> |
to-snapshot-set-id=<id: name or index> | to-volume-id=<id: name
or index> ) [ backup-snap-suffix=<string> ] [
backup-snapshot-type=<readonly, regular> ] [ no-backup ] [
cluster-id=<id: name or index> ] [ snapshot-set-name=<string> ]
NOTE! Only one property from the following list must be
selected: from-consistency-group-id, from-snapshot-set-id,
from-volume-id, from-snapshot-set-tag-id.
NOTE! Only one property from the following list must be
selected: to-consistency-group-id, to-snapshot-set-id,
to-volume-id, to-snapshot-set-tag-id.
Example (Restore):
create-snapshot-and-reassign
from-volume-id="Last_Good_Timestamp"
to-volume-id="Production_Volume
Example (Refresh):
create-snapshot-and-reassign from-volume-id="Test_Host_Volume"
to-volume-id="Latest_Production_Snapshot
Provisioning 155
Admin CLI Commands
restore-data
Example:
restore-data from-volume-id="Last_Good_Timestamp"
to-volume-id="Production_Volume"
refresh-data
Provisioning 157
Admin CLI Commands
Example:
refresh-data from-volume-id="Last_Good_Timestamp"
to-volume-id="Production_Volume refresh-copy-dry-run
show-snapshots
The show-snapshots admin-level command displays the list of Snapshots and related
information.
Usage:
show-snapshots ancestor-vol-id=<name or index> [sg-id=<name or
index> ][ cluster-id=<id: name or index> ] [ tag-list=<List of
ids: name or index> ] [ frequency=<seconds> ] [
duration=<seconds> ] [ filter=<> ] [ prop-list=<List of
property strings> ]
Example:
show-snapshots ancestor-vol-id="vol1"
VSG-Space-In-Use The total user data space written to the Volume Snapshot Group
before deduplication and compression
Created-From-Volume The Volume that was the Snapshot source for this Volume
NAA-Identifier The SCSI Network Address Authority (NAA) identifier for the
Snapshot
Creation-Time The date and time on which the Snapshot was created
Provisioning 159
Admin CLI Commands
show-copies
The show-copies admin-level command displays a list of all copies of the specified
Volume or Consistency Group.
Usage:
show-copies ( vol-id=<Name or Index> | cg-id=<Name or Index> ) [
cluster-id=<Name or Index> ] [ duration=<seconds> ] [
frequency=<seconds> ] [ tag-list=<list of ids: Name or Index> ]
[ prop-list=<List of property strings> ] [ filter=<> ] [
from-time=<YYYY-MM-DD HH:MM:SS> ] [ to-time=<YYYY-MM-DD
HH:MM:SS> ] [ protection-only ]
NOTE! Only one of the following properties is mandatory: [
cg-id, vol-id ]
Example:
show-copies vol-id="Reserved_Volume"
show-volume-reservations
The show-volume-reservations admin-level command displays the specified
Volume’s SCSI reservation information.
Usage:
show-volume-reservations vol-id=<name or index> [
cluster-id=<id: name or index> ]
Example:
show-volume-reservations vol-id="Reserved_Volume"
Provisioning 161
Admin CLI Commands
clear-volume-reservation
The clear-volume-reservation admin-level command removes specified Volume
reservations to release them for access.
Usage:
clear-volume-reservation vol-id=<name or index> [
cluster-id=<id: name or index> ]
Example:
clear-volume-reservation vol-id="Reserved_Volume"
show-most-active-volumes
The show-most-active-volumes admin-level command displays performance data
of the most active Volumes.
Usage:
show-most-active-volumes [ duration=<seconds> ] [
frequency=<seconds> ] [ sort-by=<bw or iops> ]
Example:
show-most-active-volumes sort-by=bw
Write-BW (MB/s)
Read-BW (MB/s)
Write-IOPS
These properties indicate the current Bandwidth/IOPS.
Read-IOPS
BW (MB/s)
IOPS
show-most-active-initiator-groups
The show-most-active-initiator-groups admin-level command displays
performance data of the most active Initiator Groups.
Usage:
show-most-active-initiator-groups [ duration=<seconds> ] [
frequency=<seconds> ] [ sort-by=<bw, iops, latency> ]
Example:
show-most-active-initiator-groups sort-by=iops
Write-BW (MB/s)
Read-BW (MB/s)
Write-IOPS
These properties indicate the current Bandwidth/IOPS.
Read-IOPS
BW (MB/s)
IOPS
Provisioning 163
Admin CLI Commands
show-most-active
The show-most-active admin-level command displays the most active Volumes and
Initiator Groups.
Usage:
show-most-active [ duration=<seconds> ] [ frequency=<seconds> ]
[ sort-by=<bw or iops> ]
Example:
show-most-active
Note: The output is displayed for most active Volumes and most active Initiator Groups.
Write-BW (MB/s)
Read-BW (MB/s)
Write-IOPS
These properties indicate the current Bandwidth/IOPS.
Read-IOPS
BW (MB/s)
IOPS
calculate-savings
The calculate-savings admin-level command calculates saving metrics for the
specified Volume Snapshot Group, derived from Data Reduction Ratio per volume and
copy efficiency features.
Usage:
calculate-savings [ ( vol-id=<Name or Index> | vol-list=<list
of ids: Name or Index> | cg-id=<Name or Index> ) ] [
cluster-id=<id: name or index> ]
Example:
calculate-savings cg-id=12
show-volumes-savings
The show-volumes-savings admin-level command displays saving metrics per
Volume or group of Volumes, derived from Data Reduction Ratio per volume and copy
efficiency features.
Usage:
show-volumes-savings [ cluster-id=<Name or Index> ] [
duration=<seconds> ] [ frequency=<seconds> ] [ prop-list=<List
of property strings> ] [ filter=<> ]
Provisioning 165
Admin CLI Commands
Example:
show-volumes-savings
Host-Accessible-Size The amount of non-zero data that can be read from the Volume
Copy-Efficiency The ratio between Snapshot logical space and actual logical space
in use
remove-snapshot-set
The remove-snapshot-set admin-level command deletes a Snapshot Set.
Usage:
remove-snapshot-set ss-id=<name or index> [ cluster-id=<id:
name or index> ]
Example:
remove-snapshot-set ss-id="snapset1"
show-snapshot-set
The show-snapshot-set admin-level command displays the parameters of the
specified Snapshot Set.
Usage:
show-snapshot-set ss-id=<name or index> [ duration=<seconds> ]
[ cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
vertical ] [ prop-list=<List of property strings> ]
Example:
show-snapshot-set ss-id="volspider101458418635655" vertical
Provisioning 167
Admin CLI Commands
show-snapshot-sets
The show-snapshot-sets admin-level command displays the list of Snapshot Sets
and related information.
Usage:
show-snapshot-sets [ cluster-id=<id: name or index> ] [
frequency=<seconds> ] [ cg-id=<name or index> ] [ vertical ] [
duration=<seconds> ] [ tag-list=<List of ids: name or index> ] [
from-time=<date/time format: yyyy-mm-dd hh:mm:ss e.g.
"2017-06-20 12:45:33> ] [ to-time=<date/time format: yyyy-mm-dd
hh:mm:ss e.g. "2017-06-20 12:45:33> ] [
include-remote-protection ] [ prop-list=<list of property
strings> ] [ filter=<> ]
Example:
show-snapshot-sets
add-volume-to-consistency-group
The add-volume-to-consistency-group admin-level command adds a Volume to
an existing Consistency Group.
Usage:
add-volume-to-consistency-group cg-id=<name or index>
vol-id=<name or index> [ cluster-id=<id: name or index> ] [
reference-volume-id=<name or index> ]
Example:
add-volume-to-consistency-group cg-id="CG_1"
vol-id="Existing_Volume"
Provisioning 169
Admin CLI Commands
remove-volume-from-consistency-group
The remove-volume-from-consistency-group admin-level command removes a
Volume from a Consistency Group.
Usage:
remove-volume-from-consistency-group cg-id=<name or index>
vol-id=<name or index> [ cluster-id=<id: name or index> ]
Example:
remove-volume-from-consistency-group vol-id="vol1" cg-id="cg1"
create-consistency-group
The create-consistency-group admin-level command creates a new Consistency
Group.
Usage:
create-consistency-group [ cluster-id=<id: name or index> ] [
consistency-group-name=<string> ] [ management-locked=<enabled,
disabled> ] [ qos-enabled-mode=<enabled, disabled,
monitor_only> ] [qos-policy-id=<id: name or index> ] [
vol-list=<list of ids: name or index> ] [ tag-list=<list of ids:
name or index> ] [ result-object-tag-list=<list of ids: name or
index> ]
Example:
create-consistency-group consistency-group-name="New_CG"
tag-list["/Volume/Tag_Name"] vol-list=["Volume1","Volume2"]
modify-consistency-group
The modify-consistency-group admin-level command modifies the QoS-related
parameters of the specified Consistency Group.
Usage:
modify-consistency-group cg-id=<id: name or index> ( [
qos-enabled-mode=<enabled, disabled, monitor_only> ] [
qos-policy-id=<id: name or index> ] [ remove-qos-policy ] ) [
cluster-id=<id: name or index> ]
Note! At least one property from the following list is
mandatory: qos-enabled-mode, qos-policy-id, remove-qos-policy
Example:
modify-consistency-group cg-id="myCG" qos-enabled-mode=enabled
remove-consistency-group
The remove-consistency-group admin-level command deletes a Consistency
Group.
Usage:
remove-consistency-group cg-id=<name or index> [
cluster-id=<id: name or index> ]
Example:
remove-consistency-group cg-id="CG1"
Provisioning 171
Admin CLI Commands
modify-consistency-group-volumes
The modify-consistency-group-volumes admin-level command modifies the
Volume type for the specified a Consistency Group.
Usage:
modify-consistency-group-volumes cg-id=<name or index> [ (
vol-access=<string> | management-locked=<Enabled/Disabled> ) ]
[ cluster-id=<id: name or index> ]
NOTE! The following property is mandatory: cg-id
NOTE! At least one property from the following list is
mandatory: vol-access, management-locked
NOTE! Only one property from the following list is allowed:
vol-access, management-locked
read_access - SCSI
read commands and
discovery commands
can succeed. Write
commands will fail.
write_access - The
host can write to the
Volume.
Example:
modify-consistency-group-volumes cg-id="Existing_CG"
vol-access=write_access
add-copy-volume-to-consistency-groups
The add-copy-volume-to-consistency-groups admin-level command creates a
copy of a Volume which is a member of a Consistency Group and adds the copy to all
Consistency Groups specified in a list.
Usage:
add-copy-volume-to-consistency-groups reference-cg=<Name or
Index> reference-volume=<Name or Index> cg-list=<list of ids:
Name or Index> volume-name-suffix-list=<String> [
cluster-id=<id: Name or Index> ]
NOTE! The following properties are mandatory: [ cg-list,
reference-cg, reference-volume, volume-name-suffix-list ]
Example:
add-copy-volume-to-consistency-groups cg-list=["CG1", "CG2"]
reference-cg-id="MyCG" reference-volume-id="MyVol"
volume-name-suffix-list=["vol1", "vol2"]
Provisioning 173
Admin CLI Commands
show-consistency-group
The show-consistency-group admin-level command displays the members and
parameters of the specified Consistency Group.
Usage:
show-consistency-group cg-id=<name or index> [
duration=<seconds> ] [ cluster-id=<id: name or index> ] [
frequency=<seconds> ] [ prop-list=<List of property strings> ]
Example:
show-consistency-group cg-id="My_CG"
Creation-Time Date and time on which the Consistency Group was created
show-consistency-groups
The show-consistency-groups admin-level command displays a list of all
Consistency Groups and their parameters.
Usage:
show-consistency-groups [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
tag-list=<List of ids: name or index> ] [ filter=<> ] [
prop-list=<list of property strings> ]
Example:
show-consistency-groups tag-list=["mytag"]
Provisioning 175
Admin CLI Commands
add-initiator-group
The add-initiator-group admin-level command adds a new Initiator Group and
assigns Initiators to it.
Note: If you wish to add Initiators as part of creating the Initiator Group, then it is not
possible to configure CHAP for these Initiators.
Usage:
add-initiator-group [ cluster-id=<id: name or index> ] [
ig-name=<string> ] [ initiator-list=<[initiator-name=value
port-address=value,...]> ] [ qos-enabled-mode=<enabled,
disabled, monitor_only> ] [ qos-policy-id=<id: name or index> ]
[ tag-list=<list of ids: name or index> ]
Example:
add-initiator-group ig-name="New_IG"
tag-list=[/InitiatorGroup/tag1"]
modify-initiator-group
The modify-initiator-group admin-level command modifies the "Operating
System" setting of the specified Initiator Group.
Usage:
modify-initiator-group ig-id=<name or index> (
ig-name=<string> | operating-system=<linux, windows, esx,
solaris, aix, hpux, other> | qos-enabled-mode=<enabled,
disabled, monitor_only> | qos-policy-id=<name or index> |
remove-qos-policy ) [ cluster-id=<id: name or index> ]
Example:
modify-initiator-group ig-name="IG1" operating-system="linux"
remove-initiator-group
The remove-initiator-group admin-level command deletes an Initiator Group.
Usage:
remove-initiator-group ig-id=<name or index> [ cluster-id=<id:
name or index> ]
Example:
remove-initiator-group ig-id="IG-1"
Provisioning 177
Admin CLI Commands
show-initiator-group
The show-initiator-group admin-level command displays information for a specific
Initiator Group.
Usage:
show-initiator-group ig-id=<name or index> [ duration=<seconds>
] [ cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
prop-list=<List of property strings> ]
Example:
show-initiator-group ig-id="My_IG"
Tag-List The Tags assigned to the Initiator Group (full path name and index)
show-initiator-groups
The show-initiator-groups admin-level command displays a list of all Initiator
Groups and their parameters.
Usage:
show-initiator-groups [ duration=<seconds> ] [ cluster-id=<id:
name or index> ] [ frequency=<seconds> ] [ tag-list=<List of
ids: name or index> ] [ filter=<> ] [ prop-list=<List of
property strings> ]
Example:
show-initiator-groups
Tag-List The Tags assigned to the Initiator Group (full path name and index)
Provisioning 179
Admin CLI Commands
add-initiator
The add-initiator admin-level command adds an Initiator and associates it with an
existing Initiator Group.
Usage:
add-initiator ig-id=<name or index> port-address=<string> [
cluster-id=<id: name or index> ] [
cluster-discovery-user-name=<string> ] [
initiator-discovery-user-name=<string> ] [
operating-system=<linux, windows, esx, solaris, aix, hpux,
other> ] [ initiator-discovery-password=<string> ] [
cluster-discovery-password=<string> ] [
cluster-authentication-user-name=<string> ] [
cluster-authentication-password=<string> ] [
initiator-authentication-password=<string> ] [
initiator-authentication-user-name=<string> ] [
initiator-name=<string> ]
Example:
add-initiator ig-id="Existing_IG"
port-address="10:00:00:00:00:00:00:00"
remove-initiator
The remove-initiator admin-level command deletes an Initiator.
Usage:
remove-initiator initiator-id=<name or index> [ cluster-id=<id:
name or index> ]
Example:
remove-initiator initiator-id="ig-1"
Provisioning 181
Admin CLI Commands
modify-initiator
The modify-initiator admin-level command modifies the properties of an existing
Initiator.
Usage:
modify-initiator initiator-id=<name or index> (
initiator-discovery-password=<string> |
cluster-discovery-user-name=<string> |
cluster-authentication-user-name=<string> |
initiator-discovery-user-name=<string> |
cluster-discovery-password=<string> |
remove-initiator-authentication-credentials |
port-address=<string> | path-redundancy-monitor-mode=<enabled,
disabled> | cluster-authentication-password=<string> |
remove-initiator-discovery-credentials |
initiator-authentication-password=<string> |
operating-system=<linux, windows, esx, solaris, aix, hpux,
other> | remove-cluster-discovery-credentials |
initiator-authentication-user-name=<string> |
initiator-name=<string> |
remove-cluster-authentication-credentials ) [ cluster-id=<id:
name or index> ]
NOTE! At least one property from the following list is
mandatory: port-address, initiator-name,
path-redundancy-monitor-mode,
initiator-authentication-user-name,
initiator-authentication-password,
initiator-discovery-user-name, initiator-discovery-password,
cluster-authentication-user-name,
cluster-authentication-password, cluster-discovery-user-name,
cluster-discovery-password,
remove-initiator-authentication-credentials,
remove-initiator-discovery-credentials,
remove-cluster-authentication-credentials,
remove-cluster-discovery-credentials, operating-system.
Provisioning 183
Admin CLI Commands
IMPORTANT
The following parameters must be used as all-or-none pairs (select both parameters or
none of them):
[cluster-authentication-password, cluster-authentication-user-name],
[cluster-discovery-password, cluster-discovery-user-name],
[initiator-authentication-password, initiator-authentication-user-name],
[initiator-discovery-password, initiator-discovery-user-name]
Example:
modify-initiator initiator-id="Initiator"
port-address="50:00:00:00:00:00:00:00"
show-initiator
The show-initiator admin-level command lists the parameters of a specified
Initiator.
Usage:
show-initiator [ duration=<seconds> ] [ cluster-id=<id: name or
index> ] [ frequency=<seconds> ] [ vertical ] [ filter=<> ] [
prop-list=<List of property strings> ]
Example:
show-initiator initiator-id=1
show-initiators
The show-initiators admin-level command lists all Initiators and their parameters.
Usage:
show-initiators [ duration=<seconds> ] [ cluster-id=<id: name
or index> ] [ frequency=<seconds> ] [ vertical ] [ filter=<> ] [
prop-list=<List of property strings> ]
Provisioning 185
Admin CLI Commands
Example:
show-initiators
Scheduler Management
create-scheduler
The create-scheduler admin-level command creates a new Protection scheduler.
Refer to the XtremIO Storage Array User Guide for details on the scheduler-type and
time parameters
Usage:
create-scheduler snapshot-object-id=<name or index>
snapshot-object-type=<string> scheduler-type=<interval /
explicit> time=<string - interval [h:m:s] / explicit [day:h:m]>
( snapshots-to-keep-number=<integer> |
snapshots-to-keep-time=<integer suffixed by [Mhdmy]> ) [
enabled-state=<enabled / user_disabled> ]
[scheduler-name=<string> ] [ suffix=<string> ] [
snapshot-type=<string> ] [ cluster-id=<id: name or index> ]
NOTE! At least one property from the following list is
mandatory: snapshots-to-keep-number, snapshots-to-keep-time.
Provisioning 187
Admin CLI Commands
Example:
create-scheduler scheduler-type=interval
snapshot-object-type=Volume snapshot-object-id="Volume1"
snapshots-to-keep-number=2 time="10:20:15"
modify-scheduler
The modify-scheduler admin-level command modifies an existing Protection
scheduler’s parameters. Refer to the XtremIO Storage Array User Guide for details on the
scheduler-type and time parameters.
Usage:
modify_scheduler scheduler-id=<name or index> (
snapshot-object-type=<string> | suffix=<string> |
scheduler-type=<interval / explicit> | time=<string - interval
[h:m:s] / explicit [day:h:m]> | snapshot-object-id=<name or
index> | snapshots-to-keep-number=<integer> |
snapshot-type=<string> | snapshots-to-keep-time=<string of an
integer suffixed by [Mhdmy]> ) [ cluster-id=<id: name or index>
]
NOTE! At least one property from the following list is
mandatory: snapshot-object-type, snapshot-type, suffix,
snapshots-to-keep-time, snapshot-object-id,
snapshots-to-keep-number, scheduler-type, time.
Example:
modify-scheduler snapshot-object-type=Volume
snapshot-object-id="Database_01" scheduler-type=interval
time="0:30:0" snapshots-to-keep-time="3d"
Provisioning 189
Admin CLI Commands
remove-scheduler
The remove-scheduler admin-level command deletes a Protection scheduler.
Usage:
remove-scheduler scheduler-id=<name or index> [
remove-snapshot-sets ] [ cluster-id=<id: name or index> ]
Example:
remove-scheduler scheduler-id="scheduler1"
resume-scheduler
The resume-scheduler admin-level command resumes a suspended Protection
Scheduler.
Usage:
resume-scheduler scheduler-id=<id: name or index> [
cluster-id=<id: name or index> ]
Example:
resume-scheduler scheduler-id=1
suspend-scheduler
The suspend-scheduler admin-level command suspends and active Protection
Scheduler.
Usage:
suspend-scheduler scheduler-id=<id: name or index> [
cluster-id=<id: name or index> ]
Example:
suspend-scheduler scheduler-id=1
show-scheduler
The show-scheduler admin-level command displays the parameters of a specified
Protection Scheduler.
Usage:
show-scheduler scheduler-id=<name or index> [
duration=<seconds> ] [ cluster-id=<id: name or index> ] [
frequency=<seconds> ] [ vertical ] [ filter=<> ] [
prop-list=<list of property strings> ]
NOTE! The following parameter is mandatory: scheduler-id
Example:
show-scheduler scheduler-id="My_Scheduler"
Provisioning 191
Admin CLI Commands
show-schedulers
The show-schedulers admin-level command displays a list of Protection Schedulers
and their parameters.
Usage:
show-schedulers [ duration=<seconds> ] [ cluster-id=<id: name
or index> ] [ frequency=<seconds> ] [ filter=<> ] [
prop-list=<List of property strings> ]
Example:
show-schedulers
Target Management
modify-target
The modify-target admin-level command modifies a Target parameters.
Usage:
modify-target tar-id=<name or index> ( mtu=<integer> |
ip-addr-sn=<IP Address/Subnet Bits> |
port-enabled-state=<enabled, user_disabled> |
port-type=<’iscsi’, ’eth_replication’> |
refresh-replication-password ) [ cluster-id=<id: name or index>
]
NOTE! At least one property from the following list is
mandatory: mtu, ip-addr-sn, port-type,
refresh-replication-password
Example:
modify-target tar-id="X1-SC1-iscsi1" mtu=1500
Provisioning 193
Admin CLI Commands
show-targets
The show-targets admin-level command displays a list of iSCSI and FC Target
interfaces and their properties.
Usage:
show-targets [ cluster-id=<id: name or index> ] [ sc-id=<name
or index> ] [ filter=<> ] [ prop-list=<List of property strings>
] [ duration=<seconds> ] [ frequency=<seconds> ]
Example:
show-targets
TG-Name The name of the Target Group to which the Target belongs
modify-target-group
The modify-target admin-level command modifies a Target Group’s parameters.
Usage:
modify-target-group tg-id=<name or index> mtu=<integer> [
cluster-id=<id: name or index> ]
Example:
modify-target-group tg-id="Default" mtu=1500
show-target-groups
The show-target-groups admin-level command displays the list of Target Groups.
Usage:
show-target-groups [ duration=<seconds> ] [ cluster-id=<id:
name or index> ] [ frequency=<seconds> ] [ filter=<> ] [
prop-list=<List of property strings> ]
Provisioning 195
Admin CLI Commands
Example:
show-target-groups
Cluster-Name The name of the cluster to which the Target Group is related
LUN Mapping
map-lun
The map-lun admin-level command maps a Volume to an Initiator Group and assigns a
Logical Unit Number (LUN) to it.
Usage:
map-lun vol-id=<name or index> ig-id=<name or index. If
omitted, means "Undefined Initiators"> [ cluster-id=<id: name
or index> ] [ lun=<integer> ] [ tg-id=<name or index> ]
Example:
map-lun vol-id="Volume" ig-id="Host" lun=5
cluster-id="My_Cluster"
show-lun-mappings
The show-lun-mappings admin-level command displays a list of all mappings
between Volumes and Initiator Groups.
Usage:
show-lun-mappings ( vol-id=<name or index> | ig-id=<name or
index> ) [ duration=<seconds> ] [ cluster-id=<id: name or
index> ] [ frequency=<seconds> ] [ filter=<> ] [
prop-list=<list of property strings> ]
NOTE! Only one property from the following list is allowed:
ig-id, vol-id.
Example:
show-lun-mappings vol-id="My_Vol"
Provisioning 197
Admin CLI Commands
unmap-lun
The unmap-lun admin-level command removes a Volume’s mapping to one or more
Initiator Groups.
Usage:
unmap-lun vol-id=<name or index> ( all | ig-id=<name or index.
If omitted, means "Undefined Initiators"> ) [ cluster-id=<id:
name or index> ] [ tg-id=<name or index> ]
NOTE! The following property is mandatory: vol-id
NOTE! At least one property from the following list is
mandatory: all, ig-id
NOTE! Only one property from the following list is allowed: all,
ig-id
Example:
unmap-lun vol-id="vol1" all
Quality of Service
add-qos-policy
The add-qos-policy admin-level command creates a new Quality of Service policy.
Usage:
add-qos-policy qos-policy-name=<string> limit-type=<fixed,
adaptive> ( max-bw=<integer suffixed by [km] |
max-iops=<integer> ) [ burst-percentage=<integer> ] [
cluster-id=<id: name or index> ] [ io-size=<512b, 1kb, 2kb,
4kb, 8kb, 16kb, 32kb, 64kb, 128kb, 256kb, 512kb, 1mb> ]
NOTE! The following properties are mandatory: limit-type,
qos-policy-name
NOTE! At least one property from the following list is
mandatory: max-bw, max-iops
NOTE! Only one property from the following list is allowed:
max-bw, max-iops
NOTE! io-size needs to be set if max-iops is defined.
Example:
add-qos-policy qos-policy-name="myPolicy" limit-type=fixed
max-iops=100
Provisioning 199
Admin CLI Commands
modify-qos-policy
The modify-qos-policy admin-level command modifies the parameter of a selected
Quality of Service policy.
Usage:
modify-qos-policy qos-policy-id=<id: name or index> (
burst-percentage=<integer> | io-size=<512b, 1kb, 2kb, 4kb, 8kb,
16kb, 32kb, 64kb, 128kb, 256kb, 512kb, 1mb>
| limit-type=<fixed, adaptive> | ( max-bw=<integer suffixed by
[km]> | max-iops=<integer> ) | qos-policy-name=<new Volume name
(rename)> ) [ cluster-id=<id: name or index> ]
NOTE! The following property is mandatory: qos-policy-id
NOTE! At least one property from the following list is
mandatory: qos-policy-name, limit-type, max-bw, max-iops,
io-size, burst-percentage
NOTE! Only one property from the following list is allowed:
max-bw, max-iops
NOTE! io_size needs to be set if max-iops is defined.
Example:
modify-qos-policy qos-policy-id=12 qos-policy-name="new name"
remove-qos-policy
The remove-qos-policy admin-level command removes a selected Quality of Service
policy.
Usage:
remove-qos-policy qos-policy-id=<id: name or index> [
cluster-id=<id: name or index> ]
NOTE! The following property is mandatory: qos-policy-id
Example:
remove-qos-policy qos-policy-id=12
show-qos-policy
The show-qos-policy admin-level command displays the parameters of a selected
Quality of Service policy.
Usage:
show-qos-policy qos-policy-id=<id: name or index> [
cluster-id=<id: name or index> ] [ duration=<seconds> ] [
frequency=<seconds> ] [ filter ]
NOTE! The following property is mandatory: qos-policy-id
Provisioning 201
Admin CLI Commands
Example:
show-qos-policy qos-policy-id=12
show-qos-policies
The show-qos-policies admin-level command displays the parameters of all defined
Quality of Service policies.
Usage:
show-qos-policies [ cluster-id=<id: name or index> ] [
duration=<seconds> ] [ frequency=<seconds> ] [ filter ]
Example:
show-qos-policies
Note: The selected policy’s burst-percentage should not be defined to be compatible with
admission control.
Note: To enable the system-level admission control, an approved RPQ (Request for
Product Qualification) is required.
Provisioning 203
Admin CLI Commands
iSCSI Management
add-iscsi-portal
The add-iscsi-portal admin-level command creates an iSCSI portal (IP/VLAN) on a
specific iSCSI Target port.
Note: iSCSI Targets cannot have the same subnet as the management network.
Usage:
add-iscsi-portal tar-id=<name or index> ip-addr=<IP
Address/Subnet Bits> [ cluster-id=<id: name or index> ] [
vlan=<integer> ]
Example:
add-iscsi-portal tar-id="X1-SC1-iscsi1" ip-addr="1.2.3.4/24"
add-iscsi-route
The add-iscsi-route admin-level command configures a new routing rule for iSCSI
traffic.
Usage:
add-iscsi-route gateway=<IP Address>
destination-network-and-mask=<Destination network/mask> [
iscsi-route-name=<string> ] [ cluster-id=<id: name or index> ]
Example:
add-iscsi-route destination-network-and-mask="1.2.3.0/24"
gateway="1.2.3.4"
modify-iscsi-portal
The modify-iscsi-portal admin-level command modifies an iSCSI portal
parameters.
Usage:
modify-iscsi-portal portal-id=<index> ( vlan=<integer> |
ip-addr=<IP Address/Subnet Bits> ) [ cluster-id=<id: name or
index> ]
NOTE! At least one property from the following list is
mandatory: ip-addr, vlan.
Example:
modify-iscsi-portal portal-id="X1-SC1-iscsi1"
ip-addr="1.2.3.4/24" vlan=5
remove-iscsi-portal
The remove-iscsi-portal admin-level command deletes a portal mapping from a
Target.
Note: The Target will no longer receive iSCSI traffic via the portal.
Usage:
remove-iscsi-portal ip-addr=<IP Address/Subnet Bits> [
cluster-id=<id: name or index> ]
Example:
modify-iscsi-portal ip-addr="10.2.2.1/24"
Provisioning 205
Admin CLI Commands
remove-iscsi-route
The remove-iscsi-route admin-level command deletes an iSCSI routing rule.
Usage:
remove-iscsi-route iscsi-route-id=<name or index> [
cluster-id=<id: name or index> ]
Example:
remove-iscsi-route iscsi-route-id="iSCSIRoute1"
show-iscsi-portals
The show-iscsi-portals admin-level command displays the list of iSCSI portals and
their properties.
Usage:
show-iscsi-portals [ duration=<seconds> ] [ cluster-id=<id:
name or index> ] [ frequency=<seconds> ] [ filter ]
Example:
show-iscsi-portals
show-iscsi-routes
The show-iscsi-routes admin-level command displays the list of iSCSI routes and
their properties.
Usage:
show-iscsi-routes [ duration=<seconds> ] [ cluster-id=<id: name
or index> ] [ frequency=<seconds> ] [ filter=<> ] [
prop-list=<List of property strings> ]
Provisioning 207
Admin CLI Commands
Example:
show-iscsi-routes
show-chap
The show-chap admin-level command displays the cluster’s configured CHAP
authentication and discovery modes.
Usage:
show-chap [cluster-id=<id: name or index> ] [
duration=<seconds> ] [ frequency=<seconds> ] [ filter=<> ] [
prop-list=<list of property strings> ]
Example:
show-chap
Chap-Discovery-Mode The CHAP discovery mode (Disabled, Initiator, Initiator and Target)
modify-chap
The modify-chap admin-level command modifies the CHAP configuration parameters.
Usage:
modify-chap ( chap-discovery-mode=<disabled, initiator or
initiator_and_target> | chap-authentication-mode=<disabled,
initiator or initiator_and_target> ) [ cluster-id=<name or
index> ]
NOTE! At least one property from the following list is
mandatory: chap-discovery-mode, chap-authentication-mode.
Example:
modify-chap chap-discovery-mode=initiator
chap-authentication-mode=initiator_and_target
Provisioning 209
Admin CLI Commands
show-data-protection-groups
The show-data-protection-groups admin-level command displays a list of Data
Protection Groups and their properties.
Usage:
show-data-protection-groups [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
vertical ] [ filter=<> ] [ prop-list=<list of property strings>
]
Example:
show-data-protection-groups
User-Space The total SSD space available to the XtremIO Storage Array for user
data
Rebuild-Progress The progress of a rebuild action for the Data Protection Group
following SSD failure
Preparation-Progress The Data Protection Group is being added to the cluster and is in
preparation.
Provisioning 211
Admin CLI Commands
Data Protection
Retention Policy
add-protection-retention-policy
The add-protection-retention-policy admin-level command adds a new
Retention Policy.
Usage:
add-protection-retention-policy cluster-id=<Name or Index>
retention-policy-name=<String> short-period-duration=<String>
short-period-copies=<Integer> [ middle-period-duration=<String>
] [ middle-period-copies=<Integer> ] [
long-period-duration=<String> ] [ long-period-copies=<Integer>
] [ xms-name=<name> ]
NOTE! The following properties are mandatory: [ cluster-id,
retention-policy-name, short-period-duration,
short-period-copies ]
NOTE! When providing the cluster index as the cluster-id
parameter, it is required to provide the xms-name parameter as
well; alternatively, it is possible to provide the cluster name
as cluster-id.
Example:
add-protection-retention-policy
copy-protection-retention-policy
The copy-protection-retention-policy admin-level command copies all
retention policies or a specified Retention Policy from one cluster to another.
Usage:
copy-protection-retention-policy cluster-id=<Name or Index>
retention-policy-name=<String> short-period-duration=<String>
short-period-copies=<Integer> [ middle-period-duration=<String>
] [ middle-period-copies=<Integer> ] [
long-period-duration=<String> ] [ long-period-copies=<Integer>
] [ xms-name=<name> ]
NOTE! The following properties are mandatory: [
from-cluster-id, to-cluster-id ]
NOTE! The following properties are mandatory and exclusive: [
copy-all, retention-policy-id ]
NOTE! When providing the cluster index as the cluster-id
parameter, it is required to provide the xms-name parameter as
well; alternatively, it is possible to provide the cluster name
as cluster-id.
Example:
copy-protection-retention-policy from-
modify-protection-retention-policy
The modify-protection-retention-policy admin-level command modifies the
parameters of a Retention Policy.
Note: All parameters must be assigned. Partial assignment resets the unassigned
parameters to the system defaults.
Usage:
modify-protection-retention-policy cluster-id=<Name or Index>
retention-policy-name=<String> short-period-duration=<String>
short-period-copies=<Integer> [ middle-period-duration=<String>
] [ middle-period-copies=<Integer> ] [
long-period-duration=<String> ] [ long-period-copies=<Integer>
] [ xms-name=<name> ]
NOTE! The following properties are mandatory: [ cluster-id,
retention-policy-id ]
NOTE! At least one of the following parameters must be selected:
[ retention-policy-name, short-period-copies,
short-period-duration, middle-period-copies,
middle-period-duration, long-period-copies,
long-period-duration ]
NOTE! When providing the cluster index as the cluster-id
parameter, it is required to provide the xms-name parameter as
well; alternatively, it is possible to provide the cluster name
as cluster-id.
Example:
modify-protection-retention-policy
remove-protection-retention-policy
The remove-protection-retention-policy admin-level command deletes a
protection Retention Policy.
Usage:
remove-protection-retention-policy cluster-id=<Name or Index>
retention-policy-id=<Name or Index> [ xms-name=<Name> ]
NOTE! The following properties are mandatory: [ cluster-id,
retention-policy-id ]
NOTE! When providing the cluster index as the cluster-id
parameter, it is required to provide the xms-name parameter as
well; alternatively, it is possible to provide the cluster name
as cluster-id.
Example:
remove-protection-retention-policy
show-protection-retention-policy
The show-protection-retention-policy admin-level command displays the
parameters of a specified Retention Policy.
Usage:
show-protection-retention-policy cluster-id=<Name or Index>
retention-policy-id=<Name or Index> [ prop-list=<list of
property strings> ] [ xms-name=<name> ]
NOTE! The following properties are mandatory: [ cluster-id,
retention-policy-id ]
NOTE! When providing the cluster index as the cluster-id
parameter, it is required to provide the xms-name parameter as
well; alternatively, it is possible to provide the cluster name
as cluster-id.
Example:
show-protection-retention-policy
Protection-Window-Num-Co The total number of protection copies retained at the target cluster
pies
Short-Period-Unit Unit of retention for the short period (minutes, hours, days)
Middle-Period-Unit Unit of retention for the middle period (minutes, hours, days)
Long-Period-Unit Unit of retention for the long period (minutes, hours, days)
Replication-Session-List A list of all Remote Protection Sessions using this Retention Policy
show-protection-retention-policies
The show-protection-retention-policies admin-level command displays the
parameters of all defined retention policies.
Usage:
show-protection-retention-policies [ cluster-id=<Name or Index>
] [ prop-list=<list of property strings> ] [ xms-name=<name> ]
NOTE! When providing the cluster index as the cluster-id
parameter, it is required to provide the xms-name parameter as
well; alternatively, it is possible to provide the cluster name
as cluster-id.
Example:
show-protection-retention-policies
Local Protection
add-local-protection-session
The add-local-protection-session admin-level command adds a new Local
Protection Session.
Usage:
add-local-protection-session protection-session-name=<String>
snapped-object-id=<Name or Index> snapped-object-type=<Volume,
ConsistencyGroup> local-protection-type=<interval, explicit>
schedule=<String - interval [h:m:s] / explicit [day:h:m]> [
cluster-id=<Name or Index> ] [ enabled-state=<enabled,
user_disabled> ] [ retention-policy-id=<Name or Index> ] [
suffix=<string> ] [ create-secured-snap=<True, false> ]
NOTE! The following properties are mandatory: [
protection-session-name, snapped-object-id,
snapped-object-type, local-protection-type, schedule ]
Example:
add-local-protection-session local-protection-type=interval
protection-session-name="localProt1" schedule="22:30:00"
snapped-object-id=1 snapped-object-type=Volume
manage-local-protection-session
The manage-local-protection-session admin-level command starts, suspends
or resumes a Local Protection Session.
Usage:
manage-local-protection-session protection-session-id=<Name or
Index> [ cluster-id=<Name or Index> ] [ operation=<start,
suspend, resume> ]
NOTE! The following properties are mandatory:
protection-session-id
Example:
manage-local-protection-session protection-session-id=1
operation=start
modify-local-protection-session
The modify-local-protection-session admin-level command modifies the
parameters of a Local Protection Session.
Usage:
modify-local-protection-session protection-session-id=<Name or
Index> [ new-protection-session-name=<String> ] [
local-protection-type=<interval, explicit> ] [ schedule=<string
- interval [h:m:s] / explicit [day:h:m]> ] [
retention-policy-id=<Name or Index> ] [ suffix=<String> ] [
remove-retention-policy ] [ create-secured-snap=<True, False> ]
NOTE! The following property is mandatory:
protection-session-id
NOTE! At least one of the following parameters must be selected:
[new-protection-session-name, local-protection-type, schedule,
retention-policy-id, suffix, remove-retention-policy,
create-secured-snap]
Example:
modify-local-protection-session protection-session-id=1
new-protection-session-name="localProt2"
remove-local-protection-session
The remove-local-protection-session admin-level command deletes a Local
Protection Session.
Usage:
remove-local-protection-session protection-session-id=<Name or
Index> [ cluster-id=<Name or Index> ] [ remove-snapshot-sets ]
NOTE! The following property is mandatory: [
protection-session-id ]
Example:
remove-local-protection-session protection-session-id=1
show-local-protection-consistency-group
The show-local-protection-consistency-group admin-level command
displays the details of a Consistency Group that is a part of a Local Protection Session.
Usage:
show-local-protection-consistency-group
consistency-group-id=<Name or Index> [ cluster-id=<Name or
Index> ] [ vertical ]
NOTE! The following property is mandatory: [
consistency-group-id ]
Example:
show-local-protection-consistency-group consistency-group-id=1
show-local-protection-consistency-groups
The show-local-protection-consistency-groups admin-level command
displays the details of all Consistency Group that are a part of a Local Protection Session.
Usage:
show-local-protection-consistency-groups [ cluster-id=<Name or
Index> ] [ vertical ]
Example:
show-local-protection-consistency-groups
show-local-protection-session
The show-local-protection-session admin-level command displays the details
of a specified Local Protection Session.
Note: To locate all secured Local Protection Sessions, use the prop-list input parameter
with the create-secured-snap property.
Usage:
show-local-protection-session protection-session-id=<Name or
Index> [ cluster-id=<Name or Index> ] [ duration=<seconds> ] [
filter=<> ] [ frequency=<seconds> ] [ prop-list=<list of
property strings> ] [ vertical ]
NOTE! The following property is mandatory: [
protection-session-id ]
Example:
show-local-protection-session protection-session-id=1
Current-Protection-Window- The actual total number of PITs retained on the Local Protection
Copies Session
Current-Protection-Window- The actual protection time frame (in days) for which the copies exist
Duration-in-Days
Next-Scheduled-Cycle Date and time of the next scheduled Local Protection cycle
Lag (sec) The time that passed since the last consistent PIT was replicated (in
seconds)
Last-Run-Completed-Snaps The most recent completed Snapshot Set created by this Local
hot-Set Protection Session
Num-Missing-Short-Period- The number of PITs missing for the short period (compared to the
PITs configured number)
Num-Missing-Middle-Period The number of PITs missing for the middle period (compared to the
-PITs configured number)
Num-Missing-Long-Period-P The number of PITs missing for the long period (compared to the
ITs configured number)
show-local-protection-sessions
The show-local-protection-sessions admin-level command displays the details
of all Local Protection Sessions.
Usage:
show-local-protection-sessions [ cluster-id=<Name or Index> ] [
duration=<seconds> ] [ filter=<> ] [ frequency=<seconds> ] [
prop-list=<list of property strings> ]
Example:
show-local-protection-sessions
Current-Protection-Window- Actual number of copies retained for this Local Protection Session
Copies
show-local-protection-snapshot-sets
The show-local-protection-snapshot-sets admin-level command lists the
Snapshot Sets related to a specified Local Protection Session.
Usage:
show-local-protection-snapshot-sets protection-session-id=<Name
or Index> [ cluster-id=<Name or Index> ] [ duration=<seconds> ]
[ filter=<> ] [ frequency=<seconds> ] [ prop-list=<list of
property strings> ] [ from-time=<date/time format: e.g.
"2018-06-04 14:21:29"> ] [ to-time=<date/time format: e.g.
"2018-06-04 14:21:29"> ] [ vertical ]
Example:
show-local-protection-snapshot-sets
protection-session-id="MySession"
Remote Protection
add-remote-protection-ip-link
The add-remote-protection-ip-link admin-level command adds an IP link
between a source cluster and a target cluster.
Usage:
add-remote-protection-ip-link source-cluster-id=<Name or Index>
source-ip-addr-sn=<IP Address/Subnet Bits>
target-cluster-id=<Name or Index> target-ip-addr-sn=<IP
Address/Subnet Bits> [ ip-link-name=<String> ] [
source-xms-name=<name> ] [ target-xms-name=<name> ]
NOTE! The following properties are mandatory:
[source-cluster-id, source-ip-addr-sn, target-cluster-id,
target-ip-addr-sn]
NOTE! When providing the cluster index as the cluster-id
parameter, it is required to provide the xms-name parameter as
well; alternatively, it is possible to provide the cluster name
as cluster-id.
Example:
add-remote-protection-ip-link source-cluster-id="Xbrick11"
source-ip-addr-sn="1.1.1.10/24" target-cluster-id="Xbrick21"
target-ip-addr-sn="1.1.1.20/24"
modify-remote-protection-ip-link
The modify-remote-protection-ip-link admin-level command modifies the
parameters of an IP link between a source cluster and a target cluster.
Usage:
modify-remote-protection-ip-link ip-link-id=<Name or Index>
[(enable | disable) | refresh-link-credentials |
number-of-sockets=<Integer 4-128> | ip-link-name=<String>]
NOTE! The following property is mandatory: [ip-link-id]
NOTE! At least one of the following properties is mandatory:
[disable, enable, ip-link-name, number-of-sockets,
refresh-link-credentials]
NOTE! Only one property from the following is allowed:
[enabled, disabled]
Example:
modify-remote-protection-ip-link ip-link-id=1 enable
remove-remote-protection-ip-link
The remove-remote-protection-ip-link admin-level command deletes an IP
link between a source cluster and a target cluster.
Usage:
remove-remote-protection-ip-link ip-link-id=<Name or Index> [
force ]
NOTE! The following property is mandatory: [ ip-link-id ]
Example:
remove-remote-protection-ip-link ip-link-id=1
show-remote-protection-ip-link
The show-remote-protection-ip-link admin-level command displays the
parameters of the specified IP link.
Usage:
show-remote-protection-ip-link ip-link-id=<Name or Index> [
prop-list=<List of property strings> ]
NOTE! The following property is mandatory: [ ip-link-id ]
Example:
show-remote-protection-ip-link ip-link-id=1
show-remote-protection-ip-links
The show-remote-protection-ip-links admin-level command displays the
parameters of all IP links.
Usage:
show-remote-protection-ip-links [ cluster-id=<Name or Index> ]
[ peer-cluster-id=<Name or Index> ] [ peer-xms-name=<name> ] [
protection-session-id=<Name or Index> ] [ xms-name=<name> ]
NOTE! When providing the cluster index as the cluster-id
parameter, it is required to provide the xms-name parameter as
well; alternatively, it is possible to provide the cluster name
as cluster-id.
Example:
show-remote-protection-ip-links
add-remote-protection-peer-xms
The add-remote-protection-peer-xms admin-level command registers a remote
XMS to the local XMS.
Usage:
add-remote-peer-xms remote-ip-addr=<IP Address>
remote-xms-alias-name=<name> remote-xms-user=<Sting>
remote-user-password=<String> [ local-xms-alias-name=<name> ]
NOTE! The following properties are mandatory: [remote-ip-addr,
remote-xms-alias-name, remote-xms-user, remote-user-password]
Example:
add-remote-peer-xms remote-ip-addr="1.1.1.10"
remote-xms-alias-name="XMS1" remote-xms-user="admin"
remote-user-password="MyPwd"
modify-remote-protection-peer-xms
The modify-remote-protection-peer-xms admin-level command modifies the
parameters of a remote XMS registered at the local XMS.
Usage:
modify-remote-protection-peer-xms xms-alias-name=<Name> [
new-xms-alias-name=<name> | new-ip-addr=<IP Address> ]
NOTE! The following property is mandatory: [xms-alias-name]
NOTE! At least one of the following properties is mandatory:
[new-ip-addr, new-xms-alias-name]
Example:
modify-remote-protection-peer-xms xms-alias-name="XMS1"
new-xms-alias-name="NewXMS"
remove-remote-protection-peer-xms
The remove-remote-protection-peer-xms admin-level command removes a
registration of a remote XMS from the local XMS.
Usage:
remove-remote-protection-peer-xms xms-alias-name=<Name>
NOTE! The following property is mandatory: [xms-alias-name]
Example:
remove-remote-protection-peer-xms xms-alias-name="XMS1"
show-remote-protection-peer-xms
The show-remote-protection-peer-xms admin-level command displays all
remote XMSs registered at the local XMS.
Usage:
show-remote-protection-peer-xms
Example:
show-remote-protection-peer-xms
add-remote-protection-session
The add-remote-protection-session admin-level command creates a new
Remote Protection Session.
Usage:
add-remote-protection-session protection-session-name=<String>
rpo=<Integer> source-cluster-id=<Name or Index>
source-consistency-group-id=<Name or Index>
target-cluster-id=<Name or Index> [ (
target-consistency-group-id=<Name or Index> |
auto-provision-target ) ] [
protection-window-compliance-alert=<enabled, disabled> ] [
source-retention-policy-id=<Name or Index> ] [
source-xms-name=<name> ] [ start-on-craetion ] [
target-retention-policy-id=<Name or Index> ] [
target-volume-access=<no_access, read_only> ] [
target-xms-name=<name> ] [ enable-verification=<enabled,
disabled> ], async-bw-limit=<integer> ] [
replication-mode=<async, sync> ]
NOTE! The following properties are mandatory:
[protection-session-name, rpo, source-cluster-id,
source-consistency-group-id, target-cluster-id]
NOTE! At least one property from the following list is
mandatory: [target-consistency-group-id, auto-provision-target]
NOTE! Only one property from the following list is allowed:
[target-consistency-group-id, auto-provision-target]
NOTE! When providing the cluster index as the cluster-id
parameter, it is required to provide the xms-name parameter as
well; alternatively, it is possible to provide the cluster name
as cluster-id.
Example:
add-remote-protection-session
protection-session-name="MySession" rpo=3000
source-cluster-id="SourceCluster"
source-consistency-group-id=22
target-cluster-id="TargetCluster" auto-provision-target
modify-remote-protection-session
The modify-remote-protection-session admin-level command modifies the
parameters of a Remote Protection Session.
Usage:
modify-remote-protection-session protection-session-id=<Name or
Index> [ ( source-retention-policy-id=<Name or Index> |
remove-source-retention-policy ) | (
target-retention-policy-id=<Name or Index> |
remove-target-retention-policy ) |
new-protection-session-name=<String> | rpo=<Integer> |
replication-mode=<async,sync> |
target-volume-access=<no_access, read_only> |
protection-window-compliance-alert=<enabled, disabled> |
release-lock ] | [ async-bw-limit=<Integer> ] | [
enable-verification=<enabled, disabled> ] [ force ]
NOTE! The following property is mandatory:
[protection-session-id]
NOTE! At least one property from the following list is
mandatory: [new-protection-session-name, rpo,
source-retention-policy-id, remove-source-retention-policy,
target-retention-policy-id, remove-target-retention-policy,
target-volume-access, protection-window-compliance-alert,
release-lock, async-bw-limit, enable-verification]
NOTE! Only one property from the following list is allowed:
[source-retention-policy-id, remove-source-retention-policy]
NOTE! Only one property from the following list is allowed:
[target-retention-policy-id, remove-target-retention-policy]
Example:
modify-remote-protection-session protection-session-id=1 rpo=30
manage-remote-protection-session
The manage-remote-protection-session admin-level command enables to
perform actions in the context of the Remote Protection Session.
Note: For details on the various Remote Protection Session actions, refer to For details on
the different operations, refer to the XtremIO Storage Array User Guide.
Usage:
manage-remote-protection-session protection-session-id=<Name or
Index> operation=<start, suspend, terminate, resume,
replicate_now, create-bookmark, failover, failover_cleanup,
test_copy_start, test_copy_finish, remove_snapshot_sets> (
snapshot-sets-to-remove-side=<source, target> )
(cluster-id=<name or index> ) [ bookmark-name=<String> ] [
keep-target-ss=<True, false> ] [ cluster-id=<Name or Index> ] [
force ] [ retention-time=<minutes> ] [ snapshto-set-id=<Name
or Index> ] [
snapshot-set-selection=<using_latest_snapshot_set,
use_test_copy_snapshot_set, sync_and_failover> ] [
snapshot-sets-to-remove-side=<source, target> ] [
snapshot-sets-to-remove-since=<date/time format: e.g.
"2018-01-23 11:46:37"> ] [
snapshot-sets-to-remove-until=<date/time format: e.g.
"2018-01-23 11:46:37"> ] [ start-replication-with-failover ] [
suspend-type=<graceful, immediate> ] [ xms-name=<name> ]
NOTE! The following properties are mandatory:
[protection-session-id, operation]
NOTE! Only one property from the following list is allowed:
[snapshot-sets-to-remove-side]
NOTE! Only one property from the following list is allowed:
[cluster-id]
NOTE! When providing the cluster index as the cluster-id
parameter, it is required to provide the xms-name parameter as
well; alternatively, it is possible to provide the cluster name
as cluster-id.
Example:
manage-remote-protection-session protection-session-id=1
operation=suspend
remove-remote-protection-session
The remove-remote-protection-session admin-level command deletes a
Remote Protection Session.
Usage:
remove-remote-protection-session protection-session-id=<Name or
Index> [ force ] [ remove-target-volumes ]
NOTE! The following property is mandatory: [
protection-session-id ]
Example:
remove-remote-protection-session protection-session-id=1
show-remote-protection-session
The show-remote-protection-session admin-level command displays the
parameters of a Remote Protection Session.
Usage:
show-remote-protection-session protection-session-id=<Name or
Index> [ prop-list=<List of property strings> ]
NOTE! The following property is mandatory: [
protection-session-id ]
Example:
show-remote-protection-session protection-session-id=1
Protection-Window-Num-Co The total number of protection copies retained at the target cluster
pies
Target-PIT-Num-Copies-Stat Indicates whether the number of PITs on the target cluster matches
us user configuration
Target-PIT-Window-size-Stat Indicates whether the target protection window size matches user
us configuration
Lag The time that passed since the last consistent PIT was replicated (in
seconds)
BW Bandwith (KB/sec)
Last-Cycle-Completed-Snap The most recent completed PIT that exists in the target cluster
shot-Set
Num-Missing-Short-Period- The number of Snapshot Sets that are missing on the source cluster
Snapshot-Sets according to the configured short period of the Retention Policy for
this Remote Protection Session
Num-Missing-Middle-Period The number of Snapshot Sets that are missing on the source cluster
-Snapshot-Sets according to the configured middle period of the Retention Policy
for this Remote Protection Session
Num-Missing-Long-Perios-S The number of Snapshot Sets that are missing on the source cluster
napshot-Sets according to the configured long period of the Retention Policy for
this Remote Protection Session
Target-Missing-PITs-Alert Indicates whether generation of alerts and events for missing PITs
is enabled or disabled.
Current-Command-Status Indicates the status of the last command applied to the Remote
Protection Session.
Replication-Session-Consist The state of this Remote Protection Session from XMS point of view.
ency-State
Obj-Severity The Remote Protection Session severity level based on the severity
of all current alerts
Current-Protection-Window- The actual total number of PITs retained on the Protection Session
Copies
Async-BW-Limit The maximum bandwidth that may be utilized for this async
Replication Session (mbps)
show-remote-protection-sessions
The show-remote-protection-sessions admin-level command displays the
parameters of all Remote Protection Sessions.
Usage:
show-remote-protection-sessions [ filter=<> ] [ prop-list=<List
of property strings> ]
Example:
show-remote-protection-sessions
Lag The time that passed since the last consistent PIT was replicated (in
seconds)
add-remote-protection-volume-pair
The add-remote-protection-volume-pair admin-level command pairs a source
and target Volumes and adds them to the Remote Protection Session.
Usage:
add-remote-protection-volume-pair source-vol-id=<Name or Index>
target-vol-id=<Name or Index> source-cluster-id=<Name or Index>
target-cluster-id=<Name or Index> protection-session-id=<Name
or Index> [ source-xms-name=<name> ] [ target-xms-name=<name> ]
[ volume-pair-name=<String> ]
NOTE! When providing the cluster index as the cluster-id
parameter, it is required to provide the xms-name parameter as
well; alternatively, it is possible to provide the cluster name
as cluster-id.
Example:
add-remote-protection-volume-pair protection-session-id=1
source-cluster-id="SourceCluster" source-vol-id=25
target-cluster-id="TargetCluster" target-vol-id=32
remove-remote-protection-volume-pairs
The remove-remote-protection-volume-pairs admin-level command removes
a Volume pair from the Remote Protection Session.
Usage:
remove-remote-protection-volume-pairs volume-pair-list=<list of
IDs: Name or Index> [ force ]
Example:
remove-remote-protection-volume-pairs
volume-pair-list=["VolPair1", "VolPair2"]
show-remote-protection-volume-pair
The show-remote-protection-volume-pair admin-level command displays the
properties of a Volume pair.
Usage:
show-remote-protection-volume-pair volume-pair-id=<Name or
Index> [ prop-list=<List of property strings> ]
NOTE! The following property is mandatory: [ volume-pair-id ]
Example:
show-remote-protection-volume-pair volume-pair-id=10
show-remote-protection-volume-pairs
The show-remote-protection-volume-pairs admin-level command displays the
properties of all Volume pair of a Remote Protection Session.
Usage:
show-remote-protection-volume-pairs [
protection-session-id=<Name or Index> ]
Example:
show-remote-protection-volume-pairs
Obj-Severity The Volume pair object severity level based on the severity of all
current alerts
modify-remote-protection-snapshot-set
The modify-remote-protection-snapshot-set admin-level command modifies
the name of a Protection Snapshot Set.
Usage:
modify-remote-protection-snapshot-set new-name=<string>
cluster-id=<Name or Index> [ ( snapshot-set-id=<Name or Index>
) ] [ xms-name=<name> ]
NOTE! The following properties are mandatory [cluster-id,
new-name]
NOTE! At least on property from the following list is mandatory
[snapshot-set-id]
NOTE! When providing the cluster index as the cluster-id
parameter, it is required to provide the xms-name parameter as
well; alternatively, it is possible to provide the cluster name
as cluster-id.
Example:
modify-remote-protection-snapshot-set new-name="ProtCopy2"
cluster-id="MyCluster" snapshot-set-id=25
show-remote-protection-snapshot-set
The show-remote-protection-snapshot-set admin-level command displays the
properties of a Remote Protection Session Snapshot Set.
Usage:
show-remote-protection-snapshot-set cluster-id=<Name or Index>
snapshot-set-id=<Name or Index> [ xms-name=<name> ]
NOTE! The following properties are mandatory [ cluster-id,
snapshot-set-id ]
NOTE! When providing the cluster index as the cluster-id
parameter, it is required to provide the xms-name parameter as
well; alternatively, it is possible to provide the cluster name
as cluster-id.
Example:
show-remote-protection-snapshot-set cluster-id="MyCluster"
snapshot-set-id=12
Created-By-App Indicates the application that initiated the creation of the Snapshot
Set
show-remote-protection-snapshot-sets
The show-remote-protection-snapshot-sets admin-level command displays
the PITs of a Remote Protection Session.
Usage:
show-remote-protection-snapshot-sets
protection-session-id=<Name or Index> ( role=<target, source,
both> ) ( cluster-id=<Name or Index> ) [ from-time=<date/time
format e.g. "2018-01-24 09:53:23"> ] [ to-time=<date/time
format e.g. "2018-01-24 09:53:23"> ] [ xms-name=<name> ]
NOTE! The following property is mandatory [
protection-session-id ]
NOTE! Only one property from the following list is allowed [
role ]
NOTE! Only one property from the following list is allowed [
cluster-id ]
NOTE! When providing the cluster index as the cluster-id
parameter, it is required to provide the xms-name parameter as
well; alternatively, it is possible to provide the cluster name
as cluster-id.
Example:
show-remote-protection-snapshot-sets protection-session-id=5
Created-By-App Indicates the application that initiated the creation of the Snapshot
Set
show-remote-protection-consistency-group
The show-remote-protection-consistency-group admin-level command
displays the properties of a Remote Protection Session Consistency Group.
Usage:
show-remote-protection-consistency-group cg-id=<Name or Index>
cluster-id=<Name or Index> [ xms-name=<name> ]
NOTE! The following properties are mandatory [ cg-id,
cluster-id ]
NOTE! When providing the cluster index as the cluster-id
parameter, it is required to provide the xms-name parameter as
well; alternatively, it is possible to provide the cluster name
as cluster-id.
Example:
show-remote-protection-consistency-group cluster-id="MyCluster"
cg-id=5
Last-Refresh-From-Object-N The name of the object used to refresh this Consistency Group
ame
show-remote-protection-consistency-groups
The show-remote-protection-consistency-groups admin-level command
displays the properties of all Remote Protection Session Consistency Groups.
Usage:
show-remote-protection-consistency-groups cluster-id=<Name or
Index> [ xms-name=<name> ]
NOTE! The following property is mandatory [ cluster-id ]
NOTE! When providing the cluster index as the cluster-id
parameter, it is required to provide the xms-name parameter as
well; alternatively, it is possible to provide the cluster name
as cluster-id.
Example:
show-remote-protection-consistency-groups
cluster-id="MyCluster"
Last-Refresh-From-Object-N The name of the object used to refresh this Consistency Group
ame
show-remote-protection-volume
The show-remote-protection-volume admin-level command displays the
properties of a Volume that is a part of a Remote Protection Session.
Usage:
show-remote-protection-volume cluster-id=<Name or Index>
volume-id=<Name or Index> [ xms-name=<name> ]
NOTE! The following properties are mandatory [ volume-id,
cluster-id ]
NOTE! When providing the cluster index as the cluster-id
parameter, it is required to provide the xms-name parameter as
well; alternatively, it is possible to provide the cluster name
as cluster-id.
Example:
show-remote-protection-volume cluster-id="MyCluster"
volume-id=30
Created-From-Volume The Volume that was the Snapshot source for this Volume
Created-By-App The application that created the Volume (XMS, Remote Protection)
Last-Refresh-Time The most recent date and time on which the Volume was refreshed
show-remote-protection-volumes
The show-remote-protection-volumes admin-level command displays the
properties of all Volumes included in a specified Consistency Group that is part of a
Remote Protection Session (can be applied to source cluster or target cluster).
Usage:
show-remote-protection-volumes cg-id=<Name or Index>
cluster-id=<Name or Index> [ xms-name=<Name> ]
NOTE! The following properties are mandatory [cg-id,
cluster-id]
NOTE! When providing the cluster index as the cluster-id
parameter, it is required to provide the xms-name parameter as
well; alternatively, it is possible to provide the cluster name
as cluster-id.
Example:
show-remote-protection-volumes cluster-id="MyCluster"
cg-id="MyCG"
Created-From-Volume The Volume that was the Snapshot source for this Volume
Created-By-Application The application that created the Volume (XMS, Remote Protection)
show-remote-protection-clusters
The show-remote-protection-clusters admin-level command displays all
clusters managed either by local or remote XMS and can be used for Remote Protection.
Usage:
show-remote-protection-clusters
Example:
show-remote-protection-clusters
show-remote-protection-domain
The show-remote-protection-domain admin-level command displays the
replication domain.
Usage:
show-remote-protection-domain
Example:
show-remote-protection-domain
show-remote-protection-ports
The show-remote-protection-ports admin-level command displays all ports
configured as Remote Protection Session targets.
Usage:
show-remote-protection-ports cluster-id=<Name or Index> [
xms-name=<name> ]
NOTE! The following property is mandatory [ cluster-id ]
NOTE! When providing the cluster index as the cluster-id
parameter, it is required to provide the xms-name parameter as
well; alternatively, it is possible to provide the cluster name
as cluster-id.
Example:
show-remote-protection-ports cluster-id="MyCluster"
add-event-handler-definition
The add-event-handler-definition admin-level command adds a new event
handling rule.
Usage:
add-event-handler-definition actions=<List of actions to
perform: email, snmp, syslog> category=<event category list:
'audit', 'state_change', 'hardware', 'user_threshold',
'activity', 'security', 'software'> severity=<severity level
list: 'information', 'clear', 'critical', 'major', 'minor'> [
related-alert-code=<Alert code number> ] [ entity-details=<name
or index> ] [ entity=<string> ] [ disable ] [ enable ]
Example:
add-event-handler-definition category=["audit","hardware"]
actions=["email"] severity=["clear","major"]
modify-event-handler-definition
The modify-event-handler-definition admin-level command modifies an event
handling rule.
Usage:
modify-event-handler-definition event-handler-id=<ID> (
actions=<List of actions to perform: email, snmp, syslog> |
category=<Event category list: 'audit', 'state_change',
’notification’, 'hardware', 'user_threshold', 'activity',
'security', 'software'> | severity=<Severity level list:
'information', 'clear', 'critical', 'major', 'minor'> |
entity=<string> | entity-details=<name or index> |
cluster-id=<name or index> | related-alert-code=<Alert code
number> | disable | enable )
NOTE! The following property is mandatory: event-handler-id
NOTE! At least one property from the following list is
mandatory: actions, category, disable, enable, severity,
entity, entity-details, related-alert-code, cluster-id.
Example:
modify-event-handler-definition event-handler-id=38
severity=["critical","major"] enable
remove-event-handler-definition
The remove-event-handler-definition admin-level command removes an event
handling rule.
Usage:
remove-event-handler-definition event-handler-id=<ID>
Example:
remove-event-handler-definition event-handler-id=11
show-event-handler-definitions
The show-event-handler-definitions admin-level command displays the
existing event handling rules.
Usage:
show-event-handler-definitions
Example
show-event-handler-definitions
ID Event’s ID
show-event-details
The show-event-details admin-level command displays the details of the specified
event.
Usage:
show-event-details event-id=<positive integer> [ full-object ]
Example:
show-event-details event-id=1
User-Location The location (IP address) of the user that invoked the operation
show-events
The show-events admin-level command displays cluster and XMS events.
Usage:
show-events [ cluster-id=<name or index> ] [ vertical ] [
from-event-id=<positive integer> ] [ entity=<string> ] [
from-date-time=<date/time format: "2013-11-23", "2013-11-23
10:14:15", "2013-11-23 10:14:15.123"> ] [ category=<'audit',
'state_change', 'notification' 'hardware', 'user_threshold',
'activity', 'security', 'software'> ] [
severity=<'information', 'clear', 'critical', 'major', 'minor'>
] [ free-text=<text string> ] [ entity-details=<name or index>
] [ limit=<positive integer> ] [ to-date-time=<date/time
format: "2013-11-23", "2013-11-23 10:14:15", "2013-11-23
10:14:15.123"> ] [ prop-list=<List of property strings> ]
Example:
show-events
acknowledge-alert
The acknowledge-alert admin-level command acknowledges an active alert.
Usage:
acknowledge-alert alert-id=<name or index>
Example:
acknowledge-alert alert-id=1
modify-alert-definition
The modify-alert-definition admin-level command modifies the default
parameters of a defined alert type.
Usage:
modify-alert-definition alert-type=<Alert Type> (
send-to-call-home=<Send SYR notification upon raise> |
severity=<'information', 'clear', 'critical', 'major', 'minor'>
| activity-mode=<'disabled', 'enabled'> |
clearance-mode=<'auto_clear', 'ack_required'> |
threshold=<range 0-100> )
NOTE! At least one property from the following list is
mandatory: activity-mode, clearance-mode, severity,
send-to-call-home, threshold.
Example:
modify-alert-definition alert-type="disk_empty"
activity-mode=enabled threshold=80
show-alert-definitions
The show-alert-definitions admin-level command displays a list of pre-defined
alerts and their definitions.
Usage:
show-alert-definitions [ duration=<seconds> ] [
frequency=<seconds> ]
Example:
show-alert-definitions
User-Modified Indicates that the alert definition was modified by the user.
show-alerts
The show-alerts admin-level command displays a list of active alerts and their details.
Usage:
show-alerts [ duration=<seconds> ] [ cluster-id=<id: name or
index> ] [ frequency=<seconds> ] [ filter=<> ] [
prop-list=<list of property strings> ]
Example:
show-alerts
Raise-Time The date and time on which the alert was raised
show-advisory-notice
The show-advisory-notice admin-level command displays the details of the
specified Advisory Notice.
Usage:
show-advisory-notice advisory-notice-id=<name or index> [
duration=<seconds> ] [ cluster-id=<id: name or index> ] [
frequency=<seconds> ] [ vertical ]
Example:
show-advisory-notice advisory-notice-id=12 vertical
Creation-Time The date and time on which the Advisory Notice was created
show-advisory-notices
The show-advisory-notices admin-level command displays a list of outstanding
Advisory Notices and their details.
Usage:
show-advisory-notices [ all ] [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter ] [ prop-list=<List of property strings> ]
Example:
show-advisory-notices all
Creation-Time The date and time on which the Advisory Notice was created
acknowledge-advisory-notice
The acknowledge-advisory-notice admin-level command acknowledges an
Advisory Notice.
Usage:
acknowledge-advisory-notice advisory-notice-id=<name or index>
[ cluster-id=<id: name or index> ]
Example:
acknowledge-advisory-notice advisory-notice-id=1
refresh-advisory-notices
The refresh-advisory-notices admin-level command queries for new Advisory
Notices and refreshes the displayed list.
Usage:
refresh-advisory-notices [ cluster-id=<id: name or index> ]
Example:
refresh-advisory-notices cluster-id=1
Performance
modify-performance-data-collection
The modify-performance-data-collection admin-level command modifies the
Performance Data Collection mode of specified Volumes.
Usage:
modify-performance-data-collection-mode
collection-mode=<enabled, inherit_cluster_mode> vol-list=<list
of ids: name or index> [ cluster-id=<name or index> ]
Note! The following properties are mandatory: collection-mode,
vol-list
vol-list=["vol1","testvol"]
export-performance-history
The export-performance-history admin-level command exports the cluster’s
performance history to CSV file. The exported data can be up to seven days back. Records
interval is five seconds.
Usage:
export-performance-history [ utc ] [ filename=<string> ] [
cluster-id=<name or index> ]
Field Description
Write-BW (KB) The total Write Bandwidth (in KB) over the sampling
period
Read-BW (KB) The total Read Bandwidth (in KB) over the sampling
period
Write-Latency (usec) The average write latency over the sampling period
Read-Latency (usec) The average read latency over the sampling period
Example:
export-performance-history filename="historyBrik1" utc
show-clusters-performance
The show-clusters-performance admin-level command displays clusters’
performance data.
Usage:
show-clusters-performance [cluster-id=<id: name or index> ] [
duration=<seconds> ] [ frequency=<seconds> ] [ filter=<> ] [
prop-list=<list of property strings> ]
Example:
show-clusters-performance duration=300 frequency=10
Write-BW (MB/s)
Read-BW (MB/s)
Write-IOPS
Read-IOPS
These properties indicate the current Bandwidth/IOPS.
BW (MB/s)
IOPS
Total-Write-IOs
Total-Read-IOs
show-clusters-performance-latency
The show-clusters-performance-latency admin-level command displays
clusters’ performance latency data. The command’s output is broken-down by I/O size.
Usage:
show-clusters-performance-latency [cluster-id=<id: name or
index> ] [ duration=<seconds> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<List of property strings> ]
Example:
show-clusters-performance-latency
show-clusters-performance-small
The show-clusters-performance-small admin-level command displays clusters’
performance data for small blocks.
Note: Small blocks refer to blocks smaller than 16KB for X2 cluster type and smaller than
8KB for X1 cluster type.
Usage:
show-clusters-performance-small [cluster-id=<id: name or index>
] [ duration=<seconds> ] [ frequency=<seconds> ] [ filter=<> ] [
prop-list=<list of property strings> ]
Example:
show-clusters-performance-small
S-Write-BW (MB/s)
S-Read-BW (MB/s)
S-Write-IOPS
S-IOPS
Total-S-Write-IOs
Total-S-Read-IOs
show-clusters-performance-unaligned
The show-clusters-performance-unaligned admin-level command displays
clusters’ performance data for unaligned blocks.
Note: Unaligned blocks refer to blocks unaligned to 16KB offsets for X2 cluster type and to
blocks unaligned to 8KB offsets for X1 cluster type.
Usage:
show-clusters-performance-unaligned [cluster-id=<id: name or
index> ] [ duration=<seconds> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<list of property strings> ]
Example:
show-clusters-performance-unaligned
U-Write-BW (MB/s)
U-Read-BW (MB/s)
U-Write-IOPS
These properties indicate the current Bandwidth/IOPS of I/Os
U-Read-IOPS
which are not aligned with 16KB for X2 cluster type or not aligned
with 8KB for X1 cluster type when a single host I/O request results
U-BW (MB/s)
in multiple internal requests.
U-IOPS
Total-U-Write-IOs
Total-U-Read-IOs
show-initiator-groups-performance
The show-initiator-groups-performance admin-level command displays
Initiator Groups’ performance data.
Usage:
show-initiator-groups-performance [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<List of property strings> ]
Example:
show-initiator-groups-performance
Write-BW (MB/s)
Write-IOPS
Read-BW (MB/s)
Read-IOPS
BW (MB/s)
These properties indicate current Bandwidth/IOPS and exceeded
IOPS Bandwidth/IOPS.
Total-Write-IOs
Total-Read-IOs
QOS-Exceeded-BW
QOS-Exceeded-IOPS
show-initiator-groups-performance-small
The show-initiator-groups-performance-small admin-level command
displays Initiator Groups’ performance data for small blocks.
Note: Small blocks refer to blocks smaller than 16KB for X2 cluster type and smaller than
8KB for X1 cluster type.
Usage:
show-initiator-groups-performance-small [ duration=<seconds> ]
[ cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<List of property strings> ]
Example:
show-initiator-groups-performance-small
S-Write-BW (MB/s)
S-Write-IOPS
S-Read-BW (MB/s)
S-IOPS
Total-S-Write-IOs
Total-S-Read-IOs
show-initiator-groups-performance-unaligned
The show-initiator-groups-performance-unaligned admin-level command
displays Initiator Groups’ performance data for unaligned blocks.
Note: Unaligned blocks refer to blocks unaligned to 16KB offsets for X2 cluster type and to
blocks unaligned to 8KB offsets for X1 cluster type.
Usage:
show-initiator-groups-performance-unaligned [
duration=<seconds> ] [ cluster-id=<id: name or index> ] [
frequency=<seconds> ] [ filter=<> ] [ prop-list=<List of
property strings> ]
Example:
show-initiator-groups-performance-unaligned
U-Write-BW (MB/s)
U-Write-IOPS
U-Read-BW (MB/s)
These properties indicate the current Bandwidth/IOPS of I/Os
U-Read-IOPS
which are not aligned with 16KB for X2 cluster type or not aligned
U-BW (MB/s) with 8KB for X1 cluster type when a single host I/O request results
in multiple internal requests.
U-IOPS
Total-U-Write-IOs
Total-U-Read-IOs
show-initiators-performance
The show-initiators-performance admin-level command displays Initiators’
performance data.
Usage:
show-initiators-performance [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<list of property strings> ]
Example:
show-initiators-performance
Write-BW (MB/s)
Write-IOPS
Read-BW (MB/s)
IOPS
Total-Write-IOs
Total-Read-IOs
show-initiators-performance-small
The show-initiators-performance-small admin-level command displays
Initiators’ performance data for small block sizes.
Note: Small blocks refer to blocks smaller than 16KB for X2 cluster type and smaller than
8KB for X1 cluster type.
Usage:
show-initiators-performance-small [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter ]
Example:
show-initiators-performance-small
S-Write-BW (MB/s)
S-Write-IOPS
S-Read-BW (MB/s)
S-IOPS
Total-S-Write-IOs
Total-S-Read-IOs
show-initiators-performance-unaligned
The show-initiators-performance-unaligned admin-level command displays
Initiators’ performance data for unaligned data block.
Note: Unaligned blocks refer to blocks unaligned to 16KB offsets for X2 cluster type and to
blocks unaligned to 8KB offsets for X1 cluster type.
Usage:
show-initiators-performance-unaligned [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<List of property strings> ]
Example:
show-initiators-performance-unaligned
u-Write-BW (MB/s)
u-Write-IOPS
u-Read-BW (MB/s)
These properties indicate the current Bandwidth/IOPS of I/Os
u-Read-IOPS
which are not aligned with 16KB for X2 cluster type or not aligned
with 8KB for X1 cluster type when a single host I/O request results
u-BW (MB/s)
in multiple internal requests.
u-IOPS
Total-U-Write-IOs
Total-U-Read-IOs
show-ssds-performance
The show-ssds-performance admin-level command displays SSDs’ performance
data.
Usage:
show-ssds-performance [ duration=<seconds> ] [ cluster-id=<id:
name or index> ] [ frequency=<seconds> ] [ filter=<> ] [
prop-list=<list of property strings> ]
Example:
show-ssds-performance
Write-BW (MB/s)
Read-BW (MB/s)
Write-IOPS
These properties indicate the current Bandwidth/IOPS.
Read-IOPS
BW (MB/s)
IOPS
show-target-groups-performance
The show-target-groups-performance admin-level command displays Target
Groups’ performance data.
Usage:
show-target-groups-performance [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<List of property strings> ]
Example:
show-target-groups-performance
Write-BW (MB/s)
Read-BW (MB/s)
Write-IOPS
Read-IOPS
These properties indicate the current Bandwidth/IOPS.
BW (MB/s)
IOPS
Total-Write-IOs
Total-Read-IOs
show-target-groups-performance-small
The show-target-groups-performance-small admin-level command displays
Target Groups’ performance data for small blocks.
Note: Small blocks refer to blocks smaller than 16KB for X2 cluster type and smaller than
8KB for X1 cluster type.
Usage:
show-target-groups-performance-small [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<List of property strings> ]
Example:
show-target-groups-performance-small
S-Write-BW (MB/s)
S-Read-BW (MB/s)
S-Write-IOPS
S-IOPS
Total-S-Write-IOs
Total-S-Read-IOs
show-target-groups-performance-unaligned
The show-target-groups-performance-unaligned admin-level command
displays Target Groups’ performance data for unaligned blocks.
Note: Unaligned blocks refer to blocks unaligned to 16KB offsets for X2 cluster type and to
blocks unaligned to 8KB offsets for X1 cluster type.
Usage:
show-target-groups-performance-unaligned [ duration=<seconds> ]
[ cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<List of property strings> ]
Example:
show-target-groups-performance-unaligned
U-Write-BW (MB/s)
U-Read-BW (MB/s)
U-Write-IOPS
These properties indicate the current Bandwidth/IOPS of I/Os
U-Read-IOPS
which are not aligned with 16KB for X2 cluster type or not aligned
with 8KB for X1 cluster type when a single host I/O request results
U-BW (MB/s)
in multiple internal requests.
U-IOPS
Total-U-Write-IOs
Total-U-Read-IOs
show-targets-performance
The show-targets-performance admin-level command displays Targets’
performance data.
Usage:
show-targets-performance [ active ] [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<list of property strings> ]
Example:
show-targets-performance
Write-BW (MB/s)
Read-BW (MB/s)
Write-IOPS
Read-IOPS
These properties indicate the current Bandwidth/IOPS.
BW (MB/s)
IOPS
Total-Write-IOs
Total-Read-IOs
show-targets-performance-small
The show-targets-performance-small admin-level command displays Targets’
performance data for small blocks.
Note: Small blocks refer to blocks smaller than 16KB for X2 cluster type and smaller than
8KB for X1 cluster type.
Usage:
show-targets-performance-small [ active ] [ duration=<seconds>
] [ cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<List of property strings> ]
Example:
show-targets-performance-small
S-Write-BW (MB/s)
S-Read-BW (MB/s)
S-Write-IOPS
S-IOPS
Total-S-Write-IOs
Total-S-Read-IOs
show-targets-performance-unaligned
The show-targets-performance-unaligned admin-level command displays
Targets’ performance data for unaligned blocks.
Note: Unaligned blocks refer to blocks unaligned to 16KB offsets for X2 cluster type and to
blocks unaligned to 8KB offsets for X1 cluster type.
Usage:
show-targets-performance-unaligned [ active ] [
duration=<seconds> ] [ cluster-id=<id: name or index> ] [
frequency=<seconds> ] [ filter=<> ] [ prop-list=<List of
property strings> ]
Example:
show-targets-performance-unaligned
U-Write-BW (MB/s)
U-Read-BW (MB/s)
U-Write-IOPS
These properties indicate the current Bandwidth/IOPS of I/Os
U-Read-IOPS which are not aligned with 16KB for X2 cluster type or not aligned
with 8KB for X1 cluster type when a single host I/O request results
U-BW (MB/s)
in multiple internal requests.
U-IOPS
Total-U-Write-IOs
Total-U-Read-IOs
show-volumes-performance
The show-volumes-performance admin-level command displays the Volumes’
performance data.
Usage:
show-volumes-performance [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<List of property strings> ]
Example:
show-volumes-performance cluster-id=1
Write-BW (MB/s)
Read-BW (MB/s)
Write-IOPS
Read-IOPS
BW (MB/s)
IOPS
Total-Write-IOs
These properties indicate current Bandwidth/IOPS, exceeded
Total-Read-IOs Bandwidth/IOPS and Replication Bandwidth/IOPS.
QOS-Exceeded-BW
QOS-Exceeded-IOPS
Rep-Read-IOPS
Rep-Write-IOPS
Rep-Read-BW (Kbps)
show-volumes-performance-small
The show-volumes-performance-small admin-level command displays the
Volumes’ performance data for small blocks.
Note: Small blocks refer to blocks smaller than 16KB for X2 cluster type and smaller than
8KB for X1 cluster type.
Usage:
show-volumes-performance-small [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ]
Example:
show-volumes-performance-small cluster-id=1
S-Write-BW (MB/s)
S-Read-BW (MB/s)
S-Write-IOPS
S-IOPS
Total-S-Write-IOs
Total-S-Read-IOs
show-volumes-performance-unaligned
The show-volumes-performance-unaligned admin-level command displays the
Volumes’ performance data for unaligned blocks.
Note: Unaligned blocks refer to blocks unaligned to 16KB offsets for X2 cluster type and to
blocks unaligned to 8KB offsets for X1 cluster type.
Usage:
show-volumes-performance-unaligned [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<list of property strings> ]
Example:
show-volumes-performance-unaligned cluster-id=1
U-Write-BW (MB/s)
U-Read-BW (MB/s)
U-Write-IOPS
These properties indicate the current Bandwidth/IOPS of I/Os
U-Read-IOPS
which are not aligned with 16KB for X2 cluster type or not aligned
with 8KB for X1 cluster type when a single host I/O request results
U-BW (MB/s)
in multiple internal requests.
U-IOPS
Total-U-Write-IOs
Total-U-Read-IOs
show-consistency-groups-performance
The show-consistency-groups-performance admin-level command displays the
Consistency Groups’ performance data.
Usage:
show-consistency-groups-performance [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<List of property strings> ]
Example:
show-volumes-performance cluster-id=1
Write-BW (MB/s)
Write-IOPS
Read-BW (MB/s)
Read-IOPS
BW (MB/s)
IOPS
Read-Latency (usec)
Write-Latency (usec) These properties indicate the current Bandwidth/IOPS and latency.
Avg-Latency (usec)
Total-Write-IOs
Total-Read-IOs
Total-Writes
Total-Reads
QOS-Exceeded-BW
QOS-Exceeded-IOPS
show-data-protection-groups-performance
The show-data-protection-groups-performance admin-level command
displays XDP groups performance information.
Usage:
show-data-protection-groups-performance [ duration=<seconds> ]
[ cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<List of property strings> ]
Example:
show-data-protection-groups-performance
Write-BW (MB/s)
Read-BW (MB/s)
Write-IOPS
These properties indicate the current Bandwidth/IOPS.
Read-IOPS
BW (MB/s)
IOPS
show-remote-protection-sessions-performance
The show-remote-protection-sessions-performance admin-level command
displays Remote Protection performance information.
Usage:
show-remote-protection-sessions-performance [
duration=<seconds> ] [ cluster-id=<Name or Index> ] [
frequency=<seconds> ] [ filter=<> ] [ prop-list=<List of
property strings> ]
Example:
show-remote-protection-sessions-performance
Lag (sec) The time that passed since the last consistent PIT was replicated (in
seconds)
Current-Protection-Window- The actual protection time frame (in days) for which the copies exist
Duration-In-Days
Cycle-Duration (sec) Duration of the current Remote Protection Session cycle in seconds
Cycle-Time-Remaining (sec) Number of seconds that remains for the current Remote Protection
Session cycle
Last-Cycle-Start-Time The start time of the last completed Remote Protection Session
cycle
Last-Cycle-Full-Pages The number of full pages handled during the last completed
Remote Protection Session cycle
Last-Cycle-Num-Hash-Pages The number of hash pages handled during the last completed
Remote Protection Session cycle
Last-Cycle-Link-BW (KB/s) The total link bandwidth during the last completed Remote
Protection Session cycle
Last-Cycle-Number The last cycle that was fully completed (transmitted to the target)
Last-Cycle-Num-Short-Hash- The total number of short hash mismatches in the last completed
Mismatch Remote Protection Session cycle
Last-Cycle-Total-Pages The total number of pages sent during the last completed Remote
Protection Session cycle
Last-Cycle-Num-Zero-Pages The number of zero pages handled during the last completed
Remote Protection Session cycle
Last-Cycle-Requests-Sent The total number of requests sent during the last completed
Remote Protection Cycle
Last-Cycle-Requests-Sent-R The rate of sent requests rate during the last completed Remote
ate (Req/s) Protection Cycle
Last-Cycle-Requests-Round- The average request round trip time during the last completed
Trip-Time (usec) Remote Protection Session cycle
Last-Cycle-Requests-Receiv The number of requests received during the last completed Remote
ed Protection Session cycle
Last-Cycle-Requests-Receiv The rate of received requests rate during the last completed Remote
ed-Rate (Req/s) Protection Session cycle
Last-Cycle-Sent (KB) The data sent during the last completed Remote Protection Session
cycle (in KB)
Last-Cycle-Send-Rate (KB/s) The send rate during the last completed Remote Protection Session
cycle
Last-Cycle-Received (KB) The data received during the last completed Remote Protection
Session cycle (in KB)
Last-Cycle-Received-Rate The receive rate during the last completed Remote Protection
(KB/s) Session cycle
A-End-Number-Of-Source-Pi The number of Snapshot Sets currently existing for the source
ts cluster
Z-End-Number-Of-Source-Pit The number of Snapshot Sets currently existing for the target
s cluster
show-remote-protection-targets-performance
The show-remote-protection-targets-performance admin-level command
displays Remote Protection Session targets performance information.
Usage:
show-remote-protection-targets-performance [ duration=<seconds>
] [ cluster-id=<Name or Index> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<List of property strings> ] [ vertical
]
Example:
show-remote-protection-targets-performance
IOPS IOPS
show-remote-protection-ip-links-performance
The show-remote-protection-ip-links-performance admin-level command
displays Remote Protection IP links performance information.
Usage:
show-remote-protection-ip-links-performance [cluster-id=<id:
name or index> ] [ duration=<seconds> ] [ frequency=<seconds> ]
[ filter=<> ] [ prop-list=<List of property strings> ] [
vertical ]
Example:
show-remote-protection-ip-links-performance
show-ssd-sas-error-counters
The show-ssd-sas-error-counters admin-level command displays the list of
diagnostic counters that can indicate problems in the SAS link between the DAE Row
Controller and a specified SSD.
Usage:
show-ssd-sas-error-counters ssd-id=<name or index> [
duration=<seconds> ] [ cluster-id=<id: name or index> ] [
frequency=<seconds> ]
Example:
show-ssd-sas-error-counters ssd-id="wwn-0x5000cca04e05faa0"
show-storage-controllers-sas-error-counters
The show-storage-controllers-sas-error-counters admin-level command
displays a list of diagnostic counters that can indicate problems in the SAS link between
the DAE Controller and the specified Storage Controller.
Usage:
show-storage-controllers-sas-error-counters [
duration=<seconds> ] [ sc-id=<id: name or index> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<list of property strings> ]
Example:
show-storage-controllers-sas-error-counters [
duration=<seconds> ] [ sc-id=<id: name or index> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ]
show-storage-controllers-infiniband-error-counters
The show-storage-controllers-infiniband-error-counters admin-level
command displays the Storage Controllers’ InfiniBand error counters.
Usage:
show-storage-controllers-infiniband-error-counters [
duration=<seconds> ] [ cluster-id=<id: name or index> ] [
frequency=<seconds> ] [ vertical ] [ filter=<> ] [
prop-list=<List of property strings> ]
Example:
show-storage-controllers-infiniband-error-counters
Symb-Errs
Symb-Errs-pm
Symb-Errs-pl
Recovers
Recovers-pm
Recovers-pl
Lnk-Downed
Lnk-Downed-pm
Lnk-Downed-pl
Rcv-Errs-pl
Rmt-Phys-Errs
Rmt-Phys-Errs-pm
Rmt-Phys-Errs-pl
Integ-Errs
Integ-Errs-pm
Integ-Errs-pl
show-infiniband-switches-ports-error-counters
The show-infiniband-switches-ports-error-counters admin-level
command displays status of the InfiniBand Switches' ports error counters.
Usage:
show-infiniband-switches-ports-error-counters [
duration=<seconds> ] [ cluster-id=<id: name or index> ] [
frequency=<seconds> ] [ vertical ] [ filter=<> ] [
prop-list=<List of property strings> ]
Example:
show-storage-controllers-infiniband-error-counters
Last-Day-Num-Faults The number of ports that were disabled during the last day
IB-Symb-Errs
IB-Recovers
IB-Lnk-Downed
These properties correspond to standard InfiniBand Switches ports
IB-Rcv-Errs diagnostic counters.
IB-Rmt-Phys-Errs
IB-Integrity-Errs
IB-Buffer-Overrun-Errs
show-target-groups-fc-error-counters
The show-target-groups-fc-error-counters admin-level command displays
Fibre Channel error counters per Target Group.
Usage:
show-target-groups-fc-error-counters [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
filter=<> ] [ prop-list=<list of property strings> ]
Example:
show-target-groups-fc-error-counters
Cluster-Name The name of the cluster to which the Target Group belongs
show-targets-fc-error-counters
The show-targets-fc-error-counters admin-level command displays Fibre
Channel error counters per Target.
Usage:
show-targets-fc-error-counters [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
vertical ] [ filter=<> ] [ prop-list=<list of property strings>
]
Example:
show-targets-fc-error-counters
show-daes-controllers-sas-error-counters
The show-daes-controllers-sas-error-counters admin-level command
displays a list of diagnostic counters that can indicate problems in the SAS link between
the Storage Controller/DAE Row Controller and the specified DAE Row Controller.
Usage:
show-daes-controllers-sas-error-counters [cluster-id=<cluster
ID>] [ dae-controller-id=<name or index> ] [duration=<number of
minutes>] [frequency=<number of seconds>] [ vertical ]
Example:
show-daes-controllers-sas-error-counters
Cluster-Name The name of the cluster to which the DAE Controller belongs
show-daes-row-controllers-sas-error-counters
Example:
show-daes-row-controllers-sas-error-counters
dae-row-controller-id=1 vertical
Cluster-Name The name of the cluster to which the DAE Row Controller belongs
show-targets-iscsi-counters
The show-targets-iscsi-counters admin-level command displays error counters
information for iSCSI targets.
Usage:
show-targets-iscsi-counters [ duration=<seconds> ] [
cluster-id=<id: name or index> ] [ frequency=<seconds> ] [
vertical ] [ filter=<> ] [ prop-list=<list of property strings>
]
Example:
show-targets-iscsi-counters
show-report
The show-report admin-level command displays the details of a specified report.
Usage:
show-report report-id=<name or index> [prop-list=<> ]
Example:
show-report report-id=1
show-reports
The show-reports admin-level command displays the list of defined reports.
Usage:
show-reports [ prop-list=<List of property strings> ]
Example:
show-reports
show-reports-data
The show-reports-data admin-level command displays detailed report’s data for the
specified entity and category.
Usage:
show-reports-data entity=<string> category=<string> [
to-time=<date/time format: eg. "2013-11-23 10:14:15"> ] [
cluster-id=<name or index> ] [ vertical ] [ granularity=<text
string. auto for best match> ] [ obj-list=<list of ids: name or
index> ] [ time-frame=<text string. to use without from/to> ] [
from-time=<date/time format: eg. "2013-11-23 10:14:15"> ] [
export-to-file=<string> ]
Example:
show-reports-data category=IOPS entity=Volume
obj-list=["vol1","testvol"] from-time="2016-03-03 10:15:16"
export-to-file="iops_vol" granularity=one_hour
Query Commands
query-remote-protection-objects
The query-remote-protection-objects admin-level command provides
customized monitoring data for Remote Protection objects.
Usage:
query-remote-protection-objects class=<IPLink, RSnapSet, RTag,
RVolume, ReplicationDomain, RetentionPolicy, RConsistencyGroup,
RSystem, RTarget, RXMS, ReplicationSession, VolumePair>
cluster-id=<Name or Index> xms-name=<Name> [ obj-list=<List of
ids: Name or Index> ] [ prop-list=<List of property strings> ]
NOTE! The following properties are mandatory: [ class,
cluster-id, xms-name ]
Example:
query-remote-protection-objects class=RetentionPolicy
cluster-id="MyCluster" xms-name="XMS1"