chpartnership

Use the chpartnership command to update properties that are related to a partnership between the local system and the remote system.

Syntax

Read syntax diagramSkip visual syntax diagram chpartnership -start-stop-clusteripnewipv4addrnewipv6addrnewfqdnaddr-chapsecretnewCHAPsecret-nochapsecret-newclusteridnew cluster ID from the recovered cluster-backgroundcopyratepercentage-linkbandwidthmbitslink_bandwidth_in_mbps-compressedyesno-link1portsetid1portsetname1-link2portsetid2portsetname2-nolink1-nolink2-securedyes | no-pbrinuseyesnoremote_cluster_idremote_cluster_name

Parameters

-start | -stop
(Optional) Starts or stops a partnership. To start or stop a partnership, run the chpartnership command from either system.
-clusterip newipv4addr | newipv6addr | newfqdnaddr
(Optional) Specifies the new partner system IP address, which can be IPv4, IPv6 or FQDNs. Systems that are connected over IP links are not displayed by lspartnershipcandidate before executing mkippartnership. This does not apply to FC-based or FCoE-based connections.

Specify this parameter when creating partnerships with systems connected over native IP links. To change the partner system IP address, first specify chpartnership -stop to stop the partnership.

-chapsecret newCHAPsecret
(Optional) Specifies the new Challenge-Handshake Authentication Protocol (CHAP) secret of the partner system. The maximum size of the CHAP secret is eighty alphanumeric characters.
-nochapsecret
(Optional) Resets the CHAP secret used to authenticate with the partner system. Specify chpartnership -stop to stop the partnership. Reset the CHAP secret of the partner system when authentication of discovery requests is turned off on the partner system .
-newclusterid new cluster ID from the recovered cluster
(Optional) Specifies the new cluster ID for a partnered system. Use this parameter on the local system to recover the partnership to a remote system after completing a system recovery, also known as Tier 3 (T3) recovery, on the remote system.
Note: This parameter is mutually exclusive with all other parameters. Use this parameter only under the direction of IBM® Support Center.
-backgroundcopyrate percentage
(Optional) Deprecated. This value is ignored by the system.
-linkbandwidthmbits link_bandwidth_in_mbps
(Optional) Specifies the aggregate bandwidth of the replication link between two clustered systems (systems) in megabits per second (Mbps). It is a numeric value from 1 to 100000, specified in Mbps. Asynchronous replication will aim to not exceed this value when replicating to the partnered systems. High availability will consume as much bandwidth as needed to maintain two copies of the storage partition and is not limited by this value.
Note: when using IP compression, on hardware platforms that do not have hardware compression capabilities, -linkbandwidthmbits link_bandwidth_in_mbps has limitation up to 1120 megabits per second (Mbps)

This parameter can be specified without stopping the partnership. This command is mutually-exclusive with all parameters other than -backgroundcopyrate.

-compressed yes | no
(Optional) Specifies whether compression is enabled for this partnership. The default value is no.

The following parameters are mutually exclusive with IP partnerships:

-link1 portsetid1 | portsetname1
(Optional) Specifies the portset id or name to be used for WAN link 1.
-link2 portsetid2 | portsetname2
(Optional) Specifies the portset id or name to be used for WAN link 2.
-nolink1
(Optional) Specifies the removal of the portset id or name specified for WAN link 1.
-nolink2
(Optional) Specifies the removal of the portset id or name specified for WAN link 2.
Note: A partnership is required to have at lease one active link between systems. You must have a portset defined in either -link1 or -link2 parameters for the systems. You cannot delete both portsets from -link1 and -link2.
-secured yes | no
(Optional) Specifies whether to use encryption to secure the connection between systems in the IP partnership. If -secured parameter is not specified, the connection between systems in the IP partnership will not be secured. If -secured parameter is specified, the value yes or no is mandatory.
-pbrinuse yes | no
(Optional) Specifies whether policy-based replication will be used on the partnership. The value can be yes or no.
remote_cluster_ID | remote_cluster_name
(Required) Specifies the remote system ID or name of a partnership. The specified value must match one of the system IDs or names returned after issuing lspartnershipcandidate. The specified value must match one of the system IDs or names listed by lspartnership. Specifying a remote system ID or name with chpartnership does not affect the remote system. To change the system name, specify chsystem

Description

The chpartnership command modifies the properties of a partnership. Properties that can be changed include:
  • The bandwidth of the partnership (specified using the -linkbandwidthmbits option). This affects the bandwidth available replication between the local system and the remote system specified in the partnership. To modify the background copy bandwidth from the remote system to local system, issue the chpartnership command a second time for the remote system.
  • Whether the partnership is started or stopped (specified using the -start and -stop options). This starts or stops replication between the local system and the remote system specified in the partnership. System partnership must be in either the partially_configured_stopped or fully_configured_stopped states to be started.
  • The CHAP secret (specified using the -chapsecret option) or the system IP (specified using the -clusterip option) for partnerships created using IP links. Before changing the partner CHAP secret or system IP, stop the partnership; and after making the necessary changes, start the partnership.
Note: The local and remote systems in an IP partnership must use the same IP address types, IPv4 or IPv6.

An invocation example to configure a new CHAP secret for a partner.

chpartnership –stop remote-system-2
chpartnership –chapsecret newpassword remote-system-2
chpartnership –start remote-system-2

The resulting output: 

No feedback