Use the chpartnership command to modify the bandwidth of the
partnership between the local system and the remote system that is specified in the command. This
affects the bandwidth that is available for background copy in a system partnership by either
Metro Mirror or Global Mirror operations. Additionally, use this command to disable and re-enable
the partnership, which allows the local system to be disconnected and then reconnected to the
remote system.
Syntax
chpartnership { -start | -stop } { remote_cluster_id | remote_cluster_name }
chpartnership [ -type { ipv4 | ipv6 } ] [ -clusterip { newipv4addr | newipv6addr } ] [ -chapsecretnewCHAPsecret ] [ -nochapsecret ] [ -backgroundcopyratepercentage ] [ -linkbandwidthmbitslink_bandwidth_in_mbps ] [ -compressed { yes | no } ] { remote_cluster_id | remote_cluster_name }
Parameters
- -start | -stop
- (Optional) Starts or stops a Metro Mirror or Global Mirror partnership. To start or stop a
partnership, run the chpartnership command from either system.
- -typeipv4 | ipv6
- (Optional) Specifies the Internet Protocol (IP) address format for the partnership using
either of these case-sensitive strings:
- ipv4 for Internet Protocol Version 4 (IPv4)
- ipv6 for Internet Protocol Version 6 (IPv6)
This migrates a partnership from ipv4 to ipv6 or
vice versa.
- -clusteripnewipv4addr | newipv6addr
- (Optional) Specifies the new partner system IP address, either ipv4 or
ipv6. Systems 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 chapartnership
-stop to stop the partnership.
- -chapsecretnewCHAPsecret
- (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).
- -backgroundcopyratepercentage
- (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).
- -linkbandwidthmbitslink_bandwidth_in_mbps
- (Optional) Specifies the aggregate bandwidth of the RC link between two clustered systems
(systems) in megabits per second (Mbps). It is a numeric value from 1 to
100000, specified in Mbps.
Important: For partnerships over IP
links with compression, this parameter specifies the aggregate bandwidth after the
compression had been applied to the data. Do not set this parameter higher than the physical
link bandwidth multiplied by the (carefully rounded down) compression factor.
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.
- -compressedyes | no
- (Optional) Specifies whether compression is enabled for this partnership. The default value
is 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.
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
This command modifies the bandwidth of the partnership between the local system and the remote
system specified in the command. This affects the bandwidth available for a background copy in
Metro Mirror or Global Mirror relationships (from the local to the remote system) . To modify
the background copy bandwidth from remote system to local system, issue
chpartnership a second time for the remote system.
Important: For partnerships over IP links with compression, this parameter specifies
the aggregate bandwidth after the compression had been applied to the data. Do not set this
parameter higher than the physical link bandwidth multiplied by the (carefully rounded down)
compression factor.
Change the CHAP secret or system IP for partnerships created using IP links. Before changing
the partner CHAP secret or system IP, stop the partnership.
If a stop partnership is
issued, the state is
not_present briefly before it changes to
fully_configured_stopped.
Important: - If you start with a fully configured remote copy partnership, the state (as reported by
lspartnership) is fully_configured.
- If a stop partnership is issued, the state is not_present (typically for
ten seconds or less) before it becomes fully_configured_stopped.
After making the necessary changes, start the partnership.
The system
partnership must be in either the partially_configured_stopped or
fully_configured_stopped states to be started.
Note: The local and remote
systems in an IP partnership must use the same IP address types, IPv4 or IPv6.
An invocation
example
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 -type ipv6 –clusterip fe80::200:f8ff:fe21:67cf 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 –chapsecret newpassword 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