Dell EMC Storage Systems CLI Guide for the metro node appliance 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. © 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.......................................................................................................12 Logging into the CLI.....................
capture begin..................................................................................................................................................................... 53 capture end.........................................................................................................................................................................54 capture pause......................................................................................................................................
device mirror-isolation show..........................................................................................................................................121 device resume-link-down...............................................................................................................................................123 device resume-link-up....................................................................................................................................................
export storage-view destroy.........................................................................................................................................183 export storage-view find............................................................................................................................................... 184 export storage-view find-unmapped-volumes.........................................................................................................
monitor stat-list...............................................................................................................................................................250 ndu pre-check.................................................................................................................................................................. 251 ndu pre-config-upgrade..................................................................................................................................
virtual-volume create......................................................................................................................................................315 virtual-volume destroy....................................................................................................................................................319 virtual-volume expand..............................................................................................................................................
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.
CAUTION: Indicates a hazardous situation which, if not avoided, could result in minor or moderate injury. NOTE: Addresses practices not related to personal injury. NOTE: Presents information that is important, but not hazard-related. Typographical conventions Dell EMC uses the following type style conventions in this document: Table 1.
Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to vplex.doc.feedback@dell.com.
2 Using the VPlexcli Topics: • • • • • • • Logging into the CLI Password Policies Logging out from the CLI CLI context tree Context tree searching Navigate the CLI context tree Using CLI commands Logging into 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 for the metro node appliance. 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.
Tab completion Use the Tab key to: ● vplex_c_display_valid_contexts_and_commands ● vplex_c_display_command_arguments Display valid contexts and commands Press Tab after typing a partial context path to display a list of valid commands or contexts for the current context: About this task VPlexcli:/> cd /clusters/cluster-1/ connectivity/ consistency-groups/ devices/ exports/ performance-policies/ storage-elements/ system-volumes/ virtual-volumes/ VPlexcli:/> cd /clusters/cluster-1/ Display command arg
● Use a second * wildcard specify all directors: ll clusters/cluster-*/directors/director-1-1-*/ports/ ** wildcard Use the ** wildcard to match all contexts and entities between two specified objects. For example, to display all director ports without using wildcards: ll clusters/cluster-1/directors/director-1-1-A/ports ll clusters/cluster-1/directors/director-1-1-B/ports . .
/clusters/cluster-2/directors/director-2-1-A/ports: Name Address Role Status RxPower[uW] TxPower[uW] Temp[C] Speed Topology ----- ------------------ --------- ------ ----------- ----------- ------- ---------------IO-00 0xc001445a80340000 front-end up 505 797 42 16Gbits/s p2p IO-01 0xc001445a80340100 front-end up 551 727 41 16Gbits/s p2p IO-02 0xc001445a80340800 back-end up 410 766 45 16Gbits/s p2p IO-03 0xc001445a80340900 back-end up 462 682 44 16Gbits/s p2p LC-00 128.221.250.
Command globbing Command globbing combines wildcards and context identifiers in a single command. Globbing can address multiple entities using a single command. Example 1 To display the status of all the director ports on a large configuration using no wildcards, type: VPlexcli:/> ll clusters/cluster-*/directors/director-1-1-*/ports/ for cluster and director. Using the * wildcard reduces this task to a single command.
Cluster cluster-2 This cluster has This cluster has This cluster has Cluster cluster-1 This cluster has This cluster has This cluster has 1 storage-volumes which are dead or unreachable 0 storage-volumes which do not have dual paths 0 storage-volumes which are not visible from all directors 3 storage-volumes which are dead or unreachable 0 storage-volumes which do not have dual paths 0 storage-volumes which are not visible from all directors Search command history ● To display the last commands typed, pre
3 Commands Topics: • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 24 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
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 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 consistency-group resume-at-loser consistency-group set-detach-rule no-automatic-winner consistency-group set
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 26 ds rule-set what-if ds summary 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 addport export storage-view addvirtualvolume export storage-view checkconfig export storage-view create export
• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 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 recover ndu start ndu status plugin addurl plugin listurl plugin register popd pushd rebuild set-transfer-size rebuild show-transfer-size rebuild status
• • • • • • • • • • • • 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 objects down to the storage-volume level, and optionally unclaims the storage volumes. Contexts All contexts.
If the --force argument is used, no confirmation is displayed before the dismantle. Examples In the following example, the specified volume is dismantled: VPlexcli:/clusters/cluster-1> advadm dismantle --verbose --virtual-volumes virtualvolumes/test_r1_vol --force destroyed virtual volume /clusters/cluster-1/virtual-volumes/test_r1_vol destroyed /clusters/cluster-2/devices/test_r1 Destroyed 1 out of 1 targetted extents.
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. Description Aliases are shortcuts for frequently used commands or commands that require long strings of context identifiers.
--------------mon-Dir-1-1-B -------------------------------------------------------------Substitutes the 'cd /monitoring/directors/director-1-1-B' command. Use an alias: VPlexcli:/> mon-Dir-1-1-B VPlexcli:/monitoring/directors/director-1-1-B> See also ● ls ● unalias array claim Claims and names unclaimed storage volumes for a given array. Contexts All contexts.
Other storage arrays require a hints file generated by the storage administrator using the array’s command line. The hints file contains the device names and their World Wide Names. Use the --mapping-file argument to specify a hints file to use for naming claimed storage volumes. File names will be used to determine the array name. Use the --tier argument to add a storage tier identifier in the storage-volume names. This command can fail if there is not a sufficient number of meta-volume slots.
array re-discover Re-discovers an array, and makes the array's storage volumes visible to the metro node. Contexts Cluster-specific context and lower. Syntax array re-discover [-a|--array]context-path [-c|--cluster] cluster-id [-d|--hard] [-f|--force] Arguments Required arguments [-a|--array] context-path * Context path that specifies the storage-array to re-discover. [-c|--cluster] cluster-id Cluster ID of the target cluster. Optional arguments [-d|--hard] ● Perform a hard rediscover.
Newer protocol-compliant SCSI devices return a notification code when the exported set changes, and may not require manual synchronization. Older devices that do not return a notification, must be manually synchronized. ● When the array is not experiencing I/O (the transport interface is idle), there is no mechanism by which to collect the notification code.
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
/clusters/cluster-1/devices/dev_clus1: extent_SV1_1 SV1 /clusters/cluster-1/system-volumes/log1_vol: 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/syst
/clusters/cluster-1/storage-elements/extents/extent_6006016061211100363da903017ae011_1: SV1 VPlexcli:/clusters/cluster-1/storage-elements/storage-arrays> array used-by --array DellEMC-PowerStore-JJ30643 Used-by details for storage-array DellEMC-PowerStore-JJ30643: /clusters/cluster-1/storage-elements/storage-arrays> array used-by --array E See also ● storage-volume find-array ● storage-volume summary back-end degraded list Displays a list of currently degraded I-Ts. Contexts All contexts.
-------------- ------------- -------------------------------------------- -----------------director-1-1-A A1-FC00 0xc00144878bda0800 surry-1 Manually isolated A1-FC01 0xc00144878bda0900 APM00164919257 Manually isolated director-1-1-B B1-FC01 0xc00144878bda8900 APM00164919257 Manually isolated -----------------0x5000144260321e00 EMC-Invista-rc0x5006016547e01af9 EMC-CLARiiON0x5006016547e01af9 EMC-CLARiiON- List all degraded I-Ts grouped by array VPlexcli:/> back-end degraded list --group-by array Degraded I
[--all] Recover all currently degraded I-Ts. Description Assert that the specified I-Ts are healthy and move them out of their degraded state. Examples Recover a specific degraded I-T.
Arguments Required arguments 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. [-f|--file] pathname Description Attempts to cancel every migration in the specified batch file. If the command encounters an error, the command prints a warning to the console and continues until every migration listed in the file has been processed.
[-f|--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.
Syntax batch-migrate clean [-f|--file] pathname [-e|--rename-targets] Arguments Required arguments [-f|--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 rename the target devices and virtual volumes to the source device names. [-e|--renametargets] * argument is positional.
● batch-migrate remove batch-migrate commit Commits the specified batch migration. Contexts All contexts. Syntax batch-migrate commit [-f|--file] pathname Arguments Required argument [-f|--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/clion the management server. Description Attempts to commit every migration in the batch.
● batch-migrate remove batch-migrate create-plan Creates a batch migration plan file. Contexts All contexts. Syntax batch-migrate create-plan [-f|--sources] local-devices [-t|--targets] local-devices [--file] pathname [--force] Arguments Required arguments [-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.
Examples Example: perform a batch migration 1. Create a migration plan. Use the batch-migrate create-plan command to create a plan to migrate the volumes on all the devices at cluster-1 to the storage at cluster-2: VPlexcli:/> batch-migrate create-plan migrate.txt --sources /clusters/cluster-1/ devices/* --targets /clusters/cluster-2/devices/* 2. Use the batch-migrate check-plan command to check the plan: VPlexcli:/> batch-migrate check-plan migrate.
See also ● ● ● ● ● ● ● ● ● batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate cancel check-plan clean commit pause remove resume start summary batch-migrate pause Pauses the specified batch migration. Contexts All contexts. Syntax batch-migrate pause [--file] pathname Arguments Required arguments --file pathname Directory and filename of migration plan file. Relative paths can be used.
See also ● ● ● ● ● ● ● ● ● batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate cancel check-plan clean commit create-plan remove resume start summary batch-migrate remove Removes the record of the completed batch migration. Contexts All contexts. Syntax batch-migrate remove [--file] Required arguments Arguments Required arguments --file pathname Directory and filename of migration plan file. Relative paths can be used.
● ● ● ● ● ● ● ● batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate check-plan clean commit create-plan pause resume start summary batch-migrate resume Attempts to resume every migration in the specified batch. Contexts All contexts. Syntax batch-migrate resume [--file] pathname Arguments Required arguments --file pathname Directory and filename of migration plan file. Relative paths can be used.
● batch-migrate start ● batch-migrate summary batch-migrate start Starts the specified batch migration. Contexts All contexts. Syntax batch-migrate start [--file] pathname [-s|transfer-size] 40K - 128M --force --paused 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.
Individual migrations may ask for confirmation when they start. Use the --force argument to suppress these requests for confirmation. Batch migrations across clusters can result in the following error: VPlexcli:/> batch-migrate start /var/log/VPlex/cli/migrate.txt The source device 'SveTest_tgt_r0_case2_1_0002' has a volume 'SveTest_tgt_r0_case2_1_0002_vol' in a view. Migrating to device 'SveTest_src_r0_case2_2_0002' will create a synchronous distributed device.
● ● ● ● ● batch-migrate pause batch-migrate remove batch-migrate resume batch-migrate summary dm migration start batch-migrate summary Displays a summary of the batch migration. Contexts All contexts. Syntax batch-migrate summary [--file] pathname [-v|--verbose] 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.
Table 3. batch migration summary field descriptions (continued) Field Description --verbose and non --verbose output Processed n migrations... Of the number of source-target pairs specified in the batch migration plan, the number that have been processed. committed Of the number of source-target pairs that have been processed, the number that have been committed. completed Of the number of source-target pairs that have been processed, the number that are complete.
error: cancelled: no-record: 0 0 0 See also ● ● ● ● ● ● ● ● ● batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate batch-migrate cancel check-plan clean commit create-plan pause remove resume start capture begin Begins a capture session. Contexts All contexts. Syntax capture begin [-s|session] session name [-c|capture-directory] capture-directory Arguments Required arguments [-s|--session] session name * Name of capture session.
Capture sessions can have nested capture sessions but only the capture session at the top of the stack is active. Use the capture end command to end the capture session. Use the capture replay command to resubmit the captured input to the shell. Examples In the following example, the capture begin command starts a capture session named TestCapture. Because no directory is specified, output files are placed in the /var/log/VPlex/cli/capture directory on the management server.
capture pause Pauses the current capture session. Contexts All contexts. Syntax capture pause Description Pause/resume operates only on the current capture session. 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.
[-c| --capture-directory] directory * Directory where existing captured session is located. Default directory /var/log/VPlex/cli/capture/recapture * - argument is positional. Description Replays the commands in the stdin.txt file from the specified capture session. Output of the replayed capture session is written to the /var/log/VPlex/cli/capture/recapture directory on the management server. Output is the same four files created by capture begin. Example Replay a capture session.
Examples Resume the current capture session. VPlexcli:/> capture resume See also ● ● ● ● capture capture capture capture begin end pause replay 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.
Return to the context immediately above the current context: VPlexcli:/monitoring/directors/director-1-1-B> cd .. VPlexcli:/monitoring/directors> Navigate directly to a context from any other context: VPlexcli:/clusters/clusters-1/fans> cd /clusters/cluster-1/fans/ 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.
Examples In the following example: ● The cluster add command adds two clusters.
Description Dumped data includes: ● ● ● ● ● ● ● I/O port configurations Disk information, including paths from the directors to the storage volumes Device configuration and capacity Volume configuration Initiators View configuration System-volume information 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.
In /clusters context, command is expel. Syntax cluster expel [-c|--cluster] cluster [-f|--force] 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.
health-state: health-indications: Cluster cluster-2 operational-status: transitioning-indications: transitioning-progress: health-state: health-indications: degraded 1 suspended Devices degraded suspended exports,suspended volumes degraded 2 suspended Devices 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.
● No globally visible devices at the target cluster. Use the following steps to forget a cluster: 1. If connected, use the cluster forget command on the target cluster to forget the other clusters. 2. Use the cluster forget command on all other clusters to forget the target cluster. This command does not work if the clusters have lost communications with each other. If a cluster is down, destroyed, or removed, use the cluster expel command to expel it.
-[ -c | --cluster=] cluster context Specifies the context path of the cluster to show the remote devices.
c2_Dr_device0040_2 - - - c2_Dr_device0039_2 - - - c2_Dr_device0038_2 - - - c2_Dr_device0037_2 - - - c2_Dr_device0036_2 - - - 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.
When a cluster completes shutting down, the following log message is generated for each director at the cluster: 'Director shutdown complete (cluster shutdown)' Examples In the following example: ● The cluster shutdown command without the --force argument starts the shutdown of the specified cluster. Because the --force argument was not used, a prompt to continue is displayed. ● The cluster summary commands display the transition to shutdown.
director-names island-id operational-status transition-indications transition-progress health-state health-indications [DirA, DirB] not-running [] [] unknown [] 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.
Table 4. cluster status field descriptions (continued) Field Description ● transitioning - Components of the software are recovering from a previous incident (for example, the loss of a director or the loss of an intercluster link). transitioning -indications Additional information if the transitioning-progress is anything other than blank. transitioning-progress Indicates progress for supported transitions.
Table 4. cluster status field descriptions (continued) Field Description ● partial - Some port-groups have a status of error or fail, but at least one port-group has a status of ok or warning. WAN COM is operating (possibly minimally) through at least one channel. Performance is degraded. ● none - All port-groups have a status of either error or fail. wan-com is not operational. ● not-applicable - The system is a single-cluster (i.e. Local) system. Validating wan-com connectivity is not applicable.
Table 5. cluster summary field descriptions (continued) Field Description Operational Status ● degraded - The cluster is not operating as configured and is not currently transitioning. Examples include: degraded redundancy level (a director is dead), all exports switched to write through because of hardware health problems, suspended virtual volumes, suspended exports, storage volumes not visible from all directors, meta-volume not yet processed.
Islands: Island ID --------1 Clusters -------------------cluster-1, cluster-2 Display cluster summary for metro node Metro configuration with a inter-cluster link outage: 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 false ok true false ok Health Clusters -------
[-c|--cluster] context path Arguments Required arguments [-c|--cluster] context path Cluster to unexpel. Description Clears the expelled flag for the specified cluster, allowing it to rejoin the metro node. Examples To manually unexpel a cluster, do the following: 1. Use the cluster summary command to verify that the cluster is expelled.
5. Use the cluster summary command to verify all clusters are in one island and working as expected.
● --diag-ext-.tar.gz- Contains java heap dump, fast trace dump, two latest core files, and two latest core files ( if --noextended is used, then no core file is collected). ● --diag-.tar.gz - Contains everything else including a direcotry, /opt/recoverpoint which contains the RecoverPoint splitter logs in a .zip file (vpsplitter.log.xx, vpsplitter.log.periodic_env, and vpsplitter.log.current_env). NOTE: If --noextended is used, then this file is not available.
Syntax configuration get-product-type Description Displays whether the system is a Local or Metro configuration . 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.
Example Join clusters at the specified remote IP address: VPlexcli:/> configuration join-clusters -i 10.103.97.76 Verifying the connectivity of all the directors... Verifying that all the pre-conditions for director connectivity are satisfied... All the directors are properly connected to each other... Verifying island ID Running the Join Cluster task Verifying island ID Added cluster 'cluster-1' to system (cluster-2). Join Cluster task completed. The clusters are now joined and ready for use.
Specify two or more storage volumes. Storage volumes must be: - unclaimed - on different arrays 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.
Detroit_LOGGING_VOL_vol Detroit_METAVolume1 Detroit_METAVolume1_backup_2010Dec23_052818 Detroit_METAVolume1_backup_2011Jan16_211344 See also ● configuration remote-clusters clear-addresses ● configuration show-meta-volume-candidates ● configuration system-setup configuration show-meta-volume-candidates Display the volumes which meet the criteria for a metro node meta volume. Contexts All contexts.
VPD83T3:60000970000192601707533031333135 98.5G EMC alive traditional EMC-SYMMETRIX-192601707 VPD83T3:60000970000192601707533031333136 98.5G EMC alive traditional EMC-SYMMETRIX-192601707 VPD83T3:60000970000192601707533031333137 98.5G EMC alive traditional EMC-SYMMETRIX-192601707 VPD83T3:60000970000192601707533031333138 98.
[-d | --storagevolumes= volume [, volume ...] Creates a temporary meta volume from one or more storage volumes. After the command completes successfully, the command destroys the temporary meta volume. The specified storage volumes must not be empty, and must be at the implied or specified cluster. Type the system IDs for the storage volumes separated by commas. Specify two or more storage volumes. Storage volumes should be on different arrays.
Arguments Required arguments Description director Director to discover. Optional arguments Description [-d|--storage-volumes] Display connectivity from the specified director to storage volumes. [-i|--initiators] Display connectivity from the specified director to initiators. [-n|--directors] Display connectivity from the specified director to other directors. [-f|--file] filename Save the output in the specified file.
Arguments Optional arguments Description [-h | --help] Displays the usage for this command [--verbose] Provides additional output during command execution. This may not have any effect for some commands. [-n | --directors] context path , context path ... Source director(s) for which connectivity should be reported. [-f | --file] filename Writes the connectivity report to the named file instead of echoing it. If the file exists, any previous contents will be lost.
[-u| ] uuid Arguments Optional arguments Description [-h | --help] Displays the usage for this command [--verbose] Provides additional output during command execution. This may not have any effect for some commands. [-n | --directors] context path , context path ... Source director(s) for which connectivity should be reported. [-f | --file] filename Writes the connectivity report to the named file instead of echoing it. If the file exists, any previous contents will be lost.
[-h | --help] Displays the usage for this command [--verbose] Provides additional output during command execution. This may not have any effect for some commands. [-n | --directors] context path , context path ... Source director(s) for which connectivity should be reported. [-f | --file] filename Writes the connectivity report to the named file instead of echoing it. If the file exists, any previous contents will be lost.
[--verbose] Provides additional output during command execution. This may not have any effect for some commands. [-n | --directors] context path , context path ... Source director(s) for which connectivity should be reported. [-f | --file] filename Writes the connectivity report to the named file instead of echoing it. If the file exists, any previous contents will be lost. You can write the output to a file by using an absolute path, or by using a path relative to the CLI directory.
Description Displays connectivity, but does not perform connectivity checks. Displays which ports can talk to each other. See also ● connectivity director connectivity validate-be Checks that the back-end connectivity is correctly configured. Contexts All contexts. Syntax connectivity validate-be [-d | --detailed] [-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.
Examples Entering the connectivity validate-be command without any arguments provides a summary output as shown. VPlexcli:/> connectivity validate-be Cluster cluster-1 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. 0 storage-volumes which have more than supported (4) active paths from same director.
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. 0 storage-volumes which have more than supported (4) active paths from same director. *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.
[--verbose] Provides more output during command execution. This may not have any effect for some commands. Description Verifies the expected local-com connectivity. This command assembles a list of expected local-com connectivity, compares it to the actual local-com connectivity, and reports any missing or extra connections. This command verifies only IP- or Fibre Channel-based local-com connectivity.
Description Adds the specified virtual volume to a consistency group. The properties of the consistency group immediately apply to the added volume. NOTE: Only volumes with visibility and storage-at-cluster properties which match those of the consistency group can be added to the consistency group. Additionally, you cannot add a virtual volume to a consistency group if the initialization status of the virtual volume is failed or in-progress.
● consistency-group remove-virtual-volumes ● Dell EMC Administration Guide for metro node consistency-group choose-winner Selects a winning cluster during an inter-cluster link failure. Contexts All contexts. In /clusters/cluster-n/consistency-groups/group-name context, command is choose winner.
Examples Select cluster-2 as the winner for consistency group TestCG: VPlexcli:/clusters/cluster-2/consistency-groups/TestCG> choose-winner --cluster cluster-2 WARNING: This can cause data divergence and lead to data loss. Ensure the other cluster is not serving I/O for this consistency group before continuing. Continue? (Yes/No) Yes In the following example: ● l The two ls commands show a consistency group my_cg1 when an inter-cluster link outage has occurred.
operational-status passive-clusters read-only recoverpoint-enabled storage-at-clusters virtual-volumes visibility [(cluster-1,{ summary:: suspended, details:: [cluster-departure, rebuilding-across-clusters] }), (cluster-2,{ summary:: ok, details:: [] })] [] false false [] [dr1_read_write_latency_0000_12_vol] [cluster-1, cluster-2] Contexts: advanced recoverpoint See also ● consistency-group resume-at-loser ● consistency-group summary ● Dell EMC Administration Guide for metro node consistency-group conve
Description To convert a distributed consistency group to a local consistency group, this command converts all distributed devices under each virtual volume to local distributed devices. The legs on the specified cluster become the supporting device of the virtual volumes. All target devices should not be migration temporary devices and should not be exported to any other cluster. consistency-group create Creates and names an empty consistency group. Contexts All contexts.
● auto-resume-at-loser - whether the loser automatically resumes I/O when the inter- link is repaired after a failure. Default is true. Modified using the set command in /clusters/cluster-n/consistency-groups/consistencygroup-name/advanced context. ● virtual-volumes - member volumes of the consistency group. Modified using the consistency-group addvirtual-volumes and consistency-group remove-virtual-volumes commands.
consistency-group destroy Destroys the specified empty consistency groups. Context All contexts. In /clusters/cluster-n/consistency-groups/group-name context, command is destroy. Syntax consistency-group destroy [-g|--consistency-group] consistency-group, consistency-group, ... --force Arguments Required arguments [-g|--consistency-group] consistency-group, consistency-group, ... * List of one or more comma-separated context paths of the consistency groups to destroy.
consistency-group list-eligible-virtual-volumes Displays the virtual volumes that are eligible to be added to a specified consistency group. Contexts All contexts. Syntax consistency-group list-eligible-volumes [-g|consistency-group] consistency-group Arguments Required arguments [-g|--consistencygroup] consistency-group The consistency group for which the eligible virtual volumes shall be listed.
See also ● ● ● ● consistency-group consistency-group consistency-group Dell EMC Administration add-virtual-volumes remove-virtual-volumes summary Guide for metro node consistency-group remove-virtual-volumes Removes one or more virtual volumes from the consistency group. Contexts All contexts. In /clusters/cluster-n/consistency-groups/group-name context, command is remove-virtual-volumes. Syntax consistency-group remove-virtual-volumes [-v|--virtual-volumes] virtual-volume, virtual-volume, ...
Examples In the following example: ● The ls command displays the virtual volumes in consistency group TestCG. ● The consistency-group remove-virtual-volumes command removes a specified volume from the consistency group. ● The ls command displays the change. VPlexcli:/> ls /clusters/cluster-1/consistency-groups/TestCG /clusters/cluster-1/consistency-groups/TestCG: ------------------------------- ---------------------------------------------. . .
[-g|--consistency-group consistency-group [-f|--force] Arguments Required arguments [-c|--cluster] cluster - * The cluster whose data image will be used as the source for resynchronizing the data images on both clusters. [-g|--consistency-group] consistency-group - * The consistency group on which to resolve the conflicting detach. Optional arguments [-f|--force] - Do not prompt for confirmation. Allows this command to be run using a non-interactive script. * - argument is positional.
● The ls command shows the operational-status as ok, requires-resolve-conflicting-detach at both clusters. ● The resolve-conflicting-detach command selects cluster-1 as the winner. Cluster-2 will have its view of the data discarded. I/O is suspended on cluster-2. ● The ls command displays the change in operational status. ○ At cluster-1, I/O continues, and the status is ok. ○ At cluster-2, the view of data has changed and so I/O is suspended pending the consistency-group resume-atloser command.
consistency-group resume-at-loser If I/O is suspended due to a data change, resumes I/O at the specified cluster and consistency group. Contexts All contexts (at the losing cluster). In /clusters/cluster-n/consistency-groups/group-name context, command is resume-at-loser. Syntax consistency-group resume-at-loser [-c|--cluster] cluster [-s|--consistency-group]consistency-group [-f|--force] Arguments Required arguments [-c|--cluster] cluster * The cluster on which to roll back and resume I/O.
Examples VPlexcli:/clusters/cluster-2/consistency-groups/TestCG> resume-at-loser This may change the view of data presented to applications at cluster cluster-2. You should first stop applications at that cluster. Continue? (Yes/No) Yes In the following example: ● The ls command shows consistency group cg1 as ‘suspended, requires-resume-at-loser’ on cluster-2 after cluster-2 is declared the losing cluster during an inter-cluster link failure. ● The resume-at-loser command restarts I/O on cluster-2.
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. In /clusters/cluster-n/consistency-groups/group-name context, command is set-detach-rule no-automaticwinner. Syntax consistency-group set-detach-rule no-automatic-winner [-g|--consistency-group] consistency-group, consistency-group,...
See also ● ● ● ● ● consistency-group consistency-group consistency-group consistency-group Dell EMC Administration choose-winner resume-after-rollback set-detach-rule active-cluster-wins set-detach-rule winner Guide for metro node consistency-group set-detach-rule winner Sets the detach-rule for one or more synchronous consistency groups to winner. The specified cluster becomes the winner after the specified number of seconds. Contexts All contexts.
NOTE: This command requires user confirmation unless the --force argument is used. In the event of a cluster failure or departure, this rule-set results in I/O continuing on the selected cluster only. I/O will be suspended at all other clusters. If metro node Witness is deployed it will overrides this selection if the selected cluster has failed.
See also ● consistency-group create ● consistency-group destroy ● Dell EMC Administration Guide for metro node date Displays the current date and time in Coordinated Universal Time (UTC). Contexts All contexts. Syntax date Examples VPlexcli:/> date Tue Jul 20 15:57:55 UTC 2010director ping describe Describes the attributes of the given context. Contexts All contexts with attributes.
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 [] . . .
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.
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. The following is an example of the warning message: VPlexcli:/> device attach-mirror --device xio_device --mirror vnx_device Thin-capability is only supported with homogeneous storage-array types. The top-level device 'xio_device' is supported by XtremIO but the mirror 'vnx_device' is supported by CLARiiON.
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 /clusters/cluster/directors context, command is decommission.
director fc-port-stats Displays/resets Fibre Channel port statistics for a specific director. Contexts All contexts. In /clusters/cluster/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 /clusters/cluster/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:/clusters/cluster-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 clusters/cluster/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 clusters/cluster/directors context displays director IDs.
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 /clusters/cluster/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 clusters/cluster/directors context, command is uptime. Syntax director uptime Description Uptime measures the time a machine has been up without any downtime.
VPlexcli:/clusters/cluster-1> cd /directors/ VPlexcli:/clusters/cluster-1/directors> dirs [/clusters/cluster-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 exec command Description The program can be executed with zero or more arguments. NOTE: The correct syntax for program names and arguments depends on the host system. Example To display the date and time on Director-1-1-A: VPlexcli:/> exec ssh 128.221.253.35 date Tue Sep 21 14:32:52 UTC 2010 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.
export initiator-port discovery Discovers initiator ports on the front-end fabric. Contexts Cluster context and below. In /clusters/cluster/exports context, command is initiator-port discovery. In /clusters/cluster/exports/initiator-ports context, command is discovery.
FC00, P000000003CB000E6-B1- FC00, P000000003CB001CB-B1-FC00 . . . VPlexcli:/> export initiator-port discovery --cluster cluster-1 Name iSCSI Name Port Names ------------------------ -------------------------------------------------------------------dcca-esxprd19-iscsi-init iqn.1998-01.com.
export initiator-port register Registers an initiator-port, associating it with a SCSI address. Contexts All contexts. In /clusters/cluster/exports context, command is initiator-port register. In /clusters/cluster/exports/initiator-ports context, command is register.
Registers an initiator-port and associates it with a SCSI address. For Fibre Channel, the SCSI address is represented by a WWN pair. See also ● ● ● ● export initiator-port discovery export initiator-port unregister export target-port renamewwns set export initiator-port register-host Creates a view, and registers each port WWN /name pair as an initiator port in that view. Contexts All contexts. In /clusters/cluster/exports context, command is initiator-port register-host.
See also ● export initiator-port discovery ● export initiator-port unregister export initiator-port show-logins Displays the initiator port logins to the metro node front-end target ports. Context All contexts. Syntax export initiator-port show-logins [-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.
cluster-2 initiator_22 P000000003CA00150-A0-FC00 P000000003CB00150-B0-FC00 Shows no target port logins for initiator port 22: VPlexcli:/> export initiator-port show-logins initiator_22 Cluster Names Initiator Port Names Target Port Names -----------------------------------------------------------------cluster-2 initiator_22 None See also ● ● ● ● export export export export initiator-port initiator-port initiator-port initiator-port discovery register register-host unregister export initiator-port un
See also ● export initiator-port register export port summary Displays a summary of exported ports for one or more clusters. Contexts All contexts. In /clusters/cluster/exports context, command is port summary. In /clusters/cluster/exports/ports context, command is summary. 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).
P0000000046753D21-ETH07 healthy true 1 55 views ----1 1 1 1 1 1 1 1 virtual-volumes --------------55 55 55 55 55 55 55 55 Total 8 ports, 0 unhealthy.
Display port health using verbose argument: VPlexcli:/clusters/cluster-1/exports/ports> summary --verbose 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 . . .
Arguments Required arguments [-i|--initiator-ports] initiator-ports [, initiator-ports...] * List of one or more initiator ports to add to the view. Entries must be separated by commas. Optional arguments [-v|--view] context-path View to which to add the specified initiator port(s). * - argument is positional. Description Select ports from two different directors so as to maximize redundancy.
[-p|--ports] context-path,contextpath ... * List of one or more ports to be added to the view. Entries must be separated by commas. Optional arguments [-v|--view] context-path Storage view to which to add the specified ports. * - argument is positional. Description Use the ll /clusters/cluster/exports/ports command to display ports on the cluster.
LUN-virtual-volume pairs must be enclosed in parentheses (). Virtual volumes and LUN-virtualvolume pairs can be typed on the same command line. When only virtual volumes are specified, the next available LUN is automatically assigned by metro node. Optional arguments [-v|--view] contextpath View to add the specified virtual volumes to.
-----------------------controller-tag initiators operational-status port-name-enabled-status -------------------------------------------------[] stopped [P000000003CA00147-A1-FC01,true,suspended, P000000003CB00147-B0-FC01,true,suspended] [P000000003CA00147-A1-FC01, P000000003CB00147-B0-FC01] ports virtual-volumes [(5,TestDisDevice_vol,VPD83T3:6000144000000010a0014760d64cb325,16G)] Add a virtual volume to a view using the --force option from the root context: VPlexcli:/> export storage-view addvirtualvolu
Checking cluster cluster-2: No errors found for cluster cluster-2. Volume dd_13_vol is exported multiple times: view: LicoJ009, lun: 14 view: LicoJ010, lun: 14 Volume dd_16_vol is exported multiple times: view: LicoJ009, lun: 17 view: LicoJ010, lun: 17 Volume dd_12_vol is exported multiple times: view: LicoJ009, lun: 13 view: LicoJ010, lun: 13 Volume dd_19_vol is exported multiple times: view: LicoJ009, lun: 20 view: LicoJ010, lun: 20 . . .
Description A storage view is a logical grouping of front-end ports, registered initiators (hosts), and virtual volumes used to map and mask LUNs. Storage views are used to control host access to storage. For hosts to access virtual volumes, the volumes must be in a storage view. A storage view consists of: ● One or more initiators. Initiators are added to a storage view using the export storage-view addinitiatorport command. ● One or more virtual volumes.
Arguments Required arguments [-v|--view] context-path ... * Storage view to destroy. Optional arguments Force the storage view to be destroyed even if it is in use. [-f|--force] * - argument is positional. Description Destroys the specified storage view.
Arguments Optional arguments [-c|--cluster] cluster Cluster to search for views. [-v|--volume] volume Find the views exporting the specified volume. Identify the volume by name, VPD83 identifier, or a name pattern with wildcards. [-l|--lun] LUN Find the views exporting the specified LUN number. [-i|--initiator-port] initiator Find the views including the specified initiator. May contain wildcards. [-f|--free-lun] - Find the next free LUN number for all views.
export storage-view find-unmapped-volumes Displays unexported virtual volumes. Contexts All contexts. Syntax export storage-view find-unmapped-volumes [-c|--cluster] cluster Arguments Required arguments [-c|--cluster] cluster Cluster for which to display unexported storage volumes. Description Displays unexported virtual volumes in the specified cluster. Displays the remote (on the other cluster) virtual volumes which are unexported.
Arguments Required arguments [-v|--views] view,view... * List of one or more storage views to map. Entries must be separated by commas. May contain wildcards. Optional arguments [-f|--file] file Name of the file to send the output to. If no file is specified, output is to the console screen. * argument is positional.
Syntax export storage-view removeinitiatorport [-v|--view] context-path [-i|--initiator-ports] context-path,context-path... Arguments Required arguments [-i|--initiator-ports] context-path,contextpath... * Comma- separated list of one or more initiator ports to remove. Optional arguments [-v|--view] context-path The storage view from which to remove the initiator port. * - argument is positional.
[-p|--ports] context-path,context-path... Arguments Required arguments [-p|--ports] context-path,contextpath ... * List of one or more ports to be removed from the view. Entries must be separated by commas. Optional arguments [-v|--view] context-path View from which to remove the specified ports. * - argument is positional.
Arguments Required arguments [-o|--virtual-volumes] volume,volume ... * List of one or more virtual volumes to be removed from the view. Entries must be separated by commas. Optional arguments [-f|--force] Force the virtual volumes to be removed from the view even if the specified LUNs are in use, the view is live, or some of the virtual volumes do not exist in the view. [-v|--view] context-path View from which to remove the specified virtual volumes. * - argument is positional.
Arguments Optional arguments [-c|--cluster] context-path The cluster at which to show the PowerPath interface mapping. See also ● ● ● ● export export export export storage-view storage-view storage-view storage-view checkconfig find map summary export storage-view summary Lists each view and the number of virtual volumes and initiators that it contains. Contexts All contexts. In /clusters/cluster/exports/storage-views context, command is summary.
Display storage view summary for all clusters (1 unhealthy view): VPlexcli:/> export storage-view summary View health summary(cluster-1): view name health-state exported volumes ports registered initiators ---------- ------------ ---------------- ----- --------------------poly2_view healthy 5 4 2 view1 healthy 1 4 1 Total 2 views, 0 unhealthy.
Each WWN is either '0x' followed by one or more hexadecimal digits or an abbreviation, in the following format: string:number[,number] For example, 0xd1342a|0xd1342b hyy1:194e,4|hyy1:194e 0xd1342a hyy1:194e,4 Optional arguments [-p|--port] contextpath - Target port for which to rename the WWN pair. Description Use the ll command in /clusters/cluster/export/port context to display portWWNs and nodeWWNs. CAUTION: Disable the corresponding Fibre Channel port before executing this command.
Arguments Required arguments [-d|--storage-volumes] storagevolume,storage-volume ... * Names of one or more claimed storage volumes to extent. Entries must be separated by commas. * - argument is positional. Description An extent is a slice (range of 4K byte blocks) of a storage volume. An extent is only allowed to use the entire capacity of the storage volume. Extents are the building blocks for devices. This command can fail if there is not a sufficient number of meta volume slots.
Syntax extent destroy [-f|--force] [-s|--extents] context-path,context-path... Arguments Required arguments [-s|--extents] contextpath,context-path ... * List of one or more extents to destroy. Entries must be separated by commas. Optional arguments [-f|--force] Forces the destruction of the given extents, bypassing all guards and confirmations. * - argument is positional. Description Destroys the specified extents.
Arguments Optional arguments [-c|--clusters] cluster,cluster... List of clusters to summarize, separated by commas. May contain glob characters. Description Displays a cluster's unhealthy extents (if any exist), the total number of extents by use, and calculates the total extent capacity for this cluster. An unhealthy extent has a non-nominal health state, operational status or I/O status.
Table 9. extent summary field descriptions (continued) Field Description unhealthy - Of the total number of extents on the cluster, the number with operational status or health state that is not “ok”. Use used - Of the total number of extents on the cluster, the number in use. claimed - Of the total number of extents on the cluster, the number that are claimed unclaimed - Of the total number of extents on the cluster, the number that are unclaimed.
[-c | --contexts] = pattern [, pattern ...] Pattern for matching contexts you want to find. 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 Use this command to find all contexts matching a pattern. When invoked interactively, the command prints the contexts to the screen.
front-end-performance-stats status Displays the status of front-end performance statistics collection. Contexts All contexts. 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.
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 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.
Table 10. getsysinfo field descriptions Field Description Flag includeDebug Ignore this line. Flag isLinux = 0 Denotes a linux simulator build. Ignore this line. Treating this tower like version D4 Denotes the system is Release 4.0 or later. Ignore this line. nn ports - unknown system type The getsysinfo script looked for hardware prior to Release 4.0 and did not find it.
--back-end --front-end --limits --cache --consistency-group --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.
Example Run a high-level (default) health check on a metro node Metro: VPlexcli:/> health-check Product Version: 5.1.0.00.00.
--------- ----------- ----------- ---------- ---------- ----------- ------------------------ ---------cluster-1 1 1 1 0 8 1 8/1 0 cluster-2 -/**This command is only able to check the health of the local cluster(cluster-1)'s RecoverPoint configuration, therefore if this system is a metro node Metro or metro node Geo repeat this command on the remote cluster to get the health of the remote cluster's RecoverPoint configuration.
All port-groups have a status of either ok or warning. com connectivity is complete through minor configuration errors may still exist (see individual port-group statuses). port-group-1: OK All com links have the expected connectivity: this port-group is operating correctly. port-group-0: OK All com links have the expected connectivity: this port-group is operating correctly. WAN Port Settings.................. OK WAN Port Group Settings............ OK WAN Subnet Settings................
Cluster cluster-1: There are 8 storage volumes running in degraded mode. Array: EMC-CLARiiON-APM00114102495 There are 8 storage volumes running in degraded mode.
See also ● cluster status ● validate-system-configuration 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.
-h, --help Displays the usage for this command. --verbose Provide more output during command execution. This may not have any effect for some commands. -c, --clusters= clusters whose operational-status to display. Along with the operational-status, an indication of why it could be non-nominal and a 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. . . .
Example Display the last 8 commands executed in this CLI session: VPlexcli:/> history 8 492 ll 493 cd d 494 cd device-migrations/ 495 ll 496 cd 497 ds summary 498 export storage-view checkconfig 499 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...
[-e|--extents] * List of one or more claimed extents to be added to the device. Can also be other local devices (to create a device of devices). contextpath,context-path... Optional arguments [-d|--stripedepth] depth Required if --geometry is raid-0.
----------- Status Volume ----------- ------------------ -------dev_lun_1 ok - State Count Size -------- -------- ---------- ------ -------- ----- -------- -------- ---------- ok 20709376 4K 5G raid-1 local Size - In the following example: ● ● ● ● 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 displa
● local-device summary 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.
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 /clusters/cluster-1/directors/dirA: Name Value ------------------ ----operational-status ok . . .
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. Description Creates a mirror and backup of the specified meta-volume.
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. Syntax meta-volume backup [-d|--storage-volumes] context-path,context-path... [-c|--cluster] context-path [-f|--force] Arguments Required arguments [-d|--storagevolume] context-path * List of two or more storage volumes to use in creating the backup meta-volume.
Example Back up the metadata to a RAID 1 of two specified storage volumes: VPlexcli:/> meta-volume backup --storage-volumes VPD83T3:60060480000190300487533030354636, VPD83T3:60060480000190300487533030343445 See also ● meta-volume create ● meta-volume destroy meta-volume create Creates a new meta-volume in a cluster when there is no existing active meta-volume. Contexts All contexts. Syntax meta-volume create [-n|--name] name [-d|--storage-volumes] context-path,context-path...
The meta-volume is critical for system recovery. The best practice is to mirror the meta-volume across two or more back-end arrays to eliminate the possibility of data loss. Choose the arrays used to mirror the meta-volume such that they are not required to migrate at the same time. Meta-volumes differ from standard storage volumes in that: ● A meta-volume is created without first being claimed, ● Meta-volumes are created directly on storage volumes, not extents.
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: Name Description ---------- ------------------------------------------------------------------components The list of components that support this device or system virtual volume.
See also ● meta-volume destroy meta-volume destroy Destroys a meta-volume, and frees its storage volumes for other uses. Contexts All contexts. Syntax meta-volume destroy [-v|--meta-volume] context-path [-f|--force] Arguments Required arguments [-v|--meta-volume] context-path - * Meta-volume to destroy. Optional arguments [f|--force] - Destroys the meta-volume without asking for confirmation (allows the command to be run from a non-interactive script).
block-count 23592704 . . . VPlexcli:/clusters/cluster-1/system-volumes> meta-volume destroy -v meta1 Meta-volume 'meta1' will be destroyed. Do you wish to continue? (Yes/No) y See also ● meta-volume create meta-volume detach-mirror Detaches a storage-volume/mirror from a meta-volume. Contexts All contexts.
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.
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. See the troubleshooting procedures for metro node in the SolVe Desktop for information on fixing this problem.
Description An active meta-volume with an inconsistent on-disk state can lead to a data unavailability (DU) during NDU. Best practice is to upgrade immediately after passing this meta-volume consistency check. NOTE: If any errors are reported, do not proceed with the upgrade, and contact Dell EMC Customer Support. The format of the command is: meta-volume verify-on-disk-consistency -style long --meta-volume meta-volume-name> The command takes 10-20 minutes to complete.
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-clusters Generates a capacity report for every cluster. Contexts All contexts. Syntax report capacity-clusters [-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 CapacityClusters.csv.
Examples VPlexcli:/> report capacity-clusters Cluster, Unclaimed disk capacity (GiB), Unclaimed storage_volumes, Claimed disk capacity(GiB), Claimed storage_volumes, Used storage-volume capacity (GiB), Used storage_volumes, Unexported volume capacity (GiB), Unexported volumes, Exported volume capacity (GiB), Exported volumes cluster-1, 5705.13, 341, 7947.68, 492, 360.04, 15, 3.00, 3, 2201.47, 27 cluster-2, 5337.10, 328, 7995.69, 495, 2478.45, 137, 20.00, 3, 2178.
● Number of exported virtual volumes per cluster. Example Generate a host capacity report. VPlexcli:/> report capacity-hosts Cluster, Views, Exported capacity (GiB), Exported volumes cluster-1, 2, 2209.47, 28 cluster-2, 1, 2178.
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 The rm command is used to delete a file from an SCP directory. As part of Role-based access implementation, users other than service are not allowed shell access and access by SCP is restricted to a single directory.
[-c|--command] command * The CLI command to be executed at the specified time. * - argument is positional. Examples To run the tree command every night at 1:00 a.m.: VPlexcli:/> schedule add "0 1 * * *" --command tree See also ● schedule list ● schedule modify ● schedule remove schedule list Lists all scheduled jobs. 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. [-t|--time] time * Date and time the job executes in crontab-style format enclosed in quote marks. Values are specified in the following format: “MinuteHourDay-of-the-Month MonthDay of -he-week” Minute - 0-59. Hour - 0-23. Day of the Month - 1-31. Month - 1-12, January = 1...
Syntax schedule remove [-j|--job] job-ID Arguments Required arguments [-j|--job] job-ID * ID of the scheduled job as displayed by the schedule list command. * - argument is positional. Example Remove job with the ID of 3: VPlexcli:/> schedule list [0] 30 13 * * 3 syrcollect [1] * 1 * * * tree [2] * 2 * * * tree [3] * 3 * * * tree VPlexcli:/> schedule remove 3 Removed scheduled job 3.
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. Description Typically, SYR collection and reporting are configured at initial system setup. Use this command to add a scheduled SYR collection time if none was configured. SYR data collection can be scheduled to occur at most once a week.
Syntax scheduleSYR list Example List the SYC collection schedule: VPlexcli:/> scheduleSYR list SYR data collection job is currently scheduled at: Day of Week: 1 (Sunday=0, Monday=1,...Saturday=6) Hours: 23 Minutes: 30 See also ● ● ● ● configuration event-notices-reports config configuration event-notices-reports reset scheduleSYR add scheduleSYR remove scheduleSYR remove Removes the currently scheduled SYR data collection job. Contexts All contexts.
See also ● ● ● ● configuration event-notices-reports config configuration event-notices-reports reset scheduleSYR add scheduleSYR list script Changes to interactive Jython scripting mode. Contexts All contexts. Syntax script [-i|--import] module [-u|--unimport] module Arguments Optional arguments [-i|--import] module Import the specified Jython module without changing to interactive mode. After importation, commands registered by the module are available in the CLI.
Import/unimport the specified Jython module without changing to interactive mode: VPlexcli:/> script --import ndu VPlexcli:/> script --unimport ndu See also ● source sessions Displays active Unisphere for metro node sessions. Contexts All contexts. Syntax sessions Description Displays the username, hostname, port and start time of active sessions to the Unisphere for metro node.
Arguments Optional arguments [-d|--default] Sets the specified attributes to the default values, if any exist. If no attributes are specified, displays the default values for attributes in the current/specified given context. [-f|--force] Force the value to be set, bypassing any confirmations or guards. [-a|--attributes] pattern * Attribute selector pattern. [-v|--value] value * The new value to assign to the specified attributes. * - argument is positional.
Change the name of a meta-volume: VPlexcli:/clusters/cluster-1/system-volumes/new_meta1_backup_2010May24_163810> set name backup_May24_pre_refresh Display information about attributes in the cluster-1 context: VPlexcli:/> set /clusters/cluster-1 attribute input-description ------------------------------------------------------------------------------------------------------------------/clusters/cluster-1::top-level-assembly Read-only.
underlying-storage-block-size use used-by vendor-specific-name vias-based 512 used [extent_test01_1] DGC false Enable and display iSCSI FE and BE ports: VPlexcli:/clusters/cluster-1/directors/director-1-1-A/hardware/ports> ll Name Address Role Port Status ----- -------------- --------- ----------ETH02 128.221.252.97 local-com up ETH03 128.221.253.97 local-com up ETH04 192.168.11.35 wan-com up ETH05 10.6.11.35 wan-com up ETH06 192.168.71.58 front-end up ETH07 192.168.91.58 front-end up ETH08 192.168.50.
block-count block-size cache-mode capacity consistency-group expandable health-indications health-state locality operational-status scsi-release-delay service-status storage-tier supporting-device system-id volume-type 2621440 4K synchronous 10G true [] ok local ok 0 running device_EMC-CLARiiON-APM00113700075-VNX_LUN122_1 EMC-CLARiiON-0075-VNX-LUN122_1_vol virtual-volume Return to the virtual-volumes context and change directory to the new name: VPlexcli:/clusters/cluster-1/virtual-volumes/new_name> cd ..
article. The new SPC version is applied to all the initiators in the storage-view.
Description Change the default setting for a Fibre Channel port. Default: p2p. NOTE: According to best practices, the front-end ports should be set to the default p2p and connected to the hosts via a switched fabric. WARNING: It is not recommended to change the topology on the local COM ports, as it can lead to the directors going down and data unavailability.
Arguments Required arguments [-t|--targets] * Comma separated list of target storage elements. path, path,... You can specify meta, logging and virtual volumes, local and distributed devices, extents, storagevolumes or logical-units on a single command line. NOTE: A complete context path to the targets must be specified.
Optional arguments [-t|--target_log] logName Collect only files specified under logName from smsDump.xml. Description Collects the following log files: NOTE: The log files listed below are the core set of files along with other files that are not listed. Clilogs ● /var/log/VPlex/cli/client.log* -- VPlexcli logs, logs dumped by VPlexcli scripts ● /var/log/VPlex/cli/session.log* -- what the user does in a VPlexcli session ● /var/log/VPlex/cli/firmware.log* -- nsfw.
Examples Collect the logs files on the management server and send them to the designated directory: VPlexcli:/> sms dump --destination-directory /var/log/VPlex/cli Initiating sms dump... sms dump completed to file /var/log/VPlex/cli/smsDump_2010-09-15_16.40.20.zip. See also ● ● ● ● cluster configdump collect-diagnostics director appdump getsysinfo source Reads and executes commands from a script. Contexts All contexts.
The first command in the file is run The exit command exits the command shell VPlexcli:/> source --file /var/log/VPlex/cli/Source.txt What Version ---------------------------------------------- -------------Product Version 4.1.0.00.00.12 SMSv2 0.16.15.0.0 Mgmt Server Base D4_MSB_7 Mgmt Server Software D4.70.0.9 /engines/engine-2-1/directors/Cluster_2_Dir_1B 1.2.43.9.0 /engines/engine-2-1/directors/Cluster_2_Dir_1A 1.2.43.9.0 /engines/engine-1-1/directors/Cluster_1_Dir1B 1.2.43.9.
[-s | --storage-extents= storage- Specifies the storage-extents (virtual-volumes, local or distributed devices or extents) to dismantle. extent [, storage-extent] ...]] * argument is positional Description Dismantles virtual-volumes, devices (local or distributed) and extents down to the storage-volumes, including unclaiming the storage-volumes. Run storage-tool dismantle against top-level storage elements only.
Optional arguments [-d|--storage* Specifies a list of storage volumes to build the virtual volume from. These may be claimed, but volumes] storage-volume must be unused. [, storage-volume...] [-m|--sourcemirror] source-mirror Specifies the storage volume to use as a source mirror when creating local and distributed devices. NOTE: If specified, --source-mirror will be used as a source-mirror when creating local and distributed RAID 1 devices.
/clusters/cluster-1/virtual-volumes/myVolume: Name Value -------------------------- ---------------------------------------block-count 2621440 block-size 4K cache-mode synchronous capacity 10G consistency-group expandable true expandable-capacity 0B expansion-method storage-volume expansion-status health-indications [] health-state ok locality local operational-status ok recoverpoint-protection-at [] recoverpoint-usage scsi-release-delay 0 service-status unexported storage-tier supporting-device device_myVo
Arguments Required arguments [-n|--director] path * The director on which to show or change the delay for automatic unbanishment. Optional arguments [-i|--interval] [ seconds] Number of seconds the director firmware waits before unbanishing a banished storage volume (LUN). Range: 20 seconds - no upper limit. Default: 30 seconds. * - argument is positional. Description See “Banished storage volumes (LUNs)” in the storage-volume unbanish command description.
storage-volume claim Claims the specified storage volumes. Contexts All contexts. In /clusters/cluster/storage-elements/storage-volumes context, command is claim. Syntax storage-volume claim [--appc] [-n|--name] name --thin-rebuild --batch-size integer [-d|--storage-volumes] path,path... [-f|--force] 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.
Description A storage volume is a device or LUN that is visible to metro node. The capacity of storage volumes is used to create extents, devices and virtual volumes. Storage volumes must be claimed, and optionally named before they can be used in a metro node cluster. Once claimed, the storage volume can be used as a single extent occupying the volume’s entire capacity, or divided into multiple extents (up to 128). This command can fail if there is not a sufficient number of meta volume slots.
Claim a storage volume and name it Symm1254_7BF from the clusters/cluster context: VPlexcli:/clusters/cluster-1> storage-volume claim -name Symm1254_7BF VPD83T3:60000970000192601254533030374241 -d Claim storage volumes using the --thin-rebuild option.
storage-volume claimingwizard Finds unclaimed storage volumes, claims them, and names them appropriately. Contexts All contexts. In /clusters/cluster/storage-elements/storage-volumes context, command is claimingwizard. Syntax storage-volume claimingwizard [-c|--cluster] cluster [-f|--file] file,file... [-d|--dryRun] [-t|--set-tier] list [--force] --appc --thin-rebuild Arguments Optional arguments [-c|--cluster] - Cluster on which to claim storage. cluster [-f|--file] file,file...
Storage tiers allow the administrator to manage arrays based on price, performance, capacity and other attributes. If a tier ID is assigned, the storage with a specified tier ID can be managed as a single unit. Storage volumes without a tier assignment are assigned a value of ‘no tier’. This command can fail if there is not a sufficient number of meta volume slots. See the troubleshooting section of the metro node procedures in the SolVe Desktop for a resolution to this problem.
Note that the Symmetrix storage volumes are named in the format: Symmlast-4-digits-of-array-serial-number_Symmetrix-Device-Number In the following example: ● The --cluster argument specifies cluster-1 ● The --file argument specifies a CLARiiON hints file containing device names and World Wide Names ● The --thin-rebuild argument claims the specified storage volumes as thin (data will be allocated on demand versus up front) VPlexcli:/clusters/cluster-1/storage-elements/storage-volumes> claimingwizard --cluste
Syntax storage-volume find-array [-d|--opt_s_vol] storage-volume Arguments Required arguments [-d|--opt_s_vol] storage- * Storage volume pattern for which to search. The pattern conforms to glob. The following pattern symbols are supported: *, ?, [seq], [!seq]. volume * argument is positional. Description Searches all the storage arrays in all clusters for the specified storage volumes. The search is case-sensitive.
storage-volume forget Tells the cluster that a storage volume or a set of storage volumes are physically removed. Contexts All contexts. In /clusters/cluster/storage-elements/storage-volumes context, command is forget. Syntax storage-volume forget [-d|--storage-volumes] path [,path...] Arguments Required arguments [-d|--storage-volumes] path[, path...] * List of one or more storage volumes to forget. * - argument is positional.
The 'use' property of storage-volume VPD83T3:60000970000192602773533030353933' is 'metadata' but must be 'unclaimed' or 'unusable' before it can be forgotten. . . . 3 storage-volumes were forgotten: VPD83T3:6006016030802100e405a642ed16e111 . . See also ● logical-unit forget ● storage-volume unclaim storage-volume list-banished Displays banished storage-volumes on a director. Contexts All contexts. In /clusters/cluster/storage-elements/storage-volumes context, command is list-banished.
See also ● storage-volume auto-unbanish-interval ● storage-volume unbanish storage-volume list-thin-capable Provides a summary of all thin-capable storage-volumes and determines whether or not the volumes are declared thin (thinrebuild). Contexts All contexts. Syntax storage-volume list-thin-capable [-c|--clusters] context path[, context path...
XtremIO0547_LUN_00005 XtremIO0547_LUN_00006 XtremIO0547_LUN_00007 XtremIO0547_LUN_00008 false false false false cluster-2: Name -----------------------VPD83T3:514f0c5d8320055e VPD83T3:514f0c5d83200560 XtremIO0541_LUN_00000 XtremIO0541_LUN_00002 XtremIO0541_LUN_00004 XtremIO0541_LUN_00005 XtremIO0541_LUN_00006 XtremIO0541_LUN_00007 XtremIO0541_LUN_00008 XtremIO0541_LUN_00009 XtremIO0541_LUN_00010 10G 10G 10G 10G Thin Rebuild -----------false false false false false false false false false false false cl
Description Resurrects the specified dead storage volumes and tests the resurrected device before setting its state to healthy. A storage volume is declared dead: ● After metro node retries a failed I/O to the backend arrays 20 times without success. ● If the storage volume is reachable but errors prevent the I/O from succeeding. A storage volume declared hardware dead cannot be unclaimed or removed (forgotten). Use this command to resurrect the storage volume.
storage-volume summary Displays a list of a cluster's storage volumes. Contexts All contexts. In /clusters/cluster/storage-elements/storage-volumes context, command is summary. Syntax storage-volume summary [-c|--clusters] cluster,[cluster]... Optional arguments [-c|--clusters] cluster,[cluster...] Displays storage volumes for only the specified clusters.
Table 14. storage-volume summary field descriptions (continued) Field Description Health State 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. non-recoverable-error - The extent may be out-ofdate compared to its mirror (applies only to extents that are part of a RAID 1 device), and/or the Health state cannot be determined.
Storage-Volume Summary ---------------------Health Vendor Use Capacity SUMMARY (cluster-2) Storage-Volume Summary ---------------------Health Vendor Use Capacity (no tier) -------------------out-of-date 0 storage-volumes 363 unhealthy 1 DGC 114 EMC 248 None 1 meta-data 4 unusable 0 used 358 total 2T (no tier) -------------------out-of-date 0 storage-volumes 362 unhealthy 0 DGC 114 EMC 248 meta-data 4 used 358 total 1.
used total Capacity SUMMARY (cluster-2) Storage-Volume Summary ---------------------Health 144 198T (no tier) --------------------out-of-date 0 storage-volumes 2318 unhealthy 0 EMC 2318 claimed 2172 meta-data 2 used 144 total 198T Vendor Use Capacity See also ● ● ● ● ● ● ● ● ds summary ds dd set-log export port summary export storage-view summary extent summary local-device summary storage-volume resurrect virtual-volume provision storage-volume unbanish Unbanishes a storage volume on one or more dir
Description Metro node examines path state information for LUNs on arrays. If the path state information is inconsistent, metro node banishes the LUN, and makes it inaccessible. Use this command to unbanish a banished LUN (storage volume). Banished storage volumes (LUNs) LUNs (storage volumes) are banished when metro node detects an unexpected configuration of array controllers or paths to arrays. Under normal active/passive operation, one controller for any given LUN is active, the other is passive.
[-r|--return-to-pool] Arguments Required arguments [-d|--storage-volumes] path, [path...] * Specifies the storage volumes to unclaim. Optional arguments [-b|--batch-size] integer Specifies the maximum number of storage volumes to unclaim at once. [-r|--return-to-pool] Returns the storage capacity of each VIAS-based volume to the pool on the corresponding storage-array. * - argument is positional.
storage-volume used-by Displays the components that use the specified storage volumes. Contexts All contexts. In /clusters/cluster/storage-elements/storage-volumes context, command is used-by. Syntax storage-volume used-by [-d|--storage-volumes] path [,path...] Arguments Required arguments [-d|--storage-volumes] path * List of one or more storage volumes for which to find users. Description To manually deconstruct an encapsulated storage volume, remove each layer starting from the top.
Syntax syrcollect [-d|--directory] directory Arguments Optional arguments [-d|-directory] directory Non-default directory in which to store the output. Files saved in the non-default directory are not automatically sent to Dell EMC. ● Default: Files are stored in the Event_Msg_Folder in the directory specified in the EmaAdaptorConfig.properties file. ● EmaAdaptorConfig.properties and the Event_Msg_Folder are located in /opt/emc/ VPlex on the management server.
tree Displays the context tree. Contexts All contexts. Syntax tree [-e|--expand] [-c|--context] subcontext-root [-s|--select] glob-pattern Arguments Optional arguments [-e|--expand] Expand the subcontexts. [-c|--context] subcontext-root The subcontext to use as the root for the tree. [-s|--select] glob-pattern Glob pattern for selecting the contexts in the tree. Description Displays the sub-context tree.
See also ● drill-down ● set unalias Removes a command alias. Contexts All contexts. Syntax unalias [-n|--name] name [-a|--all] Arguments Optional arguments [-n|--name] name The name of the alias to remove. [-a|--all] Remove all defined aliases.
validate-system-configuration Performs a basic system configuration check. Contexts All contexts. Syntax validate-system-configuration Description This command performs the following checks: ● ● ● ● Validates Validates Validates Validates cache mirroring. the logging volume. the meta-volume. back-end connectivity. Examples Validate system configuration: VPlexcli:/> validate-system-configuration Validate cache replication Checking cluster cluster-1 ...
See also ● cluster status ● connectivity validate-be ● health-check version Display version information for connected directors. Contexts All contexts. Syntax version [-a|--all] [-n|directors] context-path,context-path... [--verbose] Arguments Optional arguments [-a|--all] Displays version information for all connected directors. [-n|--directors] context-path * Display version information for only the specified directors.
Table 15. Software components (continued) Component Abbreviation Description FW Bundle Rev Firmware revision. POST Rev Power On Self Test revision. BIOS Rev Boot firmware revision. SSD Model Solid state disk drive model information. Examples Display management server/SMS version information: VPlexcli:/> version -a What Version Info -------------------- -------------- ---Product Version 7.0.0.00.00.47 SMSv2 170.0.0.291.0 Mgmt Server Base 170.0.0.201 Mgmt Server Software 170.0.0.
For director /engines/engine-2-1/directors/director-2-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.0-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.
Version: What: Version: What: Version: What: Version: What: Version: What: Version: What: Version: What: Version: What: Version: What: Version: 6.5.54.0.0 ECOM 6.5.1.0.0-0 VPLEX Splitter 4.1.b_vplex_D35_00_Ottawa_MR1.10-1 ZECL 6.5.52.0.0-0 ZPEM 6.5.52.0.0-0 NSFW 65.1.54.0-0 BIOS Rev 08.50 POST Rev 43.80 FW Bundle Rev 12.60 SSD Model: P30056-MTFDBAA056SAL 118032803 0005 virtual-volume create Creates a virtual volume on a host device. Contexts All contexts.
Description A virtual volume is created on a device or a distributed device, and is presented to a host through a storage view. Virtual volumes are created on top-level devices only, and always use the full capacity of the device or distributed device. The underlying storage of a virtual volume may be distributed over multiple storage volumes, but appears as a single contiguous volume. The specified device must not already have a virtual volume and must not have a parent device.
Table 16. virtual-volume field descriptions (continued) Field Description ● in-progress - An expansion has been started, but has not completed. The following operations are blocked on the volume: additional expansion, migration, and NDU. ● unknown - Metro node could not determine the expansion status of the volume. health-indications Indicates the reasons for: ● A health-state that is not 'ok' ● The reasons for the failure of virtual volume expansion or initialization.
Table 16. virtual-volume field descriptions (continued) Field Description scsi-release-delay A SCSI release delay time in milliseconds. Optimum value is 0 to 2 seconds. Setting a very high value could break the SCSI semantics. If another reserve arrives at this cluster within this time frame, neither release nor reserve will be sent across the WAN. service-status The service status of a virtual-volume. ● running - I/O is running for the virtual-volume.
consistency-group expandable expandable-capacity expansion-method expansion-status health-indications health-state initialization-status locality operational-status recoverpoint-protection-at recoverpoint-usage scsi-release-delay service-status storage-array-family storage-tier supporting-device system-id thin-capable thin-enabled volume-type vpd-id true 0B storage-volume [] ok success local ok [] 0 unexported clariion r0_C1_VATS_00001 r0_C1_VATS_00001_vol false unavailable virtual-volume VPD83T3:600014400
Description Deletes the virtual volume and leaves the underlying structure intact. The data on the volume is no longer accessible. Only unexported virtual volumes can be deleted. To delete an exported virtual volume, first remove the volume from the storage view.
[-f|--force] The meaning of this argument varies, depending on whether the --extent argument is used (expansion method = concatenation) or not used (expansion-method = storage-volume) ● For storage-volume expansion, the --force argument skips the confirmation message. ● For concatenation expansion, the --force argument expands a virtual volume built on a RAID 1 device using a target that is not a RAID 1 or that is not as redundant as the device supporting the virtual volume. * - argument is positional.
Name Expandable ... ...Capacity Locality Supporting Cache Expandable ... Device Mode Capacity ----------------- ...--------- -------- ----------- ----------- --------------------- ... Raid0_1Ga_11_vol ...5G local raid1-dev synchronous true 4.5G RaidC_1Gb_11_vol ...5G local raid1-dev synchronous true 0B Test_volume ...0.5G local Test synchronous true 4.5G . . .
● The virtual-volume expand --virtual-volume virtual-volume --extent extent command adds the specified extent to the specified virtual volume: VPlexcli:/> ll /clusters/cluster-1/virtual-volumes /clusters/cluster-1/virtual-volumes: Name Operational Health ... ... Expandable ----------------- Status State ... ... -------------------------- ----------- ------ ... ... ---------Raid0_1Ga_11_vol ok ok ... ... true RaidC_1Gb_11_vol ok ok ... ... true Raid1_1Gc_11_vol ok ok ... ... true Test-Device_vol ok ok ... ..
Syntax virtual-volume list-thin -t | --clusters context path -e | --enabled true|false -c | --capable true|false [--verbose] Arguments Required arguments -t | --clusters context path * The target cluster where virtual volumes are listed. Optional arguments -e | --enabled true|false Filters volumes with the matching thin-enabled value. The value can be true or false. If omitted, the results will match volumes regardless of whether they are thin-enabled or not.
virtual-volume re-initialize Restarts the initialization process on a virtual volume. Contexts All contexts. Syntax virtual-volume re-initialize [-v | --virtual-volume] virtual-volume [--verbose] Arguments Required arguments [-v | --virtual-volume] virtualvolume * The virtual-volume that you want to reinitialize. Optional arguments [-h|--help] Displays command line help. [--verbose] Provides more output during command execution. This may not have any effect for some commands.
Syntax virtual-volume set-thin-enabled -v | --virtual-volumes context path [, context path...] -t | --thin-enabled arg [-h|--help] [--verbose] Arguments Required arguments -t | --thin-enabled arg Specifies the desired value of the thin-enabled property. -v | --virtual-volumes context path [, context path...] * Specifies the virtual volumes for which the thin-enabled property must be set. Optional arguments [-h|--help] Displays command line help.
See also storage-volume list-thin-capable virtual-volume summary Displays a summary for all virtual volumes. Contexts All contexts. In /clusters/cluster-n/virtual-volumes context, command is summary. Syntax virtual-volume summary [-c|--clusters] cluster,cluster Arguments Optional arguments [-c|--clusters] cluster List of one or more names of clusters. Display information for only the specified clusters. Entries must be separated by commas.
Table 17. virtual-volume summary field descriptions (continued) Field Description operational status ● degraded - The virtual volume may have one or more out-of-date devices that will eventually rebuild. ● error - One or more of the virtual volume's underlying devices is hardware-dead. ● ok - The virtual volume is functioning normally. ● starting -The virtual volume is not yet ready. ● stressed - One or more of the virtual volume's underlying devices is out-of-date and will never rebuild.
Expansion summary: No expansion activity. Locality summary: distributed : 65 virtual-volumes. local : 494 virtual-volumes. remote : 30 virtual-volumes. Cache-mode summary: asynchronous : 0 virtual-volumes. synchronous : 589 virtual-volumes. Total virtual-volume capacity is 87.9T. In the following example, one distributed virtual volume has expandable capacity at both clusters: VPlexcli:/> virtual-volume summary Virtual-volume health summary (cluster-1): Total 2152 virtual-volumes, 0 unhealthy.
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 ...] Context list, separated by commas Optional arguments [-a | --attribute] Attribute name [-v | --value] Attribute value [-t | --timeout] Timeout in seconds.
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. NOTE: To ensure a successful restart of the Webserver, it is recommended to avoid using the restart option as it has proven to be unreliable in some cases due to a number of external environmental factors.
Index A alias 29 array fail 32 array:claim 31 array:re-discover 33 array:used-by 35 audience 9 B Batch migration:perform a migration 44 batch-migrate check-plan 40 batch-migrate clean 41 batch-migrate create-plan 44 batch-migrate:check-plan;check-plan, batch-migrate 40 batch-migrate:pause;pause:batch-migrate 46 batch-migrate:remove;remove:batch-migrate 47 batch-migrate:resume;resume:batch-migrate 48 batch-migrate:start;start:batch-migrate 49 batch-migrate:summary;summary:batch-migrate 51 C capture:begin;b
director:commission;commission, director 127 director:passwd;passwd, director 132 director:ping;ping 133 director:shutdown;shutdown:director 134 dirs 137 disconnect 138 Display:multiple objects using globs 228 Display:object’s attributes 228 Display:object’s attributes and contexts 228 Display:operational status 228 distributed device 149 dm migration pause 142 dm:migration cancel;migration:cancel;cancel:dm migration 139 dm:migration clean;migration:clean;clean, dm migration 140 dm:migration commit;migratio
logging-volume:add-mirror;add-mirror, logging-volume 220 logging-volume:create;create:logging-volume 220 logging-volume:destroy;destroy:logging-volume 224, 226 logical-unit forget 227 ls;list 228 M meta-volume:attach-mirror;attach-mirror:meta-volume 231 meta-volume:create;create:meta-volume 233 meta-volume:destroy;destroy:meta-volume 236 meta-volume:move;move, meta-volume 238 metadata backup:display backup volumes 76 metadata:backup:initial 76 metadata:backup:modify schedule 76 metadata:modify backup sched
Webserver 330 wildcard 14
