group
Description
The group subcommand specifies the type of monitoring data that you want to export. This command uses an operand (for example, PhyPG and PhyLDEV above) to specify a type of monitoring data.
Operands of the group subcommand and saved monitoring data shows the monitoring data that can be saved into files by each operand, and the saved ZIP files. For details on the monitoring data saved in these files, see the tables listed in the See column.
Operands of the group subcommand and saved monitoring data
|
Operand |
Monitoring data saved in the file |
Saved ZIP file |
See |
|---|---|---|---|
PhyPG |
Usage statistics about parity groups |
PhyPG_data.ZIP1 |
|
PhyLDEV |
Usage statistics about volumes |
PhyLDEV_dat.ZIP1 |
|
PhyExG |
Usage conditions about external volume groups |
PhyExg_dat.ZIP |
|
PhyExLDEV |
Usage conditions about external volumes |
PhyExLDEV_dat/PHY_ExLDEB_xxxxx.ZIP2 |
|
PhyProc |
Usage statistics about MPs and data recovery and reconstruction processors |
PhyProc_dat.ZIP1 |
|
PhyCMPK |
Usage statistics about write pending rate and cache |
PhyCMPK_dat.ZIP1 |
|
PG |
Statistics about parity groups, external volume groups |
PG_dat.ZIP |
Files with parity group and external volume group statistics |
LDEV |
Statistics about volumes in parity groups, in external volume groups |
LDEV_dat/LDEV_XXXXX.ZIP2 |
Files with statistics about volumes in parity/external volume groups |
LDEVEachOfCU |
Statistics about volumes in parity groups or in external volume groups (for volumes controlled by a particular CU) |
LDEVEachOfCU_dat/LDEV_XXXXX.ZIP3 |
|
Port |
Statistics about ports |
Port_dat.ZIP |
|
PortWWN |
Statistics about host bus adapters connected to ports |
PortWWN_dat.ZIP |
Files with statistics about host bus adapters connected to ports |
LU |
Statistics about LUs |
LU_dat.ZIP |
|
PPCGWWN |
All host bus adapters that are connected to ports |
PPCGWWN_dat.ZIP |
Files with statistics about host bus adapters belonging to SPM groups |
RemoteCopy |
Statistics about remote copy operations by TrueCopy and GAD (in complete volumes) |
RemoteCopy_dat.ZIP |
Files with statistics about remote copy operations by TC or GAD (whole volumes) |
RCLU |
Statistics about remote copy operations by TrueCopy and GAD (for each volume (LU)) |
RCLU_dat.ZIP |
Files with statistics about remote copy operations by TC or GAD (for each volume (LU)) |
RCLDEV |
Statistics about remote copy operations by TrueCopy and GAD (for volumes controlled by a particular CU) |
RCLDEV_dat/RCLDEV_XXXXX.ZIP4 |
|
Universal Replicator |
Statistics about remote copy operations by Universal Replicator (for entire volumes) |
UniversalReplicator.ZIP |
Files with statistics about remote copy operations by UR (In the whole volumes) |
URJNL |
Statistics about remote copy operations by Universal Replicator (for journals) |
URJNL_dat.ZIP |
Files with statistics about remote copy operations by UR (journals) |
URLU |
Statistics about remote copy operations by Universal Replicator (for each volume (LU)) |
URLU_dat.ZIP |
Files with statistics about remote copy operations by UR (for each volume (LU)) |
URLDEV |
Statistics about remote copy operations by Universal Replicator (for volumes controlled by a particular CU) |
URLDEV_dat/URLDEV_XXXXX.ZIP5 |
Files with statistics about remote copy operations by UR (volumes controlled by a particular CU) |
PhyMPPK |
MP usage rate of each resource allocated to MP units |
PhyMPPK_dat.ZIP |
Files with statistics about host bus adapters belonging to SPM groups |
|
Notes:
|
|||
You can use the group subcommand more than one time in a command file. For example, you can write the following script:
group PortWWN CL1-A:CL1-B group RemoteCopy
If you use an operand more than one time in a command file, the last operand takes effect. In the following example, the first group subcommand does not take effect, but the second group subcommand takes effect:
group PortWWN CL1-A:CL1-B group PortWWN CL2-A:CL2-B
Syntax
group {PhyPG[parity-group-id]:[parity-group-id]][…]| PhyLDEV [parity-group-id]:[parity-group-id]][…]| PhyExG [[exg-id]:[exg-id]][…]| PhyExLDEV [exg-id]:[exg-id]][…]| PhyProc | PG [[parity-group-id|exg-id]: [parity-group-id|exg-id]][…]| LDEV [[[parity-group-id|exg-id]: [parity-group-id|exg-id]][…]| LDEVEachOfCU[[[LDKC-CU-id]:[LDKC-CU- id]][…]|internal|virtual]| internal|virtual]| Port [[port-name]:[port-name]][…]| PortWWN [port-name]:[port-name]][…]| LU[[port-name.host-group-id]: [port-name.host-group-id]][…]| PPCGWWN[[monitor-target-name:monitor-target-name]][…]| RemoteCopy| RCLU [[port-name.host-group-id]: [port-name.host-group-id]][…]| RCLDEV[[LDKC-CU-id]:[LDKC-CU-id]][…]| UniversalReplicator | URJNL[[JNL-group-id]:[JNL-group-id]][…]| URLU [[port-name.host-group-id]: [port-name.host-group-id]][…]| URLDEV [[LDKC-CU-id]:[LDKC-CU-id]][…]| }
Operands
|
Operand |
Description |
|---|---|
|
PhyPG [[parity-group-id]:[parity-group-id]][…] |
Use this operand to export statistics about parity group usage rates, which are displayed in the Monitor Performance window. When statistics are exported to a ZIP file, the file name will be PhyPG_dat.ZIP. For details on the statistics exported by this operand, see Files with resource usage and write pending rate statistics. The exported file will contain statistics for up to 15 days. When you specify variables parity-group-id, you can narrow the range of parity groups whose monitoring data are to be exported. parity-group-id is a parity group ID. The colon (:) indicates a range. For example, 1-1:1-5 indicates parity groups from 1-1 to 1-5. Ensure that the parity-group-id value on the left of the colon is smaller than the parity-group-id value on the right of the colon. For example, you can specify PhyPG 1-1:1-5, but you cannot specify PhyPG 1-5:1-1. Also, you can specify PhyPG 1-5:2-1, but you cannot specify PhyPG 2-1:1-5. If parity-group-id is not specified, the monitoring data of all parity groups will be exported. |
|
PhyLDEV [[parity-group-id]:[parity-group-id]][…] |
Use this operand when you want to export statistics about volume usage rates, which are displayed in the Monitor Performance window. When statistics are exported to a ZIP file, the file name will be PhyLDEV_dat.ZIP. For details on the statistics exported by this operand, see Files with resource usage and write pending rate statistics. The exported file will contain statistics for up to 15 days. When you specify variables parity-group-id, you can narrow the range of parity groups whose monitoring data are to be exported. parity-group-id is a parity group ID. The colon (:) indicates a range. For example, 1-1:1-5 indicates parity groups from 1-1 to 1-5. Ensure that the parity-group-id value on the left of the colon is smaller than the parity-group-id value on the right of the colon. For example, you can specify PhyLDEV 1-1:1-5, but you cannot specify PhyLDEV 1-5:1-1. Also, you can specify PhyLDEV 1-5:2-1, but you cannot specify PhyLDEV 2-1:1-5. If parity-group-id is not specified, the monitoring data of all volumes will be exported. |
|
PhyExG [[exg-id]:[exg-id]][…] |
Use this operand when you want to export statistics about external volume groups, which are displayed in the Monitor Performance window. When statistics are exported to a ZIP file, the file name will be PhyExG_dat.ZIP. For details on the statistics exported by this operand, see Files with resource usage and write pending rate statistics. When you specify variables exg-id, you can narrow the range of external volume groups whose monitoring data are to be exported. exg-id is an ID of an external volume group. The colon (:) indicates a range. For example, E1-1:E1-5 indicates external volume groups from E1-1 to E1-5. Ensure that the exg-id value on the left of the colon is smaller than the exg-id value on the right of the colon. For example, you can specify PhyExG E1-1:E1-5, but you cannot specify PhyExG E1-5:E1-1. Also, you can specify PhyExG E1-5:E2-1, but you cannot specify PhyExG E2-1:E1-5. If exg-id is not specified, the monitoring data of all external volume groups will be exported. |
|
PhyExLDEV[[exg-id]:[exg-id]][…] |
Use this operand when you want to export statistics about volumes in external volume groups, which are displayed in the Monitor Performance window. When statistics are exported to a ZIP file, the file name will be PhyExLDEV_dat.ZIP. For details on the statistics exported by this operand, see Files with resource usage and write pending rate statistics. When you specify variables exg-id, you can narrow the range of external volume groups whose monitoring data are to be exported. exg-id is an ID of an external volume group. The colon (:) indicates a range. For example, E1-1:E1-5 indicates external volume groups from E1-1 to E1-5. Ensure that the exg-id value on the left of the colon is smaller than the exg-id value on the right of the colon. For example, you can specify PhyExLDEV E1-1:E1-5, but you cannot specify PhyExLDEV E1-5:E1-1. Also, you can specify PhyExLDEV E1-5:E2-1, but you cannot specify PhyExLDEV E2-1:E1-5. If exg-id is not specified, the monitoring data of all external volumes will be exported. |
|
PhyProc |
Use this operand when you want to export the usage rates of MPs, which are displayed in the Monitor Performance window. When statistics are exported to a ZIP file, the file name will be PhyProc_dat.ZIP. For details on the statistics exported by this operand, see Files with resource usage and write pending rate statistics. The exported file will contain statistics for up to 15 days. |
|
PG [[parity-group-id|exg-id]: [parity-group-id|exg-id][…] |
Use this operand when you want to export statistics about parity groups or external volume groups which are displayed in the Monitor Performance window. When statistics are exported to a ZIP file, the file name will be PG_dat.ZIP. For details on the statistics exported by this operand, see Files with resource usage and write pending rate statistics. When you specify variables parity-group-id, or exg-id you can narrow the range of parity groups, or external volume groups whose monitoring data are to be exported. parity-group-id is a parity group ID. exg-id is an ID of an external volume group. You can check to which group each LDEV belongs in the Logical Devices window. The colon (:) indicates a range. For example, 1-1:1-5 indicates parity groups from 1-1 to 1-5. E1-1:E1-5 indicates external volume groups from E1-1 to E1-5. Ensure that the parity-group-id, or exg-id value on the left of the colon is smaller than the parity-group-id, or exg-id value on the right of the colon. For example, you can specify PG 1-1:1-5, but you cannot specify PG 1-5:1-1. Also, you can specify PG 1-5:2-1, but you cannot specify PG 2-1:1-5. If neither parity-group-id, nor exg-id is specified, the statistics of all parity groups and external volume groups will be exported. |
|
LDEV [[[parity-group-id|exg-id]: [parity-group-id||exg-id]][…] |internal|virtual]| |
Use this operand when you want to export statistics about volumes, which are displayed in the Monitor Performance window. When statistics are exported to a ZIP file, multiple ZIP files whose names are beginning with LDEV_ will be output. For details on the statistics exported by this operand, see Files with statistics about ports. When you specify variables parity-group-id, or exg-id, you can narrow the range of parity groups, or external volume groups whose monitoring data are to be exported. parity-group-id is a parity group ID. exg-id is an ID of an external volume group. You can check to which group each LDEV belongs in the Logical Devices window. The colon (:) indicates a range. For example, 1-1:1-5 indicates parity groups from 1-1 to 1-5. E1-1:E1-5 indicates external volume groups from E1-1 to E1-5. Ensure that the parity-group-id, or exg-id value on the left of the colon is smaller than the parity-group-id, or exg-id value on the right of the colon. For example, you can specify LDEV 1-1:1-5, but you cannot specify LDEV 1-5:1-1. Also, you can specify LDEV 1-5:2-1, but you cannot specify LDEV 2-1:1-5. If internal is specified, you can export statistics about volumes in the parity group. If virtual is specified, you can export statistics about volumes in the external volume group. If neither parity-group-id, nor exg-id is specified, the statistics of all parity groups and external volumes will be exported. Either one of the following values can be specified:
|
|
LDEVEachOfCU[[[LDKC-CU-id]:[LDKC-CU-id]][…]| internal|virtual] |
Use this operand when you want to export statistics about volumes which are displayed in the Monitoring Performance window. By using this operand, you can export monitoring data at volumes controlled by a particular CU. When statistics are exported to a ZIP file, multiple ZIP files whose names are beginning with LDEV_ will be output. For details on the statistics exported by this operand, see Files with statistics about volumes in parity groups or external volume groups (volumes controlled by a particular CU). When you specify variables LDKC-CU-id, you can narrow the range of LDKC:CUs that control the volumes whose monitoring data are to be exported. LDKC-CU-id is an ID of a LDKC:CU. The colon (:) indicates a range. For example, 000:105 indicates LDKC:CUs from 00:00 to 01:05. Ensure that the LDKC-CU-id value on the left of the colon is smaller than the LDKC-CU-id value on the right of the colon. For example, you can specify LDEVEachOfCU 000:105, but you cannot specify LDEVEachOfCU 105:000. If internal is specified, you can export statistics about volumes in the parity group. If virtual is specified, you can export statistics about volumes in the external volume or V-VOL. If LDKC-CU-id, internal or virtual is not specified, the monitoring data of all volumes will be exported. Either one of LDKC-CU-id, internal, or virtual can be specified. |
|
Port [[port-name]:[port-name]][…] |
Use this operand when you want to export port statistics, which are displayed in the Monitor Performance window. When statistics are exported in a ZIP file, the file name will be Port_dat.ZIP. For details on the statistics exported by this operand, see Files with statistics about ports. When you specify variables port-name, you can narrow the range of ports whose monitoring data are to be exported, where port-name is a port name and the colon (:) indicates a range. For example, CL3-a:CL3-c indicates ports from CL3-a to CL3-c. Ensure that the port-name value on the left of the colon is smaller than the port-name value on the right of the colon. The smallest port-name value is CL1-A and the largest port-name value is CL4-r. The following formula illustrates which value is smaller than which value: CL1-A < CL1-B < … < CL2-A < CL2-B < … < CL3-a < CL3-b < … < CL4-a < … < CL4-r For example, you can specify Port CL1-C:CL2-A, but you cannot specify Port CL2-A:CL1-C. Also, you can specify Port CL3-a:CL3-c, but you cannot specify Port CL3-c:CL3-a. If port-name is not specified, the monitoring data of all ports will be exported. |
|
PortWWN[[port-name]:[port-name]][…] |
Use this operand when you want to export statistics about host bus adapters (WWNs) connected to ports, which are displayed in the Monitor Performance window. When statistics are exported in a ZIP file, the file name will be PortWWN_dat.ZIP. For details on the statistics exported by this operand, see Files with statistics about ports. When you specify variables port-name, you can narrow the range of ports whose monitoring data are to be exported. port-name is a port name. The colon (:) indicates a range. For example, CL3-a:CL3-c indicates ports from CL3-a to CL3-c. Ensure that the port-name value on the left of the colon is smaller than the port-name value on the right of the colon. The smallest port-name value is CL1-A and the largest port-name value is CL4-r. The following formula illustrates which value is smaller than which value: CL1-A < CL1-B < … < CL2-A < CL2-B < … < CL3-a < CL3-b < … < CL4-a < … < CL4-r For example, you can specify PortWWN CL1-C:CL2-A, but you cannot specify PortWWN CL2-A:CL1-C. Also, you can specify PortWWN CL3-a:CL3-c, but you cannot specify PortWWN CL3-c:CL3-a. If port-name is not specified, the monitoring data of all host bus adapters will be exported. |
|
LU[[port-name.host-group-id]:[port-name.host-group-id]][…] |
Use this operand when you want to export statistics about LU paths, which are displayed in the Monitor Performance window. When statistics are exported in a ZIP file, the file name will be LU_dat.ZIP. For details on the statistics exported by this operand, see Files with statistics about volumes (LUs). When you specify variables port-name.host-group-id, you can narrow the range of LU paths whose monitoring data are to be exported. port-name is a port name. host-group-id is the ID of a host group (that is, a host storage domain). The host group (host storage domain) ID must be a hexadecimal numeral. The colon (:) indicates a range. For example, CL1-C.01:CL1-C.03 indicates the range from the host group #01 of the CL1-C port to the host group #03 of the CL1-C port. Ensure that the value on the left of the colon is smaller than the value on the right of the colon. The smallest port-name value is CL1-A and the largest port-name value is CL4-r. The following formula illustrates which port-name value is smaller than which port-name value: CL1-A < CL1-B < … < CL2-A < CL2-B < … < CL3-a < CL3-b < … < CL4-a < … < CL4-r For example, you can specify LU CL1-C.01:CL2-A.01, but you cannot specify LU CL2-A.01:CL1-C.01. Also, you can specify LU CL1-C.01:CL1-C.03, but you cannot specify LU CL1-C.03:CL1-C.01. If port-name.host-group-id is not specified, the monitoring data of all LU paths will be exported. |
|
PPCGWWN[[Monitor-target-name]:[Monitor-target-name]][…] |
Use this operand when you want to export statistics about all host bus adapters connected to ports, which are displayed in the Monitor Performance window. When statistics are exported in a ZIP file, the file name will be PPCGWWN_dat.ZIP. For details on the statistics exported by this operand, see Files with statistics about host bus adapters belonging to SPM groups. When you specify variables monitor-target-name, you can narrow the range of monitoring target groups whose monitoring data are to be exported. Monitor-target-name is the name of an monitoring target group. If the name includes any non-alphanumeric character, the name must be enclosed by double quotation marks ("). The colon (:) indicates a range. For example, Grp01:Grp03 indicates a range of SPM groups from Grp01 to Grp03. Ensure that the monitor-target-name value on the left of the colon is smaller than the monitor-target-name value on the right of the colon. Numerals are smaller than letters and lowercase letters are smaller than uppercase letters. In the following formulas, values are arranged so that smaller values are on the left and larger values are on the right:
If monitor-target-name is not specified, the monitoring data of all host bus adapters will be exported. |
|
RemoteCopy |
Use this operand when you want to export statistics about remote copy operations of TrueCopy or global-active device. By using this operand, you can export monitoring data about remote copy operations performed by TC and GAD in the whole volumes. When statistics are exported to a ZIP file, the file name will be RemoteCopy_dat.ZIP. For details on the statistics exported by this operand, see Files with statistics about remote copy operations by TC or GAD (whole volumes). |
|
RCLU[[port-name.host-group-id]:[port-name.host-group-id]][…] |
Use this operand when you want to export statistics about remote copy operations of TrueCopy or global-active device. By using this operand, you can export monitoring data about remote copy operations performed by TC and GAD at each volume (LU). When statistics are exported to a ZIP file, the file name will be RCLU_dat.ZIP. For details on the statistics exported by this operand, see Files with statistics about remote copy operations by TC or GAD (for each volume (LU)). When you specify variables Ensure that the value on the left of the colon is smaller than the value on the right of the colon. The smallest port-name value is CL1-A and the largest port-name value is CL4-r. The following formula illustrates which port-name value is smaller than which port-name value: CL1-A < CL1-B < … < CL2-A < CL2-B < … < CL3-a < CL3-b < … < CL4-a < … < CL4-r For example, you can specify RCLU CL1-C.01:CL2-A.01, but you cannot specify RCLU CL2-A.01:CL1-C.01. Also, you can specify RCLU CL1-C.01:CL1-C.03, but you cannot specify RCLU CL1-C.03:CL1-C.01. If port-name.host-group-id is not specified, the monitoring data of all volumes (LUs) will be exported. |
|
RCLDEV[[LDKC-CU-id]:[LDKC-CU-id]][…]| |
Use this operand when you want to export statistics about remote copy operations of TrueCopy or global-active device. By using this operand, you can export monitoring data about remote copy operations performed by TC and GAD at volumes controlled by each CU. When statistics are exported to a ZIP file, multiple ZIP files whose names are beginning with RCLDEV_ will be output. For details on the statistics exported by this operand, see Files with statistics about remote copy operations by TC or GAD (volumes controlled by a particular CU). When you specify variables LDKC-CU-id, you can narrow the range of LDKC:CUs that control the volumes whose monitoring data are to be exported. LDKC-CU-id is an ID of a LDKC:CU. The colon (:) indicates a range. For example, 000:105 indicates LDKC:CUs from 00:00 to 01:05. Ensure that the LDKC-CU-id value on the left of the colon is smaller than the LDKC-CU-id value on the right of the colon. For example, you can specify RCLDEV 000:105, but you cannot specify RCLDEV 105:000. If LDKC-CU-id is not specified, the monitoring data of all volumes will be exported. |
|
UniversalReplicator |
Use this operand when you want to export statistics about remote copy operations of UR. By using this operand, you can export monitoring data about remote copy operations performed by Universal Replicator in the whole volume. When statistics are exported to a ZIP file, the file name will be UniversalReplicator.zip. For details on the statistics exported by this operand, see Files with statistics about remote copy operations by UR (In the whole volumes). |
|
URJNL[[JNL-group-id]:[JNL-group-id]][…] |
Use this operand when you want to export statistics about remote copy operations of UR. By using this operand, you can export monitoring data about remote copy operations performed by Universal Replicator at each journal. When statistics are exported to a ZIP file, the file name will be URJNL_dat.ZIP. For details on the statistics exported by this operand, see Files with statistics about remote copy operations by UR (journals). When you specify variables JNL-group-id, you can narrow the range of journals whose monitoring data are to be exported. JNL-group-id is a journal number. The colon (:) indicates a range. For example, 00:05 indicates journals from 00 to 05. Ensure that the JNL-group-id value on the left of the colon is smaller than the JNL-group-id value on the right of the colon. For example, you can specify URJNL 00:05, but you cannot specify URJNL 05:00. If JNL-group-id is not specified, the monitoring data of all journal volumes will be exported. |
|
URLU[[port-name.host-group-id]:[port-name.host-group-id]][…] |
Use this operand when you want to export statistics about remote copy operations of UR. By using this operand, you can export monitoring data about remote copy operations performed by Universal Replicator at each volume (LU). When statistics are exported to a ZIP file, the file name will be URLU_dat.ZIP. For details on the statistics exported by this operand, see Files with statistics about remote copy operations by UR (for each volume (LU)). When you specify variables Ensure that the value on the left of the colon is smaller than the value on the right of the colon. The smallest port-name value is CL1-A and the largest port-name value is CL4-r. The following formula illustrates which port-name value is smaller than which port-name value: CL1-A < CL1-B < … < CL2-A < CL2-B < … < CL3-a < CL3-b < … < CL4-a < … < CL4-r For example, you can specify URLU CL1-C.01:CL2-A.01, but you cannot specify URLU CL2-A.01:CL1-C.01. Also, you can specify URLU CL1-C.01:CL1-C.03, but you cannot specify URLU CL1-C.03:CL1-C.01. If port-name.host-group-id is not specified, the monitoring data of all volumes (LUs) will be exported. |
|
URLDEV [[LDKC-CU-id]:[LDKC-CU-id]][…] |
Use this operand when you want to export statistics about remote copy operations which of UR. By using this operand, you can export monitoring data about remote copy operations performed by Universal Replicator at volumes controlled by each CU. When statistics are exported to a ZIP file, multiple ZIP files whose names are beginning with URLDEV_ will be output. For details on the statistics exported by this operand, see Files with statistics about remote copy operations by UR (volumes controlled by a particular CU). When you specify variables LDKC-CU-id, you can narrow the range of LDKC:CUs that control the volumes whose monitoring data are to be exported. LDKC-CU-id is an ID of a LDKC:CU. The colon (:) indicates a range. For example, 000:105 indicates LDKC:CUs from 00:00 to 01:05. Ensure that the LDKC-CU-id value on the left of the colon is smaller than the LDKC-CU-id value on the right of the colon. For example, you can specify URLDEV 000:105, but you cannot specify URLDEV 105:000. If LDKC-CU-id is not specified, the monitoring data of all volumes will be exported. |
|
PhyMPPK |
Use this operand when you want to export statistics about the MP usage rate of each resource allocated to MP units. When statistics are exported to a ZIP file, the filename is PHY_MPPK.ZIP. For details on the statistics exported by this operand, see Files with statistics about host bus adapters belonging to SPM groups |
Examples
The following example exports statistics about host bus adapters:
group PortWWN
The following example exports statistics about three ports (CL1-A, CL1-B, and CL1-C):
group Port CL1-A:CL1-C
The following example exports statistics about six ports (CL1-A to CL1-C, and CL2-A to CL2-C)
group Port CL1-A:CL1-C CL2-A:CL2-C
The following example exports statistics about the parity group 1-3:
group PG 1-3:1-3
The following example exports statistics about the parity group 1-3 and other parity groups whose ID is larger than 1-3 (for example, 1-4 and 1-5):
group PG 1-3:
The following example exports statistics about the external volume groups E1-1 to E1-5:
group PG E1-1:E1-5
The following example exports statistics about the parity group 1-3 and other parity groups whose ID is smaller than 1-3 (for example, 1-1 and 1-2):
group LDEV:1-3
The following example exports statistics about LU paths for the host group (host storage domain) ID 01 for the port CL1-A:
group LU CL1-A.01:CL1-A.01