lspartnership

Use the lspartnership command to display a concise or detailed view of the current clustered systems (systems) that are associated with the local system.

Syntax

lspartnership [ -filtervalueattribute=value ] [ -filtervalue? ] [ { system_id | system_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.

Some filters allow the asterisk character (*) when you enter the command. The following rules apply to the use of wildcard characters with the SAN Volume Controller command-line interface (CLI):
- The wildcard character is an asterisk (*).
- The command can contain a maximum of one wildcard.
- When you use a wildcard, you must enclose the filter entry within double quotation marks (""):
```
lspartnership -filtervalue "name=md*"
```

-filtervalue?

(Optional) displays a list of filters that can be applied against this view. The following filter attributes are valid:

id
name

system_id | system_name

(Optional) Specifies the name or ID of a system. Using this parameter displays the detailed view of the specific partner system, and any value specified by the -filtervalue (which filters a view that is based on specific attribute values that relate to each object type) parameter is ignored. When specifying system_id or system_name parameter, the concise view of all systems that match the filtering requirements that are specified by the -filtervalue parameter are displayed.

Description

Table 1 described attribute values.

Table 1. lspartnership attribute values
Attribute	Value
id	Indicates the system ID.
name	Indicates the system name.
location	Indicates the system location.
code_level	Indicates the code level.
partnership	Indicates the current state of the partnership; not applicable for the local system and is blank. The partnership field can show the following values: fully_configured The mkfcpartnership or mkippartnership command has been issued in both directions and the remote system is online and available. partially_configured_local The mkfcpartnership or mkippartnership command has only been issued from the local system to the remote system. The remote system is online and available for partnership. partially_configured_local_stopped The mkfcpartnership or mkippartnership command has only been issued from the local system to the remote system. The chpartnership command with the stop parameter has been issued from the local system, and the remote system is online and available. Issue chpartnership -start on the local system, and mkfcpartnership or mkippartnership on the remote system not_present The mkfcpartnership or mkippartnership command has been issued from the local system to the remote system, and the remote system is not available. The remote system is either offline or not connected to the local system. fully_configured_stopped The mkfcpartnership or mkippartnership command has been issued in both directions and the remote system is online and available. The chpartnership command with the stop parameter has been issued from the local system. fully_configured_remote_stopped The mkfcpartnership or mkippartnership command has been issued in both directions and the remote system is online and available. The chpartnership command with the stop parameter has been issued from the remote system. fully_configured_local_excluded The mkfcpartnership or mkippartnership command has been issued in both directions. The local system excludes the connection to the remote system and the partnership is unable to sustain the I/O workload for the Metro Mirror or Global Mirror relationships. fully_configured_remote_excluded The mkfcpartnership or mkippartnership command has been issued in both directions. The local system excludes the connection to the remote system and the partnership is unable to sustain the I/O workload for the Metro Mirror or Global Mirror relationships. fully_configured_exceeded There are too many systems in the system network and the partnership from the local system to the remote has been disabled.
relationship_bandwidth_limit	Indicates the current bandwidth limit.
type	Indicates the type of partnership: Fibre Channel (FC) Internet Protocol Version 4 (IPv4) or Internet Protocol Version 6 (IPv6) FC partnerships are created connecting two systems over FC or Fibre Channel over Ethernet (FCoE) fabrics. IPv4 or IPv6 partnerships are created connecting two systems over native IP links.
cluster_ip	Indicates the partner system IP address, which can be IPv4 or IPv6. This information is displayed for IP-based partnerships. For IP-based partnership this field displays the system IP address specified while creating the partnership using mkippartnership.
chap_secret	Indicates the Challenge-Handshake Access Protocol (CHAP) secret (up to eighty alphanumeric characters) for the partner system. The CHAP authenticates the local system with the partner system during discover and Internet Small Computer System Interface (iSCSI) system session creation. For FC-based and FCoE-based relationships this field is always blank.
link_bandwidth_mbits	Indicates the aggregate bandwidth for the Remote Copy (RC) link in megabits per second (Mbps). This is a numeric value from `0` to `100000`. If there are multiple links between the local and remote systems, this parameter is set to the sum of the link bandwidths for these links.
background_copy_rate	Indicates the bandwidth allocation for background copy operations performed over the replication link. It is expressed as a percentage of the link bandwidth value, and is the maximum rate at which background copy operations are performed. This is a numeric value from `0` to `100` .
event_log_sequence	Indicates the last sequence number (indicating the last event) from event log for this partnership. This is a numeric value from `100` to `8000000`. For FC-based and FCoE-based relationships this field is always blank.
max_replication_delay	Indicates the value for maximum replication delay. This is a numeric value from `0` to `360`.

A concise invocation example

lspartnership

The concise resulting output:

id                name      location  partnership                type  cluster_ip                  event_log_sequence
000002006BC0A0D4  system-1  local
000002006200A0E5  system-2  remote    partially_configured_local ipv6  fe80::200:f8ff:fe21:67cf
000002006200A0F6  system-3  remote    partially_configured_local fc                                
000002006200A0G7  system-4  remote    partially_configured_local fc

A detailed invocation example

lspartnership cluster-2

The detailed resulting output:

id 000002006200A0EA
name system-2
location remote
partnership partially_configured_local
code_level 6.3.0.0 (build 35.7.1105071000)
console_IP 9.180.28.63:443
gm_link_tolerance 300
gm_inter_system_delay_simulation 0
gm_intra_system_delay_simulation 0
relationship_bandwidth_limit 25
gm_max_host_delay 5
type fc
cluster_ip
chap_secret
event_log_sequence
link_bandwidth_mbits 1024
background_copy_rate 25max_replication_delay 145