CLI Guide
Table Of Contents
- Dell EMC PowerVault ME4 Series Storage System CLI Guide
- Contents
- Using the CLI
- Categorical list of commands
- Alphabetical list of commands
- abort copy
- abort replication
- abort scrub
- abort verify
- add disk-group
- add host-group-members
- add host-members
- add ipv6-address
- add spares
- add storage
- add volume-group-members
- check firmware-upgrade-health
- check support-assist
- clear cache
- clear disk-metadata
- clear dns-parameters
- clear events
- clear expander-status
- clear fde-keys
- clear fenced-data
- clear replication-queue
- clear support-assist-proxy
- copy volume
- create certificate
- create chap-record
- create host
- create host-group
- create peer-connection
- create replication-set
- create schedule
- create snapshots
- create task
- create user
- create vdisk
- create volume
- create volume-group
- create volume-set
- delete all-snapshots
- delete chap-records
- delete host-groups
- delete hosts
- delete initiator-nickname
- delete peer-connection
- delete pools
- delete remote-system
- delete replication-set
- delete schedule
- delete snapshot
- delete task
- delete user
- delete vdisks
- delete volume-groups
- delete volumes
- dequarantine
- exit
- expand disk-group
- expand vdisk
- expand volume
- fail
- help
- map volume
- meta
- ping
- query peer-connection
- recover replication-set
- release volume
- remove disk-groups
- remove host-group-members
- remove host-members
- remove ipv6-address
- remove spares
- remove volume-group-members
- replicate
- rescan
- reset all-statistics
- reset controller-statistics
- reset disk-error-statistics
- reset disk-group-statistics
- reset disk-statistics
- reset dns-management-hostname
- reset host-link
- reset host-port-statistics
- reset pool-statistics
- reset smis-configuration
- reset snapshot
- reset vdisk-statistics
- reset volume-statistics
- restart mc
- restart sc
- restore defaults
- resume replication-set
- rollback volume
- scrub disk-groups
- scrub vdisk
- scrub volume
- send support-assist-logs
- set advanced-settings
- set chap-record
- set cli-parameters
- set cloud-iq
- set controller-date
- set debug-log-parameters
- set disk
- set disk-group
- set disk-parameters
- set dns-management-hostname
- set dns-parameters
- set email-parameters
- set enclosure
- set expander-fault-isolation
- set expander-phy
- set fde-import-key
- set fde-lock-key
- set fde-state
- set host
- set host-group
- set host-parameters
- set host-port-mode
- set initiator
- set ipv6-network-parameters
- set iscsi-parameters
- set led
- set network-parameters
- set ntp-parameters
- set password
- set peer-connection
- set pool
- set prompt
- set protocols
- set replication-set
- set schedule
- set snapshot-space
- set snmp-parameters
- set support-assist
- set support-assist-info
- set support-assist-proxy
- set syslog-parameters
- set system
- set task
- set user
- set vdisk
- set volume
- set volume-cache-parameters
- set volume-group
- show advanced-settings
- show cache-parameters
- show certificate
- show chap-records
- show cli-parameters
- show cloud-iq
- show configuration
- show controller-date
- show controllers
- show controller-statistics
- show debug-log-parameters
- show disk-groups
- show disk-group-statistics
- show disk-parameters
- show disks
- show disk-statistics
- show dns-management-hostname
- show dns-parameters
- show email-parameters
- show enclosures
- show events
- show expander-status
- show fan-modules
- show fans
- show fde-state
- show fenced-data
- show frus
- show host-groups
- show host-phy-statistics
- show host-port statistics
- show initiators
- show inquiry
- show ipv6-addresses
- show ipv6-network-parameters
- show iscsi-parameters
- show license
- show maps
- show network-parameters
- show ntp-status
- show peer-connections
- show pools
- show pool-statistics
- show ports
- show power-supplies
- show protocols
- show provisioning
- show redundancy-mode
- show refresh-counters
- show remote-systems
- show replication-sets
- show replication-snapshot-history
- show sas-link-health
- show schedules
- show sensor-status
- show service-tag-info
- show sessions
- show shutdown-status
- show snapshot-space
- show snapshots
- show snmp-parameters
- show support-assist
- show syslog-parameters
- show system
- show system-parameters
- show tasks
- show tiers
- show tier-statistics
- show unwritable-cache
- show users
- show vdisks
- show vdisk-statistics
- show versions
- show volume-copies
- show volume-groups
- show volume-names
- show volume-reservations
- show volume-statistics
- show volumes
- shutdown
- suspend replication-set
- test
- trust
- unfail controller
- unmap volume
- verify disk-groups
- verify links
- verify vdisk
- API basetype properties
- adapt-expand-preview
- advanced-settings-table
- cache-parameter
- cache-settings
- certificate-status
- chap-records
- cli-parameters
- cloud-iq
- code-load-readiness
- code-load-readiness-reasons
- communication-ports
- compact-flash
- contact-information
- controller-cache-parameters
- controllers
- controller-statistics
- copy-volumes
- cs-replicate-tasks
- cs-replication
- cs-replication-set
- current-replication-snapshots
- debug-log-parameters
- disk-groups
- disk-groups-preview
- disk-group-statistics
- disk-group-statistics-paged
- disk-hist-statistics
- disk-statistics
- dns-parameters
- drawers
- drive-parameters
- drive-summary
- drives
- email-parameters
- enclosure-fru
- enclosure-list
- enclosures
- events
- eventsLogs
- expander-ports
- expander-versions
- expanders
- fan
- fan-module-versions
- fan-modules
- fc-port
- fde-state
- fenced-data
- fru-versions
- host
- host-group
- host-group-view
- host-port-statistics
- host-view-mappings
- initiator
- initiator-view
- inquiry
- io-modules
- iom-versions
- ipv6-network-parameters
- iscsi-parameters
- iscsi-port
- license
- local-ports
- local-ports-detail
- log-header-table
- mgmt-hostnames
- midplane-versions
- network-parameters
- ntp-status
- peer-connection-info
- peer-connections
- peer-controllers
- peer-ports
- pool-hist-statistics
- pool-statistics
- pool-summary
- pools
- port
- power-supplies
- product-info
- provisioning
- proxy-information
- psu-versions
- readcache-hist-statistics
- redundancy
- refresh-counters
- remote-ports
- remote-ports-detail
- remote-system
- replication-snapshot-history
- reset-snapshot-tasks
- resettable-statistics
- sas-host-phy-statistics
- sas-port
- sas-status-controller-a
- sas-status-drawer
- schedules
- security-communications-protocols
- sensors
- service-tag-info
- sessions
- show-other-MC-status
- shutdown-status
- sideplanes
- snap-space
- snapshots
- snapshot-with-retention-tasks
- snap-tasks
- snmp-parameters
- spares-preview
- status
- storage-preview
- support-assist
- syslog-parameters
- system
- system-parameters-table
- tasks
- tier-hist-statistics
- tier-statistics
- tier-summary
- tiers
- time-settings-table
- unhealthy-component
- unused-disks-preview
- unwritable-cache
- users
- vdisk-hist-statistics
- vdisk-statistics
- versions
- virtual-disk-summary
- virtual-disks
- volume-groups
- volume-group-view
- volume-group-view-mappings
- volume-names
- volume-reservations
- volumes
- volume-statistics
- volume-view
- volume-view-mappings
- Settings changed by restore defaults
Using JSON API output
The simplest mechanism to handle JSON output is by using either a JavaScript or a Python parser to interpret the data.
The JSON output is organized according to the basetypes defined for the system. All basetype objects are returned in an array.
The JSON object uses the same name for the key as the XML API uses in the name attribute. Objects can also be embedded
inside of other objects are always presented as an array as well. This is different from the XML API where the default output
uses associations. The JSON output always uses a hierarchical presentation of objects to identify relationships between objects.
Each object also has an object-name property that may be used in some cases to identify the object uniquely. For example, the
show versions command uses the object-name property to identify the version for controller A and controller B:
{
"versions":[
{
"object-name":"controller-a-versions",
"sc-cpu-type":"SC-CPU-type",
"bundle-version":"bundle-version",
"bundle-base-version":"bundle-base-version",
"build-date":"Mon Jul 17 14:15:44 MDT 2017",
...
},
{
"object-name":"controller-b-versions",
...
}
],
"status":[
{
"object-name":"status",
"response-type":"Success",
"response-type-numeric":0,
"response":"Command completed successfully. (2017-07-27 10:21:36)",
"return-code":0,
"component-id":"",
"time-stamp":"2017-07-27 10:21:36",
"time-stamp-numeric":1501150896
}
]
}
Other basetypes may use the durable ID to uniquely identify the objects.
Scripting guidelines
When scripting command input, use CLI syntax as defined in this guide. For use with SSH or Telnet, use a space character
between command names, parameters, and their values (as shown throughout this guide). For use with the HTTP or HTTPS
interface, use a ’/’ character instead of a space character between command names, parameters, and their values.
When writing scripts to parse XML API output, use an XML library to parse the data. For parsing, a script should not rely on
ordering, spacing, or column position. To find a specific property, a script should compare property names as it searches through
the data. This allows the script to be compatible with future versions that could potentially add new fields to the output.
CAUTION:
Because API format does not use confirmation prompts, use caution when scripting commands that
may cause data unavailability or data loss.
The output of show commands is intended for monitoring or obtaining the current configuration. Other commands provide
configuration data and display one or more status objects that specify the status of command processing. The last status object
specifies the overall status of the command; other status objects indicate intermediate processing status.
The following example shows the API status object, using the ipa output option:
OBJECT basetype="status" name="status" oid="1"
<PROPERTY name="response-type" type="string">Success</PROPERTY>
<PROPERTY name="response-type-numeric" type="uint32">0</PROPERTY>
<PROPERTY name="response" type="string">Command completed successfully. (2017-07-20
11:38:26)</PROPERTY>
<PROPERTY name="return-code" type="sint32">0</PROPERTY>
<PROPERTY name="component-id" type="string"></PROPERTY>
Using the CLI
15