lsrcconsistgrp

Use the lsrcconsistgrp command to return a concise list or a detailed view of remote copy relationships such as Metro Mirror, Global Mirror, or active-active consistency groups visible to the system.

Syntax

lsrcconsistgrp [ -filtervalue attribute=value ] [ -nohdr ] [ -delim delimiter ] [ -filtervalue? ] [ { object_id | object_name } ]

Parameters

-filtervalueattribute=value

(Optional) Specifies a list of one or more filters. Only objects with a value that matches the filter attribute value are displayed. 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 Lenovo Storage V series command line interface (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:
```
lsrcconsistgrp -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.

-delimdelimiter

(Optional) By default in a concise view, all columns of data are space-separated. The width of each column is set to the maximum possible 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 one-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 displayed 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 matching the filtering requirements that is 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 following filter attributes for the lsrcconsistgrp command are valid:

group_id
name
master_cluster_id
master_cluster_name
aux_cluster_id
aux_cluster_name
primary
state
relationship_count
id
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 remote copy relationships such as Global Mirror, Metro Mirror, or active-active consistency groups that are visible to the system.

Table 1 provides possible values for the attributes that are displayed as data in the output views.

Table 1. lsrcconsistgrp command output values
Attribute	Value
primary	n/a, master, aux
state	The state: `consistent_copying` `inconsistent_stopped` `inconsistent_copying` `consistent_stopped` `consistent_synchronized` `idling` `idling_disconnected` `inconsistent_disconnected` `consistent_disconnected` empty
cycle_period_seconds	The minimum period in seconds between multiple cycles (integer between 60 an 86400; default is 300).
cycling_mode	The type of Global Mirroring, Metro Mirroring, or `active-active` cycling to use: `none` (default) or `multi`
freeze_time	The time in `YYMMDDHHMM` format
status	The values are: `online`, which indicates that the relationship is online and accessible. If the relationship state is `ConsistentSynchronized`, `ConsistentCopying`, or `InconsistentCopying` the volumes replicate host I/O operations that the primary volume receives. `primary_offline`, which indicates that the primary volume in the relationship is offline. This prevents additional I/O operations, and synchronization pauses until the primary volume is online again. `secondary_offline`, which indicates that the secondary volume in the relationship is offline. For r Global Mirror relationships in a `ConsistentSynchronized` state (no change volumes) and Metro Mirror relationships, additional I/O write operations to the primary volume terminate the relationship. `io_channel_offline`, which indicates that the remote system is not accessible. For Global Mirror relationships in a `ConsistentSynchronized` state (no change volumes) and Metro Mirror relationships, additional I/O write operations to the primary volume terminate the relationship. `primary_change_offline`, which indicates that the primary change volume in the relationship is offline. For Global Mirror with change volume relationships, the current I/O cycle ends, and a new I/O cycle begins when the primary change volume is online again. `secondary_change_offline`, which indicates that the secondary change volume in the relationship is offline. For Global Mirror with change volume relationships, the current I/O cycle pauses and a new I/O cycle resumes when the secondary volume is online again. `change_volumes_needed`, indicates an `active-active` relationship that is in a HyperSwap^® volume or Global Mirror volume with a change volume relationship. Additionally, at least one change volume is not configured. Important: Replication services are not usable. Remember: This field is blank.
sync	The values for this field: `in_sync` `out_of_sync`
mutually_consistent	The values for this field: `yes` `no` blank Note: This relationship is consistent with other consistency group relationships. This value is blank unless there is also a value in `consistent_stopped`, `consistent_disconnected`, and `consistent_copying`.
copy_type	The copy type: `metro` `global` `activeactive` blank

Note: The names of the Global Mirror or Metro Mirror relationships and consistency groups might 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

lsrcconsistgrp -delim :

The concise resulting output:

id:name:master_cluster_id:master_cluster_name:aux_cluster_id:aux_cluster_name:
primary:state:relationship_count:copy_type:cycling_mode:freeze_time

 248:jdemo_BA_cons1:0000020060406746:clusterB:0000020061413ABA:clusterA:master:
consistent_stopped:2:global:none:06/06/27/08/31/37
 249:rccstgrp0:0000020061413ABA:clusterA:0000020061413ABA:clusterA::empty:0
:empty_group
 250:jdemo_BA_cons2:0000020060406746:clusterB:0000020061413ABA:clusterA:master:
inconsistent_stopped:1:metro:none:06/06/27/08/31/37
 251:BA_cons1:0000020060406746:clusterB:0000020061413ABA:clusterA:master:
consistent_stopped:4:metro:none:06/06/27/08/31/37
 252:AB_cons2:0000020061413ABA:clusterA:0000020060406746:clusterB::empty:0
:empty_group:none:06/06/27/08/31/37
 253:AB_cons1:0000020061413ABA:clusterA:0000020060406746:clusterB:aux:
consistent_stopped:3:global:none:06/06/27/08/31/37
 254:AA_cons2:0000020061413ABA:clusterA:0000020061413ABA:clusterA::empty:0
:empty_group:none:06/06/27/08/31/37
 255:AA_cons1:0000020061413ABA:clusterA:0000020061413ABA:clusterA:master:
consistent_synchronized:2:global:none:06/06/27/08/31/37

A detailed invocation example

lsrcconsistgrp -delim : 254

The detailed resulting output:

id:254
name:rccstgrp0
master_cluster_id:0000010030A007E5
master_cluster_name:clusterA
aux_cluster_id:0000010030A007E5
aux_cluster_name:clusterA
primary:master
state:consistent_synchronized
relationship_count:1
freeze_time:06/06/27/08/31/37
status:online
sync:in_sync
copy_type:activeactive
cycle_period_seconds:300
cycling_mode:none
RC_rel_id:2
RC_rel_name:aaa