Quantum DXi-Series Command Line Interface (CLI) Guide
6-67081-09 Rev B
February 2014
10
Web Services Support (Optional)
• deleteReplicationTarget (syscli -del targetrep)
• addReplicationTarget (syscli -add targetrep)
• deleteReplicationSource (syscli -del sourcerep)
WSNas Service
Available Operations:
• deleteAllShares (syscli –deleteall share)
• getShare (syscli –get share)
• updateShare (syscli –edit share)
• deleteShare (syscli –del share)
• getShares (syscli –list share)
• getShareNames (syscli –list sharename)
• getShareCount (syscli –getcount share)
• addShare (syscli –add share)
WSSystem Service (System Utility)
Available Operations:
• runCommand (syscli –runcmd)
• getPermissions (syscli –get permission)
• releaseCredential (syscli –release credential)
• authenticate (syscli –authenticate)
How to Run
Unsupported Web
Services Commands
The vast majority of CLI commands are not supported to run over Web Services
in DXi 2.x Software. However, they can be run over WS via the command
syscli --runcmd
because this command is supported for execution over Web
Services.
Consider the command
--list healthcheckstatus
, which is not supported in Web
Services. To understand how it can be run over Web Services, one needs to
understand how the
runcmd
CLI works.
The
runcmd
CLI is very simple. Any CLI command can run directly as is, such as
the following command:
syscli --list healthcheckstatus
However, the command can be run indirectly by specifying it as options to the
runcmd CLI as follows:
syscli --runcmd --list healthcheckstatus
The syntax above runs the
runcmd
CLI, which then parses the options specified
after the “—runcmd” token. Based on these options, the runcmd CLI invokes
the appropriate system API to execute. In the end the effect is executing the
--list healthcheckstatus
command.
Because the
runcmd
CLI is supported over Web Services, it can accept the –ws
option to send the command to a WS server for execution as follows:
syscli --runcmd --list healthcheckstatus --ws [<remotehost>[:<port>]]
