>>- svcinfo -- -- lscluster -- ---------------------------------> >--+--------------------------------+-- --+----------+-- -------> '- -filtervalue -- attrib=value -' '- -nohdr -' >--+----------+-- --+-----------------------+-- ----------------> '- -bytes -' '- -delim -- delimiter -' >--+-------------+-- --+-----------------+--------------------->< +- object_id -+ '- -filtervalue? -' '- name ------'
| Note: If there is no data to be displayed (for example, an empty view has been returned), then headings are not displayed irrespective of whether the -nohdr option was used or not. |
This command will return a concise list or a detailed view, of clusters.
The following list provides possible values that are applicable to the attributes that are displayed as data in the output views:
| location | local, remote |
| statistics status | on, off |
| SNMP setting | none, all, hardware_only |
The location, partnership and bandwidth fields are relevant to Remote Copy configurations where the SAN fabrics of two clusters are linked together. Information about the remote cluster will be reported by the lscluster command if the mkpartnership command has been issued from the local cluster to the remote cluster, ie. if the partnership has been at least partially established from the local cluster.
You can issue the svcinfo lscluster command to display
a concise view of the cluster.
svcinfo lscluster -delim : 10030a007e5
where 10030a007e5 is the name of the
cluster. The output from this command will include the following for each
cluster on the fabric:
For the remote cluster, these fields indicate the following:
location: remote
partnership: partially_configured (mkpartnership command has only been
issued from the local cluster to the remote cluster)
fully_configured (mkpartnership command has been issued
in both directions)
bandwidth: MB/sec (the bandwidth available on the inter-cluster link for
background copy)
A concise invocation example
svcinfo lscluster -delim :
The concise resulting output
id:name:location:partnership:bandwidth:cluster_IP_address:
id:name:location:partnership:bandwidth:cluster_IP_address:
cluster_service_ip_address:id_alias
0000020062813ABA:clusterA:local:::9.20.247.210:1.1.1.1:0000020062813ABA
0000020062006746:clusterB:remote:fully_configured:50:9.20.247.211:
1.1.1.1:0000020062006746
A detailed invocation example
svcinfo lscluster -delim : 10030a007e5
The detailed resulting output
id:1521071282978998 name:cluster1 location:local partnership: bandwidth: cluster_IP_address:9.20.165.16 cluster_service_IP_address:9.20.165.17 total_mdisk_capacity:59.8GB space_in_mdisk_grps:0 space_allocated to vdisks:0 total_free_space:59.8GB statistics_status:on statistics_frequency:300 required_memory:1280 subnet_mask:255.255.255.0 default_gateway:9.20.165.1 cluster_locale:en_US SNMP_setting:snmp all SNMP_community: SNMP_server_IP_address:9.20.165.18 time_zone:522 UTC email_setting:all email_id:another@uk.ibm.com code_level:1.20abcG FC_port_speed:1Gb id_alias:1521071282978998
A concise invocation example for a Remote Copy configuration, where clusterA has issued the mkpartnership to clusterB, and the intercluster bandwidth is set to 50 MB/s.
svcinfo lscluster -delim :
The concise resulting output
id:name:location:partnership:bandwidth: cluster IP address:cluster service IP address 0000020062813ABA:clusterA:local:::9.20.247.210:1.1.1.1 0000020062006746:clusterB:remote: fully_configured:50:9.20.247.211:1.1.1.1