Dell EMC Storage Systems CLI Guide for PowerStore and UnityXT metro node feature Version 7.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2020 2021 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents Chapter 1: Introduction................................................................................................................. 9 Preface...................................................................................................................................................................................9 Chapter 2: Using the VPlexcli....................................................................................................... 11 Logging in to the CLI...................
capture begin..................................................................................................................................................................... 52 capture end.........................................................................................................................................................................54 capture pause......................................................................................................................................
device mirror-isolation auto-unisolation disable........................................................................................................ 121 device mirror-isolation auto-unisolation enable........................................................................................................122 device mirror-isolation disable......................................................................................................................................
export port summary...................................................................................................................................................... 182 export storage-view addinitiatorport..........................................................................................................................185 export storage-view addport........................................................................................................................................
meta-volume verify-on-disk-consistency................................................................................................................. 248 monitor add-console-sink............................................................................................................................................. 250 monitor add-file-sink.......................................................................................................................................................
storage-volume summary.............................................................................................................................................. 312 storage-volume unbanish...............................................................................................................................................315 storage-volume unclaim.................................................................................................................................................
1 Introduction Topics: • Preface Preface 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.
Table 1. Typographical conventions Bold Used for names of interface elements, such as names of windows, dialog boxes, buttons, fields, tab names, key names, and menu paths (what the user specifically selects or clicks). italic Used for full titles of publications referenced in text. Monospace Used for: ● System code ● System output, such as an error message or script ● Pathnames, filenames, prompts, and syntax ● Commands and options Monospace italic Used for variables.
2 Using the VPlexcli Topics: • • • • • • • Logging in to the CLI Password Policies Logging out from the CLI CLI context tree Context tree searching Navigate the CLI context tree Using CLI commands Logging in to the CLI The metro node command line interface supports all metro node operations. You can access the CLI in the metro node clusters. Use an SSH client, such as PuTTY and OpenSSH, to log in to the interface.
Password Policies The management server uses a Pluggable Authentication Module (PAM) infrastructure to enforce minimum password quality. For more information about technology used for password protection, see the Security Configuration Guide. Note the following: ● Password policies do not apply to users configured using the LDAP server. ● The Password inactive days policy does not apply to the admin account to protect the admin user from account lockouts.
Logging out from the CLI Use the exit command to exit the command line interface from any context. About this task For example: VPlexcli:/clusters> exit Connection closed by foreign host. CLI context tree The CLI is divided into command contexts. Some commands are accessible from all contexts, and are referred to as global commands. The remaining commands are arranged in a hierarchical context tree. These commands can only be executed from the appropriate location in the context tree.
Navigate the CLI context tree Use the cd command to navigate between command contexts.
pushd and popd commands ● Use the pushd directory command to save the current directory, and jump to the specified directory. Once a directory is added to the pushd stack, use the pushd command with no argument to switch back to the previous directory.
P000000003B2017DF-A0-FC02 P000000003B3017DF-B0-FC00 P000000003B3017DF-B0-FC02 P000000003B2017DF-A0-FC03 P000000003B3017DF-B0-FC01 P000000003B3017DF-B0-FC03 VPlexcli:/clusters/cluster-1/exports/ports> ls P000000000482F211-ETH06 P000000000482F211-ETH07 P000000000482F221-ETH06 P000000000482F221-ETH07 P000000000492F211-ETH06 P000000000492F211-ETH07 P000000000492F221-ETH06 P000000000492F221-ETH07 ● The cd command followed by a displays the same information as ls at the context level.
. . . storage-views LicoJ009 LicoJ013 storage-elements extents extent_CX4_Logging_1 Using CLI commands The commands that make up the CLI fall into two groups: ● Global commands that can be used in any context. For example: cd, date, ls, exit, and user. ● Context-specific commands that can be used only in specific contexts. For example, to use the copy command, the context must be /distributed-storage/rule-sets.
q - Exits paging mode. Tab completion Use the Tab key to: ● vplex_c_complete_a_command ● vplex_c_display_valid_contexts_and_commands ● vplex_c_display_command_arguments Complete a command Use the Tab key to automatically complete a path or command until the path or command is no longer unique.
Wildcards The command line interface includes 3 wildcards: ● * - matches any number of characters. ● ? - matches any single character. ● [a|b|c] - matches any of the single characters a or b or c. NOTE: Use the find command with wildcards to find context names and data matching specific patterns in the CLI context tree. See Context Tree Searching for more information. * wildcard Use the * wildcard to apply a single command to multiple objects of the same type (directors or ports).
[a|b|c] wildcard Use the [a|b|c] wildcard to match one or more characters in the brackets. ll engines/engine-1-1/directors/director-1-1-A/hardware/ports/A[0-1] displays only ports with names starting with an A, and a second character of 0 or 1. Names Major components are named as follows: Clusters Metro node local configurations have a single cluster, with a cluster ID of cluster 1. Metro node metro configurations have two clusters with cluster IDs of 1 and 2.
Example 2 In the following example, a single command enables ports in all engines and all directors (A and B) whose name include 0-FC and 1-FC: set /engines/*/directors/*/hardware/ports/*[0-1]-FC*:: enabled true ● ● ● ● ● First * wildcard — All engines in the cluster. Second * wildcard — All directors in the cluster. Third * wildcard — All A-side ports and all B-side ports. The [0-1] limits the selections to all port numbers that start with A0, A1, B0, or B1.
This cluster has 0 storage-volumes which do not have dual paths This cluster has 0 storage-volumes which are not visible from all directors Search command history ● To display the last commands typed, press the up arrow key. ● To search for a command typed in the current CLI session, press Ctrl-r. The reverse search prompt is displayed: (reverse-i-search)'': Type the first letter of the command to search for. After you type the first letter, the search tool displays a list of possible matches.
3 Commands Topics: • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • advadm dismantle alias array claim array forget array re-discover array used-by back-end degraded list back-end degraded recover batch-migrate cancel batch-migrate check-plan batch-migrate clean batch-migrate commit batch-migrate create-plan batch-migrate pause batch-migrate remove batch-migrate resume batch-migrate start batch-migrate summary capture begin capture end capture pause capture repl
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 24 connectivity show connectivity validate-be connectivity validate-local-com connectivity validate-wan-com consistency-group add-virtual-volumes consistency-group choose-winner consistency-group convert-to-local consistency-group create consistency-group destroy consistency-group list-eligible-virtual-volumes consistency-group remove-virtual-volumes consistency-group resolve-conflicting-detach
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • ds rule island-containing ds rule-set copy ds rule-set create ds rule-set destroy ds rule-set what-if ds summary esrs status esrs un-register exec exit export initiator-port discovery export initiator-port register export initiator-port register-host export initiator-port show-logins export initiator-port unregister export port summary export storage-view addinitiatorport export storage-view addp
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 26 ls manifest upgrade manifest version meta-volume attach-mirror meta-volume backup meta-volume create meta-volume destroy meta-volume detach-mirror meta-volume move meta-volume verify-on-disk-consistency monitor add-console-sink monitor add-file-sink monitor collect monitor create monitor destroy monitor get-stats monitor remove-sink monitor stat-list ndu pre-check ndu pre-config-upgrade ndu r
• • • • • • • • • • • • • • • • • • • • • storage-volume list-banished storage-volume list-thin-capable storage-volume resurrect storage-volume summary storage-volume unbanish storage-volume unclaim storage-volume used-by syrcollect tree unalias validate-system-configuration version virtual-volume create virtual-volume destroy virtual-volume expand virtual-volume list-thin virtual-volume re-initialize virtual-volume set-thin-enabled virtual-volume summary wait webserver advadm dismantle Dismantles storage
Description To dismantle a virtual volume, the specified volume must: ● Not be exported to a storage view. ● Not a member of a consistency group virtual volume exported through a storage view or belonging to a consistency group are not eligible to be dismantled. The command skips any volumes that are not eligible for dismantle, prints a message listing skipped volumes, and dismantles those volumes that are eligible. If the --force argument is used, no confirmation is displayed before the dismantle.
alias Creates a command alias. Contexts All contexts. Syntax alias [-n|--name] name [-t|--to] "commands and arguments " Arguments Required arguments [-n|--name] name * ● ● ● The name of the new alias. Up to 63 characters. May contain letters, numbers, and underscores '_'. s Cannot start with a number. [-t|--to] “commands and arguments” * A string of commands and arguments enclosed in quotation marks. This string is invoked when the aliased command is used. * - argument is positional.
Examples Create an alias: VPlexcli:/> alias mon-Dir-1-1-B "cd /monitoring/directors/director-1-1-B" Display a list of aliases: VPlexcli:/> alias Name Description --------------- ------------------------------------------------------? Substitutes the 'help' command. mon-Dir-1-1-B Substitutes the 'cd /monitoring/directors/director-1-1-B' ll Substitutes the 'ls -al' command. quit Substitutes the 'exit' command.
Optional arguments [-m|--mapping-file] mapping file Location of the name mapping file. [-t|--tier] mapping file Add a tier identifier to the storage volumes to be claimed. [-l|--claim] Try to claim unclaimed storage-volumes. [--force] Force the operation without confirmation. Allows the command to be run from a non-interactive script. * - argument is positional. Description Claims and names unclaimed storage volumes for a given array.
--verbose Provides more output during command execution. This might not have any effect for some commands. -r | --retire-logicalunits Retires all logical units before retiring the array. If not specified, the command fails if there are still logical units from the array in the logical-units context on metro node. Required arguments -a | --array= array Specifies the context path of the storage-array to forget.
[-f|--force] Force the operation without confirmation. Allows the command to be run from a non-interactive script. * - argument is positional. Description Manually synchronizes the export state of the target device. Used in two scenarios: ● When the exported LUNs from the target array to metro node are modified. Newer protocol-compliant SCSI devices return a notification code when the exported set changes, and may not require manual synchronization.
from the root context: VPlexcli:/> array re-discover /clusters/cluster-1/storage-elements/storage-arrays/ EMC-0x00000000192601378 --cluster cluster-1 --force from the clusters/cluster context: VPlexcli:/> cd /clusters/cluster-1 VPlexcli:/clusters/cluster-1> array re-discover storage-elements/storage-arrays/ EMC-0x00000000192601378 --force from the individual storage array context: VPlexcli:/> cd /clusters/cluster-1/storage-elements/storage-arrays/ VPlexcli:/clusters/cluster-1/storage-elements/storage-arrays
Syntax array used-by [-a|--array] context-path Arguments [-a|--array] context-path * Specifies the storage-array for which to find users. This argument is not required if the context is the target array. * - argument is positional. Description Displays the components (storage-volumes) that use the specified storage array.
extent_SV1_2 SV1 /clusters/cluster-1/devices/clus1_device1: extent_SV1_3 SV1 /clusters/cluster-1/devices/clus1_dev2: extent_SV1_4 SV1 /clusters/cluster-1/devices/device_6006016061211100d42febba1bade011_1: extent_6006016061211100d42febba1bade011_1 VPD83T3:6006016061211100d42febba1bade011 /distributed-storage/distributed-devices/dev1_source: dev1_source2012Feb16_191413 extent_sv1_1 sv1 /clusters/cluster-1/system-volumes/MetaVol: VPD83T3:6006016022131300de76a5cec256df11 /clusters/cluster-1/system-volumes/MetaV
Arguments Optional arguments [-h|--help] Display the usage for this command. [--verbose] Provides more output during command execution. [-g|--group-by= ] Group degraded I-Ts by the specified field. Supported fields: array, director. Description Lists I-Ts that have degraded performance, and I-Ts that have been isolated manually or isolated due to unstable performance. Examples List all degraded I-Ts grouped by director.
back-end degraded recover Recovers the specified degraded I-Ts. Contexts All contexts. Syntax back-end degraded recover [-h|--help] [--verbose] [-p|--paths= ] [--all] Arguments Optional arguments [-h|--help] Display the usage for this command. [--verbose] Provides more output during command execution. [-p|--paths= ] The degraded I-Ts to recover. Each I-T must be expressed as a pair in the form "(,)". [--all] Recover all currently degraded I-Ts.
Director Director Port Initiator Array Degradation Reason -------------- ------------- -------------------------------------------- -----------------director-1-1-A A1-FC00 0xc00144878bda0800 surry-1 Manually isolated director-1-1-B B1-FC01 0xc00144878bda8900 APM00164919257 Manually isolated Target -----------------0x5000144260321e00 EMC-Invista-rc0x5006016547e01af9 EMC-CLARiiON- See also back-end degraded list batch-migrate cancel Cancels an active migration and returns the source volumes to their state
● ● ● ● ● ● ● batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate commit create-plan pause remove resume start summary batch-migrate check-plan Checks a batch migration plan. Contexts All contexts. Syntax batch-migrate check-plan [-f|--file] pathname Arguments Required arguments [-f|--file] pathname Directory and filename of migration plan file. Relative paths can be used.
In the following example, a migration plan passes the check. VPlexcli:/> batch-migrate check-plan --file migrate.txt Checking migration plan file /temp/migration_plans/migrate.txt. Plan-check passed. See also ● ● ● ● ● ● ● ● ● batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate cancel clean commit create-plan pause remove resume start summary batch-migrate clean Cleans the specified batch migration and deletes the source devices.
For device migrations only, use the optional --rename-targets argument to rename the target device after the source device. If the target device is renamed, the virtual volume on top of it is also renamed if the virtual volume has a systemassigned default name. Without renaming, the target devices retain their target names, which can make the relationship between volumes and devices less evident.
Description Attempts to commit every migration in the batch. Migrations in the batch cannot be committed until all the migrations are complete. If the command encounters an error, the command displays a warning continues until every migration has been processed. The batch migration process inserts a temporary RAID 1 structure above the source devices/extents with the target devices/ extents as an out-of-date leg of the RAID.
[-f|--sources] localdevices * List of local-devices to migrate virtual volumes from. May contain wildcards. [-t|--targets] localdevices * List of local-devices to migrate the source virtual volumes to. May contain wildcards. --file pathname * Directory and filename of migration plan file. Relative paths can be used. If no directory is specified, the default directory is /var/log/VPlex/cli on the management server.
cancelled: no-record: 0 0 5. When all the migrations are complete, use the batch-migrate commit command to commit the migration: VPlexcli:/> batch-migrate commit migrate.txt The source volumes now reside on the target devices. 6. Use batch-migrate clean to clean the migration: VPlexcli:/> batch-migrate clean --rename-targets --file migrate.txt This dismantles the source devices down to their storage volumes and renames the target devices and volumes using the source device names. 7.
Arguments Required arguments --file pathname Directory and filename of migration plan file. Relative paths can be used. If no directory is specified, the default directory is /var/log/VPlex/cli on the management server. Description Pauses every migration in the batch. If the command encounters an error, the command prints a warning and continues until every migration has been processed. You can pause active migrations (a migration that has been started) and resume that migration at a later time.
Arguments Required arguments --file pathname Directory and filename of migration plan file. Relative paths can be used. If no directory is specified, the default directory is /var/log/VPlex/cli on the management server. Description Remove the migration record only if the migration has been committed or canceled. Migration records are in the /data-migrations/device-migrations context. Examples Remove a group of migration jobs.
Arguments Required arguments --file pathname Directory and filename of migration plan file. Relative paths can be used. If no directory is specified, the default directory is /var/log/VPlex/cli on the management server. Description Resumes the given batch migration. If an error is encountered, a warning is printed to the console and the command continues until every migration has been processed. Examples Resume all of the migrations specified in the file BSO_19.
Arguments Required arguments --file pathname * Directory and filename of migration plan file. Relative paths can be used. If no directory is specified, the default directory is /var/log/VPlex/cli on the management server. Optional arguments [-s|transfersize] size Maximum number of bytes to transfer as one operation per device. Specifies the size of read sector designated for transfer in cache. Setting transfer size to a lower value implies more host I/O outside the transfer boundaries.
About transfer-size Transfer-size is the size of the region in cache used to service the migration. The area is globally locked, read at the source, and written at the target. Transfer-size can be as small 40 K, as large as 128 M, and must be a multiple of 4 K. The default recommended value is 128 K. A larger transfer-size results in higher performance for the migration, but may negatively impact front-end I/O. This is especially true for metro node Metro migrations.
Arguments Required arguments --file pathname Directory and filename of migration plan file. Relative paths can be used. If no directory is specified, the default directory is /var/log/VPlex/cli on the management server. Optional arguments [-v|verbose] In addition to the specified migration, displays a summary for any in-progress and paused migrations. Description Displays a summary of the batch migration. If the --verbose option is used, displays in the batch that are in an error state. Table 3.
Examples Display a batch migration: VPlexcli:/> batch-migrate summary migrate.txt Processed 10 migrations from batch migration migrate.txt: committed: 0 complete: 10 in-progress: 0 paused: 0 error: 0 cancelled: 0 no-record: 0 Display a batch migration using the --verbose option: VPlexcli:/> batch-migrate summary batch-migrate2.
Syntax capture begin [-s|session] session name [-c|capture-directory] capture-directory Arguments Required arguments [-s|--session] session name * Name of capture session. Output files from the capture session are named using this value. [-c|--capture-directory] directory * Pathname for the capture directory. Default capture directory: /var/log/ VPlex/cli/capture * - argument is positional.
capture end Ends the current capture session and removes it from the session capture stack. Contexts All contexts. Syntax capture end Description The session at the top of the stack becomes the active capture session. Examples End a capture session. VPlexcli:/clusters/cluster-1> capture end # capture end TestCapture VPlexcli:/clusters/cluster-1> See also ● ● ● ● capture capture capture capture begin pause replay resume capture pause Pauses the current capture session. Contexts All contexts.
Examples Pause a capture session. VPlexcli:/> capture pause See also ● ● ● ● capture capture capture capture begin end replay resume capture replay Replays a previously captured session. Contexts All contexts. Syntax capture replay [-s|-session] session name [-c|--capture-directory] directory Arguments Required arguments [-s|--session] session name * Name of existing capture session. [-c| --capture-directory] directory * Directory where existing captured session is located.
Example Replay a capture session. VPlexcli:/> capture replay TestCapture Attributes: Name Value ---------------------- -------------------------------------------allow-auto-join true auto-expel-count 0 auto-expel-period 0 . . . See also ● ● ● ● capture capture capture capture begin end pause resume capture resume Resumes the current capture session. Contexts All contexts. Syntax capture resume Description Pause/resume operates only on the current capture session.
cd Changes the working directory. Contexts All contexts. Syntax cd [context] Arguments Optional arguments context Change to the specified context. The context can be one of the following: ● context path - The full or relative pathname of the context. ● .. - the parent context of the context you are currently in. ● ... - the root context. ● -(dash) - The context you were in before changing to this context. If you do not specify a context, the cd command changes to the root directory.
cluster add Adds a cluster to a running metro node. Contexts All contexts. Syntax cluster add [-c|--cluster] context path [-t|--to] cluster [-f|--force] Arguments Required arguments [-c|--cluster] context path * Cluster to add. [-t|--to] cluster * Cluster to which the given cluster is added. This is only necessary if the system cannot be automatically determined. Optional arguments [-f|--force] Forces the cluster addition to proceed even if conditions are not optimal. * - argument is positional.
-------------------------------------------------------------cluster-1 1 FNM00103600160 true false cluster-2 2 FNM00103600161 true false Islands: Island ID Clusters ---------------------------1 cluster-1, cluster-2 -------ok ok ok ok See also ● cluster expel ● cluster status ● cluster summary cluster configdump Dumps cluster configuration in an XML format, optionally directing it to a file. Contexts All contexts. In /clusters context, command is configdump.
The XML output includes the DTD to validate the content. Examples Dump cluster-1’s configuration to an .xml file: VPlexcli:/clusters/> configdump -c cluster-1 -f cluster1_config.xml Dump the configuration at cluster-1, navigate to the cli context on the management server, and display the file: VPlexcli:/clusters> configdump --verbose --file /var/log/VPlex/cli/config-dumpcluster-1.txt --cluster cluster-1 VPlexcli:/clusters> exit Connection closed by foreign host.
Arguments Required arguments [-c|--clusters] cluster * The cluster to expel. [-f|--force] Forces the cluster to be expelled. * - argument is positional. Description Cluster expulsion prevents a cluster from participating in a metro node. Expel a cluster when: ● ● ● ● The cluster is experiencing undiagnosed problems. To prepare for scheduled outage. The target cluster, or the WAN over which the rest of the system communicates, is going to be inoperable for a while.
See also ● cluster unexpel cluster forget Tells metro node and Unisphere for metro node to forget the specified cluster. Contexts All contexts. In /clusters context, command is forget. Syntax cluster forget [-c|--cluster] context path [-d|--disconnect] [-f|--force] Arguments Required arguments [-c|--clusters] context path * Cluster to forget.
Examples VPlexcli:/clusters/> cluster forget --cluster cluster-1 --disocnnect --force See also ● ● ● ● cluster cluster cluster cluster add expel status unexpel cluster show-remote-devices Displays the list of remote devices for the specified cluster. Contexts All contexts. Syntax cluster show-remote-devices options cluster Description The command displays the list of remote devices for the specified cluster.
Remote Device ------------------ Virtual Volume -------------- Cluster --------- Views -------- c2_dev c2_dev_vol cluster-1 [View_67] c2_Dr_device0049_2 - - - c2_Dr_device0048_2 - - - c2_Dr_device0047_2 vol2 - - c2_Dr_device0046_2 vol3 cluster-1 [view1, view2] c2_Dr_device0045_2 - - - c2_Dr_device0044_2 - - - c2_Dr_device0043_2 vol4 cluster-2 [view3] c2_Dr_device0042_2 - - - c2_Dr_device0041_2 (181 more) To see all results please run the command with --verbose option.
c2_Dr_device0035_2 - - - c2_Dr_device0034_2 - - - c2_Dr_device0033_2 - - - cluster shutdown Starts the orderly shutdown of all directors at a single cluster. Contexts All contexts. In /clusters context, command is shutdown. Syntax cluster shutdown [-c|--cluster] context path --force Arguments Required arguments [-c|--cluster] context path Cluster to shut down. [-f|--force] Forces the shutdown to proceed.
Because the --force argument was not used, a prompt to continue is displayed. ● The cluster summary commands display the transition to shutdown. ● The ll command in clusters/cluster-n context displays the shutdown cluster. VPlexcli:/> cluster shutdown -c cluster-1 VPlexcli:/> cluster shutdown cluster-1 Warning: Shutting down a VPlex cluster may cause data unavailability. Please refer to the VPlex documentation for the recommended procedure for shutting down a cluster.
See also ● ● ● ● cluster add cluster expel cluster forget director shutdown cluster status Displays a cluster's operational status and health state. Contexts All contexts. Syntax cluster status Description The following table shows the fields displayed in the cluster status command: Table 4. cluster status field descriptions Field Description operational status Operational status of the cluster. During transition periods cluster moves from one operational state to another.
Table 4. cluster status field descriptions (continued) Field Description ● degraded - The cluster is not functioning at an optimal level. This may indicate non-functioning remote virtual volume, unhealthy devices or storage volumes, suspended devices, conflicting director count configuration values, or out-ofdate devices. ● ok - The cluster is functioning normally. ● unknown - Metro node cannot determine the cluster's health state, or the state is invalid.
See also ● cluster summary ● ds summary cluster summary Displays a summary of all clusters and the connectivity between them. Contexts All contexts. In /clusters context, command is summary. Syntax cluster summary Description The following table shows the fields available in the cluster summary output. Table 5. cluster summary field descriptions Field Description Clusters: Name Name of the cluster. Cluster ID For metro node Local, always 1. For metro node Metro, 1 or 2.
Table 5. cluster summary field descriptions (continued) Field Description ● If no meta-volume has been configured, operational status is transitioning. ● unknown - The metro node encountered a problem determining the operational status of the cluster. This may indicate a degraded state, since it usually means that at least one of the directors is not responding or is communicating abnormally. Health State ● critical failure - The cluster is not functioning and may have failed completely.
cluster-2 degraded Islands: Island ID --------1 2 2 43A7DL9 true false ok Clusters --------cluster-1 cluster-2 Display cluster summary for metro node Metro configuration with a cluster expelled: VPlexcli:/> cluster summary Clusters: Name Cluster ID TLA State --------- ---------- ------------------------cluster-1 1 43A5DL9 degraded cluster-2 2 43A7DL9 degraded Islands: Island ID --------1 2 Connected Expelled Operational Status --------- -------- ------------------ true true isolated true t
Examples To manually unexpel a cluster, do the following: 1. Use the cluster summary command to verify that the cluster is expelled. VPlexcli:/> cluster summary Clusters: Name Cluster ID TLA Health State --------- ---------- ------------------------cluster-1 1 FNM00190701072 cluster-2 2 FNM00190701073 Islands: Island ID --------1 Connected Expelled Operational Status --------- -------- ------------------ true true false false ok ok ok ok Clusters -------------------cluster-1, cluster-2 2.
See also ● cluster expel collect-diagnostics Collects the core files from each component, logs, and configuration information from the management server and directors. Contexts All contexts. Syntax collect-diagnostics --local-only Arguments Optional arguments Description --local-only Gathers diagnostics only from the local cluster and directors. -r | --log-range= Range Collect only the logs that are generated in the range specified.
NOTE: On metro node Metro configurations, collect-diagnostics must be invoked from each management server in order to collect complete diagnostics. The management server diagnostics files are only collected for the local cluster. The director diagnostics are retrieved from ALL directors in a metro node Metro unless the --local-only argument is used. All trace files under the folder /cores/nsfw-trace/ on each director will be copied and put in the collected diagnostics.
Example Display the configuration type. VPlexcli:/> configuration get-product-type The cluster is currently configured as a metro node Metro See also ● cluster status ● cluster summary ● version configuration join-clusters Validates WAN connectivity and joins the two clusters. Contexts All contexts. Syntax configuration join-clusters [-i|--remote-ip] remote IP address [-h|--help] Arguments Optional arguments [-i|--remote-ip] remote IP address Specifies the IP address of the remote server.
Verifying island ID Added cluster 'cluster-1' to system (cluster-2). Join Cluster task completed. The clusters are now joined and ready for use. See also ● cluster add ● configuration continue-system-setup ● configuration system-setup configuration metadata-backup Configures and schedules the daily backup of metro node metadata. Contexts All contexts. Syntax configuration metadata-backup Description Selects the volumes to use as backup volumes and creates the initial backup of both volumes.
Example Configure the metro node metadata backup schedule: VPlexcli:/clusters/cluster-1/system-volumes> configuration metadata-backup Configuring Meta-data Backups To configure meta-data backups you will need to select two volumes (78G or greater), preferably on two different arrays. Backups will occur automatically each day, at a time you specify.
See also ● configuration remote-clusters clear-addresses ● configuration show-meta-volume-candidates ● configuration system-setup configuration remote-clusters add-addresses Adds entries to the /clusters/*/connectivity/wan-com::remote-cluster-addresses list. Context All contexts. Syntax configuration remote-clusters add-addresses [-c |--cluster] cluster context [-d |--default] [-r |--remote-cluster] cluster context [-a |--addresses]addresses[, addresses...
See the metro node procedures in the SolVe Desktop for more information on managing WAN-COM IP addresses. Examples Add a cluster 2 address to cluster 1: VPlexcli:/> ls /clusters/cluster-1/connectivity/wan-com /clusters/cluster-1/connectivity/wan-com: Attributes: Name Value ------------------------ --------------------------------------------------discovery-address 224.100.100.100 discovery-port 10000 listening-port 11000 remote-cluster-addresses cluster-2 [192.168.11.
Syntax configuration remote-clusters clear-addresses [-c |--cluster] cluster context [-r |--remote-cluster] cluster context [-a |--addresses] addresses[,addresses] [-h |--help] [--verbose] Arguments Optional arguments Description [-c |--cluster] cluster context * Specifies the cluster whose connectivity configuration is to be modified. Typically the cluster above the current context. [-r | --remote-cluster] cluster context * Specifies the remote-cluster configuration entry to modify.
See also ● configuration remote-clusters add-addresses configuration show-meta-volume-candidates Display the volumes which meet the criteria for a metro node meta volume. Contexts All contexts. Syntax configuration show-meta-volume-candidates Description Candidate volumes are: ● Unclaimed ● At least 78 GB capacityIf ● At least 20 GB capacity CAUTION: If you configure the meta volume on a CLARiiON® array, do not configure the meta volume on the vault drives of the CLARiiON.
VPD83T3:60000970000192601707533031333138 98.5G EMC alive traditional EMC-SYMMETRIX-192601707 VPD83T3:6006016049e02100442c66c8890ee011 80G DGC alive traditional EMC-CLARiiON-FNM00083800068 The log summary for configuration automation has been captured in /var/log/VPlex/cli/ VPlexconfig.log The task summary and the commands executed for each automation task has been captured in /var/log/VPlex/cli/VPlexcommands.
[-f | --force] Arguments Optional arguments Description [-h | --help] Displays the usage for this command. [--verbose] Provides more output during command execution. [-c | --cluster=] cluster The cluster at which to upgrade the slot count of the active meta volume. When specified from within a /clusters/cluster context, the value of that context is used as cluster. The -c or --cluster argument is positional. [-d | --storagevolumes= volume [, volume ...
connect Connects to a director. Contexts All contexts. Syntax connect [-o|--host] [host-name|IP address] --logport port number --secondary-host [host name|IP address] --secondary-logport secondary port number [-n|--name] name [-t|--type] system type [-p|--password] password [-c|--connection-file] filename [-s|--save-authentication] --no-prompt Arguments Optional arguments Description [-o|--host] {host-name|IP address} * Host name or IP address of the director to which to connect. Default: localhost.
* - argument is positional. Description Use the connect command to: ● Re-establish connectivity if connectivity is lost to one or more directors. ● Manually re-connect after a power outage if the management server is not able to connect to the directors. During normal system setup, connections to directors are established and stored in a file: /var/log/VPlex/cli/ connections. Use the connect -c command if the entry for the director exists in the connections file.
connectivity director Displays connections from the specified director through data (non-management) ports. Contexts All contexts. Syntax connectivity director director [-d|--storage-volumes] [-i|--initiators] [-n|--directors] [-f|--file] filename [-s|sort-by][name|wwn|port] Arguments Required arguments director Optional arguments Director to discover. [-d|--storage-volumes] Display connectivity from the specified director to storage volumes.
connectivity list all Displays the initiators, storage volumes, directors, and the targets connected to a director. Contexts /: connectivity list all /engines/*/directors/*/: list all Syntax connectivity list all [-h| --help] [--verbose] [-n| --directors]context path, context path... [-f| ] filename [-d| ] [-i| ] [-v| ] [-t| ] [-s| --sort-by]key Arguments Optional arguments Description [-h | --help] Displays the usage for this command [--verbose] Provides additional output during command execution.
See also ● connectivity list directors ● connectivity list initiators ● connectivity list storage-volumes connectivity list directors Displays the inter-director connections for a director. Contexts /: connectivity list directors /engines/*/directors/*/: list directors Syntax connectivity list directors [-h| --help] [--verbose] [-n| --directors]context path, context path...
connectivity list initiators Displays the initiators connected to directors. Contexts /: connectivity list initiators /engines/*/directors/*/: list initiators Syntax connectivity list directors [-h| --help] [--verbose] [-n| --directors]context path, context path... [-f| ] filename Arguments Optional arguments [-h | --help] Displays the usage for this command [--verbose] Provides additional output during command execution. This may not have any effect for some commands.
connectivity list storage-volumes Displays the storage volumes connected to directors. Contexts /: connectivity list storage-volumes /engines/*/directors/*/: list storage-volumes Syntax connectivity list directors [-h | --help] [--verbose] [-n | --directors]context path, context path... [-f | ] filename [-s | --sort-by] key [-l | --long-luns] Arguments Optional arguments [-h | --help] Displays the usage for this command [--verbose] Provides additional output during command execution.
connectivity show Displays the communication endpoints that can see each other. Contexts All contexts. Syntax connectivity show [-p|--protocol[fc|ib|tcp|udp] [e|--endpoints] port, port,... Arguments Optional arguments Description [-p|--protocol] {ib|tcp|udp} [-p|-protocol] {fc|ib| tcp|udp} Display endpoints with only the specified protocol. Arguments are case-sensitive, and include: ● fc - Fibre Channel. ● ib - InfiniBand. Not supported in the current release.
[-h | --help] --verbose Arguments Optional arguments Description [-h | --help] Displays the usage for this command. [-d| --detailed] Details are displayed first, followed by the summary. --verbose Provides more output during command execution. This may not have any effect for some commands. Description This provides a summary analysis of the back-end connectivity information displayed by connectivity director if connectivity director was executed for every director in the system.
*To meet the high availability requirement for storage volume paths each storage volume must be accessible from each of the directors through 2 or more metro node backend ports, and 2 or more Array target ports, and there should be 2 or more ITLs. Cluster cluster-2 0 storage-volumes which are dead or unreachable. 0 storage-volumes which do not meet the high availability requirement for storage volume paths*. 5019 storage-volumes which are not visible from all directors.
connectivity validate-local-com Validates that the actual connectivity over local-com matches the expected connectivity. Contexts All contexts. Syntax connectivity validate-local-com [-c|--cluster] context path [-e|--show-expected] [-p|--protocol] communication protocol [-h|--help] [--verbose] Arguments Optional arguments Description [-c|--cluster] contextpath path of the cluster where local-com should be validated.
connectivity validate-wan-com Verifies the expected IP and FC WAN COM connectivity. Contexts All contexts. Syntax connectivity validate-wan-com [-e|--show-expected] [-p|--protocol] communication-protocol Arguments Optional arguments [-e|--showexpected] Displays the expected connectivity map instead of comparing it to the actual connectivity. The map is a list of every port involved in the WAN COM network and the ports to which it is expected to have connectivity.
consistency-group add-virtual-volumes Adds one or more virtual volume to a consistency group. Contexts All contexts. In /clusters/cluster-n/consistency-groups/group-name context, command is add-virtual-volumes Syntax consistency-group add-virtual-volumes [-v|--virtual-volumes] virtual-volume, virtual-volume, ... [-g|--consistency-group] consistency-group Arguments Required arguments [-v|--virtual-volumes] virtual-volume,virtual-volume,...
● The consistency-group add-virtual-volumes command adds the specified virtual volume to the consistency group.
Arguments Required arguments [-c|--cluster] cluster *The cluster on which to roll back and resume I/O. [-g|--consistency-group] consistency-group * Context path of the consistency group on which to roll back and resume I/O. Optional arguments [-f|--force] Do not prompt for confirmation. Allows this command to be run using a non-interactive script. * - argument is positional.
Attributes: Name -------------------active-clusters cache-mode detach-rule operational-status passive-clusters read-only recoverpoint-enabled storage-at-clusters virtual-volumes visibility Contexts: Name -----------advanced recoverpoint Value --------------------------------------------------------[] synchronous no-automatic-winner [(cluster-1,{ summary:: suspended, details:: [cluster-departure, rebuilding-across-clusters, restore-link-or-choose-winner] }), (cluster-2,{ summary:: suspended, details:: [clu
consistency-group convert-to-local Converts a distributed consistency group to a local consistency group. context All contexts Syntax convert-to-local [-h | --help] [--verbose] [[-c | --cluster=]cluster-context] [-f | --force] [[-g | --consistency-group=]consistency-group] Arguments Optional arguments -h | --help Displays the usage for this command. --verbose Provides more output during command execution. This may not have any effect for some commands.
[-c|--cluster] cluster Arguments Required arguments [-n|--name] consistency-group name * Name of the new consistency group. Must be unique within a cluster. Name conflicts across s can be resolved by changing the name later using the set name command. [-c|--cluster] cluster Context path of the at which to create the consistency group. If the current context is a cluster or below, that is the default. Otherwise, this argument is required. * - argument is positional.
. VPlexcli:/> cd /clusters/cluster-1/consistency-groups/ VPlexcli:/clusters/cluster-1/consistency-groups> consistency-group create --name TestCG --cluster cluster-1 VPlexcli:/clusters/cluster-1/consistency-groups> ls TestCG test10 test11 test12 test13 test14 test15 test16 test5 test6 test7 test8 test9 vs_RAM_c1wins vs_RAM_c2wins vs_oban005 vs_sun190 VPlexcli:/clusters/cluster-1/consistency-groups> ls TestCG /clusters/cluster-1/consistency-groups/TestCG: Attributes: Name Value ------------------- -----------
Force the operation to continue without confirmation. Allows this command to be run using a non-interactive script. [-f|--force] * - argument is positional. Description Destroys the specified consistency groups. All clusters where the consistency group is visible must be operational in order for the consistency group to be destroyed. All clusters where the consistency group has storage-at-clusters must be operational in order for the consistency group to be destroyed.
Description Displays eligible virtual volumes that can be added to a consistency group. Eligible virtual volumes: ● ● ● ● Must not be a logging volume Have storage at every cluster in the storage-at-clusters property of the target consistency group Are not members of any other consistency group Have no properties (detach rules, auto-resume) that conflict with those of the consistency group. That is, detach and resume properties of either the virtual volume or the consistency group must not be set.
--force Arguments Required arguments [-v|--virtualvolumes] virtualvolume,virtual-volume,... *Glob pattern or a list of one or more comma-separated context paths of the virtual volumes to remove from the consistency group. [-g|--consistencygroup] context path *Context path of the consistency group from which to remove the specified virtual volume. If the current context is a consistency-group or is below, then that consistency group is the default. Otherwise, this argument is required.
dr1_C12_0922_vol] . . . See also ● consistency-group create ● consistency-group destroy ● Dell EMC Administration Guide for metro node consistency-group resolve-conflicting-detach Select a winning cluster on a consistency group on which there has been a conflicting detach. Contexts All contexts. In /clusters/cluster-n/consistency-groups/group-name context, command is resolve-conflictingdetach.
When the inter-cluster link is restored, the clusters learn that I/O has proceeded independently. I/O continues at both clusters until the administrator picks a winning cluster whose data image will be used as the source to synchronize the data images. Use this command to pick the winning cluster. For the distributed volumes in the consistency group: ● ● ● ● I/O at the losing cluster is suspended (there is an impending data change) The administrator stops applications running at the losing cluster.
Name ------------------active-clusters cache-mode detach-rule operational-status Value ---------------------------------------------------------[cluster-1, cluster-2] synchronous no-automatic-winner [(cluster-1,{ summary:: ok, details:: [] }), (cluster-2,{ summary:: suspended, details:: [requires-resume-at- loser] })] passive-clusters [] read-only false recoverpoint-enabled false storage-at-clusters [cluster-1, cluster-2] virtual-volumes [dd1_vol, dd2_vol] visibility [cluster-1, cluster-2] Contexts: advan
Description During an inter-cluster link failure, you can permit I/O to resume at one of the two clusters: the “winning” cluster. I/O remains suspended on the “losing” cluster. When the inter-cluster link heals, the winning and losing clusters re-connect, and the losing cluster discovers that the winning cluster has resumed I/O without it. Unless explicitly configured otherwise (using the auto-resume-at-loser property), I/O remains suspended on the losing cluster.
storage-at-clusters [cluster-1, cluster-2] virtual-volumes [dd1_vol, dd2_vol] visibility [cluster-1, cluster-2] Contexts: advanced recoverpoint See also ● consistency-group choose-winner ● consistency-group resume-after-rollback ● Dell EMC Administration Guide for metro node consistency-group set-detach-rule no-automaticwinner Sets or changes the detach-rule for one or more asynchronous consistency groups to no-automatic-winner. Contexts All contexts.
Examples Set the detach-rule for a single consistency group from the group’s context: VPlexcli:/clusters/cluster-1/consistency-groups/TestCG> set-detach-rule no-automaticwinner Set the detach-rule for two consistency groups from the root context: VPlexcli:/> consistency-group set-detach-rule no-automatic-winner -g /clusters/cluster-1/ consistency-groups/TestCG,/clusters/cluster-1/consistency -groups/TestCG2 See also ● ● ● ● ● consistency-group consistency-group consistency-group consistency-group Dell EMC
Optional arguments [-g|--consistencygroup] consistency-group, consistency-group, ... The consistency groups on which to apply the winner detach rule. [-f|--force] Force the operation to continue without confirmation. Allows this command to be run from non-interactive scripts. Description Applies the winner detach rule to one or more specified synchronous consistency groups. NOTE: This command requires user confirmation unless the --force argument is used.
Example Display a summary of unhealthy consistency groups: VPlexcli:/> consistency-group summary 1 consistency groups have status not 'OK'. Consistency Goup Operational Status Status Name ------------------ Detailed ------------------ ------------------ ------------GRP3 Suspended 0 consistency groups have risk of roll back.
Arguments Optional arguments [-c|--context] context-path Context to describe. Examples In the following example, the ll command displays information about a port, and the describe command with no arguments displays additional information. VPlexcli:/clusters/cluster-2/exports/ports/P000000003CB001CB-B1-FC01> ll Name Value ------------------------ -----------------director-id 0x000000003cb001cb discovered-initiators [] . . .
[-r|--rule-set] rule-set [-f|--force] Arguments Required arguments [-d|--device] context-path or device-name * Name or context path of the device to which to attach the mirror. Does not have to be a top-level device. If the device name is used, verify that the name is unique throughout the metro node, including local devices on other clusters. Optional arguments [-m|--mirror] context-path or mirror-name * Name or context path of the mirror to detach. Does not need to be a top-level device.
Homogeneous array requirement for thin volumes To preserve thinness of the new RAID-1 device where the parent device is created on a thin volume and is thin-capable, the mirror device must be created from the same storage-array-family as the parent device. If the user tries to attach a mirror leg from a dissimilar array-family, the command displays a warning that the thin-capability of the RAID-1 device will be lost and it can render the virtual volume to be thin disabled.
Arguments Required arguments [-d|--device] [context-path|devicename] * Name or context path of the device to collapse. Does not have to be a top-level device. If the device name is used, verify that the name is unique throughout the metro node, including local devices on other clusters. * - argument is positional. Description If a RAID 1 device is left with only a single child (after removing other children), use the device collapse command to collapse the remaining structure.
Arguments Required arguments [-d|--device] context-path or devicename * Name or context path of the device from which to detach the mirror. Does not have to be a top-level device. If the device name is used, verify that the name is unique throughout the system, including local devices on other clusters. Optional arguments [-m|--mirror] context-name or mirrorname * Name or context path of the mirror to detach. Does not have to be a top-level device.
Figure 2. Devices and virtual volumes: after detach mirror - no discard If the RAID device supports a virtual volume, and you use the --discard argument, the command: ● ● ● ● Removes the mirror (child device) from the RAID 1 parent device. Makes the detached child a top-level device. Creates no new virtual. Detaches the mirror regardless of its current state and does not guarantee data consistency. Figure 3.
Identify and detach a dead mirror leg from a distributed device. In the following example: ● The ll command in /distributed-storage/distributed-devices context displays a stressed distributed device. ● The ll device-name/distributed-device-components command displays the components of the device (output is truncated) Note the Slot number of the failed leg in the display. ● The device detach-mirror command removes the failed device using the slot number displayed in the previous step.
device mirror-isolation auto-unisolation disable Disables mirror auto-unisolation. Contexts All contexts. Syntax device mirror-isolation auto-unisolation disable [-f|--force] [-h|--help] [--verbose] Arguments Optional arguments [-f|--force] Forces the operation to continue without confirmation. [-h|--help] Displays command line help. [--verbose] Provides more output during command execution. This may not have any effect for some commands.
Shows auto-unisolation was not disabled because the feature is not supported: VPlexcli:/> device mirror-isolation auto-unisolation disable Mirror isolation is not enabled on clusters cluster-1,cluster-2. Mirror isolation provides a mechanism to automatically unisolate mirrors that were previously isolated. When mirror isolation is enabled, this operation will prevent the system from automatically unisolating the underlying storage-volumes once their performance is in the acceptable range.
[--verbose] Provides more output during command execution. This may not have any effect for some commands. Description This command enables auto mirror unisolation. Mirror isolation provides a mechanism to automatically unisolate mirrors that were previously isolated. When mirror isolation is enabled, auto-unisolation allows the system to automatically unisolate the underlying storage-volumes once their performance is in the acceptable range.
● ● ● ● device device device Dell EMC mirror-isolation disable mirror-isolation enable mirror-isolation show Administration Guide for metro node device mirror-isolation disable Disables mirror isolation on the specified clusters. Contexts All contexts. Syntax device mirror-isolation disable [-c|--clusters] context-path [, context-path...
Continue to disable mirror isolation on cluster-1,cluster-2? (Yes/No) Yes Mirror isolation has been disabled on 'cluster-1'. Mirror isolation has been disabled on 'cluster-2'. Disable mirror isolation on all clusters without being prompted to confirm: VPlexcli:/> device mirror-isolation disable -f WARNING: Disabling the mirror isolation feature will prevent metro node from improving the performance of a RAID-1 device containing a poorly performing mirror leg.
device mirror-isolation enable Enables mirror isolation on the specified clusters. Contexts All contexts. Syntax device mirror-isolation enable [-c|--clusters] context-path [, context-path...] [--also-enable-autounisolation] [-h|--help] [--verbose] Arguments Optional arguments [-c|--clusters] context-path [, contextpath...] Specifies the list of clusters on which to enable mirror isolation. [--also-enable-autounisolation] Enables auto-unisolation if specified. [-h|--help] Displays command line help.
Enable mirror isolation on one cluster: VPlexcli:/> device mirror-isolation enable -c cluster-1 Mirror isolation has been enabled on 'cluster-1'. Attempt to enable mirror-isolation on the clusters when it is already enabled: VPlexcli:/> device mirror-isolation enable Mirror isolation has been enabled on 'cluster-1'. Mirror isolation has been enabled on 'cluster-2'.
Syntax device mirror-isolation show [-c|--clusters] context-path [, context-path...] [-h|--help] [--verbose] Arguments Optional arguments [-c|--clusters] context-path [, context-path...] Specifies the list of clusters on which to show mirror isolation configuration parameters. [-h|--help] Displays command line help. [--verbose] Provides more output during command execution. This may not have any effect for some commands.
--------cluster-1 cluster-2 ------true true ---------------false false -----------------60 60 -------------------14400 14400 Shows the mirror isolation configuration parameters on one cluster: VPlexcli:/> device mirror-isolation show -c cluster-1 Cluster Enabled Auto unisolation Isolation Interval --------- ------- ---------------- -----------------cluster-1 true false 60 Unisolation Interval -------------------14400 Shows the command executed on an invalid cluster: VPlexcli:/> device mirror-isolatio
[-f|--force] Arguments Optional arguments [-c|--cluster] context path Resume I/O on the specified cluster and the clusters it is in communication with during a link outage. Applicable only when the all-at-island argument is used or when the specified devices are distributed devices. Not required for local devices with global visibility. [-r|--devices] context path or device-name Name or context path of the devices for which to resume I/O. They must be top-level devices.
See also ● device resume-link-up ● ds dd declare-winner device resume-link-up Resumes I/O on suspended top level devices, virtual volumes, or all virtual volumes in the metro node. Contexts All contexts. Syntax device resume-link-up [-r|--devices] context path,context path... [-v|--virtual-volumes] context path,context path... [-a|--all] [-f|--force] Arguments Optional arguments [-r|--devices] context path, context path...
Example Resume I/O on two specified devices: VPlexcli:/distributed-storage/distributed-devices> device resume-link-up --devices CLAR0014_LUN17_1, CLAR0014_LUN18_1 –-force Resume I/O on a specified virtual volume: VPlexcli:/> device resume-link-up --virtual-volumes /clusters/cluster-1/virtual-volumes/ ESX_DataStore1_vol --force Resume I/O on all virtual volumes in the losing cluster: VPlexcli:/> device resume-link-up --all -–force See also ● device mirror-isolation disable device resurrect-dead-storage-vol
node mirror leg. After resolving the underlying issue that lead to an out of space error, use this command to resume I/O for supporting storage-volumes that have been marked dead. The target devices may be of any geometry, local or distributed. This command executes storage-volume resurrect for all dead-storage-volumes of a device. This scenario should only happen on an XtremIO storage volume that is used as a metro node mirror leg. director commission Starts the director’s participation in the cluster.
Examples Add a director to a running cluster using the default timeout (60 seconds): VPlexcli:/> director commission --director Cluster_1_Dir1A --apply-cluster-settings See also ● director decommission ● version director decommission Decommissions a director. The director stops participating in cluster activities. Contexts All contexts. In /engines/engine/directors context, command is decommission.
director fc-port-stats Displays/resets Fibre Channel port statistics for a specific director. Contexts All contexts. In /engines/engine/directors context, command is fc-port-stats director. In context, command is fc-port-stats Syntax director fc-port-stats [-d|--director] director [-o|--role] role [-r|--reset] Arguments Required arguments [-d|--director] Context path of the director for which to display FC statistics. Not required if the current context director is /engines/engine/directors/director.
Reset the port statistics counters on a director’s Fibre Channel ports from the root context: VPlexcli:/> director fc-port-stats -d director-2-1-A --reset Display a director’s Fibre Channel port statistics from the director context: VPlexcli:/engines/engine-1-1/directors/director-1-1-A> fc-port-stat Results for director 'director-2-1-A' at Fri Feb 10 16:10:15 MST 2012: Port: A1-FC00 A1-FC01 A1-FC02 A1-FC03 A3-FC00 A3-FC01 Frames: - Discarded: 0 0 0 0 0 - Expired: 0 0 0 0 0 0 - Bad CRCs: 0 0 0 0 0 0 - Encodi
Description Show firmware status and version for one or more directors. Table 7. director firmware show-banks field descriptions Field Description Banks Each director has two firmware banks; A and B. Status active - The software in this bank is currently operating on the director. inactive - The software in this bank is not operating on the director. Marked for next reboot no - The software in this bank will not be used the next time the director reboots.
Arguments Required arguments [-n|--director] director-uuid Director ID number. Use the ll command in engines/engine/directors context to display director ID numbers. Description Removes the specified director from the context tree. Deletes all information associated with the director. Examples In the following example: ● The ll command in engines/engine/directors context displays director IDs. ● The director forget command instructs metro node to delete all records pertaining to the specified director.
Arguments Required arguments [-n|--director] director The remote director on which to change the access password. [-c|--current-password] current-password The current access password of the specified director. [-p|--new-password] new-password The new access password to set for the specified director. Description Changes the password for a specified director. director ping Displays the round-trip latency from a given director to the target machine, excluding any metro node overhead.
If ICMP is enabled on the specified director, a series of lines is displayed: service@ManagementServer:~> ping 128.221.252.36 PING 128.221.252.36 (128.221.252.36) 56(84) bytes of data. 64 bytes from 128.221.252.36: icmp_seq=1 ttl=63 time=0.638 ms 64 bytes from 128.221.252.36: icmp_seq=2 ttl=63 time=0.591 ms 64 bytes from 128.221.252.36: icmp_seq=3 ttl=63 time=0.495 ms 64 bytes from 128.221.252.36: icmp_seq=4 ttl=63 time=0.401 ms 64 bytes from 128.221.252.36: icmp_seq=5 ttl=63 time=0.552 ms --- 128.221.252.
Arguments Required arguments [-f|--force] Forces this operation. Optional arguments [-n|--director] context-path * Director to shut down. * - argument is positional. Description Shuts down the director firmware. NOTE: Does not shut down the operating system on the director. After shutdown, state of the director is as follows: ● Power is on. ● Director OS running. ● Director firmware (GeoSynchrony) is stopped. Examples In the following example: ● The director shutdown command shuts down DirA.
director tracepath Displays the route taken by packets from a specified director to the target machine. Contexts All contexts. In /engines/engine/directors context, command is tracepath. Syntax director tracepath [-i|--ip-address] ip-address [-n|--director] director Arguments Required arguments [-i|--ip-address] IPaddress The target's IP address. This address is one of the Ethernet WAN ports on another director. Use the ll port-group command to display the Ethernet WAN ports on all directors.
In engines/engine/directors context, command is uptime. Syntax director uptime Description Uptime measures the time a machine has been up without any downtime.
VPlexcli:/engines/engine-1-1> cd /directors/ VPlexcli:/engines/engine-1-1/directors> dirs [/engines/engine-1-1/directors] See also ● tree disconnect Disconnects one or more connected directors. Contexts All contexts. Syntax disconnect [-n|--directors] context-path, context-path... Arguments Required arguments [-n|--directors] context-path, context-path... List of one or more remote directors from which to disconnect. Entries must be separated by commas.
dm migration cancel Cancels an existing data migration. Contexts All contexts. In all data-migration (device or extent) contexts, command is migration cancel. In data-migrations/extent-migrations context, command is cancel. Syntax dm migration cancel [-m|--migrations] context-path,context-path... [-f|--force] Arguments Required arguments [-m|--migrations] * List of one or more migrations to cancel. Entries must be separated by commas.
See also ● ● ● ● ● dm dm dm dm dm migration migration migration migration migration commit pause remove resume start dm migration clean Cleans a committed data migration. Contexts All contexts. In /data-migrations context, command is migration clean. In /data-migrations/device-migrations context, command is clean. In /data-migrations/extent-migrations context, command is clean. Syntax dm migration clean [-m|--migrations] context-path,context-path...
Without renaming, the target devices retain their target names, which can make the relationship between volume and device less evident. For extent migrations, cleaning destroys the source extent and unclaims the underlying storage volume if there are no extents on it. Examples VPlexcli:/data-migrations/device-migrations> dm migration clean --force --migrations migrate_012 Cleaned 1 data migration(s) out of 1 requested migration(s).
Description The migration process inserts a temporary RAID 1 structure above the source device/extent with the target device/extent as an out-of-date leg of the RAID 1. The migration can be understood as the synchronization of the out-of-date leg (the target). After the migration is complete, the commit step detaches the source leg of the RAID 1 and removes the RAID 1.
* - argument is positional. Description Pause an active migration to release bandwidth for host I/O during periods of peak traffic. Specify the migration by name if that name is unique in the global namespace. Otherwise, specify a full pathname. Use the dm migration resume command to resume a paused migration.
* - argument is positional. Description Before a migration record can be removed, it must be canceled or committed to release the resources allocated to the migration. Example Remove a migration: VPlexcli:/data-migrations/device-migrations> remove -m beta_device_mig1 –f Removed 1 data migration(s) out of 1 requested migration(s).
Use the dm migration resume command to resume a paused migration. Example Resume a paused device migration: VPlexcli:/data-migrations/device-migrations> dm migration resume --migrations migrate_012 See also ● ● ● ● ● dm dm dm dm dm migration migration migration migration migration cancel commit pause remove start dm migration start Starts the specified migration. Contexts All contexts. In /data-migrations context, command is migration start.
[-t|--to] {targetextent|target-device} * The name of target extent or device for the migration. Specify the target device or extent by name if that name is unique in the global namespace. Otherwise, specify a full pathname. Optional arguments [-s|--transfersize] value Maximum number of bytes to transfer per operation per device. A bigger transfer size means smaller space available for host I/O. Must be a multiple of 4 K. Range: 40 KB - 128 M. Default: 128 K.
dm migration start: Evaluation of <> failed. cause: Failed to create a new data-migration. cause: Unable to attach mirror 'SveTest_src_r0_case2_2_0002' to distributed Device 'MIGRATE_cc2'. cause: Firmware command error. cause: Active metadata device does not have a free slot. See the troubleshooting section of the metro node procedures in the SolVe Desktop for instructions on increasing the number of slots.
[-o|--virtual-volume] context-path,context-path... List of one or more virtual volumes to drill down. Entries must be separated by commas. Glob style pattern matching is supported. [-r|--device] contextpath,context-path... List of one or more devices to drill down. Entries must be separated by commas. Glob style pattern matching is supported. Description Displays the components of the specified object.
Display the components of a device: VPlexcli:/clusters/cluster-2/devices> drill-down --device dev_Symm1723_918 local-device: dev_Symm1723_918 (cluster-2) extent: extent_Symm1723_918_1 storage-volume: Symm1723_918 (blocks: 0 - 4195199) See also ● tree ds dd convert-to-local To convert a distributed device to a local device, this command detaches the leg that is not on the specified cluster.
ds dd create Creates a new distributed-device. Contexts All contexts. Syntax ds dd create [-n|name] name [-d|--devices] context-path [,contextpath,...] [-l|--logging-volumes] context-path [,context-path,...] [-r| rule-set] rule-set [-s|--source-leg] context-path [-f|--force] Arguments Required arguments [-n|--name] name * The name of the new distributed device. Must be unique across the metro node. [-d|--devices] context-path [, contextpath,...
CAUTION: Use this command only if the resulting device will be initialized using tools on the host. Do not use this command if one leg of the resulting device contains data that must be preserved. Applications using the device may corrupt the pre-existing data. To create a device when one leg of the device contains data that must be preserved, use the device attach-mirror command to add a mirror to the leg. The data on the leg will be copied automatically to the new mirror.
See also ● device attach-mirror ● ds dd destroy ● local-device create ds dd declare-winner Declares a winning cluster for a distributed-device that is in conflict after a link outage. Contexts All contexts. In /distributed-storage/distributed-device context, command is declare-winner. In /distributed-storage context, command is dd declare-winner.
ds dd destroy Destroys the specified distributed-device(s). Contexts All contexts. Syntax ds dd destroy [-d|--distributed-device] context-path, context-path,... [-f|--force] Arguments Required arguments [-d|--distributed-device] context-path, context-path,... * List of one or more distributed devices to destroy. [-f|--force] Forces the distributed devices to be destroyed. * - argument is positional. Description In order to be destroyed, the target distributed device must not host virtual volumes.
Syntax ds dd remove-all-rules [ -f|--force] Arguments Optional arguments [-f|--force] Force the operation to continue without confirmation. Description From any context, removes all rules from all distributed devices. WARNING: There is NO undo for this procedure. Examples VPlexcli:/distributed-storage/distributed-devices/dd_23> remove-all-rules All the rules in distributed-devices in the system will be removed.
[-n|--cancel] Arguments Required arguments [-d|--distributed- One or more distributed devices for which segments of the specified logging volume are allocated/ devices] context-path, unallocated. context-path... All components of the distributed-device are included. [-c|--distributeddevice-component] context-path The distributed device component for which segments of the specified logging volume are allocated/unallocated. [-l|--loggingvolume] context-path, context-path...
Examples Allocate segments of a logging volume to a distributed device: VPlexcli:/distributed-storage/distributed-devices/TestDisDevice> ds dd set-log -distributed-devices TestDisDevice --logging-volumes /clusters/cluster-2/system-volumes/ New-Log_Vol Remove the logging volume for a distributed device: VPlexcli:/distributed-storage/distributed-devices/TestDisDevice> ds dd set-log -distributed-devices TestDisDevice --cancel Attempt to cancel a logging volume for a distributed device that is not fully logged:
Description A rule-set contains rules. Use the ll command in the rule-set context to display the rules in the rule-set. Examples Use the ds rule destroy command to destroy a rule in the rule set.
[-r|--rule-set] Rule-set to which this rule is added. * - argument is positional. Description Describes when to resume I/O on all clusters in the island containing the specified cluster. Example In the following example, the rule island-containing command creates a rule that dictates: 1. Metro node waits for 10 seconds after a link failure and then: 2. Resumes I/O to the island containing cluster-1, 3. Detaches any other islands.
Arguments Required arguments [-s|--source] rule-set * Source rule-set. [-d|--destination] new-rule-set The destination rule-set name. * - argument is positional. Description Copies an existing rule-set and assigns the specified name to the copy.
Arguments Required arguments [-n|--name] rule-set Name of the new rule-set. Examples Create a rule-set: VPlexcli:/> ds rule-set create --name TestRuleSet Name -------------TestRuleSet PotentialConflict ----------------false UsedBy ------ See also ● ● ● ● ● ● ● ● ds dd remove-all-rules ds rule destroy ds rule island-containing ds rule-set copy ds rule-set create ds rule-set destroy ds rule-set what-if set ds rule-set destroy Destroys an existing rule-set. Contexts All contexts.
Description Deletes the specified rule-set. The specified rule-set can be empty or can contain rules. Before deleting a rule-set, use the set command to detach the rule-set from any virtual volumes associated with the rule-set. Examples Delete a rule-set: VPlexcli:/distributed-storage/rule-sets/NewRuleSet> ds rule-set destroy NewRuleSet Context '/distributed-storage/rule-sets/NewRuleSet' has been removed. In the following example: ● The ll command displays to which devices the rule-set is attached.
Syntax ds rule-set what-if [-i|--islands] “cluster-1,cluster-2” [-r|--rule-set] context-path Arguments Required arguments [-i|--islands] “cluster-1,cluster-2” List of islands, in quotes. The clusters are separated by commas, the islands by a space. [-r|--rule-set] context-path Context path of the rule-set used in the what-if scenario. Description This command supports only two clusters and one island.
Description Displays summarized information for all distributed-devices. Displays more detailed information for any device with a health-state or operational-status other than ok, and a service-status other than running. Displays devices per cluster, and calculates total and free capacity. Use the --verbose argument to display additional information about unhealthy volumes in each consistency group. Table 8.
Table 8. ds summary field descriptions (continued) Field Description Capacity Summary Number of devices with free capacity, amount of free capacity for the cluster, and total capacity for all clusters. Distributed volumes (in consistency groups) unhealthy summary: CG Name Name of the consistency group of which the unhealthy device is a member. Cache Mode Cache mode of the consistency group.
Table 8. ds summary field descriptions (continued) Field Description ● requires-resume-after-data-loss-failure There have been at least two concurrent failures, and data has been lost. For example, a director fails shortly after the inter-cluster link fails, or when two directors fail at almost the same time. Use the consistency-group resumeafter-data-loss-failure command to select a winning cluster and allow I/O to resume. ● cluster-departure - Not all the visible clusters are in communication.
Cluster summary: Capacity summary: Total 25 devices, 0 unhealthy. Cluster cluster-2 : 25 distributed devices. Cluster cluster-1 : 25 distributed devices. 0 devices have some free capacity. 0B free capacity of 500G total capacity. Distributed volume summary: Total 25 distributed devices in consistency groups, 0 unhealthy.
---------------- ------------ Vols ---------------------------------------------------------- ------------ ------------------------------------------------------AA_ACW_Cluster12 synchronous 9 departure, or-choose-winner] AP_ACW_Cluster1 synchronous departure, ---------------- --------- ---------------- cluster-1 cluster-2 unknown suspended [] [clusterrestore-link- 10 departure, or-choose-winner] AP_ACW_Cluster2 synchronous --------- cluster-1 cluster-2 unknown suspended [] [clusterrestore-link-
Syntax esrs status -h | --help --verbose Arguments Optional arguments -h |--help Displays the usage for this command. --verbose Provides more output during command execution. This may not have any effect for some commands. Description Displays the connectivity status between metro node and SRSv3. NOTE: In Metro systems, run this command on both the management servers. Examples ESRS status. VPlexcli:/> esrs status ESRS Gateway IP --------------10.228.67.
Arguments Optional arguments -h |--help Displays the usage for this command. --verbose Provides more output during command execution. This may not have any effect for some commands. Description Removes information about SRSv3 gateway from metro node. NOTE: In Metro systems, run this command on both the management servers. Examples Unregister ESRS. VPlexcli:/> esrs un-register ESRS instance for this metro node(FNM00121500305) cluster un-registered successfully.
exit Exits the shell. Contexts All contexts. Syntax exit [-e|--exit-code] exit-code [-s|--shutdown] Arguments Optional arguments [-e|--exit-code] exitcode Returns the specified value when the shell exits. If no exit code is specified, then 0 is returned. [-s|--shutdown] When running in server mode, shuts down the shell instead of closing the socket. No effect if not running in server mode. Description If the shell is not embedded in another application, the shell process will stop.
[-w|--wait] seconds [-c|--cluster] context-path] Arguments Optional arguments [-t|--timeout] seconds The maximum number of seconds to wait for the front-end fabric discovery operation to complete. Default: 300. Range: 1- 3600. [-w|--wait] seconds The maximum number of seconds to wait for a response from the fabric discovery. Default: 10. Range: 1- 3600. [-c|--cluster] contextpath Discover initiator ports on the specified cluster.
P0000000046753D21-ETH06, P0000000046753D21-ETH07 dcca-esxprd20-iscsi-init P0000000046653D11-ETH06, iqn.1998-01.com.vmware:dcca-esxprd20-21d30945 default iqn.1998-01.com.vmware:dcca-esxprd17-05ddcbad default iqn.1998-01.com.
[-p|--port] port Arguments Required arguments [-i|--initiatorport] initiator-port * Name to assign to the registered port. Name must be unique in the system. Command fails if the specified name is already in use. [-p|--port] port * Port identifier. For Fibre Channel initiators, a WWN pair as follows: portWWN|nodeWWN. nodeWWN is optional. Each WWN is either '0x' followed by one or more hex digits, or an abbreviation using the format: string:number[,number].
In /clusters/cluster/exports context, command is initiator-port register-host. In /clusters/cluster/exports/initiator-ports context, command is register-host. Syntax export initiator-port register-host [-p|--ports] port,port... [-f|--file] file [-c|--cluster] cluster-context Arguments Required arguments [-f|--file] file * The host declaration file path name. Optional arguments [-c|--cluster] cluster-context * The cluster at which to create the view. [-p|--ports] port,port... List of port names.
[-i|--initiator-ports] initiator-ports [, initiator-ports...] [-h|--help] Arguments Optional arguments [-i|--initiator-ports] initiator-ports [, initiator-ports...] * Specifies the initiator-ports for which the login information is required. [-h|--help] Displays command line help. * - argument is positional. Description Displays a list of target port logins for the specified initiator ports.
export initiator-port unregister Unregisters the specified initiator-port(s). Contexts All contexts. In /clusters/cluster/exports context, command is initiator-port unregister. In /clusters/cluster/exports/initiator-ports context, command is unregister. Syntax export initiator-port unregister i|--initiator-port] initiator-port [,initiator-port...] [-f|--force] [- Arguments Required arguments [-i|--initiator-port] initiator-port [, initiator-port...] * One or more initiator ports to remove.
Syntax export port summary [-c|--clusters] cluster [, cluster,...] [-h|--help] [--verbose] Arguments Optional arguments [-c|--clusters] cluster [, cluster,...] Display unhealthy ports for only the specified cluster(s). [-h|--help] Displays command line help. [--verbose] Displays the names of the unhealthy volumes exported on each port. Description Prints a summary of the views and volumes exported on each port, and a detailed summary of the unhealthy ports.
Display port health for a specified cluster: VPlexcli:/> export port summary --clusters cluster-1 Port health summary(cluster-1): port name export status view summary ------------------------- ------------- -----------------P000000003CA00147-A0-FC01 suspended no unhealthy views P000000003CA00147-A0-FC03 suspended no unhealthy views P000000003CA00147-A1-FC01 suspended no unhealthy views . . .
. . . P000000003CB00147-B0-FC03 unhealthy P000000003CB00147-B1-FC01 unhealthy P000000003CB00147-B1-FC03 unhealthy Total 16 ports, 8 unhealthy. LicoJ013 LicoJ009 true true true 1 27 no views no views no views See also ● ● ● ● ● ● ds summary export storage-view summary extent summary local-device summary storage-volume summary virtual-volume provision export storage-view addinitiatorport Adds the specified initiator port(s) to a storage view. Contexts All contexts.
Example Add the initiator iE_209_hba0 to the view named Dell_209_view: VPlexcli:/clusters/cluster-1/exports> storage-view addinitiatorport --view Dell_209_view --initiator-ports iE_209_hba0 See also ● export storage-view create ● export storage-view removeinitiatorport export storage-view addport Adds the specified port(s) to the storage view. Contexts All contexts. In clusters/cluster/exports/storage-views/storage-view context, command is addport.
See also ● export storage-view create ● export storage-view removeport export storage-view addvirtualvolume Adds a virtual volume to a storage view. Contexts All contexts. In /clusters/cluster/exports context, command is storage-view addvirtualvolume. In /clusters/cluster/exports/storage-views context, command is addvirtualvolume. Syntax export storage-view addvirtualvolume [-v|--view] context-path [-o|--virtual-volumes] virtual-volume, virtual-volume...
Virtual-volumes and LUN-virtual-volume pairs can be specified in the same command line. For example: r0_1_101_vol,(2,r0_1_102_vol),r0_1_103_vol To modify the LUN assigned to a virtual volume, specify a virtual volume that is already added to the storage view and provide a new LUN. NOTE: You cannot add a virtual volume to a storage view if the initialization status of the virtual volume is failed or in-progress.
● virtual-volume re-initialize export storage-view checkconfig Checks the configuration of the views. Contexts All contexts. In /clusters/cluster/exports context, command is storage-view checkconfig. In /clusters/cluster/exports/storage-views context, command is checkconfig. Syntax export storage-view checkconfig Description Performs the following checks: ● Identifies any virtual volumes that are exported more than once. ● Identifies views that contain only a single port.
export storage-view create Creates a view with the given ports. Contexts All contexts. Syntax export storage-view create [-c|--cluster] context-path [-n|--name] name [-p|--ports] context-path,context-path... Arguments Required arguments [-n|--name] name * Name of the new view. Must be unique throughout metro node. [-p|--ports] context-path,context-path... * List of one or more ports to add to the view. Optional arguments [-c|--cluster] context-path The cluster to create the view on.
Example Create a view named E_209_view for front-end ports A0 and B0: VPlexcli:/clusters/cluster-1/exports/storage-views> storage-view create --cluster / clusters/cluster-1 --name E_209_View --ports P000000601610428F-A0-FC00,P000000601610672EB0-FC00 VPlexcli:/clusters/cluster-1/exports/storage-views> storage-view create -c cluster-1/ -n test -p P0000000046653D11-ETH06/ P0000000046653D11-ETH07/ See also ● ● ● ● export export export export storage-view storage-view storage-view storage-view addport addini
Example VPlexcli:/> export storage-view destroy /clusters/cluster-1/exports/storage-views/ TestStorageView See also ● ● ● ● export export export export storage-view storage-view storage-view storage-view create removeinitiatorport removeport removevirtualvolume export storage-view find Displays export views for a specified volume, LUN, initiator, or cluster. Displays next available LUN number for all storage views. Contexts Cluster/exports and below.
Description This command is most useful for configurations with thousands of LUNs, and a large number of views and exported virtual volumes. Example Find the next available LUN numbers on cluster 1: VPlexcli:/clusters/cluster-1/exports/storage-views> find --cluster cluster-1 --free-lun View LicoJ009 : next free LUN number is 27. View LicoJ013 : next free LUN number is 1.
Description Displays unexported virtual volumes in the specified cluster. Displays the remote (on the other cluster) virtual volumes which are unexported. See also ● export storage-view addvirtualvolume ● export-storage-view removevirtualvolume export storage-view map Displays all the virtual volumes that are exported to the storage view. Contexts All contexts. In /clusters/cluster/exports context, command is storage-view map. In /clusters/cluster/exports/storage-views context, command is map.
. . . Display unhealthy storage volumes for all the views at cluster-2: VPlexcli:/> export storage-view map /clusters/cluster-2/exports/storage-views/* VPD83T3:6000144000000010a000e68dc5f76188 base01_vol VPD83T3:6000144000000010a0014760d64cb21f dd_00_vol VPD83T3:6000144000000010a0014760d64cb221 dd_01_vol . . .
Description Use the ll /clusters/cluster/exports/storage-views/storage-view command to display the initiator ports in the specified storage view. Example Remove an initiator port from /clusters/cluster/exports/storage-views/storage-view context: VPlexcli:/clusters/cluster-1/exports/storage-views /LicoJ009> removeinitiatorport LicoJ009_hba1 -i See also ● export storage-view addinitiatorport ● export storage-view removeport export storage-view removeport Removes the specified port(s) from a storage view.
Example Remove a port from /clusters/cluster/exports/storage-views/storage-view context: VPlexcli:/clusters/cluster-1/exports/storage-views/LicoJ009> removeport -p P000000003CA00147-A0-FC02 See also ● export storage-view addport ● export storage-view destroy export storage-view removevirtualvolume Removes the specified virtual volume from the view. Contexts All contexts. In /clusters/cluster/exports context, command is storage-view removevirtualvolume.
Example Delete a virtual volume from the specified storage view, even though the storage view is active: VPlexcli:/clusters/cluster-1/exports/storage-views> removevirtualvolume --view E209_View --virtual-volume (1,test3211_r0_vol) --force WARNING: The storage-view 'E209_View' is a live storage-view and is exporting storage through the following initiator ports: 'iE209_hba1_b', 'iE209_hba0'. Performing this operation may affect hosts' storage-view of storage. Proceeding anyway.
In /clusters/cluster/exports/storage-views context, command is summary. Syntax export storage-view summary [-c|--clusters] cluster,cluster... Arguments Optional arguments [-c|--cluster] cluster, cluster... List of clusters. Entries must be separated by commas. Display information only for storage views on the specified clusters. Description At the root level, displays information for all clusters.
● ● ● ● export storage-view checkconfig export storage-view map export storage-view show-powerpath-interfaces storage-volume summary export target-port renamewwns Renames a target port's WWN pair. Contexts All contexts. In /clusters/cluster/exports context, command is target-port renamewwns.
Example VPlexcli:/> export target-port renamewwns --wwns 0xd1342a|0xd1342b --port P0000000000000001-FK00 See also ● export initiator-port discovery extent create Creates one or more storage-volume extents. Contexts All contexts. Syntax extent create [-s|--size] size [-o|--block-offset] integer [-n|--num-extents] integer [-d|--storage-volumes] storage-volume,storage-volume... Arguments Required arguments [-d|--storage-volumes] storagevolume,storage-volume ...
● The cd command changes the context to the storage-volume context on cluster-1. ● The extent create command creates an extent from two claimed 16 GB storage volumes. VPlexcli:/> ll -p **/storage-volumes VPlexcli:/>cd /clusters/cluster-1/storage-elements/storage-volumes VPlexcli:/clusters/cluster-1/storage-elements/storage-volumes> extent create Symm1723_1DC,Symm1723_1E0 See also ● extent create ● extent destroy extent destroy Destroys one or more storage-volume extents. Contexts All contexts.
Description Destroys the specified extents. Example Destroy an extent: VPlexcli:/clusters/cluster-1/storage-elements/extent> extent destroy --force extent_Symm1254_7BA_1 Destroyed 1 out of 1 targeted extents. See also ● extent create extent summary Displays a list of a cluster's unhealthy extents. Contexts All contexts. In /clusters/cluster/storage-elements/extents context, command is summary. Syntax extent summary [-c|--clusters] cluster,cluster...
Table 9. extent summary field descriptions (continued) Field Description I/O Status alive - I/O is proceeding normally on the extent. dead - The underlying storage volume is marked as hardwaredead. unreachable - The underlying storage volume is unreachable. Operational Status degraded - The extent may be out-of-date compared to its mirror (applies only to extents that are part of a RAID 1 device). ok - The extent is functioning normally. starting - The extent is not yet ready.
See also ● ● ● ● ● ● ds summary export port summary export storage-view summary local-device summary storage-volume summary virtual-volume provision find Finds all the contexts matching a pattern and returns a set contexts matching supplied pattern. Contexts All contexts. Syntax find [-c | --contexts] = pattern [, pattern ...] [-h | --help] [--verbose] Arguments Required arguments [-c | --contexts] = pattern [, pattern ...] Pattern for matching contexts you want to find.
front-end-performance-stats start Starts the collection of the read and write statistics with the I/O size and the logical block addressing (LBA) information on the metro node virtual volumes through periodic polling. Contexts All contexts. Syntax front-end-performance-stats start Arguments Optional arguments -h | --help Displays the usage for this command. --verbose Provides more output during command execution. This might not have any effect for some commands.
Syntax front-end-performance-stats status Arguments Optional arguments -h | --help Displays the usage for this command. --verbose Provides more output during command execution. This might not have any effect for some commands. Description Provides the status of the front-end performance statistics collection.
Description Stops the front-end performance statistics collection. The statistics are available in the fe_perf_stats_.log file at /var/log/VPlex/cli/. NOTE: Run this command on each cluster to stop the front-end performance statistics collection. See also ● front-end-performance-stats start ● front-end-performance-stats status getsysinfo Returns information about the current system. Contexts All contexts.
Table 10. getsysinfo field descriptions (continued) Field Description System does NOT have comtcp enabled Communication protocol used on Ethernet ports for connections to other clusters prior to Release 4.0. Ignore this line.
--wan --hardware --cluster_witness --virtual-ha Arguments Optional arguments [-m|--highlevel] Checks for major subcomponents with error conditions. Warnings are ignored. Used for instantaneous, high level view of the health of the metro node. Default behavior if no other argument is specified. [-f|--full] Runs full scan. --configuration Perform configuration checks. --back-end Perform back end checks. --front-end Perform front end checks. --cache Perform cache check.
Cluster Cluster Oper Health Connected Expelled Name ID State State --------- ------- ----- -------- --------- -------cluster-1 1 ok degraded True False cluster-2 2 ok ok True False cluster-1 Transition/Health Indications: Device initializing 20 unhealthy Devices or storage-volumes Meta Data: ---------Cluster Volume Volume Oper Health Active Name Name Type State State --------- ------------------------------- -------------- ----- ------ -----cluster-1 Advil_1 meta-volume ok ok True cluster-1 logging_c1_log_v
this command on the remote cluster to get the health of the remote cluster's RecoverPoint configuration. Array Aware: -----------Cluster Name Provider Address Connectivity Registered Total Arrays Storage Pool ------------ -------- ------------- ------------ ---------- -----------Hopkinton dsvea125 10.108.64.125 connected 2 13 Hopkinton dsvea123 10.108.64.123 connected 2 29 Providence dsvea124 10.108.64.
WAN WAN WAN WAN WAN Port Settings.................. OK Port Group Settings............ OK Subnet Settings................ OK Bridged and Routed Settings.... OK Ping Remote IPs................ OK ping from director-1-1-A: Remote Discovery IP: 224.100.100.100 is reachable, Round-trip time:0.328 ms Remote Cluster IPs: 192.168.4.252 is reachable, Round-trip time:0.083 ms 192.168.5.252 is reachable, Round-trip time:0.081 ms ping from director-1-1-B: Remote Discovery IP: 224.100.100.
VPD83T3:600601601dd028007fc9ec0e6427e111 is degraded ['degraded-read-writelatencies'] VPD83T3:600601601dd0280080c9ec0e6427e111 is degraded ['degraded-timeout', 'degraded-write-latency'] VPD83T3:600601601dd0280083c9ec0e6427e111 is degraded ['degraded-write-latency'] Checking Unhealthy Virtual Volumes......... OK Back end array status......................
help Displays help on one or more commands. Contexts All contexts. Syntax help [-i|--interactive] [-G|--no-global] [-n|--no-internal] Arguments Optional arguments [-i|--interactive] Invoke interactive help. Type quit to exit interactive help. [-G|--no-global] Suppresses the list of global commands for contexts other than root context. [-n|--internal] Include commands that are normally used for low-level debugging and development.
progress indicator are displayed. Health-state has a similar indicator. Invoke interactive help: VPlexcli:/clusters/cluster-1> help -i Welcome to Python 2.2! This is the online help utility. . . . help> topics Here is a list of available topics. Enter any topic name to get more help. ASSERTION DYNAMICFEATURES NONE TRACEBACKS ASSIGNMENT ELLIPSIS NUMBERMETHODS TRUTHVALUE . . . help> EXPRESSIONS -----------------------------------------------------------------------5.
496 497 498 499 cd ds summary export storage-view checkconfig history 8 local-device create Creates a new local-device. Contexts All contexts. Syntax local-device create [-d|--stripe-depth] depth [-n|name] name [-g|--geometry] {raid-0|raid-1|raid-c} [-e|extents] context-path,context-path... [-s|--source-leg] context-path --force Arguments Required arguments [-n|--name] name * Name for the new device. Must be unique across all clusters.
● A multiple of the block size: 4 K bytes A depth of 32 means 128 K (32 x 4 K) is written to the first disk then the next 128 K is written to the next disk. Concatenated RAID devices are not striped. [-s|--sourceleg] context-path When geometry argument is raid-1, picks one of the extents specified by the --extents argument to be used as the source data image for the new device. The command copies data from the -source-leg to the other legs of the new device.
● ● ● ● The The The The ll command displays the available (claimed) extents local-device create command is used to create a 16 GB RAID 1 device named TestDevCluster1 on cluster 1 cd command returns to the root context ll -p **/devices command displays the new device VPlexcli:/clusters/cluster-1/storage-elements/extents> ll Name StorageVolume Capacity Use --------------------- ------------- -------- ------. . .
local-device destroy Destroys existing local-devices. Contexts All contexts. Syntax local-device destroy [-f|--force] [-d|--devices] context-path,context-path... Arguments Required arguments [-d|--devices] context-path,context-path... * List of one or more device(s) to destroy. Optional arguments [-f|--force] Force the destruction of the devices without asking for confirmation. * - argument is positional. Description The device must not be hosting storage or have a parent device.
local-device summary Displays unhealthy local devices and a summary of all local devices. Contexts All contexts. In /clusters/cluster/devices context, command is summary. Syntax local-device summary [-c|--clusters] cluster,cluster... Arguments Optional arguments [-c|--clusters] cluster,cluster... Display information only for the specified clusters. Description Displays unhealthy local devices and a summary of all local devices.
Example Display local devices for a specified cluster: VPlexcli:/> local-device summary --clusters cluster-1 device name health state operational status --------------- ---------------- -----------------dev_sym1723_1FC critical-failure error Device Summary (no tier) -------------- --------------------Health devices 5 unhealthy 1 Visibility local 5 Capacity devices w/ space 0 free capacity 0B total capacity 12G service status -------------suspended See also ● ● ● ● ● ds summary export port summary export
7 - debug (debug-level messages) 6 - info (informational messages) 5 - notice (normal but significant messages) 4 - warning (warning messages) 3 - err (error messages) 2 - crit (critical messages) 1 - alert (messages that must be handled immediately) 0 - emerg (messages notifying the system as unusable) Default modifier is>. [-c|--component] name Component name to filter. Takes a regular expression as an argument. Plain strings are searched for in the component name.
log filter destroy Removes a firmware log filter. Contexts All contexts. Syntax log filter destroy [-f|--filter] filter Arguments Required arguments [-f|--filter] filter ID of filter to delete. Description The filter is removed from the filter stack. Use the log filter list command to display the filters configured on the system, and associated IDs of those filters. Example VPlexcli:/> log filter list 1. [Source='/var/log/VPlex/cli/events.
Syntax log filter list Description The number printed beside each filter serves as both an identifier for the log filter destroy command as well as the order in which each respective filter will see an event. Example VPlexcli:/> log filter list 1. [Message matches 'Family and Fru Id Mismatch Retrieved'] Destination='null' Consume='true' 2. [Component='logserver'] Destination='null' Consume='true' 3.
Description CAUTION: For use by Dell EMC personnel only. Creates a source for writing entries to the firmware log. Example VPlexcli:/> log source create --source 128.221.252.69:5988 Enter the source connection password: VPlexcli:/> log source list 1. /var/log/VPlex/cli/events.log . . . 6. [128.221.252.69:5988]/cpu0/log 7. [128.221.252.69:5988]/xmmg/log See also ● log source destroy ● log source list log source destroy Destroys the specified log source. Contexts All contexts.
Example VPlexcli:/> log source list 1. /var/log/VPlex/cli/events.log 2. 128.221.252.67:5988,[128.221.253.67:5988]/cpu0/log 3. 128.221.252.67:5988,[128.221.253.67:5988]/xmmg/log 4. 128.221.253.68:5988,[128.221.252.68:5988]/cpu0/log 5. 128.221.253.68:5988,[128.221.252.68:5988]/xmmg/log 6. [128.221.252.69:5988]/cpu0/log 7. [128.221.252.69:5988]/xmmg/log 8. [128.221.252.70:5988],128.221.253.70:5988/cpu0/log 9. [128.221.252.70:5988],128.221.253.70:5988/xmmg/log VPlexcli:/> log source destroy --source 128.221.
logging-volume add-mirror Adds a logging volume mirror. Contexts All contexts. Syntax logging-volume add-mirror [-v|--logging-volume] logging-volume [-m|--mirror] {name|context-path} Arguments Optional arguments [-v|--logging-volume] logging-volume Logging volume to which to add the mirror. [-m|--mirror] {name| context-path} The name or context path of the device or storage-volume extent to add as a mirror. Must be top-level device or a storage-volume extent.
[-n|--name] name * Name for the new logging volume. [-g|--geometry] {raid-0|raid-1} * Geometry for the new volume. [-e|--extents] context-path,contextpath... * List of one or more storage-volume extents to use to create the logging volume. Must not be empty, and must contain storage-volume extents that are all at the specified cluster. Entries must be separated by commas. Optional arguments [-d|--stripedepth] depth Required if --geometry is raid-0.
Table 12. logging volume display fields (continued) Field Description geometry Indicates the geometry or redundancy of this device. Will always be raid-1. health-indications If health-state is not “ok”, additional information. health-state ● ok - The storage volume is functioning normally. ● degraded - The storage volume may be out-of-date compared to its mirror. (This state applies only to a storage volume that is part of a RAID 1 Metadata Volume.
Table 12. logging volume display fields (continued) Field Description system-id Name assigned to the logging-volume. transfer-size The transfer size during rebuild in bytes. See About transfersize in the batch-migrate start command. volume-type For logging volumes, this is always logging-volume. /components context Name Name of the extent. Slot number The slot number of the component. Type Indicates the type of component: a storage-volume, extent, or device.
---------components segments ------------------------------------------------------------------The list of components that support this logging-volume. Shows what parts of the logging volume are assigned to log changes on distributed-device legs.
[-s|--slot] slot-number [-h|--help] [--verbose] Arguments Optional arguments [-m|--mirror] mirror * Specifies the name or context path of the logging volume mirror to detach. If you specify the mirror, do not specify the slot number. [-v|--loggingvolume] logging-volume Specifies the name of the logging volume from which to detach the mirror. [-s|--slot] slotnumber Specifies the slot number of the mirror to detach. If you specify the slot number, do not specify the mirror.
volume-type logging-volume Contexts: Name Description ---------- ------------------------------------------------------------------components The list of components that support this logging-volume. segments Shows what parts of the logging volume are assigned to log changes on distributed-device legs.
Description The volume to be destroyed must not be currently used to store block write logs for a distributed-device. Example VPlexcli:/clusters/cluster-1/system-volumes> logging-volume destroy --logging-volume cluster_6_log_vol See also ● logging-volume add-mirror ● logging-volume create ● logging-volume detach-mirror logical-unit forget Forgets the specified logical units (LUNs). Contexts All contexts.
Use the --forget-storage-volume argument to forget the logical unit AND its associated storage-volume. This is equivalent to using the storage-volume forget command on those storage-volumes. Example Forget the logical units in the current logical unit context: VPlexcli:/clusters/cluster-1/storage-elements/storage-arrays/EMC-SYMMETRIX-192602773/ logical-units> logical-unit forget 13 logical-units were forgotten.
[-C|--no-contexts] [-x |--cache-max-age] context,[[context]...] Arguments Optional arguments [-l|--long] Display more detailed information. [-a|--attributes] Includes the attributes of the target contexts. [-A|--no-attributes] Excludes attributes. [-t|--attribute-selector] attribute-selector Display the contents of the specified attributes. [-p|--paged] Page output if it is longer than the window height. [-m|--commands] depth Includes commands in the listing.
operational-status ok /engines/engine-2-1/directors/dirA: Name Value ------------------ ----operational-status ok . . .
manifest upgrade Loads a new manifest file, replacing the old one, if it exists. Contexts All contexts. Syntax manifest upgrade -m|--manifest] pathname Arguments Required arguments [-m|--manifest] pathname Path to manifest file. Relative paths can be used. Description The new manifest file will be validated before it replaces the old one. If there is no current valid manifest file (corrupted or missing), the specified manifest file is installed without confirmation.
Example VPlexcli:/> manifest version 1.106.0 See also ● manifest upgrade meta-volume attach-mirror Attaches a storage-volume as a mirror to a meta-volume. Contexts All contexts. Syntax meta-volume attach-mirror [-d|--storage-volume] context-path [-v|--meta-volume] context-path Arguments Required arguments [-d|--storage-volume] context-path Storage-volume to attach as a mirror to the meta-volume. [v|--meta-volume] context-path Meta-volume to which the storage volume should be attached as a mirror.
Example Attach storage volume VPD83T3:6…ade11 as a mirror to the existing meta-volume _dmx: VPlexcli:/engines/engine-1-1/directors> meta-volume attach-mirror --storage-volume VPD83T3:6006016023901d00484f496fa07ade11 --meta-volume _dmx -volume _dmx is created at /clusters/cluster-1/system-volumes. See also ● meta-volume detach-mirror meta-volume backup Creates a new meta-volume and writes the current in-memory system data to the new meta-volume without activating it. Contexts All contexts.
current-metadata-namebackup_yyyyMMMdd_HHmms Metadata is read from the meta-volume only during the boot of each director. Create a backup meta-volume: ● As part of an overall system health check before a major migration or update. ● If the system permanently loses access to both meta-volumes. NOTE: No modifications should be made to the system during the backup procedure. Make sure that all other users are notified.
[f|--force] Forces the meta-volume to be created without asking for confirmation. * - argument is positional. Description Metadata includes virtual-to-physical mappings, data about devices, virtual volumes, and configuration settings. Metadata is stored in cache and backed up on a specially designated external volume called the meta-volume. The meta-volume is critical for system recovery.
/clusters/cluster-1/system-volumes/c1_meta: Attributes: Name Value ---------------------- ----------active true application-consistent false block-count 20971264 block-size 4K capacity 80G component-count 2 free-slots 27199 geometry raid-1 health-indications [] health-state ok locality local operational-status ok ready true rebuild-allowed true rebuild-eta rebuild-progress rebuild-status done rebuild-type full slots 32000 stripe-depth system-id c1_meta transfer-size 128K volume-type meta-volume Contexts: Na
VPD83T3:6006048c460345d122db7605e8b18863 EMC-Celerra-APM00140825464 VPD83T3:6006048c54c01376339c6efc9542317c EMC-Celerra-APM00140825464 VPD83T3:6006048c5b272e8526c2203c6d56dc88 APM00140825464 VPD83T3:6006048c8918b7022b8ca80efbaa7fa0 EMC-Celerra-APM00140825464 VPD83T3:6006048cbc54f178bb648e9d48a3cd7c EMC-Celerra-APM00140825464 VPD83T3:6006048cbf68882ef8b8031ba611ad77 EMC-Celerra-APM00140825464 45G 20G 100G EMC-Celerra- 45G 45G 20G See also ● meta-volume destroy meta-volume destroy Destroys a meta-volume
● ll displays that the target meta-volume has an active state of false. ● The meta-volume destroy command destroys the meta-volume: VPlexcli:/clusters/cluster-1/system-volumes> ll meta1 /clusters/cluster-1/system-volumes/meta1: Attributes: Name Value ---------------------- ----------active false application-consistent false block-count 23592704 . . . VPlexcli:/clusters/cluster-1/system-volumes> meta-volume destroy -v meta1 Meta-volume 'meta1' will be destroyed.
[-u|--detach-unreachablemirror] Supports the discard of an unreachable mirror. --discard Discards the mirror to be detached. The data is not discarded. * - argument is positional. Description Detaches the specified storage volume from a meta-volume. Use the ll command in /clusters/cluster/system-volumes/meta-volume/components context to display the slot number when using the discard argument.
● Must be 20 GB or larger. Description Writes the metadata to the specified meta-volume, and activates it. The specified meta-volume must already exist (it is not created automatically). This command fails if the destination meta volume has a lower number of meta data slots than required to support the current configuration. This is highly likely if the target meta-volume was manually created before Release 5.1 and has 32000 slots. Confirm this by using the ll command in the system volume context.
short - Requires special firmware support available only in Release 5.0 and later. long - Requires special firmware support available only in Release 5.0 and later. slow - Available for all Release versions. Downloads the meta-volume headers from the metavolume legs one at a time and compares them. CAUTION: The slow option may take hours to complete on a production meta-volume. Description An active meta-volume with an inconsistent on-disk state can lead to a data unavailability (DU) during NDU.
monitor add-console-sink Adds a console sink to the specified performance monitor. Contexts All contexts. In context, command is add-console-sink. Syntax monitor add-console-sink [-o|--format] {csv|table} [-m|--monitor] monitor-name [--force] Arguments Required arguments [-m|--monitor] context-path * Performance monitor to which to add a console sink. Optional arguments [-f|--force] Forces the creation of the sink, even if existing monitors are delayed in their polling.
------- ------- ------ ------console true table console VPlexcli:/monitoring/directors/Director-2-1-B/monitors/Director-2-1-B_TestMonitor/sinks> ll console /monitoring/directors/Director-2-1-B/monitors/Director-2-1-B_TestMonitor/sinks/console: Name Value ------- ------enabled true format table sink-to console type console See also ● monitor add-file-sink ● monitor remove-sink ● monitor create monitor add-file-sink Adds a file sink to the specified performance monitor. Contexts All contexts.
Description Creates a file sink for the specified monitor. File sinks send output to the specified file. The default location of the output file is /var/log/VPlex/cli. The default name for the file sink context is file. Every monitor must have at least one sink, and may have multiple sinks. A monitor does not begin operation (polling and collecting performance data) until a sink is added to the monitor Use the monitor add-file-sink command to add a file sink to an existing monitor.
Arguments Required arguments [-m|--monitor] context-path,context-path One or more performance monitors to update immediately. Description Polls and collects performance data from user-defined monitors. Monitors must have at least one enabled sink. Example VPlexcli:/> monitor collect /monitoring/directors/director-2-1-B/monitors/director-2-1B_TestMonitor VPlexcli:/> Source: director-2-1-B_TestMonitor Time: 2010-07-01 10:05:55 director.be-ops (counts/s): . . .
Arguments Required arguments [-n|--name] monitorname * Name of the monitor. The name is appended to the director on which the monitor is configured. [-s|--stats] stat[,stat,...] * One or more statistics to monitor, separated by commas. Use the monitor stat-list command to display the available statistics. Optional arguments [-p|--period] collectionperiod Frequency at which this monitor collects statistics.
About file rotation and timestamps The log files created by a monitor’s file sink are automatically rotated when they reach a size of 10 MB. The 10MB file is saved as filename.csv.n where n is a number 1 - 10, and output is saved in a new file named filename.csv.n+1. The .csv files are rotated up to 10 times. In the following example, a monitor has exceeded 10MB of output. The initial 10MB are stored in filename.csv.1. Subsequent output is stored in filename.csv.
monitor destroy Destroys a performance monitor. Contexts All contexts. In /monitoring context, command is destroy. Syntax monitor destroy [-m|--monitor] monitor-name,monitor-name... [-c|--context-only] [-f|--force] Arguments Required arguments [-m|--monitor] monitor-name * List of one or more names of the monitors to destroy. Optional arguments [-f|-- force] Destroy monitors with enabled sinks and bypass confirmation.
See also ● monitor create ● report create-monitors monitor get-stats Get last stats from monitors Contexts All Syntax get-stats [m | --monitors= context paths [, context paths>...]] -p | --parseable -h | --help --verbose Arguments Required arguments -m | --monitors= context paths [, context paths ...] * Get the last stats from the monitors specified by the listed context paths. -p | --parseable Output parser-friendly stats names Optional arguments -h | --help Displays the usage for this command.
Examples monitor get-stat –monitors director-1-1-A_PERPETUAL_vplex_sys_perf_mon_v19,director-1-1B_PERPETUAL_vplex_sys_perf_mon_v19 monitor get-stat –monitors director-1-1-A_VIRTUAL_VOLUMES_PERPETUAL_MONITOR,director-1-1B_VIRTUAL_VOLUMES_PERPETUAL_MONITOR monitor remove-sink Removes a sink from a performance monitor. Contexts All contexts. In /monitoring context, command is remove-sink. Syntax monitor remove-sink [-s|--sinks] context-path,context-path...
monitor stat-list Displays statistics available for performance monitoring. Contexts All contexts. In /monitoring context, command is stat-list. Syntax monitor stat-list [-c|--categories] category,category... Arguments Optional arguments [-c|--categories] category, category... List of one or more statistics categories to display. Description Performance statistics are grouped into categories Use the monitor stat-list command followed by the key to display the statistics categories.
ndu pre-check Performs a pre-NDU validation and check. Contexts All contexts. Syntax ndu pre-check Description The ndu pre-check command should be run before you run a non-disruptive upgrade on a system to upgrade GeoSynchrony. This command runs through a number of checks to see if the non-disruptive upgrade would run into any errors in upgrading GeoSynchrony. CAUTION: NDU pre-checks must be run within 24 hours before starting the NDU process.
[-u|--firmware] firmware-tar-file - Full path to director firmware package on the management server. [-i|--image] firmware-image-file - Full path to director firmware image on the management server. Description Disruptively upgrades a metro node when the metro node is not fully installed and configured. CAUTION: This command requires the metro node be in a pre-config state. Specifically, do not use this procedure unless NO meta-volume is configured (or discoverable).
ndu start Begins the non-disruptive upgrade (NDU) process of the director firmware. Contexts All contexts. Syntax ndu start [--io-fwd-ask-for-confirmation] prompt type [-u|--firmware] firmware-tar-file [optional-argument [optionalargument]] Arguments Required arguments [-u|--firmware] firmware-tar-file * Full path to director firmware package on the management server. [--io-fwd-ask-forconfirmation] prompt type The type of the prompt that you want to see during the IO forwarding phase of the NDU.
● ● ● ● s m h d for for for for seconds minutes hours days --cws-package cwsfirmware-tar-file Full path to Cluster Witness Server package on the management server. --force Ignore manifest checking of supported upgrades. --skip-cws-upgrade Skips the upgrade of the Cluster Witness Server and proceeds with the rest of the NDU. --skip-be-switchcheck Skips the NDU pre-check for unhealthy back-end switches.
--skip-total-numberof-volumes-check Skips the NDU pre-check for total number of volumes. --skip-interdirector-mgmtconnectivity-check Skips the NDU pre-check for inter-director management connectivity. --do-not-verifywanlink-after-upgrade NDU does not check whether first-upgraders see each other on the WAN link after the upgrade. --skip-storage-viewmissing-lun0-check Skips the NDU pre-check for storage-views with virtual-volumes that do not have a LUN0 ID.
Description If an NDU firmware or OS upgrade is running, this command displays the upgrade activity. If neither NDU firmware or OS upgrade is running, this command displays information about the previous NDU firmware upgrade. If the last operation was a rolling-upgrade, the OS upgrade information is displayed. The ndu start command clears this information. If an NDU firmware or OS upgrade has failed, this command displays a message to use the ndu recover command.
plugin addurl Adds an URL to the plug-in search path. Contexts All contexts. Syntax plugin addurl [-u|--urls] url,url... Arguments Required arguments [-u|--urls] url, url... A list of URLs to add to the search path. Entries must be separated by commas. Description NOTE: The plugin commands are not intended for customer use. Plug-ins extend the class path of the CLI. Plug-ins support dynamic addition of functionality. The plugin search path is used by the plugin register command.
Example VPlexcli:/> plugin listurl file:/opt/emc/VPlex/jython2.2/LibExt/AutoBundles/prodscripts.jar, file:/opt/emc/VPlex/ apache-tomcat-6.0.x/bin/commons-daemon.jar, file:/opt/emc/VPlex/apache-tomcat-6.0.x/bin/ bootstrap.jar, file:/opt/emc/VPlex/apache-tomcat-6.0.x/bin/tomcat-juli.jar, file:/opt/emc/VPlex/apache-tomcat-6.0.x/lib/tomcat-i18n-es.jar, file:/opt/emc/ VPlex/apache-tomcat-6.0.x/lib/tomcat-juli-adapters.jar, file:/opt/emc/VPlex/apachetomcat-6.0.x/lib/catalina-tribes.
See also ● plugin addurl ● plugin listurl popd Pops the top context off the stack, and changes the current context to that context. Contexts All contexts. Syntax popd Description If the context stack is currently empty, an error message is displayed. Example In the following example: ● The pushd command adds a third context to the context stack. The output of the command displays the three contexts in the stack.
Syntax pushd [-c|--context] context Arguments Optional arguments [-c|--context] context The context to push onto the context stack. Description Adds the context to the context stack. If no context is supplied, and there is a context on the stack, the current context is exchanged with the top-of-stack context. Use the popd command to remove the topmost context from the context stack.
Syntax rebuild set-transfer-size [-r|--devices] context-path,context-path... [-l|--limit] limit Arguments Required arguments [-r|-devices] context-path * List of one or more devices for which to change the transfer size. Wildcards are permitted. Entries must be separated by commas. [-l|--limit] limit * Transfer size in bytes. Maximum number of bytes to transfer as one operation per device. Specifies the size of read sector designated for transfer in cache.
rebuild show-transfer-size Shows the transfer-size of specified RAID 1 devices. Contexts All contexts. Syntax rebuild show-transfer-size [-r|--devices] context-path Arguments Optional arguments [-r|-devices] contextpath... List of one or more RAID 1 devices for which to display the transfer size. Entries must be separated by commas. Wildcards are permitted.
● rebuild status rebuild status Displays all global and cluster-local rebuilds along with their completion status. Contexts All contexts. Syntax rebuild status [--show-storage-volumes] Arguments Optional arguments --show-storagevolumes Displays all storage volumes that need to be rebuilt, both active and queued. If not present, only the active rebuilds are displayed.
--------testvol1 full s1_220d_spa 12.3min Local rebuilds: No active local rebuilds. 4.06G/11.2G 36.17% 9.94M/s See also ● rebuild show-transfer-size report capacity-arrays Generates a capacity report. Contexts All contexts. Syntax report capacity-arrays [-t|--tier-regx] regular-expression [-d|--directory] directory Arguments Optional arguments [-t|-tier-regex] Regular expression which when applied to the storage-volume name, returns the tier ID in a group.
NOTE: Tier IDs are required to determine the tier of a storage volume/storage array. Storage volumes that do not contain any of the specified IDs are given the tier value no-tier. The report is separated into two parts: local storage and shared storage. ● Local storage is accessible only from the same cluster where the storage is physically located.
alloc: unalloc devices: unalloc storage-volumes: . . . Shared Storage (in GiB): alloc: 2192.468 unalloc devices: 0.000 Tier summary (local, by cluster): cluster-1 Tier no-tier cluster-2 Allocated (GiB) 9.000 0.000 0.000 4929.053 Unallocated Devices (GiB) 3.000 Unallocated StorageVolumes (GiB) 10596.152 Unallocated Unallocated Tier Allocated (GiB) Devices (GiB) StorageVolumes (GiB) no-tier 2.000 4.000 8467.
● Storage_volumes and volumes are listed before the summary is printed. ● Two additional files are created: CapacityClustersVolumes.csv and CapacityClustersStorageVolumes.csv. Description The capacity report information includes: ● ● ● ● ● ● ● ● ● ● Unclaimed storage-volume capacity in GB. Number of unclaimed storage volumes. Claimed storage-volume capacity in GB. Number of claimed storage volumes. Used storage-volume capacity in GB. Number of used storage volumes.
[-d|--directory] directory [--verbose] Arguments Optional arguments [-d|-directory] directory --verbose Directory in which to create the csv files. Output is written to a file named CapacityHosts.csv. Default directory path: /var/log/VPlex/cli/reports/ on the management server. If the --verbose argument is used, an additional file is created: CapacityHostsViews.csv. Description The host capacity information includes: ● Number of views. ● Total exported capacity in GB.
● report capacity-arrays rm Deletes a file from the corresponding share location. Contexts This command can only be executed in the in or out sub-contexts within the share context of the management server (either /management-server/share/in or /management-server/share/out. Syntax rm -n|--filename filename [-h | --help] [--verbose] Arguments Optional arguments [-h|--help] Displays the usage for this command. [--verbose] Provides more output during command execution.
Syntax schedule add [-t|--time] time [-c|--command] command Arguments Required arguments [-t|--time] time * Date and time the job executes in crontab-style format enclosed in quote marks. Values are specified in the crontab-style format: “Minute Hour Day-of-the-Month Month Day-of-the-week” ● Minute - 0-59. ● Hour - 0-23. ● Day of the Month - 1-31. ● Month - 1-12, January = 1...December = 12 ● Day of the week - 0-6, Sunday = 0...
Examples VPlexcli:/> [0] 30 13 * [1] * 1 * * [2] * 2 * * schedule list * 3 syrcollect * tree * tree See also ● schedule modify ● schedule remove schedule modify Modifies an existing scheduled job. Contexts All contexts. Syntax schedule modify [-j|--job] job-ID [-t|--time] time [-c|--command] command Arguments Required arguments [-j|--job] job-ID * ID of the scheduled job as displayed by the schedule list command.
Examples To modify a job with the ID of 3 so that it runs every day at 11:00 a.m. type: VPlexcli:/> [0] 30 13 * [1] * 1 * * [2] * 2 * * [3] * 3 * * VPlexcli:/> schedule list * 3 syrcollect * tree * tree * tree schedule modify 3 -t "0 11 * * *" -c tree See also ● schedule list ● schedule remove schedule remove Removes a scheduled job. Contexts All contexts.
See also ● schedule list ● schedule modify scheduleSYR add Schedules a weekly SYR data collection. Contexts All contexts. Syntax scheduleSYR add [-d|--dayOfWeek] [0-6] [-t|--hours] [0-23] [-m|--minutes] [0-59] Arguments Required arguments [-d|--dayOfWeek] [0-6] Day of the week run the collection. Valid values are 0-6, where Sunday = 0...Saturday = 6. [-t|--hours] [0-23] Hour at which to run the collection. [-m|--minutes] [0-59] Minute at which to run the collection.
SYR data collection job is currently scheduled at: Day of Week: 3 (Sunday=0, Monday=1,...Saturday=6) Hours: 12 Minutes: 30 See also ● ● ● ● ● ● configuration event-notices-reports config configuration event-notices-reports reset schedule list scheduleSYR list scheduleSYR remove syrcollect scheduleSYR list Lists the scheduled SYR data collection job. Contexts All contexts.
Syntax scheduleSYR remove Description Only one SYR data collection can be scheduled. The current SYR collection cannot be modified. To modify the SYR data collection job: ● Use the scheduleSYR remove command to remove the existing collection job. ● Use the scheduleSYR add command to create a new collection job. Example Remove a scheduled collection: VPlexcli:/> scheduleSYR remove Removing SYR data collection job scheduled at: Day of Week: 3 (Sunday=0, Monday=1,...
[-u|--unimport] module Unimport the specified Jython module without changing to interactive mode. All the commands that were registered by that module are unregistered. Description Changes the command mode from VPLEX CLI to Jython interactive mode. To return to the normal CLI shell, type a period '.' and press ENTER. Use the --import and --export arguments to import or export the specified Jython module without changing to interactive mode.
Example VPlexcli:/> sessions Type Username ------------- -------TELNET_SHELL service DEFAULT_SHELL - Hostname --------localhost - Port ----23848 - Creation Time ---------------------------Wed Sep 15 15:34:33 UTC 2010 Tue Aug 03 17:16:07 UTC 2010 set Changes the value of writable attributes in the given context. Contexts All contexts.
Examples Display which attributes are writable in the current context, and their valid inputs: VPlexcli:/distributed-storage/distributed-devices/TestDisDevice> set attribute input-description -----------------------------------------------------------------------------------------------------application-consistent Takes one of '0', '1', 'f', 'false', 'n', 'no', 'off', 'on', 't', 'true', 'y', 'yes' (not case sensitive).
Attach a rule-set to cluster1_Active to the device dd_00: VPlexcli:/distributed-storage/distributed-devices> set dd_00::rule-set-name cluster1_Active Set a storage volume’s thin-rebuild attribute to true: VPlexcli:/clusters/cluster-1/storage-elements/storage-volumes/clar_LUN83> set thinrebuild true VPlexcli:/clusters/cluster-1/storage-elements/storage-volumes/clar_LUN83> ll Name Value ---------------------- ------------------------------------------------------application-consistent false . . .
A3-FC02 0x0000000000000000 down A3-FC03 0x0000000000000000 down VPlexcli:/engines/engine-1-1/directors/director-1-1-A/hardware/ports> set A0FC03::enabled true VPlexcli:/engines/engine-1-1/directors/director-1-1-A/hardware/ports> ll Name Address Role Port Status ------- ------------------ --------- ----------A0-FC00 0x5000144260006e00 front-end no-link A0-FC01 0x5000144260006e01 front-end up A0-FC02 0x5000144260006e02 front-end up A0-FC03 0x5000144260006e03 front-end no-link A1-FC00 0x5000144260006e10 back-e
storage-tier supporting-device system-id volume-type device_EMC-CLARiiON-APM00113700075-VNX_LUN122_1 new_name virtual-volume Set the SPC version to Version 3 on an initiator port: VPlexcli:/clusters/cluster-1/exports/initiator-ports/test_port_1> set scsi-spc-version 3 To avoid Data Unavailability and host issues, follow the procedure described in the KB article 'SPC-3 support in VPLEX' to change the SPC version.
set topology Changes the topology attribute for a Fibre Channel port. Contexts /engines/engine/directors/director/hardware/ports/port Syntax set topology [p2p|loop] Arguments Required arguments p2p Sets the port’s topology as point-to-point. The port comes up as an F-port. Use the p2p topology to connect the Fibre Channel fabric to a node. loop Sets the port’s topology as loop. The port comes up as an FL-Port.
target-port topology p2p See also ● set show-use-hierarchy Display the complete usage hierarchy for a storage element from the top-level element down to the storage-array. Contexts All contexts. Syntax show-use-hierarchy [-t|--targets] path, path,... Arguments Required arguments [-t|--targets] * Comma separated list of target storage elements. path, path,...
sms dump Collects the logs files on the management server. Contexts All contexts. Syntax sms dump [-d|--destination-directory] directory [-t|--target_log] logName Arguments Required arguments [-d| --destination-directory] directory Destination directory for the sms dump logs. Optional arguments [-t|--target_log] logName Collect only files specified under logName from smsDump.xml.
● ● ● ● ● /opt/vs1/backup/*.ini /opt/backup/*.xml /opt/vs1/backup/*.xml /opt/emc/VPlex/*.xml /opt/emc/VPlex/*.properties Upgrade ● ● ● ● ● /var/log/VPlex/cli/capture/* (ndu status files) /tmp/VPlexInstallPackages/*.xml /tmp/VPlexInstallPackages/*.properties /tmp/VPlexInstallPackages/*.log /var/log/install.log system ● ● ● ● ● ● ● ● ● /var/log/warn* /var/log/messages* /var/log/boot.msg /var/log/boot.
Arguments Required arguments [-f| --file] filename * Name of the script file to read and execute. * - argument is positional. Description Filenames use the syntax of the underlying platform. The script file may contain any CLI commands. If the exit command is included, the shell exits immediately, without processing the commands that follow it in the file. Examples In the following example, a text file Source.txt contains only two commands: service@ManagementServer:/var/log/VPlex/cli> cat Source.
Syntax storage-tool dismantle [--do-not-unclaim] [-h | --help] [--verbose] [-f | --force] [-s | --storage-extents= storage-extent [, storage-extent] ...]] Arguments Optional arguments [-h | --help] Displays the usage for this command. [--verbose] Provides more output during command execution. This may not have any effect for some commands. [-f | --force] Do not ask for confirmation. --do-not-unclaim Skips unclaiming of the storage-volume. NOTE: By default, the storage volumes are unclaimed.
Syntax storage-tool compose [-n|--name] name [-g|--geometry] {raid-0|raid-1|raid-c} [-d|--storage-volumes] storage-volume [, storage-volume...] [-m|--source-mirror] source-mirror [-c|--consistency-group] consistency-group [-v|--storage-views] storage-view [, storage-view ...] [-t|--thin] [-h|--help] [--verbose] Arguments Required arguments [-n|--name] name * Specifies the name for the new virtual volume. Must be unique across the system.
Description This command supports building local or distributed (i.e., distributed RAID 1 based) virtual volumes with RAID 0, RAID 1, or RAID C local devices. It does not support creating multi-device storage hierarchies (such as a RAID 1 on RAID 0s on RAID Cs). For RAID 1 local devices, a maximum of eight legs may be specified. If the new virtual volume’s global geometry is not compatible with the specified consistency group or storage views, the virtual volume will not be created.
Example Create a virtual volume with RAID 1 local devices and specified storage volumes: VPlexcli:/> storage-tool compose --name TEST --geometry raid-1 --storage-volumes VPD83T3:60060160cea33000fc39e04dac48e211, VPD83T3:60060160cea33000fb9c532eac48e211, VPD83T3:600601605a903000f2a9692fa548e211, VPD83T3:600601605a903000f3a9692fa548e211 See also ● storage-volume unclaim storage-volume auto-unbanish-interval Displays or changes auto-unbanish interval on a single director. Contexts All contexts.
NOTE: This change in the interval value is not saved between restarts of the director firmware (NDU, director reboots). When the director firmware is restarted, the interval value is reset to the default of 30 seconds. Use the auto-unbanish-interval --director director command to display the current delay (in seconds) for automatic unbanishment on the specified director.
Arguments Required arguments [-d|--storagevolumes] path,path... * List of one or more storage volumes to claim. Optional arguments [--appc] Make the specified storage volumes application consistent. Prevents data already on the specified storage volumes from being deleted or overwritten during the process of constructing a virtual volume. After a virtual volume is constructed using this storage volume, there is no restriction on the access to the data, i.e. the data can be overwritten by host I/O.
If: ● The thin storage allocation pool runs out of space, and ● If this is the last redundant leg of the RAID 1, further writing to a thinly provisioned device causes the volume to lose access to the device. Examples In the following example: ● The ll command in storage-volumes context displays the available storage. ● The claim command claims the specified unclaimed storage volume from the clusters/cluster/storageelements/storage-volumes context.
largest-free-chunk locality operational-status storage-array-name storage-volumetype system-id thin-capable thin-rebuild total-free-space use used-by vendor-specific-name 0x5000144220354910/0x5006016930600523/6, 0x5000144220354910/0x5006016830600523/6, 0x5000144220354911/0x5006016930600523/6, 0x5000144220354911/0x5006016830600523/6 2G ok EMC-CLARiiON-APM00042201310 normal VPD83T3:6006016091c50e005057534d0c17e011 false false 2G claimed [] DGC Claim multiple storage volumes whose names begin with VPD83T3:60
[-c|--cluster] - Cluster on which to claim storage. cluster [-f|--file] file,file... List of one or more files containing hints for storage-volume naming, separated by commas. Required for claiming volumes on storage arrays that do not include their array and serial number in response to SCSI inquiries. [-d|dryRun] Do a dry-run only, do not claim and name the storage volumes. [-t|--settier] list Set a storage tier identifier per storage array in the storage-volume names.
Example Use the --set-tier argument to add or change a storage tier identifier in the storage-volume names from a given storage array.
. . . Claimed 37 storage-volumes in storage array Symm0487 Claimed 64 storage-volumes in storage array HDS20816 Claimed 101 storage-volumes in total. See also ● storage-volume claim ● storage-volume unclaim storage-volume find-array Searches storage arrays for the specified storage-volumes. Contexts All contexts. In /clusters/cluster/storage-elements/storage-volumes context, command is find-array.
storage-arrays/EMC-CLARiiON-APM00111501912 Searching for CLAR1912_10G_Aleve_1_vol_2 Storage-volume: CLAR1912_10G_Aleve_1_vol_2 is in: /clusters/cluster-1/storage-elements/ storage-arrays/EMC-CLARiiON-APM00111501912 . . .
This command also forgets the logical unit for this storage volume. Use the storage-volume forget command to tell the cluster that unclaimed and unreachable storage volumes are not coming back and it is safe to forget them. Forgotten storage volumes are removed from the context tree. Use the --verbose argument to print a message for each volume that could not be forgotten. Use the logical-unit forget command for the functionality supported by the removed arguments.
Arguments Required arguments [-n|--director] path *The director whose banished storage volumes to display. Description Displays the names of storage volumes that are currently banished for a given director. See “Banished storage volumes (LUNs)” in the storage-volume unbanish command description.
Provides more help during command execution. This may not have any effect for some commands. [--verbose] * - argument is positional. Description Lists all thin-capable storage volumes at the given clusters with an abbreviated list of fields for performance. The fields include: name, thin-rebuild status, capacity, current use, and I/O status. If more fields are desired, use the --verbose option. Example Displays thin-capable storage volumes for the specified clusters.
In /clusters/cluster/storage-elements/storage-volumes context, command is resurrect. Syntax storage-volume resurrect [-d|--storage-volume] path[, path...] [-f|--force] Arguments Required arguments [-d|--storage-volume] path[, path...] List of one or more storage volume with dead I/O status to resurrect. Optional arguments [-f|--force] Force the storage-volume resurrect and bypass the test.
StorageVolume Name -----------------------dead_volume Symptom: Storage-volume is dead IO Status --------dead Operational Status -----------------error Health State ---------------critical-failure Examples Resurrect two storage volumes: VPlexcli:/> storage-volume resurrect --storage-volumes Symm1852_BAC,Symm1852_BA8 See also ● cluster status ● storage-volume forget ● storage-volume summary storage-volume summary Displays a list of a cluster's storage volumes. Contexts All contexts.
Table 14. storage-volume summary field descriptions (continued) Field Description Name Name of storage volume. I/O Status alive - I/O is proceeding normally on the storage volume. dead - Metro node has marked the storage volume as dead; I/O cannot proceed on the storage volume. This can happen when a certain number of I/Os to the storage volume fails. unreachable - The storage volume is unreachable. Operational Status ok - The storage volume is functioning normally.
Table 14. storage-volume summary field descriptions (continued) Field Description Meta Slots Total - The total slots used. reclaimable - The number of slots that can be reclaimed. used - The number of slots that are used. storage-volume - The number of slots used for storage volumes. extents - The number of slots used for extents. logging-segments - The number of slots used for logging segments.
Use Capacity None claimed meta-data unclaimed unusable used total 966 824 1 11 143 2 16T When slot usage reaches 90%, this command also displays the following: Meta Slots reclaimable used 57600 storage-volumes 8000 extents 24000 logging-segments 25600 9600 total 64000 Display summary for both clusters in a metro node with no unhealthy storage volumes: VPlexcli:/> storage-volume summary SUMMARY (cluster-1) Storage-Volume Summary (no tier) ---------------------- --------------------Health out-of-date
All contexts. Syntax storage-volume unbanish [-n|--directors] path[, path...] [-d|--storage-volume] path Arguments Required arguments [-n|--directors] path[, path,]... * The context path of the directors to unbanish the given storage volume on. Optional arguments [-d|--storage-volume] path The context path of the storage volume to unbanish. This argument is not required if the current context is a storage-volume or below.
volume list-banished --director director-1-1-A There are no banished storage-volumes on director 'director-1-1-A'. See also ● storage-volume auto-unbanish-interval ● storage-volume list-banished storage-volume unclaim Unclaims the specified previously claimed storage volumes. Contexts All contexts. In /clusters/cluster/storage-elements/storage-volumes context, command is unclaim. Syntax storage-volume unclaim [-b|--batch-size] integer [-d|--storage-volumes] path, [path...
NOTE: The thin-rebuild attribute can only be modified for storage volumes that are either claimed or used. When the unclaimed storage volume is claimed and its state is claimed or used, use the set command to modify the thin-rebuild attribute.
Example VPlexcli:/clusters/cluster-2/storage-elements/storage-volumes> used-by CX4_lun0 /clusters/cluster-1/devices/base0: extent_CX4_lun0_1 CX4_lun0 /clusters/cluster-1/devices/base1: extent_CX4_lun0_2 CX4_lun0 /clusters/cluster-1/devices/base2: extent_CX4_lun0_3 CX4_lun0 /clusters/cluster-1/devices/base3: extent_CX4_lun0_4 CX4_lun0 /clusters/cluster-1/storage-elements/extents/extent_CX4_lun0_5: CX4_lun0 /clusters/cluster-1/storage-elements/extents/extent_CX4_lun0_6: CX4_lun0 syrcollect Collects system co
● RAID information ● Port information ● Back end storage information The output of the command is a zipped xml file named: VPLEXTLA_Config_TimeStamp.zip. in the specified output directory. Files in the default directory are automatically sent to Dell EMC. Use the --directory argument to specify a non-default directory. Output files sent to a non-default directory are not automatically sent to Dell EMC.
Description Displays the sub-context tree. Use the tree command with no arguments to display the sub context tree from the current context. Use the --context subcontext root to display the sub context tree from the specified subcontext. Use the --expand argument to expand the sub-contexts if applicable. Use the --select glob-pattern argument to display contexts in the specified sub-tree that match the glob pattern. The glob pattern may match more contexts that are outside the given sub-tree.
Arguments Optional arguments [-n|--name] name The name of the alias to remove. [-a|--all] Remove all defined aliases. Example In the following example: ● alias displays a list of all aliases on the metro node ● unalias deletes the specified alias ● alias confirms the deletion VPlexcli:/> alias Name Description ------------ ------------------------------------------? Substitutes the 'help' command. GoToDir_2_2A Substitutes the 'cd /engines/engine-2-2/directors/Cluster_2_Dir_2A' command.
Examples Validate system configuration: VPlexcli:/> validate-system-configuration Validate cache replication Checking cluster cluster-1 ... rmg component not found skipping the validation of cache replication. ok Validate logging volume No errors found ok Validate back-end connectivity Cluster cluster-2 0 storage-volumes which are dead or unreachable. 0 storage-volumes which do not meet the high availability requirement for storage volume paths*. 0 storage-volumes which are not visible from all directors.
Arguments Optional arguments [-a|--all] Displays version information for all connected directors. [-n|--directors] context-path * Display version information for only the specified directors. --verbose Displays version information for individual software components on each director. * - argument is positional. Description This command displays version information for all directors, a specified director, or individual software components for each director. Table 15.
Product Version SMSv2 Mgmt Server Base Mgmt Server Software /engines/engine-2-1/directors/director-2-1-B 5.4.0.00.00.10 D35.20.0.10.0 D35.20.0.1 D35.20.0.13 6.5.54.0.
What: NSFW Version: 65.1.54.0-0 What: BIOS Rev Version: 08.50 What: POST Rev Version: 43.80 What: FW Bundle Rev Version: 12.60 What: SSD Model: P30056-MTFDBAA056SAL 118032803 Version: 0005 For director /engines/engine-1-1/directors/director-1-1-B: What: O/S Version: D35.20.0.1 (SLES11) What: Director Software Version: 6.5.54.0.0 What: ECOM Version: 6.5.1.0.0-0 What: VPLEX Splitter Version: 4.1.b_vplex_D35_00_Ottawa_MR1.10-1 What: ZECL Version: 6.5.52.0.0-0 What: ZPEM Version: 6.5.52.0.
Syntax virtual-volume create [-r|--device] context-path [-t|--set-tier] tier [-n | --thin] [-i | --initialize] [--confirm-init] [--verbose] Arguments Required arguments [-r | --device] context-path * Device on which to host the virtual volume. Optional arguments [-t | --set-tier] tier Set the storage-tier for the new virtual volume. [-n | --thin] Specifies whether to create a thin-enabled virtual volume or not.
Table 16. virtual-volume field descriptions (continued) Field Description expandable-capacity Excess capacity not yet exposed to the host by the virtual volume. This capacity is available for expanding the virtual volume. ● Zero (0) - Expansion is not supported on the virtual volume or that there is no capacity available for expansion. ● Non-zero - The capacity available for virtual volume expansion using the storage-volume method.
Table 16. virtual-volume field descriptions (continued) Field Description NOTE: If initialization is requested during the creation of the virtual volume, you must wait until the initialization process is completed successfully to use the virtual volume. If the initialization process fails, restart the process by using the virtual-volume reinitialize command. locality ● local - The virtual volume relies completely on storage at its containing cluster.
About storage tier IDs The storage-tier identifier is displayed to the host as part of the virtual volumes’s product ID. Use the storage-tier identifier to logically group storage. For example, assign Symmetrix arrays as tier 1 storage, and CLARiiON as tier 2 storage. Use the ll command in a specific virtual volume’s context to display the current storage-tier. Use the set command to modify a virtual volume’s storage-tier.
virtual-volume destroy Destroys existing virtual volumes. Contexts All contexts. Syntax virtual-volume destroy [-v|--virtual-volumes] context-path,context-path... [-f|--force] Arguments Required arguments [-v|--virtual-volumes] List of one or more virtual volumes to destroy. Entries must be separated by commas. The context-path, context-path... specified virtual volumes must not be exported to hosts.
virtual-volume expand Non-disruptively increases the capacity of an existing virtual volume. Contexts All contexts. In clusters/cluster/virtual-volumes/ context and below, command is expand. Syntax virtual-volume expand [-v|--virtual-volume] context-path [-e|--extent] extent [-f|--force] Arguments Required arguments [-v|-virtualvolume] context-path * The virtual volume to expand.
expandable-capacity expansion-method expansion-status . . . 4.5G storage-volume - There are two methods to expand a virtual volume; storage-volume and concatenation. ● storage-volume - If the virtual volume has a non-zero expandable-capacity, this command will expand the capacity of the virtual volume by it's full expandable-capacity. To use the storage-volume method of expansion, use this command without the --extent argument.
expansion. In some cases hosts and their applications may need to be restarted once the expansion has completed. Do you wish to proceed ? (Yes/No) yes The expansion of virtual-volume 'Test_volume' has started. VPlexcli:/clusters/cluster-1/virtual-volumes> cd Test_volume/ VPlexcli:/clusters/cluster-1/virtual-volumes/Test_volume> ll Name Value ------------------- -------------block-count 131072 block-size 4K cache-mode synchronous capacity 0.5G consistency-group expandable true expandable-capacity 4.
-------------------------------- ----------------------- -------extent_Symm1554Tdev_061D_1 Symm1554Tdev_061D 100G extent_Symm1554Tdev_0624_1 Symm1554Tdev_0624 100G extent_Symm1554Tdev_0625_1 Symm1554Tdev_0625 100G extent_Symm1554_0690_1 Symm1554_0690 8.43G extent_Symm1554_0691_1 Symm1554_0691 8.43G extent_Symm1554_0692_1 Symm1554_0692 8.43G . . .
[--verbose] Provides more help during command execution. This may not have any effect for some commands. * - argument is positional. Description This command lists virtual volumes at the given clusters with additional thin-property filtering options. The following table describes the filter combinations, and the results that are listed. Thin-capable Thin-enabled Results True true Volumes that are both thin-capable and thin-enabled.
* - argument is positional. Description This command restarts a failed initialization process on a virtual-volume. The command runs only if the initializationstatus field of the virtual volume shows failed. See Also ● ● ● ● virtual-volume virtual-volume virtual-volume virtual-volume create destroy expand provision virtual-volume set-thin-enabled Sets the thin-enabled property to either true or false for the given virtual volumes. Contexts All contexts.
The virtual-volume set-thin-enabled command does not fail even if virtual volumes are not thin-capable. Virtual volumes that are not thin-capable are skipped. For brevity of the user messages, the regular output of this command only includes: ● the number of volumes that are set as thin-enabled (or not set) ● the number of volumes that are skipped If you want detailed output showing exactly which volumes are set as thin-enabled or skipped, use the --verbose option. However, the output can be very long.
Displays a summary including devices per locality (distributed versus local), cache-mode, and total capacity for the cluster. Displays any volumes with an expandable capacity greater than 0, and whether an expansion is in progress. If the --clusters argument is not specified and the command is executed at or below a /clusters/cluster context, information is displayed for the current cluster. Otherwise, virtual volumes of all clusters are summarized. Table 17.
Table 17. virtual-volume summary field descriptions (continued) Field Description Expansion summary ● virtual-volume name - Name of any volume with expandable capacity greater than 0 or an expansion underway. ● expandable-capacity - Additional capacity (if any) added to the back end storage volume not yet added to the metro node virtual volume. ● capacity - Current capacity of the virtual volume. ● expansion-status - Indicates whether an expansion is possible is in progress, or has failed.
See also ● ● ● ● ● ds summary export port summary export storage-view summary extent summary local-device summary wait Causes a wait until specified context-tree conditions are met. Contexts All contexts. Syntax wait [-a [-v [-t [-c | --context-list] [, context-list ...] | --attribute= attribute] | --value= value] | --timeout= timeout] [-h | --help] [--verbose] Arguments Required arguments [-c | --context-list] [, context-list ...
webserver Start, stop, or restart the Webserver. Contexts All contexts. Syntax webserver [stop | start | restart] [-h | --help] [--verbose] Arguments Optional arguments [-h | --help] Displays the usage for this command [--verbose] Provides additional output during command execution. This may not have any effect for some commands. Description This command starts, stops, or restarts the Webserver.
Index A alias 29 array fail 31 array:claim 30 array:re-discover 32 array:used-by 34 audience 9 B Batch migration:perform a migration 43 batch-migrate check-plan 40 batch-migrate clean 41 batch-migrate create-plan 43 batch-migrate:check-plan;check-plan, batch-migrate 40 batch-migrate:pause;pause:batch-migrate 45 batch-migrate:remove;remove:batch-migrate 46 batch-migrate:resume;resume:batch-migrate 47 batch-migrate:start;start:batch-migrate 48 batch-migrate:summary;summary:batch-migrate 50 C capture:begin;b
director firmware show-banks 136 director forget 137 director shutdown 140 director tracepath 142 director traceroute 142 director:commission;commission, director 133 director:passwd;passwd, director 138 director:ping;ping 139 director:shutdown;shutdown:director 140 dirs 143 disconnect 144 Display:multiple objects using globs 236 Display:object’s attributes 236 Display:object’s attributes and contexts 236 Display:operational status 236 distributed device 155 dm migration pause 148 dm:migration cancel;migrat
log:filter create;create:log filter 222 log:filter destroy;destroy:log filter 224 log:filter list;list:log filter 224 log:source create;create:log source 225 log:source destroy;destroy:log source 226 log:source list;list:log source 227 logging-volume detach-mirror 232 logging-volume:add-mirror;add-mirror, logging-volume 228 logging-volume:create;create:logging-volume 228 logging-volume:destroy;destroy:logging-volume 232, 234 logical-unit forget 235 ls;list 236 R M schedule:add 278 schedule:modify 280 sch
virtual-volume:expand (back end) 332 virtual-volume:re-initialize 336 virtual-volume:summary 338 volume:summary;summary:volume 338 W Wait 341 Webserver 342 wildcard 13
