chpartnership

Edit online

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

Syntax

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 (by specifying chsystem -rcauthmethod).
-backgroundcopyrate percentage: (Optional) Specifies the maximum percentage of aggregate link bandwidth that can be used for background copy operations. This parameter can be specified without stopping the partnership. The percentage is a numeric value from 0 to 100, and the default value is 50, which means that a maximum of 50% of the aggregate link bandwidth can be used for background copy operations. This command is mutually-exclusive with all parameters other than -linkbandwidthmbits.
Note: If the specified value is non-zero, the combination of both the -backgroundcopyrate and the -linkbandwidthmbits values must result in a background copy bandwidth of at least 8 megabits per second (Mbps).
On hardware platforms that do not have hardware compression capabilities, the -linkbandwidthmbits has limitation upto 1120 Mbps when using IP compression.
-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.
Note: when using IP compression, on hardware platforms that do not have hardware compression capabilities, -linkbandwidthmbits link_bandwidth_in_mbps has limitation upto 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.
Note: If the specified value is non-zero, the combination of both the -backgroundcopyrate and the -linkbandwidthmbits values must result in a background copy bandwidth of at least 8 Mbps.
-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.

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.

Remember: Specifying a remote system ID or name with chpartnership does not affect the remote system. To change the system name, specify chsystem.

To configure the maximum bandwidth available for Metro Mirror intrasystem relationships, specify:

A local system ID or name.
The -linkbandwidthmbps and -backgroundcopyrate parameters.

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 stop replication on the partnership.

chpartnership -stop cluster1

The resulting output:

No feedback

An invocation example to change the allocated background copy rate.

chpartnership -backgroundcopyrate 20 remote-system-2

The resulting output:

No feedback

An invocation example to change the link bandwidth.

chpartnership -linkbandwidthmbits 1024 remote-system-2

The resulting output:

No feedback

An invocation example to migrate existing partnership from IPv4 to IPv6 type.

chpartnership -stop remote-sys-2
chpartnership –clusterip xxxx::xxx:xxxx:xxxx:xxxx remote-sys-2

The resulting output:

No feedback

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

An invocation example to configure a new system IP.

chpartnership -stop remote-system-2
chpartnership –clusterip 202.49.86.2 remote-system-2
chpartnership –start remote-system-2

The resulting output:

No feedback

An invocation example setting the aggregate bandwidth and background copy rate.

chpartnership -linkbandwidthmbits 2048 -backgroundcopyrate 100 localCluster

The resulting output:

No feedback

An invocation example enabling compression on an IP replication link.

chpartnership -compressed yes svtcluster1

The resulting output:

No feedback

An invocation example to modify portset associated with WAN link 1.

chpartnership -link1 5 svtcluster1

The resulting output:

No feedback

An invocation example to remove portset associated with WAN link 1.

chpartnership -nolink1 svtcluster1

The resulting output:

No feedback

An invocation example to remove portset associated with WAN link 2. This is allowed only when WAN links 1 and 2 have portset IDs associated with this partnership.

chpartnership -nolink2 svtcluster1

The resulting output:

No feedback