lsrcrelationship
Use the lsrcrelationship command to return a concise list or a detailed view of Metro Mirror or Global Mirror relationships visible to the clustered system (system).
Syntax
>>- lsrcrelationship -- ----------------------------------------> >--+-----------------------------------+-- --+----------+-- ----> '- -filtervalue -- attribute=value -' '- -nohdr -' >--+-----------------------+-- -- --+-----------------+---------> '- -delim -- delimiter -' '- -filtervalue? -' >--+---------------+------------------------------------------->< +- object_id ---+ '- object_name -'
Parameters
- -filtervalue attribute=value
- (Optional) Specifies a list of one or more filters. Only objects with a value that matches the filter attribute value are returned. If a capacity is specified, the units must also be included.
- Note: Some filters allow the use of a wildcard when you enter the command. The following rules apply to the use of wildcards with the Storwize® V3700 CLI:
- The wildcard character is an asterisk (*).
- The command can contain a maximum of one wildcard, which must be the first or last character in the string.
- When using a wildcard, you must enclose the filter entry with
double quotation marks (" "), as follows:
lsrcrelationship -filtervalue "name=md*"
- -nohdr
- (Optional) By default, headings are displayed for each column
of data in a concise style view, and for each item of data in a detailed
style view. The -nohdr parameter suppresses the
display of these headings.Note: If there is no data to be displayed, headings are not displayed even if the -nohdr parameter is specified.
- -delim delimiter
- (Optional) By default in a concise view, all columns of data are space-separated. The width of each column is set to the maximum width of each item of data. In a detailed view, each item of data has its own row, and if the headers are displayed the data is separated from the header by a space. The -delim parameter overrides this behavior. Valid input for the -delim parameter is a 1-byte character. If you enter -delim : on the command line, the colon character (:) separates all items of data in a concise view; for example, the spacing of columns does not occur. In a detailed view, the data is separated from its header by the specified delimiter.
- object_id | object_name
- (Optional) Specifies the name or ID of an object. When you use this parameter, the detailed view of the specific object is returned and any value that is specified by the -filtervalue parameter is ignored. If you do not specify the object_id | object_name parameter, the concise view of all objects that match the filtering requirements that are specified by the -filtervalue parameter are displayed.
- -filtervalue?
- (Optional) Specifies that you want your report to display any
or all of the list of valid filter attributes. The valid filter attributes
for the lsrcrelationship command are:
- RC_rel_id
- RC_rel_name
- master_system_id
- master_system_name
- master_vdisk_id
- master_vdisk_name
- aus_system_id
- aux_system_name
- aux_vdisk_id
- aux_vdisk_name
- primary
- consistency_group_id
- consistency_group_name
- state
- progress
- copy_type
For more information about filtering attributes, see Attributes of the -filtervalue parameters.
Description
This command returns a concise list or a detailed view of Metro Mirror or Global Mirror relationships visible to the system.
Table 1 provides
possible values for the attributes that are displayed as data in the
output views.
Attribute | Value |
---|---|
primary | n/a, master, aux |
state | consistent_copying, inconsistent_stopped, inconsistent_copying, consistent_stopped, consistent_synchronized, idling, idling_disconnected, inconsistent_disconnected, consistent_disconnected |
progress | Integer between 0 and 100, n/a |
cycle_period_seconds | The minimum period in seconds between multiple cycles (integer between 60 and 86400; default is 300). |
cycling_mode | The type of Global Mirror or Metro Mirror
cycling to use. The choices are:
|
copy_type | The copy type:
|
freeze time | The time in YY/MM/DD/HH/MM format |
status | The values are:
|
sync | n/a, in_sync, out_of_sync |
master_change_vdisk_name | The name of the volume acting as the master change volume for the relationship (blank if not defined) Note: This field identifies the change volume for the master volume if configured. For an intersystem relationship, if the master volume is in the other clustered system (system), the master change volume is also in the other system.
|
aux_change_vdisk_id | The id of the volume acting as the auxiliary
change volume for the relationship (blank if not defined) Note: This
field identifies the change volume for the auxiliary volume, if such
a volume has been configured. For an intersystem relationship, if
the auxiliary volume is in the other system, the auxiliary change
volume is also in the other system.
|
aux_change_vdisk_name | The name of the volume acting as the auxiliary
change volume for the relationship (blank if not defined) Note: This
field identifies the change volume for the auxiliary volume if configured.
For an intersystem relationship, if the auxiliary volume is in the
other system, the auxiliary change volume is also in the other system.
|
bg_copy_priority | Unused. |
Note: The names of the Global Mirror or Metro Mirror
relationships and consistency groups can be blank if the relationship
or consistency groups are intersystem and the system partnership is
disconnected.
The sync attribute has a value of in_sync when the contents are synchronized (identical) between volumes. If write operations take place on either the primary or secondary volume after a consistent (stopped) or idling state occurs, they will no longer be synchronized.
A concise invocation example
lsrcrelationship -delim : -filtervalue name=j*
The concise resulting output:
id:name:master_cluster_id:master_cluster_name:master_vdisk_id:master_vdisk_name:
aux_cluster_id:aux_cluster_name:aux_vdisk_id:
aux_vdisk_name:primary:consistency_group_id:consistency_group_name:state:bg_copy
_priority:progress:copy_type:cycling_mode:freeze_time
45:jrel_AB1:0000020061413ABA:clusterA:45:jdisk_B8:0000020060406746:clusterB:38:j
disk_B1:master:::consistent_stopped:50:metro:none:06/06/27/08/31/37
48:jrel_AB2:0000020061413ABA:clusterA:48:jdisk_A4:0000020060406746:clusterB:41:j
disk_B4:master:::consistent_synchronized:50:metro:none:06/06/27/09/31/37
49:jrel_BA_1:0000020060406746:clusterB:42:jdisk_B5:0000020061413ABA:clusterA:49:j
disk_A5:master:248:jdemo_BA_cons1:consistent_stopped:50:metro:none:06/06/27/10/31/37
50:jrel_BA_2:0000020060406746:clusterB:43:jdisk_B6:0000020061413ABA:clusterA:
50:jdisk_A6:master:248:jdemo_BA_cons1:consistent_stopped:50:metro:none:06/06/27/11/31/37
A detailed invocation example
lsrcrelationship -delim : AB_2
The detailed resulting output:
id:9
name:AB_2
master_cluster_id:0000020061413MOE
master_cluster_name:chelseaB
master_vdisk_id:9
master_vdisk_name:stripe9
aux_cluster_id:0000020061413MOE
aux_cluster_name:chelseaB
aux_vdisk_id:10
aux_vdisk_name:stripe9_b
copy_type:metro
cycle_period_seconds:300
cycling_mode:multi
primary:master
consistency_group_id:
consistency_group_name:
state:consistent_synchronized
bg_copy_priority:50
progress:
freeze_time:2006/05/05/08/26/46
status:online
sync:in_sync